Quidway S5300 - Device Management(V100R005C01_02).pdf

8/10/2019 Quidway S5300 - Device Management(V100R005C01_02).pdf

1/57

Quidway S5300 Series Ethernet Switches

V100R005C01

Feature Description - Device

Management

Issue 02

Date 2010-12-01

HUAWEI TECHNOLOGIES CO., LTD.


2/57


3/57

Copyright Huawei Technologies Co., Ltd. 2010. 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 02 (2010-12-01) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


4/57


5/57

About This Document

Intended Audience

This document describes the device management feature in terms of its overview, principle, and

applications.

This document together with other types of document helps intended readers get a deep

understanding of the device management feature.

This document is intended for:

l Network planning engineers

l Commissioning engineers

l Data configuration 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.


Feature Description - Device Management About This Document



iii


6/57

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.

& 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 updates made in previous issues.

Changes in Issue 02 (2010-12-01)

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

Minor mistakes are modified.

Changes in Issue 01 (2010-08-15)

Initial commercial release.

About This Document


Feature Description - Device Management

iv Huawei Proprietary and Confidential


Issue 02 (2010-12-01)


7/57

Contents

About This Document...................................................................................................................iii

1 Mirroring......................................................................................................................................1-1

1.1 Introduction to Mirroring................................................................................................................................1-2

1.2 References.......................................................................................................................................................1-21.3 Principles.........................................................................................................................................................1-2

1.3.1 1:1 or N:1 Mirroring...............................................................................................................................1-3

1.3.2 Port Mirroring for Inbound or Outbound Packets..................................................................................1-4

1.3.3 VLAN Mirroring for Inbound Packets...................................................................................... .............1-4

1.3.4 MAC-Address-based Mirroring.............................................................................................................1-5

1.3.5 Flow-based Mirroring............................................................................................................................1-5

1.3.6 RSPAN...................................................................................................................................................1-5

1.4 Terms and Abbreviations.................................................................................................... ............................1-6

2 Information Center....................................................................................................................2-12.1 Introduction to the Information Center...........................................................................................................2-2

2.2 Reference.........................................................................................................................................................2-3

2.3 Pinciples..........................................................................................................................................................2-3

2.3.1 Information Classification.................................................................................................... ..................2-3

2.3.2 Information Hierarchy........................................................................................................ ....................2-7

2.3.3 Information Output........................................................................................ .........................................2-9

2.3.4 Information Shield................................................................................................................................2-10

2.4 Terms and Abbreviations................................................................................................ ..............................2-11

3 PoE.................................................................................................................................................3-13.1 Introduction to PoE.........................................................................................................................................3-2

3.2 References.......................................................................................................................................................3-2

3.3 Principle..........................................................................................................................................................3-3

3.4 Terms and Abbreviations................................................................................................................................3-9

4 NAP...............................................................................................................................................4-1

4.1 Introduction to NAP........................................................................................................................................4-2

4.2 References.......................................................................................................................................................4-2

4.3 Principles.........................................................................................................................................................4-2



Feature Description - Device Management Contents



v


8/57

5 Stacking........................................................................................................................................5-1

5.1 Stacking Overview..........................................................................................................................................5-2

5.2 References.......................................................................................................................................................5-2

5.3 Principles.........................................................................................................................................................5-2

5.4 Application......................................................................................................................................................5-8


Contents



vi Huawei Proprietary and Confidential


Issue 02 (2010-12-01)


9/57

Figures

Figure 1-1Schematic diagram of 1:1 mirroring...................................................................................................1-3

Figure 1-2Schematic diagram of N:1 mirroring..................................................................................................1-4

Figure 1-3Schematic diagram of port mirroring.................................................................................................1-4

Figure 2-1Output format of logs.........................................................................................................................2-4

Figure 2-2Output format of traps........................................................................................................................2-5

Figure 2-3Diagram of outputting debugging information...................................................................................2-7

Figure 2-4Diagram of information filtration.....................................................................................................2-11

Figure 3-1Power supply in Alternative A mode on the 10BaseT and 100Base-TX Ethernet.............................3-4

Figure 3-2Power supply in Alternative A mode on the 1000Base-T Ethernet....................................................3-4

Figure 3-3Power supply in Alternative B mode on the 10BaseT and 100Base-TX Ethernet.............................3-5

Figure 3-4Power supply in Alternative B mode on the 1000Base-T Ethernet....................................................3-5

Figure 3-5TLV packet header.............................................................................................................................3-6

Figure 3-6TLV information field........................................................................................................................3-7

Figure 4-1Establishing a NAP connection..........................................................................................................4-3Figure 4-2Format of the NAP packet..................................................................................................................4-4

Figure 4-3NAP negotiation process....................................................................................................................4-5

Figure 5-1Setting up a stack................................................................................................................................5-3

Figure 5-2Adding a member switch to a stack....................................................................................................5-4

Figure 5-3Removing a slave switch from a stack...............................................................................................5-5

Figure 5-4Combining two stacks........................................................................................................................5-6

Figure 5-5Dividing a stack 1...............................................................................................................................5-7

Figure 5-6Dividing a stack 2...............................................................................................................................5-8

Figure 5-7Increasing ports...................................................................................................................................5-8

Figure 5-8Increasing bandwidth..........................................................................................................................5-9


Feature Description - Device Management Figures



vii


10/57


11/57

Tables

Table 2-1Feature list of the information center...................................................................................................2-2

Table 2-2Description of each field in a log.........................................................................................................2-4

Table 2-3Description of each field in a trap........................................................................................................2-6

Table 2-4Description of the severity levels of information.................................................................................2-8

Table 2-5Relationship between information channels and output directions......................................................2-9

Table 3-1References............................................................................................................................................3-3

Table 4-1Description of fields that indicate the types of NAP packets...............................................................4-4

Table 4-2Mappings between data types and user data in the variable-size TLV data area of the NAP packet

...............................................................................................................................................................................4-4


Feature Description - Device Management Tables



ix


12/57


13/57

1MirroringAbout This Chapter

1.1 Introduction to Mirroring

1.2 References

1.3 Principles

1.4 Terms and Abbreviations


Feature Description - Device Management 1 Mirroring



1-1


14/57

1.1 Introduction to Mirroring

Definition

Mirroring is a function of copying packets to an observing interface and then monitoring the

packets.

Purpose

Mirroring is used to monitor packets that meet certain requirements.According to the

configurations of users, mirroring is classified into the following types:

l 1:1 port mirroring and N:1 port mirroring

1:1 port mirroring is used to observe packets on an interface.

N:1 port mirroring is used to observe packets on multiple interfaces.

l Port mirroring for inbound or outbound packets

It is used to observe packets received or sent by a specific interface.

l VLAN mirroring for inbound packets

It is used to observe packets received by the switch from a specific VLAN.

l MAC-address-based mirroring

It is used to observe packets with a specific MAC address from a specific VLAN. This

MAC address can be a source MAC address or a destination MAC address.

l Flow mirroring

It is used to mirror packets according to the configurations of users. For example, packetsthat match the traffic policy based on the 802.1p priority are mirrored.

l RSPAN

It is used to observe packets on an interface or a VLAN of a remote switch.

The S5300SI does not support remote mirroring based on flows, VLANs, and MAC addresses.

1.2 References

None.

1.3 Principles

In the process of mirroring, a packet is copied to an observing interface on the condition that the

packet is processed normally.

1.3.1 1:1 or N:1 Mirroring

1.3.2 Port Mirroring for Inbound or Outbound Packets

1.3.3 VLAN Mirroring for Inbound Packets

1.3.4 MAC-Address-based Mirroring

1.3.5 Flow-based Mirroring

1 Mirroring



1-2 Huawei Proprietary and Confidential


Issue 02 (2010-12-01)


15/57

1.3.6 RSPAN

1.3.1 1:1 or N:1 Mirroring

l 1:1 mirroring is used for mirroring packets passing through a specific interface to anobserving interface.

As shown in Figure 1-1, packets on mirroring interface B are copied to observing interface C.

Mirror indicates a mirroring interface; Monitor indicates an observing interface; Forward

indicates the path for forwarding packets normally; Mirroring indicates that packets are copied

to the observing interface.

Figure 1-1Schematic diagram of 1:1 mirroring

Mirror

B

A

C

Packets

Forward

Mirroring

Monitor

Mirrored packets

l N:1 mirroring is used for mirroring packets passing through several interfaces to an

observing interface.

As shown in Figure 1-2, packets received on mirroring interfaces B and D are copied to

observing interface C. Mirror indicates a mirroring interface; Monitor indicates an observing

interface; Forward indicates the path for forwarding packets normally; Mirroring indicates that

packets are copied to the observing interface.





1-3


16/57

Figure 1-2Schematic diagram of N:1 mirroring

Mirror

B

A

C

Packets

Forward

Mirroring

Monitor

Mirrored packets

MirroringMirror

D

Packets

1.3.2 Port Mirroring for Inbound or Outbound Packets

Figure 1-3shows port mirroring for inbound and outbound packets.

l Port mirroring for inbound packets is used to copy packets that are received on a port to an

observing port.

l Port mirroring for outbound packets is used to copy packets that are sent out by a port to

an observing port.

Figure 1-3Schematic diagram of port mirroring

Observinginterface

Switch

Monitoring host

Interface

Flows of packets

Mirroring interface

Mirroing interface

Copied flows of packets

1.3.3 VLAN Mirroring for Inbound Packets

The S-switch does not support VLAN mirroring for outbound packets.

1 Mirroring





Issue 02 (2010-12-01)


17/57

VLAN mirroring for inbound packets is used to copy inbound packets on all active interfaces

in a specified VLAN to an observing interface.

The VLAN ID is specified by a command.

1.3.4 MAC-Address-based Mirroring

MAC-address-based mirroring is used for mirroring packets with a specific MAC address to an

observing interface. MAC-address-based mirroring is configured in the VLAN view. Therefore,

when a packet arrives, check whether the VLAN where the packet is sent is consistent with the

VLAN where MAC-address-based mirroring is configured first.

MAC-address-based mirroring is used to mirror only incoming packets.

1.3.5 Flow-based Mirroring

Flow-based mirroring is used for mirroring packets to an observing interface according to thepolicy configured by a user.

Flow-based mirroring is used to mirror only incoming packets.

1.3.6 RSPAN

RSPAN is used for mirroring packets from the source switch to the remote switch.

It is implemented by adding an RSPAN VLAN tag to a mirroring packet on the outbound

interface of the source switch. The packet is then transparently transmitted by the intermediate

switches to the remote switch. After the packet arrives at the remote switch, the remote switch

removes the RSPAN VLAN tag from the packet. Packets contain the RSPAN VLAN tag whenbeing transparently transmitted on Layer 2 networks. Therefore, RSPAN VLAN tags and service

VLAN tags need to be distinguished during VLAN planning.

RSPAN is classified into the following types:

l RSPAN based on an inbound or outbound interface

RSPAN based on an inbound or outbound interface is used for mirroring packets received

or sent by a specific interface of the source switch to the remote switch.

l Inbound VLAN-based RSPAN

RSPAN based on an inbound VLAN is used for mirroring packets received by the source

switch from a specific VLAN to the remote switch.l MAC-address-based RSPAN

MAC-address-based RSPAN is used for mirroring packets with a specific MAC address

that are received on the source switch to the remote switch. Like local Switched Port

Analyzer (SPAN), RSPAN needs to first match the VLAN ID on the source switch. That

is, the MAC address belongs to a specific VLAN where the source switch is located.

l Flow-based RSPAN

Flow-based RSPAN is used for mirroring packets that match a specific policy and are

received on the source switch to the remote switch. Flow-based RSPAN is flexible, which

mirrors flows according to certain fields of flows. Flow-based RSPAN is configured on

interfaces. Flow-based RSPAN is implemented with the action of a traffic policy.





1-5


18/57


19/57

2Information CenterAbout This Chapter

2.1 Introduction to the Information Center

2.2 Reference

2.3 Pinciples



Feature Description - Device Management 2 Information Center



2-1


20/57

2.1 Introduction to the Information Center

Definition

The information center, which is indispensable to a device, functions as the information hub of

the device. The information center manages most output information. Output information is

refinedly classified and then effectively filtered. Cooperated with the debugging program (the

debuggingcommand), RMON module and SNMP module, the information center provides

powerful supports for the network administrator to monitor the operation of devices and locate

faults.

The working principle of the information center is as follows:

Generally speaking, the information center distributes three types of information with eight

severity levels to ten information channels and then outputs information in different directions.Details are as follows:

1. Receives logs, traps, and debugging information of different severity levels that are output

by each module.

NOTE

The logs, traps, and debugging information of each module are saved in the corresponding log, trap,

and debugging queues in the information center. Each queue can hold 30 k messages.

2. Distributes information of different types and with different severity levels to different

information channels according to user settings.

3. Outputs information in different directions based on the association between the

information channel and the output direction.

The following table lists main features of the information center.

Table 2-1Feature list of the information center

Feature Description

Information

type

Information is classified into log, trap, and debugging information.

Information

severity

Eight severity levels are defined for information. The more important the

information is, the smaller the severity value is.

Information

output

The information center can output information to the console, VTY/TTY

terminal, log host, SNMP agent, log buffer and trap buffer.

Information

shield

You can shield the output information of a severity level or a module through

commands.

Purpose

The information center outputs information in a unified format to different directions, thusimproving readability, maintainability, and flexibility of logs.

2 Information Center





Issue 02 (2010-12-01)


21/57

1. Controls where information is output. Currently, information can be output to the console,

VTY/TTY terminal, log host, SNMP agent, log buffer and trap buffer.

2. Filters information. Currently, information can be filtered based on the source, severity

level, type, and output direction.

3. Provides a system-level information output platform.

4. Displays the system-level debugging information.

2.2 Reference

The following table lists the reference of this feature:

Document Description

RFC 3164 The BSD syslog

2.3 Pinciples

2.3.1 Information Classification

2.3.2 Information Hierarchy

2.3.3 Information Output

2.3.4 Information Shield

2.3.1 Information Classification

To meet different requirements of clarified information in different directions, the information

center classifies information into three types: logs, traps, and debugging information.

Logs are used to record user operations and diagnosis information. Diagnosis logs are used by

R&D personnel for fault location; users can view user logs only.

Traps are used to record faults. After receiving traps, the information center sends them to the

SNMP agent. Then, the SNMP agent sends the traps to the NMS.

Debugging information is used to trace the running status of a device.

Log Information

l Log overview

Defined by the ITU-T, logs refer to records about events and abnormal activities of the

managed object. It is generally accepted that the log module is capable of tracing activities

of users, managing security affairs of the system, providing basis for diagnosis and

maintenance. Therefore, log recording is an important method for operation maintenance

and fault location.

l Implementation of logs on S5300 devices

By default, the information center is enabled and it can output logs to the console, log bufferand SNMP agent.





2-3


22/57

After a log host is configured, logs can be sent to it. Currently, up to eight log hosts can be

configured for a S5300 device. In this manner, logs can be sent to different log hosts

simultaneously for backup.

By default, the device can send logs to the console and log buffer. The number of logs

stored in the log buffer or the log buffer can be configured from 1 to 1024. The defaultvalue is 512. If the number of logs in the log buffer reaches the upper limit, new logs will

replace the existing logs in a time order until all the new logs are stored. That is, the log

put into the log buffer earliest is replaced first.

l Output format of logs

Syslog is a sub-function of the information center. Syslog uses UDP as the transmission

protocol and outputs logs to log hosts through port 514.

Figure 2-1shows the log format.

Figure 2-1Output format of logs

TIMESTAMP HOSTNAME %%ddAAA/B/CCC(l): -Slot=k-XXX; YYYY

Table 2-2describes each field in a log.

Table 2-2Description of each field in a log

Field Meaning Description

Leading character Before logs are output to log hosts, leading

characters are added to logs. Logs saved in the local

device do not contain leading characters.

TIMESTAMP Time to send logs Five timestamp formats are available:

l boot: indicates relative time.

l date: indicates system time. By default,

debugging information, logs and traps adopt

this timestamp format.

l short-date: indicates system time. The short-

date format does not contain year information.

l format-date: indicates another format of system

time.

l none: indicates that no timestamp is contained

in logs.

The timestamp and the host name are separated by

a blank space.

HOSTNAME System name of the

local device

By default, the system name is Quidway.

The host name and the module name are separated

by a blank space.

%% Huawei identifier Indicates that the log is output by a Huawei

product.

dd Version number Identifies the version of the log format.






Issue 02 (2010-12-01)


23/57


AAA Module name Indicates the name of the module that outputs

information to the information center.

B Log level Indicates the severity level of logs.

CCC Description Further describes the information type.

(L) Information type l l: log information

l T: trap information

l d: debugging information

-Slot=k-XXX Location information Slot: indicates the number of the slot that sends

location information. Location information begins

and ends with a blank space. Some modules

generate logs without location information.

YYYY Descriptor Indicates detailed log information output from

each module to the information center. Every time

a log is output, the module fills this field with

detailed information.

Trap Information

l Trap overview

Traps are notifications generated when the system detects faults. Information about the

faults are carried in traps. Different from logs, traps are time sensitive and need to be notified

to administrators in time. Therefore, the information center processes traps sent to the NMS

in a different method.

Traps are sent from a device to an NMS device. With SNMP agent enabled on a device,

the trap function enabled on the related module, and the NMS host to which traps are sent

configured, when an event happens (for example, the network interface becomes Down),

the deivce generates a trap and sends it to the specified destination address. If the device

and the NMS are routable, the NMS can receive the trap.

In addition, the device has a trap buffer for storing traps. If the information source is

configured for the buffer on the information center, the buffer can store traps generated by

the local device regardless whether the destination NMS host is configured.

l Concepts about traps

Event: indicates anything that takes place on the managed object. For example, the

managed object is added, deleted, or modified.

Fault: indicates that the system does not work normally. A fault may cause the system

to be disabled in operation or redundancy.

Trap: indicates the notification generated when the system detects a fault.

l Output format of traps

Figure 2-2Output format of traps

Severity Brief:DescriptionTimeStamp HostName ModuleName





2-5


24/57

Table 2-3describes each field in a trap.

Table 2-3Description of each field in a trap


TimStamp Time to send traps Five timestamp formats are available:

l boot: indicates relative time. By default,

debugging information adopts this timestamp

format.

l date: indicates the timestamp in the format of

system time. By default, logs and traps adopt

this timestamp format.

l short-date: indicates system time. The short-

date format does not contain year information.

l format-date: indicates another format of system

time.

l none: indicates that no timestamp is contained

in traps.

The timestamp and the host name are separated by

a blank space.

HostName System name of the

local device

By default, the system name is Quidway.

The host name and the module name are separated

by a blank space.

ModuleName Module name Indicates the name of the module that generates

traps.

Serverity Severity Indicates the severity level of traps.

l Critical

l Major

l Minor

l Warning

l indeterminate

Brief Description Indicates brief description of traps.

Description Description Indicates detailed description of traps.

Debugging Information

Debugging information is the output of the tracing information about the running status of a

device. Devices can generate debugging information only after the debugging of the module to

be debugged is enabled in the user view. Debugging information shows the contents of packets

sent or received by the debugged module. Note that enabling debugging only generatesdebugging information. Displaying debugging information requires more configurations.






Issue 02 (2010-12-01)


25/57

Different from logs and traps, no buffer is available for debugging information. Debugging

information can be output to the console or be sent to log hosts through certain configurations.

You can connect the PC to the console port of a device (the console mode) or to a network

interface of a device through Telnet (the terminal mode). When debugging the device through

the console or the terminal, you can control the contents of the output debugging information.

Abundant debugging commands are provided for debugging protocols and functions that a

device supports. You can enable the debugging of a protocol or a function to diagnose and locate

the fault.

The output of debugging information depends on the following situations:

l Whether debugging information about a protocol is output

l Whether terminal display is enabled, that is, whether to display the debugging information

on the screen

Figure 2-3shows the relationship between the preceding two situations. After the debugging of

protocol 1 and 3 is enabled, corresponding debugging information is output. As screen displayis also enabled, the debugging information is displayed. No debugging information about

protocol 2 is output because the debugging of protocol 2 is not enabled.

Figure 2-3Diagram of outputting debugging information

1 2 3

1 3 1 3

1 3

Debug

information

Protocol debug

switchON OFF

ON

ON

OFF

Termina display

switch

2.3.2 Information Hierarchy

Overview

In the case of much information, users can hardly differentiate between information about normal

operation and information about faults. Therefore, information hierarchy is designed to help

users roughly determine whether to take action immediately or shield the information that doesnot require an action.





2-7


26/57

Severity Levels of Information

Information is categorized into eight severity levels. The severer the information is, the lower

the severity level threshold is. Details are shown in Table 2-4.

Table 2-4Description of the severity levels of information

Value SeverityLevel

Description

0 Emergency A fatal fault occurs in the device, which causes the system to fail

to run normally unless the device is restarted. For example, the

device is restarted because of the abnormal operation of a

program or because of a detected fault about memory usage.

1 Alert A grave fault occurs in the device, which requires actions to be

taken immediately. For example, memory usage of the system

reaches the upper limit.

2 Critical A grave fault occurs in the device, which requires actions to be

taken to analyze or process it. For example, the memory usage

is lower than the lower limit; the temperature is lower than the

lower limit; Bidirectional Forwarding Detection (BFD) detects

that the device is unreachable; error messages generated by the

device itself are detected.

3 Error A fault about improper operation or abnormal process occurs in

the device, which does not affect subsequent services but

requires attention and cause analysis. For example, users enter

incorrect instructions or passwords; error protocol packets

received by other devices are detected.

4 Warning An abnormality that may result in a fault occurs in the device,

which requires full attention. For example, the routing process

is disabled; packet loss is detected through BFD; error protocol

packets are detected.

5 Notice A key operation is performed to keep the device running

normally. For example, the shutdowncommand is run on an

interface; a neighbor is discovered; the state of the protocol state

machine normally changes.

6 informational A normal operation is performed. For example, the displaycommand is run.

7 Debugging A normal operation is performed, which requires no attention.

The severity level of output information is configurable. If information is filtered according to

the configured severity level, only information with a severity level lower than or equal to the

configured severity level threshold is output. That is, only information with the configured

severity level and more serious information are output.

For example, if the severity level threshold is set to 6, only the information whose severity levelranges from 0 to 6 is output.






Issue 02 (2010-12-01)


27/57

2.3.3 Information Output

The information center needs to output information to the terminal, console, log buffer and

SNMP agent. To output information in different directions, ten information channels are defined

for the information center and the channels work independently from each other.

Information Output Channel

The ten channels are equal and same. Before using information channels, you need to specify

information sources for channels. The defaults information sources for the fist six channels

(console, monitor, log host, trap buffer, log buffer, and SNMP agent).

Besides the default channels, you can customize information sources for the rest four channels

(Channel 6, Channel 7, Channel 8, and Channel 9) by configuring their channel name or by

running the configuration commands.

Information Output Direction

The information center supports ten channels, among which Channel 0 to Channel 5 have their

default channel names. By default, the six information channels are respectively related to six

output directions, as shown in Table 2-5.

Table 2-5Relationship between information channels and output directions

ChannelNumb

er

DefaultChannelName

OutputDirection

Description

0 console Console Outputs information to the local console that can

receive logs, traps, and debugging information.

1 monitor Monitor Outputs information to the virtual type terminal

(VTY) that can receive logs, traps, and debugging

information. This is helpful for remote maintenance.

2 loghost Log host Outputs information to the log host that can receive

logs, traps, and debugging information. The

information is saved to the log host in the file format

for the convenience of reference.

3 trapbuffer Trap

buffer

Outputs information to the trap buffer that can receive

traps. An area is specified inside a device as the trap

buffer to record traps.

4 logbuffer Log buffer Outputs information to the log buffer that can receive

logs. An area is specified inside a device as the log

buffer to record logs.

5 snmpagent SNMP

agent

Outputs information to the SNMP agent that can

receive traps.

6 unspecified Unspecifie

d

Reserved.





2-9


28/57

ChannelNumber

DefaultChannelName

OutputDirection

Description


d

Reserved.


d

Reserved.


d

Reserved.

Owning to associating each information channel with an output direction, information can be

output to a specific direction through the associated channel.

You can change channel names or relationships between channels and output directions as

required.

Information Output

Terminals that are connected to the device dynamically change. The information center needs

to know the change in time so that it determines whether to output information to terminals and

in which format information is output. Once an EXEC user enters or quits or its attribute changes,

the change is notified to the information center through the EXEC module so that information

can be correctly output.

2.3.4 Information Shield

To control information output flexibly, the information center provides the information shield

function. Through commands, the information center can determine whether a specific type of

information is output, information with which severity level is output, and information from

which module is output.

Information Shield Table

The information center filters information by using a shield table.

With the shield table, information that is output to multiple directions is filtered and then output

according to information types, severity levels, and sources. Multiple information shield table

can be set up in the information center. Each information shield table can correspond to one or

several output directions. Shielded information can be unshielded through modification as

required.

The contents of an information shield table are as follows:

l Number of the module that generates the information

l Whether logs can be output

l Logs at which severity levels can be output

l Whether traps can be output






Issue 02 (2010-12-01)


29/57

l Traps with which severity levels can be output

l Whether debugging information can be output

l Debugging information with which severity levels can be output

As shown in Figure 2-4, by default, logs, traps, and debugging information are output throughdefault channels. You can specify a channel through which information is output. For example,

you can configure logs to be output to the log buffer through Channel 6. In this manner, logs are

output through the configured Channel 6 rather than the default Channel 4.

Figure 2-4Diagram of information filtration

Infomation type Infomation channel

Console

Remote

terminal

Loghost

Trap buffer

Log buffer

SNMP agent

Logs

Traps

Debugs

Output direction

Direction of logs

Direction of alarms

Direction of debugging

information

Console

SNMP agent

Monitor

Loghost

Logbuffer

Trapbuffer

0

1

2

3

4

5

channel6

channel7

channel8

channel9

6

7

8

9


TermsTerm Description

Log Log information

Event Anything that takes place on the managed object. For example, the

managed object is added, deleted, or modified.

Trap Trap information

Debug Debugging information

SNMP Simple Network Management Protocol





2-11


30/57


31/57

3PoEAbout This Chapter

3.1 Introduction to PoE

3.2 References

3.3 Principle



Feature Description - Device Management 3 PoE



3-1


32/57

3.1 Introduction to PoE

Power over Ethernet (PoE) provides power through the Ethernet. It is also called Power overLAN (PoL) or active Ethernet.

PoE involves the following devices:

l PSE: Power-sourcing Equipment

l PD: Powered Device

Purpose

With wide application of IP phones, network video monitoring, and wireless Ethernet networks,

the power supply requirements on the Ethernet become urgent. In most situations, access point

devices need DC powersupply, but access point devices are often installed on the ceiling thathas a long distance from the ground. The nearby proper power socket is difficult to find. Even

if the proper power socket is available, the network administrator finds it hard to install the

converter of the AC and DC power required by access point devices. On large-scale LANs, the

administrators need to manage multiple access point devices that require uniform power supply

and management. In this case, power supply management is difficult. The PoE function

addresses this problem.

The PoE technology is used on the wired Ethernet and is most widely used on LANs. This

technology transmits power coupled with data to terminals through cables or transmits power

without data through idle lines.

This technology provides power on the 10Base-T, 100Base-TX, or 1000Base-T Ethernet at a

distance of up to 100 m. PoE can be used to effectively provide centralized power for terminalssuch as IP phones, Access Points (APs), chargers of portable devices, POS machines, cameras,

and data collection devices. Terminals are powered when they access the network. Therefore,

the indoor cabling of power supply is not required.

Benefits

The costs on the cabling of power supply are saved. The power supply for IP cameras, video

servers, and code converters, can be installed flexibly. In addition, the Uninterruptible Power

Supply (UPS) ensures uninterrupted power supply for the devices.

3.2 References

Table 3-1lists the references related to the PoE function.

3 PoE





Issue 02 (2010-12-01)


33/57

Table 3-1References

Document Description Remarks

IEEE 802.3af PoE industry standards. The

output power of the PSE is limitedto 15.4 W, the power consumption

of the PD is limited to 12.95 W,

and the transmission length of

Category 5 cable is 100 m. The

resistance is 20 ohms.

-

IEEE 802.3at Extension of IEEE802.3af. The

output power of the PSE is limited

to 30 W, the power consumption

of the PD is limited to 25.5 W, and

the transmission length is still 100

M. The resistance is 12.5 ohms.You are advised to use super-

category 5 cables.

-

3.3 Principle

Introduction to PoE Power Supply

According to IEEE 802.3af, PoE involves PSEs and PDs. The PSEs provide power for otherdevices and are classified into MidSpan (the PoE module is installed out of the switch) and

Endpoint (the PoE module is integrated to the switch) PSEs. The S5300 is the Endpoint switch.

IEEE 802.3af and IEEE 802.3at allow the Endpoint PSE to use four copper line pairs connected

to pins 1 and 2 and pins 3 and 6 or pins 4 and 5 and pins 7 and 8 for power supply. The Endpoint

PSE is compatible with 10Base-T, 100Base-TX, and 1000Base-T interfaces. The Endpoint PSE

is more widely used than the Midspan PSE.

The Endpoint PSE provides power in either of the following modes according to the line:

l Alternative A: The Endpoint PSE use line pairs connected to pins 1 and 2 and pins 3 and

6 for power supply.

10Base-T and 100Base-TX interfaces use copper line pairs connected to pins 1 and 2 andpins 3 and 6 to transmit data, and 1000Base-T interfaces use four line pairs to transmit data.

The PSE provides power for the PD through copper line pairs connected to pins 1 and 2

and pins 3 and 6. DC power and data frequency are independent. Pin 1 and pin 2 form the

positive (negative) pole; pin 3 and pin 6 form the negative (positive) pole.

Figure 3-1shows the power supply in Alternative A mode on the 10BaseT and 100Base-

TX Ethernet.





3-3


34/57

Figure 3-1Power supply in Alternative A mode on the 10BaseT and 100Base-TX

Ethernet

Data pair

Data pair

Data pair

Data pair

PD

1

24

5

7

8

3

6

1

24

5

7

8

3

6

PSE

Figure 3-2shows the power supply in Alternative A mode on the 1000Base-T Ethernet.

Figure 3-2Power supply in Alternative A mode on the 1000Base-T Ethernet

Data pair

Data pair

Data pair

Data pair

Data pair

Data pair

PD

1

2

4

5

7

8

3

6

1

2

4

5

7

8

3

6

PSE

Data pair

Data pair

l Alternative B: The Endpoint PSE uses copper line pairs connected to pins 4 and 5 and pins

7 and 8 for power supply.

The PSE provides power for the PD through copper line pairs connected to pins 4 and 5

and pins 7 and 8. DC power and data frequency are independent. Pin 4 and pin 5 form the

positive pole; pin 7 and pin 8 form the negative pole.

Figure 3-3shows the power supply in Alternative B mode on the 10BaseT and 100Base-

TX Ethernet.

3 PoE





Issue 02 (2010-12-01)


35/57

Figure 3-3Power supply in Alternative B mode on the 10BaseT and 100Base-TX

Ethernet

Data

pair

Data

pair

Data

pair

Data

pair

PD

1

24

5

7

8

3

6

1

24

5

7

8

3

6

PSE

Figure 3-4shows the power supply in Alternative B mode on the 1000Base-T Ethernet.

Figure 3-4Power supply in Alternative B mode on the 1000Base-T Ethernet

Data pair

Data pair

Data pair

Data pair

Data pair

Data pair

PD

1

2

4

5

7

83

6

1

2

4

5

7

83

6

PSE

Data pair

Data pair

The S5300 adopts the Endpoint PSE in Alternative A mode.

Working Process of PoE Power Supply

When you deploy a PSE on a network, the working process of PoE on the Ethernet is as follows:

1. Detection: The PSE provides a low voltage on an interface until it detects the PDs that

support IEEE 802.3af or IEEE 802.3at on the cable and are connected to the terminal of

the cable.

2. PD classification: When detecting the PDs, the PSE classifies the PDs and evaluates the

power consumption of the PDs.

3. Starting power-on: In a period shorter than 15 s, the PSE provides low voltage for thePDs, and then the voltage is increased to 48 V DC power supply.





3-5


36/57

4. Power-on: The PSE provides 48 V DC power supply for the PDs and the power

consumption of the PDs is smaller than 30 W.

5. Power-off: If a PD is disconnected from the network, the PSE stops powering on the PD

within 300 ms to 400 ms. Then the PSE detects whether the terminal of the cable is

connected to the PDs.

When you connect any network device to a PSE, the PSE detects whether the device is the PD

supporting PoE. If the PD does not support PoE, the PSE does not provide the current for the

PD. The damage to the deviceis thus prevented. The PSE provides a low voltage of the limited

current for the cable to detect the remote end provides the proper resistance. The PSE provides

48 V voltage only when it detects the resistance, whereas the current is still limited. In this case,

the terminal device can retain in correct state.

In addition, the PSE can classify the PDs so that the PSE can provide power supply efficiently.

When the PSE starting providing power supply, it detects the input current of the PD

continuously. The PSE cuts off the power supply and starts detection again when the current of

the PD is reduced to the minimum value in any of the following situations:l The PD is removed.

l The power consumption of the PD is overloaded or short-circuited.

l The power consumption of the PD exceeds the power supply load.

Intelligent PoE Management

The switch functions as the PSE. When the total power is insufficient, ensure that the core PD

can obtain power from the PSE. On the S5300, each interface supporting PoE provides three

power supply priorities for PDs, that is, critical, high, and low. When the power consumption

of PDs is greater than the total power of the PSE, the S5300 first provides power supply for the

PD with the highest priority of the interface. If different interfaces have the same priority, the

S5300 provides power supply for PDs in descending order of port numbers. The PD with the

smallest port number of the interface first obtains power supply.

Discovery and Advertisement of MDI Power Support Capabilities Through LLDP

IEEE 802.1ab defines the optional TLV: Power via MDI TLV. This TLV allows discovery and

advertisement of Media Dependent Interface (MDI) power support capabilities.

The Power via MDI TLV is composed of 2-byte packet header and 12-byte TLV information

field:

l Figure 3-5shows the format of the TLV packet header.

Figure 3-5TLV packet header

0

TLV information

string length=12

TLV

type=127

6 15

l Figure 3-6shows the format of the TLV information field.

3 PoE





Issue 02 (2010-12-01)


37/57


38/57


39/57

allocated by a PSE to a PD equals the decimal value of this field multiplied by 0.1. For

example, the value 255 indicates that the allocated power is 25.5 W.

3.4 Terms and AbbreviationsAbbreviation Full Spelling

PoE Power over Ethernet

PSE Power-sourcing Equipment

PD Powered Device





3-9


40/57


41/57

4NAPAbout This Chapter

4.1 Introduction to NAP

4.2 References

4.3 Principles



Feature Description - Device Management 4 NAP



4-1


42/57

4.1 Introduction to NAP

Definition

Neighbor Access Protocol (NAP) is a Huawei proprietary protocol designed for implementing

remote configuration and deployment of devices with empty configurations. With NAP,

engineers are able to establish temporary neighbor relationship between devices having empty

configurations and a device in the current network that is physically linked to the devices to be

deployed. In this manner, engineers can perform a remote login from the device in the current

network to any of the devices having an empty configuration, and implement remote

configuration and deployment of the device.

Purpose

As is often the case, when a device is delivered, it is only installed with the necessary software

and lacks specific configurations. This means that, rather than performing a remote login to the

devices to be deployed, engineers have to be on the site to configure the devices and ensure

connectivity of the network. This results in inconvenience in network deployment and extra

operational and delivery costs.

A partial solution, called the Huawei Group Management Protocol (HGMP), is already available

to address this issue. However, HGMP is applicable only to Layer 2 networks, and is applied in

Ethernet environments.

Now, with NAP, a Layer 3 protocol, engineers are able to establish temporary neighbor

relationship between new devices having empty configurations and a device in the current

network that is physically linked to the new devices to be deployed. In this manner, engineerscan perform a remote login from the device in the current network to any of the new devices

having empty configuration, and implement remote configuration and deployment. Extensive

deployment of this protocol is sure to cut costs significantly in terms of network maintenance

and delivery.

Benefits

The NAP protocol greatly reduces the costs of equipment operation, maintenance, and delivery.

4.2 ReferencesNone

4.3 Principles

NAP is a Layer 3 protocol, and is used to perform remote login to a device with an empty

configuration and to configure the device. The NAP connection can be established after the

device to be configured and the master device are physically connected.

As shown in Figure 4-1, Switch A and Switch B are devices in the current network, and

Switch C is a device with an empty configuration. Switch B and Switch C are connected via asingle hop, and both support NAP.

4 NAP





Issue 02 (2010-12-01)


43/57

Figure 4-1Establishing a NAP connection

Network

SwitchAPC SwitchB SwitchC

1

2

3

Master device Slave device

Master interface

Slave interface

1

2

3

NAP negotiation

Remote login

IP address allocation

The phases for establishing a NAP connection are as follows.

1. NAP negotiation

2. IP address allocation

3. Remote login

In the first two phases, that is, NAP negotiation and IP address allocation, a device in the current

network and the device with an empty configuration are respectively the master device and the

slave device, whereas the two physical interfaces connecting the two devices are called the

master interface (on the master device) and the slave interface (on the slave device). In the thirdphase, that is, remote login, the master device and the slave device are respectively the Client

and the Server for performing the NAP login.

Format of the NAP Packet

NAP packets are UDP-encapsulated, and adopt the UDP port numbered 53535. The destination

IP address of the NAP packet is the reserved multicast IP address 224.0.0.128, whereas the

source IP address is the configured IP address of the sending interface. If the sending interface

has no IP address, 0.0.0.0 is used as the source IP address of the NAP packet. The TTL of the

NAP packet is 1. Figure 4-2shows the format of the NAP packet.





4-3


44/57

Figure 4-2Format of the NAP packet

Version

0 4321

Protocol Type Reserved

Length Checksum

.

.

.

TLV1 (n byte)

TLV2 (n byte)

TLVn (n byte)

TLV Number

The following describes the main fields of the NAP packet.

l Version: Version number of NAP. The value is 01.

l Type: Types of NAP packets. Table 4-1lists five types of NAP packets.

Table 4-1Description of fields that indicate the types of NAP packets

Value Type

01 Detection packet

02 Response packet

03 Establish packets (confirming the establishment of neighbor

relationship)

04 Hello packet

05 Close packet

l TLVn: Variable-size TLV data area. This field consists of three parts: data type, data length,

and user data.

Table 4-2lists the TLV data types and their corresponding types of user data.

Table 4-2Mappings between data types and user data in the variable-size TLV data area of the

NAP packet

Type Number Value

01 Primary IP address of the local interface

4 NAP





Issue 02 (2010-12-01)


45/57

Type Number Value

02 Secondary IP address of the local interface

03 Primary IP address of the remote interface

04 Secondary IP address of the remote interface

05 Subnet mask of the IP address

06 Hello interval

07 Name of the local interface

08 Type of the local device

09 ID of the local device

NAP Negotiation

By default, any NAP-supporting device is a slave device, and the interface on the device is the

slave interface, responsible for listening rather than initiating packets. After the NAP master

device and slave device are started, listening is started on the slave interface by default. After

NAP is started on the master interface on the master device, the master device sends a protocol

packet to discover neighbors, and enters the NAP negotiation phase. The NAP negotiation

process is shown in Figure 4-3.

Figure 4-3NAP negotiation process

Master device Slave device

Protocalpacket

Analyzing

ACK

ACK

1. The NAP slave device is started, and listening is started on the slave interface by default.

Then, the slave device waits for a negotiation packet from the master device.

2. The master device sends a negotiation packet from the master interface to discover

neighbors.

3. The slave device receives the NAP negotiation packet and starts to analyze it.





4-5


46/57

4. The master device and the slave device enter the NAP negotiation phase.

5. The slave device receives the neighbor-discovery packet on its slave interface, and sends

a response packet. Then, the master device sends an acknowledge packet to the slave device,

and the NAP neighbor relationship is established.

IP Address Allocation

The master interface and the slave interface need to be configured with two IP addresses out of

two considerations. First, to facilitate the configuration of service IP addresses for the master

and slave interfaces; second, to configure service IP addresses without interrupting the current

NAP login.

In the current system, no secondary IP address can be configured unless there is a primary IP

address. In addition, the primary IP address is necessary for NAP to go up. Therefore, the master

and slave interfaces need to be configured with primary IP addresses first. However, when the

master device uses the primary IP address to telnet to the slave device, the primary IP address

cannot be changed during the telnet operation. This means that the primary IP address cannotbe changed to meet the actual networking requirements.

Therefore, in NAP, two IP addresses - a primary IP address and a secondary IP address - are

allocated to both the master interface and the slave interface on the master device and the slave

device. Primary IP addresses are used for NAP to go Up, whereas in the actual communication

and NAP-based remote login, secondary IP addresses are used to maintain the NAP connection.

By default, NAP automatically allocates IP addresses to the interfaces from the IP address pool

10.167.253.0/24. To avoid conflicting IP addresses, you can manually allocate IP addresses to

the interfaces. In this case, you can specify the NAP IP address pool only. IP addresses in the

NAP IP address pool are automatically calculated according to the NAP address allocation

algorithm. You can also choose to specify four IP addresses that are on the same network segment

instead of specifying the NAP IP address pool.

Remote Login

l After the IP address allocation, a remote login is performed from the master device to the

slave device through Telnet. Then, the interactive interface is displayed for initializing the

configurations on the slave device.

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.

l If, however, the slave device is configured with user name(s) and password(s), you must

enter the correct user name and password to perform a NAP-based remote login to the slave

device.NOTE

The slave device with an empty configuration checks the Telnet 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 of the remote device that initiates the

login is the same as in the login through the console interface on the device that is telneted to, which enjoys

the highest user level. If the Telnet source address is not the NAP address of the master device, the remote

login fails. In this way, the system security of the device with an empty configuration is ensured.

When the NAP-based connection is logged off, the temporary master and secondary IP addresses

allocated for the master and slave devices are automatically released. After all the slave devices

having empty configurations are deployed, the slave interface attribute can be globally disabledon the slave devices to decline any NAP negotiation. In addition, existing neighbor relationships

4 NAP





Issue 02 (2010-12-01)


47/57

and allocated IP addresses are automatically cancelled and released. After the slave interface

attribute is globally disabled on a slave device, interfaces on the slave device can only function

as master interfaces to initiate connections with other devices having empty configurations. In

this way, the network security is ensured by preventing the slave device from responding to

negotiation requests from other master interfaces.


Abbreviations

Abbreviation Full Spelling

HGMP Huawei Group Management Protocol

NAP Neighbor Access Protocol





4-7


48/57


49/57

5StackingAbout This Chapter

5.1 Stacking Overview

5.2 References

5.3 Principles

5.4 Application



Feature Description - Device Management 5 Stacking



5-1


50/57

5.1 Stacking Overview

Definition

Stacking is a technology that enables multiple devices supporting the stacking feature to function

as a logical device.

Purpose

The stacking technology is generally used on enterprise networks, campus networks, and

residential networks to expand device capacities and improve device reliability.

The stacking technology can increase device ports and reduce single-point faults by using the

active/standby mechanism.

Benefits

The stacking technology brings the following benefits to operators:

l Protecting investments during network capacity expansion

l Simplifying configuration and management during capacity expansion: multiple physical

switches form a logical switch

l Improving system reliability by using the redundancy backup mechanism

l Supporting link aggregation between member switches

lProviding more ports and higher bandwidth

5.2 References

None

5.3 Principles

Stacking is enabled on a switch by default. After switches are installed with stack cards and

started, a stack is set up.

Roles of Member Switches

Each switch in a stack is a member switch. Member switches are classified into the following

roles:

l Master switch

A stack has only one master switch. The master switch manages the entire stack system by

assigning stack IDs to member switches, collecting information about the stack topology,

and notifying all the member switches of the topology. A stack ID is similar to a slot ID in

a chassis, and the master switch is similar to the main control board of a chassis-shaped

switch.

l Standby switch

5 Stacking





Issue 02 (2010-12-01)


51/57

A stack has only one standby switch. The standby switch is the backup of the master switch

and is similar to the slave main control board of a chassis-shaped switch. When the master

switch fails, the standby switch takes over all services from the master switch.

l Slave switch

Slave switches implement Layer 2 forwarding based on MAC addresses and Layer 3distributed forwarding based on unicast and multicast routing. A slave switch sends a

topology change notification message to the master switch when detecting that a neighbor

is lost. In a stack, all member switches except the master switch are slave switches. The

standby switch is also a slave switch.

Setting Up a Stack

Before a stack is set up, each switch is an independent entity with its own IP address and needs

to be managed separately. In addition, link aggregation between switches is not supported.

As shown in Figure 5-1, three switches are connected through stack cables to form a ring network

(or a chain network). After the master switch is selected, it selects the standby switch. If themaster switch fails, the standby switch becomes the master switch and manages the entire stack

system. Other switches function as slave switches. All member switches implement Layer 2

forwarding based on MAC addresses and Layer 3 distributed forwarding based on unicast and

multicast routing.

Figure 5-1Setting up a stack

Stack Setup

SwitchA

Master

Stack

SwitchA

SwitchCSwitchB SwitchB

Standby

SwitchC

Slave

After the master switch, standby switch, and slave switches are selected, the master switch

collects the topology report packets sent from all the slave switches, and then generates

forwarding entries accordingly and delivers the entries to all the member switches in the stack.

The process of selecting the master switch is:

l The switches compare their operating status. A switch may be in running or starting state.

The switches in running state are preferred. When switches are in the same state, the switch

running for the longest time is selected as the master switch.

l If the running time of the switches is the same, they compare the priorities. The switch with

the highest priority is selected as the master switch.

l If all the preceding factors are the same, the switches compare their MAC addresses. The

switch with the smallest MAC address is selected as the master switch.

NOTE

If the master switch and slave switches run different software versions, the slave switches synchronize thesoftware version with the master switch after the stack is set up.





5-3


52/57

Adding a Member Switch to a Stack

Figure 5-2illustrates how a new switch is added to a stable stack system.

A switch can be added to a stack system after being powered off or with power-on. In Figure

5-2, the new member switch is powered off before being added to the stack. In Figure 5-4, themember switches are added to a stack with power-on.

Figure 5-2Adding a member switch to a stack

SwitchA

Master

SwitchB

Standby

SwitchC

Slave

SwitchD

Master

Standalone

Stack

Add a member

SwitchB

Standby

SwitchA

Master

SwitchC

Slave

SwitchD

Slave

Stack

The new switch is powered off and connected to the member switches of the stack by using stack

cables. Then the switch is restarted. The new switch is selected as a slave switch after it starts,

and roles of other member switches in the stack remain unchanged. After the election is complete,

the master switch updates the topology information and synchronizes the topology information

to other switches. Then the master switch assigns a stack ID to the new member switch. The

new member switch updates the stack ID, registers to the master switch, synchronizes the

configuration, and then enters the stable running state.

Removing a Member Switch from a Stack

Figure 5-3shows how a slave switch quits a stack. After a member switch is removed, the stack

is affected in the following ways:

l When the master switch is removed, the neighbor switches notify other member switches

of the topology change and update the neighbor information. The standby switch becomes

the master switch. It recalculates the stack topology information, synchronizes the

information to other members, and specifies a new standby switch. Then the stack runs

stably.

l When the standby switch is removed, the master switch specifies a new standby switch,

and then recalculates the stack topology information and synchronizes the information toother member switches.

5 Stacking





Issue 02 (2010-12-01)


53/57

l When a slave switch is removed, the master switch recalculates the stack topology

information and synchronizes the information to other member switches.

Figure 5-3Removing a slave switch from a stack

Remove a member

SwitchB

Standby

SwitchA

Master

SwitchC

Slave

SwitchD

Slave

Stack

SwitchAMaster

SwitchB

Standby

SwitchC

Slave

SwitchD

Master

Stand

alone

Stack

Combining Two Stacks

As shown in Figure 5-4, two stable stacks are combined into one stack. The superior switch

between the master switches of the two stacks is selected as the master switch. The original stack

containing the new master switch remain the original device roles and configurations, and

services in this stack are not affected. Switches in the other stack restart and join the new stack

as slave switches. Then the master switch assigns new stack IDs to the restarted switches and

synchronizes configurations to the switches. Services on these switches are interrupted in this

period.





5-5


54/57

Figure 5-4Combining two stacks

SwitchA

Master

SwitchB

Standby

SwitchC

Slave

Stack 1

SwitchA

Master

SwitchB

Standby

SwitchD

Master

SwitchE

Slave

SwitchD

Slave

SwitchC

Slave

Stack 1

Stack 2

SwitchE

Slave

Merge Stacks

NOTE

The new stack can contain a maximum of nine member switches. In addition, the member switches mustadopt the same hardware model.

Dividing a Stack

A stable stack can be divided into two stacks with power-on. Member switches act differently

after the stack is divided:

l The original master and standby switches are in the same stack after the original stack is

divided.

As shown in Figure 5-5, the master switch recalculates the stack topology and deletes the

removed switches from the topology. The removed slave switches restart after detecting

that the stack packets time out, and then select a new master switch.

5 Stacking





Issue 02 (2010-12-01)


55/57

Figure 5-5Dividing a stack 1

Partition Stack

SwitchA

Master

SwitchB

Standby

SwitchE

Slave

SwitchD

Slave

SwitchC

Slave

Stack 1

SwitchA

Master

SwitchB

Standby

SwitchC

Slave

Stack 1

SwitchD

Master

Stack 2

S

Quidway S5300 - Device Management(V100R005C01_02).pdf

Documents

Transcript of Quidway S5300 - Device Management(V100R005C01_02).pdf