S300, S500, S2700, S5700, and S6700 V200R023C00 Configuration Guide - Interface Management
S300, S500, S2700, S5700, and S6700 V200R023C00 Configuration Guide - Interface Management
Ethernet Switches
V200R023C00
Issue 01
Date 2023-09-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://e.huawei.com
Intended Audience
This document is intended for network engineers responsible for switch
configuration and management. You should be familiar with basic Ethernet
knowledge and have extensive experience in network deployment and
management.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as
follows.
Convention Description
Convention Description
Security Conventions
● Password setting
– To ensure device security, use ciphertext when configuring a password
and change the password periodically.
– The switch considers all passwords starting and ending with %^%#, %#
%#, %@%@ or @%@% as ciphertext and attempts to decrypt them. If
you configure a plaintext password that starts and ends with %^%#, %#
%#, %@%@ or @%@%, the switch decrypts it and records it into the
configuration file (plaintext passwords are not recorded for the sake of
security). Therefore, do not set a password starting and ending with %^
%#, %#%#, %@%@ or @%@%.
– When you configure passwords in ciphertext, different features must use
different ciphertext passwords. For example, the ciphertext password set
for the AAA feature cannot be used for other features.
● Encryption algorithms
The switch currently supports the 3DES, AES, RSA, SHA1, SHA2, and MD5.
3DES, RSA, and AES are reversible, whereas SHA1, SHA2, and MD5 are
irreversible. Using the encryption algorithms DES, 3DES, RSA (RSA-1024 or
lower), MD5 (in digital signature scenarios and password encryption), or
SHA1 (in digital signature scenarios) is a security risk. If protocols allow, use
more secure encryption algorithms, such as AES, RSA (RSA-2048 or higher),
SHA2, or HMAC-SHA2.
An irreversible encryption algorithm must be used for the administrator
password. SHA2 is recommended for this purpose.
● Personal data
Some personal data (such as MAC or IP addresses of terminals) may be
obtained or used during operation or fault location of your purchased
products, services, features, so you have an obligation to make privacy policies
and take measures according to the applicable law of the country to protect
personal data.
● Mirroring
The terms mirrored port, port mirroring, traffic mirroring, and mirroring in this
document are mentioned only to describe the product's function of
communication error or failure detection, and do not involve collection or
processing of any personal information or communication data of users.
● Reliability design declaration
Network planning and site design must comply with reliability design
principles and provide device- and solution-level protection. Device-level
protection includes planning principles of dual-network and inter-board dual-
link to avoid single point or single link of failure. Solution-level protection
refers to a fast convergence mechanism, such as FRR and VRRP. If solution-
level protection is used, ensure that the primary and backup paths do not
share links or transmission devices. Otherwise, solution-level protection may
fail to take effect.
Disclaimer
● This document is designed as a reference for you to configure your devices. Its
contents, including web pages, command line input and output, are based on
laboratory conditions. It provides instructions for general scenarios, but does
not cover all use cases of all product models. The examples given may differ
from your use case due to differences in software versions, models, and
configuration files. When configuring your device, alter the configuration
depending on your use case.
● The specifications provided in this document are tested in a lab environment
(for example, a certain type of cards have been installed on the tested device
or only one protocol is run on the device). Results may differ from the listed
specifications when you attempt to obtain the maximum values due to factors
such as differences in hardware configurations and carried services.
● In this document, public IP addresses may be used in feature introduction and
configuration examples and are for reference only unless otherwise specified.
Contents
Physical interfaces are sometimes called ports. This document uses the term interface.
Table 1-1 describes the physical interfaces that the switch supports.
Fast Ethernet (FE) A LAN-side FE interface works at the data link layer,
interface provides a maximum transmission rate of 100 Mbit/s,
processes Layer 2 protocol packets, and implements
Layer 2 forwarding.
Table 1-2 describes the management interfaces that the switch supports.
● Logical interfaces
Logical interfaces do not physically exist. They are manually configured and
can be used to exchange data and transmit service data.
Table 1-3 describes the logical interfaces that the switch supports.
NULL interface A null interface is used to filter routes because any data
packets received by the null interface are discarded.
Interface Description
Interface Number
As shown in Figure 1-1, There are two rows of service interfaces on the device.
These interfaces are numbered from bottom to top and left to right, starting from
1.
Some 40GE optical interfaces can be split into multiple interfaces. The converted
interfaces are numbered using the following rules:
● 10GE interfaces converted from a 40GE interface are numbered based on the
number of the last 10GE interface on the switch. For interfaces on the switch
panel, if the last 10GE interface is numbered XGE 0/y/m and a 40GE interface
to be split is numbered 40GE 0/y/n, the four 10GE interfaces converted from
the 40GE interface are numbered XGE 0/y/(m + 4 * (n - 1) + z + 1). For
example, if the last 10GE interface on a switch is numbered XGE 0/0/48, the
four 10GE interfaces converted from 40GE 0/0/3 are numbered XGE 0/0/57,
XGE 0/0/58, XGE 0/0/59, and XGE 0/0/60. For interfaces on a card, m has a
fixed value of 0. For example, the four 10GE interfaces converted from 40GE
1/1/1 on a card are numbered XGE 1/1/1, XGE 1/1/2, XGE 1/1/3, and XGE
1/1/4.
– y: indicates the subcard number.
– m: indicates the sequence number of the last 10GE interface on the
switch.
– n: indicates the sequence number of the 40GE interface.
– z: indicates the interface location. The value ranges from 0 to 3.
● 25GE interfaces converted from a 100GE interface are numbered based on the
number of the last 25GE interface on the switch. Because only the 100GE
interfaces on cards support interface split, if a 100GE interface to be split is
numbered 100GE 0/y/n, the four 25GE interfaces converted from the 100GE
interface are numbered 25GE 0/y/(4 * (n - 1) + z + 1). For example, the four
25GE interfaces converted from 100GE 0/1/1 on a card are numbered 25GE
0/1/1, 25GE 0/1/2, 25GE 0/1/3, and 25GE 0/1/4.
– y: indicates the subcard number.
– m: indicates the sequence number of the last 10GE interface on the
switch.
– n: indicates the sequence number of the 40GE interface.
– z: indicates the interface location. The value ranges from 0 to 3.
NOTE
Split interfaces are numbered in the same sequence as the wires of a cable are numbered.
For example, in a 1-to-4 cable, the wire numbered 1 corresponds to the interface with the
lowest interface number, and the wire numbered 4 corresponds to the interface with the
highest interface number.
After the interface rate increases, the interface numbering rule is as follows:
● On the S5736-S48S4X-A and S5736-S48S4X-D, the subcard ID of the 48
1000BASE-X Ethernet optical interfaces is 0, and the interface rate is increased
to 10 Gbit/s after an RTU license for interface rate improvement is loaded. To
prevent subcard ID conflicts, the subcard ID of the previous four 10GE SFP+
Ethernet optical interfaces is fixed at 1.
● On the S6730-H24X4Y4C, the subcard ID of the 24 10GE SFP+ Ethernet
optical interfaces is 0. After an RTU license for interface rate improvement is
loaded, the interface rate is increased to 25 Gbit/s, the subcard ID becomes 1,
and the subcard ID of the previous four 1GE/10GE/25GE SFP28 Ethernet
optical interfaces remains at 0.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
interface-type interface-number specifies the type and number of an interface.
NOTE
If the specified interface does not exist, this command creates the interface and displays the
interface view.
● Only the S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6735-S, S6720-EI, S6720S-
EI, S6730-H, S6730S-H, S6730-S, and S6730S-S support Ethernet sub-interfaces.
● Only hybrid and trunk interfaces on the preceding switches support Layer 2 Ethernet
sub-interface configuration.
● After you run the undo portswitch command to switch Layer 2 interfaces on the
preceding series of switches into Layer 3 interfaces, you can configure Layer 3 Ethernet
sub-interfaces on the interfaces.
● After an interface is added to an Eth-Trunk, sub-interfaces cannot be configured on the
interface.
● VLAN termination sub-interfaces cannot be created on a VCMP client.
----End
Context
To facilitate switch management and maintenance, you can configure interface
descriptions. An interface description can contain:
Procedure
Step 1 Run system-view
----End
Context
To check the network status or locate network faults, you can enable IPv4 or IPv6
packet statistics collection on an interface and view packet statistics on the
interface, monitoring traffic on the interface.
Procedure
Step 1 Run system-view
NOTE
Only the S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6735-S, S6720-EI, S6720S-EI,
S6730-H, S6730S-H, S6730-S, and S6730S-S support IPv4 or IPv6 packet statistics collection
on interfaces.
This command and the statistic enable { both | inbound | outbound } command used in
the VLANIF interface view are mutually exclusive.
If this command and the traffic policy command are configured together on the S5731-H,
S5731-S, S5731S-H, S5731S-S, S5732-H, S6730-H, S6730S-H, S6730-S, and S6730S-S traffic
statistics will fail to be collected.
----End
Context
By setting the traffic statistics collection interval, you can collect and analyze
packet statistics. According to traffic statistics, you can take measures to prevent
network congestion and service interruption.
● When congestion occurs, you can set the statistics collection interval on an
interface to 300 seconds or less (30 seconds if congestion worsens). Then
observe traffic distribution on the interface within a short period of time. Take
measures to data packets that cause congestion to control the rate of the
packets.
● When the network bandwidth is sufficient and services are running properly,
set the statistics collection interval on an interface to more than 300 seconds.
If traffic parameters on an interface are out of the specified range, change the
statistics collection interval to observe the traffic statistics in real time.
NOTE
● The interval set in the system view takes effect on all the interfaces that use the default
interval.
● The interval set in the interface view takes effect only on this interface.
● The interval set in the interface view takes precedence over the interval set in the
system view.
Procedure
● Configure the global traffic statistics collection interval in the system view.
a. Run system-view
----End
NOTE
● If the switch supports the autocomplete function, you must enter at least the characters
shut before the switch can automatically complete the shutdown command.
● Running the shutdown and undo shutdown commands is equivalent to running the
restart command. Configuration information of interfaces is not modified or deleted.
● A NULL interface is always Up and cannot be enabled or disabled by commands.
● A loopback interface is always Up after being created and cannot be enabled or
disabled by commands.
Procedure
● Disable an interface.
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The interface view is displayed.
c. (Optional) To configure this function in a sub-interface view, run
interface interface-type interface-number.subinterface-number
The Ethernet sub-interface view is displayed.
● Enable an interface.
a. Run system-view
----End
Procedure
● Run the display interface [ interface-type [ interface-number [.subinterface-
number ] ] ] command to check information about an interface, including
interface running status, basic interface configuration, and packet forwarding
on the interface.
● Run the display interface brief [ main ] command to check brief information
about interfaces, including the physical status, protocol status, bandwidth
usage in the inbound and outbound directions during a specific period, and
the number of error packets sent and received.
● Run the display ip interface [ interface-type interface-number [.subinterface-
number ] ] command to check the IP configuration of an interface.
● Run the display interface description [ interface-type [ interface-number
[.subinterface-number ] ] ] command to check the description of an interface.
NOTICE
Interface statistics cannot be restored after they are cleared. Confirm your action
before performing an operation.
Procedure
● Run the reset counters interface [ interface-type [ interface-number
[.subinterface-number ] ] ] command to clear the interface statistics.
● Run the reset counters if-mib interface [ interface-type [ interface-number
[.subinterface-number ] ] ] command to clear traffic statistics on an interface
in the network management system.
----End
– FE interfaces
– GE interfaces
– XGE interfaces (10GE interfaces)
– MultiGE interfaces
– 25GE interfaces
– 40GE interfaces
– 100GE interfaces
● Based on the electrical attribute, Ethernet interfaces can be classified into the
following types:
– Electrical interfaces
– Optical interfaces
● Based on the packet forwarding mode, Ethernet interfaces can be classified
into the following types:
– Layer 2 Ethernet interfaces: are physical interfaces working at the data
link layer. They can only forward received packets at Layer 2 or be added
to VLANs to forward packets at Layer 3 through VLANIF interfaces.
– Layer 3 Ethernet interfaces: are physical interfaces working at the
network layer. IP addresses can be assigned to these interfaces. That is,
they can receive and send packets whose source and destination IP
addresses are on different network segments.
Licensing Requirements
An Ethernet interface is a basic feature of a switch and is not under license
control.
NOTE
For details about software mappings, visit Hardware Center and select the desired product
model.
The S5731-L and S5731S-L are remote units and do not support web-based management,
YANG, or commands. They can be configured only through configuration delivery by the
central device. For details, see "Simplified Architecture Configuration (the Solar System
Solution)" in the S300, S500, S2700, S5700, and S6700 V200R023C00 Configuration Guide -
Device Management.
Feature Limitations
● Table 2-1 lists the common attributes of Ethernet interfaces.
FE ● Transmission medium: -
electric network cable
al ● Rate: 10 Mbit/s and 100
interfa Mbit/s
ces
● Duplex mode: full-duplex/
half-duplex
● Auto-negotiation: supported
● Flow control: supported
● Flow control auto-
negotiation: supported
● Received flow control:
supported
● Received flow control auto-
negotiation: supported
GE ● Transmission medium: -
electric network cable
al ● Rate: 10 Mbit/s, 100 Mbit/s,
interfa and 1000 Mbit/s
ces
● Duplex mode: full-duplex/
half-duplex. When the rate is
1000 Mbit/s, only full-duplex
is supported.
● Auto-negotiation: supported
● Flow control: supported
● Flow control auto-
negotiation: supported
● Received flow control:
supported
● Received flow control auto-
negotiation: supported
FE ● Transmission medium: FE -
optical optical module
interfa ● Rate: 100 Mbit/s
ces
● Duplex mode: full-duplex
● Auto-negotiation: not
supported
● Flow control: supported
● Flow control auto-
negotiation: not supported
● Received flow control:
supported
● Received flow control auto-
negotiation: not supported
different subseries or
between Huawei and non-
Huawei switches.
● When the connection
medium of an XGE (10GE)
optical interface on the
S6735-S switch is a passive
high-speed cable, the
interface flap once and then
remain in the Up state.
● Only the following interfaces
of the following devices
support 2.5GE optical
modules or 2.5GE hybrid
modules. If 2.5GE optical
modules or 2.5GE hybrid
modules are installed on the
interfaces that do not
support these modules, these
modules function as GE
optical modules.
– S5731-S32ST4X, S5731-
S32ST4X-A, S5731-
S32ST4X-D, S5731S-
S32ST4X-A, and S5731S-
S32ST4X-A1: 24 downlink
GE interfaces
– S5731-S48S4X, S5731-
S48S4X-A, S5731S-
S48T4X-A, and S5731S-
S48T4X-A1: 44 GE
interfaces numbered 5 to
48
– S5731-H24HB4XZ and
S5731S-H24HB4XZ-A: first
20 downlink GE interfaces
and four downlink 10GE
interfaces
– S5731-H48HB4XZ and
S5731S-H48HB4XZ-A: 28
GE interfaces numbered 1
to 8 and 25 to 44 and
four downlink 10GE
interfaces
40GE When the transmission medium ● When you run the display
optical is a 40GE optical module: interface command on a
interfa ● Rate: 40000 Mbit/s 40GE optical interface that
ces has a high-speed cable
● Duplex mode: full-duplex installed, the command
● Auto-negotiation: not output shows that auto-
supported negotiation is enabled.
● Flow control: supported However, you cannot run the
negotiation auto command
● Flow control auto- to configure the auto-
negotiation: not supported negotiation mode.
● Received flow control: ● After a 40GE optical
supported interface on the S7Q02001,
● Received flow control auto- S5732-H24UM2CC, S5732-
negotiation: not supported H48UM2CC, and S5732-
When the transmission medium H48XUM2CC has a high-
is a high-speed cable: speed cable connected, the
interface does not support
● Rate: 40000 Mbit/s
auto-negotiation.
● Duplex mode: full-duplex
● Auto-negotiation: supported
● Flow control: supported
● Flow control auto-
negotiation: not supported
● Received flow control:
supported
● Received flow control auto-
negotiation: not supported
NOTE
For details about software mappings, visit Hardware Center and select the desired
product model.
The S5731-L and S5731S-L are remote units and do not support web-based
management, YANG, or commands. They can be configured only through
configuration delivery by the central device. For details, see "Simplified Architecture
Configuration (the Solar System Solution)" in the S300, S500, S2700, S5700, and
S6700 V200R023C00 Configuration Guide - Device Management.
● The S5720-14X-PWH-SI-AC can connect to the following devices through
MultiGE interfaces:
– All switches providing FE electrical interfaces, GE electrical interfaces or
MultiGE electrical interfaces
– AP: AP7050DN-E (with 2.5G uplink interfaces) running V200R007C00,
AP5030DN-S (with 1G uplink interfaces)
– Pico: BTS3911B running V100R010C10SPC092T
● The S5731-S24N4X2Q-A, S5731-S24UN4X2Q, S5731-S8UM16UN2Q, S5731S-
S24N4X2Q-A1, S5731S-S24UN4X2Q-A, S5731S-S8UM16UN2Q-A, S5720-14X-
PWH-SI-AC, S5720-28X-PWH-LI-AC, S5720-28X-PWH-LI-ACF, S5732-
H24UM2CC, S5732-H48UM2CC, S5736-S24UM4XC, S6720-32C-SI-AC,
S6720-32C-SI-DC, S6720-32C-PWH-SI-AC, S6720-52X-PWH-SI, S6720-56C-
PWH-SI-AC, S6720-56C-PWH-SI, and S6720-32C-PWH-SI can connect to the
following devices through MultiGE interfaces:
– All switches providing FE electrical interfaces or GE electrical interfaces
– All devices providing MultiGE interfaces defined by the NBASE-T Alliance
– All devices providing MultiGE interfaces that comply with the 802.3bz
standard
● On the S5700-SI, S5700-EI, and S5700-HI in V200R003 or V200R005, a GE
interface can go Up after it has a GE copper module installed. However, you
cannot run corresponding commands to configure the rate, duplex mode,
auto-negotiation, MDI, flow control, and virtual cable test on the interface.
The 10GE interfaces on the S5700-EI do not support GE copper modules.
● Only MEth0/0/1 on the S6700-EI, S6720-EI, S6720-HI, S5732-H, S6730-H,
S6730S-H, S6730-S, S6730S-S, S6735-S, and S6720S-EIsupports the duplex
mode configuration.
● For switches in V200R003C00 and earlier versions, only Layer 2 Ethernet
interfaces on the S5700-HI, S5710-EI, and S5710-HI can be configured as
Layer 3 interfaces. For switches in V200R005C00 and later versions, only Layer
2 Ethernet interfaces on the S5700-HI, S5710-EI, S5710-HI, S5700-EI, S6700-
EI, S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731S-H, S5731-S, S5731S-S,
S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, S6730S-S, S6735-S, S6720-
EI, and S6720S-EI can be configured as Layer 3 interfaces.
● Only the S5700-X-LI switches support the IFG configuration.
Procedure
1. Run system-view
The system view is displayed.
2. Run interface meth 0/0/1
The MEth management interface view is displayed.
3. Run undo negotiation auto
The MEth management interface is configured to work in non-auto-
negotiation mode.
By default, the MEth management interface works in auto-negotiation mode.
NOTE
When the management interface works in auto-negotiation mode, the rate and
duplex mode cannot be configured on the interface.
Interfaces at both ends of a link must use the same auto-negotiation mode. The
interfaces cannot communicate with each other if they use different auto-negotiation
modes.
4. Run speed { 10 | 100 }
The rate is configured for the MEth management interface.
By default, the MEth management interface works at the maximum rate of
100 Mbit/s.
5. Run duplex { full | half }
The duplex mode is configured for the MEth management interface.
By default, the MEth management interface works in full-duplex mode.
Procedure
● Configure a temporary port group.
a. Run system-view
The system view is displayed.
b. Run port-group group-member { interface-type interface-number1 [ to
interface-type interface-number2 ] } &<1-10>
Or interface range { interface-type interface-number1 [ to interface-type
interface-number2 ] } &<1-10>
A temporary port group is created and the port group view is displayed.
● Configure a permanent port group.
a. Run system-view
The system view is displayed.
b. Run port-group port-group-name
A permanent port group is created and the port group view is displayed.
c. Run group-member { interface-type interface-number1 [ to interface-
type interface-number2 ] } &<1-10>
Ethernet interfaces are added to the permanent port group.
NOTE
----End
Follow-up Procedure
In the port group view, you can deliver the following configurations to member
interfaces in a batch as required:
● Configuring the Working Mode of a Combo Interface
● Switching an Interface to Layer 3 Mode
● Configuring Auto-Negotiation
● Configuring the Interface Rate
● Configuring Flow Control
● Configuring the Delay in Reporting Physical Status Changes
● Configuring Link Flapping Protection
● Configuring an Interface to Transit to the Error-Down State When the
Number of Received Error Packets Exceeds the Threshold
● Setting the Jumbo Frame Length Allowed on an Interface
● Configuring Unidirectional Single-Fiber Communication
● Configuring the MDI Type
● Configuring the Duplex Mode
NOTE
After a configuration command is executed in the port group view, the device will deliver
the configuration to each port in the port group and display the configuration of each port.
You can configure both interface attribute commands and service commands in
the port group view. For details about the service commands, see the related
documentation.
A command run in the port group view takes effect only on member interfaces
that support the command. Therefore, a configuration that is batch delivered may
not take effect on all member interfaces. For example, a port group consists of
optical and electrical interfaces. If you run the transceiver power low trigger
error-down command in the port group view, the configuration will only take
effect on the optical interfaces.
fails and goes Down, the system automatically switches services to the standby
interface GE0/0/2. This switchover ensures normal service transmission and
improves device reliability.
After the standby interface GE0/0/2 takes over service transmission, the services
will not be switched back to GE0/0/1 even if GE0/0/1 is recovered. The services are
switched back to GE0/0/1 only when GE0/0/2 fails.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run port protect-group protect-group-index
A port protection group is created and the port protection group view is displayed.
Step 3 Run protect-group member interface-type interface-number master
The active interface in the port protection group is configured.
Step 4 Run protect-group member interface-type interface-number standby
The standby interface in the port protection group is configured.
A port protection group contains only an active interface and a standby interface.
NOTE
To improve service switchover performance of interfaces in a port protection group, you can run
the carrier { up-hold-time | down-hold-time } interval command on the active and standby
interfaces to set the delay in reporting status changes to 0 milliseconds. This configuration
ensures that the system immediately switches services to the standby interface when the active
interface fails.
----End
NOTE
● For details about Ethernet interfaces supporting the auto-negotiation function, see 2.2
Licensing Requirements and Limitations for Ethernet Interfaces.
● By default, auto-negotiation is enabled on GE optical interfaces and rate auto-
negotiation is disabled. You can run the speed auto-negotiation command to enable
rate auto-negotiation.
● When a GE optical module is installed on an XGE optical interface, the interface works
in auto-negotiation mode by default. To configure the interface to work in non-auto-
negotiation mode, run the undo negotiation auto command. If you replace the GE
optical module with an XGE optical module, the interface does not support the auto-
negotiation mode and works in non-auto-negotiation mode by default. If you replace
the XGE optical module with a GE optical module, the undo negotiation auto
command configuration becomes ineffective. If you need the interface to still work in
non-auto-negotiation mode, reconfigure this command.
● After configuring the auto-negotiation function on an interface, if you remove and
install a single optical fiber on the interface, the interface may be Up and the remote
interface may be Down. You can run the shutdown and undo shutdown commands on
the remote interface to make the remote interface go Up.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run negotiation auto
The Ethernet interface is configured to work in auto-negotiation mode.
By default, an Ethernet interface works in auto-negotiation mode.
----End
Context
You can configure the rate of an Ethernet interface in the following scenarios:
● Auto-negotiation mode: You can run the negotiation auto command to
configure an Ethernet interface to work in auto-negotiation mode. Interfaces
at both ends of a link negotiate the interface rate. You can configure the rate
of an Ethernet interface in the following situations:
– If the negotiated interface rate is not the required value, you can run the
auto speed command to manually set the interface rate. As shown in
Figure 2-2, Server1, Server2, and Server3 form a server cluster and their
network adapter rates are all 1000 Mbit/s. The rate of GE0/0/4
connecting the server cluster to the Internet is also 1000 Mbit/s. If the
auto-negotiation rate is not specified on the device, the rates negotiated
by GE0/0/1, GE0/0/2, and GE0/0/3 and their connected servers are all
1000 Mbit/s. When the three servers concurrently send data at the rate of
1000 Mbit/s, the outbound interface GE0/0/4 will be congested. To
prevent this situation, configure the auto-negotiation rate to 100 Mbit/s
for GE0/0/1, GE0/0/2, and GE0/0/3.
● For details about the rate supported by Ethernet interfaces, see 2.2 Licensing
Requirements and Limitations for Ethernet Interfaces.
● If two connected interfaces work in non-auto-negotiation mode, you need to configure
the same interface rate for them.
Procedure
● Configuring the interface rate in auto-negotiation mode
– Manually configuring the interface rate in auto-negotiation mode
NOTE
NOTE
NOTE
Context
Interfaces can work in the following two duplex modes:
● Half-duplex mode: An interface in this mode only receives or sends data at a
time within a specified transmission distance.
● Full-duplex mode: An interface in this mode receives and sends data at the
same time. The maximum throughput in full-duplex mode is double that in
half-duplex mode, and the transmission distance is not limited.
You can configure the duplex mode of an Ethernet electrical interface working in
either auto-negotiation or non-auto-negotiation mode.
For details about the duplex mode supported by Ethernet interfaces, see 2.2 Licensing
Requirements and Limitations for Ethernet Interfaces.
Interfaces at both ends of a link must use the same duplex mode. If two connected electrical
interfaces use different auto-negotiation modes, the interfaces work in half-duplex mode after
the negotiation and will fail to exchange packets properly.
Physical interfaces of the S5732-H24S6Q, S5732-H48S6Q, S6735-S, S6720-EI, S6720S-EI, S6730-
H, S6730S-H, S6730-S, and S6730S-S, and MultiGE interface of the S5732-H24UM2CC, S5732-
H48UM2CC, S5732-H48XUM2CC do not support the half duplex mode and this command is not
supported.
Only MEth0/0/1 on the S5732-H, S6735-S, S6720-EI, S6720S-EI, S6730-S, S6730S-S, and S6730-
H supports the duplex mode configuration.
Procedure
● Configuring the duplex mode for an interface in auto-negotiation mode
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The Ethernet interface view is displayed.
c. Run negotiation auto
The Ethernet interface is configured to work in auto-negotiation mode.
d. Run auto duplex { full | half }*
The duplex mode is set for the Ethernet interface.
By default, an Ethernet interface negotiates the duplex mode with the remote
interface.
● Configuring the duplex mode for an interface in non-auto-negotiation mode
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The Ethernet interface view is displayed.
c. Run undo negotiation auto
The Ethernet interface is configured to work in non-auto-negotiation
mode.
d. Run duplex { full | half }
The duplex mode is set for the Ethernet interface.
By default, the duplex mode of an Ethernet interface is full-duplex.
Context
There are four SFP28 Ethernet optical ports and two QSFP28 Ethernet optical
ports on the panel of S5732-H24UM2CC (part number: 02353HUC/
02353HUC-003/02353SJY/
02353SJY-001/02353SJY-004/02353SJY-010/02353SJY-011/02353SJY-014/02353SJY-
019/02353SJY-002/02353SJY-003/02353SJY-012/02353SJY-013/02353SJY-017/0235
3SJY-018), S5732-H48UM2CC (part number: 02353HUB/02353HUB-002/02353SJT/
02353SJT-001/02353SJT-003/02353SJT-004/02353SJT-010/02353SJT-011/02353SJT-
013/02353SJT-014/02353SJT-018/02353SJT-002) and S5732-H48XUM2CC. You can
run the set device port-config-mode enable command to change the working
mode of SFP28 Ethernet optical ports on the device panel and change the working
mode of QSFP28 Ethernet optical ports or split QSFP28 Ethernet optical ports. The
device supports eight types of working mode switching modes or interface split
modes:
Procedure
1. Run system-view
The system view is displayed.
2. Run set device port-config-mode port-config-mode enable { all | slot slot-
id }
The working mode of Ethernet optical ports and MultiGE interfaces on the
device panel is changed and the working mode of QSFP28 Ethernet optical
ports is changed or QSFP28 Ethernet optical ports are split.
By default, four SFP28 Ethernet optical ports on the panel of the S5732-
H24UM2CC (part number: 02353HUC/02353HUC-003/02353SJY/
02353SJY-001/02353SJY-004/02353SJY-010/02353SJY-011/02353SJY-014/0235
3SJY-019/02353SJY-002/02353SJY-003/02353SJY-012/02353SJY-013/02353SJY-
017/02353SJY-018), S5732-H48UM2CC (part number: 02353HUB/
02353HUB-002/02353SJT/
02353SJT-001/02353SJT-003/02353SJT-004/02353SJT-010/02353SJT-011/0235
3SJT-013/02353SJT-014/02353SJT-018/02353SJT-002) and S5732-H48XUM2CC
work at the rate of 25 Gbit/s, and two QSFP28 Ethernet optical ports work at
the rate of 40 Gbit/s. On the panel of the S5731-S8UM16UN2Q and S5731S-
S8UM16UN2Q-A, the first 16 MultiGE interfaces work at the rate of 2.5
Gbit/s, the last eight MultiGE interfaces work at the rate of 10 Gbit/s, four SFP
+ Ethernet optical ports are unavailable, and two QSFP+ Ethernet optical
ports work at the rate of 40 Gbit/s.
NOTE
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface MultiGE interface-number
The MultiGE interface view is displayed.
Step 3 Run port serdes-mode { 2500-base-x | 5000-base-x } { sgmii | xfi }
The Serdes mode of the MultiGE interface is configured.
By default, a MultiGE interface can work in 10G or 1G Serdes mode.
----End
NOTE
The following models support this configuration when equipped with the S7X08000 card:
● S5731-H24T4XC, S5731-H24P4XC, S5731-H48T4XC, S5731-H48P4XC, S5731-H24HB4XZ,
S5731-H48HB4XZ
● S5731S-H24T4XC-A, S5731S-H48T4XC-A, S5731S-H24HB4XZ-A, S5731S-H48HB4XZ-A
● S5736-S
● S5732-H24UM2CC, S5732-H48UM2CC, S5732-H48XUM2CC
Procedure
Step 1 Run system-view
The system view is displayed.
----End
Context
A combo interface consists of a GE electrical interface and a GE optical interface
on the panel. The multiplexed electrical and optical interfaces share one internal
forwarding interface and cannot work at the same time. When one interface
works, the other interface is disabled. You can use the electrical or optical
interface based on the remote interface type. The electrical and optical interfaces
share one interface view. When you enable the electrical or optical interface,
configure the interface attributes (such as the rate and duplex mode) in the same
interface view.
For details about the combo interface location on the panel, see "Appearance and
Structure" in the Hardware Description.
NOTE
Only combo interfaces support this function. For details about the combo interface
supported by the switch, see the Hardware Description or click Info-Finder.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface gigabitethernet interface-number
The GE interface view is displayed.
Step 3 Run combo-port { auto | copper | fiber }
The working mode of the combo interface is configured.
By default, a combo interface works in auto mode, in which the combo interface
automatically works as an optical or electrical interface.
● When the auto mode is specified, the system checks whether the combo
optical interface has an optical module installed, and selects the interface
working mode as follows:
– When the electrical interface is not connected, the combo interface works
as an optical interface if the combo optical interface has an optical
module installed.
– When the electrical interface is connected using a network cable and the
combo interface is Up, the combo interface works as an electrical
interface even if the combo optical interface has an optical module
installed. However, the combo interface works as an optical interface
after the device restarts.
– When the electrical interface is connected using a network cable and the
combo interface is Down, the combo interface works as an optical
interface if the combo optical interface has an optical module installed.
In summary, when the auto mode is specified and the combo optical interface
has an optical module installed, the combo interface works as an optical
interface after the device restarts.
● You can forcibly specify the working mode of the combo interface based on
the remote interface type. If the local combo electrical interface is connected
to a remote electrical interface, configure the combo interface to work in
copper mode. If the local combo optical interface is connected to a remote
optical interface, configure the combo interface to work in fiber mode.
----End
NOTE
Only interfaces on the S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6735-S, S6720-EI,
S6720S-EI, S6730-H, S6730S-H, S6730-S, and S6730S-S support switching between Layer 2
and Layer 3 modes.
IP addresses can be assigned to Ethernet interfaces in Layer 3 mode.
By default, an Ethernet interface works at Layer 2 and belongs to VLAN 1. An interface is
not removed from VLAN 1 immediately after being switched to Layer 3 mode. It is removed
from VLAN 1 only when Layer 3 protocols are Up.
You can configure Layer 2 and Layer 3 modes of an Ethernet interface in the Ethernet
interface view or system view. When the configurations in the two views differ, the latest
configuration takes effect.
Procedure
● Switch an Ethernet interface to Layer 3 mode in the Ethernet interface view.
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The Ethernet interface view is displayed.
c. Run undo portswitch
The interface is switched to Layer 3 mode.
By default, an Ethernet interface works in Layer 2 mode.
When you run this command on an interface, the mode switching
configuration takes effect when only attribute configurations (such as
shutdown and description configurations) exist on the interface. If
service configurations (such as the port link-type trunk configuration)
exist on the interface, you need to clear all service configurations before
running this command.
● Switch an Ethernet interface to Layer 2 mode in the Ethernet interface view.
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The Ethernet interface view is displayed.
c. Run portswitch
The interface is switched to Layer 2 mode.
By default, an Ethernet interface works in Layer 2 mode.
When you run this command on an interface, the mode switching
configuration takes effect when only attribute configurations (such as
shutdown and description configurations) exist on the interface. If
----End
Context
Flow control prevents packet loss caused by network congestion. If network
congestion occurs on the local device after flow control is configured, the local
device sends a message to the remote device, requesting the remote device to
temporarily stop sending packets. After receiving the message, the remote device
temporarily stops sending packets to the local device regardless of the interface
working rate. In this case, the device can receive and send pause frames.
If the remote device does not support auto-negotiation, you can configure flow
control on the local and remote devices. If both the local and remote devices
support auto-negotiation, you can configure flow control auto-negotiation on the
two devices. The local device then negotiates with the remote device to determine
whether to enable flow control based on the network congestion status.
NOTE
For details about Ethernet interfaces supporting the flow control function, see 2.2 Licensing
Requirements and Limitations for Ethernet Interfaces.
Flow control and flow control auto-negotiation cannot be concurrently configured on
Ethernet interfaces.
Flow control auto-negotiation takes effect only when configured on interfaces at both ends
of a link.
When an interface works in half-duplex mode, flow control does not take effect on the
interface.
A GE optical interface supports flow control and flow control auto-negotiation after it has a
GE copper module or a GE optical module installed.
An XGE optical interface supports flow control and flow control auto-negotiation after it
has a GE copper module installed.
A 25GE optical interface supports flow control and flow control auto-negotiation after it
has a GE copper module installed. Before installing a GE copper module on a 25GE optical
interface, you need to run the port mode ge command to configure the interface to work
at the rate of 1 Gbit/s.
On the S5720-52P-LI-AC, if interfaces 0 to 23 work as inbound interfaces (or outbound
interfaces) and interfaces 24 to 47 work as outbound interfaces (or inbound interfaces),
flow control auto-negotiation does not take effect on these interfaces.
Multicast functions (Layer 2 and Layer 3 multicast) and the flow control function
(configured using the flow-control command) are mutually exclusive on the following
models: S2730S-S, S5735-L-I, S5735-L1, S300, S5735-L, S5735S-L1, S5735S-L, S5735S-L-M,
S500, S5735-S, S5735S-S, S5735-S-I
Procedure
● Configuring flow control
a. Run system-view
When the device at the transmit side does not support auto-negotiation, you can
configure received flow control on the inbound interface of the link (at the
transmit side) and configure flow control on the outbound interface (at the
receive side). When devices at both ends of the link support auto-negotiation, you
can configure received flow control auto-negotiation on the inbound interface of
the link (at the transmit side) and configure flow control auto-negotiation on the
outbound interface (at the receive side), so that the devices can negotiate with
the peer devices to determine whether to enable flow control based on the
network congestion status.
NOTE
For details about Ethernet interfaces supporting received flow control, see 2.2 Licensing
Requirements and Limitations for Ethernet Interfaces.
Flow control, received flow control, flow control auto-negotiation, and received flow control
auto-negotiation can be configured on Ethernet interfaces, but cannot be configured
together.
Flow control can be implemented only after flow control is enabled on the interface of the
device at the receive side.
When an interface works in half-duplex mode, received flow control does not take effect.
GE optical interfaces support received flow control auto-negotiation after GE optical or GE
copper modules are installed on them.
XGE optical interfaces support received flow control auto-negotiation after GE copper
modules are installed on them.
A 25GE optical interface supports flow control and flow control auto-negotiation after it
has a GE copper module installed. Before installing a GE copper module on a 25GE optical
interface, you need to run the port mode ge command to configure the interface to work
at the rate of 1 Gbit/s.
For the S5720-52P-LI-AC, if received flow control auto-negotiation is configured on the
interfaces 0 to 23 that work as inbound interfaces and flow control auto-negotiation is
configured on the interfaces 24 to 47 that work as outbound interfaces, received flow
control auto-negotiation and flow control auto-negotiation do not take effect.
Multicast functions (Layer 2 and Layer 3 multicast) and the flow control function
(configured using the flow-control command) are mutually exclusive on the following
models: S2730S-S, S5735-L-I, S5735-L1, S300, S5735-L, S5735S-L1, S5735S-L, S5735S-L-M,
S500, S5735-S, S5735S-S, S5735-S-I
Procedure
● Enable received flow control.
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The Ethernet interface view is displayed.
c. Run flow-control receive
Received flow control is enabled on the Ethernet interface.
By default, received flow control is disabled on an Ethernet interface.
● Enable received flow control auto-negotiation.
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The Ethernet interface view is displayed.
c. Run negotiation auto
The interface is configured to work in auto-negotiation mode.
d. Run flow-control negotiation receive
Received flow control auto-negotiation is enabled on the Ethernet
interface.
By default, received flow control auto-negotiation is disabled on an
Ethernet interface.
----End
Context
The physical status of an Ethernet interface can be Up or Down. When the
physical status changes, the system notifies upper-layer protocol modules (such as
the routing and forwarding modules) of the change to direct packet receiving and
forwarding. The system also automatically generates traps and logs to remind
users to perform corresponding operations on physical links. For example, when
the physical status of the active interface in an interface protection group changes
from Up to Down, the system immediately instructs the upper-layer service
forwarding protocol to send service packets from the standby interface.
If frequent physical status changes are reported to the system, extra system costs
are generated. You can configure the delay in reporting physical status changes to
solve the problem. The system is unaware of the physical status changes on
interfaces within the configured delay. If the interface physical status is not
recovered after the delay expires, the physical status changes are reported to the
system.
Procedure
Step 1 Run system-view
You can configure the delay in reporting physical status changes based on the
network connection status.
● Setting a long delay
For example, an interface frequently alternates between Up and Down states
at an interval shorter than the IP route convergence time. In this case, the
upper-layer protocol does not need to sense the physical status changes. You
can set a long delay in reporting physical status changes to avoid unnecessary
routing entry refreshing caused by frequent physical status changes.
● Setting a short delay
For example, when the physical status of the active interface in an interface
protection group changes from Up to Down, the system needs to immediately
instruct the upper-layer service forwarding protocol to send service packets
from the standby interface. In this case, you can set a short delay in reporting
physical status changes to ensure real-time service switchover.
----End
Context
When the NMS obtains interface traffic statistics through the MIB tables iftable
and ifxtable, the time for querying interface traffic statistics in real time is long.
When the device has a large number of interfaces, the query efficiency of the NMS
is low. To resolve this issue, switches can be configured to periodically collect
traffic statistics on interfaces. In this case, the NMS can directly obtain traffic
statistics collected on interfaces, improving the query efficiency.
Procedure
Step 1 Run system-view
----End
Context
A link flap occurs when the physical status of an interface frequently alternates
between Up and Down due to network flapping or network cable faults. This
causes frequent network topology changes and affects user communication. For
example, two links work in primary/backup mode. If the interface of the primary
link experiences frequent Up/Down transitions, flows are switched between the
primary and backup links. Frequent service switchovers increase load of the device
and may result in service data loss.
Link flapping protection can solve the problem. To be specific, you can configure
link flapping protection globally or on a specified interface. This function disables
interfaces that frequently alternate between Up and Down so that the interfaces
become Down. This prevents the network topology from changing frequently.
When the system detects frequent physical status changes on the interface of the
primary link, the system directly disables the interface to trigger a primary/backup
link switchover. The backup link then steadily transmits services. The link flapping
protection function involves the following parameters:
● Number of link flaps: A link flap refers to an interface Up/Down transition.
● Link flapping detection period: It is a period during which the system counts
the number of link flaps.
If the number of link flaps on an interface reaches the threshold within a link
flapping detection period, the system disables the interface and records its status
as ERROR DOWN(link-flap) when link flapping protection is configured on this
interface or records its status as LINK-FLAP DOWN when link flapping protection
is configured globally. By default, after link flapping protection is enabled, an
interface goes Down if its status changes five times within 10 seconds.
To check whether a link flap occurs on a specified interface, disable global link
flapping protection and then enable link flapping protection on this interface. To
detect link flaps on all interfaces of a device, enable global link flapping protection
on the device. The link flapping protection function on a specified interface and
the global link flapping protection function are mutually exclusive. If the link
flapping protection function is enabled on an interface, the global link flapping
protection function does not take effect on this interface.
Follow-up Procedure
An interface in ERROR DOWN(link-flap) state can be recovered using either of
the following methods:
● Manual recovery. If a few interfaces need to be recovered forcibly, run the
shutdown and undo shutdown commands in sequence in the interface view.
Alternatively, run the restart command in the interface view to restart the
interface.
● Automatic recovery. If a large number of interfaces need to be recovered,
manual recovery is time consuming and error prone. Instead, you can run the
error-down auto-recovery cause link-flap interval interval-value command
in the system view to enable automatic interface recovery and set the
automatic recovery delay. Interfaces in Error-Down state then automatically
recover after the specified delay expires.
An interface in LINK-FLAP DOWN state can be recovered using either of the
following methods:
● Manual recovery. If a few interfaces need to be recovered forcibly, run the
shutdown and undo shutdown commands in sequence in the interface view.
Alternatively, run the restart command in the interface view to restart the
interface.
● Automatic recovery. Interfaces are automatically recovered after the
automatic recovery period for global link flapping protection expires. To set
the automatic recovery period, run the port link-flap auto-detect recovery
interval threshold-value command. The default value is 60 seconds.
Context
When an Ethernet interface receives excessive error packets, faults such as packet
loss will occur. Because the interface is still in Up state, traffic is still transmitted
on the interface even if a backup link is configured. To avoid impact on services,
you can configure the interface to change to the Error-down state when it receives
excessive error packets. When the number of received error packets on the
interface exceeds the threshold, the system disables the interface and records the
interface status as ERROR DOWN(error-statistics) state (indicating that the
interface is Down because of excessive error packets). Services are then switched
to the backup link immediately.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
By default, the alarm threshold of error packets is 3 and the alarm interval is 10
seconds.
The interface is configured to transit to the Error-down state when the number of
received error packets exceeds the threshold.
By default, an interface does not transit to the Error-down state when the number
of received error packets exceeds the threshold.
By default, the threshold for error packets is 3 and the interval is 10 seconds.
----End
Follow-up Procedure
An interface in Error-down state can be recovered using either of the following
methods:
● Manual recovery: If a few interfaces need to be recovered forcibly, run the
shutdown and undo shutdown commands in the interface view.
Alternatively, run the restart command in the interface view to restart the
interfaces.
● Automatic recovery: If a large number of interfaces need to be recovered,
manual recovery is time consuming and some interfaces may be omitted. You
can run the error-down auto-recovery cause error-statistics interval
interval-value command in the system view to enable automatic interface
recovery and set the recovery delay time. An interface in Error-down state
automatically recovers when the specified delay time expires.
Context
You can run the display interface command to view the running status and traffic
statistics on an interface. The Last 300 seconds input rate or Last 300 seconds
output rate field in the command output indicates the inbound or outbound
traffic rate on the interface in the last 300 seconds.
● If you want to obtain the total number of bytes passing through an interface
in a period, configure the device to count the bytes in the interframe gap
(IFG) and preamble when collecting traffic statistics on the interface. The
interface traffic rate is as follows:
Interface traffic rate = (Original packet length + IFG + Preamble) x Number of
packets passing through the interface every second
● If you want to obtain only the number of packet bytes passing through an
interface in a period, configure the device not to count the bytes in the IFG
and preamble when collecting traffic statistics on the interface. The interface
traffic rate is as follows:
Interface traffic rate = Original packet length x Number of packets passing
through the interface every second
By default, the IFG has a fixed value of 12 bytes and the preamble has a fixed
value of 8 bytes.
Procedure
Step 1 Run system-view
The device is configured to count the bytes in the IFG and preamble when
collecting traffic statistics on the interface.
By default, traffic statistics on an interface contain the IFG and preamble. You can
run the display interface command to view the running status and traffic
statistics on an interface. The Last 300 seconds input rate or Last 300 seconds
output rate field in the command output indicates the rate of incoming or
outgoing traffic on the interface in the last 300 seconds.
----End
Context
A jumbo frame is an Ethernet frame longer than 1518 bytes or a VLAN frame
longer than 1522 bytes.
When transmitting a large amount of data (such as files and videos), an Ethernet
interface may receive jumbo frames. If the jumbo frame length exceeds the
default data frame length that can be processed, the device directly discards the
jumbo frames. You can set the jumbo frame length allowed on an interface.
After you configure the device to allow jumbo frames, packet forwarding becomes
more flexible. If multiple common Ethernet frames are used to transmit a data
packet, many redundant contents such as interframe gaps (IFGs) and preambles
are also transmitted. If jumbo frames are used to transmit the data packet, fewer
frames, as well as fewer IFGs and preambles, are transmitted, improving
bandwidth efficiency.
Setting the jumbo frame length to the maximum value may not be the optimal
choice. When a jumbo frame is transmitted on a network, the jumbo frame length
must be supported by all devices on the transmission path. Otherwise, the jumbo
frame will be discarded during transmission.
NOTE
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The Ethernet interface view is displayed.
Step 3 Run jumboframe enable [ value ]
The maximum frame length allowed on the interface is set.
By default, the maximum frame length allowed on an interface is 9216 bytes.
If you run the jumboframe enable command on an Ethernet interface without
specifying the value parameter, the maximum jumbo frame length allowed on the
interface is 9216 bytes.
NOTE
If the length of an outgoing packet exceeds the maximum frame length allowed on an
interface, the interface can directly forward the packet.
----End
smaller packets, which are shorter than or equal to the MTU. If unfragmentation is
configured, some packets may be discarded during data transmission at the IP
layer. To ensure that large packets are not discarded during transmission,
configure forcible fragmentation.
The size of data frames is limited at the network layer. Therefore, a proper MTU is
a prerequisite for normal communication on a network.
● If the configured MTU is excessively small and the packet size is larger,
packets are discarded when being forwarded through the forwarding chip.
Packets are broken into a great number of fragments when being forwarded
through the CPU, affecting proper data transmission.
● If the size of packets exceeds the MTU supported by a transit node or a
receiver, the transit node or receiver fragments the packets or even discards
them, aggravating the network transmission load.
NOTE
The configured MTU takes effect for data packets on the control plane.
For S5732-H, S6730-H, S6730S-H, S6730-S, S6730S-S, S5731-H, S5731S-H, S5731-S, and
S5731S-S, the configured MTU takes effect for data packets on the forwarding plane only
after you run the ipv4 fragment enable command to enable packet fragmentation. The
configured MTU takes effect for GRE packets on the forwarding plane without the need to
execute the ipv4 fragment enable command. For other switches, the configured MTU does
not take effect for data packets on the forwarding plane.
Procedure
Step 1 Run system-view
----End
Context
Monitoring bandwidth usage helps you know current load on a device. If the
bandwidth usage exceeds a threshold, bandwidth resources are insufficient and
the device capacity needs to be expanded. For example, if the bandwidth usage
exceeds 95%, an alarm is generated, indicating that bandwidth resources are
almost exhausted. As a result, some services may be interrupted before device
capacity expansion.
You can configure two thresholds: low threshold (log threshold) and high
threshold (alarm threshold). The system generates a log when the bandwidth
usage exceeds the low threshold and generates an alarm when the bandwidth
usage exceeds the high threshold. This configuration ensures that you can expand
the device capacity in advance to avoid service interruptions caused by bandwidth
exhaustion.
As shown in Figure 2-6, the log threshold for bandwidth usage is 75% and alarm
threshold is 80%, and the interface bandwidth usage is collected at an interval of
1T.
● From 1T to 4T, the interface bandwidth usage is lower than the log threshold
75%. The system does not display any message.
● At 5T, the interface bandwidth usage reaches 75%. The system generates a
log to ask you whether to expand the device capacity.
● If you do not expand the device capacity, the interface bandwidth usage
reaches 80% at 6T. The system generates an alarm, indicating that the
bandwidth is almost exhausted and reminding you to take proper operations.
Procedure
Step 1 Run system-view
The default log threshold for inbound and outbound bandwidth usage on an
interface is 80%.
The default alarm threshold for inbound and outbound bandwidth usage on an
interface is 80%.
NOTE
To prevent logs and alarms from being frequently generated and cleared, set a large difference
between the values of bandwidth-in-use and resume-threshold.
----End
Procedure
Step 1 Run system-view
----End
Procedure
Step 1 Run system-view
The system view is displayed.
Context
Network congestion during service transmission may cause packet loss. If a lot of
packets are discarded, services are affected. To better monitor the number of
discarded packets, you can run the log-threshold { input-discard | output-
discard }* command in the system view to enable the log function for inbound
and outbound packet loss caused by congestion. The device generates a log when
the number of discarded incoming and outgoing packets on the interface in a
specified period exceeds the threshold. Logs help you know the congestion on the
interface. You can determine whether to increase the bandwidth or cancel the
bandwidth limit on the interface based on the logs. In this way, the congestion
problem can be solved.
Procedure
Step 1 Run system-view
The system view is displayed.
common optical interfaces, except that they are numbered in a different way. For
details about the numbering rule, see 1.1.2 Interface Numbering Rules.
NOTE
1-to-4 high-speed cable The cable provides fixed For details, see "Cables -
(or copper cable) optical modules that can High-Speed Cable" in
be directly installed on Hardware Description of
optical interfaces, a specified model.
lowering costs. The cable
length is fixed and the
maximum length is 5 m.
1-to-4 high-speed cable
models: QSFP-4SFP10G-
CU1M, QSFP-4SFP10G-
CU3M, and
QSFP-4SFP10G-CU5M
1-to-4 active optical The cable provides fixed For details, see "Cables -
cable (AOC) optical modules that can Optical Fiber" in
be directly installed on Hardware Description of
optical interfaces, a specified model.
lowering costs. The cable
length is fixed and the
maximum length is 10
m.
1-to-4 AOC model:
QSFP-4SFP10-AOC10M
1-to-4 40GE optical The local and remote For details, see
module + common 10GE interfaces can have a 1- "Pluggable Modules for
optical module + optical to-4 40GE optical Interfaces" in Hardware
fiber module and common Description of a specified
10GE optical modules model.
installed respectively and
be connected using a
dedicated 1-to-4 optical
fiber. The
communication distance
can be adjusted. The
optical fibers do not
provide optical modules
and the costs are high.
1-to-4 40GE optical
module models:
QSFP-40G-iSR4,
QSFP-40G-eSR4,
QSFP-40G-iSM4,
QSFP-40G-eSM4, and
CFP-40G-SR4
1-to-4 optical fiber
model: MPO-4*DLC
Common 40GE optical If the local and remote For details, see
module + optical fiber interfaces are both split "Pluggable Modules for
40GE interfaces, they Interfaces" in Hardware
can have the same 40GE Description of a specified
QSFP+ optical modules model.
installed and be
connected using an
optical fiber.
1-to-4 40GE optical
module models:
QSFP-40G-iSR4,
QSFP-40G-eSR4,
QSFP-40G-iSM4,
QSFP-40G-eSM4, and
CFP-40G-SR4
1-to-4 optical fiber
model: MPO-MPO
1-to-4 100GE optical The local and remote For details, see
module + common 25GE interfaces can have a 1- "Pluggable Modules for
optical module + optical to-4 100GE optical Interfaces" in Hardware
fiber module and common Description of a specified
25GE optical modules model.
installed respectively and
be connected using a
dedicated 1-to-4 optical
fiber. The
communication distance
can be adjusted. The
optical fibers do not
provide optical modules
and the costs are high.
1-to-4 100GE optical
modules: QSFP28-100G-
SR4, QSFP-100G-
CWDM4-Lite,
QSFP-100G-SWDM4,
and QSFP-100G-eSR4
1-to-4 optical fiber
model: MPO-4*DLC
NOTICE
Procedure
● Configuring Interface Split
– Splitting a 40GE interface into four 10GE interfaces
i. Run system-view
The system view is displayed.
ii. Run interface 40ge interface-number
The 40GE interface view is displayed.
iii. Run port split split-type 40GE:4*XGE
The 40GE interface is split into four 10GE interfaces.
By default, a 40GE interface is used as an independent interface.
After configuring interface split, save the configuration and restart the device to make
the configuration take effect.
● Configuring Interface Merge
– Merging four converted 10GE interfaces into a 40GE interface
i. Run system-view
The system view is displayed.
ii. Run interface xgigabitethernet interface-number
The view of a converted 10GE interface is displayed.
iii. Run undo port split
The four converted 10GE interfaces are merged into a 40GE
interface.
To merge converted interfaces, you only need to run this command
in the view of one converted interface.
– Merging four converted 25GE interfaces into a 100GE interface
i. Run system-view
The system view is displayed.
ii. Run interface 25ge interface-number
The view of any converted 25GE interface is displayed.
iii. Run undo port split
The four converted 25GE interfaces are merged into a 100GE
interface.
To merge converted interfaces, you only need to run this command
in the view of one converted interface.
NOTE
After configuring interface merge, save the configuration and restart the device to
make the configuration take effect.
----End
NOTE
On the S5732-H, S6730-H, and S6730S-H, only 25GE, 40GE, and 100GE interfaces support
this configuration.
On the S6730-S and S6730S-S, only 40GE interfaces support this configuration.
GE optical interfaces on the following models do not support this command: S5720-52X-
LI-24S-AC1, S5720-52X-LI-48S-AC1, S5720-52X-LI-48S-DC1, S5736-S24S4XC, S5736-
S48S4XC.
XGE optical interfaces on the following models support this command after they have GE
optical modules installed: S6735-S, S6720-EI, S6720S-EI.
Optical interfaces of other models support this command.
Note the following:
● A GE optical interface supports this command only when it works at the rate of 1000
Mbit/s.
● An XGE optical interface supports this command only when it has no optical module
installed or has an XGE optical module installed.
● A 25GE optical interface supports this command only when it has no optical module
installed or has a GE, XGE, or 25GE optical module installed.
● A 40GE optical interface supports this command only when it has no optical module
installed or has a 40GE optical module installed.
● A 100GE optical interface supports this command only when it has no optical module
installed or has a 40GE or 100GE optical module installed.
● The QSFP-40G-SR-BD, QSFP-40G-SDLC-PAM, QSFP-40G-LR4-Lite, QSFP-40G-LX4-MM,
and QSFP-40G-eSDLC-PAM optical modules do not support the single-fiber function.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run single-fiber enable
Unidirectional single-fiber communication is configured.
By default, unidirectional single-fiber communication is disabled.
----End
NOTE
● The training function can only be configured on the 40GE interfaces of the S6720-EI and
S6720S-EI.
● S5735S-H, S5731-H, S5731S-H24T4XC-A, S5731S-H48T4XC-A and S5736-S.
● When the ES5D21Q02Q00 or ES5D21Q04Q01 card is installed on these switches,
the training function can be configured on 40GE interfaces and is enabled by
default.
● When the S7C02000/S7Q02001 card is installed on these switches, the training
function cannot be configured.
● When the S7C02000/S7Q02001 card is connected to the ES5D21Q02Q00 or
ES5D21Q04Q01 card in a version earlier than V200R021C01 using a high-speed
cable, the 40GE interfaces on both ends cannot go Up. This issue does not exist
when the cards are connected using optical modules.
● When the S7C02000/S7Q02001 card is connected to the ES5D21Q02Q00 or
ES5D21Q04Q01 card in V200R021C01 or a later version using a high-speed cable,
the training function must be disabled on the 40GE interfaces of the
ES5D21Q02Q00 or ES5D21Q04Q01 card so that the 40GE interfaces at both ends
can go Up. This issue does not exist when the cards are connected using optical
modules.
● When high-speed cables are used for stack connections, the training function is
enabled by default on the ES5D21Q02Q00 or ES5D21Q04Q01 card in a version
earlier than V200R021C01. In V200R021C01 and later versions, the training
function is disabled by default, and the S7Q02001 card cannot connect to stack
interfaces in versions earlier than V200R021C01. This issue does not exist when
optical modules are used for stack connections.
● When a switch that is installed with the ES5D21Q02Q00 or ES5D21Q04Q01 card is
connected to S5732-H, S6730-S or S6730-H, the training function must be disabled
on 40GE interfaces, so that the 40G interfaces at both ends can go Up.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run training disable or undo training enable
The training function is disabled on the interface.
By default, the training function is enabled on an interface.
Precautions
● The training disable and undo training enable commands can be configured
on a 40GE interface only when the interface connects to a high-speed cable
and is not a physical member interface in a stack.
● After a cable is installed on a 40GE interface without the training disable
configuration, the training enable configuration is automatically generated
on the interface.
● If no cable is installed on an interface, only the training enable and undo
training disable commands can be configured on the interface.
● If the display this include-default command is run on an interface to view
the training configuration after a cable is installed on the interface, the
default training enable configuration is always displayed in the command
output and does not change with the training configuration change.
● The training configuration on an interface takes effect only after a cable is
installed on the interface. If the cable is replaced with an optical module, the
training disable and training enable configurations will be automatically
deleted from the interface.
● If a 40GE interface is configured as a physical member interface in a stack
system, the training disable and training enable configurations will be
automatically deleted from the interface.
● If a 40GE interface has been configured as a physical member interface in a
stack system, the training function is disabled on the interface by default and
cannot be enabled.
● If the training disable or undo training enable command is configured on a
40GE interface of the S6720S-26Q-EI-24S-AC or S6720S-26Q-EI-24S-DC after
a cable is installed on the interface, and the interface is connected to a
remote interface on which the training function is disabled or a remote
interface that does not support the training function, the two interfaces may
not go Up or go Up after a delay. Therefore, configure the training disable or
undo training enable command only when the training function is disabled
on the remote interface or the remote interface does not support the training
function. In other scenarios, it is recommended that you do not disable the
training function.
● If the training configuration does not exist on an interface of a switch running
V200R008C00 or an earlier version, the training disable configuration is
automatically generated on the interface after the system software is
upgraded to a version later than V200R009C00. If the training configuration
exists on the interface, the configuration remains unchanged after the system
software is upgraded to a version later than V200R009C00.
----End
NOTE
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run training disable or undo training enable
The training function is disabled on the interface.
By default, the training function is enabled on an interface.
Precautions
----End
Context
Low optical power on an Ethernet optical interface may cause problems such as
packet loss. Because the interface is still in Up state, traffic is still transmitted on
the interface even if a backup link is configured. To avoid impact on services, you
can configure the interface to change to the Error-down state when the optical
power is low. When the optical power on the interface falls below the lower alarm
threshold, the system disables the interface and records the interface status as
ERROR DOWN(transceiver-power-low) state (indicating that the interface is
Down because of low optical power). Services are then switched to the backup
link immediately.
Procedure
Step 1 Run system-view
The interface is configured to transit to the Error-down state when the optical
power is low.
By default, an interface does not transit to the Error-down state when the optical
power is low.
----End
Follow-up Procedure
An interface in Error-down state can be recovered using either of the following
methods:
● Manual recovery: If a few interfaces need to be recovered forcibly, run the
shutdown and undo shutdown commands in the interface view.
Alternatively, run the restart command in the interface view to restart the
interfaces.
● Automatic recovery: If a large number of interfaces need to be recovered,
manual recovery is time consuming and some interfaces may be omitted. You
can run the error-down auto-recovery cause transceiver-power-low
interval interval-value command in the system view to enable automatic
interface recovery and set the recovery delay time. An interface in Error-down
state automatically recovers when the specified delay time expires.
Context
Two types of twisted pair cables can be used to connect Ethernet devices:
● Straight-through cable: connects different types of devices, such as a switch
and a PC, or a switch and a router.
● Crossover cable: connects the same type of devices, such as two switches, two
routers, or two PCs.
Generally, if two interfaces are connected using a twisted pair cable, the transmit
and receive pins of one interface are respectively connected to the receive and
transmit pins of the other interface so that the link can be Up. Straight-through
and crossover cables have different pin assignments. Ethernet interfaces must
support negotiation and crossover of receive and transmit pins to adapt to the
cables connected to them. The device supports three medium dependent interface
(MDI) types: auto, normal, and across.
Generally, when two interfaces at both ends of a link use the auto type, they can
communicate regardless of whether a straight-through or crossover cable is used.
You need to manually set the MDI type to normal or across only when the device
cannot identify the network cable type. When configuring the MDI type on an
interface, pay attention to the following points:
● When a straight-through cable is used, configure different MDI types for the
local and remote interfaces. For example, configure the across type for one
interface and normal type for the other interface.
● When a crossover cable is used, configure the same MDI type for the local
and remote interfaces. For example, configure the across or normal type for
both interfaces or auto type for one interface.
NOTE
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The Ethernet interface view is displayed.
Step 3 Run mdi { across | auto | normal }
The MDI type is set for the Ethernet interface.
By default, an Ethernet interface uses the auto type and automatically identifies
the network cable type.
----End
Context
On a modern communications network, most telecommunications services require
that the frequency offset or time difference between devices be in an acceptable
range. When an XGE electrical interface on an ES5D21X08T00 card of a Huawei
device connects to a non-Huawei device, the clock negotiation mode of the XGE
electrical interface on the local device is auto-negotiation by default. The two
devices determine the master/slave relationship based on the negotiation result
and perform network clock synchronization. When the local device negotiates to
become the master device, the interfaces on both ends may fail to go Up or their
rate may decrease due to the impact of the non-Huawei device. In this case, run
the port clock-mode slave command to set the clock negotiation mode of the
XGE electrical interface of the local device to the slave mode. This configuration
ensures clock synchronization between the two devices.
NOTE
Only the XGE electrical interfaces of the ES5D21X08T00 cards support this function.
Procedure
1. Run system-view
The system view is displayed.
2. Run interface XGigabitEthernet interface-number
The XGE interface view is displayed.
3. Run port clock-mode slave
The clock negotiation mode of the XGE electrical interface is set to slave.
By default, the clock negotiation mode of an XGE electrical interface is the
auto-negotiation mode.
Context
During interface troubleshooting, you can view brief information about Ethernet
interfaces, including the physical status, auto-negotiation mode, duplex mode,
rate, and average inbound and outbound bandwidth usage of interfaces within the
latest period of time. The information helps you locate and rectify interface faults.
NOTE
To prevent existing traffic statistics from affecting fault cause analysis, you can run the reset
counters interface [ interface-type [ interface-number ] ] command to clear traffic statistics on
an interface, and then view brief information about Ethernet interfaces.
Procedure
● Run the display interface ethernet brief [ main ] command to view brief
information about Ethernet interfaces.
----End
Context
To monitor the status of an Ethernet interface or locate faults on the interface,
collect traffic statistics on the interface. Before collecting traffic statistics on an
Ethernet interface within a period, clear the existing traffic statistics on this
interface.
NOTICE
Traffic statistics cannot be restored after being cleared. Confirm your operation
before clearing them.
Procedure
● Run the reset counters interface [ interface-type [ interface-number ] ]
command to clear statistics on a specified interface.
● Run the reset counters if-mib interface [ interface-type [ interface-
number ] ] command to clear interface traffic statistics displayed on the NMS.
● Run the reset statistics-peak interface interface-type interface-number
command to clear peak rate statistics on an interface.
● Run the reset virtual-cable-test { interface-type interface-number | all }
command to clear virtual cable test results on an interface.
----End
# Run the clear configuration this command in the interface view to delete
configurations on GE0/0/1.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 0/0/1
[HUAWEI-GigabitEthernet0/0/1] clear configuration this
Warning: All configurations of the interface will be cleared, and its state will be shutdown. Continue? [Y/
N] :y
Info: Total 3 command(s) executed, 3 successful, 0 failed.
NOTE
After the configurations are deleted, the interface changes to shutdown state.
configured on GE0/0/1, the system generates pulse signals. After the pulse signals
reach the failure point, some energy is reflected to GE0/0/1. In this example, the
distance between SwitchA and the failure point is L, the period from sending pulse
signals to receiving reflected pulse signals is T, and the transmission rate of pulse
signals in the cable is V. The following formula is used to calculate the distance
between the failure point and GE0/0/1:
L = (V x T)/2
VCT detects the network cable fault type and identifies the failure point,
facilitating fault location on network cables.
NOTE
The MEth management interfaces of the following devices support this function: S5731-S,
S5731S-S, S5731-H, S5731S-H, S5732-H, S6730-S, S6730S-S, S6730-H, S6730S-H, S6735-S
Service interfaces on the following devices do not support this function:
● MultiGE interfaces on the S5720-28X-PWH-LI-AC and S5736-S24UM4XC
● XGE electrical interfaces on the ES5D21X08T00 card
For the S5731-S24N4X2Q-A, S5731-S24UN4X2Q, S5731-S8UM16UN2Q, S5731S-
S24N4X2Q-A1, S5731S-S24UN4X2Q-A, S5731S-S8UM16UN2Q-A, S5732-H24UM2CC (part
number: 02353SJY-020, 02353SJY-021, 02353SJY-024), and S5732-H48UM2CC (part
number: 02353SJT-020, 02353SJT-021, 02353SJT-023, 02353SJT-024), if the MultiGE
interface is configured to work in auto-negotiation mode, and the peer interface is set to
100 Mbit/s, the local check result obtained using the virtual-cable-test command is
inaccurate.
Procedure
Step 1 Run system-view
VCT is configured.
NOTE
● The test result is only for reference and may be inaccurate for cables of some vendors.
● If the detection result is Unknown, you are advised to use the cable analyzer to perform
the test.
● The test result is related to the cable signal attenuation. When the cable length is
shorter than 3 m, the cable signal attenuation mostly is resulted from the connector, not
the cable. The test result is therefore inaccurate.
● Running the virtual-cable-test command may affect services on the interface in a short
period of time, and the interface in Up state may alternate between Up and Down.
● Combo electrical interfaces support cable tests, but cable tests are not recommended on
combo electrical interfaces because services will be interrupted.
● This command can be used on an XGE optical interface or GE optical interface when the
interface has a GE copper module installed.
● After a 25GE optical interface is configured to work at the rate of 1 Gbit/s using the
port mode ge command and has a GE copper module installed, the virtual-cable-test
command can be configured on the interface.
● When a GE electrical interface on the S5720-LI, S2730S-S, S5735-L-I, S5735-L1, S300,
S5735-L, S5735S-L1, S5735S-L, S5735S-L-M, S5720S-LI, S5735S-H, S5736-S, S500,
S5735-S, S5735S-S, S5735-S-I, and S5720I-SI works at a rate of 1000 Mbit/s or 100
Mbit/s and the interface is up, the detection result is inaccurate.
● On the S6720S-EI, S5732-H, S6730-H, S6730S-H, S6730-S, S6730S-S, S6735-S, and
S6720-EI, when a GE electrical interface works at a rate of 100 Mbit/s, the detection
result is inaccurate.
● On the S5731-H, S5731S-H, S5731-S, and S5731S-S, when a GE electrical interface
works at a rate of 10 Mbit/s, 100 Mbit/s, or 1000 Mbit/s and the interface is up, the
detection result is inaccurate.
● The test result is inaccurate when the interface is in the Up state or the remote interface
is shut down.
● An FE electrical port uses only two pairs of wire pairs. The test result of the two pairs of
wire pairs that are not used during the VCT test is inaccurate.
● When a GE electrical port works at a rate of 10 Mbit/s or 100 Mbit/s, only two pairs of
cables are used to detect the VCT status. The other two pairs of cables do not detect or
return the default result.
● The virtual cable test (VCT) cannot be performed on multiple interfaces of the device at
the same time.
----End
Context
The network cable quality check allows you to locate network cable quality
problems and take corresponding measures promptly, avoiding packet loss and its
impact on services.
NOTE
This function is supported only on the XGE electrical interfaces on the ES5D21X08T00 card
of the S5731-H, and S5731S-H, GE electrical interfaces on the S5731-H, S2730S-S, S5735-L-
I, S5735-L1,S300, S5735-L, S5735S-L1, S5735S-L, S5735S-L-M, S5735-S (except the S5735-
S48S4X), S500, S5735S-S, S5735-S-I, S5720I-SI, and and MultiGE electrical interfaces on the
S5720-28X-PWH-LI-AC, S5720-28X-PWH-LI-ACF, S5732-H24UM2CC, S5732-H48UM2CC,
S5732-H48XUM2CC, S5736-S24UM4XC.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run cable-snr-test
The network cable quality check is configured.
NOTE
● This command checks real-time quality of the network cable on an interface, and the
network cable quality changes with the external environment.
● A MultiGE electrical interface supports accurate network cable quality check only when
it works at the rate of 2.5 Gbit/s or higher.
● An XGE electrical interface supports accurate network cable quality check only when it
works at the rate of 10 Gbit/s.
● A GE electrical interface supports accurate network cable quality check only when it
works at the rate of 1 Gbit/s.
● An interface does not support the network cable quality check when it is Down or in
loopback detection mode.
● After the interface goes Up, wait for several minutes before running this command.
Otherwise, the command fails to be delivered.
----End
Context
When testing some special functions, for example, locating an Ethernet fault, you
need to enable loopback detection on Ethernet interfaces to check whether the
interfaces are working properly. After loopback detection is enabled on an
Ethernet interface, the interface is in Up state if it works properly, and is in Down
state if it fails.
In internal loopback detection, a packet from an interface is sent back to the
interface through the internal chip. Internal loopback detection checks whether
the connection between the interface and internal chip is normal. In external
loopback detection, a packet from an interface is sent back to the interface
through a loopback connector. External loopback detection checks whether the
interface properly sends and receives packets. Currently, the device supports only
NOTICE
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run loopback internal
Internal loopback detection is configured on the Ethernet interface.
By default, internal loopback detection is disabled on an Ethernet interface.
----End
NOTE
After loopback detection is enabled on an interface, the Speed field in the display this
interface command output indicates the configured interface rate or the rate of the
installed optical module, copper module, or network cable, and the Bandwidth field in the
display interface ethernet brief command output indicates the actual interface rate.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run set log updown disable
The log function for interface up/down changes is disabled.
By default, the log function for interface up/down changes is enabled.
----End
Figure 2-10 Networking diagram for configuring the working mode of a combo
interface
Configuration Roadmap
The configuration roadmap is as follows:
● Configure the combo interface to work as an electrical interface. This
configuration ensures that the combo interface's working mode does not
change when the transmission medium changes, for example, a GE copper
module is installed.
Procedure
Step 1 Configure the combo interface GE0/0/4 to work as an electrical interface.
<HUAWEI> system-view
[HUAWEI] sysname Switch
[Switch] interface gigabitethernet 0/0/4
[Switch-GigabitEthernet0/0/4] combo-port copper
[Switch-GigabitEthernet0/0/4] quit
The command output shows that the combo interface works as an electrical
interface.
----End
Configuration File
Configuration file of the Switch
#
sysname Switch
#
interface GigabitEthernet0/0/4
combo-port copper
#
return
Figure 2-11 Networking diagram for configuring the rate and duplex mode in
non-auto-negotiation mode
Configuration Roadmap
The configuration roadmap is as follows:
Procedure
Step 1 Create a port group and add GE0/0/1, GE0/0/2, and GE0/0/3 to the port group.
<HUAWEI> system-view
[HUAWEI] sysname Switch
[Switch] port-group portgroup1
[Switch-port-group-portgroup1] group-member gigabitethernet 0/0/1 to gigabitethernet 0/0/3
The command output shows that the interface works in non-negotiation mode,
the rate is 100 Mbit/s, and the duplex mode is full-duplex.
Similarly, run the display interface GigabitEthernet 0/0/2 and display interface
GigabitEthernet 0/0/3 commands on GE0/0/2 and GE0/0/3 respectively to check
interface working information.
----End
Configuration File
Configuration file of the Switch
#
sysname Switch
#
interface GigabitEthernet0/0/1
undo negotiation auto
speed 100
#
interface GigabitEthernet0/0/2
undo negotiation auto
speed 100
#
interface GigabitEthernet0/0/3
undo negotiation auto
speed 100
#
port-group portgroup1
group-member GigabitEthernet0/0/1
group-member GigabitEthernet0/0/2
group-member GigabitEthernet0/0/3
#
return
Networking Requirements
In Figure 2-12, PC1, PC2, and PC3 are on three network segments, and SwitchC,
SwitchD, and SwitchE are access switches for the three network segments,
respectively. To enable SwitchA and SwitchB to communicate with each other and
provide high link bandwidth, Layer 3 Eth-Trunk interfaces need to be used
between SwitchA and SwitchB. In addition, three physical Ethernet interfaces on
SwitchB need to be used as gateway interfaces for the three network segments.
NOTE
Only interfaces on the following models support switching between Layer 2 and Layer 3
modes: S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6735-S, S6720-EI, S6720S-EI,
S6730-H, S6730S-H, S6730-S and S6730S-S.
Figure 2-12 Configuring the rate and duplex mode in non-auto-negotiation mode
Configuration Roadmap
The configuration roadmap is as follows:
● Switch interfaces to Layer 3 mode.
● Configure the IP addresses of Layer 3 Ethernet interfaces as gateway
addresses.
Procedure
Step 1 Switch the interface working mode to Layer 3.
# Switch a single interface to Layer 3 mode.
<HUAWEI> system-view
[HUAWEI] sysname SwitchB
[SwitchB] interface gigabitethernet 0/0/1
[SwitchB-GigabitEthernet0/0/1] undo portswitch
[SwitchB-GigabitEthernet0/0/1] quit
The command output shows that the interface works in Layer 3 mode.
----End
Configuration Files
SwitchB configuration file
#
sysname SwitchB
#
interface Eth-Trunk1
undo portswitch
ip address 10.10.4.1 255.255.255.0
#
interface GigabitEthernet0/0/1
undo portswitch
ip address 10.10.1.1 255.255.255.0
#
interface GigabitEthernet0/0/2
undo portswitch
ip address 10.10.2.1 255.255.255.0
#
interface GigabitEthernet0/0/3
undo portswitch
ip address 10.10.3.1 255.255.255.0
#
interface GigabitEthernet0/0/4
eth-trunk 1
#
interface GigabitEthernet0/0/5
eth-trunk 1
#
return
Troubleshooting Procedure
1. Check whether the devices are powered on, and the interface modules and
the link between the interfaces work properly.
If the two devices are connected by a twisted pair, check the following items.
Item Expected Result Follow-up Procedure
Twisted pair The tester shows that the If the twisted pair is faulty,
working status twisted pair works properly. replace it.
Twisted pair The twisted pair length is If the twisted pair length
length less than 100 m. exceeds 100 m, perform
NOTE either of the following
The 10/100/1000M electrical operations:
interfaces use RJ45
● Shorten the distance
connectors and twisted pairs
higher than Category 5. The between the two
maximum transmission devices.
distance of such cables is 100 ● If the distance between
m.
the two devices cannot
be shortened, deploy a
repeater, hub, or switch
between the devices.
Twisted pair Twisted pair cables are If the twisted pair type is
type classified into straight- incorrect, replace the
through cables and twisted pair.
crossover cables.
A straight-through cable
connects Ethernet
interfaces between the
following devices:
● A router and a hub
● A router and an
Ethernet switch
● A computer and an
Ethernet switch
● A computer and a hub
A crossover cable connects
Ethernet interfaces
between the following
devices:
● Two routers
● A router and a
computer
● Two hubs
● A hub and a switch
● Two switches
● Two computers
If the two devices are connected by optical fibers, check the following items.
Types of optical The optical fiber type If the optical fiber type
modules and matches the optical does not match the optical
optical fibers module type. For details module type, replace the
about mappings between optical module or optical
optical modules and fiber.
optical fibers, see
"Pluggable Modules for
Interfaces - Important
Notes About Using Optical
Modules Certified for
Huawei Switches" in
Hardware Description of a
specified model.
Determine whether the
optical fiber type matches
the optical module type
according to the following
information:
● A multimode optical
fiber can be used
together with a
multimode optical
module.
● A single-mode optical
fiber can only be used
with a single-mode
optical module.
Generally, a single-mode
optical fiber is yellow,
and a multimode optical
fiber is orange.
● Two connected optical
modules must have the
same wavelength.
Optical fiber The optical fiber length If the optical fiber length
length and must be shorter than the exceeds the maximum
maximum maximum transmission transmission distance of
transmission distance of an optical the optical modules,
distance of module. For the maximum shorten the distance
optical modules transmission distance between the devices or use
supported by different optical modules with a
optical modules, see longer transmission
"Pluggable Modules for distance.
Interfaces - Important
Notes About Using Optical
Modules Certified for
Huawei Switches" in
Hardware Description of a
specified model.
Optical signal The tester shows that the If the attenuation is high,
attenuation optical signal attenuation replace the optical fibers. If
is in the allowed range. For the fault persists, shorten
the attenuation range, see the distance between the
"Pluggable Modules for devices and use shorter
Interfaces - Important optical fibers.
Notes About Using Optical
Modules Certified for
Huawei Switches" in
Hardware Description of a
specified model.
Run the display interface command on the two interfaces to check their
rates, duplex modes, and auto-negotiation modes.
Troubleshooting Procedure
1. Check whether the interface modules and the link between the interfaces
work properly.
If the two devices are connected by a twisted pair, check the following items.
Item Expected Result Follow-up Procedure
Twisted pair The tester shows that the If the twisted pair is faulty,
working status twisted pair works properly. replace it.
Twisted pair The twisted pair length is If the twisted pair length
length less than 100 m. exceeds 100 m, perform
NOTE either of the following
The 10/100/1000M electrical operations:
interfaces use RJ45
● Shorten the distance
connectors and twisted pairs
higher than Category 5. The between the two
maximum transmission devices.
distance of such cables is 100 ● If the distance between
m.
the two devices cannot
be shortened, deploy a
repeater, hub, or switch
between the devices.
If the two devices are connected by optical fibers, check the following items.
Item Expected Result Follow-up Procedure
Types of optical The optical fiber type If the optical fiber type
modules and matches the optical does not match the optical
optical fibers module type. For details module type, replace the
about mappings between optical module or optical
optical modules and fiber.
optical fibers, see
"Pluggable Modules for
Interfaces - Important
Notes About Using Optical
Modules Certified for
Huawei Switches" in the
Hardware Description of a
specified model.
Optical fiber The optical fiber length If the optical fiber length
length and must be shorter than the exceeds the maximum
maximum maximum transmission transmission distance of
transmission distance of an optical the optical modules,
distance of module. For the maximum shorten the distance
optical modules transmission distance between the devices or use
supported by different optical modules with a
optical modules, see longer transmission
"Pluggable Modules for distance.
Interfaces - Important
Notes About Using Optical
Modules Certified for
Huawei Switches" in the
Hardware Description of a
specified model.
Optical signal The tester shows that the If the attenuation is high,
attenuation optical signal attenuation replace the optical fibers. If
is in the allowed range. For the fault persists, shorten
the attenuation range, see the distance between the
"Pluggable Modules for devices and use shorter
Interfaces - Important optical fibers.
Notes About Using Optical
Modules Certified for
Huawei Switches" in the
Hardware Description of a
specified model.
The command output shows that internal loopback detection is enabled on the
interface.
In V200R005C00 and later versions, run the undo portswitch command changes
the working mode of Ethernet interfaces from Layer 2 mode to Layer 3 mode.
Ethernet interfaces working at Layer 3 support IP address configuration.
● Eth-Trunk
An Eth-Trunk has Layer 2 and Layer 3 features and is formed by binding
multiple Ethernet interfaces to provide more bandwidth and higher
transmission reliability. For details about how to configure an Eth-Trunk, see
Link Aggregation Configuration in the S300, S500, S2700, S5700, and S6700
V200R023C00 Configuration Guide - Ethernet Switching.
● Tunnel interface
A tunnel interface has Layer 3 features, transmits packets, and identifies and
processes packets transmitted over a tunnel.
● VLANIF interface
A VLANIF interface has Layer 3 features, and enables VLANs to communicate
and can have Layer 3 services deployed after being assigned an IP address.
For details about how to configure a VLANIF interface, see Configuration
Examples in "VLAN Configuration" in the S300, S500, S2700, S5700, and
S6700 V200R023C00 Configuration Guide - Ethernet Switching.
● Ethernet sub-interface
Ethernet sub-interfaces are multiple logical interfaces configured on a main
interface to allow the main interface to communicate with multiple remote
interfaces. Ethernet sub-interfaces can share physical layer parameters of their
main interface, or be configured with their respective link layer parameters
and network layer parameters. Disabling or activating Ethernet sub-interfaces
does not affect the main interface status, but the main interface status
change affects the status of Ethernet sub-interfaces. Ethernet sub-interfaces
work properly only when their main interface is in Up state.
▪ Once a loopback interface is created, its physical status and data link
protocol status always stay Up, regardless of whether an IP address is
configured for the loopback interface.
● NVE interface
An NVE interface is a logical interface used to establish a VXLAN tunnel with
another NVE device. For details about how to configure an NVE interface, see
S300, S500, S2700, S5700, and S6700 V200R023C00 Configuration Guide -
VXLAN Configuration.
● VBDIF interface
A VBDIF interface is a virtual interface based on a bridge domain and
supporting Layer 3 features. VBDIF interfaces implement communication
between BDs, between BD and non-BD networks, and between BD and Layer
3 networks. For details about how to configure a VBDIF interface, see S300,
S500, S2700, S5700, and S6700 V200R023C00 Configuration Guide - VXLAN
Configuration.
● VE interface
A VE interface is used when other data link layer protocols need to be carried
by the Ethernet protocol. A VE sub-interface can be created to allow an
L2VPN to access to an L3VPN.
Licensing Requirements
A logical interface is a basic feature of a switch and is not under license control.
NOTE
For details about software mappings, visit Hardware Center and select the desired product
model.
The S5731-L and S5731S-L are remote units and do not support web-based management,
YANG, or commands. They can be configured only through configuration delivery by the
central device. For details, see "Simplified Architecture Configuration (the Solar System
Solution)" in the S300, S500, S2700, S5700, and S6700 V200R023C00 Configuration Guide -
Device Management.
Feature Limitations
● For Layer 2 interfaces, only hybrid and trunk interfaces support Ethernet sub-
interface configuration. After a Layer 2 interface is switched to a Layer 3
interface using the undo portswitch command, the interface supports Layer 3
Ethernet sub-interface configuration.
● After an interface is added to an Eth-Trunk, you can only configure sub-
interfaces on the Eth-Trunk, but not on the interface.
Procedure
Step 1 Run system-view
The delay after which the VLANIF interface goes Down is set.
By default, the delay is 0 seconds, that is, a VLANIF interface goes Down
immediately after the corresponding VLAN goes Down.
Setting a delay after which a VLANIF interface goes Down prevents network
flapping caused by status change of the VLANIF interface. This function is also
called VLAN damping.
Enable the VLAN damping function on the VLANIF interface. After the last
member interface in Up state in the corresponding VLAN goes Down, the VLAN
damping-enabled device reports the VLAN Down event to the VLANIF interface
after the configured delay. If a member interface in the VLAN goes Up during the
delay, the VLANIF interface remains in Up state.
----End
NOTE
● Only the S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6735-S, S6720-EI, S6720S-
EI, S6730-H, S6730S-H, S6730-S, and S6730S-S support Ethernet sub-interfaces.
● Only hybrid and trunk interfaces on the preceding switches support Layer 2 Ethernet
sub-interface configuration.
● After you run the undo portswitch command to switch Layer 2 interfaces on the
preceding series of switches into Layer 3 interfaces, you can configure Layer 3 Ethernet
sub-interfaces on the interfaces.
● After an interface is added to an Eth-Trunk, sub-interfaces cannot be configured on the
interface.
● VLAN termination sub-interfaces cannot be created on a VCMP client.
Pre-configuration Tasks
Before configuring an Ethernet sub-interface, properly connect the physical
interface of the Ethernet sub-interface.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number.subinterface-number [ mode l2 ]
The Ethernet sub-interface view is displayed.
subinterface-number specifies the number of an Ethernet sub-interface. mode l2
indicates that the sub-interface is configured to work in Layer 2 mode for the
VXLAN service. You need to specify this parameter only when configuring the
VXLAN service.
Step 3 Configure an Ethernet sub-interface to transmit services based on the service type.
● Layer 2 Ethernet sub-interface
– When configuring a Layer 2 sub-interface, you only need to configure a
sub-interface for termination.
VLAN packets are classified into Dot1q packets (one layer of VLAN tag)
and QinQ packets (double layers of tags). Accordingly, there are two
VLAN tag termination modes. Dot1q termination terminates Dot1q
packets and QinQ termination terminates QinQ packets. Run either of
the following commands to configure a sub-interface for termination
based on site requirements.
Specify the sub parameter when you need to configure a secondary IP address
for the sub-interface.
b. Configure a sub-interface for termination.
VLAN packets are classified into Dot1q packets (one layer of VLAN tag)
and QinQ packets (double layers of tags). Accordingly, there are two
VLAN tag termination modes. Dot1q termination terminates Dot1q
packets and QinQ termination terminates QinQ packets. Run either of
the following commands to configure a sub-interface for termination
based on site requirements.
When you enable or disable the ARP broadcast function on a sub-interface, the
routing status of the sub-interface becomes Down and then Up. This result in flapping
of routes on the entire network, affecting the normal operation of services.
● Layer 3 Ethernet sub-interface (IPv6)
a. Configure a sub-interface for termination.
VLAN packets are classified into Dot1q packets (one layer of VLAN tag)
and QinQ packets (double layers of tags). Accordingly, there are two
VLAN tag termination modes. Dot1q termination terminates Dot1q
packets and QinQ termination terminates QinQ packets. Run either of
the following commands to configure a sub-interface for termination
based on site requirements.
----End
interfaces configured with dot1q VLAN tag termination and the sub-interface
configuration.
● Run the display qinq information termination [ interface interface-type
interface-number [.subinterface-number ] ] command to check names of all
interfaces configured with QinQ VLAN tag termination and the sub-interface
configuration.
Pre-Configuration
Before configuring a loopback interface, power on the device and perform self-
check.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface loopback loopback-number
A loopback interface is created and the loopback interface view is displayed.
You can create or delete a loopback interface dynamically. After a loopback
interface is created, the link-layer protocol is always Up unless the loopback
interface is deleted.
Step 3 Run ip address ip-address { mask | mask-length } [ sub ]
The IP address of the loopback interface is configured.
----End
Context
A NULL0 interface is created automatically. The NULL0 interface is always Up and
cannot forward packets. Any packets sent to the NULL0 interface are discarded. If
the next hop of a static route to a network segment is a NULL interface, all the
data packets destined for this network segment are discarded. Therefore, the
packets that you want to filter out can be sent to the NULL0 interface directly
without configuring the access control list.
For example, run the following static route configuration command to discard
packets sent to the network segment of 192.168.0.0/24.
[HUAWEI] ip route-static 192.168.0.0 255.255.255.0 NULL 0
Pre-configuration Tasks
Before configuring a NULL interface, power on the device and perform self-check.
Procedure
Step 1 Run system-view
The NULL interface stays in Up state. It cannot forward data packets. You cannot
configure an IP address for it or encapsulate it with protocols.
----End
Only the S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6730-H, S6730S-H, S6730-S, and
S6730S-S support VE interface configuration.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface virtual-ethernet ve-number
A VE interface is created and the VE interface view is displayed.
Step 3 Configure a VE interface based on actual requirements.
● Configure the VE interface to work in Layer 2 mode.
Run portswitch
The working mode of the VE interface is changed from Layer 3 mode to Layer
2 mode.
By default, a VE interface works in Layer 3 mode.
● Configure a VE sub-interface.
You need to create a VE sub-interface when configuring an L2VPN to access
to an L3VPN.
a. Run ve-group ve-group-id { l2-terminate | l3-access }
A Layer 2 or Layer 3 VE interface is created.
b. Run quit
Return to the system view.
c. Run interface virtual-ethernet ve-number.subnumber
A VE sub-interface is created and the VE sub-interface view is displayed.
----End