Contents

Configuring Ethernet interfaces· 1

About Ethernet interface· 1

Configuring a management Ethernet interface· 1

Ethernet interface naming conventions· 1

Configuring common Ethernet interface settings· 2

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

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

Configuring basic settings of an Ethernet interface· 3

Configuring jumbo frame support 4

Configuring physical state change suppression on an Ethernet interface· 5

Configuring dampening on an Ethernet interface· 5

Configuring FEC· 7

Configuring storm suppression· 7

Configuring generic flow control on an Ethernet interface· 8

Configuring PFC· 9

Setting the statistics polling interval 10

Enabling loopback testing on an Ethernet interface· 11

Forcibly bringing up a fiber port 11

Restoring the default settings for an interface· 13

Configuring a Layer 2 Ethernet interface· 13

Setting the interface connection distance· 13

Configuring storm control on an Ethernet interface· 13

Display and maintenance commands for Ethernet interfaces· 15

 

 

Configuring Ethernet interfaces

About Ethernet interface

The switching module supports Ethernet interfaces, management Ethernet interfaces, and Console 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.) Set the duplex mode for the management Ethernet interface.

duplex { auto | full }

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

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

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

·     C—Port index.

A 10-GE breakout interface split from a 40-GE interface is named in the format of interface type A/B/C:D. A/B/C is the interface number of the 40-GE interface. D is the number of the 10-GE interface, which is in the range of 1 to 4.

 

Configuring common Ethernet interface settings

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

About this task

You can use a 100-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 100-GE interface into four 10-GE breakout interfaces.

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

For example, you can split 100-GE interface HundredGigE 1/1/9 into four 10-GE breakout interfaces Ten-GigabitEthernet 1/1/9:1 through Ten-GigabitEthernet 1/1/9:4.

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

 

 

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

 

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

·     For the interface type changes to take effect, you must save the configuration and reboot the device.

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

1.     Enter system view.

system-view

2.     Enter 100-GE interface view.

interface hundredgige interface-number

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

using tengige

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

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

1.     Enter system view.

system-view

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

interface ten-gigabitethernet interface-number

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

using hundredgige

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

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

About this task

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

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

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

 

 

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

 

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

·     For the interface type changes to take effect, you must save the configuration and reboot the device.

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

1.     Enter system view.

system-view

2.     Enter 100-GE interface view.

interface hundredgige interface-number

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

using twenty-fivegige

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

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

1.     Enter system view.

system-view

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

interface twenty-fivegige interface-number

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

using hundredgige

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

Configuring basic settings of an Ethernet interface

About this task

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

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

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

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

Restrictions and guidelines

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

 

Procedure

1.     Enter system view.

system-view

2.     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, Ten-GigabitEthernet1/1/11 Interface.

4.     Set the duplex mode for the Ethernet interface.

duplex { auto | full }

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

5.     Set the speed for the Ethernet interface.

speed { 10000 | 25000 | 40000 | 100000 | 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 jumbo frame support

About this task

An Ethernet interface might receive frames larger than a device-specific size. 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 (by using the undo jumboframe enable command), the Ethernet interface discards jumbo frames.

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

¡     Processes jumbo frames within the specified length.

¡     Discards jumbo frames that exceed the specified length.

 

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Configure jumbo frame support.

jumboframe enable [ size ]

By default, the device allows jumbo frames within 9216 bytes to pass through all Layer 2 Ethernet interfaces.

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 dampening commands are mutually exclusive on an Ethernet interface.

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 1 shows the change rule of the penalty value. The lines t0 and t2 indicate the start time and end time of the suppression, respectively. The period from t0 to t2 indicates the suppression period, t0 to t1 indicates the max-suppress-time, and t1 to t2 indicates the complete decay period.

Figure 1 Change rule of the penalty value

‌

Restrictions and guidelines

·     The dampening and link-delay 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.

Configuring FEC

About this task

The forward error correction (FEC) feature corrects packet errors to improve transmission quality. It attaches correction information to a packet at the sending end, and corrects error codes generated during transmission at the receiving end based on the correction information. You can set the FEC mode as needed.

Restrictions and guidelines

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

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

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Set the FEC mode of the Ethernet interface.

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

By default, the FEC mode of an interface is RS-FEC.

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 } [ unknown ]

By default, multicast suppression is disabled.

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

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

By default, unknown unicast suppression is disabled.

Configuring generic flow control on an Ethernet interface

About this task

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

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

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

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

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

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

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

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

 

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

About this task

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

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

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

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

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

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

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

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

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

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

Table 1 PFC configurations and negotiation results

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

‌

Restrictions and guidelines

·     You can configure PFC in both system view and Ethernet interface view. If you configure PFC in system view and Ethernet interface view multiple times, the most recent configuration takes effect.

·     For IRF and other protocols to operate correctly, as a best practice, do not enable PFC for 802.1p priorities 0, 6, and 7.

·     To perform PFC on an IRF port, configure PFC on the IRF port and the IRF physical interfaces that are bound to the IRF port. For information about IRF, see Virtual Technologies Configuration Guide.

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

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

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

¡     The PFC configuration takes effect.

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

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

Configuring PFC in system view

1.     Enter system view.

system-view

2.     Enable PFC on all Ethernet interfaces.

priority-flow-control { auto | enable }

By default, PFC is disabled on all Ethernet interfaces.

3.     Enable PFC for 802.1p priorities on all Ethernet interfaces.

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

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

Configuring PFC in Ethernet interface view

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Enable PFC on the Ethernet interface.

priority-flow-control { auto | enable }

By default, PFC is disabled on an Ethernet interface.

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.

Setting the statistics polling interval

About this task

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

Setting the statistics polling interval in Ethernet interface view

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

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

flow-interval interval

The default statistics polling interval is 300 seconds.

Enabling loopback testing on an Ethernet interface

About this task

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

Loopback testing includes the following types:

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

·     External loopback testing—Tests the 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

·     External loopback testing is not supported in the current software version.

·     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

Forcibly bringing up a fiber port

About this task

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

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

Figure 2 Forcibly bring up a fiber port

‌

Restrictions and guidelines

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

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

·     A fiber port does not support this feature if the port joins an aggregation group.

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

Restoring the default settings for an interface

Restrictions and guidelines

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

‌

This feature might fail to restore the default settings for some commands because of command dependencies or system restrictions. You can use the display this command in interface view to check for these commands and perform their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message to resolve the problem.

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Restore the default settings for the interface.

default

Configuring a Layer 2 Ethernet interface

Setting the interface connection distance

About this task

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.

Procedure

1.     Enter system view.

system-view

2.     Enter Layer 2 Ethernet interface view.

interface interface-type interface-number

3.     Set the interface connection distance.

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

 

 

By default, the interface connection distance is 10000 meters.

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.

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. For more information about storm suppression, see "Configuring storm suppression."

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.

Display and maintenance commands for Ethernet interfaces

 

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

 

Task	Command
Display interface traffic statistics.	display counters { inbound | outbound } interface [ interface-type [ interface-number ] ]
Display traffic rate statistics of interfaces in up state over the last statistics polling interval.	display counters rate { inbound | outbound } interface [ interface-type [ interface-number ] ]
Display the Ethernet module statistics.	display ethernet statistics slot slot-number
Display the operational and status information of the specified interfaces.	display interface [ interface-type [ interface-number ] ] [ brief [ description | down ] ]
Display the status and packet statistics of interfaces.	display interface link-info
Display information about dropped packets on the specified interfaces.	display packet-drop { interface [ interface-type [ interface-number ] ] | summary }
Display PFC information on the specified interfaces.	display priority-flow-control interface [ interface-type [ interface-number ] ]
Display information about storm control on the specified interfaces.	display storm-constrain [ broadcast | known-unicast | multicast | unicast ] [ interface interface-type interface-number ]
Clear interface statistics.	reset counters interface [ interface-type [ interface-number ] ]
Clear the Ethernet module statistics.	reset ethernet statistics [ slot slot-number ]
Clear the statistics of dropped packets on the specified interfaces.	reset packet-drop interface [ interface-type [ interface-number ] ]

‌