- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
07-FlexE interface commands | 556.89 KB |
FlexE interface commands
bandwidth
Use bandwidth to set the expected bandwidth of an interface.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
The expected bandwidth (in kbps) is the interface baud rate divided by 1000.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
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.
Examples
# Set the expected bandwidth of FlexE 1/0/1:1 to 1000 kbps.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] bandwidth 1000
bind interface
Use bind interface to add a FlexE physical interface to a FlexE group interface.
Use undo bind interface to remove a FlexE physical interface from a FlexE group interface.
Syntax
bind interface interface-type interface-number phy-number number
undo bind interface interface-type interface-number
Default
No FlexE physical interfaces exist in a FlexE group interface.
Views
FlexE group interface view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies a FlexE physical interface by its type and number.
phy-number number: Specifies the PHY number of the FlexE physical interface, in the range of 1 to 254.
Usage 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.
· 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.
· You can repeat this command to add multiple FlexE physical interfaces to a FlexE group interface. Make sure the PHY number for each FlexE physical interfaces is unique in a FlexE group interface.
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.
Examples
# Add FlexE-100G 1/0/1 to FlexE-group 1/0/1 and set the PHY number of the FlexE physical interface to 2.
<Sysname> system-view
[Sysname] interface flexe-group 1/0/1
[Sysname-FlexE-Group1/0/1] bind interface flexe-hundredgig 1/0/1 phy-number 2
Related commands
client
interface flexe-group
broadcast-suppression
Use broadcast-suppression to enable broadcast suppression and set the broadcast suppression threshold.
Use undo broadcast-suppression to disable broadcast suppression.
Syntax
broadcast-suppression { ratio | pps max-pps | kbps max-kbps }
undo broadcast-suppression
Default
A FlexE logical interface does not suppress broadcast traffic.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
ratio: Specifies the broadcast suppression threshold as a percentage of the interface bandwidth. The value range for this argument is 0 to 100. A smaller value means that less broadcast traffic is allowed to pass through.
pps max-pps: Specifies the maximum number of broadcast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.
kbps max-kbps: Specifies the maximum number of kilobits of broadcast traffic that the FlexE logical interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.
Usage guidelines
The broadcast storm suppression features limits the size of broadcast traffic to a threshold on an interface. When the broadcast traffic on the interface exceeds this threshold, the system drops packets until the traffic drops below this threshold.
Both the storm-constrain command and the broadcast-suppression command can suppress broadcast storms on a port. The broadcast-suppression command uses the chip to physically suppress broadcast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress broadcast traffic.
For the traffic suppression result to be determined, do not configure both the storm-constrain broadcast command and the broadcast-suppression command on an interface.
The configured suppression threshold value in pps or kbps might be converted into a multiple of a step supported by the chip. As a result, the effective suppression threshold might be different from the configured one. To determine the suppression threshold that takes effect, see the prompts on the device.
Examples
# Set the broadcast suppression threshold to 10000 kbps on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] broadcast-suppression kbps 10000
The actual value is 10048 on port FlexE1/0/1:1 currently.
The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip supports only step 64.
Related commands
multicast-suppression
unicast-suppression
client
Use client to set the client ID for a FlexE logical interface to be created and create the FlexE logical interface in a FlexE group interface.
Use undo client to restore the default.
Syntax
client client-id { bandwidth { bandwidth-value | 1 | 1.25 | 2 | 2.5 | 3 | 3.75 | 4 } | bind interface interface-type interface-number timeslot timeslot-list }
undo client client-id [ bandwidth | bind interface interface-type interface-number ]
Default
No FlexE logical interfaces exist in a FlexE group interface.
Views
FlexE group interface view
Predefined user roles
network-admin
Parameters
client-id: Specifies the client ID of the FlexE group interface to be created, in the range of 1 to 65534. The interface number of the FlexE logical interface is in the form of FlexE-group-interface-number:client-ID.
bandwidth { bandwidth-value | 1 | 1.25 | 2 | 2.5 | 3 | 3.75 | 4 }: Specifies the bandwidth of the FlexE logical interface directly.
· bandwidth-value: Specifies the bandwidth, in GB. The value range is 5 to 4194303, and the step is 5.
· 1: Specifies the bandwidth of 1 GB.
· 1.25: Specifies the bandwidth of 1.25 GB.
· 2: Specifies the bandwidth of 2 GB.
· 2.5: Specifies the bandwidth of 2.5 GB.
· 3: Specifies the bandwidth of 3 GB.
· 3.75: Specifies the bandwidth of 3.75 GB.
· 4: Specifies the bandwidth of 4 GB.
bind interface interface-type interface-number timeslot timeslot-list: Specifies the bandwidth of the FlexE logical interface based on timeslots. You can bind timeslots of a FlexE physical interface to the FlexE logical interface. The bandwidth of the FlexE logical interface is timeslot-count × 5 GB.
· interface-type interface-number: Specifies the FlexE physical interface by it type and number.
· timeslot-list: Specifies a comma-separated list of timeslot items. Each item specifies a timeslot by its ID or a range of timeslots in the form of start_timeslot-end_timeslot. For example, 1,3-5. The maximum length of the timeslot list is 31 characters. The value range of timeslot IDs depend on FlexE physical interface type.
¡ For FlexE-50G interfaces, the value range for the timeslot ID is 0 to 9. Each timeslot represent bandwidth of 5 GB.
¡ For FlexE-100G interfaces, the value range for the timeslot ID is 0 to 19. Each timeslot represents bandwidth of 5 GB.
Usage guidelines
Use this command 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 1/0/1, the device creates FlexE logical interface FlexE1/0/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.
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.
Examples
# Create FlexE logical interface FlexE1/0/1:10 and set its bandwidth to 10 GB.
<Sysname> system-view
[Sysname] interface flexe-group 1/0/1
[Sysname-FlexE-Group1/0/1] bind interface flexe-hundredgig 1/0/1 phy-number 2
[Sysname-FlexE-Group1/0/1] client 10 bandwidth 10
Related commands
bind interface
flexe config-mode
interface flexe-group
client-channel
Use client-channel to create a client channel with the specified ID, assign bandwidth to the client channel, and enter its view, or enter the view of an existing client channel.
Use undo client-channel to delete a client channel and all its configuration.
Syntax
client-channel client-channel-id [ bandwidth bandwidth-value | interface interface-type interface-number timeslot timeslot-list ]
undo client-channel client-channel-id
Default
No client channel exists.
Views
FlexE-group interface view
Predefined user roles
network-admin
Parameters
client-channel-id: Specifies a client channel by its ID in the range of 1 to 65534. The client channel ID cannot be the same as a client ID in the FlexE-group interface view.
bandwidth bandwidth-value: Directly specifies the bandwidth for the client channel. The bandwidth-value argument specifies the client channel bandwidth in the range of 5 to 4194303 in Gbps. The bandwidth must in the step of 5.
interface interface-type interface-number timeslot timeslot-list: Assigns bandwidth to the client channel through specifying timeslots.
· The interface-type interface-number argument specifies a FlexE physical interface by its type and number. Make sure the specified interface has been assigned to the FlexE-group interface.
· The timeslot-list argument specifies a timeslot ID list, for example, 1,3-5. Use a hyphen (-) to specify a timeslot ID range, and separate multiple timeslot IDs or ranges by using commas (,). A timeslot ID list can contain up to 31 characters. The value range for this argument varies by the bandwidth of the specified FlexE physical interface.
¡ For a FlexE-50G interface, the timeslot ID is in the range of 0 to 9, and a timeslot represents bandwidth of 5 Gbps.
¡ For a FlexE-100G interface, the timeslot ID is in the range of 0 to 19, and a timeslot represents bandwidth of 5 Gbps.
Usage guidelines
To allocate bandwidth at the granularity of 10 Mbps, you can create client channels in a FlexE-group interface. Then, you can create FlexE logical interfaces of smaller bandwidth in a client channel.
When you create a client channel for the first time, you must allocate bandwidth to the client channel.
For FlexE logical interfaces on two ends of a link to communicate normally, perform the following tasks on both ends:
· Create FlexE-group interfaces with the same number.
· In the FlexE-group interface, configure the same client channel ID, and configure the same bandwidth allocation mode for the client channel.
· In the client channel, configure the same client ID.
Examples
# Configure client channel ID 2, and allocate bandwidth of 10 Gbps to the client channel.
<Sysname> system-view
[Sysname] interface flexe-group 1/0/1
[Sysname-FlexE-Group1/0/1] client-channel 2 bandwidth 10
[Sysname-FlexE-Group1/0/1-channel2]
Related commands
config-mode
fg-client
clock binding interface
Use clock binding interface to bind a FlexE physical interface to a FlexE logical interface hosting the clock service.
Use undo clock binding interface to restore the default.
Syntax
clock binding interface interface-type interface-number
undo clock binding interface
Default
A FlexE physical interface is not bound to a FlexE logical interface hosting the clock service.
Views
FlexE-50-G interface view
FlexE-50-100-G interface view
FlexE-100-G interface view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies a FlexE logical interface by its type and name.
Usage guidelines
FlexE physical interfaces cannot process protocol messages for the clock service. To deploy the clock service (such as PTP) on a FlexE physical interface, you must bind the FlexE physical interface to a FlexE logical interface that hosts the clock service.
For the clock service to correctly operate between two devices, set the same client ID for the interconnecting FlexE logical interfaces at both ends.
If the bound FlexE interface fails, the clock service will be affected. To resolve the issue, bind the FlexE physical interface to another FlexE logical interface. During the rebinding process, the clock service is unavailable.
Examples
# Bind FlexE physical interface FlexE-HundredGigE 1/0/1 to FlexE logical interface FlexE 1/0/1:1 hosting the clock service.
<Sysname> system-view
[Sysname] interface flexe-hundredgige 1/0/1
[Sysname-FlexE-HundredGig1/0/1] clock binding interface flexe 1/0/1:1
For the clock service to work, make sure the FlexE logical interface and the FlexE phy interface are in the same group.
config-mode
Use config-mode to set the bandwidth allocation mode for a FlexE logical interface.
Use undo config-mode to restore the default.
Syntax
config-mode { bandwidth | sub-timeslot }
undo config-mode
Views
FlexE-FG10G interface view
Client channel view
Default
The bandwidth allocation mode is bandwidth-based.
Predefined user roles
network-admin
Parameters
bandwidth: Specifies the fine granularity bandwidth-based mode, which allows you to flexibly configure bandwidth.
sub-timeslot: Specifies the sub-timeslot-based mode, which allows you to allocate bandwidth by specifying sub-timeslots at the granularity of 10 Mbps.
Usage guidelines
To meet the differentiated service carrying requirements for small bandwidth, high isolation, and high security in the 5G+vertical industry application scenarios and private line service scenarios, you must provide carrier channels with lower granularity. The fine granularity unit (FGU) technique refines the granularity from 5 Gbps to 10 Mbps to provide carrier channels with low costs, small granularity, and hardware isolation to meet the requirements of 5G+vertical industry application scenarios and government/organization private line scenarios.
In the current software version, you can configure bandwidth at the granularity of 10 Mbps for FlexE-FG10G interfaces and client channels. Use this command to configure the bandwidth allocation mode for a fine granularity FlexE logical interface.
You can configure bandwidth for a fine-granularity FlexE logical interface flexibly or through specifying sub-timeslots with the specified granularity.
· When the bandwidth allocation mode is bandwidth-based, execute the fg-client fg-client-id bandwidth bandwidth-value command to configure bandwidth flexibly for a FlexE-FG10G interface.
· When the bandwidth allocation mode is sub-timeslot-based, execute the fg-client fg-client-id timeslot timeslotlist command to specify sub-timeslots with the granularity of 10 Mbps for a FlexE-FG10G interface.
If you have used the fg-client fg-client-id bandwidth bandwidth-value or fg-client fg-client-id timeslot timeslotlist command to configure bandwidth for a FlexE-FG10G interface or client channel, you cannot modify the bandwidth allocation mode for the FlexE-FG10G interface.
Examples
# In FlexE-FG10G interface view, configure the bandwidth allocation mode as sub-timeslot-based for fine-granularity FlexE logical interfaces.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 2/2/1
[Sysname-Ten-GigabitEthernet2/2/1] port-type flexe-fg
[Sysname-FlexE-FG10G2/2/1] config-mode sub-timeslot
# In client channel view, configure the bandwidth allocation mode as sub-timeslot-based for fine-granularity FlexE logical interfaces.
<Sysname> system-view
[Sysname] interface flexe-group 1/0/1
[Sysname-Flexe-group1/0/1] client-channel 5 bandwidth 10
[Sysname-Flexe-group1/0/1-channel5] config-mode sub-timeslot
Related commands
dampening
Use dampening to enable the device to dampen an interface when the interface is flapping.
Use undo dampening to restore the default.
Syntax
dampening [ half-life reuse suppress max-suppress-time ]
undo dampening
Default
Interface dampening is disabled on Ethernet interfaces.
Views
FlexE-50G interface view
FlexE-50-100G interface view
FlexE-100G interface view
Predefined user roles
network-admin
Parameters
half-life: Specifies the amount of time after which a penalty is decreased, in the range of 1 to 120 seconds. The default value is 54 seconds.
reuse: Specifies the reuse threshold in the range of 200 to 20000. The default value is 750. The reuse threshold must be less than the suppression threshold.
suppress: Specifies the suppression threshold in the range of 200 to 20000. The default value is 2000.
max-suppress-time: Specifies the maximum amount of time the interface can be dampened, in the range of 1 to 255 seconds. The default value is 162 seconds (three times the half-life timer).
Usage guidelines
This command and the link-delay command are mutually exclusive on an interface.
This 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 higher layer protocols.
As a best practice, do not enable the dampening function on an interface with RRPP, MSTP, or Smart Link enabled.
After an interface in down state is dampened, the interface state displayed through the display interface command, MIB, or Web is always down.
Examples
# Enable interface dampening on FlexE-HundredGigE 1/0/1.
<Sysname> system-view
[Sysname] interface flexe-hundredgige 1/0/1
[Sysname-FlexE-HundredGig1/0/1] dampening
Related commands
display interface
link-delay
dcn enable
Use dcn enable to enable DCN for a FlexE physical interface.
Use undo dcn enable to restore the default.
Syntax
dcn enable
undo dcn enable
Default
DCN is not enabled for a FlexE physical interface.
Views
FlexE-50G interface view
FlexE-50-100G interface view
FlexE-100G interface view
Predefined user roles
network-admin
Usage guidelines
With DCN enabled on a FlexE physical interface, the device automatically creates a FlexE-DCN interface numbered the same as the FlexE physical interface. A FlexE-DCN interface is used to transmit DCN management information.
Examples
# Enable DCN on FlexE physical interface FlexE-50-100GigE 2/1/1.
<Sysname> system-view
[Sysname] interface flexe-50-100g 2/1/1
[Sysname-FlexE-50-100G2/1/1] dcn enable
default
Use default to restore the default settings for an interface.
Syntax
default
Views
FlexE group interface view
FlexE physical interface view
FlexE logical interface view
FlexE-DCN interface view
Predefined user roles
network-admin
Usage guidelines
CAUTION: The default command might interrupt ongoing network services. Make sure you are fully aware of the impacts of this command when you use it in a live network. |
This command 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 identify these commands, and use their undo forms or follow the command reference to restore their default settings. If your restoration attempt still fails, follow the error message instructions to solve the problem.
Examples
# Restore the default settings for FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] default
description
Use description to configure the description of an interface.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of an interface is the interface name plus Interface (for example, FlexE1/0/1:1 Interface).
Views
FlexE group interface view
FlexE physical interface view
FlexE logical interface view
FlexE-DCN interface view
Predefined user roles
network-admin
Parameters
text: Specifies the interface description, a case-sensitive string of 1 to 255 characters.
Examples
# Configure the description of FlexE logical interface FlexE 1/0/1:1 as lan-interface.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] description lan-interface
display interface
Use display interface to display interface information.
Syntax
display interface [ interface-type [ interface-number | interface-number.subnumber ] ] [ brief [ description | down ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number. The interface-number argument represents the interface number. The subnumber argument represents the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
brief: Displays brief interface information. If you do not specify this keyword, the command displays detailed interface information.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of each interface description.
down: Displays information about interfaces in down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
Examples
# Display information about Layer 2 FlexE logical interface FlexE 1/0/1:1.
<Sysname> display interface flexe 1/0/1
FlexE1/0/1:1
Current state: DOWN
Line protocol state: DOWN
Description: FlexE1/0/1:1 Interface
Maximum frame length: 9216
FlexE group: FlexE-Group1/0/1
Min-available bandwidth percent: 20
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
IP packet frame type: Ethernet II, hardware address: 3620-018b-0100
Flow-control is not enabled
Loopback is not set
Unknown-speed mode, unknown-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
PVID: 1
MDI type: Automdix
Port link-type: Access
Tagged VLANs: None
Untagged VLANs: 1
Last link flapping: Never
Last clearing of counters: Never
Current system time:2018-12-11 09:44:14
Last time when physical state changed to up:-
Last time when physical state changed to down:2018-12-11 09:11:34
Peak input rate: 0 bytes/sec, at 00-00-00 00:00:00
Peak output rate: 0 bytes/sec, at 00-00-00 00:00:00
Last 300 second input: 0 packets/sec 0 bytes/sec -%
Last 300 second output: 0 packets/sec 0 bytes/sec -%
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, 0 overruns, 0 aborts
0 ignored, 0 parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, 0 underruns, 0 buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, 0 no carrier
# Display information about Layer 3 FlexE interface FlexE 1/0/2:2.
<Sysname> display interface flexe 1/0/2:2
FlexE1/0/2:2
Current state: DOWN
Line protocol state: DOWN
Description: FlexE1/0/2:2 Interface
Bandwidth: 5000000 kbps
Flow-control is not enabled
Maximum transmission unit: 1500
FlexE group: FlexE-Group1/0/2
Min-available bandwidth percent: 20
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
Internet protocol processing: Disabled
IP packet frame type: Ethernet II, hardware address: 0000-0000-0000
IPv6 packet frame type: Ethernet II, hardware address: 0000-0000-0000
Last link flapping: Never
Last clearing of counters: Never
Current system time:2018-12-11 09:45:13
Last time when physical state changed to up:-
Last time when physical state changed to down:2018-12-11 09:45:09
Peak input rate: 0 bytes/sec, at 00-00-00 00:00:00
Peak output rate: 0 bytes/sec, at 00-00-00 00:00:00
Last 300 second input: 0 packets/sec 0 bytes/sec -%
Last 300 second output: 0 packets/sec 0 bytes/sec -%
Input (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, 0 overruns, 0 aborts
0 ignored, 0 parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, 0 underruns, 0 buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, 0 no carrier
# Display information about FlexE-group interface FlexE-Group 1/0/2.
<Sysname> display interface flexe-group 1/0/2
FlexE-Group1/0/2
Current state: DOWN
Description: FlexE-Group1/0/2 Interface
Physical: Unknown
Table 1 Command output
# Display information about FlexE physical interface FlexE-50-100G 1/0/1.
<Sysname> display interface flexe-50-100g 1/0/1
FlexE-50-100G1/0/1
Current state: DOWN
Line protocol state: DOWN
Description: FlexE-50-100G1/0/1 Interface
Bandwidth: 50000000 kbps
FlexE group: FlexE-Group1/0/1
Bound FlexE logical interface hosting clock service: FlexE1/0/1
Current system time:2017-10-27 15:10:03
Last time when physical state changed to up:-
Last time when physical state changed to down:2017-10-27 14:56:38
Table 2 Command output
Field |
Description |
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · DOWN—The data link layer protocol is down. |
Bandwidth |
Expected bandwidth of the interface. |
FlexE group |
FlexE group interface to which the FlexE physical interface belongs. |
Bound FlexE logical interface hosting clock service |
FlexE logical interface that bound a FlexE physical interface to host the clock service. |
Current system time |
Current system time in the YYYY/MM/DD HH:MM:SS format. If the time zone is configured, this field is in the YYYY/MM/DD HH:MM:SS UTC±HH:MM:SS format. |
Last time when physical state changed to up |
Last time when physical state of the interface changed to up. A hyphen (-) indicates that the physical state of the interface has not changed to up. |
Last time when physical state changed to down |
Last time when physical state of the interface changed to down. A hyphen (-) indicates that the physical state of the interface has not changed to down. |
# Display information about interface FlexE-DCN 1/0/1.
<Sysname> display interface flexe-dcn 1/0/1
FlexE-DCN 1/0/1
Current state: Administratively DOWN
Line protocol state: DOWN
Description: FlexE-DCN1/0/1 Interface
Maximum transmission unit: 1500
Input (total): 0 packets, 0 bytes
Output (total): 0 packets, 0 bytes
Table 3 Command output
Field |
Description |
Current state |
Physical link state of the interface: · Administratively DOWN—The interface has been shut down by using the shutdown command. · DOWN—The interface is administratively up, but its physical state is down (possibly because no physical link exists or the link has failed). · DOWN (Link-Aggregation interface down)—The aggregate interface to which the interface belongs has been shut down by using the shutdown command. · DOWN (Tunnel-Bundle administratively down)—The tunnel bundle interface to which the interface belongs has been shut down by using the shutdown command. · ETH-rddc Shutdown—The interface has been shut down by the Reth module. · IRF-link-down—The interface has been shut down by IRF. This state occurs when the IRF member device that contains the interface is detected to have lost the connectivity of all its IRF links in the MDC. · mac-address moving down—The interface has been shut down by the MAC address move suppression feature. · MAD ShutDown—The interface has been shut down by IRF MAD. This state occurs if the interface is on an IRF fabric placed in Recovery state after an IRF split. · Storm-Constrain—The interface has been shut down because the storm control feature detected that unknown unicast traffic, multicast traffic, or broadcast traffic exceeded the upper threshold. · STP DOWN—The interface has been shut down by the BPDU guard feature. · UP—The interface is both administratively and physically up. |
Line protocol state |
Data link layer state of the interface. The state is determined through automatic parameter negotiation at the data link layer. · UP—The data link layer protocol is up. · UP (spoofing)—The data link layer protocol is up, but the link is an on-demand link or does not exist. This attribute is typical of null interfaces and loopback interfaces. · DOWN—The data link layer protocol is down. · DOWN (protocols)—The data link layer has been shut down by protocols included in the parentheses. Available protocols include: ¡ DLDP—Shuts down the data link layer when it detects that the link is unidirectional. ¡ OAM—Shuts down the data link layer when it detects a remote link failure. ¡ LAGG—Shuts down the data link layer when it detects that the aggregate interface does not have Selected ports. ¡ BFD—Shuts down the data link layer when it detects a link failure. ¡ MACSEC—Shuts down the data link layer when it fails to negotiate the encryption parameters. ¡ VBP—Shuts down the data link layer because Layer 2 forwarding is configured. |
Maximum transmission unit |
MTU of the interface. |
Input(total): 0 packets, 0 bytes |
Inbound traffic statistics (in packets and bytes) for the interface. All inbound normal packets, abnormal packets, and normal pause frames were counted. A hyphen (-) indicates that the statistical item is not supported. |
Output(total): 0 packets, 0 bytes |
Outbound traffic statistics (in packets and bytes) for the interface. All outbound normal packets, abnormal packets, and normal pause frames were counted. A hyphen (-) indicates that the statistical item is not supported. |
# Display brief information about all interfaces.
<Sysname> display interface brief
Brief information on interfaces in route mode:
Link: ADM – administratively down; Stby – standby
Protocol: (s) – spoofing
Interface Link Protocol Primary IP Description
FlexE-50G1/0/1 DOWN DOWN --
FlexE-100G1/0/1 DOWN DOWN --
FlexE-50-100G1/0/1 DOWN DOWN --
FlexE-Group1/0/1 DOWN -- --
50-100GE1/0/1 DOWN DOWN --
FlexE-DCN1/0/1 DOWN DOWN --
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Speed: (a) - auto
Duplex: (a)/A - auto; H - half; F - full
Type: A - access; T - trunk; H - hybrid
Interface Link Speed Duplex Type PVID Description
FlexE1/0/1:10 DOWN auto A A 1
# Display brief information about FlexE 1/0/2:2, including the complete description of the interface.
<Sysname> display interface flexe 1/0/2 brief description
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Speed: (a) - auto
Duplex: (a)/A - auto; H - half; F - full
Type: A - access; T - trunk; H - hybrid
Interface Link Speed Duplex Type PVID Description
FlexE1/0/2: 2 UP 50G F A 1 aaaaaaaaaaaaaaaa
# Display information about interfaces in DOWN state and the causes.
<Sysname> display interface brief down
Brief information on interfaces in route mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
FlexE-50G1/0/1 DOWN Not connected
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
FlexE1/0/3:3 DOWN Not connected
Table 4 Command output
Field |
Description |
Brief information on interfaces in route mode: |
Brief information about Layer 3 interfaces. |
Interface |
Interface name. |
Link |
Physical link state of the interface: · UP—The interface is physically up. · DOWN—The interface is physically down. · ADM—The interface has been shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · Stby—The interface is a backup interface in standby state. To see the primary interface, use the display interface-backup state command. |
Protocol |
Data link layer protocol state of the interface: · UP—The data link layer protocol of the interface is up. · DOWN—The data link layer protocol of the interface is down. · UP(s)—The data link layer protocol of the interface is up, but the link is an on-demand link or does not exist. The (s) attribute represents the spoofing flag. This value is typical of null interfaces and loopback interfaces. This field displays two hyphens (--) if the device does not support displays the data link layer protocol status of the interface. |
Primary IP |
Primary IP address of the interface. This field displays two hyphens (--) if the interface does not have an IP address. |
Description |
Description of the interface. |
Brief information of interfaces in bridge mode: |
Brief information about Layer 2 interfaces. |
Speed |
Speed of the interface, in bps. This field displays the (a) flag next to the speed if the speed is automatically negotiated. This field displays auto if the interface is configured to autonegotiate its speed but the autonegotiation has not started. |
Duplex |
Duplex mode of the interface: · A—Autonegotiation. The interface is configured to autonegotiate its duplex mode but the autonegotiation has not started. · F—Full duplex. · F(a)—Autonegotiated full duplex. · H—Half duplex. · H(a)—Autonegotiated half duplex. |
Type |
Link type of the interface: · A—Access. · H—Hybrid. · T—Trunk. |
PVID |
Port VLAN ID. |
Cause |
Cause for the physical link state of an interface to be DOWN: · Administratively—The interface has been manually shut down by using the shutdown command. To restore the physical state of the interface, use the undo shutdown command. · DOWN ( Link-Aggregation interface down )—The interface is a member port of an aggregate interface, and the aggregate interface is down. · DOWN (Loopback detection down)—The loopback detection module has detected loops. · DOWN ( Monitor-Link uplink down )—The monitor link module has detected that the uplink is down. · IRF-link-down—The IRF member device that contains the interface has lost the connectivity of all its IRF links in the MDC. · MAD ShutDown—The interface is on an IRF fabric placed by IRF MAD in Recovery state after an IRF split. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). · Storm-Constrain—The storm control feature has detected that unknown unicast traffic, multicast traffic, or broadcast traffic exceeded the upper threshold. · STP DOWN—The interface has been shut down by the BPDU guard feature. · Port Security Disabled—The interface has been shut down by the intrusion detection mechanism because the interface received illegal packets. · Standby—The interface is a backup interface in standby state. |
Related commands
reset counters interface
display this interface
Use display this interface to display the operating status and information of an interface.
Syntax
display this interface
Views
FlexE logical interface view
Predefined user roles
network-admin
Usage guidelines
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.
Related commands
display interface
flexe config-mode
Use flexe config-mode to set the bandwidth configuration mode of FlexE logical interfaces.
Use undo flexe config-mode to restore the default.
Syntax
flexe config-mode slot slot-number subslot subslot-number { bandwidth | timeslot }
undo flexe config-mode slot slot-number subslot subslot-number
Views
System view
Default
The bandwidth mode is used. You can flexibly set the bandwidth of FlexE logical interfaces.
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number.
subslot subslot-number: Specifies a subcard by its slot number.
bandwidth: Specifies the bandwidth mode as the bandwidth configuration mode of FlexE logical interfaces. In this mode, you can flexibly set the bandwidth of a FlexE logical interface.
timeslot: Specifies the timeslot mode as the bandwidth configuration mode for FlexE logical interfaces. In this mode, you can set the bandwidth of a FlexE logical interface by binding timeslots with the specified timeslot granularity of a FlexE physical interface to it.
Usage guidelines
You can set the bandwidth configuration mode for FlexE logical interfaces to bandwidth mode or timeslot mode.
· 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. In this mode, you can set different bandwidth for FlexE logical interfaces at both ends.
· 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. In this mode, you must bind the timeslots of the same FlexE physical interfaces to FlexE logical interface at both ends. The timeslots of the FlexE physical interface bound to the FlexE logical interfaces at both end can be different.
If you already set the bandwidth of a FlexE logical interface by using the client command, you cannot change the bandwidth configuration mode by using this command.
Examples
# Set the bandwidth configuration mode to timeslot mode for FlexE logical interfaces.
<Sysname> system-view
[Sysname] flexe config-mode slot 1 subslot 1 timeslot
Related commands
client
flexe min-bandwidth-percent
Use flexe min-bandwidth-percent to set the minimum available bandwidth percentage of a FlexE logical interface.
Use undo flexe min-bandwidth-percent to restore the default.
Syntax
flexe min-bandwidth-percent percent
undo flexe min-bandwidth-percent
Default
The minimum available bandwidth percentage is 0% for a FlexE logical interface.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
percent: Specifies the minimum available bandwidth percentage in the range of 1% to 100%.
Usage guidelines
If the available bandwidth percentage of the interface drops below the minimum available bandwidth percentage, the interface goes down.
If the available bandwidth percentage of the interface reaches or exceeds the minimum available bandwidth percentage, the interface comes up.
To display the minimum available bandwidth percentage of a FlexE logical interface, use the display interface command.
Examples
# Set the minimum available bandwidth percentage to 25% for FlexE logical interface FlexE 1/0/1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1
[Sysname-FlexE1/0/1] flexe min-bandwidth-percent 25
Related commands
display interface
flexe sub-time-slot granula
Use flexe sub-time-slot granula to set the sub-timeslot granularity.
Use undo flexe sub-time-slot granula to restore the default.
Syntax
flexe sub-time-slot granula slot slot-number subslot subslot-number { 1 | 1.25 }
undo flexe sub-time-slot granula slot slot-number subslot subslot-number
Default
The sub-timeslot granularity is 5 Gbps.
Views
System view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays entries on the active MPU.
subslot subslot-number: Specifies a subcard by its slot number.
1: Specifies a sub-timeslot granularity of 1 Gbps.
1.25: Specifies a sub-timeslot granularity of 1.25 Gbps.
Usage guidelines
You must perform this task before setting a bandwidth less than 5 Gbps to a FlexE logical interface. Plan the sub-timeslot granularity as needed.
· If the sub-timeslot granularity is 5 Gbps, the bandwidth for a FlexE logical interface can be a multiple of 5 Gbps, for example, 5 Gbps, 10 Gbps, 15 Gbps, and so on.
· If the sub-timeslot granularity is 1 Gbps, the bandwidth for a FlexE logical interface can be 1 Gbps, 2 Gbps, 3 Gbps, 4 Gbps, 5 Gbps, or a multiple of 5 Gbps.
· If the sub-timeslot granularity is 1.25 Gbps, the bandwidth for a FlexE logical interface can be 1.25 Gbps, 2.5 Gbps, 3.75 Gbps, 5 Gbps, or a multiple of 5 Gbps.
If a FlexE logical interface on an interface module has been set with the bandwidth by using the flexe-group bandwidth command, you cannot modify the sub-timeslot granularity on the interface module.
Examples
# Set the sub-timeslot granularity to 1 Gbps on an interface module.
<Sysname> system-view
[Sysname] flexe sub-time-slot granula slot 1 subslot 0 1
Related commands
flexe-group bandwidth
flow-control
Use flow-control to enable TxRx-mode generic flow control on a FlexE logical interface.
Use undo flow-control to disable TxRx-mode generic flow control on a FlexE logical interface.
Syntax
flow-control
undo flow-control
Default
TxRx-mode generic flow control is disabled on a FlexE logical interface.
Views
FlexE logical interface view
Predefined user roles
network-admin
Usage guidelines
With TxRx-mode generic flow control configured, a FlexE logical interface can both send and receive flow control frames:
· When congested, the interface sends a flow control frame to its peer.
· Upon receiving a flow control frame from the peer, the interface suspends sending packets.
To implement flow control on a link, enable generic flow control at both ends of the link.
Examples
# Enable TxRx-mode generic flow control on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] flow-control
flow-control receive enable
Use flow-control receive enable to enable Rx-mode generic flow control on a FlexE logical interface.
Use undo flow-control to disable Rx-mode generic flow control on a FlexE logical interface.
Syntax
flow-control receive enable
undo flow-control
Default
Rx-mode generic flow control is disabled on a FlexE logical interface.
Views
FlexE logical interface view
Predefined user roles
network-admin
Usage guidelines
With Rx-mode flow control enabled, a FlexE logical interface can receive but cannot send flow control frames.
· When the interface receives a flow control frame from its peer, it suspends sending packets to the peer.
· When traffic congestion occurs on the interface, it cannot send flow control frames to the 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. To enable both ends of the link to handle traffic congestion, configure the flow-control command at both ends.
Examples
# Enable Rx-mode generic flow control on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] flow-control receive enable
Related commands
flow-control
flow-interval
Use flow-interval to set the statistics polling interval on a FlexE logical interface.
Use undo flow-interval to restore the default.
Syntax
flow-interval interval
undo flow-interval
Default
The default statistics polling interval varies by device model.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
interval: Specifies the statistics polling interval in seconds. The interval is in the range of 1 to 300.
Usage guidelines
After you modify the statistics polling interval on a FlexE logical interface, the collected statistics are inaccurate until two intervals after the modification. To view the accurate statistics, see the Last interval second input and Last interval second output fields in the output from the display interface command.
Examples
# Set the statistics polling interval to 100 seconds on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] flow-interval 100
Related commands
display interface
fg-client
Use fg-client to configure a client ID, and create a FlexE logical interface.
Use undo fg-client to restore the default.
Syntax
fg-client fg-client-id { bandwidth bandwidth-value | timeslot timeslot-list }
undo fg-client fg-client-id
Default
No FlexE logical interfaces exist.
Views
FlexE-FG10G interface view
Client channel view
Predefined user roles
network-admin
Parameters
fg-client-id: Specifies an FG client ID (FlexE-FG10G logical interface number) on a FlexE logical interface. The value range for this argument varies by device model.
bandwidth bandwidth-value: Directly specifies bandwidth for a FlexE logical interface. The bandwidth-value argument specifies bandwidth for a FlexE logical interface. The value range varies by the bandwidth allocated to the client channel. The bandwidth is in the step of 10 in Mbps.
timeslot timeslot-list: Specifies bandwidth for a FlexE logical interface by specifying sub-timeslots. The timeslot-list argument specifies a sub-timeslot ID list, for example, 1,3-5. Use a hyphen (-) to specify a sub-timeslot ID range, and separate multiple sub-timeslot IDs or ranges by using commas (,). A sub-timeslot ID list can contain up to 24 characters. Only full data configuration is supported. The value range for this argument varies by the bandwidth allocated to the client channel. A sub-timeslot represents bandwidth of 10 Mbps.
Usage guidelines
When you use this command to configure a FG client ID, the system will automatically create a FlexE logical interface with the same number. For example, if you configure FG client ID 10 on FlexE-FG10G 2/2/1, the system will automatically create FlexE logical interface FlexE2/2/1/0:10.
You can also use this command to configure the bandwidth for a FlexE logical interface. You can configure bandwidth for a FlexE logical interface flexibly or through specifying sub-timeslots with the specified granularity.
· When the config-mode bandwidth command is used to configure the bandwidth allocation mode as bandwidth-based, you can only execute the fg-client fg-client-id bandwidth command to configure bandwidth flexibly for a FlexE logical interface.
· When the config-mode sub-timeslot command is used to configure the bandwidth allocation mode as sub-timeslot-based, you can only execute the fg-client fg-client-id timeslot timeslot-list command to specify sub-timeslots for a FlexE logical interface. The bandwidth of the FlexE logical interface is the number of sub-timeslots multiplied by the sub-timeslot granularity.
For FlexE-FG10G logical interfaces on two ends of a link to communicate normally, perform the following tasks on both ends:
· For PHY-level fine granularity slices, configure the same FG client ID on the FlexE-FG10G interfaces.
· For FlexE-level fine granularity slices, perform the following tasks:
¡ Create FlexE-group interfaces with the same number.
¡ In the FlexE-group interface, configure the same client channel ID, and configure the same bandwidth allocation mode for the client channel.
¡ In the client channel, configure the same FG client ID.
Examples
# On a PHY-level fine granularity slice, configure FG client ID 10, create FlexE-FG10G logical interface FlexE 2/2/1/0:10 with the same ID, and assign bandwidth of 50 Mbps to the interface.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 2/2/1
[Sysname-Ten-GigabitEthernet2/2/1] port-type flexe-fg
[Sysname-FlexE-FG10G2/2/1] config-mode bandwidth
[Sysname-FlexE-FG10G2/2/1] fg-client 10 bandwidth 50
# On a FlexE-level fine granularity slice, configure FG client ID 10, create FlexE-FG10G logical interface FlexE 2/2/1/0:10 with the same ID, and assign bandwidth of 50 Mbps to the interface.
<Sysname> system-view
[Sysname] interface flexe-group 1/0/1
[Sysname-Flexe-group2/2/1] client-channel 5 bandwidth 10
[Sysname-Flexe-group2/2/1-channel5] fg-client 10 bandwidth 50
Related commands
config-mode
ifmonitor crc-error
Use ifmonitor crc-error to set global CRC error packet alarm parameters.
Use undo ifmonitor crc-error to restore the default.
Syntax
ifmonitor crc-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor crc-error slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for CRC error packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for CRC error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for CRC error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for CRC error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming CRC error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming CRC error packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the CRC error packet alarm function enabled, when the number of incoming CRC 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 incoming CRC 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.
You can configure the CRC error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the CRC error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor crc-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for CRC error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor crc-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
ifmonitor giant
Use ifmonitor giant to configure global giant packet alarm parameters.
Use undo ifmonitor giant to restore the default.
Syntax
ifmonitor giant slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor giant slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for giant packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for giant packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for giant packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for giant packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming giant packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming giant packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the giant packet alarm function enabled, when the number of incoming giant 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 incoming giant 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.
You can configure the giant packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for giant packet alarms.
<Sysname> system-view
[Sysname] ifmonitor giant high-threshold 5 low-threshold 4 interval 6
Related commands
port ifmonitor giant
snmp-agent trap enable ifmonitor
ifmonitor input-error
Use ifmonitor input-error to set global input error packet alarm parameters.
Use undo ifmonitor input-error to restore the default.
Syntax
ifmonitor input-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor input-error slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for input error packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for input error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of input error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of input error packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the input error packet alarm function enabled, when the number of input 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 input 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.
You can configure the input error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the input error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor input-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for input error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor input-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
ifmonitor input-usage
Use ifmonitor input-usage to set global inbound bandwidth usage alarm parameters.
Use undo ifmonitor input-usage to restore the default.
Syntax
ifmonitor input-usage slot slot-number high-threshold high-value low-threshold low-value
undo ifmonitor input-usage slot slot-number
Default
The upper threshold is 90% and the lower threshold is 80% for inbound bandwidth usage alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.
low-threshold low-value: Specifies the lower threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the inbound bandwidth usage alarm function enabled, when the inbound bandwidth usage on an interface in normal state within the statistic polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the inbound bandwidth usage on an interface in the alarm state within the statistic polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
(Device that does not support the flow-interval command.) The statistics polling interval is fixed at 5 minutes.
(Device that supports the flow-interval command.) The statistics polling interval can be set by using the flow-interval command.
You can configure the inbound bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor input-usage command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 95% and lower threshold to 80% for inbound bandwidth usage alarms.
<Sysname> system-view
[Sysname] ifmonitor input-usage high-threshold 95 low-threshold 80
Related commands
flow-interval
snmp-agent trap enable ifmonitor
ifmonitor output-error
Use ifmonitor output-error to set global output error packet alarm parameters.
Use undo ifmonitor output-error to restore the default.
Syntax
ifmonitor output-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor output-error slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for output error packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for output error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for output error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for output error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of output error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of output error packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the output error packet alarm function enabled, when the number of output 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 output 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.
You can configure the output error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the output error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor output-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for output error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor output-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
ifmonitor output-usage
Use ifmonitor output-usage to set global outbound bandwidth usage alarm parameters.
Use undo ifmonitor output-usage to restore the default.
Syntax
ifmonitor output-usage slot slot-number high-threshold high-value low-threshold low-value
undo ifmonitor output-usage slot slot-number
Default
The upper threshold is 90% and the lower threshold is 80% for outbound bandwidth usage alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.
low-threshold low-value: Specifies the lower threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the outbound bandwidth usage alarm function enabled, when the outbound bandwidth usage on an interface in normal state within the statistic polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the outbound bandwidth usage on an interface in the alarm state within the statistic polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
(Device that does not support the flow-interval command.) The statistics polling interval is fixed at 5 minutes.
(Device that supports the flow-interval command.) The statistics polling interval can be set by using the flow-interval command.
You can configure the outbound bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor output-usage command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 80% and lower threshold to 60% for outbound bandwidth usage alarms.
<Sysname> system-view
[Sysname] ifmonitor output-usage high-threshold 80 low-threshold 60
Related commands
flow-interval
snmp-agent trap enable ifmonitor
ifmonitor rx-pause
Use ifmonitor rx-pause to set global incoming pause frame alarm parameters.
Use undo ifmonitor rx-pause to restore the default.
Syntax
ifmonitor rx-pause slot slot-number high-threshold high-value low-threshold low-value interval interval
undo ifmonitor rx-pause slot slot-number
Default
The upper threshold is 500, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for incoming pause frame alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for incoming pause frame alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for incoming pause frame alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for incoming pause frame, in the range of 1 to 65535 seconds.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the incoming pause frame alarm function enabled, when the number of incoming pause frames 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 incoming pause frames 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.
You can configure the incoming pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor rx-pause command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 30, lower threshold to 20, and statistics collection and comparison interval to 4 seconds for incoming pause frame alarms.
<Sysname> system-view
[Sysname] ifmonitor rx-pause high-threshold 30 low-threshold 20 interval 4
Related commands
snmp-agent trap enable ifmonitor
ifmonitor runt
Use ifmonitor runt to configure global runt packet alarm parameters.
Use undo ifmonitor runt to restore the default.
Syntax
ifmonitor runt slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor runt slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for runt packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for runt packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for runt packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for runt packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming runt packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming runt packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the runt packet alarm function enabled, when the number of incoming runt 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 incoming runt 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.
You can configure the runt packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for runt packet alarms.
<Sysname> system-view
[Sysname] ifmonitor runt high-threshold 5 low-threshold 4 interval 6
Related commands
port ifmonitor runt
snmp-agent trap enable ifmonitor
ifmonitor sdh-b1-error
Use ifmonitor sdh-b1-error to set global SDH-B1 error packet alarm parameters.
Use undo ifmonitor sdh-b1-error to restore the default.
Syntax
ifmonitor sdh-b1-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor sdh-b1-error slot slot-number
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 packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH-B1 error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH-B1 error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH-B1 error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH-B1 error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming SDH-B1 error packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the SDH-B1 error packet alarm function enabled, when the number of SDH-B1 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 SDH-B1 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.
You can configure the SDH-B1 error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor sdh-b1-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 65, lower threshold to 25, and statistics collection and comparison interval to 20 seconds for SDH-B1 error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor sdh-b1-error high-threshold 65 low-threshold 25 interval 20
Related commands
snmp-agent trap enable ifmonitor
ifmonitor sdh-b2-error
Use ifmonitor sdh-b2-error to set global SDH-B2 error packet alarm parameters.
Use undo ifmonitor sdh-b2-error to restore the default.
Syntax
ifmonitor sdh-b2-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor sdh-b2-error slot slot-number
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 packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH-B2 error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH-B2 error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH-B2 error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH-B2 error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming SDH-B2 error packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the SDH-B2 error packet alarm function enabled, when the number of SDH-B2 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 SDH-B2 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.
You can configure the SDH-B2 error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor sdh-b2-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 6, lower threshold to 5, and statistics collection and comparison interval to 2 seconds for SDH-B2 error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor sdh-b2-error high-threshold 6 low-threshold 5 interval 2
Related commands
snmp-agent trap enable ifmonitor
ifmonitor sdh-error
Use ifmonitor sdh-error to set global SDH error packet alarm parameters.
Use undo ifmonitor sdh-error to restore the default.
Syntax
ifmonitor sdh-error slot slot-number high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo ifmonitor sdh-error slot slot-number
Default
The upper threshold is 1000, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for SDH error packet alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming SDH error packets exceeds the upper threshold on the interface.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the SDH error packet alarm function enabled, when the number of SDH 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 SDH 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.
You can configure the SDH error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor sdh-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Globally set the upper threshold to 35, lower threshold to 20, and statistics collection and comparison interval to 8 seconds for SDH error packet alarms.
<Sysname> system-view
[Sysname] ifmonitor sdh-error high-threshold 35 low-threshold 20 interval 8
Related commands
snmp-agent trap enable ifmonitor
ifmonitor tx-pause
Use ifmonitor tx-pause to set global outgoing pause frame alarm parameters.
Use undo ifmonitor tx-pause to restore the default.
Syntax
ifmonitor tx-pause slot slot-number high-threshold high-value low-threshold low-value interval interval
undo ifmonitor tx-pause slot slot-number
Default
The upper threshold is 500, the lower threshold is 100, and the statistics collection and comparison interval is 10 seconds for outgoing pause frame alarms.
Views
System view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for outgoing pause frame alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for outgoing pause frame alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for outgoing pause frame, in the range of 1 to 65535 seconds.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
With the outgoing pause frame alarm function enabled, when the number of outgoing pause frames 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 outgoing pause frames 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.
You can configure the outgoing pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the outgoing pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor tx-pause command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 20, lower threshold to 10, and statistics collection and comparison interval to 5 seconds for outgoing pause frame alarms.
<Sysname> system-view
[Sysname] ifmonitor tx-pause high-threshold 20 low-threshold 10 interval 5
Related commands
snmp-agent trap enable ifmonitor
interface
Use interface to enter the view of a FlexE physical interface.
Syntax
interface interface-type interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-type: Specifies the interface type of a FlexE physical interface.
interface-number: Specifies the interface number of the FlexE physical interface.
Examples
# Enter the view of FlexE-50-100G.
<Sysname> system-view
[Sysname] interface flexe-50-100g 1/0/1
[Sysname-FlexE-50-100G1/0/1]
interface flexe
Use interface flexe to enter the view of an existing FlexE logical interface, create a subinterface and enter its view, or enter the view of an existing subinterface.
Syntax
interface flexe { interface-number | interface-number.subnumber }
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies the interface number of a FlexE logical interface, which consists of the interface number and client ID of the Flex-group interface to which the FlexE logical interface belongs.
interface-number.subnumber: Specifies a subinterface number. The interface-number argument is an interface number. The subnumber argument is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
Usage guidelines
To create a FlexE logical interface, use the client command.
Examples
# Enter the view of FlexE logical interface FlexE1/0/1:10.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:10
[Sysname-FlexE1/0/1:10]
Related commands
client
interface flexe-dcn
Use interface flexe-dcn to enter FlexE-DCN interface view.
Syntax
interface flexe-dcn interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies a FlexE-DCN interface by its number.
Usage guidelines
In FlexE-DCN interface view, you can configure the following LLDP features to implement DCN:
· LLDP operating mode.
· LLDP function.
· Configuring the interface to generate ARP or ND entries after receiving LLDP frames carrying the management address TLVs.
· Advertisable TLVs on the interface.
For more information about LLDP, see LLDP in Layer 2—Ethernet Switching Configuration Guide.
Examples
# Enter the view of interface FlexE-DCN 1/0/1.
<Sysname> system-view
[Sysname] interface flexe-dcn 1/0/1
[Sysname-FlexE-DCN1/0/1]
interface flexe-group
Use interface flexe-group to create a FlexE group interface and enter its view or enter the view of an existing FlexE group interface.
Use undo interface flexe-group to remove a FlexE group interface.
Syntax
interface flexe-group interface-number
undo interface flexe-group interface-number
Views
System view
Predefined user roles
network-admin
Parameters
interface-number: Specifies the interface number of the FlexE group interface. The last tier in the interface number represents the group number of the FlexE group interface.
Usage guidelines
After you create a FlexE group interface, you can add multiple FlexE physical interfaces to the FlexE group interface and create FlexE logical interfaces in the FlexE group interface as needed. Then, you can flexibly assign the total bandwidths of the FlexE physical interfaces to FlexE logical interfaces according to the bandwidth requirements of services.
The number of FlexE group interface must be equal to or smaller than the number of FlexE physical interfaces on the subslot.
You can delete a FlexE group interface only if the FlexE group interface does not have any FlexE physical or logical interfaces.
Examples
# Create FlexE group interface FlexE-Group 1/0/1 and enter its view.
<Sysname> system-view
[Sysname] interface flexe-group 1/0/1
[Sysname-FlexE-Group1/0/1]
Related commands
bind interface
client
jumboframe enable
Use jumboframe enable to allow jumbo frames within the specified length to pass through.
Use undo jumboframe enable to prevent jumbo frames from passing through.
Use undo jumboframe enable size to restore the default.
Syntax
jumboframe enable [ size ]
undo jumboframe enable [ size ]
Default
The device allows jumbo frames within a specific length to pass through. The length of jumbo frames that are allowed to pass through varies by device model.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
size: Specifies the maximum length (in bytes) of Ethernet frames that are allowed to pass through. The value range for this argument varies by device model.
Usage guidelines
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Allow jumbo frames to pass through FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] jumboframe enable
link-delay
Use link-delay to set the physical state change suppression interval on a FlexE interface.
Use undo link-delay to restore the default.
Syntax
link-delay { down | up } [ msec ] delay-time
undo link-delay { down | up }
Default
Each time the physical link of a FlexE interface goes up or comes down, the system immediately reports the change to the CPU.
Views
FlexE physical interface view
FlexE logical interface view
Predefined user roles
network-admin
Parameters
down: Suppresses link-down events.
up: Suppresses link-up events.
msec: Enables the physical state change suppression interval to be accurate to milliseconds. If you do not specify this keyword, the suppression interval is accurate to seconds.
delay-time: Specifies the physical state change suppression interval on the FlexE interface. A value of 0 means that physical state changes are immediately reported to the CPU and are not suppressed.
· If you do not specify the msec keyword, the value range for this argument varies by device model.
· If you specify the msec keyword, the value range is 0 to 10000 milliseconds, and the value must be a multiple of 100.
Usage guidelines
You can use this command 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.
On an interface, 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, the most recent configuration takes effect.
Examples
# Set the link-down event suppression interval to 8 seconds on FlexE logical interface FlexE 1/0/1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] link-delay down 8
# Set the link-up event suppression interval to 800 milliseconds on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] link-delay up msec 800 mode
loopback
CAUTION: After you enable loopback testing on a FlexE logical interface, the interface does not forward data traffic. |
Use loopback to enable loopback testing on a FlexE logical interface.
Use undo loopback to disable loopback testing on a FlexE logical interface.
Syntax
loopback { external | internal }}
undo loopback
Default
Loopback testing is disabled on a FlexE logical interface.
Views
FlexE physical interface view
FlexE logical interface view
Predefined user roles
network-admin
Parameters
external: Enables external loopback testing on the FlexE logical interface.
internal: Enables internal loopback testing on the FlexE logical interface.
Usage guidelines
After you enable loopback testing on a FlexE logical interface, the FlexE logical interface switches to full duplex mode. After you disable loopback testing, the FlexE logical interface restores to its duplex setting.
The shutdown and loopback commands are mutually exclusive.
Examples
# Enable internal loopback testing on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] loopback internal
mac-address
Use mac-address to set the MAC address of a FlexE logical interface.
Use undo mac-address to restore the default.
Syntax
mac-address mac-address
undo mac-address
Default
The default setting for this command varies by device model.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
mac-address: Specifies a MAC address in the format of H-H-H.
Examples
# Set the MAC address of FlexE 1/0/1:1 to 0001-0001-0001.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] mac-address 1-1-1
mtu
Use mtu to set the MTU of a FlexE interface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of a FlexE interface is 1500 bytes.
Views
FlexE logical interface view
FlexE-DCN interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MTU in bytes. The value range for this argument varies by interface type.
Usage guidelines
The MTU set by using this command or the ip mtu command takes effect only on packets that the interface delivers to the CPU, for example, packets originated from or destined for the interface. Set a reasonable MTU on the interface to avoid fragmentation.
If you configure both the mtu and ip mtu commands on the interface, the MTU set by using the command takes priority.
Examples
# Set the MTU to 1430 bytes for FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] mtu 1430
Related commands
ip mtu (Layer 3—IP Services Command Reference)
multicast-suppression
Use multicast-suppression to enable multicast storm suppression and set the multicast storm suppression threshold.
Use undo multicast-suppression to disable multicast storm suppression.
Syntax
multicast-suppression { ratio | pps max-pps | kbps max-kbps } [ unknown ]
undo multicast-suppression
Default
A FlexE logical interface does not suppress multicast traffic.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
ratio: Specifies the multicast suppression threshold as a percentage of the interface bandwidth. The value range for this argument (in percentage) is 0 to 100. A smaller value means that less multicast traffic is allowed to pass through.
pps max-pps: Specifies the maximum number of multicast packets that the FlexE logical interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.
kbps max-kbps: Specifies the maximum number of kilobits of multicast traffic that the FlexE logical interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.
unknown: Enables multicast storm suppression only on unknown packets. If you do not specify this keyword, packets suppressed by this feature depend on the device model.
Usage guidelines
The multicast storm suppression feature limits the size of multicast traffic to a threshold on an interface. When the multicast traffic on the interface exceeds this threshold, the system drops packets until the traffic drops below this threshold.
Both the storm-constrain command and the multicast-suppression command can suppress multicast storms on a port. The multicast-suppression command uses the chip to physically suppress multicast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress multicast traffic.
For the traffic suppression result to be determined, do not configure both the storm-constrain multicast command and the multicast-suppression command on an interface.
The configured suppression threshold value in pps or kbps might be converted into a multiple of a step supported by the chip. As a result, the effective suppression threshold might be different from the configured one. To determine the suppression threshold that takes effect, see the prompts on the device.
Examples
# Set the multicast storm suppression threshold to 10000 kbps on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] multicast-suppression kbps 10000
The actual value is 10048 on port FlexE1/0/1 currently.
The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.
Related commands
broadcast-suppression
unicast-suppression
port auto-power-down
Use port auto-power-down to enable auto power-down on a FlexE logical interface.
Use undo port auto-power-down to disable auto power-down on a FlexE logical interface.
Syntax
port auto-power-down
undo port auto-power-down
Default
Auto power-down is disabled on a FlexE logical interface.
Views
FlexE logical interface view
Predefined user roles
network-admin
Usage guidelines
When an interface with auto power-down enabled has been down for a specific period of time, both of the following events occur:
· The device automatically stops supplying power to the interface.
· The interface enters the power save mode.
The time period depends on the chip specifications and is not configurable.
When the interface comes up, both of the following events occur:
· The device automatically restores the power supply to the interface.
· The interface restores to its normal state.
Examples
# Enable auto power-down on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port auto-power-down
port fec mode
Use port fec mode to set the forward error correction (FEC) mode of an interface.
Use undo port fec mode to restore the default.
Syntax
port fec mode { auto | base-r | none | rs-fec }
undo port fec mode
Default
The default for this command varies by device model.
Views
50-100GE interface view
FlexE-50-100G interface view
FlexE-100G interface view
FlexE-FG100G interface view
Predefined user roles
network-admin
Parameters
auto: Autonegotiates the FEC mode or disables FEC according to the transceiver module type.
base-r: Specifies the BASE-R FEC mode. This keyword is not supported in 100-GE, 50-100-GE, FlexE-50-100GE, or FlexE-100G interface view.
none: Performs no FEC.
rs-fec: Specifies the RS-FEC mode.
Usage guidelines
The 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.
Make sure you set the same FEC mode for both interfaces of a link.
Examples
# Set the FEC mode of FlexE-100G 1/0/1 to autonegotiation.
<Sysname> system-view
[Sysname] interface flexe-100g 1/0/1
[Sysname-FlexE-100G1/0/1] port fec mode auto
port ifmonitor crc-error
Use port ifmonitor crc-error to set CRC error packet alarm parameters on a FlexE logical interface.
Use undo port ifmonitor crc-error to restore the default.
Syntax
port ifmonitor crc-error [ ratio ] high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor crc-error
Default
A FlexE logical interface uses the global CRC error packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
ratio: Specifies the alarm thresholds in percentage. If you do not specify this keyword, you configure the alarm thresholds in absolute value.
high-threshold high-value: Specifies the upper threshold for CRC error packet alarms. If you specify the ratio keyword, the value range is 1 to 100. If you do not specify the ratio keyword, the value range is 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for CRC error packet alarms. If you specify the ratio keyword, the value range is 1 to 100. If you do not specify the ratio keyword, the value range is 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for CRC error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming CRC error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming CRC error packets exceeds the upper threshold on the interface.
Usage guidelines
With the CRC error packet alarm function enabled, when the number of incoming CRC 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 incoming CRC 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.
You can configure the CRC error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the CRC error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor crc-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for CRC error packet alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor crc-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor giant
Use port ifmonitor giant to configure giant packet alarm parameters for an interface.
Use undo port ifmonitor giant to restore the default.
Syntax
port ifmonitor giant high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor giant
Default
An interface uses the global giant packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for giant packet alarms, in the range of 1 to 4294967295.
low-threshold low-value: Specifies the lower threshold for giant packet alarms, in the range of 1 to 4294967295.
interval interval: Specifies the statistics collection and comparison interval for giant packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming giant packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming giant packets exceeds the upper threshold on the interface.
Usage guidelines
With the giant packet alarm function enabled, when the number of incoming giant 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 incoming giant 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.
You can configure the giant packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for giant packet alarms on FlexE1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor giant high-threshold 5 low-threshold 4 interval 6
Related commands
ifmonitor giant
snmp-agent trap enable ifmonitor
port ifmonitor input-error
Use port ifmonitor input-error to set input error packet alarm parameters on a FlexE logical interface.
Use undo port ifmonitor input-error to restore the default.
Syntax
port ifmonitor input-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor input-error
Default
A FlexE logical interface uses the global input error packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for input error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for input error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of input error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of input error packets exceeds the upper threshold on the interface.
Usage guidelines
With the input error packet alarm function enabled, when the number of input 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 input 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.
You can configure the input error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the input error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor input-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for input error packet alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor input-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor input-usage
Use port ifmonitor input-usage to set inbound bandwidth usage alarm parameters on a FlexE logical interface.
Use undo port ifmonitor input-usage to restore the default.
Syntax
port ifmonitor input-usage high-threshold high-value low-threshold low-value
undo port ifmonitor input-usage
Default
A FlexE interface uses the global inbound bandwidth usage alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.
low-threshold low-value: Specifies the lower threshold for inbound bandwidth usage alarms, in the range of 1% to 100%.
Usage guidelines
With the inbound bandwidth usage alarm function enabled, when the inbound bandwidth usage on an interface in normal state within the statistic polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the inbound bandwidth usage on an interface in the alarm state within the statistic polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
(Device that does not support the flow-interval command.) The statistics polling interval is fixed at 5 minutes.
(Device that supports the flow-interval command.) The statistics polling interval can be set by using the flow-interval command.
You can configure the inbound bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor input-usage command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 80% and lower threshold to 6% for inbound bandwidth usage alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor input-usage high-threshold 80 low-threshold 60
Related commands
flow-interval
snmp-agent trap enable ifmonitor
port ifmonitor output-error
Use port ifmonitor output-error to set output error packet alarm parameters on a FlexE logical interface.
Use undo port ifmonitor output-error to restore the default.
Syntax
port ifmonitor output-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor output-error
Default
A FlexE logical interface uses the global output error packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for output error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for output error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for output error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of output error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of output error packets exceeds the upper threshold on the interface.
Usage guidelines
With the output error packet alarm function enabled, when the number of output 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 output 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.
You can configure the output error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the output error packet alarm function is enabled by using the snmp-agent trap enable ifmonitor output-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5000, lower threshold to 400, and statistics collection and comparison interval to 6 seconds for output error packet alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor output-error high-threshold 5000 low-threshold 400 interval 6
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor output-usage
Use port ifmonitor output-usage to set outbound bandwidth usage alarm parameters on a FlexE logical interface.
Use undo port ifmonitor output-usage to restore the default.
Syntax
port ifmonitor output-usage high-threshold high-value low-threshold low-value
undo port ifmonitor output-usage
Default
A FlexE interface uses the global outbound bandwidth usage alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.
low-threshold low-value: Specifies the lower threshold for outbound bandwidth usage alarms, in the range of 1% to 100%.
Usage guidelines
With the outbound bandwidth usage alarm function enabled, when the outbound bandwidth usage on an interface in normal state within the statistic polling interval exceeds the upper threshold, the interface generates an upper threshold exceeding alarm and enters the alarm state. When the outbound bandwidth usage on an interface in the alarm state within the statistic polling interval drops below the lower threshold, the interface generates a recovery alarm and restores to the normal state.
(Device that does not support the flow-interval command.) The statistics polling interval is fixed at 5 minutes.
(Device that supports the flow-interval command.) The statistics polling interval can be set by using the flow-interval command.
You can configure the outbound bandwidth usage alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the inbound bandwidth usage alarm function is enabled by using the snmp-agent trap enable ifmonitor output-usage command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 9% and lower threshold to 7% for inbound bandwidth usage alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1]port ifmonitor output-usage high-threshold 9 low-threshold 7
Related commands
flow-interval
snmp-agent trap enable ifmonitor
port ifmonitor rx-pause
Use port ifmonitor rx-pause to set incoming pause frame alarm parameters on a FlexE logical interface.
Use undo port ifmonitor rx-pause to restore the default.
Syntax
port ifmonitor rx-pause high-threshold high-value low-threshold low-value interval interval
undo port ifmonitor rx-pause
Default
A FlexE logical interface uses the global incoming pause frame alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for incoming pause frame alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for incoming pause frame alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for incoming pause frame, in the range of 1 to 65535 seconds.
Usage guidelines
With the incoming pause frame alarm function enabled, when the number of incoming pause frames 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 incoming pause frames 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.
You can configure the incoming pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor rx-pause command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 90, lower threshold to 50, and statistics collection and comparison interval to 5 seconds for incoming pause frame alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor rx-pause high-threshold 90 low-threshold 50 interval 5
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor runt
Use port ifmonitor runt to configure runt packet alarm parameters for an interface.
Use undo port ifmonitor runt to restore the default.
Syntax
port ifmonitor runt high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor runt
Default
An interface uses the global runt packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for runt packet alarms, in the range of 1 to 4294967295.
low-threshold low-value: Specifies the lower threshold for runt packet alarms, in the range of 1 to 4294967295.
interval interval: Specifies the statistics collection and comparison interval for runt packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming runt packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming runt packets exceeds the upper threshold on the interface.
Usage guidelines
With the runt packet alarm function enabled, when the number of incoming runt 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 incoming runt 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.
You can configure the runt packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
When you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 5, lower threshold to 4, and statistics collection and comparison interval to 6 seconds for runt packet alarms on FlexE1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor runt high-threshold 5 low-threshold 4 interval 6
Related commands
ifmonitor runt
snmp-agent trap enable ifmonitor
port ifmonitor sdh-b1-error
Use port ifmonitor sdh-b1-error to set SDH-B1 error packet alarm parameters on a FlexE logical interface.
Use undo port ifmonitor sdh-b1-error to restore the default.
Syntax
port ifmonitor sdh-b1-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor sdh-b1-error
Default
A FlexE logical interface uses the global SDH-B1 error packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH-B1 error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH-B1 error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH-B1 error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH-B1 error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming SDH-B1 error packets exceeds the upper threshold on the interface.
Usage guidelines
With the SDH-B1 error packet alarm function enabled, when the number of incoming SDH-B1 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 incoming SDH-B1 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.
You can configure the SDH-B1 error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor sdh-b1-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 20, lower threshold to 10, and statistics collection and comparison interval to 10 seconds for SDH-B1 error packet alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor sdh-b1-error high-threshold 20 low-threshold 10 interval 10
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor sdh-b2-error
Use port ifmonitor sdh-b2-error to set SDH-B2 error packet alarm parameters on a FlexE logical interface.
Use undo port ifmonitor sdh-b2-error to restore the default.
Syntax
port ifmonitor sdh-b2-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor sdh-b2-error
Default
A FlexE logical interface uses the global SDH-B2 error packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH-B2 error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH-B2 error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH-B2 error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH-B2 error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming SDH-B2 error packets exceeds the upper threshold on the interface.
Usage guidelines
With the SDH-B2 error packet alarm function enabled, when the number of incoming SDH-B2 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 incoming SDH-B2 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.
You can configure the SDH-B2 error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor sdh-b2-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 10, lower threshold to 8, and statistics collection and comparison interval to 3 seconds for SDH-B2 error packet alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor sdh-b2-error high-threshold 10 low-threshold 8 interval 3
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor sdh-error
Use port ifmonitor sdh-error to set SDH error packet alarm parameters on a FlexE logical interface.
Use undo port ifmonitor sdh-error to restore the default.
Syntax
port ifmonitor sdh-error high-threshold high-value low-threshold low-value interval interval [ shutdown ]
undo port ifmonitor sdh-error
Default
A FlexE logical interface uses the global SDH error packet alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for SDH error packet alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for SDH error packet alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for SDH error packets, in the range of 1 to 65535 seconds.
shutdown: Shuts down an interface when the number of incoming SDH error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of incoming SDH error packets exceeds the upper threshold on the interface.
Usage guidelines
With the SDH error packet alarm function enabled, when the number of incoming SDH 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 incoming SDH 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.
You can configure the SDH error packet alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the incoming pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor sdh-error command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 50, lower threshold to 30, and statistics collection and comparison interval to 10 seconds for SDH error packet alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor sdh-error high-threshold 50 low-threshold 30 interval 10
Related commands
snmp-agent trap enable ifmonitor
port ifmonitor tx-pause
Use port ifmonitor tx-pause to set outgoing pause frame alarm parameters on a FlexE logical interface.
Use undo port ifmonitor tx-pause to restore the default.
Syntax
port ifmonitor tx-pause high-threshold high-value low-threshold low-value interval interval
undo port ifmonitor tx-pause
Default
A FlexE logical interface uses the global outgoing pause frame alarm parameters.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
high-threshold high-value: Specifies the upper threshold for outgoing pause frame alarms, in the range of 1 to 4294967295 packets.
low-threshold low-value: Specifies the lower threshold for outgoing pause frame alarms, in the range of 1 to 4294967295 packets.
interval interval: Specifies the statistics collection and comparison interval for outgoing pause frames, in the range of 1 to 65535 seconds.
Usage guidelines
With the outgoing pause frame alarm function enabled, when the number of outgoing pause frames 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 outgoing pause frames 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.
You can configure the outgoing pause frame alarm parameters in system view and interface view.
· The configuration in system view takes effect on all interfaces. The configuration in interface view takes effect only on the current interface. (Devices that do not support the slot keyword.)
· The configuration in system view takes effect on all interfaces of the specified slot. The configuration in interface view takes effect only on the current interface. (Devices that support the slot keyword.)
· For an interface, the configuration in interface view takes priority, and the configuration in system view is used only when no configuration is made in interface view.
This command takes effect only when the outgoing pause frame alarm function is enabled by using the snmp-agent trap enable ifmonitor tx-pause command.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the upper threshold to 50, lower threshold to 40, and statistics collection and comparison interval to 8 seconds for outgoing pause frame alarms on FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port ifmonitor tx-pause high-threshold 50 low-threshold 40 interval 8
Related commands
snmp-agent trap enable ifmonitor
port link-mode
Use port link-mode to change the link mode of a FlexE logical interface.
Use undo port link-mode to restore the default.
Syntax
port link-mode { bridge | route }
undo port link-mode
Default
The default setting varies by device model.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
bridge: Specifies the Layer 2 mode.
route: Specifies the Layer 3 mode.
Usage guidelines
CAUTION: Changing the link mode of a FlexE logical interface also restores all commands (except shutdown) on the FlexE logical interface to their defaults in the new link mode. |
A FlexE logical interface can operate at one of the following 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.
Examples
# Configure FlexE 1/0/1:1 to operate in Layer 2 mode.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] port link-mode bridge
port-type
Use port-type flexe to change the type of an interface from Ethernet to FlexE.
Use port-type flexe-fg to change the type of an interface from Ethernet to fine granularity FlexE.
Use port-type ethernet to change the type of an interface from FlexE to Ethernet.
Syntax
In 50-GE/50-100GE/100GE interface view:
port-type flexe
In 10-GE interface view:
port-type flexe-fg
In FlexE-FG10G/FlexE-50G/FlexE-50-100G/FlexE-100G interface view:
port-type ethernet
Views
10-GE interface view
50-GE interface view
50-100GE interface view
100-GE interface view
FlexE-50-G interface view
FlexE-50-100G interface view
FlexE-100G interface view
FlexE-FG10G interface view
Predefined user roles
network-admin
Usage guidelines
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. |
The bandwidth of an interface in standard Ethernet mode is fixed, and the bandwidth of an interface in 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.
· To assign bandwidth at the granularity of 10 Mbps, execute the port-type flexe-fg command to switch the type of the interface from Ethernet to fine granularity FlexE.
If a FlexE physical interface has been added to a FlexE group interface and bandwidth has been assigned to a FlexE logical interface in the group, you cannot change the interface type.
Examples
# Change standard Ethernet interface FiftyGigE 1/0/1 to a FlexE interface.
<Sysname> system-view
[Sysname] interface fiftygige 1/0/1
[Sysname-FiftyGigE1/0/1] port-type flexe
The interface FiftyGigE1/0/1 will be deleted. Continue? [Y/N]:
# Change FlexE interface FlexE-50-100G 1/0/1 to a standard Ethernet interface.
<Sysname> system-view
[Sysname] interface flexe-50-100g 1/0/1
[Sysname-FlexE-50-100G1/0/1] port-type ethernet
The interfaces FlexE-50-100G1/0/1 and FlexE1/0/1 through FlexE1/0/3 will be deleted. Continue? [Y/N]:
# Change 10-GE interface Ten-GigabitEthernet 2/2/1 into fine granularity FlexE mode.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 2/2/1
[Sysname-Ten-GigabitEthernet2/2/1] port-type flexe-fg
The interface Ten-GigabitEthernet2/2/1 will be deleted. Continue? [Y/N]:
priority-flow-control
Use priority-flow-control to enable PFC on a FlexE logical interface.
Use undo priority-flow-control to disable PFC on a FlexE logical interface.
Syntax
priority-flow-control { auto | enable }
undo priority-flow-control
Default
PFC is disabled on a FlexE logical interface.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
auto: Specifies PFC in auto mode. In this mode, the local end automatically negotiates the PFC status with the remote end.
enable: Forcibly enables PFC.
Usage guidelines
The local device notifies the remote end 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 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 packets carrying the specified 802.1p priority, and the received packets cause congestion.
When congestion is eliminated, the local end notifies the remote end to continue to send packets carrying the specified 802.1p priority. In this way, the local device can forward packets carrying 802.1p priorities in the specified 802.1p priority list without packet drops.
Examples
# Enable PFC in auto mode on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] priority-flow-control auto
Related commands
display priority-flow-control
priority-flow-control no-drop dot1p
priority-flow-control no-drop dot1p
Use priority-flow-control no-drop dot1p to enable PFC for 802.1p priorities on a FlexE logical interface.
Use undo priority-flow-control no-drop dot1p to enable PFC for 802.1p priorities on a FlexE logical interface.
Syntax
priority-flow-control no-drop dot1p dot1p-list
undo priority-flow-control no-drop dot1p
Default
PFC is disabled for all 802.1p priorities on a FlexE logical interface.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
dot1p-list: Specifies an 802.1p priority (or dot1p priority) list to identify flows that are subject to PFC (for example: 1,3-5). A hyphen (-) connects two numeric values, which together indicate a continuous value range. Different values or value ranges are separated with commas (,). You can configure up to 16 characters for this argument.
Usage guidelines
The local device notifies the remote end 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 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 packets carrying the specified 802.1p priority, and the received packets cause congestion.
When congestion is eliminated, the local end notifies the remote end to continue to send packets carrying the specified 802.1p priority. In this way, the local device can forward packets carrying 802.1p priorities in the specified 802.1p priority list without packet drops. For more information about the 802.1p priority, see ACL and QoS Configuration Guide.
If you configure the flow control or flow-control receive enable command on a PFC-enabled device or interface, the following events occur:
· 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 device or interface only when PFC is disabled on it.
Examples
# Enable PFC in auto mode on FlexE logical interface FlexE 1/0/1:1, and enable PFC for 802.1p priority 5.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] priority-flow-control auto
[Sysname-FlexE1/0/1:1] priority-flow-control no-drop dot1p 5
Related commands
display priority-flow-control
flow-control
flow-control receive enable
priority-flow-control
shutdown
Use shutdown to shut down a FlexE interface.
Use undo shutdown to bring up a FlexE interface.
Syntax
shutdown
undo shutdown
Default
The default state of an interface varies by device model.
Views
FlexE physical interface view
FlexE logical interface view
Predefined user roles
network-admin
Usage guidelines
CAUTION: Executing the shutdown command on an interface will disconnect the link of the interface and interrupt communication. Use this command with caution. |
Some interface configurations might require an interface restart before taking effect.
The shutdown and loopback commands are mutually exclusive.
Examples
# Shut down and then bring up FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] shutdown
[Sysname-FlexE1/0/1:1] undo shutdown
snmp-agent trap enable ifmonitor
Use snmp-agent trap enable ifmonitor to enable interface alarm functions.
Use undo snmp-agent trap enable ifmonitor to disable interface alarm functions.
Syntax
snmp-agent trap enable ifmonitor [ crc-error | giant | input-error | input-usage | output-error | output-usage | rx-pause | runt | sdh-b1-error | sdh-b2-error | sdh-error | tx-pause ] *
undo snmp-agent trap enable ifmonitor [ crc-error | giant | input-error | input-usage | output-error | output-usage | rx-pause | runt | sdh-b1-error | sdh-b2-error | sdh-error | tx-pause ] *
Default
Interface alarm functions are enabled.
Views
System view
Predefined user roles
network-admin
Parameters
crc-error: Enables the CRC error packet alarm function.
giant: Enables the giant packet alarm function for interfaces.
input-error: Enables the input error packet alarm function.
input-usage: Enables the inbound bandwidth usage alarm function.
output-error: Enables the output error packet alarm function.
output-usage: Enables the outbound bandwidth usage alarm function.
rx-pause: Enables the incoming pause frame alarm function.
runt: Enables the runt packet alarm function for interfaces.
sdh-b1-error: Enables the SDH-B1 error packet alarm function.
sdh-b2-error: Enables the SDH-B2 error packet alarm function.
sdh-error: Enables the SDH error packet alarm function.
tx-pause: Enables the outgoing pause frame alarm function.
Examples
# Enable the CRC error packet alarm function.
<Sysname> system-view
[Sysname] snmp-agent trap enable ifmonitor crc-error
speed-mode
Use speed-mode to change the speed mode of an interface between 50 Gbps and 100 Gbps.
Use undo speed-mode to restore the default.
Syntax
speed-mode { 50ge | 100ge }
undo speed-mode
Default
An interface operates at a speed of 50 Gbps.
Views
50-100GE interface view
FlexE-50-100G interface view
Predefined user roles
network-admin
Parameters
50ge: Specifies the speed of 50 Gbps.
100ge: Specifies the speed of 100 Gbps.
Usage guidelines
Assume that an interface module has only two interfaces A and B and that A has a smaller interface number than B. When you change the speed mode of the interfaces, follow these restrictions:
· If both A and B operate at a speed of 50 Gbps, you can change only the speed mode of A to 100 Gbps. After the speed mode of A changes, B will be deleted.
· If you change the speed mode of A from 100 Gbps to 50 Gbps, B will be created and will operate at a speed of 50 Gbps.
· If A or B has been added to a FlexE group interface, you cannot directly change its speed mode. Before changing the speed mode, remove the interface from the FlexE group interface.
· If A operates at a speed of 50 Gbps and B has been added to a FlexE group interface, you cannot directly change the speed mode of A. Before changing the speed mode of A, you must remove B from the FlexE group interface.
To display the speed mode of an interface, use the display interface command.
Examples
# Configure Fifty-HundredGigE 1/0/1 to operate at a speed of 50 Gbps.
<Sysname> system-view
[Sysname] interface fifty-hundredgige 1/0/1
[Sysname-Fifty-HundredGigE1/0/1] speed-mode 50ge
Related commands
display interface
switch-mode
Use switch-mode to set the speed mode for a 50-100GE interface.
Use undo switch-mode to restore the default.
Syntax
switch-mode manual
undo switch-mode
Views
50-100GE interface view
Default
The speed of an interface is determined by the transceiver module installed.
Predefined user roles
network-admin
Parameters
manual: Sets the speed mode to manual for the 50-100GE interface.
Usage guidelines
Suppose two interfaces on an expansion interface card operate at 50 Gbps. After you execute the switch-mode manual mode on an interface, you can execute the speed-mode 100ge command to configure the interface to operate at 100 Gbps. At the same time, the other interface will be deleted. To view the interface changes, execute the display interface brief command.
If an interface on an expansion interface card is a FlexE interface operating at 100 Gbps and has been assigned to a FlexE group, you cannot configure the interface to operate at 50 Gbps. To do that, first remove it from the FlexE group.
After you execute this command on an interface, you must use the speed-mode command to manually specify a speed mode for the interface.
Examples
# Configure interface Fifty-HundredGigE 1/0/1 to operate in manual mode.
<Sysname> system-view
[Sysname] interface fifty-hundredgige 1/0/1
[Sysname-Fifty-HundredGigE1/0/1] switch-mode manual
Related commands
display interface
speed-mode
unicast-suppression
Use unicast-suppression to enable unknown unicast storm suppression and set the unknown unicast storm suppression threshold.
Use undo unicast-suppression to disable unknown unicast storm suppression.
Syntax
unicast-suppression { ratio | pps max-pps | kbps max-kbps }
undo unicast-suppression
Default
A FlexE logical interface does not suppress unknown unicast traffic.
Views
FlexE logical interface view
Predefined user roles
network-admin
Parameters
ratio: Specifies the unknown unicast suppression threshold as a percentage of the interface bandwidth. The value range for this argument (in percentage) is 0 to 100. A smaller value means that less unknown unicast traffic is allowed to pass through.
pps max-pps: Specifies the maximum number of unknown unicast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the interface bandwidth.
kbps max-kbps: Specifies the maximum number of kilobits of unknown unicast traffic that the FlexE logical interface can forward per second. The value range for this argument (in kbps) is 0 to the interface bandwidth.
Usage guidelines
The unknown unicast storm suppression feature limits the size of unknown unicast traffic to a threshold on an interface. When the unknown unicast traffic on the interface exceeds this threshold, the system discards packets until the unknown unicast traffic drops below this threshold.
Both the storm-constrain command and the unicast-suppression command can suppress unknown unicast storms on a port. The unicast-suppression command uses the chip to physically suppress unknown unicast traffic. It has less influence on the device performance than the storm-constrain command, which uses software to suppress unknown unicast traffic.
For the unknown unicast traffic suppression result to be determined, do not configure both the storm-constrain unicast command and the unicast-suppression command on an interface.
The configured suppression threshold value in pps or kbps might be converted into a multiple of a step supported by the chip. As a result, the effective suppression threshold might be different from the configured one. To determine the suppression threshold that takes effect, see the prompts on the device.
Examples
# Set the unknown unicast storm suppression threshold to 10000 kbps on FlexE logical interface FlexE 1/0/1:1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1
[Sysname-FlexE1/0/1:1] unicast-suppression kbps 10000
The actual value is 10048 on port FlexE1/0/1:1 currently.
The output shows that the value that takes effect is 10048 kbps (157 times of 64), because the chip only supports step 64.
Related commands
broadcast-suppression
multicast-suppression
traffic-statistic enable
Use traffic-statistic enable to enable packet statistics collection for an interface.
Use undo traffic-statistic enable to disable packet statistics collection for an interface.
Syntax
traffic-statistic enable
undo traffic-statistic enable
Default
Packet statistics collection is disabled for an interface.
Views
FlexE logical subinterface view
Predefined user roles
network-admin
Usage guidelines
You can use the display interface or display counters command to display the subinterface traffic statistics.
Examples
# Enable packet statistics collection for FlexE1/0/1:1.1.
<Sysname> system-view
[Sysname] interface flexe 1/0/1:1.1
[Sysname-FlexE1/0/1:1.1] traffic-statistic enable
Related commands
display counters
display interface