AIX Linux
After installing the reporting and monitoring agent, you can manually create and configure the reporting and monitoring agent instance using the command-line interface method.
Before you create and configure your agent instance you must increase the Java heap size from 64 MB to 128 MB.
v Save a copy of the kskprov.sh file:/opt/tivoli/tsm/reporting/itm/
ITM_BINARCH/sk/bin/kskprov.sh
v Add-Xmx128mto the following line in thekskprov.shscript.
$JAVA_HOME/bin/java -cp $CANDLEHOME/$ITM_BINARCH/sk/bin/adminapi.jar:$CANDLEHOME/ $ITM_BINARCH/sk/bin/cpci.jar:$CANDLEHOME/$ITM_BINARCH/sk/bin/derby.jar:
$CANDLEHOME/$ITM_BINARCH/sk/bin/TSMCustomClient.jar -Xmx128m com.ibm.tivoli. monitoring.TSMAgent.TSMCustomClient
Note: Increase the heap size in 64 MB increments if 128 MB is not sufficient. Create and configure your agent instance using this command-line interface method, or you can use the CandleManage graphical interface method: “Creating and configuring the reporting and monitoring agent instance using
CandleManage” on page 30.
If you must monitor multiple Tivoli Storage Manager servers from the same IBM Tivoli Monitoring server, create an instance of the reporting and monitoring agent using the following method for each Tivoli Storage Manager server you want to monitor. If you install the reporting and monitoring agent on your Tivoli Storage Manager servers, you do this task once, for each Tivoli Storage Manager server where the reporting and monitoring agent is installed.
Note: The term,reporting agent, that is displayed in the following examples is synonymous with the reporting and monitoring agent.
To configure a reporting and monitoring agent instance using the command-line interface, complete the following steps:
1. Run the following command from the directory where you installed the reporting and monitoring agent. The default directory is: /opt/Tivoli/TSM/ Reporting/itm/bin.
itmcmd config -A -t sk
The command returns the following instruction: Enter the instance name
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
2. Enter a name for the reporting and monitoring agent instance, for example: myinstance
The command returns the following question:
Edit "Monitoring Agent for Tivoli Storage Manager" settings? [ 1=Yes, 2=No ] (default is: 1): myserver.mycompany.com 3. Enter1. The command returns the following question:
Edit ’TSM Server Connection Information’ settings? [ 1=Yes, 2=No ] (default is: 1):
4. Enter1. The command returns the following prompts for your response: Server Address (default is: ):
Port Number (default is: 1500): TSM Administrator (default is: ):
TSM Administrator Password (default is: ):
5. For the Server Address, enter the address of the Tivoli Storage Manager server to be monitored.
6. For the Port Number, take the default or enter another port number. 7. For the TSM Administrator ID, enter the Tivoli Storage Manager
administrator ID to access the server where the monitoring agent is installed. 8. For the TSM Administrator Password, enter the correct password for the
administrator ID. The command returns the following question: Will this agent connect to a TEMS?
[1=YES, 2=NO] (Default is: 1):
9. Enter1, and specify the name of the host that TEMS is installed on. The command returns the following prompts, for your response:
TEMS Host Name (Default is: sysback):
Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe): Now choose the next protocol number from one of these:
- ip - sna - ip.spipe - 0 for none
Network Protocol 2 (Default is: 0): IP.PIPE Port Number (Default is: 1918):
Enter name of KDC_PARTITION (Default is: null):
10. Enter a protocol name or enter the defaultip.pipe. The command returns the following information:
Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2):
11. To have this agent connect to another Tivoli Enterprise Monitoring Server, enter1. Otherwise, go to step 15 on page 34
If you entered 1to connect to another server, the command returns the following information:
Enter Optional Primary Network Name or 0 for "none" (Default is: 0):
The command returns the following information: Agent configuration completed...
| | | | | | | | | | | | | |
12. If the agent was installed separately on to an existing IBM Tivoli Monitoring server, you might need to seed the Tivoli Enterprise Monitoring server and Tivoli Enterprise Portal server, to allow it to pick up the new agent
configuration. Issue these commands: itmcmd config -A cq
itmcmd support -t tems_name sk
Tip: The itmcmd program is located in the bin directory under the ITM installed directory. The default is: /opt/IBM/ITM/bin.
13. Enter the following commands to stop and restart the Tivoli Enterprise Monitoring server, and the Tivoli Enterprise Portal server:
itmcmd server stop tems_server
itmcmd server start tems_server
14. Enter the following commands to stop and restart the agent: itmcmd agent stop cq
itmcmd agent start cq
15. Enter the following command to start the reporting and monitoring agent you configured in step 3 on page 33.
# itmcmd agent -o myinstance start sk
If successful, the command returns the following information: Starting Reporting Agent for Tivoli Storage Manager
Agent Started Successfully
If there is a problem with the reporting and monitoring agent instance starting, the command returns the following information:
Starting Reporting Agent for Tivoli Storage Manager ... KCIIN0198E Unable to start agent. Please, check log file. # exit
Related tasks