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

TRILL

TRILL_1.3.6.1.4.1.2011.5.25.331.1.3.1 trillNicknameConflict

Description

TRILL local nickname is conflicted and inhibited. (LocalSysId=[hwTrillLocalSysId], ConflictNickname=[hwTrillConflictNickname], LocalPriority=[hwTrillLocalPriority])

The local nickname conflicted with another nickname.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

trillNicknameConflict

Trap OID

1.3.6.1.4.1.2011.5.25.331.1.3.1

Alarm ID

0x00F10042

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

TRILL_1.3.6.1.4.1.2011.5.25.331.1.3.2 trillNicknameConflictClear

Parameters

Parameter

Description

LocalSysId

Local system ID

ConflictNickname

Conflicted nickname

LocalPriority

Priority of the nickname

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.331.1.1.1.1.2

hwTrillSysID

hwTrillInstanceID

1.3.6.1.4.1.2011.5.25.331.1.1.2.1.3

hwTrillPriority

hwTrillInstanceID;

hwTrillNickname;

Impact on the System

None

Possible Causes

The nickname that the user configured for the local device was the same as the nickname of anther device.

Procedure
  • Run the nickname nicknamevalue command in the TRILL view to change the nickname to a unique one.

TRILL_1.3.6.1.4.1.2011.5.25.331.1.3.2 trillNicknameConflictClear

Description

TRILL local nickname is released. (LocalSysId=[hwTrillLocalSysId], ConflictNickname=[hwTrillConflictNickname], LocalPriority=[hwTrillLocalPriority])

The local nickname conflict was cleared.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

trillNicknameConflictClear

Trap OID

1.3.6.1.4.1.2011.5.25.331.1.3.2

Alarm ID

0x00F10042

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

TRILL_1.3.6.1.4.1.2011.5.25.331.1.3.1 trillNicknameConflict

Parameters

Parameter

Description

LocalSysId

Local system ID

ConflictNickname

Conflicted nickname

LocalPriority

Priority of the nickname

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.331.1.1.1.1.2

hwTrillSysID

hwTrillInstanceID

1.3.6.1.4.1.2011.5.25.331.1.1.2.1.3

hwTrillPriority

hwTrillInstanceID;

hwTrillNickname;

Impact on the System

None

Possible Causes

The conflict between the nickname that the user configured for the local device and the nickname of anther device was cleared.

Procedure
  • This trap message is informational only, and no action is required.

TRILL_1.3.6.1.4.1.2011.5.25.331.1.3.3 trillAuthenticationFailure

Description

The authentication password of received PDU is different from local configuration. (trillSysInstance=[trillSysInstance], trillCircIndex=[trillCircIndex], trillCircIfIndex=[trillCircIfIndex], trillPduFragment=[trillPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The device received a PDU carrying an authentication password that was different from the local one.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Error

Mnemonic Code

TRILL_AUTHENTICATION_FAILURE

Trap OID

1.3.6.1.4.1.2011.5.25.331.1.3.3

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

trillSysInstance

TRILL process ID

trillCircIndex

TRILL interface index

trillCircIfIndex

Interface index obtained from the interface management module

trillPduFragment

64-byte PDU fragment

ifIndex

Interface index defined by the interface management module

IfName

Interface name

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.331.1.1.3.1.1

hwTrillSysInstance

ifIndex

1.3.6.1.4.1.2011.5.25.331.1.1.3.1.2

hwTrillCircIfIndex

ifIndex

1.3.6.1.4.1.2011.5.25.331.1.1.3.1.3

hwTrillPduFragment

ifIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

1. If a Hello packet fails to be authenticated, no TRILL neighbor relationship can be established.

2. If an LSP or SNP fails to be authenticated, LSDBs cannot be synchronized, but a TRILL neighbor relationship can still be established.

Possible Causes

TRILL authentication was configured for the local interface or process. The authentication mode configured on the remote device was the same as that configured on the local device, but the authentication password configured on the remote device was different from that configured on the local device.

Procedure
  1. Search the trap for the TRILL process ID, convert the decimal value of the if-index field into a hexadecimal value based on the TRILL packet format, and identify the PDU type and the system ID of the source switch (device that sent the PDU) in the pdu-fragment field.
  • If the PDU is a Hello packet, go to Step 2.
  • If the PDU is an LSP or SNP, go to Step 4.
Table 4-24 Methods of identifying system IDs and TRILL PDU types

Identifying the PDU Type

Identifying the System ID

Hello: The fifth byte in the pdu-fragment field is 0f, 10, or 11.

The six consecutive bytes from the tenth byte of the pdu-fragment field is the system ID.

LSP: The fifth byte in the pdu-fragment field is 12 or 14.

The six consecutive bytes from the thirteenth byte of the pdu-fragment field is the system ID.

SNP: The fifth byte in the pdu-fragment field is 18, 19, 1A, or 1B.

The six consecutive bytes from the eleventh byte of the pdu-fragment field is the system ID.

  1. Run the display trill peer command on the source switch to check the interface that sent the PDU and run the display this command in the interface view to check whether the configured authentication password is the same as that configured on the destination switch.

    • If the two passwords are the same, go to Step 6.
    • If the two passwords are different, go to Step 3.

  2. Run the trill authentication-mode command in the interface view of the source switch to change the authentication password to the one configured on the destination switch and then check whether the trap is cleared.

    • If the trap is cleared, go to Step 7.
    • If the trap persists, go to Step 6.

  3. Run the display current-configuration configuration trill command on the source switch to check whether the configured authentication password is the same as that configured on the destination switch.

    • If the two passwords are the same, go to Step 6.
    • If the two authentication passwords are different, go to Step 5.

  4. Run the area-authentication-mode command in the TRILL view of the source switch to change the authentication password to the one configured on the destination switch and then check whether the trap is cleared.

    • If the trap is cleared, go to Step 7.
    • If the trap persists, go to Step 6.

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

TRILL_1.3.6.1.4.1.2011.5.25.331.1.3.4 trillAuthenticationTypeFailure

Description

The authentication type of received PDU is different from local configuration. (trillSysInstance=[trillSysInstance], trillCircIndex=[trillCircIndex], trillCircIfIndex=[trillCircIfIndex], trillPduFragment=[trillPduFragment], ifIndex=[ifIndex], IfName=[IfName])

The device received a PDU carrying an authentication mode that was different from the local one.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Error

Mnemonic Code

TRILL_AUTHENTICATION_TYPE_FAILURE

Trap OID

1.3.6.1.4.1.2011.5.25.331.1.3.4

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the match trap.

Parameters

Parameter

Description

trillSysInstance

TRILL process ID

trillCircIndex

TRILL interface index

trillCircIfIndex

Interface index obtained from the interface management module

trillPduFragment

64-byte PDU fragment

ifIndex

Interface index defined by the interface management module

IfName

Interface name

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.331.1.1.3.1.1

hwTrillSysInstance

ifIndex

1.3.6.1.4.1.2011.5.25.331.1.1.3.1.2

hwTrillCircIfIndex

ifIndex

1.3.6.1.4.1.2011.5.25.331.1.1.3.1.3

hwTrillPduFragment

ifIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

1. If a Hello packet fails to be authenticated, no TRILL neighbor relationship can be established.

2. If an LSP or SNP fails to be authenticated, LSDBs cannot be synchronized, but a TRILL neighbor relationship can still be established.

Possible Causes

Cause 1: TRILL authentication was configured for the local interface or process. The authentication mode configured on the remote device was different from that configured on the local device.

Cause 2: TRILL authentication was configured for the local interface or process, but not for the remote interface or process.

Procedure
  1. Check the TRILL process ID from the trillSysInstance field in the trap information.
  2. Identify the PDU type based on the second byte of the trillPduFragment field.

    • 14: Hello packet. Go to Step 3.
    • 1B: LSP. Go to Step 5.
    • 11: SNP. Go to Step 6.

  3. Run the display trill peer command on the source switch to check the interface that sent the PDU and run the display this command in the interface view to check whether the configured authentication mode is the same as that configured on the destination switch.

    • If the two authentication modes are the same, go to Step 8.
    • If the two authentication modes are different, go to Step 4.

  4. Run the trill authentication-mode command in the interface view of the source switch to change the authentication mode to the one configured on the destination switch, ensure that the passwords configured on both sides are the same, and then check whether the trap is cleared.

    • If the trap is cleared, go to Step 8.
    • If the trap persists, go to Step 7.

  5. Run the display current-configuration configuration trill command on the source switch to check whether an authentication mode is configured in the TRILL process and whether the authentication mode is the same as that configured on the destination switch. Ensure that the passwords configured on both sides are the same.

    • If an authentication mode is configured in the TRILL process and the two authentication modes are the same, go to Step 8.
    • If no authentication mode is configured in the TRILL process or the two authentication modes are different, go to Step 7.

  6. Run the area-authentication-mode command in the TRILL view of the source switch to change the authentication mode to the one configured on the destination switch and then check whether the trap is cleared.

    • If the trap is cleared, go to Step 8.
    • If the trap persists, go to Step 7.

  7. Collect alarm information and configuration information, and then contact technical support personnel.
  8. End.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 210884

Downloads: 1591

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