No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ISIS

ISIS

ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload

Description

ISIS/3/OLOAD:OID [oid] The overload state of IS-IS LSDB changed. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], overLoadState=[integer])

The database entered or exited from the Overload state.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.1

Minor

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

overLoadState

Indicates the LSDB Overload state:
  • 1: off

  • 2: on

  • 3: waiting

  • 4: overloaded

Impact on the System

1. If the trap is triggered by the change of the LSDB Overload state, route selection of the neighbor will be affected.

2. If the trap is triggered by memory failure, it indicates that the IS-IS database is unauthentic.

Possible Causes

1. The set-overload or undo set-overload command is run in the IS-IS view.

2. Memory application failed because memory was insufficient. As a result, the system of the switch may crash.

Procedure

  1. Run the display this command in the IS-IS view to check whether the set-overload command has been run in this process.

    • If so, this trap message is informational only, and no action is required. Go to Step 6.

    • If not, go to Step 2.

  2. Run the display history-command command in any view to check whether the undo set-overload command has been run in the process.

    • If the undo set-overload command has been run in the process, go to Step 6.

    • If the undo set-overload command has not been run in the process, go to Step 3.

  3. Run the display memory-usage command to check the memory usage of the switch. Check whether the memory usage reaches the threshold.

    • If so, go to Step 4.

    • If not, go to Step 5.

  4. Obtain the logs.
  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.2 isisManualAddressDrops

Description

ISIS/2/MANAREA_DROP:OID [oid] Some area addresses were discarded because the number of area addresses exceeded three. (sysInstance=[process-id], sysInstanceofLevel=[process-id], sysLevel=[level], sysInstanceofManAreaAddrExistState=[process-id], manAreaAddr=[area-address], manAreaAddrExistState=[area-address-state])

On the Level-1-2 switch, IS-IS leaked the Level-1 area addresses to the Level-2 area. As a result, the number of Level-2 area addresses was more than 3 and IS-IS selected the top three smallest area addresses as the Level-2 area addresses. This may lead to the loss of Level-2 area addresses of the local IS-IS system.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.2

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofManAreaAddrExistState

Indicates the ID of the IS-IS process.

manAreaAddr

Indicates the area address. If the value is 0, it indicates the parameter is not used.

manAreaAddrExistState

Indicates the area address state:
  • 1: active

  • 2: notInService

  • 3: notReady

  • 4: createAndGo

  • 5: createAndWait

  • 6: destroy

Impact on the System

The Level-2 area addresses of the local IS-IS system may be lost.

Possible Causes

On the Level-1-2 switch, IS-IS leaked the Level-1 area addresses to the Level-2 area. When the number of Level-2 area addresses exceeded 3, IS-IS selected top three smallest area addresses. Then, the local area addresses in the Level-2 area may be lost.

Procedure

  1. Run the display isis lsdb level-1 verbose command to check the detailed information about the Level-1 IS-IS LSDB, and the AREA ADDR field carried in the LSP with the LSP fragment ID being 0. Then, count the number of different Level-1 area addresses to check whether the number is larger than three.

    • If so, go to step 2.
    • If not, go to step 3.

  2. Run the display isis lsdb { level-1 | level-2 } verbose command to check whether the value of the Level-1 Area Address field is the same as the value of the Level-2 Area Address field in the LSP with the fragment number being 0 on the local switch.
  3. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  4. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.3 isisCorruptedLSPDetected

Description

ISIS/3/CORRUPT_LSP:OID [oid] The checksum of LSP is wrong. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], pduLspId=[opaque])

A trap was generated when the LSP checksum authentication of the local LSDB failed before the IS-IS switch sent LSPs.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.3

Minor

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

pduLspId

Indicates the LSP ID.

Impact on the System

Relevant IS-IS services may be interrupted.

Possible Causes

During the LSP refreshing period, a fault occurred in the memory, and consequently the LSP was modified.

Procedure

  1. Run the display memory-usage command to check whether the memory usage exceeds the threshold (approximately 80%).

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Run the reset isis all command to restart the IS-IS process. After the IS-IS process is restarted, check whether the trap is cleared.

    • If so, go to Step 4.

    • If not, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.4 isisAttemptToExceedMaxSequence

Description

ISIS/3/MAXSEQ_EXCEED:OID [oid] The LSP sequence number almost reaches the maximum value. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], pduLspId=[opaque])

The sequence number of the IS-IS LSP would reach the maximum value.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.4

Minor

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

pduLspId

Indicates the LSP ID.

Impact on the System

After the sequence number reaches the maximum value 0xFFFFFFFF, the IS-IS process will be suspended for a period of time, namely, the sum of the maximum lifetime and zero aging time of an LSP. As a result, IS-IS services will be interrupted.

Possible Causes

The sequence number of the LSP generated locally reached the maximum value 0xFFFFFFFF.

Procedure

  1. If the trap is automatically cleared, no action is required. If the trap persists, after the LSP whose sequence number is 0xFFFFFFFF (the maximum lifetime of an LSP + 60, of which, the default maximum lifetime of an LSP is 1200s) ages out, the sequence number of the LSP starts from 1 again. The display isis lsdb local command can be used to check the Seq Num field of an LSP generated by the local switch.

    • If the increasing speed of the LSP sequence number is matched with the configured refreshing period, it indicates that this trap message is informational only, and no action is required, go to Step 5.

    • If the sequence number increases quickly, go to Step 2.

  2. Check whether there is another switch whose system ID is the same as the system ID or the virtual system ID of the local switch. According to ISO10589, the system ID in an IS-IS domain must be unique.

    • If so, go to Step 3.

    • If not, go to Step 4.

  3. Enter the IS-IS view of the local switch or another switch whose system ID is the same as the system ID or the virtual System ID of the local switch. Then run the undo network-entity command or the undo virtual-system command to delete the repeated system ID or virtual system ID and the network-entity command or the virtual-system command to configure a different system ID or virtual system ID for the switch. Check whether the trap is cleared. If the undo network-entity or undo virtual-system command is run, the conflicting system ID or virtual system ID becomes unavailable. Therefore, make sure that the system ID or virtual system ID conflict exists before you run the undo network-entity or undo virtual-system command.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  5. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.5 isisIDLenMismatch

Description

ISIS/2/SYSID_MISMATCH:OID [oid] The ID length of received PDU is different from local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofPduFieldLen=[integer], circIndex=[integer], ifIndex=[integer], pduFieldLen=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])

The length of the system ID carried in the header of the received PDU, including all types of IS-IS packets, did not match the length of the system ID of the local switch.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.5

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofPduFieldLen

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

pduFieldLen

Indicates the length of the received PDU.

circIfIndex

Indicates the IF index of the interface.

pduFrag

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

Impact on the System

1. If the trap is triggered because of a hardware fault on the board, route flapping may occur.

2. If the trap is triggered because of intercommunication between switch devices, neighbors cannot be established, or routes cannot be learnt from each other.

Possible Causes

1. The length of the system ID supported by other switch devices mismatch with the length of the system ID supported by the local switch.

2. The system ID Length field was modified during packet transmission.

Procedure

  1. Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (in hexadecimal) in the trap and fetch the system ID of the source switch. Check whether the length of the system ID is neither 0 nor 6.

    • If so, go to Step 2.

    • If not, go to Step 3.

    Table 46-1  Methods of searching for system IDs and types of IS-IS packets

    Searching for the Packet Type

    Searching for the System ID

    Hello: the 5th byte in the pdu-fragment field being 0f, 10, or 11

    The system ID is continuous 6 bytes after the 10th byte in the pdu-fragment field

    LSP: the 5th byte in the pdu-fragment field being 12 or 14

    The system ID is continuous 6 bytes after the 13th byte in the pdu-fragment field

    SNP: the 5th byte in the pdu-fragment field being 18, 19, 1A, or 1B

    The system ID is continuous 6 bytes after the 11th byte in the pdu-fragment field

  2. Modify the system ID length configured on the source switch to 6. Then, check whether the trap is cleared.

    • If so, go to Step 4.

    • If not, go to Step 3.

  3. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  4. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.6 isisMaxAreaAddressesMismatch

Description

ISIS/2/MAXAREA_MISMATCH:OID [oid] The MaxAreaAddress field of received PDU is different from local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], pduMaxAreaAddress=[integer], sysInstanceofPduMaxAreaAddress=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])

The maximum number of area addresses supported in the header of the received Level-1 PDU mismatched with that supported by the local switch.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.6

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

pduMaxAreaAddress

Indicates the maximum number of area addresses.

sysInstanceofPduMaxAreaAddress

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduFrag

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

Impact on the System

1. If the trap is triggered by a hardware fault of the board, route flapping may occur and the CPU usage will increase.

2. If the trap is triggered because of the intercommunication failure between switch devices, neighbors cannot be established, and routes cannot be learnt from each other.

Possible Causes

1. The maximum number of area addresses supported by the local switch mismatch the number of area addresses supported by other switch devices.

2. The maximum area address field was modified.

Procedure

  1. Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (in hexadecimal) in the trap and fetch the system ID of the source switch. Then, find the value of the pdu-max-area field in the trap and check whether the number of maximum area addresses is neither 0 nor 3.

    • If so, go to Step 2.

    • If not, go to Step 3.

    Table 46-2  Methods of searching for system IDs and types of IS-IS packets

    Searching for the Packet Type

    Searching for the System ID

    Hello: the 5th byte in the pdu-fragment field being 0f, 10, or 11

    The system ID is continuous 6 bytes after the 10th byte in the pdu-fragment field

    LSP: the 5th byte in the pdu-fragment field being 12 or 14

    The system ID is continuous 6 bytes after the 13th byte in the pdu-fragment field

    SNP: the 5th byte in the pdu-fragment field being 18, 19, 1A, or 1B

    The system ID is continuous 6 bytes after the 11th byte in the pdu-fragment field

  2. Modify the maximum number of area addresses of the source switch to 3. Then, check whether the trap is cleared.

    • If so, go to Step 4.

    • If not, go to Step 3.

  3. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  4. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.7 isisOwnLSPPurge

Description

ISIS/2/OWNLSP_PURGE:OID [oid] ISIS received a self-originated LSP with the age being 0. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofInterface=[integer], circuit=[integer], ifIndex=[integer], circuitIfIndex=[integer], pduLspId=[opaque], pduRemoteRouterID=[integer], ifName=[string])

An LSP with the system ID as local IS-IS and the lifetime as 0 was received.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.7

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofInterface

Indicates the ID of the IS-IS process.

circuit

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circuitIfIndex

Indicates the IF index of the interface.

pduLspId

Indicates the ID of the LSP.

pduRemoteRouterID

Indicates the router ID of the remote system.

ifName

Indicates the name of the interface.

Impact on the System

1. If the trap triggered by the restart of the local switch, services will not be affected.

2. If the trap is generated frequently, IS-IS routes are affected and packets may not be forwarded.

Possible Causes

1. The local switch did not refresh its LSPs in time. As a result, Purge packets were generated after LSPs were aged and flooded to the local switch.

2. The packet was modified and Purge packets were generated because of transmission failure.

3. The local switch was restarted and then received the LSP with the system ID as local IS-IS and the lifetime as 0 from the neighbor.

Procedure

  1. Check whether the local switch is restarted.

    • If so, it indicates that this trap message is informational only, and no action is required. Go to Step 4.

    • If not, go to Step 2.

  2. Check whether the IS-IS authentication configuration is modified and hence the Purge packets are generated and the trap is triggered.

    • If so, it indicates that this trap message is informational only, and no action is required. Go to Step 4.

    • If not, go to Step 3.

  3. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  4. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.8 isisSequenceNumberSkip

Description

ISIS/2/SEQNUM_SKIP:OID [oid] ISIS received a self-originated LSP with a greater sequence number. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduLspId=[opaque], ifName=[string])

The sequence number of the local IS-IS LSP irregularly increases.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.8

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduLspId

Indicates the ID of the LSP.

ifName

Indicates the name of the interface.

Impact on the System

1. You can ignore the trap caused by the restart of the local switch, and services will not be affected.

2. If the trap is triggered by the incorrect configuration, routes will flap frequently.

Possible Causes

1. After the IS-IS process was restarted, IS-IS received the LSP with the greater sequence number and the same LSP ID from the neighbor.

2. The system ID of the local switch was the same as that of another switch. This caused the LSP to be updated continuously.

Procedure

  1. Run the display history-command command to check whether the reset isis all command is run on the local switch to restart the IS-IS process.

    • If so, it indicates that this trap message is informational only, and no action is required, go to Step 6.

    • If not, go to Step 2.

  2. Run the display isis lsdb command to continuously check whether the LSP sequence number of the local switch increases rapidly, that is, to check whether the actual LSP refresh period is shorter than the value configured through the timer lsp-refresh command.

    • If so, go to Step 3.

    • If not, go to Step 5.

  3. Run the display current-configuration command to check whether there is another switch whose system ID or virtual system ID is the same as that of the local switch on the network.

    • If so, go to Step 4.

    • If not, go to Step 5.

  4. Enter the IS-IS view of the local switch or another switch whose system ID is the same as the system ID or the virtual System ID of the local switch. Then run the undo network-entity command or the undo virtual-system command to delete the repeated system ID or virtual system ID and the network-entity command or the virtual-system command to configure a different system ID or virtual system ID for the switch. Check whether the trap is cleared. If the undo network-entity or undo virtual-system command is run, the conflicting system ID or virtual system ID becomes unavailable. Therefore, make sure that the system ID or virtual system ID conflict exists before you run the undo network-entity or undo virtual-system command.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  6. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.9 isisAuthenticationTypeFailure

Description

ISIS/3/AUTHTYPE_FAIL:OID [oid] The authentication type of received PDU is different from local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])

The received packet, including the LSP, CSNP, PSNP, and Hello packet, did not contain the authentication information, or the authentication type carried in the received packet was different from that of the local switch. For example, one end is configured with MD5 authentication, whereas the other end is configured with simple authentication.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.9

Minor

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduFrag

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

Impact on the System

1. If the authentication of the Hello packet fails, IS-IS neighbors cannot be established.

2. If the authentication of the LSP or SNP fails, LSDBs cannot be synchronized; however, IS-IS neighbors can be established.

Possible Causes

1. Authentication was configured on the interface or process of the local end. The authentication type configured on the peer end was different from that configured on the local end.

2. Authentication was configured on the interface or process of the local end. The peer end, however, was not configured with authentication.

Procedure

  1. Check the sysInstance field in the trap to identify the ID of the IS-IS process that receives the packet, and then check the sysLevel field to identify the level of the packet. The value 1 indicates Level-1 packets; the value 2 indicates Level-2 packets; the value 3 indicates P2P Hello packets. According to the IS-IS packet format defined in ISO 10589, check the IfName field in the trap to identify the interface that receives packets. Then, check the PduFrag field in the trap and obtain the system ID of the source router that sends the packet and packet type.

    • If the type of the packet is Hello, go to Step 2.
    • If the type of the packet is LSP or SNP, go to Step 4.
    Table 46-3  Methods of searching for system IDs and types of IS-IS packets

    Searching for the Packet Type

    Searching for the System ID

    Hello: the 5th byte in the pdu-fragment field being 0f, 10, or 11

    The system ID is continuous 6 bytes after the 10th byte in the pdu-fragment field

    LSP: the 5th byte in the pdu-fragment field being 12 or 14

    The system ID is continuous 6 bytes after the 13th byte in the pdu-fragment field

    SNP: the 5th byte in the pdu-fragment field being 18, 19, 1A, or 1B

    The system ID is continuous 6 bytes after the 11th byte in the pdu-fragment field

  2. Run the display isis peer command on the source switch to check the interface that sends the packet. Run the display this command in the interface view to check whether the interface authentication mode is configured. If the interface authentication mode is configured, check whether it is consistent with the interface authentication mode of the local switch.

    • If so, go to Step 6.

    • If not, go to Step 3.

  3. Run the isis authentication-mode command in the interface view of the source switch to configure the same authentication mode as the local switch. Ensure that the authentication passwords on the interfaces at both ends are the same. Then, check whether the trap is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  4. Run the display current-configuration configuration isis command on the source switch to check whether the area or domain authentication mode is configured in the IS-IS process. If the area or domain authentication mode is configured, check whether it is the same as the authentication mode of the local switch, and ensure that the authentication passwords configured on the two ends are the same.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Run the area-authentication-mode (for Level-1 packets) command or the domain-authentication-mode (for Level-2 packets) command in the IS-IS view of the source switch to configure the same authentication mode as the local switch. Then check whether the trap is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  7. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.10 isisAuthenticationFailure

Description

ISIS/3/AUTH_FAIL:OID [oid] The authentication password of received PDU is different from local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFrag=[opaque], ifName=[string])

The received packet, including the LSP, CSNP, PSNP, and Hello packet, contained the authentication information and the same authentication type carried in the packet was the same as that configured on the local switch, however, the authentication password in the packet was different from that configured on the local switch. For example, both ends were configured with either MD5 authentication or simple authentication, whereas the configured authentication passwords were different.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.10

Minor

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduFrag

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

Impact on the System

1. If Hello packet authentication fails, IS-IS neighbors cannot be established.

2. If LSP or SNP packet authentication fails, LSDBs cannot be synchronized; however, IS-IS neighbors can be established.

Possible Causes

Authentication was configured for the interface or process on the local end. The authentication types configured on both ends were the same, whereas the authentication passwords were different.

Procedure

  1. Through the parameter in the trap, check the ID of the IS-IS process that receives the packet and check the level that the packet belongs to. The value 1 indicates Level-1 packets; the value 2 indicates Level-2 packets; the value 3 indicates P2P Hello packets. Based on the IS-IS packet format defined in ISO10589, search for the if-index field (in decimal) in the trap and convert the decimal value into a hexadecimal value. Run the display rm interface command on the interface and search the command output for the information about the interface that receives the packet. The value of IfnetIndex in the interface information is the same as the hexadecimal if-index. Then, find the pdu-fragment field in the trap and fetch the system ID of the source switch that sends the packet and packet type.

    • If the type of the packet is Hello, go to Step 2.
    • If the type of the packet is LSP or SNP, go to Step 4.
    Table 46-4  Methods of searching for system IDs and types of IS-IS packets

    Searching for the Packet Type

    Searching for the System ID

    Hello: the 5th byte in the pdu-fragment field being 0f, 10, or 11

    The system ID is continuous 6 bytes after the 10th byte in the pdu-fragment field

    LSP: the 5th byte in the pdu-fragment field being 12 or 14

    The system ID is continuous 6 bytes after the 13th byte in the pdu-fragment field

    SNP: the 5th byte in the pdu-fragment field being 18, 19, 1A, or 1B

    The system ID is continuous 6 bytes after the 11th byte in the pdu-fragment field

  2. Run the display isis peer command in the source switch to check the interface that sends the packet. Enter the interface view and run the display this command to check the password used for authentication is the same as that configured on the local switch.

    • If so, go to Step 6.

    • If not, go to Step 3.

  3. Run the isis authentication-mode command in the interface view of the source switch to configure the same authentication password as the local switch. Then check whether the trap is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  4. Run the display current-configuration configuration isis command on the source switch to check whether the IS-IS process is configured with the same area authentication password or domain authentication password as the local switch.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Run the area-authentication-mode (for Level-1 packets) command or the domain-authentication-mode (for Level-2 packets) command in the IS-IS view of the source switch to configure the same authentication password as the local switch. Then check whether the trap is cleared.

    • If so, go to Step 7.

    • If not, go to Step 6.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew

Description

ISIS/2/VERSION_SKEW:OID [oid] IS-IS received a PDU with incorrect ProtocolVersion. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduProtocolVersion=[integer], pduFragment=[opaque], ifName=[string])

The IS-IS version number of the received Hello packet was inconsistent with that of the Hello packet supported by the local switch.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.11

Major

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduProtocolVersion

Indicates the protocol version contained in a PDU.

pduFragment

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

Impact on the System

1. If the board modifies the packet, route flapping may occur, and the CPU usage will increase.

2. If the trap is generated because of intercommunication between switch devices, neighbors cannot be established, and routes cannot be learnt from each other.

Possible Causes

1. The IS-IS version numbers supported by the local switch and other switch devices were inconsistent.

2. The version number field was modified during packet transmission.

Procedure

  1. Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (in hexadecimal) in the trap and fetch the system ID of the source switch. Check whether the value of version field on the source switch is as 1.

    • If so, go to Step 4.

    • If not, go to Step 2.

    Table 46-5  Methods of searching for system IDs and types of IS-IS packets

    Searching for the Packet Type

    Searching for the System ID

    Hello: the 5th byte in the pdu-fragment field being 0f, 10, or 11

    The system ID is continuous 6 bytes after the 10th byte in the pdu-fragment field

    LSP: the 5th byte in the pdu-fragment field being 12 or 14

    The system ID is continuous 6 bytes after the 13th byte in the pdu-fragment field

    SNP: the 5th byte in the pdu-fragment field being 18, 19, 1A, or 1B

    The system ID is continuous 6 bytes after the 11th byte in the pdu-fragment field

  2. Check whether the IS-IS version number of the source switch can be modified.

    • If so, go to Step 3.

    • If not, go to Step 4.

  3. Modify the IS-IS version number of the source switch. The Huawei switch does not support the modification of the IS-IS version number through a command. Then check whether the trap is cleared.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  5. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.12 isisAreaMismatch

Description

ISIS/3/AREA_MISMATCH:OID [oid] IS-IS received a level-1 Hello PDU whose area address is different from the local area address. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFragment=[opaque], ifName=[string])

The area address of the received Level-1 Hello packet was different from that of the local Level-1 IS-IS.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.12

Minor

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduFragment

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

Impact on the System

1. If the trap is triggered because of a hardware fault of the board, route flapping may occur and the CPU usage will increase.

2. If the trap is triggered because of incorrect configuration, neighbors cannot be established, and routes cannot be learnt from each other.

Possible Causes

1. The configuration was incorrect.

2. The area address field was modified.

Procedure

  1. Based on the IS-IS packet format defined in ISO10589, search for the pdu-fragment field (in hexadecimal) in the trap and fetch the system ID of the source switch. Then, run the display this command in the IS-IS view to check whether the area address configured on the source switch is the same as that of the local switch.

    • If so, go to Step 3.

    • If not, go to Step 2.

    Table 46-6  Methods of searching for system IDs and types of IS-IS packets

    Searching for the Packet Type

    Searching for the System ID

    Hello: the 5th byte in the pdu-fragment field being 0f, 10, or 11

    The system ID is continuous 6 bytes after the 10th byte in the pdu-fragment field

    LSP: the 5th byte in the pdu-fragment field being 12 or 14

    The system ID is continuous 6 bytes after the 13th byte in the pdu-fragment field

    SNP: the 5th byte in the pdu-fragment field being 18, 19, 1A, or 1B

    The system ID is continuous 6 bytes after the 11th byte in the pdu-fragment field

  2. Run the network-entity command in the IS-IS view of the source switch to configure a new IS-IS area address so that the area address of the switch is consistent with that of the local switch. Then, check whether the trap is cleared.

    • If so, go to Step 4.

    • If not, go to Step 3.

  3. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  4. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency

Description

ISIS/3/REJECT_ADJ:OID [oid] IS-IS failed to establish the adjacency with its peer. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduFragment=[opaque], ifName=[string], hwIsisAdjChangeReason=[integer], hwIsisAdjChangeSubReason=[integer])

The local switch received a Hello packet sent by the adjacent switch, but cannot establish the IS-IS neighbor relationship with the adjacent switch.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.13

Minor

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduFragment

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

hwIsisAdjChangeReason

Indicates the main cause of the change in the neighbor relationship:
  • 1: peer hold timer expiration

  • 2: physical interface change

  • 3: protocol reason

  • 4: BFD session getting down

  • 5: configuration change

  • 6: reason of peer router

  • 7: other reason

  • 8: alarm cleared

hwIsisAdjChangeSubReason

Indicates details about the cause of the change in the neighbor relationship:
  • 1: status of peer relation getting up

  • 2: peer deleted

  • 3: interface deleted

  • 4: interface silence

  • 5: invalid hello packets received

  • 6: authentication failed

  • 7: system ID conflict

  • 8: maximum area address number mismatch

  • 9: different L1 area addresses

  • 10: hello packet receiving failure

  • 11: interface going Down

  • 12: protocol mismatch

  • 13: adjacency deleted for space

  • 14: BFD session going down

  • 15: level change

  • 16: P2P negotiations change

  • 17: peer reset

  • 18: interface type change

  • 19: IS-IS reset

  • 20: undo network

  • 21: undo isis

  • 22: level mismatch

  • 23: no local MAC address in the received Hello packet

  • 24: three-way adjacency not up

  • 25: topology mismatch

  • 26: circuit ID mismatch

  • 27: Down three-way adjacency state

  • 28: other errors

  • 29: optional checksum TLV check failed

Impact on the System

The neighbor relationship cannot be established.

Possible Causes

1. The system ID or virtual system ID of the local switch is the same as the system ID of the neighbor.

2. The authentication mode or the authentication password configured for the interface on the local switch was inconsistent with that configured on the neighbor. As a result, the authentication of the Hello packet failed.

3. The Level-1 area address of the IS-IS neighbor was inconsistent with the Level-1 area address of the local switch.

4. The local interface received a Hello packet whose level is inconsistent with the local switch level.

5. In a broadcast network, the local interface received a Hello packet sent by the adjacent interface whose IP address is on a different network segment.

6. In a P2P network, because the isis peer-ip-ignore is not configured, the local interface received a Hello packet sent by the adjacent interface whose IP address is on a different network segment.

Procedure

  1. Check the IfName field in the trap to identify the interface that receives packets.

    • If the interface is a broadcast interface, go to Step 2.

    • If the interface is a P2P interface, go to Step 7.

  2. Check the PduFragment field in the trap, and then identify the source switch according to the consecutive six bytes beginning with the tenth byte, which indicates the system ID of the source switch. Run the display this command in the views of interfaces on the two ends of the link and in the IS-IS process view to check whether the IS-IS levels and interface levels on both ends of the link are consistent.

    • If so, go to Step 6.

    • If not, go to Step 3.

  3. Run the isis circuit-level command in the interface view to change the IS-IS levels and interface levels on both ends of the link to be consistent. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 4.

  4. Run the display ip interface command to check whether the IP address of the interface on the source switch is on the same network segment as the IP address of the local interface.

    • If so, go to Step 8.

    • If not, go to Step 5.

  5. Run the ip address command in the interface views of the source switch and local switch to configure IP addresses of interfaces on both ends to belong to the same network segment. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 8.

  6. Run the display this command in the interface views of the source switch and local switch to check whether the isis peer-ip-ignore command is run.

    • If so, go to Step 10.

    • If not, go to Step 7.

  7. Run the isis peer-ip-ignore or ip address command in the interface views of the source switch and local switch to configure IP addresses of interfaces on both ends to belong to the same network segment. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 10.

  8. Check whether the Level-1 area addresses on both ends of the link are the same.

    • If so, go to Step 10.

    • If not, go to Step 9.

  9. Run the network-entity command in the IS-IS view to configure a new area address to ensure that the Level-1 area addresses on both ends are the same. Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 10.

  10. Run the display current-configuration command to check whether the system ID of the source switch is the same as the system ID or virtual system ID of the local switch.

    • If so, go to Step 11.

    • If not, go to Step 12.

  11. Run the network-entity command to change the system ID or virtual system ID on one switch to ensure that the system IDs or virtual system IDs on both ends are different. Then, check whether the trap is cleared.

    • If so, go to Step 14.

    • If not, go to Step 12.

  12. Check IS-IS authentication modes and authentication passwords of interfaces on both ends are the same.

    • If so, go to Step 14.

    • If not, go to Step 13.

  13. Run the isis authentication-mode command in the views of interface on both ends to change the authentication mode and authentication password to ensure that IS-IS authentication modes and authentication passwords of interfaces on both ends are consistent. Alternatively, run the undo isis authentication-mode command in the views of interface on both ends to disable IS-IS authentication (disabling IS-IS authentication degrades the system security). Then, check whether the trap is cleared.

    • If so, go to Step 15.

    • If not, go to Step 14.

  14. Collect the trap information, log information, and configuration, and then contact technical support personnel.
  15. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.14 isisLSPTooLargeToPropagate

Description

ISIS/4/LARGE_LSP:OID [oid] The length of the PDU to be sent is greater than the MTU. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], circIfIndex=[integer], lspSizeSupport=[integer], pduLspId=[opaque])

The length of the PDU to be sent is greater than the MTU of the interface.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.14

Warning

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

IS-IS process ID

sysInstanceofLevel

IS-IS process ID

sysLevel

IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

IS-IS process ID

circIndex

Interface index

circIfIndex

IS-IS interface index

lspSizeSupport

Maximum LSP length

pduLspId

LSP ID

Impact on the System

None.

Possible Causes

The LSP to be forwarded exceeds the interface MTU.

Procedure

  1. Run the display ip interface interface-type interface-number command to view the interface MTU. The Maximum Transmit Unit in the command output shows the MTU value.
  2. Run the display current-configuration configuration isis command to view the maximum LSP length. lsp-length originate in the command output shows the maximum LSP length. If the command output does not show a setting, the default value is used. The default maximum LSP is 1497 bytes.
  3. Run the lsp-length originate command in the IS-IS view to change the maximum LSP length to a value smaller than the interface MTU.
  4. Check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 6.

    • If the alarm persists, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None.

ISIS_1.3.6.1.3.37.2.0.15 isisOrigLSPBuffSizeMismatch

Description

ISIS/3/LSPMTU_MISMATCH: OID [oid] The size of the local buffer for originating IS-IS LSPs is smaller than the size of the received LSP. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduLspId=[opaque], pduOriginatingBufferSize=[integer], ifName=[string])

The size of the local buffer for originating LSPs is smaller than the size of the received LSP.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.15

Minor

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduLspId

Indicates the ID of the LSP.

pduOriginatingBufferSize

Indicates the buffer size for originating LSPs.

ifName

Indicates the name of the interface.

Impact on the System

Routes cannot be learnt, and traffic forwarding is affected.

Possible Causes

The size of the LSPs originated from IS-IS on the source switch is larger than the size of the local buffer for originating LSPs.

Procedure

  1. Run the display current-configuration configuration isis command on the local device to check the size of LSPs. If the command output does not contain the LSP size, the default LSP size is used. Run the display default-parameter isis command to check the LSP-Receive-Length field.
  2. Find the source switch from which the LSPs are originated based on the lsp-id field value in the trap output. Run the display current-configuration configuration isis command to check the size of the LSPs on the source switch. If the command output does not contain the LSP size, the default LSP size is used. Run the display default-parameter isis command to check the LSP-Originate-Length field.
  3. Check whether the value obtained in Step 1 is smaller than that obtained in Step 2.

    • If so, go to Step 4.

    • If not, go to Step 7.

  4. Perform the following steps as required:

    • If the size of the local receiving buffer for LSPs is a default value, go to Step 5.
    • If the size of LSPs originated from the source switch is a default value, go to Step 6.

  5. Run the lsp-length originate command in the IS-IS process of the source switch to modify the size of LSPs, and ensure that the size is smaller than or equal to the size of the local receiving buffer. Then, check whether the trap is cleared.

    • If so, go to Step 8.

    • If not, go to Step 7.

  6. Run the lsp-length receive command in the IS-IS process to modify the size of the LSPs that can be received by the local switch, and ensure that the size is greater than or equal to the size of LSPs sent from the source switch. Then, check whether the trap is cleared.

    • If so, go to Step 8.

    • If not, go to Step 7.

  7. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  8. End.

Related Information

None.

ISIS_1.3.6.1.3.37.2.0.16 isisProtocolsSupportedMismatch

Description

ISIS/2/PROTO_MISMATCH:OID [oid] The protocol of received Protocol TLV is mismatched with local configuration. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduProtocolsSupported=[opaque], pduLspId=[opaque], pduFragment=[opaque], ifName=[string])

The type of the protocol supported TLV (the type field being 0x81) carried in the received LSP mismatched with the type of the protocol supported by the local switch.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.16

Major

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduProtocolsSupported

Indicates the supported protocol.

pduLspId

Indicates the ID of the LSP.

pduFragment

Indicates the fragment of 64-byte PDU header.

ifName

Indicates the name of the interface.

Impact on the System

LSPs cannot be learnt, and routes cannot be generated.

Possible Causes

The protocol type supported by the source switch that generated the LSP was different from that supported by the local switch.

Procedure

  1. The type of the protocol supported TLV carried in the received LSP mismatched with the type of the protocol supported by the local switch. Check whether the trap is cleared in 10 minutes.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  3. End.

Related Information

None

ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange

Description

ISIS/2/ADJ_CHANGE:OID [oid] The state of IS-IS adjacency changed. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofInterface=[integer], circuit=[integer], ifIndex=[integer], circuitIfIndex=[integer], lspID=[opaque], adjState=[integer], ifName=[string], hwIsisAdjChangeReason=[integer], hwIsisAdjChangeSubReason=[integer])

The status of the neighbor changed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.17

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofInterface

Indicates the ID of the IS-IS process.

circuit

Indicates the ID of the circuit.

ifIndex

Indicates the index of the interface.

circuitIfIndex

Indicates the IF index of the interface.

lspID

Indicates the ID of the LSP.

adjState

Indicates the status of the neighbor.
  • 1: Down

  • 2: Initializing

  • 3: Up

  • 4: Failed

  • 5: Cleared

ifName

Indicates the name of the interface.

hwIsisAdjChangeReason

Indicates the main cause of the change in the neighbor relationship:
  • 1: The hold timer expired.

  • 2: The status of the physical interface changed.

  • 3: It is a protocol-related cause.

  • 4. The BFD session went Down.

  • 5: A configuration was changed.

  • 6. It is a neighbor-related cause.

  • 7. Other causes.

  • 8. The alarm was cleared.

  • 100: The neighbor was cleared.

hwIsisAdjChangeSubReason

Indicates details about the cause of the change in the neighbor relationship:
  • 1: status of peer relation getting up

  • 2: peer deleted

  • 3: interface deleted

  • 4: interface silence

  • 5: invalid hello packets received

  • 6: authentication failed

  • 7: system ID conflict

  • 8: maximum area address number mismatch

  • 9: different L1 area addresses

  • 10: hello packet receiving failure

  • 11: interface down

  • 12: protocol mismatch

  • 13: adjacency deleted for space

  • 14: BFD session getting down

  • 15: level change

  • 16: P2P negotiations change

  • 17: peer reset

  • 18: interface type change

  • 19: IS-IS reset

  • 20: undo network

  • 21: undo isis

  • 22: level mismatch

  • 23: no local MAC address in the received Hello packet

  • 24: three-way adjacency not up

  • 25: topology mismatch

  • 26: circuit ID mismatch

  • 27: Down three-way adjacency state

  • 28: other errors

  • 29: optional checksum TLV check failed

Impact on the System

IS-IS may re-calculate routes, which causes route flapping and interrupts the IS-IS service.

Possible Causes

1. The IS-IS neighbor relationship went Up or Down.

2. The IS-IS configuration was incorrect.

3. The system was busy, and consequently the IS-IS neighbor relationship was intermittently interrupted.

4. The link failed, and consequently the status of the IS-IS neighbor relationship was changed.

Procedure

  1. According to the IS-IS packet format defined in ISO 10589, find the LspID field (in hexadecimal format) in the trap to identify the system ID of the source switch. Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 12.

    • If not, go to Step 2.

  2. Download the user logs from the source switch, and then find out the cause for the neighbor status change according to the logs. Check whether the neighbor status is changed because the interface goes Down.

    • If so, go to Step 3.

    • If not, go to Step 10.

  3. Find information about the local interface from the logs, and then check the interface status and MTU status on the interface. Ensure that both the interface status and MTU status on two ends are Up. Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 13.

    • If not, go to Step 4.

  4. Check the system IDs and ensure that the system IDs on both ends are correct. Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 13.

    • If not, go to Step 5.

  5. Check the levels of the IS-IS process and ensure that levels on both ends match. Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 13.

    • If not, go to Step 6.

  6. Check the area ID of the switch and ensure that area IDs on both ends are the same. Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 13.

    • If not, go to Step 7.

  7. Check that IP addresses of interfaces on both ends belong to the same network segment. Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 13.

    • If not, go to Step 8.

  8. Check whether the authentication mode is configured on both ends and ensure that the encryption authentication modes on both ends are the same. If authentication is required, ensure that the authentication modes and passwords on both ends are the same. Otherwise, authentication is disabled on both ends (disabling authentication degrades the system security). Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 13.

    • If not, go to Step 9.

  9. Check whether interfaces on both ends can transmit Hello packets normally and ensure that they can transmit Hello packets normally. Then, check whether the neighbor status on both ends is the same.

    • If so, go to Step 13.

    • If not, go to Step 10.

  10. Run the display cpu-usage command to check whether the CPU usage remains 100% in a period of time.

    • If so, go to Step 11.

    • If not, go to Step 12.

  11. Run the isis timer hello command in the interface view to set the interval for sending Hello packets to a larger value, which increases by 10s each time. Prolonging the interval for sending Hello packets slows down the detection of network faults and thus slows down route convergence. Then, check whether the neighbor statuses on both ends are the same.

    • If so, go to Step 13.

    • If not, go to Step 12.

  12. Collect the trap information, log information, and configuration, and then contact technical support personnel.
  13. End.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 5097

Downloads: 6

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next