- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
02-Ethernet interface commands | 257.52 KB |
Contents
Common Ethernet interface commands
priority-flow-control no-drop dot1p
Layer 2 Ethernet interface commands
Layer 3 Ethernet interface or subinterface commands
EB cards have the "EB" suffix in their marks, such as LST1GP48LEB1. The similar is true for EC, EF, FC, and FG cards.
You cannot create Layer 3 Ethernet interfaces or subinterfaces, or Layer 3 aggregate interfaces or subinterfaces when the system is operating in standard mode. For more information about switch's operating modes, see Fundamentals Configuration Guide.
Common Ethernet interface commands
bandwidth
Use bandwidth to configure 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
Ethernet interface view, Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
bandwidth-value: Specifies the expected bandwidth in the range of 1 to 400000000 kbps.
Usage guidelines
The expected bandwidth of an interface affects the link costs in OSPF, OSPFv3, and IS-IS. For more information, see Layer 3—IP Routing Configuration Guide.
Examples
# Set the expected bandwidth of interface GigabitEthernet 3/0/1 to 1000 kbps.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] bandwidth 1000
# Set the expected bandwidth of subinterface GigabitEthernet 3/0/1.1 to 1000 kbps.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1.1
[Sysname-GigabitEthernet3/0/1.1] bandwidth 1000
Related commands
speed
default
Use default to restore the default settings for an Ethernet interface or subinterface.
Syntax
default
Views
Ethernet interface view, Ethernet subinterface view
Predefined user roles
network-admin
mdc-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 for reasons such as command dependencies and system restrictions. Use the display this command in interface view to identify these commands, and then 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 resolve the problem.
Examples
# Restore the default settings for interface GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] default
# Restore the default settings for subinterface GigabitEthernet 3/0/1.1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1.1
[Sysname-GigabitEthernet3/0/1.1] default
description
Use description to change 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, GigabitEthernet3/0/1 Interface).
Views
Ethernet interface view, Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
text: Specifies the interface description, a case-sensitive string of 1 to 255 characters.
Examples
# Change the description of interface GigabitEthernet 3/0/1 to lanswitch-interface.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] description lanswitch-interface
# Change the description of Ethernet subinterface GigabitEthernet 3/0/1.1 to l2-subinterface3/0/1.1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1.1
[Sysname-GigabitEthernet3/0/1.1] description l2-subinterface3/0/1.1
display counters
Use display counters to display interface traffic statistics.
Syntax
display counters { inbound | outbound } interface [ interface-type [ interface-number | interface-number.subnumber ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
inbound: Displays inbound traffic statistics.
outbound: Displays outbound traffic statistics.
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number, where interface-number is an interface number, and subnumber is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
Usage guidelines
This command displays traffic statistics within a statistics polling interval specified by the flow-interval command.
To clear the Ethernet interface traffic statistics, use the reset counters interface command. For more information, see "reset counters interface."
If you do not specify an interface type, this command displays traffic statistics for all interfaces that have traffic counters.
If you specify an interface type but do not specify an interface number or subinterface number, this command displays traffic statistics for all interfaces of the specified type.
If you specify an interface type and an interface number or subinterface number, this command displays traffic statistics of the specified interface or subinterface.
Examples
# Display inbound traffic statistics for all GigabitEthernet interfaces.
<Sysname> display counters inbound interface GigabitEthernet
Interface Total (pkts) Broadcast (pkts) Multicast (pkts) Err (pkts)
GE3/0/1 100 100 0 0
GE3/0/1 0 0 0 0
GE3/0/1 Overflow Overflow Overflow Overflow
GE3/0/1 0 0 0 0
Overflow: More than 14 digits (7 digits for column "Err").
--: Not supported.
Table 1 Command output
Field |
Description |
Interface |
Abbreviated interface name. |
Total (pkts) |
Total number of packets received or sent through the interface. |
Broadcast (pkts) |
Total number of broadcast packets received or sent through the interface. |
Multicast (pkts) |
Total number of multicast packets received or sent through the interface. |
Err (pkts) |
Total number of error packets received or sent through the interface. |
Overflow: More than 14 digits (7 digits for column "Err") |
The command displays Overflow if any of the following cases applies: · The data length of an Err field value is greater than 7 decimal digits. · The data length of a non-Err field value is greater than 14 decimal digits. |
--: Not supported |
The statistical item is not supported. |
Related commands
· flow-interval
· reset counters interface
display counters rate
Use display counters rate to display traffic rate statistics of interfaces in up state over the last statistics polling interval.
Syntax
display counters rate { inbound | outbound } interface [ interface-type [ interface-number | interface-number.subnumber ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
inbound: Displays inbound traffic rate statistics.
outbound: Displays outbound traffic rate statistics.
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number, where interface-number is an interface number, and subnumber is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
Usage guidelines
The statistics cover only interfaces in up state.
If you specify an interface type, this command displays traffic rate statistics for all up interfaces of the specified type over the last statistics polling interval.
If you do not specify an interface type, this command displays traffic rate statistics for all up interfaces that have traffic counters over the last statistics polling interval.
If you specify an interface which is always down over the last statistics polling interval, the system prompts that the interface does not support the command.
You can use the flow-interval command to set the statistics polling interval.
Examples
# Display the inbound traffic rate statistics for all GigabitEthernet interfaces.
<Sysname> display counters rate inbound interface gigabitethernet
Usage: Bandwidth utilization in percentage
Interface Usage Total (pps) Broadcast (pps) Multicast (pps)
GE3/0/1 0% 0 -- --
GE3/0/3 0% 0 -- --
GE3/0/6 0% 0 -- --
Overflow: More than 14 digits.
--: Not supported.
Table 2 Command output
Field |
Description |
Interface |
Abbreviated interface name. |
Usage |
Bandwidth usage. |
Total (pkts/sec) |
Average rate (in pps) of receiving or sending packets during the statistics polling interval. |
Broadcast (pkts/sec) |
Average rate (in pps) of receiving or sending broadcast packets during the statistics polling interval. |
Multicast (pkts/sec) |
Average rate (in pps) of receiving or sending multicast packets during the statistics polling interval. |
Overflow: more than 14 decimal digits |
The command displays Overflow if the data length of a statistical item is greater than 14 decimal digits. |
--: not supported |
The statistical item is not supported. |
Related commands
· flow-interval
· reset counters interface
display ethernet statistics
Use display ethernet statistics to display the Ethernet module statistics.
Syntax
In standalone mode:
display ethernet statistics slot slot-number
In IRF mode:
display ethernet statistics chassis chassis-number slot slot-number
Views
User view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
slot slot-number: Displays the Ethernet module statistics on the specified card. The slot-number argument represents the number of the slot that houses the card. (In standalone mode.)
chassis chassis-number slot slot-number: Displays the Ethernet module statistics on the specified card of the specified IRF member device. The chassis-number argument represents the ID of the IRF member device. The slot-number argument represents the number of the slot that houses the card. (In IRF mode.)
Examples
# (In standalone mode.) Display the Ethernet module statistics on slot 2.
<Sysname> display ethernet statistics slot 2
ETH receive packet statistics:
Totalnum : 10447 ETHIINum : 4459
SNAPNum : 0 RAWNum : 0
LLCNum : 0 UnknownNum : 0
ForwardNum : 4459 ARP : 0
MPLS : 0 ISIS : 0
ISIS2 : 0 IP : 0
IPV6 : 0
ETH receive error statistics:
NullPoint : 0 ErrIfindex : 0
ErrIfcb : 0 IfShut : 0
ErrAnalyse : 5988 ErrSrcMAC : 5988
ErrHdrLen : 0
ETH send packet statistics:
L3OutNum : 211 VLANOutNum : 0
FastOutNum : 155 L2OutNum : 0
ETH send error statistics:
MbufRelayNum : 0 NullMbuf : 0
ErrAdjFwd : 0 ErrPrepend : 0
ErrHdrLen : 0 ErrPad : 0
ErrQoSTrs : 0 ErrVLANTrs : 0
ErrEncap : 0 ErrTagVLAN : 0
IfShut : 0 IfErr : 0
# (In IRF mode.) Display the Ethernet module statistics on slot 1 of IRF member device 1.
<Sysname> display ethernet statistics chassis 1 slot 1
ETH receive packet statistics:
Totalnum : 10447 ETHIINum : 4459
SNAPNum : 0 RAWNum : 0
LLCNum : 0 UnknownNum : 0
ForwardNum : 4459 ARP : 0
MPLS : 0 ISIS : 0
ISIS2 : 0 IP : 0
IPV6 : 0
ETH receive error statistics:
NullPoint : 0 ErrIfindex : 0
ErrIfcb : 0 IfShut : 0
ErrAnalyse : 5988 ErrSrcMAC : 5988
ErrHdrLen : 0
ETH send packet statistics:
L3OutNum : 211 VLANOutNum : 0
FastOutNum : 155 L2OutNum : 0
ETH send error statistics:
MbufRelayNum : 0 NullMbuf : 0
ErrAdjFwd : 0 ErrPrepend : 0
ErrHdrLen : 0 ErrPad : 0
ErrQoSTrs : 0 ErrVLANTrs : 0
ErrEncap : 0 ErrTagVLAN : 0
IfShut : 0 IfErr : 0
Table 3 Command output
Field |
Description |
ETH receive packet statistics |
Statistics about the Ethernet packets received on the Ethernet interface module. |
Totalnum |
Total number of received packets: · ETHIINum—Number of packets encapsulated by using Ethernet-II. · SNAPNum—Number of packets encapsulated by using SNAP. · RAWNum—Number of packets encapsulated by using RAW. · ISISNum—Number of packets encapsulated by using IS-IS. · LLCNum—Number of packets encapsulated by using LLC. · UnknownNum—Number of packets encapsulated by using unknown methods. · ForwardNum—Number of packets forwarded at Layer 2 or sent to the CPU. · ARP—Number of ARP packets. · MPLS—Number of MPLS packets. · ISIS—Number of IS-IS packets. · ISIS2—Number of large 802.3/802.2 frames encapsulated by using IS-IS. · IP—Number of IP packets. · IPv6—Number of IPv6 packets. |
ETH receive error statistics |
Statistics about the error Ethernet packets in the inbound direction on the Ethernet interface module. Errors might be included in packets or occur during the receiving process. The items include: · NullPoint—Number of packets that include null pointers. · ErrIfindex—Number of packets that include incorrect interface indexes. · ErrIfcb—Number of packets that include incorrect interface control blocks. · IfShut—Number of packets that are being received when the interface is shut down. · ErrAnalyse—Number of packets that include packet parsing errors. · ErrSrcMAC—Number of packets that include incorrect source MAC addresses. · ErrHdrLen—Number of packets that include header length errors. |
ETH send packet statistics |
Statistics about the Ethernet packets sent by the Ethernet interface module: · L3OutNum—Number of packets sent out of Layer 3 Ethernet interfaces. · VLANOutNum—Number of packets sent out of VLAN interfaces. · FastOutNum—Number of packets fast forwarded. · L2OutNum—Number of packets sent out of Layer 2 Ethernet interfaces. · MbufRelayNum—Number of packets transparently sent. |
ETH send error statistics |
Statistics about the error Ethernet packets in the outbound direction on the Ethernet interface module: · NullMbuf—Number of packets with null pointers. · ErrAdjFwd—Number of packets with adjacency table errors. · ErrPrepend—Number of packets with extension errors. · ErrHdrLen—Number of packets with header length errors. · ErrPad—Number of packets with padding errors. · ErrQoSTrs—Number of packets that failed to be sent by QoS. · ErrVLANTrs—Number of packets that failed to be sent in VLANs. · ErrEncap—Number of packets that failed to be sent due to link header encapsulation failures. · ErrTagVLAN—Number of packets that failed to be sent due to VLAN tag encapsulation failures. · IfShut—Number of packets that are being sent when the interface is shut down. · IfErr—Number of packets with incorrect outgoing interfaces. |
Related commands
reset ethernet statistics
display interface
Use display interface to display Ethernet interface information.
Syntax
display interface [ interface-type ] [ brief [ down ] ]
display interface [ interface-type [ interface-number | interface-number.subnumber ] ] [ brief [ description ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number, where interface-number is an interface number, and subnumber is 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.
down: Displays information about interfaces in the down state and the causes. If you do not specify this keyword, the command displays information about interfaces in all states.
description: Displays complete interface descriptions. If you do not specify this keyword, the command displays only the first 27 characters of interface descriptions.
Usage guidelines
If you do not specify an interface type, this command displays information about all interfaces.
If you specify an interface type but do not specify an interface number or subinterface number, this command displays information about all interfaces of that type.
If you specify both the interface type and interface number, this command displays information about the specified interface.
Examples
# Display information about Layer 3 interface GigabitEthernet 3/0/1.
<Sysname> display interface GigabitEthernet 3/0/1
GigabitEthernet3/0/1
Current state: DOWN
Line protocol state: DOWN
Description: GigabitEthernet3/0/1 Interface
Bandwidth: 1000000 kbps
Maximum transmission unit: 1500
Internet address: 10.1.1.2/24 (primary)
IP packet frame type: Ethernet II, hardware address: 7425-8a02-4d03
IPv6 packet frame type: Ethernet II, hardware address: 7425-8a02-4d03
Media type is twisted pair, Port hardware type is 1000_BASE_T
Port priority: 2
Loopback is not set
Unknown-speed mode, Unknown-duplex mode
Last clearing of counters: Never
Peak input rate: 0 bytes/sec, at 2014-12-29 09:46:13
Peak output rate: 0 bytes/sec, at 2014-12-29 09:46:13
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, - 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, - aborts
- ignored, - parity errors
Output (total): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, - pauses
Output (normal): 0 packets, 0 bytes
0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
- lost carrier, - no carrier
Table 4 Command output
Field |
Description |
Current state |
State of the interface: · Administratively DOWN—The Ethernet interface was shut down by using the shutdown command. The interface is administratively down. · DOWN—The Ethernet interface is administratively up but physically down. There might not be a physical link present or the link has failed. · UP—The Ethernet interface is both administratively and physically up. |
Line protocol state |
Link layer state of the interface. The state is determined through parameter negotiation on the link layer. · UP—The interface is up at the data link layer. · UP (spoofing)—The link layer protocol of an interface is UP, but its link is an on-demand link or not present at all. This attribute is typical of Null interfaces and loopback interfaces. · DOWN—The interface is down at the data link layer. · DOWN (DLDP DOWN)—The link layer protocol of the interface is down because DLDP detected that the link was unidirectional. · DOWN (LAGG DOWN)—The link layer protocol of the interface is down because the aggregate interface does not have Selected ports. · DOWN (OAM DOWN)—The link layer of the interface is down because OAM detected remote link failures. · DOWN (DLDP and LAGG DOWN)—The link layer of the interface is shut down by DLDP and LAGG. · DOWN (DLDP and OAM DOWN)—The link layer of the interface is shut down by DLDP and OAM. · DOWN (OAM and LAGG DOWN)—The link layer of the interface is shut down by OAM and LAGG. · DOWN (DLDP, OAM and LAGG DOWN)—The link layer of the interface is shut down by DLDP, OAM, and LAGG. |
Bandwidth |
Expected bandwidth of the interface. |
Internet protocol processing: |
Indicates that the interface cannot process IP packets. |
Output queue (Urgent queue: Size/Length/Discards) |
Output queue (the number of messages, the maximum number of messages allowed, and the number of dropped messages in the urgent queue). |
Output queue (Protocol queue: Size/Length/Discards) |
Output queue (the number of messages, the maximum number of messages allowed, and the number of dropped messages in the protocol queue). |
Output queue (FIFO queuing: Size/Length/Discards) |
Output queue (the number of messages, the maximum number of messages allowed, and the number of dropped messages in the FIFO queue). |
Unknown-speed mode |
The speed of the interface is unknown because the speed negotiation fails or the interface is physically disconnected. |
Unknown-duplex mode |
The duplex mode of the interface is unknown because the duplex mode negotiation fails or the interface is physically disconnected. |
Last clearing of counters |
Time when the reset counters interface command was last used to clear the interface statistics. Never indicates the reset counters interface command has never been used on the interface since the device’s startup. |
Last 300 seconds input rate |
Average input rate over the last 300 seconds in Bps, bps, and pps. |
Last 300 seconds output rate |
Average output rate over the last 300 seconds in Bps, bps, and pps. |
Input (total): 274955 packets, 26619800 bytes 52694 unicasts, 469 broadcasts, 221792 multicasts, - pauses |
Inbound traffic statistics (in packets and bytes) for the interface. All inbound normal and abnormal packets and normal pause frames were counted. Number of inbound unicast packets, number of inbound broadcasts, number of inbound multicasts, and number of inbound pause frames. A hyphen (-) indicates that the statistical item is not supported. |
Input (normal): 274955 packets, 26619800 bytes 52694 unicasts, 469 broadcasts, 221792 multicasts, 0 pauses |
Inbound normal traffic and pause frame statistics (in packets and bytes) for the interface. Number of inbound normal unicast packets, number of inbound normal broadcasts, number of inbound normal multicasts, and number of inbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported. |
input errors |
Number of inbound error packets. |
runts |
Number of inbound frames shorter than 64 bytes, in correct format, and containing valid CRCs. |
giants |
Number of inbound frames larger than the maximum frame length supported on the interface. · For an Ethernet interface that does not permit jumbo frames, giants refer to frames larger than 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). · For an Ethernet interface that permits jumbo frames, giants refer to frames larger than the maximum length of Ethernet frames that are allowed to pass through, which is configured when you configure jumbo frame support on the interface. |
throttles |
Number of inbound packets that contained a non-integer number of bytes. |
CRC |
Total number of inbound frames that had a normal length, but contained CRC errors. |
frame |
Total number of inbound frames that contained CRC errors and a non-integer number of bytes. |
overruns |
Number of packets dropped because the input rate of the port exceeded the queuing capability. |
aborts |
Total number of illegal inbound packets: · Fragment frames—CRC error frames shorter than 64 bytes. The length can be an integral or non-integral value. · Jabber frames—CRC error frames greater than the maximum frame length supported on the Ethernet interface (with an integral or non-integral length). ¡ For an Ethernet interface that does not permit jumbo frames, jabber frames refer to CRC error frames greater than 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). ¡ For an Ethernet interface that permits jumbo frames, jabber frames refer to CRC error frames greater than the maximum length of Ethernet frames that are allowed to pass through the interface. · Symbol error frames—Frames that contained a minimum of one undefined symbol. · Unknown operation code frames—Non-pause MAC control frames. · Length error frames—Frames whose 802.3 length fields did not match the actual frame length (46 to 1500 bytes). |
ignored |
Number of inbound frames dropped because the receiving buffer of the port ran low. |
parity errors |
Total number of frames with parity errors. |
Output (total): 275266 packets, 26640959 bytes 52980 unicasts, 488 broadcasts, 221798 multicasts, - pauses |
Outbound traffic statistics (in packets and bytes) for the interface. All outbound normal and abnormal packets and normal pause frames were counted. Number of outbound unicast packets, number of outbound broadcasts, number of outbound multicasts, and number of outbound pause frames. A hyphen (-) indicates that the statistical item is not supported. |
Output (normal): 275266 packets, 26640959 bytes 52980 unicasts, 488 broadcasts, 221798 multicasts, 0 pauses |
Outbound normal traffic and pause frame statistics (in packets and bytes) for the interface. Number of outbound normal unicast packets, number of outbound normal broadcasts, number of outbound normal multicasts, and number of outbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported. |
output errors |
Number of outbound error packets. |
underruns |
Number of packets dropped because the output rate of the interface exceeded the output queuing capability. This is a low-probability hardware anomaly. |
buffer failures |
Number of packets dropped because the transmitting buffer of the interface ran low. |
aborts |
Number of packets that failed to be transmitted, for example, because of Ethernet collisions. |
deferred |
Number of frames that the interface deferred to transmit because of detected collisions. |
collisions |
Number of frames that the interface stopped transmitting because Ethernet collisions were detected during transmission. |
late collisions |
Number of frames that the interface deferred to transmit after transmitting their first 512 bits because of detected collisions. |
lost carrier |
Number of carrier losses during transmission. This counter increases by one when a carrier is lost, and applies to serial WAN interfaces. |
no carrier |
Number of times that the port failed to detect the carrier when attempting to send frames. This counter increases by one when a port failed to detect the carrier, and applies to serial WAN interfaces. |
Peak input rate |
Peak rate of inbound traffic in Bps, and the time when the peak inbound traffic rate occurred. |
Peak output rate |
Peak rate of outbound traffic in Bps, and the time when the peak outbound traffic rate occurred. |
# Display detailed information about Layer 2 interface GigabitEthernet 3/0/1.
<Sysname> display interface GigabitEthernet 3/0/1
GigabitEthernet3/0/1
Current state: DOWN
Line protocol state: DOWN
IP packet frame type: Ethernet II, hardware address: 000c-2963-b767
Description: GigabitEthernet3/0/1 Interface
Bandwidth: 100000 kbps
Loopback is not set
Media type is twisted pair, port hardware type is 1000_BASE_T_AN_SFP
Unknown-speed mode, unknown-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 9216
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
PVID: 1
MDI type: automdix
Port link-type: Access
Tagged VLANs: None
Untagged VLANs: 1
Port priority: 2
Last clearing of counters: 14:34:09 Tue 11/01/2011
Peak input rate: 0 bytes/sec, at 2013-07-17 22:06:19
Peak output rate: 0 bytes/sec, at 2013-07-17 22:06:19
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
Table 5 Command output
Field |
Description |
Current state |
State of the Ethernet interface: · Administratively DOWN—The Ethernet interface was shut down by using the shutdown command. The interface is administratively down. · DOWN—The Ethernet interface is administratively up but physically down (possibly because no physical link is present or the link has failed). · UP—The Ethernet interface is both administratively and physically up. |
Line protocol current state |
Link layer state of the interface. The state is determined through parameter negotiation on the link layer. · UP—The interface is up at the data link layer. · UP (spoofing)—The link layer protocol of an interface is UP, but its link is an on-demand link or not present at all. This attribute is typical of Null interfaces and loopback interfaces. · DOWN—The interface is down at the data link layer. · DOWN (DLDP DOWN)—The link layer protocol of the interface is down because DLDP detected that the link was unidirectional. · DOWN (LAGG DOWN)—The link layer protocol of the interface is down because the aggregate interface does not have Selected ports. · DOWN (OAM DOWN)—The link layer of the interface is down because OAM detected remote link failures. · DOWN (DLDP and LAGG DOWN)—The link layer of the interface is shut down by DLDP and LAGG. · DOWN (DLDP and OAM DOWN)—The link layer of the interface is shut down by DLDP and OAM. · DOWN (OAM and LAGG DOWN)—The link layer of the interface is shut down by OAM and LAGG. · DOWN (DLDP, OAM and LAGG DOWN)—The link layer of the interface is shut down by DLDP, OAM, and LAGG. |
IP packet frame type |
Ethernet framing format. PKTFMT_ETHNT_2 indicates that the frames are encapsulated in Ethernet II framing format. |
hardware address |
MAC address of the interface. |
Bandwidth |
Expected bandwidth of the interface. |
Loopback is set internal |
An internal loopback test is running on the Ethernet interface. |
Loopback is set external |
An external loopback test is running on the Ethernet interface. |
Loopback is not set |
No loopback test is running on the Ethernet interface. |
10Mbps-speed mode |
The interface is operating at 10 Mbps. |
100Mbps-speed mode |
The interface is operating at 100 Mbps. |
1000Mbps-speed mode |
The interface is operating at 1000 Mbps. |
10Gbps-speed mode |
The interface is operating at 10 Gbps. |
40Gbps-speed mode |
The interface is operating at 40 Gbps. |
100Gbps-speed mode |
The interface is operating at 100 Gbps. |
Unknown-speed mode |
The speed of the interface is unknown because the speed negotiation fails or the interface is physically disconnected. |
half-duplex mode |
The interface is operating in half duplex mode. |
full-duplex mode |
The interface is operating in full duplex mode. |
unknown-duplex mode |
The duplex mode of the interface is unknown because the duplex mode negotiation fails or the interface is physically disconnected. |
Link speed type is autonegotiation |
The interface is configured with the speed auto command. |
Link speed type is force link |
The interface is configured with a speed (for example, 10 Mbps or 100 Mbps) by using the speed command. |
link duplex type is autonegotiation |
The interface is configured with the duplex auto command. |
link duplex type is force link |
The interface is configured with a duplex mode (for example, half or full) by using the duplex command. |
Maximum frame length |
Maximum Ethernet frame length allowed on the interface. |
Allow jumbo frame to pass |
The interface allows jumbo frames to pass through. |
Broadcast MAX- |
Broadcast storm suppression threshold in ratio, pps, or kbps. The unit of the threshold depends on your configuration. |
Multicast MAX- |
Multicast storm suppression threshold in ratio, pps, or kbps. The unit of the threshold depends on your configuration. |
Unicast MAX- |
Unicast storm suppression threshold in ratio, pps, or kbps. The unit of the threshold depends on your configuration. |
PVID |
Port VLAN ID (PVID) of the Ethernet interface. |
MDI type |
Cable type (depending on your configuration): · automdix. · mdi. · mdix. |
Port link-type |
Link type of the interface (depending on your configuration): · access. · trunk. · hybrid. |
Tagged VLAN ID |
VLANs for which the interface sends packets without removing VLAN tags. |
Untagged VLAN ID |
VLANs for which the interface sends packets after removing VLAN tags. |
Port priority |
Priority of the interface. |
Last clearing of counters: Never |
Time when the reset counters interface command was last used to clear statistics on the interface. Never indicates that the reset counters interface command was never used since the device was started. |
Peak input rate |
Peak rate of inbound traffic in Bps, and the time when the peak inbound traffic rate occurred. |
Peak output rate |
Peak rate of outbound traffic in Bps, and the time when the peak outbound traffic rate occurred. |
Last 300 seconds input: 0 packets/sec 0 bytes/sec 0% Last 300 seconds output: 0 packets/sec 0 bytes/sec 0% |
Average rate of inbound and outbound traffic in the last 300 seconds, in pps and Bps, and the ratio of the actual rate to the maximum interface rate. A hyphen (-) indicates that the statistical item is not supported. |
Input(total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
Inbound traffic statistics (in packets and bytes) for the interface. All inbound normal and abnormal packets and normal pause frames were counted. Number of inbound unicast packets, number of inbound broadcasts, number of inbound multicasts, and number of inbound pause frames. A hyphen (-) indicates that the statistical item is not supported. |
Input(normal): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
Inbound normal traffic and pause frame statistics (in packets and bytes) for the interface. Number of inbound normal unicast packets, number of inbound normal broadcasts, number of inbound normal multicasts, and number of inbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported. |
input errors |
Statistics of incoming error packets. |
runts |
Number of inbound frames shorter than 64 bytes, in correct format, and containing valid CRCs. |
giants |
Number of inbound frames larger than the maximum frame length supported on the interface. · For an Ethernet interface that does not permit jumbo frames, giants refer to frames larger than 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). · For an Ethernet interface that permits jumbo frames, giants refer to frames larger than the maximum length of Ethernet frames that are allowed to pass through, which is configured when you configure jumbo frame support on the interface. |
throttles |
Number of inbound packets that contained a non-integer number of bytes. |
CRC |
Total number of inbound frames that had a normal length, but contained CRC errors. |
frame |
Total number of inbound frames that contained CRC errors and a non-integer number of bytes. |
overruns |
Number of packets dropped because the input rate of the port exceeded the queuing capability. |
aborts |
Total number of illegal inbound packets: · Fragment frames—CRC error frames shorter than 64 bytes. The length can be an integral or non-integral value. · Jabber frames—CRC error frames greater than the maximum frame length supported on the Ethernet interface (with an integral or non-integral length). ¡ For an Ethernet interface that does not permit jumbo frames, jabber frames refer to CRC error frames greater than 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). ¡ For an Ethernet interface that permits jumbo frames, jabber frames refer to CRC error frames greater than the maximum length of Ethernet frames that are allowed to pass through the interface. · Symbol error frames—Frames that contained a minimum of one undefined symbol. · Unknown operation code frames—Non-pause MAC control frames. · Length error frames—Frames whose 802.3 length fields did not match the actual frame length (46 to 1500 bytes). |
ignored |
Number of inbound frames dropped because the receiving buffer of the port ran low. |
parity errors |
Total number of frames with parity errors. |
Output(total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
Outbound traffic statistics (in packets and bytes) for the interface. All outbound normal and abnormal packets and normal pause frames were counted. Number of outbound unicast packets, number of outbound broadcasts, number of outbound multicasts, and number of outbound pause frames. A hyphen (-) indicates that the statistical item is not supported. |
Output(normal): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses |
Outbound normal traffic and pause frame statistics (in packets and bytes) for the interface. Number of outbound normal unicast packets, number of outbound normal broadcasts, number of outbound normal multicasts, and number of outbound normal pause frames. A hyphen (-) indicates that the statistical item is not supported. |
output errors |
Number of outbound packets with errors. |
underruns |
Number of packets dropped because the output rate of the interface exceeded the output queuing capability. This is a low-probability hardware anomaly. |
buffer failures |
Number of packets dropped because the transmit buffer of the interface ran low. |
aborts |
Number of packets that failed to be transmitted, for example, because of Ethernet collisions. |
deferred |
Number of frames that the interface deferred to transmit because of detected collisions. |
collisions |
Number of frames that the interface stopped transmitting because Ethernet collisions were detected during transmission. |
late collisions |
Number of frames that the interface deferred to transmit after transmitting their first 512 bits because of detected collisions. |
lost carrier |
Number of carrier losses during transmission. This counter increases by one when a carrier is lost, and applies to serial WAN interfaces. |
no carrier |
Number of times that the port failed to detect the carrier when attempting to send frames. This counter increases by one when a port failed to detect the carrier, and applies to serial WAN interfaces. |
# 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
GE3/0/0 UP UP 10.1.1.2 Link to CoreRouter
GE3/0/1 DOWN DOWN --
Loop0 UP UP(s) 2.2.2.9
NULL0 UP UP(s) --
Vlan1 UP DOWN --
Vlan999 UP UP 192.168.1.42
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
GE3/0/2 DOWN auto A A 1
GE3/0/3 UP 100M(a) F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaaaa
GE3/0/4 DOWN auto A A 1
GE3/0/5 DOWN auto A A 1
GE3/0/6 UP 100M(a) F(a) A 1
GE3/0/7 DOWN auto A A 1
GE3/0/8 UP 100M(a) F(a) A 1
GE3/0/9 UP 100M(a) F(a) A 999
# Display brief information about interface GigabitEthernet 3/0/3, including the complete interface description.
<Sysname> display interface GigabitEthernet 3/0/3 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
GE3/0/3 UP 100M(a) F(a) A 1 aaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
# 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
GE3/0/1 DOWN Not connected
Brief information on interfaces in bridge mode:
Link: ADM - administratively down; Stby - standby
Interface Link Cause
GE3/0/2 DOWN Not connected
GE3/0/4 DOWN Not connected
GE3/0/5 DOWN Not connected
GE3/0/7 DOWN Not connected
Table 6 Command output
Field |
Description |
Brief information on interfaces in route mode: |
Brief information about Layer 3 interfaces. |
Link: ADM - administratively down; Stby - standby |
· ADM—The interface has been shut down by the network administrator. To recover its physical layer state, run the undo shutdown command. · Stby—The interface is a standby interface. |
Protocol: (s) – spoofing |
This field displays UP (s), where s represents the spoofing flag, when the following conditions exist: · The network layer protocol of an interface is UP. · Its link is an on-demand link or not present. This attribute is typical of interface Null 0 and loopback interfaces. |
Interface |
Interface name. |
Link |
Physical link state of the interface: · UP—The link is up. · DOWN—The link is physically down. · ADM—The link has been administratively shut down. To recover its physical state, run the undo shutdown command. · Stby—The interface is a standby interface. |
Protocol |
Link layer protocol state of the interface: · UP. · DOWN. · UP(s)—The link of the interface is an on-demand link or not present at all. |
Primary IP |
Main IP address of the interface. If the interface is not configured with an IP address, this field displays --. |
Description |
Partial or complete interface description configured by using the description command: · If the description keyword is not specified in the display interface brief command, the field displays the first 27 characters of the interface description. · If the description keyword is specified in the display interface brief command, the field displays the complete interface description. |
Brief information on interfaces in bridge mode: |
Brief information about Layer 2 interfaces. |
Speed: (a) - auto Duplex: (a)/A - auto; H - half; F - full |
If the speed of an interface is automatically negotiated, its speed attribute includes the autonegotiation flag, indicated by the letter a in parentheses. If the duplex mode of an interface is automatically negotiated, its duplex mode attribute includes the following options: · (a)/A—Autonegotiation. · H—Half negotiation. · F—Full negotiation. |
Type: A - access; T - trunk; H – hybrid |
Link type options for Ethernet interfaces. |
Speed |
Interface rate, in bps. |
Duplex |
Duplex mode of the interface: · A—Autonegotiation. · 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 |
Causes for the physical state of an interface to be DOWN. · Administratively—The port is 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 )—After an aggregate interface is shut down, the physical state of all member ports of the aggregate interface becomes DOWN. The cause is displayed as DOWN ( Link-Aggregation interface down ). · DOWN (Loopback detection down)—The port is shut down because the loopback detection module has detected loops. · DOWN ( Monitor-Link uplink down )—The port is shut down because the monitor link module has detected that the uplink is down. · IRF-link-down—When IRF detects that the IRF link is down on an MDC of a member device, the state of all physical interfaces except the excluded ports on the MDC of the member device is set to DOWN. The cause is displayed as IRF-link-down. · MAD ShutDown—After an IRF split, the state of all interfaces except the excluded ports in the IRF in recovery state is set to DOWN. The cause is displayed as MAD ShutDown. · Not connected—No physical connection exists (possibly because the network cable is disconnected or faulty). · Storm-Constrain—The port is shut down because the unknown unicast traffic, multicast traffic, or broadcast traffic exceeds the upper limit. · STP DOWN—The port is shut down by the STP BPDU guard function. · Port Security Disabled—The port is shut down by the intrusion detection mechanism because the port receives illegal packets. · Standby—The interface is a standby interface. |
reset counters interface
duplex
|
IMPORTANT: 100-GE interfaces do not support this command. |
Use duplex to set the duplex mode for an Ethernet interface.
Use undo duplex to restore the default duplex mode of the Ethernet interface.
Syntax
duplex { auto | full | half }
undo duplex
Default
· A 10-GE or 40-GE interface operates in full duplex mode.
· A GE interface operates in autonegotiation mode.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
auto: Configures the interface to autonegotiate the duplex mode with the peer.
full: Configures the interface to operate in full duplex mode. In this mode, the interface can receive and transmit packets at the same time.
half: Configures the interface to operate in half duplex mode. In this mode, the interface can only receive or transmit packets at a given time. This keyword is not supported in the current software version and is reserved for future support.
Examples
# Configure interface GigabitEthernet 3/0/1 to operate in full duplex mode.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] duplex full
flag sdh
Use flag sdh to set the value for the overhead byte J0 or J1 in SDH frames when the 10-GE interface operates in WAN mode.
Use undo flag sdh to restore the default value of the J0 or J1 byte.
Syntax
flag { j0 | j1 } sdh value
undo flag { j0 | j1 } sdh
Default
The J0 and J1 bytes are padded with 0s.
Views
Ten-GigabitEthernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
j0: Specifies the Path Trace byte in the Regenerator Section Overhead.
j1: Specifies the Path Trace byte in the High-Order Path Overhead.
value: Specifies the value for the J0 or J1 byte, a string of 1 to 15 characters.
Usage guidelines
This command is effective only when the 10-GE interface is operating in WAN mode.
Examples
# Set the value of the J0 byte in SDH frames to Sysname on interface Ten-GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 3/0/1
[Sysname-Ten-GigabitEthernet3/0/1] port-mode wan
[Sysname-Ten-GigabitEthernet3/0/1] flag j0 sdh Sysname
Related commands
port-mode
flow-control
|
IMPORTANT: The flow-control command is mutually exclusive with the priority-flow-control command. |
Use flow-control to enable generic flow control on an Ethernet interface.
Use undo flow-control to disable generic flow control on the Ethernet interface.
Syntax
flow-control
undo flow-control
Default
Generic flow control is disabled on an Ethernet interface.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
With the flow-control command configured, an 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.
Examples
# Enable TxRx mode generic flow control on the interface GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] flow-control
flow-interval
Use flow-interval to set the interface statistics polling interval.
Use undo flow-interval to restore the default interval.
Syntax
flow-interval interval
undo flow-interval
Default
The interface statistics polling interval is 300 seconds.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
interval: Sets the statistics polling interval, in seconds. The interval is in the range of 5 to 300 and must be a multiple of 5.
Examples
# Set the statistics polling interval to 100 seconds on GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] flow-interval 100
interface
Use interface to enter interface or subinterface view.
When the interface-number.subnumber argument is specified and the subinterface identified by the argument does not exist, this command creates the subinterface and enters subinterface view.
Syntax
interface interface-type { interface-number | interface-number.subnumber }
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number, where interface-number is an interface number, and subnumber is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
Examples
# Enter GigabitEthernet 3/0/1 interface view.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1]
# Create Ethernet subinterface GigabitEthernet 3/0/1.1 and enter GigabitEthernet 3/0/1.1 subinterface view.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1.1
[Sysname-GigabitEthernet3/0/1.1]
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.
Syntax
jumboframe enable [ value ]
undo jumboframe enable
Default
· The Ethernet interfaces on the device allows jumbo frames within 9216 bytes to pass through.
· The Ethernet interfaces on the LST1XP16LEB1 and LST1XP16LEC1 cards allow jumbo frames within 8164 bytes to pass through.
Views
Layer 2 Ethernet interface view, Layer 3 Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
value: Sets the maximum length of Ethernet frames that are allowed to pass through. The value range for this argument is 1552 to 9216 bytes.
Usage guidelines
If you set the value argument multiple times, the most recent configuration takes effect.
Examples
# Enable jumbo frames to pass through GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] jumboframe enable
link-delay
Use link-delay to set the physical state change suppression interval on an Ethernet interface.
Use undo link-delay to restore the default.
Syntax
link-delay [msec] delay-time mode { up | updown }
undo link-delay
Default
The suppression interval for both the link-up and link-down events on an Ethernet interface is 1 second.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
msec: Enables the physical state change suppression time to be accurate to milliseconds. If you do not specify this keyword, the suppression time is accurate to seconds.
delay-time: Sets the physical state change suppression interval on the Ethernet interface. A value of 0 indicates 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 is 0 to 30 seconds, and the value must be an integer. Values 11 through 30 are not supported in the current software version and are reserved for future support.
· If you specify the msec keyword, the value range for this argument is 0 to 10000 milliseconds, and the value must be a multiple of 100.
mode up: Suppresses the link-up events.
mode updown: Suppresses both the link-up and link-down events.
Usage guidelines
With the link-delay [msec] delay-time mode up command configured:
· When the interface comes up, the link-up event is not reported to the CPU unless the interface is still up when the suppression interval (delay-time) expires.
· When the interface goes down, the link-down event is immediately reported.
With the link-delay [msec] delay-time mode updown command configured:
· When the interface comes up, the link-up event is not reported to the CPU unless the interface is still up when the suppression interval (delay-time) expires.
· When the interface goes down, the link-down event is not reported to the CPU unless the interface is still down when the suppression interval (delay-time) expires.
On a port, if you configure the link-delay command multiple times, the most recent configuration takes effect.
Do not configure this command on a port with RRPP, MSTP, or Smart Link enabled.
When you configure the link-delay [msec] command on an Ethernet interface, the actual suppression interval is 0 to 100 milliseconds longer than the configured time. For example, if you configure the suppression interval as 100 milliseconds, the actual value is in the range of 100 to 200 milliseconds.
When you configure the link-delay command on an Ethernet interface, the actual suppression interval is 0 to 1 second longer than the configured time. For example, if you configure the suppression interval as 1 second, the actual value is 1 or 2 seconds.
Examples
# Set the link-up and link-down event suppression interval to 8 seconds on interface GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] link-delay 8 mode updown
loopback
|
CAUTION: After you enable loopback testing on an Ethernet interface, the interface does not forward data traffic. |
Use loopback to enable loopback testing on an Ethernet interface.
Use undo loopback to disable loopback testing on an Ethernet interface.
Syntax
loopback { external | internal }
undo loopback
Default
Loopback testing is disabled on an Ethernet interface.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
external: Enables external loopback testing on the Ethernet interface. This keyword is not supported in the current software version and is reserved for future support.
internal: Enables internal loopback testing on the Ethernet interface.
Usage guidelines
You cannot enable loopback testing on an administratively shut down interface (displayed as in ADM or Administratively DOWN state).
After you enable loopback testing on an interface, you cannot configure the speed, duplex, mdix-mode, port up-mode, and shutdown commands on the interface.
After you enable loopback testing on an Ethernet interface, the Ethernet interface switches to full duplex mode. After you disable loopback testing, the Ethernet interface restores to its duplex setting.
Examples
# Enable internal loopback testing on GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] loopback internal
port link-mode
Use port link-mode to change the link mode of an Ethernet interface.
Use undo port link-mode to restore the default.
Syntax
port link-mode { bridge | route }
undo port link-mode
Default
An Ethernet interface is operating in bridge mode as a Layer 2 Ethernet interface.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
bridge: Specifies the Layer 2 mode.
route: Specifies the Layer 3 mode.
Usage guidelines
Interfaces operate differently depending on the hardware structure of interface cards.
· Interfaces on EB cards can operate only as Layer 2 Ethernet interfaces.
· Other interfaces can operate either as Layer 2 or Layer 3 Ethernet interfaces.
You can use commands to set the link mode to bridge or route.
After you change the link mode of an Ethernet interface, all the commands (except the shutdown command) on the Ethernet interface are restored to their defaults in the new link mode.
Examples
# Configure GigabitEthernet 3/0/1 to operate in Layer 2 mode.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] port link-mode bridge
port-mode
Use port-mode to configure the operating mode for a 10-GE, 40-GE, or 100-GE interface.
Use undo port-mode to restore the default.
Syntax
port-mode { lan | wan }
undo port-mode
Default
A 10-GE, 40-GE, or 100-GE interface operates in LAN mode.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
lan: Configures the interface to operate in LAN mode. A port operating in this mode transmits Ethernet packets and connects an Ethernet network.
wan: Configures the interface to operate in WAN mode. A port operating in this mode transmits SDH packets and connects an SDH network. In addition, it supports point-to-point links only. 40-GE and 100-GE interfaces do not support the WAN mode.
Examples
# Configure the interface Ten-GigabitEthernet 3/0/1 to operate in WAN mode.
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 3/0/1
[Sysname-Ten-GigabitEthernet3/0/1] port-mode wan
priority-flow-control
Use priority-flow-control to enable PFC on an Ethernet interface through automatic negotiation or forcibly.
Use undo priority-flow-control to disable PFC on the interface.
Syntax
priority-flow-control { auto | enable }
undo priority-flow-control
Default
PFC is disabled on Ethernet interfaces.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
auto: Specifies PFC in auto mode. In this mode, the Ethernet interface automatically negotiates the PFC status with its peer.
enable: Forcibly enables PFC.
Usage guidelines
The state of the PFC function is co-determined by the PFC configurations on the local port and on the peer. In Table 7:
· The first line lists the PFC configuration on the local port.
· The first column lists the PFC configuration on the peer.
· The Enabled and Disabled fields in the other cells are the two possible negotiation results.
Table 7 PFC configurations and negotiation results
Local (right) Peer (below) |
enable |
auto |
disable |
enable |
Enabled |
Enabled. |
Disabled |
auto |
Enabled |
· Enabled if negotiation succeeds. · Disabled if negotiation fails. |
Disabled |
disable |
Disabled |
Disabled. |
Disabled |
This command is mutually exclusive with the flow-control command.
This command is applicable only to these interface cards: LST1XP48LFD1, LST1XP48LFD2, LST1XP40RFD1, LST1XP40RFD2, LST1XP40RFG1, LST1XP40RFG2, LST1CP4RFD1, LST1CP4RFD2, LST1CP4RFG1, LST1CP4RFG2, LST1XP20RFD1, LST1XP20RFD2, LST1XLP16RFD1, and LST1XLP16RFD2.
When configuring PFC for interfaces on an LST1XLP16RFD1 or LST1XLP16RFD2 interface card, follow these restrictions and guidelines:
· PFC is applicable to both the 40-GE interfaces and 10-GE breakout interfaces split from 40-GE interfaces.
· The sixteen 40-GE interfaces on an interface card are divided into four groups by their numbers. Interfaces numbered 1 through 4 belong to one group, interfaces numbered 5 through 8 belong to another group, and so forth. H3C recommends not splitting all interfaces in a group into 10-GE breakout interfaces. If you split all interfaces in a group into 10-GE breakout interfaces, PFC is applicable to none of the 10-GE breakout interfaces.
Physical IRF ports do not support PFC. In IRF mode, do not enable PFC on physical IRF ports of IRF member devices. For more information, see Virtual Technologies Configuration Guides.
To disable PFC on an Ethernet interface, you must disable PFC for all 802.1p priorities first. You can disable PFC for all 802.1p priorities by using the undo priority-flow-control no-drop dot1p command in the interface view.
Examples
# Forcibly enable PFC on interface GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] priority-flow-control enable
Related commands
priority-flow-control no-drop dot1p
priority-flow-control no-drop dot1p
|
IMPORTANT: Before configuring this command on an Ethernet interface, you must enable PFC on the interface first by using the priority-flow-control command. |
Use priority-flow-control no-drop dot1p to enable PFC for 802.1p priorities on an Ethernet interface.
Use undo priority-flow-control no-drop dot1p to restore the default.
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.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-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
This command is mutually exclusive with the flow-control command.
This command is applicable only to these interface cards: LST1XP48LFD1, LST1XP48LFD2, LST1XP40RFD1, LST1XP40RFD2, LST1XP40RFG1, LST1XP40RFG2, LST1CP4RFD1, LST1CP4RFD2, LST1CP4RFG1, LST1CP4RFG2, LST1XP20RFD1, LST1XP20RFD2, LST1XLP16RFD1, and LST1XLP16RFD2.
When configuring PFC for interfaces on an LST1XLP16RFD1 or LST1XLP16RFD2 interface card, follow these restrictions and guidelines:
· PFC is applicable to both the 40-GE interfaces and 10-GE breakout interfaces split from 40-GE interfaces.
· The sixteen 40-GE interfaces on an interface card are divided into four groups by their numbers. Interfaces numbered 1 through 4 belong to one group, interfaces numbered 5 through 8 belong to another group, and so forth. H3C recommends not splitting all interfaces in a group into 10-GE breakout interfaces. If you split all interfaces in a group into 10-GE breakout interfaces, PFC is applicable to none of the 10-GE breakout interfaces.
To map the 802.1p priorities to the local priorities, use the qos map-table command. For more information, see ACL and QoS Configuration Guide.
Before enabling PFC for an 802.1p priority, make sure the 802.1p priority is mapped to only one local priority.
In standalone mode, you cannot enable PFC for the 802.1p priority that has been mapped to local priority 0. In IRF mode, you cannot enable PFC for the 802.1p priority that has been mapped to local priority 0 or 7.
When network congestion occurs, the local device sends a PFC pause frame to the peer if both the local end and the peer end meet the following requirements:
· Have PFC enabled.
· Have the priority-flow-control no-drop dot1p command configured.
The peer stops sending packets carrying an 802.1p priority within the list specified by the dot1p-list argument until the congestion is removed.
Examples
# Forcibly enable PFC on interface GigabitEthernet 3/0/1, and enable PFC for 802.1p priority 5.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] priority-flow-control enable
[Sysname-GigabitEthernet3/0/1] priority-flow-control no-drop dot1p 5
Related commands
· priority-flow-control
· flow-control
reset counters interface
Use reset counters interface to clear the Ethernet interface or subinterface statistics.
Syntax
reset counters interface [ interface-type [ interface-number | interface-number.subnumber ] ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
interface-type: Specifies an interface type.
interface-number: Specifies an interface number.
interface-number.subnumber: Specifies a subinterface number, where interface-number is an interface number; subnumber is the number of a subinterface created under the interface. The value range for the subnumber argument is 1 to 4094.
Usage guidelines
Before collecting statistics for an interface within a specific time period, clear the previous statistics.
If you do not specify an interface type, this command clears statistics for all interfaces.
If you specify only the interface type, this command clears statistics for all interfaces of that type.
If you specify both the interface type and the interface or subinterface number, this command clears statistics for the specified interface or subinterface.
Examples
# Clear the statistics of GigabitEthernet 3/0/1.
<Sysname> reset counters interface GigabitEthernet 3/0/1
Related commands
· display interface
· display counters interface
· display counters rate interface
reset ethernet statistics
Use reset ethernet statistics to clear the Ethernet module statistics.
Syntax
In standalone mode:
reset ethernet statistics slot slot-number
In IRF mode:
reset ethernet statistics chassis chassis-number slot slot-number
Views
User view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
slot slot-number: Clears the Ethernet module statistics on the specified card. The slot-number argument represents the number of the slot that houses the card. (In standalone mode.)
chassis chassis-number slot slot-number: Clears the Ethernet module statistics on the specified card of the specified IRF member device. The chassis-number argument represents the ID of the IRF member device. The slot-number argument represents the number of the slot that houses the card. (In IRF mode.)
Examples
# (In standalone mode.) Clear the Ethernet module statistics on slot 6.
<Sysname> reset ethernet statistics slot 6
# (In IRF mode.) Clear the Ethernet module statistics on slot 1 of IRF member device 1.
<Sysname> reset ethernet statistics chassis 1 slot 1
Related commands
display ethernet statistics
shutdown
Use shutdown to shut down an Ethernet interface or subinterface.
Use undo shutdown to bring up an Ethernet interface or subinterface.
Syntax
shutdown
undo shutdown
Default
An Ethernet interface is down, and an Ethernet subinterface is up.
Views
Ethernet interface view, Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
You might need to shut down and then bring up an Ethernet interface to make some interface configurations take effect.
Examples
# Shut down and then bring up GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] shutdown
[Sysname-GigabitEthernet3/0/1] undo shutdown
# Shut down and then bring up GigabitEthernet 3/0/1.1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1.1
[Sysname-GigabitEthernet3/0/1.1] shutdown
[Sysname-GigabitEthernet3/0/1.1] undo shutdown
speed
Use speed to set the speed of an Ethernet interface.
Use undo speed to restore the default.
Syntax
speed { 10 | 100 | 1000 | 10000 | 40000 | 100000 | auto }
undo speed
Default
The speed of an Ethernet interface is autonegotiated.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
10: Sets the interface speed to 10 Mbps. This keyword is applicable only to fiber ports using a transceiver module and copper ports.
100: Sets the interface speed to 100 Mbps. This keyword is applicable only to fiber ports using a transceiver module, 100/1000-Mbps transceiver module, or 100-Mbps transceiver module and copper ports.
1000: Sets the interface speed to 1000 Mbps. This keyword is applicable only to fiber ports using a 100/1000-Mbps transceiver module or 1000-Mbps transceiver module and copper ports.
10000: Sets the interface speed to 10000 Mbps.
40000: Sets the interface speed to 40000 Mbps.
100000: Sets the interface speed to 100000 Mbps.
auto: Enables the interface to negotiate a speed with its peer.
Usage guidelines
For an Ethernet copper port, use the speed command to set its speed to match the speed of the peer interface.
For a fiber port, use the speed command to set its speed to match the rate of a transceiver module.
The 10000 keyword is applicable only to 10-GE interfaces.
The 40000 keyword is applicable only to 16-port 40-GE interface cards.
The 100000 keyword is applicable only to 4-port 100-GE interface cards.
When you connect a 10-GE interface to a 100-Mbps interface through a transceiver module, you must set the speed of the 10-GE interface to 100 Mbps.
Examples
# Configure GigabitEthernet 3/0/1 to autonegotiate the speed.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] speed auto
Related commands
speed auto
using fortygige
|
IMPORTANT: · This command is not supported on non-default MDCs. · 10-GE breakout interfaces split from a 40-GE interface on the default MDC can be assigned to non-default MDCs. |
Use using fortygige to combine four 10-GE breakout interfaces that are split from a 40-GE interface into a 40-GE interface.
Use undo using fortygige to cancel the configuration.
Syntax
using fortygige
undo using fortygige
Default
A 40-GE interface is used as a single interface.
Views
10-GE breakout interface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
If you need higher bandwidth, you can combine four 10-GE breakout interfaces that are split from a 40-GE interface into a 40-GE interface. To make this command take effect on the four 10-GE breakout interfaces, execute this command on only one of the 10-GE breakout interfaces.
After this command is successfully configured, you must reboot the device. The system deletes the four 10-GE breakout interface and creates the combined 40-GE interface.
Before rebooting a switch configured with this command, save the combining configuration even if the switch is an IRF member switch.
Examples
# Combine 10-GE breakout interfaces Ten-GigabitEthernet 1/0/16:1 through Ten-GigabitEthernet 1/0/16:4 into a 40-GE interface.
<System> system-view
[System] interface Ten-GigabitEthernet1/0/16:1
[System-Ten-GigabitEthernet1/0/16:1] using fortygige
The interfaces Ten-GigabitEthernet1/0/16:1 through Ten-GigabitEthernet1/0/16:4 will be deleted. Continue? [Y/N]:y
Reboot the line card to make the configuration take effect.
Related commands
using tengige
using tengige
|
IMPORTANT: · This command is not supported on non-default MDCs. · 10-GE breakout interfaces split from a 40-GE interface on the default MDC can be assigned to non-default MDCs. |
Use using tengige to split a 40-GE interface into multiple 10-GE breakout interfaces.
Use undo using tengige to cancel the configuration.
Syntax
using tengige
undo using tengige
Default
A 40-GE interface is used as a single interface, and is not split.
Views
40-GE interface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
To improve port density, reduce costs, and improve network flexibility, you can split a 40-GE interface into multiple 10-GE breakout interfaces. For example, you can split a 40-GE interface FortyGigE 1/0/49 into four 10-GE interfaces Ten-GigabitEthernet 1/0/49:1 through Ten-GigabitEthernet 1/0/49:4.
10-GE breakout interfaces support the same configuration and attributes as common 10-GE interfaces, except that they are numbered differently.
This command is applicable to 40-GE interfaces only on the LST1XLP16RFD1 and LST1XLP16RFD2 interface cards.
Before configuring this command for a fiber port, you must insert a 40-GE QSFP+ transceiver module into the fiber port.
You can split up to ten 40-GE interfaces into 10-GE breakout interfaces on each interface card.
After this command is successfully configured, you must reboot the device. The system deletes the 40-GE interface and creates the multiple 10-GE breakout interfaces.
Before rebooting a switch configured with this command, save the splitting configuration even if the switch is an IRF member switch.
The sixteen 40-GE interfaces on an LST1XLP16RFD1 or LST1XLP16RFD2 card are divided into four groups by their numbers. Interfaces numbered 1 through 4 belong to one group, interfaces numbered 5 through 8 belong to another group, and so forth. H3C recommends not splitting all interfaces in a group into 10-GE breakout interfaces. If you split all 40-GE interfaces in a group into 10-GE breakout interfaces, PFC is applicable to none of the 10-GE breakout interfaces.
Examples
# Split 40-GE interface FortyGigE 1/0/16 into four 10-GE breakout interfaces.
<System> system-view
[System] interface FortyGigE 1/0/16
[System-FortyGigE1/0/16] using tengige
The interface FortyGigE1/0/16 will be deleted. Continue? [Y/N]:y
Reboot the line card to make the configuration take effect.
Related commands
· using fortygige
· using hundredgige
Layer 2 Ethernet interface commands
broadcast-suppression
Use broadcast-suppression to enable broadcast suppression and set the broadcast suppression threshold.
Use undo broadcast-suppression to restore the default.
Syntax
broadcast-suppression { ratio | pps max-pps | kbps max-kbps }
undo broadcast-suppression
Default
Ethernet interfaces do not suppress broadcast traffic.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
ratio: Sets the broadcast suppression threshold as a percentage of the maximum interface rate. The value range for this argument is 0 to 100. The smaller the percentage, the less broadcast traffic is allowed to pass through. The parameter is not supported in the current software version and is reserved for future support.
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 maximum interface rate. For example, the value range for this argument is 0 to 1488100 on a GE interface and 0 to 59524000 on a 40-GE interface.
kbps max-kbps: Specifies the maximum number of kilobits of broadcast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the maximum interface rate.
Usage guidelines
You can use the broadcast storm suppression function to limit the size of broadcast traffic on an interface. When the broadcast traffic on the interface exceeds this threshold, the system drops packets until the traffic drops below this threshold.
When you configure the suppression threshold in pps or kbps, the device might convert the configured value into a multiple of a certain step supported by the chip. As a result, the actual 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 GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] broadcast-suppression kbps 10000
Related commands
· multicast-suppression
· unicast-suppression
mdix-mode
|
IMPORTANT: Fiber ports do not support this command. |
Use mdix-mode to configure the Medium Dependent Interface Cross-Over (MDIX) mode of an Ethernet interface.
Use undo mdix-mode to restore the default.
Syntax
mdix-mode { automdix | mdi| mdix }
undo mdix-mode
Default
Ethernet interfaces operate in automdix mode.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
automdix: Specifies that the interface negotiates pin roles with its peer.
mdi: Specifies that pins 1 and 2 are transmit pins and pins 3 and 6 are receive pins.
mdix: Specifies that pins 1 and 2 are receive pins and pins 3 and 6 are transmit pins.
Examples
# Set GigabitEthernet 3/0/1 to operate in MDI mode.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] mdix-mode mdi
multicast-suppression
Use multicast-suppression to enable multicast storm suppression and set the multicast storm suppression threshold.
Use undo multicast-suppression to restore the default.
Syntax
multicast-suppression { ratio | pps max-pps | kbps max-kbps }
undo multicast-suppression
Default
Ethernet interfaces do not suppress multicast traffic.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
ratio: Sets the multicast suppression threshold as a percentage of the maximum interface rate. The value range for this argument (in percentage) is 0 to 100. The smaller the percentage, the less multicast traffic is allowed to pass through. The parameter is not supported in the current software version and is reserved for future support.
pps max-pps: Specifies the maximum number of multicast packets that the interface can forward per second. The value range for the max-pps argument (in pps) is 0 to 1.4881 × the maximum interface rate. For example, the value range for this argument is 0 to 1488100 on a GE interface and 0 to 59524000 on a 40-GE interface.
kbps max-kbps: Specifies the maximum number of kilobits of multicast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the maximum interface rate.
Usage guidelines
You can use the multicast storm suppression function to limit the size of multicast traffic on an interface. When the multicast traffic on the interface exceeds this threshold, the system drops packets until the traffic drops below this threshold.
When you configure the suppression threshold in pps or kbps, the device might convert the configured value into a multiple of a certain step supported by the chip. As a result, the actual 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 GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] multicast-suppression kbps 10000
Related commands
· broadcast-suppression
· unicast-suppression
port connection-mode
Use port connection-mode to set the connection mode for an interface.
Use undo port connection-mode to restore the default.
Syntax
port connection-mode { extend | normal }
undo port connection-mode
Default
An interface operates in normal connection mode.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
extend: Sets the interface to operate in extend connection mode.
normal: Sets the interface to operate in normal connection mode.
Usage guidelines
To ensure the communication between the device and the card in an OAA network, configure the internal interface connecting them to operate in extend connection mode.
This command is applicable only to the internal interfaces on an LST1NSM1A1 card (OAP card). For more information about the internal interfaces on an LST1NSM1A1 card, see OAA Configuration Guide.
Examples
# Set interface Ten-GigabitEthernet 3/0/1 to operate in extend connection mode.
<Sysname> system-view
[Sysname] interface Ten-GigabitEthernet 3/0/1
[Sysname-Ten-GigabitEthernet3/0/1] port connection-mode extend
port up-mode
Use port up-mode to forcibly bring up a fiber port.
Use undo port up-mode to restore the default.
Syntax
port up-mode
undo port up-mode
Default
A fiber port is not forcibly brought up. The physical state of a fiber port depends on the physical state of the fibers.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
You can use this command to forcibly bring up a fiber Ethernet port, and enable the port to forward packets unidirectionally over a single link. In this way, transmission links are well utilized.
A fiber port forcibly brought up stays physically up whether or not a transceiver module or fiber connections are present for the port.
Only 10-GE and 40-GE fiber ports operating in LAN mode and GE fiber ports support this command. Copper ports do not support this command.
To configure this command on a port, make sure the port is operating in bridge mode.
The port up-mode command is mutually exclusive with any of the shutdown, and loopback commands.
A fiber port forcibly brought up cannot correctly forward traffic if you install a fiber-to-copper converter, 100/1000-Mbps transceiver module, or 100-Mbps transceiver module into the port. To solve the problem, use the undo port up-mode command on the fiber port.
Examples
# Forcibly bring up the fiber port GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] port up-mode
speed auto
Use speed auto to set options for speed autonegotiation.
Use undo speed to restore the default.
Syntax
speed auto { 10 | 100 | 1000 } *
undo speed
Default
The options for speed autonegotiation include 10, 100, and 1000.
Views
100-Mbps or Gigabit Layer 2 Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
10: Sets 10 Mbps as an option for speed autonegotiation.
100: Sets 100 Mbps as an option for speed autonegotiation.
1000: Sets 1000 Mbps as an option for speed autonegotiation.
Usage guidelines
The speed command and the speed auto command supersede each other. The most recent command that you configure takes effect.
If you configure speed 100 after configuring speed auto 100 1000 on an interface, the interface speed is set to 100 Mbps by force without negotiation.
If you configure speed auto 100 1000 after configuring speed 100 on the interface, the interface negotiates with its peer. The negotiated speed is either 100 Mbps or 1000 Mbps.
Speed autonegotiation enables an Ethernet interface to negotiate with its peer for the highest speed that both ends support by default. You can narrow down the speed option list for negotiation. To avoid negotiation failure, make sure a minimum of one speed option is supported at both ends.
Examples
# Configure the port GigabitEthernet 3/0/1 to use 10 Mbps and 1000 Mbps for speed negotiation.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] speed auto 10 1000
Related commands
speed
unicast-suppression
Use unicast-suppression to enable unicast storm suppression and set the unicast storm suppression threshold.
Use undo unicast-suppression to restore the default.
Syntax
unicast-suppression { ratio | pps max-pps | kbps max-kbps }
undo unicast-suppression
Default
Ethernet interfaces do not suppress unicast traffic.
Views
Layer 2 Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
ratio: Sets the unicast suppression threshold as a percentage of the maximum interface rate. The value range for this argument (in percentage) is 0 to 100. The smaller the percentage, the less unicast traffic is allowed to pass through.
pps max-pps: Specifies the maximum number of 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 maximum interface rate. For example, the value range for the argument is 0 to 1488100 on a GE interface and 0 to 59524000 on a 40-GE interface.
kbps max-kbps: Specifies the maximum number of kilobits of unicast traffic that the Ethernet interface can forward per second. The value range for this argument (in kbps) is 0 to the maximum interface rate.
Usage guidelines
You can use the unicast storm suppression function to limit the size of unicast traffic on an interface. When the unicast traffic on the interface exceeds this threshold, the system discards packets until the unicast traffic drops below this threshold.
When you configure the suppression threshold in pps or kbps, the device might convert the configured value into a multiple of a certain step supported by the chip. As a result, the actual 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 unicast storm suppression threshold to 10000 kbps on GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] unicast-suppression kbps 10000
Related commands
· broadcast-suppression
· multicast-suppression
Layer 3 Ethernet interface or subinterface commands
mtu
Use mtu to set the MTU for an Ethernet interface or subinterface.
Use undo mtu to restore the default.
Syntax
mtu size
undo mtu
Default
The MTU of an Ethernet interface or subinterface is 1500 bytes.
Views
Layer 3 Ethernet interface view, Layer 3 Ethernet subinterface view
Predefined user roles
network-admin
mdc-admin
Parameters
size: Sets the maximum transmission unit (MTU) in the range of 64 to 9198 bytes.
Usage guidelines
As the MTU size decreases, the number of fragments grows. When you set the MTU for an interface, consider QoS queue lengths to prevent a too small MTU from causing packet drops in QoS queuing. For example, consider that the default FIFO queue length is 75. To achieve the best result, you can tune the MTU by using the mtu command or tune QoS queue lengths by using the qos fifo queue-length command. For more information about the qos fifo queue-length command, see ACL and QoS Command Reference.
Examples
# Set the MTU to 1430 bytes for Layer 3 Ethernet interface GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1
[Sysname-GigabitEthernet3/0/1] mtu 1430
# Set the MTU to 1400 bytes for Layer 3 Ethernet subinterface GigabitEthernet 3/0/1.1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 3/0/1.1
[Sysname-GigabitEthernet3/0/1.1] mtu 1430