03-Interface Configuration Guide

HomeSupportResource CenterConfigure & DeployConfiguration GuidesH3C MSR1000[2600][3600] Routers Configuration Guides(V9)-R9119-6W10003-Interface Configuration Guide
02-Ethernet interface configuration
Title Size Download
02-Ethernet interface configuration 234.93 KB

Contents

Configuring Ethernet interfaces· 1

About Ethernet interface· 1

Configuring a management Ethernet interface· 1

Configuring common Ethernet interface settings· 2

Configuring the physical type for a combo interface (single combo interface) 2

Configuring basic settings of an Ethernet interface· 3

Configuring basic settings of an Ethernet subinterface· 3

Configuring basic settings for an Ethernet interface group· 4

Configuring the link mode of an Ethernet interface· 6

Configuring jumbo frame support 8

Configuring physical state change suppression on an Ethernet interface· 8

Configuring dampening on an Ethernet interface· 11

Enabling link flapping protection on an interface· 12

Configuring storm suppression· 13

Configuring generic flow control on an Ethernet interface· 15

Setting the statistics polling interval 16

Enabling subinterface rate statistics collection on an Ethernet interface· 17

Enabling loopback testing on an Ethernet interface· 17

Configuring interface alarm functions· 18

Restoring the default settings for an interface· 20

Configuring a Layer 2 Ethernet interface· 21

Setting speed options for autonegotiation on an Ethernet interface· 21

Setting the MDIX mode of an Ethernet interface· 23

Testing the cable connection of an Ethernet interface· 24

Configuring an interface to operate in promiscuous mode· 26

Configuring a Layer 3 Ethernet interface or subinterface· 27

Setting the MTU for an Ethernet interface or subinterface· 27

Setting the MAC address of an Ethernet interface· 27

Configuring an interface to operate in promiscuous mode· 27

Enabling statistics collection on a Layer 3 Ethernet subinterface· 29

Display and maintenance commands· 30

 

 


Configuring Ethernet interfaces

About Ethernet interface

The device supports Ethernet interfaces, management Ethernet interfaces, Console interfaces, and USB interfaces. For the interface types and the number of interfaces supported by a device 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 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 IRF mode.)

Each member device in an IRF system has a management Ethernet interface. For management link backup, perform the following tasks:

1.     Connect your PC to the management Ethernet interface on the master device.

2.     Connect the PC to a management Ethernet interface with the same interface number on a subordinate device.

The two management Ethernet interfaces operate as follows:

·     When the IRF system has multiple management Ethernet interfaces, only the management Ethernet interface on the master device 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.

Procedure

1.     Enter system view.

system-view

2.     Enter management Ethernet interface view.

interface M-GigabitEthernet interface-number

3.     (Optional.) Set the interface description.

description text

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

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

duplex { auto | full | half }

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

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

speed { 10 | 100 | 1000 | auto }

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

6.      (Optional.) Shut down the interface.

shutdown

By default, the management Ethernet interface is up.

 

CAUTION

CAUTION:

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

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

Configuring the physical type for a combo interface (single combo interface)

 

About this task

A combo interface is a logical interface that physically comprises one fiber combo port and one copper combo port. The two ports share one forwarding channel and one interface view. As a result, they cannot work simultaneously. When you activate one port, the other port is automatically disabled. In the interface view, you can activate the fiber or copper combo port, and configure other port attributes such as the interface rate and duplex mode.

Prerequisites

Before you configure combo interfaces, complete the following tasks:

·     Determine the combo interfaces on your device. Identify the two physical interfaces that belong to each combo interface according to the marks on the device panel.

·     Use the display interface command to determine which port (fiber or copper) of each combo interface is active:

¡     If the copper port is active, the output includes "Media type is twisted pair, Port hardware type is 1000_BASE_T."

¡     If the fiber port is active, the output does not include this information.

Also, you can use the display this command in the view of each combo interface to display the combo interface configuration:

¡     If the fiber port is active, the combo enable fiber command exists in the output.

¡     If the copper port is active, the combo enable fiber command does not exist in the output.

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Activate the copper combo port or fiber combo port.

combo enable { copper | fiber }

By default, the copper combo port is active.

Configuring basic settings of an Ethernet interface

About this task

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

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

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

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

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

Restrictions and guidelines

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

Fiber ports do not support the half keyword.

5.     Set the speed for the Ethernet interface.

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

By default, an interface autonegotiates its speed.

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

·     To transmit and receive packets through an Ethernet subinterface, you must associate it with a VLAN. For more information, see VLAN termination configuration in Layer 2—LAN Switching Configuration Guide.

·     To transmit packets between a local Ethernet subinterface and a remote Ethernet subinterface, configure them with the same subinterface number and VLAN ID.

·     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 command cannot be configured on an Ethernet interface in a loopback test.

Procedure

1.     Enter system view.

system-view

2.     Create an Ethernet subinterface.

interface interface-type interface-number.subnumber

3.     Set the description for the Ethernet subinterface.

description text

The default setting is interface-name Interface. For example, GigabitEthernet1/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 basic settings for an Ethernet interface group

About this task

When a device is shipped, some Ethernet interfaces are organized into Ethernet interface groups by default. You can set the speed for an Ethernet interface group. Then, all interfaces in the group are configured with the speed.

The Ethernet interface groups are defined by hardware and cannot be modified. In the current software version, the device supports 10-GE Ethernet interface groups.

Hardware and Ethernet interface group compatibility

Models

Feature compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

No

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

No

MSR 2630

No

MSR3600-28, MSR3600-51

No

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

No

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

No

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

 

Models

Feature compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

No

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

 

Models

Feature compatibility

MSR2630-XS

No

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

No

MSR3610-IE-XS

No

MSR3620-X1-XS

No

MSR3640-XS

No

MSR3660-XS

Yes

 

Models

Feature compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

No

MSR3600-28-SI-GL

No

Restrictions and guidelines

For the number of Ethernet interface groups, Ethernet interface group IDs, and Ethernet interfaces in a group, execute the port-group ? command in system view.

Procedure

1.     Enter system view.

system-view

2.     Set the speed for an Ethernet interface group.

port-group group-id speed speed-value

Configuring the link mode of an Ethernet interface

 

About this task

For Ethernet interfaces operating in bridge mode by default, you can use this command to change the link mode.

For Ethernet interfaces operating in route mode by default, the following matrixes show the support of hardware platforms for this command:

 

Hardware

Compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

No

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

No

MSR 2630

No

MSR3600-28, MSR3600-51

No

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

No

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

·     MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC: No

·     MSR3620-X1, MSR3640-X1: Yes

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

Hardware

Compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet

No

MSR830-10BEI-WiNet

Yes only on GE2 and GE3

MSR830-6BHI-WiNet

No

MSR830-10BHI-WiNet

Yes only on GE1, GE2, and Combo 3

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

No

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

Hardware

Compatibility

MSR2630-XS

No

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

No

MSR3610-IE-XS

No

MSR3620-X1-XS

Yes

MSR3640-XS

Yes

MSR3660-XS

Yes

Hardware

Compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

Yes only on GE2 and GE3

MSR830-6HI-GL

No

MSR830-10HI-GL

Yes only on GE1, GE2, and Combo 3

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

No

MSR3600-28-SI-GL

No

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 }

Support for the link modes of Ethernet interfaces depends on the interface card model.

 

CAUTION

CAUTION:

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

Configuring jumbo frame support

About this task

Jumbo frames are frames larger than a device-specific 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 within the specified length to pass through. For more information, see Interface Command Reference.

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.

Feature and hardware compatibility

Models

Feature compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

No

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

No

MSR 2630

No

MSR3600-28, MSR3600-51

No

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

No

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

No

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

 

Models

Feature compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

No

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

 

Models

Feature compatibility

MSR2630-XS

No

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

No

MSR3610-IE-XS

No

MSR3620-X1-XS

No

MSR3640-XS

No

MSR3660-XS

Yes

 

Models

Feature compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

No

MSR3600-28-SI-GL

No

Restrictions and guidelines

Do not enable this feature on an interface that has spanning tree protocols enabled.

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

If you configure this command multiple times for link-up or link-down events on an Ethernet interface, the most recent configuration takes effect.

The link-delay, dampening, 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 configure the link-delay command 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 [ msec ] delay-time [ mode { up | updown }]

By default, physical state change suppression is disabled.

To suppress only link-down events, do not specify the mode keyword. To suppress only link-up events, specify the mode up keywords. To suppress both link-down and link-up events, specify the mode updown keywords.

Configuring dampening on an Ethernet interface

About this task

The interface dampening feature uses an exponential decay mechanism to prevent excessive interface flapping events from adversely affecting routing protocols and routing tables in the network. Suppressing interface state change events protects the system resources.

If an interface is not dampened, its state changes are reported. For each state change, the system also generates an SNMP trap and log message.

After a flapping interface is dampened, it does not report its state changes to the CPU. For state change events, the interface only generates SNMP trap and log messages.

Parameters

·     Penalty—The interface has an initial penalty of 0. When the interface flaps, the penalty increases by 1000 for each down event until the ceiling is reached. It does not increase for up events. When the interface stops flapping, the penalty decreases by half each time the half-life timer expires until the penalty drops to the reuse threshold.

·     Ceiling—The penalty stops increasing when it reaches the ceiling.

·     Suppress-limit—The accumulated penalty that triggers the device to dampen the interface. In dampened state, the interface does not report its state changes to the CPU. For state change events, the interface only generates SNMP traps and log messages.

·     Reuse-limit—When the accumulated penalty decreases to this reuse threshold, the interface is not dampened. Interface state changes are reported to the upper layers. For each state change, the system also generates an SNMP trap and log message.

·     Decay—The amount of time (in seconds) after which a penalty is decreased.

·     Max-suppress-time—The maximum amount of time the interface can be dampened. If the penalty is still higher than the reuse threshold when this timer expires, the penalty stops increasing for down events. The penalty starts to decrease until it drops below the reuse threshold.

When configuring the dampening command, follow these rules to set the values mentioned above:

·     The ceiling is equal to 2(Max-suppress-time/Decay)  × reuse-limit. It is not user configurable.

·     The configured suppress limit is lower than or equal to the ceiling.

·     The ceiling is lower than or equal to the maximum suppress limit supported.

Figure 1 shows the change rule of the penalty value. The lines t0 and t2 indicate the start time and end time of the suppression, respectively. The period from t0 to t2 indicates the suppression period, t0 to t1 indicates the max-suppress-time, and t1 to t2 indicates the complete decay period.

Figure 1 Change rule of the penalty value

Restrictions and guidelines

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

·     The dampening command does not take effect on the administratively down events. When you execute the shutdown command, the penalty restores to 0, and the interface reports the down event to the upper-layer protocols.

·     Do not enable the dampening feature on an interface with spanning tree protocols 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.

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

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

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

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

Procedure

1.     Enter system view.

system-view

2.     Enable link flapping protection globally.

link-flap protect enable

By default, link flapping protection is disabled globally.

3.     Enter Ethernet interface view.

interface interface-type interface-number

4.     Enable link flapping protection on the Ethernet interface.

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

By default, link flapping protection is disabled on an Ethernet 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.

Hardware and feature compatibility

Hardware

Feature compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

Yes

MSR810-LMS, MSR810-LUS

Yes

MSR810-LMS-EA, MSR810-LME

Yes

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

Yes

MSR 2630

No

MSR3600-28, MSR3600-51

No

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

No

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

Yes

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

No

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

 

Hardware

Feature compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

Yes

MSR830-4LM-WiNet

Yes

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

Yes

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

 

Hardware

Feature compatibility

MSR2630-XS

Yes

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

Yes

MSR3610-IE-XS

Yes

MSR3620-X1-XS

No

MSR3640-XS

No

MSR3660-XS

Yes

 

Hardware

Feature compatibility

MSR810-LM-GL

Yes

MSR810-W-LM-GL

Yes

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

Yes

MSR3600-28-SI-GL

No

Restrictions and guidelines

·     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. Support for the ratio, pps, and kbps parameters varies by device model. For more information, see Interface Command Reference.

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.

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.

Restrictions and guidelines for setting the statistics polling interval

·     As a best practice, use the default setting when you set the statistics polling interval in system view. A short statistics polling interval 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

By default, the statistics polling interval 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 supports only internal loopback testing, which 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.

Restrictions and guidelines

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

·     The shutdown and loopback commands are mutually exclusive.

·     To enable this feature on an Ethernet interface, make sure the Ethernet interface operates in full duplex mode.

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Enable loopback testing.

loopbackinternal

Configuring interface alarm functions

About this task

With the interface alarm functions enabled, when the input or output bandwidth usage 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 input or output bandwidth usage 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.

Feature and hardware compatibility

Models

Feature compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

Yes

MSR810-LMS, MSR810-LUS

Yes

MSR810-LMS-EA, MSR810-LME

Yes

MSR1004S-5G

Yes

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

Yes

MSR 2630

Yes

MSR3600-28, MSR3600-51

Yes

MSR3600-28-SI, MSR3600-51-SI

Yes

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

Yes

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

Yes

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

Yes

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

Yes

MSR3610-G, MSR3620-G

Yes

MSR3640-X1-HI

No

 

Models

Feature compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

Yes

MSR830-4LM-WiNet

Yes

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

Yes

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

Yes

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

Yes

MSR2630-WiNet

Yes

MSR3600-28-WiNet

Yes

MSR3610-X1-WiNet

Yes

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

Yes

 

Models

Feature compatibility

MSR2630-XS

Yes

MSR3600-28-XS

Yes

MSR3610-XS

Yes

MSR3620-XS

Yes

MSR3610-I-XS

Yes

MSR3610-IE-XS

Yes

MSR3620-X1-XS

Yes

MSR3640-XS

Yes

MSR3660-XS

No

 

Models

Feature compatibility

MSR810-LM-GL

Yes

MSR810-W-LM-GL

Yes

MSR830-6EI-GL

Yes

MSR830-10EI-GL

Yes

MSR830-6HI-GL

Yes

MSR830-10HI-GL

Yes

MSR1004S-5G-GL

Yes

MSR2600-6-X1-GL

Yes

MSR3600-28-SI-GL

Yes

Restrictions and guidelines

You can configure the error packet 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.

snmp-agent trap enable ifmonitor [ input-usage | output-usage ] *

By default, all alarm functions are enabled for interfaces.

 

 

 

Configuring input bandwidth usage alarm parameters

1.     Enter system view.

system-view

2.     Configure global input bandwidth usage alarm parameters.

In standalone mode:

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

In IRF mode:

ifmonitor input-usage slot slot-number high-threshold high-value low-threshold low-value

By default, the upper threshold is 90 and the lower threshold is 80 for input bandwidth usage alarms.

3.     Enter Ethernet interface view.

interface interface-type interface-number

4.     Configure input bandwidth usage alarm parameters.

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

By default, an interface uses the global input bandwidth usage alarm parameters. Support for this feature varies by device model. For more information, see Interface Command Reference.

 

Configuring output bandwidth usage alarm parameters

1.     Enter system view.

system-view

2.     Configure global output bandwidth usage alarm parameters.

In standalone mode:

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

In IRF mode:

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. Support for this feature varies by device model. For more information, see Interface Command Reference.

 

 

 

 

 

Restoring the default settings for an interface

Restrictions and guidelines

CAUTION

CAUTION:

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

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

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view or Ethernet subinterface view.

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

3.     Restore the default settings for the interface.

default

Configuring a Layer 2 Ethernet interface

Setting speed options for autonegotiation on an Ethernet interface

About this task

By default, speed autonegotiation enables an Ethernet interface to negotiate with its peer for the highest speed that both ends support. You can narrow down the speed option list for negotiation.

Figure 2 Speed autonegotiation application scenario

As shown in Figure 2:

·     All interfaces on the device are operating in speed autonegotiation mode, with the highest speed of 1000 Mbps.

·     Port D provides access to the Internet for the servers.

If the transmission rate of each server in the server cluster is 1000 Mbps, their total transmission rate exceeds the capability of Port D.

To avoid congestion on Port D, configure 100 Mbps as the only option available for speed negotiation on interfaces Port A, Port B, and Port C. As a result, the transmission rate on each interface connected to a server is limited to 100 Mbps.

Feature and hardware compatibility

Models

Feature compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

No

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

No

MSR 2630

No

MSR3600-28, MSR3600-51

No

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

No

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

No

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

 

Models

Feature compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

No

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

 

Models

Feature compatibility

MSR2630-XS

No

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

No

MSR3610-IE-XS

No

MSR3620-X1-XS

No

MSR3640-XS

No

MSR3660-XS

Yes

 

Models

Feature compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

No

MSR3600-28-SI-GL

No

Restrictions and guidelines

The speed and speed auto commands supersede each other, and whichever is configured last takes effect.

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Set speed options for autonegotiation.

speed auto { 10 | 100 | 1000 } *

By default, no speed options are set for autonegotiation.

Setting the MDIX mode of an Ethernet interface

IMPORTANT

IMPORTANT:

Fiber ports do not support the MDIX mode setting.

About this task

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.

Restrictions and guidelines

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.

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

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.

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.

About this task

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.

Feature and hardware compatibility

Models

Feature compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

No

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

No

MSR 2630

No

MSR3600-28, MSR3600-51

No

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

No

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

No

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

 

Models

Feature compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

No

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

 

Models

Feature compatibility

MSR2630-XS

No

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

No

MSR3610-IE-XS

No

MSR3620-X1-XS

No

MSR3640-XS

No

MSR3660-XS

Yes

 

Models

Feature compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

No

MSR3600-28-SI-GL

No

Procedure

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

Configuring an interface to operate in promiscuous mode

About this task

By default, a Layer 3 Ethernet interface does not operate in promiscuous mode. In this case, the interface accepts and processes only packets destined to the MAC address of the interface, and drops packets destined to any other MAC address.

For an interface to snoop all packets received, use this command to configure the interface to operate in promiscuous mode. In this mode, a Layer 3 Ethernet interface does not perform MAC address filtering, and accepts and processes all packets regardless whether they are destined to the MAC address of the interface.

Procedure

1.     Enter system view.

system-view

2.     Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

3.     Configure the interface to operate in promiscuous mode.

port promiscuous-mode

By default, an interface does not operate in promiscuous mode.

Configuring a Layer 3 Ethernet interface or subinterface

Setting the MTU for an Ethernet interface or subinterface

Restrictions and guidelines

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.

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

About this task

In a network, when the Layer 3 Ethernet interfaces 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.

Procedure

1.     Enter system view.

system-view

2.     Enter interface view.

interface interface-type interface-number

3.     Set the interface MAC address.

mac-address mac-address

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

Configuring an interface to operate in promiscuous mode

About this task

By default, a Layer 3 Ethernet interface does not operate in promiscuous mode. In this case, the interface accepts and processes only packets destined to the MAC address of the interface, and drops packets destined to any other MAC address.

For an interface to snoop all packets received, use this command to configure the interface to operate in promiscuous mode. In this mode, a Layer 3 Ethernet interface does not perform MAC address filtering, and accepts and processes all packets regardless whether they are destined to the MAC address of the interface.

Hardware and feature compatibility

Hardware

Feature compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

No

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

Yes

MSR 2630

No

MSR3600-28, MSR3600-51

No

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

No

MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

Yes

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

Yes

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

Yes

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

 

Hardware

Feature compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

Yes

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

Yes

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

Yes

 

Hardware

Feature compatibility

MSR2630-XS

Yes

MSR3600-28-XS

No

MSR3610-XS

Yes

MSR3620-XS

Yes

MSR3610-I-XS

Yes

MSR3610-IE-XS

Yes

MSR3620-X1-XS

Yes

MSR3640-XS

Yes

MSR3660-XS

Yes

 

Hardware

Feature compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

Yes

MSR3600-28-SI-GL

No

Procedure

1.     Enter system view.

system-view

2.     Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

3.     Configure the interface to operate in promiscuous mode.

port promiscuous-mode

By default, an interface does not operate in promiscuous mode.

Enabling statistics collection on a Layer 3 Ethernet subinterface

About this task

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

Procedure

1.     Enter system view.

system-view

2.     Enter Layer 3 Ethernet subinterface view.

interface interface-type interface-number.subnumber

3.     Enable statistics collection on the Layer 3 Ethernet subinterface.

traffic-statistic enable

By default, statistics collection is disabled on a Layer 3 Ethernet subinterface.

4.     (Optional.) Display the subinterface traffic statistics.

display interface

display counters

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

Display and maintenance commands

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 Ethernet module statistics.

In standalone mode:

display ethernet statistics

In IRF mode:

display ethernet statistics slot slot-number

Display the operational and status information of the specified interfaces.

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

Display the status and packet statistics of interfaces.

display interface link-info [ main ]

Display operating status and information of all interfaces except subinterfaces.

display interface [ interface-type ] [ brief [ description | down ] ] main

Display information about link flapping protection on interfaces.

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

Display the link state change statistics of interfaces.

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

Clear interface statistics.

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

Clear the Ethernet module statistics.

In standalone mode:

reset ethernet statistics

In IRF mode:

reset ethernet statistics [ slot slot-number ]

Clear the link state change statistics of interfaces.

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