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—IRF member ID. If the switch is not in an IRF fabric, A is 1 by default.

· B—Card slot number. 0 indicates the interface is a fixed interface of the switch. 1 indicates the interface is on expansion interface card 1. 2 indicates the interface is on expansion interface card 2.

· C—Port index.

A 10-GE breakout interface split from a 40-GE interface is named in the format of interface type A/B/C:D. A/B/C is the interface number of the 40-GE interface. D is the number of the 10-GE interface, which is in the range of 1 to 4. For information about splitting a 40-GE interface, see "Splitting a 40-GE interface and combining 10-GE breakout interfaces."

A 10-GE breakout interface split from a 100-GE interface is named in the format of interface type A/B/C:D. A/B/C is the interface number of the 100-GE interface. D is the number of the 10-GE interface, which is in the range of 1 to 4. For information about splitting a 100-GE interface into 10-GE interfaces, see "Splitting a 100-GE interface and combining 10-GE breakout interfaces."

A 25-GE breakout interface split from a 100-GE interface is named in the format of interface type A/B/C:D. A/B/C is the interface number of the 100-GE interface. D is the number of the 25-GE interface, which is in the range of 1 to 4. For information about splitting a 100-GE interface into 25-GE interfaces, see "Splitting a 100-GE interface and combining 25-GE breakout interfaces."

A 50-GE breakout interface split from a 100-GE interface is named in the format of interface type A/B/C:D. A/B/C is the interface number of the 100-GE interface. D is the number of the 50-GE interface, which is in the range of 1 and 2. For information about splitting a 100-GE interface into 50-GE interfaces, see "Splitting a 100-GE interface and combing 50-GE breakout interfaces."

Restrictions and guidelines: Ethernet interface configuration

Restrictions and guidelines for 25-GE interfaces

25-GE interfaces can operate at 25 Gbps, 10 Gbps, or 1 Gbps.

· See Table 1 and Table 2 for the configuration requirements for interfaces operating at 25 Gbps.

· For a 25-GE interface on an S6850 or S9850 device to operate at 10 Gbps or 1 Gbps, execute the speed command to configure the speed. For an interface to come up, make sure the speed configured is the same as the speed of the transceiver module or cable installed in the interface. For a 25-GE interface on an S6825 device to operate at 10 Gbps or 1 Gbps, you do not need to execute the speed command to set the speed.

· A 25-GE breakout interface can operate only at 25 Gbps.

When you configure autonegotiation for a 25-GE interface, follow these restrictions and guidelines:

· When an SFP28 interface on an S6850-56HF or S6825-54HF device uses an SFP28 or SFP+ cable to connect to a peer interface that does not support autonegotiation, you must execute the speed and duplex full commands on both ends. For an interface to come up, make sure the speed configured by using the speed command is the same as the speed of the transceiver module or cable installed in the interface.

· SFP28 interfaces on an LSWM124TG2H cards do not support autonegotiation. When such an interface uses an SFP+ transceiver module/cable or SFP transceiver module, you must execute the speed and duplex full commands on both ends. For an interface to come up, make sure the speed configured by using the speed command is the same as the speed of the transceiver module or cable installed in the interface.

· When an SFP28 interface uses an SFP transceiver module except SFP-GE-T and SFP-GE-T-D to connect to a peer interface, you must disable autonegotiation on the peer interface.

When you configure the speed for 25-GE interfaces on the following devices and expansion interface cards, interfaces in the same group must be configured with the same speed. When you modify the speed of an interface in a group, the modification takes effect on all interfaces in the group. When you use the default command to restore the default settings for the interface, the speed will be restored to the default for the interface and the other interfaces in the group.

· On an S6850-56HF switch, for 25-GE interfaces 1 through 24 and 33 through 56, four continuous interfaces starting from 1 or 33 are organized into one group.

· When you use the using twenty-fivegige command to split a 100-GE interface into four 25-GE breakout interfaces, the four breakout interfaces are organized into one group.

· On an LSWM124TG2H expansion interface card, four continuous interfaces in ascending order of interface number are organized into one group.

The preceding group-based speed configuration restrictions do not apply to 25-GE interfaces on S6825 switches.

When one of the following 25-GE interfaces uses an SFP-XG-LX-SM1310-D (0231A1RQ) transceiver module, 12 contiguous interfaces in ascending order of interface number are organized into one group. For the transceiver module to operate correctly, you must set the same speed for interfaces in the same group as the interface.

· Interfaces 1 through 24 and interfaces 33 through 56 on an S6850-56HF switch. When you set the speed for an interface, the speed is set for four interfaces in the same group as the interface.

· Interfaces 1 through 24 and interfaces 31 through 54 on an S6825-54HF switch.

· Interfaces 1 through 24 on an LSWM124TG2H card. When you set the speed for an interface, the speed is set for four interfaces in the same group as the interface.

For example, when interface 3 on an S6850-56HF switch uses an SFP-XG-LX-SM1310-D transceiver module, interfaces 1 through 12 must be configured to operate at 10 Gbps for the transceiver module to operate properly. When you set the speed for an interface, set the speed for four interfaces in the same group as prompted.

For 25-GE interfaces on an LSWM124TG2H interface module, you must use the port media-type { copper | fiber } command to set the media type. Set the media type to fiber for an interface that uses a transceiver module or fiber cable. Set the media type to copper for an interface that uses a copper cable. The media type of interfaces in the same group is the same. When you set the media type for any interface in a group, the setting is synchronized to the other interfaces in the group.

When a local 25-GE interface on an S6825-54HF, S6850-56HF, or S9850-32H switch is connected to a peer 25-GE interface on a different device, the interface configuration requirements are as shown in Table 1. For interfaces to operate properly, you must enable link compensation (also known as training or CL72) on both ends when the interfaces are connected by using a copper cable. This requirement is not otherwise described in Table 1.

In Table 1, the 25-GE interfaces (including 25-GE breakout interfaces split from a 100-GE interface) are supposed to be connected when they use the default settings.

Table 1 States of a local 25-GE interface on an S6825-54HF, S6850-56HF, or S9850-32H switch

Peer device	Local interface state and operations for bringing the interface up
S6820 switch series	By default, the local interface is down. · When the local interface is connected to the peer by using a cable, perform the following operations: ¡ Configure the local interface to operate in the same speed and duplex mode as the peer interface. Do not configure autonegotiation settings. ¡ Set the FEC mode to BASE-R FEC for the local interface. ¡ Execute the port media-type copper command on the peer interface if the peer interface is one of Twenty-FiveGigE1/0/1 through Twenty-FiveGigE1/0/8 and Twenty-FiveGigE1/0/49 through Twenty-FiveGigE1/0/56 on an S6820-56HF switch or an SFP28 interface on an LSWM124TG2H interface module. · When the local interface is connected to the peer by using a transceiver module, set the FEC mode to BASE-R FEC for the local interface.
25-GE breakout interfaces split from interfaces 1 through 32 on an S9820-64H switch	Up by default.
25-GE breakout interfaces split from interfaces 33 through 64 on an S9820-64H switch	· By default, the local interface is down when connected to the peer by using a cable. To bring up the local interface, perform the following operations: ¡ Configure the local interface to operate in the same speed and duplex mode as the peer interface. Do not configure autonegotiation settings. ¡ Set the FEC mode to RS-FEC for the local interface. · The local interface is up by default when connected to the peer by using a transceiver module.
S9850-4C, S6850-2C	· By default, the local interface is down when connected to the peer by using a cable. To bring up the local interface, perform the following operations: ¡ Configure the local interface to operate in the same speed and duplex mode as the peer interface. Do not configure autonegotiation settings. ¡ Set the FEC mode to RS-FEC for the local interface. ¡ Execute the port media-type copper command on the peer interface if the peer interface is an SFP28 interface on an LSWM124TG2H interface module. · The local interface is up by default when connected to the peer by using a transceiver module.
S6825-54HF, S6850-56HF, S9850-32H	Up by default.

When a local 25-GE interface on an S9850-4C or S6850-2C switch is connected to a peer 25-GE interface on a different device, the interface configuration requirements are as shown in Table 2. For interfaces to operate properly, you must enable link compensation (also known as training or CL72) on both ends when the interfaces are connected by using a copper cable. This requirement is not otherwise described in Table 2.

In Table 2, the 25-GE interfaces (including 25-GE breakout interfaces split from a 100-GE interface) are supposed to be connected when they use the default settings.

Table 2 States of a local 25-GE interface on an S9850-4C or S6850-2C switch

Peer device	Local interface state and operations for bringing the interface up
S6820 switch series	By default, the local interface is down. · When the local interface is connected to the peer by using a cable, perform the following operations to bring up the interface: ¡ Set the FEC mode to BASE-R FEC for the local interface. ¡ Execute the port media-type copper command on the local interface if the local interface is an SFP28 interface on an LSWM124TG2H interface module. ¡ Execute the port media-type copper command on the peer interface if the peer interface is one of Twenty-FiveGigE1/0/1 through Twenty-FiveGigE1/0/8 and Twenty-FiveGigE1/0/49 through Twenty-FiveGigE1/0/56 on an S6820-56HF switch or an SFP28 interface on an LSWM124TG2H interface module. · When the local interface is connected to the peer by using a transceiver module, set the FEC mode to BASE-R FEC for the local interface.
25-GE breakout interfaces split from interfaces 1 through 32 on an S9820-64H switch	· By default, the local interface is down when connected to the peer by using a cable. To bring up the local interface, perform the following operations: ¡ Configure the peer interface to operate in the same speed and duplex mode as the local interface. Do not configure autonegotiation settings. ¡ Set the FEC mode to RS-FEC for the peer interface. ¡ Execute the port media-type copper command on the local interface if the local interface is an SFP28 interface on an LSWM124TG2H interface module. · The local interface is up by default when connected to the peer by using a transceiver module.
25-GE breakout interfaces split from interfaces 33 through 64 on an S9820-64H switch	· When the local interface is connected to the peer by using a cable, execute the port media-type copper command on the local interface if the local interface is an SFP28 interface on an LSWM124TG2H interface module. · When the local interface is connected to the peer by using a transceiver module, the local interface is up by default.
S9850-4C, S6850-2C	· When the local interface is connected to the peer by using a cable, execute the port media-type copper command on both the local interface and peer interface if the interfaces are SFP28 interfaces on LSWM124TG2H interface modules. · When the local interface is connected to the peer by using a transceiver module, the local interface is up by default.
S6825-54HF, S6850-56HF, S9850-32H	· By default, the local interface is down when connected to the peer by using a cable. To bring up the local interface, perform the following operations: ¡ Configure the peer interface to operate in the same speed and duplex mode as the local interface. Do not configure autonegotiation settings. ¡ Set the FEC mode to RS-FEC for the peer interface. ¡ Execute the port media-type copper command on the local interface if the local interface is an SFP28 interface on an LSWM124TG2H interface module. · The local interface is up by default when connected to the peer by using a transceiver module.

‌

Restrictions and guidelines for 10-GE/1GE interfaces

When an interface on an LSWM124XG2QL card uses a 1000-Mbps SFP transceiver module, the interface does not support speed or duplex mode autonegotiation. You must manually execute the speed 1000 and duplex full commands on both ends.

When an SFP+ interface uses an SFP transceiver module except SFP-GE-T and SFP-GE-T-D to connect to a peer interface, you must disable autonegotiation on the peer interface.

When a 10GBase-T Ethernet interface on an S6805-54HT device operates at 1 Gbps, you must execute the speed 1000 command on the local end.

When the speed and duplex commands or their undo forms are executed on a 10GBase-T Ethernet interface on an S6805-54HT device or its peer interface, the interface will go down and then come up.

If the local device uses the SFP-GE-T/SFP-GE-T-D module to connect to the peer device, when you reboot the local device, the peer interface might come up before the local interface. As a result, packet loss will occur. As a best practice, use dynamic aggregation for the local and peer devices connected through aggregate links to avoid the previous issue.

Restrictions and guidelines for cooperation with data buffer configuration

Switching the link mode of an Ethernet interface between Layer 2 and Layer 3, splitting an interface, or combining breakout interface will cause global packet loss when the following data buffer configuration exists on a device:

· buffer egress cell queue shared (Configure the maximum share-area space for a queue)

· buffer service-pool shared (Configure the maximum share-area space for a service pool)

For more information about data buffer configuration, see data buffer configuration in 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."

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

About this task

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

For example, you can split 40-GE interface FortyGigE 1/0/1 into four 10-GE breakout interfaces Ten-GigabitEthernet 1/0/1:1 through Ten-GigabitEthernet 1/0/1:4.

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

Hardware and feature compatibility

This feature is not supported on the S6805 or S6825 switch series.

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

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

· Device reboot is not required for this feature to take effect. You can view the split or combined interface by using the display interface brief command.

· When the LSWM18QC interface module is installed in the slot 2 on the S9850-4C switch, the interface numbered 8 on the interface module cannot be split. This restrictions does not apply when the LSWM18QC interface module is installed in any other slot.

· When the LSWM124XG2Q, LSWM124XGT2Q, LSWM124XG2QFC, or LSWM124XG2QL interface module is installed in the slot 2 on the S9850-4C switch, the interface numbered 25 on the interface module cannot be split. This restrictions does not apply when the LSWM124XG2Q, LSWM124XGT2Q, LSWM124XG2QFC, or LSWM124XG2QL interface module is installed in any other slot.

· All interfaces on the LSWM116Q interface module cannot be split.

· An interface with any of the following configurations cannot be split:

¡ IRF physical interface.

¡ Service loopback group member.

¡ Reflector port for mirroring.

¡ Forcibly bringing up a fiber port.

Splitting a 40-GE interface into four 10-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 40-GE interface view.

interface fortygige interface-number

3. Split the 40-GE interface into four 10-GE breakout interfaces.

using tengige

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

Combining four 10-GE breakout interfaces into a 40-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 four 10-GE breakout interfaces into a 40-GE interface.

using fortygige

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

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 split a 100-GE interface with a split-capable transceiver module installed into four 10-GE breakout interfaces. The 10-GE breakout interfaces support the same configuration and attributes as common 10-GE interfaces, except that they are numbered differently. For example, you can split 100-GE interface HundredGigE 1/0/1 into four 10-GE breakout interfaces Ten-GigabitEthernet1/0/1:1 through Ten-GigabitEthernet1/0/1:4.

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

Hardware and feature compatibility

On an S6805-54HT device, interfaces 51 and 52 can be split into 10-GE or 25-GE breakout interfaces. On an S6805-54HF device, interfaces 27 and 28 can be split into 10-GE or 25-GE breakout interfaces.

On an S6825-54HF device, interfaces 27 and 28 can be split into 10-GE or 25-GE breakout interfaces.

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 configuring this feature, you do not need to reboot the device. To view information about the breakout interfaces, execute the display interface brief command.

The interface numbered 31 on the S6850-56HF switch cannot be split.

The interface numbered 31 on an S9850-32H switch cannot be split by default. To split this interface, first enable the hardware resource flex mode for the device by using the hardware-resource flex-mode enable command. For more information about the hardware resource flex mode, see Fundamentals Configuration Guide.

When the LSWM18CQ or LSWM18CQMSEC interface module is installed in the slot 2 on the S9850-4C switch, the interface numbered 7 on the interface module cannot be split. This restriction does not apply when the LSWM18CQ or LSWM18CQMSEC interface module is installed in any other slot.

When the LSWM124TG2H interface module is installed in the slot 2 on the S9850-4C switch, the interface numbered 25 on the interface module cannot be split. This restriction does not apply when the LSWM124TG2H interface module is installed in any other slot.

An interface with any of the following configurations cannot be split:

· IRF physical interface.

· Service loopback group member.

· Reflector port for mirroring.

· Forcibly bringing up a fiber port.

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/0/1 into four 25-GE breakout interfaces Twenty-FiveGigE 1/0/1:1 through Twenty-FiveGigE 1/0/1:4.

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

Hardware and feature compatibility

On an S6805-54HT device, interfaces 51 and 52 can be split into 10-GE or 25-GE breakout interfaces. On an S6805-54HF device, interfaces 27 and 28 can be split into 10-GE or 25-GE breakout interfaces.

On an S6825-54HF device, interfaces 27 and 28 can be split into 10-GE or 25-GE breakout interfaces.

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 configuring this feature, you do not need to reboot the device. To view information about the breakout interfaces, execute the display interface brief command.

The interface numbered 31 on the S6850-56HF switch cannot be split.

An interface with any of the following configurations cannot be split:

· IRF physical interface.

· Service loopback group member.

· Reflector port for mirroring.

· Forcibly bringing up a fiber port.

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 100-GE interface and combing 50-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 two 50-GE breakout interfaces. The 50-GE breakout interfaces support the same configuration and attributes as common 50-GE interfaces, except that they are numbered differently. For example, you can split 100-GE interface HundredGigE 1/0/1 into two 50-GE breakout interfaces FiftyGigE 1/0/1:1 and FiftyGigE 1/0/1:2.

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

Hardware and feature compatibility

This feature is supported only on the S9850-32H switches.

Interface 31 on an S9850-32H switch cannot be split by default. To split this interface, first enable the hardware resource flex mode for the device by using the hardware-resource flex-mode enable command. For more information about the hardware resource flex mode, see Fundamentals Configuration Guide.

Restrictions and guidelines

A 100-GE interface split into breakout interfaces must use a dedicated cable. After you combine the breakout interfaces, use a dedicated one-to-one cable or 100-GE transceiver module and fiber. For more information about cables and transceiver modules, see related documents.

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

An interface with any of the following configurations cannot be split:

· IRF physical interface.

· Service loopback group member.

· Reflector port for mirroring.

· Forcibly bringing up a fiber port.

Splitting a 100-GE interface into two 50-GE interfaces

1. Enter system view.

system-view

2. Enter 100-GE interface view.

interface hundredgige interface-number

3. Split the 100-GE interface into two 50-GE interfaces.

using fiftygige

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

Combining the two 50-GE breakout interfaces into a 100-GE interface

1. Enter system view.

system-view

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

interface fiftygige interface-number

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

using hundredgige

By default, a 100-GE interface is not split and 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.

· Half-duplex mode—The interface can only send or receive packets at a given time.

· 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 and port up-mode commands are mutually exclusive.

The shutdown command cannot be configured on an Ethernet interface in a loopback test.

When a 25-GE or 10-GE interface uses a 1-Gbps transceiver module to connect to a peer, you must disable autonegotiation on the peer.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Set the description for the Ethernet interface.

description text

The default setting is interface-name Interface. For example, Twenty-FiveGigE1/0/1 Interface.

4. Set the duplex mode for the Ethernet interface.

duplex { auto | full | half }

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

Fiber ports do not support the half keyword.

5. Set the speed for the Ethernet interface.

speed { 10 | 100 | 1000 | 10000 | 25000 | 40000 | 100000 | auto }

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

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

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

· The shutdown command cannot be configured on an Ethernet interface in a loopback test.

Procedure

1. Enter system view.

system-view

2. Create an Ethernet subinterface.

interface interface-type interface-number.subnumber

3. Set the description for the Ethernet subinterface.

description text

The default setting is interface-name Interface. For example, Twenty-FiveGigE1/0/1.1 Interface.

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

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

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.

Restrictions and guidelines

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

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.

IRF system stability might be affected by IRF physical link flapping. For IRF system stability, this feature is enabled by default on IRF physical interfaces and the enabling status of this feature is not affected by the status of global link flapping protection. When the number of flaps detected on an IRF physical interface exceeds the threshold within the detection interval, the device outputs a log rather than shuts down the IRF physical interface.

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.

Procedure

1. Enter system view.

system-view

2. Enable link flapping protection globally.

link-flap protect enable

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 [ interval interval | threshold threshold ] * [ second-interval second-interval second-threshold second-threshold ]

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

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 interfaces operating at 25 Gbps.

100-GE interfaces operating at 100 Gbps support this feature.

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

On a 100-GE interface installed with a QSFP-100G-LR4-WDM1300 transceiver module, manual FEC configuration does not take effect. However, the interface will go down and then come up upon the configuration.

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 | base-r | none | rs-fec }

By default, the FEC mode of an Ethernet interface is autonegotiation.

The base-r keyword is not supported on 100-GE interfaces.

Enabling FEC bypass

About this task

By default, 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, 40-GE, and 100-GE interfaces.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Enable FEC bypass.

port fec bypass enable

By default, FEC 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.

Hardware and feature compatibility

This feature is not supported on the S6805 switch series.

Restrictions and guidelines

Only 25-GE Ethernet interfaces connected through copper cables support this command. For 25-GE interfaces connected through copper cables to operate properly, you must enable link compensation.

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

Typically, the link compensation status is controlled by the software, and do not adjust the link compensation status as a best practice. Use this command to adjust the link compensation status only when the interface cannot come up.

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 storm suppression

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.

Both storm suppression and storm control can suppress storms on an interface. Storm suppression uses the chip to suppress traffic. Storm suppression has less impact on the device performance than storm control, which uses software to suppress traffic.

Restrictions and guidelines

· For the traffic suppression result to be determined, do not configure storm control together with storm suppression for the same type of traffic. For more information about storm control, see "Configuring storm control on an Ethernet interface."

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

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

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

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

· Set the same type of thresholds for each interface, that is, set the ratio argument, pps max-pps option, or kbps max-kbps option for the interface.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Enable broadcast suppression and set the broadcast suppression threshold.

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

By default, broadcast suppression is disabled.

4. Enable multicast suppression and set the multicast suppression threshold.

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

By default, multicast suppression is disabled.

5. Enable unknown unicast suppression and set the unknown unicast suppression threshold.

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

By default, unknown unicast suppression is disabled.

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.

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.

Enabling energy saving features on an Ethernet interface

About this task

With Energy Efficient Ethernet (EEE) enabled, a link-up interface enters low power state if it has not received any packet for a period of time. The time period depends on the chip specifications and is not configurable. When a packet arrives later, the device automatically restores power supply to the interface and the interface restores to the normal state.

Restrictions and guidelines

Fiber ports do not support this feature.

On an interface, EEE and MACsec are mutually exclusive. For more information about MACsec, see Security Configuration Guide.

Configuring EEE on an Ethernet interface

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Enable EEE on the Ethernet interface.

eee enable

By default, EEE 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. The device supports only internal loopback testing. It tests the device where the Ethernet interface resides. In internal loopback test, the Ethernet interface sends outgoing packets back to the local device. If the device fails to receive the packets, the device fails.

Restrictions and guidelines

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

· You cannot perform a loopback test on the following Ethernet interfaces:

¡ Ethernet interfaces manually brought down (displayed as in ADM or Administratively DOWN state).

¡ Ethernet interfaces with the port up-mode command executed.

· The speed, duplex, and shutdown commands cannot be executed on an Ethernet interface in a loopback test.

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

¡ Enable loopback testing on the Ethernet interface.

loopback internal

By default, loopback testing is disabled on an Ethernet interface.

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

· A GE fiber port forcibly brought up cannot correctly forward traffic if it is installed with a fiber-to-copper converter, 100/1000-Mbps transceiver module, or 100-Mbps transceiver module. To solve the problem, use the undo port up-mode command on the fiber 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.

Setting the media type for an Ethernet interface

Hardware and feature compatibility

This feature is not supported on the S6805 or S6825 switch series.

Restrictions and guidelines

For 25-GE interfaces on an LSWM124TG2H interface module, you must set the media type. Set the media type to fiber for an interface that uses a transceiver module or fiber cable. Set the media type to copper for an interface that uses a copper cable. The media type of interfaces in the same group is the same. When you set the media type for any interface in a group, the setting is synchronized to the other interfaces in the group.

This configuration fails when an interface group has any service loopback interface or reflector port for mirroring.

When you configure this feature for an interface through the preprovisioning feature, the configuration on the interface is not automatically synchronized to the other interfaces in the same group. For more information about preprovisioning, see preprovisioning configuration in Fundamentals Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Set the media type for the Ethernet interface.

port media-type { copper | fiber }

By default, the media type of an Ethernet interface is fiber.

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.

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 [ 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 [ shutdown ]

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

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.

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.

This command does not take effect on a physical interface that has joined a service loopback group.

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

Restrictions and guidelines

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

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.

Changing a Layer 2 Ethernet interface to an FC interface

About this task

This feature allows you to change a Layer 2 Ethernet interface to an FC interface.

Hardware and feature compatibility

This feature is not supported on the LSWM124XG2QFC and LSWM116FC cards.

Restrictions and guidelines

After the type of an interface is changed, the system creates a new interface that is numbered the same as the original interface.

An LSWM116FC interface expansion card has 16 interfaces, and every two neighboring interfaces belong to one port group. If you change an Ethernet interface to an FC interface by using the port-type fc command, the other interface in the same port group is also changed to an FC interface. If you change an FC interface to an Ethernet interface by using the port-type ethernet command, the other interface in the same port group is also changed to an Ethernet interface. An Ethernet interface on the card operates at 25 Gbps in full duplex and cannot perform speed autonegotiation.

Procedure

1. Enter system view.

system-view

2. Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

3. Change the type of the interface:

¡ Change the Layer 2 Ethernet interface to an FC interface.

port-type fc

¡ Change the FC interface back to a Layer 2 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.

‌

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

‌

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

Hardware and feature compatibility

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

Splitting a 40-GE interface into four 10-GE breakout interfaces

Combining four 10-GE breakout interfaces into a 40-GE interface

About this task

Hardware and feature compatibility

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

Hardware and feature compatibility

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

Hardware and feature compatibility

Restrictions and guidelines

Splitting a 100-GE interface into two 50-GE interfaces

Combining the two 50-GE breakout interfaces into a 100-GE interface

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines for Ethernet subinterface basic settings

Procedure

About this task

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

Hardware and feature compatibility

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Enabling energy saving features on an Ethernet interface

About this task

Restrictions and guidelines

Configuring EEE on an Ethernet interface

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

Hardware and feature compatibility

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Enabling interface alarm functions