HP FlexFabric 12900 series User manual
HP FlexFabric 12900 Switch Series
Layer 2—LAN Switching
Configuration Guide
Part number: 5998-7268
Software version: R103x
Document version: 6W100-20150116
Legal and notice information
© Copyright 2015 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.
i
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··························································5
Performing a loopback test on an Ethernet interface····························································································6
Configuring generic flow control on an Ethernet interface··················································································7
Configuring PFC on an Ethernet interface ·············································································································8
Setting the statistics polling interval························································································································9
Forcibly bringing up a fiber port ····························································································································9
Configuring a Layer 2 Ethernet interface ···················································································································· 11
Configuring storm suppression ···························································································································· 11
Configuring storm control on an Ethernet interface··························································································· 11
Setting the MDIX mode of an Ethernet interface ································································································ 13
Testing the cable connection of an Ethernet interface······················································································· 14
Enabling bridging on an Ethernet interface ······································································································· 14
Displaying and maintaining an Ethernet interface ····································································································· 14
Configuring loopback, null, and inloopback interfaces··························································································16
Configuring a loopback interface ································································································································ 16
Configuring a null interface ·········································································································································· 17
Configuring an inloopback interface··························································································································· 17
Displaying and maintaining loopback, null, and inloopback interfaces ································································· 17
Bulk configuring interfaces ········································································································································19
Configuration restrictions and guidelines···················································································································· 19
Configuration procedure··············································································································································· 20
Displaying and maintaining bulk interface configuration·························································································· 20
Configuring the MAC address table ························································································································21
Overview········································································································································································· 21
How a MAC address entry is created ················································································································ 21
Types of MAC address entries····························································································································· 22
MAC address table configuration task list ·················································································································· 22
Configuring MAC address entries································································································································ 23
Configuration guidelines ······································································································································ 23
Adding or modifying a static or dynamic MAC address entry globally ························································· 23
Adding or modifying a static or dynamic MAC address entry on an interface············································· 24
Adding or modifying a blackhole MAC address entry····················································································· 24
Adding or modifying a multiport unicast MAC address entry ········································································· 24
Disabling MAC address learning································································································································· 26
Disabling global MAC address learning············································································································ 26
Disabling MAC address learning on interfaces································································································· 26
Disabling MAC address learning on a VLAN···································································································· 27
Configuring the aging timer for dynamic MAC address entries··············································································· 27
Configuring the MAC learning limit on interfaces······································································································ 28
ii
Configuring the device to forward unknown frames after the MAC learning limit on an interface is reached··· 28
Enabling MAC address synchronization····················································································································· 29
Enabling ARP fast update for MAC address moves··································································································· 30
Displaying and maintaining the MAC address table································································································· 31
MAC address table configuration example ················································································································ 31
Network requirements··········································································································································· 31
Configuration procedure ······································································································································ 32
Verifying the configuration··································································································································· 32
Configuring MAC Information ··································································································································33
Enabling MAC Information ··········································································································································· 33
Configuring the MAC Information mode····················································································································· 34
Configuring the MAC change notification interval ···································································································· 34
Configuring the MAC Information queue length ········································································································ 34
MAC Information configuration example···················································································································· 35
Network requirements··········································································································································· 35
Configuration restrictions and guidelines ··········································································································· 35
Configuration procedure ······································································································································ 35
Configuring Ethernet link aggregation ·····················································································································37
Basic concepts································································································································································ 37
Aggregation group, member port, and aggregate interface··········································································· 37
Aggregation states of member ports in an aggregation group ······································································· 37
Operational key ···················································································································································· 38
Configuration types··············································································································································· 38
Link aggregation modes ······································································································································· 39
Aggregating links in static mode·································································································································· 39
Choosing a reference port ··································································································································· 39
Setting the aggregation state of each member port ·························································································· 39
Aggregating links in dynamic mode···························································································································· 40
LACP ······································································································································································· 40
How dynamic link aggregation works················································································································ 41
Edge aggregate interface ············································································································································· 44
Load sharing modes for link aggregation groups ······································································································ 44
Ethernet link aggregation configuration task list········································································································· 44
Configuring an aggregation group ····························································································································· 45
Configuration restrictions and guidelines ··········································································································· 45
Configuring a Layer 2 static aggregation group······························································································· 45
Configuring a Layer 2 dynamic aggregation group ························································································· 46
Configuring a Layer 2 aggregate interface ················································································································ 47
Configuring the description of a Layer 2 aggregate interface········································································· 47
Specifying ignored VLANs on a Layer 2 aggregate interface ········································································· 47
Setting the minimum and maximum numbers of Selected ports for an aggregation group·························· 48
Configuring the expected bandwidth of an aggregate interface ···································································· 49
Configuring an edge aggregate interface·········································································································· 49
Shutting down an aggregate interface ··············································································································· 50
Restoring the default settings for an aggregate interface ················································································· 50
Configuring load sharing for link aggregation groups······························································································ 50
Configuring load sharing modes for link aggregation groups········································································· 51
Enabling local-first load sharing for link aggregation······················································································· 52
Enabling link-aggregation traffic redirection··············································································································· 53
Configuration restrictions and guidelines ··········································································································· 53
Configuration procedure ······································································································································ 53
Displaying and maintaining Ethernet link aggregation ····························································································· 54
Ethernet link aggregation configuration examples····································································································· 54
iii
Layer 2 static aggregation configuration example···························································································· 54
Layer 2 dynamic aggregation configuration example······················································································ 56
Layer 2 aggregation load sharing configuration example··············································································· 58
Layer 2 edge aggregate interface configuration example ··············································································· 60
Configuring port isolation··········································································································································63
Assigning ports to an isolation group·························································································································· 63
Displaying and maintaining port isolation ·················································································································· 63
Port isolation configuration example···························································································································· 64
Network requirements··········································································································································· 64
Configuration procedure ······································································································································ 64
Verifying the configuration··································································································································· 65
Configuring spanning tree protocols ························································································································66
STP ··················································································································································································· 66
STP protocol packets ············································································································································· 66
Basic concepts in STP············································································································································ 67
Calculation process of the STP algorithm ··········································································································· 68
RSTP················································································································································································· 74
PVST················································································································································································· 75
MSTP················································································································································································ 75
MSTP features ························································································································································ 75
MSTP basic concepts ············································································································································ 76
How MSTP works ·················································································································································· 79
MSTP implementation on devices ························································································································ 80
Protocols and standards ················································································································································ 80
Spanning tree configuration task lists ·························································································································· 80
STP configuration task list····································································································································· 81
RSTP configuration task list··································································································································· 82
PVST configuration task list··································································································································· 83
MSTP configuration task list ································································································································· 84
Setting the spanning tree mode···································································································································· 84
Configuring an MST region ·········································································································································· 85
Configuring the root bridge or a secondary root bridge ·························································································· 86
Configuring the current device as the root bridge of a specific spanning tree·············································· 87
Configuring the current device as a secondary root bridge of a specific spanning tree······························ 87
Configuring the device priority····································································································································· 87
Configuring the maximum hops of an MST region ···································································································· 88
Configuring the network diameter of a switched network························································································· 88
Configuring spanning tree timers································································································································· 89
Configuration restrictions and guidelines ··········································································································· 89
Configuration procedure ······································································································································ 90
Configuring the timeout factor ······································································································································ 90
Configuring the BPDU transmission rate······················································································································ 91
Configuring edge ports ················································································································································· 91
Configuration restrictions and guidelines ··········································································································· 91
Configuration procedure ······································································································································ 91
Configuring path costs of ports ···································································································································· 92
Specifying a standard for the device to use when it calculates the default path cost ··································· 92
Configuring path costs of ports···························································································································· 95
Configuration example ········································································································································· 95
Configuring the port priority ········································································································································· 95
Configuring the port link type······································································································································· 96
Configuration restrictions and guidelines ··········································································································· 96
Configuration procedure ······································································································································ 96
iv
Configuring the mode a port uses to recognize and send MSTP packets ······························································· 97
Enabling outputting port state transition information·································································································· 97
Enabling the spanning tree feature ······························································································································ 98
Enabling the spanning tree feature in STP/RSTP/MSTP mode········································································· 98
Enabling the spanning tree feature in PVST mode····························································································· 98
Performing mCheck························································································································································ 99
Configuration restrictions and guidelines ··········································································································· 99
Configuration procedure ······································································································································ 99
Configuring Digest Snooping ·····································································································································100
Configuration restrictions and guidelines ·········································································································100
Configuration procedure ····································································································································101
Digest Snooping configuration example···········································································································101
Configuring No Agreement Check ····························································································································102
Configuration prerequisites ································································································································103
Configuration procedure ····································································································································103
No Agreement Check configuration example··································································································104
Configuring protection functions ································································································································104
Enabling BPDU guard ·········································································································································104
Enabling root guard············································································································································105
Enabling loop guard ···········································································································································106
Configuring port role restriction·························································································································106
Configuring TC-BPDU transmission restriction··································································································107
Enabling TC-BPDU guard····································································································································107
Displaying and maintaining the spanning tree·········································································································108
Spanning tree configuration example························································································································109
MSTP configuration example ·····························································································································109
PVST configuration example ······························································································································112
Configuring loop detection····································································································································· 116
Overview·······································································································································································116
Loop detection mechanism ·································································································································116
Loop detection interval········································································································································117
Loop protection actions·······································································································································117
Port status auto recovery·····································································································································118
Loop detection configuration task list·························································································································118
Enabling loop detection ··············································································································································118
Enabling loop detection globally·······················································································································118
Enabling loop detection on a port·····················································································································118
Configuring the loop protection action······················································································································119
Configuring the global loop protection action·································································································119
Configuring the loop protection action on a Layer 2 Ethernet interface ·······················································119
Configuring the loop protection action on a Layer 2 aggregate interface···················································119
Setting the loop detection interval ······························································································································120
Displaying and maintaining loop detection ··············································································································120
Loop detection configuration example·······················································································································120
Network requirements·········································································································································120
Configuration procedure ····································································································································121
Verifying the configuration·································································································································122
Configuring VLANs················································································································································· 124
Overview·······································································································································································124
VLAN frame encapsulation ································································································································124
Protocols and standards ·····································································································································125
Configuring basic VLAN settings································································································································125
Configuring basic settings of a VLAN interface ·······································································································126
v
Configuring port-based VLANs···································································································································127
Introduction to port-based VLAN ·······················································································································127
Assigning an access port to a VLAN ················································································································128
Assigning a trunk port to a VLAN······················································································································129
Assigning a hybrid port to a VLAN···················································································································130
Displaying and maintaining VLANs···························································································································131
Port-based VLAN configuration example···················································································································132
Network requirements·········································································································································132
Configuration procedure ····································································································································132
Verifying the configuration·································································································································133
Configuring the private VLAN································································································································ 134
Configuration task list ··················································································································································134
Configuration restrictions and guidelines··················································································································135
Configuration procedure·············································································································································135
Displaying and maintaining the private VLAN ·········································································································137
Private VLAN configuration examples ·······················································································································138
Promiscuous port configuration example··········································································································138
Trunk promiscuous port configuration example ·······························································································140
Trunk promiscuous and trunk secondary port configuration example···························································144
Secondary VLAN Layer 3 communication configuration example ································································148
Configuring QinQ··················································································································································· 151
Overview·······································································································································································151
How QinQ works················································································································································151
QinQ implementations········································································································································152
Protocols and standards ·····································································································································152
Restrictions and guidelines··········································································································································153
Configuring QinQ························································································································································153
Enabling QinQ ····················································································································································153
Configuring transparent transmission for VLANs·····························································································154
Configuring the TPID for VLAN tags ··························································································································154
Configuring the CVLAN TPID ·····························································································································155
Configuring the SVLAN TPID······························································································································155
Setting the 802.1p priority in SVLAN tags ···············································································································156
Displaying and maintaining QinQ ····························································································································157
QinQ configuration examples ····································································································································157
Basic QinQ configuration example···················································································································157
VLAN transparent transmission configuration example ··················································································159
Configuring VLAN mapping ·································································································································· 162
Overview·······································································································································································162
Application scenario of one-to-one VLAN mapping························································································162
Application scenario of one-to-two and two-to-two VLAN mapping······························································163
VLAN mapping implementations ·······················································································································164
VLAN mapping configuration task list ·······················································································································166
Configuring one-to-one VLAN mapping ····················································································································167
Configuring one-to-two VLAN mapping ····················································································································168
Configuring two-to-two VLAN mapping·····················································································································168
Displaying and maintaining VLAN mapping············································································································169
VLAN mapping configuration examples ···················································································································169
One-to-one VLAN mapping configuration example ························································································169
One-to-two and two-to-two VLAN mapping configuration example ······························································171
Configuring LLDP····················································································································································· 175
Overview·······································································································································································175
vi
Basic concepts ·····················································································································································175
Work mechanism ················································································································································180
Protocols and standards ·····································································································································181
LLDP configuration task list ··········································································································································181
Performing basic LLDP configuration··························································································································182
Enabling LLDP ······················································································································································182
Configuring the LLDP bridge mode····················································································································182
Setting the LLDP operating mode ·······················································································································183
Setting the LLDP reinitialization delay ···············································································································183
Enabling LLDP polling··········································································································································184
Configuring the advertisable TLVs ·····················································································································184
Configuring the management address and its encoding format····································································186
Setting other LLDP parameters····························································································································187
Setting an encapsulation format for LLDP frames·····························································································188
Configuring CDP compatibility···································································································································188
Configuration prerequisites ································································································································189
Configuration procedure ····································································································································189
Configuring DCBX························································································································································190
DCBX configuration task list ·······························································································································191
Enabling LLDP and DCBX TLV advertising ········································································································191
Configuring the DCBX version ···························································································································191
Configuring APP parameters······························································································································192
Configuring ETS parameters ······························································································································194
Configuring PFC parameters······························································································································196
Configuring LLDP trapping and LLDP-MED trapping ································································································197
Displaying and maintaining LLDP·······························································································································197
LLDP configuration examples ······································································································································198
Basic LLDP configuration example·····················································································································198
DCBX configuration example·····························································································································202
Configuring service loopback groups ··················································································································· 208
Configuration procedure·············································································································································208
Displaying and maintaining service loopback groups·····························································································208
Service loopback group configuration example·······································································································209
Network requirements·········································································································································209
Configuration procedure ····································································································································209
Contacting HP ······························································································································································210
Subscription service ············································································································································210
Related information······················································································································································210
Documents····························································································································································210
Websites·······························································································································································210
Conventions ··································································································································································211
Index ········································································································································································ 213
1
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:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter management
Ethernet interface view.
interface M-GigabitEthernet
interface-number N/A
3. (Optional.) Set the
interface description. description text The default setting is
M-GigabitEthernet0/0/0 Interface.
4. (Optional.) Shut down
the interface. shutdown By default, the management Ethernet
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:
•A—Member ID of an IRF 2 member switch.
•B—Slot number of the card in the switch.
•C—Sub-slot number on a card.
•D—Number 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.
A Layer 3 Ethernet interface refers to an Ethernet interface that operates in route mode. To configure an
Ethernet interface to operate in route mode, use the port link-mode route command in Ethernet interface
view. For more information about the port link-mode route command, 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."
2
Splitting a 40-GE interface and combining 10-GE breakout
interfaces
This feature is not supported on non-default MDCs.
Splitting a 40-GE interface into four 10-GE breakout interfaces
IMPORTANT:
Before you restart a switch configured with the using tengige command, save the splittin
g
confi
g
uration
on the switch even if the switch is an IRF member switch. Otherwise, the splittin
g
confi
g
uration cannot take
effect.
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.
If an HP 12910 switch with an LSX1FAB10A1 module or an HP 12916 switch with an LSX1FAB16S1
module uses the LSX1QGS16EA1 board, you can split up to twelve of the sixteen 40-GE QSFP+
interfaces on the board. The 16 interfaces are divided into two groups by their numbers. Interfaces
numbered 1 through 8 belong to one group, and interfaces numbered 9 through 16 belong the other
group. You can split 6 of the 8 interfaces in each group into 10-GE breakout interfaces.
If an HP 12910 switch with an LSX1FAB10A1 module or an HP 12916 switch with an LSX1FAB16S1
module uses the LSXM1QGS24EX1 board, you can split up to eight of the twenty-four 40-GE QSFP+
interfaces on the board. The 24 interfaces are divided into two groups by their numbers. Interfaces
numbered 1 through 12 belong to one group, and interfaces numbered 13 through 24 belong the other
group. You can split 4 of the 12 interfaces in each group into 10-GE breakout interfaces.
To split a 40-GE interface into four 10-GE breakout interfaces:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter 40-GE interface view. interface interface-type
interface-number N/A
3. Split the 40-GE interface into
four 10-GE breakout
interfaces. using tengige
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
and attributes as common 10-GE
interfaces, except that they are
numbered differently.
•A 40-GE interface split into four
10-GE breakout interfaces must
use a dedicated 1-to-4 cable.
4. Reboot the card that houses
the interface. N/A
After creating the four 10-GE
breakout interfaces, the system
removes the 40-GE interface.
3
Combining four 10-GE breakout interfaces into a 40-GE interface
IMPORTANT:
Before you restart a switch configured with the using fortygige command, save the combining
configuration on the switch even if the switch is an IRF member switch. Otherwise, the combining
configuration cannot take effect.
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:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter the view of any 10-GE
breakout interface split from a
40-GE interface.
interface interface-type
interface-number N/A
3. Combine the four 10-GE
breakout interfaces into a
40-GE interface. using fortygige
By default, a 40-GE interface is not
split and operates as a single
interface.
After you combine the four 10-GE
breakout interfaces, replace the
dedicated 1-to-4 cable with a
dedicated 1-to-1 cable.
4. Reboot the card that houses
the interface. N/A
After creating the 40-GE interface,
the system removes the four 10-GE
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:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface
view.
interface interface-type
interface-number N/A
3. Set the interface
description. description text
The default setting is in the format of
interface-name Interface. For example,
Ten-GigabitEthernet1/0/1 Interface.
4
Step Command Remarks
4. Set the duplex mode of
the Ethernet interface. duplex { auto | full | half }
The default setting is auto for Ethernet
interfaces.
Copper ports operating at 1000 Mbps and
fiber ports do not support the half keyword.
You cannot configure the duplex mode for
a 100-GE CFP interface.
5. Set the port speed.
speed { 10 | 100 |1000 |
10000 |40000 | 100000 |
auto }
The default setting is auto for Ethernet
interfaces.
6. Configure the expected
bandwidth of the
interface.
bandwidth bandwidth-value
By default, the expected bandwidth (in
kbps) is the interface baud rate divided by
1000.
7. Restore the default
settings for the Ethernet
interface.
default N/A
8. Bring up the Ethernet
interface. undo shutdown By default, Ethernet interfaces are in up
state.
Configuring the link mode of an Ethernet interface
CAUTION:
A
fter you chan
g
e 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:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface view. interface interface-type
interface-number N/A
3. Change the link mode of the
Ethernet interface. port link-mode { bridge | route } By default, an Ethernet interface
operates in bridge mode.
Configuring jumbo frame support
An Ethernet interface might receive some frames larger than the standard Ethernet frame size during
high-throughput data exchanges, such as file transfers. These frames are called jumbo frames. 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:
5
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface
view.
interface interface-type
interface-number N/A
3. Configure jumbo frame
support. jumboframe enable [ value ]
By default, the switch allows jumbo
frames within 9216 bytes to pass
through Ethernet interfaces.
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
comes up or goes down, the interface immediately reports the change to the CPU. The CPU then
performs the following tasks:
•Notifies the upper-layer protocol modules (such as routing and forwarding modules) of the change
for guiding packet forwarding.
•Automatically generates traps and logs to inform the user to take the correct 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:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet
interface view.
interface interface-type
interface-number N/A
3. Set the link-down
event suppression
interval.
link-delay [msec ]
delay-time
By default, each time the physical link of a port
goes down, the interface immediately reports the
change to the CPU.
When this command is configured:
•The link-down event is not reported to the CPU
until the interface is still down when the
suppression interval (delay-time) expires.
•The link-up event is immediately reported when
the interface comes up.
6
Step Command Remarks
4. Set the link-up event
suppression interval.
link-delay [msec ]
delay-time mode up
By default, each time the physical link of a port
comes up, the interface immediately reports the
change to the CPU.
When this command is configured:
•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.
5. Set the link-updown
event suppression
interval.
link-delay [msec ]
delay-time mode updown
By default, each time the physical link of a port
comes up or goes down, the interface immediately
reports the change to the CPU.
When this command is configured, the link-up or
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 MSTP enabled.
Performing a loopback test on an Ethernet interface
If an Ethernet interface does not work correctly, you can perform a loopback test on it to identify the
problem. An Ethernet interface in a loopback test does not forward data traffic.
Loopback tests include the following types:
•Internal loopback test—Tests all on-chip functions related to Ethernet interfaces.
•External loopback test—Tests the hardware of Ethernet interfaces. To perform an external loopback
test on an Ethernet interface, connect a loopback plug to the Ethernet interface. The switch sends
test packets out of the interface, which are expected to loop over the plug and back to the interface.
If the interface fails to receive any test packets, the hardware of the interface is faulty.
Configuration restrictions and guidelines
•On an administratively shut down interface (displayed as in ADM or Administratively DOWN state),
you cannot perform an internal or external loopback test.
•The speed, duplex, and shutdown commands are not available during a loopback test.
•During a loopback test, the Ethernet interface operates in full duplex mode. When a loopback test
is complete, the port returns to its duplex setting.
Configuration procedure
To perform a loopback test on an Ethernet interface:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface view. interface interface-type
interface-number N/A
7
Step Command Remarks
3. Perform a loopback test. loopback { external | internal } By default, no loopback test is
performed.
Configuring generic flow control on an Ethernet interface
IMPORTANT:
Enabling or disabling flow control on an interface might shut down and then bring up the interface. Make
preparations before enabling or disabling this feature.
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.
•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:
Step Command Remarks
1. Enter system view. system-view N/A
8
Step Command Remarks
2. Enter Ethernet interface
view.
interface interface-type
interface-number N/A
3. Enable generic flow control.
•Enable TxRx mode generic
flow control:
flow-control
•Enable Rx mode generic flow
control:
flow-control receive enable
By default, generic flow control is
disabled on an Ethernet interface.
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.
You can enable PFC for the specified 802.1p priorities at the two ends of a link. When network
congestion occurs, the local switch checks the PFC status for the 802.1p priority carried in each arriving
packet. The switch processes the packet depending on the PFC status as follows:
•If PFC is enabled for the 802.1p priority, the local switch 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:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface view. interface interface-type
interface-number N/A
3. Enable PFC on the interface
through automatic negotiation
or forcibly.
priority-flow-control {auto |
enable }By default, PFC is disabled.
4. Enable PFC for 802.1p
priorities.
priority-flow-control no-drop
dot1p dot1p-list
By default, PFC is disabled for all
802.1p priorities.
When you configure PFC, follow these guidelines:
•To perform PFC on a network port of an IRF member switch, 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.
9
Table 1 The relationship between the PFC function and the generic flow control function
flow-control
priority-flo
w-control
enable
priority-flow-contr
ol no-drop dot1p Remarks
Unconfigurable Configured Configured
You cannot enable flow control by using the
flow-control command on a port where PFC is
enabled and PFC is enabled for the specified
802.1p priority values.
Configured Configurable Unconfigurable
•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
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.
Setting the statistics polling interval
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface
view.
interface interface-type
interface-number N/A
3. Set the statistics polling
interval. flow-interval interval By default, the interface statistics
polling interval is 300 seconds.
To display the interface statistics collected in the last polling interval, use the display interface command.
To clear interface statistics, use the reset counters interface command.
Forcibly bringing up a fiber port
CAUTION:
The following operations on a fiber port will cause link-down and link-up events before the port finally
stays up:
•Configure both the port up-mode command and the speed or duplex command.
•Install or remove fibers or transceiver modules after you forcibly bring up the fiber port.
As shown in Figure 2, a fiber port uses separate fibers for transmitting and receiving packets. The
physical state of the fiber port is up only when both transmit and receive fibers are physically connected.
If one of the fibers is disconnected, the fiber port does not work.
To enable a fiber port to forward traffic over a single link, you can use the port up-mode command. This
command brings up a fiber port by force, even when no fiber links or optical modules are present. If one
fiber link is present and up, the fiber port can forward packets over the link unidirectionally.
10
Figure 2 Forcibly bring up a fiber port
Configuration restrictions and guidelines
When you forcibly bring up a fiber port, follow these guidelines:
•The port up-mode command is mutually exclusive with both the shutdown and loopback
commands.
•A GE fiber port cannot correctly forward traffic if you configure the port up-mode command on the
port and install an electro-optical module, 100/1000-Mbps transceiver module, or 100-Mbps
transceiver module into the port. To solve the problem, use the undo port up-mode command on the
fiber port.
Configuration procedure
To forcibly bring up a fiber port:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface
view.
interface interface-type
interface-number N/A
3. Forcibly bring up the fiber
port. port up-mode
By default, a fiber Ethernet port is not
forcibly brought up, and the physical state
of a fiber port depends on the physical
state of the fibers.
Correct fiber
connection
When Ethernet
interfaces cannot
be or are not
forcibly brought up
When Ethernet interfaces
are forcibly brought up
The fiber is
disconnected.
Fiber link
XGE1/0/1
XGE1/0/1
Device A
Device B
XGE1/0/1
XGE1/0/1
Device A
Device B
XGE1/0/1
XGE1/0/1
Device A
Device B
The interface is
down.
Packets
Fiber port Tx end Rx end
11
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. They 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:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Ethernet interface view. interface interface-type
interface-number N/A
3. Enable broadcast suppression
and set the broadcast
suppression threshold.
broadcast-suppression { ratio |
pps max-pps | kbps max-kbps }
By default, broadcast traffic is
allowed to pass through an
interface.
4. Enable multicast suppression
and set the multicast
suppression threshold.
multicast-suppression { ratio |pps
max-pps | kbps max-kbps }
By default, multicast traffic is
allowed to pass through an
interface.
5. Enable unknown unicast
suppression and set the
unknown unicast suppression
threshold.
unicast-suppression { ratio |pps
max-pps | kbps max-kbps }
By default, unknown unicast traffic
is allowed to pass through an
interface.
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 meets one of the following conditions:
12
•Exceeds the upper threshold.
•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 traffic—Even 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 automatically—The 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.
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 broadcast-suppression,
multicast-suppression, and unicast-suppression commands, see "Configuring storm suppression."
Configuration procedure
To configure storm control on an Ethernet interface:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. (Optional.) Set the traffic
polling interval of the storm
control module.
storm-constrain interval seconds
The default setting is 10 seconds.
For network stability, use the
default or set a higher traffic
polling interval (10 seconds).
3. Enter Ethernet interface view. interface interface-type
interface-number N/A
4. (Optional.) Enable storm
control, and set the lower and
upper thresholds for
broadcast, multicast, or
unknown unicast traffic.
storm-constrain {broadcast |
multicast |unicast }{pps |kbps |
ratio }max-pps-values
min-pps-values
By default, storm control is
disabled.
5. Set the control action to take
when monitored traffic
exceeds the upper threshold.
storm-constrain control {block |
shutdown }
By default, storm control is
disabled.
6. (Optional.) Enable the
interface to log storm control
threshold events.
storm-constrain enable log
By default, the interface outputs log
messages when monitored traffic
exceeds the upper threshold or
falls below the lower threshold
from the upper threshold.
Other manuals for FlexFabric 12900 series
6
Table of contents
Other HP Network Router manuals
HP
HP 5900 User manual
HP
HP StorageWorks 6100 - Enterprise Virtual Array User manual
HP
HP 3600 v2 Series User manual
HP
HP 7000dl Series User instructions
HP
HP FlexNetwork MSR3044 Assembly instructions
HP
HP MSR900-W User manual
HP
HP 10500 series User manual
HP
HP N1200 - StorageWorks Network Storage Router User manual
HP
HP StorageWorks MPX200 User manual
HP
HP A6604 User manual
HP
HP VSR1000 User manual
HP
HP 7000dl Series User manual
HP
HP ProCurve Secure 7102dl User manual
HP
HP ProCurve 2510G Series User manual
HP
HP MSR2000 Series User manual
HP
HP ProCurve Series 2600 User manual
HP
HP FlexNetwork 6600 User manual
HP
HP FlexNetwork MSR 954 User manual
HP
HP MSR SERIES Installation manual
HP
HP 10500 series User manual
Popular Network Router manuals by other brands
HPE
HPE FlexNetwork HSR6600 installation guide
H3C
H3C RA100 installation guide
Planet Networking & Communication
Planet Networking & Communication MGSW-28240F user manual
TP-Link
TP-Link Deco X80 user guide
D-Link
D-Link Ethernet Broadband Router DIR-100 Quick install guide
insys icom
insys icom MRX3 LAN Quick installation guide