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 FlexE 3/1/1:1 to 1000 kbps.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] bandwidth 1000

bind interface

Use bind interface to add a FlexE physical interface to a FlexE group interface.

Use undo bind interface to remove a FlexE physical interface from a FlexE group interface.

Syntax

bind interface interface-type interface-number phy-number number

undo bind interface interface-type interface-number

Default

No FlexE physical interfaces exist in a FlexE group interface.

Views

FlexE group interface view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies a FlexE physical interface by its type and number.

phy-number number: Specifies the PHY number of the FlexE physical interface, in the range of 1 to 126 for a 50G interface and 1 to 254 for a 100G interface.

Usage guidelines

When you add a FlexE physical interface to a FlexE group interface, follow these restrictions and guidelines:

· You can add a FlexE physical interface only to a FlexE group interface.

· On an RX-NIC-CQ1LF subcard, only one FlexE physical interface can be added to a FlexE group interface.

· When the RX-NIC-CQ2LF subcard is installed on a CSPEX-1802X or CSPEX-1812X card, only one FlexE physical interface can be added to a FlexE group interface.

· On an RX-NIC-LGQ2L or RX-NIC-LGQ4L subcard, up to two FlexE physical interfaces can be added to a FlexE group interface. The member interface numbers must be 1 and 2, 3 and 4, 5 and 6, or 7 and 8.

· For correct communication between FlexE physical interfaces at both of the ends of a link, you must add the FlexE physical interfaces to the same FlexE group interface. Make sure the FlexE physical interfaces have the same PHY number.

If the bandwidth or timeslots of a FlexE physical interface have been bound to a FlexE logical interface, you cannot the following tasks:

· Remove the FlexE physical interface from the FlexE group interface.

· Change the PHY number of the FlexE physical interface.

Examples

# Add FlexE-HundredGigE 3/1/1 to FlexE-group 3/1/1 and set the PHY number of the FlexE physical interface to 2.

<Sysname> system-view

[Sysname] interface flexe-group 3/1/1

[Sysname-FlexE-Group3/1/1] bind interface flexe-hundredgig 3/1/1 phy-number 2

Related commands

client

interface flexe-group

client

Use client to set the client ID for a FlexE logical interface to be created and create the FlexE logical interface in a FlexE group interface.

Use undo client to restore the default.

Syntax

client client-id { bandwidth bandwidth-value | bind interface interface-type interface-number timeslot timeslot-list }

undo client client-id [ bandwidth | bind interface interface-type interface-number ]

Default

No FlexE logical interfaces exist in a FlexE group interface.

Views

FlexE group interface view

Predefined user roles

network-admin

Parameters

client-id: Specifies the client ID of the FlexE group interface to be created, in the range of 1 to 65534. The interface number of the FlexE logical interface is in the form of FlexE-group-interface-number:client-ID.

bandwidth bandwidth-value: Specifies the bandwidth of the FlexE logical interface directly in Gbps. The value range is 5 to 4194303, and the step is 5.

bind interface interface-type interface-number timeslot timeslot-list: Specifies the bandwidth of the FlexE logical interface based on timeslots. You can bind timeslots of a FlexE physical interface to the FlexE logical interface. The bandwidth of the FlexE logical interface is timeslot-count × 5 GB.

· interface-type interface-number: Specifies the FlexE physical interface by it type and number.

· timeslot-list: Specifies a comma-separated list of timeslot items. Each item specifies a timeslot by its ID or a range of timeslots in the form of start_timeslot-end_timeslot. For example, 1,3-5. The maximum length of the timeslot list is 31 characters. The value range of timeslot IDs depend on FlexE physical interface type.

¡ For FlexE-50G interfaces, the value range for the timeslot ID is 0 to 9. Each timeslot represent bandwidth of 5 Gbps.

¡ For FlexE-100G interfaces, the value range for the timeslot ID is 0 to 19. Each timeslot represents bandwidth of 5 Gbps.

Usage guidelines

Use this command to set the client ID for a FlexE logical interface to be created and create the FlexE logical interface in a FlexE group interface. The interface number of the FlexE logical interface is in the format of FlexE-group-interface-number:client ID. For example, after you execute the client-id 10 command in the view of FlexE-Group 3/1/1, the device creates FlexE logical interface FlexE3/1/1:10 in which 10 is the client ID.

You can set the bandwidth of a FlexE logical interface in bandwidth or timeslot configuration mode set by using the flexe config-mode command in system view.

· If the bandwidth configuration mode is bandwidth mode, you can only use the client client-id bandwidth command to set the bandwidth of the FlexE logical interface.

· If the bandwidth configuration mode is timeslot mode, you can only use the client client-id binding interface interface-type interface-number timeslot timeslot-list command to set the bandwidth of FlexE logical interfaces.

For correct communication between FlexE logical interfaces at both ends of a link, you must perform the following tasks:

· Create a FlexE group interface at both of the devices.

· Set the same client ID for the two FlexE group interfaces.

Examples

# Create FlexE logical interface FlexE3/1/1:10 and set its bandwidth to 10 Gbps.

<Sysname> system-view

[Sysname] interface flexe-group 3/1/1

[Sysname-FlexE-Group3/1/1] bind interface flexe-hundredgig 3/1/1 phy-number 2

[Sysname-FlexE-Group3/1/1] client 10 bandwidth 10

Related commands

bind interface

flexe config-mode

interface flexe-group

config-mode

Use config-mode to set the bandwidth allocation mode for a FlexE logical interface.

Use undo config-mode to restore the default.

Syntax

config-mode { bandwidth | sub-timeslot }

undo config-mode

Views

FlexE-FG10G interface view

Default

The bandwidth allocation mode is bandwidth-based.

Predefined user roles

network-admin

Parameters

bandwidth: Specifies the fine granularity bandwidth-based mode, which allows you to flexibly configure bandwidth.

sub-timeslot: Specifies the sub-timeslot-based mode, which allows you to allocate bandwidth by specifying sub-timeslots at the granularity of 10 Mbps.

Usage guidelines

To meet the differentiated service carrying requirements for small bandwidth, high isolation, and high security in the 5G+vertical industry application scenarios and private line service scenarios, you must provide carrier channels with lower granularity. The fine granularity unit (FGU) technique refines the granularity from 5 Gbps to 10 Mbps to provide carrier channels with low costs, small granularity, and hardware isolation to meet the requirements of 5G+vertical industry application scenarios and government/organization private line scenarios.

In the current software version, you can configure bandwidth at the granularity of 10 Mbps for FlexE-FG10G interfaces. Use this command to configure the bandwidth allocation mode for a fine granularity FlexE logical interface.

You can configure bandwidth for a fine-granularity FlexE logical interface flexibly or through specifying sub-timeslots with the specified granularity.

· When the bandwidth allocation mode is bandwidth-based, execute the fg-client fg-client-id bandwidth bandwidth-value command to configure bandwidth flexibly for a FlexE-FG10G interface.

· When the bandwidth allocation mode is sub-timeslot-based, execute the fg-client fg-client-id timeslot timeslotlist command to specify sub-timeslots with the granularity of 10 Mbps for a FlexE-FG10G interface.

If you have used the fg-client fg-client-id bandwidth bandwidth-value or fg-client fg-client-id timeslot timeslotlist command to configure bandwidth for a FlexE-FG10G interface, you cannot modify the bandwidth allocation mode for the FlexE-FG10G interface.

Examples

# In FlexE-FG10G interface view, configure the bandwidth allocation mode as sub-timeslot-based for fine-granularity FlexE logical interfaces.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] port-type flexe-fg

[Sysname-FlexE-FG10G3/1/1] config-mode sub-timeslot

Related commands

fg-client

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

FlexE-50G interface view

FlexE-100G 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 are mutually exclusive on an interface.

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

Do not enable the dampening function on an interface with MSTP enabled.

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

Examples

# Enable interface dampening on FlexE-HundredGigE 3/1/1.

<Sysname> system-view

[Sysname] interface flexe-hundredgige 3/1/1

[Sysname-FlexE-HundredGig3/1/1] dampening

Related commands

display interface

link-delay

default

Use default to restore the default settings for an interface.

Syntax

default

Views

FlexE group interface view

FlexE physical interface view

FlexE logical interface 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 FlexE logical interface FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/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, FlexE3/1/1:1 Interface).

Views

FlexE group interface view

FlexE physical interface view

FlexE logical interface view

Predefined user roles

network-admin

Parameters

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

Examples

# Configure the description of FlexE logical interface FlexE 3/1/1:1 as lan-interface.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] description lan-interface

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 represents the interface number. The subnumber argument represents the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 99999999.

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 information about Layer 2 FlexE logical interface FlexE 3/1/1:1.

<Sysname> display interface flexe 3/1/1:1

FlexE3/1/1:1

Current state: DOWN

Line protocol state: DOWN

Description: FlexE3/1/1:1 Interface

Link fault: None

TX bandwidth in use: 0 Gbps

RX bandwidth in use: 0 Gbps

Maximum frame length: 10240

FlexE group: FlexE-Group3/1/1

Allow jumbo frames to pass

Broadcast max-ratio: 100%

Multicast max-ratio: 100%

Unicast max-ratio: 100%

IP packet frame type: Ethernet II, hardware address: f474-88dd-6800

Flow-control is not enabled

Loopback is not set

Unknown-speed mode, full-duplex mode

Link speed type is autonegotiation, link duplex type is force link

PVID: 1

Port link-type: Access

Tagged VLANs: None

Untagged VLANs: 1

Port priority: 0

Last clearing of counters: Never

Current system time:2020-07-01 16:30:23

Last time when physical state changed to up:-

Last time when physical state changed to down:2020-07-01 16:30:13

Peak input rate: 0 bytes/sec, at 2020-07-01 16:30:13

Peak output rate: 0 bytes/sec, at 2020-07-01 16:30:13

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

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

Input (total): 0 packets, 0 bytes

0 unicasts, 0 broadcasts, 0 multicasts, - pauses

Input (normal): 0 packets, 0 bytes

- unicasts, - broadcasts, - multicasts, 0 pauses

Input: 0 input errors, 0 runts, 0 giants, 0 throttles

0 CRC, 0 frame, 0 overruns, - aborts

0 ignored, - parity errors

Output (total): 0 packets, 0 bytes

0 unicasts, 0 broadcasts, 0 multicasts, - pauses

Output (normal): 0 packets, 0 bytes

- unicasts, - broadcasts, - multicasts, 0 pauses

Output: 0 output errors, - underruns, - buffer failures

0 aborts, 0 deferred, - collisions, 0 late collisions

- lost carrier, - no carrier

# Display information about Layer 3 FlexE interface FlexE 3/1/2:1.

<Sysname> display interface flexe 3/1/1:1

FlexE3/1/1:1

Current state: DOWN

Line protocol state: DOWN

Description: FlexE3/1/1:1 Interface

Bandwidth: 5000000 kbps

Flow-control is not enabled

Maximum transmission unit: 1500

FlexE group: FlexE-Group3/1/1

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: f474-88dd-6898

IPv6 packet frame type: Ethernet II, hardware address: f474-88dd-6898

Link fault: None

TX bandwidth in use: 0 Gbps

RX bandwidth in use: 0 Gbps

Port priority: 0

Loopback is not set

unknown-speed mode, full-duplex mode

Link speed type is autonegotiation, link duplex type is force link

The maximum frame length is 10240

Last clearing of counters: Never

Current system time:2020-07-01 16:26:28

Last time when physical state changed to up:-

Last time when physical state changed to down:2020-07-01 16:26:11

Peak input rate: 0 bytes/sec, at 2020-07-01 16:26:11

Peak output rate: 0 bytes/sec, at 2020-07-01 16:26:11

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

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

Input (total): 0 packets, 0 bytes

0 unicasts, 0 broadcasts, 0 multicasts, - pauses

Input (normal): 0 packets, 0 bytes

- unicasts, - broadcasts, - multicasts, 0 pauses

Input: 0 input errors, 0 runts, 0 giants, 0 throttles

0 CRC, 0 frame, 0 overruns, - aborts

0 ignored, - parity errors

Output (total): 0 packets, 0 bytes

0 unicasts, 0 broadcasts, 0 multicasts, - pauses

Output (normal): 0 packets, 0 bytes

- unicasts, - broadcasts, - multicasts, 0 pauses

Output: 0 output errors, - underruns, - buffer failures

0 aborts, 0 deferred, - collisions, 0 late collisions

- lost carrier, - no carrier

Table 1 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. · ETH-rddc Shutdown—The interface has been shut down by the Reth module. · mac-address moving down—The interface has been shut down by the MAC address move suppression feature. · MAD ShutDown—The interface has been shut down by IRF MAD. This state occurs if the interface is on an IRF fabric placed in Recovery state after an IRF split. · 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.
FlexE group	FlexE group interface to which the FlexE logical interface belongs.
Internet protocol processing: Disabled	The interface is not assigned an IP address and cannot 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 BRAS Services Configuration Guide. · BOOTP-allocated—BOOTP allocated IP address. For more information, see BOOTP client configuration in BRAS Services Configuration Guide. · PPP-negotiated—IP address assigned by a PPP server during PPP negotiation. For more information, see PPP configuration in BRAS Services Configuration Guide. · Unnumbered—IP address borrowed from another interface. · MAD—IP address assigned to an IRF member device for MAD on the interface. For more information, see IRF configuration in Virtual Technologies Configuration Guide. · 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.
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.
Unknown-speed mode	The speed of the interface is unknown because the speed negotiation fails or the interface is physically disconnected.
unknown-duplex mode	The duplex mode of the interface is unknown because the duplex mode negotiation fails or the interface is physically disconnected.
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.
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.
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.
Last interval second input: 0 packets/sec 0 bytes/sec 0% Last interval second output: 0 packets/sec 0 bytes/sec 0%	Average inbound or outbound traffic rate (in pps and Bps) in the last statistics polling interval, and the ratio of the actual rate to the interface bandwidth. To set the statistics polling interval, use the flow-interval command. A hyphen (-) indicates that the statistical item is not supported.
Input(total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses	The two fields on the first line represent the inbound traffic statistics (in packets and bytes) for the interface. All inbound normal packets, abnormal packets, and normal pause frames were counted. The four fields on the second line represent: · Number of inbound unicast packets. · Number of inbound broadcasts. · Number of inbound multicasts. · Number of inbound pause frames. A hyphen (-) indicates that the statistical item is not supported.
Input(normal): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses	The two fields on the first line represent the inbound normal traffic and pause frame statistics (in packets and bytes) for the interface. The four fields on the second line represent: · Number of inbound normal unicast packets. · Number of inbound normal broadcasts. · Number of inbound normal multicasts. · Number of inbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported.
input errors	Statistics of incoming error packets.
runts	Number of inbound frames meeting the following conditions: · Shorter than 64 bytes. · In correct format. · Containing valid CRCs.
giants	Number of inbound giants. Giants refer to frames larger than the maximum frame length supported on the interface. For a FlexE 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 a FlexE 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 FlexE logical interface (with an integral or non-integral length). ¡ For a FlexE interface that does not permit jumbo frames, the maximum frame length is 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). ¡ For a FlexE 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.
Link fault	FlexE logical interface fault state: · Local fault. · Remote fault. · None.
TX bandwidth in use	Effective Tx bandwidth of the FlexE logical interface.
RX bandwidth in use	Effective Rx bandwidth of the FlexE logical interface.

# Display information about FlexE physical interface FlexE-50-100G 1/0/1.

<Sysname> display interface flexe-hundredgig 3/1/1

FlexE-HundredGig3/1/1

Current state: UP

Line protocol state: UP

Description: FlexE-HundredGig3/1/1 Interface

Bandwidth: 100000000 kbps

FlexE group: FlexE-Group3/1/1

Current system time:2021-07-22 10:29:15

Last time when physical state changed to up:2021-07-22 09:57:35

Last time when physical state changed to down:2021-07-22 09:55:49

Media type is not sure, port hardware type is No connector

FEC mode: None

Table 2 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). · 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. · DOWN—The data link layer protocol is down.
Bandwidth	Expected bandwidth of the interface.
FlexE group	FlexE group interface to which the FlexE physical interface belongs.
Bound FlexE logical interface hosting clock service	FlexE logical interface that bound a FlexE physical interface to host the clock service.
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.
Media type is	Media type of the interface.
Port hardware type is	Hardware type of the interface.
FEC mode	FEC mode, which depends on your configuration. When you set the FEC mode to auto, the FEC mode is determined by the model of the installed transceiver module.

# Display information about interface FlexE-Group 3/1/1.

<Sysname> display interface FlexE-Group 3/1/1

FlexE-Group3/1/1

Current state: UP

Description: FlexE-Group3/1/1 Interface

FlexE group information:

Bandwidth configuration mode: Bandwidth

Group number: 1

Total bandwidth: 100 Gbps

Valid bandwidth: 0 Gbps

FlexE PHY information:

FlexE-HundredGig3/1/1:

Status: Normal

TX overhead: PHY number 1, group number 1

RX overhead: PHY number 1, group number 1

FlexE calendar information:

FlexE-HundredGig3/1/1

Timeslots Client IDs

0, 1, 2, 3, 4 1, 1, 1, 1, 1

5, 6, 7, 8, 9 1, 1, 1, 1, 1

10, 11, 12, 13, 14 1, 1, 1, 1, 1

15, 16, 17, 18, 19 1, 1, 1, 1, 1

FlexE-HundredGig3/1/1

Timeslots Client IDs

0, 1, 2, 3, 4 1, 1, 1, 1, 1

5, 6, 7, 8, 9 1, 1, 1, 1, 1

10, 11, 12, 13, 14 1, 1, 1, 1, 1

15, 16, 17, 18, 19 1, 1, 1, 1, 1

Table 3 Command output

Field	Description
Current state	Physical link state of the interface: · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up.
Bandwidth configuration mode	Bandwidth configuration mode of a FlexE logical interface: · Bandwidth—Specify the bandwidth mode. · Timeslot—Specify timeslot mode.
Group number	FlexE group interface number.
Total bandwidth	Total bandwidth of a FlexE group interface, the sum of the bandwidth of each bound physical interface.
Valid bandwidth	Available bandwidth of a FlexE group interface, the remaining bandwidth that has not been allocated to the FlexE logical interface.
Status	State of the FlexE physical interface: · Normal—The interface is in normal state, and no alarm or error exists. · Local fault. · Remote fault. · CRC error—CRC errors exist In the FlexE overhead. · Group mismatch—The group numbers on two ends do not match. · PhyNumber mismatch—The PHY numbers on two ends do not match.
TX overhead	Parameters in the overhead sent by the local physical interface, including PHY number and group number.
RX overhead	Parameters in the overhead received by the local physical interface, including PHY number and group number.
Timeslots	Timeslot numbers of the FlexE physical interface.
Client IDs	Client IDs corresponding to the timeslot numbers of the FlexE physical interface.

# 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

FlexE-100G3/1/1 DOWN DOWN --

FlexE-Group3/1/1 DOWN -- --

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

FlexE3/1/1:10 DOWN auto A A 1

# Display brief information about FlexE 3/1/2:2, including the complete description of the interface.

<Sysname> display interface flexe 3/1/2:2 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

FlexE3/1/2 UP 50G F A 1 aaaaaaaaaaaaaaaaaaaaaa

# 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

Flex-100GE3/1/1 DOWN Not connected

Brief information on interfaces in bridge mode:

Link: ADM - administratively down; Stby - standby

Interface Link Cause

FlexE3/1/3:3 DOWN Not connected

Table 4 Command output

Field	Description
Brief information on interfaces in route mode:	Brief information about Layer 3 interfaces.
Interface	Interface name.
Link	Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state.
Protocol	Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces. This field displays two hyphens (--) if the device does not support displays the data link layer protocol status of the interface.
Primary IP	Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address.
Description	Description of the interface.
Brief information of interfaces in bridge mode:	Brief information about Layer 2 interfaces.
Speed	Speed of the interface, in bps. This field displays the (a) flag next to the speed if the speed is automatically negotiated. This field displays auto if the interface is configured to autonegotiate its speed but the autonegotiation has not started.
Duplex	Duplex mode of the interface: · A—Autonegotiation. The interface is configured to autonegotiate its duplex mode but the autonegotiation has not started. · F—Full duplex. · F(a)—Autonegotiated full duplex. · H—Half duplex. · H(a)—Autonegotiated half duplex.
Type	Link type of the interface: · A—Access. · H—Hybrid. · T—Trunk.
PVID	Port VLAN ID.
Cause	Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · DOWN ( Link-Aggregation interface down )—The interface is a member port of an aggregate interface, and the aggregate interface is down. · DOWN (Loopback detection down)—The loopback detection module has detected loops. · DOWN ( Monitor-Link uplink down )—The monitor link module has detected that the uplink is down. · MAD ShutDown—The interface is on an IRF fabric placed by IRF MAD in Recovery state after an IRF split. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). · STP DOWN—The interface has been shut down by the BPDU guard feature. · Standby—The interface is a backup interface in standby state.

Related commands

reset counters interface

display this interface

Use display this interface to display the operating status and information of an interface.

Syntax

display this interface

Views

FlexE physical interface view

FlexE logical interface view

Predefined user roles

network-admin

Usage guidelines

In interface view, to quickly view the operating status or packet statistics of the interface, execute this command.

For an interface, the output from the display this interface command in interface view is the same as the output from the display interface interface-type interface-number command in any view.

Related commands

display interface

flexe config-mode

Use flexe config-mode to set the bandwidth configuration mode of FlexE logical interfaces.

Use undo flexe config-mode to restore the default.

Syntax

In standalone mode:

flexe config-mode slot slot-number subslot subslot-number { bandwidth | mix | timeslot }

undo flexe config-mode slot slot-number subslot subslot-number

In IRF mode:

flexe config-mode chassis chassis-number slot slot-number subslot subslot-number { bandwidth | mix | timeslot }

undo flexe config-mode chassis chassis-number slot slot-number subslot subslot-number

Views

System view

Default

The bandwidth mode is used. You can flexibly set the bandwidth of FlexE logical interfaces.

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)

subslot subslot-number: Specifies a subcard by its slot number.

bandwidth: Specifies the bandwidth mode as the bandwidth configuration mode of FlexE logical interfaces. In this mode, you can flexibly set the bandwidth of a FlexE logical interface.

mix: Specifies the mixed mode as the bandwidth configuration mode of FlexE logical interfaces. In this mode, you can set the bandwidth of a FlexE logical interface in either bandwidth mode or timeslot mode.

timeslot: Specifies the timeslot mode as the bandwidth configuration mode for FlexE logical interfaces. In this mode, you can set the bandwidth of a FlexE logical interface by binding timeslots with the specified timeslot granularity of a FlexE physical interface to it.

Usage guidelines

You can set the bandwidth configuration mode for FlexE logical interfaces to one of the following modes:

· Bandwidth mode—If the bandwidth configuration mode is bandwidth mode, you can only use the client client-id bandwidth command to set the bandwidth of the FlexE logical interface. In this mode, you can set different bandwidth for FlexE logical interfaces at both ends.

· Timeslot mode—If the bandwidth configuration mode is timeslot mode, you can only use the client client-id binding interface interface-type interface-number timeslot timeslot-list command to set the bandwidth of FlexE logical interfaces. In this mode, you must bind the timeslots of the same FlexE physical interfaces to FlexE logical interface at both ends. The timeslots of the FlexE physical interface bound to the FlexE logical interfaces at both end can be different.

· Mixed mode—If the bandwidth configuration mode is mixed mode, you can use the client client-id bandwidth command to flexibly set the bandwidth of the FlexE logical interface or use the client client-id binding interface interface-type interface-number timeslot timeslot-list command to set the bandwidth of the FlexE logical interface.

If you already set the bandwidth of a FlexE logical interface by using the client command, you cannot change the bandwidth configuration mode by using this command.

Examples

# Set the bandwidth configuration mode to timeslot mode for FlexE logical interfaces.

<Sysname> system-view

[Sysname] flexe config-mode slot 1 subslot 1 timeslot

Related commands

client

flow-interval

Use flow-interval to set the statistics polling interval on a FlexE logical interface.

Use undo flow-interval to restore the default.

Syntax

flow-interval interval

undo flow-interval

Default

The statistics polling interval is 300 seconds on a FlexE logical interface.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the statistics polling interval in seconds. The interval is in the range of 1 to 300.

Usage guidelines

After you modify the statistics polling interval on a FlexE logical interface, the collected statistics are inaccurate until two intervals after the modification. To view the accurate statistics, see the Last interval second input and Last interval second output fields in the output from the display interface command.

Examples

# Set the statistics polling interval to 100 seconds on FlexE logical interface FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] flow-interval 100

Related commands

display interface

fg-client

Use fg-client to configure a client ID, and create a FlexE logical interface.

Use undo fg-client to restore the default.

Syntax

fg-client fg-client-id { bandwidth bandwidth-value | timeslot timeslot-list }

undo fg-client fg-client-id

Default

No FlexE logical interfaces exist.

Views

FlexE-FG10G interface view

Predefined user roles

network-admin

Parameters

fg-client-id: Specifies an FG client ID (FlexE-FG10G logical interface number) on a FlexE logical interface. The value range for this argument is 1 to 4000.

bandwidth bandwidth-value: Directly specifies bandwidth for a FlexE logical interface. The bandwidth-value argument specifies bandwidth for a FlexE logical interface. The bandwidth is in the step of 10 in Mbps.

timeslot timeslot-list: Specifies bandwidth for a FlexE logical interface by specifying sub-timeslots. The timeslot-list argument specifies a sub-timeslot ID list, for example, 1,3-5. Use a hyphen (-) to specify a sub-timeslot ID range, and separate multiple sub-timeslot IDs or ranges by using commas (,). A sub-timeslot ID list can contain up to 24 characters. Only full data configuration is supported. A sub-timeslot represents bandwidth of 10 Mbps.

Usage guidelines

When you use this command to configure a FG client ID, the system will automatically create a FlexE logical interface with the same number. For example, if you configure FG client ID 10 on FlexE-FG10G 3/1/1, the system will automatically create FlexE logical interface FlexE 3/1/1/0:10.

You can also use this command to configure the bandwidth for a FlexE logical interface. You can configure bandwidth for a FlexE logical interface flexibly or through specifying sub-timeslots with the specified granularity.

· When the config-mode bandwidth command is used to configure the bandwidth allocation mode as bandwidth-based, you can only execute the fg-client fg-client-id bandwidth command to configure bandwidth flexibly for a FlexE logical interface.

· When the config-mode sub-timeslot command is used to configure the bandwidth allocation mode as sub-timeslot-based, you can only execute the fg-client fg-client-id timeslot timeslot-list command to specify sub-timeslots for a FlexE logical interface. The bandwidth of the FlexE logical interface is the number of sub-timeslots multiplied by the sub-timeslot granularity.

For FlexE-FG10G logical interfaces on two ends of a link to communicate normally, configure the same FG client ID on the FlexE-FG10G interfaces on both ends.

Examples

# On a PHY-level fine granularity slice, configure FG client ID 10, create FlexE-FG10G logical interface FlexE 3/1/1/0:10 with the same ID, and assign bandwidth of 50 Mbps to the interface.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] port-type flexe-fg

[Sysname-FlexE-FG10G3/1/1] config-mode bandwidth

[Sysname-FlexE-FG10G3/1/1] fg-client 10 bandwidth 50

Related commands

config-mode

ifmonitor crc-error

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

Use undo ifmonitor crc-error to restore the default.

Syntax

In standalone mode:

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

undo ifmonitor crc-error slot slot-number [ cpu cpu-number ]

In IRF mode:

ifmonitor crc-error chassis chassis-number slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor crc-error chassis chassis-number slot slot-number [ cpu cpu-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.

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

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.

This command takes effect only when the CRC error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor crc-error command.

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

Examples

# Globally 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 3 high-threshold 5000 low-threshold 400 interval 6

Related commands

snmp-agent trap enable ifmonitor

ifmonitor input-error

Use ifmonitor input-error to set global input error packet alarm parameters.

Use undo ifmonitor input-error to restore the default.

Syntax

In standalone mode:

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

undo ifmonitor input-error slot slot-number [ cpu cpu-number ]

In IRF mode:

ifmonitor input-error chassis chassis-number slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor input-error chassis chassis-number slot slot-number [ cpu cpu-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. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

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.

This command takes effect only when the input error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor input-error command.

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

Examples

# Globally 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 3 high-threshold 5000 low-threshold 400 interval 6

Related commands

snmp-agent trap enable ifmonitor

ifmonitor input-usage

Use ifmonitor input-usage to set global inbound bandwidth usage alarm parameters.

Use undo ifmonitor input-usage to restore the default.

Syntax

In standalone mode:

ifmonitor input-usage slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value

undo ifmonitor input-usage slot slot-number [ cpu cpu-number ]

In IRF mode:

ifmonitor input-usage chassis chassis-number slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value

undo ifmonitor input-usage chassis chassis-number slot slot-number [ cpu cpu-number ]

Default

The upper threshold is 90% and the lower threshold is 80% for inbound bandwidth usage alarms.

Views

System view

Predefined user roles

network-admin

Parameters

high-threshold high-value: Specifies the upper threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.

low-threshold low-value: Specifies the lower threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Usage guidelines

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

The statistics polling interval can be set by using the flow-interval command.

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.

This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor input-usage command.

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

Examples

# Globally set the upper threshold to 95% and lower threshold to 80% for inbound bandwidth usage alarms.

<Sysname> system-view

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

Related commands

flow-interval

snmp-agent trap enable ifmonitor

ifmonitor output-error

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

Use undo ifmonitor output-error to restore the default.

Syntax

In standalone mode:

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

undo ifmonitor output-error slot slot-number [ cpu cpu-number ]

In IRF mode:

ifmonitor output-error chassis chassis-number slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo ifmonitor output-error chassis chassis-number slot slot-number [ cpu cpu-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. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

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.

This command takes effect only when the output error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor output-error command.

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

Examples

# Globally 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 3 high-threshold 5000 low-threshold 400 interval 6

Related commands

snmp-agent trap enable ifmonitor

ifmonitor output-usage

Use ifmonitor output-usage to set global outbound bandwidth usage alarm parameters.

Use undo ifmonitor output-usage to restore the default.

Syntax

In standalone mode:

ifmonitor output-usage slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value

undo ifmonitor output-usage slot slot-number [ cpu cpu-number ]

In IRF mode:

ifmonitor output-usage chassis chassis-number slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value

undo ifmonitor output-usage chassis chassis-number slot slot-number [ cpu cpu-number ]

Default

The upper threshold is 90% and the lower threshold is 80% for outbound bandwidth usage alarms.

Views

System view

Predefined user roles

network-admin

Parameters

high-threshold high-value: Specifies the upper threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.

low-threshold low-value: Specifies the lower threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Usage guidelines

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

The statistics polling interval can be set by using the flow-interval command.

You can configure the outbound 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.

This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor output-usage command.

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

Examples

# Globally set the upper threshold to 80% and lower threshold to 60% for outbound bandwidth usage alarms.

<Sysname> system-view

[Sysname] ifmonitor output-usage slot 3 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.

Syntax

In standalone mode:

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

undo ifmonitor runt slot slot-number [ cpu cpu-number ]

In IRF mode:

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

undo ifmonitor runt chassis chassis-number slot slot-number [ cpu cpu-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. 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 runt packets exceeds the upper threshold on the interface.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

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 3 high-threshold 5 low-threshold 4 interval 6

Related commands

port ifmonitor runt

snmp-agent trap enable ifmonitor

interface

Use interface to enter the view of a FlexE physical interface.

Syntax

interface interface-type interface-number

Views

System view

Predefined user roles

network-admin

Parameters

interface-type: Specifies the interface type of a FlexE physical interface.

interface-number: Specifies the interface number of the FlexE physical interface.

Examples

# Enter the view of FlexE-HundredGigE 3/1/1.

<Sysname> system-view

[Sysname] interface flexe-hundredgig 3/1/1

[Sysname-FlexE-HundredGig3/1/1]

interface flexe

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

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

interface-number: Specifies the interface number of a FlexE logical interface, which consists of the interface number and client ID of the Flex-group interface to which the FlexE logical interface belongs.

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 99999999. Up to 16383 subinterfaces can be created on a main interface.

Usage guidelines

To create a FlexE logical interface, use the client command.

Examples

# Enter the view of FlexE logical interface FlexE 3/1/1:10.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:10

[Sysname-FlexE3/1/1:10]

Related commands

client

interface flexe-group

Use interface flexe-group to create a FlexE group interface and enter its view or enter the view of an existing FlexE group interface.

Use undo interface flexe-group to remove a FlexE group interface.

Syntax

interface flexe-group interface-number

undo interface flexe-group interface-number

Views

System view

Predefined user roles

network-admin

Parameters

interface-number: Specifies the interface number of the FlexE group interface. The last digit in the interface number represents the group number of the FlexE group interface.

Usage guidelines

After you create a FlexE group interface, you can create FlexE logical interfaces in the FlexE group interface as needed. Then, you can flexibly assign the total bandwidths of the FlexE physical interfaces to FlexE logical interfaces according to the bandwidth requirements of services.

The number of FlexE group interface must be equal to or smaller than the number of FlexE physical interfaces on the subslot.

You can delete a FlexE group interface only if the FlexE group interface does not have any FlexE physical or logical interfaces.

Examples

# Create FlexE group interface FlexE-Group 3/1/1 and enter its view.

<Sysname> system-view

[Sysname] interface flexe-group 3/1/1

[Sysname-FlexE-Group3/1/1]

Related commands

bind interface

client

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

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Allow jumbo frames to pass through FlexE logical interface FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] jumboframe enable

link-delay

Use link-delay to set the physical state change suppression interval on a FlexE interface.

Use undo link-delay to restore the default.

Syntax

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

undo link-delay { down | up }

Default

Each time the physical link of a FlexE interface goes up or comes down, the system immediately reports the change to the CPU.

Views

FlexE physical interface view

FlexE logical 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: Specifies the physical state change suppression interval on the FlexE interface. A value of 0 means that physical state changes are immediately reported to the CPU and are not suppressed.

· If you do not specify the msec keyword, the value range for this argument is 0 to 1200 seconds.

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

Usage guidelines

You can use this command 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.

On an interface, you can set different suppression intervals for link-up and link-down events. If you set the suppression interval multiple times for the same type of link suppression events, the most recent configuration takes effect.

Examples

# Set the link-down event suppression interval to 8 seconds on FlexE logical interface FlexE 3/1/1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] link-delay down 8

# Set the link-up event suppression interval to 800 milliseconds on FlexE logical interface FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] link-delay up msec 800 mode

loopback

CAUTION:

After you enable loopback testing on a FlexE logical interface, the interface does not forward data traffic.

‌

Use loopback to enable loopback testing on a FlexE physical interface.

Use undo loopback to disable loopback testing on a FlexE physical interface.

Syntax

loopback { external | internal }}

undo loopback

Default

Loopback testing is disabled on a FlexE physical interface.

Views

FlexE physical interface view

Predefined user roles

network-admin

Parameters

external: Enables external loopback testing on the FlexE logical interface.

internal: Enables internal loopback testing on the FlexE logical interface.

Usage guidelines

The interfaces on a MIC-XP10LF subcard supports external loopback. When performing external loopback, make sure both local and remote interfaces operate at 10 Gbps.

After you enable loopback testing on a FlexE logical interface, the FlexE logical interface switches to full duplex mode. After you disable loopback testing, the FlexE logical interface restores to its duplex setting.

The shutdown and loopback commands are mutually exclusive.

Examples

# Enable internal loopback testing on FlexE physical interface FlexE-HundredGigE 3/1/1.

<Sysname> system-view

[Sysname] interface flexe-hundredgig3/1/1

[Sysname-FlexE-HundredGig3/1/1] loopback internal

mac-address

Use mac-address to set the MAC address of a FlexE logical interface.

Use undo mac-address to restore the default.

Syntax

mac-address mac-address

undo mac-address

Default

No MAC address is set for a Layer 3 FlexE logical interface.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

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

Examples

# Set the MAC address of FlexE 3/1/1:1 to 0001-0001-0001.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] mac-address 1-1-1

mtu

Use mtu to set the MTU of a FlexE interface.

Use undo mtu to restore the default.

Syntax

mtu size

undo mtu

Default

The MTU of a FlexE interface is 1500 bytes.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

size: Specifies the MTU in bytes. The value range varies by interface type.

Usage guidelines

The MTU set by using this command or the ip mtu command takes effect only on packets that the interface delivers to the CPU, for example, packets originated from or destined for the interface. Set a reasonable MTU on the interface to avoid fragmentation.

If you configure both the mtu and ip mtu commands on the interface, the MTU set by using the command takes priority.

Examples

# Set the MTU to 1430 bytes for FlexE logical interface FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] mtu 1430

Related commands

ip mtu (Layer 3—IP Services Command Reference)

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

FlexE-100G interface view

Predefined user roles

network-admin

Parameters

auto: Autonegotiates the FEC mode or disables FEC according to the transceiver module type.

none: Performs no FEC.

rs-fec: Specifies the RS-FEC mode.

Usage guidelines

This command is supported only on CEPC-CQ8L, RX-NIC-CQ1LF, and RX-NIC-CQ2LF subcards.

After you execute the port fec mode auto or port fec mode none command for the interface, the interface does not correct forward errors. To specify the RS-FEC mode for the interface, use the fec mode rs-fec command.

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.

For transceiver modules that support FEC, you can specify the auto, none, or rs-fec keywords. For transceiver modules that does not support FEC, their interfaces do not correct forward errors.

The following compatibility matrix shows the support of the transceiver module models for FEC:

Model	FEC compatibility
100G_CWDM4_FEC_QSFP28	Yes
100G_PSM4_QSFP28	Yes
100GBASE_CR4_QSFP28	Yes
100GBASE_ER4_QSFP28	No
100GBASE_ER4L_QSFP28	Yes
100GBASE_ESR4_QSFP28	Yes
100GBASE_LR4_QSFP28	No
100GBASE_SR4_QSFP28	Yes
100GBASE_ZR4_QSFP28	Yes

‌

Examples

# Set the FEC mode of FlexE-100G 3/1/1 to autonegotiation.

<Sysname> system-view

[Sysname] interface flexe-100g 3/1/1

[Sysname-FlexE-100G3/1/1] port fec mode auto

port ifmonitor crc-error

Use port ifmonitor crc-error to set CRC error packet alarm parameters on a FlexE logical interface.

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

Syntax

port ifmonitor crc-error [ ratio ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo port ifmonitor crc-error

Default

A FlexE logical interface uses the global CRC error packet alarm parameters.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

ratio: Specifies the alarm thresholds in percentage. If you do not specify this keyword, you configure the alarm thresholds in absolute value.

high-threshold high-value: Specifies the upper threshold for CRC error packet alarms. If you specify the ratio keyword, the value range is 1 to 100. If you do not specify the ratio keyword, the value range is 1 to 4294967295 packets.

low-threshold low-value: Specifies the lower threshold for CRC error packet alarms. If you specify the ratio keyword, the value range is 1 to 100. If you do not specify the ratio keyword, the value range is 1 to 4294967295 packets.

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

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.

This command takes effect only when the CRC error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor crc-error command.

If 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 FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

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

Related commands

snmp-agent trap enable ifmonitor

port ifmonitor input-error

Use port ifmonitor input-error to set input error packet alarm parameters on a FlexE logical interface.

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

Syntax

port ifmonitor input-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo port ifmonitor input-error

Default

A FlexE logical interface uses the global input error packet alarm parameters.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

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

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

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

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.

This command takes effect only when the input error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor input-error command.

If 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 FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1: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 set inbound bandwidth usage alarm parameters on a FlexE logical interface.

Use undo port ifmonitor input-usage to restore the default.

Syntax

port ifmonitor input-usage high-threshold high-value low-threshold low-value

undo port ifmonitor input-usage

Default

A FlexE interface uses the global inbound bandwidth usage alarm parameters.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

high-threshold high-value: Specifies the upper threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.

low-threshold low-value: Specifies the lower threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.

Usage guidelines

The statistics polling interval can be set by using the flow-interval command.

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.

This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor input-usage command.

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

Examples

# Set the upper threshold to 80% and lower threshold to 6% for inbound bandwidth usage alarms on FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1: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 set output error packet alarm parameters on a FlexE logical interface.

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

Syntax

port ifmonitor output-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]

undo port ifmonitor output-error

Default

A FlexE logical interface uses the global output error packet alarm parameters.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

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

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

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

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.

This command takes effect only when the output error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor output-error command.

If 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 FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1: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 set outbound bandwidth usage alarm parameters on a FlexE logical interface.

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

Syntax

port ifmonitor output-usage high-threshold high-value low-threshold low-value

undo port ifmonitor output-usage

Default

A FlexE interface uses the global outbound bandwidth usage alarm parameters.

Views

FlexE logical interface view

Predefined user roles

network-admin

Parameters

high-threshold high-value: Specifies the upper threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.

low-threshold low-value: Specifies the lower threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.

Usage guidelines

The statistics polling interval can be set by using the flow-interval command.

You can configure the outbound 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.

This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor output-usage command.

If 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 inbound bandwidth usage alarms on FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1: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.

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

FlexE logical interface 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.

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 FlexE3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

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

Related commands

ifmonitor runt

snmp-agent trap enable ifmonitor

port link-mode

Use port link-mode to change the link mode of a FlexE logical interface.

Use undo port link-mode to restore the default.

Syntax

port link-mode { bridge | route }

undo port link-mode

Default

A FlexE logical interface operates in Layer 3 mode.

Views

FlexE logical 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 a FlexE logical interface also restores all commands (except shutdown) on the FlexE logical interface to their defaults in the new link mode.

‌

A FlexE logical interface can operate at one of the following modes:

· bridge—The Flex logical interface operates as a Layer 2 FlexE logical interface.

· route—The Flex logical interface operates as a Layer 3 FlexE logical interface.

Examples

# Configure FlexE 3/1/1:1 to operate in Layer 2 mode.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] port link-mode bridge

port-type

Use port-type flexe to change the type of an interface from Ethernet to FlexE.

Use port-type flexe-fg to change the type of an interface from Ethernet to fine granularity FlexE.

Use port-type ethernet to change the type of an interface from FlexE to Ethernet.

Syntax

In 50-GE/100-GE interface view:

port-type flexe

In 10-GE interface view:

port-type flexe-fg

In FlexE-FG10G/FlexE-50G/FlexE-100G interface view:

port-type ethernet

Views

10-GE interface view

50-GE interface view

100-GE interface view

FlexE-50G interface view

FlexE-100G interface view

FlexE-FG10G interface view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

After the type of an interface is changed, the system deletes the original interface and creates a new interface that is numbered the same as the original interface. All the other commands are restored to the default on the new interface.

‌

This command is supported only on the MIC-CQ1LF, MIC-XP10LF, NIC-XP20L1, RX-NIC-CQ1LF, RX-NIC-CQ2LF, and RX-NIC-LGQ4L subcards. Support for interface types varies by subcard model.

· The MIC-CQ1LF and RX-NIC-CQ2LF subcards support 50-GE, 100-GE, FlexE-50G, and FlexE-100G interfaces.

· The MIC-XP10LF and NIC-XP20L1 subcards support 10-GE and FlexE-FG10G interfaces.

· The RX-NIC-LGQ4L subcards support 50-GE and FlexE-50G interfaces.

When switching the mode for interfaces on a MIC-CQ1LF subcard, follow these restrictions and guidelines:

· Only fiber port 1 supports the 100-GE and FlexE-100G modes. When fiber port 1 is switched to the 100-GE or FlexE-100G mode, fiber port 2 becomes temporarily unavailable.

· Both fiber port 1 and fiber port 2 support the 50-GE and FlexE-50G modes. When you switch the mode between 50-GE and FlexE-50G for fiber port 1 and fiber port 2, fiber port 1 and fiber port 2 operate independently without affecting each other.

· When switching between standard Ethernet mode and flexible Ethernet mode for a fiber port, make sure the speed is the same before and after switchover. For example, a 50-GE interface can be switched to a FlexE-50G interface, and a 100-GE interface can be switched to a FlexE-100G interface. However, a 50-GE interface cannot be directly switched to a FlexE-100G interface. For a fiber port in standard Ethernet mode, you can change the speed by using the using fiftygige, using fortygige, and using hundredgige commands. For more information about these commands, see Ethernet interface commands in Interface Command Reference.

To change the type of an interface on an RX-NIC-LGQ4L subcard, first execute the subslot-working-mode command to configure the subcard to operate in ethernet-flexe mode. For more information about the subslot-working-mode command, see device management commands in Fundamentals Command Reference.

The bandwidth of an interface in standard Ethernet mode is fixed, and the bandwidth of an interface in FlexE mode can be flexibly specified.

· To assign bandwidth at the granularity of 5 Gbps, execute the port-type flexe command to switch the type of the interface from Ethernet to FlexE.

· To assign bandwidth at the granularity of 10 Mbps, execute the port-type flexe-fg command to switch the type of the interface from Ethernet to fine granularity FlexE.

If a FlexE physical interface has been added to a FlexE group interface, you cannot change the interface type.

Examples

# Change standard Ethernet interface HundredGigE 3/1/1 a FlexE interface.

<Sysname> system-view

[Sysname] interface hundredgig3/1/1

[Sysname-HundredGig3/1/1] port-type flexe

The interface HundredGig3/1/1 will be deleted. Continue? [Y/N]:

# Change 10-GE interface Ten-GigabitEthernet 3/1/1 into fine granularity FlexE mode.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] port-type flexe-fg

The interface Ten-GigabitEthernet3/1/1 will be deleted. Continue? [Y/N]:

shutdown

Use shutdown to shut down a FlexE interface.

Use undo shutdown to bring up a FlexE interface.

Syntax

shutdown

undo shutdown

Default

A FlexE interface is up.

Views

FlexE physical interface view

FlexE logical interface view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

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

‌

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

The shutdown and loopback commands are mutually exclusive.

Examples

# Shut down and then bring up FlexE logical interface FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1

[Sysname-FlexE3/1/1:1] shutdown

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

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.

input-error: Enables the input error packet alarm function.

input-usage: Enables the inbound bandwidth usage alarm function.

output-error: Enables the output error packet alarm function.

output-usage: Enables the outbound bandwidth usage alarm function.

runt: Enables the runt packet alarm function for interfaces.

Examples

# Enable the CRC error packet alarm function.

<Sysname> system-view

[Sysname] snmp-agent trap enable ifmonitor crc-error

traffic-statistic include-interframe

Use traffic-statistic include-interframe to enable interframe gap and preamble statistics in the traffic statistics.

Use traffic-statistic include-interframe to restore the default.

Syntax

traffic-statistic include-interframe

undo traffic-statistic include-interframe

Default

Interframe gap and preamble statistics are enabled in the traffic statistics.

Views

FlexE interface view

Predefined user roles

network-admin

Usage guidelines

If you execute the display interface command, the Last 300 seconds input rate or Last 300 seconds output rate field in the command output displays the average outbound or inbound traffic rate in the last 300 seconds.

By default, traffic rate = native frame length × packet count per second. Execute the traffic-statistic include-interframe command if you need the total traffic statistics, including the native frame length, interframe gap length, and preamble length, for a specific time period. With this command executed, traffic rate = (native frame length + interframe gap length + preamble length) × packet throughput per second.

Examples

# Enable interframe gap and preamble statistics in the traffic statistics for FlexE 3/1/1:1.

<Sysname> system-view

[Sysname] interfaceflexe 3/1/1:1

[Sysname-FlexE3/1/1:1] traffic-statistic include-interframe

Traffic statistic will be set to include Inter-frame Gaps and Preambles. Continue? [Y/N]:y

Related commands

display interface

traffic-statistic enable

Use traffic-statistic enable to enable packet statistics collection for an interface.

Use undo traffic-statistic enable to disable packet statistics collection for an interface.

Syntax

traffic-statistic enable

undo traffic-statistic enable

Default

Packet statistics collection is disabled for an interface.

Views

FlexE logical 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.

Examples

# Enable packet statistics collection for FlexE3/1/1:1.1.

<Sysname> system-view

[Sysname] interface flexe 3/1/1:1.1

[Sysname-FlexE3/1/1:1.1] traffic-statistic enable

Related commands

display counters

display interface

03-Interface Command Reference

display this interface

ifmonitor input-usage

port fec mode

port ifmonitor runt

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