ALM-161611792 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

Parameters

Impact on the System

• The CSS or stack cannot be set up. CSS or stack members are removed, and the CSS or stack split.
• The Stack-Port on the local device receives packets from different Stack-Ports on the peer device.
• The Stack-Port on the local device receives packets from different devices.
• The Stack-Port on the local device receives packets from the Stack-Ports on different LPUs of the peer device.
• A CSS or stack cannot be set up.

Possible Causes

• Cause 1: The Stack-Ports have loop connections.
• Cause 2: A Stack-Portt on the local device is connected to two different Stack-Ports on the peer device.
• Cause 3: A Stack-Port on the local device is connected to Stack-Ports on different devices.
• Cause 4: A Stack-Port on an LPU of the local device is connected to the Stack-Ports on different LPUs of the peer device.
• Cause 5: The physical port is connected to the device with a conflicting ID.

Procedure

• Cause 1: The Stack-Ports have loop connections.
  1. Run the display interface brief command to check the member ports in a Stack-Port. Determine whether any two ports in the same Stack-Port are connected.
     • If so, disconnect the ports.
     • If not, go to step 2.
  2. Check whether the member ports in a Stack-Port are connected to different devices.
     • 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 the member ports in a Stack-Port are connected to another Stack-Port on the same device.
     • If so, run the display css topology or display stack topology command to check the CSS or 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. Collect traps, logs, and configurations, and contact technical support personnel.
• Cause 2: A Stack-Portt on the local device is connected to two different Stack-Ports on the peer device.

  Ensure one-to-one connections for Stack-Ports.

• Cause 3: A Stack-Port on the local device is connected to Stack-Ports on different devices.

  Ensure one-to-one connections for Stack-Ports.

• Cause 4: A Stack-Port on an LPU of the local device is connected to the Stack-Ports on different LPUs of the peer device.

  Remove the cross-connect cable.

• Cause 5: The physical port is connected to the device with a conflicting ID.

  Ensure that the stack IDs at the two ends of the connection are different.

Related Information

None.