- Table of Contents
-
- 03-Layer 2—LAN Switching Command Reference
- 00-Preface
- 01-MAC address table commands
- 02-Bulk interface commands
- 03-Ethernet interface commands
- 04-Ethernet link aggregation commands
- 05-M-LAG commands
- 06-Port isolation commands
- 07-VLAN commands
- 08-MVRP commands
- 09-Loopback, null, and inloopback interface commands
- 10-QinQ commands
- 11-VLAN mapping commands
- 12-Loop detection commands
- 13-Spanning tree commands
- 14-LLDP commands
- 15-L2PT commands
- 16-Service loopback group commands
- 17-Layer 2 forwarding commands
- Related Documents
-
Title | Size | Download |
---|---|---|
03-Ethernet interface commands | 621.85 KB |
Contents
Common Ethernet interface commands
display link-state-change statistics interface
interface default-description output
loadbalance ecmp rail-group enable
loadbalance link-aggregation rail-group enable
port transceiver-power-low trigger
reset link-state-change statistics interface
shutdown all-physical-interface
shutdown-interval transceiver-power-low
snmp-agent trap enable ifmonitor
Layer 2 Ethernet interface commands
Layer 3 Ethernet interface or subinterface commands
Ethernet interface commands
Common Ethernet interface commands
bandwidth
Use bandwidth to set the expected bandwidth of an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) is the interface baud rate divided by 1000.
Views
Ethernet interface view
Ethernet subinterface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth is an informational parameter used only by higher-layer protocols for calculation. You cannot adjust the actual bandwidth of an interface by using this command.
Examples
# Set the expected bandwidth of HundredGigE 1/0/1 to 1000 kbps.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] bandwidth 1000
# Set the expected bandwidth of HundredGigE 1/0/1.1 to 1000 kbps.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1.1
[Sysname-HundredGigE1/0/1.1] bandwidth 1000
Related commands
speed
broadcast-suppression
Use broadcast-suppression to enable broadcast suppression and set the broadcast suppression threshold.
Use undo broadcast-suppression to disable broadcast suppression.
Syntax
broadcast-suppression { ratio | pps max-pps | kbps max-kbps }
undo broadcast-suppression
Default
Ethernet interfaces do not suppress broadcast traffic.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
ratio: Sets the broadcast suppression threshold as a percentage of the interface bandwidth. The value range for this argument is 0 to 100. A smaller value means that less broadcast traffic is allowed to pass through.
pps max-pps: Specifies the maximum number of broadcast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.
kbps max-kbps: Specifies the maximum number of kilobits of broadcast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.
Usage guidelines
The broadcast storm suppression features limits the size of broadcast traffic to a threshold on an interface. When the broadcast traffic on the interface exceeds this threshold, the system drops packets until the traffic drops below this threshold.
Both the storm-constrain command and the broadcast-suppression command can suppress broadcast storms on a port. The broadcast-suppression command uses the chip to physically suppress broadcast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress broadcast traffic.
For the traffic suppression result to be determined, do not configure both the storm-constrain broadcast command and the broadcast-suppression command on an interface.
When you configure the suppression threshold in kbps, the actual suppression threshold might be different from the configured one as follows:
· If the configured value is smaller than 64, the value of 64 takes effect.
· If the configured value is greater than 64 but not an integer multiple of 64, the integer multiple of 64 that is greater than and closest to the configured value takes effect.
To determine the suppression threshold that takes effect, see the prompts on the switch.
Set the same type of thresholds for each interface, that is, set the ratio argument, the pps max-pps option, or the kbps max-kbps option for the interface.
Examples
# Set the broadcast suppression threshold to 10000 kbps on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] broadcast-suppression kbps 10000
The actual value is 10048 on port HundredGigE1/0/1 currently.
The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.
Related commands
multicast-suppression
unicast-suppression
dampening
Use dampening to enable the device to dampen an interface when the interface is flapping.
Use undo dampening to restore the default.
Syntax
dampening [ half-life reuse suppress max-suppress-time ]
undo dampening
Default
Interface dampening is disabled on Ethernet interfaces.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
half-life: Specifies the amount of time after which a penalty is decreased, in the range of 1 to 120 seconds. The default value is 54 seconds.
reuse: Specifies the reuse threshold in the range of 200 to 20000. The default value is 750. The reuse threshold must be less than the suppression threshold.
suppress: Specifies the suppression threshold in the range of 200 to 20000. The default value is 2000.
max-suppress-time: Specifies the maximum amount of time the interface can be dampened, in the range of 1 to 255 seconds. The default value is 162 seconds (three times the half-life timer).
Usage guidelines
When configuring the dampening command, follow these rules to set the values mentioned above:
· The ceiling is equal to 2 (Max-suppress-time/Decay) × reuse-limits. It is not user configurable.
· The configured suppress limit is lower than or equal to the ceiling.
· The ceiling is lower than or equal to the maximum suppress limit supported.
This command, the link-delay command, and the port link-flap protect enable command are mutually exclusive on an interface.
This command does not take effect on the administratively down events. When you execute the shutdown command, the penalty restores to 0, and the interface reports the down event to the higher layer protocols.
Do not enable the dampening function on an interface with RRPP, MSTP, or Smart Link enabled.
After an interface in down state is dampened, the interface state displayed through the display interface command is always down.
Examples
# Enable interface dampening on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] dampening
# Enable interface dampening on HundredGigE 1/0/1, and set the following parameters:
· Half life time to 2 seconds.
· Reuse value to 800.
· Suppression threshold to 3000.
· Maximum suppression interval to 5 seconds.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] dampening 2 800 3000 5
Related commands
display interface
link-delay
port link-flap protect enable
default
Use default to restore the default settings for an interface.
Syntax
default
Views
Ethernet interface view
Ethernet subinterface view
Predefined user roles
network-admin
Usage guidelines
CAUTION: The default command might interrupt ongoing network services. Make sure you are fully aware of the impacts of this command when you use it in a live network. |
This command might fail to restore the default settings for some commands because of command dependencies or system restrictions. You can use the display this command in interface view to identify these commands, and use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to solve the problem.
Examples
# Restore the default settings for HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] default
# Restore the default settings for HundredGigE 1/0/1.1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1.1
[Sysname-HundredGigE1/0/1.1] default
description
Use description to configure the description of an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of an interface is the interface name plus Interface (for example, HundredGigE1/0/1 Interface).
Views
Ethernet interface view
Ethernet subinterface view
Predefined user roles
network-admin
Parameters
text: Specifies the interface description, a case-sensitive string of 1 to 255 characters.
Examples
# Set the description of HundredGigE 1/0/1 to lan-interface.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] description lan-interface
# Set the description of HundredGigE 1/0/1.1 to subinterface1/0/1.1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1.1
[Sysname-HundredGigE1/0/1.1] description subinterface1/0/1.1
display counters
Use display counters to display interface traffic statistics.
Syntax
display counters { inbound | outbound } interface [ interface-type [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
inbound: Displays inbound traffic statistics.
outbound: Displays outbound traffic statistics.
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
Usage guidelines
To clear the Ethernet interface traffic statistics, use the reset counters interface command.
If you do not specify an interface type, this command displays traffic statistics for all interfaces that have traffic counters.
If you specify an interface type but do not specify an interface number, this command displays traffic statistics for all interfaces of the specified type.
If you specify an interface type and number, this command displays traffic statistics for the specified interface.
Examples
# Display inbound traffic statistics for all interfaces.
<Sysname> display counters inbound interface
Interface Total (pkts) Broadcast (pkts) Multicast (pkts) Err (pkts)
HGE1/0/1 100 100 0 0
HGE1/0/2 Overflow Overflow Overflow Overflow
Overflow: More than 14 digits (7 digits for column "Err").
--: Not supported.
Table 1 Command output
Field |
Description |
Interface |
Abbreviated interface name. |
Total (pkts) |
Total number of packets received or sent through the interface. |
Broadcast (pkts) |
Total number of broadcast packets received or sent through the interface. |
Multicast (pkts) |
Total number of multicast packets received or sent through the interface. |
Err (pkts) |
Total number of error packets received or sent through the interface. |
Overflow: More than 14 digits (7 digits for column "Err") |
The command displays Overflow when any of the following conditions exist: · The data length of an Err field value is greater than 7 decimal digits. · The data length of a non-Err field value is greater than 14 decimal digits. |
--: Not supported |
The statistical item is not supported. |
Related commands
reset counters interface
display counters rate
Use display counters rate to display traffic rate statistics for interfaces in up state for the most recent statistics polling interval.
Syntax
display counters rate { inbound | outbound } interface [ interface-type [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
inbound: Displays inbound traffic rate statistics.
outbound: Displays outbound traffic rate statistics.
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
Usage guidelines
If you do not specify an interface type, this command displays traffic rate statistics for all up interfaces that have traffic counters.
If you specify an interface type but do not specify an interface number, this command displays traffic rate statistics for all up interfaces of the specified type.
If you specify an interface type and an interface, this command displays traffic rate statistics for the specified interface.
If an interface that you specify is always down for the most recent statistics polling interval, the system prompts that the interface does not support the command.
To set the statistics polling interval, use the flow-interval command.
Examples
# Display the inbound traffic rate statistics for all interfaces.
<Sysname> display counters rate inbound interface
Usage: Bandwidth utilization in percentage
Interface Usage (%) Total (pps) Broadcast (pps) Multicast (pps)
HGE1/0/1 0 0 -- --
Overflow: More than 14 digits.
--: Not supported.
Table 2 Command output
Field |
Description |
Interface |
Abbreviated interface name. |
Usage (%) |
Bandwidth usage (in percentage) of the interface for the last statistics polling interval. |
Total (pps) |
Average receiving or sending rate (in pps) for unicast packets for the last statistics polling interval. |
Broadcast (pps) |
Average receiving or sending rate (in pps) for broadcast packets for the last statistics polling interval. |
Multicast (pps) |
Average receiving or sending rate (in pps) for multicast packets for the last statistics polling interval. . |
Overflow: more than 14 decimal digits |
The command displays Overflow if the data length of a statistical item is greater than 14 decimal digits. |
--: not supported |
The statistical item is not supported. |
Related commands
flow-interval
reset counters interface
display ethernet statistics
Use display ethernet statistics to display the Ethernet module statistics.
Syntax
display ethernet statistics slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID.
Examples
# Display the Ethernet module statistics for the specified slot.
<Sysname> display ethernet statistics slot 1
ETH receive packet statistics:
Totalnum : 10447 ETHIINum : 4459
SNAPNum : 0 RAWNum : 0
LLCNum : 0 UnknownNum : 0
ForwardNum : 4459 ARP : 0
MPLS : 0 ISIS : 0
ISIS2 : 0 IP : 0
IPV6 : 0
ETH receive error statistics:
NullPoint : 0 ErrIfindex : 0
ErrIfcb : 0 IfShut : 0
ErrAnalyse : 5988 ErrSrcMAC : 5988
ErrHdrLen : 0
ETH send packet statistics:
L3OutNum : 211 VLANOutNum : 0
FastOutNum : 155 L2OutNum : 0
ETH send error statistics:
MbufRelayNum : 0 NullMbuf : 0
ErrAdjFwd : 0 ErrPrepend : 0
ErrHdrLen : 0 ErrPad : 0
ErrQoSTrs : 0 ErrVLANTrs : 0
ErrEncap : 0 ErrTagVLAN : 0
IfShut : 0 IfErr : 0
Table 3 Output description
Field |
Description |
ETH receive packet statistics |
Statistics about the Ethernet packets received by the Ethernet module: · Totalnum—Total number of received packets. · ETHIINum—Number of packets encapsulated by using Ethernet II. · SNAPNum—Number of packets encapsulated by using SNAP. · RAWNum—Number of packets encapsulated by using RAW. · LLCNum—Number of packets encapsulated by using LLC. · UnknownNum—Number of packets encapsulated by using unknown methods. · ForwardNum—Number of packets forwarded at Layer 2 or sent to the CPU. · ARP—Number of ARP packets. · MPLS—Number of MPLS packets. · ISIS—Number of IS-IS packets. · ISIS2—Number of large 802.3/802.2 frames encapsulated by using IS-IS. · IP—Number of IP packets. · IPv6—Number of IPv6 packets. |
ETH receive error statistics |
Statistics about the error Ethernet packets in the inbound direction on the Ethernet module. Errors might be included in packets or occur during the receiving process. The items include: · NullPoint—Number of packets that include null pointers. · ErrIfindex—Number of packets that include incorrect interface indexes. · ErrIfcb—Number of packets that include incorrect interface control blocks. · IfShut—Number of packets that are being received when the interface is shut down. · ErrAnalyse—Number of packets that include packet parsing errors. · ErrSrcMAC—Number of packets that include incorrect source MAC addresses. · ErrHdrLen—Number of packets that include header length errors. |
ETH send packet statistics |
Statistics about the Ethernet packets sent by the Ethernet module: · L3OutNum—Number of packets sent out of Layer 3 Ethernet interfaces. · VLANOutNum—Number of packets sent out of VLAN interfaces. · FastOutNum—Number of packets fast forwarded. · L2OutNum—Number of packets sent out of Layer 2 Ethernet interfaces. |
ETH send error statistics |
Statistics about the error Ethernet packets in the outbound direction on the Ethernet module: · MbufRelayNum—Number of packets transparently sent. · NullMbuf—Number of packets with null pointers. · ErrAdjFwd—Number of packets with adjacency table errors. · ErrPrepend—Number of packets with extension errors. · ErrHdrLen—Number of packets with header length errors. · ErrPad—Number of packets with padding errors. · ErrQoSTrs—Number of packets that failed to be sent by QoS. · ErrVLANTrs—Number of packets that failed to be sent in VLANs. · ErrEncap—Number of packets that failed to be sent due to link header encapsulation failures. · ErrTagVLAN—Number of packets that failed to be sent due to VLAN tag encapsulation failures. · IfShut—Number of packets that are being sent when the interface is shut down. · IfErr—Number of packets with incorrect outgoing interfaces. |
Related commands
reset ethernet statistics
display interface
Use display interface to display interface information.
Syntax
display interface [ interface-type [ interface-number | interface-number.subnumber ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number. The interface-number argument is an interface number. The subnumber argument is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 25 characters of each interface description.
down: Displays information about interfaces in down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Usage guidelines
If you do not specify an interface type, this command displays information about all interfaces.
If you specify an interface type but do not specify an interface number, this command displays information about all interfaces of the specified type.
Examples
# Display information about Layer 3 interface HundredGigE 1/0/1.
<Sysname> display interface hundredgige 1/0/1
HundredGigE1/0/1
Current state: DOWN
Line protocol state: DOWN
Description: HundredGigE1/0/1 Interface
Bandwidth: 100000000 kbps
Maximum transmission unit: 1500
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
Known-unicast max-ratio: 100%
Internet protocol processing: Disabled
IP packet frame type: Ethernet II, hardware address: 00e0-fc00-6851
IPv6 packet frame type: Ethernet II, hardware address: 00e0-fc00-6851
Loopback is not set
Media type is not sure, port is No connector
FEC mode: None
Ethernet port mode: LAN
Port priority: 0
Unknown-speed mode, unknown-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
The maximum frame length is 9416
Last link flapping: Never
Last clearing of counters: Never
Current system time:2001-01-05 01:20:48
Last time when physical state changed to up:-
Last time when physical state changed to down:2001-01-05 01:20:46
Peak input rate: 0 bytes/sec, at 2001-01-05 01:20:48
Peak output rate: 0 bytes/sec, at 2001-01-05 01:20:48
Last 300 seconds input: 0 packets/sec 0 bytes/sec -%
Last 300 seconds output: 0 packets/sec 0 bytes/sec -%
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input (normal): 0 packets, - bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output (normal): 0 packets, - bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, - underruns, 0 buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier
IPv4 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
IPv6 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
# Display detailed information about Layer 2 interface HundredGigE 1/0/1.
<Sysname> display interface hundredgige 1/0/1
HundredGigE1/0/1
Current state: DOWN
Line protocol state: DOWN
IP packet frame type: Ethernet II, hardware address: 00e0-fc00-686e
Description: HundredGigE1/0/1 Interface
Bandwidth: 100000000 kbps
Loopback is not set
Media type is not sure, port is No connector
FEC mode: None
Ethernet port mode: LAN
Unknown-speed mode, unknown-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 9416
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
Known-unicast max-ratio: 100%
PVID: 1
MDI type: Automdix
Port link-type: Access
Tagged VLANs: None
Untagged VLANs: 1
Port priority: 0
Last link flapping: Never
Last clearing of counters: Never
Current system time:2001-01-05 01:10:27
Last time when physical state changed to up:-
Last time when physical state changed to down:2001-01-01 00:08:46
Peak input rate: 0 bytes/sec, at 2001-01-04 06:10:49
Peak output rate: 0 bytes/sec, at 2001-01-04 06:10:49
Last 300 seconds input: 0 packets/sec 0 bytes/sec -%
Last 300 seconds output: 0 packets/sec 0 bytes/sec -%
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input (normal): 0 packets, - bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output (normal): 0 packets, - bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, - underruns, 0 buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier
IPv4 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
IPv6 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
Field |
Description |
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · Administratively DOWN(Global)—The interface has been shut down by using the shutdown all-physical-interfaces command in system view. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · DOWN ( Link-Aggregation interface down )—The aggregate interface to which the interface belongs has been shut down by using the shutdown command. · DOWN (Monitor-Link uplink down )—The interface has been shut down by Monitor Link. · Link-Flap DOWN—The interface has been shut down by the link flapping protection feature. · mac-address moving down—The interface has been shut down by the MAC address move suppression feature. · MAD ShutDown—The interface has been shut down by IRF MAD. This state occurs if the interface is on an IRF fabric placed in Recovery state after an IRF split. · OFP DOWN—The interface has been shut down by OpenFlow. · Storm-Constrain—The interface has been shut down because the storm control feature detected that unknown unicast traffic, multicast traffic, or broadcast traffic exceeded the upper threshold. · STP DOWN—The interface has been shut down by the BPDU guard feature. · M-LAG MAD Shutdown—The interface was set to the M-LAG MAD DOWN state when the M-LAG system split. · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · UP (spoofing)—The data link layer protocol is up, but the link is an on-demand link or does not exist. This attribute is typical of null interfaces and loopback interfaces. · DOWN—The data link layer protocol is down. · DOWN (protocols)—The data link layer has been shut down by protocols included in the parentheses. Available protocols include: ¡ DLDP—Shuts down the data link layer when it detects that the link is unidirectional. ¡ OAM—Shuts down the data link layer when it detects a remote link failure. ¡ LAGG—Shuts down the data link layer when it detects that the aggregate interface does not have Selected ports. ¡ BFD—Shuts down the data link layer when it detects a link failure. |
Bandwidth |
Expected bandwidth of the interface. |
Maximum transmission unit |
MTU of the interface. |
Internet protocol processing: Disabled |
The interface is not assigned an IP address and cannot process IP packets. |
Internet address |
IP address of the interface. The primary attribute indicates that the address is the primary IP address. |
Internet address: ip-address/mask-length (Type) |
IP address of the interface and type of the address in parentheses. Possible IP address types include: · Primary—Manually configured primary IP address. · Sub—Manually configured secondary IP address. If the interface has both primary and secondary IP addresses, the primary IP address is displayed. If the interface has only secondary IP addresses, the lowest secondary IP address is displayed. · DHCP-allocated—DHCP allocated IP address. For more information, see DHCP client configuration in Layer 3—IP Services Configuration Guide. · Unnumbered—IP address borrowed from another interface. |
IP packet frame type |
IPv4 packet framing format. |
hardware address |
MAC address of the interface. |
FEC mode |
FEC mode of the interface, which depends on the configuration. When the FEC mode of an interface is set to autonegotiation, the actual FEC mode depends on the model of the transceiver module installed in the fiber port. |
IPv6 packet frame type |
IPv6 packet framing format. |
Port priority |
Port priority of the interface. |
Loopback is set internal |
An internal loopback test is running on the interface. This field depends on your configuration. |
Loopback is set external |
An external loopback test is running on the interface. This field depends on your configuration. |
Loopback is not set |
No loopback test is running on the interface. This field depends on your configuration. |
10Gbps-speed mode |
The interface is operating at 10 Gbps. This field depends on your configuration and the link parameter negotiation result. |
25Gbps-speed mode |
The interface is operating at 25 Gbps. This field depends on your configuration and the link parameter negotiation result. |
40Gbps-speed mode |
The interface is operating at 40 Gbps. This field depends on your configuration and the link parameter negotiation result. |
50Gbps-speed mode |
The interface is operating at 50 Gbps. This field depends on your configuration and the link parameter negotiation result. |
100Gbps-speed mode |
The interface is operating at 100 Gbps. This field depends on your configuration and the link parameter negotiation result. |
Unknown-speed mode |
The speed of the interface is unknown because the speed negotiation fails or the interface is physically disconnected. |
full-duplex mode |
The interface is operating in full duplex mode. This field depends on your configuration and the link parameter negotiation result. |
unknown-duplex mode |
The duplex mode of the interface is unknown because the duplex mode negotiation fails or the interface is physically disconnected. |
Link speed type is autonegotiation |
The interface is configured with the speed auto command. |
Link speed type is force link |
The interface is manually configured with a speed (for example, 1000 Mbps) by using the speed command. |
link duplex type is autonegotiation |
The interface is configured with the duplex auto command. |
link duplex type is force link |
The interface is manually configured with a duplex mode (for example, half or full) by using the duplex command. |
Flow-control is not enabled |
Generic flow control is disabled on the interface. This field depends on your configuration and the link parameter negotiation result. |
Maximum frame length |
Maximum length of Ethernet frames allowed to pass through the interface. |
Allow jumbo frame to pass |
The interface allows jumbo frames to pass through. |
Broadcast max- |
Broadcast storm suppression threshold. |
Multicast max- |
Multicast storm suppression threshold. |
Unicast max- |
Unknown unicast storm suppression threshold. |
Known-unicast max- |
This field is not supported in the current software version. Known unicast storm suppression threshold. |
PVID |
Port VLAN ID (PVID) of the interface. |
MDI type |
MDIX mode of the interface: · automdix. · mdi. · mdix. |
Dampening enabled |
Damping is enabled on the interface. |
Penalty |
Penalty value. |
Ceiling |
The penalty stops increasing when it reaches the ceiling. |
Reuse |
Reuse threshold. |
Suppress |
Suppression threshold. |
Half-life |
Amount of time after which a penalty is decreased, in seconds. |
Max-suppress-time |
Maximum amount of time the interface can be dampened, in seconds. |
Flap count |
Number of flaps (up/down events) on the interface. |
Port link-type |
Link type of the interface: · access. · trunk. · hybrid. |
Tagged VLANs |
VLANs for which the interface sends packets without removing VLAN tags. |
Untagged VLANs |
VLANs for which the interface sends packets after removing VLAN tags. |
VLAN Passing |
VLANs whose packets can be forwarded by the port. The VLANs must have been created. |
VLAN permitted |
VLANs whose packets are permitted by the port. |
Trunk port encapsulation |
Encapsulation protocol type for the trunk port. |
Last link flapping |
The amount of time that has elapsed since the most recent physical state change of the interface. This field displays Never if the interface has been physically down since device startup. |
Last clearing of counters |
Time when the reset counters interface command was last used to clear the interface statistics. This field displays Never if the reset counters interface command has never been used on the interface since device startup. |
Current system time |
Current system time in the YYYY/MM/DD HH:MM:SS format. If the time zone is configured, this field is in the YYYY/MM/DD HH:MM:SS zone-name±HH:MM:SS format, where the zone-name argument is the local time zone. |
Last time when physical state changed to up |
Last time when the physical state of the interface changed to up. If the time zone is configured, this field is in the YYYY/MM/DD HH:MM:SS zone-name±HH:MM:SS format, where the zone-name argument is the local time zone. A hyphen (-) indicates that the physical state of the interface has never changed. |
Last time when physical state changed to down |
Last time when the physical state of the interface changed to down. If the time zone is configured, this field is in the YYYY/MM/DD HH:MM:SS zone-name±HH:MM:SS format, where the zone-name argument is the local time zone. A hyphen (-) indicates that the physical state of the interface has never changed. |
Last interval seconds input: 0 packets/sec 0 bytes/sec 0% Last interval seconds output: 0 packets/sec 0 bytes/sec 0% |
Average inbound or outbound traffic rate (in pps and Bps) in the last statistics polling interval, and the ratio of the actual rate to the interface bandwidth. To set the statistics polling interval (interval), use the flow-interval command. A hyphen (-) indicates that the statistical item is not supported. |
Input(total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
The two fields on the first line represent the inbound traffic statistics (in packets and bytes) for the interface. All inbound normal packets, abnormal packets, and normal pause frames were counted. The four fields on the second line represent: · Number of inbound unicast packets. · Number of inbound broadcasts. · Number of inbound multicasts. · Number of inbound pause frames. A hyphen (-) indicates that the statistical item is not supported. |
Input(normal): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
The two fields on the first line represent the inbound normal traffic and pause frame statistics (in packets and bytes) for the interface. The four fields on the second line represent: · Number of inbound normal unicast packets. · Number of inbound normal broadcasts. · Number of inbound normal multicasts. · Number of inbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported. |
input errors |
Statistics of incoming error packets. |
runts |
Number of inbound frames meeting the following conditions: · Shorter than 64 bytes. · In correct format. · Containing valid CRCs. |
giants |
Number of inbound giants. Giants refer to frames larger than the maximum frame length supported on the interface. For an Ethernet interface that does not permit jumbo frames, the maximum frame length is as follows: · 1518 bytes (without VLAN tags). · 1522 bytes (with VLAN tags). For an Ethernet interface that permits jumbo frames, the maximum Ethernet frame length is set when you configure jumbo frame support on the interface. |
throttles |
Number of inbound frames that had a non-integer number of bytes. |
CRC |
Total number of inbound frames that had a normal length, but contained CRC errors. |
frame |
Total number of inbound frames that contained CRC errors and a non-integer number of bytes. |
overruns |
Number of packets dropped because the input rate of the port exceeded the queuing capability. |
aborts |
Total number of illegal inbound packets: · Fragment frames—CRC error frames shorter than 64 bytes. The length (in bytes) can be an integral or non-integral value. · Jabber frames—CRC error frames greater than the maximum frame length supported on the Ethernet interface (with an integral or non-integral length). ¡ For an Ethernet interface that does not permit jumbo frames, the maximum frame length is 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). ¡ For an Ethernet interface that permits jumbo frames, the maximum Ethernet frame length is set when you configure jumbo frame support on the interface. · Symbol error frames—Frames that contained a minimum of one undefined symbol. · Unknown operation code frames—Non-pause MAC control frames. · Length error frames—Frames whose 802.3 length fields did not match the actual frame length (46 to 1500 bytes). |
ignored |
Number of inbound frames dropped because the receiving buffer of the port ran low. |
parity errors |
Total number of frames with parity errors. |
Output(total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
The two fields on the first line represent the outbound traffic statistics (in packets and bytes) for the interface. All outbound normal packets, abnormal packets, and normal pause frames were counted. The four fields on the second line represent: · Number of outbound unicast packets. · Number of outbound broadcasts. · Number of outbound multicasts. · Number of outbound pause frames. A hyphen (-) indicates that the statistical item is not supported. |
Output(normal): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
The two fields on the first line represent the outbound normal traffic and pause frame statistics (in packets and bytes) for the interface. The four fields on the second line represent: · Number of outbound normal unicast packets. · Number of outbound normal broadcasts. · Number of outbound normal multicasts. · Number of outbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported. |
output errors |
Number of outbound packets with errors. |
underruns |
Number of packets dropped because the output rate of the interface exceeded the output queuing capability. This is a low-probability hardware anomaly. |
buffer failures |
Number of packets dropped because the transmitting buffer of the interface ran low. |
aborts |
Number of packets that failed to be transmitted, for example, because of Ethernet collisions. |
deferred |
Number of frames that the interface deferred to transmit because of detected collisions. |
collisions |
Number of frames that the interface stopped transmitting because Ethernet collisions were detected during transmission. |
late collisions |
Number of frames that the interface deferred to transmit after transmitting their first 512 bits because of detected collisions. |
lost carrier |
Number of carrier losses during transmission. This counter increases by one when a carrier is lost, and applies to serial WAN interfaces. |
no carrier |
Number of times that the port failed to detect the carrier when attempting to send frames. This counter increases by one when a port failed to detect the carrier, and applies to serial WAN interfaces. |
Peak input rate |
Peak rate of inbound traffic in Bps, and the time when the peak inbound traffic rate occurred. |
Peak output rate |
Peak rate of outbound traffic in Bps, and the time when the peak outbound traffic rate occurred. |
IPv4 traffic statistics |
IPv4 packet statistics. |
IPv6 traffic statistics |
IPv6 packet statistics. |
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec |
Average inbound traffic rate (in pps and Bps) in the last 300 seconds. A hyphen (-) indicates that the statistical item is not supported. |
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec |
Average outbound traffic rate (in pps and Bps) in the last 300 seconds. A hyphen (-) indicates that the statistical item is not supported. |
Input: 0 packets, 0 bytes |
Inbound traffic statistics (in packets and bytes) for the interface. A hyphen (-) indicates that the statistical item is not supported. |
Output: 0 packets, 0 bytes |
Outbound traffic statistics (in packets and bytes) for the interface. A hyphen (-) indicates that the statistical item is not supported. |
# Display brief information about all interfaces.
<Sysname> display interface brief
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) – spoofing
Interface Link Protocol Primary IP Description
HGE1/0/1 DOWN DOWN --
Loop0 UP UP(s) 2.2.2.9
NULL0 UP UP(s) --
Vlan1 UP UP --
Vlan999 UP UP 192.168.1.42
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Speed: (a) - auto
Duplex: (a)/A - auto; H - half; F - full
Type: A - access; T - trunk; H - hybrid
Interface Link Speed Duplex Type PVID Description
HGE1/0/2 DOWN auto A A 1
HGE1/0/3 UP 1G(a) F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaa
# Display brief information about HundredGigE 1/0/3, including the complete description of the interface.
<Sysname> display interface hundredgige 1/0/3 brief description
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Speed: (a) - auto
Duplex: (a)/A - auto; H - half; F - full
Type: A - access; T - trunk; H - hybrid
Interface Link Speed Duplex Type PVID Description
HGE1/0/3 UP 1G(a) F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
# Display information about interfaces in DOWN state and the causes.
<Sysname> display interface brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
HGE1/0/1 DOWN Not connected
Vlan2 DOWN Not connected
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
HGE1/0/2 DOWN Not connected
Field |
Description |
Brief information on interfaces in route mode: |
Brief information about Layer 3 interfaces. |
Interface |
Interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. |
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces. |
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
Description |
Description of the interface. |
Brief information of interfaces in bridge mode: |
Brief information about Layer 2 interfaces. |
Type: A - access; T - trunk; H – hybrid |
Link type options for interfaces. |
Speed |
Speed of the interface, in bps. This field displays the (a) flag next to the speed if the speed is automatically negotiated. This field displays auto if the interface is configured to autonegotiate its speed but the autonegotiation has not started. |
Duplex |
Duplex mode of the interface: · A—Autonegotiation. The interface is configured to autonegotiate its duplex mode but the autonegotiation has not started. · F—Full duplex. · F(a)—Autonegotiated full duplex. · H—Half duplex. · H(a)—Autonegotiated half duplex. |
Type |
Link type of the interface: · A—Access. · H—Hybrid. · T—Trunk. |
PVID |
Port VLAN ID. |
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · DOWN ( Link-Aggregation interface down )—The interface is a member port of an aggregate interface, and the aggregate interface is down. · DOWN (Loopback detection down)—The loopback detection module has detected loops. · DOWN ( Monitor-Link uplink down )—The monitor link module has detected that the uplink is down. · MAD ShutDown—The interface is on an IRF fabric placed by IRF MAD in Recovery state after an IRF split. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). · Storm-Constrain—The storm control feature has detected that unknown unicast traffic, multicast traffic, or broadcast traffic exceeded the upper threshold. · STP DOWN—The interface has been shut down by the BPDU guard feature. · OFP DOWN—The interface has been shut down by OpenFlow. |
flow-interval
reset counters interface
display interface link-info
Use display interface link-info to display the status and packet statistics of interfaces.
Syntax
display interface link-info [ main ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
main: Specifies all interfaces except subinterfaces. If you do not specify this keyword, this command displays status and packet statistics of all interfaces.
Examples
# Display status and statistics of all interfaces.
<Sysname> display interface link-info
Link: ADM - administratively down; Stby - standby
Protocol: (s) - spoofing
Interface Link Protocol InUsage OutUsage InErrs OutErrs
HGE1/0/1 UP UP 10% 0% 0 0
NULL0 UP UP(s) 0% 0% 0 0
Overflow: More than 7 digits.
--: Not supported.
Table 6 Command output
Field |
Description |
Link: ADM - administratively down; Stby - standby |
Physical link state of the interface: · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command. |
Protocol: (s) – spoofing |
The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces, loopback interfaces, and InLoopback interfaces. |
Interface |
Abbreviated interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. |
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces, loopback interfaces, and InLoopback interfaces. |
InUsage |
Inbound bandwidth usage within the most recent statistics polling interval. It is calculated by this formula: Average inbound speed of the interface within the most recent statistics polling interval/interface bandwidth. To set the statistics polling interval, use the flow-interval command. |
OutUsage |
Outbound bandwidth usage within the most recent statistics polling interval. It is calculated by this formula: Average outbound speed of the interface within the most recent statistics polling interval/interface bandwidth. To set the statistics polling interval, use the flow-interval command. |
InErrs |
Number of error packets received. |
OutErrs |
Number of error packets sent. |
Overflow: More than 7 digits. |
The data length of a statistical item value is greater than 7 decimal digits. |
--: Not supported. |
A hyphen (-) indicates that the corresponding statistical item is not supported. |
Related commands
flow-interval
display interface main
Use display interface main to display operating status and information of all interfaces except subinterfaces.
Syntax
display interface [ interface-type ] [ brief [ description | down ] ] main
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type: Specifies an interface type. If you do not specify this argument, the command displays information about interfaces of all types.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 25 characters of each interface description.
down: Displays information about interfaces in down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display operating status and information of all interfaces except subinterfaces.
<Sysname> display interface main
HundredGigE1/0/1
Current state: Administratively DOWN
Line protocol state: DOWN
IP packet frame type: Ethernet II, hardware address: 4005-6538-0100
Description: HundredGigE1/0/1 Interface
Bandwidth: 1000000 kbps
Loopback is not set
Unknown-speed mode, unknown-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 9216
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
PVID: 1
MDI type: Automdix
Port link-type: Access
Tagged VLANs: None
Untagged VLANs: 1
Port priority: 2
Last link flapping: Never
Last clearing of counters: Never
Current system time:2020-04-11 10:20:24
Last time when physical state changed to up:-
Last time when physical state changed to down:2020-04-11 09:11:09
Peak input rate: 0 bytes/sec, at 00-00-00 00:00:00
Peak output rate: 0 bytes/sec, at 00-00-00 00:00:00
Last 300 seconds input: 0 packets/sec 0 bytes/sec -%
Last 300 seconds output: 0 packets/sec 0 bytes/sec -%
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, 0 overruns, 0 aborts
0 ignored, 0 parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, 0 underruns, 0 buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, 0 no carrier
IPv4 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
IPv6 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
HundredGigE1/0/2
Current state: Administratively DOWN
Line protocol state: DOWN
Description: HundredGigE1/0/2 Interface
Bandwidth: 1000000 kbps
Flow-control is not enabled
Maximum transmission unit: 1500
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
Internet protocol processing: Disabled
IP packet frame type: Ethernet II, hardware address: 4005-6538-0107
IPv6 packet frame type: Ethernet II, hardware address: 4005-6538-0107
Output queue - Urgent queuing: Size/Length/Discards 0/100/0
Output queue - Protocol queuing: Size/Length/Discards 0/500/0
Output queue - FIFO queuing: Size/Length/Discards 0/75/0
Last link flapping: Never
Last clearing of counters: Never
Current system time:2020-04-11 10:20:24
Last time when physical state changed to up:-
Last time when physical state changed to down:2020-04-11 09:33:52
Peak input rate: 0 bytes/sec, at 00-00-00 00:00:00
Peak output rate: 0 bytes/sec, at 00-00-00 00:00:00
Last 300 seconds input: 0 packets/sec 0 bytes/sec -%
Last 300 seconds output: 0 packets/sec 0 bytes/sec -%
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, 0 overruns, 0 aborts
0 ignored, 0 parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, 0 underruns, 0 buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, 0 no carrier
IPv4 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
IPv6 traffic statistics:
Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
Input: 0 packets, 0 bytes
Output: 0 packets, 0 bytes
# Display brief information of all interfaces except subinterfaces.
<Sysname> display interface brief main
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Protocol: (s) – spoofing
Interface Link Protocol Primary IP Description
HGE1/0/1 DOWN DOWN --
Loop0 UP UP(s) 2.2.2.9
NULL0 UP UP(s) --
Vlan1 UP DOWN --
Vlan999 UP UP 192.168.1.42
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Speed: (a) - auto
Duplex: (a)/A - auto; H - half; F - full
Type: A - access; T - trunk; H - hybrid
Interface Link Speed Duplex Type PVID Description
HGE1/0/2 DOWN auto A A 1
# Display brief information about all interfaces except subinterfaces, including the complete interface descriptions.
<Sysname> display interface brief description main
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Speed: (a) - auto
Duplex: (a)/A - auto; H - half; F - full
Type: A - access; T - trunk; H - hybrid
Interface Link Speed Duplex Type PVID Description
HGE1/0/3 UP auto F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
# Display information about interfaces except subinterfaces in DOWN state and the causes.
<Sysname> display interface brief down main
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
HGE1/0/1 DOWN Not connected
Vlan2 DOWN Not connected
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
HGE1/0/2 DOWN Not connected
For description on the display interface main command output, see Table 4 and Table 5.
display link-flap protection
Use display link-flap protection to display information about link flapping protection on an interface.
display link-flap protection [ interface interface-type [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
interface-type: Specifies an interface type. If you do not specify an interface type, the command displays information about link flapping protection on all interfaces.
interface-number: Specifies an interface number. If you do not specify an interface number, the command displays information about link flapping protection on all interfaces of the specified type.
Examples
# Display information about link flapping protection on all interfaces.
<Sysname> display link-flap protection
Link-flap protection: Enabled
Interface Link-flap Status Interval(L1/L2) Threshold(L1/L2)
HGE1/0/1 Enabled Down 10/5 5/60
HGE1/0/2 Disabled N/A --/-- --/--
Field |
Description |
Link-flap protection |
Status of global link flapping protection: · Enabled—Link flapping protection is enabled globally. · Disabled—Link flapping protection is disabled globally. |
Link-flap |
Status of link flapping protection on an interface: · Enabled—Link flapping protection is enabled on an interface. · Disabled—Link flapping protection is disabled on an interface. |
Status |
Status of an interface: · Down—The interface has been shut down by the link flapping protection feature. · N/A—The interface status is not affected by the link flapping protection feature. |
Interval(L1/L2) |
Level-1/Level-2 link flapping detection interval for an interface. |
Threshold(L1/L2) |
Level-1/Level-2 link flapping detection threshold for an interface. |
Related commands
link-flap protect enable
port link-flap protect enable
display link-state-change statistics interface
Use display link-state-change statistics interface to display the physical link state change statistics of interfaces.
Syntax
display link-state-change statistics interface [ interface-type [ interface-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
Usage guidelines
If you do not specify an interface type, this command displays the link state change statistics for all interfaces.
If you specify an interface type but do not specify an interface number, this command displays the link state change statistics for all interfaces of the specified type.
Examples
# Display the link state change statistics of all interfaces.
<Sysname> display link-state-change statistics interface
Interface Change-times Last-change-time Reset link-state time
Link-flap-begin Link-flap-end
HGE1/0/1 0 Never Never
Never Never
Table 8 Command output
Field |
Description |
Interface |
Abbreviated interface name. |
Change-times |
Number of physical state changes. |
Last-change-time |
Last time when the physical state changed. |
Reset link-state time |
Time when the physical link state change statistics were cleared. |
Link-flap-begin |
Last time when a physical link state flapping began. If no link state flapping has occurred, this field displays Never. |
Link-flap-end |
Last time when a physical link state flapping ended. If no link state flapping has occurred, this field displays Never. |
Related commands
reset link-state-change statistics interface
display packet-drop
Use display packet-drop to display information about packets dropped on an interface.
Syntax
display packet-drop { interface [ interface-type [ interface-number ] ] | summary }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
summary: Displays the summary of dropped packets on only interfaces that support this command.
Usage guidelines
If you do not specify an interface type, this command displays information about dropped packets on only interfaces that support this command on the device.
If you specify an interface type but do not specify an interface number, this command displays information about dropped packets on only interfaces of the specified type that support this command.
Examples
# Display information about dropped packets on HundredGigE 1/0/1.
<Sysname> display packet-drop interface hundredgige 1/0/1
HundredGigE1/0/1:
Packets dropped due to Egress Filter Processor (EFP): 0
Packets dropped due to Fast Filter Processor (FFP): 261
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped:0
Packets of ECN marked: 0
Packets of WRED droped: 0
# Display the summary of dropped packets on only interfaces that support this command.
<Sysname> display packet-drop summary
All interfaces:
Packets dropped due to Egress Filter Processor (EFP): 0
Packets dropped due to Fast Filter Processor (FFP): 261
Packets dropped due to STP non-forwarding state: 0
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped:0
Packets of ECN marked: 0
Packets of WRED droped: 0
Table 9 Command output
Field |
Description |
Packets dropped due to Fast Filter Processor (FFP) |
Packets that are filtered out. |
Packets dropped due to Egress Filter Processor (EFP) |
Packets that are dropped due to EFP in the outbound direction. |
Packets dropped due to STP non-forwarding state |
Packets that are dropped because STP is in the non-forwarding state. |
Packets dropped due to insufficient data buffer. Input dropped: 0 Output dropped:0 |
Inbound and outbound packets that are dropped due to insufficient data buffer. |
Packets of ECN marked |
Packets with the ECN field set to 11 because WRED queue thresholds are reached. For more information about WRED and ECN, see ACL and QoS Configuration Guide. |
Packets of WRED dropped |
Packets that are dropped because the WRED queue thresholds are reached. |
display rail-group status
Use display rail-group status to display rail group information.
Syntax
display rail-group status
Views
System view
Predefined user roles
network-admin
network-operator
Example
# Display rail group information.
<System> display rail-group status
Global rail-group configuration: Enable
GroupName GroupIndex Index Interface
Leaf1 1 0 HundredGigE1/0/2
HundredGigE1/0/1
Leaf 2 0 HundredGigE1/0/3
HundredGigE1/0/4
Table 10 Command output
Field |
Description |
Global rail-group configuration |
Status of the rail group feature: · Disable · Enable |
GroupName |
Name of the rail group. |
GroupIndex |
Index of an interface in the rail group. |
Index |
Index of the rail group. |
Interface |
Name of the interface. |
Related commands
group-member interface
duplex
Use duplex to set the duplex mode for an Ethernet interface.
Use undo duplex to restore the default.
Syntax
duplex { auto | full }
undo duplex
Default
Ethernet interfaces operate in autonegotiation mode.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
auto: Configures the interface to autonegotiate the duplex mode with the peer.
full: Configures the interface to operate in full duplex mode. In this mode, the interface can receive and transmit packets simultaneously.
Examples
# Configure HundredGigE 1/0/1 to operate in full duplex mode.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] duplex full
flow-control
Use flow-control to enable TxRx-mode generic flow control on an Ethernet interface.
Use undo flow-control to disable TxRx-mode generic flow control on the Ethernet interface.
Syntax
flow-control
undo flow-control
Default
TxRx-mode generic flow control is disabled on an Ethernet interface.
Views
Ethernet interface view
Predefined user roles
network-admin
Usage guidelines
With TxRx-mode generic flow control configured, an interface can both send and receive flow control frames:
· When congested, the interface sends a flow control frame to its peer.
· Upon receiving a flow control frame from the peer, the interface suspends sending packets.
To implement flow control, configure flow control on each interface that the traffic passes through.
This command and the priority-flow-control no-drop dot1p command are mutually exclusive.
When you enable or disable flow control on the following types of interfaces, the interfaces might flap:
· Copper ports.
· Fiber ports with the DAC cables installed.
Examples
# Enable TxRx-mode generic flow control on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] flow-control
flow-control receive enable
Use flow-control receive enable to enable Rx-mode generic flow control on an Ethernet port.
Use undo flow-control to disable Rx-mode generic flow control on an Ethernet port.
Syntax
flow-control receive enable
undo flow-control
Default
Rx-mode generic flow control is disabled on Ethernet interfaces.
Views
Ethernet interface view
Predefined user roles
network-admin
Usage guidelines
With Rx-mode flow control enabled, an interface can receive but cannot send flow control frames.
· When the interface receives a flow control frame from its peer, it suspends sending packets to the peer.
· When traffic congestion occurs on the interface, it cannot send flow control frames to the peer.
To handle unidirectional traffic congestion on a link, configure the flow-control receive enable command at one end, and the flow-control command at the other. To enable both ends of the link to handle traffic congestion, configure the flow-control command at both ends.
This command is mutually exclusive with the priority-flow-control or priority-flow-control no-drop dot1p command.
When you enable or disable flow control on the following types of interfaces, the interfaces might flap:
· Copper ports.
· Fiber ports with the DAC cables installed.
Examples
# Enable Rx-mode generic flow control on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-hundredgige 1/0/1] flow-control receive enable
Related commands
flow-control
flow-interval
Use flow-interval to set the statistics polling interval.
Use undo flow-interval to restore the default.
Syntax
flow-interval interval
undo flow-interval
Default
The statistics polling interval is 300 seconds.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
interval: Sets the statistics polling interval in seconds. The interval is in the range of 1 to 300 and must be a multiple of 5.
Examples
# Set the statistics polling interval to 100 seconds on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] flow-interval 100
https://support.huawei.com/hedex/api/pages/EDOC1100302098/AZM0425D/02/resources/cmdqueryname=load-balance+ecmp+rail-group+enable-member interface
Use group-member interface to assign interfaces to a rail group.
Use undo group-member interface to remove interfaces from a rail group.
Syntax
group-member interface interface-type interface-number [ to interface-type interface-number ]
undo group-member interface interface-type interface-number [ to interface-type interface-number ]
group-member interface interface-type interface-number index index-value
undo group-member interface interface-type interface-number index index-value
Views
Rail group view
Default
A rail group does not contain any interfaces.
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
to: Specifies the end member interface number.
index-value: Specifies an interface by its index, in the range of 0 to 63.
Usage guidelines
You can specify an index to assign an interface with the specified index to a rail group or specify a list of interfaces to allow the device to automatically assign indexes to the interfaces and assign the interfaces in bulk to a rail group.
As a best practice, do not manually specify an index. If you specify a list of non-contiguous interface indexes, the traffic outgoing interfaces will become discontinuous, causing unbalanced traffic. If you have to manually specify an index, do that under guidance of professionals.
You can assign only physical interfaces to a rail group, and the interfaces must be incoming interfaces.
Assign interfaces to a rail group in the order of interface numbers. To avoid index change after a device reboot, do not change the interface type after you assign an interface to a rail group.
Interfaces in a rail group cannot be split or combined.
If you specify a list of interfaces, make sure the two interfaces before and after the to keyword are the same type.
Example
# Assign interfaces HundredGigE 1/0/1 through HundredGigE 1/0/4 to rail group Leaf1.
<Sysname> system-view
[Sysname] rail-group Leaf1
[Sysname-rail-group-Leaf1] group-member interface HundredGigE1/0/1 to HundredGigE1/0/4
# Assign interface HundredGigE1/0/1 with index 3 to rail group Leaf1.
<Sysname> system-view
[Sysname] rail-group Leaf1
[Sysname-rail-group-Leaf1] group-member interface HundredGigE1/0/1 index 3
ifmonitor crc-error
Use ifmonitor crc-error to configure global CRC error packet alarm parameters.
Use undo ifmonitor crc-error to restore the default.
Syntax
ifmonitor crc-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ down-auto-recovery | shutdown ]
undo ifmonitor crc-error slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for CRC error packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for CRC error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for CRC error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for CRC error packets, in the range of 1 to 65535 seconds.
down-auto-recovery: Shuts down an interface when the number of incoming CRC error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. After the port recovery time set by the shutdown-interval crc-error command, the port automatically restores to its actual physical state. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters alarm state when the number of incoming CRC error packets exceeds the upper threshold on the interface.
shutdown: Shuts down an interface when the number of incoming CRC error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming CRC error packets exceeds the upper threshold on the interface, but the interface will not be shut down. If you specify this keyword when the upper threshold has been exceeded on an interface, the interface will be shut down.
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
With the CRC error packet alarm function enabled, when the number of incoming CRC error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of incoming CRC error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can configure the CRC error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for CRC error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor crc-error slot 1 high-threshold 5000 low-threshold 400 interval 6
Related commands
shutdown-interval crc-error
snmp-agent trap enable ifmonitor
ifmonitor input-error
Use ifmonitor input-error to configure global input error packet alarm parameters.
Use undo ifmonitor input-error to restore the default.
Syntax
ifmonitor input-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor input-error slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for input error packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for input error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of input error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of input error packets exceeds the upper threshold on the interface, but the interface will not be shut down. If you specify this keyword when the upper threshold has been exceeded on an interface, the interface will be shut down.
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
With the input error packet alarm function enabled, when the number of input error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of input error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can configure the input error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for input error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor input-error slot 1 high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
ifmonitor input-usage
Use ifmonitor input-usage to configure global input bandwidth usage alarm parameters.
Use undo ifmonitor input-usage to restore the default.
Syntax
ifmonitor input-usage slot slot-number high-threshold high-value low-threshold low-value
undo ifmonitor input-usage slot slot-number
Default
The upper threshold is 90, and the lower threshold is 80.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for input bandwidth usage alarms, in the range of 1 to 100.
low-threshold low-value: Specifies the lower threshold for input bandwidth usage alarms, in the range of 1 to 100.
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
With the input bandwidth usage alarm function enabled, when the input bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the input bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can use the flow-interval command to set the statistics polling interval.
You can configure the input bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the input bandwidth usage alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 95 and lower threshold to 80 for input bandwidth usage alarms.
<Sysname> system-view
[Sysname] ifmonitor input-usage slot 1 high-threshold 95 low-threshold 80
Related commands
flow-interval
snmp-agent trap enable ifmonitor
ifmonitor output-usage
Use ifmonitor output-usage to configure global output bandwidth usage alarm parameters.
Use undo ifmonitor output-usage to restore the default.
Syntax
ifmonitor output-usage slot slot-number high-threshold high-value low-threshold low-value
undo ifmonitor output-usage slot slot-number
Default
The upper threshold is 90, and the lower threshold is 80.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for output bandwidth usage alarms, in the range of 1 to 100.
low-threshold low-value: Specifies the lower threshold for output bandwidth usage alarms, in the range of 1 to 100.
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
With the output bandwidth usage alarm function enabled, when the output bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the output bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can use the flow-interval command to set the statistics polling interval.
You can configure the output bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the output bandwidth usage alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 80 and lower threshold to 60 for output bandwidth usage alarms.
<Sysname> system-view
[Sysname] ifmonitor output-usage slot 1 high-threshold 80 low-threshold 60
Related commands
flow-interval
snmp-agent trap enable ifmonitor
ifmonitor rx-pause
Use ifmonitor rx-pause to configure global received pause frame alarm parameters.
Use undo ifmonitor rx-pause to restore the default.
Syntax
ifmonitor rx-pause slot slot-number high-threshold high-value low-threshold low-value interval interval
undo ifmonitor rx-pause slot slot-number
Default
The upper threshold is 500, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for received pause frame alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for received pause frame alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for received pause frame alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for received pause frames, in the range of 1 to 65535 seconds.
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
With the received pause frame alarm function enabled, when the number of received pause frames on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of received pause frames on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can configure the received pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the received pause frame alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 30, lower threshold to 20, and statistics collection and comparison interval to 4 seconds for received pause frame alarms.
<Sysname> system-view
[Sysname] ifmonitor rx-pause slot 1 high-threshold 30 low-threshold 20 interval 4
Related commands
snmp-agent trap enable ifmonitor
ifmonitor tx-pause
Use ifmonitor tx-pause to configure global sent pause frame alarm parameters.
Use undo ifmonitor tx-pause to restore the default.
Syntax
ifmonitor tx-pause slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor tx-pause slot slot-number
Default
The upper threshold is 500, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for sent pause frame alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for sent pause frame alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for sent pause frame alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for sent pause frames, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of sent pause frames on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of sent pause frames exceeds the upper threshold on the interface, but the interface will not be shut down. If you specify this keyword when the upper threshold has been exceeded on an interface, the interface will be shut down.
slot slot-number: Specifies an IRF member device by its member ID.
Usage guidelines
With the sent pause frame alarm function enabled, when the number of sent pause frames on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of sent pause frames on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can configure the sent pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the sent pause frame alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 20, lower threshold to 10, and statistics collection and comparison interval to 5 seconds for sent pause frame alarms.
<Sysname> system-view
[Sysname] ifmonitor tx-pause slot 1 high-threshold 20 low-threshold 10 interval 5
Related commands
snmp-agent trap enable ifmonitor
interface
Use interface to enter interface view, create a subinterface and enter its view, or enter the view of an existing subinterface.
Syntax
interface interface-type { interface-number | interface-number.subnumber }
Views
System view
Predefined user roles
network-admin
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number. The interface-number argument is an interface number. The subnumber argument is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
Examples
# Enter the view of HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1]
# Create Ethernet subinterface HundredGigE 1/0/1.1 and enter its view.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1.1
[Sysname-HundredGigE1/0/1.1]
interface default-description output
Use interface default-description output to display the default description for interfaces when the interface information is displayed.
Use undo interface default-description output to not display the default description for interfaces when the interface information is displayed.
Syntax
interface default-description output
undo interface default-description output
Default
The device displays the default description for interfaces when it displays the interface information.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command takes effect only on physical interfaces.
Examples
# Configure the device to not display the the default description for interfaces when it displays the interface information.
<Sysname> system-view
[Sysname] undo interface default-description output
Related commands
description
jumboframe enable
Use jumboframe enable to allow jumbo frames within the specified length to pass through.
Use undo jumboframe enable to prevent jumbo frames from passing through.
Use undo jumboframe enable size to restore the default.
Syntax
jumboframe enable [ size ]
undo jumboframe enable [ size ]
Default
The device allows jumbo frames within 9416 bytes to pass through.
Views
Layer 2 Ethernet interface view
Layer 3 Ethernet interface view
Predefined user roles
network-admin
Parameters
size: Sets the maximum length (in bytes) of Ethernet frames that are allowed to pass through. The value range for this argument is 1536 to 9416.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Allow jumbo frames to pass through HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] jumboframe enable
link-delay
Use link-delay to set the physical state change suppression interval on an Ethernet interface.
Use undo link-delay to restore the default.
Syntax
link-delay { down | up } [ msec ] delay-time
undo link-delay { down | up }
Default
Each time the physical link of a port goes up or comes down, the interface immediately reports the change to the CPU.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
down: Suppresses link-down events.
up: Suppresses link-up events.
msec: Enables the physical state change suppression interval to be accurate to milliseconds. If you do not specify this keyword, the suppression interval is accurate to seconds.
delay-time: Sets the physical state change suppression interval on the Ethernet interface. A value of 0 means that physical state changes are immediately reported to the CPU and are not suppressed.
· If you do not specify the msec keyword, the value range is 0 to 300 seconds.
· If you specify the msec keyword, the value range is 0 to 10000 milliseconds, and the value must be a multiple of 100.
Usage guidelines
You can configure this feature to suppress only link-down events, only link-up events, or both. If an event of the specified type still exists when the suppression interval expires, the system reports the event.
When you configure this feature, follow these guidelines:
· To suppress link-down events, execute the link-delay down command.
· To suppress link-up events, execute the link-delay up command.
On an interface, you can configure different suppression intervals for link-up and link-down events. If you execute the link-delay command multiple times on an interface, the following rules apply:
· You can configure the suppression intervals for link-up and link-down events separately.
· If you configure the suppression interval multiple times for link-up or link-down events, the most recent configuration takes effect.
Do not execute this command on an interface that has RRPP, spanning tree protocols, or Smart Link enabled.
This command, the dampening command, and the port link-flap protect enable command are mutually exclusive on an Ethernet interface.
Examples
# Set the link-down event suppression interval to 8 seconds on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] link-delay down 8
# Set the link-up event suppression interval to 800 milliseconds on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] link-delay up msec 800
Related commands
dampening
port link-flap protect enable
link-fault-signal enable
Use link-fault-signal enable to enable remote fault signal detection.
Use undo link-fault-signal enable to disable remote fault signal detection.
Syntax
link-fault-signal enable
undo link-fault-signal enable
Default
Remote fault signal detection is enabled.
Views
Ethernet interface view
Predefined user roles
network-admin
Usage guidelines
Only fiber ports support this command.
A fiber port forwards packets by using two optical fibers. One is used to receive packets, and the other one is used to send packets. The fiber port can go up and forward packets only when both optical fibers operate correctly. When the fiber port receives a remote fault signal, the physical state of the port becomes down. To keep the port in up state to operate correctly upon receiving a remote fault signal, disable remote fault signal detection on the port. Then, the port can forward packets unidirectionally when only one fiber operates correctly.
Examples
# Disable remote fault signal detection on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] undo link-fault-signal enable
link-flap protect enable
Use link-flap protect enable to enable link flapping protection globally.
Use undo link-flap protect enable to disable link flapping protection globally.
Syntax
link-flap protect enable [ down-auto-recovery ]
undo link-flap protect enable
Default
Link flapping protection is disabled globally.
Views
System view
Predefined user roles
network-admin
Parameters
down-auto-recovery: Shuts down an interface when the device detects link flapping on that interface. When the port status detection timer for the ports that are shut down by the link flapping protection feature expires (configured by the shutdown-interval link-flap command), the interface automatically comes up. If you do not specify this keyword, an interface does not come up automatically when the port status detection timer for the ports that are shut down by the link flapping protection feature expires.
Usage guidelines
Link flapping on any interface changes network topology and increases the system overhead. For example, in an active/standby link scenario, when the interface status on the active link changes between UP and DOWN, traffic switches between active and standby links. To solve this problem, execute this command.
With link flapping protection enabled on an interface, when the interface goes down, the system enables link flapping detection on the interface. During the link flapping detection interval, if the number of detected flaps reaches or exceeds the link flapping detection threshold, the system shuts down the interface.
Link flapping protection takes effect only when it is enabled in both system view and interface view.
Examples
# Enable link flapping protection globally.
<Sysname> system-view
[Sysname] link-flap protect enable
Related commands
port link-flap protect enable
loadbalance ecmp rail-group enable
Use loadbalance ecmp rail-group enable to enable the ECMP-mode rail group feature.
Use undo loadbalance ecmp rail-group enable to disable the ECMP-mode rail group feature.
Syntax
loadbalance ecmp rail-group enable
undo loadbalance ecmp rail-group enable
Views
System view
Default
The ECMP-mode rail group feature is disabled.
Predefined user roles
network-admin
Usage guidelines
This command takes effect only on a network configured with ECMP.
Example
# Enable the ECMP-mode rail group feature.
<Sysname> system-view
[Sysname] loadbalance ecmp rail-group enable
Related commands
loadbalance link-aggregation rail-group enable
loadbalance link-aggregation rail-group enable
Use loadbalance link-aggregation rail-group enable to enable the Ethernet link aggregation mode rail group feature.
Use undo loadbalance link-aggregation rail-group enable to disable the Ethernet link aggregation mode rail group feature.
Syntax
loadbalance link-aggregation rail-group enable
undo loadbalance link-aggregation rail-group enable
Views
System view
Default
The Ethernet link aggregation mode rail group feature is disabled.
Predefined user roles
network-admin
Usage guidelines
This command takes effect only on a network configured with Ethernet link aggregation.
Example
# Enable the Ethernet link aggregation mode rail group feature.
<Sysname> system-view
[Sysname] loadbalance link-aggregation rail-group enable
Relate commands
loadbalance ecmp rail-group enable
loopback-test
Use loopback-test to perform a loopback test.
Syntax
loopback-test { external | internal }
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
external: Performs an external loopback test.
internal: Performs an internal loopback test.
Usage guidelines
Execute this command to determine whether an Ethernet link works correctly. Loopback tests includes the following types:
· Internal loopback test—Tests the device where the Ethernet interface resides. The Ethernet interface sends outgoing packets back to the local device. If the device fails to receive the packets, the device fails.
· External loopback test—Tests the inter-device link. The Ethernet interface sends incoming packets back to the remote device. If the remote device fails to receive the packets, the inter-device link fails.
The shutdown, port up-mode, and loopback-test commands are mutually exclusive on an interface.
Examples
# Perform an internal loopback test on HundredGigE1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] loopback-test internal
multicast-suppression
Use multicast-suppression to enable multicast storm suppression and set the multicast storm suppression threshold.
Use undo multicast-suppression to disable multicast storm suppression.
Syntax
multicast-suppression { ratio | pps max-pps | kbps max-kbps } [ unknown ]
undo multicast-suppression
Default
Ethernet interfaces do not suppress multicast traffic.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
ratio: Sets the multicast suppression threshold as a percentage of the interface bandwidth. The value range for this argument (in percentage) is 0 to 100. A smaller value means that less multicast traffic is allowed to pass through.
pps max-pps: Specifies the maximum number of multicast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.
kbps max-kbps: Specifies the maximum number of kilobits of multicast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.
unknown: Enables multicast storm suppression only on unknown packets. If you do not specify this keyword, this command suppresses all the multicast packets that the interface can forward.
Usage guidelines
The multicast storm suppression feature limits the size of multicast traffic to a threshold on an interface. When the multicast traffic on the interface exceeds this threshold, the system drops packets until the traffic drops below this threshold.
Both the storm-constrain command and the multicast-suppression command can suppress multicast storms on a port. The multicast-suppression command uses the chip to physically suppress multicast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress multicast traffic.
For the traffic suppression result to be determined, do not execute both the storm-constrain multicast command and the multicast-suppression command on an interface.
When you configure the suppression threshold in kbps, the actual suppression threshold might be different from the configured one as follows:
· If the configured value is smaller than 64, the value of 64 takes effect.
· If the configured value is greater than 64 but not an integer multiple of 64, the integer multiple of 64 that is greater than and closest to the configured value takes effect.
To determine the suppression threshold that takes effect, see the prompts on the switch.
Set the same type of thresholds for each interface, that is, set the ratio argument, the pps max-pps option, or the kbps max-kbps option for the interface.
Examples
# Set the multicast storm suppression threshold to 10000 kbps on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] multicast-suppression kbps 10000
The actual value is 10048 on port HundredGigE1/0/1 currently.
The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.
Related commands
broadcast-suppression
unicast-suppression
port fec bypass
Use port fec bypass enable to enable FEC bypass.
Use port fec bypass disable to disable FEC bypass.
Use undo port fec bypass to restore the default.
Syntax
port fec bypass { disable | enable }
undo port fec bypass
Default
FEC bypass is disabled.
Views
Ethernet interface view
Predefined user roles
network-admin
Usage guidelines
This command is supported only on 25-GE split interfaces and 100-GE interfaces.
With FEC bypass disabled, when an interface continuously receives three or more packets that it cannot process, the device will shut down and then bring up the interface to fix the interface. However, there are many possible packet error reasons. If you are sure that the interface is not faulty, you do not need to fix the interface. To avoid service interruption in this case, you can enable FEC bypass on the interface to prevent the device from shutting down and bringing up the interface.
Examples
# Enable FEC bypass.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port fec bypass enable
port fec mode
Use port fec mode to set the forward error correction (FEC) mode of an interface.
Use undo port fec mode to restore the default.
Syntax
port fec mode { auto | none | rs-fec }
undo port fec mode
Default
The FEC mode of an interface varies by transceiver module model.
Views
25-GE split interface view
50-GE split interface view
100-GE interface view
Predefined user roles
network-admin
Parameters
auto: Specifies the FEC autonegotiation mode.
none: Performs no FEC.
rs-fec: Specifies the RS-FEC mode.
Usage guidelines
The FEC feature corrects packet errors to improve transmission quality. It attaches correction information to a packet at the sending end, and corrects error codes generated during transmission at the receiving end based on the correction information. You can set the FEC mode as needed.
Make sure you set the same FEC mode for both interfaces of a link.
Examples
# Set the FEC mode of HundredGigE1/0/1 to autonegotiation.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port fec mode auto
port ifmonitor crc-error
Use port ifmonitor crc-error to configure CRC error packet alarm parameters for an interface.
Use undo port ifmonitor crc-error to restore the default.
Syntax
port ifmonitor crc-error [ ratio ] high-threshold high-value low-threshold low-value interval interval [ down-auto-recovery | shutdown ]
undo port ifmonitor crc-error
Default
An interface uses the global CRC error packet alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
ratio: Specifies the alarm thresholds in percentage. If you do not specify this keyword, you configure the alarm thresholds in absolute value.
high-threshold high-value: Specifies the upper threshold for CRC error packet alarms. If you specify the ratio keyword, the value range is 1 to 100. If you do not specify the ratio keyword, the value range is 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for CRC error packet alarms. If you specify the ratio keyword, the value range is 1 to 100. If you do not specify the ratio keyword, the value range is 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for CRC error packets, in the range of 1 to 65535 seconds.
down-auto-recovery: Shuts down an interface when the number of incoming CRC error packets on the interface exceeds the upper threshold. When the port status detection timer for the ports that are shut down by the CRC error packet alarm feature expires, the interface automatically comes up. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters alarm state when the number of incoming CRC error packets exceeds the upper threshold on the interface, but the interface will not be shut down.
shutdown: Shuts down an interface when the number of incoming CRC error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming CRC error packets exceeds the upper threshold on the interface, but the interface will not be shut down. If you specify this keyword when the upper threshold has been exceeded on an interface, the interface will be shut down.
Usage guidelines
With the CRC error packet alarm function enabled, when the number of incoming CRC error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of incoming CRC error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can configure the CRC error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for CRC error packet alarms on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] port ifmonitor crc-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor input-error
Use port ifmonitor input-error to configure input error packet alarm parameters for an interface.
Use undo port ifmonitor input-error to restore the default.
Syntax
port ifmonitor input-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor input-error
Default
An interface uses the global input error packet alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for input error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of input error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of input error packets exceeds the upper threshold on the interface, but the interface will not be shut down. If you specify this keyword when the upper threshold has been exceeded on an interface, the interface will be shut down.
Usage guidelines
With the input error packet alarm function enabled, when the number of input error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of input error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for input error packet alarms on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] port ifmonitor input-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor input-usage
Use port ifmonitor input-usage to configure input bandwidth usage alarm parameters.
Use undo port ifmonitor input-usage to restore the default.
Syntax
port ifmonitor input-usage high-threshold high-value low-threshold low-value
undo port ifmonitor input-usage
Default
An interface uses the global input bandwidth usage alarm parameters.
Views
Interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for input bandwidth usage alarms, in the range of 1 to 100.
low-threshold low-value: Specifies the lower threshold for input bandwidth usage alarms, in the range of 1 to 100.
Usage guidelines
With the input bandwidth usage alarm function enabled, when the input bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the input bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can use the flow-interval command to set the statistics polling interval.
You can configure the input bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the input bandwidth usage alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 80 and lower threshold to 60 for input bandwidth usage alarms on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port ifmonitor input-usage high-threshold 80 low-threshold 60
Related commands
flow-interval
snmp-agent trap enable ifmonitor
port ifmonitor output-error
Use port ifmonitor output-error to configure output error packet alarm parameters for an interface.
Use undo port ifmonitor output-error to restore the default.
Syntax
port ifmonitor output-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor output-error
Default
An interface uses the global output error packet alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for output error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for output error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for output error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of output error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of output error packets exceeds the upper threshold on the interface, but the interface will not be shut down. If you specify this keyword when the upper threshold has been exceeded on an interface, the interface will be shut down.
Usage guidelines
With the output error packet alarm function enabled, when the number of output error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of output error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for output error packet alarms on GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] port ifmonitor output-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor output-usage
Use port ifmonitor output-usage to configure output bandwidth usage alarm parameters.
Use undo port ifmonitor output-usage to restore the default.
Syntax
port ifmonitor output-usage high-threshold high-value low-threshold low-value
undo port ifmonitor output-usage
Default
An interface uses the global output bandwidth usage alarm parameters.
Views
Interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for output bandwidth usage alarms, in the range of 1 to 100.
low-threshold low-value: Specifies the lower threshold for output bandwidth usage alarms, in the range of 1 to 100.
Usage guidelines
With the output bandwidth usage alarm function enabled, when the output bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the output bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can use the flow-interval command to set the statistics polling interval.
You can configure the output bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the output bandwidth usage alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 9 and lower threshold to 7 for output bandwidth usage alarms on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port ifmonitor output-usage high-threshold 9 low-threshold 7
Related commands
flow-interval
snmp-agent trap enable ifmonitor
port ifmonitor rx-pause
Use port ifmonitor rx-pause to configure received pause frame alarm parameters for an interface.
Use undo port ifmonitor rx-pause to restore the default.
Syntax
port ifmonitor rx-pause high-threshold high-value low-threshold low-value interval interval
undo port ifmonitor rx-pause
Default
An interface uses the global received pause frame alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for received pause frame alarms, in the range of 1 to 4294967295.
low-threshold low-value: Specifies the lower threshold for received pause frame alarms, in the range of 1 to 4294967295.
interval interval: Specifies the statistics collection and comparison interval for received pause frame packets, in the range of 1 to 65535 seconds.
Usage guidelines
With the received pause frame alarm function enabled, when the number of received pause frame packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of received pause frame packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can configure the received pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the received pause frame alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 90, lower threshold to 50, and statistics collection and comparison interval to 5 seconds for received pause frame alarms on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port ifmonitor rx-pause high-threshold 90 low-threshold 50 interval 5
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor tx-pause
Use port ifmonitor tx-pause to configure sent pause frame alarm parameters for an interface.
Use undo port ifmonitor tx-pause to restore the default.
Syntax
port ifmonitor tx-pause high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor tx-pause
Default
An interface uses the global sent pause frame alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for sent pause frame alarms, in the range of 1 to 4294967295.
low-threshold low-value: Specifies the lower threshold for sent pause frame alarms, in the range of 1 to 4294967295.
interval interval: Specifies the statistics collection and comparison interval for sent pause frame packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of sent pause frames on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of sent pause frames exceeds the upper threshold on the interface, but the interface will not be shut down. If you specify this keyword when the upper threshold has been exceeded on an interface, the interface will be shut down.
Usage guidelines
With the sent pause frame alarm function enabled, when the number of sent pause frame packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of sent pause frame packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
You can configure the sent pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the sent pause frame alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 50, lower threshold to 40, and statistics collection and comparison interval to 8 seconds for sent pause frame alarms on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port ifmonitor tx-pause high-threshold 50 low-threshold 40 interval 8
Related commands
snmp-agent trap enable ifmonitor
port link-flap protect enable
Use port link-flap protect enable to enable link flapping protection on an interface.
Use undo port link-flap protect enable to disable link flapping protection on an interface.
Syntax
port link-flap protect enable [ down-auto-recovery ] [ interval interval | threshold threshold ] * [ second-interval second-interval second-threshold second-threshold ]
undo port link-flap protect enable [ interval | threshold ]
Default
Link flapping protection is disabled on an interface.
Ethernet interface view
Predefined user roles
network-admin
Parameters
down-auto-recovery: Shuts down an interface when the device detects link flapping. When the port status detection timer set by the shutdown-interval link-flap command expires, the port automatically restores to its actual physical state. If you do not specify this keyword, the system does not automatically restore the interface status, and you must execute the down-auto-recovery command to manually restore the interface status.
interval interval: Specifies the level-1 link flapping detection interval in seconds. The value range for this argument is 5 to 86400. The default value for this argument is 10.
threshold threshold: Specifies the level-1 link flapping detection threshold in the range of 2 to 1200. The default value for this argument is 5.
second-interval interval: Specifies the level-2 link flapping detection interval in seconds. The value range for this argument is 5 to 86400.
second-threshold threshold: Specifies the level-2 link flapping detection threshold in the range of 2 to 1200.
Usage guidelines
Operating mechanism
When you configure this feature on an interface, how link flapping protection is triggered depends on the parameters specified:
· If you specify level-1 link flapping protection parameters but do not specify level-2 parameters, link flapping protection will be triggered and the interface will be shut down when the level-1 link flapping protection conditions are met.
· If you specify both level-1 and level-2 link flapping protection parameters, link flapping protection will be triggered and the interface will be shut down when either of level-1 and level-2 link flapping protection conditions are met.
Restrictions and guidelines
Link flapping protection takes effect only when it is enabled in both system view and interface view.
If you do not specify the interval interval or threshold threshold option, the command uses the default level-1 link flapping protection settings. If you do not specify the second-interval interval or second-threshold threshold option, the command uses only the level-1 link flapping protection settings.
If you specify the interval or threshold keyword when you execute the undo port link-flap protect enable command, the command restores the default setting for the keyword.
With link flapping protection enabled on an interface, when the interface goes down, the system enables link flapping detection on the interface. During a link flapping detection interval, if the number of detected flaps reaches or exceeds the corresponding link flapping detection threshold, the system shuts down the interface. If you specify both level-1 and level-2 link flapping protection settings, link flapping protection will be triggered and the interface will be shut down when either of level-1 and level-2 link flapping protection conditions are met.
This command, the dampening command, and the link-delay command are mutually exclusive on an Ethernet interface.
Examples
# Enable link flapping protection on an interface. Set the link flapping detection interval to 10 seconds, and set the link flapping detection threshold to 5.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE 1/0/1] port link-flap protect enable interval 10 threshold 5
Related commands
dampening
link-delay
link-flap protect enable
shutdown-interval link-flap
port link-mode
Use port link-mode to change the link mode of an Ethernet interface.
Use undo port link-mode to restore the default.
Syntax
port link-mode { bridge | route }
undo port link-mode
Default
Interfaces operate in bridge mode.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
bridge: Specifies the Layer 2 mode.
route: Specifies the Layer 3 mode.
Usage guidelines
CAUTION: Changing the link mode of an Ethernet interface also restores all commands (except description, duplex, jumboframe enable, speed, shutdown) on the Ethernet interface to their defaults in the new link mode. |
Interfaces on the device can operate either as Layer 2 or Layer 3 Ethernet interfaces.
You can use commands to set the link mode to bridge or route.
Examples
# Configure HundredGigE 1/0/1 to operate in Layer 2 mode.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port link-mode bridge
The configuration of the interface will be restored to the default. Continue? [Y/N]:y
port training
Use port training to configure link compensation on an interface.
Use undo port training to restore the default.
Syntax
port training { disable | enable }
undo port training
Default
Link compensation is disabled on an interface.
Views
25-GE interface view
Predefined user roles
network-admin
Parameters
disable: Disables link compensation.
enable: Enables link compensation.
Usage guidelines
Link compensation enables the sending and receiving ends to exchange pre-emphasis and equalization parameters through frames. This feature improves the performance of pre-emphasis and equalization.
Only 25-GE Ethernet interfaces connected through copper cables support this command. For 25-GE interfaces connected through copper cables to operate properly, you must enable link compensation.
You must enable or disable link compensation on both interfaces of a link.
Typically, the link compensation status is controlled by the software, and do not adjust the link compensation status as a best practice. Use this command to adjust the link compensation status only when the interface cannot come up.
Examples
# Enable link compensation on Twenty-FiveGigE 1/0/1.
<Sysname> system-view
[Sysname] interface twenty-fivegige 1/0/1
[Sysname-Twenty-FiveGigE1/0/1] port training enable
port transceiver-power-low trigger
Use port transceiver-power-low trigger to enable optical power anomaly detection for an interface.
Use undo port transceiver-power-low trigger to disable optical power anomaly detection for an interface.
Syntax
port transceiver-power-low trigger { down-auto-recovery | error-down }
undo port transceiver-power-low trigger
Default
Optical power anomaly detection is disabled for an interface.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
down-auto-recovery: Shuts down an interface when the optical power is abnormal on the device. When the port status detection timer set by the shutdown-interval transceiver-power-low command expires, the port automatically restores to its actual physical state.
error-down: Shuts down an interface when the optical power is abnormal on the device. Then, the interface stops forwarding all packets. After the optical power returns to normal, you must execute the undo shutdown command to restore the interface status.
Usage guidelines
When the optical power is abnormal on a device, failures such as service flapping might occur. To ensure service continuity, you can enable this feature on an interface. When the optical power is abnormal on an interface, the interface will be shut down and stop sending or receiving packets. Then, you can promptly switch service traffic to other interfaces for processing.
You can use the following methods to restore an interface when that interface is shut down because the port optical power anomaly detection feature detects interface optical power anomalies:
· Automatic recovery—With the down-auto-recovery keyword specified, the device shuts down the interface when the optical power of a transceiver module is abnormal. When the port status detection timer set by the shutdown-interval transceiver-power-low command expires, the port automatically restores to its actual physical state.
· Manual recovery—With the error-down keyword specified, the device shuts down the interface when the optical power of a transceiver module is abnormal. After the optical power returns to normal, you must execute the undo shutdown command to restore the interface status.
Examples
# Enable optical power anomaly detection on HundredGigE 1/0/1, and specify the manual interface restoration mode.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port transceiver-power-low trigger error-down
Related commands
shutdown-interval transceiver-power-low
port up-mode
Use port up-mode to forcibly bring up a fiber Ethernet port.
Use undo port up-mode to restore the default.
Syntax
port up-mode
undo port up-mode
Default
A fiber Ethernet port is not forcibly brought up. The physical state of a fiber port depends on the physical state of the fibers.
Views
Ethernet interface view
Predefined user roles
network-admin
Usage guidelines
This command forcibly brings up a fiber Ethernet port and enables the port to forward packets unidirectionally over a single link. In this way, transmission links are well utilized.
The following operations on a fiber port will cause link updown events before the port finally stays up:
· Configure both the port up-mode command and the speed or duplex command.
· Install or remove fiber links or transceiver modules after you forcibly bring up the fiber port.
The shutdown and port up-mode commands are mutually exclusive.
A fiber Ethernet port does not support this command if the port is shut down by a protocol or by using the shutdown command.
Examples
# Forcibly bring up fiber port HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port up-mode
rail-group
Use rail-group to create a rail group and enter its view.
Use undo rail-group to delete a rail group.
Syntax
rail-group group-name
undo rail-group group-name
Views
System view
Default
No rail group exists.
Predefined user roles
network-admin
Parameters
group-name: Specifies a rail group name, a string of 1 to 31 characters.
Usage guidelines
The rail group feature assigns different incoming interfaces on the device to a rail group and assigns indexes to these interfaces. The device distributes traffic across various interfaces based on their configured index values by using a specific algorithm. Traffic that arrives at different incoming interfaces is then forwarded through different outgoing interfaces, achieving traffic load sharing.
If you configure both the load sharing feature (using the ip load-sharing mode command) and the rail group feature, the rail group feature takes precedence. Traffic on interfaces within the configured rail group will be load shared using the rail group feature, and traffic on other interfaces will be load shared as configured by the ip load-sharing mode command. For more information about the ip load-sharing mode command, see Layer 3—IP Services Command Reference.
Examples
# Create a rail group named test and enter its view.
<Sysname> system-view
[Sysname] rail-group test
[Sysname-rail-group-test]
reset counters interface
Use reset counters interface to clear the interface statistics.
Syntax
reset counters interface [ interface-type [ interface-number | interface-number.subnumber ] ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number. The interface-number argument is an interface number. The subnumber argument is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
Usage guidelines
Use this command to clear history statistics if you want to collect traffic statistics for a specific time period.
If you do not specify an interface type, this command clears statistics for all interfaces.
If you specify an interface type but do not specify an interface number, this command clears statistics for all interfaces of the specified type.
Examples
# Clear the statistics for HundredGigE 1/0/1.
<Sysname> reset counters interface hundredgige 1/0/1
Related commands
display counters interface
display counters rate interface
display interface
reset ethernet statistics
Use reset ethernet statistics to clear the Ethernet module statistics.
Syntax
reset ethernet statistics [ slot slot-number ]
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command clears statistics for all IRF member devices.
Examples
# Clear the Ethernet module statistics for the specified slot.
<Sysname> reset ethernet statistics slot 1
Related commands
display ethernet statistics
reset link-state-change statistics interface
Use reset link-state-change statistics interface to clear link state change statistics of interfaces.
Syntax
reset link-state-change statistics interface [ interface-type [ interface-number ] ]
Default
Link state change statistics of an interface are not cleared.
Views
User view
Predefined user roles
network-admin
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
Usage guidelines
If you do not specify an interface type, this command clears the link state change statistics for all interfaces.
If you specify an interface type but do not specify an interface number, this command clears the link state change statistics for all interfaces of the specified type.
Examples
# Clear the link state change statistics of HundredGigE 1/0/1.
<Sysname> reset link-state-change statistics interface hundredgige 1/0/1
Related commands
display link-state-change statistics interface
reset packet-drop interface
Use reset packet-drop interface to clear the dropped packet statistics for an interface.
Syntax
reset packet-drop interface [ interface-type [ interface-number ] ]
Views
User view
Predefined user roles
network-admin
Parameters
interface-type: Specify an interface type.
interface-number: Specify an interface number.
Usage guidelines
If you do not specify an interface type, this command clears dropped packet statistics for all interfaces on the device.
If you specify an interface type but do not specify an interface number, the command clears dropped packet statistics for all interfaces of the specified type.
Examples
# Clear dropped packet statistics for HundredGigE 1/0/1.
<Sysname> reset packet-drop interface hundredgige 1/0/1
# Clear dropped packet statistics for all interfaces.
<Sysname> reset packet-drop interface
Related commands
display packet-drop
shutdown
Use shutdown to shut down an Ethernet interface or subinterface.
Use undo shutdown to bring up an Ethernet interface or subinterface.
Syntax
shutdown
undo shutdown
Default
Ethernet interfaces and subinterfaces are in up state.
Views
Ethernet interface view
Ethernet subinterface view
Predefined user roles
network-admin
Usage guidelines
CAUTION: Executing the shutdown command on an interface will disconnect the link of the interface and interrupt communication. Use this command with caution. |
Some interface configurations might require an interface restart before taking effect.
The shutdown and port up-mode commands are mutually exclusive.
The shutdown command cannot be configured on an interface in a loopback test.
Examples
# Shut down and then bring up HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] shutdown
[Sysname-HundredGigE1/0/1] undo shutdown
# Shut down and then bring up HundredGigE 1/0/1.1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1.1
[Sysname-HundredGigE1/0/1.1] shutdown
[Sysname-HundredGigE1/0/1.1] undo shutdown
shutdown all-physical-interface
Use shutdown all-physical-interfaces to shut down all physical interfaces except management Ethernet interfaces.
Use undo shutdown all-physical-interfaces to bring up all physical interfaces except management Ethernet interfaces.
Syntax
shutdown all-physical-interfaces [ include irf-physical-interface ]
undo shutdown all-physical-interfaces
Default
Physical interfaces are up.
Views
System view
Predefined user roles
network-admin
Parameters
include irf-physical-interface: Shuts down all physical interfaces including the IRF physical interfaces. If you do not specify this keyword, this command does not shut down IRF physical interfaces.
Usage guidelines
With the shutdown all-physical-interfaces command, you can shut down all physical interfaces except the management Ethernet interfaces on the device. Physical interfaces shut down by using this command are in ADM state.
This command is not effective for physical interfaces that have joined a service loopback group.
To shut down all physical interfaces or the specified interface, execute the shutdown all-physical-interfaces command in system view or execute the shutdown command in interface view.
To bring up interfaces shut down by using the shutdown all-physical-interfaces command, execute its undo form in system view. To bring up an interface shut down by using the shutdown command, execute its undo form in interface view.
If you execute this command with the include irf-physical-interface keyword multiple times, this command shuts down all physical interfaces except the management Ethernet interfaces on the device.
Examples
# Shut down all physical interfaces except management Ethernet interfaces and IRF physical interfaces.
<Sysname> system-view
[Sysname] shutdown all-physical-interfaces
Related commands
shutdown
shutdown-interval crc-error
Use shutdown-interval crc-error to set the port status detection timer for the ports that are shut down by the CRC error packet alarm feature.
Use undo shutdown-interval crc-error to restore the default.
Syntax
shutdown-interval [ crc-error ] interval
undo shutdown-interval [ crc-error ]
Default
The port status detection timer is 30 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
crc-error: Specifies the CRC error packet alarm feature. If you do not specify this keyword, the port status detection timer configured by this command takes effect for all features that support the shutdown-interval command, for example, the CRC error packet alarm feature.
interval: Specifies the port status detection timer, in the range of 0 to 300 seconds. When the value is 0, the system does not automatically restore the interface status, and you must execute the undo shutdown command to manually restore the interface status.
Usage guidelines
Operating mechanism
When a port is shut down automatically by a feature, the device starts a port status detection timer. When the timer expires, the device restores the port status to its actual physical status automatically.
If you change the timer setting during port detection, the device compares the new setting (T1) with the time that elapsed since the port was shut down (T).
· If T < T1, the port will be brought up after T1 – T seconds.
· If T ≥ T1, the port is brought up immediately.
For example, the timer setting is 30 seconds. If you change it to 10 seconds 2 seconds after the port is shut down, the port will come up 8 seconds later. If you change the timer setting to 2 seconds 10 seconds after the port is shut down, the port comes up immediately.
Restrictions and guidelines
The ifmonitor crc-error command takes effect only if you specify the down-auto-recovery keyword.
Examples
# Set the port status detection timer to 100 seconds for the ports that are shut down by the CRC error packet alarm feature.
<Sysname> system-view
[Sysname] shutdown-interval crc-error 100
Related commands
ifmonitor crc-error
shutdown-interval link-flap
Use shutdown-interval link-flap to set the port status detection timer for the ports that are shut down by the link flapping protection feature.
Use undo shutdown-interval link-flap to restore the default.
Syntax
shutdown-interval [ link-flap ] interval
undo shutdown-interval [ link-flap ]
Default
The port status detection timer is 30 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
link-flap: Specifies the link flapping protection feature. If you do not specify this keyword, the port status detection timer configured by this command takes effect for all features that support the shutdown-interval command, for example, the CRC error packet alarm feature.
interval: Specifies the port status detection timer, in the range of 0 to 300 seconds. When the value is 0, the system does not automatically restore the interface status, and you must execute the undo shutdown command to manually restore the interface status.
Usage guidelines
Operating mechanism
When a port is shut down automatically by a feature, the device starts a port status detection timer. When the timer expires, the device restores the port status to its actual physical status automatically.
If you change the timer setting during port detection, the device compares the new setting (T1) with the time that elapsed since the port was shut down (T).
· If T < T1, the port will be brought up after T1 – T seconds.
· If T ≥ T1, the port is brought up immediately.
For example, the timer setting is 30 seconds. If you change it to 10 seconds 2 seconds after the port is shut down, the port will come up 8 seconds later. If you change the timer setting to 2 seconds 10 seconds after the port is shut down, the port comes up immediately.
Restrictions and guidelines
The ifmonitor crc-error command takes effect only if you specify the down-auto-recovery keyword.
Examples
# Set the port status detection timer to 100 seconds for the ports that are shut down by the link flapping protection feature.
<Sysname> system-view
[Sysname] shutdown-interval link-flap 100
Related commands
port link-flap protect enable
shutdown-interval transceiver-power-low
Use shutdown-interval transceiver-power-low to set the port status detection timer for the ports that are shut down by the optical power anomaly detection feature.
Use undo shutdown-interval transceiver-power-low to restore the default.
Syntax
shutdown-interval [ transceiver-power-low ] interval
undo shutdown-interval [ transceiver-power-low ]
Default
The port status detection timer is 30 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
transceiver-power-low: Specifies the optical power anomaly detection feature. If you do not specify this keyword, the port status detection timer configured by this command takes effect for all features that support the shutdown-interval command, for example, the CRC error packet alarm feature.
interval: Specifies the port status detection timer, in the range of 0 to 300 seconds. When the value is 0, the system does not automatically restore the interface status, and you must execute the undo shutdown command to manually restore the interface status.
Usage guidelines
Operating mechanism
When a port is shut down automatically by a feature, the device starts a port status detection timer. When the timer expires, the device restores the port status to its actual physical status automatically.
If you change the timer setting during port detection, the device compares the new setting (T1) with the time that elapsed since the port was shut down (T).
· If T < T1, the port will be brought up after T1 – T seconds.
· If T ≥ T1, the port is brought up immediately.
For example, the timer setting is 30 seconds. If you change it to 10 seconds 2 seconds after the port is shut down, the port will come up 8 seconds later. If you change the timer setting to 2 seconds 10 seconds after the port is shut down, the port comes up immediately.
Restrictions and guidelines
The ifmonitor crc-error command takes effect only if you specify the down-auto-recovery keyword.
Examples
# Set the port status detection timer to 100 seconds for the ports that are shut down by the optical power anomaly detection feature.
<Sysname> system-view
[Sysname] shutdown-interval transceiver-power-low 100
Related commands
port transceiver-power-low trigger
snmp-agent trap enable eth
Use snmp-agent trap enable eth to enable SNMP notifications for the ETH module.
Use undo snmp-agent trap enable eth to disable SNMP notifications for the ETH module.
Syntax
snmp-agent trap enable eth
undo snmp-agent trap enable eth
Default
SNMP notifications are disabled for the ETH module.
Views
System view
Predefined user roles
network-admin
Usage guidelines
To report critical ETH events to an SNMP NMS, enable SNMP notifications for the ETH module.
For ETH SNMP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see SNMP configuration in Network Management and Monitoring Configuration Guide.
Examples
# Enable SNMP notifications for the ETH module.
<Sysname> system-view
[Sysname] snmp-agent trap enable eth
snmp-agent trap enable ifmonitor
Use snmp-agent trap enable ifmonitor to enable interface alarm functions.
Use undo snmp-agent trap enable ifmonitor to disable interface alarm functions.
Syntax
snmp-agent trap enable ifmonitor [ crc-error | input-error | input-usage | output-error | output-usage | rx-pause | tx-pause ] *
undo snmp-agent trap enable ifmonitor [ crc-error | input-error | input-usage | output-error | output-usage | rx-pause | tx-pause ] *
Default
All interface alarm functions are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
crc-error: Enables the input CRC error packet alarm function for interfaces. With the CRC error packet alarm function enabled, when the number of incoming CRC error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the number of incoming CRC error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
input-error: Enables the input error packet alarm function for interfaces. With the input error packet alarm function enabled, when the number of input error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the number of input error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
input-usage: Enables the input bandwidth usage alarm function for interfaces. With the input bandwidth usage alarm function enabled, when the input bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the input bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
output-error: Enables the output error packet alarm function for interfaces. With the output error packet alarm function enabled, when the number of output error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the number of output error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
output-usage: Enables the output bandwidth usage alarm function for interfaces. With the output bandwidth usage alarm function enabled, when the output bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the output bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
rx-pause: Enables the received pause frame alarm function for interfaces. guidelines With the received pause frame alarm function enabled, when the number of received pause frames on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the number of received pause frames on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
tx-pause: Enables the sent pause frame alarm function for interfaces. With the sent pause frame alarm function enabled, when the number of sent pause frames on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the number of sent pause frames on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
Usage guidelines
Operating mechanism
With interface alarm functions enabled, when the number of incoming or outgoing error packets or the bandwidth usage on an interface exceeds the upper threshold or drops below the lower threshold, the interface generates an alarm. Error packets include CRC error packets, error packets, pause frames, SDH-B1 error packets, SDH-B2 error packets, and SDH error packets.
Prerequisites
To report critical interface events to an NMS, enable SNMP notifications for Ethernet interfaces. For interface alarms to be sent correctly, you must also configure SNMP as described in Network Management and Monitoring Configuration Guide.
For more information about the alarm thresholds, see the commands listed in related commands.
Restrictions and guidelines
If you do not specify any parameters, this feature enables or disables all alarm functions on interfaces. If you specify a parameter, this feature enables only the alarm function specified by that parameter.
Examples
# Enable the CRC error packet alarm function for interfaces.
<Sysname> system-view
[Sysname] snmp-agent trap enable ifmonitor crc-error
Related commands
ifmonitor crc-error
ifmonitor input-error
ifmonitor input-usage
ifmonitor output-error
ifmonitor output-usage
ifmonitor rx-pause
ifmonitor sdh-b1-error
ifmonitor sdh-b2-error
ifmonitor sdh-error
ifmonitor tx-pause
port ifmonitor crc-error
port ifmonitor input-error
port ifmonitor input-usage
port ifmonitor output-error
port ifmonitor output-usage
port ifmonitor rx-pause
port ifmonitor sdh-b1-error
port ifmonitor sdh-b2-error
port ifmonitor sdh-error
port ifmonitor tx-pause
speed
Use speed to set the speed of an Ethernet interface.
Use undo speed to restore the default.
Syntax
speed { 10 | 100 | 1000 | 10000 | 25000 | 40000 | 100000 | auto }
undo speed
Default
An Ethernet interface negotiates a speed with its peer.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
10: Sets the interface speed to 10 Mbps.
100: Sets the interface speed to 100 Mbps.
1000: Sets the interface speed to 1000 Mbps.
10000: Sets the interface speed to 10000 Mbps.
25000: Sets the interface speed to 25000 Mbps.
40000: Sets the interface speed to 40000 Mbps.
100000: Sets the interface speed to 100000 Mbps.
400000: Sets the interface speed to 400000 Mbps.
auto: Enables the interface to negotiate a speed with its peer.
Usage guidelines
For an Ethernet copper port, use the speed command to set its speed to match the speed of the peer interface. Support of copper ports for keywords of this command varies by copper port type. For more information, use the speed ? command in interface view. If the system does not prompt that operation failed when you configure a speed for a copper port, the copper port supports this speed. Otherwise, the copper port does not support this speed.
For a fiber port, use the speed command to set its speed to match the rate of a transceiver module. Support of fiber ports for keywords of this command varies by fiber port type. For more information, use the speed ? command in interface view. If the system does not prompt that operation failed when you configure a speed for a fiber port, the fiber port supports this speed. Otherwise, the fiber port does not support this speed.
Additionally, you must select a speed for a fiber port according to the transceiver module installed to ensure that the transceiver module can be used properly. If the transceiver module installed in a fiber port does not support the speed for the fiber port, the transceiver module cannot be used. For example, if the transceiver module installed in an SFP+ fiber port is an SFP GE transceiver module and the speed 10000 command is executed on the fiber port or the transceiver module installed in an SFP+ fiber port is a 10-GE transceiver module and the speed 1000 command is executed on the fiber port, the transceiver module cannot be used.
When an SFP-GE-T or SFP-GE-T-D transceiver module is installed in a fixed SFP port of the device, you can use the speed command to set the speed to 1000 Mbps or use the speed auto command to configure the port to autonegotiate the speed to 1000 Mbps.
For more information, see Layer 2—LAN Switching Configuration Guide.
Examples
# Configure HundredGigE 1/0/1 to autonegotiate the speed.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] speed auto
unicast-suppression
Use unicast-suppression to enable unknown unicast storm suppression and set the unknown unicast storm suppression threshold.
Use undo unicast-suppression to disable unknown unicast storm suppression.
Syntax
unicast-suppression { ratio | pps max-pps | kbps max-kbps }
undo unicast-suppression
Default
Ethernet interfaces do not suppress unknown unicast traffic.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
ratio: Sets the unknown unicast suppression threshold as a percentage of the interface bandwidth. The value range for this argument (in percentage) is 0 to 100. A smaller value means that less unknown unicast traffic is allowed to pass through.
pps max-pps: Specifies the maximum number of unknown unicast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.
kbps max-kbps: Specifies the maximum number of kilobits of unknown unicast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.
Usage guidelines
The unknown unicast storm suppression feature limits the size of unknown unicast traffic to a threshold on an interface. When the unknown unicast traffic on the interface exceeds this threshold, the system discards packets until the unknown unicast traffic drops below this threshold.
Both the storm-constrain command and the unicast-suppression command can suppress unknown unicast storms on a port. The unicast-suppression command uses the chip to physically suppress unknown unicast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress unknown unicast traffic.
For the unknown unicast traffic suppression result to be determined, do not configure both the storm-constrain unicast command and the unicast-suppression command on an interface.
When you configure the suppression threshold in kbps, the actual suppression threshold might be different from the configured one as follows:
· If the configured value is smaller than 64, the value of 64 takes effect.
· If the configured value is greater than 64 but not an integer multiple of 64, the integer multiple of 64 that is greater than and closest to the configured value takes effect.
For the suppression threshold that takes effect, see the prompt on the device.
Set the same type of thresholds for each interface, that is, set the ratio argument, the pps max-pps option, or the kbps max-kbps option for the interface.
Examples
# Set the unknown unicast storm suppression threshold to 10000 kbps on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] unicast-suppression kbps 10000
The actual value is 10048 on port HundredGigE1/0/1 currently.
The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.
Related commands
broadcast-suppression
multicast-suppression
using hundredgige
Use using hundredgige to combine breakout interfaces split from a 100-GE interface into a 100-GE interface,.
Syntax
using hundredgige
Default
The breakout interfaces are not combined and operate as single interfaces.
Views
10-GE breakout interface view
25-GE breakout interface view
Predefined user roles
network-admin
Usage guidelines
If you need higher bandwidth on a single interface, perform the following tasks as needed:
· After a 100-GE interface has a split-capable 40-GE transceiver module or cable installed, you can combine the four 10-GE breakout interfaces into a 100-GE interface. To do so, execute this command on any of these 10-GE breakout interfaces.
· You can combine four 25-GE breakout interfaces split from a 100-GE interface into a 100-GE interface. To do so, execute this command on any of these 25-GE breakout interfaces.
Device reboot is not required for this command to take effect. You can view the split or combined interface by using the display interface brief command.
Examples
# Combine Ten-GigabitEthernet 1/0/1:1 through Ten-GigabitEthernet 1/0/1:4 into an interface.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 1/0/1:1
[Sysname-Ten-GigabitEthernet1/0/1:1]using hundredgige
The interfaces Ten-GigabitEthernet1/0/1:1 through Ten-GigabitEthernet1/0/1:10 will be deleted. Continue? [Y/N]:y
# Combine Twenty-FiveGigE 1/0/1:1 through Twenty-FiveGigE 1/0/1:4 into a 100-GE interface.
<Sysname> system-view
[Sysname] interface twenty-fivegige 1/0/1:1
[Sysname-Twenty-FiveGigE1/0/1:1] using hundredgige
The interfaces Twenty-FiveGigE 1/0/1:1 through Twenty-FiveGigE 1/0/1:4 will be deleted. Continue? [Y/N]:y
Related commands
using tengige
using twenty-fivegige
using tengige
Use using tengige to split a high bandwidth interface into multiple 10-GE breakout interfaces.
Syntax
using tengige
Default
A high bandwidth interface is not split and operates as a single interface.
Views
100-GE interface view
Predefined user roles
network-admin
Usage guidelines
To improve port density, reduce costs, and improve network flexibility, you can split a high bandwidth interface into multiple 10-GE breakout interfaces. For example:
· Split a 100-GE interface HundredGigE 1/0/1 with a split-capable 40-GE transceiver module or cable installed into four 10-GE breakout interfaces Ten-GigabitEthernet 1/0/1:1 through Ten-GigabitEthernet 1/0/1:4.
After executing this command, you do not need to reboot the device. To view information about the 10-GE breakout interfaces, execute the display interface brief command.
On the device, only odd-numbered interfaces can be split. When an odd-numbered interface is split, the even-numbered interface whose interface number is the odd number plus 1 is also deleted.
An interface with any of the following configurations cannot be split:
· IRF physical interface.
· Service loopback group member.
· Reflector port for mirroring.
· Forcibly bringing up a fiber port.
Examples
# Split HundredGigE 1/0/1 into 10-GE breakout interfaces.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] using tengige
The interface HundredGigE1/0/1 will be deleted. Continue? [Y/N]:y
Related commands
using twenty-fivegige
Use using twenty-fivegige to split a 100-GE interface into four 25-GE breakout interfaces.
Syntax
using twenty-fivegige
Default
A 100-GE interface is not split and operates as a single interface.
Views
100-GE interface view
Predefined user roles
network-admin
Usage guidelines
To improve port density, reduce costs, and improve network flexibility, you can split a 100-GE interface into four 25-GE breakout interfaces. For example, you can split the 100-GE interface HundredGigE 1/0/1 into four 25-GE breakout interfaces Twenty-FiveGigE 1/0/1:1 through Twenty-FiveGigE 1/0/1:4.
After executing this command, you do not need to reboot the device. To view information about the breakout interfaces, execute the display interface brief command. Only odd-numbered interfaces on the switch can be split. When an odd-numbered interface is split, the interface numbered the odd number + 1 is deleted.
An interface with any of the following configurations cannot be split:
· IRF physical interface.
· Service loopback group member.
· Reflector port for mirroring.
· Forcibly bringing up a fiber port.
Examples
# Split HundredGigE 1/0/1 into four 25-GE breakout interfaces.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] using twenty-fivegige
The interface HundredGigE1/0/1 will be deleted. Continue? [Y/N]:y
Related commands
using hundredgige
Layer 2 Ethernet interface commands
display storm-constrain
Use display storm-constrain to display storm control settings and statistics.
Syntax
display storm-constrain [ broadcast | multicast | unicast ] [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
broadcast: Displays broadcast storm control settings and statistics.
multicast: Displays multicast storm control settings and statistics.
unicast: Displays unknown unicast storm control settings and statistics.
interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify this option, the command displays storm control settings and statistics for all storm control-enabled interfaces.
Usage guidelines
If you do not specify any keywords, this command displays all storm control settings on all storm control-enabled interfaces.
Examples
# Display the storm control settings on all storm control-enabled ports.
<Sysname> display storm-constrain
Abbreviation: BC - broadcast; MC - multicast; UC - unknown unicast;
FW - forwarding
Flow Statistic Interval: 5 (in seconds)
Port Type Lower Upper Unit Mode Status Trap Log StateChg
--------------------------------------------------------------------------------
HGE1/0/1 MC 100 200 kbps shutdown shutdown off on 10
Table 11 Command output
Field |
Description |
Flow Statistic Interval |
Traffic polling interval (in seconds) of the storm control module. |
Port |
Abbreviated interface name. |
Type |
Type of traffic subjected to storm control: · BC—Broadcast packets. · MC—Multicast packets. · UC—Unknown unicast packets. · KNUC—Known unicast packets. This field is not supported in the current software version. |
Lower |
Lower storm control threshold, in pps, kbps, or percentage. |
Upper |
Upper storm control threshold, in pps, kbps, or percentage. |
Unit |
Storm control threshold unit: · pps. · kbps. · percentage. |
Mode |
Action (block or shutdown) taken on the interface when the upper threshold is reached. N/A indicates that no action is configured. |
Status |
Packet forwarding status: · FW—The port is forwarding traffic correctly. · shutdown—The port has been shut down. · block—The port drops the type of traffic. |
Trap |
Status of the storm control threshold event trap switch: · on—The port sends threshold event traps. · off—The port does not send threshold event traps. |
Log |
Status of the storm control threshold event log switch: · on—The port sends threshold event log messages. · off—The port does not send threshold event log messages. |
StateChg |
Number of forwarding state changes of the interface. When the StateChg field reaches 65535, it resets automatically. |
port bridge enable
Use port bridge enable to enable bridging on an Ethernet interface.
Use undo port bridge enable to disable bridging on an Ethernet interface.
Syntax
port bridge enable
undo port bridge enable
Default
Bridging is disabled on an Ethernet interface.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
Usage guidelines
By default, the device drops packets whose outgoing interface and incoming interface are the same.
To enable the device to forward such packets rather than drop them, configure this command in Ethernet interface view. After the device receives a broadcast or unknown unicast packet, the device forwards the packet through all interfaces in the VLAN to which the incoming interface of the packet belongs.
Do not add interfaces configured with this command to an aggregation group.
Bridging and Ethernet service instance configuration are mutually exclusive on an interface.
Examples
# Enable bridging on HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] port bridge enable
storm-constrain
Use storm-constrain to enable storm control and set thresholds for broadcast, multicast, or unknown unicast packets on an Ethernet interface.
Use undo storm-constrain to disable storm control for broadcast, multicast, unknown unicast, or all types of traffic.
Syntax
storm-constrain { broadcast | multicast | unicast } { pps | kbps | ratio } upperlimit lowerlimit
undo storm-constrain { all | broadcast | multicast | unicast }
Default
Traffic storm control is disabled.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
Parameters
all: Disables storm control for all types of traffic: broadcast, multicast, and unknown unicast.
broadcast: Enables or disables broadcast storm control.
multicast: Enables or disables multicast storm control.
unicast: Enables or disables unknown unicast storm control.
pps: Sets storm control thresholds in pps.
kbps: Sets storm control thresholds in kbps.
ratio: Sets storm control thresholds as a percentage of the transmission capacity of the interface.
upperlimit: Sets the upper threshold, in pps, kbps, or percentage.
· If you specify the pps keyword, the value range for the upperlimit argument is 1 to 1.4881 × the interface bandwidth.
· If you specify the kbps keyword, the value range for the upperlimit argument is 1 to the interface bandwidth.
· If you specify the ratio keyword, the value range for the upperlimit argument is 1 to 100.
lowerlimit: Sets the lower threshold, in pps, kbps, or percentage.
· If you specify the pps keyword, the value range for the lowerlimit argument is 1 to 1.4881 × the interface bandwidth.
· If you specify the kbps keyword, the value range for the lowerlimit argument is 1 to the interface bandwidth.
· If you specify the ratio keyword, the value range for the lowerlimit argument is 1 to 100.
Usage guidelines
After you configure storm control for a type of traffic, the device collects the statistics for the type of traffic at the interval configured by using the storm-constrain interval command. When the type of traffic exceeds its upper threshold, the interface takes an action configured by using the storm-constrain control command.
The storm-constrain, broadcast-suppression, multicast-suppression, and unicast-suppression commands can suppress storms on an interface. The broadcast-suppression, multicast-suppression, and unicast-suppression commands use the chip to physically suppress traffic. They have less influence on the device performance than the storm-constrain command, which uses software to suppress traffic.
For the traffic suppression result to be determined, do not configure both storm control and storm suppression for the same type of traffic.
When configuring this command, make sure upperlimit is greater than lowerlimit.
Examples
# Enable unknown unicast storm control on HundredGigE 1/0/1 and set the upper and lower thresholds to 200 pps and 150 pps, respectively.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] storm-constrain unicast pps 200 150
# Enable broadcast storm control on HundredGigE 1/0/2, and set the upper and lower thresholds to 2000 kbps and 1500 kbps, respectively.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/2
[Sysname-HundredGigE1/0/2] storm-constrain broadcast kbps 2000 1500
# Enable multicast storm control on HundredGigE 1/0/3, and set the upper and lower thresholds to 80% and 15%, respectively.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/3
[Sysname-HundredGigE1/0/3] storm-constrain multicast ratio 80 15
Related commands
storm-constrain control
storm-constrain interval
storm-constrain control
Use storm-constrain control to set the action to take on an Ethernet interface when a type of traffic (unknown unicast, multicast, or broadcast) exceeds the upper storm control threshold.
Use undo storm-constrain control to restore the default.
Syntax
storm-constrain control { block | shutdown }
undo storm-constrain control
Default
No action is taken on an Ethernet interface when a type of traffic exceeds the upper storm control threshold.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
Parameters
block: Blocks this type of traffic and forwards other types of traffic. Even though the interface does not forward the blocked traffic, it still counts the traffic. When the blocked traffic drops below the lower threshold, the port begins to forward the traffic.
shutdown: Goes down automatically. The interface goes down automatically and stops forwarding any traffic. When the blocked traffic drops below the lower threshold, the interface does not forward the traffic. To bring up the interface, use the undo shutdown command or disable storm control on the interface.
Examples
# Configure HundredGigE 1/0/1 to block a specific type of traffic when the type of traffic exceeds the upper storm control threshold.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] storm-constrain control block
Related commands
storm-constrain
storm-constrain control
storm-constrain enable log
Use storm-constrain enable log to enable an Ethernet interface to output log messages when it detects storm control threshold events.
Use undo storm-constrain enable log to disable an Ethernet interface from outputting log messages for storm control threshold events.
Syntax
storm-constrain enable log
undo storm-constrain enable log
Default
An Ethernet interface outputs log messages when monitored traffic exceeds the upper threshold or drops below the lower threshold from a value above the upper threshold.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
Examples
# Enable HundredGigE 1/0/1 to output log messages when it detects storm control threshold events.
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] storm-constrain enable log
storm-constrain enable trap
Use storm-constrain enable trap to enable an Ethernet interface to send storm control threshold event traps.
Use undo storm-constrain enable trap to disable an Ethernet interface from sending storm control threshold event traps.
Syntax
storm-constrain enable trap
undo storm-constrain enable trap
Default
An interface sends out storm control threshold event traps when monitored traffic exceeds the upper threshold or drops below the lower threshold from a value above the upper threshold.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
Examples
# Enable HundredGigE 1/0/1 to send traps when it detects storm control threshold events.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] storm-constrain enable trap
storm-constrain interval
Use storm-constrain interval to set the traffic polling interval of the storm control module.
Use undo storm-constrain interval to restore the default.
Syntax
storm-constrain interval interval
undo storm-constrain interval
Default
The storm control module polls traffic statistics every 10 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Sets the traffic polling interval of the storm control module. The value range is 1 to 300 seconds. To ensure network stability, as a best practice, do not use a traffic polling interval shorter than 10 seconds.
Usage guidelines
The traffic polling interval set by using the storm-constrain interval command is specific to storm control. To set the statistics polling interval of an interface, use the flow-interval command.
Examples
# Set the traffic statistics polling interval of the storm control module to 60 seconds.
<Sysname> system-view
[Sysname] storm-constrain interval 60
Related commands
storm-constrain
storm-constrain control
Layer 3 Ethernet interface or subinterface commands
mac-address
Use mac-address to set the MAC address of an Ethernet interface.
Use undo mac-address to restore the default.
Syntax
mac-address mac-address
undo mac-address
Default
No MAC address is set for a Layer 3 Ethernet interface.
Views
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Predefined user roles
network-admin
Parameters
mac-address: Specifies a MAC address in the format of H-H-H.
Usage guidelines
Do not set a VRRP-reserved MAC address for a Layer 3 Ethernet subinterface.
Examples
# Set the MAC address of HundredGigE 1/0/1 to 0001-0001-0001.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] mac-address 1-1-1
mtu
Use mtu to set the MTU for an Ethernet interface or subinterface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of an Ethernet interface or subinterface is 1500 bytes.
Views
Layer 3 Ethernet interface view
Layer 3 Ethernet subinterface view
Predefined user roles
network-admin
Parameters
size: Sets the MTU in bytes. The value range for this argument is 128 to 9416.
Usage guidelines
The MTU configured on an interface takes effect only on packets sent to the CPU for software forwarding. Configure the MTU as appropriate for interfaces in the network to avoid fragmentation.
If an interface supports both the mtu and ip mtu commands, the device fragments an IPv4 packet based on the MTU set by using the ip mtu command. For more information about the ip mtu command, see Layer 3—IP Services Command Reference.
Examples
# Set the MTU to 1430 bytes for HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] mtu 1430
# Set the MTU to 1430 bytes for HundredGigE 1/0/1.1.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1.1
[Sysname-HundredGigE1/0/1.1] mtu 1430