Transition Networks
S4224 Web User Guide
33558 Rev. C
Page 70 of 669
SNMP v1 Traps
Most SNMPv1 messages follow a model where a client (Network Management System) makes a request
and a server (agent) responds to that request. Traps are the exception. An SNMP agent will transmit a
trap to the NMS when it has a condition to report that is deemed too important to wait until asked. A
common example of this is the failure of a communications link.
With most traps, the agent will include something called "'Interesting' variable bindings," which are the
OID(s) and value(s)of MIB variable(s) that provide more information about the condition. So, for example,
when a communications channel fails, the agent will send a pSError trap, which will have the OID of the
"Link" or "Signal Detect" variable for that channel, and the value "down." Newer versions of Management
Module firmware will also include bindings for the BIA (Cabinet serial number), slot, and (if applicable)
subdevice of the entity in question. This information is always embedded in the first binding (as above),
but are repeated separately for more convenient viewing under certain NMS packages.
SNMP v2 Traps
All S4224 SNMP Trap messages conform to SNMPv2 MIB RFC-2573. See the “Supported MIBs” section
on page
Error! Bookmark not defined.
for information on support for public (standard) and private MIBs.
A sample SNMP Message sequence is shown below.
SNMP v3 Traps
The SNMP v3 traps are mainly SNMPv2 traps with added authentication and privacy capabilities.
SNMPv3 Traps use the engineID of the local application sending the trap rather than the engineID of the
remote application. This means that you must create users in your remote user database and create one
for each engineID you wish to send traps from.
See “
Appendix E: SNMP Traps and MIBs”
SNMP v3 Configuration Process
Perform these procedures to configure the S4224 for SNMP v3.
System
- see
on page
Trap
on page
Communities
- se
SNMPv3 Community Configuration
on page
Users
- see
on page
Groups
- see
on page
Views
- see
on page
Access
- see
on page
The procedures in this process are defined in the following sections.
