9-10
MAX Administration Guide
Using Traps to Monitor Performance
Using OSPF-related SNMP traps
Using OSPF-related SNMP traps
MAX units support OSPF-related SNMP traps defined in RFC 1850 (rfc1850.mib), which
replaces RFC 1253 (rfc1253.mb).
RFC 1850 defines MIB object
ospfSetTrap
, for enabling trap events, as follows:
iso.org.dod.internet.mgmt.mib-2.
ospf.ospfTrap.ospfTrapControl.ospfSetTrap
This object defaults initially to the octet string {
’\0x0’,’0x0’,’0x0’,’0x0’
} (or the
hex value 00), which disables all trap events. NVRAM stores the value of this object.
SNMP Trap profile settings
The OSPF parameter, in the SNMP Trap profile, enables OSPF traps. Verify that OSPF is
active (
OSPF=Yes
) in the SNMP trap profile, as it is in the following example:
90-801 trap-profile
Name=trap-profile
Alarm=No
Port=No
Security=No
OSPF=Yes
Comm=
Dest=0.0.0.0
Enable traps...
Note:
With the
Yes
setting, the MAX unit generates traps that have been enabled in
Ethernet > SNMP Traps > any profile > Enable Traps. When you set OSPF to
No
, the MAX
unit does not generate any OSPF traps regardless of any individual OSPF trap settings in
Enable Traps.
Mod Config settings
The MAX # ASE LSA parameter, in the Mod Config profile, specifies the number of
Link-State Advertisements (LSAs) the MAX unit stores before going into a state of database
overload. When the unit reaches a database overload, it does not accept new entries and
discards self-originated entries. The default setting is
0
, as in the following example:
Telnet Password
Specifies whether all failed Telnet login attempts generate
a trap.
Use Exceeded
Specifies whether the system generates a trap when a
specific port has exceeded the number of DS0 minutes
allocated to it or when the system DS0 usage has been
exceeded.
Table 9-2. Trap-related parameters (continued)
Parameter
Description
