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.