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

Configuration Guide - Device Management

S9300, S9300E, and S9300X V200R012C00

This document describes the configurations of Device Management, including device status query, hardware management, CSS, SVF, PoE, OPS, OIDS, energy-saving management, information center, fault management, NTP, synchronous ethernet, PTP.
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).
Checking Whether a CSS Is Established Through Service Port Connections

Checking Whether a CSS Is Established Through Service Port Connections

After you complete CSS configurations, review key indicators to check that 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 status 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
When two switches establish a CSS successfully, the indicator status is as follows:
  • 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/SRUKs/MFUXs 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 3-12 or log in to the CSS and run commands to locate and rectify the faults.

Indicator Status in Service Port Connection Mode

Table 3-12 describes the indicators that show status of a CSS set up using service ports.

Table 3-12  Indicator status in service port connection mode

Indicator Location

Indicator

Description

MPU

ACT: MPU master/standby status indicator

  • Steady green: The MPU is the master MPU of the CSS, and the local chassis is the master switch.

  • Blinking green: The MPU is the standby MPU of the CSS, and the local chassis is the standby switch.

  • Off: The MPU is the cold standby MPU of the CSS.

MPU

CSS ID: CSS ID indicator

NOTE:

This indicator exists only on SRUCs/SRUKs/MFUXs.

There are eight CSS ID indicators on the panel, but only one is on at a time.
  • CSS ID N is steady on: The CSS ID of the local chassis is N.

  • All CSS ID indicators are off: The chassis is not running the CSS service.

MPU

CSS MASTER: master/standby status indicator

  • Steady green: The MPU is the master MPU of the CSS, and the local chassis is the master switch.
  • Off: The CSS function is not enabled or the local MPU is not the master MPU of the CSS.

Service card

LINK: port status indicator

  • Steady green: The port is Up, and cable connection on the port is correct.

  • Blinking green: Cable connection on the port is incorrect.

  • Off: The link status of the port is Down.

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

  1. 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 from a Layer 3 interface using Telnet, STelnet, web, or SNMP.
    NOTE:
    • 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.

  2. 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.

    <Quidway> display device
    Chassis 1 (Master Switch)                                                       
    S9306's Device status:                                                          
    Slot  Sub Type         Online    Power      Register       Status     Role   
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -   
    1     -   LE0DX12XSA00 Present   PowerOn    Registered     Normal     NA        
    2     -   LE0DX12XSA00 Present   PowerOn    Registered     Normal     NA        
    3     -   -            Present   PowerOn    Unregistered   -          NA        
    7     -   LE0D00SRUB00 Present   PowerOn    Registered     Normal     Master    
    8     -   LE0D00SRUB00 Present   PowerOn    Registered     Normal     Slave     
    PWR1  -   -            Present   PowerOn    Registered     Normal     NA        
    CMU1  -   LE0DCMUA0000 Present   PowerOn    Registered     Normal     Master    
    FAN1  -   -            Present   PowerOn    Registered     Normal     NA        
    FAN2  -   -            Present   PowerOn    Registered     Normal     NA        
    Chassis 2 (Standby Switch)                                                      
    S9306's Device status:                                                          
    Slot  Sub Type         Online    Power      Register       Status     Role   
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -   
    1     -   LE0DX12XSA00 Present   PowerOn    Registered     Normal     NA        
    2     -   LE0DX12XSA00 Present   PowerOn    Registered     Normal     NA        
    3     -   LE0DX40SFC00 Present   PowerOn    Registered     Normal     NA        
    5     -   -            Present   PowerOff   Unregistered   -          NA        
    6     -   LE0DX12XSA00 Present   PowerOn    Registered     Normal     NA        
    7     -   LE0D00SRUB00 Present   PowerOn    Registered     Normal     Master    
    8     -   LE0D00SRUB00 Present   PowerOn    Registered     Normal     Slave     
    PWR1  -   -            Present   PowerOn    Registered     Normal     NA        
    CMU2  -   LE0DCMUA0000 Present   PowerOn    Registered     Normal     Master     
    FAN1  -   -            Present   PowerOn    Registered     Normal     NA        
    FAN2  -   -            Present   PowerOn    Registered     Normal     NA        

    Alternatively, 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.

    <Quidway> 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           

  3. Check whether the CSS link topology is the same as the actual hardware connection.

    Run the display css channel all command to check whether the CSS link connections are the same as the actual hardware connections. The following is an example of the display css channel all command output.

    <Quidway> 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 CSS link connections are the same as the actual hardware connections, all the CSS links are running normally and a CSS is established successfully.
    • If some CSS links are not displayed, run the display css css-port all command to check the status of all CSS ports.
    <Quidway> 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 CSS 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 CSS 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 connections 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 3-13 describes how to rectify a fault according to the alarm message.

    Table 3-13  Rectifying a fault according to the alarm message

    Error 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.
Translation
Download
Updated: 2018-09-03

Document ID: EDOC1100038289

Views: 39327

Downloads: 15

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