- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
03-Ethernet interface commands | 679.66 KB |
Contents
Common Ethernet interface commands
display fdr-statistics interface
display ifmonitor buffer statistics
display ifmonitor buffer status
display link-state-change statistics interface
loadbalance ecmp lbn-group enable
loadbalance ecmp lbn-group mode
loadbalance link-aggregation lbn-group enable
port ifmonitor buffer queue enable
port ifmonitor buffer queue threshold
reset link-state-change statistics interface
shutdown all-physical-interface
snmp-agent trap enable ifmonitor
Layer 2 Ethernet interface commands
Layer 3 Ethernet interface or subinterface commands
Ethernet interface commands
Common Ethernet interface commands
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 MSTP 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 FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] dampening
# Enable interface dampening on FourHundredGigE 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 fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] dampening 2 800 3000 5
Related commands
display interface
link-delay
port link-flap protect enable
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 the slot number of the device, which is fixed at 1.
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 1 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. · ISISNum—Number of packets encapsulated by using ISIS. · 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. This parameter is not supported in the current software version. · 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 fdr-statistics interface
Use display fdr-statistics interface to display Flight Data Recorder (FDR) statistics for an interface.
Syntax
display fdr-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
You can execute this command to display FDR statistics for interfaces. FDR collects FEC information, which can help you evaluate the robustness and quality for a link.
If you do not specify an interface type and interface number, this command displays FDR statistics for all interfaces.
If you specify an interface type but do not specify an interface number, this command displays FDR statistics for all interfaces of the specified type.
Examples
# Display FDR statistics for Layer 3 Ethernet interface FourHundredGigE 1/0/1.
<Sysname> display fdr-statistics interface FourHundredGigE 1/0/1
Collecting Data ...
FDR start to collect data timestamp: 8267.762672128 sec
FDR end to collect data timestamp: 12137.849311488 sec
Number of Uncorrected codewords: 4 0
Number of codewords: 2476043710513 585958921
Symbol errors: 32 0
code words err S0: 2476043710422 585958930
code words err S1: 0 0
code words err S2: 0 0
code words err S3: 0 0
code words err S4: 0 0
code words err S5: 0 0
code words err S6: 0 0
code words err S7: 0 0
code words err S8: 4 0
code words err S9: 0 0
code words err S10: 0 0
code words err S11: 0 0
code words err S12: 0 0
code words err S13: 0 0
code words err S14: 0 0
code words err S15: 0 0
code words err S16: 0 0
Table 2 Command output
Field |
Description |
Collecting Data |
Data collected by FDR. |
PRE-FEC is not work now |
PRE-FEC is not operating. |
FDR start to collect data timestamp |
Time when FDR started to collect data. |
FDR end to collect data timestamp |
Time when FDR stopped collecting data. |
Number of Uncorrected codewords |
Number of uncorrectable codewords. The data in column 2 represents cumulative interface statistics. The data in column 3 represents the most recent interface statistics. |
Number of codewords |
Number of codewords processed by FEC. The data in column 2 represents cumulative interface statistics. The data in column 3 represents the most recent interface statistics. |
Symbol errors |
Total number of error symbols processed by FEC, and each symbol in an FEC packet contains 10 bits. The data in column 2 represents cumulative interface statistics. The data in column 3 represents the most recent interface statistics. |
code words err Sn |
Number of codewords that have the specified entries for error symbols. Each codeword has multiple symbols. The data in column 2 represents cumulative interface statistics. The data in column 3 represents the most recent interface statistics. |
display ifmonitor buffer statistics
Use display ifmonitor buffer statistics to display monitoring and data collection statistics for the buffer on an interface.
Syntax
display ifmonitor buffer statistics interface interface-type interface-number [ queue queue-index ] [ last number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. The interface-type argument represents the interface type and the interface-number argument represents the interface number.
queue queue-index: Specifies a queue by its index. If you do not specify a queue, this command displays statistics about all queues.
last number: Displays the most recently generated statistic entries. If you do not specify this keyword, this command displays the statistics within the last 24 hours.
Examples
# Display the monitoring and data collection statistics for the buffer on FourHundredGigE1/0/1.
<Sysname> display ifmonitor buffer statistics interface fourhundredgige 1/0/1
Queue: 1
Time: 2021-06-02 14:54:43
Input:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Output:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Time: 2021-06-02 14:49:43
Input:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Output:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Queue: 2
Time: 2021-06-02 14:54:43
Input:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Output:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Time: 2021-06-02 14:49:43
Input:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Output:
A-Rate: 840385600
P-Rate: 845712000
Discard: 29956755
A-Buffer: 2503
P-Buffer: 2507
Buffer Rate: 12%
Table 3 Command output
Field |
Description |
Queue |
Queue number. |
Time |
Time when statistics collection started. |
Input |
Input interface. |
Output |
Output interface. |
A-Rate |
Average rate of the packet, in bps. |
P-Rate |
Peak rate of the packet, in bps. |
Discard |
Number of dropped packets. |
A-Buffer |
Average buffer usage, in bytes. |
P-Buffer |
Peak buffer usage, in bytes. |
Buffer Rate |
Buffer usage, in percentage. |
Related commands
ifmonitor buffer mode
port ifmonitor buffer queue enable
display ifmonitor buffer status
Use display ifmonitor buffer status to display the status of the buffer statistics monitoring and collection feature on an interface.
Syntax
display ifmonitor buffer status [ interface interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface interface-type interface-number: Specifies an interface by its type and number. The interface-type argument represents the interface type and the interface-number argument represents the interface number.
Usage guidelines
To clear interface statistics, execute the reset counters interface command.
Examples
# Display the status of the buffer statistics monitoring and collection feature.
<Sysname> display ifmonitor buffer status
Slot 1 Mode: standard
Interface/Queue Interval(ms) InputDiscard OutputDiscard
400GE1/0/1 - 0 0
queue1 10 0 0
queue2 5 0 0
queue3 10 0 0
queue4 10 0 0
queue5 10 0 0
queue6 10 0 0
400GE1/0/2 - 0 0
queue1 10 0 0
queue2 5 0 0
queue3 10 0 0
queue4 10 0 0
queue5 10 0 0
queue6 10 0 0
Table 4 Command output
Field |
Description |
Chassis |
Member ID. |
Slot |
Slot number of the card. |
Mode |
Modes of the buffer statistics monitoring and collection feature: · Standard mode · Enhanced mode |
Interface/Queue |
Interface name or interface queue number. |
Interval |
Collection interval. |
InputDiscard |
Number of dropped packets in the incoming queue. |
OutputDiscard |
Number of dropped packets in the outgoing queue. |
Related commands
ifmonitor buffer mode
port ifmonitor buffer queue enable
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 27 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.
This command only counts payload data.
Examples
# Display information about Layer 3 interface FourHundredGigE 1/0/1.
<Sysname> display interface fourhundredgige 1/0/1
FourHundredGigE1/0/1
Current state: Administratively DOWN
Line protocol state: DOWN
Description: FourHundredGigE1/0/1 Interface
Bandwidth: 400000000 kbps
Link delay (up): 10 msec. Link delay (down): 1 msec
Fec counter Last 15mins uncorr errors: 0, corr errors: 0
Peak1 Fec counter uncorr errors: 0, corr errors: 0 00/00/0000 00:00:00:000000
Peak2 Fec counter uncorr errors: 0, corr errors: 0 00/00/0000 00:00:00:000000
PRE-FEC is not work now. PRE-FEC Last 30 seconds BER: <0.00e+00
SER[0]: <0.00e+00 SER[1]: <0.00e+00 SER[2]: <0.00e+00 SER[3]: <0.00e+00
SER[4]: <0.00e+00 SER[5]: <0.00e+00 SER[6]: <0.00e+00 SER[7]: <0.00e
+00
Each serdes rate is:53.125 Gbps
Packets received of length [Byte]:
[64]: 0 [65-127]: 0 [128-255]: 0
[256-511]: 0 [512-1023]: 0 [1024-1518]: 0
[1519-2047]: 0 [2048-4095]: 0 [4096-9216]: 0 [9217-16383]: 0
Packets transmitted of length [Byte]:
[64]: 0 [65-127]: 0 [128-255]: 0
[256-511]: 0 [512-1023]: 0 [1024-1518]: 0
[1519-2047]: 0 [2048-4095]: 0 [4096-9216]: 0 [9217-16383]: 0
Maximum transmission unit: 1500
Allow jumbo frames to pass
Internet protocol processing: Disabled
IP packet frame type: Ethernet II, hardware address: 3822-d666-bd0c
IPv6 packet frame type: Ethernet II, hardware address: 3822-d666-bd0c
Media type is not sure, port hardware type is No connector
Port power is 12W
Port priority: 2
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
Last link flapping: 6 hours 39 minutes 28 seconds
Last hardware down reason: PHY line side is down
Last clearing of counters: Never
Current system time:2019-01-08 14:50:06
Last time when physical state changed to up:2019-01-08 14:49:45
Last time when physical state changed to down:2019-01-08 14:49:45
Peak input rate: 0 bytes/sec, at 2013-07-07 16:07:11
Peak output rate: 0 bytes/sec, at 2013-07-07 16:07:11
Last 300 seconds input: 0 packets/sec 0 bytes/sec 0%
Last 300 seconds output: 0 packets/sec 0 bytes/sec 0%
Traffic statistic: Not include Inter-frame Gaps and Preambles
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, - 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, - aborts
- ignored, - parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, - pauses
Output (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
- 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 FourHundredGigE 1/0/1.
<Sysname> display interface fourhundredgige 1/0/1
FourHundredGigE1/0/1
Current state: DOWN
Line protocol state: DOWN
IP packet frame type: Ethernet II, hardware address: 000c-2963-b767
Description: FourHundredGigE1/0/1 Interface
Bandwidth: 400000000 kbps
Link delay (up): 10 msec. Link delay (down): 1 msec
Loopback is not set
Media type is not sure, port hardware type is No connector
Port power is 12W
Fec counter Last 15mins uncorr errors: 0, corr errors: 0
Peak1 Fec counter uncorr errors: 0, corr errors: 0 00/00/0000 00:00:00:000000
Peak2 Fec counter uncorr errors: 0, corr errors: 0 00/00/0000 00:00:00:000000
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 frame to pass
Broadcast max-ratio: 100%
Unknown-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: 6 hours 39 minutes 25 seconds
Last hardware down reason: PHY line side is down
Last clearing of counters: 14:34:09 Tue 11/01/2011
Current system time:2019-01-08 14:50:06
Last time when physical state changed to up:2019-01-08 14:49:45
Last time when physical state changed to down:2019-01-08 14:49:45
Peak input rate: 0 bytes/sec, at 2013-07-17 22:06:19
Peak output rate: 0 bytes/sec, at 2013-07-17 22:06:19
Last 300 seconds input: 0 packets/sec 0 bytes/sec -%
Last 300 seconds output: 0 packets/sec 0 bytes/sec -%
Traffic statistic: Not include Inter-frame Gaps and Preambles
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
Table 5 Command output
Field |
Description |
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · DOWN (up-delay)—The interface up event is delayed on the interface, because the port up-delay command is executed on the interface. · DOWN ( Link-Aggregation interface down )—The aggregate interface to which the interface belongs has been shut down by using the shutdown command. · DOWN ( Tunnel-Bundle administratively down )—The tunnel bundle 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. · 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: ¡ 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. ¡ MACSEC—Shuts down the data link layer when it fails to negotiate the encryption parameters. |
Bandwidth |
Expected bandwidth of the interface. |
Link delay (up): 10 msec. Link delay (down): 1 msec |
Physical connection status suppression time of the interface, in milliseconds. |
Maximum transmission unit |
MTU of the interface. |
Internet protocol processing |
IP packet processing capability of the interface when the interface is not assigned an IP address: · Disabled—The interface cannot process IP packets. · Enabled—The interface can process IP packets. |
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. · BOOTP-allocated—BOOTP allocated IP address. For more information, see BOOTP 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. |
IPv6 packet frame type |
IPv6 packet framing format. |
Port priority |
Port priority of the interface. |
Fec counter Last 15mins uncorr errors |
FEC data is collected every 15 minutes. This field displays the most recently saved data. |
Peak1 Fec counter uncorr errors |
This field records the peak value and time based on the correctable errors. |
Peak2 Fec counter uncorr errors |
This field records the peak value and time based on the uncorrectable errors. |
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. |
100Gbps-speed mode |
The interface is operating at 100 Gbps. This field depends on your configuration and the link parameter negotiation result. |
200Gbps-speed mode |
The interface is operating at 200 Gbps. This field depends on your configuration and the link parameter negotiation result. |
400Gbps-speed mode |
The interface is operating at 400 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 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, 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 in ratio, pps, or kbps. The unit of the threshold depends on your configuration. |
Multicast max- |
Multicast storm suppression threshold in ratio, pps, or kbps. The unit of the threshold depends on your configuration. |
Unicast max- |
Unknown unicast storm suppression threshold in ratio, pps, or kbps. The unit of the threshold depends on your configuration. |
PVID |
Port VLAN ID (PVID) of the interface. |
MDI type |
MDIX mode of the interface: · automdix. · mdi. · mdix. |
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 hardware down reason |
Reason for which the interface hardware went down: · PHY line side is down. · PHY system side is down. · No optical signal has been received at the optical port. |
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 date and time, which is displayed in the YYYY-MM-DD hh:mm:ss format by default. 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 name. |
Last time when physical state changed to up |
Last date and time when the physical state of the interface changed to up, which is displayed in the YYYY-MM-DD hh:mm:ss format by default. 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 name. If the physical state of the interface has never changed to up, this field displays a hyphen (-). |
Last time when physical state changed to down |
Last date and time when the physical state of the interface changed to down, which is displayed in the YYYY-MM-DD hh:mm:ss format by default. 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 name. If the physical state of the interface has never changed to down, this field displays a hyphen (-). |
Last 300 seconds input: 0 packets/sec 0 bytes/sec 0% Last 300 seconds output: 0 packets/sec 0 bytes/sec 0% |
Average inbound or outbound traffic rate (in pps and Bps) in the last 300 seconds, and the ratio of the actual rate to the interface bandwidth. 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
400GE1/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
400GE1/0/2 DOWN auto A A 1
400GE1/0/3 UP auto F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaaaa
# Display brief information about FourHundredGigE 1/0/3, including the complete description of the interface.
<Sysname> display interface fourhundredgige 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
400GE1/0/3 UP auto F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaaaaaa
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
400GE1/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
400GE1/0/2 DOWN Not connected
Table 6 Command output
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. |
Speed: (a) - auto |
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: (a)/A - auto; H - half; F - full |
· A—Autonegotiation. The interface is configured to autonegotiate its duplex mode. · A(a)—Autonegotiation. The interface is configured to autonegotiate its duplex mode but the autonegotiation has not started. · F—Full duplex. · H—Half duplex. |
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. · 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. · Port Security Disabled—The interface has been shut down by the intrusion detection mechanism, because the interface received illegal packets. · OFP DOWN—The interface has been shut down by OpenFlow. |
reset counters interface
display lbn-group status
Use display lbn-group status to display rail group information.
Syntax
display lbn-group status
Views
System view
Predefined user roles
network-admin
network-operator
Example
# Display LBN group information.
<System> display lbn-group status
Global lbn-group configuration: Enable
GroupName GroupIndex Index Interface
Leaf1 1 0 FourHundredGigE1/0/2
FourHundredGigE1/0/1
Leaf 2 0 FourHundredGigE1/0/3
FourHundredGigE1/0/4
Table 7 Command output
Field |
Description |
Global lbn-group configuration |
Status of the LBN group feature: · Disable · Enable |
GroupName |
Name of the LBN group. |
GroupIndex |
Index of an interface in the LBN group. |
Index |
Index of the LBN group. |
Interface |
Name of the interface. |
Related commands
group-member interface
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 an interface.
<Sysname> display link-flap protection
Link-flap protection: Enabled
Interface Link-flap Status Interval Threshold
400GE1/0/1 Enabled Down 10 5
400GE1/0/2 Disabled N/A -- --
Field |
Description |
Link-flap protection |
Status of link flapping protection on all interfaces: · Enabled—Link flapping protection is enabled on all interfaces. · Disabled—Link flapping protection is disabled on all interfaces. |
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. · Unconfig—Link flapping protection is not configured 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 |
Link flapping detection interval for an interface. |
Threshold |
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 up interfaces that have traffic counters.
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
400GE1/0/1 0 Never Never
Never Never
Table 9 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 FourHundredGigE 1/0/1.
<Sysname> display packet-drop interface fourhundredgige 1/0/1
FourHundredGigE1/0/1:
Packets dropped due to full GBP or insufficient bandwidth: 301
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
# Display the summary of dropped packets on only interfaces that support this command.
<Sysname> display packet-drop summary
All interfaces:
Packets dropped due to full GBP or insufficient bandwidth: 301
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
Table 10 Command output
Field |
Description |
Packets dropped due to full GBP or insufficient bandwidth |
Packets that are dropped because the buffer is used up or the bandwidth is insufficient. |
Packets dropped due to Fast Filter Processor (FFP) |
Packets that are filtered out. |
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. |
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 FourHundredGigE 1/0/1 to operate in full duplex mode.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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 on a link, enable generic flow control at both ends of the link.
Examples
# Enable TxRx-mode generic flow control on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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.
Examples
# Enable Rx-mode generic flow control on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-fourhundredgige 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 is300 seconds.
Views
System view
Ethernet interface view
Predefined user roles
network-admin
Parameters
interval: Sets the statistics polling interval in seconds. In system view, the interval is in the range of 5 to 300 and must be a multiple of 5. In Ethernet interface view, the interval is in the range of 1 to 300 and must be a multiple of 1.
Usage guidelines
You can use this command in system view or interface view.
· In system view, the command takes effect on all interfaces.
· In interface view, the command takes effect only on the specified interface.
The statistics polling interval configured in Ethernet interface view takes precedence over the statistics polling interval configured in system view. The interval configured in system view takes effect on an Ethernet interface only when no interval is configured or the default interval is configured for the Ethernet interface.
As a best practice, use the default value for the flow-interval command in system view. A short static polling interval in system view might decrease the system performance and result in inaccurate statistics.
Examples
# Set the statistics polling interval to 100 seconds on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] flow-interval 100
group-member interface
Use group-member interface to assign interfaces to an LBN group.
Use undo group-member interface to remove interfaces from an LBN 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
LBN group view
Default
An LBN 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 an LBN 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 an LBN 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 an LBN group, and the interfaces must be incoming interfaces.
If you specify a list of interfaces, make sure the two interfaces before and after the to keyword are the same type.
Using the port link-mode command to change the link mode of a member interface or splitting a member interface will remove that interface from the LBN group.
Example
# Assign interfaces FourHundredGigE 1/0/1 through FourHundredGigE 1/0/4 to LBN group Leaf1.
<Sysname> system-view
[Sysname] lbn-group Leaf1
[Sysname-lbn-group-Leaf1] group-member interface FourHundredGigE1/0/1 to FourHundredGigE1/0/4
# Assign interface FourHundredGigE 1/0/1 with index 3 to LBN group Leaf1.
<Sysname> system-view
[Sysname] lbn-group Leaf1
[Sysname-lbn-group-Leaf1] group-member interface FourHundredGigE1/0/1 index 3
ifmonitor buffer mode
User ifmonitor buffer mode to set the buffer data monitoring mode.
Use undo ifmonitor buffer mode to restore the default.
Syntax
ifmonitor buffer mode standardslot slot-number
undo ifmonitor buffer mode slot slot-number
Default
No buffer data monitoring mode is configured.
Views
System view
Predefined user roles
network-admin
Parameters
standard: Specifies the standard mode.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
Usage guidelines
Operating mechanism
Buffer data monitoring can operate in the following modes:
· Standard—In this mode, a card supports monitoring and collecting queue buffer data from multiple interfaces, and the data collection interval can be set to 5 ms, 10 ms, 20 ms, 50 ms, or 100 ms.
· Enhanced—In this mode, a card supports monitoring and collecting queue buffer data from only one interface, and the data collection interval is fixed at 1 ms.
Restrictions and guidelines
To disable or change the buffer data monitoring mode for a card, you must first execute the undo port ifmonitor buffer queue enable command.
Examples
# Set the buffer data monitoring mode to standard.
<Sysname> system-view
[Sysname] ifmonitor buffer mode standard slot 1
Related commands
display ifmonitor buffer statistics
display ifmonitor buffer status
port ifmonitor buffer queue enable
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 [ 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.
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.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 high-threshold 5000 low-threshold 400 interval 6
Related commands
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.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 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 the slot number of the device, which is fixed at 1.
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.
The statistics polling interval varies by device model:
· On a device that does not support the flow-interval command, the statistics polling interval is 5 minutes.
· On a device that supports the flow-interval command, 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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 high-threshold 95 low-threshold 80
Related commands
flow-interval
snmp-agent trap enable ifmonitor
ifmonitor output-error
Use ifmonitor output-error to configure global output error packet alarm parameters.
Use undo ifmonitor output-error to restore the default.
Syntax
ifmonitor output-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor output-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 output error packet alarms.
Views
System 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.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
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.
You can configure the output error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 output error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor output-error high-threshold 5000 low-threshold 400 interval 6
Related commands
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 the slot number of the device, which is fixed at 1.
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.
The statistics polling interval varies by device model:
· On a device that does not support the flow-interval command, the statistics polling interval is 5 minutes.
· On a device that supports the flow-interval command, 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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 95 and lower threshold to 80 for output bandwidth usage alarms.
<Sysname> system-view
[Sysname] ifmonitor output-usage high-threshold 95 low-threshold 80
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 the slot number of the device, which is fixed at 1.
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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 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
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.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 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 FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1]
# Create Ethernet subinterface FourHundredGigE 1/0/1.1 and enter its view.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1.1
[Sysname-FourHundredGigE1/0/1.1]
itf number
Use itf number to set the number of interframe padding tags.
Use undo itf number to restore the default.
Syntax
itf number number
undo itf number
Default
The default varies by device model.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
number: Sets the number of interframe padding tags, in the range of 0 to 14.
Usage guidelines
Ethernet frames are separated by the interframe gaps. By adjusting the interframe gap size for an interface, you can adjust the packet forwarding rate and the forwarding capability of the interface. When rate limit is configured for an interface, to ensure smooth communication, you might need to adjust the interframe gap size. You must set the same interframe gap size for interfaces on both ends of a link.
Typically, use the default interframe gap size. To modify the interframe gap size, consult the professionals. An improper interframe gap size setting might cause packet loss or even interface failure.
This command might cause interface flapping.
Examples
# Set the number of interframe padding tags to 9 for GigabitEthernet 1/0/1.
<Sysname> system view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] itf number 9
Itf number will be set. Continue? [Y/N]:y
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 a length of 9216 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 is 1536 to 9216.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Allow jumbo frames to pass through FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] jumboframe enable
lbn-group
Use lbn-group to create an LBN group and enter its view.
Use undo lbn-group to delete an LBN group.
Syntax
lbn-group group-name
undo lbn-group group-name
Views
System view
Default
No LBN group exists.
Predefined user roles
network-admin
Parameters
group-name: Specifies an LBN group name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
The LBN group feature assigns different incoming interfaces on the device to an LBN 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.
Changing the link type for an interface in an LBN group between Layer 2 and Layer 3 will remove that interface from the LBN group.
In the primary/backup scenario, if the ECMP mode is eligible, an interface is added to an LBN group, and LBN is enabled globally, traffic will be forwarded through the backup link.
You must add both the incoming and outgoing interfaces to an LBN group and make sure the number of incoming interfaces is an integer multiple of the number of outgoing interfaces.
Examples
# Create an LBN group named test and enter its view.
<Sysname> system-view
[Sysname] lbn-group test
[Sysname-lbn-group-test]
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
Physical state change suppression is disabled.
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 30 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 events. 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 spanning tree protocols enabled.
This 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 FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] link-delay down 8
# Set the link-up event suppression interval to 800 milliseconds on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] link-delay up msec 800
Related commands
port link-flap protect 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 [ batch [ interval interval | threshold threshold ] * ]
undo link-flap protect enable [ batch [ interval | threshold ] ]
Default
Link flapping protection is disabled globally.
Views
System view
Predefined user roles
network-admin
Parameters
batch: Enables link flapping protection both globally and on all interfaces, and sets the default link flapping detection interval and link flapping detection threshold. If you do not specify this keyword, this command enables link flapping protection only globally.
interval interval: Specifies the 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 link flapping detection threshold in the range of 2 to 1200. The default value for this argument is 5.
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 the system view and interface view.
Any of the following operations can enable link flapping protection:
· Execute the link-flap protect enable batch command in system view, and do not configure link flapping protection on interfaces.
· Execute the link-flap protect enable batch command in system view, and execute the port link-flap protect enable command in interface view.
· Execute the link-flap protect enable command in system view, and execute the port link-flap protect enable command in interface view.
The undo link-flap protect enable command works different depending on the keywords specified as follows:
· If the batch keyword is not specified, this command disables link flapping protection globally.
· If the batch keyword is specified but the interval or threshold keyword is not specified, this command restores the default for the interval and threshold keywords.
· If the interval or threshold keyword is specified, this command restores the default for the interval or threshold keyword.
If an interface is already configured with the link-delay or dampening command, the link-delay or dampening command applies when you execute the link-flap protect enable batch command.
Examples
# Enable link flapping protection on all interfaces.
<Sysname> system-view
[Sysname] link-flap protect enable
Related commands
port link-flap protect enable
loadbalance ecmp lbn-group enable
Use loadbalance ecmp lbn-group enable to enable the ECMP-mode LBN group feature.
Use undo loadbalance ecmp lbn-group enable to disable the ECMP-mode LBN group feature.
Syntax
loadbalance ecmp lbn-group enable
undo loadbalance ecmp lbn-group enable
Views
System view
Default
The ECMP-mode LBN 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 LBN group feature.
<Sysname> system-view
[Sysname] loadbalance ecmp lbn-group enable
Related commands
loadbalance link-aggregation lbn-group enable
loadbalance ecmp lbn-group mode
Use loadbalance ecmp lbn-group mode to set a mode for the ECMP-mode LBN group feature.
Use undo loadbalance ecmp lbn-group mode to restore the default.
Syntax
loadbalance ecmp lbn-group mode enhanced-fixed
undo loadbalance ecmp lbn-group mode
Default
The mode for the ECMP-mode LBN group feature is common. If the incoming and outgoing interfaces for the traffic are both in an LBN group and the number of incoming interfaces is an integer number of outgoing interfaces, the mode for the ECMP-mode LBN group feature is enhanced.
Views
System view
Predefined user roles
network-admin
Parameters
enhanced-fixed: Specifies the fixed enhanced mode the ECMP-mode LBN group feature.
Usage guidelines
Operating mechanism
The ECMP-mode LBN group feature supports the following modes:
· Normal mode—When a link fault occurs on an outgoing interface that implements load sharing by using the LBN group feature, traffic from its incoming interface will be distributed to one of other ECMP route outgoing interfaces. The forwarding outgoing interfaces for the other incoming interfaces will also be re-calculated.
· Enhanced mode—When a link fault occurs on an outgoing interface that implements load sharing by using the LBN group feature, traffic from its incoming interface will be load-shared to other ECMP route outgoing interfaces through a hash algorithm. The forwarding outgoing interfaces for the other incoming interfaces will also be re-calculated.
· Fixed enhanced mode—When a link fault occurs on an outgoing interface that implements load sharing by using the LBN group feature, traffic from its incoming interface will be load-shared to other ECMP route outgoing interfaces through a hash algorithm. The forwarding outgoing interfaces for the other incoming interfaces are not changed.
Restrictions and guidelines
To execute this command, you must first execute the loadbalance ecmp lbn-group enable command.
Examples
# Set the fixed enhanced mode for the ECMP-mode LBN group feature.
<Sysname> system-view
[Sysname] loadbalance ecmp lbn-group mode enhanced-fixed
Related commands
loadbalance ecmp lbn-group enable
loadbalance link-aggregation lbn-group enable
Use loadbalance link-aggregation lbn-group enable to enable the Ethernet link aggregation mode LBN group feature.
Use undo loadbalance link-aggregation lbn-group enable to disable the Ethernet link aggregation mode LBN group feature.
Syntax
loadbalance link-aggregation lbn-group enable
undo loadbalance link-aggregation lbn-group enable
Views
System view
Default
The Ethernet link aggregation mode LBN 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 LBN group feature.
<Sysname> system-view
[Sysname] loadbalance link-aggregation lbn-group enable
Relate commands
loadbalance ecmp lbn-group enable
loopback
CAUTION: After you enable loopback testing on an Ethernet interface, the interface does not forward data traffic. |
Use loopback to enable loopback testing on an Ethernet interface.
Use undo loopback to disable loopback testing on an Ethernet interface.
Syntax
loopback internal
undo loopback
Default
Loopback testing is disabled on an Ethernet interface.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
internal: Enables internal loopback testing on the Ethernet interface.
Usage guidelines
After you enable loopback testing on an Ethernet interface, the Ethernet interface switches to full duplex mode. After you disable loopback testing, the Ethernet interface restores to its duplex setting.
The shutdown, port up-mode, and loopback commands are mutually exclusive.
Examples
# Enable internal loopback testing on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] loopback 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 }
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.
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 configure both the storm-constrain multicast command and the multicast-suppression command on an interface.
The configured suppression threshold value in pps or kbps might be converted into a multiple of a step supported by the chip. As a result, the effective suppression threshold might be different from the configured one. To determine the suppression threshold that takes effect, see the prompts on the device.
Examples
# Set the multicast storm suppression threshold to 10000 kbps on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] multicast-suppression kbps 10000
The actual value is 10048 on port FourHundredGigE1/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 ifmonitor buffer queue enable
Use port ifmonitor buffer queue enable to enable buffer monitoring for a queue.
Use undo port ifmonitor buffer queue enable to restore the default.
Syntax
port ifmonitor buffer queue queue-index enable [ interval interval ]
undo port ifmonitor buffer queue queue-index enable
Default
Buffer monitoring is disabled for queues.
Views
Interface view
Predefined user roles
network-admin
Parameters
queue-index: Specifies a queue index in the range of 0 to 7. The value range for this argument is 0 to 7.
interval interval: Specifies the data collection interval. The value is 5, 10, 20, 50, or 100 milliseconds. The default is 5 milliseconds when the buffer data monitoring mode is set to standard. In enhanced mode, this parameter is not supported, and the data monitoring collection interval is 1 millisecond.
Usage guidelines
Operating mechanism
After you configure this feature on an interface, the device will perform the following operations:
Collect buffer data for a queue periodically, and report the collected data at intervals of one second to the gRPC or NETCONF module.
Monitor the buffer usage and microbursts for a specified queue periodically. When a microburst event occurs, the device reports the event to the gRPC or NETCONF module. For more information about the buffer usage and microbursts, see the port ifmonitor buffer queue threshold command.
Restrictions and guidelines
Before you configure this feature, execute the ifmonitor buffer mode command.
Examples
# Enable buffer data monitoring and collection for queue 1 on FourHundredGigE 1/0/1, and set the collection interval to 10 ms.
<Sysname> system-view
[Sysname] ifmonitor buffer mode standard slot 1
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port ifmonitor buffer queue 1 enable interval 10
Related commands
ifmonitor buffer mode
port ifmonitor buffer queue threshold
Use port ifmonitor buffer queue threshold to set the upper and lower buffer usage thresholds on a queue.
Use undo port ifmonitor buffer queue threshold to restore the default.
Syntax
port ifmonitor buffer queue queue-index threshold high high-percent low low-percent
undo port ifmonitor buffer queue queue-index
Default
The upper and lower buffer usage thresholds on a queue are 80% and 30%, respectively.
Views
Interface view
Predefined user roles
network-admin
Parameters
queue-index: Specifies a queue index in the range of 0 to 7.
threshold high high-percent: Specifies the upper buffer usage threshold on a queue in the range 1 to 100 in percentage.
low low-percent: Specifies the lower buffer usage threshold on a queue in the range 0 to 100 in percentage.
Usage guidelines
The device periodically monitors the queue buffer usage every 100ms to detect and report microburst events.
Table 11 describes the conditions for triggering and reporting a microburst event.
Table 11 Conditions for triggering a microburst event
Scenario |
Conditions for triggering a microburst event |
Conditions for reporting a microburst event |
Scenario 1 |
Both of the following conditions are met: · The queue buffer usage higher than the upper threshold or the lower threshold is 0%. · The queue buffer usage has increased by more than 2% compared to the last interval. |
If microbursts occur more than 1 second after the last reported microburst event, the device will report a microburst event. If the time when the last microburst event was reported cannot be obtained, the device determines it as the first microburst event and reports it directly. |
Scenario 2 |
Both of the following conditions are met: · The queue buffer usage is not higher than the upper threshold and not lower than the lower threshold. · The queue buffer usage has increased by more than 2% compared to the last interval. |
Both of the following conditions are met: · Microbursts were detected in the last detection period. · If microbursts occur more than 1 second after the last reported microburst event, the device will report a microburst event. If the time when the last microburst event was reported cannot be obtained, the device determines it as the first microburst event and reports it directly. |
As shown in Figure 1:
· For scenario 1:
¡ Microbursts occurred at T0 for the first time. The device will directly report a microburst event.
¡ Microbursts occurred at T0+0.5s and T0+0.8s, but not more than 1 second after the last reported microburst event. The device will not report a microburst event.
¡ Microbursts occurred at T0+1.5s, more than 1 second after the last reported microburst event. The device will report a microburst event.
¡ Microbursts occurred at T0+1.6s, but not more than 1 second after the last reported microburst event. The device will not report a microburst event.
· For scenario 2:
¡ Microbursts occurred at T0 for the first time. The device will directly report a microburst event.
¡ Microbursts occurred at T0+0.5s and T0+0.8s, but not more than 1 second after the last reported microburst event. The device will not report a microburst event.
¡ Microbursts occurred at T0+1.5s, more than 1 second after the last reported microburst event. However, no microbursts occurred at T0+1.4s in the last period. The device will not report a microburst event.
¡ Microbursts occurred at T0+1.6s, more than 1 second after the last reported microburst event, and microbursts occurred at T0+1.5s in the last period. The device will report a microburst event.
Figure 1 Conditions for triggering a microburst event
Examples
# Set the upper and lower buffer usage thresholds to 60% and 30%, respectively, for queue 1 on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port ifmonitor buffer queue 1 threshold high 60 low 30
Related commands
ifmonitor buffer mode
port ifmonitor buffer queue enable
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 [ 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.
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.
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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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.
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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 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.
The statistics polling interval varies by device model:
· On a device that does not support the flow-interval command, the statistics polling interval is 5 minutes.
· On a device that supports the flow-interval command, 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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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.
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.
You can configure the output error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 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.
The statistics polling interval varies by device model:
· On a device that does not support the flow-interval command, the statistics polling interval is 5 minutes.
· On a device that supports the flow-interval command, 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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port ifmonitor rx-pause high-threshold 90 low-threshold 50 interval 5
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor sdh-b1-error
Use port ifmonitor sdh-b1-error to configure SDH-B1 error packet alarm parameters for an interface.
Use undo port ifmonitor sdh-b1-error to restore the default.
Syntax
port ifmonitor sdh-b1-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor sdh-b1-error
Default
An interface uses the global SDH-B1 error packet alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH-B1 error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH-B1 error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH-B1 error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH-B1 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 SDH-B1 error packets exceeds the upper threshold on the interface.
Usage guidelines
With the SDH-B1 error packet alarm function enabled, when the number of incoming SDH-B1 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 SDH-B1 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 SDH-B1 error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 SDH-B1 error packet 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 10 seconds for SDH-B1 error packet alarms on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port ifmonitor sdh-b1-error high-threshold 20 low-threshold 10 interval 10
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor sdh-b2-error
Use port ifmonitor sdh-b2-error to configure SDH-B2 error packet alarm parameters for an interface.
Use undo port ifmonitor sdh-b2-error to restore the default.
Syntax
port ifmonitor sdh-b2-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor sdh-b2-error
Default
An interface uses the global SDH-B2 error packet alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH-B2 error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH-B2 error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH-B2 error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH-B2 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 SDH-B2 error packets exceeds the upper threshold on the interface.
Usage guidelines
With the SDH-B2 error packet alarm function enabled, when the number of incoming SDH-B2 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 SDH-B2 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 SDH-B2 error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 SDH-B2 error packet alarm function.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 10, lower threshold to 8, and statistics collection and comparison interval to 3 seconds for SDH-B2 error packet alarms on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port ifmonitor sdh-b2-error high-threshold 10 low-threshold 8 interval 3
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor sdh-error
Use port ifmonitor sdh-error to configure SDH error packet alarm parameters for an interface.
Use undo port ifmonitor sdh-error to restore the default.
Syntax
port ifmonitor sdh-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor sdh-error
Default
An interface uses the global SDH error packet alarm parameters.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH 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 SDH error packets exceeds the upper threshold on the interface.
Usage guidelines
With the SDH error packet alarm function enabled, when the number of incoming SDH 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 SDH 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 SDH error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 SDH error packet 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 30, and statistics collection and comparison interval to 10 seconds for SDH error packet alarms on FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port ifmonitor sdh-error high-threshold 50 low-threshold 30 interval 10
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
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.
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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· 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. (Devices that support the slot keyword.)
· 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 FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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
Use port link-flap protect to configure link flapping protection on an interface.
Use undo port link-flap protect to restore the default.
Syntax
port link-flap protect { disable | enable [ interval interval | threshold threshold ] * }
undo port link-flap protect { disable | enable [ interval | threshold ] }
Default
Link flapping protection is not configured on an interface, and the global link flapping protection configuration applies on the interface.
Ethernet interface view
Predefined user roles
network-admin
Parameters
disable: Disables link flapping protection on the interface.
enable: Enables link flapping protection on the interface.
interval interval: Specifies the 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 link flapping detection threshold in the range of 2 to 1200. The default value for this argument is 5.
Usage guidelines
Link flapping protection takes effect only when it is enabled in both the system view and interface view.
Any of the following operations can enable link flapping protection:
· Execute the link-flap protect enable batch command in system view, and do not configure link flapping protection on interfaces.
· Execute the link-flap protect enable batch command in system view, and execute the port link-flap protect enable command in interface view.
· Execute the link-flap protect enable command in system view, and execute the port link-flap protect enable command in interface view.
If the interval or threshold keyword is not specified when you execute the port link-flap protect enable command, the command uses the default settings for the interval and threshold keywords.
The undo port link-flap protect command works different depending on the keywords specified as follows:
· If the disable or enable keyword is not specified, this command restores the default for the link flapping protection function on the interface.
· If the interval or threshold keyword is specified, this command restores the default for the interval or threshold keyword.
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.
To bring up an interface that has been shut down by link flapping protection, execute the undo shutdown command.
This 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 fourhundredgige 1/0/1
[Sysname-FourHundredGigE 1/0/1] port link-flap protect enable interval 10 threshold 5
Related commands
link-delay
link-flap protect enable
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
An interface operates in Layer 2 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, combo enable, port fec mode, and port training) on the Ethernet interface to their defaults in the new link mode. |
Ethernet interfaces can operate either as Layer 2 or Layer 3 Ethernet interfaces. You can use this command to set the link mode to bridge (Layer 2) or route (Layer 3) for these Ethernet interfaces.
Examples
# Configure FourHundredGigE 1/0/1 to operate in Layer 2 mode.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port link-mode bridge
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 shutdown, port up-mode, and loopback commands are mutually exclusive.
Examples
# Forcibly bring up fiber port FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] port up-mode
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 the slot number of the device, which is fixed at 1.
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 up interfaces that have traffic counters.
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 FourHundredGigE 1/0/1.
<Sysname> reset link-state-change statistics interface fourhundredgige 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 FourHundredGigE 1/0/1.
<Sysname> reset packet-drop interface fourhundredgige 1/0/1
# Clear dropped packet statistics for all interfaces.
<Sysname> reset packet-drop interface
Related commands
display packet-drop
shutdown all-interfaces
Use shutdown all-interfaces to shut down all main interfaces except management interfaces, IRF physical interfaces, and interfaces excluded from shutdown.
Use undo shutdown all-interfaces to bring up all main interfaces except management interfaces, IRF physical interfaces, and interfaces excluded from shutdown.
Syntax
shutdown all-interfaces exclude interface-list
undo shutdown all-interfaces exclude interface-list
Default
A physical interface is up.
Views
System view
Predefined user roles
network-admin
Parameters
exclude interface-list: Specifies interfaces to be excluded from shutdown. With this option specified, this command will shut down all main interfaces except the management Ethernet interfaces, IRF physical interfaces, and the specified interfaces excluded from shutdown. Shutdown interfaces are in ADM state. Specify the interface list in the format of interface-list = { interface-type interface-number1 [ to interface-type interface-number2 ] }. You can specify the interface-list parameter for any times. The interface-type interface-number argument specifies an interface by its type and number. The selected interfaces must reside on the same interface card or subcard. The value for the interface-number2 argument must be greater than the value for the interface-number1 argument. For the configuration to succeed, make sure the start interface and the end interface, which are before and after the to keyword respectively, are of the same type.
Usage guidelines
This command shuts down all interfaces except the management Ethernet interfaces, IRF physical interfaces, and interfaces excluded from shutdown on a device. For an interface that supports subinterfaces, only the main interface is shut down, and its subinterfaces will not be shut down by this command. In this case, if you execute the display this command on an interface that is shut down, the output shows that the shutdown command is automatically generated on the interface.
To bring up an interface shut down by using the shutdown all-interfaces command, you can execute the undo shutdown command in interface view or the undo shutdown all-interfaces command in system view.
Examples
# Shut down all main interfaces except management interfaces, IRF physical interfaces, and interfaces FourHundredGigE 1/0/1 through FourHundredGigE 1/0/4.
<Sysname> system-view
[Sysname] shutdown all-interfaces exclude fourhundredgige 1/0/1 to fourhundredgige 1/0/4
Related commands
shutdown
shutdown all-physical-interfaces
shutdown all-physical-interface
Use shutdown all-physical-interfaces to shut down all physical interfaces.
Use undo shutdown all-physical-interfaces to bring up all physical interfaces.
Syntax
shutdown all-physical-interfaces
undo shutdown all-physical-interfaces
Default
A physical interface is up.
Views
System view
Predefined user roles
network-admin
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.
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 a shutdown interface, execute the undo shutdown all-physical-interfaces command in system view and execute the undo shutdown command in interface view.
Examples
# Shut down all physical interfaces.
<Sysname> system-view
[Sysname] shutdown all-physical-interfaces
Related commands
shutdown
shutdown-interval link-flap
Use shutdown-interval link-flap interval 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 interval 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
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 | giant | input-error | input-usage | output-error | output-usage | rant | 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
Interface alarm functions are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
crc-error: Enables the CRC error packet alarm function for interfaces.
input-error: Enables the input error packet alarm function for interfaces.
input-usage: Enables the input bandwidth usage alarm function for interfaces.
output-error: Enables the output error packet alarm function for interfaces.
output-usage: Enables the output bandwidth usage alarm function for interfaces.
rx-pause: Enables the received pause frame alarm function for interfaces.
tx-pause: Enables the sent pause frame alarm function for interfaces.
buffer-usage: Enables the sent traffic congestion alarm function for interfaces. With the sent traffic congestion alarm function enabled, when the buffer usage of an interface in normal state reaches the upper threshold, the interface generates an upper threshold exceeding alarm and enters alarm state. When the buffer usage of an interface in the alarm state drops below the lower threshold, the interface generates a recovery alarm and restores to normal state.
Examples
# Enable the CRC error packet alarm function for interfaces.
<Sysname> system-view
[Sysname] snmp-agent trap enable ifmonitor crc-error
speed
Use speed to set the speed of an Ethernet interface.
Use undo speed to restore the default.
Syntax
speed { 10000 | 200000 | 400000 | auto }
undo speed
Default
The speed of an Ethernet interface is autonegotiated.
Views
Ethernet interface view
Predefined user roles
network-admin
Parameters
10000: Sets the interface speed to 10000 Mbps.
200000: Sets the interface speed to 200000 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.
The speed 10000 command is available only on the S9827-128DH and S9827-64EP switches.
Examples
# Configure FourHundredGigE 1/0/1 to autonegotiate the speed.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] speed auto
Related commands
speed auto-reduction enable
Use speed auto-reduction enable to enable automatic speed reduction for an interface.
Use undo speed auto-reduction enable to disable automatic speed reduction for an interface.
Syntax
speed auto-reduction enable
undo speed auto-reduction enable
Default
Automatic speed reduction is disabled.
Views
400-GE interface view
Predefined user roles
network-admin
Usage guidelines
Operating mechanism
With this feature enabled, if an underlying data forwarding channel of an interface fails, the interface state will not change to down. Instead, it continues to use the remaining underlying data forwarding channels that are operating correctly and automatically decreases its speed, for example, from 400G to 200G.
Restrictions and guidelines
After you execute this command, the interface speed decreases automatically only when an underlying data forwarding channel fails.
The undo speed auto-reduction enable command restore the speed of an interface. To restore the speed of an interface, execute the speed auto-reduction restore command.
You cannot configure the speed, port up-mode, loopback internal, link-delay, using hundred, or using twohundred command for an interface if the interface has been configured with RLM, and vice versa.
If the speed of an aggregate member port configured with the speed auto-reduction enable command decreases because of channel failure, the member port cannot be selected due to inconsistent speeds. To avoid this issue, execute the link-agge ignore speed command on the aggregate member port.
Examples
# Enable automatic speed reduction for an interface.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] speed auto-reduction enable
Related commands
speed auto-reduction restore
speed auto-reduction restore
Use speed auto-reduction restore to restore the speed of an interface that has automatically reduced its speed.
Syntax
speed auto-reduction restore
Views
400-GE interface view
Predefined user roles
network-admin
Usage guidelines
Before you execute this command on an interface, make sure the underlying data forwarding channel of that interface has recovered.
Examples
# Restore the speed of an interface that has automatically reduced its speed.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] speed auto-reduction restore
Related commands
speed auto-reduction enable
sub-interface rate-statistic
Use sub-interface rate-statistic to enable rate statistics collection for the subinterfaces of an Ethernet interface.
Use undo sub-interface rate-statistic to disable rate statistics collection for the subinterfaces of an Ethernet interface.
Syntax
sub-interface rate-statistic
undo sub-interface rate-statistic
Default
The system does not collect rate statistics for the subinterfaces of an Ethernet interface.
Views
Ethernet interface view
Predefined user roles
network-admin
Usage guidelines
This command is resource intensive. When you use this command, make sure you fully understand its impact on system performance.
Examples
# Enable rate statistics collection for the subinterfaces of FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] sub-interface rate-statistic
This configuration may make a negative effect on the performance. Are you sure to continue? [Y/N]:y
using eighthundredgige
Use using eighthundredgige to combine breakout interfaces split from an 800-GE interface into an 800-GE interface or restore a low-bandwidth interface changed from an 800-GE interface to an 800-GE interface.
Use undo using eighthundredgige to cancel the operation of combining breakout interfaces or cancel restoring a low-bandwidth interface changed from an 800-GE interface to an 800-GE interface.
Syntax
using eighthundredgige
undo using eighthundredgige
Default
The breakout interfaces are not combined and operate as single interfaces.
Views
400-GE breakout interface view
200-GE breakout interface view
100-GE breakout interface view
400-GE downrated interface view
Predefined user roles
network-admin
Usage guidelines
If you need higher bandwidth on a single interface, you can combine two 400-GE breakout interfaces split from an 800-GE interface into an 800-GE interface. To do so, execute this command on any of these 400-GE breakout interfaces.
After executing this command, you do not need to reboot the device. To view the 400-GE breakout interfaces, execute the display interface brief command.
Examples
# Combine FourHundredGigE 1/0/1:1 and FourHundredGigE 1/0/1:2 into an 800-GE interface.
<Sysname> system-view
[Sysname] interface fourthundredgige 1/0/1:1
[Sysname-FourHundredGigE1/0/1:1] using eighthundredgige
The interfaces HundredGigE1/0/1:1 will be deleted. Continue? [Y/N]:y
Related commands
using fourhundredgige
using tworhundredgige
using hundredgige
using fourhundredgige
Use using fourhundredgige to combine 200-GE breakout interfaces split from a 400-GE interface into a 400-GE interface, split an 800-GE interface into multiple 400-GE breakout interfaces, change an 800-GE interface to a 400-GE interface, or restore a low-bandwidth interface to a 400-GE interface.
Use undo using fourhundredgige to cancel the operation of combining breakout interfaces, or cancel the operation of splitting an 800-GE interface.
|
NOTE: The mode 1-channel keyword is available only on the S9827-64E switches. |
Syntax
using fourhundredgige [ mode 1-channel ]
undo using fourhundredgige
Default
200-GE breakout interfaces are not combined and operate as single interfaces. An 800-GE interface is not split or changed and operates as a single interface. A 100-GE interface is not restored to a 400-GE interface.
Views
100-GE downrated interface view
200-GE downrated interface view
200-GE breakout interface view
800-GE interface view
Predefined user roles
network-admin
Parameters
mode 1-channel: Changes an 800-GE interface to a 400-GE interface. If you do not specify this keyword, this command splits an 800-GE interface into two 400-GE breakout interfaces.
Usage guidelines
If you need higher bandwidth on a single interface, you can split an 800-GE interface into two 400-GE interfaces. For example, you can split 800-GE interface EightHundredGigE 1/0/1 into two 400-GE interfaces FourHundredGigE 1/0/1:1 and FourHundredGigE 1/0/1:2. The 400-GE breakout interfaces support the same configuration and attributes as common 400-GE interfaces, except that they are numbered differently and cannot be split.
If you need higher bandwidth on a single interface, combine 200-GE breakout interfaces split from a 400-GE interface into a 400-GE interface. To do so, execute this command on any of these 200-GE breakout interfaces.
After executing this command, you do not need to reboot the device. To view the breakout interfaces, combined interfaces, or changed interfaces, execute the display interface brief command.
Examples
# Combine TwoHundredGigE 1/0/1:1 and TwoHundredGigE 1/0/1:2 into a 400-GE interface.
<Sysname> system-view
[Sysname] interface twohundredgige 1/0/1:1
[Sysname-TwoHundredGigE1/0/1:1] using fourhundredgige
The interfaces TwoHundredGigE1/0/1:1 and TwoHundredGigE1/0/1:2 will be deleted. Continue? [Y/N]:y
# Split EightHundredGigE 1/0/1 into two 400-GE interfaces.
<Sysname> system-view
[Sysname] interface eighthundredgige 1/0/1
[Sysname-EightHundredGigE1/0/1] using fourhundredgige
The interface EightHundredGigE1/0/1 will be deleted. Continue? [Y/N]:y
# Restore HundredGigE 1/0/1 to a 400-GE interface.
<Sysname> system-view
[Sysname] interface hundredgige 1/0/1
[Sysname-HundredGigE1/0/1] using fourhundredgige
The interface HundredGigE1/0/1 and HundredGigE1/0/9 will be deleted. Continue? [Y/N]:y
Related commands
using eighthundredgige
using hundredgige
using hundredgige mode 1-channel
using hundredgige mode 2-channel
using twohundredgige
using twohundredgige mode 1-channel
using hundredgige
Use using hundredgige to split a 400-GE or 800-GE interface into multiple 100-GE breakout interfaces, or change a 400-GE or 800-GE interface to a 100-GE interface.
Use undo using hundredgige to cancel the operation of splitting a 400-GE or 800-GE interface, or cancel the operation of changing a 400-GE or 800-GE interface.
|
NOTE: The mode 1-channel keyword is available only on 400-GE interfaces. |
Syntax
using hundredgige [ mode { 1-channel | 2-channel } ]
undo using hundredgige
Default
A 400-GE or 800-GE interface is used as a single interface, and is not split or not changed to a 100-GE interface.
Views
400-GE interface view
800-GE interface view
Predefined user roles
network-admin
Parameters
mode 1-channel: Changes an 800-GE or 400-GE interface to a 100-GE interface. If you do not specify this keyword, this command splits an 800-GE interface into multiple 100-GE breakout interfaces or splits a 400-GE interface into four 100-GE breakout interfaces.
mode 2-channel: Splits an 800-GE or 400-GE interface into two 100-GE interfaces. If you do not specify this keyword, this command splits an 800-GE interface into multiple 100-GE breakout interfaces or splits a 400-GE interface into four 100-GE interfaces.
Usage guidelines
To improve port density, reduce costs, and improve network flexibility, you can split an 800-GE or 400-GE interface into multiple 100-GE breakout interfaces. For example, you can split the 400-GE interface FourHundredGigE 1/0/1 into four 100-GE breakout interfaces HundredGigE 1/0/1:1 through HundredGigE 1/0/1:4. The 100-GE breakout interfaces support the same configuration and attributes as common 100-GE interfaces, except that they are numbered differently and cannot be split.
Specify the mode 1-channel keyword to change a 400-GE interface to a 100-GE interface if the peer is a 100-GE interface or only 100-GE transceiver modules are available.
The device reports the transceiver module alarm information only for the first breakout interface.
The breakout interfaces split from an interface share the same transceiver module. If threshold settings are configured on one breakout interface, the other breakout interfaces will automatically load the threshold settings.
After executing this command, you do not need to reboot the device. To view the changed interfaces, execute the display interface brief command.
For an S9827-128DH switch, when a 400-GE interface is changed to a 100-GE interface, the 400-GE interfaces in the same interface group are also changed to 100-GE interfaces. When a 100-GE interface is restored to a 400-GE interface, the 100-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 12 shows interface groups of an S9827-128DH switch.
Table 12 Interface groups of an S9827-128DH switch
Interface group number |
Interfaces |
1 |
FourHundredGigE 1/0/1, FourHundredGigE 1/0/9 |
2 |
FourHundredGigE 1/0/2, FourHundredGigE 1/0/10 |
3 |
FourHundredGigE 1/0/3, FourHundredGigE 1/0/4 |
4 |
FourHundredGigE 1/0/5, FourHundredGigE 1/0/6 |
5 |
FourHundredGigE 1/0/7, FourHundredGigE 1/0/15 |
6 |
FourHundredGigE 1/0/8, FourHundredGigE 1/0/16 |
7 |
FourHundredGigE 1/0/11, FourHundredGigE 1/0/12 |
8 |
FourHundredGigE 1/0/13, FourHundredGigE 1/0/14 |
9 |
FourHundredGigE 1/0/17, FourHundredGigE 1/0/25 |
10 |
FourHundredGigE 1/0/18, FourHundredGigE 1/0/26 |
11 |
FourHundredGigE 1/0/19, FourHundredGigE 1/0/21 |
12 |
FourHundredGigE 1/0/20, FourHundredGigE 1/0/22 |
13 |
FourHundredGigE 1/0/23, FourHundredGigE 1/0/31 |
14 |
FourHundredGigE 1/0/24, FourHundredGigE 1/0/32 |
15 |
FourHundredGigE 1/0/27, FourHundredGigE 1/0/29 |
16 |
FourHundredGigE 1/0/28, FourHundredGigE 1/0/30 |
17 |
FourHundredGigE 1/0/33, FourHundredGigE 1/0/41 |
18 |
FourHundredGigE 1/0/34, FourHundredGigE 1/0/42 |
19 |
FourHundredGigE 1/0/35, FourHundredGigE 1/0/37 |
20 |
FourHundredGigE 1/0/36, FourHundredGigE 1/0/38 |
21 |
FourHundredGigE 1/0/39, FourHundredGigE 1/0/47 |
22 |
FourHundredGigE 1/0/40, FourHundredGigE 1/0/48 |
23 |
FourHundredGigE 1/0/43, FourHundredGigE 1/0/45 |
24 |
FourHundredGigE 1/0/44, FourHundredGigE 1/0/46 |
25 |
FourHundredGigE 1/0/49, FourHundredGigE 1/0/57 |
26 |
FourHundredGigE 1/0/50, FourHundredGigE 1/0/58 |
27 |
FourHundredGigE 1/0/51, FourHundredGigE 1/0/52 |
28 |
FourHundredGigE 1/0/53, FourHundredGigE 1/0/54 |
29 |
FourHundredGigE 1/0/55, FourHundredGigE 1/0/63 |
30 |
FourHundredGigE 1/0/56, FourHundredGigE 1/0/64 |
31 |
FourHundredGigE 1/0/59, FourHundredGigE 1/0/60 |
32 |
FourHundredGigE 1/0/61, FourHundredGigE 1/0/62 |
33 |
FourHundredGigE 1/0/65, FourHundredGigE 1/0/73 |
34 |
FourHundredGigE 1/0/66, FourHundredGigE 1/0/74 |
35 |
FourHundredGigE 1/0/67, FourHundredGigE 1/0/68 |
36 |
FourHundredGigE 1/0/69, FourHundredGigE 1/0/70 |
37 |
FourHundredGigE 1/0/71, FourHundredGigE 1/0/79 |
38 |
FourHundredGigE 1/0/72, FourHundredGigE 1/0/80 |
39 |
FourHundredGigE 1/0/75, FourHundredGigE 1/0/76 |
40 |
FourHundredGigE 1/0/77, FourHundredGigE 1/0/78 |
41 |
FourHundredGigE 1/0/81, FourHundredGigE 1/0/89 |
42 |
FourHundredGigE 1/0/82, FourHundredGigE 1/0/90 |
43 |
FourHundredGigE 1/0/83, FourHundredGigE 1/0/85 |
44 |
FourHundredGigE 1/0/84, FourHundredGigE 1/0/86 |
45 |
FourHundredGigE 1/0/87, FourHundredGigE 1/0/95 |
46 |
FourHundredGigE 1/0/88, FourHundredGigE 1/0/96 |
47 |
FourHundredGigE 1/0/91, FourHundredGigE 1/0/93 |
48 |
FourHundredGigE 1/0/92, FourHundredGigE 1/0/94 |
49 |
FourHundredGigE 1/0/97, FourHundredGigE 1/0/105 |
50 |
FourHundredGigE 1/0/98, FourHundredGigE 1/0/106 |
51 |
FourHundredGigE 1/0/99, FourHundredGigE 1/0/101 |
52 |
FourHundredGigE 1/0/100, FourHundredGigE 1/0/102 |
53 |
FourHundredGigE 1/0/103, FourHundredGigE 1/0/111 |
54 |
FourHundredGigE 1/0/104, FourHundredGigE 1/0/112 |
55 |
FourHundredGigE 1/0/107, FourHundredGigE 1/0/109 |
56 |
FourHundredGigE 1/0/108, FourHundredGigE 1/0/110 |
57 |
FourHundredGigE 1/0/113, FourHundredGigE 1/0/121 |
58 |
FourHundredGigE 1/0/114, FourHundredGigE 1/0/122 |
59 |
FourHundredGigE 1/0/115, FourHundredGigE 1/0/116 |
60 |
FourHundredGigE 1/0/117, FourHundredGigE 1/0/118 |
61 |
FourHundredGigE 1/0/119, FourHundredGigE 1/0/127 |
62 |
FourHundredGigE 1/0/120, FourHundredGigE 1/0/128 |
63 |
FourHundredGigE 1/0/123, FourHundredGigE 1/0/124 |
64 |
FourHundredGigE 1/0/125, FourHundredGigE 1/0/126 |
For an S9857-24DH8EP switch, when a 400-GE interface is changed to a 100-GE interface, the 400-GE interfaces in the same interface group are also changed to 100-GE interfaces. When a 100-GE interface is restored to a 400-GE interface, the adjacent 100-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 13 shows interface groups of an S9857-24DH8EP switch.
Table 13 Interface groups of an S9857-24DH8EP switch
Interface group number |
Interfaces |
1 |
FourHundredGigE 1/0/1, FourHundredGigE 1/0/2 |
2 |
FourHundredGigE 1/0/3, FourHundredGigE 1/0/4 |
3 |
FourHundredGigE 1/0/5, FourHundredGigE 1/0/6 |
4 |
FourHundredGigE 1/0/7, FourHundredGigE 1/0/8 |
5 |
FourHundredGigE 1/0/9, FourHundredGigE 1/0/10 |
6 |
FourHundredGigE 1/0/11, FourHundredGigE 1/0/12 |
7 |
FourHundredGigE 1/0/13, FourHundredGigE 1/0/14 |
8 |
FourHundredGigE 1/0/15, FourHundredGigE 1/0/16 |
9 |
FourHundredGigE 1/0/17, FourHundredGigE 1/0/18 |
10 |
FourHundredGigE 1/0/19, FourHundredGigE 1/0/20 |
11 |
FourHundredGigE 1/0/21, FourHundredGigE 1/0/22 |
12 |
FourHundredGigE 1/0/23, FourHundredGigE 1/0/24 |
Examples
# Split FourHundredGigE 1/0/1 into multiple 100-GE breakout interfaces.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] using hundredgige
The interface FourHundredGigE1/0/1 will be deleted. Continue? [Y/N]:y
# Change FourHundredGigE 1/0/1 to a 100-GE interface.
<System> system-view
[System] interface fourhundredgige 1/0/1
[System-FourHundredGigE1/0/1] using hundredgige mode 1-channel
The interface FourHundredGigE1/0/1 and FourHundredGigE1/0/9 will be deleted. Continue? [Y/N]:y
Related commands
using fourhundredgige
using eighthundredgige
using twohundredgige
Use using twohundredgige to split a 400-GE interface into two 200-GE breakout interfaces, or change an 800-GE or 400-GE interface to a 200-GE interface.
Use undo using twohundredgige to cancel the operation of splitting a 400-GE interface, or cancel the operation of changing an 800-GE or 400-GE interface to a 200-GE interface.
|
NOTE: The mode 2-channel keyword is available only on the 800-GE interfaces. |
Syntax
using twohundredgige [ mode { 1-channel | 2-channel } ]
undo using twohundredgige
Default
An 800-GE or 400-GE interface is not split and operates as a single interface.
Views
400-GE interface view
800-GE interface view
Predefined user roles
network-admin
Parameters
mode 1-channel: Changes a 400-GE interface to a 200-GE interface. If you do not specify this keyword, this command splits a 400-GE interface into two 200-GE breakout interfaces.
mode 2-channel: Splits an 800-GE into two 200-GE interfaces. If you do not specify this keyword, this command splits an 800-GE interface into multiple 200-GE breakout interfaces or splits a 400-GE interface into two 200-GE interfaces.
Usage guidelines
To improve port density, reduce costs, and improve network flexibility, you can split a 400-GE interface into two 200-GE breakout interfaces. For example, you can split the 400-GE interface FourHundredGigE 1/0/1 into two 200-GE breakout interfaces TwoHundredGigE 1/0/1:1 and TwoHundredGigE 1/0/1:2.
The 200-GE breakout interfaces are numbered differently than common 200-GE interfaces, and you cannot use the speed command to change the speed for the 200-GE breakout interfaces.
Specify the mode 1-channel or mode 2-channel keywords to change an 800-GE or 400-GE interface to a 200-GE interface if the peer is a 200-GE interface or only 200-GE transceiver modules are available.
After executing this command, you do not need to reboot the device. To view the breakout interfaces or changed interfaces, execute the display interface brief command.
For an S9827-128DH switch, when a 400-GE interface is changed to a 200-GE interface, the 400-GE interfaces in the same interface group are also changed to 200-GE interfaces. When a 200-GE interface is restored to a 400-GE interface, the 200-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 14 shows interface groups of an S9827-128DH switch.
Table 14 Interface groups of an S9827-128DH switch
Interface group number |
Interfaces |
1 |
FourHundredGigE 1/0/1, FourHundredGigE 1/0/9 |
2 |
FourHundredGigE 1/0/2, FourHundredGigE 1/0/10 |
3 |
FourHundredGigE 1/0/3, FourHundredGigE 1/0/4 |
4 |
FourHundredGigE 1/0/5, FourHundredGigE 1/0/6 |
5 |
FourHundredGigE 1/0/7, FourHundredGigE 1/0/15 |
6 |
FourHundredGigE 1/0/8, FourHundredGigE 1/0/16 |
7 |
FourHundredGigE 1/0/11, FourHundredGigE 1/0/12 |
8 |
FourHundredGigE 1/0/13, FourHundredGigE 1/0/14 |
9 |
FourHundredGigE 1/0/17, FourHundredGigE 1/0/25 |
10 |
FourHundredGigE 1/0/18, FourHundredGigE 1/0/26 |
11 |
FourHundredGigE 1/0/19, FourHundredGigE 1/0/21 |
12 |
FourHundredGigE 1/0/20, FourHundredGigE 1/0/22 |
13 |
FourHundredGigE 1/0/23, FourHundredGigE 1/0/31 |
14 |
FourHundredGigE 1/0/24, FourHundredGigE 1/0/32 |
15 |
FourHundredGigE 1/0/27, FourHundredGigE 1/0/29 |
16 |
FourHundredGigE 1/0/28, FourHundredGigE 1/0/30 |
17 |
FourHundredGigE 1/0/33, FourHundredGigE 1/0/41 |
18 |
FourHundredGigE 1/0/34, FourHundredGigE 1/0/42 |
19 |
FourHundredGigE 1/0/35, FourHundredGigE 1/0/37 |
20 |
FourHundredGigE 1/0/36, FourHundredGigE 1/0/38 |
21 |
FourHundredGigE 1/0/39, FourHundredGigE 1/0/47 |
22 |
FourHundredGigE 1/0/40, FourHundredGigE 1/0/48 |
23 |
FourHundredGigE 1/0/43, FourHundredGigE 1/0/45 |
24 |
FourHundredGigE 1/0/44, FourHundredGigE 1/0/46 |
25 |
FourHundredGigE 1/0/49, FourHundredGigE 1/0/57 |
26 |
FourHundredGigE 1/0/50, FourHundredGigE 1/0/58 |
27 |
FourHundredGigE 1/0/51, FourHundredGigE 1/0/52 |
28 |
FourHundredGigE 1/0/53, FourHundredGigE 1/0/54 |
29 |
FourHundredGigE 1/0/55, FourHundredGigE 1/0/63 |
30 |
FourHundredGigE 1/0/56, FourHundredGigE 1/0/64 |
31 |
FourHundredGigE 1/0/59, FourHundredGigE 1/0/60 |
32 |
FourHundredGigE 1/0/61, FourHundredGigE 1/0/62 |
33 |
FourHundredGigE 1/0/65, FourHundredGigE 1/0/73 |
34 |
FourHundredGigE 1/0/66, FourHundredGigE 1/0/74 |
35 |
FourHundredGigE 1/0/67, FourHundredGigE 1/0/68 |
36 |
FourHundredGigE 1/0/69, FourHundredGigE 1/0/70 |
37 |
FourHundredGigE 1/0/71, FourHundredGigE 1/0/79 |
38 |
FourHundredGigE 1/0/72, FourHundredGigE 1/0/80 |
39 |
FourHundredGigE 1/0/75, FourHundredGigE 1/0/76 |
40 |
FourHundredGigE 1/0/77, FourHundredGigE 1/0/78 |
41 |
FourHundredGigE 1/0/81, FourHundredGigE 1/0/89 |
42 |
FourHundredGigE 1/0/82, FourHundredGigE 1/0/90 |
43 |
FourHundredGigE 1/0/83, FourHundredGigE 1/0/85 |
44 |
FourHundredGigE 1/0/84, FourHundredGigE 1/0/86 |
45 |
FourHundredGigE 1/0/87, FourHundredGigE 1/0/95 |
46 |
FourHundredGigE 1/0/88, FourHundredGigE 1/0/96 |
47 |
FourHundredGigE 1/0/91, FourHundredGigE 1/0/93 |
48 |
FourHundredGigE 1/0/92, FourHundredGigE 1/0/94 |
49 |
FourHundredGigE 1/0/97, FourHundredGigE 1/0/105 |
50 |
FourHundredGigE 1/0/98, FourHundredGigE 1/0/106 |
51 |
FourHundredGigE 1/0/99, FourHundredGigE 1/0/101 |
52 |
FourHundredGigE 1/0/100, FourHundredGigE 1/0/102 |
53 |
FourHundredGigE 1/0/103, FourHundredGigE 1/0/111 |
54 |
FourHundredGigE 1/0/104, FourHundredGigE 1/0/112 |
55 |
FourHundredGigE 1/0/107, FourHundredGigE 1/0/109 |
56 |
FourHundredGigE 1/0/108, FourHundredGigE 1/0/110 |
57 |
FourHundredGigE 1/0/113, FourHundredGigE 1/0/121 |
58 |
FourHundredGigE 1/0/114, FourHundredGigE 1/0/122 |
59 |
FourHundredGigE 1/0/115, FourHundredGigE 1/0/116 |
60 |
FourHundredGigE 1/0/117, FourHundredGigE 1/0/118 |
61 |
FourHundredGigE 1/0/119, FourHundredGigE 1/0/127 |
62 |
FourHundredGigE 1/0/120, FourHundredGigE 1/0/128 |
63 |
FourHundredGigE 1/0/123, FourHundredGigE 1/0/124 |
64 |
FourHundredGigE 1/0/125, FourHundredGigE 1/0/126 |
For an S9857-24DH8EP switch, when a 400-GE interface is changed to a 200-GE interface, the 400-GE interfaces in the same interface group are also changed to 200-GE interfaces. When a 200-GE interface is restored to a 400-GE interface, the adjacent 200-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 15 shows interface groups of an S9857-24DH8EP switch.
Table 15 Interface groups of an S9857-24DH8EP switch
Interface group number |
Interfaces |
1 |
FourHundredGigE 1/0/1, FourHundredGigE 1/0/2 |
2 |
FourHundredGigE 1/0/3, FourHundredGigE 1/0/4 |
3 |
FourHundredGigE 1/0/5, FourHundredGigE 1/0/6 |
4 |
FourHundredGigE 1/0/7, FourHundredGigE 1/0/8 |
5 |
FourHundredGigE 1/0/9, FourHundredGigE 1/0/10 |
6 |
FourHundredGigE 1/0/11, FourHundredGigE 1/0/12 |
7 |
FourHundredGigE 1/0/13, FourHundredGigE 1/0/14 |
8 |
FourHundredGigE 1/0/15, FourHundredGigE 1/0/16 |
9 |
FourHundredGigE 1/0/17, FourHundredGigE 1/0/18 |
10 |
FourHundredGigE 1/0/19, FourHundredGigE 1/0/20 |
11 |
FourHundredGigE 1/0/21, FourHundredGigE 1/0/22 |
12 |
FourHundredGigE 1/0/23, FourHundredGigE 1/0/24 |
Examples
# Split FourHundredGigE 1/0/1 into two 200-GE breakout interfaces.
<System> system-view
[System] interface fourhundredgige 1/0/1
[System-FourHundredGigE1/0/1] using twohundredgige
The interface FourHundredGigE1/0/1 will be deleted. Continue? [Y/N]:y
Related commands
using fourhundredgige
using eighthundredgige
Layer 2 Ethernet interface commands
display storm-constrain
Use display storm-constrain to display storm control settings and statistics.
Syntax
display storm-constrain [ broadcast | known-unicast | 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.
known-unicast: Displays known unicast 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;
KNUC - known unicast; FW - forwarding
Flow Statistic Interval: 5 (in seconds)
Port Type Lower Upper Unit CtrlMode Status Trap Log SwitchNum
--------------------------------------------------------------------------------
400GE1/0/1 MC 100 200 kbps shutdown shutdown off on 10
Table 16 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. |
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. |
CtrlMode |
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. |
SwitchNum |
Number of forwarding state changes of the interface. When the SwitchNum field reaches 65535, it resets automatically. |
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 | known-unicast | multicast | unicast } { pps | kbps | ratio } upperlimit lowerlimit
undo storm-constrain { all | broadcast | known-unicast | 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: unknown unicast, known unicast, multicast, and broadcast.
broadcast: Enables or disables broadcast storm control.
known-unicast: Enables or disables known unicast 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 0 to 1.4881 × the interface bandwidth.
· If you specify the kbps keyword, the value range for the upperlimit argument is 0 to the interface bandwidth.
· If you specify the ratio keyword, the value range for the upperlimit argument is 0 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 0 to 1.4881 × the interface bandwidth.
· If you specify the kbps keyword, the value range for the lowerlimit argument is 0 to the interface bandwidth.
· If you specify the ratio keyword, the value range for the lowerlimit argument is 0 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.
When configuring this command, make sure upperlimit is greater than lowerlimit.
Examples
# Enable unknown unicast storm control on FourHundredGigE 1/0/1 and set the upper and lower thresholds to 200 pps and 150 pps, respectively.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] storm-constrain unicast pps 200 150
# Enable broadcast storm control on FourHundredGigE 1/0/2, and set the upper and lower thresholds to 2000 kbps and 1500 kbps, respectively.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/2
[Sysname-FourHundredGigE1/0/2] storm-constrain broadcast kbps 2000 1500
# Enable multicast storm control on FourHundredGigE 1/0/3, and set the upper and lower thresholds to 80% and 15%, respectively.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/3
[Sysname-FourHundredGigE1/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 FourHundredGigE 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 fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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 FourHundredGigE 1/0/1 to output log messages when it detects storm control threshold events.
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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 FourHundredGigE 1/0/1 to send traps when it detects storm control threshold events.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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 configured for an Ethernet interface. The default MAC address for Layer 3 subinterface is the same as the MAC address of its main 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.
When you set a MAC address, make sure the following requirements are met:
· The MAC address must have the same highest 36 bits as the base MAC address.
· The MAC address must be no lower than the base MAC address plus 160 (decimal).
For more information about base MAC address, see MAC address table in Layer 2—LAN Switching Configuration Guide.
Examples
# Set the MAC address of FourHundredGigE 1/0/1 to 0001-0001-0001.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/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 varies by interface type.
Usage guidelines
A smaller MTU size results in more fragments. When you set the MTU for an interface, consider QoS queue lengths, for example, consider that the default FIFO queue length is 75. To prevent a too small MTU from causing packet drops in QoS queuing, you can perform one of the following configurations:
· Tune the MTU with the mtu command.
· Tune QoS queue lengths with the qos fifo queue-length command.
For more information about the qos fifo queue-length command, see ACL and QoS Command Reference.
Examples
# Set the MTU to 1430 bytes for FourHundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1
[Sysname-FourHundredGigE1/0/1] mtu 1430
# Set the MTU to 1430 bytes for FourHundredGigE 1/0/1.1.
<Sysname> system-view
[Sysname] interface fourhundredgige 1/0/1.1
[Sysname-FourHundredGigE1/0/1.1] mtu 1430