isis
isisAdjacencyBfdSessionSetupFailed
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisAdjacencyBfdSessionSetupFailed |
Default severity |
warning |
Message format string |
In network-instance network_instance, BFD session setup failed for the level IS-IS adjacency with system sys_id, using interface subinterface. Failure reason: bfd_failure_reason. |
Cause |
This event is generated when BFD session setup fails with an adjacent neighbor. |
Effect |
Fast failure detection may not be possible. |
isisAdjacencyChange
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisAdjacencyChange |
Default severity |
warning |
Message format string |
In network-instance network_instance, the level IS-IS adjacency with system sys_id, using interface subinterface, moved to state adj_state. |
Cause |
This event is generated when an IS-IS adjacency enters or leaves the up state. |
Effect |
IS-IS traffic can only be forwarded along adjacencies that are up. |
isisAdjacencyRestartStatusChange
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisAdjacencyRestartStatusChange |
Default severity |
warning |
Message format string |
In network-instance network_instance, the graceful restart status for the level IS-IS adjacency on interface subinterface moved to new state restart_status. |
Cause |
This event is generated when the graceful restart status of a neighbor changes. |
Effect |
None |
isisAreaMismatch
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisAreaMismatch |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level1 PDU was received on interface subinterface with no Area Addresses matching the areas to which this IS router belongs. The PDU starts with: pdu_fragment |
Cause |
This event is generated to alert of a possible area-id misconfiguration inside a L1 area. |
Effect |
L1 adjacency cannot form |
isisAuthDataFail
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisAuthDataFail |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level PDU was received on interface subinterface with unexpected or incorrect data in the Authentication TLV. The PDU starts with: pdu_fragment |
Cause |
This event could be caused by incorrect keychain configuration in this router or its neighbor. |
Effect |
PDUs are dropped, with the effect depending on the PDU type |
isisAuthTypeMismatch
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisAuthTypeMismatch |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level PDU was received on interface subinterface with an unrecognized or unsupported authentication type in TLV 10. The PDU starts with: pdu_fragment |
Cause |
This event could be caused by incorrect keychain configuration in this router or its neighbor. |
Effect |
PDUs are dropped, with the effect depending on the PDU type |
isisCircuitIdsExhausted
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisCircuitIdsExhausted |
Default severity |
warning |
Message format string |
In network-instance network_instance, the IS-IS interface subinterface is operationally down because the limit of 255 circuit IDs available to LAN interfaces was reached. |
Cause |
This event is caused by having too many LAN interfaces. |
Effect |
LAN adjacencies are not formed |
isisCircuitMtuTooLow
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisCircuitMtuTooLow |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level LSP PDU or SNP PDU could not be transmitted on interface subinterface because the IP MTU is only operational_subif_mtu and an MTU of at least required_mtu is required. |
Cause |
The port MTU is too small and/or the lsp-mtu-size is too large. |
Effect |
PDUs are dropped |
isisCorruptedLspDetected
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisCorruptedLspDetected |
Default severity |
warning |
Message format string |
In network-instance network_instance, the LSP PDU with ID lsp_id in the level database has become corrupted. |
Cause |
Memory corruption or other. |
Effect |
LSP is removed |
isisLdpSyncExited
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisLdpSyncExited |
Default severity |
warning |
Message format string |
In network-instance network_instance, the LDP synchronization state has ended on IS-IS interface subinterface, and now the state is sync_state |
Cause |
The LDP synchronization timer can be stopped because of a tools command, hold-down timer expiry or indication from the LDP peer that End-of-LIB has been received. When LDP sync is exited IS-IS resumes advertising a normal metric for the interface. |
Effect |
Transit traffic can start using this interface again. |
isisLdpSyncTimerStarted
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisLdpSyncTimerStarted |
Default severity |
warning |
Message format string |
In network-instance network_instance, the LDP synchronization timer has started on IS-IS interface subinterface |
Cause |
The sync timer is started when LDP synchronization is configured and the LDP adjacency comes up with the LDP peer. When this timer expires IS-IS will resume advertisement of a normal metric for the interface. |
Effect |
Transit traffic will continue to avoid using this interface. |
isisLspFragmentTooLarge
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisLspFragmentTooLarge |
Default severity |
warning |
Message format string |
In network-instance network_instance, the level LSP PDU fragment lsp_id received on interface subinterface could not be accepted because the configured LSP MTU size is too small. An LSP MTU size of at least required_lsp_mtu bytes is required. |
Cause |
Misconfiguration of LSP MTU size |
Effect |
LSP PDU is not accepted |
isisLspPurge
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisLspPurge |
Default severity |
warning |
Message format string |
In network-instance network_instance, the LSP PDU with ID lsp_id in the level database has been purged by purge_originator. |
Cause |
LSP lifetime expired or other reason |
Effect |
The PDU is removed |
isisLspSequenceNumberSkip
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisLspSequenceNumberSkip |
Default severity |
warning |
Message format string |
In network-instance network_instance, the LSP with id lsp_id in the level database was re-originated with a sequence number that incremented by more than one. |
Cause |
There may be another IS router configured with the same system ID. |
Effect |
None |
isisMaxAreaAddressesMismatch
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisMaxAreaAddressesMismatch |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level PDU was received on interface subinterface with an unexpected Max Area Addresses value in the IS-IS PDU header. The PDU starts with: pdu_fragment |
Cause |
Misconfiguration of max area addresses in the neighbor |
Effect |
The PDU is dropped |
isisMaxLspSequenceNumberExceeded
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisMaxLspSequenceNumberExceeded |
Default severity |
warning |
Message format string |
In network-instance network_instance, the LSP with id lsp_id in the level database was purged because the sequence number was already at its maximum value and could not be incremented. |
Cause |
A possible cause could be that the same system-id is configured on multiple systems; when 2 systems have the same system-id they both keep incrementing the LSP sequence number, causing the sequence counter to rollover. |
Effect |
The PDU is purged and reachability may be temporarily lost |
isisOverloadEntry
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisOverloadEntry |
Default severity |
warning |
Message format string |
In the IS-IS instance of network-instance network_instance, the level database has entered the overload state. |
Cause |
Overload bit configuration |
Effect |
No transit traffic is routed through the overloaded router. |
isisOverloadExit
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisOverloadExit |
Default severity |
warning |
Message format string |
In the IS-IS instance of network-instance network_instance, the level database has exited from the overload state. |
Cause |
Overload bit configuration |
Effect |
Transit traffic can again be routed through the router. |
isisOwnLspPurge
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisOwnLspPurge |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level LSP PDU was received with the system ID of this IS router and age equal to zero. The purge originator was purge_originator. |
Cause |
LSP lifetime expired or other reason |
Effect |
The PDU is removed |
isisSystemIdLengthMismatch
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisSystemIdLengthMismatch |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level PDU was received on interface subinterface with an unexpected System ID length in the IS-IS PDU header. The PDU starts with: pdu_fragment |
Cause |
Misconfiguration of system ID length in the neighbor |
Effect |
The PDU is dropped |
isisVersionMismatch
Property name |
Value |
---|---|
Application name |
isis |
Event name |
isisVersionMismatch |
Default severity |
warning |
Message format string |
In network-instance network_instance, a level PDU was received on interface subinterface with an IS-IS protocol version not matching the expected value. The PDU starts with: pdu_fragment |
Cause |
Unsupported IS-IS version |
Effect |
PDUs cannot be exchanged |