NE40E-F V800R011C10 Configuration Guide - Interface and Data Link 02
NE40E-F V800R011C10 Configuration Guide - Interface and Data Link 02
Router
V800R011C10
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: [email protected]
Contents
Purpose
This document provides the basic concepts, configuration procedures, and configuration
examples in different application scenarios of the Interface Management feature supported by
the NE40E device.
Related Version
The following table lists the product version related to this document.
U2000 V200R018C60
NCE-IP V100R019C00
Intended Audience
This document is intended for:
Security Declaration
l Encryption algorithm declaration
The encryption algorithms DES/3DES/RSA (RSA-1024 or lower)/MD5 (in digital
signature scenarios and password encryption)/SHA1 (in digital signature scenarios) have
a low security, which may bring security risks. If protocols allowed, using more secure
encryption algorithms, such as AES/RSA (RSA-2048 or higher)/SHA2/HMAC-SHA2 is
recommended.
Special Declaration
l This document serves only as a guide. The content is written based on device
information gathered under lab conditions. The content provided by this document is
intended to be taken as general guidance, and does not cover all scenarios. The content
provided by this document may be different from the information on user device
interfaces due to factors such as version upgrades and differences in device models,
board restrictions, and configuration files. The actual user device information takes
precedence over the content provided by this document. The preceding differences are
beyond the scope of this document.
l The maximum values provided in this document are obtained in specific lab
environments (for example, only a certain type of board or protocol is configured on a
tested device). The actually obtained maximum values may be different from the
maximum values provided in this document due to factors such as differences in
hardware configurations and carried services.
l Interface numbers used in this document are examples. Use the existing interface
numbers on devices for configuration.
l The pictures of hardware in this document are for reference only.
l In this document, public IP addresses may be used in feature introduction and
configuration examples and are for reference only unless otherwise specified.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
l Changes in Issue 02 (2019-09-30)
This issue is the second official release. The software version of this issue is
V800R011C10SPC100.
l Changes in Issue 01 (2019-08-08)
This issue is the first official release. The software version of this issue is
V800R011C10.
2 Interface Management
Interface management helps to provide quick and accurate communication between devices.
You can disable the alarm function for an optical module to prevent the optical module from
reporting alarms when its optical power exceeds the threshold.
2.11 Managing Non-Huawei-Certified Optical Modules
To manage non-Huawei-certified optical modules, you can suppress the alarms for non-
Huawei-certified optical modules and enable the function of setting interfaces with the optical
modules inserted to Down.
2.12 Configuring the Control-Flap Function
This section describes how to configure the control-flap function.
2.13 Configuring Logical Interfaces
This section describes how to configure logical interfaces. Logical interfaces are manually
configured interfaces, which are used to exchange data. Logical interfaces do not exist
physically.
2.14 Configuring an Interface Group
An interface group can be used to perform interface configuration in batches, simplifying
interface configurations and reducing management costs.
2.15 Configuring an Interface Monitoring Group
In a dual-device backup scenario, you can configure an interface monitoring group to allow
the user-side interface status to change with the network-side interface status so that traffic
can be switched between the master and backup links.
2.16 Maintaining Interfaces
The reset commands help locate faults on interfaces.
2.17 Configuration Examples for Interface Management
This section provides interface management examples.
Interface Types
The Router exchanges data and interacts with other devices on a network through interfaces.
Interfaces are classified into physical and logical interfaces.
l Physical Interfaces
Physical interfaces physically exist on boards. They are divided into the following types:
– LAN interfaces: interfaces through which the Router can exchange data with the
devices on a LAN.
– WAN interfaces: interfaces through which the Router can exchange data with
remote devices on a WAN.
l Logical Interfaces
Logical interfaces are manually configured interfaces that do not exist physically.
Logical interfaces can be used to exchange data.
NOTICE
The management network port of the IPU does not forward services.
Table 2-1 Command views and prompts of physical interfaces supported by the NE40E
Major link layer protocols supported by the NE40E are listed as follows:
l Ethernet
Currently, the LAN mostly refers to the Ethernet. The Ethernet is a broadcast network,
which is flexible and simple in configuration and is easy to expand. The Ethernet is
widely used.
l Trunk
The trunk technology has the following advantages:
– Bandwidth increase: The bandwidth of an IP-Trunk is the total bandwidth of all
member interfaces.
– Reliability enhancement: When a link fails, other links in the same trunk
automatically take over the services on the faulty link to prevent traffic interruption.
The interface of a Properly plan the interface Other interface types cannot
channelized sub-interface type. be configured.
supports only an Ethernet
interface.
On eTM boards and Plan services properly. When the egress traffic on a
subcards, when the egress channelized sub-interface
traffic on a channelized sub- exceeds its configured
interface exceeds the bandwidth in eTM
configured bandwidth of the scenarios, the statistics are
channelized sub-interface, inaccurate.
the egress traffic is limited
to the bandwidth of the
channelized sub-interface.
In this case, the number of
packets, the number of
bytes, and the rate in the
outbound direction are
incorrect. However, the
statistics on unicast,
broadcast, multicast, and
IPv4/IPv6 dual-stack traffic
are the egress traffic before
the rate limit.
When member interfaces of Set a smaller delay for When member interfaces of
an Eth-Trunk interface are interfaces to go Up on the an Eth-Trunk interface are
located on different chassis inter-chassis interfaces in a located on different chassis
in a virtual cluster, the virtual cluster, and set a in a virtual cluster, the
master chassis is restarted. larger delay for interfaces to master chassis is restarted.
When the master chassis go Up in the system view. When the master chassis
recovers and Eth-Trunk The difference between the recovers and Eth-Trunk
traffic is switched back, a two delays depends on the traffic is switched back, a
small amount of traffic may time for the inter-chassis small amount of traffic may
be discarded. link to become available and be discarded.
is at least 5 minutes.
Configuration command:
carrier up-hold-time
0-86400000
In L2VE access to L3VE Run the set access-ve-mac Layer 2 MAC flapping
scenarios, if an L2VE mac-address command in occurs.
interface and Eth-Trunk the slot view.
interface are bound to the Change the MAC address of
same local VSI, Layer 3 the L3VE interface.
interconnection needs to be
implemented between the Alternatively, run the mac-
Eth-Trunk and L3VE address mac-address
interfaces. The MAC command in the Eth-Trunk
address of the L3VE or Eth- interface view to change the
Trunk interface needs to be MAC address of the Eth-
manually changed. Trunk interface.
Usage Scenario
To ensure smooth communication between devices on a network, configure both physical and
logical interfaces properly and set the following parameters:
l Interface description
l Maximum transmission unit (MTU)
l Trap threshold for the outbound and inbound bandwidth usage on a specified interface
l Interval at which traffic statistics are collected
l Whether the device sends a trap message to the network management system (NMS)
when the interface status changes
l Whether the control-flap function is enabled
Pre-configuration Tasks
Before performing basic configurations on an interface, verify that the device has been
installed and powered on properly.
Procedure
Step 1 Run system-view
In this command, interface-type specifies the type of the interface, and interface-number
specifies the number of the interface.
If the interface of the specified type and number exists in the preceding step, you do not need
to run the commit command.
----End
Context
Table 2-4 describes the configurable parameters of an interface.
Parameter Description
Interface MTU After the MTU is configured for an interface, the device
fragments a packet transmitted on the interface if the size of the
packet exceeds the MTU.
NOTE
Loopback and NULL interfaces do not support the MTU.
Setting of interface You can calculate the bandwidth usage by setting the interface
bandwidth obtained by bandwidth obtained by the NMS from the MIB.
the NMS from the MIB
Whether the device You can enable the device to send a trap message to the NMS
sends a trap message to when the interface status changes. After this function is enabled,
the network the NMS monitors the interface status in real time.
management system When an interface alternates between Up and Down, the device
(NMS) when the will frequently send trap messages to the NMS, which increases
interface status changes the processing load on the NMS. In this situation, you can
disable the device from sending trap messages to the NMS to
avoid adverse impact on the NMS.
Interval at which traffic After setting the interval at which traffic statistics are collected
statistics are collected for an interface, you can view the traffic volumes and rates of the
interface in different time ranges.
Parameter Description
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
In this command, interface-type specifies the type of the interface, and interface-number
specifies the number of the interface.
Step 3 Perform one or more operations in Table 2-5 to set the desired interface parameters.
Operation Description
Set an MTU for an Run the mtu mtu or ipv6 mtu mtu command to set an MTU for
interface. an interface.
The default MTU is 1500 bytes. Run the mtu mtu spread or
ipv6 mtu mtu spread command to set an MTU for an interface
and apply the MTU to all the sub-interfaces on the interface.
NOTE
l After changing the MTU of a interface using the mtu or mtu spread
command, run the shutdown and undo shutdown commands in
sequence in the interface view, or run the restart command alone in
the interface view to restart the interface for the new MTU to take
effect.
l If IPv4 attributes are configured on an interface, run the mtu or mtu
spread command to set an MTU for IPv4 packets to be sent by an
interface.
l If IPv6 attributes are configured on an interface, run the ipv6 mtu or
ipv6 mtu spread command to set an MTU for IPv6 packets to be
sent by an interface.
Set configuration Run the bandwidth command to set configuration bandwidth for
bandwidth for an an interface.
interface. NOTE
To view the command configurations, you can check the ifSpeed and
ifHighSpeed objects in the IF-MIB on the NMS.
Configure whether the Run the enable snmp trap updown command to enable the
device sends a trap device to send a trap message to the NMS when the interface
message to the NMS status changes.
when the interface NOTE
status changes. When an interface alternates between Up and Down, the device will
frequently send trap messages to the NMS, which increases the
processing load on the NMS. In this situation, you can run the undo
enable snmp trap updown command to disable the device from sending
trap message to the NMS to avoid adverse impact on the NMS.
Set the interval at Run the set flow-stat interval interval command to set the
which traffic statistics interval at which traffic statistics are collected.
are collected. NOTE
l To globally set the interval at which traffic statistics are collected, run
the set flow-stat interval interval command in the system view. To
set the interval at which traffic statistics are collected for an interface,
run the interface interface-type interface-number command to
specify an interface and run the set flow-stat interval interval
command on the interface. The global interval applies to all
interfaces for which the interval at which traffic statistics are
collected is not set.
l The new interval takes effect after the original interval expires. For a
logical interface, traffic statistics will be updated after the new
interval takes effect and the first interval expires. For a physical
interface, traffic statistics are updated immediately after the new
interval takes effect.
Operation Description
Enable the control-flap Run the control-flap [ suppress reuse ceiling decay-ok decay-
function. ng ] command to enable the control-flap function on an interface.
The value of suppress is 1000 times the interface suppression
threshold. It ranges from 1 to 20000. The default value is 2000.
The value of suppress must be greater than the value of reuse
and less than the value of ceiling.
The value of reuse is 1000 times the interface reuse threshold. It
ranges from 1 to 20000. The default value is 750. The value of
reuse must be less than the value of suppress.
The value of ceiling is 1000 times the maximum interface
suppression penalty value. It ranges from 1001 to 20000. The
default value is 6000. The value of ceiling must be greater than
the value of suppress.
decay-ok specifies the half life for the penalty value when an
interface is Up. It ranges from 1 to 900, in seconds. The default
value is 54.
decay-ng specifies the half life for the penalty value when an
interface is Down. It ranges from 1 to 900, in seconds. The
default value is 54.
----End
Context
Procedure
l By default, interfaces are started.
l If an interface is shut down, perform the following steps to start the interface:
a. Run system-view
The system view is displayed.
b. Run interface interface-type interface-number
The interface view is displayed.
c. Run undo shutdown
The interface is started.
d. Run commit
The configuration is committed.
----End
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run enable snmp trap physical-updown
The device is enabled to send a trap message to the NMS when the interface physical status
changes.
----End
Context
Do as follows on the Router that needs to be configured with IPv4 and IPv6 traffic statistics.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Run statistic enable
IPv4 and IPv6 traffic statistics about a main interface are collected.
IPv4 and IPv6 traffic statistics about a specified interface are collected.
----End
Context
Figure 2-1 shows the interface layout on a device panel.
l Every four interfaces in the range 0 to 23 and each interface in the range 24 to 29 are
grouped together to share the 100 Gbit/s bandwidth. The interfaces are arranged into the
following six groups: (0–3, 24), (4–7, 25), (8–11, 26), (12–15, 27), (16–19, 28),
and (20–23, 29).
l Each interface in the range 30 to 43 exclusively occupies 100 Gbit/s bandwidth.
The bandwidth of interfaces 0 to 43 is controlled by a license. Table 2-6 shows the default
bandwidth of the interfaces.
24–29 0 0
Because every four interfaces in the range 0 to 23 and each interface in the range 24 to 29 are
grouped together to share the 100 Gbit/s bandwidth, the bandwidth mode of the interfaces in
the range 24 to 29 can be switched using the port split dimension interface command. Table
2-7 uses the group (0–3, 24) as an example to show the supported bandwidth modes.
After licenses are activated for interfaces 30 to 43, the bandwidth is 100 Gbit/s by default.
You can switch the bandwidth to the following modes using the port split dimension
interface command.
2 1 x 40G No No
3 4 x 10G No Yes
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run license
The license view is displayed.
Step 3 Run active port-basic slot slot-id card card-id port port-list
The interface-specific basic hardware license is activated.
To deactivate interface-specific basic hardware license, run the undo active port-basic slot
slot-id card card-id [ port port-list ] command in the license view. After the configuration is
committed, the basic hardware license resources are released.
When configuring the bandwidth mode for interfaces 0 to 29, perform both license activation and
interface splitting on interfaces 24 to 29.
----End
Context
To switch an interface bandwidth mode, configure an interface splitting mode, which
increases the networking flexibility and saves interface costs.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run port split dimension interface { { interface-name1 | interface-type interface-number1 }
[ to { interface-name2 | interface-type interface-number2 } ] } &<1–12> split-type split-
type
Interface splitting is configured.
----End
Procedure
l Run the display interface [ interface-type interface-number ] command to check the
status of the interface and statistics on the interface.
l Run the display control-flap interface interface-type interface-number command to
check the configuration and running status of the control-flap function on interfaces.
l Run the display counters [ bit ] [ inbound | outbound ] [ interface interface-type
[ interface-number ] ] [ slot slot-id ] command to check the interface traffic statistics.
l Run the display counters [ bit ] rate [ inbound | outbound ] [ interface interface-type
[ interface-number | slot slot-id ] | slot slot-id ] command to check the interface traffic
rates.
l Run the display port split or display port split slot command to display the splitting
status of the interface.
l Run the display interface neighbor [ interface-type interface-number | slot slot-id
[ card card-number ] ] command to check information about the neighboring devices
and interfaces of physical interfaces on a device.
----End
Usage Scenario
When plenty of alarms are generated on links, system performance deteriorates because the
system has to process the huge number of alarms. You can set thresholds for different types of
alarms, so that alarms are generated only when the alarm thresholds are reached. In addition,
measures can be taken when necessary to remove faults and guarantee the transmission of
normal traffic.
Pre-configuration Tasks
Before configuring physical link detection, complete the following tasks:
l Powering on the Router, ensuring that the Router works properly and completes self-
check successfully.
l Configure physical attributes for interfaces on the Router.
Context
If the alarm function is enabled on an interface, the system generates an alarm when the
number of errors or bandwidth usage exceeds or falls below the threshold set on the interface.
If the alarm function is disabled, the system does not generate any alarm, no matter whether
the number of errors or bandwidth utilization exceeds or falls below the set threshold. The
configuration takes effect on all physical interfaces supporting the alarm function.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run snmp-agent trap enable port { crcexc-error | input-error | output-error | sdh-error-
rising | optical-module-abnormal }
The alarm function is enabled on interfaces.
The configuration takes effect on all physical interfaces supporting the alarm function.
Different types of alarms can be set on an interface as necessary.
l crcexc-error: Enables the alarm function for CRC errors on an interface.
l sdh-error-rising: Enables the alarm function for SDH errors on an interface.
l optical-module-abnormal: Enables the alarm function for optical module power
exceptions on an interface.
In VS mode, this command is supported only by the admin VS.
Step 3 Run interface interface-type interface-number
The interface view is displayed.
Step 4 Configure thresholds for different types of interface alarms and the alarm intervals.
l Configure the alarm threshold for inbound and outbound bandwidth usage:
– Run trap-threshold { input-rate | output-rate } bandwidth-in-use [ resume-rate
resume-threshold ]
The inbound and outbound bandwidth usage threshold is set.
To prevent alarms from being generated frequently, keep a large difference between
bandwidth-in-use and resume-threshold.
– Run set flow-stat interval interval
The traffic statistic collection interval is set for the interface, in seconds.
The new traffic statistic collection interval takes effect after the original traffic
statistic collection interval expires. If the interface is logical, traffic statistics about
the interface are updated when the new traffic statistic collection interval takes
effect for the second time. If the interface is physical, traffic statistics about the
interface are updated immediately after the new traffic statistic collection interval
takes effect.
The traffic statistic collection interval set on an interface is effective only on the
interface.
You can configure a global traffic statistic collection interval, which takes effect on all
interfaces, including the interfaces on which no traffic statistic collection interval has been
set. To configure a global traffic statistic collection interval, run the set flow-stat interval
interval command in the system view. The traffic statistic collection interval of an interface
takes preference over a global traffic statistic collection interval.
l Configure CRC alarm thresholds and a detection interval (for Ethernet interfaces using
either of the following methods):
– Run trap-threshold crc-error threshold interval-second interval [ shutdown ]
An alarm threshold is set based on a specified interval.
A device will generate an alarm if the number of packets with CRC errors received
within the interval exceeds the configured alarm threshold.
– Run trap-threshold crc-error high-threshold high-threshold low-threshold low-
threshold interval-second interval [ shutdown ]
The upper threshold and lower threshold for generating a CRC alarm, and the
detection interval are set.
You can run the trap-threshold slot slot-id card card-id crc-error high-threshold high-
threshold low-threshold low-threshold interval-second interval command in the system
view to configure global values for all interfaces on the specified subcard.
l Configure SDH alarm thresholds and a detection interval (for 10GE WAN interfaces
using either of the following methods):
– Run trap-threshold sdh-error threshold interval-second interval
An alarm threshold is set based on a specified interval.
A device will generate an alarm if the number of packets with SDH errors received
within the interval exceeds the configured alarm threshold.
– Run trap-threshold sdh-error high-threshold high-threshold low-threshold low-
threshold interval-second interval
The upper threshold and lower threshold for generating an SDH alarm, and the
detection interval are set.
You can run the trap-threshold slot slot-id card card-id sdh-error high-threshold high-
threshold low-threshold low-threshold interval-second interval command in the system
view to configure global values for all interfaces on the specified subcard.
l Configure symbol alarm thresholds and a detection interval (for Ethernet interfaces
only).
You can run the trap-threshold slot slot-id card card-id symbol-error high-threshold
high-threshold low-threshold low-threshold interval-second interval command in the
system view to configure global values for all interfaces on the specified subcard.
l Configure input/output alarm thresholds and a detection interval (for Ethernet
interfaces).
– Run trap-threshold { input-error | output-error } high-threshold high-threshold
low-threshold low-threshold interval-second interval
The upper threshold and lower threshold for generating an interface input or output
alarm are set.
You can run the trap-threshold slot slot-id card card-id symbol-error high-threshold
high-threshold low-threshold low-threshold interval-second interval command in the
system view to configure global values for all interfaces on the specified subcard.
l Configure an alarm threshold and a clear alarm threshold for the CRC error packet ratio:
– Run trap-threshold crc-error packet-error-ratio alarm-threshold coefficient-
value power-value [ resume-threshold coefficient-value power-value ] [ trigger-lsp
| trigger-section ]
An alarm threshold and a clear alarm threshold for the CRC error packet ratio are
set.
l Configure parameters for the algorithm to calculate the CRC packet error ratio:
– Run crc-error packet-error-ratio algorithm-parameter sample-window-factor
child-window-max-number child-window-alarm-number child-window-resume-
number
The parameters are set for the algorithm to calculate the CRC packet error ratio.
l Configure CRC alarm threshold in percentages:
– Run trap-threshold crc-error percent percent-value
The CRC alarm threshold in percentages is set.
l You can run the port-alarm down slot slot-id card card-id { crc-error | sdh-error | symbol-error |
input-error | output-error } command in the system view to apply the configurations to all
interfaces on the subcard.
l After an interface is configured to go Down upon receiving the alarms, you can run the port-alarm
clear { crc-error | sdh-error | symbol-error | input-error | output-error } command to clear the
alarms on the interface.
----End
Context
A device generates an alarm and sends it to an NMS only when the number of pause-frame
error packets sent or received by the device reaches the upper threshold for three consecutive
detection intervals. The device sends a clear alarm to the NMS only when the number of
pause-frame error packets sent or received by the device falls below the lower threshold for
three consecutive detection intervals.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The view of an interface is displayed.
Step 3 Run trap-threshold pause-frame high-threshold high-threshold low-threshold low-
threshold interval-second interval
The upper threshold, lower threshold, and detection interval for the pause-frame error alarm
are set.
Step 4 Run commit
The configuration is committed.
----End
Context
If an interface receives a large number of SDH B1 or SDH B2 error packets, the link is in a
poor condition, affecting service transmission. In this situation, you can configure the alarm
function, alarm threshold, and detection interval on an interface. The system then detects the
number of SDH B1 or SDH B2 error packets that the interface receives at the configured
interval. If the number of SDH B1 or SDH B2 error packets exceeds the configured alarm
threshold, the system generates an alarm and sends it to the NMS, prompting the
administrator to perform maintenance on the interface and troubleshoot the fault. When the
number of SDH B1 or SDH B2 error packets falls below the alarm threshold, the system
generates a clear alarm and sends it to the NMS, notifying the administrator that the alarm has
been cleared.
Procedure
Step 1 Run system-view
The alarm function is configured in case the number of SDH B1 or SDH B2 error packets
exceeds an alarm threshold.
A threshold and detection interval for the SDH B1 or SDH B2 error alarm on an interface are
set.
----End
Context
If an interface receives a large number of bytes of error packets, the link is in a poor
condition, affecting service transmission. In this situation, you can configure the alarm
function, alarm threshold, and detection interval on an interface. The system then detects the
number of bytes of error packets that the interface receives at the configured interval. If the
number of bytes of error packets exceeds the configured alarm threshold, the system generates
an alarm and sends it to the NMS, prompting the administrator to perform maintenance on the
interface and troubleshoot the fault. When the number of bytes of error packets falls below the
alarm threshold, the system generates a clear alarm and sends it to the NMS, notifying the
administrator that the alarm has been cleared.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run snmp-agent trap enable port bad-bytes
The alarm function is configured in case the number of bytes of error packets exceeds an
alarm threshold.
----End
Context
You can check the interface configuration and state information after configuring the physical
link detection function.
Procedure
l Run the display trap-info command in the interface view, or run the display trap-info
{ interface-type interface-number | interface-name | slot slot-id card card-id } command
in the system view to check configuration and state information about the specified
interface, including whether the alarm function is enabled on the interface, alarm
threshold, alarm interval, alarm blocking, current alarm state, and the number of current
alarms.
l Run the display port-error-info interface { interface-type interface-number | interface-
name command in the interface view to check the trap information about error codes/
error packets of an interface.
----End
Usage Scenario
Procedure
Step 1 Run system-view
----End
If you need to re-check MAC accounting statistics after a period, run the reset mac
accounting command to delete the existing statistics and then run the display mac
accounting command. This ensures statistics accuracy.
Usage Scenario
On a BD scenario, the Router has two sub-interfaces configured in a main interface, one with
the Dot1q encapsulation type and the other with the default encapsulation type. Once the sub-
interface encapsulated Dot1q receives traffic, the sub-interface with the default encapsulation
type also sends out the traffic. This may cause the illusion of return current. Besides, the
Router has two interfaces configured on a BD scenario. The first interface has a sub-interface
that is configured with the Dot1q encapsulation type. The second interface has two sub-
interfaces that are configured with the Dot1q and default encapsulation types respectively.
Once traffic passes through the sub-interface on the first interface, the second interface also
sends two copied traffic from each of its sub-interfaces. This causes traffic to be replicated,
wasting resources and reducing the board's forwarding efficiency. To allow traffic to be sent
through specific interfaces, enable strict filter.
Pre-configuration Tasks
Before configuring strict filter on an interface, configure physical attributes for interfaces on
the Router.
Procedure
l Enable strict filter globally.
a. Run system-view
----End
Usage Scenario
After a device is restarted or a board is replaced, if an interface sends signals immediately
after initialization before the link completes a switchover or configuration restoration, data
loss may occur. To prevent data loss, configure the signal sending delay function.
l Only physical interfaces can be configured with signal sending delays. Logical interfaces do not
support this function.
l Configuring a signal sending delay does not affect an interface that has sent signals to the peer, and
the configuration takes effect after the interface is initialized.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Perform either of the following configurations as required.
1. Run interface interface-type interface-number
The GE, 10GE WAN or 10G LAN interface view is displayed.
Step 3 Run port-tx-enabling-delay port-tx-delay-time
The signal sending delay function is enabled, and the signal sending delay is configured.
----End
The preceding command output shows that the signal sending delay configured on GE 0/1/0 is
100 ms and that the interface sends signals in 20 ms.
Usage Scenario
Before locating or troubleshooting a link failure, maintenance engineers should ensure that the
optical module laser is disabled so that it cannot cause injury. The optical module can be
configured to disable the laser automatically if it detects a link failure. The laser can also be
disabled manually. If the optical module is configured to disable the laser automatically, the
laser is not immediately re-enabled when the link failure is cleared. However, maintenance
engineers can enable the optical module laser manually to check whether services have
recovered.
Pre-configuration Tasks
Before enabling or disabling the optical module laser, complete the following tasks:
l Power on the Router.
l Ensure that the optical module has been installed and that the interface is Up.
Context
Before locating or troubleshooting a link failure, maintenance engineers should ensure that the
optical module laser is disabled so that it cannot cause injury. The optical module can be
configured to disable the laser automatically if it detects a link failure. The laser can also be
disabled manually.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number
The interface view is displayed.
Step 3 Perform either of the following operations:
l Configure the optical module to disable the laser automatically.
a. To configure the optical module to disable the laser automatically, run the laser
autoshutdown enable command.
b. (Optional) To configure intervals at which the optical module laser is disabled or
enabled and the system checks for link failures, run the laser auto-shutdown-
interval { open opentime-interval | close closetime-interval } command.
NOTICE
Running the laser turn-off command interrupts services on the interface. Therefore, do
not run the command when the interface is working properly.
----End
Context
If the optical module is configured to disable the laser automatically, the laser is not
immediately re-enabled when the link failure is cleared. However, maintenance engineers can
enable the optical module laser manually to check whether services have recovered.
Procedure
Step 1 Run system-view
The optical module laser is enabled, and the duration for which the optical module laser will
be temporarily enabled is configured.
The duration takes effect only after the laser autoshutdown enable command is run.
----End
Prerequisites
The optical module laser has been enabled or disabled as required.
Context
The following operations affect the status of the optical module laser:
l Run the laser turn-on command to enable the optical module laser.
l Run the laser turn-off command to disable the optical module laser.
l Run the laser autoshutdown enable command to configure the optical module to
disable the laser automatically if it detects a link failure.
l Run the shutdown command to deactivate the interface.
Procedure
l Run the display laser status { interface interface-type interface-number } command in
any view to check the status of the optical module laser.
----End
Context
Enabling alarm threshold standardization implements optical power-related alarm threshold
standardization and changes the mode of obtaining thresholds for sending and receiving
optical power. If the optical-module threshold-standardization enable command is not run,
thresholds are calculated based on data read from the optical module registers, which is the
default mode of obtaining a threshold. If the optical-module threshold-standardization
enable command is run, optical power thresholds use a standardized value that is calculated
based on the optical module transmission distance and bandwidth.
The device has two types of optical module power alarms: warning and alarm. A warning is reported
when the difference between the actual power and vendor-defined threshold is not great. It can also be
considered as a precaution. Some optical modules can continue working properly when the actual optical
power is at the warning level. You can disable the alarm function for these optical modules to prevent
these optical modules from frequently reporting warnings by executing the following command.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run optical-module alarm-threshold standardization enable
The alarm threshold standardization function is enabled for the optical module.
----End
Context
The system automatically obtains the vendor-defined power threshold of an optical module
and compares it with the actual power. If the actual power exceeds the vendor-defined
threshold, an alarm will be generated. Generally, the actual power is greater than the vendor-
defined threshold, which means frequent alarm reporting. It is unfeasible to install an
attenuator on each optical module to prevent frequent reporting of such power alarms. You
can disable the alarm function for the optical module by executing the following command.
The device has two types of optical module power alarms: warning and alarm. A warning is reported
when the difference between the actual power and vendor-defined threshold is not great. It can also be
considered as a precaution. Some optical modules can continue working properly when the actual optical
power is at the warning level. You can disable the alarm function for these optical modules to prevent
these optical modules from frequently reporting warnings by executing the following command.
Procedure
Step 1 Run system-view
----End
Context
When an interface is inserted with a non-Huawei-certified optical module, the system
automatically reports an alarm. If you want to suppress the alarm, you can disable the function
of reporting the alarm for the non-Huawei-certified optical module. If you do not want to use
the interface with the optical module inserted, you can enable the function of setting the
interface to Down.
Procedure
Step 1 Run system-view
----End
Usage Scenario
The flapping of routing protocols, MPLS, and other protocols caused by the frequent change
of the interface status may influence the stability of the whole network. To resolve this
problem, you can configure the control-flap function.
Pre-configuration Tasks
Before configuring the control-flap function, configure the physical attributes for the Router
interfaces.
Procedure
l Configure the control-flap function.
a. Run system-view
The null interface and loopback interface do not support the control-flap function.
c. Run control-flap [ suppress reuse ceiling decay-ok decay-ng ]
The control-flap function is enabled on the interface.
The value of suppress is 1000 times the suppress threshold of the interface. It
ranges from 1 to 20000. The default value is 2000. The value of suppress must be
greater than the value of reuse and smaller than the value of ceiling.
The value of reuse is 1000 times the reuse threshold of the interface. It ranges from
1 to 20000. The default value is 750. The value of reuse must be smaller than the
value of suppress.
The value of ceiling is 1000 times the suppress penalty value of the interface. It
ranges from 1001 to 20000. The default value is 6000. The value of ceiling must be
greater than the value of suppress.
The value of decay-ok is the time taken to decay the penalty value to half when the
interface is Up. It ranges from 1 to 900 seconds. The default value is 54 seconds.
The value of decay-ng is the time taken to decay the penalty value to half when the
interface is Down. It ranges from 1 to 900 seconds. The default value is 54 seconds.
d. Run commit
The configuration is committed.
l Configure the damp-interface function.
a. Run system-view
The system view is displayed.
b. (Optional) Run interface interface-type interface-number
The view of an interface is displayed.
c. Run damp-interface enable
Suppression on interfaces' physical status flappings is enabled.
d. (Optional) Run damp-interface level { light | middle | heavy | manual { half-life-
period suppress reuse max-suppress-time } }
A suppression level is configured for interfaces' physical status flappings.
n light: If light suppression is configured, the system triggers suppression only
when an interface's status flaps frequently and rapidly. The light suppression
level is the default setting and applies to flappings that have the maximum
impact on the system.
n heavy: If heavy suppression is configured, the system triggers suppression
when detecting an interface's status begins to flap, even if the flapping is not
severe. On the heavy suppression level, an interface is prone to be suppressed.
This level applies to services that are sensitive to flappings. Enabling heavy
suppression prevents service interruptions or resource waste caused by
interface flappings.
n middle: Intensity of middle suppression is between the light and heavy levels.
n manual: If light, middle, or heavy suppression cannot meet your requirement,
you can specify manual.
Usage Scenario
For usage scenarios of logical interfaces, see "Logical Interface" in NE40E-Feature
Description-Interface Management.
Pre-configuration Tasks
Before configuring logical interfaces, connect interfaces and set their physical parameters to
ensure that these interfaces are physically up.
Procedure
Step 1 Run system-view
----End
Context
To prevent services from affecting each other, a mechanism to isolate different types of
services is in need. Different service flows are forwarded through specific VLAN channelized
sub-interfaces with dot1q encapsulation. Each channelized sub-interface implements
independent HQoS scheduling to isolate services of different types.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface interface-type interface-number.subinterface-number
The view of a physical sub-interface is displayed.
Step 3 Run vlan-type dot1q
The encapsulation mode of the physical sub-interface is set to dot1q.
Step 4 Run quit
Return to the system view.
Step 5 Run license
The license view is displayed.
----End
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface loopback loopback-number
----End
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run interface null 0
The NULL interface view is displayed.
The NULL interface is always in the Up state but does not forward any data packets. In
addition, IP addresses cannot be configured on the NULL interface, and data link layer
protocol cannot be encapsulated on the NULL interface.
----End
Follow-up Procedure
The NULL interface is used to prevent routing loops and filtering traffic. If the ip route-static
192.168.0.0 255.255.0.0 NULL 0 command is run, the device will discard all packets
destined for the network segments 192.168.0.1 to 192.168.255.255.
Prerequisites
Configuration of the Global-VE interface, Loopback interface or NULL interface is
completed.
Procedure
l Run the display interface global-ve [ ve-number ] command to check the status of the
Global-VE interface.
l Run the display interface loopback [ loopback-number ] command to check the status
of the Loopback interface.
l Run the display interface null [ 0 ] command to check the status of the NULL interface.
----End
Context
Interface groups are classified into permanent and temporary interface groups. Multiple
interfaces can be added to the same permanent or temporary interface group to enable batch
command configurations for the interfaces. The differences between permanent and
temporary interface groups are described as follows:
l After a user exits the view of a temporary interface group, the system automatically
deletes the temporary interface group. A permanent interface group, however, can be
deleted only by using the undo port-group command.
l Information about a permanent interface group can be viewed using the display port-
group command, whereas information about a temporary interface group cannot.
l After a permanent interface group is configured, a configuration file is generated.
However, no configuration file is generated after a temporary interface group is
configured.
Procedure
l Configure a permanent interface group.
a. Run system-view
A permanent interface group is created and the view of the permanent interface
group is displayed.
c. Run group-member { interface-type interface-number1 [ to interface-type
interface-number2 ] } &<1-10>
A temporary interface group is created and specified interfaces are added to the
temporary interface group.
----End
Usage Scenario
In a dual-device backup scenario, when a network-side interface goes Down, user-side
devices cannot detect the Down event and therefore do not switch traffic to the backup link.
As a result, traffic overloads or interruptions occur. To prevent these problems, you can
configure an interface monitoring group to monitor the network-side interface status and
instruct the user-side interface to change its status accordingly. An interface monitoring group
allows traffic to be switched between the master and backup links and prevents traffic
overloads or interruptions.
On the network shown in Figure 2-3, PE2 backs up PE1. NPE1 through NPEM on the user
side is dual-homed to the two PEs to load-balance traffic, and the two PEs are connected to
DeviceA through DeviceN on the network side. When only the link between PE1 and
DeviceN is available and all the links between PE1 and all the other routers fail, the NPEs do
not detect the failure and continue sending packets to DeviceN through PE1. As a result, the
link between PE1 and DeviceN becomes overloaded.
To resolve this problem, you can configure an interface monitoring group and add multiple
network-side interfaces on the PEs to the interface monitoring group. When a link failure
occurs on the network side and the interface monitoring group detects that the status of a
certain proportion of network-side interfaces changes, the system instructs the user-side
interfaces associated with the interface monitoring group to change their status accordingly
and allows traffic to be switched between the master and backup links. Therefore, the
interface monitoring group can be used to prevent traffic overloads or interruptions.
Pre-configuration Tasks
Before configuring an interface monitoring group, configure physical attributes for interfaces
on the Router.
Procedure
Step 1 Run system-view
----End
Context
NOTICE
Statistics cannot be restored after being cleared. Exercise caution when running the following
commands.
Procedure
l To clear the traffic statistics on an interface, run the reset counters interface command
in the user view.
----End
Procedure
l Run the monitor interface-statistics interface-type interface-number &<1-5> [ interval
interval-value | times { times-value | infinity } ] * command in any view to check traffic
statistics on a specified interface.
l Run the monitor interface-statistics batch [ interface-type [ interface-number-begin
[ to interface-number-end ] ] ] [ interval interval-value | times { times-value |
infinity } ] * [ main ] command in any view to check traffic statistics on interfaces in a
batch.
l Run the monitor interface-information interface interface-type interface-number
[ interval interval-value | times { times-value | infinity } ] * command in any view to
check detailed information, including the running status and traffic statistics, on a
specified interface.
l Run the monitor counters bit [ rate ] interface interface-type interface-number
[ interval interval-value | times { times-value | infinity } ] * command in any view to
monitor traffic statistics on an interface. The traffic statistics include the number of
unicast, multicast, and broadcast packets sent or received by the interface and the packet
transmission rate.
----End
Networking Requirements
To ensure smooth communication between devices on a network, you need to configure both
physical and logical interfaces properly and set the following parameters:
l Interface description
l MTU
l Trap threshold for the outbound and inbound bandwidth usage on a specified interface
l Interval at which traffic statistics are collected
l Whether the device sends a trap message to the network management system (NMS)
when the interface status changes
l Whether the control-flap function is enabled
Configuration Roadmap
The configuration roadmap is as follows:
Data Preparation
To complete the configuration, you need the following data:
l Interface name
l Interface description
l Interface MTU
l Interval at which traffic statistics are collected globally
l Sub-interface MTU
Procedure
Step 1 Configure description for an interface.
<HUAWEI> system-view
[~HUAWEI] interface gigabitethernet 0/2/0
[~HUAWEI-GigabitEthernet0/2/0] description for IFM
[*HUAWEI-GigabitEthernet0/2/0] commit
Step 3 Set the interval at which traffic statistics are collected globally.
[*HUAWEI] set flow-stat interval 100
[*HUAWEI] commit
----End
Configuration Files
#
sysname HUAWEI
#
set flow-stat interval 100
#
interface gigabitethernet0/2/0
description for IFM
mtu 1000
#
interface gigabitethernet0/2/0.1
mtu 800
#
return