NEC ELECTRA ELITE IPK II, User Manual

Page: 918 / 1190

Document Revision 4C Electra Elite IPK II
2 - 894 SNMP Simple Network Management Protocol
Conditions

The SNMP software module (Agent) located on the Elite IPK II CPUII supports remote
monitoring and debugging of Elite IPK II system by using the SNMP command set.

SNMP Agent uses port 161 for communicating with NMS manager for Get/Set Getnext and
walk operations.

SNMP Agent uses port 162 for sending the traps and alarms. These ports can be
configured through MB IDs.

If multiple ETUs of the same type exist in a system, by default the SNMP Agent provides
interface for the first available ETU. To get the details of other ETUs, the user must set
other ETU locations in the system by setting cabinet number and slot number definitions.

A User only needs to set the NMS Manager’s IP address to receive the traps and alarms
TrapDestIP for one ETU. This setting is applied for every card in the Elite IPK II System.

A system reset is required to enable the SNMP feature.

SNMP V1, V2 and V3 with MD5 authentication are supported.

The MIB tree interfaces with Elite IPK cards like Main CPUII card, PRI card, BRI card, DTI
card, COI card, PVA, SLI card and Intra Mail cards.

Support for MIB
It provides a complete MIB-II (RFC 1213) support. The package also supports the MIBs for
monitoring the system and measuring the system performance and extended private MIB.

Monolithic Agent – The default behavior of the SNMP Agent is as a monolithic agent.
MIBs
The Elite IPK II SNMP Agent implemented a set of Managed Objects described in MIB
documents written in ASN.1 data description language.
The Elite IPK II MIBs to support the Elite IPK II SNMP Agent may be downloaded for free from
the cng web site:
www.cng.nec.com .
Default Setting
None