The Flexible Ethernet (FlexE) technology provides service providers with flexibility to assign different bandwidth to interfaces to meet bandwidth requirements of different services.

FlexE interfaces include the following types:

· FlexE physical interface—A FlexE physical interface is a physical interface that switches from standard Ethernet mode to flexible Ethernet mode. FlexE physical interfaces can be added to a FlexE group interface and the bandwidth of the FlexE group interface is the sum of the bandwidths of all FlexE physical interfaces in the group interface.

· FlexE logical interface—A FlexE logical interface is a logical interface of which the bandwidth can be flexibly specified. A FlexE group interface assigns bandwidth to FlexE logical interfaces according to requirements of different services.

FlexE interface tasks at a glance

To configure FlexE interfaces, perform the following tasks:

1. Changing the type of an interface

2. Configuring a FlexE group interface

a. Creating a FlexE group interface

b. (Optional.) Setting the sub-timeslot granularity

c. Adding a FlexE physical interface to a FlexE group interface

d. Creating a FlexE logical interface and set its bandwidth

e. Creating a FlexE-DCN interface

3. Configuring basic settings of a FlexE interface

4. Configure a FlexE physical interface

¡ Changing the speed mode of an interface

¡ (Optional.) Binding a FlexE physical interface to a FlexE logical interface for clock service hosting

¡ (Optional.) Configuring physical state change suppression on a FlexE interface

¡ (Optional.) Configuring dampening on a FlexE physical interface

¡ (Optional.) Configuring FEC

¡ (Optional.) Enabling loopback testing on a FlexE interface

5. Configure a FlexE logical interface

¡ (Optional.) Setting the MAC address of a FlexE logical interface

¡ (Optional.) Setting the MTU of a FlexE logical interface

¡ (Optional.) Setting the minimum available bandwidth percentage of a FlexE logical interface

¡ (Optional.) Changing the link mode of a FlexE logical interface

¡ (Optional.) Configuring jumbo frame support for a FlexE logical interface

¡ (Optional.) Configuring physical state change suppression on a FlexE interface

¡ (Optional.) Configuring storm suppression on a FlexE logical interface

¡ (Optional.)

¡ Configuring generic flow control on a FlexE logical interface

¡ (Optional.) Configuring PFC on a FlexE logical interface

¡ (Optional.) Configuring auto power-down on a FlexE logical interface

¡ (Optional.) Enabling loopback testing on a FlexE interface

¡ (Optional.) Enabling packet statistics collection on a FlexE logical subinterface

¡ (Optional.) Displaying the operating status and information of an interface

6. (Optional.) Configuring interface alarm functions

7. (Optional.) Restoring the default settings for a FlexE interface

Changing the type of an interface

About this task

The bandwidth of an interface in standard Ethernet mode is fixed, and the bandwidth of an interface is 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.

Restrictions and guidelines

You cannot change the type of a FlexE physical interface if the interface has been added to a FlexE group interface and bandwidth has been assigned to a FlexE logical interface in the group.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Change the type of the interface.

¡ Change a standard Ethernet interface to a FlexE interface.

port-type flexe

¡ Change the type of an interface from Ethernet to fine granularity FlexE.

port-type flexe-fg

¡ Change a FlexE interface to a standard Ethernet interface.

port-type ethernet

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.

‌

Creating a FlexE group interface

About this task

After you create a FlexE group interface, you can add multiple FlexE physical interfaces to the FlexE group interface and 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.

Restrictions and guidelines

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

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

Procedure

1. Enter system view.

system-view

2. Create a FlexE group interface and enter its view.

interface flexe-group interface-number

The last tier in the interface number of a FlexE group interface represents the group ID.

3. (Optional.) Configure a description of the FlexE group interface.

description text

By default, the configuration of a FlexE group interface is the interface name plus Interface (for example, FlexE-Group1/0/1 Interface).

Setting the sub-timeslot granularity

You must perform this task before setting a bandwidth less than 5 Gbps to a FlexE logical interface. Plan the sub-timeslot granularity as needed.

· If the sub-timeslot granularity is 5 Gbps, the bandwidth for a FlexE logical interface can be a multiple of 5 Gbps, for example, 5 Gbps, 10 Gbps, 15 Gbps, and so on.

· If the sub-timeslot granularity is 1 Gbps, the bandwidth for a FlexE logical interface can be 1 Gbps, 2 Gbps, 3 Gbps, 4 Gbps, 5 Gbps, or a multiple of 5 Gbps.

· If the sub-timeslot granularity is 1.25 Gbps, the bandwidth for a FlexE logical interface can be 1.25 Gbps, 2.5 Gbps, 3.75 Gbps, 5 Gbps, or a multiple of 5 Gbps.

If a FlexE logical interface on an interface module has been set with a bandwidth by using the flexe-group bandwidth command, you cannot modify the sub-timeslot granularity on the interface module.

Procedure

1. Enter system view.

system-view

2. Set the sub-timeslot granularity on an interface module.

flexe sub-time-slot granula slot slot-number subslot subslot-number { 1 | 1.25 }

By default, the sub-timeslot granularity is 5 Gbps for an interface module.

Adding a FlexE physical interface to a FlexE group interface

About this task

Perform this task so you can bind timeslots of FlexE physical interfaces in a FlexE group interface to FlexE logical interfaces as per service requirements.

Restrictions and 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.

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

· You can repeat this command to add multiple FlexE physical interfaces to a FlexE group interface. Make sure the PHY number for each FlexE physical interfaces is unique in a FlexE group interface.

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.

Procedure

1. Enter system view.

system-view

2. Enter FlexE group interface view.

interface flexe-group interface-number

3. Add a FlexE physical interface to the FlexE group interface.

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

By default, no FlexE physical interfaces exist in a FlexE group interface.

Creating a FlexE logical interface and set its bandwidth

Creating a FlexE logical interface at the granularity of 5 Gbps and configuring interface bandwidth

About this task

Perform this task 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 1/0/1, the device creates FlexE logical interface FlexE1/0/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.

Restrictions and guidelines

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.

Procedure

1. Enter system view.

system-view

2. Set the bandwidth configuration mode for FlexE logical interfaces.

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

By default, the bandwidth mode is used.

3. Enter FlexE group interface view.

interface flexe-group interface-number

4. Create a FlexE logical interface and set its bandwidth.

client client-id { bandwidth { bandwidth-value | 1 | 1.25 | 2 | 2.5 | 3 | 3.75 | 4 } | bind interface interface-type interface-number timeslot timeslot-list }

Creating a FlexE logical interface at the granularity of 10 Mbps and configuring interface bandwidth

About this task

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 and client channels.

· A FlexE-FG10G interface is a FlexE physical interface changed from a 10-GE interface. On the interface, you can create FlexE logical interfaces at the granularity of 10 Mbps.

· To allocate bandwidth at the granularity of 10 Mbps, you can create client channels in a FlexE-group interface. Then, you can create FlexE logical interfaces of smaller bandwidth in a client channel.

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 2/2/1, the system will automatically create FlexE logical interface FlexE2/2/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.

Restrictions and guidelines

For FlexE-FG10G logical interfaces on two ends of a link to communicate normally, perform the following tasks on both ends:

· For PHY-level fine granularity slices, configure the same FG client ID on the FlexE-FG10G interfaces.

· For FlexE-level fine granularity slices, perform the following tasks:

¡ Create FlexE-group interfaces with the same number.

¡ In the FlexE-group interface, configure the same client channel ID, and configure the same bandwidth allocation mode for the client channel.

¡ In the client channel, configure the same FG client ID.

For FlexE logical interfaces on two ends of a link to communicate normally, perform the following tasks on both ends:

· Create FlexE-group interfaces with the same number.

· In the FlexE-group interface, configure the same client channel ID, and configure the same bandwidth allocation mode for the client channel.

· In the client channel, configure the same client ID.

Procedure

1. Enter system view.

system-view

2. Enter FlexE-FG10G interface view or client channel view.

¡ Enter FlexE-FG10G interface view.

interface flexe-fg10g interface-number

¡ Execute the following commands to enter client channel view:

interface flexe-group interface-number

client-channel client-channel-id [ bandwidth bandwidth-value | interface interface-type interface-number timeslot timeslot-list ]

3. Configure the bandwidth allocation mode for the FlexE logical interface.

config-mode { bandwidth | sub-timeslot }

By default, the bandwidth allocation mode for a FlexE logical interface is bandwidth-based.

4. Create a FlexE logical interface and configure the interface bandwidth.

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

By default, no FlexE logical interfaces exist.

Creating a FlexE-DCN interface

About this task

With DCN enabled on a FlexE physical interface, the device automatically creates a FlexE-DCN interface numbered the same as the FlexE physical interface. A FlexE-DCN interface is used to transmit DCN management information.

Restrictions and guidelines

When you switch the type of or delete a FlexE physical interface, its FlexE-DCN interface is also deleted.

Procedure

1. Enter system view.

system-view

2. Enter FlexE physical interface view..

interface interface-type interface-number

3. Enable DCN on the FlexE physical interface.

dcn enable

4. Enter FlexE-DCN interface view.

interface flexe-dcn interface-number

Configuring basic settings of a FlexE interface

1. Enter system view.

system-view

2. Enter FlexE physical interface view, FlexE logical interface view, or FlexE-DCN interface view.

interface interface-type interface-number

3. Configure the description of the FlexE interface.

description text

By default, the description of a FlexE interface is interface-name Interface. For example, FlexE1/0/1 Interface.

4. Set the expected bandwidth of the FlexE interface.

bandwidth bandwidth-value

The default setting varies by interface type.

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.

This command is not supported on FlexE physical interfaces.

5. Bring up the FlexE interface.

undo shutdown

The default setting varies by device type.

Changing the speed mode of an interface

About this task

Suppose two interfaces on an expansion interface card operate at 50 Gbps. After you execute the switch-mode manual mode on an interface, you can execute the speed-mode 100ge command to configure the interface to operate at 100 Gbps. At the same time, the other interface will be deleted. To view the interface changes, execute the display interface brief command.

You can use the display interface command to view the operating mode of an interface.

Restrictions and guidelines

When you switch the speed of an interface, follow these restrictions and guidelines:

· If ports on an interface expansion card have been assigned to a FlexE interface group, you cannot switch the operating mode. To do that, first remove the ports from the FlexE interface group.

· If interface A on an interface expansion card operates at 50 Gbps and interface B has been assigned to a FlexE group interface, you cannot switch the operating mode of interface A to 100 Gbps. To do that, first remove interface B from the FlexE group interface.

· If an interface on an expansion interface card is a FlexE interface operating at 100 Gbps and has been assigned to a FlexE group, you cannot configure the interface to operate at 50 Gbps. To do that, first remove it from the FlexE group.

· If an interface on an expansion interface card is a FlexE interface operating at 50 Gbps and has been assigned to a FlexE group, you cannot configure the interface to operate at 100 Gbps. To do that, first remove it from the FlexE group.

Procedure (Ethernet interface)

1. Enter system view.

system-view

2. Enter 50-100-GE interface view.

interface fifty-hundredgige interface-number

3. Set the transceiver module mode for the Ethernet interface.

switch-mode manual

By default, the speed of an interface is determined by the transceiver module installed.

4. Change the speed mode of the interface between 50 Gbps and 100 Gbps.

speed-mode { 50ge | 100ge }

By default, an interface operates in 50-GE mode.

Procedure (FlexE physical interface)

1. Enter system view.

system-view

2. Enter FlexE-50-100-G interface view.

interface flexe-50-100g interface-number

3. Change the speed mode of the interface between 50 Gbps and 100 Gbps.

speed-mode { 50ge | 100ge }

By default, an interface operates at a speed of 50 Gbps.

Binding a FlexE physical interface to a FlexE logical interface for clock service hosting

About this task

FlexE physical interfaces cannot process protocol messages for the clock service. To deploy the clock service (such as PTP) on a FlexE physical interface, you must bind the FlexE physical interface to a FlexE logical interface. For more information about PTP, see Network Management and Monitoring Configuration Guide.

Restrictions and guidelines

For the clock service to correctly operate between two devices, set the same client ID for the interconnecting FlexE logical interfaces at both ends.

If the bound FlexE logical interface fails, the clock service will be affected. To resolve the issue, bind the FlexE physical interface to another FlexE logical interface. During the rebinding process, the clock service is unavailable.

Procedure

1. Enter system view.

system-view

2. Enter FlexE physical interface view.

interface interface-type interface-number

3. Bind the FlexE physical interface to a FlexE logical interface for clock service hosting.

clock binding interface interface-type interface-number

By default, a FlexE physical interface is not bound to any FlexE logical interface for clock service hosting.

Setting the MAC address of a FlexE logical interface

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

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

3. Set the MAC address of the FlexE logical interface.

mac-address mac-address

The default setting varies by device model.

Setting the MTU of a FlexE logical interface

Restrictions and guidelines

The maximum transmission unit (MTU) of a FlexE logical interface affects the fragmentation and reassembly of IP packets on the interface. Typically, you do not need to modify the MTU of a FlexE logical interface.

Procedure

1. Enter system view.

system-view

2. Enter FlexE interface view.

¡ Enter FlexE logical interface view.

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

¡ Enter FlexE-DCN interface view.

interface flexe-dcn interface-number

3. Set the MTU of the FlexE logical interface.

mtu size

By default, the MTU of a FlexE logical interface is 1500 bytes.

Setting the minimum available bandwidth percentage of a FlexE logical interface

About this task

The available bandwidth percentage of a FlexE logical interface affects the physical status of the interface.

· If the available bandwidth percentage of the interface drops below the minimum available bandwidth percentage, the interface goes down.

· If the available bandwidth percentage of the interface reaches or exceeds the minimum available bandwidth percentage, the interface comes up.

Restrictions and guidelines

To display the minimum available bandwidth percentage of a FlexE logical interface, use the display interface command.

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

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

3. Set the minimum available bandwidth percentage of the FlexE logical interface.

flexe min-bandwidth-percent percent

By default, the minimum available bandwidth percentage is 0% for a FlexE logical interface.

Changing the link mode of a FlexE logical interface

About this task

A FlexE logical interface can operate at one of the following link 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.

Restrictions and guidelines

After you change the link mode of a FlexE logical interface, all commands (except the shutdown command) on the FlexE logical interface are restored to their defaults in the new link mode.

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Change the link mode of the FlexE logical interface.

port link-mode { bridge | route }

The default setting varies by device model.

Configuring jumbo frame support for a FlexE logical interface

About this task

Jumbo frames are frames larger than a device-specific size and are typically received by a FlexE logical interface during high-throughput data exchanges, such as file transfers.

The FlexE logical interface processes jumbo frames in the following ways:

· When the FlexE logical interface is configured to deny jumbo frames (by using the undo jumboframe enable command), the FlexE logical interface discards jumbo frames.

· When the FlexE logical interface is configured with jumbo frame support, the FlexE logical interface performs the following operations:

¡ Processes jumbo frames within the specified length.

¡ Discards jumbo frames that exceed the specified length.

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Configure jumbo frame support.

jumboframe enable [ size ]

By default, the device allows jumbo frames within the specified length to pass through all FlexE logical interfaces. The maximum length of jumbo frames varies by device model.

Configuring physical state change suppression on a FlexE interface

About this task

The physical link state of a FlexE interface is either up or down. Each time the physical link of an interface comes up or goes down, the interface immediately reports the change to the CPU. The CPU then performs the following operations:

· Notifies the upper-layer protocol modules (such as routing and forwarding modules) of the change for guiding packet forwarding.

· Automatically generates traps and logs to inform users to take the correct actions.

To prevent frequent physical link flapping from affecting system performance, configure physical state change suppression. You can configure this feature to suppress only link-down events, only link-up events, or both. If an event of the specified type still exists when the suppression interval expires, the system reports the event to the CPU.

Restrictions and guidelines

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 on a FlexE physical interface, the most recent configuration takes effect.

Procedure

1. Enter system view.

system-view

2. Enter FlexE physical interface view or FlexE logical interface view.

interface flexe interface-number

3. Configure physical state change suppression on the FlexE interface.

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

By default, the device reports the physical state change of a FlexE interface to the CPU immediately.

Configuring dampening on a FlexE physical interface

About this task

The interface dampening feature uses an exponential decay mechanism to prevent excessive interface flapping events from adversely affecting routing protocols and routing tables in the network. Suppressing interface state change events protects the system resources.

If an interface is not dampened, its state changes are reported. For each state change, the system also generates an SNMP trap and log message.

After a flapping interface is dampened, it does not report its state changes to the CPU. For state change events, the interface only generates SNMP trap and log messages.

Parameters

· Penalty—The interface has an initial penalty of 0. When the interface flaps, the penalty increases by 1000 for each down event until the ceiling is reached. It does not increase for up events. When the interface stops flapping, the penalty decreases by half each time the half-life timer expires until the penalty drops to the reuse threshold.

· Ceiling—The penalty stops increasing when it reaches the ceiling.

· Suppress-limit—The accumulated penalty that triggers the device to dampen the interface. In dampened state, the interface does not report its state changes to the CPU. For state change events, the interface only generates SNMP traps and log messages.

· Reuse-limit—When the accumulated penalty decreases to this reuse threshold, the interface is not dampened. Interface state changes are reported to the upper layers. For each state change, the system also generates an SNMP trap and log message.

· Decay—The amount of time (in seconds) after which a penalty is decreased.

· Max-suppress-time—The maximum amount of time the interface can be dampened. If the penalty is still higher than the reuse threshold when this timer expires, the penalty stops increasing for down events. The penalty starts to decrease until it drops below the reuse threshold.

· When configuring the dampening command, follow these rules to set the values mentioned above:

· The ceiling is equal to 2(Max-suppress-time/Decay) × reuse-limit. It is not user configurable.

· The configured suppress limit is lower than or equal to the ceiling.

· The ceiling is lower than or equal to the maximum suppress limit supported.

Figure 1 shows the change rule of the penalty value. The lines t0 and t2 indicate the start time and end time of the suppression, respectively. The period from t0 to t2 indicates the suppression period, t0 to t1 indicates the max-suppress-time, and t1 to t2 indicates the complete decay period.

Figure 1 Change rule of the penalty value

‌

Restrictions and guidelines

The link-delay and dampening commands are mutually exclusive on an interface.

The dampening 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 upper-layer protocols.

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

Procedure

1. Enter system view.

system-view

2. Enter FlexE physical interface view.

interface interface-type interface-number

3. Enable dampening on the interface.

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

By default, interface dampening is disabled on Ethernet interfaces.

Configuring FEC

About this task

The forward error correction (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.

Restrictions and guidelines

The BASE-R FEC mode is not supported on 100GE, 50-100GE, FlexE-50-100GE, and FlexE-100G interfaces.

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

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Set the FEC mode of the interface.

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

The default for this command varies by device model.

Configuring storm suppression on a FlexE logical interface

About this task

The storm suppression feature ensures that the size of a particular type of traffic (broadcast, multicast, or unknown unicast traffic) does not exceed the threshold on an interface. When the broadcast, multicast, or unknown unicast traffic on the interface exceeds this threshold, the system discards packets until the traffic drops below this threshold.

Restrictions and guidelines

The configured suppression threshold value in pps or kbps might be converted into a multiple of the step value supported by the chip. As a result, the effective suppression threshold might be different from the configured one. For information about the suppression threshold that takes effect, see the prompt on the device.

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Enable broadcast suppression and set the broadcast suppression threshold on the FlexE logical interface.

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

By default, broadcast suppression is disabled on a FlexE logical interface.

4. Enable multicast suppression and set the multicast suppression threshold on the FlexE logical interface.

multicast-suppression { ratio | pps max-pps | kbps max-kbps } [ unknown ]

By default, multicast suppression is disabled on a FlexE logical interface.

5. Enable unknown unicast suppression and set the unknown unicast suppression threshold on the FlexE logical interface.

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

By default, unknown unicast suppression is disabled on a FlexE logical interface.

Configuring generic flow control on a FlexE logical interface

About this task

To avoid dropping packets on a link, you can enable generic flow control at both ends of the link. When traffic congestion occurs at the receiving end, the receiving end sends a flow control (Pause) frame to ask the sending end to suspend sending packets. Generic flow control includes the following types:

· TxRx-mode generic flow control—Enabled by using the flow-control command. With TxRx-mode generic flow control enabled, an interface can both send and receive flow control frames:

¡ When congestion occurs, the interface sends a flow control frame to its peer.

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

· Rx-mode generic flow control—Enabled by using the flow-control receive enable command. With Rx-mode generic flow control enabled, an interface can receive flow control frames, but it cannot send flow control frames:

¡ When congestion occurs, the interface cannot send flow control frames to its peer.

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

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

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Enable generic flow control.

¡ Enable TxRx-mode generic flow control.

flow-control

¡ Enable Rx-mode generic flow control.

flow-control receive enable

By default, generic flow control is disabled on a FlexE logical interface.

Configuring PFC on a FlexE logical interface

About this task

When congestion occurs in the network, the local device notifies the peer to stop sending packets carrying the specified 802.1p priority if all of the following conditions exist:

· Both the local end and the remote end have priority-based flow control (PFC) enabled.

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

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

· The local end receives a packet carrying the specified 802.1p priority.

The state of the PFC feature is determined by the PFC configuration on the local end and on the peer end. In Table 1:

· The first row lists the PFC configuration on the local interface.

· The first column lists the PFC configuration on the peer.

· The Enabled and Disabled fields in other cells are possible negotiation results.

Make sure all interfaces that a data flow passes through have the same PFC configuration.

Table 1 PFC configurations and negotiation results

Local (right) Peer (below)	enable	auto	Default
enable	Enabled	Enabled.	Disabled
auto	Enabled	· Enabled if negotiation succeeds. · Disabled if negotiation fails.	Disabled
Default	Disabled	Disabled.	Disabled

Restrictions and guidelines

To avoid packet loss, apply the same PFC configuration to all interfaces that the packets pass through.

If you do not enable PFC on an interface, the interface can receive but cannot process PFC pause frames. For PFC to take effect, you must enable PFC on both ends.

If you configure the flow control or flow-control receive enable command on a PFC-enabled interface, the following rules apply:

· The PFC configuration takes effect.

· The configuration of the flow control or flow-control receive enable command is ignored.

· The flow control or flow-control receive enable command takes effect on the interface only when PFC is disabled on it.

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Enable PFC in auto mode or forcibly on the FlexE logical interface.

priority-flow-control { auto | enable }

By default, PFC is disabled.

4. Enable PFC for 802.1p priorities.

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

By default, PFC is disabled for all 802.1p priorities.

Configuring auto power-down on a FlexE logical interface

About this task

When a FlexE logical interface with auto power-down enabled has been down for a certain period of time, both of the following events occur:

· The device automatically stops supplying power to the FlexE logical interface.

· The FlexE logical interface enters the power save mode.

The time period depends on the chip specifications and is not configurable.

When the FlexE logical interface comes up, both of the following events occur:

· The device automatically restores power supply to the FlexE logical interface.

· The FlexE logical interface restores to its normal state

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Enable auto power-down on the FlexE logical interface.

port auto-power-down

By default, auto power-down is disabled on a FlexE logical interface.

Setting the statistics polling interval on a FlexE logical interface

About this task

The statistics polling interval defines the interval at which the device collects packet statistics on a FlexE logical interface. To display the interface statistics collected in the last statistics polling interval, use the display interface command. To clear the interface statistics, use the reset counters interface command.

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Set the statistic polling interval on the FlexE logical interface.

flow-interval interval

The default setting varies by device model. For more information, see the command reference.

Enabling loopback testing on a FlexE interface

About this task

Use this feature to determine whether a FlexE interface works correctly.

Loopback testing includes the following types:

· Internal loopback testing—Tests the device where the FlexE interface resides. The FlexE interface sends outgoing packets back to the local device. If the device fails to receive the packets, the device fails.

· External loopback testing—Tests the inter-device link. The FlexE interface sends incoming packets back to the remote device. If the remote device fails to receive the packets, the inter-device link fails.

Restrictions and guidelines

After you enable this feature on a FlexE interface, the interface does not forward data traffic.

Procedure

1. Enter system view.

system-view

2. Enter FlexE physical interface view or FlexE logical interface view.

interface interface-type interface-number

3. Enable loopback testing on the interface.

loopback { external | internal }

Support for the external and internal keywords depends on the device model.

Enabling packet statistics collection on a FlexE logical subinterface

1. Enter system view.

system-view

2. Enter FlexE logical subinterface view.

interface flexe interface-number.subnumber

3. Enable packet statistics collection on the subinterface.

traffic-statistic enable

By default, packet statistics collection is disabled on an subinterface.

4. (Optional.) Display the FlexE logical subinterface traffic statistics.

display interface

display counters

The Input and Output fields in the display interface command output display the FlexE logical subinterface traffic statistics.

Configuring interface alarm functions

About interface alarm functions

With the interface alarm functions enabled, when the number of 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 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.

Restrictions and guidelines

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

· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)

· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)

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

An interface that is shut down because of error packet alarms cannot automatically recover. To bring up the interface, execute the undo shutdown command on the interface.

Enabling interface alarm functions

1. Enter system view.

system-view

2. Enable alarm functions for the interface monitoring module.

By default, all alarm functions are enabled on interfaces.

Setting CRC error packet alarm parameters

1. Enter system view.

system-view

2. Set global CRC error packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for CRC error packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set CRC error packet alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global CRC error packet alarm parameters.

Setting input error packet alarm parameters

1. Enter system view.

system-view

2. Set global input error packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for input error packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set input error packet alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global input error packet alarm parameters.

Setting output error packet alarm parameters

1. Enter system view.

system-view

2. Set global output error packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for output error packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set output error packet alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global output error packet alarm parameters.

Setting inbound bandwidth usage alarm parameters

1. Enter system view.

system-view

2. Set global inbound bandwidth usage alarm parameters.

ifmonitor input-usage slot slot-number high-threshold high-value low-threshold low-value

By default, the upper threshold is 90% and the lower threshold is 80%.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set inbound bandwidth usage alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global inbound bandwidth usage alarm parameters.

Setting outbound bandwidth usage alarm parameters

1. Enter system view.

system-view

2. Set global outbound bandwidth usage alarm parameters.

ifmonitor output-usage slot slot-number high-threshold high-value low-threshold low-value

By default, the upper threshold is 90% and the lower threshold is 80%.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set outbound bandwidth usage alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global outbound bandwidth usage alarm parameters.

Setting incoming pause frame alarm parameters

1. Enter system view.

system-view

2. Set global incoming pause frame alarm parameters.

ifmonitor rx-pause slot slot-number high-threshold high-value low-threshold low-value interval interval

By default, the upper threshold is 500, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for incoming pause frames.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set incoming pause frame alarm parameters on the FlexE logical interface.

port ifmonitor rx-pause high-threshold high-value low-threshold low-value interval interval

By default, a FlexE logical interface uses the global incoming pause frame alarm parameters.

Setting outgoing pause frame alarm parameters

1. Enter system view.

system-view

2. Set global outgoing pause frame alarm parameters.

ifmonitor tx-pause slot slot-number high-threshold high-value low-threshold low-value interval interval

By default, the upper threshold is 500, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for outgoing pause frames.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set outgoing pause frame alarm parameters on the FlexE logical interface.

port ifmonitor tx-pause high-threshold high-value low-threshold low-value interval interval

By default, a FlexE logical interface uses the global outgoing pause frame alarm parameters.

Setting SDH error packet alarm parameters

1. Enter system view.

system-view

2. Set global SDH error packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for SDH error packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set SDH error packet alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global SDH error packet alarm parameters.

Setting SDH-B1 error packet alarm parameters

1. Enter system view.

system-view

2. Set global SDH-B1 error packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for SDH-B1 error packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set SDH-B1 error packet alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global SDH-B1 error packet alarm parameters.

Setting SDH-B2 error packet alarm parameters

1. Enter system view.

system-view

2. Set global SDH-B2 error packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for SDH-B2 error packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Set SDH-B2 error packet alarm parameters on the FlexE logical interface.

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

By default, a FlexE logical interface uses the global SDH-B2 error packet alarm parameters.

Configuring giant packet alarm parameters

1. Enter system view.

system-view

2. Configure global giant packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for giant packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Configure giant packet alarm parameters for the interface.

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

By default, an interface uses the global giant packet alarm parameters.

Configuring runt packet alarm parameters

1. Enter system view.

system-view

2. Configure global runt packet alarm parameters.

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

By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for runt packets.

3. Enter FlexE logical interface view.

interface flexe interface-number

4. Configure runt packet alarm parameters for the interface.

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

By default, an interface uses the global runt packet alarm parameters.

Displaying the operating status and information of an interface

About this task

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.

Procedure

1. Enter system view.

system-view

2. Enter FlexE logical interface view.

interface flexe interface-number

3. Display the operating status and information of an interface.

display this interface

Restoring the default settings for a FlexE interface

CAUTION:

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

This feature 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 check for these commands and perform their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message to resolve the problem.

Procedure

1. Enter system view.

system-view

2. Enter FlexE physical interface view, FlexE logical interface view, FlexE-DCN interface view, or FlexE group interface view.

interface interface-type interface-number

3. Restore the default settings for the interface.

default

Display and maintenance commands for FlexE interfaces

Execute display commands in any view.

Task	Command
Display interface information.	display interface [ interface-type [ interface-number \| interface-number.subnumber ] ] [ brief [ description \| down ] ]

03-Interface Configuration Guide

Configuring FlexE interfaces

About FlexE interfaces

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure (Ethernet interface)

Procedure (FlexE physical interface)

About this task

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Parameters

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Procedure

Display and maintenance commands for FlexE interfaces

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