IBM Support

ITM Agent Insights: Agentless Linux monitoring agent (R4) configuration walk-through

Technical Blog Post


Abstract

ITM Agent Insights: Agentless Linux monitoring agent (R4) configuration walk-through

Body

There are numerous "agentless" agents:
Agentless Monitoring for Windows Operating Systems 5724C04RW - KR2
Agentless Monitoring for AIX Operating Systems 5724C04RA - KR3
Agentless Monitoring for Linux Operating Systems 5724C04RL - KR4
Agentless Monitoring for HP-UX Operating Systems 5724C04RH - KR5
Agentless Monitoring for Solaris Operating Systems 5724C04RS - KR6

All of the "agentless" agents can be installed on Windows / UNIX / Linux platforms, and then configured to remotely monitor the type of endpoint remotely where the monitored systems do not have an agent installed locally so are "agentless".

The remote Linux "agentless" agent - the R4 component - can be installed on a UNIX or Linux or Windows system, then configured to remotely monitor Linux systems via SNMP.

This blog post will provide an example walk-through of configuration for R4 monitoring agent on Windows and UNIX / Linux systems.

6.3 FP2 ITM InfoCenter:

http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/welcome.htm

6.3 FP2 User's Guide for Agentless Monitoring for Linux:
http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3/agleslinux/fac_landing_user.htm

 

Agentless agents are "multi-instance" agents.

Windows:

If installed on Windows platform, configure the instance through MTEMS GUI.

On Windows, it is important to always launch the MTEMS with "Run As Administrator", this will prevent problems with Microsoft permissions issue which can occur since Windows tightened down security starting with 2008 release.
Launch the MTEMS GUI by right-clicking on the traffic light icon and selecting to "Run As Administrator"
image

To launch from command line, open an Administrator DOS command prompt, and launch the MTEMS with "kinconfg.exe":
image

As a "multi-instance" agent, there will be a "Template" item in the MTEMS GUI used to configure new instances.
This is different than a single instance agents like the OS agent - NT - where there is only a single row that you right-click to configure.

image
To configure an R4 instance on Windows, right-click on the "Template" entry. Either chose to "Configure Using Defaults" or choose "Advanced -> Configure Advanced":

"Configure Using Defaults":

image

When prompted, provide a unique instance name:

imageThere are three sections for configuration:
SNMP connection:

imageIf using SNMP V1 or V2c, provide communitiy name when prompted.
If using SNMP V3, provide different details for establishing the SNMP connection to gather data from the remote Linux endpoint

SNMP Connection Details:

image

image

After setting the version of SNMP tol use, and the details for authenticating to the SNMP environment, configure the remote Linux endpoints to monitor:

Remote System Details:

Click "New" to add a new remote system.
image

For the Remote Managed System, specify a value for the Managed System Name for the "subnode" that will be seen in the TEP under the instance.
This name should be unique for the subnodes on the system, and be aware that ITM has an overall limit of 32 characters for the total MSN, which will include the subnode name, the product code - R4, and the instance name. Managed System Names (MSN) need to be unique in order to prevent confusion by the TEMS, and the ITM infrastructure has a limitation of 32 characters for the overall MSN before it is truncated.

The "SNMP host" value will be the hostname / IP address for the remote Linux endpoint system.
Recommendation is to use numeric IP to avoid any issues with DNS resolution that might prevent communicating with the remote system.

The "Advanced" section is for overriding any of the default values specified for the SNMP connection / SNMP version details that would be the "default" for all subnodes.

If some endpoints require a different community name, it can be overriden specifically for that Remote Managed System.
imageAdd additional remote managed systems for each remote Linux endpoint to monitor as a subnode under the R4 instance.

When done with configuring the Remote System Details for the remote Linux endpoints, there will be a new entry in the MTEMS for the R4 instance:

image


"Advanced -> Configure Advanced":
image

"Configure Advanced" method goes through the configuration screens for setting the communication details to connect to the TEMS:
image

Provide an instance name when prompted:

imageWalk through the rest of the configuration as above for the "R4" specific settings.
 


To demonstrate how to keep the subnodes separate between the multiple instances, this example updates the Managed System Name, as well as shows using an "override" to specify SNMP V2c

image
The MTEMS now shows two R4 instances, along with the "Template":
image

*NOTE*  The "Task/SubSystem" column will contain the name of the instance.

To configure an additional instance, use the "Template".
To re-configure an existing instance, right-click on the row for the instance to reconfigure (or remove trying to delete an instance).

 

With both instances started, the following is displayed in the TEP portal navigator tree:

image

The "Agentless Linux OS" entry is displayed under the Windows system where the R4 agent is installed.
Note that since there are two instances (since agentless agents are "multi-instance") there is a folder for the "Agentless Linux OS" that has the individual instances underneath.
The MSN for the instance has a naming format of:
<Instance Name>:<hostname>:R4

Under each instance, the "Managed Systems" which would be the remote Linux endpoints you have configured to gather data from are displayed.
  These are "subnodes" of the specific R4 instance.

The MSN for a "subnode" has a naming format of:
R4:<"Managed System Name" from the Remote System Details>:LNX

The "LNX" is an indication of the connection type, which there is only one for Linux remote endpoints - SNMP.
This demonstrates why it is important that subnode names are unique during configuration, since the overall MSN for a subnode does not include the "instance" name.

Naming the subnodes the same thing under multiple instances would confuse the TEMS when both of these instances are running, since there would be multiple subnodes that the TEMS would see as the "same" thing due to the identical MSN.
 

...

 

UNIX / Linux:

If installed on UNIX / Linux, configure the instance through using "itmcmd config" command.

On UNIX / Linux, use "itmcmd config" command to configure instances:

Refer to the product manual for command syntax:
IBM Tivoli Monitoring Command Reference V6.3 Fix Pack 2.pdf
https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=0587adbc-8477-431f-8c68-9226adea11ed#fullpageWidgetId=W42ce7c6afdb9_42c2_a9ea_e1ba310bea8c&file=83016a5e-5936-4959-9199-d06a6f0ecd02


Since 6.3 FP2 manuals are only available in PDF that must be downloaded, the direct link to the specific command from the 6.3 release of the Command Reference manual:

itmcmd config
https://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/cmdref/candleconfig.htm

Example:
/products/doug/ITM/bin # ./itmcmd config -A -o testR4 r4
Agent configuration started...
Edit "Monitoring Agent for Agentless Linux OS" settings? [ 1=Yes, 2=No ]
(default is: 1): 1
SNMP connection :
Linux SNMP server properties
The port number of the SNMP server.
Port Number (default is: 161):
The SNMP version to use to make the connection.
SNMP Version [ 1=SNMP Version 1, 2=SNMP Version 2c, 3=SNMP Version 3 ]
(default is: 1): 2
SNMP Version 2c :
SNMP version 2c parameters
The SNMP server community name.
Enter Community Name (default is: ):
Re-type : Community Name (default is: ):
Remote System Details :
Managed System Details
No 'Remote System Details' settings available.
Edit 'Remote System Details' settings, [1=Add, 2=Edit, 3=Del, 4=Next,
5=Exit] (default is: 5): 1
Managed System Name (default is: ): remote1
The host or IP address of the SNMP server.
SNMP host (default is: ): 127.0.0.1
Advanced (select a section to override values), type "0" to remove
existing override values, , or type "q" to exit.
[1=SNMP connection, 2=SNMP Version 1, 3=SNMP Version 2c, 4=SNMP Version
3] (default is: q): q
'Remote System Details' settings: Managed System Name=remote1
Edit 'Remote System Details' settings, [1=Add, 2=Edit, 3=Del, 4=Next,
5=Exit] (default is: 5): 4
'Remote System Details' settings: Managed System Name=remote1
Edit 'Remote System Details' settings, [1=Add, 2=Edit, 3=Del, 4=Next,
5=Exit] (default is: 5): 5
Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): 1
TEMS Host Name (Default is: nmp137): 9.65.143.111
Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):
Now choose the next protocol 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):
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):
Agent configuration completed...

 


To configure a second instance, perfor the same procedure but specify a new "instance" name for the additional instance for the -o parameter.
./itmcmd config -A -o secondR4 r4

 

To start an R4 instance, specify the instance parameter on the "itmcmd agent" command:
nmp137:/products/doug/ITM/bin # ./cinfo -r
*********** Wed Mar 6 13:47:18 EST 2013 ******************
User: root Groups: root
Host name : nmp137 Installer Lvl:06.23.02.00
CandleHome: /products/doug/ITM
***********************************************************
...no known processes are running

 

nmp137:/products/doug/ITM/bin # ./itmcmd agent -o testR4 start r4
Processing. Please wait...
Starting Agentless Monitoring for Linux Operating Systems ...
Agentless Monitoring for Linux Operating Systems started
nmp137:/products/doug/ITM/bin # ./cinfo -r
*********** Wed Mar 6 13:47:50 EST 2013 ******************
User: root Groups: root
Host name : nmp137 Installer Lvl:06.23.02.00
CandleHome: /products/doug/ITM
***********************************************************
Host Prod PID Owner Start ID ..Status
nmp137 r4 15178 root 13:47 testR4 ...running

To add additional monitored systems to the "testR4" instance, reconfigure the agent instance and add / edit the "Remote Managed System" under "Edit 'Remote System Details' settings".

Configure a second R4 instance on this system, which has its own list of managed systems:
nmp137:/products/doug/ITM/bin # ./itmcmd config -A -o secondR4 r4
Agent configuration started...
Edit "Monitoring Agent for Agentless Linux OS" settings? [ 1=Yes, 2=No ]
(default is: 1): 1
SNMP connection :
Linux SNMP server properties
The port number of the SNMP server.
Port Number (default is: 161):
The SNMP version to use to make the connection.
SNMP Version [ 1=SNMP Version 1, 2=SNMP Version 2c, 3=SNMP Version 3 ]
(default is: 1): 1
SNMP Version 1 :
SNMP version 1 parameters
The SNMP server community name.
Enter Community Name (default is: ): g
Re-type : Community Name (default is: ):
Remote System Details :
Managed System Details
No 'Remote System Details' settings available.
Edit 'Remote System Details' settings, [1=Add, 2=Edit, 3=Del, 4=Next,
5=Exit] (default is: 5): 1
Managed System Name (default is: ): bogus1
The host or IP address of the SNMP server.
SNMP host (default is: ): 123.456.789.001
Advanced (select a section to override values), type "0" to remove
existing override values, , or type "q" to exit.
[1=SNMP connection, 2=SNMP Version 1, 3=SNMP Version 2c, 4=SNMP Version
3] (default is: q): q
'Remote System Details' settings: Managed System Name=bogus1

Edit 'Remote System Details' settings, [1=Add, 2=Edit, 3=Del, 4=Next,
5=Exit] (default is: 5): 1
Managed System Name (default is: ): bogus2
The host or IP address of the SNMP server.
SNMP host (default is: ): 123.456.789.002
Advanced (select a section to override values), type "0" to remove
existing override values, , or type "q" to exit.
[1=SNMP connection, 2=SNMP Version 1, 3=SNMP Version 2c, 4=SNMP Version
3] (default is: q): q
'Remote System Details' settings: Managed System Name=bogus1

Edit 'Remote System Details' settings, [1=Add, 2=Edit, 3=Del, 4=Next,
5=Exit] (default is: 5): 1
Managed System Name (default is: ): bogus3
The host or IP address of the SNMP server.
SNMP host (default is: ): 123.456.789.003
Advanced (select a section to override values), type "0" to remove
existing override values, , or type "q" to exit.
[1=SNMP connection, 2=SNMP Version 1, 3=SNMP Version 2c, 4=SNMP Version
3] (default is: q): q

'Remote System Details' settings: Managed System Name=bogus1
Edit 'Remote System Details' settings, [1=Add, 2=Edit, 3=Del, 4=Next,
5=Exit] (default is: 5): 5
Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): 1
TEMS Host Name (Default is: nmp137): 9.65.143.111
Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):
Now choose the next protocol 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):
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):
Agent configuration completed...

 

...


As a reminder, restart appropriate instance(s) for new configuration settings to take effect.

Starting / Stopping ITM agents on UNIX / Linux is done with the "itmcmd agent" command:

itmcmd agent
https://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/cmdref/candleagent.htm

To stop a running R4 agent instance:

./itmcmd agent -o <instance_name> stop r4

To start an R4 agent instance:

./itmcmd agent -o <instance_name> start r4

Example:
nmp137:/products/doug/ITM/bin # ./itmcmd agent -o secondR4 start r4
Processing. Please wait...
Starting Agentless Monitoring for Linux Operating Systems ...
Agentless Monitoring for Linux Operating Systems started
nmp137:/products/doug/ITM/bin # ./cinfo -r
*********** Wed Mar 6 14:07:48 EST 2013 ******************
User: root Groups: root
Host name : nmp137 Installer Lvl:06.23.02.00
CandleHome: /products/doug/ITM
***********************************************************
Host Prod PID Owner Start ID ..Status
nmp137 r4 15178 root 13:47 testR4 ...running
nmp137 r4 20961 root 14:07 secondR4 ...running

 

...

 

 

The above covers how to perform the R4 configuration on the system where the agentless monitoring agent is running, but it does not mean that SNMP data can be gathered by the R4 agent from the remote Linux endpoints.  If the TEP does not display any subnode data under an R4 agent instance beneath the "Managed Systems" in TEP navigator tree, confirm SNMP is working outside of ITM R4 agent using "snmpwalk" to verify that SNMP is capable of returning data using same SNMP version / authentication as the R4 agent is configured to use.

 

Submitter: drd401709
Compid: 5724C04RL - Agentless Monitoring for Linux Operating Systems
Reference DCF technotes:

DCF 1616192 - KCICF8038E message when attempting to create an agent instance / configure agent instance through MTEMS GUI on Windows 2008.

Keywords: kr4agent

 

 

 

Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM Agent Insights: Introduction.

 

Tutorials Point

Subscribe and follow us for all the latest information directly on your social feeds:

 

imageimageimage

Check out all our other posts and updates:

Academy Blogs
Academy Videos
Academy Google+
Academy Twitter

image

 

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""}]

UID

ibm11083063