S2700 V100R006C00 Configuration Guide - Device Management 02

8/20/2019 S2700 V100R006C00 Configuration Guide - Device Management 02

1/138

Configuration Guide - Device

Management

Issue 02

Date 2012-07-20

HUAWEI TECHNOLOGIES CO., LTD.


2/138

Copyright © Huawei Technologies Co., Ltd. 2012. 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 a 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 02 (2012-07-20) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/


3/138

About This Document

Intended Audience

This document describes procedures and provides examples for configuring the Device

Management features of the S2700.

This document guides you through the configuration and applicable environment of the Device

Management features of the S2700.

S2700 includes S2700EI and S2700SI series products. S2700SI does not support the following

features:

l Configuring Interface-based RSPAN

l Configuring Local SPAN Based on MAC Addresses

l Configuring RSPAN Based on MAC Addresses

l Configuring VLAN-based Local SPAN

l Configuring VLAN-based RSPAN

l Configuring Flow-based Local SPAN

l Configuring Flow-based RSPAN

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.

WARNING

Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.

Configuration Guide - Device Management About This Document



ii


4/138

Symbol Description

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.

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 byvertical bars. One item is selected or no item is selected.

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

vertical 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 HistoryUpdates between document issues are cumulative. Therefore, the latest document issue contains

all changes made in previous issues.

Changes in Issue 02 (2012-07-20)

Based on issue 01 (2011-07-15), the document is updated as follows:

The following information is modified:




iii


5/138

l Minor mistakes are rectified.

Changes in Issue 01 (2011-07-15)

Initial commercial release.




iv


6/138

Contents

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

1 Auto-Config....................................................................................................................................1

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

1.2 Auto-Config Features Supported by the S2700..................................................................................................31.3 Deploying Unconfigured Switches (Same Network Segment)..........................................................................6

1.3.1 Establishing the Configuration Task.........................................................................................................6

1.3.2 Configuring the DHCP Server...................................................................................................................7

1.3.3 Configuring the FTP/TFTP Server............................................................................................................8

1.3.4 Checking the Configuration.......................................................................................................................8

1.4 Deploying Unconfigured Switches (Different Network Segments)...................................................................9

1.4.1 Esta blishing the Configuration Task.................................................................... .....................................9

1.4.2 Conf iguring the DHCP Server.................................................................................................................10

1.4.3 Configuring DHCP Relay........................................................................................................................11

1.4.4 Configuring the FTP/TFTP Server..........................................................................................................11

1.4.5 Checking the Configuration.....................................................................................................................11

2 NAP Configuration.....................................................................................................................13

2.1 NAP Overview.................................................................................................................................................14

2.2 Configuring NAP-based Remote Deployment.................................................................................................14

2.2.1 Esta blishing the Configuration Task.................................................................. .....................................14

2.2.2 Configuring and Starting the NAP Master Interface...............................................................................15

2.2.3 Remote Login..........................................................................................................................................17

2.2.4 Disabling NAP on the Slave Device........................................................................................................18


2.3 Configuration Examples...................................................................................................................................19

2.3.1 Example for Configuring NAP-based Remote Deployment in Static Mode...........................................20

2.3.2 Example for Configuring NAP-based Remote Deployment in Automatic Mode...................................21

3 Stacking.........................................................................................................................................24

3.1 Stacking Overview...........................................................................................................................................25

3.2 Stacking Function Supported by the S2700.....................................................................................................25

3.3 Configuring the Stacking Function on the S2700............................................................................................26

3.3.1 Establishing the Configuration Task.......................................................................................................26

3.3.2 Configuring an IP Address Pool for a Stack............................................................................................26

Configuration Guide - Device Management Contents



v


7/138

3.3.3 Enabling the Stacking Function on the S2700.........................................................................................27

3.3.4 (Optional) Logging in to the Slave Switch from the Master Switch.......................................................28



3.4.1 Example for Configuring the Stacking Function.....................................................................................29

4 Using display commands to check the status of the device................................................32

4.1 Introduction......................................................................................................................................................33

4.2 Checking the Status of the S2700.....................................................................................................................33

4.2.1 Checking Information About the S2700..................................................................................................33

4.2.2 Checking the Version of the S2700.........................................................................................................33

4.2.3 Checking the Electronic Labels...............................................................................................................33

4.2.4 Checking Temperature............................................................................................................................34

4.2.5 Checking the Fan Status..........................................................................................................................35

4.2.6 Checking the Power Supply Status..........................................................................................................35

4.2.7 Checking the CPU Usage........................................................................................................................35

4.2.8 Checking the Memory Usage..................................................................................................................35

4.2.9 Checking Alarms.....................................................................................................................................36

4.2.10 Checking the Status of an Interface.......................................................................................................36

5 Hardware Management..............................................................................................................37

5.1 Hardware Management Overview....................................................................................................................38

5.2 Hardware Management Features Supported by the S2700...............................................................................38

5.3 Backing U p the Electronic Label......................................................................................................................38


5.3.2 Backing Up the Electronic Label.............................................................................................................39

5.4 Configuring Electrical Port Sleep.....................................................................................................................39

5.4.1 Esta blishing the Configuration Task.................................................................. .....................................39

5.4.2 Enabling Electrical Port Sleep.................................................................................................................40


6 Monitoring the Device Through the Information Center...................................................41

6.1 Information Center Overview...........................................................................................................................42

6.1.1 Introduction to the Information Center....................................................................................................426.1.2 Information Center Supported by the S2700...........................................................................................42

6.2 Configuring the Information Center.................................................................................................................47


6.2.2 Enabling the Information Center.............................................................................................................48

6.2.3 (Optional) Naming the Information Channel..........................................................................................49

6.2.4 Defining the Information Channel...........................................................................................................49

6.2.5 (Optional) Configuring the Timestamp for the Output Information.......................................................49


6.3 Sending Information to the Information Center...............................................................................................50

6.3.1 Sending Information to the Console........................................................................................................50




vi


8/138

6.3.2 Sending Information to the Telnet Terminal...........................................................................................51

6.3.3 Sending Information to the SNMP Agent...............................................................................................52

6.3.4 Sending Information to the Log Buffer...................................................................................................52

6.3.5 Sending Information to the Trap Buffer..................................................................................................52

6.3.6 Sending Information to the Log Host......................................................................................................53


6.4 Maintaining the Information Center.................................................................................................................53


6.5.1 Example for Configuring the Information Center...................................................................................54

7 Mirroring.......................................................................................................................................57

7.1 Introduction......................................................................................................................................................59

7.1.1 Mirroring Functions.................................................................................................................................59

7.2 Configuring Local Port Mirroring....................................................................................................................62


7.2.2 Conf iguring Local Port Mirroring...........................................................................................................63


7.3 Configuring R emote Port Mirroring.................................................................................................................64


7.3.2 Conf iguring Remote Port Mirroring........................................................................................................65


7.4 Canceling Por t Mirroring..................................................................................................................................68


7.4.2 Canceling Port Mirroring.........................................................................................................................69


7.5 Configuring Local VLAN Mirroring................................................................................................................69


7.5.2 Conf iguring Local VLAN Mirroring.......................................................................................................70


7.6 Configuring R emote VLAN Mirroring............................................................................................................71


7.6.2 Conf iguring Remote VLAN Mirroring...................................................................................................72

7.6.3 Checking the Configuration.....................................................................................................................737.7 Canceling VLAN Mirroring.............................................................................................................................73


7.7.2 Canceling VLAN Mirroring....................................................................................................................74


7.8 Configuring MAC Address-based Local Mirroring.........................................................................................74


7.8.2 Configuring Local SPAN Based on MAC Addresses.............................................................................75


7.9 Configuring RSPAN Based on MAC Addresses.............................................................................................76





vii


9/138

7.9.2 Configuring Remote MAC Address Mirroring.......................................................................................77


7.10 Canceling Mirroring Based on MAC Addresses............................................................................................79

7.10.1 Establishing the Configuration Task.....................................................................................................79

7.10.2 Canceling Mirroring Based on MAC Addresses...................................................................................79

7.10.3 Checking the Configuration...................................................................................................................79

7.11 Configuring Local Flow Mirroring.................................................................................................................80


7.11.2 Configuring Traffic Classification Rules..............................................................................................80

7.11.3 Configuring Flow Mirroring..................................................................................................................81

7.11.4 Creating and Applying a Traffic Policy................................................................................................81


7.12 Configuring Remote Flow Mirroring.............................................................................................................83


7.12.2 Setting Traffic Classification Rules.......................................................................................................83

7.12.3 Configuring Remote Flow Mirroring....................................................................................................83

7.12.4 Creating and Applying a Traffic Policy................................................................................................85


7.13 Canceling Flow Mirroring..............................................................................................................................86


7.13.2 Canceling Flow Mirroring.....................................................................................................................86


7.14 Changing or Deleting an Observing Port.......................................................................................................877.14.1 Establishing the Configuration Task.....................................................................................................87

7.14.2 (Optional) Deleting an Observing Port..................................................................................................88

7.14.3 (Optional) Changing an Observing Port................................................................................................89


7.15 Configuring CPU Mirroring...........................................................................................................................89


7.15.2 (Optional) Configuring an ACL Rule....................................................................................................90

7.15.3 Configuring an Observing Port..............................................................................................................90

7.15.4 Configuring CPU Mirroring..................................................................................................................91


7.16 Cancelling CPU Mirroring.............................................................................................................................91


7.16.2 Cancelling CPU Mirroring....................................................................................................................92


7.17 Configuration Examples.................................................................................................................................92

7.17.1 Example for Configuring Local Port Mirroring....................................................................................92

7.17.2 Example for Configuring Local VLAN Mirroring................................................................................94

7.17.3 Example for Configuring MAC Address-based Local Mirroring.........................................................96

7.17.4 Example for Configuring Local Flow Mirroring...................................................................................98




viii


10/138

7.17.5 Example for Configuring Remote Port Mirroring...............................................................................101

7.17.6 Example for Changing an Observing Port...........................................................................................103

8 PoE Configuration.....................................................................................................................106

8.1 PoE Overview.................................................................................................................................................1078.2 PoE Features Supported by the S2700...........................................................................................................107

8.3 Configuring PoE Functions............................................................................................................................107


8.3.2 Configuring the PoE Function Globally................................................................................................108

8.3.3 Configuring the PoE Function on an Interface......................................................................................110



8.4.1 Example for Configuring PoE on the Switch........................................................................................112

9 ALS Configuration....................................................................................................................1159.1 ALS Over view................................................................................................................................................116

9.2 ALS Features Supported by the S2700...........................................................................................................116

9.3 Configuring ALS............................................................................................................................................117

9.3.1 Esta blishing the Configuration Task................................................................................ .....................117

9.3.2 Enabling ALS on an Interface...............................................................................................................118

9.3.3 (Optional) Setting the Restart Mode of the Laser..................................................................................119

9.3.4 (Optional) Starting the Laser Manually.................................................................................................119

9.3.5 (Optional) Setting the ALS Pulse Interval and Width of the Laser.......................................................120



9.4.1 Example for Configuring ALS..............................................................................................................121

10 Restarting and Resetting........................................................................................................124

10.1 Introduction..................................................................................................................................................125

10.1.1 Process of Starting the S2700..............................................................................................................125

10.1.2 Process of Starting the BootROM.......................................................................................................125

10.2 Restarting the S2700 Immediately...............................................................................................................126

10.2.1 Restarting the S2700 Immediately Through Command Lines............................................................127

10.2.2 Restarting the S2700 by Pressing the Power Button on the S2700.....................................................12710.3 Restarting the S2700 at a Fixed Time..........................................................................................................127




ix


11/138

1 Auto-Config About This Chapter

This chapter describes the concept, working mechanism, and deployment of Auto-Config.

1.1 Overview

This section describes the functions, application scenarios, and terms of Auto-Config.

1.2 Auto-Config Features Supported by the S2700

This section describes how Auto-Config runs on the S2700.

1.3 Deploying Unconfigured Switches (Same Network Segment)

This section describes how to deploy S2700s without configuration file.

1.4 Deploying Unconfigured Switches (Different Network Segments)

This section describes how to deploy unconfigured S2700s.

Configuration Guide - Device Management 1 Auto-Config



1


12/138

1.1 Overview

This section describes the functions, application scenarios, and terms of Auto-Config.

When a new switch or a switch without any configuration file is powered on, Auto-Config runs

automatically to obtain a configuration file. With the Auto-Config function, the network

administrator can manage new switches or switches without any configuration file remotely.

NOTE

When Auto-Config starts, the system delivers the dhcp enable command by default to enable DHCP

globally. After DHCP is enabled globally, DHCP are sent to the CPU.

The Auto-Config function is applicable to new switches or switches without any configuration file

(unconfigured switches).

The Auto-Config function has the following advantages:

l The maintenance personnel do not need to manually configure each switch. With this

function, a few maintenance personnel can maintenance widely deployed devices.

l Auto-Config simplifies the network configurations and implements unified management

and remote debugging on switches.

l With Auto-Config allows switches to automatically download corresponding configuration

files, reducing the workload of network administrators.

Intermediate File

The intermediate file lswnet.cfg is used in the Auto-Config process. The intermediate file records

the mapping between MAC addresses of switches and names of configuration files. After anunconfigured switch obtains the IP address of the FTP/TFTP server, it downloads the

lswnet.cfg file from the FTP/TFTP server to search for the name of the required configuration

file, and then downloads the configuration file from the FTP/TFTP server.

NOTE

Auto-Config uses Option 67 to obtain the configuration file first. If Option 67 is not configured, Auto-

Config obtains the intermediate file.

For example, if the MAC address of an S2700 is 0018-82C5-AA89 and the S2700 needs to

download the configuration file S2700.cfg, the contents of the intermediate file are as follows:

mac=0018-82C5-

AA89;vrpfile=V100R006C00.cc;vrpver=V100R006C00;cfgfile=S2700.cfg;patchfile=S2700-

pat.pat;

esn=0213778899;vrpfile=V100R006C00.cc;vrpver=V100R006C00;cfgfile=S2700.

cfg;patchfile=S2700-pat.pat;

NOTE

If the configuration file is located on the FTP or TFTP server, its extension must be .cfg.

A MAC address and a configuration file name are separated by a semicolon. The format of a MAC address

is xxxx-xxxx-xxxx-xxxx. The name of a configuration file contains up to 48 characters, including the

extension .cfg. The name is case insensitive and cannot contain special characters. It is recommended that

the name consists of English letters, numbers, and underscore (_).

If multiple unconfigured switches need to be configured, each row in the intermediate file records the MACaddress of a switch and the name of the configuration file that the switch requires.




2


13/138

Option 67

The Option 67 field is configured on the DHCP server to specify the configuration file.

Option 150The Option 150 field is configured on the DHCP server to specify the IP address of the TFTP

server.

Option 14x

The Option 14x field is configured on the DHCP server to specify the IP address, user name,

and password of the FTP server.

l Option 141: specifies the user name of the FTP user.

l Option 142: specifies the password of the FTP user.

l

Option 143: specifies the IP address of the FTP server.l Option 145: version file.

l Option 146: identity.

l Option 147: authentication.

1.2 Auto-Config Features Supported by the S2700

This section describes how Auto-Config runs on the S2700.

Figure 1-1 shows the basic process of Auto-Config.




3


14/138

Figure 1-1 Basic process of Auto-Config

No

Obtain a configuration

file

Timer expires, delete

temporary

configuration and

make configuration

file effective

End

Does thedevice need to be

upgraded?

Start a timer to set thedelay in device restart

Can apatch file be

downloaded todevice?

Obtain a version file Obtain the patch file

Is the

version fileobtained?

Is the patch

file obtained?

No

Yes

Is there patch fileinformation?

No

No

NoYes

Yes Yes

Yes

Is the version file

valid?

Restart device

Is the patch file

valid?

Obtain the Web file

Is theconfiguration fileobtained?

Yes

Is there Web

file information?

Yes

Set the restart flag

Yes

Yes

Specify it as next

startup file

Specify it as next

startup file

Start a new

AutoConfig process

Is the restart

flag 1?

No

Yes

No No

No

No

No

Send DHCP Request

packets periodically

Auto-Config starts

No

Stop sending DHCP

Request packets

Yes

No

Yes

Configure non-

authentication for VTYs

Allocate IP address

Parse Option

parameters

AreDHCP Reply Packets

received?

AreDHCP Reply packets

valid?

Are thereVersion file name and

version info?




4


15/138

The Auto-Config process can be divided into three phases:

l Startup

After being powered on, an unconfigured switch checks whether there is *.cfg or *.zip fileexcept the *web.zip and web.zip files in the flash memory, and then takes actions according

to the checking result:

– If the switch detects a configuration file, it loads the configuration file to complete the

startup.

– If the switch does not detect any configuration file, it checks whether Auto-Config is

enabled. If Auto-Config is enabled, the switch starts a 5-minute timer for obtaining a

configuration file and then load the default configuration to complete the startup. If

Auto-Config is disabled, the switch loads the default configuration to complete the

startup.

l Obtaining a configuration file when the timer expires

When the timer set for obtaining a configuration file expires, the switch checks whether a

configuration file is saved in the flash memory. If the flash memory does not contain any

configuration file, the switch checks whether it is added to a Huawei Group Management

Protocol (HGMP) cluster. If the switch is not in any HGMP cluster, the switch begins to

obtain a configuration file as follows:

1. Obtaining the IP address and information about the FTP/TFTP server

A switch that does not load any configuration file automatically enables the DHCP

client function on the VLANIF1 interface in Up state. VLANIF1 then broadcasts

DHCP Request packets (presuming that the DHCP server has been configured with

the address pool, Option 150 or Option 14x, and gateway information). Then, the

DHCP server sends the related configurations to the switch, including the IP address

allocated to the switch, IP address of the FTP/TFTP server, FTP user name and

password, and default gateway.

If the switch fails to obtain the IP address of the FTP/TFTP server, it sends DHCP

requests repeatedly until it obtains the IP address.

2. Downloading files

If Option 67 is not configured on the DHCP server, the Auto-Config downloads the

intermediate file lswnet.cfg from the FTP/TFTP server and obtains required files. If

Option 67 is configured on the DHCP server, the Auto-Config parses parameters in

Option 145 fields and obtains required files from the FTP/TFTP server.

a. Obtaining a version file

After a version file is downloaded successfully, it is automatically configured as

the version file for next startup and the reset flag is automatically set to 1.

b. Obtaining a patch file

After a patch file is downloaded successfully, it is automatically configured as

the patch file for next startup and the device is restarted.

c. Obtaining a configuration file

NOTE

If the file fails to be obtained, it is downloaded once every 30 minutes. If it cannot be obtained

after 3 days, it is downloaded once every 2 hours. If it cannot be obtained after 30 days, the

process of downloading the patch file stops and waits to be handled manually.

l Loading a configuration file




5


16/138

After a configuration file is downloaded successfully, the configuration takes effect

according to the setting of Option 146. If no Option 146 is configured, the configuration

takes effect immediately after the configuration file is downloaded.

1.3 Deploying Unconfigured Switches (Same NetworkSegment)

This section describes how to deploy S2700s without configuration file.

1.3.1 Establishing the Configuration Task

Applicable Environment

As shown in Figure 1-2, unconfigured switches are reachable from a DHCP server. A PC isconnected to the DHCP server and functions as an FTP or a TFTP server to store configuration

files. After the DHCP server and FTP/TFTP server are configured, every switch obtains a

configuration file through Auto-Config.

The DHCP server, FTP/TFTP server, and switches are deployed on the same network segment.

Figure 1-2 Auto-Config networking where the DHCP server, FTP/TFTP server, and

unconfigured switch are on the same network segment

SwitchA

SwitchC

SwitchB

DHCP Server FTP/TFTP Server

Operator

Pre-configuration Tasks

Before deploying unconfigured switches, complete the following tasks:

l Ensuring that there are routes from the DHCP server and FTP/TFTP server to the switches

l Ensuring that there is no *.cfg or *.zip file except the *web.zip and web.zip files in the

flash memory of each switch

l Ensuring that the switches are not added to any HGMP cluster

Data Preparation

To deploy unconfigured switches, you need the following data.




6


17/138

No.

Data

1 Interconnection information about the upstream interfaces on each S2700 and the

downstream interfaces on the DHCP server

2 MAC address of each unconfigured switch

3 IP address, mask, address pool, and Option 150 or Option 14x of the DHCP server

4 IP address, version file, patch file, and configuration file on the FTP/TFTP server

1.3.2 Configuring the DHCP Server

ContextThe configuration procedure varies according to the device type of the DHCP server. Therefore,

the configuration procedure is not described and only the configuration contents are provided.

NOTE

The DHCP server must support either Option 150 or Option 14x.

Procedure

l Enable DHCP server.

l Configure an address pool, including the address range and Option 150 (or Option 14x).

It is required that the address pool be on the same network segment with unconfigured

switches and the FTP/TFTP server.

NOTE

Pay attention to the following points when configuring Option 150 or Option 14x:

l When new switches obtain configuration files through TFTP, the DHCP server must support

Option 150.

l When new switches obtain configuration files through FTP, the DHCP server must support

Option 141, Option 142, and Option 143.

l If both Option 150 and Option 14x are configured on the DHCP server, Option 150 takes

precedence over Option 14x.

l If you use ordinary characters to configure Option 150 or Option 143 on the DHCP server, the

Auto-Config module cannot recognize the IP address, which results in an Auto-Config process

sends the DHCP messages incessantly.

l Add the downstream interface on the DHCP server to the management VLAN in access

mode and assign an IP address on the same network segment as the IP address of the DHCP

server to the management VLAN.

After Auto-Config is enabled, packets from an unconfigured switch do not carry tags.

Therefore, ensure that untagged packets can be transmitted between unconfigured switches

and the DHCP server.

----End




7


18/138

1.3.3 Configuring the FTP/TFTP Server

Context

The configuration procedure varies according to the device type of the FTP/TFTP server.Therefore, the configuration procedure is not described and only the configuration contents are

provided.

Procedure

l Set the IP address of the FTP/TFTP server.

For an FTP server, the IP address must be the same as the value of Option 143 configured

on the DHCP server; for a TFTP server, the IP address must be the same as the value of

Option 150 configured on the DHCP server.

l Create and configure an intermediate file.

The intermediate file is configured according to the MAC addresses of unconfiguredswitches and the names of configuration files. For the format of the intermediate file, see

1.1 Overview.

l Save the intermediate file and configuration files to the working directory on the FTP/TFTP

server.

----End

1.3.4 Checking the Configuration

Prerequisites

The configurations of the DHCP server and FTP/TFTP server are complete.

Context

You can check different items in different phases in the Auto-Config process to confirm that

Auto-Config runs properly.

Procedure

Step 1 Five minutes after unconfigured switches are powered on, check address allocation on the DHCPserver to confirm that the switches are connected to the DHCP server.

NOTE

If the switches are connected to the DHCP server, you can log in to the switches through Telnet but do not

configure the switches.

Step 2 Five minutes after the switches obtain IP addresses, check the file downloading log on the FTP/TFTP server or log in to the switches to confirm that correct configuration files have been

downloaded.

NOTE

Do not save a configuration file to a switch to be configured immediately after the configuration file is

downloaded; otherwise, only a temporary configuration file is saved because the configurations have not

taken effect.

Step 3 If the user has specified the activation delay, the configuration file will take effect after the delay.If the user has not specified the activation delay, the configuration file will take effect




8


19/138

immediately by default. Then run the display current-configuration command to check

whether the configurations take effect.

NOTE

If you access the switch when it is busy delivering configurations in the Auto-Config process, the switchmay not respond in real time.

After the configurations take effect, modify the configuration of the downstream interface on the DHCP

server as required.

----End

1.4 Deploying Unconfigured Switches (Different NetworkSegments)

This section describes how to deploy unconfigured S2700s.



As shown in Figure 1-3, unconfigured switches are reachable from a DHCP relay and a DHCP

server. A PC is connected to the DHCP server and functions as an FTP or a TFTP server to store

configuration files. After the DHCP server and FTP/TFTP server are configured, every switch

obtains a configuration file through Auto-Config.

The DHCP server, FTP/TFTP server, and switches are deployed on different network segments.

Figure 1-3 Auto-Config networking where the DHCP server, FTP/TFTP server, and

unconfigured switches are on different network segments

SwitchA

SwitchC

SwitchB

DHCP Server FTP/TFTP Server

Operator

Network

DHCP Relay


Before deploying unconfigured switches, complete the following tasks:

l

Ensuring that there are routes from the DHCP server, DHCP relay, and FTP/TFTP server to the switches




9


20/138

l Ensuring that there is no *.cfg or *.zip file except the *web.zip and web.zip files in the

flash memory of each switch

l Ensuring that the switches are not added to any HGMP cluster and USB upgrade

Data Preparation

To deploy unconfigured switches, you need the following data.

No.

Data

1 Interconnection information about the upstream interfaces on each S2700 and the

downstream interfaces on the DHCP relay

2 Interconnection information about the DHCP relay and DHCP server

3 MAC address of each unconfigured switch

4 IP address, mask, address pool, and Option 150 or Option 14x of the DHCP server

5 IP address, mask, and relay address of the DHCP relay

6 IP address, default configuration file, and configuration files on the FTP/TFTP server

1.4.2 Configuring the DHCP Server

ContextThe configuration procedure varies according to the device type of the DHCP server. Therefore,

the configuration procedure is not described and only the configuration contents are provided.

NOTE

The DHCP server must support either Option 150 or Option 14x.

Procedure

l Enable DHCP server.

l Configure an address pool, including the address range, gateway, and Option 150 (or Option

14x).

NOTE

Pay attention to the following points when configuring Option 150 or Option 14x:

l When new switches obtain configuration files through TFTP, the DHCP server must support

Option 150.

l When new switches obtain configuration files through FTP, the DHCP server must support

Option 141, Option 142, and Option 143.

l If both Option 150 and Option 14x are configured on the DHCP server, Option 150 takes

precedence over Option 14x.

l If you use ordinary characters to configure Option 150 or Option 143 on the DHCP server, the

Auto-Config module cannot recognize the IP address.

----End




10


21/138

1.4.3 Configuring DHCP Relay

Context

The configuration procedure varies according to the device type of the DHCP relay. Therefore,the configuration procedure is not described and only the configuration contents are provided.

Procedure

l Enable DHCP relay.

l Configure the upstream and downstream interfaces.

You need to configure the IP address and mask for the upstream interface and configure

the IP address, mask, and DHCP relay address for the downstream interface.

NOTE

You can temporarily set the IP address of the downstream interface on the same network segment

with the IP addresses of unconfigured switches, and then add the downstream interface to the

management VLAN in access mode.

----End

1.4.4 Configuring the FTP/TFTP Server

Context

The configuration procedure varies according to the device type of the FTP/TFTP server.

Therefore, the configuration procedure is not described and only the configuration contents are

provided.

Procedure

l Set the IP address of the FTP/TFTP server.

For an FTP server, the IP address must be the same as the value of Option 143 configured

on the DHCP server; for a TFTP server, the IP address must be the same as the value of

Option 150 configured on the DHCP server.

l Create and configure an intermediate file.

The intermediate file is configured according to the MAC addresses of unconfigured

switches and the names of configuration files. For the format of the intermediate file, see

1.1 Overview.

l Save the intermediate file and configuration files to the working directory on the FTP/TFTP

server.

----End


Prerequisites

The configurations of the DHCP server, DHCP relay, and FTP/TFTP server are complete.




11


22/138

Context

You can check different items in different phases in the Auto-Config process to confirm that

Auto-Config runs properly.

Procedure

Step 1 Five minutes after unconfigured switches are powered on, check address allocation on the DHCPserver to confirm that the switches are connected to the DHCP server.

NOTE

If the switches are connected to the DHCP server, you can log in to the switches through Telnet but do not

configure the switches.

Step 2 Five minutes after the switches obtain IP addresses, check the file downloading log on the FTP/TFTP server or log in to the switches to confirm that correct configuration files have been

downloaded.

NOTE

Do not save a configuration file to a switch to be configured immediately after the configuration file is

downloaded; otherwise, only a temporary configuration file is saved because the configurations have not

taken effect.

Step 3 If the user has specified the activation delay, the configuration file will take effect after the delay.If the user has not specified the activation delay, the configuration file will take effect

immediately by default. Then run the display current-configuration command to check

whether the configurations take effect.

NOTE

If you access the switch when it is busy delivering configurations in the Auto-Config process, the switch

may not respond in real time.

After the configurations take effect, modify the configuration of the downstream interface on the DHCP

relay as required.

----End




12


23/138

2 NAP ConfigurationAbout This Chapter

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

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

2.2 Configuring NAP-based Remote Deployment

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

deployment.

2.3 Configur ation Examples

This section provides upgrade and maintenance examples together with the configuration

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

and configuration roadmap.

Configuration Guide - Device Management 2 NAP Configuration



13


24/138

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

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


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.


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.


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




14


25/138

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.

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




15


26/138

The system view is displayed.

2. Run:

interface interface-type interface-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-pool ip-address mask-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-pool ip-address mask-length command 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-ip mast-inter-mast-ip sub-ip mast-inter-sub-ip peer-ip sub-inter-mast-ip sub-ip sub-inter-sub-ip mask-length




16


27/138

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

2.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 nap interface command, 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:interface interface-type interface-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 enable command is executed on an interface, the interface cannot connect

to the NAP neighbor.

----End




17


28/138

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


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

Prerequisites

NAP-based remote deployment has been completed.

Procedure

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

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

----End

Example

Run the display nap status command to view the current NAP status.

display nap status Slave port status : Enable

Nap ip-pool/Mask : 12.12.12.0/24

Run the display nap interface interface-type interface-number command to view the NAP status

of the specified interface.

display nap interface gigabitethernet0/0/1




18


29/138

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

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

NAP master port list:

Port count : 2

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

Port property : Master Current status : DETECTING

Local port : GigabitEthernet0/0/1

Peer port : GigabitEthernet0/0/1 Local primary ip : NULL Peer primary ip : NULL

Local secondary ip : NULL

Peer secondary ip : NULL Hello time : 3s

Linked time : 00:00:00

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

Current status : DETECTING


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

Peer primary ip : NULL Local secondary ip : NULL

Peer secondary ip : NULL Hello 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 : GigabitEthernet0/0/1 Local primary ip : 12.12.12.5

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

Hello time : 3s

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


Current status : IP-ASSIGNED

Local port : GigabitEthernet0/0/2 Peer port : GigabitEthernet0/0/2

Local primary ip : 10.10.10.5

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

Hello time : 3s Linked time : 00:03:41------------------------------------------------------

2.3 Configuration Examples

This section provides upgrade and maintenance examples together with the configuration

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

and configuration roadmap.




19


30/138

2.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 2-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 2-1 Networking 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 B system-view[Quidway] sysname SwitchB[SwitchB] interface gigabitethernet0/0/1

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

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




20


31/138

[SwitchB-GigabitEthernet0/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 status command on

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

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

assigned to the master and slave interfaces. For example:

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

Slave port status : Enable Nap ip-pool/Mask : 10.167.253.0/24

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

NAP master port listPort count : 1

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


Current status : IP-ASSIGNED Local port : GigabitEthernet0/0/1

Peer port : GigabitEthernet0/0/1

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

Peer secondary ip : 12.12.12.10

Hello time : 3s Linked time : 00:02:33

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

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

# Configure Switch B.

[SwitchB-GigabitEthernet0/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 Files None

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

Networking Requirements

As shown in Figure 2-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




21


32/138

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 2-2 Networking diagram of NAP-based remote deployment

Network

SwitchAPC SwitchB SwitchC

Configuration Roadmap

The configuration roadmap is as follows:

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

Procedure

Step 1 Configuring the NAP master interface

# Do as follows on Switch B.When configuring the NAP master interface, ensure that there are

unused VLAN IDs in the system.

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

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

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

# Do as follows on Switch B.

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

Press CTRL+K to abort

Connected 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




22


33/138

Configuration Files

None




23


34/138

3 Stacking About This Chapter

This chapter describes the basic concepts and configuration methods of the stacking function.

3.1 Stacking Overview

This section describes basic concepts of the stacking function.

3.2 Stacking Function Supported by the S2700

This section describes the basic principle of the stacking function.

3.3 Configuring the Stacking Function on the S2700

This section describes how to configure the stacking function on the S2700.

3.4 Configuration Examples

This section provides an example for configuring the stacking function.

Configuration Guide - Device Management 3 Stacking



24


35/138

3.1 Stacking Overview

This section describes basic concepts of the stacking function.

The stacking function indicates that multiple S2700es are connected together to form an

administrative domain. The stack devices that are connected logically through the stacking

function can be regarded as one device. Up to 16 stack devices are deployed in a link topology.

Roles of devices in a stack are as follows:

l Master switch

The master switch assigns numbers and IP addresses to member switches in a stack.

l Slave switch

In addition to a master switch, all the other switches in a stack are slave switches.

Interfaces connecting stack devices are stack interfaces, and other interfaces are common user interfaces. Stack devices can be connected through upstream GE interfaces only. Interfaces can

be connected through common twisted pair cables or optical fibers.

3.2 Stacking Function Supported by the S2700

This section describes the basic principle of the stacking function.

Prerequisites for Creating a Stack System

To successfully create a stack system, ensure that:l All the devices support the stacking function.

l All the devices are connected through uplink GE interfaces.

l The uplink GE interfaces are connected through twisted pair cables or optical fibers.

l Interfaces connecting switches belong to one management VLAN and the VLANIF

interface corresponding to the management VLAN has been created on the member

switches.

By default, the management VLAN is VLAN 1 and you can create VLANIF 1.

l All the devices can be started normally.

Creation of a Stack System

When all the devices meet the preceding prerequisites, a stack system is created as follows:

l Configure an address pool

You need to specify the range of IP addresses for a stack before setting up a stack. When

a slave switch is added to a stack, the master switch automatically assigns an available IP

address to the slave switch.

NOTE

The stack system supports the link topology only. If the master switch is faulty, the stack system does

not work. In this case, you need to select a new master switch and then set up a new stack system.

l Select a master switch

Configuration Guide - Device Management 3 Stacking



25


36/138

If you run the stacking enable command to enable the stacking function on a device where

an IP address pool is configured, the device is configured as the master switch, and other

switches function as slave switches.

l Add a slave switch to a stack system

The master switch sends a request packet to stack interfaces in the Up state to invite slaveswitches to join the stack system. After receiving the packet, a slave switch sends a reply

packet to the master switch and forwards the request packet to its other connected stack

interfaces in the Up state.

Then, the master switch assigns a stack ID and an IP address to the slave switch after

receiving the reply packet. The slave switch sends an Ack packet to the master switch after

receiving the stack ID and IP address. In this manner, a stack system is created.

3.3 Configuring the Stacking Function on the S2700

This section describes how to configure the stacking function on the S2700.



To meet the increasing requirements of services, the devices on the current network keep

Documents

S2700 V100R006C00 Configuration Guide - Device Management 02