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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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).
IS-IS

IS-IS

ISIS_1.3.6.1.3.37.2.0.1 isisDatabaseOverload

Description

The overload state of IS-IS LSDB changed. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisSysLevelOverloadState=[isisSysLevelOverloadState])

The database entered or exited the Overload state.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.1

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisSysLevelOverloadState

Indicates the LSDB Overload state:

  • 1: off
  • 2: on
  • 3: waiting
  • 4: overloaded
Impact on the System

1. If the trap is generated because the IS-IS LSDB entered or exited the overload state, route selection on the IS-IS neighbor will be affected.

2. If the trap is generated because the memory usage exceeds the upper threshold, the IS-IS LSDB is unreliable.

Possible Causes

Cause 1: The set-overload or undo set-overload command was run in the IS-IS view.

Cause 2: After the set-overload on-startup command was run in the IS-IS view, the restarted.

Cause 3: The IS-IS process entered and then exited the Overload state.

Cause 4: Applying for memory resources failed due to memory shortage, causing a system crash.

Procedure
  1. Run the display this command in the IS-IS view to check whether the set-overload or undo set-overload command has been run in the process.
  • If set-overload or undo set-overload command has been run in the process, go to Step 5.
  • If set-overload or undo set-overload command has not been run in the process, go to Step 2.
  1. Run the display memory command to check whether the memory usage of the has reached the upper threshold.

    • If the memory usage has reached the upper threshold, go to Step 3.
    • If the memory usage has not reached the upper threshold, go to Step 4.

  2. Obtain user logs and diagnosis logs.
  3. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  4. End.

ISIS_1.3.6.1.3.37.2.0.2 isisManualAddressDrops

Description

Some area addresses were discarded because the number of area addresses exceeded three. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisManAreaAddrExistState=[isisManAreaAddrExistState])

Some area addresses of a device were discarded because the device had more than three area addresses.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.2

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisManAreaAddrExistState

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

The Level-1-2 leaked the LSP with the area ID of Level-1 to Level-2. When the number of Level-2 area ID exceeded 3, IS-IS selected top three smallest area IDs. 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.
  1. Run the undo network-entity command (this command needs to be run with caution) in the IS-IS view to delete the IS-IS area address, and then run the network-entity command in the IS-IS view to configure a new IS-IS area address to ensure that there are not more than three different IS-IS area addresses in the Level-1 area that is connected to the Level-1-2 router. Run the display isis lsdb 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 .

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

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

ISIS_1.3.6.1.3.37.2.0.3 isisCorruptedLSPDetected

Description

The checksum of LSP is wrong. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisPduLspId=[isisPduLspId])

The checksum of an LSP was incorrect.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.3

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisPduLspId

LSP ID.

Impact on the System

The LSP checksum failure will lead to the reset of the IS-IS process and relevant IS-IS services will be interrupted.

Possible Causes

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

Procedure
  1. Run the display memory command to check whether the memory usage exceeds the threshold (approximately 80%).
  • If so, go to Step 3.
  • If not, go to Step 2.
  1. 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.

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

ISIS_1.3.6.1.3.37.2.0.4 isisAttemptToExceedMaxSequence

Description

The LSP sequence number almost reaches the maximum value. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisPduLspId=[isisPduLspId])

The sequence number of an LSP approached the maximum value.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.4

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisPduLspId

LSP ID.

Impact on the System

After the sequence number reaches the maximum value 0xFFFFFFFF, the IS-IS process will be suspended for 20 minutes, 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. 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 .
  • 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 rapidly, go to Step 2.
  1. Check whether there is another whose system ID is the same as the system ID or the virtual system ID of the local . 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.

  2. (Use the undo network-entity command or the undo virtual-system command with caution.) Enter the IS-IS view of the local or another whose system ID is the same as the system ID or the virtual system ID of the local . 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 . Check whether the trap is cleared.

    • If so, go to Step 5.
    • If not, go to Step 4.

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

ISIS_1.3.6.1.3.37.2.0.5 isisIDLenMismatch

Description

The ID length of received PDU is different from local configuration. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisPduFieldLen=[isisPduFieldLen], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The ID length in the header of a received PDU was different from the locally supported one.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.5

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisPduFieldLen

Indicates the length of the received PDU.

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduFragment

Indicates the fragment of 64-byte PDU header.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

Impact on the System

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

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

Possible Causes

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

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 . 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 4-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

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

    • If so, go to Step 6.
    • If not, go to Step 3.

  2. View the logs or ping the device to check whether the device has a fault and hence the packet is tampered.

    • If so, go to Step 4.
    • If not, go to Step 5.

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

ISIS_1.3.6.1.3.37.2.0.6 isisMaxAreaAddressesMismatch

Description

The MaxAreaAddress field of received PDU is different from local configuration. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisPduMaxAreaAddress=[isisPduMaxAreaAddress], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The maximum number of area addresses in a received PDU was different from the locally supported one.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.6

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisPduMaxAreaAddress

Indicates the maximum number of area addresses.

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduFragment

Indicates the fragment of 64-byte PDU header.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

Impact on the System

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

2. If the trap is triggered because of the intercommunication failure between s, 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 mismatch the number of area addresses supported by other s.

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 . 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 4-7 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

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

    • If so, go to Step 6.
    • If not, go to Step 3.

  2. View the logs or ping the device to check whether the device has a fault and hence the packet is tampered.

    • If so, go to Step 4.
    • If not, go to Step 5.

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

ISIS_1.3.6.1.3.37.2.0.7 isisOwnLSPPurge

Description

ISIS received a self-originated LSP with the age being 0. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduLspId=[isisPduLspId], isisPduRemoteRouterID=[isisPduRemoteRouterID], ifIndex=[ifIndex], IfName=[IfName])

IS-IS received a self-originated LSP with the age field value of 0.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.7

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduLspId

LSP ID.

isisPduRemoteRouterID

Indicates the router ID of the remote system.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

Impact on the System

1. If the trap is triggered by the restart of the local , 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 did not refresh its LSPs in time. As a result, Purge packets were generated after LSPs were aged and flooded to the local .

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

3. The local 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 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.
  1. Check the system ID of the source device that sends the LSP.
  2. Download the user log on the source device and check whether the LSP is sent by the device.

    • If the LSP is sent by the device, go to Step 4.
    • If the LSP is not sent by the device, go to Step 5.

  3. Check whether the age field value of the LSP is 0 on the source device.

    • If the age field value of the LSP is 0, this trap is informational only, and no action is required.
    • If the age field value of the LSP is not 0, go to Step 7.

  4. If this trap is also generated on the source device, perform Step 2 to locate the source device that sends the LSP with the age field value of 0.
  5. Collect trap, log, and configuration information, and contact Huawei technical support personnel.
  6. End.

ISIS_1.3.6.1.3.37.2.0.8 isisSequenceNumberSkip

Description

ISIS received a self-originated LSP with a greater sequence number. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduLspId=[isisPduLspId], ifIndex=[ifIndex], IfName=[IfName])

IS-IS received a self-originated LSP of which the sequence number is greater than the local one.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.8

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduLspId

LSP ID.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

Impact on the System

1. You can ignore the trap caused by the restart of the local , 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 was the same as that of another . 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 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 5.
  • If not, go to Step 2.
  1. Run the display isis lsdb command to continuously check whether the LSP sequence number of the local 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 4.

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

    • If so, go to Step 4.
    • If not, go to Step 5.

  3. (Use the undo network-entity command or the undo virtual-system command with caution.) Enter the IS-IS view of the local or another whose system ID is the same as the system ID or the virtual system ID of the local . 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 undo virtual-system command to configure a different system ID or virtual system ID for the . Check whether the trap is cleared.

    • If so, go to Step 6.
    • If not, go to Step 5.

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

ISIS_1.3.6.1.3.37.2.0.9 isisAuthenticationTypeFailure

Description

The authentication type of received PDU is different from local configuration. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The authentication type of a received PDU was different from the local one.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.9

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduFragment

Indicates the fragment of 64-byte PDU header.

ifIndex

Indicates the IF index of the interface.

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 relationship 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.
  2. Check the second byte of the isisPduFragment field and confirm the packet type.

    • If the second byte is 14, Hello packets are received. Go to Step 3.
    • If the second byte is 1b, LSPs are received. Go to Step 5.
    • If the second byte is 11, SNPs are received. Go to Step 6.

  3. In a Hello packet, the 10th to 15th bytes of the isisPduFragment field form the system ID of the source device that sends the packet. Run the display isis peer command on the source 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 .

    • If so, go to Step 8.
    • If not, go to Step 4.

  4. Run the isis authentication-mode command in the interface view of the source to configure the same authentication mode as the local . The authentication mode can be simple mode, MD5, or keychain mode. 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 8.
    • If not, go to Step 7.

  5. Run the display current-configuration configuration isis command on the source 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 , and ensure that the authentication passwords configured on the two ends are the same.

    • If so, go to Step 8.
    • If not, go to Step 7.

  6. 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 to configure the same authentication mode as the local , which can be the simple mode, MD5 or keychain mode. Then, check whether the trap is cleared.

    • If so, go to Step 8.
    • If not, go to Step 7.

  7. Collect trap, log, and configuration information, and contact Huawei technical support personnel.
  8. End.

ISIS_1.3.6.1.3.37.2.0.10 isisAuthenticationFailure

Description

The authentication password of received PDU is different from local configuration. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The authentication password of a received PDU was different from the local one.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.10

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduFragment

Indicates the fragment of 64-byte PDU header.

ifIndex

Indicates the IF index of the interface.

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 on the interface or process of 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. Then, find the pdu-fragment field in the trap and fetch the system ID of the source 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 4-8 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

  1. Run the display isis peer command on the source 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 .

    • If so, go to Step 6.
    • If not, go to Step 3.

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

    • If so, go to Step 7.
    • If not, go to Step 6.

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

    • If so, go to Step 6.
    • If not, go to Step 5.

  4. 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 to configure the same authentication password as the local . Then, check whether the trap is cleared.

    • If so, go to Step 7.
    • If not, go to Step 6.

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

ISIS_1.3.6.1.3.37.2.0.11 isisVersionSkew

Description

IS-IS received a PDU with incorrect ProtocolVersion. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduProtocolVersion=[isisPduProtocolVersion], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

IS-IS received a PDU with an incorrect protocol version number.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.11

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduProtocolVersion

Indicates a version number.

isisPduFragment

Indicates the fragment of 64-byte PDU header.

ifIndex

Indicates the IF index of the interface.

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 s, neighbors cannot be established, and routes cannot be learnt from each other.

Possible Causes

1. The IS-IS version numbers supported by the local and other s 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 . Check whether the value of version field on the source is as 1.
  • If so, go to Step 2.
  • If not, go to Step 4.
Table 4-9 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

  1. View the logs or ping the board to check whether the board has a fault.

    • If so, go to Step 3.
    • If not, go to Step 6.

  2. Change the board. Then, check whether the trap is cleared.

    • If so, go to Step 7.
    • If not, go to Step 6.

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

    • If so, go to Step 5.
    • If not, go to Step 6.

  4. Modify the IS-IS version number of the source . The Huawei 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 7.
    • If not, go to Step 6.

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

ISIS_1.3.6.1.3.37.2.0.12 isisAreaMismatch

Description

IS-IS received a level-1 Hello PDU whose area address is different from the local area address. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

IS-IS received a Level-1 Hello PDU that carried an area address different from the local one.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.12

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduFragment

Indicates the fragment of 64-byte PDU header.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

Impact on the System

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

2. If the trap is triggered by an 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 . Then, run the display this command in the IS-IS view to check whether the area address configured on the source is the same as that of the local .
  • If so, go to Step 3.
  • If not, go to Step 2.
Table 4-10 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

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

    • If so, go to Step 4.
    • If not, go to Step 3.

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

ISIS_1.3.6.1.3.37.2.0.13 isisRejectedAdjacency

Description

IS-IS failed to establish the adjacency with its peer. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

IS-IS failed to establish a neighbor relationship.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.13

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduFragment

Indicates a 64-byte PDU fragment.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

Impact on the System

The neighbor relationship cannot be established.

Possible Causes

1. The system ID or virtual system ID of the local 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 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 .

4. The local interface received a Hello packet whose level is inconsistent with the local 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.
  1. Check the PduFragment field in the trap, and then identify the source according to the consecutive six bytes beginning with the tenth byte, which indicates the system ID of the source . 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.

  2. 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.

  3. Run the display ip interface command to check whether the IP address of the interface on the source 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.

  4. Run the ip address command in the interface views of the source and local 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.

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

    • If so, go to Step 10.
    • If not, go to Step 7.

  6. Run the isis peer-ip-ignore or ip address command in the interface views of the source and local 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.

  7. 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.

  8. 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.

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

    • If so, go to Step 11.
    • If not, go to Step 12.

  10. (Run the undo network-entity command with caution.) Change the system ID or virtual system ID on one 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.

  11. 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.

  12. 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.

  13. Collect the trap information, log information, and configuration, and then contact Huawei technical personnel.
  14. End.

ISIS_1.3.6.1.3.37.2.0.14 isisLSPTooLargeToPropagate

Description

ISIS attempt to propagate an LSP which is larger than the dataLinkBlockSize for the circuit. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduLspSize=[isisPduLspSize], isisPduLspId=[isisPduLspId], ifIndex=[ifIndex], IfName=[IfName])

IS-IS attempted to send an LSP of which the size is larger than the maximum transmission unit of an interface.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.14

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduLspSize

Indicates the length of an LSP.

isisPduLspId

LSP ID.

ifIndex

Indicates the IF index of the interface.

IfName

Indicates the name of the interface.

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 the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  6. End.

ISIS_1.3.6.1.3.37.2.0.15 isisOrigLSPBuffSizeMismatch

Description

The size of the local buffer for originating IS-IS LSPs is smaller than the size of the received LSP. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduLspId=[isisPduLspId], isisPduOriginatingBufferSize=[isisPduOriginatingBufferSize], ifIndex=[ifIndex], IfName=[IfName])

The size of a received LSP is larger than that of the local buffer.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.15

Trap severity

Minor

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of the IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduLspId

LSP ID.

isisPduOriginatingBufferSize

Indicates the size of a buffer.

ifIndex

Indicates the IF index of the interface.

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 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 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 . 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 is a default value, go to Step 6.

  5. Run the lsp-length orignate command in the IS-IS process of the source 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 recieve command in the IS-IS process to modify the size of the LSPs that can be received by the local , and ensure that the size is greater than or equal to the size of LSPs sent from the source . 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 , and contact Huawei technical support personnel.
  8. End.

ISIS_1.3.6.1.3.37.2.0.16 isisProtocolsSupportedMismatch

Description

The protocol of received Protocol TLV is mismatched with local configuration. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduProtocolsSupported=[isisPduProtocolsSupported], isisPduLspId=[isisPduLspId], isisPduFragment=[isisPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The protocol-supported TLV of a received PDU is different from the local TLV.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.16

Trap severity

Major

Parameters

Parameter

Description

isisSysInstance

Indicates the ID of an IS-IS process.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisCircIndex

Indicates the index of the interface.

isisCircIfIndex

Indicates the index of the interface.

isisPduProtocolsSupported

Indicates supported protocols.

isisPduLspId

LSP ID.

isisPduFragment

Indicates the fragment of 64-byte PDU header.

ifIndex

Indicates the IF index of the interface.

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 that generated the LSP was different from that supported by the local .

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 . Check whether the trap is cleared in 10 minutes.
  • If so, go to Step 3.
  • If not, go to Step 2.
  1. Collect the trap information, log information, and configuration of the , and contact Huawei technical personnel.
  2. End.

ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange

Description

ISIS adjacency state change. (IfName=[IfName], AdjLevel=[AdjLevel], NbrSysId=[NbrSysId], AdjState=[AdjState], AddressFamily=[AddressFamily], Reason=[Reason])

The IS-IS adjacency state changed.

Attributes

Attribute

Description

Trap OID

1.3.6.1.3.37.2.0.10

Trap severity

Minor

Match trap

Generate-alarm trap and clear-alarm trap use the same trap name, which is ISIS_1.3.6.1.3.37.2.0.17 isisAdjacencyChange. The two traps are distinguished by the Reason parameter. When the Reason parameter is The alarm was cleared, the trap indicates that an alarm has been cleared. The other values of the Reason parameter indicate that an alarm has been generated.

Parameters

Parameter

Description

IfName

Name of a neighbor interface

AdjLevel

Level of the adjacency of which the status changes

  • 1: Level-1
  • 2: Level-2

NbrSysId

System ID of a neighbor

AdjState

Previous status of the IS-IS adjacency

AddressFamily

Address family of an IS-IS neighbor

Reason

Reason for the status change of the IS-IS adjacency

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 . Then, check whether the neighbor status on both ends is the same.
  • If so, go to Step 12.
  • If not, go to Step 2.
  1. Download the user logs from the source , 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.

  2. 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.

  3. 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.

  4. 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.

  5. Check the area ID of the 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.

  6. 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.

  7. 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.

  8. 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.

  9. Run the display cpu 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.

  10. 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 status on both ends is the same.

    • If so, go to Step 13.
    • If not, go to Step 12.

  11. Collect the trap information, log information, and configuration, and then contact Huawei technical personnel.
  12. End.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 196203

Downloads: 1571

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