Login
- Table of Contents
-
- 03-Interface Configuration Guide
- 00-Preface
- 01-Bulk interface configuration
- 02-Ethernet interface configuration
- 03-WAN interface configuration
- 04-POS interface configuration
- 05-CPOS interface configuration
- 06-ATM interface configuration
- 07-Loopback, null, and inloopback interface configuration
- 08-FlexE interface configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-FlexE interface configuration | 218.32 KB |
Restrictions and guidelines: FlexE interface configuration
FlexE interface tasks at a glance
Changing the type of an interface
Creating a FlexE group interface
Adding a FlexE physical interface to a FlexE group interface
Creating a FlexE logical interface and set its bandwidth
Creating a FlexE logical interface at the granularity of 5 Gbps and configuring interface bandwidth
Configuring basic settings of a FlexE interface
Setting the MAC address of a Layer 3 FlexE logical interface
Setting the MTU of a FlexE logical interface
Changing the link mode of a FlexE logical interface
Configuring jumbo frame support for a FlexE logical interface
Configuring physical state change suppression on a FlexE interface
Configuring dampening on a FlexE physical interface
Setting the statistics polling interval on a FlexE logical interface
Enabling loopback testing on a FlexE interface
Enabling packet statistics collection on a FlexE logical subinterface
Enabling interframe gap and preamble statistics in the traffic statistics
Configuring interface alarm functions
About interface alarm functions
Enabling interface alarm functions
Setting CRC error packet alarm parameters
Setting input error packet alarm parameters
Setting output error packet alarm parameters
Setting inbound bandwidth usage alarm parameters
Setting outbound bandwidth usage alarm parameters
Configuring giant packet alarm parameters
Configuring runt packet alarm parameters
Displaying the operating status and information of an interface
Restoring the default settings for a FlexE interface
Display and maintenance commands for FlexE interfaces
Configuring FlexE interfaces
Only CEPC-CQ8L, RX-NIC-CQ1LF, RX-NIC-CQ2LF, RX-NIC-LGQ2L, and RX-NIC-LGQ4L subcards support this feature.
About FlexE interfaces
The Flexible Ethernet (FlexE) technology provides service providers with flexibility to assign different bandwidth to interfaces to meet bandwidth requirements of different services.
FlexE interfaces include the following types:
· FlexE physical interface—A FlexE physical interface is a physical interface that switches from standard Ethernet mode to flexible Ethernet mode. FlexE physical interfaces can be added to a FlexE group interface and the bandwidth of the FlexE group interface is the sum of the bandwidths of all FlexE physical interfaces in the group interface.
· FlexE logical interface—A FlexE logical interface is a logical interface of which the bandwidth can be flexibly specified. A FlexE group interface assigns bandwidth to FlexE logical interfaces according to requirements of different services.
Restrictions and guidelines: FlexE interface configuration
FlexE interfaces cannot be used as IRF physical interfaces.
FlexE interface tasks at a glance
To configure FlexE interfaces, perform the following tasks:
1. Changing the type of an interface
2. Configuring a FlexE group interface
a. Creating a FlexE group interface
b. Adding a FlexE physical interface to a FlexE group interface
c. Creating a FlexE logical interface and set its bandwidth
3. Configuring basic settings of a FlexE interface
4. Configure a FlexE physical interface
¡ (Optional.) Configuring physical state change suppression on a FlexE interface
¡ (Optional.) Configuring dampening on a FlexE physical interface
¡ (Optional.) Configuring FEC
¡ (Optional.) Enabling loopback testing on a FlexE interface
5. Configure a FlexE logical interface
¡ (Optional.) Setting the MAC address of a Layer 3 FlexE logical interface
¡ (Optional.) Setting the MTU of a FlexE logical interface
¡ (Optional.) Changing the link mode of a FlexE logical interface
¡ (Optional.) Configuring jumbo frame support for a FlexE logical interface
¡ (Optional.) Configuring physical state change suppression on a FlexE interface
¡ (Optional.) Enabling loopback testing on a FlexE interface
¡ (Optional.) Enabling packet statistics collection on a FlexE logical subinterface
¡ (Optional.) Enabling interframe gap and preamble statistics in the traffic statistics
¡ (Optional.) Displaying the operating status and information of an interface
6. (Optional.) Configuring interface alarm functions
7. (Optional.) Restoring the default settings for a FlexE interface
Changing the type of an interface
About this task
The bandwidth of an interface in standard Ethernet mode is fixed, and the bandwidth of an interface is FlexE mode can be flexibly specified. To assign bandwidth at the granularity of 5 Gbps, execute the port-type flexe command to switch the type of the interface from Ethernet to FlexE.
Restrictions and guidelines
You cannot change the type of a FlexE physical interface if the interface has been added to a FlexE group interface.
For an RX-NIC-LGQ2L subcard, to change the type of an interface on it, you must execute the card-mode command to change the operating mode of the subcard. For more information about the card-mode command, see device management commands in Fundamentals Command Reference.
For an RX-NIC-CQ1LF, RX-NIC-CQ2LF, or RX-NIC-LGQ4L subcard, you can use the port-type command to directly change the type of an interface.
To change the type of an interface on an RX-NIC-LGQ4L card, first execute the subslot-working-mode command to configure the subcard to operate in ethernet-flexe mode. For more information about the subslot-working-mode command, see device management commands in Fundamentals Command Reference.
Procedure
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
3. Change the type of the interface.
¡ Change a standard Ethernet interface to a FlexE interface.
port-type flexe
¡ Change a FlexE interface to a standard Ethernet interface.
port-type ethernet
|
|
CAUTION: After the type of an interface is changed, the system deletes the original interface and creates a new interface that is numbered the same as the original interface. All the other commands are restored to the default on the new interface. |
Creating a FlexE group interface
About this task
After you create a FlexE group interface, you can create FlexE logical interfaces in the FlexE group interface as needed. Then, you can flexibly assign the total bandwidths to FlexE logical interfaces according to the bandwidth requirements of services.
Restrictions and guidelines
When the device operates in standalone mode, FlexE group interfaces are named in the format of FlexE-Group A/B/C. The letters that follow the interface type represent the following elements:
· A—Card slot number.
· B—Subcard slot number.
· C—Group ID of the FlexE group interface.
When the device is in IRF mode, FlexE group interfaces are named in the format of FlexE-Group A/B/C/D. The letters that follow the interface type represent the following elements:
· A—IRF member ID, which can be 1, 2, 3, or 4.
· B—Card slot number.
· C—Subcard slot number.
· D—Group ID of the FlexE group interface.
The number of FlexE group interfaces must be equal to or smaller than the number of FlexE physical interfaces on an interface module.
You can delete a FlexE group interface only if the FlexE group interface does not have any FlexE physical or logical interfaces.
Procedure
1. Enter system view.
system-view
2. Create a FlexE group interface and enter its view.
interface flexe-group interface-number
The last tier in the interface number of a FlexE group interface represents the group ID.
3. (Optional.) Configure a description of the FlexE group interface.
description text
By default, the configuration of a FlexE group interface is the interface name plus Interface (for example, FlexE-Group3/1/1 Interface).
Adding a FlexE physical interface to a FlexE group interface
About this task
Perform this task so you can bind timeslots of FlexE physical interfaces in a FlexE group interface to FlexE logical interfaces as per service requirements.
Restrictions and guidelines
When you add a FlexE physical interface to a FlexE group interface, follow these restrictions and guidelines:
· You can add a FlexE physical interface only to a FlexE group interface.
· On an RX-NIC-CQ1LF or RX-NIC-CQ2LF subcard, only one FlexE physical interface can be added to a FlexE group interface.
· On an RX-NIC-LGQ2L or RX-NIC-LGQ4L subcard, up to two FlexE physical interfaces can be added to a FlexE group interface. The member interface numbers must be 1 and 2, 3 and 4, 5 and 6, or 7 and 8.
· For correct communication between FlexE physical interfaces at both of the ends of a link, you must add the FlexE physical interfaces to the same FlexE group interface. Make sure the FlexE physical interfaces have the same PHY number.
If the bandwidth or timeslots of a FlexE physical interface have been bound to a FlexE logical interface, you cannot the following tasks:
· Remove the FlexE physical interface from the FlexE group interface.
· Change the PHY number of the FlexE physical interface.
Procedure
1. Enter system view.
system-view
2. Enter FlexE group interface view.
interface flexe-group interface-number
3. Add a FlexE physical interface to the FlexE group interface.
bind interface interface-type interface-number phy-number number
By default, no FlexE physical interfaces exist in a FlexE group interface.
Creating a FlexE logical interface and set its bandwidth
Creating a FlexE logical interface at the granularity of 5 Gbps and configuring interface bandwidth
About this task
Perform this task to set the client ID for a FlexE logical interface to be created and create the FlexE logical interface in a FlexE group interface. The interface number of the FlexE logical interface is in the format of FlexE-group-interface-number:client ID. For example, after you execute the client-id 10 command in the view of FlexE-Group 3/1/1, the device creates FlexE logical interface FlexE3/1/1:10 in which 10 is the client ID.
You can set the bandwidth of a FlexE logical interface in bandwidth or timeslot configuration mode set by using the flexe config-mode command in system view.
· If the bandwidth configuration mode is bandwidth mode, you can only use the client client-id bandwidth command to set the bandwidth of the FlexE logical interface.
· If the bandwidth configuration mode is timeslot mode, you can only use the client client-id binding interface interface-type interface-number timeslot timeslot-list command to set the bandwidth of FlexE logical interfaces.
Restrictions and guidelines
For correct communication between FlexE logical interfaces at both ends of a link, you must perform the following tasks:
· Create a FlexE group interface at both of the devices.
· Set the same client ID for the two FlexE group interfaces.
Procedure
1. Enter system view.
system-view
2. Set the bandwidth configuration mode for FlexE logical interfaces.
In standalone mode:
flexe config-mode slot slot-number subslot subslot-number { bandwidth | timeslot }
In IRF mode:
flexe config-mode chassis chassis-number slot slot-number subslot subslot-number { bandwidth | timeslot }
By default, the bandwidth mode is used.
3. Enter FlexE group interface view.
interface flexe-group interface-number
4. Create a FlexE logical interface and set its bandwidth.
client client-id { bandwidth bandwidth-value | bind interface interface-type interface-number timeslot timeslot-list }
Configuring basic settings of a FlexE interface
1. Enter system view.
system-view
2. Enter FlexE physical interface view or FlexE logical interface view.
interface interface-type interface-number
3. Configure the description of the FlexE interface.
description text
By default, the description of a FlexE interface is interface-name Interface. For example, FlexE3/1/1 Interface.
4. Set the expected bandwidth of the FlexE interface.
bandwidth bandwidth-value
By default, the expected bandwidth of an interface is interface bandwidth divided by 1000 kbps.
The expected bandwidth is an informational parameter used only by higher-layer protocols for calculation. You cannot adjust the actual bandwidth of an interface by using this command.
This command is not supported on FlexE physical interfaces.
5. Bring up the FlexE interface.
undo shutdown
By default, a FlexE interface is up.
Setting the MAC address of a Layer 3 FlexE logical interface
1. Enter system view.
system-view
2. Enter Layer 3 FlexE logical interface view.
interface flexe interface-number
3. Set the MAC address of the Layer 3 FlexE logical interface.
mac-address mac-address
By default, no MAC address is set for a Layer 3 FlexE logical interface.
Setting the MTU of a FlexE logical interface
Restrictions and guidelines
The maximum transmission unit (MTU) of a FlexE logical interface affects the fragmentation and reassembly of IP packets on the interface. Typically, you do not need to modify the MTU of a FlexE logical interface.
Procedure
1. Enter system view.
system-view
2. Enter FlexE logical interface view.
interface flexe { interface-number | interface-number.subnumber }
3. Set the MTU of the FlexE logical interface.
mtu size
By default, the MTU of a FlexE logical interface is 1500 bytes.
Changing the link mode of a FlexE logical interface
About this task
A FlexE logical interface can operate at one of the following link modes:
· bridge—The Flex logical interface operates as a Layer 2 FlexE logical interface.
· route—The Flex logical interface operates as a Layer 3 FlexE logical interface.
Restrictions and guidelines
After you change the link mode of a FlexE logical interface, all commands (except the shutdown command) on the FlexE logical interface are restored to their defaults in the new link mode.
Procedure
1. Enter system view.
system-view
2. Enter FlexE logical interface view.
interface flexe interface-number
3. Change the link mode of the FlexE logical interface.
port link-mode { bridge | route }
By default, the link mode of a FlexE logical interface is route.
Configuring jumbo frame support for a FlexE logical interface
About this task
Jumbo frames are frames larger than a device-specific size and are typically received by a FlexE logical interface during high-throughput data exchanges, such as file transfers.
The FlexE logical interface processes jumbo frames in the following ways:
· When the FlexE logical interface is configured to deny jumbo frames (by using the undo jumboframe enable command), the FlexE logical interface discards jumbo frames.
· When the FlexE logical interface is configured with jumbo frame support, the FlexE logical 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 FlexE logical interface view.
interface flexe interface-number
3. Configure jumbo frame support.
jumboframe enable [ size ]
By default, the device allows jumbo frames within 10240 bytes to pass through all FlexE logical interfaces.
If you execute this command multiple times, the most recent configuration takes effect.
Configuring physical state change suppression on a FlexE interface
About this task
The physical link state of a FlexE 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
You can set different suppression intervals for link-up and link-down events.
If you set the suppression interval multiple times for the same type of link suppression events on a FlexE physical interface, the most recent configuration takes effect.
Procedure
1. Enter system view.
system-view
2. Enter FlexE physical interface view or FlexE logical interface view.
interface flexe interface-number
3. Configure physical state change suppression on the FlexE interface.
link-delay { down | up } [ msec ] delay-time
By default, the device reports the physical state change of a FlexE interface to the CPU immediately.
Configuring dampening on a FlexE physical 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 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 FlexE physical 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 CEPC-CQ8L, RX-NIC-CQ1LF, and RX-NIC-CQ2LF subcards.
Make sure you set the same FEC mode for both interfaces of a link.
Procedure
1. Enter system view.
system-view
2. Enter FlexE physical interface view.
interface interface-type interface-number
3. Set the FEC mode of the interface.
port fec mode { auto | none | rs-fec }
By default, the FEC mode of an interface is auto.
Setting the statistics polling interval on a FlexE logical interface
About this task
The statistics polling interval defines the interval at which the device collects packet statistics on a FlexE logical interface. 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.
Procedure
1. Enter system view.
system-view
2. Enter FlexE logical interface view.
interface flexe interface-number
3. Set the statistic polling interval on the FlexE logical interface.
flow-interval interval
By default, the statistic polling interval is 300 seconds on a FlexE logical interface.
Enabling loopback testing on a FlexE interface
About this task
Use this feature to determine whether a FlexE interface works correctly.
Internal loopback testing tests the device where the FlexE interface resides. The FlexE 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 a FlexE interface, the interface does not forward data traffic.
Procedure
1. Enter system view.
system-view
2. Enter FlexE physical interface view.
interface interface-type interface-number
3. Enable loopback testing on the interface.
loopback internal
By default, loopback testing is disabled on a FlexE physical interface.
Enabling packet statistics collection on a FlexE logical subinterface
1. Enter system view.
system-view
2. Enter FlexE logical subinterface view.
interface flexe interface-number.subnumber
3. Enable packet statistics collection on the subinterface.
traffic-statistic enable
By default, packet statistics collection is disabled on an subinterface.
4. (Optional.) Display the FlexE logical subinterface traffic statistics.
display interface
display counters
The Input and Output fields in the display interface command output display the FlexE logical subinterface traffic statistics.
Enabling interframe gap and preamble statistics in the traffic statistics
About this task
With the display interface command executed, the Last 300 seconds input rate or Last 300 seconds output rate field in the command output displays the average outbound or inbound traffic rate in the most recent 300 seconds.
By default, traffic rate = native frame length × packet count per second. Execute the traffic-statistic include-interframe command to obtain the total traffic statistics, including the native frame length, interframe gap length and preamble length, within a specific time period. With this command executed, traffic rate = (native frame length + interframe gap length + preamble length) × packet count per second.
Procedure
1. Enter system view.
system-view
2. Enter FlexE logical interface view.
interface interface-type interface-number
3. Enable interframe gap and preamble statistics in the traffic statistics.
traffic-statistic include-interframe
By default, interframe gap and preamble statistics are disabled in the traffic statistics.
Configuring interface alarm functions
About interface alarm functions
With the interface alarm functions enabled, when the number of error packets 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 error packets 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 interface 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 | giant | input-error | input-usage | output-error | output-usage | runt ] *
By default, all alarm functions are enabled on interfaces.
Setting CRC error packet alarm parameters
1. Enter system view.
system-view
2. Set global CRC error packet alarm parameters.
In standalone mode:
ifmonitor crc-error slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
In IRF mode:
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 FlexE logical interface view.
interface flexe interface-number
4. Set CRC error packet alarm parameters on the FlexE logical interface.
port ifmonitor crc-error [ ratio ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, a FlexE logical interface uses the global CRC error packet alarm parameters.
Setting input error packet alarm parameters
1. Enter system view.
system-view
2. Set global input error packet alarm parameters.
In standalone mode:
ifmonitor input-error slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
In IRF mode:
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 FlexE logical interface view.
interface flexe interface-number
4. Set input error packet alarm parameters on the FlexE logical interface.
port ifmonitor input-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, a FlexE logical interface uses the global input error packet alarm parameters.
Setting output error packet alarm parameters
1. Enter system view.
system-view
2. Set global output error packet alarm parameters.
In standalone mode:
ifmonitor output-error slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
In IRF mode:
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 FlexE logical interface view.
interface flexe interface-number
4. Set output error packet alarm parameters on the FlexE logical interface.
port ifmonitor output-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, a FlexE logical interface uses the global output error packet alarm parameters.
Setting inbound bandwidth usage alarm parameters
1. Enter system view.
system-view
2. Set global inbound bandwidth usage alarm parameters.
In standalone mode:
ifmonitor input-usage slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value
In IRF mode:
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%.
3. Enter FlexE logical interface view.
interface flexe interface-number
4. Set inbound bandwidth usage alarm parameters on the FlexE logical interface.
port ifmonitor input-usage high-threshold high-value low-threshold low-value
By default, a FlexE logical interface uses the global inbound bandwidth usage alarm parameters.
Setting outbound bandwidth usage alarm parameters
1. Enter system view.
system-view
2. Set global outbound bandwidth usage alarm parameters.
In standalone mode:
ifmonitor output-usage slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value
In IRF mode:
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%.
3. Enter FlexE logical interface view.
interface flexe interface-number
4. Set outbound bandwidth usage alarm parameters on the FlexE logical interface.
port ifmonitor output-usage high-threshold high-value low-threshold low-value
By default, a FlexE logical interface uses the global outbound bandwidth usage alarm parameters.
Configuring giant packet alarm parameters
1. Enter system view.
system-view
2. Configure global giant packet alarm parameters.
In standalone mode:
ifmonitor giant slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
In IRF mode:
ifmonitor giant 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 giant packets.
3. Enter FlexE logical interface view.
interface flexe interface-number
4. Configure giant packet alarm parameters for the interface.
port ifmonitor giant high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global giant packet alarm parameters.
.
Configuring runt packet alarm parameters
1. Enter system view.
system-view
2. Configure global runt packet alarm parameters.
In standalone mode:
ifmonitor runt slot slot-number [ cpu cpu-number ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
In IRF mode:
ifmonitor runt 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 runt packets.
3. Enter FlexE logical interface view.
interface flexe interface-number
4. Configure runt packet alarm parameters for the interface.
port ifmonitor runt high-threshold high-value low-threshold low-value interval interval [ shutdown ]
By default, an interface uses the global runt 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 FlexE logical interface view.
interface flexe interface-number
3. Display the operating status and information of an interface.
display this interface
Restoring the default settings for a FlexE interface
|
|
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 FlexE physical interface view, FlexE logical interface view, or FlexE group interface view.
interface interface-type interface-number
3. Restore the default settings for the interface.
default
Display and maintenance commands for FlexE interfaces
Execute display commands in any view.
|
Task |
Command |
|
Display interface information. |
display interface [ interface-type [ interface-number | interface-number.subnumber ] ] [ brief [ description | down ] ] |
