configuration guide - device management(v100r006c01_01)

8/10/2019 Configuration Guide - Device Management(V100R006C01_01)

1/262

Quidway S9300 Terabit Routing Switch

V100R006C01

Configuration Guide - Device

Management

Issue 01

Date 2011-10-26

HUAWEI TECHNOLOGIES CO., LTD.


2/262

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the

customer. All or part of the products, services and features described in this document may not be within the

purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representations

of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 01 (2011-10-26) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


3/262

About This Document

Intended Audience

This document provides the basic concepts, configuration procedures, and configuration

examples in different application scenarios of the device management feature supported by the

S9300.

This document describes how to configure the device management feature.

This document is intended for:

l Data configuration engineers

l Commissioning engineers

l Network monitoring engineers

l System maintenance engineers

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

DANGER

Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

CAUTION

Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,

performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save

time.

NOTE Provides additional information to emphasize or supplement

important points of the main text.


Configuration Guide - Device Management About This Document



ii


4/262

Command Conventions

The command conventions that may be found in this document are defined as follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of all

items can be selected.

[x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

& The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.

Change History

Updates between document issues are cumulative. Therefore, the latest document issue contains

all changes made in previous issues.

Changes in Issue 01 (2011-10-26)

Initial commercial release.


Configuration Guide - Device Management About This Document



iii


5/262

Contents

About This Document.....................................................................................................................ii

1 NAP Configuration.......................................................................................................................1

1.1 NAP Overview...................................................................................................................................................2

1.2 Configuring NAP-based Remote Deployment...................................................................................................21.2.1 Establishing the Configuration Task.........................................................................................................2

1.2.2 Configuring and Starting the NAP Master Interface.................................................................................3

1.2.3 Remote Login............................................................................................................................................5

1.2.4 Disabling NAP on the Slave Device..........................................................................................................6

1.2.5 Checking the Configuration.......................................................................................................................6

1.3 ConfigurationExamples.....................................................................................................................................7

1.3.1 Examplefor Configuring NAP-based Remote Deployment in Static Mode.............................................8

1.3.2 Examplefor Configuring NAP-based Remote Deployment in Automatic Mode.....................................9

2 CSS Configuration......................................................................................................................122.1 CSS Overview..................................................................................................................................................13

2.2 CSS Features Supported by the S9300.............................................................................................................13

2.3 Configuring the CCS Function.........................................................................................................................16

2.3.1 Establishing the Configuration Task.......................................................................................................17

2.3.2 Configuring Frame ID or Priority of the S9300......................................................................................18

2.3.3 (Optional) Specifying the Master Switch................................................................................................18

2.3.4 Enabling the CSS Function......................................................................................................................19

2.3.5 Checking the Configuration.....................................................................................................................20

2.4 ConfigurationExamples...................................................................................................................................20

2.4.1 Examplefor Configuring a CSS..............................................................................................................20

3 Displaying the Device Status....................................................................................................23

3.1 Display Commands...........................................................................................................................................24

3.2 Displaying the Status of the S9300...................................................................................................................24

3.2.1 Displaying Information About the S9300...............................................................................................24

3.2.2 Displaying the Version............................................................................................................................25

3.2.3 Displaying the Power Status of the S9300..............................................................................................25

3.2.4 Displaying the Board Voltage.................................................................................................................26

3.2.5 Displaying the Temperature....................................................................................................................26

3.2.6 Displaying the Fan Status........................................................................................................................27


Configuration Guide - Device Management Contents



iv


6/262


7/262

5.1 Introduction to the Information Center.............................................................................................................52

5.2 Information Center Supported by the S9300....................................................................................................52

5.3 Enabling Log Output........................................................................................................................................58


5.3.2 Enabling the Information Center.............................................................................................................58

5.3.3 (Optional) Naming an Information Channel...........................................................................................59

5.3.4 (Optional) Configuring the Function of Filtering Logs by IDs...............................................................59

5.3.5 (Optional) Configuring the Function of Generating a Data Dictionary..................................................60

5.3.6 Outputting Logs to the Log Buffer..........................................................................................................60

5.3.7 Outputting Logs to a Log File.................................................................................................................61

5.3.8 Outputting Logs to the Console...............................................................................................................62

5.3.9 Outputting Logs to the Terminal.............................................................................................................62

5.3.10 Outputting Logs to the Log Host...........................................................................................................63

5.3.11 Checking the Configuration...................................................................................................................64

5.4 Enabling Alarm Output....................................................................................................................................66



5.4.3 (Optional) Naming the Information Channel..........................................................................................67

5.4.4 Outputting Alarms to the Alarm Buffer..................................................................................................68

5.4.5 Outputting Alarms to the Log File..........................................................................................................69

5.4.6 Outputting Alarms to the Console...........................................................................................................69

5.4.7 Outputting Alarms to the Terminal.........................................................................................................70

5.4.8 Outputting Alarms to the SNMP Agent..................................................................................................715.4.9 Checking the Configuration.....................................................................................................................72

5.5 Enabling the Output of Debugging Information...............................................................................................73



5.5.3 (Optional) Naming the Information Channel..........................................................................................75

5.5.4 Outputting Debugging Information to the Log File................................................................................75

5.5.5 Outputting Debugging Information to the Console.................................................................................76

5.5.6 Outputting Debugging Information to the Terminal...............................................................................77

5.5.7 Outputting Debugging Information to the Log Host...............................................................................78

5.5.8 Checking the Configuration.....................................................................................................................79

5.6 Maintaining Information Center.......................................................................................................................80

5.7 Information Center configuration Examples....................................................................................................80

5.7.1 Examplefor Outputting Logs to the Log File.........................................................................................80

5.7.2 Examplefor Outputting Logs to Log Hosts............................................................................................82

5.7.3 Examplefor Configuring Log Messages to be Output to the Log Host on the Public Network when the

Management VPN Instance Is used..................................................................................................................86

5.7.4 Example for Configuring Binary Logs to be sent to the Log Host..........................................................89

5.7.5 Example for Outputting Alarms to the SNMP Agent..............................................................................91

5.7.6 Example for Outputting the Debugging Information to the Console......................................................94





vi


8/262

6 Mirroring Configuration............................................................................................................96

6.1 Introduction to Mirroring..................................................................................................................................97

6.2 Mirroring Features Supported by the S9300....................................................................................................97

6.3 Configuring Local Port Mirroring....................................................................................................................99

6.3.1 Establishing the Configuration Task.....................................................................................................100

6.3.2 Configuring a Local Observing Port.....................................................................................................100

6.3.3 Configuring a Local Mirrored Port........................................................................................................101


6.4 Configuring Remote Port Mirroring...............................................................................................................101

6.4.1 Establishing the Configuration Task................................................................ .....................................102

6.4.2 Configuring a Remote Observing Port..................................................................................................102

6.4.3 Configuring a Remote Mirrored Port....................................................................................................103


6.5 Configuring Traffic Mirroring........................................................................................................................104


6.5.2 Configuring an Observing Port..............................................................................................................104

6.5.3 Configuring Complex Traffic Classification.........................................................................................105

6.5.4 Creatinga Traffic Behavior...................................................................................................................105

6.5.5 Creating a Traffic Policy.......................................................................................................................106

6.5.6 Applying a Traffic Policy......................................................................................................................106


6.6 Configuration Examples.................................................................................................................................108

6.6.1 Example for Configuring Local Port Mirroring....................................................................................108

6.6.2 Examplefor Configuring Layer 2 Remote Port Mirroring....................................................................112

6.6.3 Examplefor Configuring Traffic Mirroring..........................................................................................114

7 PoE Power Supply Configuration..........................................................................................120

7.1 PoE Overview.................................................................................................................................................121

7.2 PoE Features Supported by the S9300...........................................................................................................121

7.3 Configuring PoE Functions............................................................................................................................121


7.3.2 Configuring the PoE Function Globally................................................................................................122

7.3.3 Configuring the PoE Function on an Interface......................................................................................124



8 ALS Configuration....................................................................................................................133

8.1 ALS Overview................................................................................................................................................134

8.2 ALS FeaturesSupported by the S9300...........................................................................................................134

8.3 Configuring ALS............................................................................................................................................135

8.3.1 Establishing the Configuration Task................................................................ .....................................135

8.3.2 Enabling ALS on an Interface...............................................................................................................136

8.3.3 (Optional) Setting the Restart Mode of the Laser..................................................................................137

8.3.4 (Optional) Starting the Laser Manually.................................................................................................137





vii


9/262

8.3.5 (Optional) Setting the ALS Pulse Interval and Width of the Laser.......................................................138



8.4.1 Example for Configuring ALS..............................................................................................................139

9 Rebooting....................................................................................................................................142

9.1 Process of Booting the S9300.........................................................................................................................143

9.2 Process of Booting the BootROM..................................................................................................................144

9.3 Process ofBooting the System Software........................................................................................................145

9.4 Rebooting the S9300......................................................................................................................................146


9.4.2 (Optional) Rebooting the S9300 Through Command Lines.................................................................146

9.4.3 (Optional) Rebooting the S9300 Immediately by Pressing the Power Button......................................147

9.4.4 (Optional) Rebooting the S9300 on Schedule Using Command Lines.................................................147


10 ISSU Configuration.................................................................................................................149

10.1 Introduction to ISSU.....................................................................................................................................150

10.2 ISSU Supported by the S9300......................................................................................................................150

10.3 Implementing ISSU......................................................................................................................................151

10.3.1 Establishing the Configuration Task...................................................................................................151

10.3.2 (Optional) Configuring ISSU Precheck...............................................................................................151

10.3.3 (Optional) Configuring the Length of the ISSU Rollback Timer........................................................152

10.3.4 Implementing ISSU.............................................................................................................................152

10.3.5 Checking the Configuration.................................................................................................................156

10.4 Maintaining ISSU.........................................................................................................................................159

10.4.1 Monitoring the Running Status of ISSU..............................................................................................159

10.5 Configuration Examples...............................................................................................................................159

10.5.1 Example for Implementing ISSU........................................................................................................159

11 Ethernet Clock Syntonization Configuration....................................................................163

11.1 Overviewof Ethernet Clock Syntonization..................................................................................................164

11.2 Ethernet Clock Syntonization Features Supported by the S9300.................................................................164

11.3 Forcibly Specifying a Reference Clock Source............................................................................................16611.3.1 Establishing the Configuration Task...................................................................................................166

11.3.2 Forcibly Specifying a Reference Clock Source for the Main Control Board......................................167


11.4 Manually Specifying a Reference Clock Source..........................................................................................169


11.4.2 Manually Specifying a Reference Clock Source for the Main Control Board....................................170


11.5 Selectinga Clock Source Based on the Priority...........................................................................................171


11.5.2 Setting the Priority of a Clock Source.................................................................................................172





viii


10/262


11.6 Selecting the Clock Source Based on the SSM Quality Level.....................................................................174


11.6.2 Enabling the SSM Quality Level to Be Used in Clock Source Selection...........................................175

11.6.3 (Optional) Setting the SSM Quality Level of a Clock Source............................................................175

11.6.4 (Optional) Preventing Timing Loops Between BITS Interfaces.........................................................177


11.7 (Optional) Configuring Other Attributes of a Clock Source........................................................................177


11.7.2 SettingClock Mode or Time Mode of a BITS Clock..........................................................................179

11.7.3 Settingthe ID of a Clock Source.........................................................................................................179

11.7.4 Configuring Attributes of the S1 Byte.................................................................................................180

11.7.5 Setting the Priority of the Clock Signal That an Interface Sends to the Clock Board.........................181

11.7.6 Locking a Clock Source......................................................................................................................182

11.7.7 Configuring Frequency Offset Check..................................................................................................182

11.7.8 Settingthe Delay Time for the System to Consider a Clock Source Lost...........................................183

11.7.9 Settingthe WTR Time of a Clock Source...........................................................................................183

11.7.10 Enable the Permanent Holding Mode of the Clock Module.............................................................184

11.7.11 Configuring the Non-Retrieve Mode of the Clock Source................................................................184

11.7.12 Checking the Configuration...............................................................................................................185

11.8 Configuration Examples...............................................................................................................................186

11.8.1 Example for Selecting the Clock Source Based on the Priority..........................................................186

11.8.2 Example for Selecting the Clock Source Based on the SSM Quality Level.......................................19111.8.3 Example for Selecting the Clock Source Based on the SSM Quality Level in Extended Mode.........196

12 PTP Configuration...................................................................................................................203

12.1 PTP Overview...............................................................................................................................................204

12.2 PTP Feature Supported by the S9300...........................................................................................................208

12.3 Configuring PTP for an OC..........................................................................................................................210


12.3.2 Configuring PTP Globally...................................................................................................................211

12.3.3 Configuring PTP for an Interface........................................................................................................212

12.3.4 Configuring Time Attributes for PTP Packets....................................................................................21312.3.5 Configuring Encapsulation Types for PTP Packets............................................................................214


12.4 Configuring PTP for a BC............................................................................................................................217




12.4.4 Configuring Time Attributes for PTP Packets....................................................................................220

12.4.5 Configuring Encapsulation Types for PTP Packets............................................................................220


12.5 Configuring PTP for a TC............................................................................................................................223





ix


11/262







12.6 Configuring PTP for a TCandBC.................................................................................................................229







12.7 Configuring the PTP Clock Source..............................................................................................................236


12.7.2 Configuring BITS Signals to Participate in the BMC Calculation......................................................237

12.7.3 Configuring Attributes for the PTP Clock Source...............................................................................237


12.8 Maintaining PTP...........................................................................................................................................238

12.8.1 Clearing PTP Statistics........................................................................................................................238

12.8.2 Monitoring PTP...................................................................................................................................238

12.8.3 Debugging PTP....................................................................................................................................239

12.9 Configuration Examples...............................................................................................................................23912.9.1 Example for Configuring the BITS as the PTP Master Clock Source................................................239

12.9.2 Example for Configuring Clock Synchronization Through Unicast UDP-Encapsulation 1588v2 Packets

in Pdelay Mechanism......................................................................................................................................242

12.9.3 Example for Configuring Clock Synchronization Through Multicast MAC-Encapsulation 1588v2

Packets in Delay Mechanism..........................................................................................................................247





x


12/262

1NAP ConfigurationAbout This Chapter

This chapter describes how to configure the Neighbor Access Protocol (NAP) on the S9300.

1.1 NAP Overview

NAP is a Huawei proprietary protocol that implements remote configuration and deployment of

unconfigured devices. You can log in to an unconfigured device from a directly connected device

and configure the unconfigured device remotely through NAP.

1.2 Configuring NAP-based Remote Deployment

Using NAP, you can remotely log in to devices with empty configurations to implement remote

deployment.

1.3 Configuration Examples

This sectionprovides upgrade and maintenance examples together with the configuration

flowchart. The configuration examples explain networking requirements, configuration notes,

and configuration roadmap.


Configuration Guide - Device Management 1 NAP Configuration



1


13/262

1.1 NAP Overview

NAP is a Huawei proprietary protocol that implements remote configuration and deployment of

unconfigured devices. You can log in to an unconfigured device from a directly connected device

and configure the unconfigured device remotely through NAP.

Usually, a device is installed with only necessary software before delivery and no configuration

is made. Therefore, engineers must configure and commission new devices on site but cannot

log in to the devices remotely. This makes the deployment inconvenient and increases the costs

of project operation and delivery.

The Huawei Group Management Protocol (HGMP) implements remote configuration on Layer

2 networks and is applicable to Ethernet networks. NAP implements remote configuration on

Layer 3 networks. It establishes a temporary neighbor relationship between a configured device

and an unconfigured device that are directly connected through physical links. Then you can log

in to the unconfigured device from the configured device and configure the unconfigured device

remotely. NAP greatly reduces the costs of network operation, maintenance, and delivery.

1.2 Configuring NAP-based Remote Deployment

Using NAP, you can remotely log in to devices with empty configurations to implement remote

deployment.

Context

CAUTION

After the device with an empty configuration is powered on and started, you must make sure

that its interfaces connected to the devices on the current network are Up and support NAP;

otherwise, the function of NAP-based remote deployment cannot take effect.

1.2.1 Establishing the Configuration Task

Before configuring NAP-based remote deployment, familiarize yourself with the applicableenvironment, complete the pre-configuration tasks, and obtain the required data. This can help

you complete the configuration task quickly and accurately.

Applicable Environment

To deploy devices having empty configurations, you can use NAP to perform remote login to

the devices from a device in the current network. In this manner, you can implement remote

deployment of devices.

Pre-configuration Tasks

Before configuring NAP-based remote deployment, complete the following tasks:





2


14/262

l Connecting the device having an empty configuration to a device in the current network

via a single hop by using network cables

l Ensuring that the interfaces connecting the device with an empty configuration and the

device in the current network are both in the Up state, and support NAP.

Data Preparation

NOTE

l If the IP addresses used for establishing NAP connections are to be manually configured, you need to

prepare the following data before configuring NAP.

l Conversely, if the IP addresses for establishing NAP connections are to be automatically configured,

you can skip this.

To configure NAP-based remote deployment, you need the following data.

No. Data

1 Two primary IP addresses. The two IP addresses are primary IP addresses for the

master interface and the slave interface respectively, and should be on the same

network segment.

2 Two secondary IP addresses. The two IP addresses are secondary IP addresses for

the master interface and the slave interface respectively, and should be on the same

network segment.

1.2.2 Configuring and Starting the NAP Master Interface

You can assign an IP address to the NAP master interface or use the IP address that is

automatically allocated by the system to start the NAP master interface.

Context

CAUTION

If commands affecting the IP address configuration or IP packet forwarding (such as

configurations and commands related to the VPN, Eth-Trunk, or Layer 2 interface) exist ondevice of the master interface, NAP enabled on the master interface becomes unavailable. You

are recommended to delete these commands and re-enable NAP.

Do as follows on the switch to configure and start the NAP master interface.

In NAP, IP addresses can be allocated either automatically or manually.

Procedure

l Automatic allocation of IP addresses

1. Run:system-view





3


15/262

The system view is displayed.

2. Run:

interfaceinterface-typeinterface-number

The interface view is displayed.

3. Run:

nap port master

The NAP Master interface is configured and started.

l Manual IP address allocation

Two methods are available for manually allocating IP addresses. You can choose the

method according to actual needs.

You can specify the NAP IP address pool. Then, IP addresses are automatically allocated

to the IP address pool. To use this method, do as follows.

1. Run:

system-view


2. Run:

nap ip-poolip-addressmask-length

An IP address pool is configured for NAP.

The default IP address pool for establishing NAP connections is 10.167.253.0/24. You

can run the nap ip-poolip-address mask-lengthcommand to change the IP address

pool.

NOTE

After NAP is started on the master device, the IP address pool cannot be changed.

3. Run:



4. Run:

nap port master

The NAP Master interface is configured and started.

You can also specify the NAP IP addresses. To use this method, do as follows.

1. Run:

system-view


2. Run:



3. Run:

nap port master

The NAP master interface is configured and started.

4. Run:

nap local-ipmast-inter-mast-ipsub-ipmast-inter-sub-ippeer-ipsub-inter-mast-ipsub-ipsub-inter-sub-ipmask-length





4


16/262

IP addresses are configured for establishing NAP connections.

The default IP address pool for establishing NAP connections is 10.167.253.0/24.

When configuring IP addresses, ensure that the primary IP addresses of both the master

and the slave interfaces are on the same network segment, and that the secondary IPaddresses of both the master and the slave interfaces are on the same network segment.

----End

1.2.3 Remote Login

After the neighbor relationship is set up, you can log in to the NAP slave device from the NAP

master device.

Context

Using the display napinterfacecommand, you can view the NAP status of an interface to

ensure that the interface is assigned a correct IP address.

Do as follows on the switch where the NAP master interface is configured.

Procedure

Step 1 Run:

system-view


Step 2 Run:interfaceinterface-typeinterface-number


Step 3 Run:

nap login neighbor

The login to the slave device from the master device is performed.

l If the slave device has an empty configuration, you can log in to the slave device from the

master device without a user name and a password.

lIf, however, the slave device is configured with user name(s) and password(s), you mustenter the correct user name and password to perform a NAP-based remote login to the slave

device.

NOTE

To ensure security for NAP, the slave device having an empty configuration checks the source address of

the Telnet login. If the Telnet source address is the NAP address of the master device that is telnetting to

the slave device, the slave device allows the master device to directly log in without being authenticated.

This is because by default, the user level of the remote login based on the NAP address is the same as the

login through the console interface, which enjoys the highest user level. If the Telnet source address is not

the NAP address of the master device, the remote login fails.

If ip source check user-bind enablecommand is executed on an interface, the interface cannot connect

to the NAP neighbor.

----End





5


17/262

1.2.4 Disabling NAP on the Slave Device

If the NAP function is no longer required, you need to disable NAP on the slave interface of the

slave device.

Context

The master device has logged in to the slave device through Telnet. The NAP function is no

longer required, and to ensure security of the network, NAP should be globally disabled on the

slave interface of the slave device.

Do as follows on the switch that is configured as the NAP slave device.

Procedure

Step 1 Run:

system-view


Step 2 Run:undo nap slave enable

NAP is disabled on the slave device.

----End

1.2.5 Checking the Configuration

After configuring NAP-based remote deployment, you can view the NAP status globally or ona specified interface.

Prerequisite

NAP-based remote deployment has been completed.

Procedure

Step 1 Using the display napstatuscommand, you can view the current NAP status.

Step 2 Using the display napinterface[ interface-typeinterface-number] command, you can viewthe NAP status of the specified interface.

----End

Example

Run the display napstatuscommand to view the current NAP status.

display nap statusSlave port status : Enable

Nap ip-pool/Mask : 12.12.12.0/24

Run the display napinterfaceinterface-typeinterface-numbercommand to view the NAP status

of the specified interface.

display nap interface gigabitethernet1/0/1





6


18/262

l If the interface is not assigned an IP address, the following information is displayed.

------------------------------------------------------

NAP master port list:

Port count : 2

------------------------------------------------------

Port property : MasterCurrent status : DETECTING

Local port : GigabitEthernet1/0/1

Peer port : GigabitEthernet1/0/1Local primary ip :NULLPeer primary ip :NULL

Local secondary ip :NULL

Peer secondary ip :NULLHello time : 3s

Linked time : 00:00:00

------------------------------------------------------Port property : Master

Current status : DETECTING


Peer port : GigabitEthernet1/0/2Local primary ip :NULL

Peer primary ip :NULLLocal secondary ip :NULL

Peer secondary ip :NULLHello time : 3s

Linked time : 00:00:00

------------------------------------------------------

l If the interface is assigned an IP address, the following information is displayed.

------------------------------------------------------

NAP master port list :

Port count : 2------------------------------------------------------

Port property : Master

Current status : IP-ASSIGNED


Peer port : GigabitEthernet1/0/1Local primary ip : 12.12.12.5

Peer primary ip : 12.12.12.6Local secondary ip : 12.12.12.9Peer secondary ip : 12.12.12.10

Hello time : 3s

Linked time : 00:09:12------------------------------------------------------


Current status : IP-ASSIGNED

Local port : GigabitEthernet1/0/2Peer port : GigabitEthernet1/0/2

Local primary ip : 10.10.10.5

Peer primary ip : 10.10.10.6Local secondary ip : 10.10.10.9Peer secondary ip : 10.10.10.10

Hello time : 3sLinked time : 00:03:41------------------------------------------------------


This section provides upgrade and maintenance examples together with the configuration

flowchart. The configuration examples explain networking requirements, configuration notes,

and configuration roadmap.





7


19/262

1.3.1 Example for Configuring NAP-based Remote Deployment inStatic Mode

In this example, the temporary neighbor relationship is set up between the switch and the device

with the empty configuration and IP addresses are assigned to the switch and the device toimplement remote deployment in manual mode.

Networking Requirements

As shown in Figure 1-1, the user needs to perform a remote login to Switch B from Switch A.

Switch B is the master device, and temporary neighbor relationship is to be set up between

Switch B and Switch C having an empty configuration. Switch B and Switch C need to be directly

connected via a single hop. Both the interfaces connecting Switch B and Switch C should be in

the Up state, and should support NAP.

Figure 1-1Networking diagram of NAP-based remote deployment

Network

SwitchAPC SwitchB SwitchC

Configuration Roadmap

The configuration roadmap is as follows:

1. Configure a NAP master interface on Switch B.

2. Configure an IP address for establishing a NAP connection on Switch B.

3. Use NAP to log in to Switch C from Switch B by means of Telnet.

Data Preparation

To complete the configuration, you need the following data:

l Two primary IP addresses. The two IP addresses are primary IP addresses for the master

interface and the slave interface respectively, and should be on the same network segment.

l Two secondary IP addresses. The two IP addresses are secondary IP addresses for the

master interface and the slave interface respectively, and should be on the same network

segment.

Procedure

Step 1 Configure a NAP master interface on Switch Bsystem-view

[Quidway]sysname SwitchB

[SwitchB]interface gigabitethernet1/0/1[SwitchB-GigabitEthernet1/0/1]nap port master

Step 2 Configure an IP address for establishing a NAP connection on Switch B





8


20/262

[SwitchB-GigabitEthernet1/0/1]nap local-ip 12.12.12.5 sub-ip 12.12.12.9 peer-ip

12.12.12.6 sub-ip 12.12.12.10 30

Are you sure to continue?[Y/N]y

# After the preceding configuration is complete, run the display nap statuscommand on

Switch B. You can view that NAP has been enabled on Switch B. Then, run the display nap

interfacecommand. You can view that the primary and secondary IP addresses have been

assigned to the master and slave interfaces. For example:

[SwitchB-GigabitEthernet1/0/1]display nap status

Slave port status : EnableNap ip-pool/Mask : 10.167.253.0/24

[SwitchB-GigabitEthernet1/0/1]display nap interface------------------------------------------------------

NAP master port listPort count : 1

------------------------------------------------------


Current status : IP-ASSIGNEDLocal port : GigabitEthernet1/0/1

Peer port : GigabitEthernet1/0/1

Local primary ip : 12.12.12.5Peer primary ip : 12.12.12.6Local secondary ip : 12.12.12.9

Peer secondary ip : 12.12.12.10

Hello time : 3sLinked time : 00:02:33

------------------------------------------------------

Step 3 Log in to the slave device from the master device.

# Configure Switch B.

[SwitchB-GigabitEthernet1/0/1]nap login neighborTrying 12.12.12.10 ...

Press CTRL+K to abort

Connected to 12.12.12.10 ...

Info: The max number of VTY users is 10, and the number

of current VTY users on line is 1.

Step 4 Disable NAP on the slave device.

# Configure Switch C.

system-view[Quidway]sysname SwitchC

[SwitchC]undo nap slave enable

----End

Configuration FilesNone

1.3.2 Example for Configuring NAP-based Remote Deployment inAutomatic Mode

In this example, the temporary neighbor relationship is set up between a switch and another

switch that has the empty configuration to implement remote deployment in automatic mode.


As shown in Figure 1-2, the user needs to perform a remote login to Switch B from Switch A.Switch B is the master device, and temporary neighbor relationship is to be set up between





9


21/262

Switch B and Switch C having an empty configuration. Switch B and Switch C need to be directly

connected via a single hop. Both the interfaces connecting Switch B and Switch C should be in

the Up state, and should support NAP.

Figure 1-2Networking diagram of NAP-based remote deployment

Network

SwitchAPC SwitchB SwitchC



1. Configure a primary IP address and a secondary IP address on Switch B.

2. Configure a NAP master interface on Switch B.

3. Telnet to Switch C from Switch B by means of NAP.

Data Preparation

None

ProcedureStep 1 Configuring the NAP master interface

# Do as follows on Switch B.

system-view[Quidway]sysname SwitchB[SwitchB]interface gigabitethernet1/0/1

[SwitchB-GigabitEthernet1/0/1]nap port master

Step 2 Logging in to the slave device from the master device.

# Do as follows on Switch B.

[SwitchB-GigabitEthernet1/0/1]nap login neighborTrying 10.167.253.10 ...

Press CTRL+K to abortConnected to 10.167.253.10 ...

Info: The max number of VTY users is 10, and the number

of current VTY users on line is 1.

Step 3 Shutting down NAP on the slave device.

# Do as follows on Switch C.

system-view

[Quidway]sysname SwitchC

[SwitchC]undo nap slave enable

----End





10


22/262

Configuration Files

None





11


23/262

2CSS ConfigurationAbout This Chapter

This chapter describes how to configure the cluster switch system (CSS) function on the

S9300.

2.1 CSS Overview

A CSS is also called a stack. In a CSS, two switches are connected through dedicated stacking

cables to form a logical switch.

2.2 CSS Features Supported by the S9300

This section describes the CSS features supported by the S9300.

2.3 Configuring the CCS Function

This section describes how to configure the CSSfunction on the S9300.


This sectionprovides a CSS configuration example.


Configuration Guide - Device Management 2 CSS Configuration



12


24/262

2.1 CSS Overview

A CSS is also called a stack. In a CSS, two switches are connected through dedicated stackingcables to form a logical switch.

A single switch cannot meet requirements of the increasing access volume of a data center and

network reliability. To meet the forwarding requirement of the data center and improve network

reliability, the CSS technology is used.

After two switches set up a CSS, one switch functions as the master switch, and the other

functions as the backup switch.

2.2 CSS Features Supported by the S9300

This section describes the CSS features supported by the S9300.

NOTE

CSS cannot be configured on the Web NMS.

Prerequisites for Setting Up a CSS

A CSS can be set up when the following conditions are met:

l The switches support the CSS feature. (Currently, the S9306 and the S9312 support the

CSS feature.) An S9306 and an S9312 can form a CSS.

l The CSS contains only two switches.

l Both the switches are configured with stacking cards.

l The same type of SRUs (SRUA or SRUB) must be used on each switch.

NOTE

The LE02SRUA VER.A and LE02SRUB VER.A do not support the CSS function.

l The two switches are connected through stacking cables.

l The two switches run normally.

l The CSS function is enabled on the two switches.

lThe two switches use the same software version. If the master switch detects a differentsoftware version on the backup switch, the software of the backup switch is upgraded or

rolled back to the version of the master switch.

Connection of Stacking Cables

Each SRU can be installed with a stacking card and each stacking card provides four interfaces.

When the two S9300s are installed with double SRUs, the eight pairs of interfaces on the stacking

cards are connected through stacking cables, as shown in Figure 2-1. Connect the stacking

interfaces strictly according to Figure 2-1and do not change the connections. Every interface

must be connected to a stacking cable.





13


25/262


26/262

standby SRU of the CSS. HA is implemented between the active and standby SRUs of the CSS.

The standby SRUs of SwitchA and SwitchB function as the candidate standby SRUs of the CSS.

If active/standby switchover is performed on SwitchA or SwitchB, the standby SRU of the switch

becomes the standby SRU of the CSS.

l When active/standby switchover occurs on the master switch (SwitchA): SwitchB becomes the master switch, and the original standby SRU of the CSS becomes

the active SRU of the CSS.

SwitchA becomes the backup switch.

The active SRU of SwitchA restarts. The standby SRU of SwitchA becomes the standby

SRU of the CSS and synchronizes data from the new active SRU of the CSS.

l When active/standby switchover occurs on the backup switch (SwitchB):

The master switch and backup switch remain unchanged.

The active SRU of SwitchB (namely the original standby SRU of the CSS) restarts. The

standby SRU of SwitchB becomes the standby SRU of the CSS and synchronizes data

from the active SRU of the CSS.

Management and Traffic Forwarding in a CSS

After a CSS is set up, you can log in to the CSS through service interfaces on LPUs and the

serial port or console port on the active SRU to configure services and manage the CSS.

In a CSS, the interface view is identified by the frame ID, slot ID, subcard ID, and interface

number. You can specify any interface on the two switches to configure services on the interface.

You can also choose to specify only the frame ID and slot ID to manage the specified LPU, for

example, query information about the LPU or reset the LPU.

Different from the service traffic forwarded on a single switch, the service traffic forwarded

between the two switches of the CSS needs to pass through the switching fabric twice. Similar

to the single switch, the CSS also processes the packet content in both inbound direction and

outbound direction.

CSS Breaking

l Cause of CSS breaking

After a CSS is set up, the active and standby SRUs of the CSS send heartbeat messages to

each other to maintain the CSS status. If a stacking cable, a stacking card, or an SRU is

faulty, communication between the two switches may fail because no stacking link is

available. In this case, the heartbeat between the two switches times out and the CSS breaksinto two independent switches.

l Impact of CSS breaking

If the two switches run normally after the CSS breaks, they use the same IP address and

same MAC address to communicate with other devices on the network because their global

configurations are exactly the same. This causes faults on the entire network and conflict

of IP addresses and MAC addresses. In this case, the system displays a message, asking

you to change the IP address and MAC address of a switch or remove a switch from the

network.

NOTE

When the CSS breaks, the alarm message may be displayed only on the serial port of a switch and cannotbe sent to the NMS because of conflict of IP addresses and MAC addresses.





15


27/262

Backing Up and Restoring Configuration Files

When a device enters the CSS state, it automatically backs up the previous configuration file.

In this way, the device can restore the previous configuration after the CSS function is disabled.

After you enable the CSS function and restart the device immediately, the system generates a

backup configuration file and names it by adding the extension .bakto the previous configuration

file name.

l If the original extension of the configuration file is .cfg, the extension of the backup

configuration file is .cfg.bak.

l If the original extension of the configuration file is .zip, the extension of the backup

configuration file is .zip.bak.

Device status Configuration Files

Non-CSS Current configuration file: s9300.cfg

CSS Current configuration file: s9300.cfg

Backup configuration file: s9300.cfg.bak

If you want to restore the previous configuration after disabling the CSS function, do as follows:

1. Run the renamesource-filenamedestination-filenamecommand to change the name of

the backup configuration file or run the copysource-filenamedestination-filename[ all]

command to copy the backup configuration file and name the copied file.

2. Run the startup saved-configurationconfiguration-filecommand to specify the renamedconfiguration file as the next startup configuration file.

3. Run the undo css enable[ all| frameframe-id] command to disable the CSS function and

restart the device immediately.

NOTE

Automatic configuration file backup prevents configuration loss caused by misoperation. It is

recommended that you save the configuration manually when upgrading the system software and adjusting

the network.

Features Supported in a CSS

All features of the S9300 except the following are supported in a CSS:

l Ethernet clock synchronization

l PTP

l PoE

2.3 Configuring the CCS Function

This section describes how to configure the CSS function on the S9300.





16


28/262

2.3.1 Establishing the Configuration Task

Before configuring the CSS function, familiarize yourself with the applicable environment,

complete the pre-configuration tasks, and obtain the required data. This helps you complete the

configuration task quickly and accurately.

Applicable Environment

As shown in Figure 2-2, SwitchA and SwitchB form a CSS. SwitchC is a user-side device and

is connected to the CSS through Eth-Trunk 1. The CSS is connected to an OSPF network through

Eth-Trunk 2.

By using the trunk technology, you can configure physical Ethernet ports on different switches

as an aggregated port. In this way, if a switch is faulty, the aggregated link still works, and

another switch manages and maintains the other aggregated ports. The device capacity is

improved and the backup between switches is implemented.

Figure 2-2Networking of CSS application

SwitchA SwitchB

SwitchC

PC

OSPF

Eth-Trunk1

Eth-Trunk2

Stacking cable

Common cable

Pre-configuration Tasks

Before configuring the CSS function, complete the following tasks:

l Installing SRUs of the same type (SRUA or SRUB) on each switch

NOTE


l Installing a stacking card on each SRU





17


29/262

l Connecting the two switches through stacking cables

l Ensuring that the two switches run normally

l Ensuring that the two switches use the same software version (If the master switch detects

a different software version on the backup switch, the software of the backup switch is

upgraded or rolled back to the version of the master switch.)

Data Preparation

To configure the CSS function, you need the following data.

No. Data

1 Frame IDs of member switches

Priorities of member switches

2.3.2 Configuring Frame ID or Priority of the S9300

When two switches with different frame IDs set up a CSS, the master switch is elected based

on the running status and priorities of the two switches. Two switches with the same frame ID

cannot set up a CSS.

Context

The switch with a higher priority is more likely to be elected as the master switch.

Procedure

Step 1 Run:system-view


Step 2 Run:set css{ idnew-id|prioritypriority} [ frameframe-id]

The frame ID or priority of the S9300 is configured.

By default, the frame ID of the S9300 in a CSS is 1 and its priority is 1.

The frame IDs of the two switches in a CSS must be 1 and 2; otherwise, the CSS cannot be set

up.

NOTE

The configuration takes effect after the device is restarted.

----End

2.3.3 (Optional) Specifying the Master Switch

Generally, the master switch of a CSS is elected when the CSS is set up. If you want anS9300 to function as the master switch, perform the following operation.





18


30/262

Context

If the specified switch is already the master switch, status of the CSS remains unchanged.

If the specified switch is the backup switch, this switch becomes the master switch after data

backup is complete.

Procedure



Step 2 Run:css master force[ frameframe-id]

The S9300 is specified as the master switch.NOTE


In a CSS, if you do not specify frameframe-idin the command, the command takes effect only on the

master switch.

If the CSS function is disabled, this command takes effect only on the local device.

----End

2.3.4 Enabling the CSS Function

Before configuring the CSS function, you must enable the CSS function.

Context

The constraints on the CSS function are as follows:

l Currently, the S9306 and S9312 support the CSS feature.

l The CSS contains only two switches.

l Each switch must be configured with two SRUs and each SRU must be installed with a

stacking card.

l The SRUs on a switch must be of the same type.

NOTE


l The two switches are connected through stacking cables.

l The two switches must run normally.

l The two switches must use the same software version. If the master switch detects a different

software version on the backup switch, the software of the backup switch is upgraded or

rolled back to the version of the master switch.

Procedure






19


31/262


Step 2 Run:

css enable

The CSS function is enabled.

NOTE


By default, the CSS function is disabled on a device.

----End

2.3.5 Checking the Configuration

After a CSS is set up, you can view the frame ID, priority, and CSS status of each member

switch, and whether the CSS function is enabled.

Prerequisite

CSS configurations of the S9300 are complete.

Procedure

Step 1 Run the display css status[ save] [ all| frameframe-id] command to check the CSSinformation.

----End

Example display css statusProperty Item Property Value

Frame ID 1

Priority 255Enable switch On

CSS master force Off

CSS status master

2.4 Configuration ExamplesThis section provides a CSS configuration example.

2.4.1 Example for Configuring a CSS

You can configure the CSS function to improve the capacity and reliability of devices.


As shown in Figure 2-3, SwitchA and SwitchB form a CSS. SwitchC is a user-side device and

is connected to the CSS through Eth-Trunk 1. The CSS is connected to an OSPF network throughEth-Trunk 2. The CSS improves the capacity and reliability of switches.





20


32/262

Figure 2-3Networking of CSS application

SwitchA SwitchB

SwitchC

PC

OSPF

Eth-Trunk1

Eth-Trunk2

Stacking cable

Common cable



1. Configure the frame IDs and priorities of SwitchA and SwitchB.

2. Enable the CSS function on SwitchA and SwitchB.

Data Preparation

To complete the configuration, you need the following data:

l Frame IDs of member switches

l Priorities of member switches

Procedure

Step 1 Set the priority of SwitchA to 255 and enable the CSS function on SwitchA.

# Set the priority of the local frame to 255.

system-view[Quidway] sysname SwitchA

[SwitchA] set css priority 255Info: CSS config has been changed, need reboot to take effect.

# Enable the CSS function.





21


33/262

[SwitchA] css enable

Reboot needed to change CSS config. Are you sure this operation and reboot now?

[Y/N]y

Step 2 Set the frame ID of SwitchB to 2 and enable the CSS function on SwitchB.

# Set the frame ID to 2.

system-view

[Quidway] sysname SwitchB

[SwitchB] set css id 2Info: CSS config has been changed, need reboot to take effect.

# Enable the CSS function.

[SwitchB] css enableReboot needed to change CSS config. Are you sure this operation and reboot now?

[Y/N]y

Step 3 Verify the configuration.

# Check the CSS status of the switch with frame ID 1. dis css status frame 1Property Item Property Value

Frame ID 1

Priority 255

Enable switch OnCSS master force Off

CSS status master

# Check the CSS status of the switch with frame ID 2.

dis css status frame 2Property Item Property Value

Frame ID 2

Priority 1

Enable switch OnCSS master force Off

CSS status backup

----End

Configuration Files

None.





22


34/262

3Displaying the Device StatusAbout This Chapter

This chapter describes the functions and applications of the displaycommands and how to use

the displaycommands to view the running status of the device.

3.1 Display Commands

This section describes the functions of displaycommands and lists the displaycommands in

common use.

3.2 Displaying the Status of the S9300

This section describes how to use displaycommands to view the version, CPU, memory, and

voltage of a device.


Configuration Guide - Device Management 3 Displaying the Device Status



23


35/262

3.1 Display Commands

This section describes the functions of displaycommands and lists the displaycommands in

common use.

As an important means to maintain and troubleshoot a network, the display commands can be

used to collect current information about the version, device, and diagnosis of the S9300.

Table 3-1lists the displaycommands in common use. For details, see the Quidway S9300

Terabit Routing Switch - Command Reference.

CAUTION

You are disallowed to run the display diagnostic-informationcommand simultaneously onmultiple terminals connected to the S9300. Otherwise, the CPU usage of the S9300 may

obviously rise and the network performance may be degraded.

Table 3-1Common displaycommands

Command Description

display current-configuration Displays the parameters that take effect currently on the

S9300.

display device Displays information about the S9300.

display version Displays the version and boards information of the

S9300.

display this Displays valid configurations in the current view.

display diagnostic-information It is mainly used to collect information about the S9300

when a fault cannot be located or rectified. Then, you can

send the information to Huawei technical personnel for

fault analysis.

NOTEThis command is not recommended for routine troubleshooting.

display this interface Displays the current status of the interface.

3.2 Displaying the Status of the S9300

This section describes how to use displaycommands to view the version, CPU, memory, and

voltage of a device.

3.2.1 Displaying Information About the S9300

You can use the display command to view information about S9300 components.





24


36/262

Procedure

Step 1 Run:display device[ subrack-id/slot-id]

The component type, online status, power status, register status, alarm status, and master/backupstatus are displayed.

You can use the command in any view. The information displayed includes the slot number,

component type, online status, power status, register status, alarm status, and master/backup

status.

----End

3.2.2 Displaying the Version

You can run the command to view information about the software version, chassis type, main

control board version, and LPU version of the S9300.

Context

Do as follows on the S9300.

Procedure

Step 1 Run:display version[ slotslot-id| subrack-id/silkname]

Version information is displayed.

You can run the display versioncommand in any view to view the version of the S9300. You

can specifysubrack-id/silknameto view the version of the board in a specified slot.

This command output includes information about the software version, chassis type, main

control board version, and LPU version.

----End

3.2.3 Displaying the Power Status of the S9300

You can use display commands to view information about the power status and power of the

S9300.

ContextDo as follows on the S9300 whose power status is to be viewed.

Procedure

l Run:

display power

The power status is displayed.

l Run:

display power system

Information about the power is displayed.





25


37/262

You can use the command in any view to view the power status of the S9300. The

information displayed includes the power status, power used by the system (W), and power

used by boards (W).

CAUTION

Before expanding the system capacity, check whether the power supplies of the S9300 can

provide sufficient power after the expansion.

----End

3.2.4 Displaying the Board Voltage

You can use the display command to view the board voltage status, including the current voltage,the upper threshold of the voltage, and the lower threshold of the voltage.

Context

Do as follows on the S9300 whose board voltage is to be viewed.

Procedure

Step 1 Run:

display voltage{ all| slotslot-id}

The board voltage is displayed.

You can use the command in any view to view the board voltage of the S9300.

----End

Example display voltage slot 4

-------------------------------------------------------------------------------Slot Card SDR No. SensorName Status Upper Lower Voltage.(V)

-------------------------------------------------------------------------------

4 - 2 3.3V normal 3.9576 2.6316 3.4680

- 3 2.5V normal 3.0396 2.0808 2.6316 - 4 12V normal 14.4420 9.5700 12.7890

- 5 1.8V normal 2.1624 1.4382 1.8768

- 6 1.1V normal 1.3158 0.8772 1.1424

3.2.5 Displaying the Temperature

You can use the display command to view the board temperature, including the current

temperature, the upper threshold of the temperature, and the lower threshold of the temperature.

Context

Do as follows on the S9300 whose temperature is to be viewed.



configuration guide - device management(v100r006c01_01)

Documents