1. What are the Install support files on RTEMS?
bash-2.04$ ./installIraAgentTEMS.sh /opt/IBM/ITM
Loading TEMS support without restart requires 6.2 Fixpack 1 or higher and HUB TEMS information passed via -h, -u, and -p.
Restarting TEMS to activate support.
Stopping TEMS...
It can take up to ten minutes.
TEMS stopped...
Starting TEMS...
It can take up to ten minutes.
TEMS started...
Install of K1s TEMS support successful.
2. What are the install support files to TEPS?
bash-2.04$ ./installIraAgentTEPS.sh /IBM/ITM Installing k2s .....
Online help for this agent will not be available until the Help Server is restarted, which also requires restarting the TEPS.
3. What are the pre requisite for Agent Builder?
To install the Agent Builder, you must first install and have running one of the following operating systems:
• AIX 5.2 ML10 x86 (32-bit) or later
• AIX 5.3 ML5 x86 (32-bit) or later
• AIX 6.1
• AIX 7.1
• Red Hat Enterprise Linux 4.0 + U2 x86 (32-bit) or later
• Red Hat Desktop Linux 4.0 + U2 x86 (32-bit) or later
• Red Hat Enterprise Linux 5.0 x86 (32-bit)
• Red Hat Enterprise Linux 5.0 x86-64 (64-bit)
• Red Hat Enterprise Linux 6.0 x86 (32-bit)
• SUSE Linux Enterprise Server 9 Sp1 x86 (32-bit) or later
• SUSE Linux Enterprise Server 10 x86 (32-bit)
• SUSE Linux Enterprise Server 10 x86-64 (64-bit)
• SUSE Linux Enterprise Server 11 x86 (32-bit)
• SUSE Linux Enterprise Server 11 x86-64 (64-bit)
• Windows Server 2000
• Windows 2000 Advanced Server
• Windows Server 2003 EE x86 (32-bit)
• Windows Server 2003 SE x86 (32-bit)
• Windows Server 2003 Data Center x86 (32-bit)
• Windows Server 2003 EE x86-64 (64-bit)
• Windows Server 2003 SE x86-64 (64-bit)
• Windows Server 2003 Data Center x86-64 (64-bit)
• Windows XP Professional
• Windows Server 2008 Data Center x86 (32-bit)
• Windows Server 2008 EE x86 (32-bit
• Windows Server 2008 Data Center x86-64 (64-bit)
• Windows Server 2008 EE x86-64 (64-bit)
• Windows Server 2008 SE x86-64 (64-bit)
• Windows Server 2008 R2 Data Center x86-64 (64-bit)
• Windows Server 2008 R2 EE x86-64 (64-bit)
• Windows Server 2008 R2 SE x86-64 (64-bit)
• Windows 7 x86 (32-bit)
• Windows 7 x86-64 (64-bit)
• Windows Server 2008 SE x86 (32-bit)
Before you can run IBM Tivoli Monitoring Agent Builder, you must have Administrator authorization for the following reasons:
• Ability to ensure a consistent running environment for the Agent Builder and the agents designed with it.
• Ability to access parts of the operating system, which requires Administrator authorization. The Agent Builder is installed on a development system and is designed for developers who require this type of access
• Before installing the IBM Tivoli Monitoring Agent Builder, uninstall any previous versions. No data is lost when you uninstall.
4. Write the command to verify the agent running status?
Verify Agent Running Status:
Go to /IBM/ITM/bin and run the below command:
bash-3.2$ ./cinfo -r
*********** Wed Sep 28 12:03:30 IST 2011 ******************
User: itmuser Groups: staff
Host name : CNDAUSSDAPZP01 Installer Lvl:06.21.00.000
CandleHome: /IBM/ITM
***********************************************************
Host Prod PID Owner Start ID ..Status
CNDAUSSDAPZP01 ux 3539062 itmuser 12:03:12 None ...running
Also run the below command to verify the agent has establish the connection with RTEMS
bash-2.04$ netstat -an | grep IP
5. How to configure the Agent?
Login as itmuser and go to /IBM/ITM/bin folder and run the below mentioned command-
NOTE: In the below command the product code ux stands for Unix types of OS that includes AIX, HP Unix,Sun Solaris ect., For linux servers lz should be entered in place of ux. The same product code will be applicable for starting or stopping the agent. For simplicity use ./cinfo –I command as mentioned above to get the exact product code.
bash-2.04$ ./itmcmd config -A ux
Agent configuration started...
Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1):
TEMS Host Name (Default is: <serverhostname>): IP
Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe): ip.spipe
Now choose the next protocol number from one of these:
- ip
- sna
- ip.pipe
- 0 for none
Network Protocol 2 (Default is: ip.pipe): ip.pipe
Now choose the next protocol number from one of these:
- ip
- sna
- 0 for none
Network Protocol 3 (Default is: 0):
IP.PIPE Port Number (Default is: 1918):
Enter name of KDC_PARTITION (Default is: null):
IP.SPIPE Port Number (Default is: 3660):
Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2):
Enter Optional Primary Network Name or 0 for "none" (Default is: 0):
Are you installing this product into a clustered environment [1=YES, 2=NO] (Default is: 2):
KCIIN2569E ERROR: You are not running as root, and rexec is not enabled on this machine,
so your machine boot scripts cannot be updated automatically for you. Please re-run
this configuration session as root, or please manually run /opt/IBM/ITM/bin/UpdateAutoRun.sh as rootAgent configuration completed...
bash-2.04$
TCLI(Tivoli Command Line Interface)
• Most of the Tivoli operations can be performed on command line interface.
• Must setup/”source” the Tivoli environment first.
o /etc/Tivoli/setup_env.sh
o %systemroot%system32driversetctivolisetup_env.cmd
o Most commands begin with a w
o Must have the same authorization to perform operations from the CLI or the Tivoli Desktop.
o W+verb+object
--Wcrtgate/wdelgate
--Wsetpr
TMR means Tivoli Management Region. It is a set of systems that are managed by one server. Each TME has its unique set of clients. Tivoli does not support more then one TMR at a particular time, but you can interconnect one or more TMRs.
• TMR consist of :
o Tivoli Server
o 1 or more Managed Nodes/Gateways
o Tivoli Management Agents/Endpoints
8. What are the features of Business Service Management?
Business Service Management features the following products:
• IBM Tivoli Business Systems Manager.
• IBM Tivoli Service Level Advisor.
• IBM Tivoli Enterprise Console.
• IBM Tivoli Netview.
9. Give the categorization of IBM Tivoli Software Products?
IBM Tivoli Softwares are categorized into six areas:
• Availability
• Business Service Management
• Orchestration
• Provisioning
• Security Management
• Storage and Optimization solution
10. Give the steps to Configure qi agent?
i) Go to /IBM/ITM/config
ii) copy the qi.xmland create a new file as given below-
cp qi.xml <ServerHostname>_qi_<MSGBROKERID>.xml
eg : cp qi.xml CNDAEAI2APZP16_qi_BREIBP5.xml
iii) Edit the new file as shown below-
Enter the Message broker ID in the shown in bold character below
bash-3.2$ more CNDAEAI2APZP16_qi_BREIBP5.xml
<!--defaultPersistentBrokerData="NO"-->
<!--Agent performance during startup will be greatly enhanced if the defaultPersistentBrokerData parameter is set to YES.-->
<!--Note: the defaultReplyQueueModel parameter must be set to "SYSTEM.BROKER.INTERBROKER.MODEL.QUEUE" or the name of another permanent model q
ueue if the defaultPersistentBrokerData parameter is set to YES.-->
<!--When agent is not running, the subscription $SYS/Broker/<broker_label>/# and the reply queue used by the agent will continue to receive an
d store broker event messages ready for processing when the agent is restarted.-->
<!--You must ensure that the reply queue does not become full when the agent is stopped. In particular, the reply queue will become full extr
emely fast if snapshot accounting is enabled. -->
<!--The requirements and effects of setting the persistentBrokerData parameter to YES for a single broker are same as setting the defaultPersi
stentBrokerData parameter to YES described in above.-->
<!--END OF COMMENTS-->
<KqiAgent version="700"
agentId="BREIBP5"
defaultRetainBrokerEvents="10"
defaultRetainFlowEvents="10"
retainProductEvents="10"
discoveryInterval="300"
defaultStatisticInterval="60"
defaultFlowEventInterval="15"
defaultHistoricalAccountingType="Archive"
defaultRetainRecentSnapshotSamples="15"
defaultRetainRecentArchiveSamples="5"
defaultRetainRecentPubSubSamples="15"
holdTimeForQuery="180"
defaultReplyQueueName="KQI.AGENT.REPLY.QUEUE"
defaultReplyQueueModel="SYSTEM.BROKER.MODEL.QUEUE"
defaultCollectNodeData="NO"
maximumMessageLength="10240"
defaultPersistentBrokerData="NO"
defaultRefreshInterval="300"
defaultTakeActionAuthUsers="*">
</KqiAgent>
bash-3.2$
