This chapter describes the MIBs and traps supported in IPriori, and includes the following information:
- The versions of SNMP and PDU types supported
- MIB-2 functionality
- The order in which MIBs should be compiled
- A listing of the CLI commands used to enable traps, configure SNMP, and display SNMP debug information
- The standard, experimental, and Avici proprietary MIBs supported in IPriori Release 6.2.
- Alarms, traps and other events
Changes Since Release 6.0
IPriori includes support for the following additional MIBs:
- AVICI-GBE-MIB - specifies objects to support Gigabit signal integrity and member operational status.
- RADIUS-MIB - specifies objects to support Radius Authorization and conformance as well as Radius Accounting and Conformance.
- SNMP-v3 - specifies objects to support Framework, Target, Notification. USM, Vacm and Community MIBS.
- AVICI-Netflow MIB - specifies objects to support 16- and 32-Bit Index Tables and Conformance.
The AVICI-GBE-MIB includes 2 new traps:
- aviciGbeEvent
- aviciGbeMemberLinkEvent
The TE MIB includes 7 new traps:
- aviciTeTunnelUp
- aviciTeTunnelDown
- aviciTeTunnelChange
- aviciTeMainLSPFullyProtected
- aviciTeMainLSPPartiallyProtected
- aviciTeTunnelBackupInUse
- aviciTeTunnelBackupNotInUse
SNMP Version
IPriori supports SNMP Version 1 (SNMPv1) and SNMP Version 2c (SNMPv2c) and SNMP Version 3 (SNMPv3).
SNMPv2c is necessary to support 64 bit counters. Some counters would wrap in a few seconds if implemented as 32 bit counters. 64 bit counters will be used in the following areas:
- Performance Management
- Accounting
- Fault Management (counting errors)
- Quality of Service (QoS)
The version of trap PDUs are configurable on a per-host basis. Version 1, Version 2, and Version 3 trap PDU types are supported.
The default is to send a SNMP Version 1 trap if configured to send traps to a host.
A get request via an SNMPv1 PDU for a 64-bit counter will return an error.
A getnext request via an SNMPv1 PDU will skip over any 64 bit counters or other SNMPv2-only data types.
IPriori supports SMI v2.
MIB-2 Support
MIB-2 functionality previously provided by RFC 1213 is now supported via:
- RFC 1907
- RFC 2011
- RFC 2012
- RFC 2013
- RFC 2096
- RFC 2233
Other MIB Information
The CustomerMibs.txt file contains the MIB loading order and the numbers.txt file contains the OIDs for the entire MIB tree.
CLI to Configure SNMP and Events
For more detailed information regarding configuration of event thresholds, refer to the "SONET/SDH Commands" chapter of the IPriori Command Line Reference, Volume 1.
For more detailed information regarding the commands to configure SNMP, refer to the "SNMP Commands" chapter of the IPriori Command Line Reference, Volume 1.
CLI to Configure SONET Event Thresholds
The following table lists the CLI commands used to configure SONET event thresholds, their syntax, and a brief description.
Table A-1. Commands to Configure SONET Event Thresholds
| SONET/SDH Commands
|
Description
|
show sonet thresholds pos
|
Displays the setting for SONET thresholds.
|
[no|default] sonet threshold
|
Sets the threshold for events occurring on a SONET connection to the default values.
|
[no]sonet threshold line
|
Sets the threshold values for events occurring in the line layer at the local end of a SONET connection.
|
[no] sonet threshold line-far-end
|
Sets the threshold values for events occurring in the line layer at the remote end of a SONET connection.
|
[no] sonet threshold path
|
Sets the threshold values for events occurring in the path layer at the local end of a SONET connection.
|
[no] sonet threshold path-far-end
|
Sets the threshold values for events occurring in the path layer at the remote end of a SONET connection.
|
[no] sonet threshold section
|
Sets the threshold values for events occurring in the local end of the section layer of a SONET connection.
|
CLI to Configure SNMP
The following table lists the global CLI commands to configure SNMP, including SONET event thresholds, their syntax, and a brief description.
Table A-2. Commands to Configure SNMP
| SNMP Commands
|
Description
|
[no] snmp-server community
|
Sets the community string and configures read/write access privileges to MIB objects.
|
[no] snmp-server contact
|
Sets text for MIB object sysContact.
|
[no] snmp-server enable traps type
|
Enables/disables SNMP traps. Types of SNMP traps that can be enabled/disabled are:
- bay-controller
- bgp
- comp-link
- environment (fan, temperature, and voltage)
- link-up/link down
- module
- ospf
- pim
- rmon
- snmp
- sonet
- ldp
- te (Traffic Engineering)
- qos (Quality of Service)
|
[no] snmp-server host
|
Specify hosts to receive SNMP traps.
|
[no] snmp-server location
|
Sets the text for MIB object sysLocation
|
[no] snmp-server trap source
|
Configures an interface as the source address for SNMP traps.
|
CLI for SNMP Debug
The following table lists the debut SNMP. Support for debug sessions may be via a console or telnet session.
Table A-3. Commands to Debug SNMP
| SNMP Commands
|
Description
|
debug snmp headers
all | trace | traps | varibinds
|
Displays the information of SNMP packets received, including IP address of SNMP manager requested, type of request (Get/ Get next), request id of the packet.
The all keyword displays all SNMP information.
The trace keyword displays operations within the Agent.
The traps keyword displays dump SNMP traps.
The varibinds keyword displays output varibinds in SNMP queries.
|
debug snmp dump-packets
|
Displays the variable bindings in SNMP packets received and transmitted.
|
no debug snmp
|
Disables the debugging displays.
|
Standard MIBs Supported
The following table lists:
- The standard MIBs supported in IPriori
- Any exceptions to the standards.
- Any unsupported features.
Table A-4. Standard MIBs Supported
| Standard MIB Number
|
Description of Exceptions and Unsupported Features
|
RFC 1471
|
Managed Objects for the Link Control Protocol of the Point-to-Point Protocol.
The following are not supported:
- PPP LQR
- PPP Tests (depends on ifExtnsTestTable which has been deprecated in RFC 2233)
|
RFC 1473
|
Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol.
|
RFC 1573
|
The IANAifType-MIB defines the IANAifType Textual Convention, and thus the enumerated values of the ifType object defined in MIB-II's ifTable.
|
RFC 1595
|
Managed Objects for the SONET/SDH Interface Type Exceptions.
The following are not supported:
- SONET/SDH Virtual Tributary group
- SONET/SDH VT Current Table
SONET/SDH VT Interval Table
|
RFC 1657
|
Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2.
|
RFC 1757
|
Remote Network Monitoring.
The following are supported only for Gigabit Ethernet modules:
- Ethernet Statistics Group
- History Control Group
- Ethernet History Group
The following are not supported:
- Host Group
- HostTopN Group
- Matrix Group
- Filter Group
- Packet Capture Group
|
RFC 1850
|
OSPF Version 2 Management Information Base
The following are not supported:
- obsolete tables
- ospfTrapControl - Objects have no context and probably should be textual conventions.
- ospfLsdbTable (optional)
- ospfExtLsdbTable (optional)
- ospfHostTable (not applicable)
|
RFC 1907
|
SNMPv2 Management Information Base
The following are not supported:
|
RFC 2011
|
SNMPv2 Management Information Base for the Internet Protocol using SMIv2.
Exceptions:
- ipForwarding - Read Only (always a router)
- ipDefaultTTL - Read Only
|
RFC 2012
|
SNMPv2 MIB for the TCP using SMIv2.
|
RFC 2013
|
SNMPv2 MIB for the UDP using SMIv2.
|
RFC 2096
|
IP Forwarding Table MIB
Exceptions:
The following are not supported:
Deprecated objects.
|
RFC 2233
|
Evolution of the Interfaces Group of MIB-II.
The following are not supported:
|
RFC 2514
|
This MIB module provides Textual Conventions and OBJECT-_IDENTITY Objects to be used by ATM systems.
|
RFC 2515
|
This is the MIB modules for ATM and AAL5-related objects for managing ATM interfaces, ATM virtual links, ATM cross-connects, AAL5 entities, and AAL5 connections.
|
RFC 2571
|
An Architecture for Describing SNMP Management Frameworks.
|
RFC 2613
|
This MIB module is for managing remote monitoring device implementations for Switched Networks.
|
RFC 2618
|
This is the MIB module for entities implementing the client side of the Remote Access Dial-in User Service (RADIUS) authentication protocol.
|
RFC 2620
|
This is the MIB module for entities implementing the client side of the Remote Access Dial-in User Service (RADIUS) accounting protocol.
|
RFC 2932
|
IPv4 Multicast Routing MIB
In the ipMRouteInterfaceTable, the following attributes are not supported:
- ipMRouteInterfaceInMcastOctets
- ipMRouteInterfaceOutMcastOctets
- ipMRouteInterfaceHCInMcastOctets
- ipMRouteInterfaceHCOutMcastOctets
- ipMRouteInterfaceTtl
- ipMRouteInterfaceRateLimit
In the ipMRouteTable, the following attributes are not supported:
- ipMRouteOctets
- ipMRouteHCOctets
The ipMRouteScopeNameTable is not supported.
In the ipMRouteNextHopTable, the following attributes are not supported:
- ipMRouteNextHopPkts
- ipMRouteNextHopClosestMemberHops
|
RFC 2665
|
Definitions of Managed Objects for the Ethernet-like Interface Types.
The following objects are supported:
- dot3StatsEntry
- dots3PauseEntry
- etherControlGroup
The remaining object are not supported.
|
IEEE-LAG-MIB
|
Monitors all aspects of Link Aggregation interfaces as defined by IEEE Std. 802.3ad.
|
INET-ADDRESS-MIB
|
This MIB module defines textual conventions for representing Internet addresses. An Internet address can be IPv4 address, an IPv6 address or a DNS domain name. Also defined are textual conventions for Internet port numbers, autonomous system numbers and the length of an Internet address prefix.
|
IANA-RPTPROTO-MIB
|
This MIB module defines the RTPROTO\IANAipRouteProtocol and IANAipMRoute Protocol textual conventions for use in MIBs which need to identify unicast or multicast routing mechanisms.
|
iannaaddressfamilynumbers.mib
|
This MIB module defines the AddressFamilyNumbers textual convention.
|
SNMP-COMMUNITY-MIB
RFC2576
|
This MIB module defines object to help support coexistence between SNMPv1, SNMPv2c, and SNMPv3.
|
SNMP-MDP-MIB
RFC 2572
|
This MIB module defines Message Processing and Dispatching.
|
SNMP-NOTIFICATION-MIB
RFC2573
|
This MIB modules defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of notifications.
|
SNMP-TARGET-MIB
RFC 2573
|
This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of SNMP messages.
|
SNMP-USER-BASED-SM-MIB
RFC 2574
|
This MIB module contains management information definitions for the SNMP User-based Security Model.
|
SNMP-VIEW-BASED-ACM-MIB
RFC 2575
|
This MIB module contains management information definitions for the View-based Access Control Model for SNMP.
|
Experimental MIBs Supported
The following table lists the experimental MIBs supported in IPriori:
Table A-5. Experimental MIBs Supported
| Experimental MIB Name
|
Description of Supported Features
|
RFC 2934
|
Protocol Independent Multicast MIB for IPv4.
In the pimIpMRouteTable, the following attributes are not supported:
- pimIpMRouteUpstreamAssertTimer
- pimIpMRouteAssertMetric
- pimIpMRouteAssertMetricPref
- pimIpMRouteAssertRPTBit
- Any deprecated objects and tables.
The pimIpMRouteNextHopTable is not supported (not required for PIM sparse mode).
|
msdpMIB
|
Experimental MIB module for MSDP Management.
|
TE-MIB (Avici experimental MIB derived from draft-ietf-tewg-ib-00.txt)
|
This MIB is derived from draft-ietf-tewg-mib-00.txt, and is the MIB module for Multi-Protocol Label Switched Paths.
CAUTION This MIB has been modified from the IETF draft version to add a MIB arc, correct syntax errors and enable the MIB to be compiled.
The following objects are not supported:
- teTunnelOctets
- teTunnelPackets
|
LDP-MIB
(draft-mpls-ldp-mib-07.txt)
|
Definitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP)
The ATM, Frame Relay and mapping groups are not supported in this release.
|
Avici MIBs Supported
The following table lists the Avici proprietary MIBs supported in IPriori:
Table A-6. Avici MIBS Supported
| Avici MIB Name
|
Description
|
AVICI-BANDWIDTH-MIB
|
This MIB module specifies proprietary objects to support bandwidth on Avici interfaces.
|
AVICI-BAY-MIB
|
Monitor and control the voltage lines, voltage rails, breakers, CO alarms, monitor boards, slots and fans.
|
AVICI-BGP-MIB
|
Specifies objects that configure thresholds for BGP and the Avici proprietary BGP notifications.
|
AVICI-FABRIC-MIB
|
Monitors the number packets/flits inserted, forwarded, and extracted for both high and low priority traffic. Monitors links and channels in the Avici fabric.
|
AVICI-GBE-MIB
|
This MIB module contains notifications describing the Avici implementation of Gigabit ethernet.
|
AVICI-MEMORY-MIB
|
Monitor memory usage on a server, module or bay controller.
|
AVICI-MODULE-MIB
|
Monitor and control aspects of a module including inventory control, diagnostics, ICMP, and IP traffic monitoring.
|
AVICI-PROCESS-MIB
|
Monitor the CPU utilization on a server, module or bay controller. Monitors the total CPU busy percentage in the last 5 second, 1 minute and 5 minute periods.
|
AVICI-PRODUCTS-MIB
|
Defines the Avici product MIB arcs used in SysObjectId.
|
AVICI-SERVER-MIB
|
Specifies those managed objects that monitor and control a route server.
|
AVICI-SONET-MIB
|
Extensions to the SONET/SDH medium table defined by RFC-1595; Definitions of Managed Objects for the SONET/SDH Interface Type. The managed objects contained by this table provide additional control of the electrical or fiber physical layer of a SONET/SDH interface. Includes:
- Additional control of the section entity associated with a SONET/SDH interface.
- This table also serves as a "catch-all" for managed objects that apply to the medium, section, line, and path entities comprising a SONET/SDH interface.
|
AVICI-SMI
|
Common definitions for all vendor-specific MIBs authored by Avici Systems, Inc.
|
AVICI-SYSTEM-MIB
|
Monitor and control of the components comprising a Avici router system including inventory control, slot configuration and health monitoring. Includes:
- Router ID for the entire Avici router.
- aviciSysInventoryTable - List of components in the system: modules, bays and control servers.
- aviciSysIfTransTable - maps line card interfaces into their corresponding bay and slot numbers. Only line card interfaces are mapped by this table, not server interfaces.
|
AVICI-TC
|
Specifies the types to be used in Avici MIBs, including system types, inventory types, etc.
|
AVICI-QOS-MIB
|
Provides statistics, parameters, and notifications for the Avici implementation of Quality of Service. Includes:
|
AVICI-COMPOSITELINK-MIB
|
This MIB specifies objects to support the Avici proprietary compositeLink interface. It includes information regarding link bandwidth, members, and thresholds.
|
AVICI-NETFLOW-MIB
|
Contains mappings to and from 32-bit ifIndex values and 16-bit Netflow interface id's.
|
Table Index Translation
ifIndex to Bay, slot and port
The aviciSysIfTransTable (AVICI-SYSTEM-MIB) is indexed by ifIndex and contains bay, slot port and logical interface, and the ifType of the interface.
MIB Hierarchies
Refer to the enclosed MIBs chart for an illustration of the Standard and Avici proprietary MIB trees.
Traps and Alarms Supported
The table below describes the traps and alarms supported in Release 6.2.
Table A-7. Traps and Alarms Supported
| MIB Name
|
Description of Traps, Alarms, and Other Events
|
Interface
|
linkDown (RFC 2233)
linkUp (RFC 2233)
|
AVICI-MODULE-MIB
|
aviciModuleColdStart indicates that the specified module has been powered up.
aviciModuleWarmStart indicates that the specified module has been restarted.
aviciModuleCommunicationDown signifies a module that has not reached the up state has lost communication with the bay controller.
aviciModuleCommunicationUp signifies that a new module has been discovered in a unconfigured slot.
aviciModuleDormant indicates a module has decided not to boot up because of Module Reboot Policy. Module Reboot Policy is defined as, module should not come up after it has rebooted aviciModuleRPThreshold number of times continuously, within aviciModuleRPDuration minutes.
aviciModuleDown. indicates that a server is no longer communicating with the specified module after having established communication.
aviciModuleIncompatibleSW signifies software image running on the module is incompatible with server image.
aviciModuleTemperatureNormal trap signifies that the specified module is now operating within the normal temperature range. The current temperature is reported in the aviciModuleCurrTemp object.
aviciModuleTemperatureMinor trap signifies that the specified module is reporting a temperature above the minor temperature threshold but below the major temperature threshold. The current module temperature is reported in the aviciModuleCurrTemp object. When the reported temperature drops below the minor threshold, the aviciModuleTemperatureNormal notification will be sent to clear this fault.
aviciModuleTemperatureMajor trap signifies that the specified module is reporting a temperature above the major temperature threshold but below the critical temperature threshold. The current module temperature is reported in the aviciModuleCurrTemp object. When the reported temperature drops below the major threshold, the aviciModuleTemperatureMinor notification will be sent to clear this fault.
aviciModuleTemperatureCritical trap signifies that the specified module is reporting a temperature above the critical temperature threshold. The current module temperature is reported in the aviciModuleCurrTemp object. When the reported temperature drops below the critical threshold, the aviciModuleTemperatureMajor notification will be sent to clear this fault.
aviciModuleMisconfigured trap indicates when the fabric version mismatch, or a module in a multi-module set is not in the proper slot.
aviciServerAccessModuleDown notification signifies that a server access module has gone down.
aviciServerAccessModuleUp notification signifies that a server access module has come up.
|
AVICI-BAY-MIB
|
aviciAllServerAccessModulesDown notification signifies that all server access modules have gone down.
aviciAllServerAccessModulesDownClear notification signifies that at least one server access module has come up.
aviciBayMonitorUp signifies that the bay monitor has powered-up.
aviciBayMonitorDown signifies that a bay controller is no longer getting reliable data from the bay monitor.
aviciBayControllerColdStart signifies that the bay controller has powered up.
aviciBayControllerWarmStart signifies that the bay controller has been restarted.
aviciBayControllerDown signifies that a server is no longer communicating with the bay controller after having established communication.
aviciBayCommLinkNotification is sent when there is a state change in the bay communications links..
aviciBayVoltageNotification - A Voltage notification is sent when a change is detected in the 5 volt backplane communication rails. The backplane communication rails are used by the bay controller to communicate with the occupant of a given slot. There are 8 rails, each servicing the slots in one half of a shelf in the bay (aviciBayVoltageIndex = rail):
5 Volt Rails:
-------------
Rail Slots Index
=====================
1 1 - 5 1
2 6 - 10 2
3 11 - 15 3
4 16 - 20 4
5 21 - 25 5
6 26 - 30 6
7 31 - 35 7
8 36 - 40 8
If the voltage is out of specification, the communication path will not function. When a given backplane communication channel is not functioning, modules serviced by this rail cannot be discovered (if a module is inserted) and will not be authorized to boot (if an existing module reboots). The current voltage is reported in the aviciBayVoltage object. A human readable description of the event triggering this notification is
included in the aviciSysTrapDescr object.The breaker rails refer to the rails for each power breaker. There are 2 redundant breakers for each shelf. On the TSR they are organized as follows:
|
AVICI-BAY-MIB
(continued)
|
There are 2 redundant breakers for each shelf. On the TSR they
are organized as follows:
-48 Volt Rails:
---------------
Rail Shelf Index
=====================
1 1a 9
2 2a 10
3 3a 11
4 4a 12
5 5a 13
aviciBayFanNotification: A Fan notification is sent when the specified fan detects a fault or clears a fault. The current ambient air temperature entering the fan is reported in the aviciBayFanCurrTemp object. All existing fan faults are reported in the aviciBayFanCurrFailures object as a bitmap. If no failures exist, this object contains a 0. A human readable description of the event triggering this notification is included in the aviciSysTrapDescr object.
Bit 0 Communication Failure: This failure indicates that the cooling module has been removed or the cooling module firmware is no longer communicating with the bay controller. If a communication failure occurs, the fans will run in autonomous mode until communication with the bay controller is reestablished. Once communication is established, the failure is cleared.
Bit 1 General Failure: This failure indicates that the cooling module firmware is able to communicate with the bay controller and is reporting a broken fan. This could mean that the fan is burned out, jammed, or the firmware is unable to sense fan speed due to tachometer failure. When the problem is corrected, the failure is cleared.
Bit 2 Filter Blocked: This failure indicates that the fan detected that the filter is blocked. When the obstruction is removed from the filter or the clogged air filter is replaced, this failure will clear.
Bit 3 Bad or absent internal thermistor: This failure indicates that the fan internal thermistor is missing or is not functioning. If the thermister is not functioning, the fan cannot sense the incoming ambient air temperature. The ambient temperature is used to control fan speed in autonomous mode and when there are no modules reporting their current temperature.
Bit 4 Bad or absent external thermistor: This failure indicates that the fan external thermistor is expected to be installed and is not functioning.
Bit 5 Minor temperature threshold: This failure indicates that the incoming ambient air temperature is above the minor threshold temperature, but below the major threshold temperature. Either the cooling system in the building has failed, or it has insufficient cooling capacity for the equipment in the room. A rapid rise in temperature usually indicates cooling system failure whereas a slow rise usually indicates insufficient cooling capacity. When the temperature drops below the minor threshold, this failure will clear.
|
AVICI-BAY-MIB
(Continued)
|
Bit 6 Major temperature threshold: This failure indicates that the incoming ambient air temperature is above the major threshold temperature, but below the critical threshold temperature. Either the cooling system in the building has failed, or it has insufficient cooling capacity for the equipment in the room. A rapid rise in temperature usually indicates cooling system failure whereas a slow rise usually indicates insufficient cooling capacity. When the temperature drops below the major threshold, this failure will clear.
Bit 7 Critical temperature threshold: This failure indicates that the incoming ambient air temperature is above the critical threshold temperature. Either the cooling system in the building has failed, or it has insufficient cooling capacity for the equipment in the room. A rapid rise in temperature usually indicates cooling system failure whereas a slow rise usually indicates insufficient cooling capacity. When the temperature drops below the critical threshold, this failure will clear.
aviciBayBreakerNotification indicates the specified breaker has tripped or been manually reset. The breaker may have tripped due to a short circuit, excessive current being drawn, or by an excessively high incoming voltage. This failure is cleared when the breaker is manually reset. If the breaker is manually opened, no trap will be sent.
aviciBayMultiFanFailures indicates two or more fans have failed in this bay.
aviciBayMultiBayControllerFailures indicates both bay controllers have failed in this bay.
aviciBayMultiBayMonitorFailures indicates both bay monitor controllers have failed in this bay.
|
BGP-MIB
|
bgpEstablished generates when the BGP FSM enters the ESTABLISHED state.
bgpBackwardTransition generates when the BGP FSM moves from a higher numbered state to a lower numbered state.
|
AVICI-BGP-MIB
|
aviciBgpSessionPolluted is generated when routes have been rejected from this BGP session. A BGP route is rejected when any of four thresholds is exceeded. The thresholds are:
- aviciBgpConfigMinimumMemoryThreshold
- aviciBgpConfigPrefixesThreshold
- aviciBgpConfigRouteInstancesThreshold
- aviciBgpPeerConfigPrefixes.
The session must be manually cleared in the CLI.
aviciBgpSessionCleared is generated after a BGP session has been manually cleared in the CLI.
|
AVICI-SONET-MIB
|
aviciSonetSectionEvent specifies which events have occurred in the current 15 minute interval. The value represents a vector of bits, each specifying a unique event:
- Bit 0 Rising threshold alarm, sonetSectionCurrentES
- Bit 1 Rising threshold alarm, sonetSectionCurrentSESs.
- Bit 2 Rising threshold alarm, sonetSectionCurrentSEFSs.
- Bit 3 Rising threshold alarm, sonetSectionCurrentCVs.
- Bit 4 Reserved.
- Bit 5 LOS (Loss of signal) failure indication.
- Bit 6 LOS failure cleared.
- Bit 7 LOF (Loss of frame) failure indication.
- Bit 8 LOF failure cleared.
|
AVICI-SONET-MIB
|
aviciSonetPathEvent specifies which events have occurred in the current 15 minute interval. The value represents a vector of bits, each specifying a unique event:
- Bit 0 Rising threshold alarm, sonetPathCurrentESs.
- Bit 1 Rising threshold alarm, sonetPathCurrentSESs.
- Bit 2 Reserved.
- Bit 3 Rising threshold alarm, sonetPathCurrentCVs.
- Bit 4 Rising threshold alarm, sonetPathCurrentUASs.
- Bit 5 LOP (loss of pointer) failure indication.
- Bit 6 LOP failure cleared.
- Bit 7 AIS (alarm indication signal) failure indication.
- Bit 8 AIS failure cleared.
- Bit 9 RFI (remote defect indication) indication.
- Bit 10 RFI cleared.
- Bit 11 UNEQ failure indication.
- Bit 12 UNEQ failure cleared.
- Bit 13 PLM failure indication.
- Bit 14 PLM failure cleared.
aviciSonetLineEvent specifies which events have occurred in the current 15 minute interval. The value represents a vector of bits, each specifying a unique event:
- Bit 0 Rising threshold alarm, sonetLineCurrentESs.
- Bit 1 Rising threshold alarm, sonetLineCurrentSESs.
- Bit 2 Reserved.
- Bit 3 Rising threshold alarm, sonetLineCurrentCVs.
- Bit 4 Rising threshold alarm, sonetLineCurrentUASs.
- Bit 5 AIS (alarm indication signal) failure indication.
- Bit 6 AIS failure cleared.
- Bit 7 RFI (remote failure indication
- Bit 8 RFI cleared.
aviciSonetFarEndLineEvent specifies which events have occurred in the current 15 minute interval. The value represents a vector of bits, each specifying a unique event:
- Bit 0 Rising threshold alarm, sonetFarEndLineCurrentESs.
- Bit 1 Rising threshold alarm, sonetFarEndLineCurrentSESs.
- Bit 2 Reserved.
- Bit 3 Rising threshold alarm, sonetFarEndLineCurrentCVs.
Bit 4 Rising threshold alarm, sonetFarEndLineCurrentUASs
aviciSonetFarEndPathEvent specifies which events have occurred in the current 15 minute interval. The value represents a vector of bits, each specifying a unique event:
- Bit 0 Rising threshold alarm, sonetFarEndPathCurrentESs.
- Bit 1 Rising threshold alarm, sonetFarEndPathCurrentSESs.
- Bit 2 Reserved.
- Bit 3 Rising threshold alarm, sonetFarEndPathCurrentCVs.
Bit 4 Rising threshold alarm, sonetFarEndPathCurrentUASs
|
AVICI-SERVER-MIB
|
aviciServerUp signifies the server changed state to "up".
aviciServerDown signifies the server detected that a peer server went down.
aviciServerHeartbeatUp signifies the server heartbeat transitioned to "up".
aviciServerHeartbeatDown signifies the server heartbeat transitioned to "down".
aviciServerDefaultConfigFileChanged indicates that the default configuration file startup.cfg has changed.
aviciServerDisqualified indicates that a route server has entered
a disqualified role.
aviciServerFailedToDetectBackupServer sends when a primary route server which is in a administratively Hot or Warm standby mode fails to detect a backup server.
aviciServerDetectedBackupServer sends when a primary route server which is in a administratively Hot or Warm standby mode detects a backup server.
aviciServerStateTransition sends when server state transition occurs.
aviciServerLdpFecVerifyInconsistent sends when periodic LDP FEC verifications finds inconsistent FECs.
aviciServerLdpFecVerifyConsistent sends when periodic LDP FEC verifications finds all FECs to be consistent. This notification is sent only if the last periodic verification cycle found some FECs to be
inconsistent.
aviciServerMisconfigured signifies a server is misconfigured and must be manually configured.
aviciServerUseAuthenication Failure indicates a user has tried to log and failed to be authorized after the maximum number of retries.
aviciServerMemoryThresholdExceeded indicates free memory has fallen below the configured threshold for the system.
aviciServerMemoryThresholdCleared indicates the free memory has risen above the falling configured threshold for the system.
aviciServerPkgFileReadFailure indicates that the package file containing the images cannot be read to extract version information and the images.
aviciServerIncompatibleSW indicates that the server is running an image that is incompatible with the image contained in the package file.
aviciServerDefaultConfigFileChanged indicates the default configuration file start.cfg has changed.
aviciServerCPUThresholdExceeded indicates the CPU loading has risen above the rising threshold for the system
aviciServerCPUThresholdCleared indicates the CPU loading has dropped below the falling threshold for the system.
|
OSPF (RFC 1850)
|
ospfIfStateChange An ospfIfStateChange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the interface state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup)
ospfVirtIfStateChange An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF virtual interface.
ospfNbrStateChange An ospfNbrStateChange trap signifies that there has been a change in the state of a non-virtual OSPF neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). When an neighbor transitions from or to Full on non-broadcast multi-access and broadcast networks, the trap should be generated by the designated router. A designated router transitioning to Down will be noted by ospfIfStateChange.
ospfVirtNbrStateChange An ospfIfStateChange trap signifies that there has been a change in the state of an OSPF virtual neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full).
ospfIfConfigError An ospfIfConfigError trap signifies that a packet has been received on a non-virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a trap only if it prevents an adjacency from forming.
ospfVirtIfConfigError An ospfConfigError trap signifies that a packet has been received on a virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a trap only if it prevents an adjacency from forming.
ospfIfAuthFailure An ospfIfAuthFailure trap signifies that a packet has been received on a non-virtual interface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.
|
OSPF (RFC 1850)
(Continued)
|
ospfVirtIfAuthFailure An ospfVirtIfAuthFailure trap signifies that a packet has been received on a virtual interface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.
ospfIfRxBadPacket An ospfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
ospfVirtIfRxBadPacket An ospfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.
ospfTxRetransmit An ospfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a non-virtual interface. All packets that may be re-transmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
ospfVirtIfTxRetransmit An ospfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
ospfOriginateLsa An ospfOriginateLsa trap signifies that a new LSA has been originated by this router. This trap should not be invoked for simple refreshes of LSAs (which happens every 30 minutes), but instead will only be invoked when an LSA is (re)originated due to a topology change. Additionally, this trap does not include LSAs that are being flushed because they have reached MaxAge.
ospfMaxAgeLsa An ospfMaxAgeLsa trap signifies that one of the LSA in the router's link-state database has aged to MaxAge.
ospfLsdbOverflow trap signifies that the number of LSAs in the router's link-state data-base has exceeded ospfExtLsdbLimit.
ospfLsdbApproachingOverflow signifies that the number of LSAs in the router's link-state database has exceeded ninety percent of ospfExtLsdbLimit.
|
BGP (RFC 1657)
|
bgpEstablished (RFC 1657)The BGP Established event is generated when the BGP FSM enters the ESTABLISHED state.
bgpBackwardTransition (RFC 1657) The BGPBackwardTransition Event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.
|
Miscellaneous
|
risingAlarm (RFC1757)
fallingAlarm (RFC1757)
coldStart (RFC1907) trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself and that its configuration may have been altered.
warmStart (RFC1907)trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself such that its configuration is unaltered.
authenticationFailure (RFC1907) This functionality will be supported in a future release.
linkDown trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links
is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of ifOperStatus.
linkUp signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication linksleft the down state and transitioned into some other state (but not into the notPresent state). This other state is indicated by the included value of
ifOperStatus.
|
PIM (RFC 2934)
|
pimNeighborLoss trap signifies the loss of an adjacency with a neighbor. This trap is generated when the neighbor timer expires, and the router has no other neighbors on the same interface with a lower IP address than itself.
|
LDP-MIB
(draft-mpls-ldp-mib
-07.txt)
|
mplsLdpEntityFailedInitSessonThresholdExceeded generates when mplLdpEntityFailedInitSessionTrapEnable is set to enabled and the value of mplsLdpEntityFailedInitSessionThreshold object has been exceeded.
MplsLdpEntityPathVectorLimitMismatch generates when mplLdpEntityFailedInitSessionTrapEnable is set to enable and the mplsLdpEntityPathVectorLimit value does not match the value of mplsLdpPeerPathVectorLimit.
MplsLdpSessionUp generates when mplLdpSessionUpDownTrapEnable is set to enable and the value of mplsLdpSessionState changes from any state except nonexistent(1) to operational(5).
MplsLdpSessionDown generates when plLdpSessionUpDownTrapEnable is set to enable and the value of mplsLdpSessionState changes from operational(5) to any other state.
|
MSDP-MIB
|
msdpEstablished event generates when the MSDP FSM
enters the ESTABLISHED state.
msdpBackwardTransition Event generates when the MSDP
FSM moves from a higher numbered state to a lower numbered
state.
|
TE-MIB
(derived from draft-ietf-tewg-mib
-00.txt)
|
teTunnelUp signifies that the specified tunnel is up. The current active path for the tunnel is tePathName.
teTunnelDown signifies that the specified tunnel is down, because the current active path tePathName went down.
teTunnelChange signifies that the specified tunnel has switched traffic to the new active path 'toTunnelPath'. The tunnel maintains up state before and after the switch over.
teMainLSPFullyProtected signifies that the main LSP is fully protected along the entire path.
teMainLSPPartiallyProtected signifies that the main LSP is only partially protected.
teTunnelBackupInUse signifies that the specified Tunnel has switched traffic to the backup tunnel 'teTunnelName'.
teTunnelBackupNotInUse signifies that the specified Tunnel has switched traffic from the backup tunnel 'x' back to the primary tunnel. The switch occurs when the primary recovers from the failure that caused the backup to take over.
|
AVICI-QOS-MIB
|
These traps are typically generated only when queues are configured using absolute bandwidth or buffer spaces, and the loss of a member-link is sufficient to impact configured queues.
aviciQosConfigBWChange is generated by an interface when the configured bandwidth is changed. This can happen when a member of a composite interface is lost.
aviciQosConfigBWRestored is generated by an interface when bandwidth is restored to its original configuration. This can happen when a member of a composite interface is restored.
aviciQosConfigBufferSpaceChange is generated by an interface when configured queue depth is lost. This can happen when a member of a composite interface is lost.
aviciQosConfigBufferSpaceRestored is generated by an interface when configured queue depth is restored. This can happen when a member of a composite interface is restored.
|
AVICI-COMPOSITE
LINK-MIB
|
aviciMemberLinkAdd signifies that a new memberLink interface has been administratively added as a member of this compositeLink interface.
aviciMemberLinkRemove signifies that a memberLink interface has been administratively removed as a member of this compositeLink interface.
aviciCompositeLinkActualBWIncrease signifies that the actual bandwidth available on the specified compositeLink interface has increased by the amount in aviciCompositeLinkActualBWChange.
aviciCompositeLinkActualBWDecrease signifies that the actual bandwidth available on the specified compositeLink interface has decreased by the amount in aviciCompositeLinkActualBWChange.
aviciCompositeLinkUp signifies that the minimal number of link members are present and operational such that the composite linkidentified by aviciCompositeLinkIfIndex itself becomes operational.The last such member to go operational is indicated by the aviciMemberLinkIfIndex object.
aviciCompositeLinkDown signifies that the minimal number oflink members are no longer present and/or operational such that the composite linkidentified by aviciCompositeLinkIfIndex itself becomes non-operational.The last such member to go out of service is indicated by theaviciMemberLinkIfIndex object.
aviciMemberLinkAdd signifies that a new memberLink interface has been administratively added as a member of this compositeLink interface. IfName contains the name of the member link added to this composite link.IfHighSpeed contains the bandwidth of the new member.
aviciMemberLinkRemove signifies that a memberLink interface has been administratively removed as a member of this compositeLink interface. IfName containsthe name of the member link removed from this composite link.IfHighSpeed contains the bandwidth of the removed member.
|
SNMP Sets Supported
Other than those listed below, SNMP sets are not supported:
- SysName - also set using the hostname command
- SysLocation - also set using the snmp-server location command
- SysContact - also set using the snmp-server contact command
- SnmpSetSerialNo - An advisory lock used to allow several cooperating SNMPv2 entities, all acting in a manager role, to coordinate their use of the SNMPv2 set operation.
- This object is used for coarse-grain coordination. To achieve fine-grain coordination, one or more similar objects might be defined within each MIB group, as appropriate.
RMON sets Supported
Starting in Release 3.3, the following sets are supported in RMON (RFC 1757):
- In the Alarm Table:
- alarmInterval
- alarmVariable
- alarmSampleType
- alarmStartupAlarm
- alarmRisingThreshold
- alarmFallingThreshold
- alarmRisingEventIndex
- alarmFallingEventIndex
- alarmOwner
- alarmStatus
- In the Event Table:
- eventDescription
- eventType
- eventCommunity
- eventOwner
- eventStatus
- In the History Control Table:
- historyControlDataSource
- historyControlBucketsRequested
- historyControlInterval
- historyControlOwner
- historyControlStatus
- In the EtherStatsTable:
- etherStatsDataSource
- etherStatsOwner
- etherStatsStatus
Refer to "Configuring Remote Monitoring" chapter for the steps to configure and display RMON.
