Tivoli Netcool Supports Guide to the Nortel IEMS probe by Jim Hutchinson Document release: 2.0

Transcription

1 Tivoli Netcool Supports Guide to the Nortel IEMS probe by Jim Hutchinson Document release: 2.0

2 Table of Contents 1Introduction Overview...2 2Troubleshooting Sending an SNMPv1 trap Checking the Nortel IEMS server Performing a Manual Resync Request SNMPWALK SNMPGETNEXT and SNMPGET...6 IBM Copyright

3 1 Introduction 1.1 Overview The Nortel IEMS Probe is a direct SNMP monitoring probe, similar to the MTTrapd (SNMP) probe. The probe acquires event data by acting as a trap daemon and monitoring SNMP traps and events on both UDP and TCP sockets. When the probe starts, it performs a full resynchronization with the Nortel IEMS server using SNMPGET and SNMPGETNEXT. The probe then processes new alarms as they are generated. The Nortel IEMS server stores the most recently generated alarms in a cache table. It is possible to specify the number of alarms held in the cache table using the NlmConfigGlobalEntryLimit property (default 25). The value of NlmConfigGlobalEntryLimit muist reflect the value set on the Nortel IEMS server. Each alarm has a sequence number. If the Nortel IEMS probe misses one or more alarm, such as it receives alarms that do not have consecutive sequence numbers, it will perform either a full or an incremental resynchronization with the Nortel IEMS server. The type of synchronisation depends on the number of consecutive events that the probe has missed. If the number of consecutive events missed by the Nortel IEMS probe is greater than the number specified by the NlmConfigGlobalEntryLimit property, the probe performs a full resynchronization. If the number of consecutive events missed by the probe is less than or equal to this number, the probe performs an incremental resynchronization. IBM Copyright

4 The Nortel IEMS probe uses two ports, one for sending SNMP requests to the Nortel IEMS server, the other for listening to SNMP traps. The diagram below illustrates which properties refer to which part of the communication process. Probe BindAddress Nortel IEMS Server NortelEMSHostName NortelEMSPort GET LISTEN Port LISTEN SEND The probe will request events when its experiences a drift in the event sequence numbers or when a resynchronisation requested is received. It is important to have the NlmConfigGlobalEntryLimit configured to be the same as the cache value in the Nortel IEMS server. IBM Copyright

5 2 Troubleshooting The NET-SNMP software is freely available for probe supported platforms from This software can be used to query the Nortel IEMS server and send events to the Nortel IEMS probe. Useful commands snmptrap : Sends a trap to a given ipaddress and port snmpwalk : Walks a given MIB snmpget : Gets values from a given OID snmpgetnext : Gets the next value from an OID The values that define the system are; Nortel IEMS Server:- NortelEMSHostName : IP Address or hostname of IEMS Server NortelEMSPort : Port to which SNMPGET/SNMPGETNEXT requests are sent Nortel IEMS Probe:- BindAddress : IP-Address of probe server, used for multiple interfaces Port : Port the probe listens for SNMP traps Protocol : Type of SNMP traps listened for by the probe 2.1 Sending an SNMPv1 trap The net-snmp tools provide a command called snmptrap, that can send SNMPv1, SNMPv2 and SNMPv3 traps and informs to a given ip-address and port; e.g. snmptrap -v 1 -c public ipaddress:1620 "" "" 6 99 ""e Where ipaddress is the ip-address of the probe and 1620 the port it is listening on. By default UDP requests are sent. In order to specify TCP traps the following syntax is required; snmptrap -v 1 -c public TCP:ipaddress:1620 "" "" 6 99 ""e IBM Copyright

6 2.2 Checking the Nortel IEMS server Ensure that the Nortel IEMS Server is avaliable ping <NortelEMSHostName> traceroute <NortelEMSHostName> Check that the NortelEMSPort is active snmpwalk -v2c -Cc -c public <NortelEMSHostName>:<NortelEMSPort> SNMPv2-SMI::mib Check the NlmConfigGlobalEntry matches the value set n the Nortel IEMS Server IBM Copyright

7 2.3 Performing a Manual Resync Request SNMPWALK List of all active oid's : snmpwalk -v2c -Cc -c public ipaddress:8001 SNMPv2-SMI::mib SNMPGETNEXT and SNMPGET Use snmpgetnext starting with Where is the active index oid snmpgetnext -t10 -r0 -v2c -c public ipaddress: Results:- SNMPv2-SMI::mib = OID: SNMPv2-SMI::mib Returned value is used in the next snmpgetnext command: snmpgetnext -t10 -r0 -v2c -c public ipaddress: This is repeated until the original oid is returned From the list of oid's collected, extract the last digit of each oid collected : e.g. The return-oid is one IBM Copyright

8 Perform an SNMPGET on the elements; snmpget -r0 -v2c -c public ipaddress: return-oid.2 e.g. snmpget -r0 -v2c -c public ipaddress: The returned value will be one of the following alarm types; nnextalarmwarning " " nnextalarmminor " " nnextalarmmajor " " nnextalarmcritical " " nnextalarmclear " " nnisoextalarmwarning nnisoextalarmminor nnisoextalarmmajor nnisoextalarmcritical nnisoextalarmclear ".iso " ".iso " ".iso " ".iso " ".iso " nnnlmextalarmwarning " " nnnlmextalarmminor " " nnnlmextalarmmajor " " nnnlmextalarmcritical " " nnnlmextalarmclear " " nnisonlmextalarmwarning nnisonlmextalarmminor nnisonlmextalarmmajor nnisonlmextalarmcritical nnisonlmextalarmclear ".iso " ".iso " ".iso " ".iso " ".iso " IBM Copyright