Manual HP 7900

HP FlexFabric 7900 Switch Series
Layer 2LAN Switching

Configuration Guide
Part number: 5998-4281

Software version: Release 2109
Document version: 6W100-20140122
Legal and notice information
Copyright 2014 Hewlett-Packard Development Company, L.P.

No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained
herein.
Contents
Configuring Ethernet interfaces 1

Configuring a management Ethernet interface 1
Ethernet interface naming conventions 1
Configuring common Ethernet interface settings 1
Splitting a 40-GE interface and combining 10-GE breakout interfaces 2
Configuring basic settings of an Ethernet interface 3
Configuring the link mode of an Ethernet interface 4
Configuring jumbo frame support 4
Configuring physical state change suppression on an Ethernet interface 4
Configuring generic flow control on an Ethernet interface 5
Configuring PFC on an Ethernet interface 6
Configuring a Layer 2 Ethernet interface 8
Configuring storm suppression 8
Configuring storm control on an Ethernet interface 9
Displaying and maintaining an Ethernet interface 10
Configuring loopback, null, and inloopback interfaces 12

Configuring a loopback interface 12
Configuring a null interface 13
Configuring an inloopback interface 13
Displaying and maintaining loopback, null, and inloopback interfaces 13
Bulk configuring interfaces 15

Configuration restrictions and guidelines 15
Configuration procedure 15
Displaying and maintaining bulk interface configuration 16
Configuring the MAC address table 17

Overview 17
How a MAC address entry is created 17
Types of MAC address entries 17
Configuring the MAC address table 18
Configuring MAC address entries 18
Adding or modifying a blackhole MAC address entry 19
Adding or modifying a multiport unicast MAC address entry 20
Disabling MAC address learning 21
Configuring the aging timer for dynamic MAC address entries 22
Enabling MAC address synchronization 22
Displaying and maintaining the MAC address table 24
MAC address table configuration example 24
Network requirements 24
Verifying the configuration 25
Configuring MAC Information 26

Configuration guidelines 26
Enabling MAC Information 26
Configuring the MAC Information mode 26
Configuring the MAC change sending interval 27
Configuring the MAC Information queue length 27
MAC Information configuration example 27
i
Configuring Ethernet link aggregation 30

Basic concepts 30
Aggregation group, member port, and aggregate interface 30
Aggregation states of member ports in an aggregation group 30
Operational key 31
Configuration types 31
Link aggregation modes 31
Aggregating links in static mode 32
Choosing a reference port 32
Setting the aggregation state of each member port 32
Aggregating links in dynamic mode 33
LACP 33
How dynamic link aggregation works 34
Load sharing criteria for link aggregation groups 37
Ethernet link aggregation configuration task list 37
Configuring an aggregation group 37
Configuration guidelines 37
Configuring a Layer 2 static aggregation group 38
Configuring a Layer 2 dynamic aggregation group 38
Configuring a Layer 2 aggregate interface 39
Configuring the description of a Layer 2 aggregate interface 39
Specifying ignored VLANs on a Layer 2 aggregate interface 40
Setting the minimum and maximum numbers of Selected ports for an aggregation group 40
Configuring the expected bandwidth of an aggregate interface 41
Shutting down an aggregate interface 41
Restoring the default settings for an aggregate interface 42
Configuring load sharing for link aggregation groups 42
Configuring load sharing criteria for link aggregation groups 42
Enabling local-first load sharing for link aggregation 43
Enabling link-aggregation traffic redirection 44
Displaying and maintaining Ethernet link aggregation 44
Ethernet link aggregation configuration examples 45
Layer 2 static aggregation configuration example 45
Layer 2 dynamic aggregation configuration example 47
Layer 2 aggregation load sharing configuration example 48
Configuring port isolation 52

Assigning ports to an isolation group 52
Displaying and maintaining port isolation 52
Port isolation configuration example 53
Configuring spanning tree protocols 55

STP 55
STP protocol packets 55
Basic concepts in STP 56
Calculation process of the STP algorithm 57
RSTP 62
ii
MSTP 62
MSTP features 62
MSTP basic concepts 62
How MSTP works 66
MSTP implementation on devices 67
Protocols and standards 67
Spanning tree configuration task lists 67
STP configuration task list 68
RSTP configuration task list 68
MSTP configuration task list 69
Setting the spanning tree mode 70
Configuring an MST region 71
Configuring the root bridge or a secondary root bridge 72
Configuring the current device as the root bridge of a specific spanning tree 72
Configuring the current device as a secondary root bridge of a specific spanning tree 72
Configuring the device priority 73
Configuring the maximum hops of an MST region 73
Configuring the network diameter of a switched network 73
Configuring spanning tree timers 74
Configuring the timeout factor 75
Configuring the BPDU transmission rate 76
Configuring edge ports 76
Configuring path costs of ports 77
Specifying a standard for the device to use when it calculates the default path cost 77
Configuring path costs of ports 78
Configuration example 79
Configuring the port priority 79
Configuring the port link type 80
Configuring the mode a port uses to recognize and send MSTP packets 80
Enabling outputting port state transition information 81
Enabling the spanning tree feature 81
Performing mCheck 82
Performing mCheck globally 82
Performing mCheck in interface view 82
Configuring Digest Snooping 83
Digest Snooping configuration example 84
Configuring No Agreement Check 85
Configuration prerequisites 86
No Agreement Check configuration example 87
Configuring protection functions 87
Enabling BPDU guard 87
Enabling root guard 88
Enabling loop guard 88
Configuring port role restriction 89
iii
Configuring TC-BPDU transmission restriction 90
Enabling TC-BPDU guard 90
Displaying and maintaining the spanning tree 91
Spanning tree configuration example 91
Configuring loop detection 96

Overview 96
Loop detection mechanism 96
Loop detection interval 97
Loop protection actions 97
Port status auto recovery 97
Loop detection configuration task list 98
Enabling loop detection 98
Enabling loop detection globally 98
Enabling loop detection on a port 98
Configuring the loop protection action 98
Configuring the global loop protection action 99
Configuring the loop protection action on a Layer 2 Ethernet interface 99
Configuring the loop protection action on a Layer 2 aggregate interface 99
Setting the loop detection interval 99
Displaying and maintaining loop detection 100
Loop detection configuration example 100
Configuring VLANs 103

Overview 103
VLAN frame encapsulation 103
Configuring basic VLAN settings 104
Configuring basic settings of a VLAN interface 105
Configuring port-based VLANs 106
Introduction to port-based VLAN 106
Assigning an access port to a VLAN 107
Assigning a trunk port to a VLAN 108
Assigning a hybrid port to a VLAN 109
Displaying and maintaining VLANs 110
Port-based VLAN configuration example 110
Configuring LLDP 113

Overview 113
Basic concepts 113
Work mechanism 118
LLDP configuration task list 119
Performing basic LLDP configuration 119
Enabling LLDP 119
Configuring the LLDP bridge mode 120
Setting the LLDP operating mode 120
iv
Setting the LLDP re-initialization delay 121
Enabling LLDP polling 121
Configuring the advertisable TLVs 122
Configuring the management address and its encoding format 123
Setting other LLDP parameters 124
Setting an encapsulation format for LLDPDUs 125
Configuring CDP compatibility 125
Configuration prerequisites 126
Configuring LLDP trapping and LLDP-MED trapping 126
Displaying and maintaining LLDP 127
LLDP configuration example 128
Support and other resources 133

Contacting HP 133
Subscription service 133
Related information 133
Documents 133
Websites 133
Conventions 134
Index 136
v
Configuring Ethernet interfaces
The switch series supports Ethernet interfaces, management Ethernet interfaces, and Console interfaces.
For the interface types and the number of interfaces supported by a switch model, see the installation
guide.
This document describes how to configure management Ethernet interfaces and Ethernet interfaces.
Configuring a management Ethernet interface

A management interface uses an RJ-45 connector. You can connect the interface to a PC for software
loading and system debugging.
To configure a management Ethernet interface:
Step Command Remarks

1. Enter system view. system-view N/A
2. Enter management interface M-GigabitEthernet
N/A
Ethernet interface view. interface-number
3. (Optional.) Set the The default setting is
description text
interface description. M-GigabitEthernet0/0/0 Interface.
4. (Optional.) Shut down By default, the management Ethernet
shutdown
the interface. interface is up.
Ethernet interface naming conventions

For a switch in an IRF fabric, its Ethernet interfaces are numbered in the format of interface type
A/B/C/D; for a switch not in any IRF fabric, its Ethernet interfaces are numbered in the format of
interface type B/C/D, where the following definitions apply:
ANumber of the switch in an IRF fabric.
BSlot number of the card in the switch.
CSub-slot number on a card.
DNumber of an interface on a card.
Configuring common Ethernet interface settings

This section describes the settings common to Layer 2 Ethernet interfaces and Layer 3 Ethernet interfaces.
You can set an Ethernet port as a Layer 3 interface by using the port link-mode route command. For more
information, see "Configuring the link mode of an Ethernet interface." For more information about the
settings specific to Layer 2 Ethernet interfaces, see "Configuring a Layer 2 Ethernet interface."
1
Splitting a 40-GE interface and combining 10-GE breakout
interfaces
Splitting a 40-GE interface into four 10-GE breakout interfaces
You can use a 40-GE interface as a single interface. To improve port density, reduce costs, and improve
network flexibility, you can also split a 40-GE interface into four 10-GE breakout interfaces.
For example, you can split a 40-GE interface FortyGigE 1/0/16 into four 10-GE breakout interfaces
Ten-GigabitEthernet 1/0/16:1 through Ten-GigabitEthernet 1/0/16:4.
To split a 40-GE interface into four 10-GE breakout interfaces:

interface interface-type
2. Enter 40-GE interface view. N/A
interface-number
By default, a 40-GE interface is not

split and operates as a single
interface.
The 10-GE breakout interfaces
split from a 40-GE interface
support the same configuration
3. Split the 40-GE interface into
and attributes as common 10-GE
four 10-GE breakout using tengige
interfaces, except that they are
interfaces.
numbered differently.
A 40-GE interface split into four
10-GE breakout interfaces must
use a dedicated 1-to-4 cable or a
1-to-4 fiber and transceiver
modules.
After creating the four 10-GE

4. Reboot the card that houses
N/A breakout interfaces, the system
the interface.
removes the 40-GE interface.
Combining four 10-GE breakout interfaces into a 40-GE interface

If you need higher bandwidth, you can combine the four 10-GE breakout interfaces into a 40-GE
interface.
To combine four 10-GE breakout interfaces into a 40-GE interface:

2. Enter the view of any 10-GE
breakout interface split from a N/A
interface-number
40-GE interface.
2
By default, a 40-GE interface is not
split and operates as a single
interface.
The 40-GE interface combined
3. Combine the four 10-GE from the four 10-GE breakout
breakout interfaces into a using fortygige interfaces must use a dedicated
40-GE interface. 1-to-1 cable or a 40-GE transceiver
module and fiber. For more
information about the cable and
transceiver module, see the
installation guide.
After creating the 40-GE interface,

4. Reboot the card that houses
N/A the system removes the four 10-GE
the interface.
breakout interfaces.
Configuring basic settings of an Ethernet interface

You can set an Ethernet interface to operate in one of the following duplex modes:
Full-duplex mode (full)Interfaces can send and receive packets simultaneously.
Half-duplex mode (half)Interfaces cannot send and receive packets simultaneously.
Autonegotiation mode (auto)Interfaces negotiate a duplex mode with their peers.
You can set the speed of an Ethernet interface or enable it to automatically negotiate a speed with its
peer.
To configure an Ethernet interface:

2. Enter Ethernet interface interface interface-type
N/A
view. interface-number
The default setting is in the format of

3. Set the interface
description text interface-name Interface. For example,
description.
FortyGigE1/0/1 Interface.
4. Set the duplex mode of The default setting is auto for Ethernet
duplex { auto | full }
the Ethernet interface. interfaces.
The default setting is auto for Ethernet

5. Set the port speed. speed { 40000 | auto }
interfaces.
6. Configure the expected By default, the expected bandwidth (in
bandwidth of the bandwidth bandwidth-value kbps) is the interface baud rate divided by
interface. 1000.
7. Restore the default
settings for the Ethernet default N/A
interface.
8. Bring up the Ethernet By default, Ethernet interfaces are in up
undo shutdown
interface. state.
3
Configuring the link mode of an Ethernet interface
CAUTION:
After you change the link mode of an Ethernet interface, all commands (except the shutdown command)
on the Ethernet interface are restored to their defaults in the new link mode.
On the switch, Ethernet interfaces can operate either as Layer 2 or Layer 3 Ethernet interfaces (you can
set the link mode to bridge or route).
To change the link mode of an Ethernet interface:

2. Enter Ethernet interface view. N/A
interface-number
3. Change the link mode of the By default, an Ethernet interface
port link-mode { bridge | route }
Ethernet interface. operates in bridge mode.
Configuring jumbo frame support

An Ethernet interface might receive some frames larger than the standard Ethernet frame size (called
"jumbo frames") during high-throughput data exchanges, such as file transfers. When the Ethernet
interface is configured to deny jumbo frames, the Ethernet interface discards jumbo frames without
further processing. When the Ethernet interface is configured with jumbo frame support, the Ethernet
interface processes jumbo frames within the specified length.
To configure jumbo frame support in interface view:

N/A
By default, the device allows jumbo

frames within 12288 bytes to pass
3. Configure jumbo frame through Ethernet interfaces.
jumboframe enable [ value ]
support. If you set the value argument multiple
times, the most recent configuration
takes effect.
Configuring physical state change suppression on an Ethernet

interface
The physical link state of an Ethernet interface is either up or down. Each time the physical link of a port
goes up or comes down, the interface immediately reports the change to the CPU. The CPU then notifies
the upper-layer protocol modules (such as routing and forwarding modules) of the change for guiding
4
packet forwarding, and automatically generates traps and logs, informing the user to take
corresponding actions.
To prevent frequent physical link flapping from affecting system performance, configure physical state
change suppression to suppress the reporting of physical link state changes. The system reports physical
layer changes only when the suppression interval expires.
To configure physical state change suppression on an Ethernet interface:

2. Enter Ethernet interface interface-type
N/A
interface view. interface-number
By default, each time the physical link of a port

comes down, the interface immediately reports the
change to the CPU.
3. Set the link-down When this command is configured:
event suppression link-delay delay-time The link-down event is not reported to the CPU
interval. until the interface is still down when the
suppression interval (delay-time) expires.
The link-up event is immediately reported when
the interface goes up.

goes up, the interface immediately reports the
change to the CPU.
4. Set the link-up event link-delay [ msec ] When this command is configured:
suppression interval. delay-time mode up The link-up event is not reported to the CPU until
the interface is still up when the suppression
interval (delay-time) expires.
The link-down event is immediately reported.
goes up or comes down, the interface immediately
5. Set the link-updown reports the change to the CPU.
link-delay [ msec ]
event suppression When this command is configured, the link-up or
delay-time mode updown
interval. link-down event is not reported to the CPU until the
interface is still up or down when the suppression
interval (delay-time) expires.
The link-delay command and the link-delay mode command overwrite each other, and whichever is
configured last takes effect.
Do not configure physical state change suppression on a port with RRPP or MSTP enabled.
Configuring generic flow control on an Ethernet interface

To avoid packet drops on a link, you can enable generic flow control at both ends of the link. When
traffic congestion occurs at the receiving end, the receiving end sends a flow control (Pause) frame to ask
the sending end to suspend sending packets.
5
With TxRx mode generic flow control enabled, an interface can both send and receive flow control
frames. When congestion occurs, the interface sends a flow control frame to its peer. When the
interface receives a flow control frame from the peer, it suspends sending packets.
With Rx flow mode generic control enabled, an interface can receive flow control frames, but it
cannot send flow control frames. When the interface receives a flow control frame from its peer, it
suspends sending packets to the peer. When congestion occurs, the interface cannot send flow
control frames to the peer.
As shown in Figure 1, when both Port A and Port B forward packets at the rate of 1000 Mbps, Port C will
be congested. To avoid packet loss, enable flow control on Port A and Port B.
Figure 1 Flow control on ports
When TxRx mode generic flow control is enabled on Port B and Rx mode generic flow control is enabled
on Port A:
When Port C is congested, Switch B buffers the packet. When the buffered packets reach a specific
size, Switch B learns that the traffic forwarded from Port B to Port C is too heavy and exceeds the
forwarding capability of Port C. In this case, Port B with TxRx mode generic flow control enabled
sends generic pause frames to Port A and tells Port A to suspend sending packets.
When Port A receives the generic pause frames, Port A suspends sending packets to Port B for a
certain period, which is carried in the generic pause frames. Port B sends generic pause frames to
Port A until congestion is removed.
To handle unidirectional traffic congestion on a link, configure the flow-control receive enable command
at one end and the flow-control command at the other end. To enable both ends of a link to handle traffic
congestion, configure the flow-control command at both ends.
To enable generic flow control on an Ethernet interface:

N/A
Enable TxRx mode generic
flow control:
flow-control By default, generic flow control is
3. Enable generic flow control.
Enable Rx mode generic flow disabled on an Ethernet interface.
control:
flow-control receive enable
Configuring PFC on an Ethernet interface

PFC performs flow control based on 802.1p priorities. With PFC enabled, an interface requires its peer
to suspend sending packets with the specified 802.1p priorities when congestion occurs. By decreasing
the transmission rate, PFC helps avoid packet loss.
6
You can enable PFC for the specified 802.1p priorities at the two ends of a link. When network
congestion occurs, the local device checks the PFC status for the 802.1p priority carried in each arriving
packet. The device processes the packet depending on the PFC status as follows:
If PFC is enabled for the 802.1p priority, the local device accepts the packet and sends a PFC pause
frame to the peer. The peer stops sending packets carrying this 802.1p priority for an interval as
specified in the PFC pause frame. This process is repeated until the congestion is removed.
If PFC is disabled for the 802.1p priority, the local port drops the packet.
To configure PFC on an Ethernet interface:

interface-number
3. Enable PFC on the interface
priority-flow-control { auto |
through automatic negotiation By default, PFC is disabled.
enable }
or forcibly.
4. Enable PFC for specific priority-flow-control no-drop By default, PFC is disabled for all
802.1p priorities. dot1p dot1p-list 802.1p priorities.
When you configure PFC, follow these guidelines:

To perform PFC on a network port of an IRF member device, configure PFC on both the network port
and the IRF physical ports. For information about IRF, see IRF configuration Guide.
To ensure correct operations of IRF and other protocols, HP recommends not enabling PFC for
802.1p priorities 0, 6, and 7.
Perform the same PFC configuration on all ports that traffic travels through.
A port can receive PFC pause frames whether or not PFC is enabled on the port. However, only a
port with PFC enabled can process PFC pause frames. To make PFC take effect, make sure PFC is
enabled on both the local end and the peer end.
The relationship between the PFC function and the generic flow control function is shown in Table 1.
Table 1 The relationship between the PFC function and the generic flow control function
priority-flo
priority-flow-contr
flow-control w-control Remarks
ol no-drop dot1p
enable
You cannot enable flow control by using the
flow-control command on a port where PFC is
Unconfigurable Configured Configured
enabled and PFC is enabled for the specified
802.1p priority values.
7
priority-flo
priority-flow-contr
flow-control w-control Remarks
ol no-drop dot1p
enable
On a port configured with the flow-control
command, you can enable PFC, but you
cannot enable PFC for specific 802.1p
priorities.
Enabling both generic flow control and PFC on
Configured Configurable Unconfigurable
a port disables the port from sending common
or PFC pause frames to inform the peer of
congestion conditions. However, the port can
still handle common and PFC pause frames
from the peer.
Configuring a Layer 2 Ethernet interface

Configuring storm suppression
You can use the storm suppression function to limit the size of a particular type of traffic (broadcast,
multicast, or unknown unicast traffic) on an interface. When the broadcast, multicast, or unknown unicast
traffic on the interface exceeds this threshold, the system discards packets until the traffic drops below this
threshold.
Any of the storm-constrain, broadcast-suppression, multicast-suppression, and unicast-suppression
commands can suppress storm on a port. The broadcast-suppression, multicast-suppression, and
unicast-suppression commands suppress traffic in hardware, and have less impact on device
performance than the storm-constrain command, which performs suppression in software.
Configuration guidelines
For the same type of traffic, do not configure the storm constrain command together with any of the
broadcast-suppression, multicast-suppression, and unicast-suppression commands. Otherwise, the
traffic suppression result is not determined. For more information about the storm-constrain command,
see "Configuring storm control on an Ethernet interface."
Configuration procedure
To set storm suppression thresholds on one or multiple Ethernet interfaces:

interface-number
3. Enable broadcast suppression By default, broadcast traffic is
broadcast-suppression { ratio |
and set the broadcast allowed to pass through an
pps max-pps | kbps max-kbps }
suppression threshold. interface.
4. Enable multicast suppression By default, multicast traffic is
multicast-suppression { ratio | pps
and set the multicast allowed to pass through an
max-pps | kbps max-kbps }
suppression threshold. interface.
8
5. Enable unknown unicast
By default, unknown unicast traffic
suppression and set the unicast-suppression { ratio | pps
is allowed to pass through an
unknown unicast suppression max-pps | kbps max-kbps }
interface.
threshold.
Configuring storm control on an Ethernet interface

About storm control
Storm control compares broadcast, multicast, and unknown unicast traffic regularly with their respective
traffic thresholds on an Ethernet interface. For each type of traffic, storm control provides a lower
threshold and a higher threshold.
For management purposes, you can configure the interface to output threshold event traps and log
messages when monitored traffic exceeds the upper threshold or falls below the lower threshold from the
upper threshold.
Depending on your configuration, when a particular type of traffic exceeds its upper threshold, the
interface does either of the following:
Blocks this type of traffic, while forwarding other types of trafficEven though the interface does
not forward the blocked traffic, it still counts the traffic. When the blocked traffic drops below the
lower threshold, the port begins to forward the traffic.
Shuts down automaticallyThe interface shuts down automatically and stops forwarding any
traffic. When the blocked traffic is detected dropping below the lower threshold, the port does not
forward the traffic. To bring up the interface, use the undo shutdown command or disable the storm
control function.
Any of the storm-constrain, broadcast-suppression, multicast-suppression, and unicast-suppression
commands can suppress storm on a port. The broadcast-suppression, multicast-suppression, and
unicast-suppression commands suppress traffic in hardware, and have less impact on device
performance than the storm-constrain command, which performs suppression in software.
Storm control uses a complete polling cycle to collect traffic data, and analyzes the data in the next cycle.
An interface takes one to two polling intervals to take a storm control action.
For the same type of traffic, do not configure the storm constrain command together with any of the
broadcast-suppression, multicast-suppression, and unicast-suppression commands. Otherwise, the
traffic suppression result is not determined. For more information about the broadcast-suppression,
multicast-suppression, and unicast-suppression commands, see "Configuring storm suppression."
To configure storm control on an Ethernet interface:

9
The default setting is 10 seconds.
2. (Optional.) Set the traffic
polling interval of the storm storm-constrain interval seconds For network stability, use the
control module. default or set a higher traffic
polling interval (10 seconds).
interface-number
4. (Optional.) Enable storm
storm-constrain { broadcast |
control, and set the lower and
multicast | unicast } { pps | kbps | By default, storm control is
upper thresholds for
ratio } max-pps-values disabled.
broadcast, multicast, or
min-pps-values
unknown unicast traffic.
5. Set the control action to take
storm-constrain control { block | By default, storm control is
when monitored traffic
shutdown } disabled.
exceeds the upper threshold.
By default, the interface outputs log

6. (Optional.) Enable the messages when monitored traffic
interface to log storm control storm-constrain enable log exceeds the upper threshold or
threshold events. falls below the lower threshold
from the upper threshold.
By default, the interface sends

7. (Optional.) Enable the traps when monitored traffic
interface to send storm control storm-constrain enable trap exceeds the upper threshold or
threshold event traps. drops below the lower threshold
from the upper threshold.
Displaying and maintaining an Ethernet interface

Execute display commands in any view and reset commands in user view.
Task Command
display counters { inbound | outbound } interface [ interface-type
Display interface traffic statistics.
[ interface-number ] ]
Display traffic rate statistics of interfaces in display counters rate { inbound | outbound } interface
up state over the last sampling interval. [ interface-type [ interface-number ] ]
Display the operational and status

information of the specified interface or all display interface [ interface-type [ interface-number ] ]
interfaces.
Display summary information about the display interface [ interface-type [ interface-number ] ] brief
specified interface or all interfaces. [ description ]
Display information about dropped

display packet-drop { interface [ interface-type
packets on the specified interface or all
[ interface-number ] ] | summary }
interfaces.
Display information about storm control display storm-constrain [ broadcast | multicast | unicast ]
on the specified interface or all interfaces. [ interface interface-type interface-number ]
Display the Ethernet module statistics. display ethernet statistics
10
Task Command
Clear the interface statistics. reset counters interface [ interface-type [ interface-number ] ]
Clear the statistics of dropped packets on

reset packet-drop interface [ interface-type [ interface-number ] ]
the specified interfaces.
Clear the Ethernet module statistics. reset ethernet statistics
11
Configuring loopback, null, and inloopback
interfaces
This chapter describes how to configure a loopback interface, a null interface, and an inloopback
interface.
Configuring a loopback interface

A loopback interface is a virtual interface. The physical layer state of a loopback interface is always up
unless the loopback interface is manually shut down. Because of this benefit, loopback interfaces are
widely used in the following scenarios:
Configuring a loopback interface address as the source address of the IP packets that the device
generatesBecause loopback interface addresses are stable unicast addresses, they are usually
used as device identifications.
{ When you configure a rule on an authentication or security server to permit or deny packets that
a device generates, you can simplify the rule by configuring it to permit or deny packets
carrying the loopback interface address that identifies the device.
{ When you use a loopback interface address as the source address of IP packets, make sure the
route from the loopback interface to the peer is reachable by performing routing configuration.
All data packets sent to the loopback interface are considered packets sent to the device itself,
so the device does not forward these packets.
Using a loopback interface in dynamic routing protocolsWith no router ID configured for a
dynamic routing protocol, the system selects the highest loopback interface IP address as the router
ID. In BGP, to avoid interruption of BGP sessions due to physical port failure, you can use a
loopback interface as the source interface of BGP packets.
To configure a loopback interface:

2. Create a loopback interface
interface loopback
and enter loopback interface N/A
interface-number
view.
The default setting is interface name

3. Set the interface description. description text Interface (for example, LoopBack1
Interface).
4. Configure the expected
By default, the expected bandwidth
bandwidth of the loopback bandwidth bandwidth-value
of a loopback interface is 0 kbps.
interface.
5. Restore the default settings for
default N/A
the loopback interface.
6. Bring up the loopback
undo shutdown By default, a loopback interface is up.
interface.
12
Configuring a null interface
A null interface is a virtual interface and is always up, but you can neither use it to forward data packets
nor can you configure it with an IP address or link layer protocol. The null interface provides a simpler
way to filter packets than ACL. You can filter undesired traffic by transmitting it to a null interface instead
of applying an ACL. For example, if you specify a null interface as the next hop of a static route to a
specific network segment, any packets routed to the network segment are dropped.
To configure a null interface:

Interface Null 0 is the default null

interface on the device and cannot
be manually created or removed.
2. Enter null interface view. interface null 0
Only one null interface, Null 0, is
supported on the device. The null
interface number is always 0.
3. Set the interface description. description text The default setting is NULL0 Interface.
4. Restore the default settings for
default N/A
the null interface.
Configuring an inloopback interface

An inloopback interface is a virtual interface created by the system, which cannot be configured or
deleted. The physical layer and link layer protocol states of an inloopback interface are always up. All
IP packets sent to an inloopback interface are considered packets sent to the device itself and are not
further forwarded.
Displaying and maintaining loopback, null, and

inloopback interfaces
Task Command
display interface [ loopback ] [ brief [ down ] ]
Display information about the specified or all
loopback interfaces. display interface [ loopback [ interface-number ] ] [ brief
[ description ] ]
Display information about the null interface. display interface [ null [ 0 ] ] [ brief [ description ] ]
Display information about the inloopback

display interface [ inloopback [ 0 ] ] [ brief [ description ] ]
interface.
Clear the statistics on the specified or all loopback

reset counters interface loopback [ interface-number ]
interfaces.
Clear the statistics on the null interface. reset counters interface [ null [ 0 ] ]
13
Task Command
Clear the statistics on the inloopback interface. reset counters interface
14
Bulk configuring interfaces
You can enter interface range view to bulk configure multiple interfaces with the same feature instead of
configuring them one by one. For example, you can execute the shutdown command in interface range
view to shut down a range of interfaces.
If a command fails to take effect on the first interface in an interface range, the command does not take
effect on all the other member interfaces. Failure to apply a command on a member interface except for
the first interface does not affect the application of the command on the other member interfaces.
Configuration restrictions and guidelines

When you bulk configure interfaces in interface range view, follow these restrictions and guidelines:
In interface range view, only the commands supported by the first interface are available. The first
interface is specified with the interface range command.
If you cannot enter the view of an interface by using the interface interface-type interface-number
command, do not configure the interface as the first interface in the interface range.
Do not assign an aggregate interface and any of its member interfaces to an interface range at the
same time. Some commands, after being executed on both an aggregate interface and its member
interfaces, can break up the aggregation.
No limit is set on the maximum number of interfaces in an interface range. The more interfaces in
an interface range, the longer the command execution time.
The maximum number of interface range names is only limited by the system resources. To
guarantee bulk interface configuration performance, HP recommends that you configure fewer than
1000 interface range names.
interface range { interface-type
interface-number [ to
Use either command.
interface-type
interface-number ] } &<1-5> By using the interface range name
2. Enter interface range command, you assign a name to an
view. interface range name name
interface range and can specify this
[ interface { interface-type
name rather than the interface range to
interface-number [ to
enter the interface range view.
interface-type
interface-number ] } &<1-5> ]
3. (Optional.) Display
commands available for Enter a question mark (?) at the
N/A
the first interface in the interface range prompt.
interface range.
15
4. Use available
Available commands vary by
commands to configure N/A
interface.
the interfaces.
5. (Optional.) Verify the

display this N/A
configuration.
Displaying and maintaining bulk interface

configuration
Execute display commands in any view.
Task Command
Display information about interface ranges configured
display interface range [ name name ]
through the interface range name command.
16
Configuring the MAC address table
Overview
An Ethernet device uses a MAC address table to forward frames. A MAC address entry contains a
destination MAC address, an outgoing interface, and a VLAN ID. Upon receiving a frame, the device
uses the destination MAC address of the frame to look for a match in the MAC address table. If a match
is found, the device forwards the frame out of the outgoing interface in the matching entry. If no match
is found, the device floods the frame to all interfaces in the same VLAN as the incoming interface.
How a MAC address entry is created

The entries in the MAC address table originate from two sources: automatically learned by the device
and manually added by the administrator.
MAC address learning

The device can automatically populate its MAC address table by learning the source MAC addresses of
incoming frames on each interface.
When a frame arrives at an interface (for example, Port A), the device performs the following tasks:
1. Checks the source MAC address (for example, MAC-SOURCE) of the frame.
2. Looks up the source MAC address in the MAC address table.
{ If an entry is found, the device updates the entry.
{ If no entry is found, the device adds an entry for MAC-SOURCE and Port A.
3. When the device receives a frame destined for MAC-SOURCE after learning this source MAC
address, the device finds the MAC-SOURCE entry in the MAC address table and forwards the
frame out of Port A.
The device performs the learning process each time it receives a frame from an unknown source MAC
address until the MAC address table is fully populated.
Manually configuring MAC address entries

With dynamic MAC address learning, a device does not distinguish between illegitimate and legitimate
frames, which can invite security hazards. For example, when an illegal user sends frames with a forged
source MAC address to an interface different from the one where the real MAC address is associated, the
device creates an entry for the forged MAC address, and forwards frames destined for the legal user to
the illegal user instead.
To improve interface security and prevent illegal users from stealing data, you can manually add MAC
address entries to the MAC address table of the device to bind specific user devices to the interface.
Types of MAC address entries

A MAC address table can contain the following types of entries:
17
Static entriesStatic entries are manually added in order to forward frames with a specific
destination MAC address out of their associated interfaces and never age out. A static entry has
higher priority than a dynamically learned one.
Dynamic entriesDynamic entries can be manually configured or dynamically learned in order to
forward frames with a specific destination MAC address out of their associated interfaces and
might age out. A manually configured dynamic entry has the same priority as a dynamically
learned one.
Blackhole entriesBlackhole entries are manually configured and never age out. Blackhole entries
are configured for filtering out frames with a specific destination MAC address. For example, to
block all frames destined for a specific user for security concerns, you can configure the MAC
address of this user as a blackhole MAC address entry.
Multiport unicast entriesMultiport unicast entries are manually added in order to send frames
with a specific unicast destination MAC address out of multiple ports and never age out. A multiport
unicast entry has higher priority than a dynamically learned one.
A static, blackhole, or multiport unicast MAC address entry can overwrite a dynamic MAC address entry,
but not vice versa.
Configuring the MAC address table

The configuration tasks discussed in the following sections are all optional and can be performed in any
order.
This document covers only the configuration of unicast MAC address entries, including static, dynamic,
blackhole, and multiport unicast MAC address entries. For information about configuring static multicast
MAC address entries, see IP Multicast Configuration Guide.
Configuring MAC address entries

When you configure a dynamic MAC address entry, if an automatically learned MAC address
entry with the same MAC address but a different outgoing interface already exists in the MAC
address table, the manually configured one overwrites the automatically learned MAC address
entry.
The manually configured static, blackhole, and multiport unicast MAC address entries cannot
survive a reboot if you do not save the configuration. The manually configured dynamic MAC
address entries, however, are lost upon reboot whether or not you save the configuration.
A frame whose source MAC address matches different types of MAC address entries is differently
processed.
Type Description
Discards the frame entered on a different interface from that in the entry.
Static MAC address entry
Forwards the frame entered on the same interface with that in the entry.
Learns the MAC address (for example, MAC A) of the frame, adds a dynamic
Multiport unicast MAC MAC address entry for MAC A, and forwards the frame.
address entry Forwards the frames destined for MAC A according to only the multiport
unicast MAC address entry.
18
Type Description
Learns the MAC address of the frame entered on a different interface from
Dynamic MAC address that in the entry and overwrites the original entry.
entry Forwards the frame entered on the same interface with that in the entry and
updates the aging timer for the entry.
Adding or modifying a static or dynamic MAC address entry globally

By default, no MAC address

2. Add or modify a
mac-address { dynamic | static } mac-address entry is configured globally.
static or dynamic
interface interface-type interface-number vlan Make sure you have created
MAC address
vlan-id the VLAN and assigned the
entry.
interface to the VLAN.
Adding or modifying a static or dynamic MAC address entry on an interface

Enter Layer 2 Ethernet interface
view:
interface-number
2. Enter interface view. N/A
Enter Layer 2 aggregate
interface view:
interface bridge-aggregation
interface-number
By default, no MAC address entry

is configured on an interface.
3. Add or modify a static or mac-address { dynamic | static }
dynamic MAC address entry. mac-address vlan vlan-id Make sure you have created the
VLAN and assigned the interface
to the VLAN.
Adding or modifying a blackhole MAC address entry

By default, no blackhole MAC

2. Add or modify a blackhole mac-address blackhole address entry is configured.
MAC address entry. mac-address vlan vlan-id Make sure you have created the
VLAN.
19
Adding or modifying a multiport unicast MAC address entry
You can configure a multiport unicast MAC address entry to associate a unicast destination MAC
address with multiple ports, so that the frame with a destination MAC address matching the entry is
forwarded out of multiple ports. For example, in NLB unicast mode, all servers within the cluster uses the
cluster's MAC address as their own address, and frames destined for the cluster are forwarded to every
server. In this case, you can configure a multiport unicast MAC address entry on the device connected to
the group of servers. In this manner, the device forwards the frame destined for the server group through
all ports connected to the servers within the cluster.
Figure 2 NLB cluster
Device
NLB cluster
You can configure a multiport unicast MAC address entry globally or on an interface.
Configuring a multiport unicast MAC address entry globally

By default, no multiport unicast

MAC address entry is configured
globally.
Make sure you have created the
to the VLAN.
mac-address multiport
2. Add or modify a multiport
mac-address interface interface-list Do not configure an interface as
unicast MAC address entry.
vlan vlan-id the output interface of a multiport
unicast MAC address entry if the
interface receives frames destined
for the multiport unicast MAC
address. Otherwise, the frames are
flooded in the VLAN to which they
belong.
Configuring a multiport unicast MAC address entry on an interface

20
view:
interface-number
interface view:
interface-number
By default, no multiport unicast

MAC address entry is configured
on an interface.
Make sure you have created the
to the VLAN.
3. Add the interface to a
mac-address multiport Do not configure an interface as
multiport unicast MAC
mac-address vlan vlan-id the output interface of a multiport
address entry.
unicast MAC address entry if the
interface receives frames destined
for the multiport unicast MAC
address. Otherwise, the frames are
flooded in the VLAN to which they
belong.
Disabling MAC address learning

MAC address learning is enabled by default. To prevent the MAC address table from being saturated
when the device is experiencing attacks, disable MAC address learning. For example, you can disable
MAC address learning to prevent the device from being attacked by a large amount of frames with
different source MAC addresses.
When MAC address learning is disabled, the learned dynamic MAC addresses remain valid until they
age out.
Disabling global MAC address learning

2. Disable global MAC address undo mac-address mac-learning By default, global MAC address
learning. enable learning is enabled.
Disabling global MAC address learning disables the learning function on all interfaces.
Disabling MAC address learning on interfaces

With global MAC address learning enabled, you can disable MAC address learning on a single
interface.
To disable MAC address learning on an interface:
21
view:
interface-number
Enter Layer 2 aggregate interface
view:
interface-number
By default, MAC address

3. Disable MAC address undo mac-address mac-learning
learning on the interface is
learning on the interface. enable
enabled.
Configuring the aging timer for dynamic MAC address entries

The MAC address table uses an aging timer for dynamic MAC address entries for security and efficient
use of table space. If a dynamic MAC address entry has failed to update before the aging timer expires,
the device deletes the entry. This aging mechanism makes sure the MAC address table could promptly
update to accommodate latest network topology changes.
Set the aging timer appropriately. A stable network requires a longer aging interval and an unstable
network requires a shorter aging interval. A too long aging interval might cause the MAC address table
to retain outdated entries, exhaust the MAC address table resources, and fail to update its entries to
accommodate the latest network changes. A too short interval might result in removal of valid entries,
causing unnecessary floods, which might increase network burden.
You can reduce floods on a stable network by setting a long aging timer or disabling the aging timer to
prevent dynamic entries from unnecessarily aging out. By reducing floods, you improve not only network
performance, but also security, because the chances for a data frame to reach unintended destinations
are reduced.
To configure the aging timer for dynamic MAC address entries:

By default, the aging timer for

2. Configure the aging timer for dynamic MAC address entries is
mac-address timer { aging seconds 300 seconds.
dynamic MAC address
| no-aging }
entries. The no-aging keyword disables the
aging timer.
Enabling MAC address synchronization

To avoid unnecessary floods and improve forwarding speed, make sure all cards possess the same MAC
address table. After you enable MAC address table synchronization, each card advertises learned MAC
address entries to other cards. (In standalone mode.)
22
To avoid unnecessary floods and improve forwarding speed, make sure all cards possess the same MAC
address table. After you enable MAC address table synchronization, each card advertises learned MAC
address entries to other cards of all member devices. (In IRF mode.)
As shown in Figure 3, Device A and Device B form an IRF fabric enabled with MAC address
synchronization. They connect to AP C and AP D, respectively. When Client A associates with AP C,
Device A learns a MAC address entry for Client A and advertises it to Device B.
Figure 3 MAC address tables of devices when Client A accesses AP C
If Client A roams to AP D, Device B learns a MAC address entry for Client A and advertises it to Device
A to ensure service continuity for Client A, as shown in Figure 4.
Figure 4 MAC address tables of devices when Client A roams to AP D
To enable MAC address synchronization:
23
2. Enable MAC address By default, MAC address

mac-address mac-roaming enable
synchronization. synchronization is disabled.
Displaying and maintaining the MAC address table

Task Command
display mac-address [ mac-address [ vlan vlan-id ] | [ [ dynamic |
Display MAC address table
static ] [ interface interface-type interface-number ] | blackhole |
information.
multiport ] [ vlan vlan-id ] [ count ] ]
Display the aging timer for dynamic

display mac-address aging-time
MAC address entries.
Display the system or interface MAC display mac-address mac-learning [ interface interface-type
address learning state. interface-number ]
Display MAC address statistics. display mac-address statistics
MAC address table configuration example

Network requirements
Host A at 000f-e235-dc71 is connected to interface FortyGigE 1/0/1 of Device and belongs to VLAN
1.
Host B at 000f-e235-abcd, which once behaved suspiciously on the network, also belongs to VLAN 1.
Configure the MAC address as follows:
To prevent MAC address spoofing, add a static entry for Host A in the MAC address table of
Device.
Add a blackhole MAC address entry for Host B, so that all frames destined for the host will be
dropped.
Set the aging timer for dynamic MAC address entries to 500 seconds.
# Add a static MAC address entry for MAC address 000f-e235-dc71 on FortyGigE 1/0/1 that belongs
to VLAN 1.
<Device> system-view
[Device] mac-address static 000f-e235-dc71 interface fortygige 1/0/1 vlan 1
# Add a blackhole MAC address entry for MAC address 000f-e235-abcd that belongs to VLAN 1.
[Device] mac-address blackhole 000f-e235-abcd vlan 1
24
# Set the aging timer for dynamic MAC address entries to 500 seconds.
[Device] mac-address timer aging 500
Verifying the configuration

# Display the static MAC address entry for interface FortyGigE 1/0/1.
[Device] display mac-address static interface fortygige 1/0/1
MAC Address VLAN ID State Port/NickName Aging
000f-e235-dc71 1 Static FGE1/0/1 N
# Display information about the blackhole MAC address entries.

[Device] display mac-address blackhole
MAC Address VLAN ID State Port/NickName Aging
000f-e235-abcd 1 Blackhole N/A N
# View the aging time of dynamic MAC address entries.

[Device] display mac-address aging-time
MAC address aging time: 500s.
25
Configuring MAC Information
The MAC Information feature can generate syslog messages or SNMP notifications when MAC address
entries are learned or deleted. You can use these messages to monitor users leaving or joining the
network and analyze network traffic.
The MAC Information feature buffers the MAC change syslog messages or SNMP notifications in a
queue. When the timer set for sending syslog messages or SNMP notifications does not expire, the
device overwrites the last piece of information written into the queue with the new MAC address change
if the queue has been exhausted. To send a syslog message or SNMP notification immediately after it is
created, set the queue length to zero.
The device does not write MAC address change information or send MAC address change messages for
blackhole MAC addresses, static MAC addresses, multiport unicast MAC addresses, multicast MAC
addresses, and local MAC addresses except for dynamic MAC addresses.
Enable MAC Information globally before you enable it on interfaces.
Enabling MAC Information

2. Enable MAC Information By default, global MAC
mac-address information enable
globally. Information is disabled.
3. Enter Layer 2 Ethernet interface interface-type
N/A
4. Enable MAC Information on mac-address information enable By default, MAC Information is
the interface. { added | deleted } disabled on an interface.
Configuring the MAC Information mode

The following MAC Information modes are available for sending MAC address changes:
SyslogThe device sends syslog messages to notify MAC address changes. In this mode, the
device sends syslog messages to the information center, which then outputs them to the monitoring
terminal. For more information about information center, see Network Management and
Monitoring Configuration Guide.
TrapThe device sends SNMP notifications to notify MAC address changes. In this mode, the
device sends SNMP notifications to the NMS. For more information about SNMP, see Network
Management and Monitoring Configuration Guide.
To configure the MAC Information mode:
26
2. Configure the MAC mac-address information mode Optional.

Information mode. { syslog | trap } The default setting is trap.
Configuring the MAC change sending interval

To prevent syslog messages or SNMP notifications from being sent too frequently, you can set the MAC
change sending interval.
To set the MAC change sending interval:

2. Set the MAC change sending mac-address information interval
The default setting is 1 second.
interval. interval-time
Configuring the MAC Information queue length

2. Configure the MAC mac-address information
The default setting is 50.
Information queue length. queue-length value
MAC Information configuration example

Enable MAC Information on interface FortyGigE 1/0/1 on Device in Figure 5 to send MAC address
changes in syslog messages to the log host, Host B, through interface FortyGigE 1/0/2.
27
Figure 5 Network diagram

When you edit the file /etc/syslog.conf, follow these restrictions and guidelines:
Comments must be on a separate line and must begin with a pound sign (#).
No redundant spaces are allowed after the file name.
The logging facility name and the severity level specified in the /etc/syslog.conf file must be
identical to those configured on the device by using the info-center loghost and info-center source
commands. Otherwise, the log information might not be output correctly to the log host.
1. Configure Device to send syslog messages to Host B:
# Enable the information center.
[Device] info-center enable
# Specify the log host 192.168.1.2/24 and specify local4 as the logging facility.
[Device] info-center loghost 192.168.1.2 facility local4
# Disable log output to the log host.
[Device] info-center source default loghost deny
To avoid output of unnecessary information, disable all modules from outputting logs to the
specified destination (loghost, in this example) before you configure an output rule.
# Configure an output rule to output to the log host MAC address logs that have a severity level of
at least informational.
[Device] info-center source mac loghost level informational
2. Configure the log host, Host B:
The following configurations were performed on Solaris. Other UNIX operating systems have
similar configurations.
a. Log in to the log host as a root user.
b. Create a subdirectory named Device in directory /var/log/, and then create file info.log in the
Device directory to save logs from Device.
# mkdir /var/log/Device
28
# touch /var/log/Device/info.log
c. Edit the file syslog.conf in directory /etc/ and add the following contents:
# Device configuration messages
local4.info /var/log/Device/info.log
In this configuration, local4 is the name of the logging facility that the log host uses to receive
logs, and info is the informational level. The UNIX system records the log information that has
a severity level of at least informational to the file /var/log/Device/info.log.
d. Display the process ID of syslogd, kill the syslogd process, and then restart syslogd using the r
option to make the new configuration take effect.
# ps -ae | grep syslogd
147
# kill -HUP 147
# syslogd -r &
Now, the device can output MAC address logs to the log host, which stores the logs to the
specified file.
3. Enable MAC Information on Device:
# Enable MAC Information globally.
[Device] mac-address information enable
# Configure the MAC Information mode as syslog.
[Device] mac-address information mode syslog
# Enable MAC Information on interface FortyGigE 1/0/1, so that interface FortyGigE 1/0/1 can
record MAC address change information when learning a new MAC address or deleting an
existing MAC address.
[Device] interface fortygige 1/0/1
[Device-FortyGigE1/0/1] mac-address information enable added
[Device-FortyGigE1/0/1] mac-address information enable deleted
[Device-FortyGigE1/0/1] quit
# Set the MAC Information queue length to 100.
[Device] mac-address information queue-length 100
# Set the MAC change sending interval to 20 seconds.
[Device] mac-address information interval 20
29
Configuring Ethernet link aggregation
Ethernet link aggregation bundles multiple physical Ethernet links into one logical link, called an
aggregate link. Link aggregation has the following benefits:
Increased bandwidth beyond the limits of any single link. In an aggregate link, traffic is distributed
across the member ports.
Improved link reliability. The member ports dynamically back up one another. When a member
port fails, its traffic is automatically switched to other member ports.
As shown in Figure 6, Device A and Device B are connected by three physical Ethernet links. These
physical Ethernet links are combined into an aggregate link called link aggregation 1. The bandwidth of
this aggregate link can be as high as the total bandwidth of the three physical Ethernet links. At the same
time, the three Ethernet links back up one another. When a physical Ethernet link fails, the traffic
previously carried on the failed link is switched to the other two links.
Figure 6 Ethernet link aggregation diagram
Basic concepts
Aggregation group, member port, and aggregate interface
Link bundling is implemented through interface bundling. An aggregation group is a group of Ethernet
interfaces bundled together, which are called member ports of the aggregation group. For each
aggregation group, a logical interface (called an aggregate interface), is created. To an upper layer
entity that uses the link aggregation service, a link aggregation group appears the same as a single
logical link and data traffic is transmitted through the aggregate interface.
When you create an aggregate interface, the device automatically creates an aggregation group of the
same type and number as the aggregate interface. For example, when you create aggregate interface
1, aggregation group 1 is created.
You can assign Layer 2 Ethernet interfaces only to a Layer 2 aggregation group.
The port rate of an aggregate interface equals the total rate of its member ports in Selected state, and its
duplex mode is the same as that of the selected member ports. For more information about the states of
member ports in an aggregation group, see "Aggregation states of member ports in an aggregation
group."
Aggregation states of member ports in an aggregation group

A member port in an aggregation group can be in either of the following aggregation states:
SelectedA Selected port can forward traffic.
30
UnselectedAn Unselected port cannot forward traffic.
Operational key
When aggregating ports, the system automatically assigns each port an operational key based on port
information, such as port rate and duplex mode. Any change to this information triggers a recalculation
of the operational key.
In an aggregation group, all Selected ports are assigned the same operational key.
Configuration types
Every configuration setting on a port might affect its aggregation state. Port configurations include the
following types:
Attribute configurationsTo become a Selected port, a member port must have the same attribute
configurations as the aggregate interface. Table 2 describes the attribute configurations.
Attribute configurations made on an aggregate interface are automatically synchronized to all
member ports. These configurations are retained on the member ports even after the aggregate
interface is removed.
Any attribute configuration change might affect the aggregation state of link aggregation member
ports and running services. To make sure that you are aware of the risk, the system displays a
warning message every time you attempt to change an attribute configuration setting on a member
port.
Table 2 Attribute configurations
Feature Considerations
Indicates whether the port has joined an isolation group, and the isolation group
Port isolation
to which the port belongs.
Permitted VLAN IDs, PVID, link type (trunk, hybrid, or access), operating mode
VLAN (promiscuous, trunk promiscuous, host), and VLAN tagging mode. For
information about VLAN, see "Configuring VLANs."
Protocol configurationsAs opposed to attribute configurations, protocol configurations do not

affect the aggregation state of the member ports, even if they are different from those on the
aggregate interface. MAC address learning and spanning tree settings are examples of protocol
configurations.
NOTE:
The protocol configuration for a member port is effective only when the member port leaves the
aggregation group.
Link aggregation modes

Link aggregation has dynamic and static modes:
Static aggregation modeAggregation is stable. The aggregation state of the member ports are
not affected by the peer ports.
31
Dynamic aggregation modeThe peering system automatically maintains the aggregation state of
the member ports, thus reducing the workload of administrators.
An aggregation group in static mode is called a "static aggregation group" and an aggregation group
in dynamic mode is called a "dynamic aggregation group."
Aggregating links in static mode

The static link aggregation process contains:
Choosing a reference port
Setting the aggregation state of each member port

When setting the aggregation state of the ports in an aggregation group, the system automatically picks
a member port as the reference port. A Selected port must have the same operational key and attribute
configurations as the reference port.
The system chooses a reference port from the member ports that are in up state with the same attribute
configurations as the aggregate interface.
The candidate ports are sorted in the following order:
1. Highest port priority
2. Full duplex/high speed
3. Full duplex/low speed
4. Half duplex/high speed
5. Half duplex/low speed
The candidate port at the top is chosen as the reference port. If two ports have the same port priority,
duplex mode, and speed, the original Selected port is chosen. If more than one such original Selected
port exists, the one with the lower port number is chosen.

After a static aggregation group has reached the limit on Selected ports, any port that joins the group is
placed in Unselected state to avoid traffic interruption on the existing Selected ports.
32
Figure 7 Setting the aggregation state of a member port in a static aggregation group
The maximum number of Selected ports in a static aggregation group is 16.

To ensure stable aggregation state and service continuity, do not change port attributes or class-two
configurations on any member port. If you need to make this change, make sure you understand its
impact on the live network. Any port attribute or class-two configuration change might affect the
aggregation state of link aggregation member ports and ongoing traffic.
Aggregating links in dynamic mode

Dynamic aggregation mode is implemented through IEEE 802.3ad Link Aggregation Control Protocol
(LACP).
LACP
LACP uses LACPDUs to exchange aggregation information between LACP-enabled devices.
Each member port in an LACP-enabled aggregation group exchanges information with its peer. When a
member port receives an LACPDU, it compares the received information with information received on the
other member ports. In this way, the two systems reach an agreement on which ports are placed in
Selected state.
33
LACP functions
LACP offers basic LACP functions and extended LACP functions, as described in Table 3.
Table 3 Basic and extended LACP functions
Category Description
Implemented through the basic LACPDU fields, including the system LACP priority,
Basic LACP functions
system MAC address, port priority, port number, and operational key.
Implemented by extending the LACPDU with new TLV fields. This is how the LACP
MAD mechanism of the IRF feature is implemented. it can participate in LACP MAD
Extended LACP as either an IRF member device or an intermediate device.
functions
For more information about IRF and the LACP MAD mechanism, see IRF
Configuration Guide.
LACP priorities
LACP priorities include system LACP priority and port priority, as described in Table 4. The smaller the
priority value, the higher the priority.
Table 4 LACP priorities
Type Description
Used by two peer devices (or systems) to determine which one is superior in link
aggregation.
System LACP priority In dynamic link aggregation, the system that has higher system LACP priority sets the
Selected state of member ports on its side, after which the system that has lower priority
sets port state accordingly.
Determines the likelihood of a member port to be selected on a system. The higher port
Port priority
priority, the higher the likelihood of selection.
LACP timeout interval

The LACP timeout interval specifies how long a member port waits to receive LACPDUs from the peer port.
If a local member port fails to receive LACPDUs from the peer within the LACP timeout interval, the
member port assumes that the peer port has failed.
The LACP timeout interval also determines the LACPDU sending rate of the peer. You can configure the
LACP timeout interval as the short timeout interval (3 seconds) or the long timeout interval (90 seconds).
If you configure the short timeout interval, the peer sends LACPDUs fast (one LACPDU per second); if you
configure the long timeout interval, the peer sends LACPDUs slowly (one LACPDU every 30 seconds).
How dynamic link aggregation works

The dynamic link aggregation process contains:

The system chooses a reference port from the member ports that are in up state and have the same
attribute configurations as the aggregate interface. A Selected port must have the same operational key
and attribute configurations as the reference port.
34
The local system (the actor) and the remote system (the partner) negotiate a reference port by using the
following workflow:
1. The systems compare their system IDs. (A system ID contains the system LACP priority and the
system MAC address.) The lower the LACP priority, the smaller the system ID. If LACP priority
values are the same, the two systems compare their MAC addresses. The lower the MAC address,
the smaller the system ID.
2. The system with the smaller system ID chooses the port with the smallest port ID as the reference
port. (A port ID contains a port priority and a port number.) The port with the lower priority value
is chosen. If two ports have the same aggregation priority, the system compares their port numbers.
The port with the smaller port number and the same attribute configurations as the aggregate
interface becomes the reference port.

After the reference port is chosen, the system with the lower system ID sets the state of each member port
in the dynamic aggregation group on its side as shown in Figure 8.
35
Figure 8 Setting the state of a member port in a dynamic aggregation group
Meanwhile, the system with the higher system ID, being aware of the aggregation state changes on the
remote system, sets the aggregation state of local member ports the same as their peer ports.
When you aggregate interfaces in dynamic mode, follow these guidelines:
The maximum number of Selected ports in a dynamic aggregation group is 16.
A dynamic link aggregation group preferably sets full-duplex ports as the Selected ports, and will
set one, and only one, half-duplex port as a Selected port when none of the full-duplex ports can be
selected or only half-duplex ports exist in the group.
To ensure stable aggregation and service continuity, do not change the operational key or attribute
configurations on any member port.
In a dynamic aggregation group, when the aggregation state of a local port changes, the
aggregation state of the peer port also changes.
36
A port that joins a dynamic aggregation group after the Selected port limit has been reached is
placed in Selected state if it is more eligible to be selected than a current member port.
Load sharing criteria for link aggregation groups

In a link aggregation group, traffic may be load-shared across the selected member ports based on a set
of criteria, depending on your configuration.
You can choose one of the following criteria or any combination of the criteria for load sharing:
Per-flow load sharingClassifies traffic flows and forwards packets of the same flow on the same
link by the following criteria, or any combination:
{ Source or destination MAC address.
{ Source or destination port number.
{ Ingress port.
{ Source or destination IP address.
Packet type-based load sharingAutomatically chooses link-aggregation load sharing criteria
based on packet types (Layer 2 or IPv4 for example).
Ethernet link aggregation configuration task list

Tasks at a glance
(Required.) Configuring an aggregation group:
Configuring a Layer 2 static aggregation group
Configuring a Layer 2 dynamic aggregation group
(Optional.) Configuring an aggregate interface:
Configuring the description of a Layer 2 aggregate interface
Specifying ignored VLANs on a Layer 2 aggregate interface
Setting the minimum and maximum numbers of Selected ports for an aggregation group
Configuring the expected bandwidth of an aggregate interface
Shutting down an aggregate interface
Restoring the default settings for an aggregate interface
(Optional.) Configuring load balancing for link aggregation group:

Configuring load sharing criteria for link aggregation groups
Enabling local-first load sharing for link aggregation
Enabling link-aggregation traffic redirection
Configuring an aggregation group

This section explains how to configure an aggregation group.
When you configure an aggregation group, follow these guidelines:
37
Removing an aggregate interface also removes its aggregation group and causes all member ports
to leave the aggregation group.
You must configure the same aggregation mode on the two ends of an aggregate link.
Configuring a Layer 2 static aggregation group

To guarantee a successful static aggregation, make sure that the ports at both ends of each link are in the
same aggregation state.
Avoid assigning ports to a static aggregation group that has reached the limit on Selected ports. These
ports will be placed in Unselected state to avoid traffic interruption on the current Selected ports.
However, a device reboot can cause the aggregation state of member ports to change.
To configure a Layer 2 static aggregation group:

When you create a Layer 2

2. Create a Layer 2 aggregate aggregate interface, the system
interface and enter Layer 2 automatically creates a Layer 2
interface-number
aggregate interface view. static aggregation group
numbered the same.
3. Exit to system view. quit N/A
a. Enter Layer 2 Ethernet
interface view:
interface-number Repeat these two sub-steps to
4. Assign an interface to the
assign more Layer 2 Ethernet
specified Layer 2 aggregation b. Assign the interface to the
interfaces to the aggregation
group. specified Layer 2
group.
aggregation group:
port link-aggregation
group number
Configuring a Layer 2 dynamic aggregation group

To guarantee a successful dynamic aggregation, make sure that the peer ports of the ports aggregated
at one end are also aggregated. The two ends can automatically negotiate the aggregation state of each
member port.
To configure a Layer 2 dynamic aggregation group:

By default, the system LACP priority

is 32768.
2. Set the system LACP priority. lacp system-priority system-priority Changing the system LACP priority
might affect the aggregation state
of the ports in a dynamic
aggregation group.
38
When you create a Layer 2
3. Create a Layer 2 aggregate aggregate interface, the system
interface and enter Layer 2 automatically creates a Layer 2
interface-number
aggregate interface view. static aggregation group
numbered the same.
4. Configure the aggregation By default, an aggregation group
group to operate in dynamic link-aggregation mode dynamic operates in static aggregation
aggregation mode. mode.
5. Exit to system view. quit N/A
a. Enter Layer 2 Ethernet
interface view:
interface-number Repeat these two sub-steps to
6. Assign an interface to the
assign more Layer 2 Ethernet
specified Layer 2 aggregation b. Assign the interface to the
interfaces to the aggregation
group. specified Layer 2
group.
aggregation group:
port link-aggregation
group number
7. Configure the port priority for link-aggregation port-priority
the interface. port-priority
By default, the long LACP timeout

8. Configure the short LACP
interval (90 seconds) is adopted by
timeout interval (3 seconds) lacp period short
the interface. The peer sends
on the interface.
LACPDUs slowly.
Configuring a Layer 2 aggregate interface

In addition to the configurations in this section, most of the configurations that can be performed on Layer
2 Ethernet interfaces can also be performed on Layer 2 aggregate interfaces.
Configuring the description of a Layer 2 aggregate interface

You can configure the description of an aggregate interface for administration purposes such as
describing the purpose of the interface.
To configure the description of a Layer 2 aggregate interface:

2. Enter Layer 2 aggregate interface bridge-aggregation

N/A
39
3. Configure the By default, the description of an
description of the description text interface is in the format of
aggregate interface. interface-name Interface.
Specifying ignored VLANs on a Layer 2 aggregate interface

By default, the member ports cannot become Selected ports when the permit state and tagging mode of
each VLAN are not same for the member ports and the Layer 2 aggregate interface.
You can set a VLAN as an ignored VLAN if you want to allow member ports to be set in Selected state
even if the permit state and tagging mode of the VLAN are different between the member ports and the
Layer 2 aggregate interface.
To configure ignored VLANs on a Layer 2 aggregate interface:

N/A
By default, a Layer 2 aggregate

link-aggregation ignore vlan
3. Configure ignored VLANs. interface does not ignore any
vlan-id-list
VLANs.
Setting the minimum and maximum numbers of Selected ports

for an aggregation group
IMPORTANT:
The minimum and maximum number of Selected ports must be the same for the local and peer
aggregation groups.
The bandwidth of an aggregate link increases as the number of selected member ports increases. To
avoid congestion caused by insufficient Selected ports on an aggregate link, you can set the minimum
number of Selected ports required for bringing up the specific aggregate interface.
This minimum threshold setting affects the aggregation state of both aggregation member ports and the
aggregate interface:
When the number of member ports eligible to be selected is smaller than the minimum threshold,
all member ports change to the Unselected state and the link of the aggregate interface goes down.
When the minimum threshold is reached, the eligible member ports change to the Selected state,
and the link of the aggregate interface goes up.
The maximum number of Selected ports allowed in an aggregation group is limited by either the
configured maximum number or hardware capability, whichever value is smaller.
You can configure backup between two ports by assigning two ports to an aggregation group and
configuring the maximum number of Selected ports allowed in the aggregation group as 1. In this way,
40
only one Selected port is allowed in the aggregation group at any point in time, while the Unselected
port serves as a backup port.
To set the minimum and maximum numbers of Selected ports for an aggregation group:


N/A
3. Set the minimum number of By default, the minimum number of

link-aggregation selected-port
Selected ports for the Selected ports for the aggregation
minimum number
aggregation group. group is not specified.
4. Set the maximum number of By default, the maximum number of
link-aggregation selected-port
Selected ports for the Selected ports for an aggregation
maximum number
aggregation group. group is 16.
Configuring the expected bandwidth of an aggregate interface

To set the expected bandwidth of an aggregate interface:

N/A
By default, the expected

bandwidth bandwidth-value bandwidth (in kbps) is the interface
bandwidth of the interface.
baud rate divided by 1000.
Shutting down an aggregate interface

Make sure no member port in an aggregation group is configured with the loopback command when
you shut down the aggregate interface. Similarly, a port configured with the loopback command cannot
be assigned to an aggregate interface already shut down. For more information about the loopback
command, see Layer 2LAN Switching Command Reference.
Shutting down or bringing up an aggregate interface affects the aggregation state and link state of ports
in the corresponding aggregation group in the following ways:
When an aggregate interface is shut down, all Selected ports in the corresponding aggregation
group become unselected and their link state becomes down.
When an aggregate interface is brought up, the aggregation state of ports in the corresponding
aggregation group is recalculated.
To shut down an aggregate interface:
41

N/A
3. Shut down the aggregate By default, aggregate interfaces

shutdown
interface. are up.
Restoring the default settings for an aggregate interface

You can return all configurations on an aggregate interface to default settings.
To restore the default settings for an aggregate interface:
Step Command
1. Enter system view. system-view
2. Enter Layer 2 aggregate interface view. interface bridge-aggregation interface-number
3. Restore the default settings for the aggregate
default
interface.
Configuring load sharing for link aggregation

groups
This section explains how to configure load sharing criteria for link aggregation groups and how to
enable local-first load sharing for link aggregation.
Configuring load sharing criteria for link aggregation groups

You can configure global load sharing criteria, which take effect on all link aggregation groups.
To configure the global link-aggregation load sharing criteria:

link-aggregation global load-sharing By default, the system

2. Configure the global
mode { destination-ip | destination-mac automatically chooses
link-aggregation load
| destination-port | ingress-port | link-aggregation load sharing
sharing criteria.
source-ip | source-mac | source-port } * criteria based on packet types.
In system view, the switch supports the following load sharing criteria and combinations:
Source IP address
42
Destination IP address
Source MAC address
Destination MAC address
Source IP address and destination IP address
Source IP address and source port
Destination IP address and destination port
Source IP address, source port, destination IP address, and destination port
Any combination of ingress port, source MAC address, and destination MAC address
Enabling local-first load sharing for link aggregation

Use the local-first load sharing mechanism in a multi-device link aggregation scenario to distribute traffic
preferentially across member ports on the ingress card or device rather than all member ports.
When you aggregate ports on different member devices in an IRF fabric, you can use local-first load
sharing to reduce traffic on IRF links, as shown in Figure 9. For more information about IRF, see IRF
Figure 9 Load sharing for multi-switch link aggregation in an IRF fabric
The egress port for a traffic flow is an

aggregate interface that has Selected
ports on different IRF member switches
Yes Local-first load sharing No

mechanism enabled?
Any Selected ports on the No

ingress switch?
Yes
Packets are load shared only

Packets are load shared across
across the Selected ports on the
all Selected ports
ingress switch
To enable local-first load sharing for link aggregation:

2. Enable local-first load sharing link-aggregation load-sharing By default, local-first load sharing
for link aggregation. mode local-first for link aggregation is enabled.
43
NOTE:
Local-first load sharing for link aggregation takes effect on only known unicast packets.
Enabling link-aggregation traffic redirection

Link-aggregation traffic redirection prevents traffic interruption.
With this feature, when you restart a card that contains Selected ports, traffic can be redirected to other
cards. (In standalone mode.)
With this feature, when you restart an IRF member device or its card that contains Selected ports, traffic
can be redirected to other IRF member devices or other cards. (In IRF mode.)

When you enable link-aggregation traffic redirection, follow these restrictions and guidelines:
Link-aggregation traffic redirection applies only to dynamic link aggregation groups and takes
effect on only known unicast packets.
To prevent traffic interruption, enable link-aggregation traffic redirection on devices at both ends of
the aggregate link.
To prevent packet loss that might occur at a reboot, do not enable spanning tree together with
link-aggregation traffic redirection.
To enable link-aggregation traffic redirection:

2. Enable link-aggregation traffic link-aggregation lacp By default, link-aggregation traffic
redirection. traffic-redirect-notification enable redirection is disabled.
Displaying and maintaining Ethernet link

aggregation
Task Command
display interface [ bridge-aggregation ] [ brief [ down |
Display information for an aggregate interface description ] ]
or multiple aggregate interfaces. display interface bridge-aggregation interface-number
[ brief [ description ] ]
Display the local system ID. display lacp system-id
44
Task Command
Display the global or group-specific display link-aggregation load-sharing mode [ interface
link-aggregation load sharing criteria. [ bridge-aggregation interface-number ] ]
Display detailed link aggregation information

display link-aggregation member-port [ interface-list ]
for link aggregation member ports.
Display summary information about all

display link-aggregation summary
aggregation groups.
Display detailed information about specific or display link-aggregation verbose [ bridge-aggregation

all aggregation groups. [ interface-number ] ]
Clear LACP statistics for specific or all link

reset lacp statistics [ interface interface-list ]
aggregation member ports.
Clear statistics for specific or all aggregate reset counters interface [ bridge-aggregation
interfaces. [ interface-number ] ]
Ethernet link aggregation configuration examples

Layer 2 static aggregation configuration example
As shown in Figure 10, configure a Layer 2 static aggregation group on both Device A and Device B, and
enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other end, and
VLAN 20 at one end to communicate with VLAN 20 at the other end.
1. Configure Device A:
# Create VLAN 10, and assign port FortyGigE 1/0/4 to VLAN 10.
<DeviceA> system-view
[DeviceA] vlan 10
[DeviceA-vlan10] port fortygige 1/0/4
[DeviceA-vlan10] quit
45
# Create VLAN 20, and assign port FortyGigE 1/0/5 to VLAN 20.
[DeviceA] vlan 20
# Create Layer 2 aggregate interface Bridge-Aggregation 1.
[DeviceA] interface bridge-aggregation 1
[DeviceA-Bridge-Aggregation1] quit
# Assign ports FortyGigE 1/0/1 through FortyGigE 1/0/3 to link aggregation group 1.
[DeviceA] interface fortygige 1/0/1
[DeviceA-FortyGigE1/0/1] port link-aggregation group 1
[DeviceA-FortyGigE1/0/1] quit
# Configure Layer 2 aggregate interface Bridge-Aggregation 1 as a trunk port and assign it to
VLANs 10 and 20.
[DeviceA-Bridge-Aggregation1] port link-type trunk
[DeviceA-Bridge-Aggregation1] port trunk permit vlan 10 20
2. Configure Device B in the same way Device A is configured.

# Display detailed information about all aggregation groups on Device A.
[DeviceA] display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregate Interface: Bridge-Aggregation1

Aggregation Mode: Static
Loadsharing Type: Shar
Port Status Priority Oper-Key
--------------------------------------------------------------------------------
FGE1/0/1 S 32768 1
FGE1/0/2 S 32768 1
FGE1/0/3 S 32768 1
The output shows that link aggregation group 1 is a Layer 2 static aggregation group and it contains
three Selected ports.
46
Layer 2 dynamic aggregation configuration example
As shown in Figure 11, configure a Layer 2 dynamic aggregation group on both Device A and Device B,
enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other end, and
VLAN 20 at one end to communicate with VLAN 20 at the other end.
# Create VLAN 10, and assign the port FortyGigE 1/0/4 to VLAN 10.
[DeviceA] vlan 10
[DeviceA] vlan 20
# Create Layer 2 aggregate interface Bridge-Aggregation 1, and configure the link aggregation
mode as dynamic.
[DeviceA-Bridge-Aggregation1] link-aggregation mode dynamic
# Assign ports FortyGigE 1/0/1 through FortyGigE 1/0/3 to link aggregation group 1.
47
VLANs 10 and 20.
[DeviceA-Bridge-Aggregation1] port trunk permit vlan 10 20


Aggregation Mode: Dynamic
System ID: 0x8000, 000f-e267-6c6a
Local:
Port Status Priority Oper-Key Flag
--------------------------------------------------------------------------------
FGE1/0/1 S 32768 1 {ACDEF}
FGE1/0/2 S 32768 1 {ACDEF}
FGE1/0/3 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
--------------------------------------------------------------------------------
FGE1/0/1 1 32768 1 0x8000, 000f-e267-57ad {ACDEF}
FGE1/0/2 2 32768 1 0x8000, 000f-e267-57ad {ACDEF}
FGE1/0/3 3 32768 1 0x8000, 000f-e267-57ad {ACDEF}
The output shows that link aggregation group 1 is a Layer 2 dynamic aggregation group and it contains
three Selected ports.
Layer 2 aggregation load sharing configuration example

As shown in Figure 12:
Configure two Layer 2 static aggregation groups (1 and 2) on Device A and Device B respectively,
and enable VLAN 10 at one end of the aggregate link to communicate with VLAN 10 at the other
end, and VLAN 20 at one end to communicate with VLAN 20 at the other end.
Configure the global load sharing criterion as the source MAC addresses of packets to load-share
traffic across aggregation group member ports.
48
[DeviceA] vlan 10
[DeviceA] vlan 20
# Assign ports FortyGigE 1/0/1 and FortyGigE 1/0/2 to link aggregation group 1.
VLAN 10.
[DeviceA-Bridge-Aggregation1] port trunk permit vlan 10
# Assign ports FortyGigE 1/0/3 and FortyGigE 1/0/4 to link aggregation group 2.
49
VLAN 20.
[DeviceA-Bridge-Aggregation2] port trunk permit vlan 20
# Configure the source MAC address as the global link-aggregation load sharing criterion.
[DeviceA] link-aggregation global load-sharing mode source-mac


--------------------------------------------------------------------------------
FGE1/0/1 S 32768 1
FGE1/0/2 S 32768 1

--------------------------------------------------------------------------------
FGE1/0/3 S 32768 2
FGE1/0/4 S 32768 2
The output shows that link aggregation groups 1 and 2 are both load-shared Layer 2 static aggregation
groups and each contains two Selected ports.
# Display all the group-specific load sharing criteria on Device A.
[DeviceA] display link-aggregation load-sharing mode interface
Bridge-Aggregation1 Load-Sharing Mode:

source-mac address
50
Bridge-Aggregation2 Load-Sharing Mode:
source-mac address
The output shows that the load sharing criteria for both link aggregation group 1 and link aggregation
group 2 are the source MAC addresses of packets.
51
Configuring port isolation
The port isolation feature isolates Layer 2 traffic for data privacy and security without using VLANs. You
can also use this feature to isolate the hosts in a VLAN from one another.
You can manually create isolation groups on the switch, but only the isolation group numbered 1 is valid.
The number of ports assigned to an isolation group is not limited.
Within the same VLAN, ports in an isolation group can communicate with those outside the isolation
group at Layer 2.
Assigning ports to an isolation group

2. Create an isolation For this switch series, only the isolation
port-isolate group group-number
group. group numbered 1 is valid.
The configuration in Layer 2 Ethernet
interface view applies only to the
interface.
Enter Layer 2 Ethernet The configuration in Layer 2 aggregate
interface view: interface view applies to the Layer 2
interface interface-type aggregate interface and its
interface-number aggregation member ports. If the
3. Enter interface view. device fails to apply the configuration
to the aggregate interface, it does not
interface view:
assign any aggregation member port
to the isolation group. If the failure
interface-number
occurs on an aggregation member
port, the device skips the port and
continues to assign other aggregation
member ports to the isolation group.
No ports are assigned to an isolation

4. Assign ports to the
port-isolate enable group group by default.
specified isolation
group-number For this switch series, you can assign ports
group.
to only isolation group 1.
Displaying and maintaining port isolation

Task Command
display port-isolate group [ group-number ] [ | { begin |
Display isolation group information
exclude | include } regular-expression ]
52
Port isolation configuration example
As shown in Figure 13, LAN users Host A, Host B, and Host C are connected to FortyGigE 1/0/1,
FortyGigE 1/0/2, and FortyGigE 1/0/3 on the device, respectively. The device connects to the Internet
through FortyGigE 1/0/4.
Configure the device to provide Internet access for the hosts, and isolate them from one another at Layer
2.
# Create isolation group 1.
[Device] port-isolate group 1
# Assign FortyGigE 1/0/1, FortyGigE 1/0/2, and FortyGigE 1/0/3 to isolation group 1.
[Device-FortyGigE1/0/1] port-isolate enable group 1

# Display information about isolation group 1.
[Device-FortyGigE1/0/3] display port-isolate group 1
Port isolation group information:
53
Group ID: 1
Group members:
FortyGigE1/0/1
FortyGigE1/0/2
FortyGigE1/0/3
54
Configuring spanning tree protocols
Spanning tree protocols eliminate loops in a physical link-redundant network by selectively blocking
redundant links and putting them in a standby state.
The recent versions of STP include the Rapid Spanning Tree Protocol (RSTP) and the Multiple Spanning
Tree Protocol (MSTP).
STP
STP was developed based on the 802.1d standard of IEEE to eliminate loops at the data link layer in a
LAN. Networks often have redundant links as backups in case of failures, but loops are a very serious
problem. Devices running STP detect loops in the network by exchanging information with one another,
and eliminate loops by selectively blocking certain ports to prune the loop structure into a loop-free tree
structure. This avoids proliferation and infinite cycling of packets that would occur in a loop network.
In the narrow sense, STP refers to IEEE 802.1d STP. In the broad sense, STP refers to the IEEE 802.1d STP
and various enhanced spanning tree protocols derived from that protocol.
STP protocol packets

STP uses bridge protocol data units (BPDUs), also known as configuration messages, as its protocol
packets. This chapter uses BPDUs to represent all types of spanning tree protocol packets.
STP-enabled network devices exchange BPDUs to establish a spanning tree. BPDUs contain sufficient
information for the network devices to complete spanning tree calculation.
STP uses the following types of BPDUs:
Configuration BPDUsUsed by the network devices to calculate a spanning tree and maintain the
spanning tree topology.
Topology change notification (TCN) BPDUsNotify network devices of network topology changes.
Configuration BPDUs contain sufficient information for the network devices to complete spanning tree
calculation. Important fields in a configuration BPDU include the following:
Root bridge IDConsisting of the priority and MAC address of the root bridge.
Root path costCost of the path to the root bridge denoted by the root identifier from the
transmitting bridge.
Designated bridge IDConsisting of the priority and MAC address of the designated bridge.
Designated port IDConsisting of the priority and global port number of the designated port.
Message ageAge of the configuration BPDU while it propagates in the network.
Max ageMaximum age of the configuration BPDU stored on the switch.
Hello timeConfiguration BPDU transmission interval.
Forward delayDelay that STP bridges use to transit port state.
55
Basic concepts in STP
Root bridge
A tree network must have a root bridge. The entire network contains only one root bridge, and all the
other bridges in the network are called "leaf nodes". The root bridge is not permanent, but can change
with changes of the network topology.
Upon initialization of a network, each device generates and periodically sends configuration BPDUs,
with itself as the root bridge. After network convergence, only the root bridge generates and periodically
sends configuration BPDUs. The other devices only forward the BPDUs.
Root port
On a non-root bridge, the port nearest to the root bridge is the root port. The root port communicates with
the root bridge. Each non-root bridge has only one root port. The root bridge has no root port.
Designated bridge and designated port
Classification Designated bridge Designated port

Device directly connected with the local
Port through which the designated
For a device device and responsible for forwarding BPDUs
bridge forwards BPDUs to this device
to the local device
Port through which the designated

Device responsible for forwarding BPDUs to
For a LAN bridge forwards BPDUs to this LAN
this LAN segment
segment
As shown in Figure 14, Device B and Device C are directly connected to a LAN. If Device A forwards
BPDUs to Device B through port A1, the designated bridge for Device B is Device A, and the designated
port of Device B is port A1 on Device A. If Device B forwards BPDUs to the LAN, the designated bridge
for the LAN is Device B, and the designated port for the LAN is port B2 on Device B.
Figure 14 Designated bridges and designated ports
Device A
Port A1 Port A2
Device B Device C
Port B1 Port C1
Port B2 Port C2
LAN
Path cost
Path cost is a reference value used for link selection in STP. STP calculates path costs to select the most
robust links and block redundant links that are less robust, to prune the network into a loop-free tree.
56
Calculation process of the STP algorithm
The spanning tree calculation process described in the following sections is a simplified process for
example only.
Calculation process
The STP algorithm uses the following calculation process:
1. Network initialization.
Upon initialization of a device, each port generates a BPDU with the port as the designated port,
the device as the root bridge, 0 as the root path cost, and the device ID as the designated bridge
ID.
2. Root bridge selection.
Initially, each STP-enabled device on the network assumes itself to be the root bridge, with its own
device ID as the root bridge ID. By exchanging configuration BPDUs, the devices compare their
root bridge IDs to elect the device with the smallest root bridge ID as the root bridge.
3. Root port and designated ports selection on the non-root bridges.
Step Description
A non-rootbridge device regards the port on which it received the optimum configuration
1
BPDU as the root port. Table 5 describes how the optimum configuration BPDU is selected.
Based on the configuration BPDU and the path cost of the root port, the device calculates a
designated port configuration BPDU for each of the other ports.
The root bridge ID is replaced with that of the configuration BPDU of the root port.
2 The root path cost is replaced with that of the configuration BPDU of the root port plus the
path cost of the root port.
The designated bridge ID is replaced with the ID of this device.
The designated port ID is replaced with the ID of this port.
The device compares the calculated configuration BPDU with the configuration BPDU on the
port whose port role will be determined, and acts depending on the result of the comparison:
If the calculated configuration BPDU is superior, the device considers this port as the
designated port, replaces the configuration BPDU on the port with the calculated
3
configuration BPDU, and periodically sends the calculated configuration BPDU.
If the configuration BPDU on the port is superior, the device blocks this port without
updating its configuration BPDU. The blocked port can receive BPDUs, but cannot send
BPDUs or forward data traffic.
When the network topology is stable, only the root port and designated ports forward user traffic.
Other ports are all in the blocked state to receive BPDUs but not to forward BPDUs or user traffic.
Table 5 Selecting the optimum configuration BPDU
Step Actions
Upon receiving a configuration BPDU on a port, the device compares the priority of the
received configuration BPDU with that of the configuration BPDU generated by the port, and:
If the former priority is lower, the device discards the received configuration BPDU and
1
keeps the configuration BPDU the port generated.
If the former priority is higher, the device replaces the content of the configuration BPDU
generated by the port with the content of the received configuration BPDU.
57
Step Actions
The device compares the configuration BPDUs of all the ports and chooses the optimum
2
configuration BPDU.
The following are the principles of configuration BPDU comparison:

a. The configuration BPDU with the lowest root bridge ID has the highest priority.
b. If configuration BPDUs have the same root bridge ID, their root path costs are compared. For
example, the root path cost in a configuration BPDU plus the path cost of a receiving port is S.
The configuration BPDU with the smallest S value has the highest priority.
c. If all configuration BPDUs have the same root bridge ID and S value, their designated bridge
IDs, designated port IDs, and the IDs of the receiving ports are compared in sequence. The
configuration BPDU that contains a smaller designated bridge ID, designated port ID, or
receiving port ID is selected.
A tree-shape topology forms when the root bridge, root ports, and designated ports are selected.
Example of STP calculation

Figure 15 provides an example showing how the STP algorithm works.
Figure 15 The STP algorithm
Device A
Priority = 0
Port A1 Port A2
Port B1 Port C1
Port B2 Port C2
Path cost = 4
Device B Device C
Priority = 1 Priority = 2
As shown in Figure 15, the priority values of Device A, Device B, and Device C are 0, 1, and 2, and the
path costs of links among the three devices are 5, 10, and 4, respectively.
1. Device state initialization.
In Table 6, each configuration BPDU contains the following fields: root bridge ID, root path cost,
designated bridge ID, and designated port ID.
Table 6 Initial state of each device
Configuration BPDU on the

Device Port name
port
Port A1 {0, 0, 0, Port A1}
Device A
Port A2 {0, 0, 0, Port A2}
Device B Port B1 {1, 0, 1, Port B1}
58
Configuration BPDU on the
Device Port name
port
Port B2 {1, 0, 1, Port B2}
Port C1 {2, 0, 2, Port C1}

Device C
Port C2 {2, 0, 2, Port C2}
2. Configuration BPDUs comparison on each device.

In Table 7, each configuration BPDU contains the following fields: root bridge ID, root path cost,
designated bridge ID, and designated port ID.
Table 7 Comparison process and result on each device
Configuration BPDU on
Device Comparison process
ports after comparison
Port A1 receives the configuration BPDU of Port B1 {1, 0,
1, Port B1}, finds that its existing configuration BPDU {0, 0,
0, Port A1} is superior to the received configuration BPDU,
and discards the received one.
Port A2 receives the configuration BPDU of Port C1 {2, 0, Port A1: {0, 0, 0, Port
2, Port C1}, finds that its existing configuration BPDU {0,
A1}
Device A 0, 0, Port A2} is superior to the received configuration
BPDU, and discards the received one.
Port A2: {0, 0, 0, Port
A2}
Device A finds that it is both the root bridge and
designated bridge in the configuration BPDUs of all its
ports, and considers itself as the root bridge. It does not
change the configuration BPDU of any port and starts to
periodically send configuration BPDUs.
Port B1 receives the configuration BPDU of Port A1 {0, 0,
0, Port A1}, finds that the received configuration BPDU is
superior to its existing configuration BPDU {1, 0, 1, Port Port B1: {0, 0, 0, Port
B1}, and updates its configuration BPDU. A1}
Port B2 receives the configuration BPDU of Port C2 {2, 0, Port B2: {1, 0, 1, Port
2, Port C2}, finds that its existing configuration BPDU {1, B2}
0, 1, Port B2} is superior to the received configuration
BPDU, and discards the received one.
Device B compares the configuration BPDUs of all its
ports, decides that the configuration BPDU of Port B1 is the
Device B optimum, and selects Port B1 as the root port with the
configuration BPDU unchanged.
Based on the configuration BPDU and path cost of the root Root port (Port B1): {0,
port, Device B calculates a designated port configuration 0, 0, Port A1}
BPDU for Port B2 {0, 5, 1, Port B2}, and compares it with
Designated port (Port
the existing configuration BPDU of Port B2 {1, 0, 1, Port
B2): {0, 5, 1, Port B2}
B2}. Device B finds that the calculated one is superior,
decides that Port B2 is the designated port, replaces the
configuration BPDU on Port B2 with the calculated one,
and periodically sends the calculated configuration
BPDU.
59
Configuration BPDU on
Device Comparison process
ports after comparison
Port C1 receives the configuration BPDU of Port A2 {0, 0,
0, Port A2}, finds that the received configuration BPDU is
superior to its existing configuration BPDU {2, 0, 2, Port Port C1: {0, 0, 0, Port
C1}, and updates its configuration BPDU. A2}
Port C2 receives the original configuration BPDU of Port Port C2: {1, 0, 1, Port
B2 {1, 0, 1, Port B2}, finds that the received configuration B2}
BPDU is superior to the existing configuration BPDU {2, 0,
2, Port C2}, and updates its configuration BPDU.
Device C compares the configuration BPDUs of all its
ports, decides that the configuration BPDU of Port C1 is
the optimum, and selects Port C1 as the root port with the
configuration BPDU unchanged.
Based on the configuration BPDU and path cost of the root Root port (Port C1): {0,
port, Device C calculates the configuration BPDU of Port 0, 0, Port A2}
C2 {0, 10, 2, Port C2}, and compares it with the existing Designated port (Port
configuration BPDU of Port C2 {1, 0, 1, Port B2}. Device C C2): {0, 10, 2, Port C2}
finds that the calculated configuration BPDU is superior to
the existing one, selects Port C2 as the designated port,
and replaces the configuration BPDU of Port C2 with the
calculated one.
Port C2 receives the updated configuration BPDU of Port
B2 {0, 5, 1, Port B2}, finds that the received configuration
Device C BPDU is superior to its existing configuration BPDU {0, 10, Port C1: {0, 0, 0, Port
2, Port C2}, and updates its configuration BPDU. A2}
Port C1 receives a periodic configuration BPDU {0, 0, 0, Port C2: {0, 5, 1, Port
Port A2} from Port A2, finds that it is the same as the B2}
existing configuration BPDU, and discards the received
one.
Device C finds that the root path cost of Port C1 (10) (root
path cost of the received configuration BPDU (0) plus path
cost of Port C1 (10)) is larger than that of Port C2 (9) (root
path cost of the received configuration BPDU (5) plus path
cost of Port C2 (4)), decides that the configuration BPDU of
Port C2 is the optimum, and selects Port C2 as the root
port with the configuration BPDU unchanged.
Blocked port (Port C1):
Based on the configuration BPDU and path cost of the root {0, 0, 0, Port A2}
port, Device C calculates a designated port configuration
Root port (Port C2): {0,
BPDU for Port C1 {0, 9, 2, Port C1} and compares it with
5, 1, Port B2}
the existing configuration BPDU of Port C1 {0, 0, 0, Port
A2}. Device C finds that the existing configuration BPDU is
superior to the calculated one and blocks Port C1 with the
configuration BPDU unchanged. Then Port C1 does not
forward data until a new event triggers a spanning tree
calculation process, for example, the link between Device
B and Device C is down.
After the comparison processes described in Table 7, a spanning tree with Device A as the root bridge
is established, and the topology is shown in Figure 16.
60
Figure 16 The final calculated spanning tree
The configuration BPDU forwarding mechanism of STP

The configuration BPDUs of STP are forwarded according to these guidelines:
Upon network initiation, every device regards itself as the root bridge, generates configuration
BPDUs with itself as the root, and sends the configuration BPDUs at a regular hello interval.
If the root port received a configuration BPDU and the received configuration BPDU is superior to
the configuration BPDU of the port, the device increases the message age carried in the
configuration BPDU following a certain rule and starts a timer to time the configuration BPDU while
sending this configuration BPDU through the designated port.
If the configuration BPDU received on a designated port has a lower priority than the configuration
BPDU of the local port, the port immediately sends its own configuration BPDU in response.
If a path becomes faulty, the root port on this path no longer receives new configuration BPDUs and
the old configuration BPDUs will be discarded due to timeout. The device generates a configuration
BPDU with itself as the root and sends the BPDUs and TCN BPDUs. This triggers a new spanning
tree calculation process to establish a new path to restore the network connectivity.
However, the newly calculated configuration BPDU cannot be propagated throughout the network
immediately, so the old root ports and designated ports that have not detected the topology change
continue forwarding data along the old path. If the new root ports and designated ports begin to
forward data as soon as they are elected, a temporary loop might occur.
STP timers
The most important timing parameters in STP calculation are forward delay, hello time, and max age.
Forward delayForward delay is the delay time for port state transition.
A path failure can cause spanning tree re-calculation to adapt the spanning tree structure to the
change. However, the resulting new configuration BPDU cannot propagate throughout the
network immediately. If the newly elected root ports and designated ports start to forward data
immediately, a temporary loop will likely occur.
For this reason, as a mechanism for state transition in STP, the newly elected root ports or
designated ports require twice the forward delay time before they transit to the forwarding state to
make sure the new configuration BPDU has propagated throughout the network.
Hello timeThe device sends hello packets at the hello time interval to the neighboring devices to
make sure the paths are fault-free.
Max ageThe device uses the max age to determine whether a stored configuration BPDU has
expired and discards it if the max age is exceeded.
61
RSTP
RSTP achieves rapid network convergence by allowing a newly elected root port or designated port to
enter the forwarding state much faster than STP.
If the old root port on the device has stopped forwarding data and the upstream designated port has
started forwarding data, a newly elected RSTP root port rapidly enters the forwarding state.
A newly elected RSTP designated port rapidly enters the forwarding state if it is an edge port (a port that
directly connects to a user terminal rather than to another network device or a shared LAN segment) or
it connects to a point-to-point link. Edge ports directly enter the forwarding state. Connecting to a
point-to-point link, a designated port enters the forwarding state immediately after the device receives a
handshake response from the directly connected device.
MSTP
MSTP overcomes the following STP and RSTP limitations:
STP limitationsSTP does not support rapid state transition of ports. A newly elected port must wait
twice the forward delay time before it transits to the forwarding state, even if it connects to a
point-to-point link or is an edge port.
RSTP limitationsAlthough RSTP enables faster network convergence than STP, RSTP fails to
provide load balancing among VLANs. As with STP, all RSTP bridges in a LAN share one spanning
tree and forward packets from all VLANs along this spanning tree.
MSTP features
Developed based on IEEE 802.1s, MSTP overcomes the limitations of STP and RSTP. In addition to
supporting rapid network convergence, it provides a better load sharing mechanism for redundant links
by allowing data flows of different VLANs to be forwarded along separate paths.
MSTP provides the following features:
MSTP divides a switched network into multiple regions, each of which contains multiple spanning
trees that are independent of one another.
MSTP supports mapping VLANs to spanning tree instances by means of a VLAN-to-instance
mapping table. MSTP can reduce communication overheads and resource usage by mapping
multiple VLANs to one instance.
MSTP prunes a loop network into a loop-free tree, which avoids proliferation and endless cycling of
packets in a loop network. In addition, it supports load balancing of VLAN data by providing
multiple redundant paths for data forwarding.
MSTP is compatible with STP and RSTP.
MSTP basic concepts

Figure 17 shows a switched network that comprises four MST regions, each MST region comprising four
MSTP devices. Figure 18 shows the networking topology of MST region 3.
62
Figure 17 Basic concepts in MSTP
VLAN 1 MSTI 1 VLAN 1 MSTI 1

Other VLANs MSTI 0 Other VLANs MSTI 0
MST region 1 MST region 4
MST region 2 MST region 3

VLAN 2 MSTI 2 CST VLAN 2&3 MSTI 2
Other VLANs MSTI 0 Other VLANs MSTI 0
Figure 18 Network diagram and topology of MST region 3

To MST region 2
MST region
A multiple spanning tree region (MST region) consists of multiple devices in a switched network and the
network segments among them. All these devices have the following characteristics:
A spanning tree protocol enabled
Same region name
63
Same VLAN-to-instance mapping configuration
Same MSTP revision level
Physically linked together
Multiple MST regions can exist in a switched network. You can assign multiple devices to the same MST
region. In Figure 17, the switched network comprises four MST regions, MST region 1 through MST region
4, and all devices in each MST region have the same MST region configuration.
MSTI
MSTP can generate multiple independent spanning trees in an MST region, and each spanning tree is
mapped to the specific VLANs. Each spanning tree is referred to as a "multiple spanning tree instance
(MSTI)".
In Figure 18, MST region 3 comprises three MSTIs, MSTI 1, MSTI 2, and MSTI 0.
VLAN-to-instance mapping table

As an attribute of an MST region, the VLAN-to-instance mapping table describes the mapping
relationships between VLANs and MSTIs.
In Figure 18, the VLAN-to-instance mapping table of MST region 3 is: VLAN 1 to MSTI 1, VLAN 2 and
VLAN 3 to MSTI 2, and other VLANs to MSTI 0. MSTP achieves load balancing by means of the
VLAN-to-instance mapping table.
CST
The common spanning tree (CST) is a single spanning tree that connects all MST regions in a switched
network. If you regard each MST region as a device, the CST is a spanning tree calculated by these
devices through STP or RSTP.
The blue lines in Figure 17 represent the CST.
IST
An internal spanning tree (IST) is a spanning tree that runs in an MST region. It is also called MSTI 0, a
special MSTI to which all VLANs are mapped by default.
In Figure 17, MSTI 0 is the IST in MST region 3.
CIST
The common and internal spanning tree (CIST) is a single spanning tree that connects all devices in a
switched network. It consists of the ISTs in all MST regions and the CST.
In Figure 17, the ISTs (MSTI 0) in all MST regions plus the inter-region CST constitute the CIST of the entire
network.
Regional root
The root bridge of the IST or an MSTI within an MST region is the regional root of the IST or MSTI. Based
on the topology, different spanning trees in an MST region might have different regional roots.
In MST region 3 in Figure 18, the regional root of MSTI 1 is Device B, the regional root of MSTI 2 is Device
C, and the regional root of MSTI 0 (also known as the IST) is Device A.
Common root bridge

The common root bridge is the root bridge of the CIST.
In Figure 17, the common root bridge is a device in MST region 1.
64
Port roles
A port can play different roles in different MSTIs. As shown in Figure 19, an MST region comprises Device
A, Device B, Device C, and Device D. Port A1 and port A2 of Device A connect to the common root
bridge. Port B2 and Port B3 of Device B form a loop. Port C3 and Port C4 of Device C connect to other
MST regions. Port D3 of Device D directly connects to a host.
Figure 19 Port roles
MSTP calculation involves the following port roles:

Root portForwards data for a non-root bridge to the root bridge. The root bridge does not have
any root port.
Designated portForwards data to the downstream network segment or device.
Alternate portServes as the backup port for a root port or master port. When the root port or
master port is blocked, the alternate port takes over.
Backup portServes as the backup port of a designated port. When the designated port is invalid,
the backup port becomes the new designated port. A loop occurs when two ports of the same
spanning tree device are connected, so the device blocks one of the ports. The blocked port acts as
the backup.
Edge portDoes not connect to any network device or network segment, but directly connects to a
user host.
Master portServes as a port on the shortest path from the local MST region to the common root
bridge. The master port is not always located on the regional root. It is a root port on the IST or CIST
and still a master port on the other MSTIs.
Boundary portConnects an MST region to another MST region or to an STP/RSTP-running device.
In MSTP calculation, a boundary port's role on an MSTI is consistent with its role on the CIST. But
that is not true with master ports. A master port on MSTIs is a root port on the CIST.
Port states
In MSTP, a port can be in one of the following states:
65
ForwardingThe port receives and sends BPDUs, learns MAC addresses, and forwards user
traffic.
LearningThe port receives and sends BPDUs, learns MAC addresses, but does not forward user
traffic. Learning is an intermediate port state.
DiscardingThe port receives and sends BPDUs, but does not learn MAC addresses or forward
user traffic.
NOTE:
When in different MSTIs, a port can be in different states.
A port state is not exclusively associated with a port role. Table 8 lists the port states that each port role
supports. (A check mark [] indicates that the port supports this state, while a dash [] indicates that the
port does not support this state.)
Table 8 Port states that different port roles support
Port role (right) Root port/master

Designated port Alternate port Backup port
Port state (below) port
Forwarding
Learning
Discarding
How MSTP works

MSTP divides an entire Layer 2 network into multiple MST regions, which are connected by a calculated
CST. Inside an MST region, multiple spanning trees, called MSTIs, are calculated. Among these MSTIs,
MSTI 0 is the IST.
Like STP, MSTP uses configuration BPDUs to calculate spanning trees. An important difference is that an
MSTP BPDU carries the MSTP configuration of the bridge from which the BPDU is sent.
CIST calculation
The calculation of a CIST tree is also the process of configuration BPDU comparison. During this process,
the device with the highest priority is elected as the root bridge of the CIST. MSTP generates an IST within
each MST region through calculation. At the same time, MSTP regards each MST region as a single
device and generates a CST among these MST regions through calculation. The CST and ISTs constitute
the CIST of the entire network.
MSTI calculation
Within an MST region, MSTP generates different MSTIs for different VLANs based on the
VLAN-to-instance mappings. For each spanning tree, MSTP performs a separate calculation process
similar to spanning tree calculation in STP. For more information, see "Calculation process of the STP
algorithm."
In MSTP, a VLAN packet is forwarded along the following paths:
Within an MST region, the packet is forwarded along the corresponding MSTI.
Between two MST regions, the packet is forwarded along the CST.
66
MSTP implementation on devices
MSTP is compatible with STP and RSTP. Devices that are running MSTP and that are used for spanning
tree calculation can identify STP and RSTP protocol packets.
In addition to basic MSTP functions, the following functions are provided for ease of management:
Root bridge hold
Root bridge backup
Root guard
BPDU guard
Loop guard
TC-BPDU guard
Port role restriction
TC-BPDU transmission restriction
Support for hot swapping of interface cards
Protocols and standards

MSTP is documented in the following protocols and standards:
IEEE 802.1d, Media Access Control (MAC) Bridges
IEEE 802.1w, Part 3: Media Access Control (MAC) BridgesAmendment 2: Rapid Reconfiguration
IEEE 802.1s, Virtual Bridged Local Area NetworksAmendment 3: Multiple Spanning Trees
IEEE 802.1Q-REV/D1.3, Media Access Control (MAC) Bridges and Virtual Bridged Local Area
Networks Clause 13: Spanning tree Protocols
Spanning tree configuration task lists

Before configuring a spanning tree, you must determine the spanning tree protocol to be used (STP, RSTP,
or MSTP) and plan the device roles (the root bridge or leaf node).

When you configure the spanning tree feature, follow these restrictions and guidelines:
Configurations made in system view take effect globally. Configurations made in Ethernet interface
view or WLAN mesh interface view take effect on the interface only. Configurations made in Layer
2 aggregate interface view take effect only on the aggregate interface. Configurations made on an
aggregation member port can take effect only after the port is removed from the aggregation
group.
After you enable a spanning tree protocol on a Layer 2 aggregate interface, the system performs
spanning tree calculation on the Layer 2 aggregate interface, but not on the aggregation member
ports. The spanning tree protocol enable state and forwarding state of each selected member port
is consistent with those of the corresponding Layer 2 aggregate interface.
67
Though the member ports of an aggregation group do not participate in spanning tree calculation,
the ports still reserve their spanning tree configurations for participating in spanning tree
calculation after leaving the aggregation group.
STP configuration task list

Tasks at a glance
Configuring the root bridge:
(Required.) Setting the spanning tree mode
(Optional.) Configuring the root bridge or a secondary root bridge
(Optional.) Configuring the device priority
(Optional.) Configuring the network diameter of a switched network
(Optional.) Configuring spanning tree timers
(Optional.) Configuring the timeout factor
(Optional.) Configuring the BPDU transmission rate
(Optional.) Enabling outputting port state transition information
(Required.) Enabling the spanning tree feature
Configuring the leaf nodes:

(Optional.) Configuring path costs of ports
(Optional.) Configuring the port priority
(Optional.) Configuring protection functions
RSTP configuration task list

Tasks at a glance
(Optional.) Configuring edge ports
(Optional.) Configuring the port link type
68
Tasks at a glance
(Optional.) Performing mCheck
MSTP configuration task list

Tasks at a glance
(Required.) Configuring an MST region
(Optional.) Configuring the maximum hops of an MST region
(Optional.) Configuring the mode a port uses to recognize and send MSTP packets
69
Tasks at a glance
(Required.) Configuring an MST region
(Optional.) Configuring the mode a port uses to recognize and send MSTP packets
(Optional.) Performing mCheck
(Optional.) Configuring Digest Snooping
(Optional.) Configuring No Agreement Check
Setting the spanning tree mode

The spanning tree modes include:
STP modeAll ports of the device send STP BPDUs. Select this mode when the peer device of a port
supports only STP.
RSTP modeAll ports of the device send RSTP BPDUs. A port in this mode automatically transits to
the STP mode when it receives STP BPDUs from the peer device, and a port in this mode does not
transit to the MSTP mode when it receives MSTP BPDUs from the peer device.
MSTP modeAll ports of the device send MSTP BPDUs. A port in this mode automatically transits
to the STP mode when receiving STP BPDUs from the peer device, and a port in this mode does not
transit to the RSTP mode when receiving RSTP BPDUs from the peer device.
MSTP mode is compatible with RSTP mode, and RSTP mode is compatible with STP mode.
To set the spanning tree mode:

The default setting is the

2. Set the spanning tree mode. stp mode { mstp | rstp | stp }
MSTP mode.
70
NOTE:
In STP or RSTP mode, do not specify an MSTI. Otherwise, the spanning tree configuration does not take
effect.
In MSTP mode, if you specify an MSTI, the spanning tree configuration takes effect on the specified MSTI.
If you do not specify an MSTI, the spanning tree configuration takes effect on the CIST.
Configuring an MST region

Two or more spanning tree devices belong to the same MST region only if they are configured to have the
same format selector (0 by default, not configurable), MST region name, MST region revision level, and
the same VLAN-to-instance mapping entries in the MST region, and they are connected through a
physical link.
The configuration of MST region-related parameters (especially the VLAN-to-instance mapping table)
might cause MSTP to begin a new spanning tree calculation. To reduce the possibility of topology
instability, the MST region configuration takes effect only after you activate it by using the active
region-configuration command, or enable a spanning tree protocol by using the stp global enable
command if the spanning tree protocol is disabled.
To configure an MST region:

2. Enter MST region view. stp region-configuration N/A
3. Configure the MST region The default setting is the MAC
region-name name
name. address.
Use one of the commands.

4. Configure the instance instance-id vlan
VLAN-to-instance mapping vlan-id-list By default, all VLANs in an MST
table. region are mapped to the CIST (or
vlan-mapping modulo modulo
MSTI 0).
5. Configure the MSTP revision
revision-level level The default setting is 0.
level of the MST region.
6. (Optional.) Display the MST
region configurations that are check region-configuration N/A
not activated yet.
7. Manually activate MST region
active region-configuration N/A
configuration.
8. (Optional.) Display the
activated configuration
display stp region-configuration Available in any view.
information of the MST
region.
71
Configuring the root bridge or a secondary root
bridge
You can have the spanning tree protocol determine the root bridge of a spanning tree through MSTP
calculation, or you can specify the current device as the root bridge or as a secondary root bridge.
A device has independent roles in different spanning trees. It can act as the root bridge in one spanning
tree and as a secondary root bridge in another. However, one device cannot be the root bridge and a
secondary root bridge in the same spanning tree.
A spanning tree can have only one root bridge. If two or more devices are selected as the root bridge in
a spanning tree at the same time, the device with the lowest MAC address is chosen.
When the root bridge of an instance fails or is shut down, the secondary root bridge (if you have
specified one) becomes the root bridge if you have not specified a new root bridge. If you specify
multiple secondary root bridges for an instance, the secondary root bridge with the lowest MAC address
is given priority.
You can specify one root bridge for each spanning tree, regardless of the device priority settings. Once
you specify a device as the root bridge or a secondary root bridge, you cannot change its priority.
You can configure the current device as the root bridge by setting the device priority to 0. For the device
priority configuration, see "Configuring the device priority."
Configuring the current device as the root bridge of a specific

spanning tree
In STP/RSTP mode:
2. Configure the current
stp root primary By default, a device does not
device as the root
bridge. In MSTP mode: function as the root bridge.
stp [ instance instance-list ] root primary
Configuring the current device as a secondary root bridge of a

specific spanning tree
In STP/RSTP mode:
2. Configure the current stp root secondary By default, a device does not
device as a secondary root In MSTP mode: function as a secondary root
bridge. stp [ instance instance-list ] root bridge.
secondary
72
Configuring the device priority
Device priority is a factor in calculating the spanning tree. The priority of a device determines whether the
device can be elected as the root bridge of a spanning tree. A lower value indicates a higher priority.
You can set the priority of a device to a low value to specify the device as the root bridge of the spanning
tree. A spanning tree device can have different priorities in different MSTIs.
During root bridge selection, if all devices in a spanning tree have the same priority, the one with the
lowest MAC address is selected as the root bridge of the spanning tree. You cannot change the priority
of a device after it is configured as the root bridge or as a secondary root bridge.
To configure the priority of a device in a specified MSTI:

In STP/RSTP mode:
stp priority priority
2. Configure the priority of
the current device. In MSTP mode: The default setting is 32768.
stp [ instance instance-list ] priority
priority
Configuring the maximum hops of an MST region

Restrict the region size by setting the maximum hops of an MST region. The hop limit configured on the
regional root bridge is used as the hop limit for the MST region.
Configuration BPDUs sent by the regional root bridge always have a hop count set to the maximum value.
When a device receives this configuration BPDU, it decrements the hop count by one, and uses the new
hop count in the BPDUs that it propagates. When the hop count of a BPDU reaches zero, it is discarded
by the device that received it. Devices beyond the reach of the maximum hop can no longer participate
in spanning tree calculations, so the size of the MST region is limited.
Make this configuration only on the root bridge. All other devices in the MST region use the maximum
hop value set for the root bridge.
To configure the maximum number of hops of an MST region:

2. Configure the maximum hops
stp max-hops hops The default setting is 20.
of the MST region.
Configuring the network diameter of a switched

network
Any two terminal devices in a switched network are connected through a specific path composed of a
series of devices. The network diameter is the number of devices on the path composed of the most
73
devices. The network diameter is a parameter that indicates the network size. A bigger network diameter
indicates a larger network size.
Based on the network diameter you configured, the system automatically sets an optimal hello time,
forward delay, and max age for the device. Each MST region is considered a device and the configured
network diameter is effective only on the CIST (or the common root bridge) but not on other MSTIs.
To configure the network diameter of a switched network:

2. Configure the network
diameter of the switched stp bridge-diameter diameter The default setting is 7.
network.
Configuring spanning tree timers

The following timers are used for spanning tree calculation:
Forward delayDelay time for port state transition. To prevent temporary loops on a network, the
spanning tree feature sets an intermediate port state (the learning state) before it transits from the
discarding state to the forwarding state. The feature also requires that the port transit its state after
a forward delay timer to make sure the state transition of the local port stays synchronized with the
peer.
Hello timeInterval at which the device sends configuration BPDUs to detect link failures. If the
device receives no configuration BPDUs within the timeout time, it recalculates the spanning tree.
(Timeout time = timeout factor 3 hello time.)
Max ageIn the CIST of an MSTP network, the device uses the max age timer to determine if a
configuration BPDU received by a port has expired. If it has, a new spanning tree calculation
process starts. The max age timer does not take effect on other MSTIs except the CIST.
To avoid frequent network changes, make sure the timer settings meet the following formulas:
2 (forward delay 1 second) max age
Max age 2 (hello time + 1 second)
HP recommends not manually setting the spanning tree timers. HP recommends specifying the network
diameter and letting spanning tree protocols automatically calculate the timers based on the network
diameter. If the network diameter uses the default value, the timers also use their default values.
Configure the timers only on the root bridge. The timer settings on the root bridge apply to all devices on
the entire switched network.

The length of the forward delay timer is related to the network diameter of the switched network. The
larger the network diameter is, the longer the forward delay time should be. If the forward delay
timer is too short, temporary redundant paths might occur. If the forward delay timer is too long,
network convergence might take a long time. HP recommends using the default setting.
An appropriate hello time setting enables the device to promptly detect link failures on the network
without using excessive network resources. If the hello time is too long, the device mistakes packet
74
loss for a link failure and triggers a new spanning tree calculation process. If the hello time is too
short, the device frequently sends the same configuration BPDUs, which waste device and network
resources. HP recommends using the default setting.
If the max age timer is too short, the device frequently begins spanning tree calculations and might
mistake network congestion as a link failure. If the max age timer is too long, the device might fail
to promptly detect link failures and quickly launch spanning tree calculations, reducing the
auto-sensing capability of the network. HP recommends using the default setting.
To configure the spanning tree timers:

2. Configure the forward stp timer forward-delay
The default setting is 15 seconds.
delay timer. time
3. Configure the hello timer. stp timer hello time The default setting is 2 seconds.
4. Configure the max age

stp timer max-age time The default setting is 20 seconds.
timer.
Configuring the timeout factor

The timeout factor is a parameter used to decide the timeout time, in the following formula: Timeout time
= timeout factor 3 hello time.
After the network topology is stabilized, each non-root-bridge device forwards configuration BPDUs to
the downstream devices at the hello interval to detect link failures. If a device does not receive a BPDU
from the upstream device within nine times the hello time, it assumes that the upstream device has failed
and starts a new spanning tree calculation process.
Sometimes a device might fail to receive a BPDU from the upstream device because the upstream device
is busy. If a spanning tree calculation occurs, the calculation can fail and also waste network resources.
On a stable network, you can prevent undesired spanning tree calculations by setting the timeout factor
to 5, 6, or 7.
To configure the timeout factor:

2. Configure the timeout factor
stp timer-factor factor The default setting is 3.
of the device.
75
Configuring the BPDU transmission rate
The maximum number of BPDUs a port can send within each hello time equals the BPDU transmission
rate plus the hello timer value. Configure an appropriate BPDU transmission rate based on the physical
status of the port and the network structure.
The higher the BPDU transmission rate, the more BPDUs are sent within each hello time, and the more
system resources are used. By setting an appropriate BPDU transmission rate, you can limit the rate at
which the port sends BPDUs and prevent spanning tree protocols from using excessive network resources
when the network topology changes. HP recommends using the default setting.
To configure the BPDU transmission rate:

2. Enter Layer 2 Ethernet or
interface interface-type interface-number N/A
aggregate interface view.
3. Configure the BPDU
stp transmit-limit limit The default setting is 10.
transmission rate of the ports.
Configuring edge ports

If a port directly connects to a user terminal rather than another device or a shared LAN segment, this
port is regarded as an edge port. When network topology change occurs, an edge port will not cause
a temporary loop. Because a device does not determine whether a port is directly connected to a
terminal, you must manually configure the port as an edge port. After that, the port can rapidly transit
from the blocked state to the forwarding state.

If BPDU guard is disabled, a port set as an edge port becomes a non-edge port again if it receives
a BPDU from another port. To restore the edge port, re-enable it.
If a port directly connects to a user terminal, configure it as an edge port and enable BPDU guard
for it. This enables the port to quickly transit to the forwarding state when ensuring network security.
On a port, the loop guard function and the edge port setting are mutually exclusive.
To specify a port as an edge port:

3. Configure the current ports as By default, all ports are
stp edged-port
edge ports. non-edge ports.
76
Configuring path costs of ports
Path cost is a parameter related to the rate of a port. On a spanning tree device, a port can have different
path costs in different MSTIs. Setting appropriate path costs allows VLAN traffic flows to be forwarded
along different physical links, achieving VLAN-based load balancing.
You can have the device automatically calculate the default path cost, or you can configure the path cost
for ports.
Specifying a standard for the device to use when it calculates

the default path cost
CAUTION:
If you change the standard that the device uses to calculate the default path costs, you restore the path
costs to the default.
You can specify a standard for the device to use in automatic calculation for the default path cost. The
device supports the following standards:
dot1d-1998The device calculates the default path cost for ports based on IEEE 802.1d-1998.
dot1tThe device calculates the default path cost for ports based on IEEE 802.1t.
legacyThe device calculates the default path cost for ports based on a private standard.
When you specify a standard for the device to use when it calculates the default path cost, follow these
guidelines:
When it calculates the path cost for an aggregate interface, IEEE 802.1t takes into account the
number of Selected ports in its aggregation group, but IEEE 802.1d-1998 does not. The calculation
formula of IEEE 802.1t is: Path cost = 200,000,000/link speed (in 100 kbps), where link speed is
the sum of the link speed values of the Selected ports in the aggregation group.
IEEE 802.1d-1998 or the private standard always assigns the smallest possible value to a single port
or an aggregate interface when the link speed of the port or interface exceeds 10 Gbps. The
forwarding path selected based on this criterion might not be the best one. To solve this problem,
use dot1t as the standard for default path cost calculation, or manually set the path cost for the port
(see "Configuring path costs of ports").
To specify a standard for the device to use when it calculates the default path cost:

2. Specify a standard for the
device to use when it stp pathcost-standard
The default setting is legacy.
calculates the default path { dot1d-1998 | dot1t | legacy }
costs of its ports.
77
Table 9 Mappings between the link speed and the path cost
Path cost
Link speed Port type IEEE
IEEE 802.1t Private standard
802.1d-1998
0 N/A 65535 200000000 200000
Single port 2000000 2000
Aggregate interface
1000000 1800
containing 2 Selected ports
10 Mbps Aggregate interface 100
666666 1600
Aggregate interface
500000 1400
Aggregate interface
100000 180
66666 160
Aggregate interface
50000 140
Aggregate interface
10000 18
6666 16
Aggregate interface
5000 14
Single port 2000 2
Aggregate interface
1000 1
10 Gbps Aggregate interface 2
666 1
Aggregate interface
500 1
Configuring path costs of ports

78
In STP/RSTP mode:
stp cost cost By default, the system
3. Configure the path cost of the
automatically calculates the
ports. In MSTP mode:
path cost of each port.
stp [ instance instance-list ] cost cost
NOTE:
When the path cost of a port changes, the system re-calculates the role of the port and initiates a state
transition.
Configuration example
# In MSTP mode, configure the device to calculate the default path costs of its ports by using IEEE
802.1d-1998, and set the path cost of FortyGigE 1/0/3 to 200 on MSTI 2.
<Sysname> system-view
[Sysname] stp pathcost-standard dot1d-1998
Cost of every port will be reset and automatically re-calculated after you change the
current pathcost standard. Continue?[Y/N]:y
Cost of every port has been re-calculated.
[Sysname] interface fortygige 1/0/3
[Sysname-FortyGigE1/0/3] stp instance 2 cost 200
Configuring the port priority

The priority of a port is a factor that determines whether the port can be elected as the root port of a
device. If all other conditions are the same, the port with the highest priority is elected as the root port.
On a spanning tree device, a port can have different priorities and play different roles in different
spanning trees, so that data of different VLANs can be propagated along different physical paths,
implementing per-VLAN load balancing. You can set port priority values based on the actual networking
requirements.
To configure the priority of a port:

In STP/RSTP mode:
stp port priority priority
The default setting is 128
3. Configure the port priority. In MSTP mode:
for all ports.
stp [ instance instance-list ] port priority
priority
NOTE:
When the priority of a port changes, the system re-calculates the port role and initiates a state transition.
79
Configuring the port link type
A point-to-point link directly connects two devices. If two root ports or designated ports are connected
over a point-to-point link, they can rapidly transit to the forwarding state after a proposal-agreement
handshake process.

You can configure the link type as point-to-point for a Layer 2 aggregate interface or a port that
operates in full duplex mode. HP recommends using the default setting and letting the device
automatically detect the port link type.
The stp point-to-point force-false or stp point-to-point force-true command configured on a port in
MSTP mode is effective on all MSTIs.
If you configure a non-point-to-point link as a point-to-point link, the configuration might cause a
temporary loop.
To configure the link type of a port:

2. Enter Layer 2 Ethernet or interface interface-type
N/A
aggregate interface view. interface-number
By default, the link type is auto

stp point-to-point { auto | force-false
3. Configure the port link type. where the port automatically
| force-true }
detects the link type.
Configuring the mode a port uses to recognize and

send MSTP packets
A port can receive and send MSTP packets in the following formats:
dot1s802.1s-compliant standard format
legacyCompatible format
When the number of existing MSTIs exceeds 48, the port can send only 802.1s MSTP packets.
By default, the packet format recognition mode of a port is auto. The port automatically distinguishes the
two MSTP packet formats, and determines the format of packets that it will send based on the recognized
format.
You can configure the MSTP packet format on a port. When operating in MSTP mode after the
configuration, the port sends only MSTP packets of the format that you have configured to communicate
with devices that send packets of the same format.
80
A port in auto mode sends 802.1s MSTP packets by default. When the port receives an MSTP packet of
a legacy format, the port starts to send packets only of the legacy format. This prevents the port from
frequently changing the format of sent packets. To configure the port to send 802.1s MSTP packets, shut
down and then bring up the port.
To configure the MSTP packet format to be supported on a port:

3. Configure the mode that the
port uses to recognize/send stp compliance { auto | dot1s | legacy } The default setting is auto.
MSTP packets.
Enabling outputting port state transition information

In a large-scale spanning tree network, you can enable devices to output the port state transition
information of all MSTIs or the specified MSTI in order to monitor the port states in real time.
To enable outputting port state transition information:

In STP/RSTP mode:
stp port-log instance 0
2. Enable outputting port state By default, this function is
transition information. In MSTP mode:
enabled.
stp port-log { all | instance
instance-list }
Enabling the spanning tree feature

You must enable the spanning tree feature for the device before any other spanning tree related
configurations can take effect. Make sure the spanning tree feature is enabled globally and on the
desired ports.
You can disable the spanning tree feature for certain ports with the undo stp enable command to exclude
them from spanning tree calculation and save CPU resources of the device.
To enable the spanning tree feature:

81
If the device starts up with the initial settings
(or empty configuration), the spanning tree
feature is disabled globally.
If the device starts up with the default
2. Enable the spanning tree
stp global enable configuration file (or factory defaults), the
feature.
spanning tree feature is enabled globally.
For more information about the startup
configuration, see Fundamentals Configuration
Guide.
aggregate interface N/A
interface-number
view.
4. (Optional.) Enable the
By default, the spanning tree feature is enabled
spanning tree feature for stp enable
on all ports.
the port.
Performing mCheck
The mCheck feature enables user intervention in the port status transition process.
If a port on a device that is running MSTP or RSTP connects to an STP device, this port automatically
transits to STP mode when the port receives STP BPDUs. However, if the peer STP device is shut down or
removed and the local device cannot detect the change, the local device cannot automatically transit
back to the original mode. To forcibly transit the port to operate in the original mode, you can perform
an mCheck operation.
Suppose a scenario where Device A, Device B, and Device C are connected in sequence. Device A runs
STP, Device B does not run any spanning tree protocol, and Device C runs RSTP or MSTP. In this case,
when Device C receives an STP BPDU transparently transmitted by Device B, the receiving port transits to
the STP mode. If you configure Device B to run RSTP or MSTP with Device C, you must perform mCheck
operations on the ports interconnecting Device B and Device C.
The following methods for performing mCheck produce the same result.
Performing mCheck globally

Step Command
2. Perform mCheck. stp global mcheck
Performing mCheck in interface view

Step Command
82
Step Command
2. Enter Layer 2 Ethernet or aggregate interface
interface interface-type interface-number
view.
3. Perform mCheck. stp mcheck
NOTE:
An mCheck operation takes effect on a device that operates in MSTP or RSTP mode.
Configuring Digest Snooping

As defined in IEEE 802.1s, connected devices are in the same region only when their MST region-related
configurations (region name, revision level, and VLAN-to-instance mappings) are identical. A spanning
tree device identifies devices in the same MST region by determining the configuration ID in BPDU
packets. The configuration ID includes the region name, revision level, and configuration digest, which is
16-byte long and is the result calculated through the HMAC-MD5 algorithm based on VLAN-to-instance
mappings.
Because spanning tree implementations vary by vendor, the configuration digests calculated through
private keys are different. The devices of different vendors in the same MST region cannot communicate
with each other.
To enable communication between an HP device and a third-party device, enable the Digest Snooping
feature on the port that connects the HP device to the third-party device in the same MST region.

When you configure Digest Snooping, follow these guidelines:
Before you enable Digest Snooping, make sure associated devices of different vendors are
connected and run spanning tree protocols.
With digest snooping enabled, in-the-same-region verification does not require comparison of
configuration digest, so the VLAN-to-instance mappings must be the same on associated ports.
With digest snooping enabled globally, modify the VLAN-to-instance mappings or execute the
undo stp region-configuration command to restore the default MST region configuration with
caution. If the local device has different VLAN-to-instance mappings than its neighboring devices,
loops or traffic interruption occurs.
To make Digest Snooping take effect, you must enable Digest Snooping both globally and on
associated ports. HP recommends that you enable Digest Snooping on all associated ports first and
then enable it globally. This will make the configuration take effect on all configured ports and
reduce impact on the network.
To prevent loops, do not enable Digest Snooping on MST region edge ports.
HP recommends that you enable Digest Snooping first and then the spanning tree feature. To avoid
traffic interruption, do not configure Digest Snooping when the network is already working well.
83
You can enable Digest Snooping only on the HP device that is connected to a third-party device that uses
its private key to calculate the configuration digest.
To configure Digest Snooping:

N/A
3. Enable Digest Snooping on By default, Digest Snooping is

stp config-digest-snooping
the interface. disabled on ports.
4. Return to system view. quit N/A

5. Enable Digest Snooping By default, Digest Snooping is
stp global config-digest-snooping
globally. disabled globally.
Digest Snooping configuration example

As shown in Figure 20, Device A and Device B connect to Device C, which is a third-party device. All
these devices are in the same region.
Enable Digest Snooping on the ports of Device A and Device B that connect to Device C, so that the three
devices can communicate with one another.
MST region Device C

(Root bridge)
FGE1/0/1 FGE1/0/2 Root port
Designated port
Blocked port
Normal link
FGE1/0/1 FGE1/0/1
Blocked link
FGE1/0/2 FGE1/0/2
Device A Device B
# Enable Digest Snooping on FortyGigE 1/0/1 of Device A and enable global Digest Snooping on
Device A.
84
[DeviceA-FortyGigE1/0/1] stp config-digest-snooping
[DeviceA] stp global config-digest-snooping
# Enable Digest Snooping on FortyGigE 1/0/1 of Device B and enable global Digest Snooping on
Device B.
<DeviceB> system-view
[DeviceB] interface fortygige 1/0/1
[DeviceB-FortyGigE1/0/1] stp config-digest-snooping
[DeviceB-FortyGigE1/0/1] quit
[DeviceB] stp global config-digest-snooping
Configuring No Agreement Check

In RSTP and MSTP, the following types of messages are used for rapid state transition on designated
ports:
ProposalSent by designated ports to request rapid transition
AgreementUsed to acknowledge rapid transition requests
Both RSTP and MSTP devices can perform rapid transition on a designated port only when the port
receives an agreement packet from the downstream device. RSTP and MSTP devices have the following
differences:
For MSTP, the root port of the downstream device sends an agreement packet only after it receives
an agreement packet from the upstream device.
For RSTP, the downstream device sends an agreement packet regardless of whether an agreement
packet from the upstream device is received.
Figure 21 Rapid state transition of an MSTP designated port
85
Figure 22 Rapid state transition of an RSTP designated port
If the upstream device is a third-party device, the rapid state transition implementation might be limited.
For example, when the upstream device uses a rapid transition mechanism similar to that of RSTP, and the
downstream device adopts MSTP and does not operate in RSTP mode, the root port on the downstream
device receives no agreement packet from the upstream device and sends no agreement packets to the
upstream device. As a result, the designated port of the upstream device fails to transit rapidly, and can
only change to the forwarding state after a period twice the Forward Delay.
You can enable the No Agreement Check feature on the downstream device's port to enable the
designated port of the upstream device to transit its state rapidly.
Configuration prerequisites
Before you configure the No Agreement Check function, complete the following tasks:
Connect a device to a third-party upstream device that supports spanning tree protocols through a
point-to-point link.
Configure the same region name, revision level and VLAN-to-instance mappings on the two devices,
assigning them to the same region.
Enable the No Agreement Check feature on the root port.
To configure No Agreement Check:

3. Enable No Agreement By default, No Agreement
stp no-agreement-check
Check. Check is disabled.
86
No Agreement Check configuration example
Device A connects to a third-party device that has a different spanning tree implementation. Both
devices are in the same region.
The third-party device (Device B) is the regional root bridge, and Device A is the downstream
device.
# Enable No Agreement Check on FortyGigE 1/0/1 of Device A.
[DeviceA-FortyGigE1/0/1] stp no-agreement-check
Configuring protection functions

A spanning tree device supports the following protection functions:
BPDU guard
Root guard
Loop guard
Port role restriction
TC-BPDU transmission restriction
TC-BPDU guard
Enabling BPDU guard

For access layer devices, the access ports can directly connect to the user terminals (such as PCs) or file
servers. The access ports are configured as edge ports to allow rapid transition. When these ports
receive configuration BPDUs, the system automatically sets the ports as non-edge ports and starts a new
spanning tree calculation process. This causes a change of network topology. Under normal conditions,
these ports should not receive configuration BPDUs. However, if someone forges configuration BPDUs
maliciously to attack the devices, the network will become unstable.
The spanning tree protocol provides the BPDU guard function to protect the system against such attacks.
With the BPDU guard function enabled on the devices, when edge ports receive configuration BPDUs,
the system closes these ports and notifies the NMS that these ports have been closed by the spanning tree
87
protocol. The device reactivates the closed ports after a detection interval. For more information about
this detection interval, see Fundamentals Configuration Guide.
BPDU guard does not take effect on loopback-testing-enabled ports. For more information about
loopback testing, see "Configuring Ethernet interfaces."
Configure BPDU guard on a device with edge ports configured.
To enable BPDU guard:

2. Enable the BPDU guard By default, BPDU guard is
stp bpdu-protection
function for the device. disabled.
Enabling root guard

The root bridge and secondary root bridge of a spanning tree should be located in the same MST region.
Especially for the CIST, the root bridge and secondary root bridge are put in a high-bandwidth core
region during network design. However, due to possible configuration errors or malicious attacks in the
network, the legal root bridge might receive a configuration BPDU with a higher priority. Another device
supersedes the current legal root bridge, causing an undesired change of the network topology. The
traffic that should go over high-speed links is switched to low-speed links, resulting in network
congestion.
To prevent this situation, MSTP provides the root guard function. If the root guard function is enabled on
a port of a root bridge, this port plays the role of designated port on all MSTIs. After this port receives a
configuration BPDU with a higher priority from an MSTI, it immediately sets that port to the listening state
in the MSTI, without forwarding the packet. This is equivalent to disconnecting the link connected with
this port in the MSTI. If the port receives no BPDUs with a higher priority within twice the forwarding delay,
it reverts to its original state.
On a port, the loop guard function and the root guard function are mutually exclusive.
Configure root guard on a designated port.
To enable root guard:

3. Enable the root guard By default, root guard is
stp root-protection
function. disabled.
Enabling loop guard

By continuing to receive BPDUs from the upstream device, a device can maintain the state of the root port
and blocked ports. However, link congestion or unidirectional link failures might cause these ports to fail
to receive BPDUs from the upstream devices. The device reselects the port roles: Those ports in forwarding
state that failed to receive upstream BPDUs become designated ports, and the blocked ports transit to the
88
forwarding state, resulting in loops in the switched network. The loop guard function can suppress the
occurrence of such loops.
The initial state of a loop guard-enabled port is discarding in every MSTI. When the port receives BPDUs,
it transits its state. Otherwise, it stays in the discarding state to prevent temporary loops.
Do not enable loop guard on a port that connects user terminals. Otherwise, the port stays in the
discarding state in all MSTIs because it cannot receive BPDUs.
On a port, the loop guard function is mutually exclusive with the root guard function or the edge port
setting.
Configure loop guard on the root port and alternate ports of a device.
To enable loop guard:

3. Enable the loop guard By default, loop guard is
stp loop-protection
function for the ports. disabled.
Configuring port role restriction

CAUTION:
Use this feature with caution, because enabling port role restriction on a port might affect the connectivity
of the spanning tree topology.
The change to the bridge ID of a device in the user access network might cause a change to the spanning
tree topology in the core network. To avoid this problem, you can enable port role restriction on a port.
With this feature enabled, when the port receives a superior BPDU, it becomes an alternate port rather
than a root port.
Make this configuration on the port that connects to the user access network.
To configure port role restriction:

N/A
By default, port role restriction is

3. Enable port role restriction. stp role-restriction
disabled.
89
Configuring TC-BPDU transmission restriction
CAUTION:
Enabling TC-BPDU transmission restriction on a port might cause the previous forwarding address table to
fail to be updated when the topology changes.
The topology change to the user access network might cause the forwarding address changes to the core
network. When the user access network topology is unstable, the user access network might affect the
core network. To avoid this problem, you can enable TC-BPDU transmission restriction on a port. With
this feature enabled, when the port receives a TC-BPDU, it does not forward the TC-BPDU to other ports.
Make this configuration on the port that connects to the user access network.
To configure TC-BPDU transmission restriction:

N/A
3. Enable TC-BPDU transmission By default, TC-BPDU transmission
stp tc-restriction
restriction. restriction is disabled.
Enabling TC-BPDU guard

When a device receives topology change (TC) BPDUs (the BPDUs that notify devices of topology
changes), it flushes its forwarding address entries. If someone forges TC-BPDUs to attack the device, the
device will receive a large number of TC-BPDUs within a short time and be busy with forwarding address
entry flushing. This affects network stability.
With the TC-BPDU guard function, you can set the maximum number of immediate forwarding address
entry flushes that the device can perform within a specified period of time (10 seconds) after it receives
the first TC-BPDU. For TC-BPDUs received in excess of the limit, the device performs a forwarding address
entry flush when the time period expires. This prevents frequent flushing of forwarding address entries.
To enable TC-BPDU guard:

By default, TC-BPDU guard is

enabled.
2. Enable the TC-BPDU guard function. stp tc-protection
HP recommends not
disabling this feature.
3. (Optional.) Configure the maximum
number of forwarding address entry stp tc-protection threshold
flushes that the device can perform every number
10 seconds.
90
Displaying and maintaining the spanning tree
Execute display commands in any view and reset command in user view.
Task Command
Display information about ports blocked by spanning tree
display stp abnormal-port
protection functions.
display stp bpdu-statistics [ interface

Display BPDU statistics on ports. interface-type interface-number [ instance
instance-list ] ]
Display information about ports shut down by spanning

display stp down-port
tree protection functions.
Display the historical information of port role calculation display stp [ instance instance-list ] history [ slot
for the specified MSTI or all MSTIs (in standalone mode). slot-number ]
Display the historical information of port role calculation display stp [ instance instance-list ] history [ chassis
for the specified MSTI or all MSTIs (in IRF mode). chassis-number slot slot-number ]
Display the statistics of TC/TCN BPDUs sent and received

display stp [ instance instance-list ] tc [ slot
by all ports in the specified MSTI or all MSTIs (in
slot-number ]
standalone mode).
Display the statistics of TC/TCN BPDUs sent and received

display stp [ instance instance-list ] tc [ chassis
by all ports in the specified MSTI or all MSTIs (in IRF
chassis-number slot slot-number ]
mode).
Display the spanning tree status and statistics (in display stp [ instance instance-list ] [ interface
standalone mode). interface-list | slot slot-number ] [ brief ]
display stp [ instance instance-list ] [ interface

Display the spanning tree status and statistics (in IRF
interface-list | chassis chassis-number slot
mode).
slot-number ] [ brief ]
Display the MST region configuration information that has

display stp region-configuration
taken effect.
Display the root bridge information of all MSTIs. display stp root
Clear the spanning tree statistics. reset stp [ interface interface-list ]
Spanning tree configuration example

As shown in Figure 24, all devices on the network are in the same MST region. Device A and Device B
work at the distribution layer. Device C and Device D work at the access layer.
Configure MSTP so that packets of different VLANs are forwarded along different spanning trees: Packets
of VLAN 10 are forwarded along MSTI 1, those of VLAN 30 are forwarded along MSTI 3, those of VLAN
40 are forwarded along MSTI 4, and those of VLAN 20 are forwarded along MSTI 0.
91
VLAN 10 and VLAN 30 are terminated on the distribution layer devices, and VLAN 40 is terminated on
the access layer devices. The root bridges of MSTI 1 and MSTI 3 are Device A and Device B, respectively,
and the root bridge of MSTI 4 is Device C.
MST region
Device A Device B
Permit: all VLAN
FGE1/0/3 FGE1/0/3
FG 2
E1 /0/
/0/ E1
2 FG
Permit: VLAN 10, 20 Permit: VLAN 20, 30

0 Pe
,2 rm
N 10 it:
V
LA LA
V N2
it: 0, FG
/2 rm 3 E1
1/0 Pe 0 /0/
F GE 2
FGE1/0/3 FGE1/0/3
Permit: VLAN 20, 40
Device C Device D
1. Configure VLANs and VLAN member ports: (Details not shown.)
{ Create VLAN 10, VLAN 20, and VLAN 30 on both Device A and Device B.
{ Create VLAN 10, VLAN 20, and VLAN 40 on Device C.
{ Create VLAN 20, VLAN 30, and VLAN 40 on Device D.
{ Configure the ports on these devices as trunk ports and assign them to related VLANs.
# Enter MST region view, and configure the MST region name as example.
[DeviceA] stp region-configuration
[DeviceA-mst-region] region-name example
# Map VLAN 10, VLAN 30, and VLAN 40 to MSTI 1, MSTI 3, and MSTI 4, respectively.
[DeviceA-mst-region] instance 1 vlan 10
# Configure the revision level of the MST region as 0.
[DeviceA-mst-region] revision-level 0
# Activate MST region configuration.
[DeviceA-mst-region] active region-configuration
[DeviceA-mst-region] quit
# Specify the current device as the root bridge of MSTI 1.
[DeviceA] stp instance 1 root primary
# Enable the spanning tree feature globally.
[DeviceA] stp global enable
92
3. Configure Device B:
[DeviceB] stp region-configuration
[DeviceB-mst-region] region-name example
[DeviceB-mst-region] instance 1 vlan 10
[DeviceB-mst-region] revision-level 0
[DeviceB-mst-region] active region-configuration
[DeviceB-mst-region] quit
[DeviceB] stp instance 3 root primary
[DeviceB] stp global enable
4. Configure Device C:
<DeviceC> system-view
[DeviceC] stp region-configuration
[DeviceC-mst-region] region-name example
[DeviceC-mst-region] instance 1 vlan 10
[DeviceC-mst-region] revision-level 0
[DeviceC-mst-region] active region-configuration
[DeviceC-mst-region] quit
[DeviceC] stp instance 4 root primary
[DeviceC] stp global enable
5. Configure Device D:
<DeviceD> system-view
[DeviceD] stp region-configuration
[DeviceD-mst-region] region-name example
[DeviceD-mst-region] instance 1 vlan 10
93
[DeviceD-mst-region] revision-level 0
[DeviceD-mst-region] active region-configuration
[DeviceD-mst-region] quit
[DeviceD] stp global enable

In this example, suppose that Device B has the lowest root bridge ID. As a result, Device B is elected as
the root bridge in MSTI 0.
You can use the display stp brief command to display brief spanning tree information on each device
after the network is stable.
# Display brief spanning tree information on Device A.
[DeviceA] display stp brief
[DeviceA] display stp brief
MSTID Port Role STP State Protection
0 FortyGigE1/0/1 ALTE DISCARDING NONE
0 FortyGigE1/0/2 DESI FORWARDING NONE
0 FortyGigE1/0/3 ROOT FORWARDING NONE
# Display brief spanning tree information on Device B.

[DeviceB] display stp brief
# Display brief spanning tree information on Device C.

[DeviceC] display stp brief
# Display brief spanning tree information on Device D.

[DeviceD] display stp brief
94
Based on the output, you can draw each MSTI mapped to each VLAN, as shown in Figure 25.
Figure 25 MSTIs mapped to different VLANs
A B A B
C C D
MSTI 1 mapped to VLAN 10 MSTI 0 mapped to VLAN 20
A B
D C D
MSTI 3 mapped to VLAN 30 MSTI 4 mapped to VLAN 40
Root bridge Normal link Blocked link
95
Configuring loop detection
Overview
Incorrect network connections or configurations can create Layer 2 loops, which results in repeated
transmission of broadcasts, multicasts, or unknown unicasts, waste network resources, and sometimes
even paralyze networks. The loop detection mechanism immediately generates a log when a loop occurs
so that you are promptly notified to adjust network connections and configurations. You can even
configure loop detection to shut down the looped port. Logs are maintained in the information center. For
more information, see Network Management and Monitoring Configuration Guide.
Loop detection mechanism

The device detects loops by sending detection frames and then checking whether these frames return to
any port on the device. If they do, the device considers that the port is on a looped link.
Figure 26 Ethernet frame header for loop detection
The Ethernet frame header for loop detection contains the following fields:
DMACDestination MAC address of the frame, which is the multicast MAC address
010F-E200-0007. When a loop detection-enabled device receives a frame with this destination
MAC address, it sends the frame to the CPU and floods the frame in the VLAN from which the frame
was originally received.
SMACSource MAC address of the frame, which is the bridge MAC address of the sending
device.
TPIDType of the VLAN tag, with the value of 0x8100.
TCIInformation of the VLAN tag, including the priority and VLAN ID.
TypeProtocol type, with the value of 0x8918.
Figure 27 Inner frame header for loop detection
The inner frame header for loop detection contains the following fields:
CodeProtocol sub-type, which is 0x0001, indicating the loop detection protocol.
96
VersionProtocol version, which is always 0x0000.
LengthLength of the frame. The value includes the inner header, but excludes the Ethernet header.
ReservedThis field is reserved.
Frames for loop detection are encapsulated as TLV triplets.
Table 10 TLVs supported by loop detection
TLV Description Remarks
End of PDU End of a PDU. Optional.
Device ID Bridge MAC address of the sending device. Required.
Port ID ID of the PDU sending port. Optional.
Port Name Name of the PDU sending port. Optional.
System Name Device name. Optional.
Chassis ID Chassis ID of the sending port. Optional.
Slot ID Slot ID of the sending port. Optional.
Sub Slot ID Sub-slot ID of the sending port. Optional.
Loop detection uses the following important concepts.
Loop detection interval

Loop detection is a continuous process as the network changes. Loop detection frames are sent at a
specified interval (called a "loop detection interval") to check whether loops occur on ports and whether
loops are removed.
Loop protection actions

When the device detects a loop on a port, it generates a log but performs no action on the port by default.
You can configure the device to take one of the following actions:
BlockDisables the port from learning MAC addresses and blocks inbound traffic to the port.
No-learningDisables the port from learning MAC addresses.
ShutdownShuts down the port to disable it from receiving and sending any frames. The port is
always in the down state until manually brought up with the undo shutdown command.
Port status auto recovery

Port status auto recovery applies only to the block and no-learning loop protection actions. If the device
receives no loop detection frame three loop detection intervals after a loop is detected on a port, the
device automatically sets the port to the forwarding state, and notifies the user of the event.
NOTE:
Incorrect recovery can occur when loop detection frames are discarded to reduce the load. To avoid this,
use the shutdown action, or manually remove the loop.
97
Loop detection configuration task list
Tasks at a glance
(Required.) Enabling loop detection
(Optional.) Configuring the loop protection action
(Optional.) Setting the loop detection interval
Enabling loop detection

You can enable loop detection globally or on specific ports. The global configuration applies to all ports
in the specified VLAN. The per-port configuration applies to the individual port only when the port
belongs to the specified VLAN. Per-port configurations take precedence over global configurations.
Enabling loop detection globally

2. Globally enable loop loopback-detection global enable
Disabled by default.
detection. vlan { vlan-list | all }
Enabling loop detection on a port

2. Enter Layer 2 Ethernet interface
view or Layer 2 aggregate N/A
interface-number
interface view.
3. Enable loop detection on the loopback-detection enable vlan
Disabled by default.
port. { vlan-list | all }
Configuring the loop protection action

You can configure the loop protection action globally or on specific ports. The global configuration
applies to all ports. The per-port configuration applies to the individual ports. The per-port configuration
takes precedence over the global configuration.
98
Configuring the global loop protection action
By default, the device generates a

2. Configure the global loop loopback-detection global action
log but performs no action on the
protection action. shutdown
port on which a loop is detected.
Configuring the loop protection action on a Layer 2 Ethernet

interface
2. Enter Layer 2 Ethernet interface interface interface-type
N/A
By default, the device generates

3. Configure the loop protection loopback-detection action { block | a log but performs no action on
action on the interface. no-learning | shutdown } the port on which a loop is
detected.
Configuring the loop protection action on a Layer 2 aggregate

interface
N/A
By default, the device generates

3. Configure the loop protection loopback-detection action a log but performs no action on
action on the interface. shutdown the port on which a loop is
detected.
Setting the loop detection interval

With loop detection enabled, the device sends loop detection frames at a specified interval. A shorter
interval offers more sensitive detection but consumes more resources. Consider the system performance
and loop detection speed when you set the loop detection interval.
To set the loop detection interval:
99
loopback-detection interval-time
2. Set the loop detection interval. The default setting is 30 seconds.
interval
Displaying and maintaining loop detection

Task Command
Display the loop detection configuration and status. display loopback-detection
Loop detection configuration example

As shown in Figure 28, configure loop detection on Device A, so that Device A generates a log as a
notification and automatically shuts down the port on which a loop is detected.
Device A
FGE1/0/1 FGE1/0/2
Device B Device C
VLAN 100
# Create VLAN 100, and globally enable loop detection for the VLAN.
[DeviceA] vlan 100
100
[DeviceA] loopback-detection global enable vlan 100
# Configure FortyGigE 1/0/1 and FortyGigE 1/0/2 as trunk ports, and assign them to VLAN
100.
[DeviceA-FortyGigE1/0/1] port link-type trunk
[DeviceA-FortyGigE1/0/1] port trunk permit vlan 100
[DeviceA-FortyGigE1/0/2] port trunk permit vlan 100
# Configure the global loop protection action as shutdown.
[DeviceA] loopback-detection global action shutdown
# Set the loop detection interval to 35 seconds.
[DeviceA] loopback-detection interval-time 35
2. Configure Device B:
# Create VLAN 100.
[DeviceB] vlan 100
[DeviceBvlan100] quit
100.
[DeviceB-FortyGigE1/0/1] port link-type trunk
[DeviceB-FortyGigE1/0/1] port trunk permit vlan 100
[DeviceB-FortyGigE1/0/2] port link-type trunk
[DeviceB-FortyGigE1/0/2] port trunk permit vlan 100
3. Configure Device C:
# Create VLAN 100.
<DeviceC> system-view
[DeviceC] vlan 100
[DeviceCvlan100] quit
100.
[DeviceC] interface fortygige 1/0/1
[DeviceC-FortyGigE1/0/1] port link-type trunk
[DeviceC-FortyGigE1/0/1] port trunk permit vlan 100
[DeviceC-FortyGigE1/0/1] quit
[DeviceC] interface fortygige 1/0/2
[DeviceC-FortyGigE1/0/2] port link-type trunk
[DeviceC-FortyGigE1/0/2] port trunk permit vlan 100
[DeviceC-FortyGigE1/0/2] quit
101
After the configurations are complete, Device A detects loops on ports FortyGigE 1/0/1 and
FortyGigE 1/0/2 within a loop detection interval. Consequently, Device A automatically shuts
down the ports and generates the following log messages:
[DeviceA]
%Feb 24 15:04:29:663 2011 DeviceA LPDT/4/LOOPED:Slot=1;
Loopback exists on FortyGigE 1/0/1.
%Feb 24 15:04:29:667 2011 DeviceA LPDT/4/LOOPED:Slot=1;
Loopback exists on FortyGigE 1/0/2.
%Feb 24 15:04:44:243 2011 DeviceA LPDT/4/RECOVERED:Slot=1;
Loopback on FortyGigE 1/0/1 recovered.
%Feb 24 15:04:44:248 2011 DeviceA LPDT/4/RECOVERED:Slot=1;
Loopback on FortyGigE 1/0/2 recovered.
Use the display loopback-detection command to display the loop detection configuration and
status on Device A.
# Display the loop detection configuration and status on Device A.
[DeviceA] display loopback-detection
Loop detection is enabled.
Loop detection interval is 35 second(s).
No loopback is detected.
The output shows that the device has removed the loops from FortyGigE 1/0/1 and FortyGigE
1/0/2 according to the shutdown action. Use the display interface command to display the status
of FortyGigE 1/0/1 and FortyGigE 1/0/2 on Device A.
# Display the status of FortyGigE 1/0/1 on Device A.
[DeviceA] display interface fortygige 1/0/1
FortyGigE 1/0/1 current state: DOWN (Loop detection down)
...
# Display the status of FortyGigE 1/0/2 on Device A.
[DeviceA] display interface fortygige 1/0/2
FortyGigE 1/0/2 current state: DOWN (Loop detection down)
...
The output shows that FortyGigE 1/0/1 and FortyGigE 1/0/2 are already shut down by the loop
detection module.
102
Configuring VLANs
This chapter provides an overview of VLANs and explains how to configure them.
Overview
Ethernet is a family of shared-media LAN technologies based on the CSMA/CD mechanism. An Ethernet
LAN is both a collision domain and a broadcast domain. Because the medium is shared, collisions and
broadcasts are common in an Ethernet LAN. Typically, bridges and Layer 2 switches can reduce
collisions in an Ethernet LAN. To confine broadcasts, a Layer 2 switch must use the Virtual Local Area
Network (VLAN) technology.
VLANs enable a Layer 2 switch to break a LAN down into smaller broadcast domains, as shown
in Figure 29.
Figure 29 A VLAN diagram
VLAN 2
Switch A Switch B
Router
VLAN 5
A VLAN is logically divided on an organizational basis rather than on a physical basis. For example, you
can assign all workstations and servers used by a particular workgroup to the same VLAN, regardless of
their physical locations. Hosts in the same VLAN can directly communicate with one another. You need
a router or a Layer 3 switch for hosts in different VLANs to communicate with one another.
All these VLAN features reduce bandwidth waste, improve LAN security, and enable flexible virtual
group creation.
VLAN frame encapsulation

To identify Ethernet frames from different VLANs, IEEE 802.1Q inserts a four-byte VLAN tag between the
destination and source MAC address (DA & SA) field and the upper layer protocol type (Type) field, as
shown in Figure 30.
103
Figure 30 VLAN tag placement and format
A VLAN tag includes the following fields:

TPID16-bit tag protocol identifier that indicates whether a frame is VLAN-tagged. By default, the
TPID value is 0x8100, indicating that the frame is VLAN-tagged. However, device vendors can set
TPID to different values. For compatibility with neighbor devices, configure the TPID value on the
device to be the same as the neighbor device.
Priority3-bit long 802.1p priority of the frame. For more information, see ACL and QoS
CFI1-bit long canonical format indicator that indicates whether the MAC addresses are
encapsulated in the standard format when packets are transmitted across different media. Value 0
(the default) indicates that the MAC addresses are encapsulated in the standard format. Value 1
indicates that MAC addresses are encapsulated in a non-standard format. The CFI is 0 in Ethernet.
VLAN ID12-bit long, identifies the VLAN that the frame belongs to. The VLAN ID range is 0 to
4095. VLAN IDs 0 and 4095 are reserved, and VLAN IDs 1 to 4094 are user configurable.
A network device handles an incoming frame depending on whether the frame is VLAN tagged and the
value of the VLAN tag, if any. For more information, see "Introduction to port-based VLAN."
Ethernet supports encapsulation formats Ethernet II, 802.3/802.2 LLC, 802.3/802.2 SNAP, and 802.3
raw. The Ethernet II encapsulation format is used here. For how the VLAN tag fields are added to frames
encapsulated in the other formats for VLAN identification, see related protocols and standards.
For a frame with multiple VLAN tags, the device handles it according to its outer-most VLAN tag and
transmits its inner VLAN tags as payload.

IEEE 802.1Q, IEEE Standard for Local and Metropolitan Area Networks: Virtual Bridged Local Area
Networks
Configuring basic VLAN settings

2. (Optional.) Create a
vlan { vlan-id1 [ to vlan-id2 ] | By default, only the system default VLAN
VLAN and enter its view,
all } (VLAN 1) exists.
or create a list of VLANs.
To configure a specific VLAN after you

3. Enter VLAN view. vlan vlan-id create a list of VLANs, you must perform
this step.
By default, VLAN names are in the format

4. Configure a name for
name text VLAN vlan-id. For example, the name of
the VLAN.
VLAN 100 is VLAN 0100 by default.
104
The default setting is VLAN vlan-id, which is
5. Configure the the ID of the VLAN. For example, the
description text
description of the VLAN. description of VLAN 100 is VLAN 0100 by
default.
NOTE:
As the system default VLAN, VLAN 1 cannot be created or removed.
You cannot use the undo vlan command to delete a dynamic VLAN, a VLAN with a QoS policy
applied, or a VLAN locked by an application. To delete such a VLAN, first remove the configuration
from the VLAN.
Configuring basic settings of a VLAN interface

For hosts of different VLANs to communicate at Layer 3, you can use VLAN interfaces. VLAN interfaces
are virtual interfaces used for Layer 3 communication between different VLANs. They do not exist as
physical entities on devices. For each VLAN, you can create one VLAN interface. You can assign the
VLAN interface an IP address and specify it as the gateway of the VLAN to forward packets destined for
an IP subnet different from that of the VLAN.
When you configure a VLAN interface, follow these guidelines:
Before you create a VLAN interface for a VLAN, create the VLAN first.
You cannot create a VLAN interface for a sub VLAN.
To configure basic settings of a VLAN interface:

2. Create a VLAN interface If the VLAN interface already exists, you

interface vlan-interface enter its view directly.
and enter VLAN interface
vlan-interface-id
view. By default, no VLAN interface is created.
3. Assign an IP address to the ip address ip-address { mask | By default, no IP address is assigned to
VLAN interface. mask-length } [ sub ] any VLAN interface.
The default setting is the VLAN interface

4. Configure the description
description text name. For example, Vlan-interface1
of the VLAN interface.
Interface.
5. (Optional.) Specify a line
processing unit (LPU) for
forwarding the traffic on service slot slot-number By default, no LPU is specified.
the current VLAN interface
(in standalone mode).
6. (Optional.) Specify an LPU
for forwarding the traffic on service chassis chassis-number By default, no IRF member device or LPU
the current VLAN interface slot slot-number is specified.
(in IRF mode).
105
By default, the expected bandwidth (in
bandwidth bandwidth-value kbps) is the interface baud rate divided
bandwidth of the interface.
by 1000.
8. (Optional.) Restore the
default settings for the default N/A
VLAN interface.
By default, a VLAN interface is not

9. (Optional.) Cancel the manually shut down. The VLAN interface
action of manually shutting undo shutdown is up if one or more ports in the VLAN is
down the VLAN interface. up, and goes down if all ports in the
VLAN go down.
Configuring port-based VLANs

Introduction to port-based VLAN
Port-based VLANs group VLAN members by port. A port forwards packets from a VLAN only after it is
assigned to the VLAN.
Port link type

You can configure the link type of a port as access, trunk, or hybrid. The link types use the following
VLAN tag handling methods:
AccessAn access port can forward packets from only one specific VLAN and send these packets
untagged. An access port can connect a terminal device that does not support VLAN packets or is
used in scenarios that do not distinguish VLANs.
TrunkA trunk port can forward packets from multiple VLANs. Except packets from the port VLAN
ID (PVID), packets sent out of a trunk port are VLAN-tagged. Ports connecting network devices are
typically configured as trunk ports.
HybridA hybrid port can forward packets from multiple VLANs. A hybrid port allows traffic from
some VLANs to pass through untagged and traffic from other VLANs to pass through tagged. A
hybrid port can connect a network device or terminal device.
PVID
The PVID identifies the default VLAN of a port.
When you configure the PVID on a port, follow these restrictions and guidelines:
An access port can join only one VLAN. The VLAN to which the access port belongs is the PVID of
the port.
A trunk or hybrid port can carry multiple VLANs, and you can configure a PVID for the port.
You can use a nonexistent VLAN as the PVID for a hybrid or trunk port, but not for an access port.
After you remove the VLAN that an access port resides in with the undo vlan command, the PVID
of the port changes to VLAN 1. However, the removal of the VLAN specified as the PVID of a trunk
or hybrid port does not affect the PVID setting on the port.
HP recommends that you set the same PVID for local and remote ports.
106
Make sure a port is assigned to its PVID. Otherwise, when the port receives frames tagged with the
PVID or untagged frames, the port filters out these frames.
How ports of different link types handle frames
Actions Access Trunk Hybrid

In the
inbound If the PVID is permitted on the port, tags the frame with the PVID
Tags the frame with the tag.
direction for
PVID tag.
an untagged If not, drops the frame.
frame
Receives the frame if
In the its VLAN ID is the
inbound same as the PVID. Receives the frame if its VLAN is permitted on the port.
direction for
Drops the frame if its Drops the frame if its VLAN is not permitted on the port.
a tagged
VLAN ID is different
frame
from the PVID.
Removes the tag and sends
the frame if the frame carries Sends the frame if its VLAN is
the PVID tag and the port permitted on the port. The frame
In the belongs to the PVID. is sent with the VLAN tag
Removes the VLAN tag
outbound removed or intact depending on
and sends the frame. Sends the frame without
direction your configuration with the port
removing the tag if its VLAN
hybrid vlan command. This is
is carried on the port but is
true of the PVID.
different from the PVID.
Assigning an access port to a VLAN

You can assign an access port to a VLAN in VLAN view or interface view.
Make sure the VLAN has been created.
Assigning one or multiple access ports to a VLAN in VLAN view

2. Enter VLAN view. vlan vlan-id N/A
3. Assign one or a group of By default, all ports belong to
port interface-list
access ports to the VLAN. VLAN 1.
Assigning an access port to a VLAN in interface view

107
The configuration made in Layer 2
Ethernet interface view applies
only to the port.
Enter Layer 2 Ethernet The configuration made in Layer 2
interface view: aggregate interface view applies
interface interface-type to the aggregate interface and its
interface-number aggregation member ports. If the
2. Enter interface view. system fails to apply the
configuration to an aggregation
interface view:
member port, it skips the port and
interface
moves to the next member port. If
bridge-aggregation
the system fails to apply the
interface-number
configuration to the aggregate
interface, it stops applying the
configuration to aggregation
member ports.
3. Configure the link type of the
port link-type access By default, all ports are access ports.
ports as access.
4. (Optional.) Assign the access By default, all access ports belong to
port access vlan vlan-id
ports to a VLAN. VLAN 1.
Assigning a trunk port to a VLAN

A trunk port can carry multiple VLANs. You can assign it to a VLAN in interface view.
When you assign a trunk port to a VLAN, follow these guidelines:
To change the link type of a port from trunk to hybrid or vice versa, set the link type to access first.
You must configure the trunk port to allow packets from the PVID to pass through by using the port
trunk permit vlan command.
To assign a trunk port to one or multiple VLANs:

108
The configuration made in
Layer 2 Ethernet interface view
applies only to the port.
Enter Layer 2 Ethernet interface Layer 2 aggregate interface
view: view applies to the aggregate
interface interface-type interface and its aggregation
interface-number member ports. If the system fails
2. Enter interface view. to apply the configuration to an
aggregation member port, it
interface view:
skips the port and moves to the
next member port. If the system
interface-number
fails to apply the configuration
to the aggregate interface, it
stops applying the
member ports.
3. Configure the link type of the By default, all ports are access
port link-type trunk
ports as trunk. ports.
4. Assign the trunk ports to the port trunk permit vlan { vlan-id-list By default, a trunk port only permits
specified VLANs. | all } VLAN 1.
5. (Optional.) Configure the
port trunk pvid vlan vlan-id The default setting is VLAN 1.
PVID of the trunk ports.
Assigning a hybrid port to a VLAN

A hybrid port can carry multiple VLANs. You can assign it to the specified VLANs in interface view. Make
sure the VLANs have been created.
When you assign a hybrid port to a VLAN, follow these guidelines:
To change the link type of a port from trunk to hybrid or vice versa, set the link type to access first.
You must configure the hybrid port to allow packets from the PVID to pass through by using the port
hybrid vlan command.
To assign a hybrid port to one or multiple VLANs:

109
Layer 2 Ethernet interface view
applies only to the port.
Enter Layer 2 Ethernet interface Layer 2 aggregate interface
view: view applies to the aggregate
interface interface-type interface and its aggregation
interface-number member ports. If the system fails
2. Enter interface view. to apply the configuration to an
aggregation member port, it
interface view:
skips the port and moves to the
next member port. If the system
interface-number
fails to apply the configuration
to the aggregate interface, it
stops applying the
member ports.
3. Configure the link type of the By default, all ports are access
port link-type hybrid
ports as hybrid. ports.
By default, a hybrid port is an

4. Assign the hybrid ports to the port hybrid vlan vlan-id-list untagged member of the VLAN to
specified VLANs. { tagged | untagged } which the port was assigned as an
access port.
By default, the PVID of a hybrid

5. (Optional.) Configure the port is the ID of the VLAN to which
port hybrid pvid vlan vlan-id
PVID of the hybrid ports. the port was assigned as an access
port.
Displaying and maintaining VLANs

Task Command
display vlan [ vlan-id1 [ to vlan-id2 ] | all | dynamic |
Display VLAN information.
reserved | static ]
display interface vlan-interface [ vlan-interface-id ] [ brief

Display VLAN interface information.
[ description ] ]
Display hybrid ports or trunk ports on the

display port { hybrid | trunk }
device.
Port-based VLAN configuration example

110
Host A and Host C belong to Department A. VLAN 100 is assigned to Department A.
Host B and Host D belong to Department B. VLAN 200 is assigned to Department B.
Configure port-based VLANs so that hosts only in the same department can communicate with each
other.
# Create VLAN 100, and assign FortyGigE 1/0/1 to VLAN 100.
[DeviceA] vlan 100
# Create VLAN 200, and assign FortyGigE 1/0/2 to VLAN 200.
[DeviceA] vlan 200
# Configure FortyGigE 1/0/3 as a trunk port, and assign it to VLANs 100 and 200.
[DeviceA-FortyGigE1/0/3] port trunk permit vlan 100 200
Please wait... Done.
3. Configure hosts:
{ Configure Host A and Host C to be on the same IP subnet. For example, 192.168.100.0/24.
{ Configure Host B and Host D to be on the same IP subnet. For example, 192.168.200.0/24.

# Verify that Host A and Host C can ping each other, but they both fail to ping Host B. (Details not
shown.)
# Verify that Host B and Host D can ping each other, but they both fail to ping Host A. (Details not
shown.)
# Verify that VLANs 100 and 200 are correctly configured on devices, for example, on Device A.
[DeviceA-FortyGigE1/0/3] display vlan 100
111
VLAN ID: 100
VLAN type: Static
Route interface: Not configured
Description: VLAN 0100
Name: VLAN 0100
Tagged ports:
FortyGigE1/0/3
Untagged ports:
FortyGigE1/0/1
[DeviceA-FortyGigE1/0/3] display vlan 200
VLAN ID: 200
VLAN type: Static
Route interface: Not configured
Description: VLAN 0200
Name: VLAN 0200
Tagged ports:
FortyGigE1/0/3
Untagged ports:
FortyGigE1/0/2
112
Configuring LLDP
You can set an Ethernet port as a Layer 3 interface by using the port link-mode route command (see
"Configuring Ethernet interfaces").
Overview
In a heterogeneous network, a standard configuration exchange platform ensures that different types of
network devices from different vendors can discover one another and exchange configuration for the
sake of interoperability and management.
The Link Layer Discovery Protocol (LLDP) is specified in IEEE 802.1AB. The protocol operates on the data
link layer to exchange device information between directly connected devices. With LLDP, a device sends
local device information (including its major functions, management IP address, device ID, and port ID)
as TLV (type, length, and value) triplets in LLDP Data Units (LLDPDUs) to the directly connected devices. At
the same time, the device stores the device information received in LLDPDUs sent from the LLDP neighbors
in a standard MIB. For more information about MIBs, see Network Management and Monitoring
Configuration Guide. LLDP enables a network management system to quickly detect and identify Layer 2
network topology changes.
Basic concepts
LLDP agent
An LLDP agent is a mapping of an entity where LLDP runs. Multiple LLDP agents can run on an interface
at the same time.
LLDP agents include the following types:
Nearest bridge agent.
Nearest customer bridge agent.
Nearest non-TPMR bridge agent.
A Two-port MAC Relay (TPMR) is a type of bridge that has only two externally-accessible bridge ports,
and supports a subset of the functions of a MAC bridge. A TPMR is transparent to all frame-based media
independent protocols except those destined to it and those destined to reserved MAC addresses that the
relay function of the TPMR is defined not to forward. LLDP exchanges packets between neighbor agents
and creates and maintains neighbor information for them. Figure 32 shows the neighbor relationships for
these LLDP agents. LLDP has two bridge modes: customer bridge (CB) and service bridge (SB).
Figure 32 LLDP neighbor relationships
113
LLDPDU formats
LLDP sends device information in LLDPDUs. LLDPDUs are encapsulated in Ethernet II or SNAP frames.
1. LLDPDU encapsulated in Ethernet II
Figure 33 Ethernet II-encapsulated LLDPDU
Table 11 Fields in an Ethernet II-encapsulated LLDPDU
Field Description
MAC address to which the LLDPDU is advertised. To distinguish between
LLDP packets sent and received by different agent types on the same
interface, LLDP specifies different multicast MAC addresses as destination
MAC addresses for LLDP packets to agents of different types. It is fixed to
Destination MAC address multicast MAC address 0x0180-C200-000E for LLDP packets destined for
the nearest bridge neighbor, 0x0180-C200-0000 for LLDP packets
destined for the nearest customer bridge neighbor, or
0x0180-C200-0003 for LLDP packets destined for the nearest TPMR
bridge neighbor.
Source MAC address MAC address of the sending port.
Type Ethernet type for the upper layer protocol. It is 0x88CC for LLDP.
Data LLDPDU.
Frame check sequence, a 32-bit CRC value used to determine the validity
FCS
of the received Ethernet frame.
2. LLDPDU encapsulated in SNAP

Figure 34 SNAP-encapsulated LLDPDU
114
Table 12 Fields in a SNAP-encapsulated LLDPDU
Field Description
MAC address to which the LLDPDU is advertised. It is the same as that for
Destination MAC address
Ethernet II-encapsulated LLDPDUs.
Source MAC address MAC address of the sending port.
SNAP type for the upper layer protocol. It is 0xAAAA-0300-0000-88CC

Type
for LLDP.
Data LLDPDU.
Frame check sequence, a 32-bit CRC value used to determine the validity
FCS
of the received Ethernet frame.
LLDPDUs
LLDP uses LLDPDUs to exchange information. An LLDPDU comprises multiple TLV sequences. Each TLV
carries a type of device information, as shown in Figure 35.
Figure 35 LLDPDU encapsulation format
An LLDPDU can carry up to 32 types of TLVs. Mandatory TLVs include Chassis ID TLV, Port ID TLV, Time
to Live TLV, and End of LLDPDU TLV. Other TLVs are optional.
TLVs
TLVs are type, length, and value sequences that carry information elements.
LLDPDU TLVs include the following categories:
Basic management TLVs
Organizationally (IEEE 802.1 and IEEE 802.3) specific TLVs
LLDP-MED (media endpoint discovery) TLVs
Basic management TLVs are essential to device management. Organizationally specific TLVs and
LLDP-MED TLVs are used for enhanced device management; they are defined by standardization or other
organizations and are optional to LLDPDUs.
1. Basic management TLVs
Table 13 lists the basic management TLV types. Some of them are mandatory to LLDPDUs (they
must be included in every LLDPDU).
Table 13 Basic management TLVs
Type Description Remarks

Chassis ID Specifies the bridge MAC address of the sending device.
Specifies the ID of the sending port.

Mandatory.
Port ID If the LLDPDU carries LLDP-MED TLVs, the port ID TLV carries
the MAC address of the sending port. Otherwise, the port ID
TLV carries the port name.
115
Type Description Remarks
Specifies the life of the transmitted information on the
Time to Live
receiving device.
End of LLDPDU Marks the end of the TLV sequence in the LLDPDU.
Port Description Specifies the port description of the sending port.
System Name Specifies the assigned name of the sending device.
System Description Specifies the description of the sending device.

Optional.
Identifies the primary functions of the sending device and the
System Capabilities
enabled primary functions.
Specifies the management address, and the interface number

Management Address
and object identifier (OID) associated with the address.
2. IEEE 802.1 organizationally specific TLVs

Table 14 IEEE 802.1 organizationally specific TLVs
Type Description
Port VLAN ID Specifies the port's VLAN identifier (PVID).
Indicates whether the device supports protocol VLANs and, if so, what
Port And Protocol VLAN ID
VLAN IDs these protocols will be associated with.
VLAN Name Specifies the textual name of any VLAN to which the port belongs.
Protocol Identity Indicates protocols supported on the port.
Data center bridging exchange protocol.

DCBX NOTE:
The switch does not support DCBX TLV in the current software version.
Edge Virtual Bridging module, comprising EVB TLV and CDCP TLV.
NOTE:
EVB module
The switch does not support EVB TLV and CDCP TLV in the current software
version.
Indicates whether the port supports link aggregation, and if yes, whether
Link Aggregation
link aggregation is enabled.
Management VID Management VLAN ID.
VID Usage Digest VLAN ID usage digest.
ETS Configuration Enhanced Transmission Selection configuration.
ETS Recommendation ETS recommendation.
PFC Priority-based Flow Control.
APP Application protocol.
NOTE:
HP devices support only receiving protocol identity TLVs and VID usage digest TLVs.
Layer 3 Ethernet ports support only link aggregation TLVs.
3. IEEE 802.3 organizationally specific TLVs
116
Table 15 IEEE 802.3 organizationally specific TLVs
Type Description
Contains the bit-rate and duplex capabilities of the sending port,
MAC/PHY Configuration/Status support for autonegotiation, enabling status of autonegotiation,
and the current rate and duplex mode.
Contains the power supply capability of the port, including the

PoE type (PSE or PD), PoE mode, whether PSE power supply is
Power Via MDI
supported, whether PSE power supply is enabled, and whether
the PoE mode is controllable.
Indicates the supported maximum frame size. It is now the MTU of

Maximum Frame Size
the port.
Indicates the power state control configured on the sending port,

Power Stateful Control including the power type of the PSE/PD, PoE sourcing/receiving
priority, and PoE sourcing/receiving power.
NOTE:
The Power Stateful Control TLV is defined in IEEE P802.3at D1.0 and is not supported in later
versions. HP devices send this type of TLVs only after receiving them.
4. LLDP-MED TLVs
LLDP-MED TLVs provide multiple advanced applications for voice over IP (VoIP), such as basic
configuration, network policy configuration, and address and directory management. LLDP-MED
TLVs provide a cost-effective and easy-to-use solution for deploying voice devices in Ethernet.
LLDP-MED TLVs are shown in Table 16.
Table 16 LLDP-MED TLVs
Type Description
Allows a network device to advertise the LLDP-MED TLVs that it
LLDP-MED Capabilities
supports.
Allows a network device or terminal device to advertise the VLAN

Network Policy ID of the specific port, the VLAN type, and the Layer 2 and Layer
3 priorities for specific applications.
Allows a network device or terminal device to advertise power

Extended Power-via-MDI supply capability. This TLV is an extension of the Power Via MDI
TLV.
Hardware Revision Allows a terminal device to advertise its hardware version.
Firmware Revision Allows a terminal device to advertise its firmware version.
Software Revision Allows a terminal device to advertise its software version.
Serial Number Allows a terminal device to advertise its serial number.
Manufacturer Name Allows a terminal device to advertise its vendor name.
Model Name Allows a terminal device to advertise its model name.
Allows a terminal device to advertise its asset ID. The typical case
Asset ID is that the user specifies the asset ID for the endpoint to facilitate
directory management and asset tracking.
117
Type Description
Allows a network device to advertise the appropriate location
Location Identification identifier information for a terminal device to use in the context of
location-based applications.
NOTE:
If the MAC/PHY configuration/status TLV is not advertisable, none of the LLDP-MED TLVs will be
advertised even if they are advertisable. If the LLDP-MED capabilities TLV is not advertisable, the other
LLDP-MED TLVs will not be advertised even if they are advertisable.
Management address
The network management system uses the management address of a device to identify and manage the
device for topology maintenance and network management. The management address is encapsulated
in the management address TLV.
Work mechanism
LLDP operating modes
An LLDP agent can operate in one of the following modes:
TxRx modeAn LLDP agent in this mode can send and receive LLDPDUs.
Tx modeAn LLDP agent in this mode can only send LLDPDUs.
Rx modeAn LLDP agent in this mode can only receive LLDPDUs.
Disable modeAn LLDP agent in this mode cannot send or receive LLDPDUs.
Each time the LLDP operating mode of an LLDP agent changes, its LLDP protocol state machine
re-initializes. A configurable re-initialization delay prevents frequent initializations because of frequent
changes to the operating mode. With this delay configured, before an LLDP agent can initialize LLDP, it
must wait for the specified interval after the LLDP operating mode changes.
Transmitting LLDPDUs
An LLDP agent operating in TxRx mode or Tx mode sends LLDPDUs to its directly connected devices both
periodically and when the local configuration changes. To prevent LLDPDUs from overwhelming the
network during times of frequent changes to local device information, LLDP uses the token bucket
mechanism to rate limit LLDPDUs. For more information about the token bucket mechanism, see ACL and
QoS Configuration Guide.
LLDP automatically enables the fast LLDPDU transmission mechanism in either of the following cases:
A new neighbor is discovered. A new LLDPDU is received and carries device information new to the
local device.
The LLDP operating mode of the LLDP agent changes from Disable or Rx to TxRx or Tx.
With this mechanism, a specific number of LLDPDUs are sent successively at a configurable fast
transmission interval to help LLDP neighbors discover the local device as soon as possible. Then, the
normal LLDPDU transmit interval resumes.
118
Receiving LLDPDUs
An LLDP agent that is operating in TxRx mode or Rx mode checks the validity of TLVs carried in every
received LLDPDU. If valid, the information is saved and an aging timer is set for it based on the TTL value
in the TTL TLV carried in the LLDPDU. If the TTL value is zero, the information ages out immediately.

IEEE 802.1AB-2005, Station and Media Access Control Connectivity Discovery
IEEE 802.1AB-2009, Station and Media Access Control Connectivity Discovery
ANSI/TIA-1057, Link Layer Discovery Protocol for Media Endpoint Devices
LLDP configuration task list

Tasks at a glance
Performing basic LLDP configuration:
(Required.) Enabling LLDP
(Optional.) Configuring the LLDP bridge mode
(Optional.) Setting the LLDP operating mode
(Optional.) Setting the LLDP re-initialization delay
(Optional.) Enabling LLDP polling
(Optional.) Configuring the advertisable TLVs
(Optional.) Configuring the management address and its encoding format
(Optional.) Setting other LLDP parameters
(Optional.) Setting an encapsulation format for LLDPDUs
(Optional.) Configuring CDP compatibility
(Optional.) Configuring LLDP trapping and LLDP-MED trapping
Performing basic LLDP configuration

Enabling LLDP
To make LLDP take effect on specific ports, you must enable LLDP both globally and on these ports.
To enable LLDP:

By default, LLDP is disabled

2. Enable LLDP globally. lldp global enable
globally.
119
3. Enter Layer 2 or Layer 3

Ethernet interface view or
Layer 2 aggregate interface
view.
By default, LLDP is enabled

4. (Optional.) Enable LLDP. lldp enable
on a port.
Configuring the LLDP bridge mode

The following LLDP bridge modes are available: service bridge mode and customer bridge mode.
In service bridge mode, LLDP supports nearest bridge agents and nearest non-TPMR bridge agents.
LLDP processes the LLDPDUs with destination MAC addresses for these agents and transparently
transmits the LLDPDUs with other destination MAC addresses in the VLAN.
In customer bridge mode, LLDP supports nearest bridge agents, nearest non-TPMR bridge agents,
and nearest customer bridge agents. LLDP processes the LLDPDUs with destination MAC addresses
for these agents and transparently transmits the LLDPDUs with other destination MAC addresses in
the VLAN.
To configure the LLDP bridge mode:

2. Configure LLDP to operate By default, LLDP operates in
lldp mode service-bridge
in service bridge mode. customer bridge mode.
Setting the LLDP operating mode

An LLDP agent can operate in one of the following modes:
TxRx modeAn LLDP agent in this mode can send and receive LLDPDUs.
Tx modeAn LLDP agent in this mode can only send LLDPDUs.
Rx modeAn LLDP agent in this mode can only receive LLDPDUs.
Disable modeAn LLDP agent in this mode cannot send or receive LLDPDUs.
To set the LLDP operating mode:

view.
120
By default, the nearest
bridge agent operates in
txrx mode, and the nearest
customer bridge agent and
nearest non-TPMR bridge
In Layer 2 or Layer 3 Ethernet interface agent operate in disable
view: mode.
lldp [ agent { nearest-customer |
nearest-nontpmr } ] admin-status In Ethernet interface view, if
3. Set the LLDP operating no agent type is specified,
{ disable | rx | tx | txrx }
mode. the command configures
In Layer 2 aggregate interface view:
the operating mode for
lldp agent { nearest-customer |
nearest bridge agents.
nearest-nontpmr } admin-status { disable
| rx | tx | txrx } In aggregate interface
view, you can configure the
operating mode for only
nearest customer bridge
agents and nearest
non-TPMR bridge agents.
Setting the LLDP re-initialization delay

When LLDP operating mode changes on a port, the port initializes the protocol state machines after a
certain delay. By adjusting the LLDP re-initialization delay, you can avoid frequent initializations caused
by frequent changes to the LLDP operating mode on a port.
To set the LLDP re-initialization delay for ports:

2. Set the LLDP re-initialization
lldp timer reinit-delay delay The default setting is 2 seconds.
delay.
Enabling LLDP polling

With LLDP polling enabled, a device periodically searches for local configuration changes. When the
device detects a configuration change, it sends LLDPDUs to inform neighboring devices of the change.
To enable LLDP polling:


view.
121
In Layer 2 or Layer 3 Ethernet interface
view:
nearest-nontpmr } ]
3. Enable LLDP polling and set By default, LLDP polling is
check-change-interval interval
the polling interval. disabled.
nearest-nontpmr }
check-change-interval interval
Configuring the advertisable TLVs


view.
lldp tlv-enable { basic-tlv { all |

port-description | system-capability |
system-description | system-name |
management-address-tlv [ ip-address ] }
| dot1-tlv { all | port-vlan-id | By default:
link-aggregation | protocol-vlan-id Nearest bridge agents
[ vlan-id ] | vlan-name [ vlan-id ] | can advertise all types
management-vid [ mvlan-id ] } | dot3-tlv of LLDP TLVs except the
{ all | mac-physic | max-frame-size | location identification
power } | med-tlv { all | capability | TLV, port and protocol
inventory | network-policy | VLAN ID TLVs, VLAN
power-over-ethernet | location-id name TLVs, and
3. Configure the advertisable { civic-address device-type country-code management VLAN ID
TLVs (in Layer 2 Ethernet { ca-type ca-value }&<1-10> | TLVs.
interface view). elin-address tel-number } } }
Nearest non-TPMR
lldp agent nearest-nontpmr tlv-enable bridge agents
{ basic-tlv { all | port-description | advertise no TLVs.
system-capability | system-description |
Nearest customer
system-name | management-address-tlv
bridge agents can
[ ip-address ] } | dot1-tlv { all |
advertise basic TLVs
port-vlan-id | link-aggregation } }
and IEEE 802.1
lldp agent nearest-customer tlv-enable organizationally
{ basic-tlv { all | port-description | specific TLVs.
system-capability | system-description |
system-name | management-address-tlv
[ ip-address ] } | dot1-tlv { all |
port-vlan-id | link-aggregation } }
122
lldp tlv-enable { basic-tlv { all | By default:

port-description | system-capability | Nearest bridge agents
system-description | system-name | can advertise all types
management-address-tlv [ ip-address ] } of LLDP TLVs (only link
| dot1-tlv { all | link-aggregation } | aggregation TLV in
dot3-tlv { all | mac-physic | 802.1
max-frame-size | power } | med-tlv { all organizationally
| capability | inventory | specific TLVs) except
4. Configure the advertisable power-over-ethernet | location-id network policy TLVs.
TLVs (in Layer 3 Ethernet { civic-address device-type country-code Nearest non-TPMR
interface view). { ca-type ca-value }&<1-10> | bridge agents
elin-address tel-number } } } advertise no TLVs.
lldp agent { nearest-nontpmr | Nearest customer
nearest-customer } tlv-enable { basic-tlv bridge agents can
{ all | port-description | advertise basic TLVs
system-capability | system-description | and IEEE 802.1
system-name | management-address-tlv organizationally
[ ip-address ] } | dot1-tlv { all | specific TLVs (only link
link-aggregation } } aggregation TLV).
By default:
lldp agent nearest-nontpmr tlv-enable Nearest non-TPMR

{ basic-tlv { all | management-address-tlv bridge agents
[ ip-address ] | port-description | advertise no TLVs.
system-capability | system-description | Nearest customer
system-name } | dot1-tlv { all | bridge agents can
port-vlan-id } } advertise basic TLVs
5. Configure the advertisable lldp agent nearest-customer tlv-enable and IEEE 802.1
TLVs (in Layer 2 aggregate { basic-tlv { all | management-address-tlv organizationally
interface view). [ ip-address ] | port-description | specific TLVs (only port
system-capability | system-description | and protocol VLAN ID
system-name } | dot1-tlv { all | TLV, VLAN name TLV,
port-vlan-id } } and management
VLAN ID TLV).
lldp tlv-enable dot1-tlv { protocol-vlan-id
[ vlan-id ] | vlan-name [ vlan-id ] | Nearest bridge agents
management-vid [ mvlan-id ] } are not supported on
Layer 2 aggregate
interfaces.
Configuring the management address and its encoding format

LLDP encodes management addresses in numeric or string format in management address TLVs.
By default, management addresses are encoded in numeric format. If a neighbor encodes its
management address in character string format, you must configure the encoding format of the
management address as string on the connecting port to guarantee normal communication with the
neighbor.
To configure a management address to be advertised and its encoding format on a port:
123
Ethernet interface view or interface interface-type
N/A
Layer 2 aggregate interface interface-number
view.
In Layer 2 or Layer 3 Ethernet
interface view:
lldp [ agent { nearest-customer
| nearest-nontpmr } ]
tlv-enable basic-tlv By default, nearest bridge agents
3. Allow LLDP to advertise the and nearest customer bridge
management-address-tlv
management address in agents can advertise the
[ ip-address ]
LLDPDUs and configure the management address in LLDPDUs,
advertised management In Layer 2 aggregate interface
and nearest non-TPMR bridge
address. view:
agents cannot advertise the
lldp agent { nearest-customer
management address in LLDPDUs.
| nearest-nontpmr } tlv-enable
basic-tlv
management-address-tlv
[ ip-address ]
In Layer 2 or Layer 3 Ethernet
interface view:
lldp [ agent { nearest-customer
| nearest-nontpmr } ]
management-address-format
4. Configure the encoding By default, the management
string
format of the management address is encapsulated in the
address as character string. In Layer 2 aggregate interface
numeric format.
view:
lldp agent { nearest-customer
| nearest-nontpmr }
management-address-format
string
Setting other LLDP parameters

The TTL TLV carried in an LLDPDU determines how long the device information carried in the LLDPDU can
be saved on a recipient device.
By setting the TTL multiplier, you can configure the TTL of locally sent LLDPDUs, which determines how
long information about the local device can be saved on a neighboring device. The TTL is expressed by
using the following formula:
TTL = Min (65535, (TTL multiplier LLDPDU transmit interval))
As the expression shows, the TTL can be up to 65535 seconds. TTLs greater than 65535 will be rounded
down to 65535 seconds.
To change LLDP parameters:

2. Set the TTL multiplier. lldp hold-multiplier value The default setting is 4.
124
3. Set the LLDPDU transmit The default setting is 30
lldp timer tx-interval interval
interval. seconds.
4. Set the token bucket size for
lldp max-credit credit-value The default setting is 5.
sending LLDPDUs.
5. Set the LLDPDU transmit delay. lldp timer tx-delay delay The default setting is 2 seconds.
6. Set the number of LLDPDUs
sent each time fast LLDPDU lldp fast-count count The default setting is 4.
transmission is triggered.
7. Set an interval for fast LLDPDU
lldp timer fast-interval interval The default setting is 1 second.
transmission.
Setting an encapsulation format for LLDPDUs

LLDPDUs can be encapsulated in the following formats: Ethernet II or SNAP frames.
With Ethernet II encapsulation configured, an LLDP port sends LLDPDUs in Ethernet II frames.
With SNAP encapsulation configured, an LLDP port sends LLDPDUs in SNAP frames.
To set the encapsulation format for LLDPDUs to SNAP:

view.
view:
3. Set the encapsulation lldp [ agent { nearest-customer | By default, Ethernet II
format for LLDPDUs to nearest-nontpmr } ] encapsulation snap encapsulation format
SNAP. In Layer 2 aggregate interface view: applies.
nearest-nontpmr } encapsulation snap
NOTE:
LLDP of earlier versions requires the same encapsulation format on both ends to process LLDPDUs. For this
reason, to communicate stably with a neighboring device running LLDP of earlier versions, the local device
should be configured with the same encapsulation format.
Configuring CDP compatibility

When the switch is directly connected to a Cisco device that supports only CDP rather than LLDP, you can
enable CDP compatibility to enable the switch to exchange information with the directly-connected
device.
With CDP compatibility enabled on the switch, the switch can use LLDP to receive and recognize the CDP
packets received from the directly-connected device and send CDP packets to the directly-connected
125
device. The packets that the switch sends to the neighboring CDP device carry the device ID, the ID of the
port connecting to the neighboring device, the port IP address, the PVID, and the TTL. The port IP address
is the main IP address of the VLAN interface that is in up state and whose corresponding VLAN ID is the
lowest among the VLANs permitted on the port. If none of the VLAN interfaces of the permitted VLANs
is assigned an IP address or all VLAN interfaces are down, no port IP address will be advertised. The
CDP neighbor-information-related fields in the output of the display lldp neighbor-information command
show the CDP neighboring device information that can be recognized by the switch. For more
information about the display lldp neighbor-information command, see Layer 2LAN Switching
Command Reference.
Configuration prerequisites
Before you configure CDP compatibility, complete the following tasks:
Globally enable LLDP.
Enable LLDP on the port connecting to a device supporting CDP, and configure the port to operate
in TxRx mode.
CDP-compatible LLDP operates in one of the following modes:
TxRxCDP packets can be transmitted and received.
DisableCDP packets cannot be transmitted or received.
LLDP traps are sent periodically, and the interval is configurable. To make CDP-compatible LLDP take
effect on specific ports, first enable CDP-compatible LLDP globally, and then configure CDP-compatible
LLDP to operate in TxRx mode.
The maximum TTL value that CDP allows is 255 seconds. To make CDP-compatible LLDP work correctly
with Cisco IP phones, configure the LLDPDU transmit interval to be no more than 1/3 of the TTL value.
To enable LLDP to be compatible with CDP:

2. Enable CDP compatibility By default, CDP compatibility is
lldp compliance cdp
globally. disabled globally.
3. Enter Layer 2 or Layer 3 interface interface-type
N/A
Ethernet interface view. interface-number
4. Configure CDP-compatible lldp compliance admin-status cdp By default, CDP-compatible LLDP
LLDP to operate in TxRx mode. txrx operates in Disable mode.
Configuring LLDP trapping and LLDP-MED trapping

LLDP trapping or LLDP-MED trapping notifies the network management system of events such as newly
detected neighboring devices and link malfunctions.
To prevent excessive LLDP traps from being sent when the topology is unstable, set a trap transmit interval
for LLDP.
126
To configure LLDP trapping and LLDP-MED trapping:

view.
view:
nearest-nontpmr } ] notification
remote-change enable By default, LLDP trapping is
3. Enable LLDP trapping.
disabled.
nearest-nontpmr } notification
remote-change enable
4. Enable LLDP-MED trapping
lldp notification med-topology-change By default, LLDP-MED
(in Layer 2 or Layer 3
enable trapping is disabled.
Ethernet interface view).
5. Return to system view. quit N/A
6. (Optional.) Set the LLDP The default setting is 30
lldp timer notification-interval interval
trap transmit interval. seconds.
Displaying and maintaining LLDP

Task Command
display lldp local-information [ global | interface interface-type
Display local LLDP information.
interface-number ]
Display the information contained display lldp neighbor-information [ [ [ interface interface-type

in the LLDP TLVs sent from interface-number ] [ agent { nearest-bridge | nearest-customer |
neighboring devices. nearest-nontpmr } ] [ verbose ] ] | list [ system-name system-name ] ]
display lldp statistics [ global | [ interface interface-type

Display LLDP statistics. interface-number ] [ agent { nearest-bridge | nearest-customer |
nearest-nontpmr } ] ]
display lldp status [ interface interface-type interface-number ] [ agent

Display LLDP status of a port.
{ nearest-bridge | nearest-customer | nearest-nontpmr } ]
Display types of advertisable display lldp tlv-config [ interface interface-type interface-number ]

optional LLDP TLVs. [ agent { nearest-bridge | nearest-customer | nearest-nontpmr } ]
127
LLDP configuration example
As shown in Figure 36, the NMS and Switch A are located in the same Ethernet network. An MED device
and Switch B are connected to FortyGigE1/0/1 and FortyGigE1/0/2 of Switch A.
Enable LLDP globally on Switch A and Switch B to monitor the link between Switch A and Switch B and
the link between Switch A and the MED device on the NMS.
MED
FGE1/0/1
NMS
FGE1/0/2 FGE1/0/1
Switch A Switch B
1. Configure Switch A:
# Enable LLDP globally.
<SwitchA> system-view
[SwitchA] lldp global enable
# Enable LLDP on FortyGigE1/0/1. By default, LLDP is enabled on the port.
[SwitchA] interface fortygige 1/0/1
[SwitchA-FortyGigE1/0/1] lldp enable
# Set the LLDP operating mode to Rx.
[SwitchA-FortyGigE1/0/1] lldp admin-status rx
[SwitchA-FortyGigE1/0/1] quit
[SwitchA] interface fortygige 1/0/2
[SwitchA-FortyGigE1/0/2] lldp enable
# Set the LLDP operating mode to Rx.
[SwitchA-FortyGigE1/0/2] lldp admin-status rx
[SwitchA-FortyGigE1/0/2] quit
2. Configure Switch B:
# Enable LLDP globally.
<SwitchB> system-view
[SwitchB] lldp global enable
[SwitchB] interface fortygige 1/0/1
128
[SwitchB-FortyGigE1/0/1] lldp enable
# Set the LLDP operating mode to Tx.
[SwitchB-FortyGigE1/0/1] lldp admin-status tx
[SwitchB-FortyGigE1/0/1] quit

# Verify that:
FortyGigE1/0/1 of Switch A connects to an MED device.
FortyGigE1/0/2 of Switch A connects to a non-MED device.
Both ports operate in Rx mode, and they can receive LLDPDUs but cannot send LLDPDUs.
[SwitchA] display lldp status
Global status of LLDP: Enable
Bridge mode of LLDP: customer-bridge
The current number of LLDP neighbors: 2
The current number of CDP neighbors: 0
LLDP neighbor information last changed time: 0 days, 0 hours, 4 minutes, 40 seconds
Transmit interval : 30s
Fast transmit interval : 1s
Transmit credit max : 5
Hold multiplier : 4
Reinit delay : 2s
Trap interval : 30s
Fast start times : 4
LLDP status information of port 1 [FortyGigE1/0/1]:

LLDP agent nearest-bridge:
Port status of LLDP : Enable
Admin status : RX_Only
Trap flag : No
MED trap flag : No
Polling interval : 0s
Number of LLDP neighbors : 1
Number of MED neighbors : 1
Number of CDP neighbors : 0
Number of sent optional TLV : 21
Number of received unknown TLV : 0
LLDP agent nearest-customer:

Admin status : Disable
Trap flag : No
MED trap flag : No
129

Trap flag : No
MED trap flag : No
LLDP agent nearest-nontpmr:

Trap flag : No
MED trap flag : No

Trap flag : No
MED trap flag : No
# Remove the link between Switch A and Switch B.

# Verify that FortyGigE1/0/2 of Switch A does not connect to any neighboring devices.
[SwitchA] display lldp status
Global status of LLDP: Enable
The current number of LLDP neighbors: 1
The current number of CDP neighbors: 0
LLDP neighbor information last changed time: 0 days, 0 hours, 5 minutes, 20 seconds
Transmit interval : 30s
Fast transmit interval : 1s
130
Transmit credit max : 5
Hold multiplier : 4
Reinit delay : 2s
Trap interval : 30s
Fast start times : 4

Trap flag : No
MED trap flag : No

Trap flag : No
MED trap flag : No

Trap flag : No
MED trap flag : No

Trap flag : No
131
MED trap flag : No

Trap flag : No
MED trap flag : No
132
Support and other resources
Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
Product model names and numbers
Technical support registration number (if applicable)
Product serial numbers
Error messages
Operating system type and revision level
Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/wwalerts
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Related information
Documents
To find related documents, browse to the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals
For related documentation, navigate to the Networking section, and select a networking category.
For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms.
Websites
HP.com http://www.hp.com
HP Networking http://www.hp.com/go/networking
HP manuals http://www.hp.com/support/manuals
HP download drivers and software http://www.hp.com/support/downloads
HP software depot http://www.software.hp.com
HP Education http://www.hp.com/learn
133
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[] Square brackets enclose syntax choices (keywords or arguments) that are optional.
Braces enclose a set of required syntax choices separated by vertical bars, from which
{ x | y | ... }
you select one.
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
[ x | y | ... ]
which you select one or none.
Asterisk-marked braces enclose a set of required syntax choices separated by vertical

{ x | y | ... } *
bars, from which you select at least one.
Asterisk-marked square brackets enclose optional syntax choices separated by vertical

[ x | y | ... ] *
bars, from which you select one choice, multiple choices, or none.
The argument or keyword and argument combination before the ampersand (&) sign can
&<1-n>
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Window names, button names, field names, and menu items are in bold text. For
Boldface
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
An alert that calls attention to important information that if not understood or followed can
WARNING result in personal injury.
An alert that calls attention to important information that if not understood or followed can
CAUTION result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
134
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the switching engine

on a unified wired-WLAN switch.
Represents an access point.
Represents a security product, such as a firewall, a UTM, or a load-balancing or security

card that is installed in a device.
Represents a security card, such as a firewall card, a load-balancing card, or a

NetStream card.
Port numbering in examples

The port numbers in this document are for illustration only and might be unavailable on your device.
135
Index
Numerics port-based VLAN trunk port, 108

802.x attribute
802.1 LLDPDU TLV types, 115 Ethernet link aggregation attribute configuration, 31
802.3 LLDPDU TLV types, 115 auto
Ethernet interface autonegotiation mode, 3
A
loop detection port status auto recovery, 97
accessing
B
port-based VLAN access port, 107
port-based VLAN access port (in interface backup port (MST), 65
view), 107 bandwidth
port-based VLAN access port (in VLAN Ethernet link aggregate interface (expected
view), 107 bandwidth), 41
action basic management LLDPDU TLV types, 115
loop detection block, 97 blackhole entry
loop detection no-learning protection, 97 MAC address table, 17, 19
loop detection shutdown protection, 97 block action (loop detection), 97
adding boundary port (MST), 65
MAC address table blackhole entry, 19 BPDU
MAC address table multiport unicast entry, 20 MST region max hops, 73
address STP BPDU forwarding, 61
MAC address learning disable, 21 STP BPDU guard, 87
MAC address table address synchronization, 22 STP hello time, 74
MAC Information queue length, 27 STP max age timer, 74
advertising STP TC-BPDU guard, 90
LLDP advertisable TLV, 122 STP TC-BPDU transmission restriction, 90
aggregating transmission rate configuration, 76
link. See Ethernet link aggregation bridge
aging LLDP agent customer bridge, 113
MAC address table timer, 22 LLDP agent nearest bridge, 113
STP max age timer, 74 LLDP agent non-TPMR bridge, 113
algorithm MST common root bridge, 64, 64
STP calculation, 57 MST regional root, 64
alternate port (MST), 65 MSTP root bridge configuration, 72
assigning MSTP secondary root bridge configuration, 72
port to isolation group (multiple), 52 RSTP root bridge configuration, 72
port-based VLAN access port, 107 RSTP secondary root bridge configuration, 72
port-based VLAN access port (in interface STP designated bridge, 56
view), 107 STP loop guard, 88
port-based VLAN access port (in VLAN STP root bridge, 56
view), 107 STP root bridge configuration, 72
port-based VLAN hybrid port, 109 STP root guard, 88
136
STP secondary root bridge configuration, 72 Ethernet link aggregation group, 37
bulk Ethernet link aggregation group load sharing
interface configuration, 15 criteria, 42
interface configuration display, 16 Ethernet link aggregation load sharing, 42
inloopback interface, 12, 13
C
Layer 2 Ethernet interface, 8
calculating
Layer 2 Ethernet interface storm control, 9
MSTI calculation, 66
Layer 2 Ethernet interface storm suppression, 8
MSTP CIST calculation, 66
Layer 2 Ethernet link aggregation (dynamic), 47
STP algorithm, 57
Layer 2 Ethernet link aggregation (static), 45
STP port path cost calculation standard, 77
Layer 2 Ethernet link aggregation group
STP timeout factor, 75 (dynamic), 38
CDP Layer 2 Ethernet link aggregation group (static), 38
LLDP CDP compatibility, 125 Layer 2 Ethernet link aggregation load sharing, 48
changing LLDP, 113, 119
MAC Information change send interval, 27 LLDP advertisable TLVs, 122
checking LLDP basics, 119, 128
STP mCheck, 82 LLDP bridge mode, 120
STP mCheck (global), 82 LLDP CDP compatibility, 125
STP mCheck (interface view), 82 LLDP management address, 123
STP No Agreement Check, 85, 87 LLDP management address encoding format, 123
choosing LLDP trapping, 126
Ethernet link aggregation reference port, 32, 34 LLDP-MED trapping, 126
Cisco loop detection, 96, 98, 100
LLDP CDP compatibility, 125 loop detection protection action, 98
CIST loop detection protection action (global), 99
calculation, 66 loop detection protection action (Layer 2 aggregate
network device connection, 64 interface), 99
STP max age timer, 74 loop detection protection action (Layer 2 Ethernet
common root bridge, 64 interface), 99
configuring loopback interface, 12, 12
Ethernet aggregate interface, 39 MAC address table, 17, 18, 24
Ethernet aggregate interface (description), 39 MAC address table dynamic aging timer, 22
Ethernet interface, 1 MAC address table entry, 18
Ethernet interface basic settings, 3 MAC Information, 26, 27
Ethernet interface common settings, 1 MAC Information change send interval, 27
Ethernet interface generic flow control, 5 MAC Information mode, 26
Ethernet interface jumbo frame support, 4 MAC Information queue length, 27
Ethernet interface link mode, 4 management Ethernet interface, 1
Ethernet interface PFC, 6 MST region, 71
Ethernet interface physical state change MST region max hops, 73
suppression, 4 MSTP, 55, 67, 91
Ethernet link aggregate interface (expected MSTP device priority, 73
bandwidth), 41 MSTP root bridge, 72
Ethernet link aggregation, 30, 37, 45 MSTP root bridge device, 72
137
MSTP secondary root bridge, 72 Ethernet link aggregate interface default
MSTP secondary root bridge device, 72 settings, 42
null interface, 12, 13 designated
port isolation, 52 MST port, 65
port isolation (on LAN), 53 STP bridge, 56
RSTP, 55, 67, 91 STP port, 56
RSTP device priority, 73 device
RSTP root bridge, 72 Ethernet interface configuration, 1
RSTP root bridge device, 72 LLDP basic configuration, 119, 128
RSTP secondary root bridge, 72 LLDP CDP compatibility, 125
RSTP secondary root bridge device, 72 LLDP configuration, 113, 119
STP, 55, 67, 91 LLDP parameters, 124
STP BPDU transmission rate, 76 loop protection actions, 97
STP device priority, 73 MSTP implementation, 67
STP Digest Snooping, 83, 84 MSTP priority, 73
STP edge port, 76 MSTP root bridge configuration, 72
STP No Agreement Check, 85, 87 MSTP secondary root bridge configuration, 72
STP port link type, 80 RSTP priority, 73
STP port mode, 80 RSTP root bridge configuration, 72
STP port path cost, 77, 78 RSTP secondary root bridge configuration, 72
STP port priority, 79 STP BPDU guard, 87
STP port role restriction, 89 STP Digest Snooping, 83, 84
STP protection functions, 87 STP loop guard, 88
STP root bridge, 72 STP No Agreement Check, 85, 87
STP root bridge device, 72 STP port role restriction, 89
STP secondary root bridge, 72 STP priority, 73
STP secondary root bridge device, 72 STP protection functions, 87
STP switched network diameter, 73 STP root bridge configuration, 72
STP TC-BPDU transmission restriction, 90 STP root guard, 88
STP timeout factor, 75 STP secondary root bridge configuration, 72
STP timer, 74 STP TC-BPDU guard, 90
VLAN (port-based), 106, 110 STP TC-BPDU transmission restriction, 90
VLAN basic settings, 104 Digest Snooping (STP), 83, 84
VLAN interface basic settings, 105 disabling
cost MAC address learning, 21
STP path cost, 56 discarding
STP port path cost calculation standard, 77 MST discarding port state, 65
STP port path cost configuration, 77, 78 displaying
CST bulk interface configuration, 16
MST region connection, 64 Ethernet interface, 10
customer Ethernet link aggregation, 44
LLDP customer bridge mode, 120 inloopback interface, 13
LLDP, 127
D
loop detection, 100
default
loopback interface, 13
138
MAC address table, 24 interface. See Ethernet interface
MSTP, 91 link aggregation. See Ethernet link aggregation
null interface, 13 LLDP trapping, 126
port isolation, 52 LLDPDU encapsulated in Ethernet II, 114
RSTP, 91 LLDP-MED trapping, 126
STP, 91 loop detection configuration, 96, 100
VLAN, 110 MAC address table configuration, 17, 18, 24
dot1d-1998 (STP port path cost calculation), 77 MAC Information configuration, 26, 27
dot1s (STP port mode), 80 port isolation configuration, 52
dot1t (STP port path cost calculation), 77 port isolation configuration (on LAN), 53
dynamic port-based VLAN access port assignment, 107
Ethernet link aggregation dynamic mode, 33 port-based VLAN access port assignment (in
Ethernet link aggregation mode, 31 interface view), 107
Layer 2 Ethernet link aggregation, 47 port-based VLAN access port assignment (in VLAN
Layer 2 Ethernet link aggregation group view), 107
(dynamic), 38 port-based VLAN hybrid port assignment, 109
link aggregation process, 34 port-based VLAN trunk port assignment, 108
MAC address table dynamic aging timer, 22 VLAN basic configuration, 104
MAC address table entry, 17 VLAN configuration, 103
VLAN frame encapsulation, 103
E
VLAN interface basic configuration, 105
edge port
VLAN port-based configuration, 106, 110
MST, 65
Ethernet interface
STP, 76
basic settings configuration, 3
enabling
common settings configuration, 1
Ethernet link aggregation traffic redirection, 44
configuration, 1
LLDP, 119
configuring management Ethernet interface, 1
LLDP polling, 121
displaying, 10
loop detection, 98
generic flow control, 5
loop detection (global), 98
jumbo frame support configuration, 4
loop detection (port-specific), 98
link mode, 4
MAC address synchronization, 22
maintaining, 10
MAC Information, 26
naming convention, 1
STP BPDU guard, 87
PFC configuration, 6
STP feature, 81
physical state change suppression, 4
STP loop guard, 88
splitting and combining, 2
STP port state transition information output, 81
Ethernet link aggregation
STP root guard, 88
aggregate group min/max number Selected
STP TC-BPDU guard, 90 ports, 40
encapsulating aggregate interface, 30
LLDPDU encapsulated in Ethernet II, 114 aggregate interface (description), 39
LLDPDU encapsulated in SNAP format, 114 aggregate interface configuration, 39
LLDPDU encapsulation format, 125 aggregate interface default settings, 42
VLAN frame encapsulation, 103 aggregate interface shutdown, 41
Ethernet aggregation group, 30
139
basic concepts, 30 frame
configuration, 30, 37, 45 Ethernet interface jumbo frame support, 4
configuration types, 31 loop detection, 96
displaying, 44 loop detection (Ethernet frame header), 96
dynamic mode, 33 loop detection (inner frame header), 96
dynamic process, 34 loop detection interval, 97
group configuration, 37 MAC address learning, 17
group load sharing criteria, 42 MAC address table blackhole entry, 19
interface configuration (expected MAC address table configuration, 17, 18, 24
bandwidth), 41 MAC address table entry configuration, 18
LACP, 33 MAC address table multiport unicast entry, 20
Layer 2 aggregate interface (ignored MAC Information configuration, 26, 27
VLAN), 40, 40 port-based VLAN frame handling, 107
Layer 2 aggregation (dynamic), 47 VLAN frame encapsulation, 103
Layer 2 aggregation (static), 45 full-duplex mode (Ethernet interface), 3
Layer 2 aggregation load sharing, 48
G
Layer 2 group (dynamic), 38
Layer 2 group (static), 38 generic flow control (Ethernet interface), 5
load sharing configuration, 42 group
load sharing criteria, 37 Ethernet link aggregate group min/max number
Selected ports, 40
local-first load sharing, 43
Ethernet link aggregation group, 30
maintaining, 44
Ethernet link aggregation group configuration, 37
member port, 30
Ethernet link aggregation LACP, 33
member port state, 30, 32, 35
Ethernet link aggregation load sharing, 42
modes, 31
Ethernet link aggregation load sharing
operational key, 31
criteria, 37, 42
reference port, 34
Ethernet link aggregation member port state, 30
reference port choice, 32
static mode, 32
(dynamic), 38
traffic redirection, 44
Layer 2 Ethernet link aggregation group (static), 38
traffic redirection restrictions, 44
H
F
half-duplex mode (Ethernet interface), 3
flow control
hello
Ethernet interface generic flow control, 5
STP timer, 61, 74
Ethernet interface PFC, 6
hybrid port
format
port-based VLAN assignment, 109
LLDP management address encoding
format, 123 I
LLDPDU encapsulated in Ethernet II, 114 ignored VLAN
LLDPDU encapsulated in SNAP format, 114 Layer 2 aggregate interface, 40
LLDPDU encapsulation format, 125 implementing
forwarding MSTP device implementation, 67
MST forwarding port state, 65 inloopback interface
STP BPDU forwarding, 61 configuration, 13
STP forward delay timer, 61, 74 displaying, 13
140
maintaining, 13 Ethernet link aggregation load sharing criteria, 37
interface Ethernet link aggregation static mode, 32
bulk configuration, 15 Ethernet link aggregation traffic redirection, 44
configuring inloopback, 12 Layer 2
configuring loopback, 12 Ethernet aggregate interface (description), 39
configuring null, 12 Ethernet aggregate interface configuration, 39
Ethernet aggregate interface (description), 39 Ethernet link aggregate group min/max number
Ethernet aggregate interface configuration, 39 Selected ports, 40
Ethernet link aggregate interface default Ethernet link aggregate interface (expected
settings, 42 bandwidth), 41
Ethernet link aggregate interface shutdown, 41 Ethernet link aggregate interface default
Layer 2 Ethernet aggregate interface (ignored settings, 42
VLAN), 40 Ethernet link aggregate interface shutdown, 41
interval Ethernet link aggregation (dynamic), 47
loop detection, 97, 99 Ethernet link aggregation (static), 45
MAC Information change send interval, 27 Ethernet link aggregation configuration, 30, 37, 45
isolating Ethernet link aggregation group (dynamic), 38
ports. See port isolation Ethernet link aggregation group (static), 38
IST Ethernet link aggregation group configuration, 37
MST region, 64 Ethernet link aggregation group load sharing
criteria, 42
J
Ethernet link aggregation load sharing, 42, 48
jumbo frame support (Ethernet interface), 4 Ethernet link aggregation load sharing criteria, 37
K Ethernet link aggregation local-first load
sharing, 43
key
Ethernet link aggregation operational key, 31
LLDP basic configuration, 128
L LLDP trapping, 126
LACP LLDP-MED trapping, 126
Ethernet link aggregation, 33 loop detection configuration, 96, 98, 100
LAN port isolation configuration, 52
port isolation configuration, 53 port isolation configuration (on LAN), 53
VLAN basic configuration, 104 port-based VLAN access port assignment, 107
VLAN configuration, 103 port-based VLAN access port assignment (in
VLAN interface basic configuration, 105 interface view), 107
VLAN port-based configuration, 106, 110 port-based VLAN access port assignment (in VLAN
LAN switching view), 107
Ethernet aggregate interface configuration, 39 port-based VLAN hybrid port assignment, 109
Ethernet link aggregation basic concepts, 30 port-based VLAN trunk port assignment, 108
Ethernet link aggregation VLAN basic configuration, 104
configuration, 30, 37, 45 VLAN configuration, 103
Ethernet link aggregation dynamic mode, 33 VLAN interface basic configuration, 105
Ethernet link aggregation group VLAN port-based configuration, 106, 110
configuration, 37 Layer 2 Ethernet interface
Ethernet link aggregation LACP, 33 configuration, 1, 8
Ethernet link aggregation load sharing, 42 storm control configuration, 9
141
storm suppression configuration, 8 LLDPDU format, 114
Layer 3 LLDPDU management address TLV, 118
LLDP basic configuration, 128 LLDPDU reception, 119
LLDP trapping, 126 LLDPDU TLV types, 115
LLDP-MED trapping, 126 LLDPDU TLVs, 115
port-based VLAN access port assignment, 107 LLDPDU transmission, 118
port-based VLAN access port assignment (in LLDP-MED trapping configuration, 126
interface view), 107 management address configuration, 123
port-based VLAN access port assignment (in management address encoding format, 123
VLAN view), 107 operating mode (disable), 118, 120
port-based VLAN hybrid port assignment, 109 operating mode (Rx), 118, 120
port-based VLAN trunk port assignment, 108 operating mode (Tx), 118, 120
VLAN interface basic configuration, 105 operating mode (TxRx), 118, 120
VLAN port-based configuration, 106, 110 operating mode set, 120
Layer 3 Ethernet interface parameter set, 124
configuration, 1 polling enable, 121
learning protocols and standards, 119
loop detection no-learning action, 97 re-initialization delay, 121
MAC address, 17 trapping configuration, 126
MAC address learning disable, 21 LLDPDU
MST learning port state, 65 encapsulated in Ethernet II format, 114
legacy encapsulated in SNAP format, 114
STP port mode, 80 encapsulation format, 125
STP port path cost calculation, 77 LLDP basic configuration, 119, 128
link LLDP configuration, 113, 119
aggregation. See Ethernet link aggregation LLDP parameters, 124
Ethernet interface link mode, 4 management address configuration, 123
link layer discovery protocol. See LLDP management address encoding format, 123
MSTP configuration, 55, 67, 91 management address TLV, 118
RSTP configuration, 55, 67, 91 receiving, 119
STP configuration, 55, 67, 91 TLV basic management types, 115
STP hello time, 74 TLV LLDP-MED types, 115
STP port link type configuration, 80 TLV organization-specific types, 115
LLDP transmitting, 118
advertisable TLV configuration, 122 load sharing
agent, 113 Ethernet link aggregation configuration, 42
basic concepts, 113 Ethernet link aggregation group criteria, 42
basic configuration, 119, 128 Ethernet link aggregation group load sharing, 37
bridge mode configuration, 120 Ethernet link aggregation local-first load
CDP compatibility configuration, 125 sharing, 43
configuration, 113, 119 Ethernet link aggregation packet type-based load
displaying, 127 sharing, 37
enable, 119 Ethernet link aggregation per-flow load sharing, 37
how it works, 118 Ethernet link aggregation per-packet load
LLDPDU encapsulation format, 125 sharing, 37
142
Layer 2 Ethernet link aggregation entry types, 17
configuration, 48 MAC address learning disable, 21
local manual entries, 17
Ethernet link aggregation local-first load multiport unicast entry, 20
sharing, 43 MAC Information
logging change send interval, 27
loop detection configuration, 96, 98, 100 configuration, 26, 27
loop enable, 26
MSTP configuration, 55, 67, 91 mode configuration, 26
RSTP configuration, 55, 67, 91 queue length configuration, 27
STP configuration, 55, 67, 91 MAC relay (LLDP agent), 113
STP loop guard, 88 maintaining
loop detection Ethernet interface, 10
configuration, 96, 98, 100 Ethernet link aggregation, 44
displaying, 100 inloopback interface, 13
enable, 98 loopback interface, 13
enable (global), 98 MSTP, 91
enable (port-specific), 98 null interface, 13
interval, 97 RSTP, 91
interval setting, 99 STP, 91
mechanisms, 96 VLAN, 110
port status auto recovery, 97 management address
protection action configuration, 98 LLDP encoding format, 123
protection action configuration (global), 99 management Ethernet interface
protection action configuration (Layer 2 configuration, 1
aggregate interface), 99
mapping
protection action configuration (Layer 2 Ethernet
MSTP VLAN-to-instance mapping table, 64
interface), 99
master port (MST), 65
protection actions, 97
max age timer (STP), 61
loopback interface
mCheck (STP), 82, 82, 82
configuration, 12
MED (LLDP-MED trapping), 126
displaying, 13
MIB
maintaining, 13
LLDP basic configuration, 119, 128
M LLDP configuration, 113, 119
MAC address mode
VLAN frame encapsulation, 103 Ethernet interface autonegotiation, 3
MAC address table Ethernet interface full-duplex, 3
address learning, 17 Ethernet interface half-duplex, 3
address synchronization, 22 Ethernet interface link mode, 4
blackhole entry, 19 Ethernet link aggregation dynamic, 31
configuration, 17, 18, 24 Ethernet link aggregation dynamic mode, 33
displaying, 24 Ethernet link aggregation load sharing criteria, 37
dynamic aging timer, 22 Ethernet link aggregation static, 31
entry configuration, 18 Ethernet link aggregation static mode, 32
entry creation, 17 LLDP customer bridge mode, 120
143
LLDP disable, 118, 120 STP max age timer, 74
LLDP Rx, 118, 120 STP port mode configuration, 80
LLDP service bridge mode, 120 VLAN-to-instance mapping table, 64
LLDP Tx, 118, 120 multiport unicast entry (MAC address table), 17, 20
LLDP TxRx, 118, 120 N
MAC Information syslog, 26
network
MAC Information trap, 26
Ethernet interface basic settings configuration, 3
modifying
Ethernet interface common settings configuration, 1
MAC address table blackhole entry, 19
Ethernet interface generic flow control, 5
MAC address table multiport unicast entry, 20
Ethernet interface jumbo frame support
MST
configuration, 4
CIST, 64
Ethernet interface link mode, 4
common root bridge, 64
Ethernet interface PFC, 6
CST, 64
Ethernet interface physical state change
IST, 64 suppression, 4
MSTI, 64 Ethernet interface splitting and combining, 2
port roles, 65 Ethernet link aggregation configuration types, 31
port states, 65 Ethernet link aggregation dynamic mode, 33
region, 63 Ethernet link aggregation LACP, 33
region configuration, 71 Ethernet link aggregation member port
region max hops, 73 state, 32, 35
regional root, 64 Ethernet link aggregation modes, 31
MSTI Ethernet link aggregation operational key, 31
calculation, 66 Ethernet link aggregation reference port, 34
MST instance, 64 Ethernet link aggregation reference port choice, 32
MSTP, 55, See also STP Ethernet link aggregation static mode, 32
basic concepts, 62 inloopback interface configuration, 13
CIST calculation, 66 Layer 2 Ethernet interface configuration, 8
configuration, 55, 67, 69, 91 Layer 2 Ethernet interface storm control
device implementation, 67 configuration, 9
device priority configuration, 73 Layer 2 Ethernet interface storm suppression
displaying, 91 configuration, 8
features, 62 loop detection interval, 97, 99
how it works, 66 loop detection protection action configuration, 98
maintaining, 91 loop protection actions, 97
mode set, 70 loopback interface configuration, 12
MSTI calculation, 66 MAC address table address synchronization, 22
No Agreement Check, 85, 87 MAC address table blackhole entry, 19
protocols and standards, 67 MAC address table dynamic aging timer, 22
relationship to RSTP and STP, 62 MAC address table entry configuration, 18
root bridge configuration, 72 MAC address table entry types, 17
root bridge device configuration, 72 MAC address table multiport unicast entry, 20
secondary root bridge configuration, 72 MST region configuration, 71
secondary root bridge device configuration, 72 MSTP mode set, 70
STP basic concepts, 56 null interface configuration, 13
144
port-based VLAN access port assignment, 107 LLDP basic concepts, 113
port-based VLAN access port assignment (in LLDP basic configuration, 119, 128
interface view), 107 LLDP configuration, 113, 119
port-based VLAN access port assignment (in loop detection, 96
VLAN view), 107 loop detection configuration, 98, 100
port-based VLAN hybrid port assignment, 109 loopback interface configuration, 12
port-based VLAN trunk port assignment, 108 MAC address table configuration, 17, 18, 24
RSTP mode set, 70 MAC Information configuration, 26, 27
RSTP network convergence, 62 MSTP configuration, 55, 67, 91
STP algorithm calculation, 57 null interface configuration, 12
STP BPDU guard, 87 port isolation configuration, 52
STP BPDU transmission rate, 76 port isolation configuration (on LAN), 53
STP designated bridge, 56 RSTP configuration, 55, 67, 91
STP designated port, 56 STP configuration, 55, 67, 91
STP Digest Snooping, 83, 84 VLAN basic configuration, 104
STP edge port, 76 VLAN configuration, 103
STP loop guard, 88 No Agreement Check (STP), 85, 87
STP mode set, 70 no-learning action (loop detection), 97
STP No Agreement Check, 85, 87 null interface
STP path cost, 56 configuration, 12, 13, 13
STP port link type, 80 displaying, 13
STP port mode, 80 maintaining, 13
STP port path cost, 77, 78
O
STP port priority, 79
STP port role restriction, 89 operational key (Ethernet link aggregation), 31
STP port state transition, 81 organization-specific LLDPDU TLV types, 115
STP protection functions, 87 outputting
STP root bridge, 56 STP port state transition information, 81
STP root guard, 88 P
STP root port, 56 packet
STP switched network diameter, 73 Ethernet link aggregation packet type-based load
STP TC-BPDU guard, 90 sharing, 37
STP TC-BPDU transmission restriction, 90 LLDP CDP compatibility, 125
VLAN interface basic configuration, 105 STP BPDU protocol packets, 55
VLAN port-based configuration, 106, 110 STP port mode configuration, 80
network management STP TCN BPDU protocol packets, 55
Ethernet interface configuration, 1 parameter
Ethernet link aggregation STP timeout factor, 75
configuration, 30, 37, 45 per-flow load sharing, 37
inloopback interface configuration, 12 performing
interface bulk configuration, 15 STP mCheck, 82
Layer 2 Ethernet link aggregation (dynamic), 47 STP mCheck globally, 82
Layer 2 Ethernet link aggregation (static), 45 STP mCheck in interface view, 82
Layer 2 Ethernet link aggregation load per-packet load sharing, 37
sharing, 48
PFC (Ethernet interface), 6
145
physical Layer 2 Ethernet link aggregation group (static), 38
Ethernet interface physical state change Layer 2 Ethernet link aggregation load sharing, 48
suppression, 4 LLDP basic configuration, 119, 128
polling LLDP configuration, 113, 119
LLDP enable, 121 LLDP disable operating mode, 118, 120
port LLDP enable, 119
Ethernet aggregate interface (description), 39 LLDP operating mode, 120
Ethernet aggregate interface configuration, 39 LLDP polling, 121
Ethernet link aggregate group min/max number LLDP re-initialization delay, 121
Selected ports, 40 LLDP Rx operating mode, 118, 120
Ethernet link aggregate interface (expected LLDP Tx operating mode, 118, 120
bandwidth), 41
LLDP TxRx operating mode, 118, 120
Ethernet link aggregate interface default
LLDPDU encapsulation format, 125
settings, 42
LLDPDU reception, 119
Ethernet link aggregate interface shutdown, 41
LLDPDU transmission, 118
Ethernet link aggregation
loop detection configuration, 96, 98, 100
configuration, 30, 37, 45
loop detection interval, 97, 99
Ethernet link aggregation configuration
types, 31 loop detection protection action configuration, 98
Ethernet link aggregation dynamic mode, 33 loop detection protection actions, 97
Ethernet link aggregation group loop detection status auto recovery, 97
configuration, 37 MAC address learning, 17
Ethernet link aggregation LACP, 33 MAC address table blackhole entry, 19
Ethernet link aggregation load sharing, 42 MAC address table configuration, 17, 18, 24
Ethernet link aggregation load sharing MAC address table entry configuration, 18
criteria, 37 MAC address table multiport unicast entry, 20
Ethernet link aggregation local-first load MAC Information configuration, 26, 27
sharing, 43 MST port roles, 65
Ethernet link aggregation member port, 30 MST port states, 65
Ethernet link aggregation member port RSTP network convergence, 62
state, 30, 32, 35 STP BPDU guard, 87
Ethernet link aggregation modes, 31 STP BPDU transmission rate, 76
Ethernet link aggregation operational key, 31 STP designated port, 56
Ethernet link aggregation reference port, 34 STP edge port configuration, 76
Ethernet link aggregation reference port STP forward delay timer, 74
choice, 32
STP loop guard, 88
Ethernet link aggregation static mode, 32
STP mCheck, 82
STP mCheck (global), 82
group assignment (port isolation), 52
STP mCheck (interface view), 82
isolation. See port isolation
STP path cost calculation standard, 77
Layer 2 aggregate interface (ignored
STP path cost configuration, 77, 78
VLAN), 40
STP port link type configuration, 80
Layer 2 Ethernet link aggregation (dynamic), 47
STP port mode configuration, 80
Layer 2 Ethernet link aggregation (static), 45
STP port priority configuration, 79
(dynamic), 38 STP port role restriction, 89
STP port state transition output, 81
146
STP root guard, 88 configuring Ethernet interface basic settings, 3
STP root port, 56 configuring Ethernet interface common settings, 1
STP TC-BPDU guard, 90 configuring Ethernet interface generic flow
STP TC-BPDU transmission restriction, 90 control, 5
VLAN port link type, 106 configuring Ethernet interface jumbo frame
port isolation support, 4
configuration, 52 configuring Ethernet interface link mode, 4
configuration (on LAN), 53 configuring Ethernet interface PFC, 6
displaying, 52 configuring Ethernet interface physical state change
suppression, 4
port assignment to group (multiple), 52
configuring Ethernet link aggregate interface
port-based VLAN
(expected bandwidth), 41
access port assignment, 107
configuring Ethernet link aggregation, 37, 45
access port assignment (in interface view), 107
configuring Ethernet link aggregation group, 37
access port assignment (in VLAN view), 107
configuring Ethernet link aggregation group load
configuration, 106, 110
sharing criteria, 42
hybrid port assignment, 109
configuring Ethernet link aggregation load
port frame handling, 107 sharing, 42
port link type, 106 configuring inloopback interface, 13
PVID, 106 configuring Layer 2 Ethernet interface, 8
trunk port assignment, 108 configuring Layer 2 Ethernet interface storm
priority control, 9
Ethernet link aggregation LACP, 33 configuring Layer 2 Ethernet interface storm
MSTP device priority, 73 suppression, 8
RSTP device priority, 73 configuring Layer 2 Ethernet link aggregation
STP device priority, 73 (dynamic), 47
STP port priority configuration, 79 configuring Layer 2 Ethernet link aggregation
priority-based flow control. Use PFC (static), 45
procedure configuring Layer 2 Ethernet link aggregation group

(dynamic), 38
adding MAC address table blackhole entry, 19
configuring Layer 2 Ethernet link aggregation group
adding MAC address table multiport unicast
(static), 38
entry, 20
configuring Layer 2 Ethernet link aggregation load
assigning port to isolation group (multiple), 52
sharing, 48
assigning port-based VLAN access port, 107
configuring LLDP, 119
assigning port-based VLAN access port (in
configuring LLDP advertisable TLVs, 122
interface view), 107
configuring LLDP basics, 119, 128
assigning port-based VLAN access port (in
VLAN view), 107 configuring LLDP bridge mode, 120
assigning port-based VLAN hybrid port, 109 configuring LLDP CDP compatibility, 125
assigning port-based VLAN trunk port, 108 configuring LLDP management address, 123
bulk configuring interfaces, 15 configuring LLDP management address encoding
format, 123
combining 10-GE breakout interfaces into
40-GE interface, 2 configuring LLDP trapping, 126
configuring Ethernet aggregate interface, 39 configuring LLDP-MED trapping, 126
configuring Ethernet aggregate interface configuring loop detection, 98, 100
(description), 39 configuring loop detection protection action, 98
147
configuring loop detection protection action configuring STP protection functions, 87
(global), 99 configuring STP root bridge, 72
configuring loop detection protection action configuring STP root bridge device, 72
(Layer 2 aggregate interface), 99 configuring STP secondary root bridge, 72
configuring loop detection protection action configuring STP secondary root bridge device, 72
(Layer 2 Ethernet interface), 99
configuring STP switched network diameter, 73
configuring loopback interface, 12
configuring STP TC-BPDU transmission
configuring MAC address table, 24 restriction, 90
configuring MAC address table dynamic aging configuring STP timeout factor, 75
timer, 22
configuring STP timer, 74
configuring MAC address table entry, 18
configuring VLAN (port-based), 106, 110
configuring MAC Information, 27
configuring VLAN basic settings, 104
configuring MAC Information change send
configuring VLAN interface basic settings, 105
interval, 27
disabling global MAC address learning, 21
configuring MAC Information mode, 26
disabling MAC address learning, 21
configuring MAC Information queue length, 27
disabling MAC address learning on interface, 21
configuring management Ethernet interface, 1
displaying bulk interface configuration, 16
configuring MST region, 71
displaying Ethernet interface, 10
configuring MST region max hops, 73
displaying Ethernet link aggregation, 44
configuring MSTP, 67, 69, 91
displaying inloopback interface, 13
configuring MSTP device priority, 73
displaying LLDP, 127
configuring MSTP root bridge, 72
displaying loop detection, 100
configuring MSTP root bridge device, 72
displaying loopback interface, 13
configuring MSTP secondary root bridge, 72
displaying MAC address table, 24
configuring MSTP secondary root bridge
displaying MSTP, 91
device, 72
displaying null interface, 13
configuring null interface, 13
displaying port isolation, 52
configuring port isolation (on LAN), 53
displaying RSTP, 91
configuring RSTP, 67, 68, 91
displaying STP, 91
configuring RSTP device priority, 73
displaying VLAN, 110
configuring RSTP root bridge, 72
enabling Ethernet link aggregation local-first load
configuring RSTP root bridge device, 72
sharing, 43
configuring RSTP secondary root bridge, 72
enabling Ethernet link aggregation traffic
configuring RSTP secondary root bridge
redirection, 44
device, 72
enabling LLDP, 119
configuring STP, 67, 68, 91
enabling LLDP polling, 121
configuring STP BPDU transmission rate, 76
enabling loop detection, 98
configuring STP device priority, 73
enabling loop detection (global), 98
configuring STP Digest Snooping, 83, 84
enabling loop detection (port-specific), 98
configuring STP edge port, 76
enabling MAC address synchronization
configuring STP No Agreement Check, 85, 87
globally, 22
configuring STP port link type, 80
enabling MAC Information, 26
configuring STP port mode for MSTP packets, 80
enabling STP BPDU guard, 87
configuring STP port path cost, 77, 78
enabling STP feature, 81
configuring STP port priority, 79
enabling STP loop guard, 88
configuring STP port role restriction, 89
148
enabling STP port state transition information LLDP, 119
output, 81 MSTP, 67
enabling STP root guard, 88 STP protocol packets, 55
enabling STP TC-BPDU guard, 90 VLAN, 104
maintaining Ethernet interface, 10 PVID (port-based VLAN), 106
maintaining Ethernet link aggregation, 44
Q
maintaining inloopback interface, 13
QinQ
maintaining loopback interface, 13
maintaining MSTP, 91
queuing
maintaining null interface, 13
MAC Information queue length, 27
maintaining RSTP, 91
maintaining STP, 91 R
maintaining VLAN, 110 rate
modifying MAC address table blackhole STP BPDU transmission rate, 76
entry, 19 receiving
modifying MAC address table multiport unicast LLDPDUs, 119
entry, 20
recovering
performing STP mCheck, 82
loop detection port status auto recovery, 97
performing STP mCheck globally, 82
reference port (Ethernet link aggregation), 32, 34
performing STP mCheck in interface view, 82
region
restoring Ethernet link aggregate interface
MST, 63
default settings, 42
MST region configuration, 71
setting Ethernet link aggregate group min/max
number Selected ports, 40 MST region max hops, 73
setting LLDP operating mode, 120 MST regional root, 64
setting LLDP parameters, 124 re-initialization delay (LLDP), 121
setting LLDP re-initialization delay, 121 restoring
setting LLDPDU encapsulation format, 125 Ethernet link aggregate interface default
settings, 42
setting loop detection interval, 99
restrictions
setting MSTP mode, 70
setting RSTP mode, 70
STP Digest Snooping configuration, 83
setting STP mode, 70
STP edge port configuration, 76
shutting down Ethernet link aggregate
interface, 41 STP port link type configuration, 80
specifying Layer 2 aggregate interface (ignored STP port role restriction, 89
VLAN), 40 STP TC-BPDU transmission restriction, 90
specifying STP port path cost calculation STP timer configuration, 74
standard, 77 root
splitting 40-GE interface into 10-GE breakout MST common root bridge, 64
interfaces, 2 MST regional root, 64
splitting and combining Ethernet interface, 2 MST root port role, 65
protecting MSTP root bridge configuration, 72
STP protection functions, 87 MSTP secondary root bridge configuration, 72
protocols and standards RSTP root bridge configuration, 72
Ethernet link aggregation protocol RSTP secondary root bridge configuration, 72
configuration, 31 STP algorithm calculation, 57
149
STP root bridge, 56 LLDPDU encapsulated in SNAP format, 114
STP root bridge configuration, 72 LLDPDU encapsulation format, 125
STP root guard, 88 SNMP
STP root port, 56 MAC Information configuration, 26, 27
STP secondary root bridge configuration, 72 snooping
RSTP, 55, See also STP STP Digest Snooping, 83, 84
configuration, 55, 67, 68, 91 spanning tree. Use STP, RSTP, MSTP
device priority configuration, 73 specifying
displaying, 91 Layer 2 aggregate interface (ignored VLAN), 40
maintaining, 91 STP port path cost calculation standard, 77
mode set, 70 state
network convergence, 62 Ethernet interface state change suppression, 4
No Agreement Check, 85, 87 Ethernet link aggregation member port
root bridge configuration, 72 state, 30, 32, 35
root bridge device configuration, 72 static
secondary root bridge configuration, 72 Ethernet link aggregation mode, 31
secondary root bridge device configuration, 72 Ethernet link aggregation static mode, 32
STP basic concepts, 56 Layer 2 Ethernet link aggregation, 45
Layer 2 Ethernet link aggregation group, 38
S
MAC address table entry, 17
selecting
storm
Ethernet link aggregation Selected ports, 40
Layer 2 Ethernet interface storm control, 9
Ethernet link aggregation selected state, 30
Layer 2 Ethernet interface storm suppression, 8
Ethernet link aggregation unselected state, 30
STP
sending
algorithm calculation, 57
MAC Information change send interval, 27
basic concepts, 56
service
BPDU forwarding, 61
LLDP service bridge mode, 120
BPDU guard enable, 87
setting
BPDU transmission rate configuration, 76
Ethernet link aggregate group min/max number
CIST, 64
Selected ports, 40
configuration, 55, 67, 68, 91
Ethernet link aggregation member port
CST, 64
state, 32, 35
designated bridge, 56
LLDP operating mode, 120
designated port, 56
LLDP parameters, 124
device priority configuration, 73
LLDP re-initialization delay, 121
Digest Snooping, 83, 84
LLDPDU encapsulation format, 125
Digest Snooping configuration restrictions, 83
loop detection interval, 99
displaying, 91
MSTP mode, 70
edge port configuration, 76
RSTP mode, 70
edge port configuration restrictions, 76
STP mode, 70
feature enable, 81
shutting down
IST, 64
Ethernet link aggregate interface, 41
loop detection, 55
loop detection shutdown action, 97
loop guard enable, 88
SNAP
maintaining, 91
150
mCheck, 82 Ethernet interface physical state change
mCheck (global), 82 suppression, 4
mCheck (interface view), 82 Layer 2 Ethernet interface storm control
mode set, 70 configuration, 9
MST common root bridge, 64 Layer 2 Ethernet interface storm suppression
configuration, 8
MST port roles, 65
switching
MST port states, 65
Ethernet interface configuration, 1
MST region, 63
inloopback interface configuration, 12, 13
MST region configuration, 71
loopback interface configuration, 12, 12
MST regional root, 64
MAC address table configuration, 17, 18, 24
MSTI, 64
null interface configuration, 12, 13
MSTI calculation, 66
port isolation configuration, 52
MSTP, 62, See also MSTP
port isolation configuration (on LAN), 53
MSTP CIST calculation, 66
port-based VLAN access port assignment, 107
MSTP device implementation, 67
port-based VLAN access port assignment (in
No Agreement Check, 85, 87
interface view), 107
path cost, 56
port-based VLAN access port assignment (in VLAN
port link type configuration, 80
view), 107
port link type configuration restrictions, 80
port-based VLAN hybrid port assignment, 109
port mode configuration, 80
port-based VLAN trunk port assignment, 108
port path cost calculation standard, 77
VLAN basic configuration, 104
port path cost configuration, 77, 78
VLAN configuration, 103
port priority configuration, 79
VLAN interface basic configuration, 105
port role restriction, 89
VLAN port-based configuration, 106, 110
port state transition output, 81
synchronizing
protection functions, 87
MAC addresses, 22
protocol packets, 55
system
root bridge, 56
interface bulk configuration, 15
root bridge configuration, 72
T
root bridge device configuration, 72
root guard enable, 88 table
root port, 56 MAC address, 17, 18, 24
RSTP, 62, See also RSTP MSTP VLAN-to-instance mapping table, 64
secondary root bridge configuration, 72 TC-BPDU
secondary root bridge device configuration, 72 STP TC-BPDU guard, 90
switched network diameter, 73 STP TC-BPDU transmission restriction, 90
TC-BPDU guard, 90 time
TC-BPDU transmission restriction, 90 Ethernet link aggregation LACP timeout interval, 33
timeout factor configuration, 75 timeout
timer configuration, 74 STP timeout factor, 75
timer configuration restrictions, 74 timer
timers, 61 LLDP re-initialization delay, 121
VLAN-to-instance mapping table, 64 MAC address table dynamic aging timer, 22
suppressing STP forward delay, 61, 74
STP hello, 61, 74
151
STP max age, 61, 74 MSTP VLAN-to-instance mapping table, 64
TLV port isolation configuration, 52
LLDP advertisable TLV configuration, 122 port link type, 106
LLDP management address configuration, 123 port-based configuration, 106, 110
LLDP management address encoding port-based VLAN access port assignment, 107
format, 123 port-based VLAN access port assignment (in
LLDP parameters, 124 interface view), 107
LLDPDU basic management types, 115 port-based VLAN access port assignment (in VLAN
LLDPDU LLDP-MED types, 115 view), 107
LLDPDU management address TLV, 118 port-based VLAN frame handling, 107
LLDPDU organization-specific types, 115 port-based VLAN trunk port assignment, 108
topology protocols and standards, 104
STP TCN BPDU protocol packets, 55 PVID, 106
traffic voice traffic
Ethernet link aggregation traffic redirection, 44 LLDP CDP compatibility, 125
transmitting
LLDPDUs, 118
STP TC-BPDU transmission restriction, 90
trapping
LLDP configuration, 126
LLDP-MED configuration, 126
MAC Information configuration, 26, 27
MAC Information mode configuration, 26
trunk port
port-based VLAN assignment, 108
U
unicast
MAC address table configuration, 17, 18, 24
MAC address table multiport unicast entry, 17
V
Virtual Local Area Network. Use VLAN
VLAN
basic configuration, 104
configuration, 103
configuring, 103
displaying, 110
frame encapsulation, 103
hybrid port assignment, 109
interface basic configuration, 105
Layer 2 Ethernet aggregate interface (ignored
VLAN), 40
LLDP CDP compatibility, 125
maintaining, 110
152

Manual HP 7900

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Manual HP 7900

Caricato da

Copyright:

Formati disponibili

HP FlexFabric 7900 Switch Series

Layer 2LAN Switching

Part number: 5998-4281

Copyright 2014 Hewlett-Packard Development Company, L.P.

Configuring Ethernet interfaces 1

Configuring loopback, null, and inloopback interfaces 12

Bulk configuring interfaces 15

Configuring the MAC address table 17

Configuring MAC Information 26

Configuring Ethernet link aggregation 30

Configuring port isolation 52

Configuring spanning tree protocols 55

Configuring loop detection 96

Configuring VLANs 103

Configuring LLDP 113

Support and other resources 133

Configuring a management Ethernet interface

Step Command Remarks

Ethernet interface naming conventions

Configuring common Ethernet interface settings

Step Command Remarks

By default, a 40-GE interface is not

After creating the four 10-GE

Combining four 10-GE breakout interfaces into a 40-GE interface

Step Command Remarks

After creating the 40-GE interface,

Configuring basic settings of an Ethernet interface

Step Command Remarks

The default setting is in the format of

The default setting is auto for Ethernet

Step Command Remarks

Configuring jumbo frame support

Step Command Remarks

By default, the device allows jumbo

Configuring physical state change suppression on an Ethernet

Step Command Remarks

By default, each time the physical link of a port

By default, each time the physical link of a port

Configuring generic flow control on an Ethernet interface

Step Command Remarks

Configuring PFC on an Ethernet interface

Step Command Remarks

When you configure PFC, follow these guidelines:

Configuring a Layer 2 Ethernet interface

Step Command Remarks

Configuring storm control on an Ethernet interface

Step Command Remarks

By default, the interface outputs log

By default, the interface sends

Displaying and maintaining an Ethernet interface

Display the operational and status

Display information about dropped

Display the Ethernet module statistics. display ethernet statistics

Clear the statistics of dropped packets on

Clear the Ethernet module statistics. reset ethernet statistics

Configuring a loopback interface

Step Command Remarks

The default setting is interface name

Step Command Remarks

Interface Null 0 is the default null

Configuring an inloopback interface

Displaying and maintaining loopback, null, and

Display information about the inloopback