When we receive an LSP with our System ID
and different contents, we may need to reissue
the LSP with a higher sequence number.
We send this notification if we need to increase
the sequence number by more than one. If two
Intermediate Systems are configured with the same
System ID, this notification will fire.
Parsed from file CISCO-IETF-ISIS-MIB.mib
Module: CISCO-IETF-ISIS-MIB
When we receive an LSP with our System ID
and different contents, we may need to reissue
the LSP with a higher sequence number.
We send this notification if we need to increase
the sequence number by more than one. If two
Intermediate Systems are configured with the same
System ID, this notification will fire.
Parsed from file CISCO-IETF-ISIS-MIB.my.txt
Company: None
Module: CISCO-IETF-ISIS-MIB
When we receive an LSP with our System ID
and different contents, we may need to reissue
the LSP with a higher sequence number.
We send this notification if we need to increase
the sequence number by more than one. If two
Intermediate Systems are configured with the same
System ID, this notification will fire.
ciiSequenceNumberSkip NOTIFICATION-TYPE OBJECTS { ciiNotifIsLevelIndex, ciiCircIfIndex, ciiPduLspId } STATUS current DESCRIPTION "When we receive an LSP with our System ID and different contents, we may need to reissue the LSP with a higher sequence number. We send this notification if we need to increase the sequence number by more than one. If two Intermediate Systems are configured with the same System ID, this notification will fire." ::= { ciscoIetfIsisMIBNotifs 8 }
Vendor: Cisco
Module: CISCO-IETF-ISIS-MIB
[Automatically extracted from oidview.com]
ciiSequenceNumberSkip NOTIFICATION-TYPE OBJECTS { ciiNotifIsLevelIndex, ciiCircIfIndex, ciiPduLspId } STATUS current DESCRIPTION "When we receive an LSP with our System ID and different contents, we may need to reissue the LSP with a higher sequence number. We send this notification if we need to increase the sequence number by more than one. If two Intermediate Systems are configured with the same System ID, this notification will fire." ::= { ciscoIetfIsisMIBNotifs 8 }
ciiSequenceNumberSkip NOTIFICATION-TYPE OBJECTS { ciiNotifIsLevelIndex, ciiCircIfIndex, ciiPduLspId } STATUS current DESCRIPTION "When we receive an LSP with our System ID and different contents, we may need to reissue the LSP with a higher sequence number. We send this notification if we need to increase the sequence number by more than one. If two Intermediate Systems are configured with the same System ID, this notification will fire." ::= { ciscoIetfIsisMIBNotifs 8 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.10.118.0.1 | ciiDatabaseOverload | 0 | 0 | This notification is generated when the system enters or leaves the Overload state. The number of times this has be generated an… |
| 1.3.6.1.4.1.9.10.118.0.2 | ciiManualAddressDrops | 0 | 0 | This notification is generated when one of the manual areaAddresses assigned to this system is ignored when computing routes. Th… |
| 1.3.6.1.4.1.9.10.118.0.3 | ciiCorruptedLSPDetected | 0 | 0 | This notification is generated when we find that an LSP that was stored in memory has become corrupted. The number of times this… |
| 1.3.6.1.4.1.9.10.118.0.4 | ciiAttemptToExceedMaxSequence | 0 | 0 | When the sequence number on an LSP we generate wraps the 32 bit sequence counter, we purge and wait to re-announce this informati… |
| 1.3.6.1.4.1.9.10.118.0.5 | ciiIDLenMismatch | 0 | 0 | A notification sent when we receive a PDU with a different value of the System ID Length. This notification includes an index to … |
| 1.3.6.1.4.1.9.10.118.0.6 | ciiMaxAreaAddressesMismatch | 0 | 0 | A notification sent when we receive a PDU with a different value of the Maximum Area Addresses. This notification includes the he… |
| 1.3.6.1.4.1.9.10.118.0.7 | ciiOwnLSPPurge | 0 | 0 | A notification sent when we receive a PDU with our systemID and zero age. This notification includes the circuit Index and router… |
| 1.3.6.1.4.1.9.10.118.0.9 | ciiAuthenticationTypeFailure | 0 | 0 | A notification sent when we receive a PDU with the wrong authentication type field. This notification includes the header of the p… |
| 1.3.6.1.4.1.9.10.118.0.10 | ciiAuthenticationFailure | 0 | 0 | A notification sent when we receive a PDU with incorrect authentication information field. This notification includes the header… |
| 1.3.6.1.4.1.9.10.118.0.11 | ciiVersionSkew | 0 | 0 | A notification sent when we receive a Hello PDU from an IS running a different version of the protocol. This notification include… |
| 1.3.6.1.4.1.9.10.118.0.12 | ciiAreaMismatch | 0 | 0 | A notification sent when we receive a Hello PDU from an IS which does not share any area address. This notification includes the h… |
| 1.3.6.1.4.1.9.10.118.0.13 | ciiRejectedAdjacency | 0 | 0 | A notification sent when we receive a Hello PDU from an IS, but do not establish an adjacency for some reason. This should be an e… |
| 1.3.6.1.4.1.9.10.118.0.14 | ciiLSPTooLargeToPropagate | 0 | 0 | A notification sent when we attempt to propagate an LSP which is larger than the dataLinkBlockSize for the circuit. This should be… |
| 1.3.6.1.4.1.9.10.118.0.15 | ciiOrigLSPBuffSizeMismatch | 0 | 0 | A notification sent when a Level 1 LSP or Level 2 LSP is received which is larger than the local value for ciiSysLevelOrigLSPBuff… |
| 1.3.6.1.4.1.9.10.118.0.16 | ciiProtocolsSupportedMismatch | 0 | 0 | A notification sent when a non-pseudonode segment 0 LSP is received that has no matching protocols supported. This may be because … |
| 1.3.6.1.4.1.9.10.118.0.17 | ciiAdjacencyChange | 0 | 0 | A notification sent when an adjacency changes state, entering or leaving state up. The first 6 bytes of the ciiPduLspId are the Sy… |
| 1.3.6.1.4.1.9.10.118.0.18 | ciiLSPErrorDetected | 0 | 0 | This notification is generated when we receive an LSP with a parse error. The ciiCircIfIndex holds in index of the circuit on wh… |