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

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

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).
STACKMNG_1.3.6.1.4.1.2011.5.25.183.1.22.9 hwStackLogicStackPortLinkErr

STACKMNG_1.3.6.1.4.1.2011.5.25.183.1.22.9 hwStackLogicStackPortLinkErr

Description

The interface Stack-Port was linked invalidly. (hwStackLocalIfName=[hwStackLocalIfName], hwStackPeerIfName=[hwStackPeerIfName], Reason=[Reason])

Physical member ports of the stack port were connected incorrectly.

Attribute

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Alert

Mnemonic Code

hwStackLogicStackPortLinkErr

Trap OID

1.3.6.1.4.1.2011.5.25.183.1.22.9

Alarm ID

0x09a20010

Alarm Type

environmentalAlarm

Raise or Clear

Raise

Match trap

STACKMNG_1.3.6.1.4.1.2011.5.25.183.1.22.13 hwStackLogicStackPortLinkErrResume

Parameters

Name Meaning

hwStackLocalIfName

Indicates the name of the local stack port.

hwStackPeerIfName

Indicates the name of the peer stack port.

Reason

Indicates a possible cause.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.183.1.32.1

hwStackLocalIfName

N/A

1.3.6.1.4.1.2011.5.25.183.1.32.2

hwStackPeerIfName

N/A

Impact on the System

The stack cannot be created. Stack members were removed, and the stack split.

Possible Causes

  • Cable connection of physical member ports caused a loop.
  • Physical member ports of a local stack port connected to those of two stack ports on the remote device.
  • Physical member ports of a local stack port connected to those of stack ports on different remote devices.
  • The member port of Stack-Port is connected to a common service port.

Procedure

  1. Run the display interface brief command to enter the stack port view, and check whether physical ports of the same stack port are connected.

    • If so, disconnect the ports.
    • If not, go to step 2.

  2. Check whether physical ports of the stack port are connected to a different device.

    • If so, check the protocol status of these ports. Remove the cables that connect the ports whose physical status is Up but protocol status is Down.
    • If not, go to step 3.

  3. Check whether any physical port of the same stack port is connected to another stack port on the same device.

    • If so, run the display stack topology command to check the stack ID of the device that the stack port is connected to. Remove the cables that connect the ports to another device.
    • If not, go to step 4.

  4. Check whether the physical member ports are connected to common service ports.

    • If so, remove the incorrectly connected links or change the ports on both ends of the links to the same mode (stack or common service port mode).
    • If not, go to step 5.

  5. Collect traps, logs, and configurations, and contact technical support personnel.
Translation
Download
Updated: 2019-03-20

Document ID: EDOC1000166558

Views: 194247

Downloads: 113

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