FSP
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.1 hwStackLinkUp
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.2 hwStackLinkDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.3 hwStackStandbyChange
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.4 hwStackSwitchOver
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.5 hwStackSystemRestart
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.6 hwStackStackMemberAdd
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7 hwStackStackMemberLeave
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.8 hwStackSystemMacChange
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.9 hwStackLogicStackPortLinkErr
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.10 hwStackPhyStackPortLinkErr
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.11 hwPhyStackPortIsDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.12 hwPhyStackPortIsUp
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.14 hwStackPortConfigureFailed
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.32 hwStackMemberExceedSpec
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.41 hwPhyStackPortErrorDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.42 hwPhyStackPortErrorDownRecover
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.49 hwPhyStackVlanConflict
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.59 hwStackPortErrorDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.60 hwStackPortErrorDownRecovery
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.61 hwStackSetUpFailure
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.64 hwStackAutoConfigFailed
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.65 hwStackPortLinkErr
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.1 hwStackLinkUp
Description
FSP/4/STACKPORT_UP: OID [oid] Stack-port [integer]/[integer] changes to up.
This alarm was sent to the NMS by the master switch when the logical stack port of a switch in the stack system was Up.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.183.1.22.1 |
Warning |
equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
[integer] |
Stack ID of the device generating the alarm. |
[integer] |
ID of the logical stack port whose status changes on the device. This ID starts from 0. |
Impact on the System
If the stack interface is Up, service interfaces in the stack system increase. Services, however, are not interrupted.
If the stack interface is Down, the stack system recalculates the ring-breaking point, and then refreshes the forwarding entries. In this case, services are transiently interrupted and automatically recover after the forwarding entries are refreshed.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.2 hwStackLinkDown
Description
FSP/3/STACKPORT_DOWN: OID [oid] Stack-port [integer]/[integer] changes to down.
This alarm was sent to the NMS by the master switch when the logical stack port of a switch in the stack system was Down.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.183.1.22.2 |
Minor |
equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
[integer] |
Stack ID of the device generating the alarm. |
[integer] |
ID of the logical stack port whose status changes on the device. This ID starts from 0. |
Impact on the System
If the previous stack system is in a ring topology and the interface in the Down state just functions as the ring-breaking point, the topology may become a link topology. Services, however, are not affected. If the logical stack port in the Down state does not function as the ring-breaking point, the stack system refreshes the forwarding entries. In this case, services are transiently interrupted and automatically recover after the forwarding entries are refreshed.
If the previous stack system is in a link topology, services on the switch that is Down are interrupted and cannot recover until the switch is added to the stack system again.
Possible Causes
1. The switch in the stack system was powered off.
2. The stack cable was connected loosely or even removed.
3. The stack card was loosened.
Procedure
- Check whether the switch was powered off.
If it was powered off, power on it. The alarm handling ends.
If not, go to step 2.
- Run the display stack port command to check whether physical member ports are Up.
If so, collect alarm information and configuration information, and then contact technical support personnel.
If not, go to step 3.
- Check whether the stack card is loose. If it is loose, install it securely and then run the display stack port command to check whether physical member ports are Up.
If so, the alarm handling ends.
If not, rectify the fault according to An Ethernet Interface Is Physically Down.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.3 hwStackStandbyChange
Description
FSP/4/STANDBY_CHANGE: OID [oid] Slot [integer] is designated as standby.
This alarm was generated when a slave switch was elected as the standby switch.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.3 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| [integer] | Stack ID of the device generating the alarm. |
Impact on the System
Services on the original standby switch are interrupted and cannot recover until the switch is added to the stack system again.
Possible Causes
1. Once a new stack system was created, a slave switch was elected as the standby switch.
2. The original standby switch left the stack system if the switch was powered off or the stack cable was loosened or manually removed. In this case, a new standby switch was elected.
Procedure
- Check whether the stack system was just set up and the
standby switch was elected.
- If so, this alarm is informational only, and no action is required.
- If not, go to step 2.
- Check whether the switch was powered off.
If it was powered off, power on it. The alarm handling ends.
If not, go to step 3.
- Run the display stack port command to check whether physical
member ports are Up.
If so, collect alarm information and configuration information, and then contact technical support personnel.
If not, go to step 4.
- Check whether the stack card of the
original standby switch is loose. If it is loose, install it securely
and then run the display stack port command to check whether physical
member ports are Up.
If so, the alarm handling ends.
If not, rectify the fault according to An Ethernet Interface Is Physically Down.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.4 hwStackSwitchOver
Description
FSP/4/STACK_SWITCHOVER: OID [oid] After switchover, slot [integer] is selected as master.
This alarm was generated when the original standby switch became the master switch.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.4 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| [integer] | Stack ID of the device generating the alarm. |
Impact on the System
When the standby switch becomes the master switch to replace the faulty original master switch, the device needs to refresh entries, which interrupts services.
Possible Causes
1. The master switch was powered off and left the stack system.
2. The stack cable connecting the master switch was loosened or the stack card was loosened.
3. The master/standby switchover was manually performed.
Procedure
- Check whether the active/standby switchover was manually performed using the slave switchover command.
- If so, this alarm is informational only, and no action is required.
- If not, go to step 2.
- Check whether the original master switch was powered off.
- If so, power on it. The alarm handling ends.
- If not, go to step 3.
- Check whether the stack cable of the original master switch is loose.
- If so, install the stack cable securely. The alarm handling ends.
- If not, go to step 4.
- Check whether the stack card to which the stack cable of the original master switch is connected is loose.
- If so, remove and install the stack card. The alarm handling ends.
- If not, collect alarm information and configuration information, and then contact technical support personnel.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.5 hwStackSystemRestart
Description
FSP/4/STACK_RESTART: OID [oid] After stack restart, the new master is slot [integer].
This alarm was sent to the NMS by the master switch after all the switches in the stack system were restarted.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.5 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| [integer] | Stack ID of the device generating the alarm. |
Impact on the System
During the restart of the stack system, services are interrupted. After the restart of the stack system, services recover.
Possible Causes
1. The reboot command was manually run on the master switch to restart the stack system.
2. The master and standby switches in the stack system were powered off at the same time.
3. All the switches in the stack system were powered off at the same time.
Procedure
- Check whether the stack system was manually restarted using
the reboot command.
If so, the alarm handling ends.
If not, go to step 2.
- Check whether the stack system was powered off.
If so, the alarm handling ends.
If not, collect alarm information and configuration information, and then contact technical support personnel.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.6 hwStackStackMemberAdd
Description
FSP/4/STACKMEMBER_ADD: OID [oid] Slot [integer] is added into stack.
This alarm is generated when a new member switch is added to the stack system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.6 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| [integer] | Stack ID of the device generating the alarm. |
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7 hwStackStackMemberLeave
Description
FSP/4/STACKMEMBER_LEAVE: OID [oid] Slot [integer] leaves from stack.
This alarm was generated when a member switch left the stack system.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.7 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| [integer] | Stack ID of the device generating the alarm. |
Possible Causes
1. A switch was manually removed from the stack system.
2. A switch in the stack system was powered off.
3. The stack cable connecting a switch in the stack system was removed or the stack card was loosened.
Procedure
- Check whether the switch was manually removed from the stack system.
- If so, the alarm handling ends.
- If not, go to step 2.
- Check whether the switch was manually powered off.
- If so, power on it. The alarm handling ends.
- If not, go to step 3.
- Check whether the stack cable of the switch was loose.
- If so, install the stack cable securely. The alarm handling ends.
- If not, go to step 4.
- Check whether the stack card to which the stack cable of the switch is connected is loose.
- If so, remove and install the stack card. The alarm handling ends.
- If not, collect alarm information and configuration information, and then contact technical support personnel.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.8 hwStackSystemMacChange
Description
FSP/4/STACK_MAC_CHANGE: OID [oid] Stack system's MAC address changes to slot [integer]'s MAC address [octet].
When the master switch in the stack system changed, the MAC address of the stack system was switched to the MAC address of the new master switch if the MAC address switching function was enabled in the stack system. In this case, this alarm was generated.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.8 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
| oid | Indicates the MIB object ID of the alarm. |
| [integer] | Stack ID of the device generating the alarm. |
| [octet] | New MAC address currently used by the stack system. |
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.9 hwStackLogicStackPortLinkErr
Description
FSP/3/LOGPORT_ILLEGAL: OID [OID] Stack port [octet1] connects to [octet2], and there are port members of the same logic stack port ID.
The logical stack ports are connected in a wrong order. The switch requires that the member ports in logical stack port 1 be connected to the member ports in stack port 2.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.9 | Minor | communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| [octet1] | Indicates the local interface name. |
| [octet2] | Indicates the name of remote interface connected to the local interface. |
Procedure
- Run the display stack port command to check member ports of logical stack ports.
- Connect the member ports in the local logical stack port 1 to those in the remote logical stack port 2, and connect the member ports in the local logical stack port 2 to those in the remote logical stack port 1.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.10 hwStackPhyStackPortLinkErr
Description
FSP/3/PHYPORT_ILLEGAL: OID [OID] Stack ports [octet1] and [octet2] are in the same logical stack port, but connect to different switches.
The member ports in a logical stack port on the switch are connected to different switches. The switch requires that the member ports in the same logical stack port be connected to the same switch.
Incorrect stack logical connection: When physical ports connecting two member switches belong the same logical stack port, for example, logical stack port 1 or 2, the alarm hwStackLogicStackPortLinkErr is generated, indicating an incorrect stack logical connection.
Incorrect stack physical connection: When physical ports belonging to the same logical stack port connect to two member switches, the alarm hwStackPhyStackPortLinkErr is generated, indicating an incorrect stack physical connection.
If a physical port in a logical stack port experiences both physical and logical connection errors, only the alarm hwStackLogicStackPortLinkErr is generated, indicating an incorrect stack logical connection.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.10 | Minor | communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| [octet1] | Name of one physical port of the local device. |
| [octet2] | Name of the other physical port of the local device. |
Possible Causes
The member ports in a logical stack port on the switch are connected to different switches.
Procedure
- Run the display stack port command to check member ports of logical stack ports.
- Run the display lldp neighbor brief command to check the remote device and ports to which member ports are connected.
- Check whether the member ports in a logical stack port
are connected to different devices.
- If so, connect all member ports in the logical stack port to the same device according to the stack port connection rule.
- If not, collect alarm information and configuration information, and then contact technical support personnel.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.11 hwPhyStackPortIsDown
Description
FSP/3/STACKPORTISDOWN: OID [OID] Stack port [octet] state is down.
A member port that has been added to a logical stack port becomes Down.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.11 | Minor | communicationsAlarm(2) |
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.12 hwPhyStackPortIsUp
Description
FSP/4/STACKPORTISUP: OID [OID] Stack port [octet] state has changed to up.
A member port that has been added to a logical stack port becomes Up.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.12 | Warning | communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| [octet] | Indicates the name of the local interface. |
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.14 hwStackPortConfigureFailed
Description
FSP/3/STACKPORTCFGFAIL: OID [OID] Stack port configuration failed. Please reset slot [OCTET] and re-configure the stack port.
The stacking configuration failed on the interface, and the device needs to be restarted.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.14 | Minor | communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| OCTET | Indicates the stack ID of the device. |
Procedure
- Obtain the stack ID of the device from the alarm.
- Run the reset slot slot-id command to restart the device.
- After the device is restarted successfully, reconfigure the stack port.
- If the stack port can be configured successfully, the alarm handling ends.
- If the stack port cannot be reconfigured, collect alarm information and configuration information, and then contact technical support personnel.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.32 hwStackMemberExceedSpec
Description
FSP/2/STACKMEMBER_EXCEED: OID [OID] The number of stack members exceeds the upper limit. (UpperLimit=[Integer])
The number of member switches in a stack exceeds the maximum value.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.32 | Major | qualityOfServiceAlarm (3) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| Integer | Maximum number of member switches in a stack. |
Impact on the System
When the number of member switches in a stack reaches the maximum value, new member switches cannot join the stack and restart repeatedly.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.41 hwPhyStackPortErrorDown
Description
FSP/2/ERRORDOWN: OID [OID] Runts-error-down occured. (StackPort=[octet])
An error-down event occurred on a physical member port that has been added to a logical stack port.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.41 | Major | communicationsAlarm (2) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| Stack port | Indicates the local port name. |
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.42 hwPhyStackPortErrorDownRecover
Description
FSP/4/ERRORDOWNRECOVER: OID [OID] Runts-error-down recovered. (StackPort=[octet], RecoverType=[octet])
The physical member port that has been added to a logical stack port recovered from the error-down state.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.42 | Warning | communicationsAlarm (2) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| Stack port | Indicates the local port name. |
| Recover type | Indicates the recovery type. |
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.49 hwPhyStackVlanConflict
Description
FSP/3/VLAN_CONFLICT: OID [OID] [octet] conflicts with the stack reserved VLAN. (VlanId=[integer])
The service VLAN conflicts with the stack reserved VLAN.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.183.1.22.49 |
Minor |
environmentalAlarm(6) |
Parameters
| Name | Meaning |
|---|---|
OID |
Indicates the MIB object ID of the alarm. |
[octet] |
Indicates the services or protocols that conflict with the stack reserved VLAN. |
[integer] |
Indicates the stack reserved VLAN ID. |
Impact on the System
The stack reserved VLAN has been used by other service modules. As a result, other devices cannot join the stack.
Possible Causes
When a master/standby switchover occurs in the stack or member switches in the stack restart, and the master switch becomes a standalone switch, the VLAN manually created by users or automatically created by protocols such as VCMP and GVRP is the same as the stack reserved VLAN ID.
Procedure
- Run the display stack command to check the stack reserved VLAN ID.
- Run the display vlan summary command to check the created VLANs. Determine whether the stack reserved VLAN has been created on the switch.
If so, go to step 3.
If not, collect alarm information and configuration information, and then contact technical support personnel.
- Check whether the stack reserved VLAN ID can be changed to another VLAN ID.
If so, run the stack reserved-vlan vlan-id command to change the stack reserved VLAN ID.
If not, go to step 4.
- Delete the created stack reserved VLAN ID.
- If the created stack reserved VLAN is Static VLAN, run the undo vlan vlan-id command to delete it.
- If the created stack reserved VLAN is Dynamic VLAN, run the undo gvrp command to disable the GVRP function.
- If the created stack reserved VLAN is Rrpp reserved, run the control-vlan command to change the control VLAN of RRPP.
- If the created stack reserved VLAN is Sep reserved, run the control-vlan (SEP segment view) command to change the control VLAN of SEP.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.59 hwStackPortErrorDown
Description
FSP/3/PORTERRDOWN: OID [OID] STACK port [STRING] trigger error down. (ErrorDownType=[STRING])
An error-down event occurred on a stack port.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.183.1.22.59 |
Minor |
communicationsAlarm (2) |
Parameters
| Name | Meaning |
|---|---|
OID |
Indicates the MIB object ID of the alarm. |
STACK port |
Indicates the local port name. |
Error down type |
Indicates the error-down event type. |
Possible Causes
Cause 1: The stack port receives CRC error packets.
Cause 2: The stack port frequently alternates between Up and Down states.
Cause 3: The rate of the optical module installed in the port is different from the rate of the port.
Procedure
- Run the display stack port brief command to check the stack port error-down reason.
If the reason is Link-flapping trigger error down, rectify the fault according to An Ethernet Interface Frequently Alternates Between Up and Down States.
If the reason is CRC trigger error down or Runts trigger error down, go to step 2.
If the reason is Media mismatch trigger error down, go to step 4.
- Replace the optical module and run the display interface interface-type interface-number command to check whether the number of CRC error packets received by the interface keeps increasing.
If so, go to step 3.
If not, the alarm handling ends.
- Replace the fiber and run the display interface interface-type interface-number command to check whether the number of CRC error packets received by the interface keeps increasing.
If so, collect alarm information and configuration information, and then contact technical support personnel.
If not, the alarm handling ends.
- Replace the optical module with the one matching the port rate. For details about the optical module matching the port, see service port stacking support in the "Stack Configuration Notes". After the corresponding optical module has been replaced, check whether this alarm is still displayed:
If so, Collect alarm information and configuration information, and then contact technical support personnel.
If not, the alarm handling ends.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.60 hwStackPortErrorDownRecovery
Description
FSP/4/PORTERRDOWN_RECOV: OID [OID] STACK port [STRING] has recovered from error-down state. (ErrorDownType=[STRING])
The stack port recovered from the error-down state.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.60 | Warning | communicationsAlarm (2) |
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.61 hwStackSetUpFailure
Description
FSP/3/SETUPFAILURE: OID [OID] Failed to set up a stack. (LocalSlotID=[integer], PeerSlotID=[integer], Reason=[STRING])
A stack fails to be set up.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.183.1.22.61 |
Minor |
communicationsAlarm (2) |
Parameters
| Name | Meaning |
|---|---|
OID |
Indicates the MIB object ID of the alarm. |
LocalSlotID |
Indicates the slot ID of the local stack member switch. |
PeerSlotID |
Indicates the slot ID of the remote stack member switch. |
Reason |
Indicates the reason why the stack fails to be set up. |
Possible Causes
- The switches cannot set up a stack because of a device model mismatch.
- The switches cannot set up a stack because ports on a dedicated stack card are connected to service ports.
Procedure
- Check whether ports on a dedicated stack card are connected to service ports on the panel or a service card.
- If so, change the connections.
- If not, go to step 2.
- Run the display device command to check the switch model.
- Use switches of the same model or different models that allow to set up a stack together based on Stack Support and Version Requirements.
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. |
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.
Run the display stack port auto-cable-info command to view the logical stack port to which this port needs to be added.
- 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.
Run the display stack port auto-cable-info command to view the logical stack port to which this port needs to be added.
- 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.
- 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.
- Run the interface_fabric-port command to enter the fabric port view.
- 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.
- 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.
- Run the interface_fabric-port command to enter the fabric port view.
- 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.
- 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.
- Run the interface_fabric-port command to enter the fabric port view.
- 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.
Run the display stack port auto-cable-info command to view the logical stack port to which this port needs to be added.
- 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.
FSP_1.3.6.1.4.1.2011.5.25.183.1.22.65 hwStackPortLinkErr
Description
FSP/3/PORTLINK_ERR: OID [OID] Stack ports [octet1] and [octet2] are incorrectly connected. (Reason = [octet])
Service cables are correctly with stack cables incorrectly.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.183.1.22.65 | Minor | communicationsAlarm (2) |
Parameters
| Name | Meaning |
|---|---|
| [OID] | Indicates the MIB object ID of the alarm. |
| [octet1] | Indicates the name of a stack member port in a logical stack port. |
| [octet2] | Indicates the name of the other stack member port in a logical stack port. |
| Reason | Indicates the fault reason. |
Possible Causes
A self-loop occurred in stack connections. For example, two stack member ports in a logical stack cable are connected with the same cable.
Procedure
- Run the display stack port brief command to view information about stack member ports in a logical stack port.
- Check whether two stack member ports in a logical stack
cable are connected with the same cable.
- If so, reconnect the stack member ports.
- If not, go to step 3.
- Collect alarm information and configuration information, and then contact technical support personnel.
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.1 hwStackLinkUp
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.2 hwStackLinkDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.3 hwStackStandbyChange
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.4 hwStackSwitchOver
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.5 hwStackSystemRestart
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.6 hwStackStackMemberAdd
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.7 hwStackStackMemberLeave
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.8 hwStackSystemMacChange
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.9 hwStackLogicStackPortLinkErr
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.10 hwStackPhyStackPortLinkErr
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.11 hwPhyStackPortIsDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.12 hwPhyStackPortIsUp
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.14 hwStackPortConfigureFailed
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.32 hwStackMemberExceedSpec
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.41 hwPhyStackPortErrorDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.42 hwPhyStackPortErrorDownRecover
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.49 hwPhyStackVlanConflict
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.59 hwStackPortErrorDown
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.60 hwStackPortErrorDownRecovery
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.61 hwStackSetUpFailure
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.64 hwStackAutoConfigFailed
- FSP_1.3.6.1.4.1.2011.5.25.183.1.22.65 hwStackPortLinkErr