The Switch Series supports Ethernet interfaces, management Ethernet interfaces, Console interfaces, and USB interfaces. For the interface types and the number of interfaces supported by a switch model, see ‌the hardware manuals.

This chapter describes how to configure management Ethernet interfaces and Ethernet interfaces.

Configuring a management Ethernet interface

About this task

You can connect a management Ethernet interface to a PC for software loading and system debugging, or connect it to a remote NMS for remote system management.

Procedure

1. Enter system view.

system-view

2. Enter management Ethernet interface view.

interface M-GigabitEthernet interface-number

3. (Optional.) Set the interface description.

description text

The default setting is M-GigabitEthernet0/0/0 Interface.

4. (Optional.) Set the duplex mode for the management Ethernet interface.

duplex { auto | full | half }

By default, the duplex mode is auto for a management Ethernet interface.

5. (Optional.)_Set the speed for the management Ethernet interface.

speed { 10 | 100 | 1000 | auto }

By default, the speed is auto for a management Ethernet interface.

6. (Optional.) Shut down the interface.

shutdown

By default, the management Ethernet interface is up.

CAUTION:

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

‌

Ethernet interface naming conventions

The Ethernet interfaces are named in the format of interface type A/B/C. The letters that follow the interface type represent the following elements:

· A—Device ID, which is fixed at 1.

· B—Card slot number.

· C—Port index.

Restrictions and guidelines: Ethernet interface configuration

Changing the link type of an Ethernet interface, splitting an interface, or combining breakout interfaces will cause global packet loss on the device if the following data buffer configuration exists on the device:

· buffer egress cell queue shared (setting the maximum size of the shared area that the queue can use)

· buffer service-pool shared (setting the size of the shared area that the service pool can use)

For more information about data buffer configuration, see ACL and QoS Configuration Guide.

Configuring common Ethernet interface settings

This section describes the settings common to Layer 2 Ethernet interfaces, Layer 3 Ethernet interfaces, and Layer 3 Ethernet subinterfaces. For more information about the settings specific to Layer 2 Ethernet interfaces, see "Configuring a Layer 2 Ethernet interface." For more information about the settings specific to Layer 3 Ethernet interfaces or subinterfaces, see "Configuring a Layer 3 Ethernet interface or subinterface."

Setting the operating mode of an S9820-8C switch

About this task

When an S9820-8C switch operates in flex mode, interfaces on an LSWM116H subcard can be split. Interfaces on each LSWM116H subcard can be split into 18 × 10G/25G breakout interfaces. Interfaces on the whole device can be split into up to 144 × 10G/25G breakout interfaces.

To have the flex mode configuration take effect, you must save the configuration and then reboot the device.

Restrictions and guidelines

When an S9820-8C switch operates in non-flex mode, interfaces on an LSWM116H expansion card (subcard) cannot be split.

When an S9820-8C switch operates in flex mode, it supports only LSWM116H expansion cards.

When an S9820-8C switch operates in flex mode, interfaces on an LSWM116H expansion card can be split as shown in Table 1.

Table 1 LSWM116H expansion card interface splitting description

Expansion card slots	Numbers of interfaces that can be split on the expansion card	Numbers of interfaces deleted after an interface on the same expansion card is split
Subslots 1 through 4	3	1, 2, 6
	4	5, 7, 9
	8 (You can split the interface only into two breakout interfaces. For example, HundredGigE 1/1/8 can be split into Twenty-FiveGigE 1/1/8:1 and Twenty-FiveGigE 1/1/8:2 or Ten-GigabitEthernet 1/1/8:1 and Ten-GigabitEthernet 1/1/8:2.)	12
	10	11
	13	14, 15, 16
Subslots 5 through 8	3	1, 2, 6
	4 (You can split the interface only into two breakout interfaces. For example, HundredGigE 1/5/4 can be split into Twenty-FiveGigE 1/5/4:1 and Twenty-FiveGigE 1/5/4:2 or Ten-GigabitEthernet 1/5/4:1 and Ten-GigabitEthernet 1/5/4:2.)	5
	8	10, 11, 12
	9	7
	13	14, 15, 16

When you are splitting interface 8 or 10 on a card in one of subslots 1 through 4, the following restrictions apply to interfaces 8, 10, 11, and 12:

· To split an interface into 25G breakout interfaces, make sure all the other interfaces operate at 100 Gbps or 25 Gbps, either by installing 100G transceiver modules or executing the speed 100000 command . If another interface among the four interfaces is split, the interface must be split into 25G breakout interfaces. If the preceding conditions are not met, the system prompts that the split operation is not supported.

· To split an interface into 10G breakout interfaces, make sure all the other interfaces operate at 40 Gbps or 10 Gbps, either by installing 40G transceiver modules or executing the speed 40000 command . If another interface among the four interfaces is split, the interface must be split into 10G breakout interfaces. If the preceding conditions are not met, the system prompts that the split operation is not supported.

· When no transceiver module is inserted into an interface, the interface operates at 100 Gbps by default. To split the interface into 10G breakout interfaces, execute the speed 40000 command on the other three interfaces. To split an interface into 25G breakout interfaces, make sure the other three interfaces do not have the speed 40000 command executed. If the preceding conditions are not met, the system prompts that the split operation is not supported.

· If you have split an interface into 25G breakout interfaces and execute the speed 40000 command on the other two interfaces, the command does not take effect in the hardware and the interfaces will not come up.

· If you have split an interface into 10G breakout interfaces and execute the speed 100000 command on the remaining two interfaces, the interfaces can come up as 100G interfaces. However, do not perform this operation, which might cause the device to operate abnormally.

· When you are splitting interface 4 or 9 on a card in one of subslots 5 through 8, the similar restrictions apply to interfaces 4, 9, 5, and 7.

Procedure

7. Enter system view.

system-view

8. Configure the device to operate in flex mode.

hardware-resource flex-mode { disable | enable }

9. Save the configuration.

save

10. Return to user view.

quit

11. Reboot the device to make the mode take effect.

reboot

Splitting a 100-GE interface and combining 10-GE breakout interfaces

About this task

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

If you need higher bandwidth on a single interface, you can combine the multiple 10-GE breakout interfaces into a 100-GE interface.

Restrictions and guidelines for 100-GE interface splitting and 10-GE breakout interface combining

A 100-GE interface split into multiple 10-GE breakout interfaces must use a dedicated cable. After you combine the multiple 10-GE breakout interfaces, replace the dedicated cable with a dedicated 1-to-1 cable or a 100-GE transceiver module. For more information about the cable or transceiver module, see the installation guides.

After you configure this feature, you do not need to reboot the device. To view the breakout interfaces, execute the display interface brief command.

As shown in Table 1, when you split an interface on an LSWM116H expansion card, the other interfaces on the expansion card will be deleted. If those interfaces to be deleted have the following configuration, splitting is not allowed:

· Service loopback group member.

· Reflector port for mirroring.

· Forcibly bringing up a fiber port.

For example, when you split interface 3, if interface 1, 2, or 6 has the above configuration, the splitting will fail.

Splitting a 100-GE interface into multiple 10-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 100-GE interface view.

interface hundredgige interface-number

3. Split the 100-GE interface into multiple 10-GE breakout interfaces.

using tengige

By default, a 100-GE interface is not split and operates as a single interface.

Combining multiple 10-GE breakout interfaces into a 100-GE interface

1. Enter system view.

system-view

2. Enter the view of any 10-GE breakout interface.

interface ten-gigabitethernet interface-number

3. Combine the multiple 10-GE breakout interfaces into a 100-GE interface.

using hundredgige

By default, a 10-GE breakout interface operates as a single interface.

Splitting a 100-GE interface and combining 25-GE breakout interfaces

About this task

You can use a 100-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 100-GE interface into four 25-GE breakout interfaces. The 25-GE breakout interfaces support the same configuration and attributes as common 25-GE interfaces, except that they are numbered differently.

For example, you can split 100-GE interface HundredGigE 1/1/10 into four 25-GE breakout interfaces Twenty-FiveGigE 1/1/10:1 through Twenty-FiveGigE 1/1/10:4.

If you need higher bandwidth on a single interface, you can combine the four 25-GE breakout interfaces into a 100-GE interface.

Restrictions and guidelines for 100-GE interface splitting and 25-GE breakout interface combining

A 100-GE interface split into four 25-GE breakout interfaces must use a dedicated 1-to-4 cable. After you combine the four 25-GE breakout interfaces, replace the dedicated 1-to-4 cable with a dedicated 1-to-1 cable or a 100-GE transceiver module. For more information about the cable or transceiver module, see the installation guides.

After you configure this feature, you do not need to reboot the device. To view the breakout interfaces, execute the display interface brief command.

· Service loopback group member.

· Reflector port for mirroring.

· Forcibly bringing up a fiber port.

For example, when you split interface 3, if interface 1, 2, or 6 has the above configuration, the splitting will fail.

Splitting a 100-GE interface into four 25-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 100-GE interface view.

interface hundredgige interface-number

3. Split the 100-GE interface into four 25-GE breakout interfaces.

using twenty-fivegige

By default, a 100-GE interface is not split and operates as a single interface.

Combining four 25-GE breakout interfaces into a 100-GE interface

1. Enter system view.

system-view

2. Enter the view of any 25-GE breakout interface.

interface twenty-fivegige interface-number

3. Combine the four 25-GE breakout interfaces into a 100-GE interface.

using hundredgige

By default, a 25-GE breakout interface operates as a single interface.

Splitting a 400-GE interface and combining 100-GE breakout interfaces

About this task

You can use a 400-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 400-GE interface into two 100-GE breakout interfaces. The 100-GE breakout interfaces support the same configuration and attributes as common 100-GE interfaces, except that they are numbered differently.

For example, you can split 400-GE interface FourHundredGigE1/0/1 into two 100-GE breakout interfaces HundredGigE1/0/1:1 and HundredGigE1/0/1:2.

If you need higher bandwidth on a single interface, you can combine the 100-GE breakout interfaces into a 400-GE interface.

Restrictions and guidelines for 400-GE interface splitting and 100-GE breakout interface combining

After configuring this feature, you do not need to reboot the device. To view the breakout interfaces, execute the display interface brief command.

Splitting a 400-GE interface into two 100-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 400-GE interface view.

interface fourhundredgige interface-number

3. Split the 400-GE interface into two 100-GE breakout interfaces.

using hundredgige mode 2-channel

By default, a 400-GE interface is not split and operates as a single interface.

Combining two 100-GE breakout interfaces into a 400-GE interface

1. Enter system view.

system-view

2. Enter the view of any 100-GE breakout interface.

interface hundredgige interface-number

3. Combine the two 100-GE breakout interfaces into a 400-GE interface.

using fourhundredgige

By default, a 400-GE interface operates as a single interface.

Splitting a 400-GE interface and combining 200-GE breakout interfaces

About this task

You can use a 400-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 400-GE interface into two 200-GE breakout interfaces. The 200-GE breakout interfaces support the same configuration and attributes as common 200-GE interfaces, except that they are numbered differently.

For example, you can split 400-GE interface FourHundredGigE 1/0/1 into two 200-GE breakout interfaces TwoHundredGigE 1/0/1:1 and TwoHundredGigE 1/0/1:2.

If you need higher bandwidth on a single interface, you can combine the two 200-GE breakout interfaces into a 400-GE interface.

Restrictions and guidelines for 400-GE interface splitting and 200-GE breakout interface combining

After configuring this feature, you do not need to reboot the device. To view the breakout interfaces, execute the display interface brief command.

Splitting a 400-GE interface into two 200-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 400-GE interface view.

interface fourhundredgige interface-number

3. Split the 400-GE interface into two 200-GE breakout interfaces.

using twohundredgige

By default, a 400-GE interface is not split and operates as a single interface.

Combining two 200-GE breakout interfaces into a 400-GE interface

1. Enter system view.

system-view

2. Enter the view of any 200-GE breakout interface.

interface twohundredgige interface-number

3. Combine the two 200-GE breakout interfaces into a 400-GE interface.

using fourhundredgige

By default, a 200-GE breakout interface operates as a single interface.

Configuring basic settings of an Ethernet interface

About this task

You can configure an Ethernet interface to operate in one of the following duplex modes:

· Full-duplex mode—The interface can send and receive packets simultaneously.

· Autonegotiation mode—The interface negotiates a duplex mode with its peer.

You can set the speed of an Ethernet interface or enable it to automatically negotiate a speed with its peer.

Restrictions and guidelines

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

Procedure

1. Enter system view.

system-view

2. Configure the device to display the default description for interfaces when it displays the interface information.

interface default-description output

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Set the description for the Ethernet interface.

description text

The default setting is interface-name Interface. For example, HundredGigE1/1/1 Interface.

5. Set the duplex mode for the Ethernet interface.

duplex { auto | full }

By default, the duplex mode is auto for Ethernet interfaces.

6. Set the speed for the Ethernet interface.

speed { 40000 | 100000 | 200000 | 400000 | auto }

By default, an Ethernet interface negotiates a speed with its peer.

7. Set the expected bandwidth for the Ethernet interface.

bandwidth bandwidth-value

By default, the expected bandwidth (in kbps) is the interface baud rate divided by 1000.

8. Bring up the Ethernet interface.

undo shutdown

By default, Ethernet interfaces are in up state.

Configuring basic settings of an Ethernet subinterface

About this task

By default, a Layer 3 Ethernet subinterface processes packets for only the VLAN whose ID is the same as the subinterface number.

Restrictions and guidelines for Ethernet subinterface basic settings

Procedure

1. Enter system view.

system-view

2. Configure the device to display the default description for interfaces when it displays the interface information.

interface default-description output

3. Create an Ethernet subinterface.

interface interface-type interface-number.subnumber

4. Set the description for the Ethernet subinterface.

description text

The default setting is interface-name Interface. For example, HundredGigE1/1/1.1 Interface.

5. Set the expected bandwidth for the Ethernet subinterface.

bandwidth bandwidth-value

By default, the expected bandwidth (in kbps) is the interface baud rate divided by 1000.

6. Bring up the Ethernet subinterface.

undo shutdown

By default, Ethernet subinterfaces are in up state.

Configuring the link mode of an Ethernet interface

About this task

Interfaces on the device can operate either as Layer 2 or Layer 3 Ethernet interfaces. You can use commands to set the link mode to bridge or route.

Restrictions and guidelines

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Configure the link mode of the Ethernet interface.

port link-mode { bridge | route }

By default, all Ethernet interfaces on the device operate in bridge mode.

CAUTION:

After you change the link mode of an Ethernet interface, all commands (except the description, duplex, jumboframe enable, speed, shutdown commands) on the Ethernet interface are restored to their defaults in the new link mode.

‌

Configuring jumbo frame support

About this task

Jumbo frames are frames larger than 1536 bytes and are typically received by an Ethernet interface during high-throughput data exchanges, such as file transfers.

The Ethernet interface processes jumbo frames in the following ways:

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

· When the Ethernet interface is configured with jumbo frame support, the Ethernet 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 Ethernet interface view.

interface interface-type interface-number

3. Configure jumbo frame support.

jumboframe enable [ size ]

By default, the device allows jumbo frames within 9416 bytes to pass through.

If you set the size argument multiple times, the most recent configuration takes effect.

Configuring physical state change suppression on an Ethernet interface

About this task

The physical link state of an Ethernet 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

Do not enable this feature on an interface that has RRPP, spanning tree protocols, or Smart Link enabled.

You can configure different suppression intervals for link-up and link-down events.

If you execute the link-delay command multiple times on an interface, the following rules apply:

· You can configure the suppression intervals for link-up and link-down events separately.

· If you configure the suppression interval multiple times for link-up or link-down events, the most recent configuration takes effect.

The link-delay, dampening, and port link-flap protect enable commands are mutually exclusive on an Ethernet interface.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Configure physical state change suppression.

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

By default, each time the physical link of an interface goes up or comes down, the interface immediately reports the change to the CPU.

Configuring dampening on an Ethernet 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 dampening, link-delay, and port link-flap protect enable 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 Ethernet 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.

Enabling link flapping protection on an interface

About this task

Link flapping on an interface changes network topology and increases the system overhead. For example, in an active/standby link scenario, when interface status on the active link changes between UP and DOWN, traffic switches between active and standby links. To solve this problem, configure this feature on the interface.

With this feature enabled on an interface, when the interface goes down, the system enables link flapping detection. During the link flapping detection interval, if the number of detected flaps reaches or exceeds the link flapping detection threshold, the system shuts down the interface.

When a port is shut down automatically by a feature, the device starts a port status detection timer. When the timer expires, the device restores the port status to its actual physical status automatically.

Restrictions and guidelines

This feature takes effect only if it is configured in both the system view and interface view.

An interface can automatically come up only when the down-auto-recovery keyword is specified in both system view and the view of that interface.

When you configure this feature on an interface, how link flapping protection is triggered depends on the parameters specified:

· If you specify level-1 link flapping protection parameters but do not specify level-2 parameters, link flapping protection will be triggered and the interface will be shut down when the level-1 link flapping protection conditions are met.

· If you specify both level-1 and level-2 link flapping protection parameters, link flapping protection will be triggered and the interface will be shut down when either of level-1 and level-2 link flapping protection conditions are met.

The dampening, link-delay, and port link-flap protect enable commands are mutually exclusive on an Ethernet interface.

To bring up an interface that has been shut down by link flapping protection, execute the undo shutdown command.

In the display interface command output, the Link-Flap DOWN value of the Current state field indicates that the interface has been shut down by link flapping protection.

If you change the timer setting during port detection, the device compares the new setting (T1) with the time that elapsed since the port was shut down (T).

· If T < T1, the port will be brought up after T1 – T seconds.

· If T ≥ T1, the port is brought up immediately.

For example, the timer setting is 30 seconds. If you change it to 10 seconds 2 seconds after the port is shut down, the port will come up 8 seconds later. If you change the timer setting to 2 seconds 10 seconds after the port is shut down, the port comes up immediately.

Procedure

1. Enter system view.

system-view

2. Enable link flapping protection globally.

link-flap protect enable [ down-auto-recovery ]

By default, link flapping protection is disabled globally.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Enable link flapping protection on the Ethernet interface.

port link-flap protect enable [ down-auto-recovery ] [ interval interval | threshold threshold ] * [ second-interval second-interval second-threshold second-threshold ]

By default, link flapping protection is disabled on an Ethernet interface.

5. Set the port status detection timer for the ports that are shut down by the link flapping protection feature.

shutdown-interval [ link-flap ] interval

By default, the timer is 30 seconds.

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

This feature is supported only on 25-GE split interfaces, 100-GE interfaces, and 100-GE split interfaces.

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

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Set the FEC mode of the Ethernet interface.

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

By default, the FEC mode for the interface is autonegotiation.

Configuring FEC bypass

About this task

With FEC bypass disabled, when an interface continuously receives three or more packets that it cannot process, the device will shut down and then bring up the interface to fix the interface. However, there are many possible packet error reasons. If you are sure that the interface is not faulty, you do not need to fix the interface. To avoid service interruption in this case, you can enable this feature on the interface to prevent the device from shutting down and bringing up the interface.

Restrictions and guidelines

This feature is supported only on 25-GE split interfaces, 100-GE interfaces, and 100-GE split interfaces.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Configure FEC bypass.

port fec bypass { disable | enable }

By default, FEC bypass is disabled.

Configuring link compensation

About this task

As the signal transmission rate or frequency increases, high frequency components in signals attenuate more severely. For signal transmission performance, common signal compensation technologies such as pre-emphasis and equalization are introduced. Pre-emphasis amplifies high frequency components but increases the probability of crosstalk. Equalization is introduced to filter out high frequency crosstalk on the receiving end.

Link compensation enables the sending and receiving ends to exchange pre-emphasis and equalization parameters through frames. This feature improves the performance of pre-emphasis and equalization.

Restrictions and guidelines

This feature is supported only on 25-GE interfaces connected through copper cables.

You must enable or disable link compensation on both interfaces of a link.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Configure link compensation on the interface.

port training { disable | enable }

By default, link compensation is disabled on an interface.

Configuring generic flow control on an Ethernet 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.

Restrictions and guidelines

To implement flow control, configure flow control on each interface that the traffic passes through.

When you enable or disable flow control on the following types of interfaces, the interfaces might flap:

· Copper ports.

· Fiber ports with the DAC cables installed.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type 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 an Ethernet interface.

Setting the statistics polling interval

About this task

By setting the statistics polling interval, you can collect statistics of packets and analyze packets at the specified interval. Based on the interface traffic statistics, you can take traffic control measures promptly to avoid network congestion and service interruption.

· When network congestion is detected, you can set the statistics polling interval to be smaller than 300 seconds (30 seconds when congestion deteriorates). Then, check traffic distribution on interfaces within a short period of time. For data packets that cause congestion, take traffic control measures.

· When the network bandwidth is sufficient and services are operating normally, you can set the statistics polling interval to be greater than 300 seconds. Once traffic parameter anomalies occur, modify the statistics polling interval promptly so that you can observe the traffic parameter trend in real time.

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.

Setting the statistics polling interval in Ethernet interface view

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Set the statistics polling interval for the Ethernet interface.

flow-interval interval

By default, the statistics polling interval is 300 seconds.

Enabling loopback testing on an Ethernet interface

About this task

Perform this task to determine whether an Ethernet link works correctly.

Loopback testing includes the following types:

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

· External loopback testing—Tests the hardware function of the Ethernet interface. The Ethernet interface sends outgoing packets to the local device through a self-loop plug. If the device fails to receive the packets, the hardware function of the Ethernet interface fails.

Restrictions and guidelines

· After you enable this feature on an Ethernet interface, the interface does not forward data traffic.

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

· After you enable this feature on an Ethernet interface, the Ethernet interface switches to full duplex mode. After you disable this feature, the Ethernet interface restores to its duplex setting.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Configure loopback testing on the Ethernet interface.

¡ Perform a loopback test.

loopback-test{ external | internal }

Forcibly bringing up a fiber port

About this task

As shown in Figure 2, a fiber port uses separate fibers for transmitting and receiving packets. The physical state of the fiber port is up only when both transmit and receive fibers are physically connected. If one of the fibers is disconnected, the fiber port does not work.

To enable a fiber port to forward traffic over a single link, you can use the port up-mode command. This command forcibly brings up a fiber port, even when no fiber links or transceiver modules are present for the fiber port. When one fiber link is present and up, the fiber port can forward packets over the link unidirectionally.

Figure 2 Forcibly bring up a fiber port

‌

Restrictions and guidelines

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

· A fiber port does not support this feature if the port is shut down by a protocol or by using the shutdown command.

· A fiber port forcibly brought up stays physically up whether or not a transceiver module or a fiber link is present for the port.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Forcibly bring up the fiber port.

port up-mode

By default, a fiber port is not forcibly brought up, and the physical state of a fiber port depends on the physical state of the fibers.

Enabling optical power anomaly detection on an interface

About this task

When the optical power of a transceiver module is abnormal, failures such as service flapping might occur. To ensure service continuity, you can enable this feature on an interface. When the optical power is abnormal on an interface, the interface will be shut down and stop sending or receiving packets. Then, you can promptly switch service traffic to the backup link for processing.

You can use the following methods to restore an interface when that interface is shut down because the port optical power anomaly detection feature detects interface optical power anomalies:

· Automatic recovery—With the down-auto-recovery keyword specified, the device shuts down the interface when the optical power of a transceiver module is abnormal. When the port status detection timer set by the shutdown-interval transceiver-power-low command expires, the port automatically restores to its actual physical state.

· Manual recovery—With the error-down keyword specified, the device shuts down the interface when the optical power of a transceiver module is abnormal. After the optical power returns to normal, you must execute the undo shutdown command to restore the interface status.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Enable optical power anomaly detection on the interface.

port transceiver-power-low trigger error-down { down-auto-recovery | error-down }

By default, optical power anomaly detection is disabled for an interface.

4. Set the port status detection timer for the ports that are shut down by the optical power anomaly detection feature.

shutdown-interval [ transceiver-power-low ] interval

By default, the timer is 30 seconds.

Configuring interface alarm functions

About this task

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

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.

If you change the timer setting during port detection, the device compares the new setting (T1) with the time that elapsed since the port was shut down (T).

· If T < T1, the port will be brought up after T1 – T seconds.

· If T ≥ T1, the port is brought up immediately.

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 for interfaces.

Configuring CRC error packet parameters

1. Enter system view.

system-view

2. Configure global CRC error packet alarm parameters.

ifmonitor crc-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ down-auto-recovery | 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 Ethernet interface view.

interface interface-type interface-number

4. Configure CRC error packet alarm parameters for the interface.

port ifmonitor crc-error [ ratio ] high-threshold high-value low-threshold low-value interval interval [down-auto-recovery | shutdown ]

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

5. Set the port status detection timer for the ports that are shut down by the CRC error packet alarm feature.

shutdown-interval [ crc-error ] interval

By default, the timer is 30 seconds.

Configuring input error packet alarm parameters

1. Enter system view.

system-view

2. Configure 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 Ethernet interface view.

interface interface-type interface-number

4. Configure input error packet alarm parameters for the interface.

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

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

Configuring output error packet alarm parameters

1. Enter system view.

system-view

2. Configure 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 Ethernet interface view.

interface interface-type interface-number

4. Configure output error packet alarm parameters.

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

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

Configuring input bandwidth usage alarm parameters

1. Enter system view.

system-view

2. Configure global input 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 for input bandwidth usage alarms.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Configure input bandwidth usage alarm parameters.

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

By default, an interface uses the global input bandwidth usage alarm parameters.

Configuring output bandwidth usage alarm parameters

1. Enter system view.

system-view

2. Configure global output 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 for output bandwidth usage alarms.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Configure output bandwidth usage alarm parameters.

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

By default, an interface uses the global output bandwidth usage alarm parameters.

Configuring received pause frame alarm parameters

1. Enter system view.

system-view

2. Configure global received 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 received pause frames.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Configure received pause frame alarm parameters.

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

By default, an interface uses the global received pause frame alarm parameters.

Configuring sent pause frame alarm parameters

1. Enter system view.

system-view

2. Configure global sent pause frame alarm parameters.

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

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

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Configure sent pause frame alarm parameters.

port ifmonitor tx-pause high-threshold high-value low-threshold low-value interval interval [ shutdown ]

By default, an interface uses the global sent pause frame alarm parameters.

Enabling SNMP notifications for the ETH module

About this task

To report critical ETH events to an SNMP NMS, enable SNMP notifications for the ETH module.

For ETH SNMP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see SNMP configuration in Network Management and Monitoring Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enable SNMP notifications for the ETH module.

snmp-agent trap enable eth

By default, SNMP notifications are disabled for the ETH module.

Enabling remote fault signal detection

About this task

A fiber port forwards packets by using two optical fibers. One is used to receive packets, and the other one is used to send packets. The fiber port can go up and forward packets only when both optical fibers operate correctly. When the fiber port receives a remote fault signal, the physical state of the port becomes down. To keep the port in up state to operate correctly upon receiving a remote fault signal, disable remote fault signal detection on the port. Then, the port can forward packets unidirectionally when only one fiber operates correctly.

Restrictions and guidelines

Only fiber ports support this feature.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

interface interface-type interface-number

3. Enable remote fault signal detection.

link-fault-signal enable

By default, remote fault signal detection is enabled.

Shutting down all physical interfaces

About this task

This feature shuts down all physical interfaces except the management Ethernet interfaces on the device. Physical interfaces shut down by using this command are in ADM state.

Restrictions and guidelines

To shut down all physical interfaces or the specified interface, execute the shutdown all-physical-interfaces command in system view or execute the shutdown command in interface view.

To bring up interfaces shut down by using the shutdown all-physical-interfaces command, execute its undo form in system view. To bring up an interface shut down by using the shutdown command, execute its undo form in interface view.

If you execute the shutdown all-physical-interfaces command with the include irf-physical-interface keyword multiple times, this command shuts down all physical interfaces except the management Ethernet interfaces on the device.

Procedure

1. Enter system view.

system-view

2. Shut down all physical interfaces except management Ethernet interfaces.

shutdown all-physical-interfaces [ include irf-physical-interface ]

By default, physical interfaces are up.

Restoring the default settings for an interface

Restrictions and guidelines

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 Ethernet interface view or Ethernet subinterface view.

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

3. Restore the default settings for the interface.

default

Configuring the rail group feature

About this task

Rail group is a load balancing technique that improves network throughput. In scenarios with high network performance requirements, you can configure the rail group feature to improve network throughput. The rail group feature assigns different incoming interfaces on the device to a rail group and assigns indexes to these interfaces. The device distributes traffic across various interfaces based on their configured index values by using a specific algorithm. Traffic that arrives at different incoming interfaces is then forwarded through different outgoing interfaces, achieving traffic load sharing. You can configure a rail group in ECMP mode or Ethernet link aggregation mode as needed. The ECMP-mode rail group feature is available only on a network configured with ECMP. The Ethernet link aggregation mode rail group feature is available only on a network enabled with Ethernet link aggregation.

Restrictions and guidelines

You can specify an index to assign an interface with the specified index to a rail group or specify a list of interfaces to allow the device to automatically assign indexes to the interfaces and assign the interfaces in bulk to a rail group.

As a best practice, do not manually specify an index. If you specify a list of non-contiguous interface indexes, the traffic outgoing interfaces will become discontinuous, causing unbalanced traffic. If you have to manually specify an index, do that under guidance of professionals.

You can assign only physical interfaces to a rail group, and the interfaces must be incoming interfaces.

Assign interfaces to a rail group in the order of interface numbers. To avoid index change after a device reboot, do not change the interface type after you assign an interface to a rail group.

Interfaces in a rail group cannot be split or combined.

If you specify a list of interfaces, make sure the two interfaces before and after the to keyword are the same type.

If you configure both the load sharing feature (using the ip load-sharing mode command) and the rail group feature, the rail group feature takes precedence. Traffic on interfaces within the configured rail group will be load shared using the rail group feature, and traffic on other interfaces will be load shared as configured by the ip load-sharing mode command. For more information about the ip load-sharing mode command, see Layer 3—IP Services Command Reference.

Procedure

1. Enter system view.

system-view

2. Create a rail group and enter its view.

rail-group group-name

3. Assign interfaces to the rail group.

group-member interface interface-type interface-number [ to interface-type interface-number ]

group-member interface interface-type interface-number index index-value

4. Return to system view.

quit

5. (Optional.) Enable the ECMP-mode rail group feature.

loadbalance ecmp rail-group enable

By default, this feature is disabled.

6. (Optional.) Enable the Ethernet link aggregation mode rail group feature.

loadbalance link-aggregation rail-group enable

By default, this feature is disabled.

Configuring a Layer 2 Ethernet interface

Configuring storm control on an Ethernet interface

About this task

Storm control compares broadcast, multicast and unknown unicast traffic regularly with their respective traffic thresholds on an Ethernet interface. For each type of traffic, storm control provides a lower threshold and an upper threshold.

Depending on your configuration, when a particular type of traffic exceeds its upper threshold, the interface performs either of the following operations:

· Blocks this type of traffic and forwards other types of traffic—Even though the interface does not forward the blocked traffic, it still counts the traffic. When the blocked traffic drops below the lower threshold, the interface begins to forward the traffic.

· Goes down automatically—The interface goes down automatically and stops forwarding any traffic. When the blocked traffic drops below the lower threshold, the interface does not automatically come up. To bring up the interface, use the undo shutdown command or disable the storm control feature.

You can configure an Ethernet interface to output threshold event traps and log messages when monitored traffic meets one of the following conditions:

· Exceeds the upper threshold.

· Drops below the lower threshold.

Storm control uses a complete polling cycle to collect traffic data, and analyzes the data in the next cycle. An interface takes one to two polling intervals to take a storm control action.

Procedure

1. Enter system view.

system-view

2. (Optional.) Set the statistics polling interval of the storm control module.

storm-constrain interval interval

The default setting is 10 seconds.

For network stability, use the default or set a longer statistics polling interval.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Enable storm control, and set the lower and upper thresholds for broadcast, multicast, or unknown unicast traffic.

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

By default, storm control is disabled.

5. Set the control action to take when monitored traffic exceeds the upper threshold.

storm-constrain control { block | shutdown }

By default, storm control is disabled.

6. Enable the Ethernet interface to output log messages when it detects storm control threshold events.

storm-constrain enable log

By default, the Ethernet interface outputs log messages when monitored traffic exceeds the upper threshold or drops below the lower threshold from a value above the upper threshold.

7. Enable the Ethernet interface to send storm control threshold event traps.

storm-constrain enable trap

By default, the Ethernet interface sends traps when monitored traffic exceeds the upper threshold or drops below the lower threshold from the upper threshold from a value above the upper threshold.

Enabling bridging on an Ethernet interface

About this task

By default, the device drops packets whose outgoing interface and incoming interface are the same.

To enable the device to forward such packets rather than drop them, enable the bridging feature in Ethernet interface view.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Enable bridging on the Ethernet interface.

port bridge enable

By default, bridging is disabled on an Ethernet interface.

Configuring a Layer 3 Ethernet interface or subinterface

Setting the MTU for an Ethernet interface or subinterface

About this task

The maximum transmission unit (MTU) determines the maximum number of bytes in a single IP packet that can be sent. The length of an IP packet refers to the number of bytes starting from the IP header to the payload.

When the IP layer receives an IP data packet to be sent, the IP layer determines the local destination interface of the packet and obtains the MTU of the interface. The IP layer compares the MTU with the length of the data packet to be sent. If the length is greater than the MTU, the IP layer fragments the packet. The length of a fragment can be smaller than or equal to the MTU to ensure that big packets are not lost on the network.

As a best practice, use the default MTU. When the packet length or the packet receiver changes, you can adjust the MTU as needed. When configuring the MTU, follow these restrictions and guidelines:

· If the configured MTU is small but the packet length is large, the following events might occur:

¡ Packets will be dropped when they are forwarded by hardware.

¡ Packets will be fragmented into too many fragments when packets are forwarded through the CPUs, which affects normal data transmission.

· If the configured MTU is too large, the MTU will exceed the receiving capabilities of the receiver or a device along the transmission path. As a result, packets will be fragmented or even dropped, which increases the network transmission load and affects data transmission.

Restrictions and guidelines

The MTU of an Ethernet interface affects the fragmentation and reassembly of IP packets on the interface. Typically, you do not need to modify the MTU of an interface.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

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

3. Set the MTU for the interface.

mtu size

The default setting is 1500 bytes.

Setting the MAC address of an Ethernet interface or subinterface

About this task

In a network, when the Layer 3 Ethernet interfaces or subinterfaces of different devices have the same MAC address, the devices might fail to communicate correctly. To eliminate the MAC address conflicts, use the mac-address command to modify the MAC addresses of Layer 3 Ethernet interfaces or subinterfaces.

Procedure

1. Enter system view.

system-view

2. Enter interface view.

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

3. Set the interface MAC address.

mac-address mac-address

By default, no MAC address is set for an Ethernet interface.

As a best practice, do not set a MAC address in the VRRP-reserved MAC address range for a Layer 3 Ethernet subinterface.

Display and maintenance commands for Ethernet interfaces

For more information about the display diagnostic-information command, see device management in Fundamentals Command Reference.

Execute display commands in any view and reset commands in user view.

Task	Command
Display interface traffic statistics.	display counters { inbound \| outbound } interface [ interface-type [ interface-number \| interface-number.subnumber ] ]
Display traffic rate statistics of interfaces in up state over the last statistics polling interval.	display counters rate { inbound \| outbound } interface [ interface-type [ interface-number \| interface-number.subnumber ] ]
Display the operating information for the IFMGR module.	display diagnostic-information ifmgr [ key-info ] [ filename ]
Display the Ethernet module statistics.	display ethernet statistics slot slot-number
Display the operational and status information of the specified interfaces.	display interface [ interface-type [ interface-number \| interface-number.subnumber ] ] [ brief [ description \| down ] ]
Display the status and packet statistics of interfaces.	display interface link-info [ main ]
Display the operational and status information of interfaces except subinterfaces.	display interface [ interface-type ] [ brief [ description \| down ] ] main
Display information about link flapping protection on interfaces.	display link-flap protection [ interface interface-type [ interface-number ] ]
Display the physical link state change statistics of interfaces.	display link-state-change statistics interface [ interface-type [ interface-number ] ]
Display information about dropped packets on the specified interfaces.	display packet-drop { interface [ interface-type [ interface-number ] ] \| summary }
Display rail group information.	display rail-group status
Display information about storm control on the specified interfaces.	display storm-constrain [ broadcast \| multicast \| unicast ] [ interface interface-type interface-number ]
Clear interface statistics.	reset counters interface [ interface-type [ interface-number \| interface-number.subnumber ] ]
Clear the Ethernet module statistics.	reset ethernet statistics [ slot slot-number ]
Clear the physical link state change statistics of interfaces.	reset link-state-change statistics interface [ interface-type [ interface-number ] ]
Clear the statistics of dropped packets on the specified interfaces.	reset packet-drop interface [ interface-type [ interface-number ] ]

‌

02-Layer 2—LAN Switching Configuration Guide

Configuring Ethernet interfaces

About Ethernet interface

About this task

Procedure

Restrictions and guidelines: Ethernet interface configuration

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines for 100-GE interface splitting and 10-GE breakout interface combining

Splitting a 100-GE interface into multiple 10-GE breakout interfaces

Combining multiple 10-GE breakout interfaces into a 100-GE interface

About this task

Restrictions and guidelines for 100-GE interface splitting and 25-GE breakout interface combining

Splitting a 100-GE interface into four 25-GE breakout interfaces

Combining four 25-GE breakout interfaces into a 100-GE interface

About this task

Restrictions and guidelines for 400-GE interface splitting and 100-GE breakout interface combining

Splitting a 400-GE interface into two 100-GE breakout interfaces

Combining two 100-GE breakout interfaces into a 400-GE interface

About this task

Restrictions and guidelines for 400-GE interface splitting and 200-GE breakout interface combining

Splitting a 400-GE interface into two 200-GE breakout interfaces

Combining two 200-GE breakout interfaces into a 400-GE interface

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines for Ethernet subinterface basic settings

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

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Setting the statistics polling interval

About this task

Setting the statistics polling interval in Ethernet interface view

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Enabling interface alarm functions

Configuring CRC error packet parameters

Configuring input error packet alarm parameters

Configuring output error packet alarm parameters

Configuring input bandwidth usage alarm parameters

Configuring received pause frame alarm parameters

Configuring sent pause frame alarm parameters

About this task

Procedure