03-Layer 2—LAN Switching Configuration Guide

HomeSupportSwitchesS6860 SeriesConfigure & DeployConfiguration GuidesH3C S6860 Switch Series Configuration Guide-Release 26xx-6W10303-Layer 2—LAN Switching Configuration Guide
01-Ethernet interface configuration
Title Size Download
01-Ethernet interface configuration 207.78 KB

Contents

Configuring Ethernet interfaces· 1

Ethernet interface naming conventions· 1

Configuring a management Ethernet interface· 1

Configuration restrictions and guidelines for Ethernet interfaces on the S6860 switch series· 2

Configuring common Ethernet interface settings· 2

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

Combining 40-GE interfaces and splitting a 100-GE interface· 3

Configuring basic settings of an Ethernet interface or subinterface· 4

Configuring the link mode of an Ethernet interface· 6

Configuring jumbo frame support 6

Configuring physical state change suppression on an Ethernet interface· 7

Configuring dampening on an Ethernet interface· 7

Enabling link flapping protection on an interface· 9

Enabling loopback testing on an Ethernet interface· 10

Configuring generic flow control on an Ethernet interface· 10

Setting PFC thresholds· 11

Setting the statistics polling interval 13

Configuring storm suppression· 13

Enabling remote fault signal detection· 14

Configuring a Layer 2 Ethernet interface· 14

Configuring storm control on an Ethernet interface· 14

Forcibly bringing up a fiber port 16

Setting the MDIX mode of an Ethernet interface· 17

Testing the cable connection of an Ethernet interface· 18

Enabling bridging on an Ethernet interface· 18

Setting the interface connection distance· 18

Configuring a Layer 3 Ethernet interface or subinterface· 19

Setting the MTU for an Ethernet interface or subinterface· 19

Setting the MAC address of an Ethernet interface or subinterface· 19

Enabling packet statistics collection on an Ethernet subinterface· 20

Displaying and maintaining an Ethernet interface or subinterface· 20


Configuring Ethernet interfaces

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.

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 or virtual slot number of the PEX on an IRF 3.1 system. 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.

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

Configuring a management Ethernet interface

A management interface uses an RJ-45 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.

In an IRF system, each member device has physical management Ethernet interfaces. To back up a management link, use a cable to connect two management Ethernet interfaces of the same number on the master device and a subordinate device. The two management Ethernet interfaces back up each other as follows:

·           When the management Ethernet interface on the master device is in normal state, it is the only one that processes management traffic.

·           When the management Ethernet interface on the master device fails, the management Ethernet interface on the subordinate device takes over to process management traffic.

·           When the management Ethernet interface on the master device recovers, it takes over to process management traffic again.

To configure a management Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter management Ethernet interface view.

interface M-GigabitEthernet interface-number

N/A

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.

 

Configuration restrictions and guidelines for Ethernet interfaces on the S6860 switch series

By default, the six highest-numbered interfaces on this switch series are 40-GE interfaces. Among them, three proximate odd-numbered interfaces (for example, interfaces 49, 51, and 53 or 25, 27, and 29) are in one group and three proximate even-numbered interfaces (for example, interfaces 50, 52, and 54 or 26, 28, and 29) are in one group. To combine three 40-GE interfaces in one group into a 100-GE interface, execute the using hundredgige command on any 40-GE interface in the group. After combination, only the two highest-numbered 100-GE interfaces are usable (interfaces numbered 53 and 54, or interfaces numbered 29 and 30). To restore a 100-GE interface back to 40-GE interfaces, executing the using fortygige command on the 100-GE interface.

If any 40-GE interface in a group is split into four 10-GE interfaces, interfaces in the group cannot be combined into a 100-GE interface.

If any 40-GE interface in a group is configured as an IRF physical interface, the using hundredgige command is not supported on any interface in the group.

If any 100-GE interface is configured as an IRF physical interface, the using fortygige command is not supported on the interface.

Interfaces numbered 29 through 36 on the S6860-54HF switch do not support 1000-Mbps SFP modules.

Interfaces numbered 29 through 36 on the S6860-54HT switch can be only set to 10000 Mbps or configured to negotiate a speed with its peer. The negotiated speed can only be 10000 Mbps.

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 or subinterfaces, 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

IMPORTANT

IMPORTANT:

On this switch series, a 100-GE interface with a 40-GE transceiver module installed cannot be split into four 10-GE breakout interfaces.

 

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

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.

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.

After you configure this feature on a 40-GE interface, the system deletes the 40-GE interface and creates the four 10-GE breakout interfaces.

After the using tengige command is successfully configured, you do not need to reboot the switch. You can view the four 10-GE breakout interfaces by using the display interface brief command.

A 40-GE interface split into four 10-GE breakout interfaces must use a dedicated 1-to-4 cable. For more information about the cable, see the installation guides.

To split a 40-GE interface into four 10-GE breakout interfaces:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter 40-GE interface view.

interface interface-type interface-number

N/A

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.

The 10-GE breakout interfaces support the same configuration and attributes as common 10-GE interfaces, except that they are numbered differently.

 

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

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

After you configure this feature on a 10-GE breakout interface, the system deletes the four 10-GE breakout interfaces and creates the 40-GE interface.

After the using fortygige command is successfully configured, you do not need to reboot the switch. You can view the 40-GE interface by using the display interface brief command.

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.

To combine four 10-GE breakout interfaces into a 40-GE interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

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

interface interface-type interface-number

N/A

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.

 

Combining 40-GE interfaces and splitting a 100-GE interface

Combining three 40-GE interfaces into a 100-GE interface

If you need higher bandwidth on a single interface, you can combine three 40-GE interfaces into a 100-GE interface.

After you combine the three 40-GE interfaces, use a 100-GE transceiver module. For more information about the  transceiver module, see the installation guides.

After you configure this feature on a 40-GE interface, you do not need to reboot the switch. You can view the 100-GE interface by using the display interface brief command.

To combine three 40-GE interfaces into a 100-GE interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter the view of any 40-GE interface.

interface fortygige interface-number

N/A

3.      Combine three 40-GE interfaces into a 100-GE interface.

using hundredgige

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

 

Splitting a 100-GE interface into three 40-GE breakout interfaces

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 three 40-GE breakout interfaces.

After you configure this feature on a 100-GE interface, you do not need to reboot the switch. You can view the three 40-GE breakout interfaces by using the display interface brief command.

To split a 100-GE interface into three 40-GE breakout interfaces:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter 100-GE interface view.

interface hundredgige interface-number

N/A

3.      Split the 100-GE interface into three 40-GE breakout interfaces.

using fortygige

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

 

Configuring basic settings of an Ethernet interface or subinterface

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.

Configuring an Ethernet interface

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Set the description for the Ethernet interface.

description text

The default setting is interface-name Interface. For example, Ten-GigabitEthernet1/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.

Copper ports operating at 1000 Mbps or 10 Gbps and fiber ports do not support the half keyword.

5.      Set the speed for the Ethernet interface.

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

The default setting is auto for Ethernet interfaces.

Support for the keywords depends on the interface type and the transceiver module and device models. The actual support of an interface varies by device. If a configured interface speed is not supported, the system prompts “The operation is not supported.”

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.      Restore the default settings for the Ethernet interface.

default

N/A

8.      Bring up the Ethernet interface.

undo shutdown

By default, Ethernet interfaces are in up state.

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

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

 

Configuring an Ethernet subinterface

To associate a VPN instance with a Layer 3 Ethernet subinterface, make sure one or more of the following conditions are met:

·           A Layer 3 aggregate subinterface and a VLAN interface that have the same number as the Layer 3 Ethernet subinterface are associated with the same VPN instance.

·           Packet statistics is enabled on the Layer 3 Ethernet subinterface.

For more information about Layer 3 aggregate subinterfaces, see Ethernet link aggregation in Layer 2—LAN Switching Configuration Guide. For more information about VLAN interfaces, see VLAN in Layer 2—LAN Switching Configuration Guide. For more information about associating a VPN instance with an interface, see MPLS L3VPN and MCE in MPLS Configuration Guide.

To configure an Ethernet subinterface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Create an Ethernet subinterface.

interface interface-type interface-number.subnumber

N/A

3.      Set the description for the Ethernet subinterface.

description text

The default setting is interface-name Interface. For example, Ten-GigabitEthernet1/0/1.1 Interface.

4.      Restore the default settings for the Ethernet subinterface.

default

N/A

5.      Set the expected bandwidth for the Ethernet subinterface.

bandwidth bandwidth-value

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

6.      Bring up the Ethernet subinterface.

undo shutdown

By default, Ethernet subinterfaces are in up state.

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

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

 

Configuring the link mode of an Ethernet interface

The interfaces on this Switch Series can operate either as Layer 2 or Layer 3 Ethernet interfaces.

You can set the link mode to bridge or route.

To configure the link mode of an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Configure the link mode of the Ethernet interface.

port link-mode { bridge | route }

By default, Ethernet interfaces operate in bridge mode.

 

WARNING

CAUTION:

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

 

Configuring jumbo frame support

An Ethernet interface might receive frames larger than the device-specific Ethernet frame size during high-throughput data exchanges, such as file transfers. These frames are called jumbo frames.

The Ethernet interface processes jumbo frames in the following ways:

·           When the Ethernet interface is configured to deny jumbo frames, 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.

To configure jumbo frame support in interface view:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Configure jumbo frame support.

jumboframe enable [ size ]

By default, the switch allows jumbo frames within 10000 bytes to pass through all Ethernet interfaces.

 

Configuring physical state change suppression on an Ethernet interface

IMPORTANT

IMPORTANT:

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

 

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.

When you configure this feature, follow these guidelines:

·           To suppress only link-down events, configure the link-delay [ msec ] delay-time command.

·           To suppress only link-up events, configure the link-delay [ msec ] delay-time mode up command.

·           To suppress both link-down and link-up events, configure the link-delay [ msec ] delay-time mode updown command.

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

To configure physical state change suppression on an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Configure physical state change suppression.

link-delay [ msec ] delay-time [ mode { up | updown }]

By default, the link-down or link-up event is immediately reported to the CPU.

If you configure this command multiple times on an Ethernet interface, the most recent configuration takes effect.

 

Configuring dampening on an Ethernet interface

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

 

Configuration restrictions and guidelines

When you configure dampening on an Ethernet interface, follow these 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.

Configuration procedure

To configure dampening on an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

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 link flapping protection

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.

Configuration restrictions and guidelines

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

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.

Configuration procedure

To enable link flapping protection on an interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enable link flapping protection on all interfaces.

link-flap protect enable

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

3.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

4.      Enable link flapping protection on an interface.

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

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

 

Enabling loopback testing on an Ethernet interface

CAUTION

CAUTION:

After you enable this feature on an Ethernet interface, the interface cannot forward data traffic correctly.

 

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.

Configuration restrictions and guidelines

·           On an administratively shut down Ethernet interface (displayed as in ADM or Administratively DOWN state), you cannot perform an internal or external loopback test.

·           The speed, duplex, mdix-mode, and shutdown commands are not available during a loopback test.

·           A loopback test cannot be performed on an interface configured with the port up-mode command.

·           During a loopback test, the Ethernet interface operates in full duplex mode. When a loopback test is complete, the port returns to its duplex setting.

·           In IRF 3.1, loopback testing enabled on an interface of the parent device is disabled until you execute the undo loopback command. Loopback testing enabled on an interface of a PEX is disabled after the test is performed for once. For more information about parent devices and PEXs, see Virtual Technologies Configuration Guide.

Configuration procedure

To enable loopback testing on an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Enable loopback testing.

loopback { external | internal }

By default, no loopback test is performed.

 

Configuring generic flow control on an Ethernet interface

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.

This feature is mutually exclusive with enabling PFC for 802.1p priorities.

To enable generic flow control on an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Enable generic flow control.

·           Enable TxRx-mode generic flow control:
flow-control

·           Enable Rx-mode generic flow control:
flow-control receive enable

By default, generic flow control is disabled on an Ethernet interface.

 

Setting PFC thresholds

The storage spaces for an interface include the following types:

·           Headroom storage space.

·           Shared storage space.

·           Guaranteed storage space.

Setting PFC thresholds enables flexible control over PFC and can make good use of the storage spaces. The switch supports the following PFC thresholds:

·           Headroom buffer thresholdMaximum cell resources that can be used by packets with the specified 802.1p priority values in a headroom storage space. An interface drops received packets once this threshold is reached.

·           Back pressure frame triggering threshold—Maximum cell resources that can be used by packets with the specified 802.1p priority values in a shared storage space. PFC is triggered once this threshold is reached. The back pressure frame triggering threshold includes the following types:

¡  Dynamic back pressure frame triggering threshold—Maximum cell resources set in percentage.

¡  Static back pressure frame triggering threshold—Maximum cell resources set in an absolute value.

·           Back pressure frame stopping threshold—Number of cell resources that are used by packets with the specified 802.1p priority values. When this threshold is reached after PFC is triggered, PFC will be stopped.

·           PFC reserved threshold—Number of cell resources reserved for packets with the specified 802.1p priority values in a guaranteed storage space.

Configuration restrictions and guidelines

CAUTION

CAUTION:

After PFC for 802.1p priorities is enabled, each PFC threshold mentioned above uses a default value, which is adequate in typical network environments. As a practice, do not change the default value.

 

You must enable PFC for 802.1p priorities before setting the PFC thresholds.

If you cancel PFC threshold configurations on an interface, the PFC thresholds are restored to the state when only the priority-flow-control no-drop dot1p command is executed.

This feature does not support preprovisioning. For more information about preprovisioning, see Fundamentals Configuration Guide.

Enabling PFC for 802.1p priorities is mutually exclusive with generic flow control on an interface.

Configuration procedure

To set PFC thresholds:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Set the maximum cell resources that can be used in a headroom storage space.

priority-flow-control headroom headroom-number

By default, the number of maximum cell resources that can be used is 12288.

3.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

4.      Enable PFC for 802.1p priorities.

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

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

5.      Set the headroom buffer threshold.

priority-flow-control dot1p dot1p headroom headroom-number

By default, the headroom buffer threshold is 1000 for 10-GE interfaces and 4000 for 40-GE interfaces.

6.      Set the headroom buffer threshold.

·           Set the dynamic back pressure frame triggering threshold:
priority-flow-control dot1p dot1p ingress-buffer dynamic ratio

·           Set the static back pressure frame triggering threshold:
priority-flow-control dot1p
dot1p ingress-buffer static threshold

By default:

·           No dynamic back pressure frame triggering threshold is set.

·           The static back pressure frame triggering threshold is 250 for 10-GE interfaces and 1000 for 40-GE interfaces.

7.      Set the back pressure frame stopping threshold.

priority-flow-control dot1p dot1p ingress-threshold-offset offset-number

By default, the back pressure frame stopping threshold is 51 for 10-GE interfaces and 204 for 40-GE interfaces.

8.      Set the PFC reserved threshold.

priority-flow-control dot1p dot1p reserved-buffer reserved-number

By default, the PFC reserved threshold is 15.

 

Setting the statistics polling interval

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

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

flow-interval interval

By default, the statistics polling interval is 300 seconds.

 

To display the interface statistics collected in the last statistics polling interval, use the display interface command.

Configuring storm suppression

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. An interframe gap exists between each two continuous frames. The system excludes the time of interframe gaps in monitoring the traffic size on the interface. The configured suppression thresholds must be less than the total traffic that passes through the interface.

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.

Configuration restrictions and guidelines

When you configure storm suppression, follow these 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.

·           Storm suppression configured on a Layer 3 Ethernet interface also takes effect on its subinterfaces if the interface is on the following networks:

¡  Border of a VXLAN IP gateway network.

¡  Border of a EVPN gateway network.

For more information about VXLAN IP gateway and EVPN gateway networks, see VXLAN Configuration Guide and EVPN Configuration Guide.

Configuration procedure

To set storm suppression thresholds on an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

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.

 

Enabling remote fault signal detection

A fiber port forwards packets by using two optical fibers or only one optical fiber. Whether one optical fiber or two optical fibers are used by a fiber port depends on the fiber port model.

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

If a fiber port uses only one optical fiber, the physical state of the port becomes down when the port receives a remote fault signal. To keep the port in up state to operate correctly upon receiving a remote fault signal, disable remote fault signal detection on the port.

Configuration restrictions and guidelines

Only fiber ports support this feature.

Configuration procedure

To enable remote fault signal detection:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter interface view.

interface interface-type interface-number

N/A

3.      Enable remote fault signal detection.

link-fault-signal enable

By default, remote fault signal detection is enabled.

 

Configuring a Layer 2 Ethernet interface

Configuring storm control on an Ethernet interface

About storm control

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.

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.

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.

Configuration 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 suppression, see "Configuring storm suppression."

Configuration procedure

To configure storm control on an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

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

N/A

4.      (Optional.) 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 } max-pps-values min-pps-values

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.      (Optional.) 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.

7.      (Optional.) 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.

Forcibly bringing up a fiber port

IMPORTANT

IMPORTANT:

Copper ports do not support this feature.

 

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

 

Configuration restrictions and guidelines

When you forcibly bring up a fiber port, follow these restrictions and guidelines:

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

·           The following operations on a fiber port will cause link updown events before the port finally stays up:

¡  Configure both the port up-mode command and the speed or duplex command.

¡  Install or remove fiber links or transceiver modules after you forcibly bring up the fiber port.

·           Do not use this feature on a fiber port connected to a copper cable.

Configuration procedure

To forcibly bring up a fiber port:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

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 MDIX mode of an Ethernet interface

IMPORTANT

IMPORTANT:

Fiber ports do not support the MDIX mode setting.

 

A physical Ethernet interface has eight pins, each of which plays a dedicated role. For example, pins 1 and 2 transmit signals, and pins 3 and 6 receive signals. You can use both crossover and straight-through Ethernet cables to connect copper Ethernet interfaces. To accommodate these types of cables, a copper Ethernet interface can operate in one of the following Medium Dependent Interface-Crossover (MDIX) modes:

·           MDIX mode—Pins 1 and 2 are receive pins and pins 3 and 6 are transmit pins.

·           MDI mode—Pins 1 and 2 are transmit pins and pins 3 and 6 are receive pins.

·           AutoMDIX mode—The interface negotiates pin roles with its peer.

 

 

NOTE:

This feature does not take effect on pins 4, 5, 7, and 8 of physical Ethernet interfaces.

·       Pins 4, 5, 7, and 8 of interfaces operating at 10 Mbps or 100 Mbps do not receive or transmit signals.

·       Pins 4, 5, 7, and 8 of interfaces operating at 1000 Mbps or higher rates receive and transmit signals.

 

To enable a copper Ethernet interface to communicate with its peer, set the MDIX mode of the interface by following these guidelines:

·           Typically, set the MDIX mode of the interface to AutoMDIX. Set the MDIX mode of the interface to MDI or MDIX only when the device cannot determine the cable type.

·           When a straight-through cable is used, configure the interface to operate in an MDIX mode different than its peer.

·           When a crossover cable is used, perform one of the following tasks:

¡  Configure the interface to operate in the same MDIX mode as its peer.

¡  Configure either end to operate in AutoMDIX mode.

To set the MDIX mode of an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Set the MDIX mode of the Ethernet interface.

mdix-mode { automdix | mdi | mdix }

By default, a copper Ethernet interface operates in auto mode to negotiate pin roles with its peer.

10-GE interfaces support only the automdix mode.

 

Testing the cable connection of an Ethernet interface

IMPORTANT

IMPORTANT:

If the link of an Ethernet interface is up, testing its cable connection will cause the link to go down and then come up.

 

 

NOTE:

Fiber ports do not support this feature.

 

This feature tests the cable connection of an Ethernet interface and displays cable test result within 5 seconds. The test result includes the cable's status and some physical parameters. If any fault is detected, the test result shows the length from the local port to the faulty point.

To test the cable connection of an Ethernet interface:

 

Step

Command

1.      Enter system view.

system-view

2.      Enter Ethernet interface view.

interface interface-type interface-number

3.      Perform a test for the cable connected to the Ethernet interface.

virtual-cable-test

 

Enabling bridging on an Ethernet interface

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.

To enable bridging on an Ethernet interface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

3.      Enable bridging on the Ethernet interface.

port bridge enable

By default, bridging is disabled on an Ethernet interface.

 

Setting the interface connection distance

When two directly connected interfaces communicate, they use the buffer area to buffer the received data. A longer interface connection distance requires a greater buffer area.

Perform this task to modify the buffer area size by setting the interface connection distance.

To set the interface connection distance:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

N/A

3.      Set the interface connection distance.

port connection-distance { 300 | 10000 | 20000 | 40000 }

By default, the interface connection distance is 10000 meters.

 

Configuring a Layer 3 Ethernet interface or subinterface

Setting the MTU for an Ethernet interface or subinterface

The maximum transmission unit (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.

To set the MTU for an Ethernet interface or subinterface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface or subinterface view.

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

N/A

3.      Set the MTU of the Ethernet interface or subinterface.

mtu size

The default setting is 1500 bytes.

 

Setting the MAC address of an Ethernet interface or subinterface

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.

The mac-address command cannot be executed on Layer 3 Ethernet interfaces or subinterfaces of border gateways in VXLAN IP gateway and EVPN gateway networks.

To avoid transmission failure, do not set the MAC address of an Ethernet interface or subinterface to one of the reserved MAC addresses. To avoid transmission failure after IRF master/ subordinate switchover, do not set the MAC address of an Ethernet interface or subinterface to a reserved MAC address of an IRF member device. For the S6860-54HF and S6860-54HT switches, MAC addresses from the bridge MAC address of the device to the bridge MAC address plus 113 are reserved MAC addresses of the device. For the S6860-30HF switches, MAC addresses from the bridge MAC address of the device to the bridge MAC address plus 89 are reserved MAC addresses of the device. For more information about IRF bridge MAC addresses, see IRF in Virtual Technologies Configuration Guide.

To set the MAC address of an Ethernet interface or subinterface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet interface or subinterface view.

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

N/A

3.      Set the MAC address of the Ethernet interface or subinterface.

mac-address mac-address

By default, no MAC address is set for a Layer 3 Ethernet interface or subinterface.

 

Enabling packet statistics collection on an Ethernet subinterface

A Layer 3 Ethernet subinterface with this feature enabled cannot act as a VXLAN tunnel outgoing interface.

To enable packet statistics collection on an Ethernet subinterface:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter Ethernet subinterface view.

interface interface-type interface-number.subnumber

N/A

3.      Enable packet statistics collection on the Ethernet subinterface.

traffic-statistic enable

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

4.      (Optional.) Display the Ethernet subinterface packet statistics.

·           display interface

·           display counters

The Input and Output fields in the display interface command output display the Ethernet subinterface packet statistics.

 

Displaying and maintaining an Ethernet interface or subinterface

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

 

Task

Command

Display interface traffic statistics.

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

Display traffic rate statistics of interfaces in up state over the last statistics polling interval.

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

Display the operational and status information of the specified interfaces.

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

Display information about link flapping protection on an interface.

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

Display information about dropped packets on the specified interfaces.

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

Display the PFC information for an interface.

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

Display information about storm control on the specified interfaces.

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

Display the Ethernet module statistics.

display ethernet statistics slot slot-number

Clear interface or subinterface statistics.

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

Clear the statistics of dropped packets on the specified interfaces.

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

Clear the Ethernet module statistics.

reset ethernet statistics [ slot slot-number ]

 

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网