All MIBs › NSCTRAP
Category: Legacy High-Performance Switching
Description:
Defines SNMP traps for NSC network device fault, status change, and threshold crossing events.
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC-1215
| TRAP-TYPE |
From RFC1155-SMI
| enterprises |
From RFC1213-MIB
| DisplayString | |
| ifDescr | |
| ifIndex | |
| ifType |
What Is NSCTRAP?
NSCTRAP is a vendor-specific SNMP MIB module from NSC that defines the trap (notification) catalog used to signal fault, status-change, and threshold-crossing events on NSC network devices. Rather than exposing polled counters or configuration tables itself, it standardizes the set of asynchronous alarm messages a device can emit, spanning hardware faults, operational state transitions, and performance-threshold breaches. In a hardware/software monitoring context this module is central to alerting: it is how an NSC device proactively reports conditions like component failure, status flapping, or a metric crossing a configured limit, rather than requiring constant polling. As a trap-definition module it typically depends on standard SNMPv2-SMI/SNMPv2-TC conventions for NOTIFICATION-TYPE objects and likely complements a separate NSC MIB that defines the polled objects referenced in trap varbinds. It is deployed wherever NSC equipment is managed by an NMS configured as a trap receiver for real-time fault alerting, making the NSCTRAP MIB a key reference for interpreting these fault notifications.
IPNetwork Monitor allows you to monitor SNMP objects defined in NSCTRAP. 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.
What Can Be Monitored
- device fault events
- status change notifications
- threshold-crossing alerts
Supported Devices
- NSC network device
- vendor-specific (NSC) network equipment
Monitoring Examples
No sample objects were provided for this module, and it appears to consist solely of trap/notification definitions rather than a polled object tree, so no specific table or object names can be cited. A monitoring scenario would involve an NMS trap receiver where an NSCTRAP notification (e.g., a threshold-crossing or fault trap) triggers an alert workflow, but the exact varbinds and severities cannot be confirmed without the MIB source.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| nsc | 1.3.6.1.4.1.10 | |||
| nscMib | 1.3.6.1.4.1.10.2 | |||
| nscManagement | 1.3.6.1.4.1.10.2.2 | |||
| nscTraps | 1.3.6.1.4.1.10.2.2.4 | |||
| NTF protocolBound | 1.3.6.1.4.1.10.2.2.4.0.1 | A protocolBound trap is sent when a protocol is bound to an interface. | ||
| NTF protocolUnbound | 1.3.6.1.4.1.10.2.2.4.0.2 | A protocolBound trap is sent when a protocol is unbound from an interface. | ||
| NTF physicalLinkUp | 1.3.6.1.4.1.10.2.2.4.0.3 | A physicalLinkUp trap is sent for devices that represent both a logical and physical device. The physicalLinkUp trap is sent when the physical device becomes active. The SNMP linkUp is sent when the logical device becomes active. | ||
| NTF physicalLinkDown | 1.3.6.1.4.1.10.2.2.4.0.4 | A physicalLinkDown trap is sent for devices that represent both a logical and physical device. The physicalLinkDown trap is sent when the physical device becomes not active. The SNMP linkDown is sent when the logical device becomes not active. | ||
| NTF fddiWrap | 1.3.6.1.4.1.10.2.2.4.0.5 | A FDDI wrap trap indicates that a FDDI ring is broken and the signal path wraps through a device and out the parallel fiber. The trap also occures when the wrapped condition is relieved. | ||
| NTF vcpActive | 1.3.6.1.4.1.10.2.2.4.0.6 | This trap indicates that a VCP physical link just came up. | ||
| NTF vcpInactive | 1.3.6.1.4.1.10.2.2.4.0.7 | This trap indicates that a VCP physical link just went down. | ||
| NTF vcpReconfig | 1.3.6.1.4.1.10.2.2.4.0.8 | This trap indicates that a VCP physical link is reconfiguring. | ||
| NTF vcpBroken | 1.3.6.1.4.1.10.2.2.4.0.9 | This trap indicates that a VCP physical link lost connection with its remote end. | ||
| NTF vcpMisconfigured | 1.3.6.1.4.1.10.2.2.4.0.10 | This trap indicates that a VCP physical link has detected different configuration on the remote end. | ||
| NTF decNetCircDownFault | 1.3.6.1.4.1.10.2.2.4.0.407 | This trap shows that a fault has brought down the indicated DECnet circuit. | ||
| NTF decNetCircDown | 1.3.6.1.4.1.10.2.2.4.0.408 | This trap indicates that the named DECnet circuit is down. (This trap is not supported.) | ||
| NTF decNetCircUp | 1.3.6.1.4.1.10.2.2.4.0.410 | This trap indicates that a DECnet circuit has become enabled. | ||
| NTF decNetNodeReachChg | 1.3.6.1.4.1.10.2.2.4.0.414 | This trap reports a change in the nodes that can be reached. (This trap is not supported.) | ||
| NTF decNetAdjUp | 1.3.6.1.4.1.10.2.2.4.0.415 | This trap indicates that a DECnet adjacent node just has come up. | ||
| NTF decNetAdjRejected | 1.3.6.1.4.1.10.2.2.4.0.416 | This trap indicates that an adjacent node has been rejected of communication, or become inactive. The reason could be either the numbers of broadcast (non)routers or the address of a node exceeds the ones in the router's configuartion. | ||
| NTF decNetAreaReachChg | 1.3.6.1.4.1.10.2.2.4.0.417 | This trap reports a change in the areas that can be reached. (This trap is not supported.) | ||
| NTF decNetAdjDown | 1.3.6.1.4.1.10.2.2.4.0.418 | This trap indicates that a adjacent node has come down or lost. | ||
| NTF decNetDesignatedRouter | 1.3.6.1.4.1.10.2.2.4.0.422 | This trap reports a change in the designated router. | ||
| INT nscTrapsProtBindIndex | 1.3.6.1.4.1.10.2.2.4.1 | INTEGER | not-accessible | The communication protocols whose bind state changes would cause traps to be generated. |
| INT nscTrapsFddiSMTCFState | 1.3.6.1.4.1.10.2.2.4.2 | INTEGER | not-accessible | The attachment configuration for the station or concentrator. The values are the same as those defined in the SMT group in RFC-1285. |
| OCT nscTrapsDecNetAreaNbr | 1.3.6.1.4.1.10.2.2.4.3 | OCTET STRING | not-accessible | |
| OCT nscTrapsDecNetNodeNbr | 1.3.6.1.4.1.10.2.2.4.4 | OCTET STRING | not-accessible | |
| STR nscTrapsDecNetCircuitName | 1.3.6.1.4.1.10.2.2.4.5 | DisplayString | not-accessible | The name of a DECnet circuit. |
| STR nscTrapsDecNetEventReason | 1.3.6.1.4.1.10.2.2.4.6 | DisplayString | not-accessible | The reason that causes the routing event to happen. Possible reasons are: SYNC_LOST (0), DATA_ERRORS (1), UNEXPECTED_PKT_TYPE (2), ROUTING_UPDATE_CHECKSUM_ERROR (3), ADJ_ADDR_CHANGE (4), VERIF_RECV_TIMEOUT (5), VERSION_SKEW (6), ADJ_ADDR_OUT_OF_RANGE (7), ADJ_BLOCK_SIZE_TOO_SMALL (8), INVALID_VERIF_SEED_VALUE (9), ADJ_LIST_RECV_TIMEOUT (10), ADJ_LIST_RECV_INVALID_DATA (11), CALL_FAILED (12), VERIF_PASSWORD_REQ_FROM_PIII_NODE (13), DROPPED_BY_ADJ_NODE (14). |
| INT nscTrapsDecNetReachStatus | 1.3.6.1.4.1.10.2.2.4.7 | INTEGER | not-accessible | The reachable status of a node or area. |
| STR nscTrapsVcpPortName | 1.3.6.1.4.1.10.2.2.4.8 | DisplayString | not-accessible | The name of the VCP port. |
| STR nscTrapsVcpLogicalState | 1.3.6.1.4.1.10.2.2.4.9 | DisplayString | not-accessible | The logical state of a VCP port. The possible states are ACTIVE, DOWN, DISABLED. |
| STR nscTrapsVcpPhysicalState | 1.3.6.1.4.1.10.2.2.4.10 | DisplayString | not-accessible | The physical state of a VCP port. The possible states are Off, On, Broken_Cannot_IO, Broken_Purge, Broken_Reconfigure, Broken_Misconfigure. |
RFC description
Network System Corporation enterprise trap MIB defining SNMP notifications for protocol binding and FDDI state changes.
Start monitoring NSC network device (fault/threshold trap catalog) 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.