Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-Ethernet interface configuration | 200.28 KB |
Contents
Configuring Ethernet interfaces
Configuring a management Ethernet interface
Ethernet interface naming conventions
Configuring common Ethernet interface settings
Splitting a 100-GE interface and combining 10-GE breakout interfaces
Splitting a 100-GE interface and combining 25-GE breakout interfaces
Configuring basic settings of an Ethernet interface
Configuring basic settings of an Ethernet subinterface
Configuring the link mode of an Ethernet interface
Configuring jumbo frame support
Configuring physical state change suppression on an Ethernet interface
Configuring dampening on an Ethernet interface
Enabling link flapping protection on an interface
Configuring generic flow control on an Ethernet interface
Setting the statistics polling interval
Enabling loopback testing on an Ethernet interface
Forcibly bringing up a fiber port
Restoring the default settings for an interface
Configuring a Layer 2 Ethernet interface
Configuring storm control on an Ethernet interface
Enabling bridging on an Ethernet interface
Configuring a Layer 3 Ethernet interface or subinterface
Setting the MTU for an Ethernet interface or subinterface
Display and maintenance commands for Ethernet interfaces
Configuring Ethernet interfaces
About Ethernet interface
The Switch Series supports Ethernet interfaces, management Ethernet interfaces, Console interfaces, and USB interfaces. For the interface types and the number of interfaces supported by a switch model, see the installation guide.
This chapter describes how to configure management Ethernet interfaces and Ethernet interfaces.
Configuring a management Ethernet interface
About this task
A management interface uses an RJ-45/LC connector. You can connect the interface to a PC for software loading and system debugging, or connect it to a remote NMS for remote system management.
Restrictions and guidelines
The management Ethernet interfaces include copper ports and fiber ports.
· The default duplex mode is auto for a copper port and full for a fiber port. Both copper and fiber ports do not support modifying the default duplex mode by using the duplex command.
· The default speed is auto for a copper port and 1000 Mbps for a fiber port. Both copper and fiber ports do not support modifying the default speed by using the speed command.
When multiple management Ethernet interfaces exist in the system, only the management Ethernet interface on the active MPU processes management traffic. (In standalone mode.)
When multiple management Ethernet interfaces exist in the system, only the management Ethernet interface on the global active MPU processes management traffic. (In IRF mode.)
Procedure
1. Enter system view.
system-view
2. Enter management Ethernet interface view.
interface M-GigabitEthernet interface-number
3. (Optional.) Set the interface description.
description text
The default setting is M-GigabitEthernet0/0/0 Interface.
4. (Optional.) Shut down the interface.
shutdown
By default, the management Ethernet interface is up.
Ethernet interface naming conventions
When the switch operates in standalone mode, 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—Card slot number.
· B—Subcard slot number. In the current software version, subcards are not supported and the value is fixed at 0.
· C—Port index.
When the switch operates in IRF mode, the Ethernet interfaces are named in the format of interface type A/B/C/D. The letters that follow the interface type represent the following elements:
· A—IRF member ID, which is 1 or 2.
· B—Card slot number.
· C—Subcard slot number. In the current software version, subcards are not supported and the value is fixed at 0.
· D—Port index.
Configuring common Ethernet interface settings
This section describes the settings common to Layer 2 Ethernet interfaces, Layer 3 Ethernet interfaces, and Layer 3 Ethernet subinterfaces. For more information about the settings specific to Layer 2 Ethernet interfaces, see "Configuring a Layer 2 Ethernet interface." For more information about the settings specific to Layer 3 Ethernet interfaces or subinterfaces, see "Configuring a Layer 3 Ethernet interface or subinterface."
Splitting a 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 multiple 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 2/0/1 with a split-capable 40-GE transceiver module or cable installed into four 10-GE breakout interfaces Ten-GigabitEthernet 2/0/1:1 through Ten-GigabitEthernet 2/0/1:4.
If you need higher bandwidth on a single interface, you can combine the multiple 10-GE breakout interfaces into a 100-GE interface.
Restrictions and guidelines for 100-GE interface splitting and 10-GE breakout interface combining
· This feature is not supported on the following interfaces:
¡ Interfaces 9 and 18 on LSXM1CGQ18TE2 interface cards.
¡ Interfaces 10, 17, 28, and 35 on LSXM1CGQ36TE2 interface cards.
¡ Interface 8 on LSXM1CGQ8TD2 interface cards.
¡ Interfaces 1, 2, 17, and 18 on LSXM1CGQ18TD2 interface cards.
· This feature is supported only on the default MDC.
· 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.
· Save the configuration and reboot the device for this feature to take effect.
Splitting a 100-GE interface into multiple 10-GE breakout interfaces
1. Enter system view.
system-view
2. Enter 100-GE interface view.
interface hundredgige interface-number
3. Split the 100-GE interface into multiple 10-GE breakout interfaces.
using tengige
By default, a 100-GE interface is not split and operates as a single interface.
Combining multiple 10-GE breakout interfaces into a 100-GE interface
1. Enter system view.
system-view
2. Enter the view of any 10-GE breakout interface.
interface ten-gigabitethernet interface-number
3. Combine the multiple 10-GE breakout interfaces into a 100-GE interface.
using hundredgige
By default, a 10-GE breakout interface operates as a single interface.
Splitting a 100-GE interface and combining 25-GE breakout interfaces
About this task
You can use a 100-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 100-GE interface into four 25-GE breakout interfaces. The 25-GE breakout interfaces support the same configuration and attributes as common 25-GE interfaces, except that they are numbered differently.
For example, you can split 100-GE interface HundredGigE 3/0/1 into four 25-GE breakout interfaces Twenty-FiveGigE 3/0/1:1 through Twenty-FiveGigE 3/0/1:4.
If you need higher bandwidth on a single interface, you can combine the four 25-GE breakout interfaces into a 100-GE interface.
Restrictions and guidelines for 100-GE interface splitting and 25-GE breakout interface combining
· This feature is not supported on the following interfaces:
¡ Interfaces 9 and 18 on LSXM1CGQ18TE2 interface cards.
¡ Interfaces 10, 17, 28, and 35 on LSXM1CGQ36TE2 interface cards.
¡ Interface 8 on LSXM1CGQ8TD2 interface cards.
¡ Interfaces 1, 2, 17, and 18 on LSXM1CGQ18TD2 interface cards.
· This feature is supported only on the default MDC.
· 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.
· Save the configuration and reboot the device for this feature to take effect.
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.
· Half-duplex mode—The interface can only send or receive packets at a given time.
· Autonegotiation mode—The interface negotiates a duplex mode with its peer.
You can set the speed of an Ethernet interface or enable it to automatically negotiate a speed with its peer.
Restrictions and guidelines
The shutdown, port up-mode, and loopback commands are mutually exclusive.
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, HundredGigE3/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 | 2500 | 5000 | 10000 | 25000 | 40000 | 100000 | auto }
By default, an Ethernet interface negotiates a speed with its peer.
Support for the options of the speed command varies by interface type. For more information, execute the speed ? in interface view.
6. Set the expected bandwidth for the Ethernet interface.
bandwidth bandwidth-value
By default, the expected bandwidth (in kbps) is the interface baud rate divided by 1000.
7. Bring up the Ethernet interface.
undo shutdown
By default, Ethernet interfaces are in up state.
Configuring basic settings of an Ethernet subinterface
Restrictions and guidelines for Ethernet subinterface basic settings
· The shutdown, port up-mode, and loopback commands are mutually exclusive.
· The shutdown command cannot be configured on an Ethernet interface in a loopback test.
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, HundredGigE3/0/1.1 Interface.
4. Set the expected bandwidth for the Ethernet subinterface.
bandwidth bandwidth-value
By default, the expected bandwidth (in kbps) is the interface baud rate divided by 1000.
5. Bring up the Ethernet subinterface.
undo shutdown
By default, Ethernet subinterfaces are in up state.
Configuring the link mode of an Ethernet interface
About this task
Interfaces on the device can operate either as Layer 2 or Layer 3 Ethernet interfaces. You can use commands to set the link mode to bridge or route.
Restrictions and guidelines
After you change the link mode of an Ethernet interface, all commands (except the description, duplex, jumboframe enable, speed, shutdown commands) on the Ethernet interface are restored to their defaults in the new link mode.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Configure the link mode of the Ethernet interface.
port link-mode { bridge | route }
By default, all Ethernet interfaces on the device operate in bridge mode.
Configuring jumbo frame support
About this task
Jumbo frames are frames larger than 1536 bytes and are typically received by an Ethernet interface during high-throughput data exchanges, such as file transfers.
The Ethernet interface processes jumbo frames in the following ways:
· When the Ethernet interface is configured to deny jumbo frames (by using the undo jumboframe enable command), the Ethernet interface discards jumbo frames.
· When the Ethernet interface is configured with jumbo frame support, the Ethernet interface performs the following operations:
¡ Processes jumbo frames within the specified length.
¡ Discards jumbo frames that exceed the specified length.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Configure jumbo frame support.
jumboframe enable [ size ]
By default, the device allows jumbo frames within 9416 bytes to pass through.
If you set the size argument multiple times, the most recent configuration takes effect.
Configuring physical state change suppression on an Ethernet interface
About this task
The physical link state of an Ethernet interface is either up or down. Each time the physical link of an interface comes up or goes down, the interface immediately reports the change to the CPU. The CPU then performs the following operations:
· Notifies the upper-layer protocol modules (such as routing and forwarding modules) of the change for guiding packet forwarding.
· Automatically generates traps and logs to inform users to take the correct actions.
To prevent frequent physical link flapping from affecting system performance, configure physical state change suppression. You can configure this feature to suppress only link-down events, only link-up events, or both. If an event of the specified type still exists when the suppression interval expires, the system reports the event to the CPU.
Restrictions and guidelines
Do not enable this feature on an interface that has RRPP, spanning tree protocols, or Smart Link enabled.
You can configure different suppression intervals for link-up and link-down events.
If you execute the link-delay command multiple times on an interface, the following rules apply:
· You can configure the suppression intervals for link-up and link-down events separately.
· If you configure the suppression interval multiple times for link-up or link-down events, the most recent configuration takes effect.
The link-delay, dampening, and port link-flap protect enable commands are mutually exclusive on an Ethernet interface.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Configure physical state change suppression.
link-delay { down | up } [ msec ] delay-time
By default, each time the physical link of an interface goes up or comes down, the interface immediately reports the change to the CPU.
Configuring dampening on an Ethernet interface
About this task
The interface dampening feature uses an exponential decay mechanism to prevent excessive interface flapping events from adversely affecting routing protocols and routing tables in the network. Suppressing interface state change events protects the system resources.
If an interface is not dampened, its state changes are reported. For each state change, the system also generates an SNMP trap and log message.
After a flapping interface is dampened, it does not report its state changes to the CPU. For state change events, the interface only generates SNMP trap and log messages.
Parameters
· Penalty—The interface has an initial penalty of 0. When the interface flaps, the penalty increases by 1000 for each down event until the ceiling is reached. It does not increase for up events. When the interface stops flapping, the penalty decreases by half each time the half-life timer expires until the penalty drops to the reuse threshold.
· Ceiling—The penalty stops increasing when it reaches the ceiling.
· Suppress-limit—The accumulated penalty that triggers the device to dampen the interface. In dampened state, the interface does not report its state changes to the CPU. For state change events, the interface only generates SNMP traps and log messages.
· Reuse-limit—When the accumulated penalty decreases to this reuse threshold, the interface is not dampened. Interface state changes are reported to the upper layers. For each state change, the system also generates an SNMP trap and log message.
· Decay—The amount of time (in seconds) after which a penalty is decreased.
· Max-suppress-time—The maximum amount of time the interface can be dampened. If the penalty is still higher than the reuse threshold when this timer expires, the penalty stops increasing for down events. The penalty starts to decrease until it drops below the reuse threshold.
When configuring the dampening command, follow these rules to set the values mentioned above:
· The ceiling is equal to 2(Max-suppress-time/Decay) × reuse-limit. It is not user configurable.
· The configured suppress limit is lower than or equal to the ceiling.
· The ceiling is lower than or equal to the maximum suppress limit supported.
Figure 1 shows the change rule of the penalty value. The lines t0 and t2 indicate the start time and end time of the suppression, respectively. The period from t0 to t2 indicates the suppression period, t0 to t1 indicates the max-suppress-time, and t1 to t2 indicates the complete decay period.
Figure 1 Change rule of the penalty value
Restrictions and guidelines
· The dampening, link-delay, and port link-flap protect enable commands are mutually exclusive on an interface.
· The dampening command does not take effect on the administratively down events. When you execute the shutdown command, the penalty restores to 0, and the interface reports the down event to the upper-layer protocols.
· Do not enable the dampening feature on an interface with RRPP, MSTP, or Smart Link enabled.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Enable dampening on the interface.
dampening [ half-life reuse suppress max-suppress-time ]
By default, interface dampening is disabled on Ethernet interfaces.
Enabling link flapping protection on an interface
About this task
Link flapping on an interface changes network topology and increases the system overhead. For example, in an active/standby link scenario, when interface status on the active link changes between UP and DOWN, traffic switches between active and standby links. To solve this problem, configure this feature on the interface.
With this feature enabled on an interface, when the interface goes down, the system enables link flapping detection. During the link flapping detection interval, if the number of detected flaps reaches or exceeds the link flapping detection threshold, the system shuts down the interface.
Restrictions and guidelines
This feature takes effect only if it is configured in both the system view and interface view.
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 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 { auto | base-r | none | rs-fec }
By default, the FEC mode is RS-FEC for 25-GE interfaces and autonegotiation for 100-GE interfaces.
The base-r keyword is not supported on 100-GE interfaces.
Configuring link compensation
About this task
As the signal transmission rate or frequency increases, high frequency components in signals attenuate more severely. For signal transmission performance, common signal compensation technologies such as pre-emphasis and equalization are introduced. Pre-emphasis amplifies high frequency components but increases the probability of crosstalk. Equalization is introduced to filter out high frequency crosstalk on the receiving end.
Link compensation enables the sending and receiving ends to exchange pre-emphasis and equalization parameters through frames. This feature improves the performance of pre-emphasis and equalization.
Restrictions and guidelines
This feature is supported only on 25-GE interfaces.
You must enable or disable link compensation on both interfaces of a link.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Configure link compensation on the interface.
port training { disable | enable }
By default, link compensation is enabled on an interface.
Configuring storm suppression
About this task
The storm suppression feature ensures that the size of a particular type of traffic (broadcast, multicast, or unknown unicast traffic) does not exceed the threshold on an interface. When the broadcast, multicast, or unknown unicast traffic on the interface exceeds this threshold, the system discards packets until the traffic drops below this threshold.
Both storm suppression and storm control can suppress storms on an interface. Storm suppression uses the chip to suppress traffic. Storm suppression has less impact on the device performance than storm control, which uses software to suppress traffic.
Restrictions and guidelines
· For the traffic suppression result to be determined, do not configure storm control together with storm suppression for the same type of traffic. For more information about storm control, see "Configuring storm control on an Ethernet interface."
· 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
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 perform PFC in an overlay network, execute the qos trust tunnel-dot1p command. For information about the overlay network, see VXLAN Configuration Guide. For information about the qos trust tunnel-dot1p command, see ACL and QoS Command Reference.
· 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 on inner interfaces
1. Enter system view.
system-view
2. Enable PFC on inner interfaces.
priority-flow-control inner-port enable
By default, PFC is disabled on inner interfaces.
An inner interface is the inner Ethernet interface through which a card communicates with the device, and is invisible to users.
3. Enable PFC for 802.1p priorities on inner interfaces.
priority-flow-control inner-port no-drop dot1p dot1p-list
By default, PFC is disabled for all 802.1p priorities.
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
By default, the statistics polling interval is 300 seconds.
Enabling loopback testing on an Ethernet interface
About this task
Perform this task to determine whether an Ethernet link works correctly.
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.
Restrictions and guidelines
· After you enable this feature on an Ethernet interface, the interface does not forward data traffic.
· The shutdown, port up-mode, and loopback commands are mutually exclusive.
· After you enable this feature on an Ethernet interface, the Ethernet interface switches to full duplex mode. After you disable this feature, the Ethernet interface restores to its duplex setting.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Enable loopback testing.
loopbackinternal
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.
· A GE fiber port forcibly brought up cannot correctly forward traffic if it is installed with a fiber-to-copper converter, 100/1000-Mbps transceiver module, or 100-Mbps transceiver module. To solve the problem, use the undo port up-mode command on the fiber port.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Forcibly bring up the fiber port.
port up-mode
By default, a fiber port is not forcibly brought up, and the physical state of a fiber port depends on the physical state of the fibers.
Restoring the default settings for an interface
Restrictions and guidelines
|
|
CAUTION: This feature might interrupt ongoing network services. Make sure you are fully aware of the impacts of this feature when you use it in a live network. |
This feature might fail to restore the default settings for some commands because of command dependencies or system restrictions. You can use the display this command in interface view to check for these commands and perform their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message to resolve the problem.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view or Ethernet subinterface view.
interface interface-type { interface-number | interface-number.subnumber }
3. Restore the default settings for the interface.
default
Configuring a Layer 2 Ethernet interface
Configuring storm control on an Ethernet interface
About this task
Storm control compares broadcast, multicast, 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.
Enabling bridging on an Ethernet interface
About this task
By default, the device drops packets whose outgoing interface and incoming interface are the same.
To enable the device to forward such packets rather than drop them, enable the bridging feature in Ethernet interface view.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Enable bridging on the Ethernet interface.
port bridge enable
By default, bridging is disabled on an Ethernet interface.
Configuring a Layer 3 Ethernet interface or subinterface
Setting the MTU for an Ethernet interface or subinterface
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 MTU for the interface.
mtu size
The default setting is 1500 bytes.
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 | 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 slot slot-number (In IRF mode.) display ethernet statistics chassis chassis-number 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 information about link flapping protection on interfaces. |
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 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 | interface-number.subnumber ] ] |
|
Clear the Ethernet module statistics. |
(In standalone mode.) reset ethernet statistics [ slot slot-number ] (In IRF mode.) reset ethernet statistics [ chassis chassis-number slot slot-number ] |
|
Clear the statistics of dropped packets on the specified interfaces. |
reset packet-drop interface [ interface-type [ interface-number ] ] |
|
Display the status and packet statistics of interfaces. |
display interface link-info [ main ] |
|
Display the operational and status information of interfaces except subinterfaces. |
display interface [ interface-type ] [ brief [ description | down ] ] main |
