The expected bandwidth is an informational parameter used only by higher-layer protocols for calculation. You cannot adjust the actual bandwidth of an interface by using this command.

Examples

# Set the expected bandwidth of Ten-GigabitEthernet 1/0/1 to 1000 kbps.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] bandwidth 1000

# Set the expected bandwidth of Ten-GigabitEthernet 1/0/1.1 to 1000 kbps.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1.1

[Sysname-Ten-GigabitEthernet1/0/1.1] bandwidth 1000

Related commands

speed

broadcast-suppression

Use broadcast-suppression to enable broadcast suppression and set the broadcast suppression threshold.

Use undo broadcast-suppression to disable broadcast suppression.

Syntax

broadcast-suppression { ratio | pps max-pps | kbps max-kbps }

undo broadcast-suppression

Default

Ethernet interfaces do not suppress broadcast traffic.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

ratio: Sets the broadcast suppression threshold as a percentage of the interface bandwidth. The value range for this argument is 0 to 100. A smaller value means that less broadcast traffic is allowed to pass through.

pps max-pps: Specifies the maximum number of broadcast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.

kbps max-kbps: Specifies the maximum number of kilobits of broadcast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.

Usage guidelines

The broadcast storm suppression features limits the size of broadcast traffic to a threshold on an interface. When the broadcast traffic on the interface exceeds this threshold, the system drops packets until the traffic drops below this threshold.

Both the storm-constrain command and the broadcast-suppression command can suppress broadcast storms on a port. The broadcast-suppression command uses the chip to physically suppress broadcast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress broadcast traffic.

For the traffic suppression result to be determined, do not configure both the storm-constrain broadcast command and the broadcast-suppression command on an interface.

When you configure the suppression threshold in kbps, the actual suppression threshold might be different from the configured one as follows:

· If the configured value is smaller than 64, the value of 64 takes effect.

· If the configured value is greater than 64 but not an integer multiple of 64, the integer multiple of 64 that is greater than and closest to the configured value takes effect.

For the suppression threshold that takes effect, see the prompt on the device.

Examples

# Set the broadcast suppression threshold to 10000 kbps on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] broadcast-suppression kbps 10000

The actual value is 10048 on port Ten-GigabitEthernet1/0/1 currently.

The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.

Related commands

multicast-suppression

unicast-suppression

dampening

Use dampening to enable the device to dampen an interface when the interface is flapping.

Use undo dampening to restore the default.

Syntax

dampening [ half-life reuse suppress max-suppress-time ]

undo dampening

Default

Interface dampening is disabled on Ethernet interfaces.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

half-life: Specifies the amount of time after which a penalty is decreased, in the range of 1 to 120 seconds. The default value is 54 seconds.

reuse: Specifies the reuse threshold in the range of 200 to 20000. The default value is 750. The reuse threshold must be less than the suppression threshold.

suppress: Specifies the suppression threshold in the range of 200 to 20000. The default value is 2000.

max-suppress-time: Specifies the maximum amount of time the interface can be dampened, in the range of 1 to 255 seconds. The default value is 162 seconds (three times the half-life timer).

Usage guidelines

This command and the link-delay command cannot be both configured on an interface.

This command does not take effect on the administratively down events. When you execute the shutdown command, the penalty restores to 0, and the interface reports the down event to the higher layer protocols.

Do not enable the dampening function on an interface with RRPP, MSTP, or Smart Link enabled.

After an interface in down state is dampened, the interface state displayed through the display interface command is always down.

Examples

# Enable interface dampening on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] dampening

# Enable interface dampening on Ten-GigabitEthernet 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 ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] dampening 2 800 3000 5

Related commands

display interface

link-delay

default

Use default to restore the default settings for an interface.

Syntax

default

Views

Ethernet interface view

Ethernet subinterface view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

The default command might interrupt ongoing network services. Make sure you are fully aware of the impacts of this command when you use it in a live network.

This command might fail to restore the default settings for some commands because of command dependencies or system restrictions. You can use the display this command in interface view to identify these commands, and use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to solve the problem.

Examples

# Restore the default settings for Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] default

# Restore the default settings for Ten-GigabitEthernet 1/0/1.1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1.1

[Sysname-Ten-GigabitEthernet1/0/1.1] default

description

Use description to configure the description of an interface.

Use undo description to restore the default.

Syntax

description text

undo description

Default

The description of an interface is the interface name plus Interface (for example, Ten-GigabitEthernet1/0/1 Interface).

Views

Ethernet interface view

Ethernet subinterface view

Predefined user roles

network-admin

Parameters

text: Specifies the interface description, a case-sensitive string of 1 to 255 characters.

Examples

# Set the description of Ten-GigabitEthernet 1/0/1 to lan-interface.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] description lan-interface

# Set the description of Ten-GigabitEthernet 1/0/1.1 to subinterface1/0/1.1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1.1

[Sysname-Ten-GigabitEthernet1/0/1.1] description subinterface1/0/1.1

display counters

Use display counters to display interface traffic statistics.

Syntax

display counters { inbound | outbound } interface [ interface-type [ interface-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

inbound: Displays inbound traffic statistics.

outbound: Displays outbound traffic statistics.

interface-type: Specifies an interface type.

interface-number: Specifies an interface number.

Usage guidelines

To clear the Ethernet interface traffic statistics, use the reset counters interface command.

If you do not specify an interface type, this command displays traffic statistics for all interfaces that have traffic counters.

If you specify an interface type but do not specify an interface number, this command displays traffic statistics for all interfaces of the specified type.

If you specify an interface type and an interface, this command displays traffic statistics for the specified interface.

Examples

# Display inbound traffic statistics for all GigabitEthernet interfaces.

<Sysname> display counters inbound interface gigabitethernet

Interface Total(pkt) Broadcast(pkt) Multicast(pkt) Err(pkt)

XGE1/0/1 100 100 0 0

XGE1/0/2 Overflow Overflow Overflow Overflow

Overflow: More than 14 digits (7 digits for column "Err").

--: Not supported.

Table 1 Command output

Field	Description
Interface	Abbreviated interface name.
Total(pkt)	Total number of packets received or sent through the interface.
Broadcast(pkt)	Total number of broadcast packets received or sent through the interface.
Multicast(pkt)	Total number of multicast packets received or sent through the interface.
Err(pkt)	Total number of error packets received or sent through the interface.
Overflow: More than 14 digits (7 digits for column "Err")	The command displays Overflow when any of the following conditions exist: · The data length of an Err field value is greater than 7 decimal digits. · The data length of a non-Err field value is greater than 14 decimal digits.
--: Not supported	The statistical item is not supported.

Related commands

reset counters interface

display counters rate

Use display counters rate to display traffic rate statistics for interfaces in up state within the most recent statistics polling interval.

Syntax

display counters rate [ inbound | outbound ] interface [ interface-type [ interface-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

inbound: Displays inbound traffic rate statistics.

outbound: Displays outbound traffic rate statistics.

interface-type: Specifies an interface type.

interface-number: Specifies an interface number.

Usage guidelines

If you do not specify the inbound or outbound keyword, this command displays both the inbound and outbound traffic rate statistics for interfaces in up state within the most recent statistics polling interval.

If you do not specify an interface type, this command displays traffic rate statistics for all up interfaces that have traffic counters.

If you specify an interface type but do not specify an interface number or subinterface number, this command displays traffic rate statistics for all up interfaces of the specified type.

If you specify an interface type and an interface or subinterface number, this command displays traffic rate statistics for the specified interface or subinterface.

If an interface that you specify is always down for the most recent statistics polling interval, the system prompts that the interface does not support the command.

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.

Examples

# Display the inbound and outbound traffic rate statistics for Ten-GigabitEthernet 1/0/1.

<Sysname> display counters rate interface ten-gigabitethernet 1/0/1

Usage: Bandwidth utilization in percentage

Interface InUsage(%) InTotal(pps) OutUsage(%) OutTotal(pps)

XGE1/0/1 0 0 0 0

Overflow: More than 14 digits.

--: Not supported.

# Display the inbound traffic rate statistics for all GigabitEthernet interfaces.

<Sysname> display counters rate inbound interface gigabitethernet

Usage: Bandwidth utilization in percentage

Interface Usage(%) Total(pps) Broadcast(pps) Multicast(pps)

XGE1/0/1 3 200 100 100

Overflow: More than 14 digits.

--: Not supported.

Table 2 Command output

Field	Description
Interface	Abbreviated interface name.
Usage(%)	Bandwidth usage (in percentage) of the interface within the most recent statistics polling interval.
Total(pps)	Average receiving or sending rate (in pps) for all packets within the most recent statistics polling interval.
InUsage(%)	Bandwidth usage (in percentage) of all inbound packets within the most recent statistics polling interval. When the usage is smaller than 1%, 1% is displayed.
InTotal(pps)	Average receiving rate (in pps) for all packets within the most recent statistics polling interval.
OutUsage(%)	Bandwidth usage (in percentage) of all outbound packets within the most recent statistics polling interval. When the usage is smaller than 1%, 1% is displayed.
OutTotal(pps)	Average sending rate (in pps) for all packets within the most recent statistics polling interval.
Broadcast(pps)	Average receiving or sending rate (in pps) for broadcast packets within the most recent statistics polling interval.
Multicast(pps)	Average receiving or sending rate (in pps) for multicast packets within the most recent statistics polling interval.
Overflow: more than 14 decimal digits	The command displays Overflow if the data length of a statistical item is greater than 14 decimal digits.
--: not supported	The statistical item is not supported.

Related commands

flow-interval

reset counters interface

display ethernet statistics

Use display ethernet statistics to display the Ethernet module statistics.

Syntax

display ethernet statistics slot slot-number

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies 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 3 Output description

Field	Description
ETH receive packet statistics	Statistics about the Ethernet packets received by the Ethernet module: · Totalnum—Total number of received packets. · ETHIINum—Number of packets encapsulated by using Ethernet II. · SNAPNum—Number of packets encapsulated by using SNAP. · RAWNum—Number of packets encapsulated by using RAW. · LLCNum—Number of packets encapsulated by using LLC. · UnknownNum—Number of packets encapsulated by using unknown methods. · ForwardNum—Number of packets forwarded at Layer 2 or sent to the CPU. ‌ · ARP—Number of ARP packets. · MPLS—Number of MPLS packets. · ISIS—Number of IS-IS packets. · ISIS2—Number of large 802.3/802.2 frames encapsulated by using IS-IS. · IP—Number of IP packets. · IPv6—Number of IPv6 packets.‌
ETH receive error statistics	Statistics about the error Ethernet packets in the inbound direction on the Ethernet module. Errors might be included in packets or occur during the receiving process. The items include: · NullPoint—Number of packets that include null pointers. · ErrIfindex—Number of packets that include incorrect interface indexes. · ErrIfcb—Number of packets that include incorrect interface control blocks. · IfShut—Number of packets that are being received when the interface is shut down. · ErrAnalyse—Number of packets that include packet parsing errors. · ErrSrcMAC—Number of packets that include incorrect source MAC addresses. · ErrHdrLen—Number of packets that include header length errors.
ETH send packet statistics	Statistics about the Ethernet packets sent by the Ethernet module: · L3OutNum—Number of packets sent out of Layer 3 Ethernet interfaces. · VLANOutNum—Number of packets sent out of VLAN interfaces. ‌ · FastOutNum—Number of packets fast forwarded. · L2OutNum—Number of packets sent out of Layer 2 Ethernet interfaces. ‌ · MbufRelayNum—Number of packets transparently sent.
ETH send error statistics	Statistics about the error Ethernet packets in the outbound direction on the Ethernet module: · NullMbuf—Number of packets with null pointers. · ErrAdjFwd—Number of packets with adjacency table errors. ‌ · ErrPrepend—Number of packets with extension errors. · ErrHdrLen—Number of packets with header length errors. · ErrPad—Number of packets with padding errors. · ErrQoSTrs—Number of packets that failed to be sent by QoS. · ErrVLANTrs—Number of packets that failed to be sent in VLANs. ‌ · ErrEncap—Number of packets that failed to be sent due to link header encapsulation failures. · ErrTagVLAN—Number of packets that failed to be sent due to VLAN tag encapsulation failures. ‌ · IfShut—Number of packets that are being sent when the interface is shut down. · IfErr—Number of packets with incorrect outgoing interfaces.

‌

Related commands

reset ethernet statistics

display interface

Use display interface to display interface information.

Syntax

display interface [ interface-type [ interface-number | interface-number.subnumber ] ] [ brief [ description | down ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type: Specifies an interface type.

interface-number: Specifies an interface number.

interface-number.subnumber: Specifies a subinterface number. The interface-number argument is an interface number. The subnumber argument is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.

brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.

description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 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 specify an interface type but do not specify an interface number or subinterface number, this command displays information about all interfaces of the specified type.

Examples

# Display information about Layer 3 interface Ten-GigabitEthernet 1/0/1.

<Sysname> display interface ten-gigabitethernet 1/0/1

Ten-GigabitEthernet1/0/1

Current state: Administratively DOWN

Line protocol state: DOWN

Description: Ten-GigabitEthernet1/0/1 Interface

Bandwidth: 1000000 kbps

Maximum transmission unit: 1500

Allow jumbo frames to pass

Broadcast max-ratio: 100%

Multicast max-ratio: 100%

Unicast max-ratio: 100%

Internet protocol processing: Disabled

IP packet frame type: Ethernet II, hardware address: 3822-d666-bd0c

IPv6 packet frame type: Ethernet II, hardware address: 3822-d666-bd0c

Flow-control is not enabled

Loopback is not set

Media type is twisted pair, port hardware type is 1000_BASE_T

Port priority: 2

Unknown-speed mode, unknown-duplex mode

Last link flapping: 6 hours 39 minutes 28 seconds

Last clearing of counters: Never

Current system time: 2017-10-27 15:10:03

Last time when physical state changed to up:-

Last time when physical state changed to down: 2017-10-27 14:56:38

Last 300 seconds input: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%

Last 300 seconds output: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%

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

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

# Display detailed information about Layer 2 interface Ten-GigabitEthernet 1/0/1.

<Sysname> display interface ten-gigabitethernet 1/0/1

Ten-GigabitEthernet1/0/1

Current state: DOWN

Line protocol state: DOWN

IP packet frame type: Ethernet II, hardware address: 000c-2963-b767

Description: Ten-GigabitEthernet1/0/1 Interface

Bandwidth: 100000 kbps

Loopback is not set

Media type is twisted pair,port hardware type is 1000_BASE_T_AN_SFP

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%

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 clearing of counters: 14:34:09 Tue 11/01/2011

Current system time: 2017-10-27 15:10:03

Last time when physical state changed to up:-

Last time when physical state changed to down: 2017-10-27 14:56:38

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 0 bits/sec 0.00%

Last 300 seconds output: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%

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

Table 4 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 ( Link-Aggregation interface down )—The aggregate interface to which the interface belongs has been shut down by using the shutdown command. · mac-address moving down—The interface has been shut down by the MAC address move suppression feature. · 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. · UP—The interface is both administratively and physically up.
Line protocol state	Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · UP (spoofing)—The data link layer protocol is up, but the link is an on-demand link or does not exist. This attribute is typical of null interfaces and loopback interfaces. · DOWN—The data link layer protocol is down. · DOWN (protocols)—The data link layer has been shut down by protocols included in the parentheses. Available protocols include: ¡ DLDP—Shuts down the data link layer when it detects that the link is unidirectional. ¡ OAM—Shuts down the data link layer when it detects a remote link failure. ¡ LAGG—Shuts down the data link layer when it detects that the aggregate interface does not have Selected ports. ¡ BFD—Shuts down the data link layer when it detects a link failure.
Bandwidth	Expected bandwidth of the interface.
Maximum transmission unit	MTU of the interface.
Internet protocol processing	IP configuration parameter 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. · MTunnel—IP address of the multicast tunnel interface (MTI), which is the same as the IP address of the MVPN source interface. For more information, see multicast VPN configuration in IP Multicast Configuration Guide.
IP packet frame type	IPv4 packet framing format.
hardware address	MAC address of the interface.
IPv6 packet frame type	IPv6 packet framing format.
FEC mode	FEC mode of the interface, which depends on the configuration. When the FEC mode of an interface is set to autonegotiation, the actual FEC mode depends on the model of the transceiver module installed in the fiber port.
Port priority	Port priority of the interface.
Loopback is set internal	An internal loopback test is running on the interface. This field depends on your configuration .
Loopback is set external	An external loopback test is running on the interface. This field depends on your configuration.
Loopback is not set	No loopback test is running on the interface. This field depends on your configuration.
1000Mbps-speed mode	The interface is operating at 1000 Mbps. This field depends on your configuration and the link parameter negotiation result.
10Gbps-speed mode	The interface is operating at 10 Gbps. This field depends on your configuration and the link parameter negotiation result.
40Gbps-speed mode	The interface is operating at 40 Gbps. This field depends on your configuration and the link parameter negotiation result.
100Gbps-speed mode	The interface is operating at 100 Gbps. This field depends on your configuration and the link parameter negotiation result.
Unknown-speed mode	The speed of the interface is unknown because the speed negotiation fails or the interface is physically disconnected.
full-duplex mode	The interface is operating in full duplex mode. This field depends on your configuration and the link parameter negotiation result.
unknown-duplex mode	The duplex mode of the interface is unknown because the duplex mode negotiation fails or the interface is physically disconnected.
Link speed type is autonegotiation	The interface is configured with the speed auto command.
Link speed type is force link	The interface is manually configured with a speed (for example, 10 Mbps or 100 Mbps) by using the speed command.
link duplex type is autonegotiation	The interface is configured with the duplex auto command.
link duplex type is force link	The interface is manually configured with a duplex mode (for example, half or full) by using the duplex command.
Flow-control is not enabled	Generic flow control is disabled on the interface. This field depends on your configuration and the link parameter negotiation result.
Maximum frame length	Maximum length of Ethernet frames allowed to pass through the interface.
Allow jumbo frame to pass	The interface allows jumbo frames to pass through.
Broadcast max-	‌Broadcast storm suppression threshold 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 clearing of counters	Time when the reset counters interface command was last used to clear the interface statistics. This field displays Never if the reset counters interface command has never been used on the interface since device startup.
Current system time	Current system time in the YYYY/MM/DD HH:MM:SS format. If the time zone is configured, this field is in the YYYY/MM/DD HH:MM:SS UTC±HH:MM:SS format.
Last time when physical state changed to up	Last time when physical state of the interface changed to up. A hyphen (-) indicates that the physical state of the interface has not changed to up.
Last time when physical state changed to down	Last time when physical state of the interface changed to down. A hyphen (-) indicates that the physical state of the interface has not changed to down.
Last 300 seconds input: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00% Last 300 seconds output: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%	Average inbound or outbound traffic rate (in pps, Bps, and bps) in the last statistics polling interval, and the ratio of the actual rate to the interface bandwidth. To set the statistics polling interval, execute the flow-interval command. A hyphen (-) indicates that the statistical item is not supported.
Input(total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses	The two fields on the first line represent the inbound traffic statistics (in packets and bytes) for the interface. All inbound normal packets, abnormal packets, and normal pause frames were counted. The four fields on the second line represent: · Number of inbound unicast packets. · Number of inbound broadcasts. · Number of inbound multicasts. · Number of inbound pause frames. A hyphen (-) indicates that the statistical item is not supported.
Input(normal): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses	The two fields on the first line represent the inbound normal traffic and pause frame statistics (in packets and bytes) for the interface. The four fields on the second line represent: · Number of inbound normal unicast packets. · Number of inbound normal broadcasts. · Number of inbound normal multicasts. · Number of inbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported.
input errors	Statistics of incoming error packets.
runts	Number of inbound frames meeting the following conditions: · Shorter than 64 bytes. · In correct format. · Containing valid CRCs.
giants	Number of inbound giants. Giants refer to frames larger than the maximum frame length supported on the interface. For an Ethernet interface that does not permit jumbo frames, the maximum frame length is as follows: · 1518 bytes (without VLAN tags). · 1522 bytes (with VLAN tags). For an Ethernet interface that permits jumbo frames, the maximum Ethernet frame length is set when you configure jumbo frame support on the interface.
throttles	Number of inbound frames that had a non-integer number of bytes.
CRC	Total number of inbound frames that had a normal length, but contained CRC errors.
frame	Total number of inbound frames that contained CRC errors and a non-integer number of bytes.
overruns	Number of packets dropped because the input rate of the port exceeded the queuing capability.
aborts	Total number of illegal inbound packets: · Fragment frames—CRC error frames shorter than 64 bytes. The length (in bytes) can be an integral or non-integral value. · Jabber frames—CRC error frames greater than the maximum frame length supported on the Ethernet interface (with an integral or non-integral length). ¡ For an Ethernet interface that does not permit jumbo frames, the maximum frame length is 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). ¡ For an Ethernet interface that permits jumbo frames, the maximum Ethernet frame length is set when you configure jumbo frame support on the interface. · Symbol error frames—Frames that contained a minimum of one undefined symbol. · Unknown operation code frames—Non-pause MAC control frames. · Length error frames—Frames whose 802.3 length fields did not match the actual frame length (46 to 1500 bytes).
ignored	Number of inbound frames dropped because the receiving buffer of the port ran low.
parity errors	Total number of frames with parity errors.
Output(total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses	The two fields on the first line represent the outbound traffic statistics (in packets and bytes) for the interface. All outbound normal packets, abnormal packets, and normal pause frames were counted. The four fields on the second line represent: · Number of outbound unicast packets. · Number of outbound broadcasts. · Number of outbound multicasts. · Number of outbound pause frames. A hyphen (-) indicates that the statistical item is not supported.
Output(normal): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses	The two fields on the first line represent the outbound normal traffic and pause frame statistics (in packets and bytes) for the interface. The four fields on the second line represent: · Number of outbound normal unicast packets. · Number of outbound normal broadcasts. · Number of outbound normal multicasts. · Number of outbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported.
output errors	Number of outbound packets with errors.
underruns	Number of packets dropped because the output rate of the interface exceeded the output queuing capability. This is a low-probability hardware anomaly.
buffer failures	Number of packets dropped because the transmitting buffer of the interface ran low.
aborts	Number of packets that failed to be transmitted, for example, because of Ethernet collisions.
deferred	Number of frames that the interface deferred to transmit because of detected collisions.
collisions	Number of frames that the interface stopped transmitting because Ethernet collisions were detected during transmission.
late collisions	‌Number of frames that the interface deferred to transmit after transmitting their first 512 bits because of detected collisions.
lost carrier	‌Number of carrier losses during transmission. This counter increases by one when a carrier is lost, and applies to serial WAN interfaces.
no carrier	Number of times that the port failed to detect the carrier when attempting to send frames. This counter increases by one when a port failed to detect the carrier, and applies to serial WAN interfaces.
Peak input rate	Peak rate of inbound traffic in Bps, and the time when the peak inbound traffic rate occurred.
Peak output rate	Peak rate of outbound traffic in Bps, and the time when the peak outbound traffic rate occurred.

# 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

XGE1/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

XGE1/0/2 DOWN auto A A 1

XGE1/0/3 UP 1G(a) F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaaaa

# Display brief information about Ten-GigabitEthernet 1/0/3, including the complete description of the interface.

<Sysname> display interface ten-gigabitethernet 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

XGE1/0/3 UP 1G(a) 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

XGE1/0/1 DOWN Not connected

Brief information on interfaces in bridge mode:

Link: ADM - administratively down; Stby - standby

Interface Link Cause

XGE1/0/2 DOWN Not connected

Table 5 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.
Protocol	Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces.
Primary IP	Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address.
Description	Description of the interface.
Brief information of interfaces in bridge mode:	Brief information about Layer 2 interfaces.
Type: A - access; T - trunk; H – hybrid	Link type options for interfaces.
Speed	Speed of the interface, in bps. This field displays the (a) flag next to the speed if the speed is automatically negotiated. This field displays auto if the interface is configured to autonegotiate its speed but the autonegotiation has not started.
Duplex	Duplex mode of the interface: · A—Autonegotiation. The interface is configured to autonegotiate its duplex mode but the autonegotiation has not started. · F—Full duplex. · F(a)—Autonegotiated full duplex. · H—Half duplex. ‌ · H(a)—Autonegotiated half duplex. ‌
Type	Link type of the interface: · A—Access. · H—Hybrid. · T—Trunk.
PVID	Port VLAN ID.
Cause	Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · DOWN ( Link-Aggregation interface down )—The interface is a member port of an aggregate interface, and the aggregate interface is down. · DOWN (Loopback detection down)—The loopback detection module has detected loops. · DOWN ( Monitor-Link uplink down )—The monitor link module has detected that the uplink is down. · 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.

‌

Related commands

reset counters interface

display interface link-info

Use display interface link-info to display the status and packet statistics of interfaces.

Syntax

display interface link-info [ main ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

main: Specifies all interfaces except subinterfaces. If you do not specify this keyword, this command displays status and packet statistics of all interfaces.

Examples

# Display status and statistics of all interfaces.

<Sysname> display interface link-info

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol InUsage OutUsage InErrs OutErrs

XGE1/0/1 UP UP 10.09% 0% 0 0

NULL0 UP UP(s) 0% 0% 0 0

Overflow: More than 7 digits.

--: Not supported.

Table 6 Command output

Field	Description
Link: ADM - administratively down; Stby - standby	Physical link state of the interface: · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state.
Protocol: (s) – spoofing	The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces, loopback interfaces, and InLoopback interfaces.
Interface	Abbreviated interface name.
Link	Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command.
Protocol	Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces, loopback interfaces, and InLoopback interfaces.
InUsage	Inbound bandwidth usage within the most recent statistics polling interval. It is calculated by this formula: Average inbound speed of the interface within the most recent statistics polling interval/interface bandwidth. When the usage is smaller than 0.01%, 0.01% is displayed. To set the statistics polling interval, use the flow-interval command.
OutUsage	Outbound bandwidth usage within the most recent statistics polling interval. It is calculated by this formula: Average outbound speed of the interface within the most recent statistics polling interval/interface bandwidth. When the usage is smaller than 0.01%, 0.01% is displayed. To set the statistics polling interval, use the flow-interval command.
InErrs	Number of error packets received.
OutErrs	Number of error packets sent.
Overflow: More than 7 digits.	The data length of a statistical item value is greater than 7 decimal digits.
--: Not supported.	A hyphen (-) indicates that the corresponding statistical item is not supported.

Related commands

flow-interval

display interface main

Use display interface main to display operating status and information of all interfaces except subinterfaces.

Syntax

display interface [ interface-type ] [ brief [ description | down ] ] main

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type: Specifies an interface type. If you do not specify this argument, the command displays information about interfaces of all types.

brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.

description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 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.

Examples

# Display operating status and information of all interfaces except subinterfaces.

<Sysname> display interface main

Ten-GigabitEthernet1/0/1

Current state: Administratively DOWN

Line protocol state: DOWN

IP packet frame type: Ethernet II, hardware address: 4005-6538-0100

Description: Ten-GigabitEthernet1/0/1 Interface

Bandwidth: 1000000 kbps

Loopback is not set

Unknown-speed mode, unknown-duplex mode

Link speed type is autonegotiation, link duplex type is autonegotiation

Flow-control is not enabled

Maximum frame length: 9216

Allow jumbo frames to pass

Broadcast max-ratio: 100%

Multicast max-ratio: 100%

Unicast max-ratio: 100%

PVID: 1

MDI type: Automdix

Port link-type: Access

Tagged VLANs: None

Untagged VLANs: 1

Port priority: 2

Last link flapping: Never

Last clearing of counters: Never

Current system time:2018-04-11 10:20:24

Last time when physical state changed to up:-

Last time when physical state changed to down:2018-04-11 09:11:09

Peak input rate: 0 bytes/sec, at 00-00-00 00:00:00

Peak output rate: 0 bytes/sec, at 00-00-00 00:00:00

Last 300 seconds input: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%

Last 300 seconds output: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%

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

Ten-GigabitEthernet1/0/2

Current state: Administratively DOWN

Line protocol state: DOWN

Description: Ten-GigabitEthernet1/0/2 Interface

Bandwidth: 1000000 kbps

Flow-control is not enabled

Maximum transmission unit: 1500

Allow jumbo frames to pass

Broadcast max-ratio: 100%

Multicast max-ratio: 100%

Unicast max-ratio: 100%

Internet protocol processing: Disabled

IP packet frame type: Ethernet II, hardware address: 4005-6538-0107

IPv6 packet frame type: Ethernet II, hardware address: 4005-6538-0107

Output queue - Urgent queuing: Size/Length/Discards 0/100/0

Output queue - Protocol queuing: Size/Length/Discards 0/500/0

Output queue - FIFO queuing: Size/Length/Discards 0/75/0

Last link flapping: Never

Last clearing of counters: Never

Current system time:2018-04-11 10:20:24

Last time when physical state changed to up:-

Last time when physical state changed to down:2018-04-11 09:33:52

Peak input rate: 0 bytes/sec, at 00-00-00 00:00:00

Peak output rate: 0 bytes/sec, at 00-00-00 00:00:00

Last 300 seconds input: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%

Last 300 seconds output: 0 packets/sec 0 bytes/sec 0 bits/sec 0.00%

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

# Display brief information of all interfaces except subinterfaces.

<Sysname> display interface brief main

Brief information on interfaces in route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) – spoofing

Interface Link Protocol Primary IP Description

XGE1/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

XGE1/0/2 DOWN auto A A 1

# Display brief information about all interfaces, including the complete interface descriptions.

<Sysname> display interface brief description main

Brief information on interfaces in bridge mode:

Link: ADM - administratively down; Stby - standby

Speed: (a) - auto

Duplex: (a)/A - auto; H - half; F - full

Type: A - access; T - trunk; H - hybrid

Interface Link Speed Duplex Type PVID Description

XGE1/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 main

Brief information on interfaces in route mode:

Link: ADM - administratively down; Stby - standby

Interface Link Cause

XGE1/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

XGE1/0/2 DOWN Not connected

For description on the display interface main command output, see Table 4 and Table 5.

display interface split-capable

Use display interface split-capable to display interfaces capable of being split.

Syntax

display interface split-capable [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number, which is fixed at 1.

Examples

# Display interfaces capable of being split.

<Sysname> display interface split-capable

slot 1:

100-GE interfaces capable of being split into multiple 10-GE or 25-GE interfaces

HundredGigE1/0/25 HundredGigE1/0/26 HundredGigE1/0/27

HundredGigE1/0/28 HundredGigE1/0/29 HundredGigE1/0/30

40-GE interfaces capable of being split into four 10-GE interfaces:

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. If you do not specify an interface type, this command displays information about dropped packets on all interfaces on the device.

interface-number: Specifies an interface number. If you do not specify an interface number, this command displays information about dropped packets on all interfaces of the specified type.

summary: Displays the summary of dropped packets on all interfaces.

Examples

# Display information about dropped packets on Ten-GigabitEthernet 1/0/1.

<Sysname> display packet-drop interface ten-gigabitethernet 1/0/1

Ten-GigabitEthernet1/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: 321

Packets dropped due to rate-limit: 143

Packets dropped due to broadcast-suppression: 301

Packets dropped due to unicast-suppression: 215

Packets dropped due to multicast-suppression: 241

Packets dropped due to Tx packet aging: 246

# Display the summary of dropped packets on all interfaces.

<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: 321

Packets dropped due to rate-limit: 143

Packets dropped due to broadcast-suppression: 301

Packets dropped due to unicast-suppression: 215

Packets dropped due to multicast-suppression: 241

Packets dropped due to Tx packet aging: 246

Table 7 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 rate-limit	Packets that are dropped due to the rate limit set on the device.
Packets dropped due to broadcast-suppression	Packets that are dropped due to broadcast suppression.
Packets dropped due to unicast-suppression	Packets that are dropped due to unknown unicast suppression.
Packets dropped due to multicast-suppression	Packets that are dropped due to multicast suppression.
Packets dropped due to Tx packet aging	Outbound packets that are timed out.

‌

display priority-flow-control

Use display priority-flow-control to display priority-based flow control (PFC) information on an interface.

Syntax

display priority-flow-control 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 PFC information for all Ethernet interfaces.

If you specify an interface type but do not specify an interface number, this command displays PFC information for all interfaces of the specified type.

If you specify an interface type and an interface number, this command displays PFC information for the specified interface.

Examples

# Display the PFC information for all Ethernet interfaces.

Conf -- Configured mode Ne -- Negotiated mode P -- Priority

Interface Conf Ne Dot1pList P Recv Sent

XGE1/0/1 Off Off

Table 8 Command output

Field	Description
Conf -- Configured mode	Locally configured PFC status.
Ne -- Negotiated mode	Negotiated PFC status.
P -- Priority	802.1p priority value for which PFC is enabled.
Interface	Abbreviated name of the interface.
Conf	Locally configured PFC status: · Auto—The interface is configured to autonegotiate the PFC status with the remote end. · Off—PFC is disabled for the interface. · On—PFC is enabled for the interface.
Ne	Negotiated PFC status: · Off—PFC is disabled. · On—PFC is enabled.
Dot1pList	802.1p priorities that are enabled with PFC. 802.1p priority values 0 through 7 are available.
P	An 802.1p priority is displayed only when the 802.1p priority is enabled with PFC and the interface has received or sent packets with the 802.1p priority.
Recv	Number of received PFC pause frames.
Sent	Number of sent PFC pause frames.

Related commands

priority-flow-control

priority-flow-control no-drop dot1p

duplex

Use duplex to set the duplex mode for an Ethernet interface.

Use undo duplex to restore the default.

Syntax

duplex { auto | full | half }

undo duplex

Default

Ethernet interfaces autonegotiate the duplex 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.

half: Configures the interface to operate in half duplex mode. In this mode, the interface can only receive or transmit packets at a given time. This keyword is supported only on management Ethernet interfaces.

Examples

# Configure Ten-GigabitEthernet 1/0/1 to operate in full duplex mode.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/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.

This command and the priority-flow-control no-drop dot1p command are mutually exclusive.

Examples

# Enable TxRx-mode generic flow control on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] flow-control

flow-control receive enable

Use flow-control receive enable to enable Rx-mode generic flow control on an Ethernet port.

Use undo flow-control to disable Rx-mode generic flow control on an Ethernet port.

Syntax

flow-control receive enable

undo flow-control

Default

Rx-mode generic flow control is disabled on Ethernet interfaces.

Views

Ethernet interface view

Predefined user roles

network-admin

Usage guidelines

With Rx-mode flow control enabled, an interface can receive but cannot send flow control frames.

· When the interface receives a flow control frame from its peer, it suspends sending packets to the peer.

· When traffic congestion occurs on the interface, it cannot send flow control frames to the peer.

To handle unidirectional traffic congestion on a link, configure the flow-control receive enable command at one end, and the flow-control command at the other. To enable both ends of the link to handle traffic congestion, configure the flow-control command at both ends.

This command is mutually exclusive with the priority-flow-control or priority-flow-control no-drop dot1p command.

Examples

# Enable Rx-mode generic flow control on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-ten-gigabitethernet 1/0/1] flow-control receive enable

Related commands

flow-control

flow-interval

Use flow-interval to set the statistics polling interval.

Use undo flow-interval to restore the default.

Syntax

flow-interval interval

undo flow-interval

Default

The statistics polling interval is 300 seconds.

Views

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

The statistics polling interval configured in system view takes effect on all Ethernet interfaces.

The statistics polling interval configured in Ethernet interface view takes effect only on the current 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.

You can use the display interface command to view the statistics only after two consecutive statistics polling intervals. The statistics are displayed by the Last interval second input and Last interval second input fields in the display interface command output.

Examples

# Set the statistics polling interval to 100 seconds on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] flow-interval 100

Related commands

display interface

ifmonitor crc-error

Use ifmonitor crc-error to configure global CRC error packet alarm parameters.

Use undo ifmonitor crc-error to restore the default.

NOTE:

This command is supported only in R3608 and later.

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 a card by its slot number.

Usage guidelines

With the CRC error packet alarm function enabled, when the number of incoming CRC error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of incoming CRC error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.

You can configure the CRC error packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for CRC error packet alarms.

<Sysname> system-view

[Sysname] ifmonitor crc-error slot 1 high-threshold 5000 low-threshold 400 interval 6

Related commands

snmp-agent trap enable ifmonitor

ifmonitor giant

Use ifmonitor giant to configure global giant packet alarm parameters.

Use undo ifmonitor giant to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

ifmonitor giant slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor giant 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 giant packet alarms.

Views

System view

Predefined user roles

network-admin

Parameters

high-threshold high-value: Specifies the upper threshold for giant packet alarms, in the range of 1 to 4294967295 packets.

low-threshold low-value: Specifies the lower threshold for giant packet alarms, in the range of 1 to 4294967295 packets.

interval interval: Specifies the statistics collection and comparison interval for giant packets, in the range of 1 to 65535 seconds.

shutdown: Shuts down an interface when the number of incoming giant 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.

slot slot-number: Specifies a card by its slot number.

Usage guidelines

With the giant packet alarm function enabled, when the number of incoming giant 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 giant 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 giant packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for giant packet alarms.

<Sysname> system-view

[Sysname] ifmonitor giant slot 1 high-threshold 5 low-threshold 4 interval 6

Related commands

port ifmonitor giant

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.

NOTE:

This command is supported only in R3608 and later.

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 a card by its slot number.

Usage guidelines

With the input error packet alarm function enabled, when the number of input error packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of input error packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.

You can configure the input error packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for input error packet alarms.

<Sysname> system-view

[Sysname] ifmonitor input-error slot 1 high-threshold 5000 low-threshold 400 interval 6

Related commands

snmp-agent trap enable ifmonitor

ifmonitor input-usage

Use ifmonitor input-usage to configure global input bandwidth usage alarm parameters.

Use undo ifmonitor input-usage to restore the default.

NOTE:

This command is supported only in R3608 and later.

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 a card by its slot number.

Usage guidelines

With the input bandwidth usage alarm function enabled, when the input bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the input bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.

You can use the flow-interval command to set the statistics polling interval.

You can configure the input bandwidth usage alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the input bandwidth usage alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 95 and lower threshold to 80 for input bandwidth usage alarms.

<Sysname> system-view

[Sysname] ifmonitor input-usage slot 1 high-threshold 95 low-threshold 80

Related commands

flow-interval

snmp-agent trap enable ifmonitor

ifmonitor output-error

Use ifmonitor output-error to configure global output error packet alarm parameters.

Use undo ifmonitor output-error to restore the default.

NOTE:

This command is supported only in R3608 and later.

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 a card by its slot number.

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for output error packet alarms.

<Sysname> system-view

[Sysname] ifmonitor output-error slot 1 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.

NOTE:

This command is supported only in R3608 and later.

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 a card by its slot number.

Usage guidelines

With the output bandwidth usage alarm function enabled, when the output bandwidth usage on an interface in normal state within the most recent statistics polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the output bandwidth usage on an interface in the alarm state within the most recent statistics polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.

You can use the flow-interval command to set the statistics polling interval.

You can configure the output bandwidth usage alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the output bandwidth usage alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 80 and lower threshold to 60 for output bandwidth usage alarms.

<Sysname> system-view

[Sysname] ifmonitor output-usage slot 1 high-threshold 80 low-threshold 60

Related commands

flow-interval

snmp-agent trap enable ifmonitor

ifmonitor runt

Use ifmonitor runt to configure global runt packet alarm parameters.

Use undo ifmonitor runt to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

ifmonitor runt slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor runt 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 runt packet alarms.

Views

System view

Predefined user roles

network-admin

Parameters

high-threshold high-value: Specifies the upper threshold for runt packet alarms, in the range of 1 to 4294967295 packets.

low-threshold low-value: Specifies the lower threshold for runt packet alarms, in the range of 1 to 4294967295 packets.

interval interval: Specifies the statistics collection and comparison interval for runt packets, in the range of 1 to 65535 seconds.

shutdown: Shuts down an interface when the number of incoming runt 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.

slot slot-number: Specifies a card by its slot number.

Usage guidelines

With the runt packet alarm function enabled, when the number of incoming runt 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 runt 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 runt packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for runt packet alarms.

<Sysname> system-view

[Sysname] ifmonitor runt slot 1 high-threshold 5 low-threshold 4 interval 6

Related commands

port ifmonitor runt

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.

NOTE:

This command is supported only in R3608 and later.

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 a card by its slot number.

Usage guidelines

With the received pause frame alarm function enabled, when the number of received pause frames on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of received pause frames on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.

You can configure the received pause frame alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the received pause frame alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 30, lower threshold to 20, and statistics collection and comparison interval to 4 seconds for received pause frame alarms.

<Sysname> system-view

[Sysname] ifmonitor rx-pause slot 1 high-threshold 30 low-threshold 20 interval 4

Related commands

snmp-agent trap enable ifmonitor

ifmonitor sdh-b1-error

Use ifmonitor sdh-b1-error to configure global SDH-B1 error packet alarm parameters.

Use undo ifmonitor sdh-b1-error to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

ifmonitor sdh-b1-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor sdh-b1-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 SDH-B1 error packet alarms.

Views

System 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.

slot slot-number: Specifies a card by its slot number.

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the 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 65, lower threshold to 25, and statistics collection and comparison interval to 20 seconds for SDH-B1 error packet alarms.

<Sysname> system-view

[Sysname] ifmonitor sdh-b1-error slot 1 high-threshold 65 low-threshold 25 interval 20

Related commands

snmp-agent trap enable ifmonitor

ifmonitor sdh-b2-error

Use ifmonitor sdh-b2-error to configure global SDH-B2 error packet alarm parameters.

Use undo ifmonitor sdh-b2-error to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

ifmonitor sdh-b2-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor sdh-b2-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 SDH-B2 error packet alarms.

Views

System 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.

slot slot-number: Specifies a card by its slot number.

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the 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 6, lower threshold to 5, and statistics collection and comparison interval to 2 seconds for SDH-B2 error packet alarms.

<Sysname> system-view

[Sysname] ifmonitor sdh-b2-error slot 1 high-threshold 6 low-threshold 5 interval 2

Related commands

snmp-agent trap enable ifmonitor

ifmonitor sdh-error

Use ifmonitor sdh-error to configure global SDH error packet alarm parameters.

Use undo ifmonitor sdh-error to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

ifmonitor sdh-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor sdh-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 SDH error packet alarms.

Views

System 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.

slot slot-number: Specifies a card by its slot number.

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the SDH error packet alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 35, lower threshold to 20, and statistics collection and comparison interval to 8 seconds for SDH error packet alarms.

<Sysname> system-view

[Sysname] ifmonitor sdh-error slot 1 high-threshold 35 low-threshold 20 interval 8

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.

NOTE:

This command is supported only in R3608 and later.

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 a card by its slot number.

Usage guidelines

With the sent pause frame alarm function enabled, when the number of sent pause frames on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of sent pause frames on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.

You can configure the sent pause frame alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the sent pause frame alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 20, lower threshold to 10, and statistics collection and comparison interval to 5 seconds for sent pause frame alarms.

<Sysname> system-view

[Sysname] ifmonitor tx-pause slot 1 high-threshold 20 low-threshold 10 interval 5

Related commands

snmp-agent trap enable ifmonitor

interface

Use interface to enter interface view, create a subinterface and enter its view, or enter the view of an existing subinterface.

Syntax

interface interface-type { interface-number | interface-number.subnumber }

Views

System view

Predefined user roles

network-admin

Parameters

interface-type: Specifies an interface type.

interface-number: Specifies an interface number.

Usage guidelines

After creating a Layer 3 Ethernet subinterface on a device operating in enhanced Layer 2 mode, for the subinterface to forward traffic, you must use the vlan-type dot1q vid vlan-id command to configure VLAN termination on it. Make sure the value for the vlan-id argument is the same as the subinterface number. For more information about system operating mode, see device management in Fundamentals Configuration Guide.

Examples

# Enter the view of Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1]

# Create Ethernet subinterface Ten-GigabitEthernet 1/0/1.1 and enter its view.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1.1

[Sysname-Ten-GigabitEthernet1/0/1.1]

Related commands

vlan-type dot1q vid (Layer 2—LAN Switching Command Reference)

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 12288 bytes to pass through.

Views

Layer 2 Ethernet interface view

Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

size: Sets the maximum length (in bytes) of Ethernet frames that are allowed to pass through. The value range for this argument is 1536 to 12288.

Usage guidelines

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Allow jumbo frames to pass through Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] jumboframe enable

link-delay

Use link-delay to set the physical state change suppression interval on an Ethernet interface.

Use undo link-delay to restore the default.

Syntax

link-delay { down | up } [ msec ] delay-time

undo link-delay { down | up }

Default

Physical state change suppression is not configured.

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 is in seconds and the value range is 0 to 30.

· If you specify the msec keyword, the value range is 0 to 10000 milliseconds, and the value must be a multiple of 10.

Usage guidelines

You can configure this feature to suppress only link-down events, only link-up events, or both. If an event of the specified type still exists when the suppression interval expires, the system reports the event.

When you configure this feature, follow these guidelines:

· To suppress link-down events, configure the link-delay down command.

· To suppress link-up events, configure 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 with RRPP, spanning tree protocols, or Smart Link enabled.

Examples

# Set the link-down event suppression interval to 8 seconds on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] link-delay down 8

# Set the link-up event suppression interval to 800 milliseconds on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] link-delay up msec 800

linkdown trap enable shutdown

Use linkdown trap enable shutdown to enable the function of generating LinkDown notifications upon interface shutdown.

Use undo linkdown trap enable shutdown to disable the function of generating LinkDown notifications upon interface shutdown.

Syntax

linkdown trap enable shutdown

undo linkdown trap enable shutdown

Default

The function of generating LinkDown notifications upon interface shutdown is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

With the snmp-agent trap enable standard linkdown command executed in system view and the enable snmp trap updown command executed in interface view, the device sends a LinkUp notification when an interface comes up and sends a LinkDown notification when an interface goes down. Because an interface might go down for various reasons, you can use this command to enable or disable the function of generating LinkDown notifications when an interface is shut down and enters the ADM state.

The generated notifications are sent to the SNMP module, and the SNMP module can output the notifications to an NMS.

Examples

# Disable the function of generating LinkDown notifications upon interface shutdown.

<Sysname> system-view

[Sysname] undo linkdown trap enable shutdown

Related commands

enable snmp trap updown (Network Management and Monitoring Command Reference)

snmp-agent trap enable standard (Network Management and Monitoring Command Reference)

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 { external | internal }

undo loopback

Default

Loopback testing is disabled on an Ethernet interface.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

external: Enables external loopback testing on the Ethernet interface.

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 Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/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.

When you configure the suppression threshold in kbps, the actual suppression threshold might be different from the configured one as follows:

· If the configured value is smaller than 64, the value of 64 takes effect.

· If the configured value is greater than 64 but not an integer multiple of 64, the integer multiple of 64 that is greater than and closest to the configured value takes effect.

For the suppression threshold that takes effect, see the prompt on the device.

Examples

# Set the multicast storm suppression threshold to 10000 kbps on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] multicast-suppression kbps 10000

The actual value is 10048 on port Ten-GigabitEthernet1/0/1 currently.

The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.

Related commands

broadcast-suppression

unicast-suppression

port fec mode

Use port fec mode to set the forward error correction (FEC) mode of an interface.

Use undo port fec mode to restore the default.

Syntax

port fec mode { auto | none | rs-fec }

undo port fec mode

Default

The FEC mode of an interface is autonegotiated.

Views

100-GE interface view

Predefined user roles

network-admin

Parameters

auto: Specifies the FEC autonegotiation mode.

none: Performs no FEC.

rs-fec: Specifies the RS-FEC mode.

Usage guidelines

The FEC feature corrects packet errors to improve transmission quality. It attaches correction information to a packet at the sending end, and corrects error codes generated during transmission at the receiving end based on the correction information. You can set the FEC mode as needed.

Make sure you set the same FEC mode for both interfaces of a link.

Examples

# Set the FEC mode of HundredGigE 1/0/1 to autonegotiation.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port fec mode auto

port ifmonitor crc-error

Use port ifmonitor crc-error to configure CRC error packet alarm parameters for an interface.

Use undo port ifmonitor crc-error to restore the default.

NOTE:

This command is supported only in R3608 and later.

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

context-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.

Usage guidelines

You can configure the CRC error packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for CRC error packet alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port ifmonitor crc-error high-threshold 5000 low-threshold 400 interval 6

Related commands

snmp-agent trap enable ifmonitor

port ifmonitor giant

Use port ifmonitor giant to configure giant packet alarm parameters for an interface.

Use undo port ifmonitor giant to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

port ifmonitor giant high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo port ifmonitor giant

Default

An interface uses the global giant packet alarm parameters.

Views

Ethernet interface view

Predefined user roles

network-admin

context-admin

Parameters

high-threshold high-value: Specifies the upper threshold for giant packet alarms, in the range of 1 to 4294967295.

low-threshold low-value: Specifies the lower threshold for giant packet alarms, in the range of 1 to 4294967295.

interval interval: Specifies the statistics collection and comparison interval for giant packets, in the range of 1 to 65535 seconds.

Usage guidelines

You can configure the giant packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for giant packet alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port ifmonitor giant high-threshold 5 low-threshold 4 interval 6

Related commands

ifmonitor giant

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.

NOTE:

This command is supported only in R3608 and later.

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

context-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.

Usage guidelines

You can configure the input error packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for input error packet alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/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.

NOTE:

This command is supported only in R3608 and later.

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

Ethernet interface view

Predefined user roles

network-admin

context-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

You can use the flow-interval command to set the statistics polling interval.

You can configure the input bandwidth usage alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the input bandwidth usage alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 80 and lower threshold to 60 for input bandwidth usage alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port ifmonitor input-usage high-threshold 80 low-threshold 60

Related commands

flow-interval

snmp-agent trap enable ifmonitor

port ifmonitor output-error

Use port ifmonitor output-error to configure output error packet alarm parameters for an interface.

Use undo port ifmonitor output-error to restore the default.

NOTE:

This command is supported only in R3608 and later.

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

context-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.

Usage guidelines

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for output error packet alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/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.

NOTE:

This command is supported only in R3608 and later.

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

Ethernet interface view

Predefined user roles

network-admin

context-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

You can use the flow-interval command to set the statistics polling interval.

You can configure the output bandwidth usage alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the output bandwidth usage alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 9 and lower threshold to 7 for output bandwidth usage alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port ifmonitor output-usage high-threshold 9 low-threshold 7

Related commands

flow-interval

snmp-agent trap enable ifmonitor

port ifmonitor runt

Use port ifmonitor runt to configure runt packet alarm parameters for an interface.

Use undo port ifmonitor runt to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

port ifmonitor runt high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo port ifmonitor runt

Default

An interface uses the global runt packet alarm parameters.

Views

Ethernet interface view

Predefined user roles

network-admin

context-admin

Parameters

high-threshold high-value: Specifies the upper threshold for runt packet alarms, in the range of 1 to 4294967295.

low-threshold low-value: Specifies the lower threshold for runt packet alarms, in the range of 1 to 4294967295.

interval interval: Specifies the statistics collection and comparison interval for runt packets, in the range of 1 to 65535 seconds.

Usage guidelines

You can configure the runt packet alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for runt packet alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port ifmonitor runt high-threshold 5 low-threshold 4 interval 6

Related commands

ifmonitor runt

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.

NOTE:

This command is supported only in R3608 and later.

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

context-admin

Parameters

high-threshold high-value: Specifies the upper threshold for received pause frame alarms, in the range of 1 to 4294967295.

low-threshold low-value: Specifies the lower threshold for received pause frame alarms, in the range of 1 to 4294967295.

interval interval: Specifies the statistics collection and comparison interval for received pause frame packets, in the range of 1 to 65535 seconds.

Usage guidelines

With the received pause frame alarm function enabled, when the number of received pause frame packets on an interface in normal state within the specified interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the number of received pause frame packets on an interface in the alarm state within the specified interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.

You can configure the received pause frame alarm parameters in system view and interface view.

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the received pause frame alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 90, lower threshold to 50, and statistics collection and comparison interval to 5 seconds for received pause frame alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port ifmonitor rx-pause high-threshold 90 low-threshold 50 interval 5

Related commands

snmp-agent trap enable ifmonitor

port ifmonitor 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.

NOTE:

This command is supported only in R3608 and later.

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

context-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.

Usage guidelines

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the 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 HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/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.

NOTE:

This command is supported only in R3608 and later.

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

context-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.

Usage guidelines

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the 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 HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/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.

NOTE:

This command is supported only in R3608 and later.

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

context-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.

Usage guidelines

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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the 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 HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/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.

NOTE:

This command is supported only in R3608 and later.

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

context-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 of the specified slot. The configuration in interface view takes effect only on the current interface.

· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.

For this command to take effect, you must use the snmp-agent trap enable ifmonitor command to enable the sent pause frame alarm function.

When you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the upper threshold to 50, lower threshold to 40, and statistics collection and comparison interval to 8 seconds for sent pause frame alarms on HundredGigE 1/0/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] port ifmonitor tx-pause high-threshold 50 low-threshold 40 interval 8

Related commands

snmp-agent trap enable ifmonitor

port link-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 Ethernet 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 shutdown) 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 or route for these Ethernet interfaces.

Before switching the link mode or executing the default command for an Ethernet interface, first delete all settings of the interface to ensure successful link mode switchover.

Examples

# Configure Ten-GigabitEthernet 1/0/1 to operate in Layer 2 mode.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] port link-mode bridge

Related commands

default

priority-flow-control (Ethernet interface view)

Use priority-flow-control to enable PFC in auto mode or forcibly.

Use undo priority-flow-control to disable PFC.

Syntax

priority-flow-control { auto | enable }

undo priority-flow-control

Default

PFC is disabled on Ethernet interfaces.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

auto: Specifies PFC in auto mode. In this mode, the local end automatically negotiates the PFC status with its peer.

enable: Forcibly enables PFC.

Usage guidelines

The local device notifies the remote end to stop sending packets carrying the specified 802.1p priority if all of the following conditions exist:

· Both the local end and the remote end have PFC enabled.

· Both the local end and the remote end have the priority-flow-control no-drop dot1p command configured.

· The specified 802.1p priority is in the 802.1p priority list specified by the dot1p-list argument.

· The local end receives packets carrying the specified 802.1p priority, and the received packets cause congestion.

When congestion is eliminated, the local end notifies the remote end to continue to send packets carrying the specified 802.1p priority. In this way, the local device can forward packets carrying 802.1p priorities in the specified 802.1p priority list without packet drops.

You can configure PFC in both system view and Ethernet interface view. If you configure PFC in system view, PFC is issued to all interfaces. If you configure PFC in system view and Ethernet interface view multiple times, the most recent configuration takes effect.

Examples

# Enable PFC on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control enable

Related commands

display priority-flow-control

priority-flow-control (system view)

priority-flow-control no-drop dot1p

priority-flow-control (system view)

Use priority-flow-control to enable PFC on all Ethernet interfaces.

Use undo priority-flow-control to disable PFC on all Ethernet interfaces.

Syntax

priority-flow-control { auto | enable }

undo priority-flow-control

Default

PFC is disabled on Ethernet interfaces.

Views

System view

Predefined user roles

network-admin

Parameters

auto: Specifies PFC in auto mode. In this mode, the local end automatically negotiates the PFC status with the remote end.

enable: Forcibly enables PFC.

Usage guidelines

The local device notifies the remote end to stop sending packets carrying the specified 802.1p priority if all of the following conditions exist:

· Both the local end and the remote end have PFC enabled.

· Both the local end and the remote end have the priority-flow-control no-drop dot1p command configured.

· The specified 802.1p priority is in the 802.1p priority list specified by the dot1p-list argument.

· The local end receives packets carrying the specified 802.1p priority, and the received packets cause congestion.

Examples

# Enable PFC on all Ethernet interfaces.

<Sysname> system-view

[Sysname] priority-flow-control enable

Related commands

display priority-flow-control

priority-flow-control (Ethernet interface view)

priority-flow-control no-drop dot1p

priority-flow-control deadlock auto-recover action

Use priority-flow-control deadlock auto-recover action to configure the action to take on packets during the delay timer period for PFC deadlock detection recovery.

Use undo priority-flow-control deadlock auto-recover action to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock auto-recover action { discard | forwarding }

undo priority-flow-control deadlock auto-recover action

Default

The device forwards received data packets.

Views

System view

Predefined user roles

network-admin

Parameters

discard: Drops the received data packets.

forwarding: Forwards the received data packets.

Usage guidelines

This command cannot be executed when the device is in PFC deadlock status.

Examples

# Configure the device to drop received data packets during the delay timer period for PFC deadlock detection automatic recovery.

<Sysname> system-view

[Sysname] priority-flow-control deadlock auto-recover action discard

Related commands

priority-flow-control deadlock cos

priority-flow-control deadlock enable

priority-flow-control deadlock auto-recover cos

Use priority-flow-control deadlock auto-recover cos to configure the delay timer for PFC deadlock detection automatic recovery.

Use undo priority-flow-control deadlock auto-recover cos to delete the delay timer for PFC deadlock detection automatic recovery.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock auto-recover slot slot-number cos cos-value delay delay-interval

undo priority-flow-control deadlock auto-recover slot slot-number cos [ cos-value ]

Default

The delay timer for PFC deadlock detection automatic recovery is not configured.

Views

System view

Predefined user roles

network-admin

Parameters

cos cos-value: Specifies the CoS value of packets, in the range of 0 to 7. Different CoS values correspond to different 802.1p priority values. To see the CoS-to-802.1p mapping, execute the display qos map-table dot1p-lp command.

delay delay-time: Specifies the delay timer for PFC deadlock detection automatic recovery, in the range of 0 to 15.

slot slot-number: Specifies a card by its slot number, which is fixed at 1.

Usage guidelines

PFC deadlock detection periodically detects whether deadlock occurs to packets carrying the specified CoS value. If the device enters the PFC deadlock state and PFC deadlock detection is recovered in automatic mode, the device automatically recovers PFC deadlock detection after the delay timer expires. The delay timer is determined by this command and the PFC deadlock detection timer precision.

This command takes effect only in automatic recovery mode. This command cannot be executed when the device is in PFC deadlock status.

The specified CoS value must be within the 802.1p priority values configured by using the priority-flow-control no-drop dot1p command.

You can set the same delay timer for different CoS values.

If you execute this command multiple times for the same CoS value, the most recent configuration takes effect.

Examples

# Set the delay timer for PFC deadlock detection automatic recovery to 5 for packets carrying CoS value 7.

<Sysname> system-view

[Sysname] priority-flow-control deadlock auto-recover slot 1 cos 7 delay 5

Related commands

display qos map-table dot1p-lp (ACL and QoS Command Reference)

priority-flow-control deadlock precision

priority-flow-control no-drop dot1p

priority-flow-control deadlock cos

Use priority-flow-control deadlock cos to set the PFC deadlock detection interval for the specified CoS value.

Use undo priority-flow-control deadlock cos to delete the PFC deadlock detection interval for the specified CoS value or all CoS values.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock slot slot-number cos cos-value interval interval

undo priority-flow-control deadlock slot slot-number cos [ cos-value ]

Default

The PFC deadlock detection interval for a CoS value is not set.

Views

System view

Predefined user roles

network-admin

Parameters

cos cos-value: Specifies the CoS value of packets, in the range of 0 to 7.

interval interval: Specifies the PFC deadlock detection interval in the range of 1 to 15.

slot slot-number: Specifies a card by its slot number, which is fixed at 1.

Usage guidelines

The PFC deadlock detection feature periodically detects whether deadlock occurs to packets that carry the specified CoS value. To obtain the length of time for the detection interval, multiply the detection interval by the precision of the PFC deadlock detection timer.

The specified CoS value must be within the 802.1p priority list specified by using the priority-flow-control no-drop dot1p command. To view the 802.1p priority for each CoS value, execute the display qos map-table dot1p-lp command.

You can set the same detection interval for different CoS values.

If you execute this command for the same CoS value multiple times, the most recent configuration takes effect.

This command cannot be executed when the device is in PFC deadlock status.

Examples

# Set the PFC deadlock detection interval to 5 for packets carrying CoS value 7 on slot 1.

<Sysname> system-view

[Sysname] priority-flow-control deadlock slot 1 cos 7 interval 5

Related commands

display qos map-table dot1p-lp (ACL and QoS Command Reference)

priority-flow-control deadlock precision

priority-flow-control no-drop dot1p

priority-flow-control deadlock enable

Use priority-flow-control deadlock enable to enable PFC deadlock detection on an interface.

Use undo priority-flow-control deadlock enable to disable PFC deadlock detection on an interface.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock enable

undo priority-flow-control deadlock enable

Default

PFC deadlock detection is disabled on an interface.

Views

Ethernet interface view

Predefined user roles

network-admin

Usage guidelines

The device enters the PFC deadlock state if the following conditions exist on an interface:

· PFC for 802.1p priorities is enabled by using the priority-flow-control and priority-flow-control no-drop dot1p commands.

· Packets carrying the specified 802.1p priority are transmitted in a loop.

· No packets in the data buffer can be forwarded.

This command enables periodically detecting whether the device is in PFC deadlock state.

This command cannot be executed when the device is in PFC deadlock status.

Examples

# Enable PFC deadlock detection on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control deadlock enable

Related commands

priority-flow-control

priority-flow-control deadlock cos

priority-flow-control no-drop dot1p

priority-flow-control deadlock precision

Use priority-flow-control deadlock precision to set the precision for the PFC deadlock detection timer.

Use undo priority-flow-control deadlock precision to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock slot slot-number precision { high | low | normal }

undo priority-flow-control deadlock slot slot-number precision

Default

The PFC deadlock detection timer uses normal precision.

Views

System view

Predefined user roles

network-admin

Parameters

high: Specifies the high precision for the PFC deadlock detection timer, which represents one second.

low: Specifies the low precision for the PFC deadlock detection timer, which represents three seconds.

normal: Specifies the normal precision for the PFC deadlock detection timer, which represents two seconds.

slot slot-number: Specifies a card by its slot number, which is fixed at 1.

Usage guidelines

Use this command to adjust the precision for the PFC deadlock detection timer and change the PFC deadlock detection interval.

If you execute this command multiple times, the most recent configuration takes effect.

This command cannot be executed when the device is in PFC deadlock status.

Examples

# Set the high precision for the PFC deadlock detection timer on slot 1.

<Sysname> system-view

[Sysname] priority-flow-control deadlock slot 1 precision high

priority-flow-control deadlock recover

Use priority-flow-control deadlock recover to recover PFC deadlock detection on an interface.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock recover

Views

Ethernet interface view

Predefined user roles

network-admin

Usage guidelines

Before executing this command, you must use the priority-flow-control deadlock recover-mode command to set the recovery mode for PFC deadlock detection.

The device can automatically release the deadlock state, but both the PFC deadlock detection and PFC features are disabled on the interface at the same time. To manually recover PFC deadlock detection on the interface, execute this command after setting the manual recovery mode for PFC deadlock detection on the interface. The PFC feature is also enabled again when you execute this command.

This command cannot be executed when the device is in PFC deadlock status.

Examples

# Recover PFC deadlock detection on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control deadlock recover

Related commands

priority-flow-control deadlock recover-mode

Use priority-flow-control deadlock recover-mode to set the recovery mode for PFC deadlock detection on an interface.

Use undo priority-flow-control deadlock recover-mode to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock recover-mode { auto | manual }

undo priority-flow-control deadlock recover-mode

Default

PFC deadlock detection recovers in automatic mode on an interface.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

auto: Specifies the automatic recovery mode.

manual: Specifies the manual recovery mode.

Usage guidelines

When the PFC deadlock state is detected and PFC deadlock detection is recovered in automatic mode, the device automatically releases the deadlock state and recovers PFC and PFC deadlock detection after the delay timer expires. Within the delay timer period, the device disables PFC and PFC deadlock detection on the interface, so that packets can be forwarded properly. PFC deadlock detection can be recovered in automatic or manual mode on the interface. Recovering this feature enables the PFC feature again at the same time. Use the automatic recovery mode when no serious failures occur.

When a packet loop cannot be resolved and the device enters the PFC deadlock state frequently, manually recover PFC deadlock detection on the interface as follows:

1. Perform troubleshooting and set the manual recovery mode for PFC deadlock detection.

2. Execute the priority-flow-control deadlock recover command to recover the PFC deadlock detection and PFC features.

This command cannot be executed when the device is in PFC deadlock status.

Examples

# Set the manual recovery mode for PFC deadlock detection on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control deadlock recover-mode manual

Related commands

priority-flow-control deadlock recover

priority-flow-control deadlock threshold

Use priority-flow-control deadlock threshold to configure the upper threshold for PFC deadlock times within the specified period.

Use undo priority-flow-control deadlock threshold to restore the default.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control deadlock threshold slot slot-number cos cos-value period period count count

undo priority-flow-control deadlock threshold slot slot-number cos [ cos-value ]

Default

The upper threshold for PFC deadlock times within the specified period is not configured.

Views

System view

Predefined user roles

network-admin

Parameters

period period: Specifies the period for detecting PFC deadlock times, in the range of 1 to 60 seconds.

count count: Specifies the upper threshold for PFC deadlock times within the specified period, in the range of 1 to 500.

slot slot-number: Specifies a card by its slot number.

Usage guidelines

With this command configured, when the PFC deadlock times within the specified period exceed the upper threshold on an interface, the device disables PFC for all 802.1p priority values on the interface. To recover the PFC feature on the interface in this case, execute the undo priority-flow-control deadlock threshold command.

The detection period specified in this command must be longer than the PFC deadlock detection interval configured by using the priority-flow-control deadlock cos command, so that you can determine whether the device frequently enters the PFC deadlock state.

This command cannot be executed when the device is in PFC deadlock status.

The specified CoS value must be within the 802.1p priority values configured by using the priority-flow-control no-drop dot1p command.

You can set the same detection period for different CoS values.

If you execute this command multiple times for the same CoS value, the most recent configuration takes effect.

Examples

# Set the upper threshold for PFC deadlock times to 100 within the period of 5 seconds.

<Sysname> system-view

[Sysname] priority-flow-control deadlock threshold slot 1 cos 7 period 5 count 100

Related commands

priority-flow-control deadlock cos

priority-flow-control no-drop dot1p

priority-flow-control early-warning inpps

Use priority-flow-control early-warning inpps to configure the early warning threshold for incoming PFC packets.

Use undo priority-flow-control early-warning inpps to delete the early warning threshold for incoming PFC packets.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control early-warning dot1p dot1p-list inpps pps-value

undo priority-flow-control early-warning [ dot1p dot1p-list ] inpps

Default

No early warning threshold is configured for incoming PFC packets.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

dot1p-list: Specifies an 802.1p priority (or dot1p priority) list to identify flows that are subject to PFC (for example: 1,3-5). A hyphen (-) connects two numeric values, which together indicate a continuous value range. Different values or value ranges are separated with commas (,). You can configure up to 16 characters for this argument.

inpps pps-value: Specifies the number of PFC frames that an interface can receive in pps. The value range for this argument is 1 to 159783010.

Usage guidelines

You can configure the early warning threshold for incoming or outgoing PFC packets of an interface as needed. The early warning threshold notifies a situation where the PFC packet transmission rate is still within a normal range but needs attention.

When the rate of PFC packets that an interface sends or receives reaches the early warning threshold, the system generates traps and logs to notify the user. According to the traps and logs, the user can discover some exceptions in the network, for example:

· The NIC of the peer device fails and continuously sends PFC packets at a high speed. In this case, you can set the early warning threshold for incoming PFC packets.

· The device fails and continuously sends PFC frames. In this case, you can set the early warning threshold for outgoing PFC packets.

To monitor bidirectional PFC packets, you can set the early warning thresholds for incoming packets and outgoing packets separately.

The number of PFC pause frames that an interface receives is counted and the early warning threshold configuration takes effect only when PFC is enabled.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the early warning threshold to 80 pps for incoming PFC packets with 802.1p priority value 7 on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control early-warning dot1p 7 inpps 80

priority-flow-control early-warning outpps

Use priority-flow-control early-warning outpps to configure the early warning threshold for outgoing PFC packets.

Use undo priority-flow-control early-warning outpps to delete the early warning threshold for outgoing PFC packets.

NOTE:

This command is supported only in R3608 and later.

Syntax

priority-flow-control early-warning dot1p dot1p-list outpps pps-value

undo priority-flow-control early-warning [ dot1p dot1p-list ] outpps

Default

No early warning threshold is configured for outgoing PFC packets.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

outpps pps-value: Specifies the number of PFC frames that an interface can send in pps. The value range for this argument is 1 to 159783010.

Usage guidelines

· The NIC of the peer device fails and continuously sends PFC packets at a high speed. In this case, you can set the early warning threshold for incoming PFC packets.

· The device fails and continuously sends PFC frames. In this case, you can set the early warning threshold for outgoing PFC packets.

To monitor bidirectional PFC packets, you can set the early warning thresholds for incoming packets and outgoing packets separately.

The number of PFC pause frames that an interface sends is counted and the early warning threshold configuration takes effect only when PFC is enabled.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the early warning threshold to 50 pps for outgoing PFC packets with 802.1p priority value 1 on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control early-warning dot1p 1 outpps 50

priority-flow-control no-drop dot1p (Ethernet interface view)

Use priority-flow-control no-drop dot1p to enable PFC for 802.1p priorities.

Use undo priority-flow-control no-drop dot1p to disable PFC for the specified 802.1p priority.

Syntax

priority-flow-control no-drop dot1p dot1p-list

undo priority-flow-control no-drop dot1p

Default

PFC is disabled for all 802.1p priorities.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

Usage guidelines

The local device notifies the remote end to stop sending packets carrying the specified 802.1p priority if all of the following conditions exist:

· Both the local end and the remote end have PFC enabled.

· Both the local end and the remote end have the priority-flow-control no-drop dot1p command configured.

· The specified 802.1p priority is in the 802.1p priority list specified by the dot1p-list argument.

· The local end receives packets carrying the specified 802.1p priority, and the received packets cause congestion.

This command is mutually exclusive with the flow-control or flow-control receive enable command.

Examples

# Enable PFC in auto mode on Ten-GigabitEthernet 1/0/1, and enable PFC for 802.1p priority 5.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control auto

[Sysname-Ten-GigabitEthernet1/0/1] priority-flow-control no-drop dot1p 5

Related commands

display priority-flow-control

flow-control

flow-control receive enable

priority-flow-control

priority-flow-control no-drop dot1p (system view)

Use priority-flow-control no-drop dot1p to enable PFC for 802.1p priorities on all Ethernet interfaces.

Use undo priority-flow-control no-drop dot1p to disable PFC for 802.1p priorities on all Ethernet interfaces.

Syntax

priority-flow-control no-drop dot1p dot1p-list

undo priority-flow-control no-drop dot1p

Default

PFC is disabled for all 802.1p priorities on all Ethernet interfaces.

Views

System view

Predefined user roles

network-admin

Parameters

Usage guidelines

The local device notifies the remote end to stop sending packets carrying the specified 802.1p priority if all of the following conditions exist:

· Both the local end and the remote end have PFC enabled.

· Both the local end and the remote end have the priority-flow-control no-drop dot1p command configured.

· The specified 802.1p priority is in the 802.1p priority list specified by the dot1p-list argument.

· The local end receives packets carrying the specified 802.1p priority, and the received packets cause congestion.

Examples

# Enable PFC for 802.1p priority 5 globally.

<Sysname> system-view

[Sysname] priority-flow-control no-drop dot1p 5

Related commands

display priority-flow-control

priority-flow-control

priority-flow-control no-drop dot1p (Ethernet interface view)

reset counters interface

Use reset counters interface to clear the interface statistics.

Syntax

reset counters interface [ interface-type [ interface-number | interface-number.subnumber ] ]

Views

User view

Predefined user roles

network-admin

Parameters

interface-type: Specifies an interface type.

interface-number: Specifies an interface number.

Usage guidelines

Use this command to clear history statistics if you want to collect traffic statistics for a specific time period.

If you do not specify an interface type, this command clears statistics for all interfaces.

If you specify an interface type but do not specify an interface number, this command clears statistics for all interfaces of the specified type.

Examples

# Clear the statistics for Ten-GigabitEthernet 1/0/1.

<Sysname> reset counters interface ten-gigabitethernet 1/0/1

Related commands

display counters interface

display counters rate interface

display interface

reset ethernet statistics

Use reset ethernet statistics to clear the Ethernet module statistics.

Syntax

reset ethernet statistics [ slot slot-number ]

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies 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 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. If you do not specify an interface type, this command clears dropped packet statistics for all interfaces on the device.

interface-number: Specify an interface number. If you do not specify this argument, the command clears dropped packet statistics for all interfaces of the specified type.

Examples

# Clear dropped packet statistics for Ten-GigabitEthernet 1/0/1.

<Sysname> reset packet-drop interface ten-gigabitethernet 1/0/1

# Clear dropped packet statistics for all interfaces.

<Sysname> reset packet-drop interface

Related commands

display packet-drop

shutdown

Use shutdown to shut down an Ethernet interface or subinterface.

Use undo shutdown to bring up an Ethernet interface or subinterface.

Syntax

shutdown

undo shutdown

Default

An Ethernet interface or subinterface is down.

Views

Ethernet interface view

Ethernet subinterface view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

Executing the shutdown command on an interface will disconnect the link of the interface and interrupt communication. Use this command with caution.

Some interface configurations might require an interface restart before taking effect.

The shutdown, port up-mode, and loopback commands are mutually exclusive.

Examples

# Shut down and then bring up Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] shutdown

[Sysname-Ten-GigabitEthernet1/0/1] undo shutdown

# Shut down and then bring up Ten-GigabitEthernet 1/0/1.1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1.1

[Sysname-Ten-GigabitEthernet1/0/1.1] shutdown

[Sysname-Ten-GigabitEthernet1/0/1.1] undo shutdown

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.

NOTE:

This command is supported only in R3608 and later.

Syntax

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.

giant: Enables the giant 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.

runt: Enables the runt packet alarm function for interfaces.

rx-pause: Enables the received pause frame alarm function for interfaces.

sdh-b1-error: Enables the SDH-B1 error packet alarm function for interfaces.

sdh-b2-error: Enables the SDH-B2 error packet alarm function for interfaces.

sdh-error: Enables the SDH error packet alarm function for interfaces.

tx-pause: Enables the sent pause frame alarm function for interfaces.

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 { 10 | 100 | 1000 | 10000 | 40000 | 100000 | auto }

undo speed

Default

The speed of an Ethernet interface is autonegotiated.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

10: Sets the interface speed to 10 Mbps.

100: Sets the interface speed to 100 Mbps.

1000: Sets the interface speed to 1000 Mbps.

10000: Sets the interface speed to 10000 Mbps.

40000: Sets the interface speed to 40000 Mbps.

100000: Sets the interface speed to 100000 Mbps.

auto: Enables the interface to negotiate a speed with its peer.

Usage guidelines

On an S6890-44HF switch, 10-GE interfaces numbered 37 through 40 do not support 1-Gbps transceiver modules.

For an Ethernet copper port, use the speed command to set its speed to match the speed of the peer interface. Support of copper ports for keywords of this command varies by copper port type. For more information, use the speed ? command in interface view. If the system does not prompt that operation failed when you configure a speed for a copper port, the copper port supports this speed. Otherwise, the copper port does not support this speed.

For a fiber port, use the speed command to set its speed to match the rate of a transceiver module. Support of fiber ports for keywords of this command varies by fiber port type. For more information, use the speed ? command in interface view. If the system does not prompt that operation failed when you configure a speed for a fiber port, the fiber port supports this speed. Otherwise, the fiber port does not support this speed.

Additionally, you must select a speed for a fiber port according to the transceiver module installed to ensure that the transceiver module can be used properly. If the transceiver module installed in a fiber port does not support the speed for the fiber port, the transceiver module cannot be used. For example, the transceiver module cannot be used if either of the following conditions exists:

· The transceiver module installed in an SFP+ fiber port is an SFP GE transceiver module and the speed 10000 command is executed on the fiber port.

· The transceiver module installed in an SFP+ fiber port is a 10-GE transceiver module and the speed 1000 command is executed on the fiber port.

Examples

# Configure Ten-GigabitEthernet 1/0/1 to autonegotiate the speed.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] speed auto

unicast-suppression

Use unicast-suppression to enable unknown unicast storm suppression and set the unknown unicast storm suppression threshold.

Use undo unicast-suppression to disable unknown unicast storm suppression.

Syntax

unicast-suppression { ratio | pps max-pps | kbps max-kbps }

undo unicast-suppression

Default

Ethernet interfaces do not suppress unknown unicast traffic.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

ratio: Sets the unknown unicast suppression threshold as a percentage of the interface bandwidth. The value range for this argument (in percentage) is 0 to 100. A smaller value means that less unknown unicast traffic is allowed to pass through.

pps max-pps: Specifies the maximum number of unknown unicast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.

kbps max-kbps: Specifies the maximum number of kilobits of unknown unicast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.

Usage guidelines

The unknown unicast storm suppression feature limits the size of unknown unicast traffic to a threshold on an interface. When the unknown unicast traffic on the interface exceeds this threshold, the system discards packets until the unknown unicast traffic drops below this threshold.

Both the storm-constrain command and the unicast-suppression command can suppress unknown unicast storms on a port. The unicast-suppression command uses the chip to physically suppress unknown unicast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress unknown unicast traffic.

For the unknown unicast traffic suppression result to be determined, do not configure both the storm-constrain unicast command and the unicast-suppression command on an interface.

When you configure the suppression threshold in kbps, the actual suppression threshold might be different from the configured one as follows:

· If the configured value is smaller than 64, the value of 64 takes effect.

· If the configured value is greater than 64 but not an integer multiple of 64, the integer multiple of 64 that is greater than and closest to the configured value takes effect.

For the suppression threshold that takes effect, see the prompt on the device.

Examples

# Set the unknown unicast storm suppression threshold to 10000 kbps on Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] unicast-suppression kbps 10000

The actual value is 10048 on port Ten-GigabitEthernet1/0/1 currently.

The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.

Related commands

broadcast-suppression

multicast-suppression

using hundredgige

Use using hundredgige to combine 10-GE breakout interfaces split from a 100-GE interface into a 100-GE interface.

NOTE:

This command is supported only in R3608 and later.

Syntax

using hundredgige

Default

The 10-GE breakout interfaces are not combined and operate as single interfaces.

Views

10-GE breakout interface view

Predefined user roles

network-admin

Usage guidelines

If you need higher bandwidth on a single interface, you can combine four 10-GE breakout interfaces split from a 100-GE interface into a 100-GE interface. To do so, execute this command on any of these 10-GE breakout interfaces.

After you execute this command, execute the display interface brief command to view the combined interfaces.

Examples

# Combine Ten-GigabitEthernet 1/0/1:1 through Ten-GigabitEthernet 1/0/1:10 into a 100-GE interface.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1:1

[Sysname-Ten-GigabitEthernet1/0/1:1]using hundredgige

The interfaces Ten-GigabitEthernet1/0/1:1 through Ten-GigabitEthernet1/0/1:10 will be deleted. Continue? [Y/N]:y

Related commands

using tengige

Use using tengige to split a high bandwidth interface into multiple 10-GE breakout interfaces.

NOTE:

This command is supported only in R3608 and later.

Syntax

using tengige

Default

A high bandwidth interface is not split and operates as a single interface.

Views

100-GE interface view

Predefined user roles

network-admin

Usage guidelines

To improve port density, reduce costs, and improve network flexibility, you can split a high bandwidth interface into multiple 10-GE breakout interfaces. For example, split a 100-GE interface HundredGigE 1/0/1 installed with a split-capable 40-GE transceiver module or cable into four 10-GE breakout interfaces Ten-GigabitEthernet 1/0/1:1 through Ten-GigabitEthernet 1/0/1:4.

The 10-GE breakout interfaces support the same configuration and attributes as common 10-GE interfaces, except that they are numbered in a different way.

After you execute this command, execute the display interface brief command to view the breakout interfaces.

Before a 100-GE interface on an S6890 switch is split, it supports eight queues numbered 0 through 7. After such a 100-GE interface is split, each breakout interface supports two queues and does not support PFC-related features.

Examples

# Split HundredGigE 1/0/1 into four 10-GE breakout interfaces.

<Sysname> system-view

[Sysname] interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1] using tengige

The interface HundredGigE1/0/1 will be deleted. Continue? [Y/N]:y

Related commands

using hundredgige

Layer 2 Ethernet interface commands

display storm-constrain

Use display storm-constrain to display storm control settings and statistics.

Syntax

display storm-constrain [ broadcast | multicast | unicast ] [ interface interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

broadcast: Displays broadcast storm control settings and statistics.

multicast: Displays multicast storm control settings and statistics.

unicast: Displays unknown unicast storm control settings and statistics.

interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify this option, the command displays storm control settings and statistics for all storm control-enabled interfaces.

Usage guidelines

If you do not specify any keywords, this command displays all storm control settings on all storm control-enabled interfaces.

Examples

# Display the storm control settings on all storm control-enabled ports.

<Sysname> display storm-constrain

Abbreviation: BC - broadcast; MC - multicast; UC - unicast

FW - forwarding

Flow Statistic Interval: 5 (in seconds)

Port Type Lower Upper Unit CtrlMode Status Trap Log StateChanges

--------------------------------------------------------------------------------

XGE1/0/1 MC 100 200 kbps shutdown shutdown off on 10

Table 9 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.
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.
StateChanges	Number of forwarding state changes of the interface. When the StateChanges field reaches 65535, it resets automatically.

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 Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] port up-mode

storm-constrain

Use storm-constrain to enable storm control and set thresholds for broadcast, multicast, or unknown unicast packets on an Ethernet interface.

Use undo storm-constrain to disable storm control for broadcast, multicast, unknown unicast, or all types of traffic.

Syntax

storm-constrain { broadcast | multicast | unicast } { pps | kbps | ratio } upperlimit lowerlimit

undo storm-constrain { all | broadcast | multicast | unicast }

Default

Traffic storm control is disabled.

Views

Layer 2 Ethernet interface view

Predefined user roles

network-admin

Parameters

all: Disables storm control for all types of traffic: broadcast, multicast, and unknown unicast.

broadcast: Enables or disables broadcast storm control.

multicast: Enables or disables multicast storm control.

unicast: Enables or disables unknown unicast storm control.

pps: Sets storm control thresholds in pps.

kbps: Sets storm control thresholds in kbps.

ratio: Sets storm control thresholds as a percentage of the transmission capacity of the interface.

upperlimit: Sets the upper threshold, in pps, kbps, or percentage.

· If you specify the pps keyword, the value range for the upperlimit argument is 1 to 1.4881 × the interface bandwidth.

· If you specify the kbps keyword, the value range for the upperlimit argument is 1 to the interface bandwidth.

· If you specify the ratio keyword, the value range for the upperlimit argument is 1 to 100.

lowerlimit: Sets the lower threshold, in pps, kbps, or percentage.

· If you specify the pps keyword, the value range for the lowerlimit argument is 1 to 1.4881 × the interface bandwidth.

· If you specify the kbps keyword, the value range for the lowerlimit argument is 1 to the interface bandwidth.

· If you specify the ratio keyword, the value range for the lowerlimit argument is 1 to 100.

Usage guidelines

After you configure storm control for a type of traffic, the device collects the statistics for the type of traffic at the interval configured by using the storm-constrain interval command. When the type of traffic exceeds its upper threshold, the interface takes an action configured by using the storm-constrain control command.

The storm-constrain, broadcast-suppression, multicast-suppression, and unicast-suppression commands can suppress storms on an interface. The broadcast-suppression, multicast-suppression, and unicast-suppression commands use the chip to physically suppress traffic. They have less influence on the device performance than the storm-constrain command, which uses software to suppress traffic.

For the traffic suppression result to be determined, do not configure both storm control and storm suppression for the same type of traffic.

When configuring this command, make sure upperlimit is greater than lowerlimit.

Examples

# Enable unknown unicast storm control on Ten-GigabitEthernet 1/0/1 and set the upper and lower thresholds to 200 pps and 150 pps, respectively.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] storm-constrain unicast pps 200 150

# Enable broadcast storm control on Ten-GigabitEthernet 1/0/2, and set the upper and lower thresholds to 2000 kbps and 1500 kbps, respectively.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/2

[Sysname-Ten-GigabitEthernet1/0/2] storm-constrain broadcast kbps 2000 1500

# Enable multicast storm control on Ten-GigabitEthernet 1/0/3, and set the upper and lower thresholds to 80% and 15%, respectively.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/3

[Sysname-Ten-GigabitEthernet1/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 Ten-GigabitEthernet 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 ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/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 Ten-GigabitEthernet 1/0/1 to output log messages when it detects storm control threshold events.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/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 Ten-GigabitEthernet 1/0/1 to send traps when it detects storm control threshold events.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] storm-constrain enable trap

storm-constrain interval

Use storm-constrain interval to set the traffic polling interval of the storm control module.

Use undo storm-constrain interval to restore the default.

Syntax

storm-constrain interval interval

undo storm-constrain interval

Default

The storm control module polls traffic statistics every 10 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Sets the traffic polling interval of the storm control module. The value range is 1 to 300 seconds. To ensure network stability, as a best practice, do not use a traffic polling interval shorter than 10 seconds.

Usage guidelines

The traffic polling interval set by using the storm-constrain interval command is specific to storm control. To set the statistics polling interval of an interface, use the flow-interval command.

Examples

# Set the traffic statistics polling interval of the storm control module to 60 seconds.

<Sysname> system-view

[Sysname] storm-constrain interval 60

Related commands

storm-constrain

storm-constrain control

Layer 3 Ethernet interface or subinterface commands

mac-address

Use mac-address to set the MAC address of an Ethernet interface.

Use undo mac-address to restore the default.

Syntax

mac-address mac-address

undo mac-address

Default

No MAC address is set for an Ethernet interface.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

mac-address: Specifies a MAC address in the format of H-H-H.

Usage guidelines

Do not set a VRRP-reserved MAC address for a Layer 3 Ethernet subinterface.

Examples

# Set the MAC address of Ten-GigabitEthernet 1/0/1 to 0001-0001-0001.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/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 [ spread ]

undo mtu [ spread ]

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 the range of 46 to 9008 bytes.

spread: Batch modifies the MTU for the subinterfaces of a main interface. Subinterfaces do not support this keyword.

Usage guidelines

The MTU setting for an interface takes effect only on packets sent by the CPU. Set a proper MTU to try to avoid packet fragmentation. If an interface has both the mtu and ip mtu commands executed, the ip mtu command rather than the mtu command takes effect on IPv4 packets sent by the interface. For more information about the ip mtu command, see IP performance optimization commands in Layer 3—IP Services Command Reference.

The mtu size command executed in main interface view takes effect only on the main interface. The mtu size command executed in subinterface view takes effect only on the subinterface.

The mtu size spread command executed in main interface view can modify the MTU for both the main interface and its subinterfaces. However, the MTU separately configured for a subinterface takes priority.

Examples

# Set the MTU to 1430 bytes for Ten-GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] mtu 1430

# Set the MTU to 1430 bytes for Ten-GigabitEthernet 1/0/1.1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1.1

[Sysname-Ten-GigabitEthernet1/0/1.1] mtu 1430

# Set the MTU to 1430 bytes for Ten-GigabitEthernet 1/0/1 and its subinterfaces.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] mtu 1430 spread

This operation may take a long time to modify the MTU of subinterfaces on this interface. Continue? [Y/N]:y

traffic-statistic enable

Use traffic-statistic enable to enable packet statistics collection for a Layer 3 Ethernet subinterface.

Use undo traffic-statistic enable to disable packet statistics collection for a Layer 3 Ethernet subinterface.

Syntax

traffic-statistic enable

undo traffic-statistic enable

Default

Packet statistics collection is disabled for a Layer 3 Ethernet subinterface.

Views

Layer 3 Ethernet subinterface view

Predefined user roles

network-admin

Usage guidelines

You can use the display interface or display counters command to display the subinterface traffic statistics. The Input and Output fields in the display interface command output display the Ethernet subinterface packet statistics.

Examples

# Enable packet statistics collection for Ten-GigabitEthernet1/0/1.1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/0/1.1

[Sysname-Ten-GigabitEthernet1/0/1.1] traffic-statistic enable

Related commands

display counters

display interface

02-Layer 2—LAN Switching Command Reference

flow-control receive enable

linkdown trap enable shutdown

priority-flow-control (Ethernet interface view)

priority-flow-control no-drop dot1p (Ethernet interface view)

priority-flow-control no-drop dot1p (system view)

display storm-constrain

port up-mode

storm-constrain

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us