FSP_1.3.6.1.4.1.2011.5.25.183.1.22.64 hwStackAutoConfigFailed

Description

FSP/2/AUTOCONFIGFAILED: OID [OID] Failed to auto configure stack port. (SlotID=[integer], Port=[octet], Reason=[STRING])

After a dedicated stack cable was connected to the port, this port did not automatically become a stack port.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.183.1.22.64	Major	environmentalAlarm (4)

Parameters

Name	Meaning
OID	Indicates the MIB object ID of the alarm.
SlotID	Indicates the slot ID of the interface to which a dedicated stack cable is connected.
Port	Indicates the port to which a dedicated stack cable is connected.
Reason	Indicates the reason why this port did not automatically become a stack port.

Impact on the System

A stack cannot be set up using dedicated stack cables.

Possible Causes

Reason 1: This port does not support dedicated stack cables.
Reason 2: Ports %s to %s have service configuration.
Reason 3: This port has service configuration.
Reason 4: The logical stack port to which this port needs to be added already has the maximum number of member ports.
Reason 5: The rate of this port is inconsistent with that of other stack member ports.
Reason 6: This port uses a different chip than other stack member ports.
Reason 7: The system power supply mode is incorrect.
Reason 8: The indirectly connected AS mode has been configured on the switch.
Reason 9: The downlink port has been configured as an uplink port.
Reason 10: This port has been configured as a member port of an SVF fabric port.
Reason 11: On an AS, this port has been configured to the independent mode.
Reason 12: A UCL group has been created using the ucl-group command.
Reason 13: The type of this port is inconsistent with the type of other stack member ports.

Procedure

Reason 1: This port does not support dedicated stack cables.
Run the display stack port auto-cable-info command to view ports supporting dedicated stack cables and then connect the dedicated stack cable to such a port.
Reason 2 and reason 3: Ports %s to %s have service configuration and this port has service configuration.
- On ASs in an SVF system, ensure that there are no other configurations except the shutdown and stp root-protection command configurations on ports. Delete unnecessary configurations according to Configuring Services for an AS.
- On switches managed by iMaster NCE-Campus, ensure that there are no other configurations except the shutdown and trust dscp command configurations on ports. Delete unnecessary configurations through a controller.
- On other devices, ensure that there are no other configurations except the shutdown command configuration on ports. Run the display this command in the interface view to view services configured on this interface.
  - If other services need to be configured, connect the dedicated stack cable to another port that supports this cable. To check ports supporting dedicated stack cables, run the display stack port auto-cable-info command.
  - If other services do not need to be configured, run the clear configuration this command in the interface view to clear the configuration of this interface.
Reason 4: The logical stack port to which this port needs to be added already has the maximum number of member ports.
1. Run the display stack port auto-cable-info command to view the logical stack port to which this port needs to be added.
2. Run the display stack port brief command to view member ports in the logical stack port.
  - If the port needs to be added to this logical stack port, delete unnecessary member ports from this logical stack port. The method is as follows: Run the shutdown interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> command in the logical stack port view to shut down specified member ports and then run the undo port interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> enable command to delete these member ports from this logical stack port.
  - If the port does not need to be added to the logical stack port, connect the dedicated stack cable to another port that supports this cable. To check ports supporting dedicated stack cables, run the display stack port auto-cable-info command.
Reason 5: The rate of this port is inconsistent with that of other stack member ports.
1. Run the display stack port auto-cable-info command to view the logical stack port to which this port needs to be added.
2. Run the display stack port brief command to view member ports in the logical stack port, and then run the display stack channel all command to view the speed of member ports.
  - If the port needs to be added to this logical stack port, delete member ports whose speed is inconsistent with the speed of port described in this alarm. The method is as follows: Run the shutdown interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> command in the logical stack port view to shut down specified member ports and then run the undo port interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> enable command to delete these member ports from this logical stack port.
  - If the port does not need to be added to this logical stack port, connect the dedicated stack cable to another port that supports this cable. To check ports supporting dedicated stack cables, run the display stack port auto-cable-info command.
Reason 6: This port uses a different chip than other stack member ports.
When one logical stack port contains two stack member ports, this logical stack port can contain only stack member ports 1 and 2, or 3 and 4. Based on this restriction, modify the logical stack port configuration or connect the dedicated stack cable to another port supporting this cable.
Reason 7: The system power supply mode is incorrect.
Run the set power manage mode command to set the energy-saving mode to any mode except standby.
Reason 8: The indirectly connected AS mode has been configured on the switch.
1. Run the uni-mng command to enter the uni-mng view and run the display this command to check the fabric port to which ports having dedicated stack cables connected are added.
2. Run the interface_fabric-port command to enter the fabric port view.
3. Run the undo port connect-type command to restore the direct connection mode of the fabric port.
Reason 9: The downlink port has been configured as an uplink port.
Run the undo uni-mng up-direction fabric-port command to restore the port as a downlink port.
Reason 10: This port has been configured as a member port of an SVF fabric port.
1. Run the uni-mng command to enter the uni-mng view and run the display this command to check the fabric port to which ports having dedicated stack cables connected are added.
2. Run the interface_fabric-port command to enter the fabric port view.
3. Run the undo port eth-trunk trunkmember command to unbind this port from the fabric port.
Reason 11: On an AS, this port has been configured to the independent mode.
1. Run the uni-mng command to enter the uni-mng view and run the display this command to check the fabric port to which ports having dedicated stack cables connected are added.
2. Run the interface_fabric-port command to enter the fabric port view.
3. Run the undo port connect command to restore the centralized mode.
Reason 12: A UCL group has been created using the ucl-group command.
Run the undo ucl-group all command in the system view to delete all UCL groups.
Reason 13: The type of this port is inconsistent with the type of other stack member ports.
1. Run the display stack port auto-cable-info command to view the logical stack port to which this port needs to be added.
2. Run the display stack port brief command to view the type of member ports in the logical stack port.
  - If the port needs to be added to this logical stack port, delete member ports whose type is inconsistent with the type of port described in this alarm. The method is as follows: Run the shutdown interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> command in the logical stack port view to shut down specified member ports and then run the undo port interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> enable command to delete these member ports from this logical stack port.
  - If the port does not need to be added to this logical stack port, connect the dedicated stack cable to another port that supports this cable. To check ports supporting dedicated stack cables, run the display stack port auto-cable-info command.