How it Works
HP
Loading...
F
Loading...
Loading...
FlexFabric 5940
ACL and QoS Command Reference
135 pgs675.07 Kb0
Configuration Manual
45 pgs607.23 Kb0
Fundamentals Command Reference
283 pgs904.31 Kb0
Fundamentals Configuration Guide
196 pgs1.41 Mb0
Installation Manual
85 pgs15.69 Mb0
Security Configuration Manual
517 pgs5.57 Mb0
VXLAN Configuration Guide
92 pgs1.08 Mb0
Table of contents
Loading...

HP FlexFabric 5940 Layer 2—LAN Switching Configuration Guide

HPE FlexFabric 5940 Switch Series
Layer 2—LAN Switching Configuration Guide
Part number: 5200-1018b Software version: Release 25xx Document version: 6W102-20170830
© Copyright 2017 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 acco mpanying such products and services. Nothing herein should be construe d as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions co ntained herein.
Confidential computer software. V alid 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 T e chnical 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® and Acrobat® are trademarks of Adobe Systems In corporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX® is a registered trademark of The Open Group.

Contents

Configuring Ethernet interfaces ··························································· 1
Ethernet interface naming conventions ··························································································· 1 Configuring a management Ethernet interface ·················································································· 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 or subinterface ················································· 3 Configuring the link mode of an Ethernet interface ······································································ 4 Configuring jumbo frame support ···························································································· 5 Configuring physical state change suppression on an Ethernet interface ········································· 5 Enabling loopback testing on an Ethernet interface ····································································· 6 Configuring generic flow control on an Ethernet interface ····························································· 7 Configuring PFC on an Ethernet interface ················································································· 7 Enabling energy saving features on an Ethernet interface ···························································· 8 Setting the statistics polling interval ························································································· 9 Configuring storm suppression ····························································································· 10
Configuring a Layer 2 Ethernet interface ······················································································· 11
Configuring storm control on an Ethernet interface ··································································· 11 Forcibly bringing up a fiber port ···························································································· 12 Setting the MDIX mode of an Ethernet interface ······································································· 14 Testing the cable connection of an Ethernet interface ································································ 14 Enabling bridging on an Ethernet interface ·············································································· 15 Setting the interface connection distance ················································································ 15
Configuring a Layer 3 Ethernet interface or subinterface··································································· 16
Setting the MTU for an Ethernet interface or subinterface ·························································· 16 Setting the MAC address of an Ethernet interface or subinterface ················································ 16
Displaying and maintaining an Ethernet interface or subinterface ······················································· 16
Configuring loopback, null, and inloopback interfaces ···························· 18
Configuring a loopback interface ································································································· 18 Configuring a null interface ········································································································· 18 Configuring an inloopback interface ····························································································· 19 Displaying and maintaining loopback, null, and inloopback interfaces ·················································· 19
Bulk configuring interfaces ······························································· 20
Configuration restrictions and guidelines ······················································································· 20 Configuration procedure ············································································································ 20 Displaying and maintaining bulk interface configuration ···································································· 21
Configuring the MAC address table ···················································· 22
Overview ································································································································ 22
How a MAC address entry is created ····················································································· 22
Types of MAC address entries ····························································································· 22 MAC address table configuration task list ······················································································ 23 Configuring MAC address entries ································································································ 24
Configuration guidelines ····································································································· 24
Adding or modifying a static or dynamic MAC address entry globally ············································ 24
Adding or modifying a static or dynamic MAC address entry on an interface ·································· 25
Adding or modifying a blackhole MAC address entry ································································· 25
Adding or modifying a multiport unicast MAC address entry ························································ 25 Disabling MAC address learning ································································································· 26
Disabling global MAC address learning ·················································································· 27
Disabling MAC address learning on interfaces ········································································· 27
Disabling MAC address learning on a VLAN ············································································ 27 Setting the aging timer for dynamic MAC address entries ································································· 28 Setting the MAC learning limit ····································································································· 28 Configuring the unknown frame forwarding rule after the MAC learning limit is reached ·························· 29 Assigning MAC learning priority to interfaces ················································································· 29
i
Enabling MAC address synchronization ························································································ 30 Configuring MAC address move notifications and suppression ·························································· 31 Enabling ARP fast update for MAC address moves ········································································· 32 Disabling static source check ······································································································ 33 Enabling conversational remote MAC learning ··············································································· 34 Enabling SNMP notifications for the MAC address table ··································································· 34 Displaying and maintaining the MAC address table ········································································· 35 MAC address table configuration example ····················································································· 35
Network requirements ········································································································ 35
Configuration procedure ····································································································· 36
Verifying the configuration ··································································································· 36
Configuring MAC Information ···························································· 37
Enabling MAC Information ········································································································· 37 Configuring the MAC Information mode ························································································ 37 Setting the MAC change notification interval ·················································································· 38 Setting the MAC Information queue length ···················································································· 38 MAC Information configuration example ························································································ 38
Network requirements ········································································································ 38
Configuration restrictions and guidelines ················································································ 38
Configuration procedure ····································································································· 39
Configuring Ethernet link aggregation ················································· 41
Basic concepts ························································································································ 41
Aggregation group, member port, and aggregate interface ························································· 41
Aggregation states of member ports in an aggregation group ······················································ 41
Operational key ················································································································· 42
Configuration types ············································································································ 42
Link aggregation modes ······································································································ 43 Aggregating links in static mode ·································································································· 43
Choosing a reference port ··································································································· 43
Setting the aggregation state of each member port ··································································· 43 Aggregating links in dynamic mode ······························································································ 44
LACP ······························································································································ 45
How dynamic link aggregation works ····················································································· 46 Edge aggregate interface ··········································································································· 48 Load sharing modes for link aggregation groups ············································································· 48 Ethernet link aggregation configuration task list ·············································································· 48 Configuring an aggregation group ································································································ 49
Configuration restrictions and guidelines ················································································ 49
Configuring a Layer 2 aggregation group ················································································ 49
Configuring a Layer 3 aggregation group ················································································ 51 Configuring an aggregate interface ······························································································ 52
Configuring the description of an aggregate interface ································································ 52
Setting the MAC address for an aggregate interface ································································· 53
Specifying ignored VLANs for a Layer 2 aggregate interface ······················································· 53
Setting the MTU for a Layer 3 aggregate interface ···································································· 54
Setting the minimum and maximum numbers of Selected ports for an aggregation group ················· 54
Setting the expected bandwidth for an aggregate interface ························································· 55
Configuring an edge aggregate interface ················································································ 55
Enabling BFD for an aggregation group·················································································· 56
Shutting down an aggregate interface ···················································································· 57
Restoring the default settings for an aggregate interface ···························································· 57 Configuring load sharing for link aggregation groups ······································································· 58
Setting load sharing modes for link aggregation groups ····························································· 58
Enabling local-first load sharing for link aggregation ·································································· 59
Configuring link aggregation load sharing algorithm settings ······················································· 59
Setting the global load sharing mode for MAC-in-MAC traffic ······················································ 60 Enabling link-aggregation traffic redirection ··················································································· 60
Configuration restrictions and guidelines ················································································ 61
Configuration procedure ····································································································· 61 Forwarding the traffic of specified VLANs out of a fixed member port on an aggregate link ······················ 61
ii
Excluding a subnet from load sharing on aggregate links ·································································· 62 Displaying and maintaining Ethernet link aggregation ······································································ 63 Ethernet link aggregation configuration examples ··········································································· 64
Layer 2 static aggregation configuration example ····································································· 64
Layer 2 dynamic aggregation configuration example ································································· 66
Layer 2 aggregation load sharing configuration example ···························································· 68
Layer 2 edge aggregate interface configuration example ··························································· 70
Layer 3 static aggregation configuration example ····································································· 71
Layer 3 dynamic aggregation configuration example ································································· 73
Layer 3 aggregation load sharing configuration example ···························································· 74
Layer 3 edge aggregate interface configuration example ··························································· 76
Configuring port isolation ································································· 78
Assigning a port to an isolation group ··························································································· 78 Displaying and maintaining port isolation ······················································································· 78 Port isolation configuration example ····························································································· 79
Network requirements ········································································································ 79
Configuration procedure ····································································································· 79
Verifying the configuration ··································································································· 79
Configuring spanning tree protocols ··················································· 81
STP ······································································································································ 81
STP protocol frames ·········································································································· 81
Basic concepts in STP ········································································································ 83
Calculation process of the STP algorithm ··············································································· 84 RSTP ···································································································································· 90
RSTP protocol frames ········································································································ 90
Basic concepts in RSTP ····································································································· 91
How RSTP works ·············································································································· 91
RSTP BPDU processing ····································································································· 92 PVST ···································································································································· 92
PVST protocol frames ········································································································ 92
Basic concepts in PVST ······································································································ 93
How PVST works ·············································································································· 93 MSTP ···································································································································· 93
MSTP features ·················································································································· 93
MSTP protocol frames ········································································································ 94
MSTP basic concepts ········································································································· 95
How MSTP works ·············································································································· 98
MSTP implementation on devices ························································································· 99
Rapid transition mechanism ································································································· 99 Protocols and standards ·········································································································· 102 Spanning tree configuration task lists ························································································· 102
STP configuration task list ································································································· 103
RSTP configuration task list ······························································································· 103
PVST configuration task list ······························································································· 104
MSTP configuration task list ······························································································ 105 Setting the spanning tree mode ································································································· 106 Configuring an MST region ······································································································ 106 Configuring the root bridge or a secondary root bridge ··································································· 107
Configuring the device as the root bridge of a specific spanning tree ·········································· 107
Configuring the device as a secondary root bridge of a specific spanning tree ······························ 108 Configuring the device priority ··································································································· 108 Configuring the maximum hops of an MST region ········································································· 108 Configuring the network diameter of a switched network································································· 109 Setting spanning tree timers ····································································································· 109
Configuration restrictions and guidelines ·············································································· 110
Configuration procedure ··································································································· 110 Setting the timeout factor ········································································································· 111 Configuring the BPDU transmission rate ····················································································· 111 Configuring edge ports ············································································································ 112
Configuration restrictions and guidelines ·············································································· 112
iii
Configuration procedure ··································································································· 112 Configuring path costs of ports ·································································································· 112
Specifying a standard for the device to use when it calculates the default path cost ······················· 113
Configuring path costs of ports ··························································································· 115
Configuration example ······································································································ 115 Configuring the port priority ······································································································ 116 Configuring the port link type ···································································································· 116
Configuration restrictions and guidelines ·············································································· 116
Configuration procedure ··································································································· 117 Configuring the mode a port uses to recognize and send MSTP frames ············································· 117 Enabling outputting port state transition information ······································································· 118 Enabling the spanning tree feature ···························································································· 118
Enabling the spanning tree feature in STP/RSTP/MSTP mode ·················································· 118
Enabling the spanning tree feature in PVST mode ·································································· 119 Performing mCheck ················································································································ 119
Configuration restrictions and guidelines ·············································································· 119
Performing mCheck globally ······························································································ 119
Performing mCheck in interface view ··················································································· 120 Disabling inconsistent PVID protection ······················································································· 120 Configuring Digest Snooping ···································································································· 120
Configuration restrictions and guidelines ·············································································· 121
Configuration procedure ··································································································· 121
Digest Snooping configuration example ··············································································· 121 Configuring No Agreement Check ····························································································· 122
Configuration prerequisites ································································································ 123
Configuration procedure ··································································································· 124
No Agreement Check configuration example ········································································· 124 Configuring TC Snooping ········································································································· 124
Configuration restrictions and guidelines ·············································································· 125
Configuration procedure ··································································································· 125 Configuring protection features ································································································· 126
Configuring BPDU guard ··································································································· 126
Enabling root guard ········································································································· 127
Enabling loop guard ········································································································· 127
Configuring port role restriction ··························································································· 128
Configuring TC-BPDU transmission restriction ······································································· 128
Enabling TC-BPDU guard ································································································· 129
Enabling BPDU drop ········································································································ 129
Enabling PVST BPDU guard ······························································································ 130
About dispute guard ········································································································· 130 Enabling the device to log events of detecting or receiving TC BPDUs ·············································· 131 Enabling BPDU transparent transmission on a port ······································································· 131 Enabling SNMP notifications for new-root election and topology change events ·································· 132 Displaying and maintaining the spanning tree ·············································································· 132 Spanning tree configuration example ························································································· 133
MSTP configuration example ····························································································· 133
PVST configuration example ······························································································ 137
Configuring loop detection ······························································ 141
Overview ······························································································································ 141
Loop detection mechanism ································································································ 141
Loop detection interval ····································································································· 142
Loop protection actions ····································································································· 142
Port status auto recovery ·································································································· 142 Loop detection configuration task list ·························································································· 143 Enabling loop detection ··········································································································· 143
Enabling loop detection globally ························································································· 143
Enabling loop detection on a port ························································································ 143 Setting the loop protection action ······························································································· 144
Setting the global loop protection action ··············································································· 144
Setting the loop protection action on a Layer 2 Ethernet interface ·············································· 144
Setting the loop protection action on a Layer 2 aggregate interface ············································ 144
iv
Setting the loop detection interval ······························································································ 144 Displaying and maintaining loop detection ··················································································· 145 Loop detection configuration example ························································································ 145
Network requirements ······································································································ 145
Configuration procedure ··································································································· 145
Verifying the configuration ································································································· 146
Configuring VLANs ······································································· 148
Overview ······························································································································ 148
VLAN frame encapsulation ································································································ 148
Protocols and standards ··································································································· 149 Configuring a VLAN ················································································································ 149 Configuring VLAN interfaces ···································································································· 150 Configuring port-based VLANs ·································································································· 151
Introduction ···················································································································· 151
Assigning an access port to a VLAN ···················································································· 152
Assigning a trunk port to a VLAN ························································································ 153
Assigning a hybrid port to a VLAN ······················································································· 153 Configuring MAC-based VLANs ································································································ 154
Introduction ···················································································································· 154
General configuration restrictions and guidelines ···································································· 157
Configuring static MAC-based VLAN assignment ··································································· 157
Configuring dynamic MAC-based VLAN assignment ······························································· 157
Configuring server-assigned MAC-based VLAN ····································································· 159 Configuring IP subnet-based VLANs ·························································································· 159 Configuring protocol-based VLANs ···························································································· 160 Configuring a VLAN group ······································································································· 161 Displaying and maintaining VLANs ···························································································· 161 VLAN configuration examples ··································································································· 162
Port-based VLAN configuration example ·············································································· 162
MAC-based VLAN configuration example ············································································· 164
IP subnet-based VLAN configuration example ······································································· 166
Protocol-based VLAN configuration example ········································································· 167
Configuring super VLANs ······························································· 171
Super VLAN configuration task list ····························································································· 171 Creating a sub-VLAN ·············································································································· 171 Configuring a super VLAN ······································································································· 171 Configuring a super VLAN interface ··························································································· 172 Displaying and maintaining super VLANs ···················································································· 172 Super VLAN configuration example ··························································································· 173
Network requirements ······································································································ 173
Configuration procedure ··································································································· 173
Verifying the configuration ································································································· 174
Configuring the private VLAN ·························································· 176
Configuration task list·············································································································· 176 Configuration restrictions and guidelines ····················································································· 177 Configuration procedure ·········································································································· 177 Displaying and maintaining the private VLAN ··············································································· 179 Private VLAN configuration examples ························································································· 179
Promiscuous port configuration example ·············································································· 179
Trunk promiscuous port configuration example ······································································ 182
Trunk promiscuous and trunk secondary port configuration example ·········································· 185
Secondary VLAN Layer 3 communication configuration example ··············································· 189
Configuring voice VLANs ······························································· 192
Overview ······························································································································ 192 Methods of identifying IP phones ······························································································· 192
Identifying IP phones through OUI addresses ········································································ 192
Automatically identifying IP phones through LLDP ·································································· 193 Advertising the voice VLAN information to IP phones ····································································· 193
v
IP phone access methods ········································································································ 193
Connecting the host and the IP phone in series ····································································· 193
Connecting the IP phone to the device ················································································· 194 Voice VLAN assignment modes ································································································ 194
Automatic mode ·············································································································· 194
Manual mode ················································································································· 195
Cooperation of voice VLAN assignment modes and IP phones ················································· 195 Security mode and normal mode of voice VLANs ·········································································· 196 Voice VLAN configuration task list ····························································································· 196 Configuring the QoS priority settings for voice traffic ······································································ 197 Configuring a port to operate in automatic voice VLAN assignment mode ·········································· 198
Configuration restrictions and guidelines ·············································································· 198
Configuration procedure ··································································································· 198 Configuring a port to operate in manual voice VLAN assignment mode ············································· 199
Configuration restrictions and guidelines ·············································································· 199
Configuration procedure ··································································································· 199 Enabling LLDP for automatic IP phone discovery ·········································································· 200
Configuration restrictions and guidelines ·············································································· 200
Configuration procedure ··································································································· 200 Configuring LLDP to advertise a voice VLAN ··············································································· 200 Configuring CDP to advertise a voice VLAN ················································································ 201 Displaying and maintaining voice VLANs ···················································································· 202 Voice VLAN configuration examples ·························································································· 202
Automatic voice VLAN assignment mode configuration example ··············································· 202
Manual voice VLAN assignment mode configuration example ··················································· 204
Configuring MVRP ········································································ 206
MRP ··································································································································· 206
MRP implementation ········································································································ 206
MRP messages ·············································································································· 206
MRP timers ···················································································································· 208 MVRP registration modes ········································································································ 209 Protocols and standards ·········································································································· 209 MVRP configuration task list ····································································································· 209 Configuration restrictions and guidelines ····················································································· 209 Configuration prerequisites ······································································································ 210 Enabling MVRP ····················································································································· 210 Setting an MVRP registration mode ··························································································· 210 Setting MRP timers ················································································································ 211 Enabling GVRP compatibility ···································································································· 212 Displaying and maintaining MVRP ····························································································· 212 MVRP configuration example ··································································································· 212
Network requirements ······································································································ 212
Configuration procedure ··································································································· 213
Verifying the configuration ································································································· 216
Configuring QinQ ········································································· 223
Overview ······························································································································ 223
How QinQ works ············································································································· 223
QinQ implementations ······································································································ 224
Protocols and standards ··································································································· 225 Restrictions and guidelines ······································································································ 225 Enabling QinQ ······················································································································· 225 Configuring transparent transmission for VLANs ··········································································· 225 Configuring the TPID for VLAN tags ··························································································· 226
Configuring the TPID for CVLAN tags ·················································································· 227
Configuring the TPID for SVLAN tags ·················································································· 227 Setting the 802.1p priority in SVLAN tags ···················································································· 227 Displaying and maintaining QinQ ······························································································· 228 QinQ configuration examples ···································································································· 229
Basic QinQ configuration example ······················································································ 229
VLAN transparent transmission configuration example ···························································· 231
vi
Configuring VLAN mapping ···························································· 233
Overview ······························································································································ 233
VLAN mapping application scenarios ··················································································· 233
VLAN mapping implementations ························································································· 235 VLAN mapping configuration task list ························································································· 238 Configuring one-to-one VLAN mapping ······················································································· 238 Configuring many-to-one VLAN mapping ···················································································· 239
Configuring many-to-one VLAN mapping in a network with dynamic IP address assignment ··········· 239
Configuring many-to-one VLAN mapping in a network with static IP address assignment ················ 242 Configuring one-to-two VLAN mapping ······················································································· 244 Configuring two-to-two VLAN mapping ······················································································· 245 Displaying and maintaining VLAN mapping ················································································· 245 VLAN mapping configuration examples ······················································································ 245
One-to-one and many-to-one VLAN mapping configuration example ·········································· 245
One-to-two and two-to-two VLAN mapping configuration example ············································· 251
Configuring LLDP ········································································· 254
Overview ······························································································································ 254
Basic concepts ··············································································································· 254
Working mechanism ········································································································ 259
Protocols and standards ··································································································· 260 LLDP configuration task list ······································································································ 260 Performing basic LLDP configurations ························································································ 261
Enabling LLDP ················································································································ 261
Setting the LLDP bridge mode ··························································································· 261
Setting the LLDP operating mode ······················································································· 261
Setting the LLDP reinitialization delay ·················································································· 262
Enabling LLDP polling ······································································································ 262
Configuring the advertisable TLVs ······················································································ 263
Configuring the management address and its encoding format ·················································· 266
Setting other LLDP parameters ·························································································· 267
Setting an encapsulation format for LLDP frames ··································································· 268
Disabling LLDP PVID inconsistency check ············································································ 269 Configuring CDP compatibility ·································································································· 269
Configuration prerequisites ································································································ 270
Configuration procedure ··································································································· 270 Configuring LLDP trapping and LLDP-MED trapping······································································ 270 Displaying and maintaining LLDP ······························································································ 271 LLDP configuration examples ··································································································· 272
Basic LLDP configuration example ······················································································ 272
CDP-compatible LLDP configuration example ······································································· 276
Configuring L2PT ········································································· 278
Overview ······························································································································ 278
Background ···················································································································· 278
L2PT operating mechanism ······························································································· 279 L2PT configuration task list ······································································································ 280 Enabling L2PT ······················································································································ 280
Restrictions and guidelines ································································································ 280
Enabling L2PT for a protocol ······························································································ 280 Setting the destination multicast MAC address for tunneled packets ················································· 281 Displaying and maintaining L2PT ······························································································ 281 L2PT configuration examples ··································································································· 282
Configuring L2PT for STP ································································································· 282
Configuring L2PT for LACP ······························································································· 283
Configuring cut-through forwarding ·················································· 287
Configuring service loopback groups ················································ 288
Configuration procedure ·········································································································· 288 Displaying and maintaining service loopback groups ····································································· 289
vii
Service loopback group configuration example ············································································· 289
Network requirements ······································································································ 289
Configuration procedure ··································································································· 289
Document conventions and icons ···················································· 290
Conventions ························································································································· 290 Network topology icons ··········································································································· 291
Support and other resources ·························································· 292
Accessing Hewlett Packard Enterprise Support ············································································ 292 Accessing updates ················································································································· 292
Websites ······················································································································· 293
Customer self repair ········································································································· 293
Remote support ·············································································································· 293
Documentation feedback ·································································································· 293
Index ························································································· 295
viii

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 chapter describes how to configure management Ethernet interfaces and Ethernet interfaces.

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—Slot number. 0 indicates the interface is a fixed interface of the switch.
• 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 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.
To configure a management Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter management
Ethernet interface view.
3. (Optional.) Set the interface description.
4. (Optional.) Shut down
the interface.
system-view interface
M-GigabitEthernet
interface-number
description
shutdown
text
N/A
N/A
The default setting is
M-GigabitEthernet0/0/0 Interface
By default, the management Ethernet interface is up.
.

Configuring common Ethernet interface settings

This section describes the settings common to Layer 2 Ethernet interfaces, Layer 3 Ethernet interfaces, and Layer 3 Ethernet subinterfaces. For more information about the settings specific to Layer 2 Ethernet interfaces or subinterfaces, see "Configuring a Layer 2 Ethernet interface." For more info "Configuring a Layer 3 Ethernet inte
rmation about the settings specific to Layer 3 Ethernet interfaces or subinterfaces, see
rface or subinterface."
1

Splitting a 40-GE interface and combining 10-GE breakout interfaces

Configuration restrictions and guidelines
When you split a 40-GE interface and combine 10-GE breakout interfaces, follow these restrictions and guidelines:
• 40-GE interfaces FortyGigE 1/0/1 through FortyGigE 1/0/4 and FortyGigE 1/0/29 through
FortyGigE 1/0/32 on an HPE FlexFabric 5940 32QSFP+ Switch (JH396A) switch do not support one-to-four splitting.
• 100-GE interfaces on an HPE FlexFabric 5940 48SFP+ 6QSFP28 Switch (JH390A) or HPE
FlexFabric 5940 48XGT 6QSFP28 Switch (JH391A) switch do not support one-to-four splitting.
• When an LSWM124XGT2Q (JH182A), LSWM124XG2Q (JH181A), or LSWM124XG2QL
(JH180A) interface module is installed in an HPE FlexFabric 5940 4-slot Switch (JH398A) switch , 40-GE interfaces on these modules do not support one-to-four splitting.
• When an LSWM18QC (JH183A) interface module is installed in an HPE FlexFabric 5940 4-slot
Switch (JH398A) switch, the last two 40-GE interfaces on the module do not support one-to-four splitting.
Splitting a 40-GE interface into four 10-GE breakout interfaces
You can use a 40-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 40-GE interface into four 10-GE breakout interfaces.
For example, you can split 40-GE interface FortyGigE 1/0/1 into four 10-GE breakout interfaces Ten-GigabitEthernet 1/0/1:1 through Ten-GigabitEthernet 1/0/1:4.
After you configure this feature on a 40-GE interface, the system deletes the 40-GE interface and creates the four 10-GE breakout interfaces.
After the using tengige command is successfully configured, you do not need to reboot the switch. You can view the four 10-GE breakout interfaces by using the display interface brief command.
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.
2. Enter 40-GE interface view.
3. Split the 40-GE interface into
four 10-GE breakout interfaces.
system-view interface
interface-number
using tengige
interface-type
Combining four 10-GE breakout interfaces into a 40-GE interface
N/A
N/A
By default, a 40-GE interface is not split and operates as a single interface.
The 10-GE breakout interfaces support the same configuration and attributes as common 10-GE interfaces, except that they are numbered differently.
If you need higher bandwidth on a single interface, you can combine the four 10-GE breakout interfaces into a 40-GE interface.
After you configure this feature on a 10-GE breakout interface, the system deletes the four 10-GE breakout interfaces and creates the 40-GE interface.
2
After the using fortygige command is successfully configured, you do not need to reboot the switch. You can view the 40-GE interface by using the display interface brief command.
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.
2. Enter the view of any 10-GE
breakout interface.
3. Combine the four 10-GE
breakout interfaces into a 40-GE interface.
system-view interface
interface-number
using fortygige
interface-type
N/A
N/A
By default, a 10-GE breakout interface operates as a single interface.

Configuring basic settings of an Ethernet interface or subinterface

You can configure an Ethernet interface to operate in one of the following duplex modes:
• Full-duplex mode—The interface can send and receive packets simultaneously.
• Half-duplex mode—The interface can only send or receive packets at a given time.
• Autonegotiation mode—The interface negotiates a duplex mode with its peer.
You can set the speed of an Ethernet interface or enable it to automatically negotiate a speed with its peer.
Configuring an Ethernet interface
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Set the description for
the Ethernet interface.
4. Set the duplex mode for
the Ethernet interface.
5. Set the speed for the
Ethernet interface.
6. Set the expected
bandwidth for the Ethernet interface.
system-view interface
interface-number
description
duplex
speed { 10 | 100 | 1000 | 10000 | 40000 | 100000 | auto }
bandwidth
interface-type
text
auto
{
full
|
bandwidth-value
|
half
}
N/A
N/A
The default setting is interface-name
Interface Ten-GigabitEthernet1/0/1 Interface
By default, the duplex mode is Ethernet interfaces.
Copper ports operating at 1000 Mbps or 10 Gbps and fiber ports do not support the
half
The default setting is interfaces.
Support for the keywords depends on the interface type. For more information, use the
By default, the expected bandwidth (in kbps) is the interface baud rate divided by
1000.
. For example,
keyword.
speed ?
auto
for Ethernet
command in interface view.
auto
.
for
3
Step Command Remarks
7. Restore the default
settings for the Ethernet interface.
8. Bring up the Ethernet
interface.
default
undo shutdown
Configuring an Ethernet subinterface
Step Command Remarks
1. Enter system view.
2. Create an Ethernet
subinterface.
3. Set the description for the
Ethernet subinterface.
4. Restore the default settings
for the Ethernet subinterface.
system-view interface
interface-number.subnumber
description
default
interface-type
text
N/A
By default, Ethernet interfaces are in up state.
loopback, shutdown
The
up-mode
exclusive.
commands are mutually
N/A
N/A
The default setting is
interface-name
example,
Ten-GigabitEthernet1/0/1.1 Interface
N/A
Interface
.
,and
port
. For
5. Set the expected bandwidth
for the Ethernet subinterface.
6. Bring up the Ethernet
subinterface.
bandwidth
undo shutdown
bandwidth-value
By default, the expected bandwidth (in kbps) is the interface baud rate divided by
1000.
By default, Ethernet subinterfaces are in up state.
shutdown
The
up-mode
exclusive.
commands are mutually

Configuring the link mode of an Ethernet interface

CAUTION:
After you change the link mode of an Ethernet interface, all commands (except the shutdown
command) on the Ethernet interface are restored to their defaults in the new link mode.
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 configure the link mode of an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Configure the link mode of
the Ethernet interface.
system-view interface
interface-number
port link-mode
interface-type
bridge | route
{
N/A
N/A
By default, Ethernet interfaces
}
operate in bridge mode.
and
port
4

Configuring jumbo frame support

An Ethernet interface might receive frames larger than the standard Ethernet frame size during high-throughput data exchanges, such as file transfers. These frames are called jumbo frames.
The Ethernet interface processes jumbo frames in the following ways:
• When the Ethernet interface is configured to deny jumbo frames, the Ethernet interface
discards jumbo frames.
• 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 that exceed the specified length.
To configure jumbo frame support in interface view:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
system-view interface
interface-number
interface-type
N/A
N/A
3. Configure jumbo frame
support.
jumboframe enable
[ size ]
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 enable this feature on an interface that has RRPP, spanning tree protocols, or Smart Link enabled.
The physical link state of an Ethernet interface is either up or down. Each time the physical link of an interface 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 to inform users to take the correct actions.
To prevent frequent physical link flapping from affecting system performance, configure physical state change suppression. You can configure this feature to suppress only link-down events, only link-up events, or both. If an event of the specified type still exists when the suppression interval expires, the system reports the event.
When you configure this feature, follow these guidelines:
• To suppress only link-down events, configure the link-delay [ msec ] delay-time command.
• To suppress only link-up events, configure the link-delay [ msec ] delay-time mode up
command.
• To suppress both link-down and link-up events, configure the link-delay [ msec ] delay-time
mode updown command.
To configure physical state change suppression on an Ethernet interface:
5
Step Command Remarks
1. Enter system view.
2. Enter Ethernet
interface view.
3. Configure physical
state change suppression.
system-view interface
interface-number
link-delay
delay-time [
updown
interface-type
msec
[
mode
}]
]
{ up |
N/A
N/A
By default, the link-down or link-up event is immediately reported to the CPU.
If you configure this command multiple times on an Ethernet interface, the most recent configuration takes effect.

Enabling loopback testing on an Ethernet interface

CAUTION:
After you enable this feature on an Ethernet interface, the interface cannot forward data traffic correctly.
Perform this task to determine whether an Ethernet link works correctly.
Loopback testing includes the following types:
• Internal loopback testing—Tests the device where the Ethernet interface resides. The
Ethernet interface sends outgoing packets back to the local device. If the device fails to receive the packets, the device fails.
• External loopback testing—Tests the inter-device link. The Ethernet interface sends incoming
packets back to the remote device. If the remote device fails to receive the packets, the inter-device link fails.
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.
• A loopback test cannot be performed on an interface configured with the port up-mode
command.
• 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 enable loopback testing on an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Enable loopback testing.
system-view interface
interface-number
loopback
interface-type
external
{
|
internal
N/A
N/A
By default, no loopback test is
}
performed.
6

Configuring generic flow control on an Ethernet interface

To avoid dropping packets 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. Generic flow control includes the following types:
• TxRx-mode generic flow control—Enabled by using the flow-control command. 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 its peer, it suspends sending packets
to its peer.
• Rx-mode generic flow control—Enabled by using the flow-control receive enable
command. With Rx-mode generic flow control enabled, an interface can receive flow control frames, but it cannot send flow control frames:
{ When congestion occurs, the interface cannot send flow control frames to its peer.
{ When the interface receives a flow control frame from its peer, it suspends sending packets
to its 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.
2. Enter Ethernet interface
view.
3. Enable generic flow
control.
system-view interface
interface-number
• Enable TxRx-mode
• Enable Rx-mode generic
interface-type
generic flow control: flow-control
flow control: flow-control receive enable
N/A
N/A
By default, generic flow control is disabled on an Ethernet interface.

Configuring PFC on an Ethernet interface

When congestion occurs in the network, the local device notifies the peer to stop sending packets carrying the specified 802.1p priority if all of the following conditions exist:
• Both the local end and the remote end have PFC enabled.
• Both the local end and the remote end have the priority-flow-control no-drop dot1p
command configured.
• The specified 802.1p priority is in the 802.1p priority list specified by the dot1p-list argument.
• The local end receives a packet carrying the specified 802.1p priority.
The state of the PFC feature is determined by the PFC configuration on the local end and on the peer end. In Table 1:
• The first row l
ists the PFC configuration on the local interface.
• The first column lists the PFC configuration on the peer.
7
• The Enabled and Disabled fields in other cells are possible negotiation results.
Make sure all interfaces that a data flow passes through have the same PFC configuration.
Table 1 PFC configurations and negotiation results
Local (right)
enable auto Default
Peer (below) enable
auto
Default
Enabled Enabled. Disabled
Enabled
Disabled Disabled. Disabled
Configuration restrictions and guidelines
When you configure PFC, follow these restrictions and guidelines:
• For IRF and other protocols to operate correctly, as a best practice, do not enable PFC for
802.1p priorities 0, 6, and 7.
• To avoid packet loss, apply the same PFC configuration to all interfaces that the packets pass
through.
• If you do not enable PFC on an interface, the interface can receive but cannot process PFC
pause frames. To make PFC take effect, you must enable PFC on both ends.
• If you configure the flow control or flow-control receive enable command on a PFC-enabled
interface, the following rules apply:
{ The PFC configuration takes effect.
{ The configuration of the flow control or flow-control receive enable command is ignored. { The flow control or flow-control receive enable command takes effect on the interface
only when PFC is disabled on it.
• Enabled if negotiation succeeds.
• Disabled if negotiation fails.
Disabled
Configuration procedure
To configure PFC on an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Enable PFC in auto mode or
forcibly on the Ethernet interface.
4. Enable PFC for 802.1p
priorities.
system-view interface
interface-number
priority-flow-control { auto enable
priority-flow-control no-drop dot1p
interface-type
|
}
dot1p-list
N/A
N/A
By default, PFC is disabled.
By default, PFC is disabled for all
802.1p priorities.

Enabling energy saving features on an Ethernet interface

IMPORTANT:
Fiber ports do not support these features.
8
Enabling auto power-down on an Ethernet interface
When an Ethernet interface with auto power-down enabled has been down for a certain period of time, both of the following events occur:
• The device automatically stops supplying power to the Ethernet interface.
• The Ethernet interface enters the power save mode.
The time period depends on the chip specifications and is not configurable.
When the Ethernet interface comes up, both of the following events occur:
• The device automatically restores power supply to the Ethernet interface.
• The Ethernet interface restores to its normal state.
To enable auto power-down on an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface view.
3. Enable auto power-down on the Ethernet interface.
system-view interface
interface-number
port auto-power-down
interface-type
Enabling EEE on an Ethernet interface
N/A
N/A
By default, auto power-down is disabled on an Ethernet interface.
With Energy Efficient Ethernet (EEE) enabled, a link-up interface enters low power state if it has not received any packet for a period of time. The time period depends on the chip specifications and is not configurable. When a packet arrives later, the device automatically restores power supply to the interface and the interface restores to the normal state.
To enable EEE on an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Enable EEE on the
Ethernet interface.
system-view interface
interface-number
eee enable
interface-type

Setting the statistics polling interval

Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Set the statistics polling
interval for the Ethernet interface.
To display the interface statistics collected in the last statistics polling interval, use the display
interface command.
system-view interface
interface-number
flow-interval
interface-type
interval
N/A
N/A
By default, EEE is disabled on an Ethernet interface.
N/A
N/A
By default, the statistics polling interval is 300 seconds.
9

Configuring storm suppression

The storm suppression feature ensures that the size of a particular type of traffic (broadcast, multicast, or unknown unicast traffic) does not exceed the threshold 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.
Both storm suppression and storm control can suppress storms on an interface. Storm suppression uses the chip to suppress traffic. Storm suppression has less impact on the device performance than storm control, which uses software to suppress traffic.
Configuration restrictions and guidelines
When you configure storm suppression, follow these restrictions and guidelines:
• An interframe gap exists between each two continuous frames. The system excludes the time
of interframe gaps in monitoring the traffic size on the interface. The configured suppression thresholds must be less than the total traffic that passes through the interface.
• For the traffic suppression result to be determined, do not configure storm control together with
storm suppression for the same type of traffic. For more information about storm control, see "Configuring storm control on an Ethernet interface."
• Storm suppression configured on a Layer 3 Ethernet interface applies to the interface and its
subinterfaces if it is on a boarder gateway of the following networks:
{ VXLAN IP gateway network.
{ EVPN gateway network.
For more information about VXLAN IP gateway and EVPN gateway networks, see VXLAN Configuration Guide and EVPN Configuration Guide.
• 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 device.
Configuration procedure
To set storm suppression thresholds on an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Enable broadcast
suppression and set the broadcast suppression threshold.
4. Enable multicast
suppression and set the multicast suppression threshold.
5. Enable unknown unicast
suppression and set the unknown unicast suppression threshold.
system-view interface
interface-number
broadcast-suppression pps
multicast-suppression pps
unknown
[
unicast-suppression
max-pps |
interface-type
max-pps |
max-pps |
]
kbps
10
kbps
max-kbps }
kbps
max-kbps }
{ ratio |
max-kbps }
{ ratio |
{ ratio |
pps
N/A
N/A
By default, broadcast suppression is disabled.
By default, multicast suppression is disabled.
By default, unknown unicast suppression is disabled.

Configuring a Layer 2 Ethernet 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 an upper threshold.
Depending on your configuration, when a particular type of traffic exceeds its upper threshold, the interface performs either of the following operations:
• Blocks this type of traffic and forwards 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 interface begins to forward the traffic.
• Goes down automatically—The interface goes down automatically and stops forwarding any
traffic. When the blocked traffic drops below the lower threshold, the interface does not
automatically come up. To bring up the interface, use the undo shutdown command or disable
the storm control feature.
You can configure an Ethernet interface to output threshold event traps and log messages when monitored traffic meets one of the following conditions:
• Exceeds the upper threshold.
• Drops below the lower threshold.
Both storm suppression and storm control can suppress storms on an interface. Storm suppression uses the chip to suppress traffic. Storm suppression has less impact on the device performance than storm control, which uses software to suppress traffic.
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 restrictions and guidelines
For the traffic suppression result to be determined, do not configure storm control together with storm suppression for the same type of traffic. For more information about storm suppression, see "Configuring storm suppression."
Configuration procedure
To configure storm control on an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. (Optional.) Set the statistics
polling interval of the storm control module.
3. Enter Ethernet interface
view.
4. (Optional.) Enable storm
control, and set the lower and upper thresholds for broadcast, multicast, or unknown unicast traffic.
system-view
storm-constrain interval
interface
interface-number
storm-constrain { broadcast | multicast | unicast } { pps | kbps
ratio }
|
min-pps-values
interface-type
max-pps-values
interval
N/A
The default setting is 10 seconds.
For network stability, use the default or set a longer statistics polling interval.
N/A
By default, storm control is disabled.
11
Step Command Remarks
5. Set the control action to take
when monitored traffic exceeds the upper threshold.
6. (Optional.) Enable the
Ethernet interface to output log messages when it detects storm control threshold events.
storm-constrain control { block
shutdown
|
storm-constrain enable log
}
By default, storm control is disabled.
By default, the Ethernet interface outputs log messages when monitored traffic exceeds the upper threshold or drops below the lower threshold.
7. (Optional.) Enable the
Ethernet interface to send storm control threshold event traps.
storm-constrain enable trap

Forcibly bringing up a fiber port

IMPORTANT:
Copper ports do not support this feature.
As shown in Figure 1, 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 u p-mode command.
This command forcibly brings up a fiber port, even when no fiber links or transceiver modules are present for the fiber port. When one fiber link is present and up, the fiber port can forward packets over the link unidirectionally.
By default, the Ethernet interface sends traps when monitored traffic exceeds the upper threshold or drops below the lower threshold from the upper threshold.
12
Figure 1 Forcibly bring up a fiber port
Correct fiber
connection
Device A
Device B
Fiber port Tx end Rx end The fiber is disconnected.Fiber link
When Ethernet interfaces
cannot be or are not forcibly
brought up
Device A
Device B
When Ethernet interfaces
are forcibly brought up
Device A
Device B
Configuration restrictions and guidelines
When you forcibly bring up a fiber port, follow these restrictions and guidelines:
• The loopback, shutdown, and port up-mode commands are mutually exclusive.
• The following operations on a fiber port will cause link updown events before the port finally
stays up:
{ Configure both the port up-mode command and the speed or duplex command.
{ Install or remove fiber links or transceiver modules after you forcibly bring up the fiber port.
Configuration procedure
To forcibly bring up a fiber port:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Forcibly bring up the fiber
port.
system-view interface
interface-number
port up-mode
interface-type
The interface is down.Packets
N/A
N/A
By default, a fiber port is not forcibly brought up, and the physical state of a fiber port depends on the physical state of the fibers.
13

Setting the MDIX mode of an Ethernet interface

IMPORTANT:
Fiber ports do not support the MDIX mode setting.
A physical Ethernet interface has eight pins, each of which plays a dedicated role. For example, pins 1 and 2 transmit signals, and pins 3 and 6 receive signals. You can use both crossover and straight-through Ethernet cables to connect copper Ethernet interfaces. To accommodate these types of cables, a copper Ethernet interface can operate in one of the following Medium Dependent Interface-Crossover (MDIX) modes:
• MDIX mode—Pins 1 and 2 are receive pins and pins 3 and 6 are transmit pins.
• MDI mode—Pins 1 and 2 are transmit pins and pins 3 and 6 are receive pins.
• AutoMDIX mode—The interface negotiates pin roles with its peer.
NOTE:
This feature does not take effect on pins 4, 5, 7, and 8 of physical Ethernet interfaces.
• Pins 4, 5, 7, and 8 of interfaces operating at 10 Mbps or 100 Mbps do not receive or transmit signals.
• Pins 4, 5, 7, and 8 of interfaces operating at 1000 Mbps or higher rates receive and transmit signals.
To enable a copper Ethernet interface to communicate with its peer, set the MDIX mode of the interface by following these guidelines:
• Typically, set the MDIX mode of the interface to AutoMDIX. Set the MDIX mode of the interface
to MDI or MDIX only when the device cannot determine the cable type.
• When a straight-through cable is used, configure the interface to operate in an MDIX mode
different than its peer.
• When a crossover cable is used, perform one of the following tasks:
{ Configure the interface to operate in the same MDIX mode as its peer.
{ Configure either end to operate in AutoMDIX mode.
To set the MDIX mode of an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Set the MDIX mode of the
Ethernet interface.
system-view interface
interface-number
mdix-mode { automdix | mdi | mdix
interface-type
}
N/A
N/A
By default, a copper Ethernet interface operates in auto mode to negotiate pin roles with its peer.
10-GE interfaces support only the
automdix
mode.

Testing the cable connection of an Ethernet interface

IMPORTANT:
If the link of an Ethernet interface is up, testing its cable connection will cause the link to go down and then come up.
14
NOTE:
Fiber ports do not support this feature.
This feature tests the cable connection of an Ethernet interface and displays cable test result within 5 seconds. The test result includes the cable's status and some physical parameters. If any fault is detected, the test result shows the length from the local port to the faulty point.
To test the cable connection of an Ethernet interface:
Step Command
1. Enter system view.
2. Enter Ethernet interface view.
3. Perform a test for the cable connected to the
Ethernet interface.
system-view interface
virtual-cable-test
interface-type interface-number

Enabling bridging on an Ethernet interface

By default, the device drops packets whose outgoing interface and incoming interface are the same.
To enable the device to forward such packets rather than drop them, enable the bridging feature in Ethernet interface view.
To enable bridging on an Ethernet interface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
view.
3. Enable bridging on the
Ethernet interface.
system-view interface
interface-number
port bridge enable
interface-type

Setting the interface connection distance

When two directly connected interfaces communicate, they use the buffer area to buffer the received data. A longer interface connection distance requires a greater buffer area.
Perform this task to modify the buffer area size by setting the interface connection distance.
To set the interface connection distance:
Step Command Remarks
1. Enter system view.
2. Enter Layer 2 Ethernet
interface view.
3. Set the interface
connection distance.
system-view interface
interface-number
port connection-distance 10000
interface-type
|
20000
|
40000
}
{
300
|
N/A
N/A
By default, bridging is disabled on an Ethernet interface.
N/A
N/A
By default, the interface connection distance is 10000 meters.
15

Configuring a Layer 3 Ethernet interface or subinterface

Setting the MTU for an Ethernet interface or subinterface

The maximum transmission unit (MTU) of an Ethernet interface affects the fragmentation and reassembly of IP packets on the interface. Typically, you do not need to modify the MTU of an interface.
To set the MTU for an Ethernet interface or subinterface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface
or subinterface view.
3. Set the MTU of the
Ethernet interface or subinterface.
Setting the MAC address of an Ethernet interface or
system-view interface
interface-number.subnumber }
mtu
interface-type { interface-number |
size
N/A
N/A
The default setting is 1500 bytes.
subinterface
In a network, when the Layer 3 Ethernet interfaces or subinterfaces of different devices have the same MAC address, the devices might fail to communicate correctly. To eliminate the MAC address
conflicts, use the mac-address command to modify the MAC addresses of Layer 3 Ethernet
interfaces or subinterfaces.
Do not configure this feature on the border gateways in the following networks:
• A VXLAN IP gateway network.
• An EVPN gateway network.
To set the MAC address of an Ethernet interface or subinterface:
Step Command Remarks
1. Enter system view.
2. Enter Ethernet interface or
subinterface view.
3. Set the MAC address of the
Ethernet interface or subinterface.
system-view interface
{ interface-number | interface-number.subnumber
}
mac-address
interface-type
mac-address
N/A
N/A
By default, no MAC address is set for a Layer 3 Ethernet interface or subinterface.

Displaying and maintaining an Ethernet interface or subinterface

Execute display commands in any view and reset commands in user view.
16
Task Command
display counters { inbound | outbound } interface
Display interface traffic statistics.
[ interface-type [ interface-number | interface-number.subnumber ] ]
Display traffic rate statistics of interfaces in up state over the last statistics polling interval.
Display the operational and status information of the specified interfaces.
Display information about dropped packets on the specified interfaces.
Display the PFC information for an interface.
Display information about storm control on the specified interfaces.
Display the Ethernet module statistics.
Clear interface or subinterface statistics.
Clear the statistics of dropped packets on the specified interfaces.
Clear the Ethernet module statistics.
display counters rate { inbound | outbound } interface
[ interface-type [ interface-number | interface-number.subnumber ] ]
display interface
[ interface-type [ interface-number |
interface-number.subnumber ] ] [
display packet-drop { interface
brief
description
[
[ interface-type
down
|
[ interface-number | interface-number.subnumber ] ] |
summary display priority-flow-control interface
[ interface-number ] ]
}
[ interface-type
display storm-constrain [ broadcast | multicast | unicast ]
interface
[
interface-type interface-number
display ethernet statistics slot reset counters interface
[ interface-type [ interface-number |
slot-number
]
interface-number.subnumber ] ]
reset packet-drop interface
[ interface-type [ interface-number
| interface-number.subnumber ] ]
reset ethernet statistics
[
slot
slot-number ]
] ]
17

Configuring loopback, null, and inloopback interfaces

This chapter describes how to configure a loopback interface, a null interface, and an inloopback interface.

Configuring a loopback interface

A loopback interface is a virtual interface. The physical layer state of a loopback interface is always up unless the loopback interface is manually shut down. Because of this benefit, loopback interfaces are widely used in the following scenarios:
• Configuring a loopback interface address as the source address of the IP packets that the device generates—Because loopback interface addresses are stable unicast addresses,
they are usually used as device identifications.
{ When you configure a rule on an authentication or security server to permit or deny packets
that a device generates, you can simplify the rule by configuring it to permit or deny packets carrying the loopback interface address that identifies the device.
{ When you use a loopback interface address as the source address of IP packets, make
sure the route from the loopback interface to the peer is reachable by performing routing configuration. All data packets sent to the loopback interface are considered packets sent to the device itself, so the device does not forward these packets.
• Using a loopback interface in dynamic routing protocols—With no router ID configured for
a dynamic routing protocol, the system selects the highest loopback interface IP address as the router ID. In BGP, to avoid interruption of BGP sessions due to physical port failure, you can use a loopback interface as the source interface of BGP packets.
To configure a loopback interface:
Step Command Remarks
1. Enter system view.
2. Create a loopback interface
and enter loopback interface view.
3. Configure the interface
description.
4. Configure the expected
bandwidth of the loopback interface.
5. Restore the default settings
for the loopback interface.
6. Bring up the loopback
interface.
system-view
interface loopback
interface-number
description
bandwidth
default
undo shutdown
text
bandwidth-value

Configuring a null interface

A null interface is a virtual interface and is always up, but you cannot use it to forward data packets or configure it with an IP address or link layer protocol. The null interface provides a simpler way to filter packets than ACL. You can filter undesired traffic by transmitting it to a null interface instead of
N/A
N/A
The default setting is interface name
Interface Interface
By default, the expected bandwidth of a loopback interface is 0 kbps.
N/A
By default, a loopback interface is up.
(for example, ).
LoopBack1
18
applying an ACL. For example, if you specify a null interface as the next hop of a static route to a network segment, any packets routed to the network segment are dropped.
To configure a null interface:
Step Command Remarks
1. Enter system view.
2. Enter null interface view.
3. Configure the interface
description.
4. Restore the default settings
for the null interface.
system-view
interface null 0
description
default
text
N/A
Interface Null 0 is the default null interface on the device and cannot be manually created or removed.
Only one null interface, Null 0, is supported on the device. The null interface number is always 0.
The default setting is NULL0 Interface.
N/A

Configuring an inloopback interface

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

Displaying and maintaining loopback, null, and inloopback interfaces

Execute display commands in any view and reset commands in user view.
Task Command
Display information about the specified or all loopback interfaces.
Display information about the null interface.
Display information about the inloopback interface.
Clear the statistics on the specified or all loopback interfaces.
Clear the statistics on the null interface.
display interface loopback
description
[
display interface null down
] ]
display interface inloopback
down
|
reset counters interface loopback
[ interface-number ]
reset counters interface null
down
|
] ]
[ interface-number ] [
] ]
brief
[ 0 ] [
[
[ 0 ] [
[ 0 ]
description
brief
description
[
|
brief
19

Bulk configuring interfaces

You can enter interface range view to bulk configure multiple interfaces with the same feature instead
of configuring them one by one. For example, you can execute the shutdown command in interface
range view to shut down a range of interfaces.

Configuration restrictions and guidelines

When you bulk configure interfaces in interface range view, follow these restrictions and guidelines:
• In interface range view, only commands supported by the first interface in the specified interface
list are available for configuration.
• Before you configure an interface as the first interface in an interface range, make sure you can enter the view of the interface by using the interface interface-type { interface-number | interface-number.subnumber } command.
• Do not assign both an aggregate interface and any of its member interfaces to an interface
range. Some commands, after being executed on both an aggregate interface and its member interfaces, can break up the aggregation.
• Understand that the more interfaces you specify in an interface range, the longer the command
execution time.
• To guarantee bulk interface configuration performance, configure fewer than 1000 interface
range names.
• After a command is executed in interface range view, one of the following situations might
occur:
{ The system displays an error message and stays in interface range view. It means that the
execution failed on one or multiple member interfaces.
− If the execution failed on the first member interface, the command is not executed on any member interfaces.
− If the execution failed on a non-first member interface, the command takes effect on the remaining member interfaces.
{ The system returns to system view. It means that:
− The command is supported in both system view and interface view.
− The execution failed on a member interface in interface range view and succeeded in
system view.
− The command is not executed on the subsequent member interfaces.
You can use the display this command to verify the configuration in interface view of each
member interface. In addition, if the configuration in system view is not needed, use the
undo form of the command to remove the configuration.

Configuration procedure

Step Command Remarks
1. Enter system view.
system-view
N/A
20
Loading...
+ 272 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use