MBR/2/CONNECTERROR: OID [oid] Connection error on the fabric-port in unified management. (Reason=[STRING])
Cable connection on the fabric port was incorrect.
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.327.31.3.2.1 |
Major |
environmentalAlarm(6) |
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
Reason |
Indicates the reason of incorrect cable connection. Reasons include the physical port number and peer AS MAC address involved in the cable connection. If the peer AS MAC address cannot be obtained, the MAC address displays --. |
Cause 1: There is a configuration file in the client.
The AS has a startup configuration file.
Cause 2: Input has been detected in the client.
Input exists on the console interface of an AS.
Cause 3: Port check failed.
The AS attempts to connect to the parent through an unsupported port.
Cause 4: The fabric-port has already linked to a client.
Member ports of the same downlink fabric port connect to two ASs.
Cause 5: The client has already linked to a father device.
The AS connects to two parent switches.
Cause 6: The client has already linked to a fabric-port from current device.
The uplink port of the AS connects to multiple fabric ports of the parent.
Cause 7: The fabric-port has been linked to another level-1 AS.
The downlink fabric port of a level-1 AS connects to another level-1 AS.
Cause 8: The parent device has been linked to a level-2 AS.
The parent directly connects to a level-2 AS.
Cause 9: The downstream fabric-port has been linked to another downstream fabric-port.
A downlink fabric port of an AS connects to the parent.
Cause 10: The port has not received any response packets.
The parent does not receive any response packet.
Cause 11: Create Trunk failed in the client.
Failed to create an Eth-Trunk on an AS.
Cause 12: Port Bind Eth-Trunk failed in the client.
Failed to add ports of an AS to an Eth-Trunk.
Cause 13: The switch has been in uni-mng system force mode.
An AS has been configured to work in client mode.
Cause 14: The fabric-port has been linked to another parent device.
The fabric port of the parent connects to another parent.
Cause 15: The current status of AS is busy.
The system is busy on the AS.
Cause 16: The Layer 3 hardware forwarding mode has been enabled on the AS.
Layer 3 hardware forwarding for IPv4 packets has been enabled using the assign forward-mode ipv4-hardware command on the AS.
Cause 17: The port cannot be added to the Eth-Trunk because the port has configurations on the AS.
Configurations exist on the port of an AS.
Cause 18: A downstream port on the AS has been configured as a stack port.
On the AS, its downlink service port is configured as a stack port.
Cause 19: The switch cannot be used as an AS because the assign trunk command has been run.
SVF cannot be enabled because Eth-Trunk specifications have been increased on the AS.
Cause 20: The AS [STRING]s's port [STRING]s has been configured as a downstream fabric port.
The AS port has been configured as a downstream fabric member port.
Cause 21: The level-1 AS's downlink fabric port mode conflicts with the level-1 AS mode.
The level-1 AS uses the centralized mode, while the level-1 AS's downlink fabric port connecting to a level-2 AS has the independent mode configured, which conflicts with the centralized mode of the level-1 AS.
Cause 22: The mode configured for the parent is inconsistent with the mode of level-1 or level-2 ASs.
The AS service configuration mode configured on the parent is inconsistent with the actual AS service configuration mode.
Cause 23: A VLAN has been created on the AS.
The VLAN for VCMP or PNP exists on the AS.
Run the undo startup saved-configuration command in the system view to clear the startup configuration file and restart the AS.
After the AS is restarted, do not perform any operation on the serial port until the message "The switch has entered the uni-mng AS mode, and console port input is allowed." is displayed on the serial port.
Connect the AS to the parent through an uplink port or subcard port. Run the display port connection-type access all command to check all downlink ports on the AS.
Member ports of a downlink fabric port can connect to only one AS, and different ASs must connect to different fabric ports.
Disconnect the AS from one parent switch.
Retain the connection with only one fabric port and disconnect the AS from other fabric ports.
Disconnect the two level-1 ASs from each other.
Disconnect the parent from the level-2 AS.
Disconnect the fabric port of the AS from the parent.
Ensure that the parent is a Huawei switch that supports the SVF function. When the parent is an S5720-EI, delete its configuration file to ensure that it starts without configuration.
Disconnect the AS from the parent and then reconnect them.
Disconnect the AS from the parent and then reconnect them.
On the parent, run the port connect-type indirect command to configure the indirect connection mode for the fabric port that connects to the AS. Alternative, run the undo uni-mng enable command on the AS and restart the AS to enable it exit from the client mode.
Disconnect the fabric port from the remote parent.
Wait until the AS is idle.
Run the undo assign forward-mode command to disable Layer 3 hardware forwarding for IPv4 packets.
Delete the configurations of the port.
Clear the stack configuration of the downlink service port.
Run the undo assign trunk command to restore the default Eth-Trunk specifications and then enable SVF.
Delete the member port configuration or use another port to replace the AS port for configuration.
Run the undo port connect command to change the service configuration mode of the downlink fabric port to centralized mode.
Ensure that the AS service configuration mode configured on the parent is consistent with the actual AS service configuration mode.
Run the reset vcmp or undo pnp startup-vlan command in user view on the AS to restart the AS.