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

Reminder

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

upgrade

Alarm Handling

S9300, S9300E, and S9300X V200R013C00

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

CSSM

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.1 hwCssLinkDown

Description

CSSM/3/CSSLINKDOWN: OID [OID] [INTEGER1]/[INTEGER2] CSS port [INTEGER3] down.

The CSS port goes Down.

NOTE:

This alarm cannot be automatically cleared and must be manually cleared on the web system.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.1 Minor equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
INTEGER1 Indicates the chassis ID.
INTEGER2 Indicates the slot ID.
INTEGER3 Indicates the port number.

Impact on the System

Bandwidth between the CSS devices is reduced or the CSS breaks up.

Possible Causes

1: The CSS cable is removed or loose.

2: The CSS cable is faulty.

Procedure

  1. Check whether the cable is connected securely to the CSS port.

    • If not, connect the CSS cable to the port securely.
    • If so, go to step 2.

  2. Check whether the indicator on the CSS card is on.

    • If not, replace the cable.
    • If so, go to step 3.

  3. Check whether a clear alarm is generated.

    • If so, no action is required.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

Related Information

None.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.2 hwCssLinkUp

Description

CSSM/4/CSSLINKUP: OID [OID] [INTEGER1]/[INTEGER2] CSS port [INTEGER3] up.

The CSS port goes Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.2 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
INTEGER1 Indicates the chassis ID.
INTEGER2 Indicates the slot ID.
INTEGER3 Indicates the port number.

Impact on the System

The connections between CSS devices are recovered and services are restored.

Possible Causes

The fault on the CSS port is rectified.

Procedure

  1. This alarm is informational and no action is required.

Related Information

None.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.3 hwCssSwitchOver

Description

CSSM/4/SWITCHOVER: OID [OID] CSS switchover is complete. The new master chassis ID is [INTEGER].

An active/standby switchover occurs in the CSS.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.3 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
INTEGER Indicates the chassis ID.

Impact on the System

Traffic processing capability of the CSS degrades.

Possible Causes

1:

The active/standby switchover is triggered by command line.

2:

The master device is reset due to a fault.

3:

The main control board of the master device is removed.

Procedure

  1. Check whether the active/standby switchover is performed by using the command line for a reason such as network maintenance.

    • If so, go to step 4.
    • If not, go to step 2.

  2. View the alarm information related to the master device's main control board. If the main control board has generated an alarm, the active/standby switchover is triggered by the master device's fault.

    • If the master device's main control board is faulty, rectify the fault.
    • If the master device's main control board functions properly, go to step 3.

  3. Check whether the main control board of the master device is removed.

    • If so, go to step 4.
    • If not, no action is required.

  4. Install the main control board and check whether the alarm is cleared.

    • If so, no action is required.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

Related Information

None.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.4 hwCssConnectError

Description

CSSM/2/CSSCONNECTERROR: OID [OID] CSS connection error, [INTEGER1]/[INTEGER2] CSS port [INTEGER3] link to [INTEGER4]/[INTEGER5] port [INTEGER6], this port should link to [INTEGER7]/[INTEGER8] port [INTEGER9].

CSS cable connections are incorrect.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.4 Major equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
INTEGER1 Indicates chassis ID 1.
INTEGER2 Indicates slot ID 1.
INTEGER3 Indicates port number 1.
INTEGER4 Indicates chassis ID 2.
INTEGER5 Indicates slot ID 2.
INTEGER6 Indicates port number 2.
INTEGER7 Indicates chassis ID 3.
INTEGER8 Indicates slot ID 3.
INTEGER9 Indicates port number 3.

Impact on the System

The CSS cannot be set up.

Possible Causes

The cluster cables are not connected according to the cable connection rule.

Procedure

  1. Check whether cable connections are correct.

    1. Remove the cable between port [INTEGER1]/[INTEGER2]/0/[INTEGER3] and port [INTEGER4]/[INTEGER5]/0/[INTEGER6].
    2. Connect a cable between port [INTEGER1]/[INTEGER2]/0/[INTEGER3] and port [INTEGER7]/[INTEGER8]/0/[INTEGER9].
    3. Run the display css channel command to check whether this connection exists. If so, the connection is correct, and the alarm will be cleared.
    4. If the alarm persists, go to step 2.

  2. Contact technical support personnel.

Related Information

None

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.5 hwCssSplit

Description

CSSM/2/CSSSPLIT: OID [OID] CSS system splited.

The CSS split.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.5 Major equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.

Impact on the System

Inter-chassis services will be affected.

Possible Causes

The CSS cable connections are interrupted.

Procedure

  1. Check whether cables are connected properly.

    • If so, go to step 3.
    • If not, go to step 2.

  2. Run the display trapbuffer command to check whether the alarm BASETRAP_1.3.6.1.4.1.2011.5.25.129.2.1.12 hwEntityBecomeMaster exists and whether the ProbableCause code is 612.

    • If so, go to step 5.
    • If not, go to step 3.

  3. Check whether the indicator on the CSS card is on.

    • If the indicator is on, go to step 4.
    • If the indicator is off, replace the cable.

  4. Check whether the alarm is cleared.

    • If so, no action is required.
    • If not, go to step 5.

  5. Contact technical support personnel.

Related Information

None.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.6 hwCssEstablish

Description

CSSM/4/CSSESTABLISH: OID [OID] CSS system established.

The CSS is set up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.6 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.

Impact on the System

The CSS is successfully set up.

Possible Causes

1:

Two devices are connected with CSS cables to form a CSS.

2:

The CSS devices are started.

Procedure

  1. This alarm is informational and no action is required.

Related Information

None.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.7 hwCssFastUpgradeFail

Description

CSSM/2/FASTUPGRADEFAIL: OID [OID] CSS fast upgrade failed.

Fast upgrade failed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.7 Major processingErrorAlarm(4)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.

Impact on the System

System software upgrade failed.

Possible Causes

Cause 1:

LPUs fail to register.

Cause 2:

The new system software cannot start and the system rolls back to the previous version.

Procedure

  1. After this alarm is displayed, by default, the system automatically rolls back to the previous system version. Run the display device command to check whether LPUs can register successfully.

    • If so, go to step 2.
    • If an LPU fails to register, the LPU hardware is faulty. Replace this LPU.

  2. Check whether the current version supports these LPUs.

    • If so, go to step 3.
    • If not, go to step 4.

  3. Run the reboot fast command to upgrade the CSS after a fast restart.
  4. Remove or replace the unsupported LPUs and then upgrade the CSS.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.8 hwCssPhyCsuConnectError

Description

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.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.8 Major processingErrorAlarm(4)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
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.

Procedure

  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.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.9 hwCssLpuInvalidLicense

Description

CSSM/1/CSSLICENSEINVALID: OID [OID] The license on the device is not activated or has expired, so the Lpu-based CSS function can not be used.

When the license on the device is not activated or has expired, no CSS can be set up using service interfaces.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.9 Critical processingErrorAlarm(4)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.

Impact on the System

No CSS can be set up using service interfaces and the established CSS breaks.

Possible Causes

To set up a CSS using service interfaces, a license is required. When the license on the device is not activated or has expired, no CSS can be set up using service interfaces.

Procedure

  1. Run the display license command to check the status of the license.
  2. If the license on the device is not activated, run the license active file-name command to activate the license, and then re-set up the CSS. If no license is on the device, apply for a license file and activate the license.
  3. If the license has expired, use the invalidation code of the old license to apply for a new license and upload the new license to the storage media on the device. Then run the license active file-name command to activate the new license, and then re-set up the CSS.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.10 hwCssPortConfigureFailed

Description

CSSM/2/CSSCFGINVALID: OID [OID] CSS port configuration failed. Please reset slot[OCTET] and configure the CSS port again.

The MPU failed when a user attempted to configure service ports as physical member ports of a CSS port. The service ports became unavailable.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.10 Major processingErrorAlarm(4)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
OCTET Indicates the sot ID of the service ports that failed to be configured as physical member ports.

Impact on the System

The service ports cannot be displayed in the system.

Possible Causes

The MPU was removed when the user was configuring the service ports as physical member ports of a CSS port.

Procedure

  1. Check whether any log was generated when this alarm was generated.

    • If so, go to step 2.
    • If not, go to step 3.

  2. Rectify the fault according to the log.
  3. Reset the card.

Related Information

None

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.11 hwCssPortUpDownAlarm

Description

CSSM/3/CSSUPDOWN: OID [OID] Link on CSS port [STRING] flaps between Up and Down repeatedly.

The number of Up/Down transitions occurring on a CSS port in a specified period reaches the configured threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.11 Minor equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
STRING Indicates the CSS port where the alarm is generated. The value is in the chassis ID/slot ID/subcard ID/port ID format.

Impact on the System

Some data packets are lost on the CSS port that repeatedly alternates between Up and Down. If the number of Up/Down transitions occurring on a CSS port in the specified period reaches the configured threshold, the CSS port is shut down.

Possible Causes

The CSS port repeatedly alternates between Up and Down because the voltage is unstable or the CSS card is swapped. The number of Up/Down transitions occurring on the CSS port in the specified period reaches the threshold.

By default, the threshold for the period during which a CSS port alternates between Up and Down states is 3 minutes, and the threshold for the number of Up/Down transitions per minute is 10. To change the thresholds, run the css port link-flap trigger command.

Procedure

  1. Check whether the voltage is unstable.

    • If so, go to step 4 after the voltage is stable.
    • If not, go to step 2.

  2. Check whether the CSS card is removed and then installed multiple times.

    • If so, do not remove and then install the CSS card and go to step 4.
    • If not, go to step 3.

  3. Replace the optical module and fiber to check whether they are faulty.

    • If so, replace the faulty optical module or fiber and then go to step 4.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

  4. Restore the CSS port that is automatically shut down. Alternatively, run the css port link-flap trigger error-down auto-recovery-interval time command to set the interval before CSS ports in error-down state can automatically turn Up.

Related Information

None.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.12 hwCssPortCrcErrorAlarm

Description

CSSM/3/CSSCRC: OID [OID] CSS port [STRING] continuously receives CRC error packets.

The number of CRC error packets received a CSS port per minute in a specified period reaches the configured threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.12 Minor equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
STRING Indicates the CSS port where the alarm is generated. The value is in the chassis ID/slot ID/subcard ID/port ID format.

Impact on the System

Some data packets are lost on the CSS port that continuously receives CRC error packets. If the number of CRC error packets received a CSS port per minute in the specified period reaches the configured threshold, the CSS port is shut down.

Possible Causes

The CSS port continuously receives CRC error packets because the voltage is unstable or the CSS card is swapped. The number of CRC error packets received by a CSS port per minute in the specified period reaches the threshold.

By default, the threshold for the period during which CRC-error packets are received is 3 minutes, and the threshold for the number of CRC-error packets received per minute is 10. To change the two thresholds, run the css port crc trigger command in the system view.

Procedure

  1. Check whether the voltage is unstable.

    • If so, go to step 4 after the voltage is stable.
    • If not, go to step 2.

  2. Check whether the CSS card is removed and then installed multiple times.

    • If so, do not remove and then install the CSS card and go to step 4.
    • If not, go to step 3.

  3. Replace the optical module and fiber to check whether they are faulty.

    • If so, replace the faulty optical module or fiber and then go to step 4.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

  4. Restore the CSS port that is automatically shut down. Alternatively, run the css port link-flap trigger error-down auto-recovery-interval time command to set the interval before CSS ports in error-down state can automatically turn Up.

Related Information

None.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.13 hwCssPortErrorDown

Description

CSSM/3/CSSERRORDOWN: OID [OID] CSS port [STRING] has turned into error-down state.

A CSS port is shut down by the CSS port error-down function.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.13 Minor equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
STRING Indicates the CSS port where the alarm is generated. The value is in the chassis ID/slot ID/subcard ID/port ID format.

Impact on the System

After the CSS port is shut down, traffic on the CSS port is distributed to another port.

Possible Causes

The number of CRC-error packets received per minute or the number of Up/Down transitions on the CSS port in the specified period reaches the configured threshold.

By default, the threshold for the period during which CRC-error packets are received on the CSS port is 3 minutes, and the threshold for the number of CRC-error packets received per minute is 10. To change the two thresholds, run the css port crc trigger command in the system view. The threshold for the period during which CSS ports alternate between Up and Down states is 3 minutes, and the threshold for the number of Up/Down transitions per minute is 10. To change the thresholds, run the css port link-flap trigger command.

Procedure

  1. Check whether the voltage is unstable.

    • If so, go to step 4 after the voltage is stable.
    • If not, go to step 2.

  2. Check whether the CSS card is removed and then installed multiple times.

    • If so, do not remove and then install the CSS card and go to step 4.
    • If not, go to step 3.

  3. Replace the optical module and fiber to check whether they are faulty.

    • If so, replace the faulty optical module or fiber and then go to step 4.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

  4. Restore the CSS port that is automatically shut down. Alternatively, run the css port link-flap trigger error-down auto-recovery-interval time command to set the interval before CSS ports in error-down state can automatically turn Up.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.14 hwCssPortErrorDownRecover

Description

CSSM/4/CSSERRORDOWNRECOVER: OID [OID] CSS port [STRING] has recovered from error-down state.

A CSS port in error-down state automatically turns Up after a specified interval.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.14 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
STRING Indicates the CSS port where the alarm is generated. The value is in the chassis ID/slot ID/subcard ID/port ID format.

Impact on the System

The CSS port in error-down state can automatically turn Up after the specified interval.

Possible Causes

The error-down recovery function has been configured on the CSS port using the css port { crc | link-flap } trigger error-down auto-recovery-interval command.

Procedure

  • This alarm is informational only, and no action is required.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.16 hwCssStandbyError

Description

CSSM/2/CSSNOMPU: OID [OID] The CSS enters the standby-no-MPU state.

The CSS enters the standby-no-MPU state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.16 Major equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.

Impact on the System

You can only run the display commands but cannot use the configuration commands.

Possible Causes

  • The last MPU in the master or standby chassis is removed.

  • The last MPU in the master or standby chassis is reset.

  • The last MPU in the master or standby chassis fails.

Procedure

  1. Run the display device command to check whether there is any MPU present in the standby chassis.

    • If no MPU is present in the standby chassis, install an MPU in the standby chassis and wait until the MPU registers successfully.
    • If an MPU is present in the standby chassis but does not register in a long time, this MPU has failed. Replace the MPU and wait until the new MPU registers successfully.

  2. Run the display css status command to check whether the CSS is working in normal state.

    • If so, no action is required.
    • If not, collect alarm information and configuration information, and then contact technical support personnel.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.17 hwCssStandbyErrorRestore

Description

CSSM/4/CSSNOMPURECOVER: OID [OID] The CSS is recovered from the standby-no-MPU state.

The CSS is recovered from the standby-no-MPU state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.17 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.

Impact on the System

Configuration commands are executable and there is no impact on services.

Possible Causes

MPUs are installed in the standby chassis.

Procedure

  • This alarm message is informational only, and no action is required.

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.18 hwCssPortStateError

Description

CSSM/3/CSSPORTSTATEERROR: OID [OID] CSS port [STRING1] status is error. Reason: [STRING2]

The status of a CSS port is abnormal.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.18 Minor processingErrorAlarm(4)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
STRING1 Indicates the name of a CSS port.
STRING2 Indicates the cause of the incorrect CSS port status.

Impact on the System

The CSS link connected to the faulty CSS port is Down. If there are other cluster links working normally in the CSS, this faulty has not impact on the CSS. If other cluster links also fail, the CSS may split.

Possible Causes

  • The CSS port is connected to a non-CSS port.

  • A local and a remote CSS ports are in Up and Down states respectively.

  • A CSS port on the third chassis connects to the CSS.

  • If the CSS is set up using CSS cards on SRUAs or SRUBs, the number of cluster cables is less than 8.

Procedure

  1. If the CSS is set up using CSS cards on SRUAs or SRUBs, and the number of cluster cables is less than 8, ensure that all CSS ports are connected based on cable connection requirements. In other situations, perform the following procedure:
  2. Find the two ports at both end of the cluster link according to the CSS port name provided in the alarm.
  3. Check the cluster cable connections against the networking diagram. If any cluster cable is connected incorrectly, correct the cable connections. After all cluster cables are correctly connected, check whether this alarm persists.

    • If so, go to step 4.
    • If not, the alarm handling ends.

  4. Perform either of the following operations depending on the CSS connection mode:

    • If the CSS card connection mode is used, go to step 6.
    • If the CSS port connection mode is used, run the display css css-port all command to check whether the remote service port connected to the local CSS port has been configured as a CSS port.
      • If so, go to step 6.
      • If not, go to step 5.

  5. Configure the remote service port as a CSS port.

    1. Run the interface css-port command to configure a logical CSS port and enter its view.
    2. Run the port interface enable command to configure the remote service port as a physical member port and add it to the logical CSS port.

  6. Check whether the alarm persists. (If the alarm persists, an alarm message is generated every 1 minute.)

    • If so, go to step 7.
    • If not, the alarm handling ends.

  7. Check whether the cables and optical modules are working properly. If they are not working properly, replace the faulty cable or optical module and then check whether this alarm persists.

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

Related Information

None

CSSM_1.3.6.1.4.1.2011.5.25.183.3.3.2.19 hwCssPhyCardConnectError

Description

CSSM/2/CSSCARDCONNECTERR: OID [OID] The connection between CSS port [STRING1] and [STRING2] is incorrect. [STRING3]

CSS ports are incorrectly connected.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.183.3.3.2.19 Major equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
STRING1 Indicates the local CSS port ID.
STRING2 Indicates the peer CSS port ID.
STRING3 Indicates the reason of incorrect connection.

Impact on the System

The incorrect connection may cause a failure to set up a CSS.

Possible Causes

  • CSS IDs conflict with each other.
  • A cluster cable connects two ports on the same chassis.
  • CSS ports are incorrectly connected.
  • Card types of the two member switches do not match. For example, the MPU models do not match, MPUs are connected to SFUs, or software versions do not match (for example, one switch using SRUEs runs V200R010, while the other switch using SRUHs runs V200R009).

Procedure

  1. If the CSS IDs conflict or a cluster cable connects two ports on the same chassis, run the display css status command to check the two CSS IDs. If they are the same, run the set css id command to modify the CSS ID of one chassis and then restart the chassis.
  2. If the two CSS IDs are different, check whether a cluster cable connects two ports on the same chassis. If so, reconnect the cluster cable correctly.
  3. If CSS ports are incorrectly connected, connect them correctly according to the alarm.
  4. If card types or software versions of the two member switches do not match, use two switches with the same card type or version to set up a CSS.
  5. If the fault persists, collect alarm information and configuration information, and then contact technical support personnel.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 5084

Downloads: 6

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