HPE FlexNetwork 5510 HI Series User manual
HPE FlexNetwork 5510 HI Switch Series
Layer 2—LAN Switching
Configuration Guide
Part number: 5200-0075a
Software version: Release 11xx
Document version: 6W101-20161221
© Copyright 2015, 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise 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. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Adobe® andAcrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
i
Contents
Configuring Ethernet interfaces ······································································ 1
Configuring a management Ethernet interface ··································································································1
Ethernet interface naming conventions··············································································································1
Configuring common Ethernet interface settings ·······························································································1
Configuring a combo interface (only applicable to HPE 5510 24G SFP 4SFP+ HI 1-slot Switch (JH149A)
switches) ····················································································································································2
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 ·········································································6
Enabling energy saving features on an Ethernet interface ········································································7
Setting the statistics polling interval ···········································································································8
Configuring the interface card operating mode ··························································································8
Enabling automatic negotiation for speed downgrading ············································································9
Configuring a Layer 2 Ethernet interface ···········································································································9
Configuring storm suppression ··················································································································9
Configuring storm control on an Ethernet interface··················································································10
Forcibly bringing up a fiber port················································································································12
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
Configuring a Layer 3 Ethernet interface ·········································································································14
Setting the MTU for an Ethernet interface································································································14
Displaying and maintaining an Ethernet interface····························································································15
Configuring loopback, null, and inloopback interfaces ·································· 16
Configuring a loopback interface ·····················································································································16
Configuring a null interface ······························································································································16
Configuring an inloopback interface·················································································································17
Displaying and maintaining loopback, null, and inloopback interfaces ····························································17
Bulk configuring interfaces············································································ 18
Configuration restrictions and guidelines ·········································································································18
Configuration procedure ··································································································································18
Displaying and maintaining bulk interface configuration ··················································································19
Configuring the MAC address table ······························································ 20
Overview ··························································································································································20
How a MAC address entry is created·······································································································20
Types of MAC address entries·················································································································20
MAC address table configuration task list ········································································································21
Configuring MAC address entries ····················································································································22
Configuration guidelines···························································································································22
Adding or modifying a static or dynamic MAC address entry globally ·····················································22
Adding or modifying a static or dynamic MAC address entry on an interface··········································22
Adding or modifying a blackhole MAC address entry ··············································································23
Adding or modifying a multiport unicast MAC address entry ···································································23
Disabling MAC address learning······················································································································24
Disabling global MAC address learning ···································································································24
Disabling MAC address learning on an interface ·····················································································25
Disabling MAC address learning on a VLAN ···························································································25
Configuring the aging timer for dynamic MAC address entries········································································25
Configuring the MAC learning limit on an interface··························································································26
Configuring the device to forward unknown frames after the MAC learning limit on an interface is reached ··26
ii
Assigning MAC learning priority to an interface ·······························································································27
Enabling MAC address synchronization ··········································································································28
Enable MAC address move notifications ·········································································································29
Enabling ARP fast update for MAC address moves ························································································30
Enabling SNMP notifications for the MAC address table·················································································31
Displaying and maintaining the MAC address table ························································································31
MAC address table configuration example ······································································································32
Network requirements ······························································································································32
Configuration procedure···························································································································32
Verifying the configuration························································································································33
Configuring MAC Information········································································ 34
Enabling MAC Information ·······························································································································34
Configuring the MAC Information mode···········································································································34
Configuring the MAC change notification interval ····························································································35
Configuring the MAC Information queue length·······························································································35
MAC Information configuration example··········································································································35
Network requirements ······························································································································35
Configuration restrictions and guidelines ·································································································36
Configuration procedure···························································································································36
Configuring Ethernet link aggregation··························································· 38
Basic concepts·················································································································································38
Aggregation group, member port, and aggregate interface ·····································································38
Aggregation states of member ports in an aggregation group ·································································38
Operational key ········································································································································39
Configuration types ··································································································································39
Link aggregation modes···························································································································40
Aggregating links in static mode ······················································································································40
Choosing a reference port························································································································40
Setting the aggregation state of each member port ·················································································40
Aggregating links in dynamic mode ·················································································································41
LACP························································································································································41
How dynamic link aggregation works·······································································································42
Edge aggregate interface·································································································································45
Load sharing modes for link aggregation groups·····························································································45
Ethernet link aggregation configuration task list ······························································································45
Configuring an aggregation group ···················································································································46
Configuration restrictions and guidelines ·································································································46
Configuring a static aggregation group ····································································································46
Configuring a dynamic aggregation group ·······························································································47
Configuring an aggregate interface··················································································································49
Configuring the description of an aggregate interface ·············································································49
Specifying ignored VLANs for a Layer 2 aggregate interface ··································································50
Setting the MTU for a Layer 3 aggregate interface ··················································································50
Setting the minimum and maximum numbers of Selected ports for an aggregation group ·····················50
Setting the expected bandwidth for an aggregate interface·····································································51
Configuring an edge aggregate interface·································································································51
Enabling BFD for an aggregation group···································································································52
Shutting down an aggregate interface ·····································································································53
Restoring the default settings for an aggregate interface ········································································53
Configuring load sharing for link aggregation groups ······················································································54
Setting load sharing modes for link aggregation groups ··········································································54
Enabling local-first load sharing for link aggregation················································································55
Configuring per-flow load sharing algorithm settings for Ethernet link aggregation ·································55
Enabling link-aggregation traffic redirection·····································································································56
Configuration restrictions and guidelines ·································································································56
Configuration procedure···························································································································57
Displaying and maintaining Ethernet link aggregation ·····················································································57
Ethernet link aggregation configuration examples ···························································································58
Layer 2 static aggregation configuration example····················································································58
Layer 2 dynamic aggregation configuration example···············································································59
iii
Layer 2 aggregation load sharing configuration example ········································································61
Layer 2 edge aggregate interface configuration example ········································································64
Layer 3 static aggregation configuration example····················································································65
Layer 3 dynamic aggregation configuration example···············································································66
Layer 3 edge aggregate interface configuration example ········································································67
Configuring port isolation ·············································································· 70
Assigning a port to an isolation group··············································································································70
Displaying and maintaining port isolation·········································································································70
Port isolation configuration example ················································································································71
Network requirements ······························································································································71
Configuration procedure···························································································································71
Verifying the configuration························································································································71
Configuring spanning tree protocols ····························································· 73
STP ··································································································································································73
STP protocol packets ·······························································································································73
Basic concepts in STP ·····························································································································73
Calculation process of the STP algorithm ································································································74
RSTP ·······························································································································································80
PVST································································································································································80
MSTP ·······························································································································································80
MSTP features ·········································································································································81
MSTP basic concepts ······························································································································81
How MSTP works·····································································································································84
MSTP implementation on devices············································································································85
Protocols and standards ··································································································································85
Spanning tree configuration task lists ··············································································································85
STP configuration task list························································································································86
RSTP configuration task list ·····················································································································87
PVST configuration task list ·····················································································································87
MSTP configuration task list·····················································································································88
Setting the spanning tree mode ·······················································································································89
Configuring an MST region ······························································································································89
Configuring the root bridge or a secondary root bridge ···················································································90
Configuring the current device as the root bridge of a specific spanning tree ·········································91
Configuring the current device as a secondary root bridge of a specific spanning tree···························91
Configuring the device priority ·························································································································91
Configuring the maximum hops of an MST region···························································································92
Configuring the network diameter of a switched network ················································································92
Configuring spanning tree timers ·····················································································································93
Configuration restrictions and guidelines ·································································································93
Configuration procedure···························································································································93
Configuring the timeout factor··························································································································94
Configuring the BPDU transmission rate ·········································································································94
Configuring edge ports·····································································································································95
Configuration restrictions and guidelines ·································································································95
Configuration procedure···························································································································95
Configuring path costs of ports ························································································································95
Specifying a standard for the device to use when it calculates the default path cost ······························96
Configuring path costs of ports ················································································································98
Configuration example ·····························································································································98
Configuring the port priority······························································································································99
Configuring the port link type ···························································································································99
Configuration restrictions and guidelines ·································································································99
Configuration procedure·························································································································100
Configuring the mode a port uses to recognize and send MSTP packets ·····················································100
Enabling outputting port state transition information······················································································101
Enabling the spanning tree feature ················································································································101
Enabling the spanning tree feature in STP/RSTP/MSTP mode·····························································101
Enabling the spanning tree feature in PVST mode ················································································102
Performing mCheck ·······································································································································102
iv
Configuration restrictions and guidelines ·······························································································102
Configuration procedure·························································································································102
Configuring Digest Snooping ·························································································································103
Configuration restrictions and guidelines ·······························································································103
Configuration procedure·························································································································104
Digest Snooping configuration example·································································································104
Configuring No Agreement Check ·················································································································105
Configuration prerequisites ····················································································································106
Configuration procedure·························································································································106
No Agreement Check configuration example·························································································107
Configuring TC Snooping·······························································································································107
Configuration restrictions and guidelines ·······························································································108
Configuration procedure·························································································································108
Configuring protection functions ····················································································································108
Enabling BPDU guard ····························································································································108
Enabling root guard································································································································109
Enabling loop guard ·······························································································································110
Configuring port role restriction ··············································································································110
Configuring TC-BPDU transmission restriction ······················································································111
Enabling TC-BPDU guard ······················································································································111
Enabling BPDU drop ······························································································································112
Displaying and maintaining the spanning tree ·······························································································112
Spanning tree configuration example ············································································································113
MSTP configuration example ·················································································································113
PVST configuration example··················································································································116
Configuring loop detection ·········································································· 120
Overview ························································································································································120
Loop detection mechanism ····················································································································120
Loop detection interval ···························································································································121
Loop protection actions ··························································································································121
Port status auto recovery ·······················································································································121
Loop detection configuration task list·············································································································122
Enabling loop detection··································································································································122
Enabling loop detection globally·············································································································122
Enabling loop detection on a port···········································································································122
Configuring the loop protection action ···········································································································123
Configuring the global loop protection action ·························································································123
Configuring the loop protection action on a Layer 2 Ethernet interface ·················································123
Configuring the loop protection action on a Layer 2 aggregate interface···············································123
Setting the loop detection interval··················································································································123
Displaying and maintaining loop detection·····································································································124
Loop detection configuration example ···········································································································124
Network requirements ····························································································································124
Configuration procedure·························································································································124
Verifying the configuration······················································································································125
Configuring VLANs ····················································································· 127
Overview ························································································································································127
VLAN frame encapsulation ····················································································································127
Protocols and standards ························································································································128
Configuring basic VLAN settings ···················································································································128
Configuring basic settings of a VLAN interface······························································································129
Configuring port-based VLANs ······················································································································130
Introduction ············································································································································130
Assigning an access port to a VLAN······································································································131
Assigning a trunk port to a VLAN ···········································································································132
Assigning a hybrid port to a VLAN ·········································································································132
Configuring MAC-based VLANs ····················································································································133
Introduction ············································································································································133
Configuration restrictions and guidelines ·······························································································136
Configuring static MAC-based VLAN assignment··················································································136
v
Configuring dynamic MAC-based VLAN assignment·············································································137
Configuring server-assigned MAC-based VLAN····················································································137
Configuring IP subnet-based VLANs ·············································································································138
Configuring protocol-based VLANs················································································································139
Configuring a VLAN group ·····························································································································140
Displaying and maintaining VLANs ················································································································141
VLAN configuration examples························································································································141
Port-based VLAN configuration example ·······························································································141
MAC-based VLAN configuration example······························································································143
IP subnet-based VLAN configuration example ······················································································145
Protocol-based VLAN configuration example ························································································146
Configuring super VLANs ··········································································· 150
Super VLAN configuration task list ················································································································150
Creating a sub-VLAN ·····································································································································150
Configuring a super VLAN ·····························································································································150
Configuring a super VLAN interface ··············································································································151
Displaying and maintaining super VLANs ······································································································151
Super VLAN configuration example ···············································································································152
Network requirements ····························································································································152
Configuration procedure·························································································································152
Verifying the configuration······················································································································153
Configuring the private VLAN ····································································· 155
Configuration task list·····································································································································155
Configuration restrictions and guidelines ·······································································································156
Configuration procedure ································································································································156
Displaying and maintaining the private VLAN································································································158
Private VLAN configuration examples ···········································································································158
Promiscuous port configuration example ·······························································································158
Trunk promiscuous port configuration example ·····················································································161
Trunk promiscuous and trunk secondary port configuration example····················································164
Secondary VLAN Layer 3 communication configuration example ·························································169
Configuring voice VLANs ············································································ 172
Overview ························································································································································172
Methods of identifying IP phones···················································································································172
Identifying IP phones through OUI addresses ·······················································································172
Automatically identifying IP phones through LLDP ················································································173
Advertising the voice VLAN information to IP phones ···················································································173
IP phone access methods······························································································································174
Connecting the host and the IP phone in series ····················································································174
Connecting the IP phone to the device ··································································································174
Configuring a voice VLAN on a port···············································································································174
Voice VLAN assignment modes·············································································································174
Security mode and normal mode of voice VLANs··················································································176
Configuration prerequisites ····················································································································177
Configuring the QoS priority settings for voice traffic ·············································································177
Configuring a port to operate in automatic voice VLAN assignment mode············································178
Configuring a port to operate in manual voice VLAN assignment mode················································179
Enabling LLDP for automatic IP phone discovery··························································································180
Configuration prerequisites ····················································································································180
Configuration restrictions and guidelines ·······························································································180
Configuration procedure·························································································································180
Configuring LLDP or CDP to advertise a voice VLAN ···················································································180
Dynamically advertising an authorization VLAN through LLDP or CDP ························································181
Displaying and maintaining voice VLANs ······································································································182
Voice VLAN configuration examples··············································································································182
Automatic voice VLAN assignment mode configuration example··························································182
Manual voice VLAN assignment mode configuration example ······························································184
vi
Configuring MVRP ······················································································ 186
MRP ·······························································································································································186
MRP implementation······························································································································186
MRP messages······································································································································186
MRP timers ············································································································································188
MVRP registration modes ······························································································································189
Protocols and standards ································································································································189
MVRP configuration task list ··························································································································189
Configuration restrictions and guidelines ·······································································································189
Configuration prerequisites ····························································································································190
Enabling MVRP··············································································································································190
Setting an MVRP registration mode···············································································································191
Setting MRP timers ········································································································································191
Enabling GVRP compatibility ·························································································································192
Displaying and maintaining MVRP·················································································································192
MVRP configuration example ························································································································192
Network requirements ····························································································································192
Configuration procedure·························································································································193
Verifying the configuration······················································································································196
Configuring QinQ ························································································ 203
Overview ························································································································································203
How QinQ works ····································································································································203
QinQ implementations····························································································································204
Protocols and standards ························································································································204
Restrictions and guidelines ····························································································································205
Enabling QinQ················································································································································205
Configuring transparent transmission for VLANs···························································································205
Configuring the TPID in VLAN tags ···············································································································206
Configuring the CVLAN TPID·················································································································207
Configuring the SVLAN TPID·················································································································207
Setting the 802.1p priority in SVLAN tags······································································································207
Displaying and maintaining QinQ···················································································································208
QinQ configuration examples·························································································································209
Basic QinQ configuration example·········································································································209
VLAN transparent transmission configuration example ·········································································211
Configuring VLAN mapping ········································································ 213
Overview ························································································································································213
Application scenario of one-to-one and many-to-one VLAN mapping ···················································213
Application scenario of one-to-two and two-to-two VLAN mapping ·······················································215
VLAN mapping implementations············································································································215
General configuration restrictions and guidelines ··························································································218
VLAN mapping configuration task list ············································································································218
Configuring one-to-one VLAN mapping ·········································································································219
Configuring many-to-one VLAN mapping ······································································································219
Configuring many-to-one VLAN mapping in a network with dynamic IP address assignment···············220
Configuring many-to-one VLAN mapping in a network with static IP address assignment····················222
Configuring one-to-two VLAN mapping ·········································································································224
Configuring two-to-two VLAN mapping··········································································································224
Displaying and maintaining VLAN mapping ···································································································225
VLAN mapping configuration examples·········································································································225
One-to-one and many-to-one VLAN mapping configuration example ···················································225
One-to-two and two-to-two VLAN mapping configuration example ·······················································230
Configuring LLDP························································································ 233
Overview ························································································································································233
Basic concepts ·······································································································································233
Working mechanism·······························································································································238
Protocols and standards ························································································································239
LLDP configuration task list ···························································································································239
vii
Performing basic LLDP configurations···········································································································239
Enabling LLDP ·······································································································································239
Configuring the LLDP bridge mode········································································································240
Setting the LLDP operating mode ··········································································································241
Setting the LLDP reinitialization delay····································································································241
Enabling LLDP polling····························································································································241
Configuring the advertisable TLVs ·········································································································242
Configuring the management address and its encoding format·····························································244
Setting other LLDP parameters··············································································································245
Setting an encapsulation format for LLDP frames ·················································································245
Configuring CDP compatibility ·······················································································································246
Configuration prerequisites ····················································································································247
Configuration procedure·························································································································247
Configuring LLDP trapping and LLDP-MED trapping ····················································································247
Displaying and maintaining LLDP ··················································································································248
LLDP configuration examples ························································································································249
Basic LLDP configuration example ········································································································249
CDP-compatible LLDP configuration example·······················································································253
Configuring service loopback groups·························································· 255
Configuration procedure ································································································································255
Displaying and maintaining service loopback groups ····················································································255
Service loopback group configuration example ·····························································································256
Network requirements ····························································································································256
Configuration procedure·························································································································256
Document conventions and icons ······························································· 257
Conventions ···················································································································································257
Network topology icons··································································································································258
Support and other resources ······································································ 259
Accessing Hewlett Packard Enterprise Support ····························································································259
Accessing updates·········································································································································259
Websites ················································································································································260
Customer self repair·······························································································································260
Remote support······································································································································260
Documentation feedback ·······················································································································260
Index ··········································································································· 262
1
Configuring Ethernet interfaces
The switch series supports Ethernet interfaces, management Ethernet interfaces, Console
interfaces, and USB 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, or connect it to a remote NMS for remote system
management.
Support for management Ethernet interfaces depends on the device model. For more information,
see the installation guide.
To configure a management Ethernet interface:
Step 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
The Ethernet interfaces are named in the format of interface type A/B/C. The letters that follow the
interface type represent the following elements:
•A—IRF member ID. If the switch is not in an IRF fabric, A is 1 by default.
•B—Card slot number. 0indicates the interface is a fixed interface of the switch. 1indicates the
interface is on expansion interface-card 1. 2indicates the interface is on expansion
interface-card 2.
•C—Port index.
A 10-GE breakout interface split from a 40-GE interface is named in the format of interface type
A/B/C:D. A/B/C is the interface number of the 40-GE interface and D is the number of the 10-GE
interface, which is in the range of 1 to 4. For information about splitting a 40-GE interface, see
"Splitting a 40-GE interface and combining 10-GE breakout interfaces."
Configuring common Ethernet interface settings
This section describes the settings common to Layer 2 and Layer 3 Ethernet interfaces. You can set
an Ethernet interface 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 and Layer 3 Ethernet interfaces, see "Configuring a Layer 2 Ethernet
interface" and "Configuring a Layer 3 Ethernet interface."
2
Configuring a combo interface (only applicable to HPE 5510
24G SFP 4SFP+ HI 1-slot Switch (JH149A) switches)
A combo interface is a logical interface that physically contains one fiber combo port and one copper
combo port. The two ports share one forwarding channel and one interface view. As a result, they
cannot work simultaneously. When you activate one port, the other port is automatically disabled. In
the interface view, you can activate the fiber or copper combo port, and configure other port
attributes such as the interface rate and duplex mode.
For more information about the number of combo interfaces, see the installation guide.
Configuration prerequisites
Use the display interface command to determine which port (fiber or copper) of each combo
interface is active:
•If the copper port is active, the output includes "Media type is twisted pair."
•If the fiber port is active, the output does not include this information.
Also, you can use the display this command in the view of each combo interface to display the
combo interface configuration:
•If the fiber port is active, the combo enable fiber command exists in the output.
•If the copper port is active, the combo enable fiber command does not exist in the output.
Changing the active port of a combo 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. Activate the copper
combo port or fiber
combo port. combo enable { copper | fiber } By default, the copper combo
port is active.
Splitting a 40-GE interface and combining 10-GE breakout
interfaces
Splitting a 40-GE QSFP+ interface into four 10-GE breakout interfaces
You can use a 40-GE QSFP+ interface as a single interface. To improve port density, reduce costs,
and improve network flexibility, you can also split a 40-GE QSFP+ interface into four 10-GE breakout
interfaces.
After the using tengige command is successfully configured, reboot your device as needed. For
more information, see Layer 2—LAN Switching Command Reference.
A 40-GE interface split into four 10-GE breakout interfaces must use a dedicated 1-to-4 cable. For
more information about the cable, see the installation guides.
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
Step Command Remarks
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 in a different
way.
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.
After the using fortygige command is successfully configured, reboot your device as needed. For
more information, see Layer 2—LAN Switching Command Reference.
After you combine the four 10-GE breakout interfaces, replace the dedicated 1-to-4 cable with a
dedicated 1-to-1 cable or a 40-GE transceiver module. For more information about the cable or
transceiver module, see the installation guides.
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.
Configuring basic settings 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. Set the interface
description. description text
The default setting is in the format of
interface-name Interface. For example,
GigabitEthernet1/0/1 Interface.
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 or
10 Gbps and fiber ports do not support the
half keyword.
5. Set the port speed. speed { 10 | 100 |1000 |10000
|40000 | auto }
The default setting is auto for Ethernet
interfaces.
Support for the keywords depends on the
interface type. For more information, see
Layer 2—LAN Switching Command
4
Step Command Remarks
Reference.
Interfaces on an HPE 5130/5510 10GbE
SFP+ 2-port Module (JH157A) or HPE
5130/5510 10GBASE-T 2-port Module
(JH156A) interface card support only the
10000 keyword.
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:
After you change the link mode of an Ethernet interface, all commands (except the shutdown and
combo enable commands) on the Ethernet interface are restored to their defaults in the new link
mode.
The interfaces on this switch series 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, Ethernet interfaces
operate 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.
The interface processes jumbo frames in the following ways:
•When the Ethernet interface is configured to deny jumbo frames (by using the undo
jumboframe enable command), the Ethernet interface discards jumbo frames without further
processing.
•When the Ethernet interface is configured with jumbo frame support, the Ethernet interface
performs the following operations:
{Processes jumbo frames within the specified length.
{Discards jumbo frames exceeding the specified length without further processing.
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 10000 bytes to pass
through all Ethernet interfaces.
Configuring physical state change suppression on an
Ethernet interface
IMPORTANT:
Do not configure physical state change suppression on an Ethernet interface that has RRPP, MSTP,
or Smart Link enabled.
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 operations:
•Notifies the upper-layer protocol modules (such as routing and forwarding modules) of the
change for guiding packet forwarding.
•Automatically generates traps and logs, informing 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.
When the link-delay delay-time command is configured:
•The link-down event is not reported to the CPU unless the interface is still down when the
suppression interval (delay-time) expires.
•The link-up event is immediately reported.
When the link-delay delay-time mode up command is configured:
•The link-up event is not reported to the CPU unless the interface is still up when the
suppression interval (delay-time) expires.
•The link-down event is immediately reported.
When the link-delay delay-time mode updown command is configured:
•The link-down event is not reported to the CPU unless the interface is still down when the
suppression interval (delay-time) expires.
•The link-up event is not reported to the CPU unless the interface is still up when the
suppression interval (delay-time) 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. Configure physical
state change
suppression on the
link-delay [ msec ]
delay-time [ mode { up |
updown }]
By default, the link-down or link-up event is
immediately reported to the CPU.
6
Step Command Remarks
interface. If you configure this command multiple times on
an Ethernet interface, the most recent
configuration takes effect.
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 the Ethernet interface.
•External loopback test—Tests the hardware of the Ethernet interface. To perform an external
loopback test on the 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 Ethernet interface (displayed as in ADM or Administratively
DOWN state), you cannot perform an internal or external loopback test.
•The speed, duplex, mdix-mode, 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
3. Perform a loopback test. loopback { external | internal } By default, no loopback test is
performed.
Configuring generic flow control on an Ethernet interface
CAUTION:
Configuring generic flow control on an Ethernet interface will cause link-up and link-down events
before the interface finally stays up.
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,
7
it suspends sending packets to the peer. When congestion occurs, the interface cannot send
flow control frames to the peer.
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
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.
Enabling energy saving features on an Ethernet interface
Enabling auto power-down on an Ethernet interface
IMPORTANT:
Fiber ports do not support this feature.
When the auto power-down feature is enabled on an interface and the interface has been down for a
certain period of time, both of the following events occur:
•The switch automatically stops supplying power to the interface.
•The interface enters the power save mode.
The time period depends on the chip specifications and is not configurable.
When the interface comes up, both of the following events occur:
•The switch automatically restores power supply to the interface.
•The interface enters its normal state.
To enable auto power-down 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 auto power-down. port auto-power-down By default, auto power-down is
disabled.
Enabling EEE energy saving for Ethernet interfaces in up state
IMPORTANT:
Fiber ports do not support this feature.
8
With the Energy Efficient Ethernet (EEE) energy saving feature, a link-up port enters the low power
state if it has not received any packet for a certain period of time. The time period depends on the
chip specifications and is not configurable. When a packet arrives later, the switch automatically
restores power supply to the interface and the port enters the normal state.
To enable EEE energy saving:
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 EEE energy
saving. eee enable By default, EEE energy
saving is disabled.
Setting the statistics polling interval
To set the statistics polling interval in Ethernet interface view:
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 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.
Configuring the interface card operating mode
IMPORTANT:
This feature is applicable only to HPE 5510 48G 4SFP+ HI 1-slot Switch (JH146A) and HPE 5510
48G PoE+ 4SFP+ HI 1-slot Switch (JH148A).
An interface card can operate in one of the following operating modes:
•0—All interfaces on the interface card are not available, and interfaces GigabitEthernet 1/0/41
through GigabitEthernet 1/0/48 on the front panel are available.
•1—Interfaces numbered 5 through 8 on the interface card are not available, and the following
interfaces are available:
{Interfaces numbered 1 through 4 on the interface card.
{Interfaces GigabitEthernet 1/0/41 through GigabitEthernet 1/0/48 on the front panel.
•2—Interfaces GigabitEthernet 1/0/41 through GigabitEthernet 1/0/48 on the front panel are not
available, and all interfaces on the interface card are available.
For HPE 5510 48G 4SFP+ HI 1-slot Switch and HPE 5510 48G PoE+ 4SFP+ HI 1-slot Switch, the
operating modes supported by the interface cards are as shown in Table 1.
9
Table 1 Operating modes supported by interface cards
Interface card Supported operating modes Remarks
HPE 5510 2-port QSFP+
Module (JH155A) 0and 2.
The operating modes take
effect only on 10-GE
breakout interfaces split from
a QSFP+ interface.
After you configure the interface card operating mode, reboot the switch to make the configuration
take effect.
You can view the interface card operating mode information by using the display
port-configuration-mode status command.
To configure the interface card operating mode:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the interface
card operating mode. port-configuration-mode slot
slot-number { 0| 1| 2} By default, the operating mode of the
interface card is 0.
Enabling automatic negotiation for speed downgrading
Perform this task to enable interfaces at two ends of a link to automatically negotiate about
downgrading their speed when the following conditions exist:
•The interfaces automatically negotiate a speed of 1000 Mbps.
•The interfaces cannot operate at 1000 Mbps because of link restrictions.
This command is applicable only to GE interfaces.
To enable automatic negotiation for speed downgrading:
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 automatic
negotiation for speed
downgrading. speed auto downgrade By default, automatic negotiation
for speed downgrading is
enabled.
Configuring a Layer 2 Ethernet interface
Configuring storm suppression
You can use the storm suppression feature 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
10
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."
When you configure the suppression threshold in kbps, the actual suppression threshold might be
different from the configured one as follows:
•If the configured value is smaller than 64, the value of 64 takes effect.
•If the configured value is greater than 64 but not an integer multiple of 64, the integer multiple of
64 that is greater than and closest to the configured value takes effect.
For the suppression threshold that takes effect, see the prompt on the switch.
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
IMPORTANT:
The known unicast storm control feature is available in Release 1121 and later.
Storm control compares broadcast, multicast, unknown unicast traffic, and known 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:
•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:
11
•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.
•Goes down automatically—The interface goes 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 feature.
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:
Step 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 |
known-unicast |multicast |
unicast }{pps |kbps |ratio }
max-pps-values min-pps-values
By default, storm control is
disabled.
The known-unicast key word is
available in Release 1121 and
later.
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.
7. (Optional.) Enable the
interface to send storm
control threshold event
traps.
storm-constrain enable trap
By default, the interface sends
traps when monitored traffic
exceeds the upper threshold or
drops below the lower threshold
from the upper threshold.
Other manuals for FlexNetwork 5510 HI Series
12
Table of contents
Other HPE Switch manuals
HPE
HPE OfficeConnect 1820 Series User manual
HPE
HPE FlexFabric 5700 Series User manual
HPE
HPE 3100 v2 Series User manual
HPE
HPE FlexFabric 5710 Series User manual
HPE
HPE Aruba 3810M Assembly instructions
HPE
HPE Aruba 3810 User manual
HPE
HPE OfficeConnect 1850 Series User manual
HPE
HPE FlexFabric 5940 SERIES User manual
HPE
HPE OfficeConnect 1420 Series User manual
HPE
HPE Aruba 2930F User manual
HPE
HPE FlexFabric 5950 Series User manual
HPE
HPE FlexFabric 5950 Series Installation manual
HPE
HPE FlexFabric 7900 Series Installation manual
HPE
HPE 5820X Series User manual
HPE
HPE FlexNetwork 7500 Series User manual
HPE
HPE FlexNetwork 5130 EI Series Installation manual
HPE
HPE FlexNetwork 7500 Series Installation manual
HPE
HPE FlexNetwork 7500 Series Installation manual
HPE
HPE StoreOnce 3100 User manual
HPE
HPE FlexNetwork 10500 SERIES Installation manual
