No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Alarm Handling

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
CSSM_1. hwCssPhyCsuConnectError

CSSM_1. hwCssPhyCsuConnectError


CSSM/2/CSUCONNECTERR: OID [OID] The connection between CSS port [OCTET1] and [OCTET2] is incorrect.Reason: [OCTET3]

Service interfaces are incorrectly connected through a cluster cable.


Alarm ID Alarm Severity Alarm Type Major processingErrorAlarm(4)


Name Meaning
OCTET1 Indicates the CSS port number of local switch.
OCTET2 Indicates the CSS port number of peer switch.
OCTET3 Indicates the reason of connection error, including:
  • 1 to 2
  • Chassis ID conflict or self-loop.
  • unknown

Impact on the System

The CSS link is wasted.

Possible Causes

1: 1 to 2

A physical member interface of a CSS interface on a member switch connects to physical member interfaces of two CSS interfaces on the other member switch.

2: Chassis ID conflict or self-loop.

The chassis IDs of two devices are same, or a self-loop occurs on the CSS connection.

3: unknown

Other reasons that are unknown.


  1. Check whether the two devices have the same CSS ID. If so, run the set css id new-id [ chassis chassis-id ] command to configure different CSS IDs for the devices.
  2. Check whether CSS interface 1 of frame 1 connects to the physical member interfaces of the same frame.

    • If so, a connection loop occurs. Remove the looped link and go to step 3.
    • If not, go to step 3.

  3. Check whether CSS interface 1 of frame 1 connects to the physical member interfaces of frame 2.

    • If so, the CSS connection is incorrect. Remove the cable of one CSS interface on frame 2 and go to step 4.
    • If not, go to step 4.

  4. Check the connection of CSS interface 2 of frame 1 according to steps 1 and 2.

    If CSS interface 2 is not configured on frame 1, go to step 5.

  5. Check the connection of frame 2 according to steps 2, 3, and 4.
  6. Check the connection of the physical member interfaces of all CSS interfaces.

    • If so, the alarm handling ends.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 183015

Downloads: 44

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next