All MIBs › CISCO-WAN-TRAP-VARS-MIB
Organization: Cisco Systems, Inc.
Last Updated: 2002-11-26
Category: Alarm and Event Management, Device Management, Vendor: Cisco Devices
Description: Defines Cisco WAN trap variable objects used as varbinds in SNMP notifications on MGX platforms.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is CISCO-WAN-TRAP-VARS-MIB?
CISCO-WAN-TRAP-VARS-MIB defines a set of varbind objects used exclusively inside SNMP trap definitions for Cisco WAN switch platforms (MGX/BPX), rather than as objects meant to be polled directly via GET/GET-NEXT. It provides generic fields such as slot number, physical vendor type, line module number, card role, and free-form octet/display strings that traps reference to carry contextual details about the hardware or SCT template involved in a fault event. Its monitoring relevance is entirely trap-driven fault/status reporting: when a card, slot, or SCT-related trap fires elsewhere in the Cisco WAN MIB set, these vars (e.g., cwTrapSlotNumber, cwTrapCardRole) populate the notification with the specific hardware location and role affected, helping an operator pinpoint which physical card or module triggered an alarm. It is a dependency-only support MIB, providing shared varbinds consumed by numerous other Cisco WAN switch trap-defining MIBs. It is used throughout Cisco MGX/BPX WAN switch deployments wherever hardware or configuration traps are generated. Network engineers evaluating or troubleshooting this functionality can download the CISCO-WAN-TRAP-VARS-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-WAN-TRAP-VARS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Cisco MGX/BPX WAN switches
Monitoring Examples
When a card-related trap fires on an MGX chassis, the notification's varbinds would include cwTrapSlotNumber and cwTrapPhysicalVendorType to identify exactly which slot and card type raised the alarm, along with cwTrapCardRole to indicate whether the affected card was primary or standby. cwTrapSctCardType/cwTrapSctId would appear in traps related to Service Class Template loading failures, tying the fault back to a specific SCT file.
What Can Be Monitored
- slot number and card role in fault traps
- physical vendor/card type
- line module identification
- SCT card type/ID referenced in traps
Imported Objects
From CISCOWAN-SMI
| ciscoWan | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| AutonomousType | |
| DisplayString |
OIDs
RFC description
Defines variables used exclusively in SNMP trap definitions for Cisco WAN and ATM equipment monitoring.
Start monitoring Cisco MGX/BPX WAN switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.