Checking Whether a CSS Is Established Through Service Port Connections
After you complete CSS configurations, review key indicators to check whether the CSS has been established successfully. If the CSS has been successfully established, log in to the CSS and run commands to confirm the CSS status information and configure enhanced CSS functions. If no CSS has been established, check the indicator abnormalities or log in to the CSS and run commands to locate and rectify faults.
Reviewing Indicators to Check Whether a CSS Is Established
Context
After a CSS is set up, you can review indicators on the member switches to check CSS status information, including the master/standby state of switches and link status.
Checking Whether Indicator Status Is Normal
- On one switch, the ACT indicator on an MPU is steady green. On the other switch, the ACT indicator on an MPU is blinking green.
- All the LINK indicators for physical member ports on service cards are steady green.
- When SRUCs are used, CSS ID indicator 1 on an MPU of one switch and CSS ID indicator 2 on an MPU of the other switch are steady green.
For details about the indicator status and meanings, see Indicator Status in Service Port Connection Mode.
Follow-Up Process
If the indicator status is normal, log in to the CSS and run commands to check CSS status information and configure enhanced CSS functions.
If the indicator status is abnormal, locate the fault according to Table 10-10 or log in to the CSS and run commands to locate and rectify the faults.
Indicator Status in Service Port Connection Mode
Table 10-10 describes the indicators that show status of a CSS set up using service ports.
Indicator Location |
Indicator |
Description |
|---|---|---|
MPU |
ACT: MPU master/standby status indicator |
|
MPU |
CSS ID: CSS ID indicator NOTE:
This indicator exists only on SRUCs. |
There are eight CSS ID indicators on the panel, but only
one is on at a time.
|
Service card |
LINK: port status indicator |
|
Logging In to a CSS to Check Whether a CSS Is Established
Context
You can log in to a CSS and run display commands to check whether the CSS is established successfully. If the CSS fails to be established, you can locate the faults according to the command output.
Procedure
- Log in to the CSS.
- Local login: Log in to the CSS from the console port on any MPU.
- Remote login: After reachable routes are configured, you can remotely log in to the CSS from a management interface on any MPU or a Layer 3 interface using Telnet, STelnet, web, or SNMP.
After a CSS is established successfully, the configuration file of the master switch takes effect. When logging in to a CSS remotely, access the IP address of the master switch.
If a CSS is not established, log in to the two member switches for troubleshooting.
- Check whether a CSS has been established successfully.
Run the display device command to check the card status. If the card status of two member switches is displayed in the command output, the CSS is established successfully.
<HUAWEI> display device Chassis 1 (Master Switch) S9706's Device status: Slot Sub Type Online Power Register Status Role - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - EH1D2X12SSA0 Present PowerOn Registered Normal NA 2 - EH1D2X12SSA0 Present PowerOn Registered Normal NA 7 - EH1D2SRUC000 Present PowerOn Registered Normal Master 8 - EH1D2SRUC000 Present PowerOn Registered Normal Slave PWR1 - - Present PowerOn Registered Normal NA PWR2 - - Present PowerOn Registered Normal NA CMU2 - EH1D200CMU00 Present PowerOn Registered Normal Master FAN1 - - Present PowerOn Registered Normal NA FAN2 - - Present PowerOn Registered Normal NA Chassis 2 (Standby Switch) S9706's Device status: Slot Sub Type Online Power Register Status Role - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - EH1D2X12SSA0 Present PowerOn Registered Normal NA 2 - EH1D2X12SSA0 Present PowerOn Registered Normal NA 7 - EH1D2SRUC000 Present PowerOn Registered Normal Master 8 - EH1D2SRUC000 Present PowerOn Registered Normal Slave PWR1 - - Present PowerOn Registered Normal NA PWR2 - - Present PowerOn Registered Normal NA CMU1 - EH1D200CMU00 Present PowerOn Registered Normal Master FAN1 - - Present PowerOn Registered Normal NA FAN2 - - Present PowerOn Registered Normal NAAlternatively, run the display css status command to check the CSS status. If the CSS status of two member switches is displayed, the CSS is established successfully. The following is an example of the display css status command output.
<HUAWEI> display css status CSS Enable switch On Chassis Id CSS Enable CSS Status CSS Mode Priority Master Force ------------------------------------------------------------------------------ 1 On Master LPU 100 Off 2 On Standby LPU 10 Off- If the command output contains information about both switches, go to step 3.
- If the command output contains information about only one switch, rectify the fault according to Checking Whether Cables Are Correctly Connected.
- Check whether the cluster link topology is the same as
the actual hardware connection.
Run the display css channel all command to check whether the cluster link connections are the same as the actual hardware connections. The following is an example of the display css channel all command output.
<HUAWEI> display css channel all CSS link-down-delay: 0ms Chassis 1 || Chassis 2 ================================================================================ Num [CSS port] [LPU Port] || [LPU Port] [CSS port] 1 1/1 XGigabitEthernet1/10/0/3 XGigabitEthernet2/10/0/3 2/1 2 1/1 XGigabitEthernet1/10/0/4 XGigabitEthernet2/10/0/5 2/1 Chassis 2 || Chassis 1 ================================================================================ Num [CSS port] [LPU Port] || [LPU Port] [CSS port] 3 2/1 XGigabitEthernet2/10/0/3 XGigabitEthernet1/10/0/3 1/1 4 2/1 XGigabitEthernet2/10/0/5 XGigabitEthernet1/10/0/4 1/1- If the displayed cluster link connections are the same as the actual hardware connections, all the cluster links are running normally and a CSS is established successfully.
- If some cluster links are not displayed, run the display css css-port all command to check the status of all CSS ports.
<HUAWEI> display css css-port all B : broadcast *down : administratively down Logic Port Num Phy Port Status (B)css-port1/1 6 XGigabitEthernet1/10/0/0 down XGigabitEthernet1/10/0/1 down XGigabitEthernet1/10/0/2 down XGigabitEthernet1/10/0/3 up XGigabitEthernet1/10/0/4 up XGigabitEthernet1/10/0/5 down css-port1/2 0 Logic Port Num Phy Port Status (B)css-port2/1 6 XGigabitEthernet2/10/0/0 down XGigabitEthernet2/10/0/1 down XGigabitEthernet2/10/0/2 down XGigabitEthernet2/10/0/3 up XGigabitEthernet2/10/0/4 down XGigabitEthernet2/10/0/5 up css-port2/2 0- If the CSS ports with abnormal cluster links are Up, the cluster cables may be connected incorrectly. Rectify the fault according to Checking Whether Cables Are Correctly Connected.
- If the CSS ports with abnormal cluster links are Down, check whether the physical member ports have been shut down (*down in Status field) and whether cluster cables on the ports are loose or damaged.
Rectifying Common CSS Faults
Checking Whether Cables Are Correctly Connected
Run the terminal monitor and terminal trapping commands in the user view to enable the alarm function. Check whether an alarm indicating incorrect cluster cable connection is displayed. (The OID is 1.3.6.1.4.1.2011.5.25.183.3.3.2.8 hwCssPhyCsuConnectError.)
- If no alarm is generated, check the LINK indicator. If the indicator is off, check whether the optical modules, optical fibers, and cables are working normally.
- If such an alarm is displayed, connect cluster cables correctly
according to the alarm message. You can obtain the following information
from the alarm message:
- Incorrect connection information. You can find the incorrectly connected cluster cable according to the CSS ID, logical CSS port number, and physical member port number displayed in the alarm message.
- Correct connection of the cluster cable.
Table 10-11 describes how to rectify a fault according to the alarm message.
Table 10-11 Rectifying a fault according to the alarm messageError Message
Cause
Problem Handling
A cluster cable connects two switches with different CSS IDs. For example, The connection between CSS port 1/10/0/9 and 2/1/0/1 is incorrect. Reason: 1 To 2
The CSS IDs are correctly configured but the cluster cable is connected to an incorrect port.
Connect the cluster cables to the correct ports according to the alarm message and ensure that the cable connectors are securely connected to the ports. After the cables are correctly connected, the two switches merge into a CSS.
A cluster cable connects two switches with the same CSS ID. For example, The connection between CSS port 1/10/0/9 and 1/1/0/1 is incorrect. Reason: Chassis ID conflict or self-loop.
Possible causes are:
- The cluster cable connects two CSS ports on the same switch.
- The connected ports are on different switches, but the switches are configured with the same CSS ID.
Run the display css status command to check the CSS IDs of the two switches.
- If they are different, the CSS IDs are configured correctly. This alarm message indicates that the cluster cable connects two CSS ports on the same switch. Connect the cluster cable correctly according to the alarm message.
- If they are the same, run the set css id command to change the CSS ID of one switch and then restart this switch.