- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
02-Ethernet interface configuration | 173.42 KB |
Contents
Configuring Ethernet interfaces
Configuring common Ethernet interface settings
Splitting a 40-GE interface and combining 10-GE breakout interfaces
Splitting a 100-GE interface and combining 10-GE breakout interfaces
Changing the interface type of a 100-GE interface
Changing the interface type of a 10-GE interface
Configuring the operating mode for a 10-GE interface
Setting the J0 and J1 overhead bytes for a 10-GE interface
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
Setting the number of interframe bytes
Configuring physical state change suppression on an Ethernet interface
Configuring dampening on an Ethernet interface
Setting the statistics polling interval
Enabling loopback testing on an Ethernet interface
Configuring interface alarm functions
Displaying the operating status and information of an interface
Restoring the default settings for an interface
Configuring a Layer 3 Ethernet interface
Setting the MTU for an Ethernet interface or subinterface
Enabling packet statistics collection on a Layer 3 Ethernet subinterface
Display and maintenance commands for an Ethernet interface or subinterface
Configuring Ethernet interfaces
About Ethernet interface
Your device supports the following types of Ethernet interfaces:
· Layer 2 Ethernet interfaces—Physical Ethernet interfaces operating at the data link layer (Layer 2) to switch packets.
· Layer 3 Ethernet interfaces—Physical Ethernet interfaces operating at the network layer (Layer 3) to route packets. You can assign an IP address to a Layer 3 Ethernet interface.
· Layer-configurable Ethernet interfaces—Physical Ethernet interfaces that can be configured to operate in bridge mode as Layer 2 Ethernet interfaces or in route mode as Layer 3 Ethernet interfaces.
· Layer 3 Ethernet subinterfaces—Logical interfaces operating at the network layer. You can assign an IP address to a Layer 3 Ethernet subinterface.
Configuring common Ethernet interface settings
Splitting a 40-GE interface and combining 10-GE breakout interfaces
About this task
You can use a 40-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 40-GE interface into four 10-GE breakout interfaces. 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 40-GE interface FortyGigE 1/2/0/1 into four 10-GE breakout interfaces Ten-GigabitEthernet 1/2/0/1:1 through Ten-GigabitEthernet 1/2/0/1:4.
If you need higher bandwidth on a single interface, you can combine the four 10-GE breakout interfaces into a 40-GE interface.
Restrictions and guidelines for 40-GE interface splitting and 10-GE breakout interface combining
This feature is supported only on the default MDC.
A 40-GE interface split into four 10-GE breakout interfaces must use a dedicated 1-to-4 cable. After you combine the four 10-GE breakout interfaces, replace the dedicated 1-to-4 cable with a dedicated 1-to-1 cable or a 40-GE transceiver module. For more information about the cable or transceiver module, see the installation guides.
This configuration takes effect in real time, and cannot be rolled back.
Splitting a 40-GE interface into four 10-GE breakout interfaces
1. Enter system view.
system-view
2. Enter 40-GE interface view.
interface interface-type interface-number
3. Split the 40-GE interface into four 10-GE breakout interfaces.
using tengige
By default, a 40-GE interface is not split and operates as a single interface.
Combining four 10-GE breakout interfaces into a 40-GE interface
1. Enter system view.
system-view
2. Enter the view of any 10-GE breakout interface.
interface interface-type interface-number
3. Combine the four 10-GE breakout interfaces into a 40-GE interface.
using fortygige
By default, a 10-GE breakout interface operates as a single interface.
Splitting a 100-GE interface and combining 10-GE breakout interfaces
About this task
You can use a 100-GE interface as a single interface. To improve port density, reduce costs, and improve network flexibility, you can also split a 100-GE interface into four 10-GE breakout interface. The 10-GE breakout interfaces support the same configuration and attributes as common 10-GE interfaces, except that they are numbered differently.
For example, you can split 100-GE interface HundredGigE 1/2/0/1 into four 10-GE breakout interfaces Ten-GigabitEthernet 1/2/0/1:1 through Ten-GigabitEthernet 1/2/0/1:4.
If you need higher bandwidth on a single interface, you can combine the ten or twelve 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 supported only on the default MDC.
A 100-GE interface split into 10-GE breakout interfaces must use a dedicated cable. After you combine the 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.
This configuration takes effect in real time, and cannot be rolled back.
Splitting a 100-GE interface into four 10-GE breakout interfaces
1. Enter system view.
system-view
2. Enter 100-GE interface view.
interface interface-type interface-number
3. Split the 100-GE interface into four 10-GE breakout interfaces.
using tengige
By default, a 100-GE interface is not split and operates as a single interface.
Combining four 10-GE breakout interfaces into a 100-GE interface
1. Enter system view.
system-view
2. Enter the view of any 10-GE breakout interface.
interface interface-type interface-number
3. Combine the four 10-GE breakout interfaces into a 100-GE interface.
using hundredgige
By default, a 10-GE breakout interface operates as a single interface.
Changing the interface type of a 100-GE interface
About this task
To improve network flexibility, you can change a 100-GE interface to a 40-GE interface. For example, you can change 100-GE interface HundredGigE 1/2/0/1 to 40-GE interface FortyGigE 1/2/0/1. The 40-GE interface changed from a 100-GE interface supports the same configuration and attributes as common 40-GE interfaces, except that it is numbered differently and cannot be split.
If you need higher bandwidth, you can restore a 40-GE interface that was changed from a 100-GE interface to a 100-GE interface.
Restrictions and guidelines for interface change between 100-GE interface and 40-GE interface
This feature is supported only on the default MDC.
A 100-GE interface that was changed to a 40-GE interface must use a 40-GE transceiver module. After you restore the 40-GE interface to a 100-GE interface, replace the 40-GE transceiver module with a 100-GE transceiver module. For more information about the transceiver module, see the installation guides.
This configuration takes effect in real time, and cannot be rolled back.
Changing a 100-GE interface to a 40-GE interface
1. Enter system view.
system-view
2. Enter 100-GE interface view.
interface interface-type interface-number
3. Change the 100-GE interface to a 40-GE interface.
using fortygige
By default, a 100-GE interface is not changed to a 40-GE interface.
Restoring a 40-GE interface that was changed from a 100-GE interface to a 100-GE interface
1. Enter system view.
system-view
2. Enter the view of a 40-GE interface that was changed from a 100-GE interface.
interface interface-type interface-number
3. Restore the 40-GE interface to a 100-GE interface.
using hundredgige
By default, a 100-GE interface is not changed to a 40-GE interface.
Changing the interface type of a 10-GE interface
About this task
Change a 10-GE interface to a GE interface when either of the following conditions exists:
· The peer is a GE interface.
· No 10-GE transceiver module is available, and GE transceiver modules are available.
If you need higher bandwidth, you can restore a GE interface that was changed from a 10-GE interface to a 10-GE interface.
Restrictions and guidelines for interface change between 10-GE interface and GE interface
This feature is supported only on the default MDC.
This configuration takes effect in real time, and cannot be rolled back.
Changing a 10-GE interface to a GE interface
1. Enter system view.
system-view
2. Enter 10-GE interface view.
interface ten-gigabitethernet interface-number
3. Change the 10-GE interface to a GE interface.
using gigabit
By default, a 10-GE interface is not changed to a GE interface.
Restoring a GE interface that was changed from a 10-GE interface to a 10-GE interface
1. Enter system view.
system-view
2. Enter the view of a GE interface that was changed from a 10-GE interface.
interface gigabitethernet interface-number
3. Restore the GE interface to a 10-GE interface.
using tengige
By default, a GE interface is not changed to a 10-GE interface.
Configuring the operating mode for a 10-GE interface
About this task
10-GE interfaces support the following operating modes:
· LAN mode—In LAN mode, a 10-GE interface transmits Ethernet packets and provides Ethernet network access.
· WAN mode—In WAN mode, a 10-GE interface transmits SDH frames and provides SDH network access. In this mode, a 10-GE interface supports only point-to-point connections.
Restrictions and guidelines
Interfaces on the interface card are separated into four-member interface groups. Interfaces in the same group must operate in the same mode. To modify the operating mode of the interfaces in a group, perform this task on the lowest numbered interface in the group. The change will be automatically synchronized to the remaining interfaces in the group.
A 10-GE interface operating in WAN mode encapsulates Ethernet packets in SDH frames. A 10G POS interface encapsulates PPP packets in SDH frames. However, they cannot communicate with each other because they encapsulate different kinds of packets.
Procedure
1. Enter system view.
system-view
2. Enter 10-GE interface view.
interface ten-gigabitethernet interface-number
3. Configure the 10-GE interface to operate in LAN or WAN mode.
port-mode { lan | wan }
By default, a 10-GE interface operates in LAN mode.
Setting the J0 and J1 overhead bytes for a 10-GE interface
About this task
The overhead bytes in SDH frames provide the operation and maintenance features such as hierarchical management of the transmission network. J0 and J1 bytes provide internetworking support between devices of different countries, regions, or vendors.
The Regenerator Section Trace byte J0 is usually configured as a section access point identifier. The sending end keeps the connection with the receiving end by sending this byte repeatedly.
The Path Trace byte J1 is usually configured as a high-order path access point identifier. J1 also enables two ends to keep their connection.
To ensure smooth communication, make sure the sending and receiving ends have the same J0 and J1 bytes.
Procedure
1. Enter system view.
system-view
2. Enter 10-GE interface view.
interface ten-gigabitethernet interface-number
3. Configure the 10-GE interface to operate in WAN mode.
port-mode wan
By default, a 10-GE interface operates in LAN mode.
4. Set the J0 and J1 bytes.
flag { j0 | j1 } sdh flag-value
By default, the J0 and J1 bytes are not set.
Configuring basic settings of an Ethernet interface
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/2/0/1 Interface.
4. Set the speed for the Ethernet interface.
speed { 1000 | 10000 }
By default, the speed of an interface on a card is its initial speed.
5. 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.
6. Bring up the Ethernet interface.
undo shutdown
By default, an Ethernet interface is up.
Configuring basic settings of an Ethernet subinterface
Restrictions and guidelines for Ethernet subinterface basic settings
The shutdown command cannot be executed 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/2/0/1.1 Interface.
4. Set the expected bandwidth for the Ethernet subinterface.
bandwidth bandwidth-value
By default, the expected bandwidth (in kbps) is the interface baud rate divided by 1000.
5. Bring up the Ethernet subinterface.
undo shutdown
By default, an Ethernet subinterface is up.
Configuring the link mode of an Ethernet interface
About this task
Ethernet interfaces operate differently depending on the hardware structure of interface cards:
· Some Ethernet interfaces can operate only as Layer 2 Ethernet interfaces (in bridge mode).
· Some Ethernet interfaces can operate only as Layer 3 Ethernet interfaces (in route mode).
· Some Ethernet interfaces can operate either as Layer 2 or Layer 3 Ethernet interfaces. You can set the link mode to bridge or route for these Ethernet interfaces.
Restrictions and guidelines
After you change the link mode of an Ethernet interface, all commands (except the shutdown command) 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, an Ethernet interface operates in Layer 3 mode.
Configuring jumbo frame support
About this task
Jumbo frames are frames larger than a fixed size and are typically received by an Ethernet interface during high-throughput data exchanges, such as file transfers.
The Ethernet interface processes jumbo frames in the following ways:
· When you configure the Ethernet interface to deny jumbo frames by using the undo jumboframe enable command, the Ethernet interface discards jumbo frames.
· When you configure the Ethernet interface 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 9732 bytes to pass through all Layer 2 Ethernet interfaces.
Setting the number of interframe bytes
About this task
Ethernet frames are separated by the interframe gaps. By adjusting the interframe gap size for an interface, you can adjust the packet forwarding ratio and the forwarding capability of the interface. When rate limit is configured for an interface, to ensure smooth communication, you might need to adjust the interframe gap size.
Restrictions and guidelines
You must set the same interframe gap size for interfaces on both ends of a link.
Typically, use the default interframe gap size. To modify the interframe gap size, consult the professionals. An improper interframe gap size setting might cause packet loss or even interface failure.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Set the number of interframe bytes.
itf number number
By default, the number of interframe bytes is 12.
Configuring physical state change suppression on an Ethernet interface
About this task
The physical link state of an Ethernet interface is either up or down. Each time the physical link of an interface comes up or goes down, the interface immediately reports the change to the CPU. The CPU then performs the following operations:
· Notifies the upper-layer protocol modules (such as routing and forwarding modules) of the change for guiding packet forwarding.
· Automatically generates traps and logs to inform users to take the correct actions.
To prevent frequent physical link flapping from affecting system performance, configure physical state change suppression. You can configure this feature to suppress only link-down events, only link-up events, or both. If an event of the specified type still exists when the suppression interval expires, the system reports the event to the CPU.
Restrictions and guidelines
Do not enable this feature on an interface that has spanning tree protocols enabled.
The link-delay and dampening commands are mutually exclusive on an Ethernet interface.
You can configure different suppression intervals for link-up and link-down events.
If you execute the link-delay command multiple times on an interface, the following rules apply:
· You can configure the suppression intervals for link-up and link-down events separately.
· If you configure the suppression interval multiple times for link-up or link-down events, the most recent configuration takes effect.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Configure physical state change suppression.
link-delay { down | up } [ msec ] delay-time
By default, physical state change suppression is not configured.
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 link-delay and dampening commands are mutually exclusive on an Ethernet interface.
The dampening command does not take effect on the administratively down events. When you execute the shutdown command, the penalty restores to 0, and the interface reports the down event to the upper-layer protocols.
Do not enable the dampening feature on an interface with MSTP enabled.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Enable dampening on the interface.
dampening [ half-life reuse suppress max-suppress-time ]
By default, interface dampening is disabled on Ethernet interfaces.
Configuring FEC
About this task
The forward error correction (FEC) feature corrects packet errors to improve transmission quality. It attaches correction information to a packet at the sending end, and corrects error codes generated during transmission at the receiving end based on the correction information. You can set the FEC mode as needed.
Restrictions and guidelines
This feature is supported only on 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
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.
A device supports either the system view settings or the Ethernet interface view settings.
· The statistics polling interval configured in system view takes effect on all Ethernet interfaces.
· The statistics polling interval configured in Ethernet interface view takes effect only on the current interface.
The statistics polling interval configured in Ethernet interface view takes precedence over the statistics polling interval configured in system view. The interval configured in system view takes effect on an Ethernet interface only when no interval is configured or the default interval is configured for the Ethernet interface.
Restrictions and guidelines for setting the statistics polling interval
As a best practice, use the default statistics polling interval in system view. A short statistics polling interval in system view might decrease the system performance and result in inaccurate statistics.
Setting the statistics polling interval in system view
1. Enter system view.
system-view
2. Set the statistics polling interval.
flow-interval interval
By default, the statistics polling interval is 300 seconds.
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 for an Ethernet interface is 300 seconds.
Enabling loopback testing on an Ethernet interface
About this task
Perform this task to determine whether an Ethernet link works correctly.
Loopback testing includes the following types:
· Internal loopback testing—Tests the device where the Ethernet interface resides. The Ethernet interface sends outgoing packets back to the local device. If the device fails to receive the packets, the device fails.
· External loopback testing—Tests the inter-device link. The Ethernet interface sends incoming packets back to the remote device. If the remote device fails to receive the packets, the inter-device link fails.
Restrictions and guidelines
After you enable this feature on an Ethernet interface, the interface does not forward data traffic.
The shutdown and loopback commands are mutually exclusive.
After you enable this feature on an Ethernet interface, the Ethernet interface switches to full duplex mode. After you disable this feature, the Ethernet interface restores to its duplex setting.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Enable loopback testing.
loopback { external | internal }
Configuring interface alarm functions
About this task
With the interface alarm functions enabled, when the number of sent or received error packets or 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 number of sent or received error packets or 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.
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 of the specified slot. The configuration in interface view takes effect only on the current interface.
· 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 [ crc-error | input-error | input-usage | output-error | output-usage | sdh-b1-error | sdh-b2-error | sdh-error ] *
By default, all alarm functions are enabled for interfaces.
Configuring CRC error packet alarm parameters
1. Enter system view.
system-view
2. Configure global CRC error packet alarm parameters.
ifmonitor crc-error chassis chassis-number slot slot-number cpu cpu-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for CRC error packets.
3. Enter Ethernet interface view.
interface interface-type interface-number
4. Configure CRC error packet alarm parameters for the interface.
port ifmonitor crc-error [ ratio ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global CRC error packet alarm parameters.
Configuring input error packet alarm parameters
1. Enter system view.
system-view
2. Configure global input error packet alarm parameters.
ifmonitor input-error chassis chassis-number slot slot-number cpu cpu-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for input error packets.
3. Enter Ethernet interface view.
interface interface-type interface-number
4. Configure input error packet alarm parameters for the interface.
port ifmonitor input-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global input error packet alarm parameters.
Configuring output error packet alarm parameters
1. Enter system view.
system-view
2. Configure global output error packet alarm parameters.
ifmonitor output-error chassis chassis-number slot slot-number cpu cpu-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for output error packets.
3. Enter Ethernet interface view.
interface interface-type interface-number
4. Configure output error packet alarm parameters.
port ifmonitor output-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global output error packet alarm parameters.
Configuring input bandwidth usage alarm parameters
1. Enter system view.
system-view
2. Configure global input bandwidth usage alarm parameters.
ifmonitor input-usage chassis chassis-number slot slot-number cpu cpu-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.
Configuring output bandwidth usage alarm parameters
1. Enter system view.
system-view
2. Configure global output bandwidth usage alarm parameters.
ifmonitor output-usage chassis chassis-number slot slot-number cpu cpu-number high-threshold high-value low-threshold low-value
By default, the upper threshold is 90 and the lower threshold is 80 for output bandwidth usage alarms.
3. Enter Ethernet interface view.
interface interface-type interface-number
4. Configure output bandwidth usage alarm parameters.
port ifmonitor output-usage high-threshold high-value low-threshold low-value
By default, an interface uses the global output bandwidth usage alarm parameters.
Configuring SDH error packet alarm parameters
1. Enter system view.
system-view
2. Configure global SDH error packet alarm parameters.
ifmonitor sdh-error chassis chassis-number slot slot-number cpu cpu-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for SDH error packets.
3. Enter Ethernet interface view.
interface interface-type interface-number
4. Configure SDH error packet alarm parameters for the interface.
port ifmonitor sdh-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global SDH error packet alarm parameters.
Configuring SDH-B1 error packet alarm parameters
1. Enter system view.
system-view
2. Configure global SDH-B1 error packet alarm parameters.
ifmonitor sdh-b1-error chassis chassis-number slot slot-number cpu cpu-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for SDH-B1 error packets.
3. Enter Ethernet interface view.
interface interface-type interface-number
4. Configure SDH-B1 error packet alarm parameters for the interface.
port ifmonitor sdh-b1-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global SDH-B1 error packet alarm parameters.
Configuring SDH-B2 error packet alarm parameters
1. Enter system view.
system-view
2. Configure global SDH-B2 error packet alarm parameters.
ifmonitor sdh-b2-error chassis chassis-number slot slot-number cpu cpu-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, the upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for SDH-B2 error packets.
3. Enter Ethernet interface view.
interface interface-type interface-number
4. Configure SDH-B2 error packet alarm parameters for the interface.
port ifmonitor sdh-b2-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global SDH-B2 error packet alarm parameters.
Displaying the operating status and information of an interface
About this task
In interface view, to quickly view the operating status or packet statistics of the interface, execute this command.
For an interface, the output from the display this interface command in interface view is the same as the output from the display interface interface-type interface-number command in any view.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface view.
interface interface-type interface-number
3. Display the operating status and information of an interface.
display this interface
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 3 Ethernet interface
Setting the MTU for an Ethernet interface or subinterface
Restrictions and guidelines
The maximum transmission unit (MTU) of an Ethernet interface or subinterface affects the fragmentation and reassembly of IP packets on the interface. Typically, you do not need to modify the MTU of an interface.
The mtu size command executed in main interface view takes effect only on the main interface. The mtu size command executed in subinterface view takes effect only on the subinterface.
When a main interface and its subinterfaces are in the same MDC, the mtu size spread command executed in main interface view can modify the MTU for both the main interface and its subinterfaces. However, the MTU separately configured for a subinterface takes priority.
Procedure
1. Enter system view.
system-view
2. Enter Ethernet interface or subinterface view.
interface interface-type { interface-number | interface-number.subnumber }
3. Set the MTU.
¡ Separately set the MTU for the Ethernet interface or subinterface.
mtu size
¡ Set the MTU for the main interface and its subinterfaces.
mtu size spread
Subinterfaces do not support this command.
The default setting is 1500 bytes.
Enabling packet statistics collection on a Layer 3 Ethernet subinterface
About this task
This feature is resource intensive. The system becomes busy and the CPU usage increases when you enable this feature on a large number of Ethernet subinterfaces or set a shorter interval by using the flow-interval command.
Procedure
1. Enter system view.
system-view
2. Enter Layer 3 Ethernet subinterface view.
interface interface-type interface-number.subnumber
3. Enable packet statistics collection on the Layer 3 Ethernet subinterface.
traffic-statistic enable
By default, packet 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 for an Ethernet interface or subinterface
Execute display commands in any view and reset commands in user view.
Task |
Command |
Display interface traffic statistics. |
display counters { inbound | outbound } interface [ interface-type [ interface-number | interface-number.subnumber ] ] |
Display traffic rate statistics of interfaces in up state over the last statistics polling interval. |
display counters rate { inbound | outbound } interface [ interface-type [ interface-number | interface-number.subnumber ] ] |
Display the Ethernet module statistics. |
display ethernet statistics chassis chassis-number slot slot-number [ cpu cpu-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 the physical attributes of an interface. |
display interface [ interface-type [ interface-number ] ] phy-option |
Display operating status and information of all interfaces except subinterfaces. |
display interface [ interface-type ] [ brief [ description | down ] ] main |
Clear interface or subinterface statistics. |
reset counters interface [ interface-type [ interface-number | interface-number.subnumber ] ] |
Clear the Ethernet module statistics. |
reset ethernet statistics [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] |
Clear the statistics of dropped packets on the specified interfaces. |
reset packet-drop interface [ interface-type [ interface-number ] ] |