NSCTRAP
File:
NSCTRAP.mib (13916 bytes)
Imported modules
Imported symbols
Defined Values
nsc |
1.3.6.1.4.1.10 |
OBJECT IDENTIFIER |
|
|
|
nscMib |
1.3.6.1.4.1.10.2 |
OBJECT IDENTIFIER |
|
|
|
nscTraps |
1.3.6.1.4.1.10.2.2.4 |
OBJECT IDENTIFIER |
|
|
|
nscTrapsProtBindIndex |
1.3.6.1.4.1.10.2.2.4.1 |
The communication protocols whose bind state changes
would cause traps to be generated. |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
INTEGER |
ip(1), decnet(2), appleTalk(3), ipx(4), xns(5), bridging(9), bridgingEc(10) |
|
nscTrapsFddiSMTCFState |
1.3.6.1.4.1.10.2.2.4.2 |
The attachment configuration for the station or
concentrator. The values are the same as those
defined in the SMT group in RFC-1285. |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
INTEGER |
cf0(1), cf1(2), cf2(3), cf3(4), cf4(5), cf5(6) |
|
nscTrapsDecNetAreaNbr |
1.3.6.1.4.1.10.2.2.4.3 |
Tok_String |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
Size(1) |
|
nscTrapsDecNetNodeNbr |
1.3.6.1.4.1.10.2.2.4.4 |
Tok_String |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
Size(1) |
|
nscTrapsDecNetEventReason |
1.3.6.1.4.1.10.2.2.4.6 |
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). |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(1..256) |
|
nscTrapsDecNetReachStatus |
1.3.6.1.4.1.10.2.2.4.7 |
The reachable status of a node or area. |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
INTEGER |
reachable(1), unreachable(2) |
|
nscTrapsVcpLogicalState |
1.3.6.1.4.1.10.2.2.4.9 |
The logical state of a VCP port. The possible states
are ACTIVE, DOWN, DISABLED. |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..30) |
|
nscTrapsVcpPhysicalState |
1.3.6.1.4.1.10.2.2.4.10 |
The physical state of a VCP port. The possible states
are Off, On, Broken_Cannot_IO, Broken_Purge,
Broken_Reconfigure, Broken_Misconfigure. |
Status: mandatory |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..30) |
|
protocolBound |
1 |
A protocolBound trap is sent when a protocol is bound
to an interface. |
TRAP-TYPE |
|
|
|
protocolUnbound |
2 |
A protocolBound trap is sent when a protocol is unbound
from an interface. |
TRAP-TYPE |
|
|
|
physicalLinkUp |
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. |
TRAP-TYPE |
|
|
|
physicalLinkDown |
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. |
TRAP-TYPE |
|
|
|
fddiWrap |
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. |
TRAP-TYPE |
|
|
|
vcpActive |
6 |
This trap indicates that a VCP physical link just came up. |
TRAP-TYPE |
|
|
|
vcpInactive |
7 |
This trap indicates that a VCP physical link just went down. |
TRAP-TYPE |
|
|
|
vcpReconfig |
8 |
This trap indicates that a VCP physical link is reconfiguring. |
TRAP-TYPE |
|
|
|
vcpBroken |
9 |
This trap indicates that a VCP physical link lost connection
with its remote end. |
TRAP-TYPE |
|
|
|
decNetCircDownFault |
407 |
This trap shows that a fault has brought down
the indicated DECnet circuit. |
TRAP-TYPE |
|
|
|
decNetCircDown |
408 |
This trap indicates that the named DECnet circuit
is down. (This trap is not supported.) |
TRAP-TYPE |
|
|
|
decNetCircUp |
410 |
This trap indicates that a DECnet circuit has
become enabled. |
TRAP-TYPE |
|
|
|
decNetNodeReachChg |
414 |
This trap reports a change in the nodes that can be
reached. (This trap is not supported.) |
TRAP-TYPE |
|
|
|
decNetAdjUp |
415 |
This trap indicates that a DECnet adjacent node
just has come up. |
TRAP-TYPE |
|
|
|
decNetAdjRejected |
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. |
TRAP-TYPE |
|
|
|
decNetAreaReachChg |
417 |
This trap reports a change in the areas that can be
reached. (This trap is not supported.) |
TRAP-TYPE |
|
|
|
decNetAdjDown |
418 |
This trap indicates that a adjacent node has
come down or lost. |
TRAP-TYPE |
|
|
|