Page 59 01/2007 AMT/PTD/PBX/0062/1/2EN
4.5.3.3 SNMP
To manage a large RFP network, an SNMP agent is provided for each RFP. This will give alarm
information and allow an SNMP management system (such as HP Open View) to manage this
network.
All agents are configured in a central place. RFP dependent parameters like sysLocation and
sysName are generated. sysLocation corresponds to the location configured via web service. . If
this location is not configured sysLocation is set to “Location”. sysName is made up of the MAC
address and ‘RFPnn’ or ‘OMM RFPnn’ if the OMM is running on this RFP. ‘nn’ stands for
31/32/33 or 34.
How long an RFP is in operational state can be requested by reading sysUpTime. This value
indicates the running time of the RFP application software. It does not indicate the running time of
the operating system which does not correspond to the operational RFP state. This value does
not make any statement about the DECT network.
The SNMP agent responds to SNMPv1, and SNMPv2c reads requests for the standard MIB-II
objects. The MIB-II contains 11 object groups.
The agent receives both SNMPv1 and SNMPv2c traps. It sends a 'coldStart' trap when it first
starts up, and an enterprise-specific trap 'nsNotifyShutdown' when it stops. When it receives an
SNMP request using an unknown community name, it sends an 'authenticationFailure' trap. The
agent generates an enterprise-specific trap 'nsNotifyRestart' (rather than the standard 'coldStart'
or 'warmStart' traps) after being re-configured.
Decoding SNMP messages with your network management system or MIB browser always
requires the publicly available IETF MIB definitions which can be downloaded from /6/. These are
the MIB-II definitions published in documents /3/ and /4/:
♦
♦
♦
♦
♦
♦
♦
♦
♦
RFC1213-MIB
RFC1212-MIB
RFC1155-SMI
and the following SNMPv2 definitions published in /5/.
SNMPv2-MIB
SNMPv2-CONF
SNMPv2-TC
SNMPv2-SMI.
Enterprise-specific traps can be decoded using the definitions in:
NET-SNMP-MIB
NET-SNMP-AGENT-MIB.
To Next Page
Loading...