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

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

Configuring a management Ethernet interface

About this task

A management interface uses an RJ-45/LC connector. You can connect the 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.) Shut down the interface.

shutdown

By default, the management Ethernet interface is up.

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—A is 1 by default.

· B—Card slot number. 0 indicates the interface is a fixed interface of the switch.

· C—Port index.

A 200-GE breakout interface split from a 400-GE interface is named in the format of interface type A/B/C:D. A/B/C is the interface number of the 400-GE interface. D is the number of the 200-GE breakout interface, which is 1 or 2.

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 400-GE interfaces 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 split a 400-GE interface into multiple 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 FourHundredGigE 1/0/1 into four 100-GE breakout interfaces HundredGigE 1/0/1:1 through HundredGigE 1/0/1:4.

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

Restrictions and guidelines

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

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

1. Enter system view.

system-view

2. Enter 400-GE Ethernet interface view.

interface fourhundredgige interface-number

3. Split the 400-GE interface into multiple 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 the multiple 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 multiple 100-GE breakout interfaces into a 400-GE interface.

using fourhundredgige

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

Splitting 400-GE interfaces 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 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 HundredGigE 1/0/1:1 and HundredGigE 1/0/1:2.

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

Restrictions and guidelines

After configuring this feature, you do not need to reboot the device. To view the 200-GE 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 Ethernet 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 the 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 400-GE interface is not split and operates as a single interface.

Changing a 400-GE interface to a 100-GE interface and restoring a 100-GE interface changed from a 400-GE interface to a 400-GE interface

About this task

You can use a 400-GE interface as a single interface. To improve network flexibility, you can also change a 400-GE interface to a 100-GE interface. If you need higher bandwidth on a single interface, you can restore the 100-GE interface that was changed from a 400-GE interface to a 400-GE interface.

Restrictions and guidelines

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

For an S9827-128DH switch, when a 400-GE interface is changed to a 100-GE interface, the 400-GE interfaces in the same interface group are also changed to 100-GE interfaces. When a 100-GE interface is restored to a 400-GE interface, the 100-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 1 shows interface groups of an S9827-128DH switch.

Table 1 Interface groups of an S9827-128DH switch

Interface group number	Interfaces
1	FourHundredGigE 1/0/1, FourHundredGigE 1/0/9
2	FourHundredGigE 1/0/2, FourHundredGigE 1/0/10
3	FourHundredGigE 1/0/3, FourHundredGigE 1/0/4
4	FourHundredGigE 1/0/5, FourHundredGigE 1/0/6
5	FourHundredGigE 1/0/7, FourHundredGigE 1/0/15
6	FourHundredGigE 1/0/8, FourHundredGigE 1/0/16
7	FourHundredGigE 1/0/11, FourHundredGigE 1/0/12
8	FourHundredGigE 1/0/13, FourHundredGigE 1/0/14
9	FourHundredGigE 1/0/17, FourHundredGigE 1/0/25
10	FourHundredGigE 1/0/18, FourHundredGigE 1/0/26
11	FourHundredGigE 1/0/19, FourHundredGigE 1/0/21
12	FourHundredGigE 1/0/20, FourHundredGigE 1/0/22
13	FourHundredGigE 1/0/23, FourHundredGigE 1/0/31
14	FourHundredGigE 1/0/24, FourHundredGigE 1/0/32
15	FourHundredGigE 1/0/27, FourHundredGigE 1/0/29
16	FourHundredGigE 1/0/28, FourHundredGigE 1/0/30
17	FourHundredGigE 1/0/33, FourHundredGigE 1/0/41
18	FourHundredGigE 1/0/34, FourHundredGigE 1/0/42
19	FourHundredGigE 1/0/35, FourHundredGigE 1/0/37
20	FourHundredGigE 1/0/36, FourHundredGigE 1/0/38
21	FourHundredGigE 1/0/39, FourHundredGigE 1/0/47
22	FourHundredGigE 1/0/40, FourHundredGigE 1/0/48
23	FourHundredGigE 1/0/43, FourHundredGigE 1/0/45
24	FourHundredGigE 1/0/44, FourHundredGigE 1/0/46
25	FourHundredGigE 1/0/49, FourHundredGigE 1/0/57
26	FourHundredGigE 1/0/50, FourHundredGigE 1/0/58
27	FourHundredGigE 1/0/51, FourHundredGigE 1/0/52
28	FourHundredGigE 1/0/53, FourHundredGigE 1/0/54
29	FourHundredGigE 1/0/55, FourHundredGigE 1/0/63
30	FourHundredGigE 1/0/56, FourHundredGigE 1/0/64
31	FourHundredGigE 1/0/59, FourHundredGigE 1/0/60
32	FourHundredGigE 1/0/61, FourHundredGigE 1/0/62
33	FourHundredGigE 1/0/65, FourHundredGigE 1/0/73
34	FourHundredGigE 1/0/66, FourHundredGigE 1/0/74
35	FourHundredGigE 1/0/67, FourHundredGigE 1/0/68
36	FourHundredGigE 1/0/69, FourHundredGigE 1/0/70
37	FourHundredGigE 1/0/71, FourHundredGigE 1/0/79
38	FourHundredGigE 1/0/72, FourHundredGigE 1/0/80
39	FourHundredGigE 1/0/75, FourHundredGigE 1/0/76
40	FourHundredGigE 1/0/77, FourHundredGigE 1/0/78
41	FourHundredGigE 1/0/81, FourHundredGigE 1/0/89
42	FourHundredGigE 1/0/82, FourHundredGigE 1/0/90
43	FourHundredGigE 1/0/83, FourHundredGigE 1/0/85
44	FourHundredGigE 1/0/84, FourHundredGigE 1/0/86
45	FourHundredGigE 1/0/87, FourHundredGigE 1/0/95
46	FourHundredGigE 1/0/88, FourHundredGigE 1/0/96
47	FourHundredGigE 1/0/91, FourHundredGigE 1/0/93
48	FourHundredGigE 1/0/92, FourHundredGigE 1/0/94
49	FourHundredGigE 1/0/97, FourHundredGigE 1/0/105
50	FourHundredGigE 1/0/98, FourHundredGigE 1/0/106
51	FourHundredGigE 1/0/99, FourHundredGigE 1/0/101
52	FourHundredGigE 1/0/100, FourHundredGigE 1/0/102
53	FourHundredGigE 1/0/103, FourHundredGigE 1/0/111
54	FourHundredGigE 1/0/104, FourHundredGigE 1/0/112
55	FourHundredGigE 1/0/107, FourHundredGigE 1/0/109
56	FourHundredGigE 1/0/108, FourHundredGigE 1/0/110
57	FourHundredGigE 1/0/113, FourHundredGigE 1/0/121
58	FourHundredGigE 1/0/114, FourHundredGigE 1/0/122
59	FourHundredGigE 1/0/115, FourHundredGigE 1/0/116
60	FourHundredGigE 1/0/117, FourHundredGigE 1/0/118
61	FourHundredGigE 1/0/119, FourHundredGigE 1/0/127
62	FourHundredGigE 1/0/120, FourHundredGigE 1/0/128
63	FourHundredGigE 1/0/123, FourHundredGigE 1/0/124
64	FourHundredGigE 1/0/125, FourHundredGigE 1/0/126

For an S9857-24DH8EP switch, when a 400-GE interface is changed to a 100-GE interface, the 400-GE interfaces in the same interface group are also changed to 100-GE interfaces. When a 100-GE interface is restored to a 400-GE interface, the adjacent 100-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 2 shows interface groups of an S9857-24DH8EP switch.

Table 2 Interface groups of an S9857-24DH8EP switch

Interface group number	Interfaces
1	FourHundredGigE 1/0/1, FourHundredGigE 1/0/2
2	FourHundredGigE 1/0/3, FourHundredGigE 1/0/4
3	FourHundredGigE 1/0/5, FourHundredGigE 1/0/6
4	FourHundredGigE 1/0/7, FourHundredGigE 1/0/8
5	FourHundredGigE 1/0/9, FourHundredGigE 1/0/10
6	FourHundredGigE 1/0/11, FourHundredGigE 1/0/12
7	FourHundredGigE 1/0/13, FourHundredGigE 1/0/14
8	FourHundredGigE 1/0/15, FourHundredGigE 1/0/16
9	FourHundredGigE 1/0/17, FourHundredGigE 1/0/18
10	FourHundredGigE 1/0/19, FourHundredGigE 1/0/20
11	FourHundredGigE 1/0/21, FourHundredGigE 1/0/22
12	FourHundredGigE 1/0/23, FourHundredGigE 1/0/24

Changing a 400-GE interface to a 100-GE interface

1. Enter system view.

system-view

2. Enter 400-GE interface view.

interface fourhundredgige interface-number

3. Change the 400-GE interface to a 100-GE interface.

using hundredgige mode 1-channel

By default, a 400-GE interface is not changed to a 100-GE interface.

Restoring a 100-GE interface changed from a 400-GE interface to a 400-GE interface

1. Enter system view.

system-view

2. Enter the view of a 100-GE interface that was changed from a 400-GE interface.

interface hundredgige interface-number

3. Restore the 100-GE interface to a 400-GE interface.

using fourhundredgige

By default, a 100-GE interface is not restored to a 400-GE interface.

Changing a 400-GE interface to a 200-GE interface and restoring a 200-GE interface changed from a 400-GE interface to a 400-GE interface

About this task

You can use a 400-GE interface as a single interface. To improve network flexibility, you can also change a 400-GE interface to a 200-GE interface. The 200-GE interfaces support the same configuration and attributes as common 200-GE interfaces, except that they are numbered differently and cannot be split. For example, you can change 400-GE interface FourHundredGigE 1/0/1 to 200-GE interface TwoHundredGigE 1/0/1.

If you need higher bandwidth on a single interface, you can restore a 200-GE interface that was changed from a 400-GE interface to a 400-GE interface.

Restrictions and guidelines

A 200-GE interface changed from a 400-GE interface requires a 200-GE transceiver module for communication. An 400-GE interface restored from a 200-GE interface requires a 400-GE transceiver module for communication. For more information about transceiver modules, see the related transceiver module guide for the device.

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

For an S9827-128DH switch, when a 400-GE interface is changed to a 200-GE interface, the 400-GE interfaces in the same interface group are also changed to 200-GE interfaces. When a 200-GE interface is restored to a 400-GE interface, the 200-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 3 shows interface groups of an S9827-128DH switch.

Table 3 Interface groups of an S9827-128DH switch

Interface group number	Interfaces
1	FourHundredGigE 1/0/1, FourHundredGigE 1/0/9
2	FourHundredGigE 1/0/2, FourHundredGigE 1/0/10
3	FourHundredGigE 1/0/3, FourHundredGigE 1/0/4
4	FourHundredGigE 1/0/5, FourHundredGigE 1/0/6
5	FourHundredGigE 1/0/7, FourHundredGigE 1/0/15
6	FourHundredGigE 1/0/8, FourHundredGigE 1/0/16
7	FourHundredGigE 1/0/11, FourHundredGigE 1/0/12
8	FourHundredGigE 1/0/13, FourHundredGigE 1/0/14
9	FourHundredGigE 1/0/17, FourHundredGigE 1/0/25
10	FourHundredGigE 1/0/18, FourHundredGigE 1/0/26
11	FourHundredGigE 1/0/19, FourHundredGigE 1/0/21
12	FourHundredGigE 1/0/20, FourHundredGigE 1/0/22
13	FourHundredGigE 1/0/23, FourHundredGigE 1/0/31
14	FourHundredGigE 1/0/24, FourHundredGigE 1/0/32
15	FourHundredGigE 1/0/27, FourHundredGigE 1/0/29
16	FourHundredGigE 1/0/28, FourHundredGigE 1/0/30
17	FourHundredGigE 1/0/33, FourHundredGigE 1/0/41
18	FourHundredGigE 1/0/34, FourHundredGigE 1/0/42
19	FourHundredGigE 1/0/35, FourHundredGigE 1/0/37
20	FourHundredGigE 1/0/36, FourHundredGigE 1/0/38
21	FourHundredGigE 1/0/39, FourHundredGigE 1/0/47
22	FourHundredGigE 1/0/40, FourHundredGigE 1/0/48
23	FourHundredGigE 1/0/43, FourHundredGigE 1/0/45
24	FourHundredGigE 1/0/44, FourHundredGigE 1/0/46
25	FourHundredGigE 1/0/49, FourHundredGigE 1/0/57
26	FourHundredGigE 1/0/50, FourHundredGigE 1/0/58
27	FourHundredGigE 1/0/51, FourHundredGigE 1/0/52
28	FourHundredGigE 1/0/53, FourHundredGigE 1/0/54
29	FourHundredGigE 1/0/55, FourHundredGigE 1/0/63
30	FourHundredGigE 1/0/56, FourHundredGigE 1/0/64
31	FourHundredGigE 1/0/59, FourHundredGigE 1/0/60
32	FourHundredGigE 1/0/61, FourHundredGigE 1/0/62
33	FourHundredGigE 1/0/65, FourHundredGigE 1/0/73
34	FourHundredGigE 1/0/66, FourHundredGigE 1/0/74
35	FourHundredGigE 1/0/67, FourHundredGigE 1/0/68
36	FourHundredGigE 1/0/69, FourHundredGigE 1/0/70
37	FourHundredGigE 1/0/71, FourHundredGigE 1/0/79
38	FourHundredGigE 1/0/72, FourHundredGigE 1/0/80
39	FourHundredGigE 1/0/75, FourHundredGigE 1/0/76
40	FourHundredGigE 1/0/77, FourHundredGigE 1/0/78
41	FourHundredGigE 1/0/81, FourHundredGigE 1/0/89
42	FourHundredGigE 1/0/82, FourHundredGigE 1/0/90
43	FourHundredGigE 1/0/83, FourHundredGigE 1/0/85
44	FourHundredGigE 1/0/84, FourHundredGigE 1/0/86
45	FourHundredGigE 1/0/87, FourHundredGigE 1/0/95
46	FourHundredGigE 1/0/88, FourHundredGigE 1/0/96
47	FourHundredGigE 1/0/91, FourHundredGigE 1/0/93
48	FourHundredGigE 1/0/92, FourHundredGigE 1/0/94
49	FourHundredGigE 1/0/97, FourHundredGigE 1/0/105
50	FourHundredGigE 1/0/98, FourHundredGigE 1/0/106
51	FourHundredGigE 1/0/99, FourHundredGigE 1/0/101
52	FourHundredGigE 1/0/100, FourHundredGigE 1/0/102
53	FourHundredGigE 1/0/103, FourHundredGigE 1/0/111
54	FourHundredGigE 1/0/104, FourHundredGigE 1/0/112
55	FourHundredGigE 1/0/107, FourHundredGigE 1/0/109
56	FourHundredGigE 1/0/108, FourHundredGigE 1/0/110
57	FourHundredGigE 1/0/113, FourHundredGigE 1/0/121
58	FourHundredGigE 1/0/114, FourHundredGigE 1/0/122
59	FourHundredGigE 1/0/115, FourHundredGigE 1/0/116
60	FourHundredGigE 1/0/117, FourHundredGigE 1/0/118
61	FourHundredGigE 1/0/119, FourHundredGigE 1/0/127
62	FourHundredGigE 1/0/120, FourHundredGigE 1/0/128
63	FourHundredGigE 1/0/123, FourHundredGigE 1/0/124
64	FourHundredGigE 1/0/125, FourHundredGigE 1/0/126

For an S9857-24DH8EP switch, when a 400-GE interface is changed to a 200-GE interface, the 400-GE interfaces in the same interface group are also changed to 200-GE interfaces. When a 200-GE interface is restored to a 400-GE interface, the adjacent 200-GE interfaces in the same interface group are also restored to 400-GE interfaces. Table 4 shows interface groups of an S9857-24DH8EP switch.

Table 4 Interface groups of an S9857-24DH8EP switch

Interface group number	Interfaces
1	FourHundredGigE 1/0/1, FourHundredGigE 1/0/2
2	FourHundredGigE 1/0/3, FourHundredGigE 1/0/4
3	FourHundredGigE 1/0/5, FourHundredGigE 1/0/6
4	FourHundredGigE 1/0/7, FourHundredGigE 1/0/8
5	FourHundredGigE 1/0/9, FourHundredGigE 1/0/10
6	FourHundredGigE 1/0/11, FourHundredGigE 1/0/12
7	FourHundredGigE 1/0/13, FourHundredGigE 1/0/14
8	FourHundredGigE 1/0/15, FourHundredGigE 1/0/16
9	FourHundredGigE 1/0/17, FourHundredGigE 1/0/18
10	FourHundredGigE 1/0/19, FourHundredGigE 1/0/20
11	FourHundredGigE 1/0/21, FourHundredGigE 1/0/22
12	FourHundredGigE 1/0/23, FourHundredGigE 1/0/24

Changing a 400-GE interface to a 200-GE interface

1. Enter system view.

system-view

2. Enter 400-GE interface view.

interface fourhundredgige interface-number

3. Change the 400-GE interface to a 200-GE interface.

using twohundredgige mode 1-channel

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

Restoring a 200-GE interface changed from a 400-GE interface to a 400-GE interface

1. Enter system view.

system-view

2. Enter the view of a 200-GE interface that was changed from a 400-GE interface.

interface twohundredgige interface-number

3. Restore the 200-GE interface to a 400-GE interface.

using fourhundredgige

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

Changing an 800-GE interface to a 400-GE interface and restoring a 400-GE interface changed from an 800-GE interface to an 800-GE interface

About this task

You can use an 800-GE interface as a single interface. To improve network flexibility, you can change an 800-GE interface to a 400-GE interface. The 400-GE interface supports the same configuration and attributes as a common 400-GE interface, except that it is numbered differently and cannot be split. For example, you can change 800-GE interface EightHundredGigE 1/0/1 to 400-GE interface FourHundredGigE 1/0/1.

If you need higher bandwidth, you can restore a 400-GE interface that was changed from an 800-GE interface to an 800-GE interface.

Restrictions and guidelines

A 400-GE interface changed from an 800-GE interface requires a 400-GE transceiver module for communication. An 800-GE interface restored from a 400-GE interface requires an 800-GE transceiver module for communication. For more information about transceiver modules, see the related transceiver module guide for the device.

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

This feature is available only on the S9827-64E switches.

Changing an 800-GE interface to a 400-GE interface

1. Enter system view.

system-view

2. Enter 800-GE Ethernet interface view.

interface eighthundredgige interface-number

3. Change the 800-GE interface to a 400-GE interface.

using fourhundredgige mode 1-channel

By default, an 800-GE interface is not changed and operates as a single interface.

Restoring a 400-GE interface changed from an 800-GE interface to an 800-GE interface

1. Enter system view.

system-view

2. Enter the view of a 400-GE interface that was changed from an 800-GE interface.

interface fourhundredgige interface-number

3. Restore the 400-GE interface to an 800-GE interface.

using eighthundredgige

By default, an 800-GE interface is not changed and operates as a single interface.

Splitting 800-GE interfaces and combining 100-GE breakout interfaces

About this task

You can use an 800-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can split an 800-GE interface into multiple 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.

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

Restrictions and guidelines

An 800-GE interface split into multiple 100-GE breakout interfaces must use a dedicated 1-to-multiple cable. After you combine the 100-GE breakout interfaces, replace the dedicated 1-to-multiple cable with 1-to-1 cable or an 800-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 the 100-GE breakout interfaces, execute the display interface brief command.

Splitting an 800-GE interface into multiple 100-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 800-GE Ethernet interface view.

interface eighthundredgige interface-number

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

using hundredgige [ mode 2-channel ]

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

Combining the multiple 100-GE breakout interfaces into an 800-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 multiple 100-GE breakout interfaces into an 800-GE interface.

using eighthundredgige

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

Splitting 800-GE interfaces and combining 200-GE breakout interfaces

About this task

You can use an 800-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can split an 800-GE interface into multiple 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.

If you need higher bandwidth on a single interface, you can combine the 200-GE breakout interfaces split from an 800-GE interface into an 800-GE interface.

Restrictions and guidelines

An 800-GE interface split into multiple 200-GE breakout interfaces must use a dedicated 1-to-multiple cable. After you combine the 200-GE breakout interfaces, replace the dedicated 1-to-multiple cable with 1-to-1 cable or an 800-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 the 200-GE breakout interfaces, execute the display interface brief command.

Splitting an 800-GE interface into multiple 200-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 800-GE Ethernet interface view.

interface eighthundredgige interface-number

3. Split the 800-GE interface into multiple 200-GE breakout interfaces.

using twohundredgige [ mode 2-channel ]

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

Combining the multiple 200-GE breakout interfaces into an 800-GE interface

4. Enter system view.

system-view

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

interface twohundredgige interface-number

6. Combine the multiple 200-GE breakout interfaces into an 800-GE interface.

using eighthundredgige

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

Splitting 800-GE interfaces and combining 400-GE breakout interfaces

About this task

You can use an 800-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can split an 800-GE interface into two 400-GE breakout interfaces. The 400-GE breakout interfaces support the same configuration and attributes as common 400-GE interfaces, except that they are numbered differently. For example, you can split 800-GE interface EightHundredGigE 1/0/1 into two 400-GE interfaces FourHundredGigE1/0/1:1 and FourHundredGigE1/0/1:2.

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

Restrictions and guidelines

An 800-GE interface split into two 400-GE breakout interfaces must use a dedicated 1-to-2 cable. After you combine the 400-GE breakout interfaces, replace the dedicated 1-to-2 cable with 1-to-1 cable or an 800-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 the 400-GE breakout interfaces, execute the display interface brief command.

When two S9827-64EP switches are connected through 800-GE interfaces, and each of the 800-GE interfaces is split into two 400-GE interfaces, the breakout 400-GE interfaces will be connected in pairs. However, due to the different fiber optic connection sequences of the transceiver modules, the interface numbers of the interconnected breakout interfaces might not correspond in order. For example, if 800-GE interfaces EightHundredGigE 1/0/1 on Device 1 and Device 2 are each split into two 400-GE interfaces FourHundredGigE 1/0/1:1 and FourHundredGigE 1/0/1:2, after the split, FourHundredGigE 1/0/1:1 on Device 1 might be interconnected with FourHundredGigE 1/0/1:1 on Device 2, or it might be interconnected with FourHundredGigE 1/0/1:2 on Device 2.

Splitting an 800-GE interface into two 400-GE breakout interfaces

1. Enter system view.

system-view

2. Enter 800-GE Ethernet interface view.

interface eighthundredgige interface-number

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

using fourhundredgige

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

Combining the two 400-GE breakout interfaces into an 800-GE interface

1. Enter system view.

system-view

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

interface fourhundredgige interface-number

3. Combine the two 400-GE breakout interfaces into an 800-GE interface.

using eighthundredgige

By default, an 800-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, port up-mode, and loopback commands are mutually exclusive.

For information about the bandwidth, description, and shutdown commands, see Interface Command Reference.

The speed 10000 command is available only on the S9827-128DH and S9827-64EP switches.

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, FourHundredGigE 1/0/1 Interface.

4. Set the duplex mode for the Ethernet interface.

duplex { auto | full }

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 { 10000 | 200000 | 400000 | auto }

By default, the speed of an Ethernet interface is autonegotiated.

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, an Ethernet interface is up.

Configuring basic settings of an Ethernet subinterface

About this task

By default, a Layer 3 Ethernet subinterface processes packets with the VLAN tag numbered the same as the subinterface number.

Restrictions and guidelines for Ethernet subinterface basic settings

· Before creating a Layer 3 Ethernet subinterface, do not reserve a resource for the VLAN interface whose interface number is the subinterface number. After you reserve a VLAN interface resource, do not create a Layer 3 Ethernet subinterface whose subinterface number is the VLAN interface number. A Layer 3 Ethernet subinterface uses the VLAN interface resource in processing tagged packets whose VLAN ID matches the subinterface number. For more information about reserving resources for VLAN interfaces, see Layer 2—LAN Switching Configuration Guide.

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

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

· For information about the bandwidth, description, and shutdown commands, see Interface Command Reference.

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, FourHundredGigE1/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, an Ethernet subinterface is up.

Configuring the link mode of an Ethernet interface

About this task

Ethernet interfaces operate differently depending on the hardware structure of interface cards:

· Some Ethernet interfaces can operate only as Layer 2 Ethernet interfaces (in bridge mode).

· Some Ethernet interfaces can operate only as Layer 3 Ethernet interfaces (in route mode).

· Some Ethernet interfaces can operate either as Layer 2 or Layer 3 Ethernet interfaces. You can set the link mode to bridge or route for these Ethernet interfaces.

¡ To configure such an Ethernet interface as a Layer 2 interface, set its link mode to bridge.

¡ To configure such an Ethernet interface as a Layer 3 interface, set its link mode to 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, an interface operates at Layer 2.

‌

CAUTION:

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

‌

Forcibly bringing up a fiber port

About this task

As shown in Figure 1, 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 1 Forcibly bring up a fiber port

‌

Restrictions and guidelines

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

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

Configuring jumbo frame support

About this task

Jumbo frames are frames larger than a fixed size 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 up to 9216 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 spanning tree protocols enabled.

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

On an interface, you can configure different suppression intervals for link-up and link-down events. If you execute the link-delay command multiple times on an interface, the following rules apply:

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

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

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, physical state change suppression is disabled.

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

Any of the following operations can enable link flapping protection:

· Execute the link-flap protect enable batch command in system view, and do not configure link flapping protection on interfaces.

· Execute the link-flap protect enable batch command in system view, and execute the port link-flap protect enable command in interface view.

· Execute the link-flap protect enable command in system view, and execute the port link-flap protect enable command in interface view.

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

If an interface is already configured with the link-delay or dampening command, the link-delay or dampening command applies when you execute the link-flap protect enable batch command.

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

By default, link flapping protection is disabled on all interfaces.

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Configure link flapping protection on the Ethernet interface.

port link-flap protect { disable | enable [ interval interval | threshold threshold ] * }

By default, link flapping protection is not configured on an interface, and the global link flapping protection configuration applies on the 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."

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

Procedure

1. Enter system view.

system-view

2. Enter 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 }

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.

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.

Configuring PFC on an Ethernet interface

Priority-based flow control (PFC) provides a finer flow control mechanism to implement lossless packet transmission on Ethernet. For more information about PFC, see PFC configuration in Layer 2—LAN Switching Configuration Guide.

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.

You can configure this feature in system view or interface view.

· In system view, the command takes effect on all interfaces.

· In interface view, the command takes effect only on the specified interface.

Restrictions and guidelines for setting the statistics polling interval

As a best practice, use the default statistics polling interval in system view. A short statistics polling interval in system view might decrease the system performance and result in inaccurate statistics.

Setting the statistics polling interval in system view

1. Enter system view.

system-view

2. Set the statistics polling interval.

flow-interval interval

The statistics polling interval is 300 seconds.

Setting the statistics polling interval in Ethernet interface view

3. Enter system view.

system-view

4. Enter Ethernet interface view.

interface interface-type interface-number

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

flow-interval interval

By default, the statistics polling interval for an Ethernet interface is 300 seconds.

Enabling subinterface rate statistics collection on an Ethernet interface

Restrictions and guidelines

This feature is resource intensive. When you use this feature, make sure you fully understand its impact on system performance.

After you enable subinterface rate statistics collection on an Ethernet interface, the device periodically refreshes the rate statistics on the subinterfaces of this Ethernet interface.

Procedure

1. Enter system view.

system-view

2. Enter Ethernet interface view.

interface interface-type interface-number

3. Enable subinterface rate statistics collection on the Ethernet interface.

sub-interface rate-statistic

By default, subinterface rate statistics collection is disabled on an Ethernet interface.

4. (Optional.) View the subinterface rate statistics.

display interface

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 inter-device link. The Ethernet interface sends incoming packets back to the remote device. If the remote device fails to receive the packets, the inter-device link fails.

Restrictions and guidelines

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

· The shutdown, port up-mode, and loopback 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. Enable loopback testing.

loopback internal

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. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)

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

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

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

Enabling interface alarm functions

1. Enter system view.

system-view

2. Enable alarm functions for the interface monitoring module.

By default, all alarm functions are enabled for interfaces.

Configuring CRC error packet parameters

3. Enter system view.

system-view

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

5. Enter Ethernet interface view.

interface interface-type interface-number

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

7. Enter system view.

system-view

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

9. Enter Ethernet interface view.

interface interface-type interface-number

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

11. Enter system view.

system-view

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

13. Enter Ethernet interface view.

interface interface-type interface-number

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

15. Enter system view.

system-view

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

17. Enter Ethernet interface view.

interface interface-type interface-number

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

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

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

Configuring the LBN group feature

About this task

Load Balance Network (LBN) is a load balancing technique that improves network throughput. In scenarios with high network performance requirements, you can use LBN to improve network throughput. This feature assigns different incoming interfaces on the device to an LBN 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, which achieves traffic load sharing.

You can configure a LBN group in ECMP mode or Ethernet link aggregation mode as needed. The ECMP-mode LBN group feature is available only on a network configured with ECMP. The Ethernet link aggregation mode LBN 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 an LBN 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 LBN group.

When the device automatically assigns indexes to interfaces, it allocates the smallest current index to the first interface configured at the CLI. Then, it assigns indexes to the remaining interfaces in ascending order of their interface numbers.

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. If removing an interface from an LBN group results in discontinuous interface indexes, you must manually adjust the indexes to have them become continuous again.

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

IRF physical ports cannot be assigned to an LBN group.

An interface can belong to only one LBN group.

The display ip load-sharing path command does not take effect on an interface in an LBN group.

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

Using the port link-mode command to change the link mode of a member interface or splitting a member interface will remove that interface from the LBN group.

Procedure

1. Enter system view.

system-view

2. Create an LBN group and enter its view.

rail-group group-name

3. Assign interfaces to the LBN 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 LBN group feature.

loadbalance ecmp lbn-group enable

By default, this feature is disabled.

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

loadbalance link-aggregation lbn-group enable

By default, this feature is disabled.

7. (Optional.) Set a mode for the ECMP-mode LBN group feature.

loadbalance ecmp lbn-group mode enhanced-fixed

By default, the LBN group mode is common mode. If both the traffic incoming and outgoing interfaces belong to LBN groups and the number of incoming interfaces is an integer multiple of outgoing interfaces, the LBN group mode is enhanced mode.

Enabling queue buffer monitoring on an interface

About this task

With this feature configured, the device will perform the following actions:

· Collect buffer data for a queue periodically, and report the collected data at intervals of one second to the gRPC or NETCONF module.

· Monitor the buffer usage and microbursts for a specified queue periodically. When a microburst event occurs, the device reports the event to the gRPC or NETCONF module.

The device periodically monitors the queue buffer usage every 100ms to detect and report microburst events.

Table 5 describes the conditions for triggering and reporting a microburst event.

Table 5 Conditions for triggering a microburst event

Scenario

Conditions for triggering a microburst event

Conditions for reporting a microburst event

Scenario 1

Both of the following conditions are met:

· The queue buffer usage higher than the upper threshold or the lower threshold is 0%.

· The queue buffer usage has increased by more than 2% compared to the last interval.

If microbursts occur more than 1 second after the last reported microburst event, the device will report a microburst event. If the time when the last microburst event was reported cannot be obtained, the device determines it as the first microburst event and reports it directly.

Scenario 2

Both of the following conditions are met:

· The queue buffer usage is not higher than the upper threshold and not lower than the lower threshold.

· The queue buffer usage has increased by more than 2% compared to the last interval.

Both of the following conditions are met:

· Microbursts were detected in the last detection period.

· If microbursts occur more than 1 second after the last reported microburst event, the device will report a microburst event. If the time when the last microburst event was reported cannot be obtained, the device determines it as the first microburst event and reports it directly.

As shown in Table 5Figure 3:

· For scenario 1:

¡ Microbursts occurred at T0 for the first time. The device will directly report a microburst event.

¡ Microbursts occurred at T0+0.5s and T0+0.8s, but not more than 1 second after the last reported microburst event. The device will not report a microburst event.

¡ Microbursts occurred at T0+1.5s, more than 1 second after the last reported microburst event. The device will report a microburst event.

¡ Microbursts occurred at T0+1.6s, but not more than 1 second after the last reported microburst event. The device will not report a microburst event.

· For scenario 2:

¡ Microbursts occurred at T0 for the first time. The device will directly report a microburst event.

¡ Microbursts occurred at T0+0.5s and T0+0.8s, but not more than 1 second after the last reported microburst event. The device will not report a microburst event.

¡ Microbursts occurred at T0+1.5s, more than 1 second after the last reported microburst event. However, no microbursts occurred at T0+1.4s in the last period. The device will not report a microburst event.

¡ Microbursts occurred at T0+1.6s, more than 1 second after the last reported microburst event, and microbursts occurred at T0+1.5s in the last period. The device will report a microburst event.

Figure 3 Conditions for triggering a microburst event

Restrictions and guidelines

Before you configure queue buffer monitoring on an interface, you must first execute the ifmonitor buffer mode command.

To disable or change the buffer data monitoring mode for a card, you must first execute the undo port ifmonitor buffer queue enable command.

Procedure

1. Enter system view.

system-view

2. Set the buffer data monitoring mode for a card.

ifmonitor buffer mode standard slot slot-number

undo ifmonitor buffer mode slot slot-number

3. Enter Ethernet interface view.

interface interface-type interface-number

4. Enable buffer monitoring for a queue.

port ifmonitor buffer queue queue-index enable [ interval interval ]

Buffer monitoring is disabled for queues.

5. (Optional.) Set the upper and lower buffer usage thresholds on a queue.

port ifmonitor buffer queue queue-index threshold high high-percent low low-percent

The upper and lower buffer usage thresholds on a queue are 80% and 30%, respectively.

Shutting down all interfaces

About this task

This feature allows you to shut down all interfaces except the management Ethernet interfaces, IRF physical interfaces, and interfaces excluded from shutdown on a device. For an interface that supports subinterfaces, only the main interface is shut down, and its subinterfaces will not be shut down by this command. However, after the main interface is shutdown, its subinterfaces will go down and cannot forward packets. In this case, if you execute the display this command on an interface that is shut down, the output shows that the shutdown command is automatically generated on the interface.

To bring up an interface shut down by using the shutdown all-interfaces command, you can execute the undo shutdown command in interface view or the undo shutdown all-interfaces command in system view.

Procedure

1. Enter system view.

system-view

2. Shut down all physical interfaces.

shutdown all-interfaces exclude interface-list

By default, a physical interface is up.

Enabling automatic speed reduction for an interface

About this task

With this feature enabled, if an underlying data forwarding channel of an interface fails, the interface state will not change to down. Instead, it continues to use the remaining underlying data forwarding channels that are operating correctly and automatically decreases its speed, for example, from 400G to 200G.

Restrictions and guidelines

After you execute the speed auto-reduction enable command, the interface speed decreases automatically only when an underlying data forwarding channel fails.

The undo speed auto-reduction enable command restore the speed of an interface. To restore the speed of an interface, execute the speed auto-reduction restore command.

Procedure

1. Enter system view.

system-view

2. Enter interface view..

interface interface-type interface-number

3. Enable automatic speed reduction.

speed auto-reduction enable

By default, automatic speed reduction is disabled.

4. Restore the speed of the interface.

speed auto-reduction restore

Shutting down all physical interfaces

About this task

This feature allows you to shut down all physical interfaces except the management Ethernet interfaces on a 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 a shutdown interface, execute the undo shutdown all-physical-interfaces command in system view and execute the undo shutdown command in interface view.

Procedure

1. Enter system view.

system-view

2. Shut down all physical interfaces.

shutdown all-physical-interfaces

By default, a physical interface is 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.

For information about the default command, see Interface Command Reference.

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, known unicast, 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 | known-unicast | 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.

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

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.

Additionally, when a Layer 3 Ethernet subinterface is created, it uses the MAC address of its main interface by default. As a result, all Layer 3 Ethernet subinterfaces of a Layer 3 Ethernet interface share the same MAC address. To set a different MAC address for a Layer 3 Ethernet subinterface, use the mac-address command.

Restrictions and guidelines

When you set a MAC address, make sure the following requirements are met:

· The MAC address must have the same highest 36 bits as the base MAC address.

· The MAC address must be no lower than the base MAC address plus 160 (decimal).

For more information about base MAC address, see MAC address table in Layer 2—LAN Switching Configuration Guide.

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 configured for an interface. The default MAC address for a Layer 3 Ethernet subinterface is the same as the MAC address of its main interface.

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

Verifying and maintaining Ethernet interfaces

Displaying the configuration and running status of Ethernet interfaces

Perform all display tasks in any view.

· Display the running status and related information of the specified interfaces.

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

· Display link flapping protection information on the specified interfaces.

display link-flap protection [ interface interface-type [ interface-number ] ]

· Display PFC information on the specified interfaces.

display priority-flow-control interface [ interface-type [ interface-number ] ]

· Display storm control information on the specified interfaces.

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

Displaying and clearing Ethernet interface statistics

Displaying Ethernet interface statistics

Perform all display tasks in any view.

· Display interface traffic statistics.

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

For information about this command, see common interface commands in Interface Command Reference.

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

For information about this command, see common interface commands in Interface Command Reference.

· Display Flight Data Recorder (FDR) statistics for an interface.

display fdr-statistics interface [ interface-type [ interface-number ] ]

· Display information about packets dropped on an interface.

display packet-drop { interface [ interface-type [ interface-number ] ] | summary }

· Display the flow statistics collection result.

display ifmonitor buffer flow-information [ interface interface-type interface-number ]

· Display monitoring and data collection statistics for the buffer on an interface.

display ifmonitor buffer statistics interface interface-type interface-number [ queue queue-index ] [ last number ]

· Display packet latency detection statistics.

display ifmonitor latency-detection statistics [ interface interface-type interface-number ]

Clearing Ethernet interface statistics

Perform all clear tasks in user view.

· Clear Ethernet interface statistics.

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

For information about this command, see common interface commands in Interface Command Reference.

· Clear the dropped packet statistics for an interface.

reset packet-drop interface [ interface-type [ interface-number ] ]

Displaying and clearing Ethernet module statistics

Displaying Ethernet module statistics

To display the Ethernet module statistics, execute the following command in any view:

display ethernet statistics slot slot-number

Clearing Ethernet module statistics

To clear the Ethernet module statistics, execute the following command in user view:

reset ethernet statistics [ slot slot-number ]

Displaying and clearing physical link state change statistics of interfaces

Displaying physical link state change statistics of interfaces

To display physical link state change statistics of interfaces, execute the following command in any view:

display link-state-change statistics interface [ interface-type [ interface-number ] ]

Clearing physical link state change statistics of interfaces

To clear physical link state change statistics of interfaces, execute the following command in user view:

reset link-state-change statistics interface [ interface-type [ interface-number ] ]

Displaying LBN group information

To display LBN group information, execute the following command in any view:

display lbn-group status

03-Interface Configuration Guide

Configuring Ethernet interfaces

About Ethernet interface

About this task

Procedure

Configuring common Ethernet interface settings

About this task

Restrictions and guidelines

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

Combining the multiple 100-GE breakout interfaces into a 400-GE interface

About this task

Restrictions and guidelines

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

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

About this task

Restrictions and guidelines

Changing a 400-GE interface to a 100-GE interface

Restoring a 100-GE interface changed from a 400-GE interface to a 400-GE interface

About this task

Restrictions and guidelines

Changing a 400-GE interface to a 200-GE interface

Restoring a 200-GE interface changed from a 400-GE interface to a 400-GE interface

About this task

Restrictions and guidelines

Changing an 800-GE interface to a 400-GE interface

Restoring a 400-GE interface changed from an 800-GE interface to an 800-GE interface

About this task

Restrictions and guidelines

Splitting an 800-GE interface into multiple 100-GE breakout interfaces

Combining the multiple 100-GE breakout interfaces into an 800-GE interface

About this task

Restrictions and guidelines

Splitting an 800-GE interface into multiple 200-GE breakout interfaces

Combining the multiple 200-GE breakout interfaces into an 800-GE interface

About this task

Restrictions and guidelines

Splitting an 800-GE interface into two 400-GE breakout interfaces

Combining the two 400-GE breakout interfaces into an 800-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

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Parameters

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Setting the statistics polling interval

About this task

Setting the statistics polling interval in Ethernet interface view

Enabling subinterface rate statistics collection on an Ethernet interface

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Enabling interface alarm functions

Configuring CRC error packet parameters

Configuring input error packet alarm parameters