Configuration Condition
No
Enter Ethernet Interface Configuration Mode
To configure on the specified port, first enter the L2 Ethernet interface configuration mode of the Ethernet interface or L3 Ethernet interface configuration mode and then execute the corresponding configuration command.
Table 2-2 Enter the L2 Ethernet interface configuration mode
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Mandatory
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
The naming rule of the Ethernet interface number is U/S/P (Unit/Slot/Port). Unit indicates the device in the stacking state, numbered from 0. When the device is initialized, it is necessary to confirm whether the device is in the stacking state. If no, the device number is 0 and hidden by default. Slot indicates the slot on the device, numbered from 0. If there is fixed port, slot 0 is reserved for the fixed port. The service slot is numbered from 1. Port indicates the Ethernet interface on the device or interface card. The Ethernet interface on each device and interface card is numbered from 1.
- The naming rule of the Ethernet interface name interface-name is Ethernet interface type + Ethernet interface number. For example, gigabitethernet0/1 indicates the 1000M Ethernet interface numbered 1; tengigabitethernet1/2 indicates the Gigabit Ethernet interface numbered 2 on the service slot numbered 1. In the VST mode, gigabitethernet0/1/2 indicates 1000M Ethernet interface numbered 2 on the service slot numbered 1 of the member device numbered 0.
Enter Batch Configuration Mode of L2 Ethernet Interface
When performing the same configuration on multiple ports, to improve the configuration efficiency and reduce the repeated steps, select entering the batch configuration mode of the L2 Ethernet interface, including the following three cases: single port, such as gigabitethernet 0/1; successive ports, using “-” to indicate one section of successive ports, such as gigabitethernet 0/3-0/5, indicating port 0/3, 0/4, 0/5; single port and successive ports, using comma to separate, such as “gigabitethernet 0/1, 0/3-0/4, 0/6”, indicating port 0/1, 0/3, 0/4, 0/6.
Table 2-3 Enter the batch configuration mode of the L2 Ethernet interface
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the batch configuration mode of the L2 Ethernet interface
|
interface interface-list
|
Mandatory
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
L3 Ethernet interface does not support the batch configuration mode.
Configure Rate and Duplex Mode
Setting the rate of the Ethernet interface includes two cases:
- One is to set the fixed rate according to the Ethernet interface rate capability set. The optional parameters include 10 (10M), 100 (100M), 1000 (1000M), 10000 (10000M), 25000 (25000M), 40000 (40000M), 100000 (100000M)
- The other is to set the rate as auto (auto-negotiation), specifying that the rate is negotiated by the local and peer Ethernet interfaces.
Similarly, setting the duplex mode of the Ethernet interface includes two cases:
- One is to set the duplex mode of the Ethernet interface according to the capability set of the Ethernet interface duplex mode. The optional parameters include full (full-duplex mode), indicating that the Ethernet interface can send packets when receiving the packets; half (half-duplex mode), indicating that the Ethernet interface can only receive or send packets at one moment, but cannot perform at the same time;
- The other is to set the duplex mode as auto (auto-negotiation), indicating that the duplex mode is negotiated automatically by the local and peer Ethernet interfaces.
Table 2-4 Configure the rate and duplex mode
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the rate of the Ethernet interface
|
speed { 10 | 100 | 1000 | 10000 | 25000 | 40000 | 100000 | auto }
|
Mandatory
|
Configure the duplex mode of the Ethernet interface
|
duplex { auto | full | half}
|
Mandatory
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
When the Ethernet interface is the 100M optical port, the supported rate is 100M and auto, and the supported duplex mode is auto and full-duplex mode; when the Ethernet interface is 1000M optical port, the supported rate is 100M, 1000M and auto, the supported duplex mode is auto and full-duplex mode; when the port is the 10 gigabit optical port, the supported rate is 1000M and 10000M, and the supported duplex mode is auto and full-duplex mode.
Configure FEC
FEC (forward error correction) is a kind of error correction method. It can improve the signal quality by adding error correction information to the packet at the sending port and using error correction information to correct the error code generated during the transmission of the packet at the receiving end, but it will also bring some delay to the signal. The user can choose to disable or enable this function according to the actual situation.
The FEC status of the port can be configured manually or in an adaptive way. If the user does not configure the supported optical module type on the port, when inserting the module or configuring the port rate, the FEC will be configured adaptively according to the module type and rate inserted in the current port. If there is user configuration on the port, it will be subject to user configuration and will not be adaptive when the port is inserted into the module or configured with speed.
Table 2-5 Configure the port FEC status
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the port FEC status
|
[no] fec mode {base-r {auto|manual} |rs { auto|manual }|none manual}
|
Mandatory
By default, the port does not enable FEC.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
When the rate is not 25G or 100G, FEC cannot be configured. When the port has manual configuration of FEC, you cannot switch the rate to non-25G or 100G.
- This function cannot be configured on the VSL member port.
- Auto is configured to be distributed adaptively. Before restarting the device, the user needs to use the write command to save the configuration.
- Only 25GE and 100GE interfaces support this function. FEC configuration will take effect only when the actual speed is 25G or 100G.
Configure MDIX Mode
The signals can be sent only after the local and the peer Ethernet interfaces are connected. Therefore, the MDIX mode is used with connection cables.
The cables connecting Ethernet interfaces are divided to two types: straight-through cable and crossover cable. To support the two types of cables, provide three kinds of MDIX modes: normal, cross and auto.
The optical port only supports straight-through cable.
The electrical port is formed by eight pins. You can change the roles of the pins by setting the MDIX mode. When setting as normal, use pin 1 and 2 to send signals, and pin 3, 6 to receive signals; when setting as cross, use pin 1, 2 to receive signals, pin 3, 6 to send signals; when setting as auto, the local and peer electrical ports automatically negotiate the functions of the pins by connecting the cables.
When using the straight-through cable, the MDIX modes of the local and peer Ethernet interfaces cannot be the same.
When using crossover cable, the MDIX modes of the local and peer Ethernet interfaces should be the same or at least one is auto.
Table 2-6 Configure the MDIX mode
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the mode of receiving and sending signals via network cable
|
mdix { auto | cross | normal }
|
Mandatory
By default, the MDIX mode of the electrical port is auto and the MDIX mode of the optical port is normal.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
The optical port does not support the configuration.
Configure Media Type
Switch to use the optical port or electrical port on the Combo port by configuring the media type of the Ethernet interface. The optical port and the corresponding electrical port cannot work at the same time. When specifying one media type on Combo port, the other media type is automatically disabled.
Table 2-7 Configure media type
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure media type
|
media-type { auto | copper | fiber }
|
Mandatory
By default, the media type of the electrical port is copper; the media type of the optical port is fiber; the media type of the Combo port is copper.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
When switching the optical port and electrical port on the Combo port, the Ethernet interface configuration after switching, such as rate, duplex mode, and MDIX mode, are initialized to the default values.
Configure MTU
The MTU configured on the L2 Ethernet interface takes effect for the ingress packets. When the length of the received packets exceeds the set value, the packets are dropped directly.
In contrast, the MTU configured on L3 Ethernet interface takes effect for the ingress packets. When the length of the packet sent by the local device exceeds the set value, the packet first performs the IP fragmenting, making the length of the fragmented packet not exceed the set value, and then send it out.
Table 2-8 Configure MTU
Step
|
Command
|
Description
|
Enter the global configuration mode |
configure terminal |
- |
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernetinterface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure MTU
|
mtu mtu-value
|
Mandatory
By default, the MTU of L2 Ethernet interface is 1824 bytes and the MTU of L3 Ethernet interface is 1500 bytes.
|
Configure Flow Control
When the sending or receiving buffer is full and if the duplex mode of the port is half-duplex, send the blocking signals back to the source end by the back pressure mode; if the duplex mode of the port is full-duplex mode, the port informs the source end to stop sending by the flow control mode.
Table 2-9 Configure flow control
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode
|
interface interface-name
|
-
|
Configure flow control
|
flowcontrol { on | off }
|
Mandatory
By default, the flow control function of the port is disabled.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
The local flow control can be realized only when the local and peer ends both enable the flow control function.
Configure Delay Time
When the port changes from Up to Down, first enter the set suppression time period and the switching of the port status is not felt by the system; and then after the set suppression time, report the port status change to the system. In this way, we can avoid the unnecessary running cost caused by the frequent switching of the ports status in short time.
Table 2-10 Configure delay time
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode
|
interface interface-name
|
-
|
Configure delay time
|
link-delay link-delay-value
|
Mandatory
By default, the delay report time of the port changing from Up to Down is 0, that is, disable the delay report function; when the port changes from Up to Down, report and process immediately.
|
Configure Auto Energy-Saving
When disabling or enabling port auto energy-saving, but not connecting cables, the port inside is always in the polling port state. To reduce the unnecessary energy consumption, automatically switch to the low energy consumption state when the port is idle by configuring the port auto energy-saving.
Table 2-11 Configure port auto energy-saving
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode
|
interface interface-name
|
-
|
Configure auto energy-saving
|
auto-power-down enable
|
Mandatory
By default, the auto energy-saving function of the port is disabled.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
The device does not support configuring auto energy-saving.
Configure Energy Efficient Ethernet Function
When no data traffic passes, the Ethernet interface inside is always polling the port state. To reduce such unnecessary consumption, you can configure the energy efficient Ethernet function. When the interface is idle, it is automatically switched to the low energy state.
When the data is normally transmitted, recover the power supply.
Table 2-12 Configure the energy efficient Ethernet function
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the energy efficient Ethernet function
|
energy-efficient-ethernet enable
|
Optional
By default, the energy efficient Ethernet function of the Ethernet interface is disabled.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
- After the Ethernet interfaces on the both sides of the cable are enabled with the energy efficient Ethernet function, the function can take effect.
- The optical interface does not support the energy efficient Ethernet function.
- The interface with the rate as 10 Mbps and with the duplex mode as any mode and the interface with the rate as 100 Mbps and the duplex mode not as the automatic negotiation mode do not support the energy efficient Ethernet function.
- The device does not support configuring energy efficient Ethernet.
Configure Optical Module Type Supported by Port
The Gigabit and 10G Ethernet optical interfaces are in the OMM disabled state when the optical modules are not inserted. This port can be enabled only when the type of optical module inserted on the port is the same as that supported by the port configuration.
Therefore, you need to configure the type of optical module supported by the port, which can be manually configured by the user or configured in an adaptive way. If the user does not configure the supported optical module type on the port, the optical module type supported by the port will be adaptively configured according to the module type inserted on the port, so that the port can use the corresponding optical module normally. If there is a user configuration on the port, it will be subject to the user configuration and will not be adaptive according to the type of module inserted in the port.
The types of optical modules include Gigabit photoelectric module, 10G photoelectric module, common optical module, and unrecognized optical module. The common optical modules include Gigabit optical module, 10G Optical module, 10G high-speed cable, 40G optical module, 40G high-speed cable and other optical modules. Unrecognized optical modules cannot be used normally.
By default, the port supports common optical modules.
Due to the different speed capability levels supported by different types of modules, when the configuration port supports different optical module types (including user configuration and adaptive configuration), the speed configuration of the port may be modified synchronously.
Table 2-13 Configure the optical module type supported by the port
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the optical module supported by the port
|
optical fiber-to-copper { get | xget }
|
Mandatory
By default, the port supports the common optical module.
|
Clear the configuration of the optical module type supported by the port
|
no optical fiber-to-copper { get [auto] | xget [auto] | unknown-module auto }
|
Mandatory
The auto command is used to clear the self-adaptive configuration, but cannot clear the user configuration. After the self-adaptive configuration is cleared, the port supports the common optical module by default.
At this time, the self-adaptive will be triggered only after the optical module is swapped or the device is restarted.
The non auto command is used to clear the user configuration and will automatically re-adapt according to the type of optical module inserted on the port.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
You can configure the function only on the Ethernet optical interface, but cannot configure on the electrical port or combo port.
- This function cannot be configured on the VSL member port.
- The function cannot be configured on 40G or 100G port.
- Auto is configured to be distributed adaptively. Before restarting the device, the user needs to use the write command to save the configuration.
Configure Forcing to Cancel OMM-disabled State of the Interface
When the Ethernet optical interface is not inserted into the optical module, the port will be in the OMM-disabled state, unable to receive and send packets. After inserting a valid optical module, the OMM disabled state of the Ethernet optical interface will be automatically cancelled. However, sometimes the Ethernet port can also be up without the optical module inserted, such as enabling the loopback detection function. At this time, you can configure to forcibly cancel the OMM disabled state of the Ethernet optical interface.
Only when the optical module is not inserted to Ethernet optical interface, it will be in the OMM disabled state. The electric interface and combo interface will not be set to the OMM disabled state, so this function is unnecessary.
Table 2-14 Configure forcing to cancel the OMM-disabled state of the interface
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2/L3 Ethernet interface configuration mode
|
interface interface-name
|
Either
After entering L2/L3 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Enable forcing to cancel the OMM-disabled state of the interface
|
optical enable port manual
|
Mandatory
By default, the function is disable.
|
Disable forcing to cancel the OMM-disabled state of the interface
|
no optical enable port manual
|
Mandatory
By default, the function is disable.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
- You can configure the function only on the Ethernet optical interface, but cannot configure on the electrical port or combo port.
- This function cannot be configured on the VSL member port.
Configure Port CRC Error Packet Detection Function
It is necessary to configure snmp-server enable traps crc-error first. This function is used to count whether CRC error packets within the time-value time range exceed the upper limit. If it exceeds the upper limit, an alarm trap will be sent. When the number of CRC error packets is recovered from higher than the upper limit to lower than the lower limit, the recovered trap will be sent.
Table 2-15 Configure the crc error packet detection function
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode/aggregation group
|
interface interface-name
|
Mandatory
After entering L2 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the crc error packet detection trap function |
crc-error max-limit max-value min-limit min-value interval time-value
|
Mandatory
By default, the function of sending trap when the crc error packet statistics of the port exceeds the alarm range is disabled.
max-value: The maximum number of the port crc error packets
min-value: The minimum number of the port crc error packets
time-value: Set the detection time range, and the unit is second
|
Disable the crc error packet detection function |
no crc-error |
Mandatory
By default, the function is disabled.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
- The function can take effect only on the L2 port.
- Meanwhile, you need to enable the flow-warn function.
Configure Port Error Packet Detection Function
It is necessary to configure snmp-server enable traps { in-packet-error | out-packet-error } first. This function is used to count whether error packets within the time-value time range exceed the upper limit. If it exceeds the upper limit, an alarm trap will be sent. When the number of port error packets in the time range time-value is recovered from higher than the upper limit to lower than the lower limit, the recovered trap will be sent.
Table 2-16 Configure the error packet detection function
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode/aggregation group configuration mode
|
interface interface-name
|
Mandatory
After entering L2 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the error packet detection trap function
|
packet-error {in-packet | out-packet} max-limit max-value min-limit min-value interval time-value
|
Mandatory
By default, the function of sending trap when the error packet statistics of the port exceeds the alarm range is disabled.
in-packet: Enable the port ingress error packet quantity trap function.
out-packet: Enable the port egress error packet quantity trap function.
max-value: The maximum number of the port error packets
min-value: The minimum number of the port error packets
time-value: Set the time range of the detection time, the unit is second
|
Disable the error packet detection trap function
|
no packet-error {in-packet | out-packet}
|
Mandatory
By default, the function is disabled.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
The function can take effect only on the L2 port.
- Meanwhile, you need to enable the flow-warn function.
Configure Port Traffic Exceeding Bandwidth Function
You need to configure snmp-server enable traps {in-usage-rate | out-usage-rate }. This function is used to send an alarm trap when the ingress/egress bandwidth utilization rate of the port exceeds the upper limit. When the ingress/egress bandwidth utilization rate of the port recovers from higher than the upper limit to lower than the lower limit, the recovered trap will be sent.
Table 2-17 Configure the port traffic exceeding bandwidth function
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode/aggregation group configuration mode
|
interface interface-name
|
Mandatory
After entering L2 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the port traffic exceeding bandwidth trap function
|
flow-warn { in-packet | out-packet } max-usage max-value min-usage min-value
|
Mandatory
By default, the function of sending trap when the port traffic exceeds the bandwidth is disabled.
in-packet: Enable the port ingress bandwidth utilization trap function.
out-packet: Enable the port egress bandwidth utilization trap function.
max-value: The maximum value of the bandwidth utilization
min-value: The minimum value of the bandwidth utilization
|
Disable the traffic exceeding bandwidth trap function |
no flow-warn {in-packet | out-packet} |
Mandatory
By default, the function is disabled.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
The function can take effect only on the L2 port.
Configure Port Splitting and Merging
Port splitting can split a high-bandwidth physical port on the device into multiple independent low-bandwidth ports. For example, split the 40G port to four 10G ports. Users can freely choose to use the original high-bandwidth port or split it into multiple low-bandwidth ports according to the specific port type of the docking device, which increases the networking flexibility and reduces the purchase cost of users.
Table 2-18 Configure the port splitting
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode/aggregation group configuration mode
|
interface interface-name
|
Mandatory
After entering L2 Ethernet interface configuration mode, the subsequent configuration just takes effect on the current interface.
|
Configure the port splitting
|
split into 10GE
|
Mandatory
By default, the Ethernet interface is not split.
|
Table 2-19 Configure the port merging
Step
|
Command
|
Description
|
Enter the global configuration mode
|
configure terminal
|
-
|
Enter the L2 Ethernet interface configuration mode
|
interface interface-name:num
|
Mandatory
After entering the configuration mode of any split L2 Ethernet interface, the subsequent configuration only takes effect on the current interface.
|
Configure the port merging
|
no split
|
Mandatory
By default, the split Ethernet interfaces are not merged.
|
![note](/storage/images/Document/Maipu/note-icon.jpg)
-
Only NSS5820-26XF(V1) supports configuring the port splitting and merging.