Windows LAN Manager MIB II provides an OID for services that are running on a box. Here is an example of how you could pull this data back into TEP by polling the SNMP agent on Windows. Why use SNMP? Maybe there are servers in your company that are SNMP-centric and the owners not allow other agents to be installed on the box.
Here's an example metafile I created to pull running services from Windows LAN Manager. This requires that the Windows SNMP Services is started, and configured properly.
//SNMP TEXT
//APPL LAN_Mgr server 1.3.6.1.4.1.77.1.2
//NAME svDescription K 300 @SNMP poll attribute group lDiskFreeMegabytes
//ATTRIBUTES
Agent_Info D 128 0.0 @SNMP host name
Agent_Name D 64 KEY 0.0 @SNMP hostname relating to specific sample of data
svSvcEntry D 255 1.3.6.1.4.1.77.1.2.3.1
Once your new SNMP application comes online in TEP, right-click it and select Take Action>Select>Monitor Start. FOr AgentInfo put your server names. You can add individual community strings per host like this - {foo community},{bar community}, or you can add global community strings with KUMP_SNMP_NET_COMMUNITY in the environment file.
Refresh your TEP workspace and you will see SNMP MIB data coming back from the SNMP agent to TEP. From here you can display, monitor of warehouse the data as needed.
Again this example is just to help get you started with SNMP polling in ITM 6. Hope it helps.
Tuesday, March 11, 2008
More SNMP polling with ITM 6
Another SNMP polling example using ITM 6...
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment