CloudEngine 6800&5800 V100R001C00 Configuration Guide - Interface Management 04 PDF

CloudEngine 6800&5800 Series Switches
V100R001C00
Configuration Guide - Interface
Management
Issue 04
Date 2013-07-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
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.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://enterprise.huawei.com
Issue 04 (2013-07-10) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Intended Audience
This document provides the basic concepts and configuration procedures of the interfaces
supported by the device.
This document is intended for:
l Data configuration engineers
l Commissioning engineers
l Network monitoring engineers
l System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
DANGER
Indicates a hazard with a high level or medium level of risk
which, if not avoided, could result in death or serious injury.
WARNING
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
CAUTION
Indicates a potentially hazardous situation that, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
TIP
Provides a tip that may help you solve a problem or save time.
NOTE
Provides additional information to emphasize or supplement
important points in the main text.

Command Conventions
The command conventions that may be found in this document are defined as follows.
Configuration Guide - Interface Management About This Document
ii
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }
*
Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]
*
Optional items are grouped in brackets and separated by
vertical bars. You can select one or several items, or select
no item.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.

Interface Numbering Conventions
Interface numbers used in this manual are examples. In device configuration, use the existing
interface numbers on devices.
Change History
Changes between document issues are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Changes in Issue 04 (2013-07-10)
This version has the following updates:
The following information is modified:
l 2.2 Ethernet Interface Features
l 2.5.1 Configuring the 40GE/10GE Interface Mode
iii
l 2.5.6 Configuring Interface Isolation
Initial commercial release.
iv
Contents
About This Document.....................................................................................................................ii
1 Basic Configuration for Interfaces.............................................................................................1
1.1 Interface Overview.........................................................................................................................................................2
1.2 Interface Features...........................................................................................................................................................3
1.3 Configuring Basic Interface Parameters.........................................................................................................................5
1.3.1 Entering the Interface View.........................................................................................................................................5
1.3.2 Configuring an Interface Description..........................................................................................................................5
1.3.3 Configuring the Traffic Statistics Collection Interval.................................................................................................6
1.3.4 Enabling or Disabling an Interface..............................................................................................................................7
1.3.5 Checking the Configuration.........................................................................................................................................8
1.4 Maintaining Interfaces....................................................................................................................................................9
1.4.1 Clearing Interface Traffic Statistics.............................................................................................................................9
2 Ethernet Interfaces Configuration............................................................................................10
2.1 Ethernet Interface Overview.........................................................................................................................................11
2.2 Ethernet Interface Features...........................................................................................................................................11
2.3 Default Configuration...................................................................................................................................................14
2.4 Configuring a Port Group.............................................................................................................................................16
2.5 Configuring Ethernet Interfaces...................................................................................................................................17
2.5.1 Configuring the 40GE/10GE Interface Mode...........................................................................................................17
2.5.2 Configuring Virtual Cable Test.................................................................................................................................19
2.5.3 Configuring the Auto-Negotiation Function.............................................................................................................20
2.5.4 Configuring Interface Rate........................................................................................................................................21
2.5.5 Configuring the Flow Control Function....................................................................................................................22
2.5.6 Configuring Interface Isolation.................................................................................................................................23
2.5.7 Configuring the IFG..................................................................................................................................................25
2.5.8 Configuring an Interface to Allow Jumbo Frames....................................................................................................25
2.5.9 Configuring the Delay in Reporting Interface Status Changes.................................................................................26
2.5.10 Configuring the Alarm Thresholds of the Outbound/Inbound Bandwidth Usage...................................................27
2.5.11 Configuring the Alarm Threshold of CRC-Error Packets.......................................................................................27
2.5.12 Configuring the EEE function.................................................................................................................................28
2.5.13 Configuring Interface Traffic Statistics to Include Inter-frame Gaps.....................................................................29
2.5.14 Configuring the Link Flapping Protection Function...............................................................................................29
Configuration Guide - Interface Management Contents
v
2.5.15 Configuring an Interface to Transit to the Error-Down State When the Optical Power Is Low.............................31
2.5.16 Configuring an Interface to Transit to the Error-Down State When the Number of Received CRC Error Packets
Exceeds the Threshold........................................................................................................................................................31
2.5.17 Checking the Configuration.....................................................................................................................................32
2.6 Maintaining Ethernet Interfaces...................................................................................................................................33
2.6.1 Configuring Loopback Detection..............................................................................................................................33
2.6.2 Clearing Interface Statistics.......................................................................................................................................34
2.7 Configuring Examples..................................................................................................................................................35
2.7.1 Example for Configuring Interface Isolation.............................................................................................................35
3 Logical Interface Configuration................................................................................................38
3.1 Introduction to Logical Interfaces................................................................................................................................39
3.2 Configuring a Loopback Interface................................................................................................................................39
3.3 Configuring a NULL Interface.....................................................................................................................................40
Configuration Guide - Interface Management Contents
vi
1 Basic Configuration for Interfaces
About This Chapter
This section interface types, interface numbering rules, and configuration parameters to facilitate
interface management.
1.1 Interface Overview
This section describes the interface types and numbering rules.
1.2 Interface Features
This section describes the management interfaces, physical interfaces, and logical interfaces
1.3 Configuring Basic Interface Parameters
This section describes how to configure basic interface parameters, including interface
description and traffic statistics collection interval, and how to shut down and enable an interface.
1.4 Maintaining Interfaces
To view statistics about traffic sent and received on an interface within a period, first clear
existing traffic statistics on the interface.
Configuration Guide - Interface Management 1 Basic Configuration for Interfaces
1
1.1 Interface Overview
This section describes the interface types and numbering rules.
Interface Type
Interfaces of a device are used to exchange data and interact with other network devices.
Interfaces are classified into management interface, physical interface, and logical interfaces.
l Management interfaces
Management interfaces are used to log in to devices. Users can use management interfaces
to configure and manage devices. Management interfaces do not transmit service data.
l Physical interfaces
Physical interfaces exist on interface cards and transmit service data.
l Logical interfaces
Logical interfaces are manually configured and do not physically exist. They can be used
to exchange data and transmit service data.
NOTE
Physical interfaces are sometimes called ports. This document uses the term interface.
Management Interface Numbering Rules
The switch supports console and MEth management interfaces.
The following table lists the numbers of the management interfaces.
Table 1-1 Management interface numbers
Interface Number
Console interface console 0
MEth interface MEth 0/0/0

Physical Interface Numbering Rules
Physical interfaces are numbered in the following way:
CloudEngine 6800&5800 Series switches use the slot ID/subcard ID/interface sequence number
to identify physical interfaces.
l Slot ID: indicates the ID of a device in a stack. CloudEngine 6800&5800 Series switches
support a maximum of 4 member devices in a stack, so the slot ID ranges from 1 to 4.
l Subcard ID: indicates the ID of the subcard that the card supports. The card does not support
any subcard, so the value is 0.
l Interface sequence number: indicates the sequence number of an interface on the device.
2
Table 1-2 Physical interface numbering rule
Numbering Diagram Description
1
2
3
4
5
6
...
...
...
There are two rows of service interfaces on the
device. These interfaces are numbered from top to
bottom and left to right, starting from 1.
For example, the interface on the top left is
numbered 1/0/1.

However, there is an exception. You can split a 40GE interface on the CE6800 series switches
into four 10GE interfaces. After a 40GE interface is split into four 10GE interfaces, the four
physical interfaces are numbered as follows:
If the 40GE interface is numbered 40GE x/0/n, the 10GE interfaces are numbered 10GE x/0/[48
+ 4(n - 1) + z].
l x: indicates the stack ID.
l n: indicates the sequence number of a 40GE interface, starting from 1.
l z: indicates the interface location. The value ranges from 1 to 4.
For example: on a single switch, if a 40GE interface is numbered 1/0/1, the 10GE interfaces are
numbered 1/0/49, 1/0/50, 1/0/51, and 1/0/52.
1.2 Interface Features
This section describes the management interfaces, physical interfaces, and logical interfaces
Management Interfaces
NOTE
This document provides only configuration of physical and logical interfaces. For the configuration of
management interfaces, see the CloudEngine 6800&5800 Series Switches Configuration Guide -- Basic
Configurations.
Table 1-3 describes the management interfaces.
Table 1-3 Description of management interfaces
Interface Description Application
Console
interface
A data connection equipment
(DCE) interface that complies with
the EIA/TIA-232 standard.
The console interface is connected to the
COM serial interface of a configuration
terminal to set up an on-site configuration
environment.
MEth
interface
Complies with the 10/100BASE-
TX standard.
The MEth interface can be connected to
the network interface of the configuration
terminal or network management
workstation, setting up on-site or remote
configuration environments.
3

Physical Interfaces
Table 1-4 describes the physical interfaces that the switch supports.
Table 1-4 Description of physical interfaces
Interface Description
GE electrical interface A LAN-side GE electrical interface works at the data link
layer, provides a maximum of 1000 Mbit/s transmission
rate, processes Layer 2 protocol packets, and implements
Layer 2 forwarding.
10GE electrical interface A LAN-side 10GE electrical interface works at the data link
layer, provides a maximum of 10 Gbit/s transmission rate,
processes Layer 2 protocol packets, and implements Layer
2 forwarding.
10GE optical interface A LAN-side 10GE optical interface works at the data link
2 forwarding.
40GE optical interface A LAN-side 40GE optical interface works at the data link
2 forwarding. A 40GE optical interface can work as an
independent interface or be split into four 10GE optical
interfaces.

Logical Interfaces
Table 1-5 describes the logical interfaces that the switch supports.
Table 1-5 Description of logical interfaces
Eth-Trunk interface
An Eth-Trunk interface is formed by binding multiple Ethernet
interfaces to provide more bandwidth and higher transmission
reliability.
VLANIF interface A VLANIF interface has Layer 3 features and enables VLANs to
communicate after being assigned an IP address.
Stack interface A stack interface is a logical interface used to implement the
stacking function. The stacking function virtualizes multiple
switches into a logical switch to provide massive data forwarding
and improve network reliability in data centers.
4
Loopback interface A loopback interface is always Up and can be configured with a
32-bit subnet mask.
NULL interface A null interface is used to filter routes because any data packets
received by the null interface are discarded.

1.3 Configuring Basic Interface Parameters
This section describes how to configure basic interface parameters, including interface
description and traffic statistics collection interval, and how to shut down and enable an interface.
1.3.1 Entering the Interface View
Context
To configure an interface, enter the interface view.
Procedure
Step 1 Run:
system-view
The system view is displayed.
Step 2 Run:
interface interface-type interface-number
The interface view is displayed.
interface-type interface-number specifies the type and number of an interface.
NOTE
If the specified interface does not exist, this command creates the interface and displays the interface view.
Step 3 (Optional) Run:
commit
The configuration is committed.
You do not need to run this command if you only want to enter the interface view.
----End
1.3.2 Configuring an Interface Description
Context
To facilitate device management and maintenance, you can configure descriptions for interfaces.
An interface description can contain the device where the interface is located, interface type,
and remote device. For example: To-[DeviceB]10GE-1/0/1 indicates that an interface of this
device is connected to 10GE1/0/1 of device B.
5
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
description description
The description is configured for the interface.
By default, an interface has no description.
NOTE
The interface description is displayed from the first non-space character.
Step 4 Run:
commit
----End
1.3.3 Configuring the Traffic Statistics Collection Interval
Context
By setting the traffic statistics collection interval, you can collect and analyze packet statistics.
According to traffic statistics, you can take measures to prevent network congestion and service
interruption.
l When congestion occurs, you can set the statistics collection interval on an interface to 300
seconds or less (30 seconds if congestion worsens). Then observe traffic distribution on the
interface within a short period of time. Take measures to data packets that cause congestion
to control the rate of the packets.
l When the network bandwidth is sufficient and services are running properly, set the
statistics collection interval on an interface to more than 300 seconds. If traffic parameters
on an interface are out of the specified range, change the statistics collection interval to
observe the traffic statistics in real time.
NOTE
l The interval set in the system view takes effect on all the interfaces that use the default interval.
l The interval set in the interface view takes effect only on this interface.
l The interval set in the interface view takes precedence over the interval set in the system view.
Procedure
l Configure the global traffic statistics collection intervals in the system view.
1. Run:
system-view
6
2. Run:
set flow-stat interval interval-time
The global traffic statistics collection interval is set.
By default, the global traffic statistics collection interval is 300s.
3. Run:
commit
l Configure the traffic statistics collection interval on an interface.
1. Run:
system-view
2. Run:
3. Run:
set flow-stat interval interval-time
The traffic statistics collection interval is set on the interface.
By default, the traffic statistics collection interval on an interface is 300s.
4. Run:
commit
----End
1.3.4 Enabling or Disabling an Interface
Context
After modifying parameters of an interface, run the shutdown and undo shutdown commands,
or run the restart command to make the modification take effect.
When an interface is not connected to a cable or a fiber, disable the interface using the
shutdown command to prevent exceptions caused by interference.
NOTE
l Running the shutdown and undo shutdown commands is equivalent to running the restart command.
l A NULL interface is always Up and cannot be enabled or disabled by commands.
l A loopback interface is always Up and cannot be enabled or disabled by commands.
Procedure
l Disable an interface.
1. Run:
system-view
7
2. Run:
3. Run:
shutdown
The interface is disabled.
By default, an interface is enabled.
4. Run:
commit
l Enable an interface.
1. Run:
system-view
2. Run:
3. Run:
undo shutdown
The interface is enabled.
By default, an interface is enabled.
4. Run:
commit
----End
1.3.5 Checking the Configuration
Procedure
l Run the display interface [ interface-type [ interface-number ] ] command to check
information about an interface, including interface running status, basic interface
configuration, and packet forwarding on the interface.
l Run the display interface brief command to check brief information about interfaces,
including the physical status, protocol status, bandwidth usage in the inbound and outbound
directions during a certain period, and the number of error packets sent and received.
l Run the display ip interface [ interface-type interface-number ] command to check the IP
configuration of an interface.
l Run the display default-parameter interface interface-type interface-number command
to check the default configuration of an interface.
l Run the display interface description [ interface-type [ interface-number ] ] command to
check the description of an interface.
8
l Run the display interface [ interface-type [ interface-number ] ] counters [ inbound |
outbound ] command to check traffic statistics on a physical interface.
l Run the display interface [ interface-type [ interface-number ] ] counters rate
[ inbound | outbound ] command to check the inbound and outbound traffic rates on an
interface.
----End
1.4 Maintaining Interfaces
To view statistics about traffic sent and received on an interface within a period, first clear
existing traffic statistics on the interface.
1.4.1 Clearing Interface Traffic Statistics
Context
To monitor the status of an interface or locate faults on the interface, collect traffic statistics on
the interface. Before collecting traffic statistics on an interface within a period, clear the existing
traffic statistics on this interface.
CAUTION
Interface statistics cannot be restored after they are cleared. Confirm your action before you
perform the operations.
Procedure
l Run the reset counters interface [ interface-type [ interface-number ] ] command to clear
the interface statistics.
----End
9
2 Ethernet Interfaces Configuration
About This Chapter
Ethernet is flexible, simple, and easy to implement, and therefore it becomes an important local
area network (LAN) networking technology. You need to configure Ethernet interfaces when
using Ethernet technology to establish LANs.
2.1 Ethernet Interface Overview
This section describes the classification of Ethernet interfaces.
2.2 Ethernet Interface Features
This section describes the Ethernet interface features supported by the CE series switches.
2.3 Default Configuration
This section describes the default configuration of common Ethernet interface parameters.
2.4 Configuring a Port Group
Port groups can reduce interface configuration workload.
2.5 Configuring Ethernet Interfaces
This section describes how to configure Ethernet interface parameters, such as the interface
rate, auto-negotiation function, and network cable type.
2.6 Maintaining Ethernet Interfaces
This section describes how to maintain Ethernet interfaces, including using the loopback
function to check the interface and deleting interface statistics.
2.7 Configuring Examples
This section provides Ethernet interface configuration examples, including network
requirements, configuration roadmap, configuration procedure, and configuration files.
Configuration Guide - Interface Management 2 Ethernet Interfaces Configuration
10
2.1 Ethernet Interface Overview
This section describes the classification of Ethernet interfaces.
Ethernet interfaces are provided by the CE series switches to transmit and receive data, and for
users to perform operations and configurations.
Based on interface rates, Ethernet interfaces of the CloudEngine 6800&5800 Series switches
can be classified into:
l GE interfaces
l 10GE interfaces
l 40GE interfaces
Based on electrical attributes, Ethernet interfaces of the CloudEngine 6800&5800 Series
switches can be classified into:
l Electrical interfaces
l Optical interfaces
2.2 Ethernet Interface Features
This section describes the Ethernet interface features supported by the CE series switches.
Ethernet interface features
Table 2-1 lists the Ethernet interface types and features supported by the device.
Table 2-1 Ethernet interface types and features supported by the device
Interface Medium Rate
(Mbit/s)
Auto-
Negotiation
Flow
Contr
ol
Flow
Control
Auto-
Negoti
ation
Dupl
ex
Mode
GE
electrical
interface
CAT-5
twisted pair
l 10
l 100
l 1000
Auto-negotiation
(can be set to non-
auto negotiation)
Y Y Full-
duple
x
10GE
electrical
interface
Enhanced
CAT-6A
twisted pair
l 100
l 1000
l 10000
Auto-negotiation
(can be set to non-
auto negotiation)
Y Y
10GE
optical
interface
SFP+ optical
module
10,000 Non-auto
negotiation
(cannot be set to
auto-negotiation)
Y N
11
Interface Medium Rate
(Mbit/s)
Auto-
Negotiation
Flow
Contr
ol
Flow
Control
Auto-
Negoti
ation
Dupl
ex
Mode
Twinax cable 10,000 Non-auto
negotiation
(cannot be set to
auto-negotiation)
Y N
SFP-GE
optical
module
1000 Auto-negotiation
(can be set to non-
auto negotiation)
Y N
SFP-GE
electrical
module
1000 Auto-negotiation
(cannot be set to
non-auto
negotiation)
Y N
40GE
optical
interface
QSFP+
optical
module
40,000 Non-auto
negotiation
(cannot be set to
auto-negotiation)
Y N
Twinax cable 40,000 Auto-negotiation
(cannot be set to
non-auto
negotiation)
N

NOTE
Y indicates supported. N indicates not supported.
The CE5800 series switches do not support 10GE electrical interfaces, and the CE6800 series switches do
not support GE electrical interfaces.
The Ethernet interfaces of CE series switches all work in full-duplex mode and do not support the half-
duplex mode.
The auto-negotiation capability of 10GE optical interfaces varies according to the optical modules installed.
Therefore, the auto-negotiation mode configured on the interface may be different from the one that takes
effect. You can run the display this interface command to check the auto-negotiation mode that takes
effect on the interface.
Port Group
The port group function of the CE series switches allow you to configure multiple interfaces at
the same time. A command executed in the port group view applies to all the interfaces in the
port group, reducing your workload.
Auto-negotiation
The auto-negotiation function allows interfaces on both ends of a link to select the same operating
parameters by exchanging capability information. Each interface sends its capability information
to the remote end and checks capabilities of the remote end. After both interfaces receive the
12
capability information from each other, they use the highest capability they support to
communicate with each other.
The interfaces negotiate the speed and flow control parameters. When the negotiation succeeds,
the interfaces use the same speed and flow control parameters.
Flow Control
After flow control is enabled on the local and the remote devices, the local device sends a pause
frame to the remote device to request it to stop sending packets if the local device is congested.
After receiving the pause frame, the remote device temporarily stops sending packets to the local
device.
Splitting One 40GE Interfaces into Four 10GE Interfaces
A 40GE interface on the CE6800 series switches can function as an independent interface or be
split into four 10GE interfaces. You only need to purchase a device to use 40GE interfaces on
the device or split a 40GE interface into four 10GE interfaces, which improves networking
flexibility and saves costs.
VCT
You can use the virtual cable test (VCT) function to check whether the cable on an interface is
faulty. If the cable is normal, the VCT test result displays the cable length. If the cable is faulty,
the VCT test result displays the type and location of the failure point to help in troubleshooting.
The VCT function can verify whether a link failure is caused by a cable fault. Virtual cable tests
cause temporary service interruption. You are not advised to perform a virtual cable test when
services are running normally.
Interface Loopback
Loopback tests can verify that an interface is working normally. The interface cannot transmit
data packets during a loopback test. Interfaces of the CloudEngine 6800&5800 Series switches
support internal loopback tests. During an internal loopback test, the device creates a self-loop
in the PHY chip. The tested interface sends testing packets, which are then sent back to the
interface through the self-loop in the PHY chip. You can use this function to check whether any
module related to the interface is faulty.
Interface Isolation
To implement Layer 2 isolation between interfaces, you can add different interfaces to different
VLANs, which wastes VLAN resources.
Interface isolation can isolate interfaces in the same VLAN. You can add interfaces to an
interface isolation group so that they will not send Layer 2 packets to each other. The isolation
is bidirectional. For example, if you isolate interface A from interface B, packets sent from
interface A cannot reach interface B, and packets sent from interface B cannot reach interface
A.
The isolation can also be unidirectional. For example, if you isolate interface A from interface
B, packets sent from interface A cannot reach interface B, but packets sent from interface B can
reach interface A.
Interface isolation provides secure and flexible networking schemes.
13
2.3 Default Configuration
This section describes the default configuration of common Ethernet interface parameters.
Table 2-2 Default configuration of GE electrical interfaces
Parameter Default Value
Auto-negotiation Auto-negotiation (can be set to non-auto negotiation)
Duplex Mode Full-duplex
Rate l Auto-negotiation mode: negotiated by the local and
remote interfaces
l Non-auto-negotiation mode: 1 Gbit/s
Maximum Frame Length
(Bytes)
9216
MDI Auto
EEE Disabled
(EEE is configurable only when an interface works in auto-
negotiation mode.)
Shutdown Or Not No
Internal Loopback Disabled
Flow Control l Auto-negotiation mode: negotiated by the local and
remote interfaces
l Non-auto-negotiation mode: disabled

Table 2-3 Default configuration of 10GE electrical interfaces
Auto-negotiation Auto-negotiation (can be set to non-auto negotiation)
Rate l Auto-negotiation mode: negotiated by the local and
remote interfaces
l Non-auto-negotiation mode: 10 Gbit/s
(Bytes)
9216
MDI Auto
14
EEE Disabled
(EEE is configurable only when an interface works in auto-
negotiation mode.)
Shutdown Or Not No
Flow Control l Auto-negotiation mode: negotiated by the local and
remote interfaces
l Non-auto-negotiation mode: disabled

Table 2-4 Default configuration of 10GE optical interfaces
Auto-negotiation l With a SFP-GE optical module installed: Auto-
negotiation (can be set to non-auto negotiation)
l With a SFP-GE copper module installed: Auto-
negotiation (cannot be set to non-auto negotiation)
l With a SFP+ optical module installed: Non-auto
negotiation (cannot be set to auto-negotiation)
l With a 10GE cable connected: Non-auto negotiation
(cannot be set to auto-negotiation)
Rate l With a SFP-GE optical module installed: 1 Gbit/s (not
configurable)
l With a SFP-GE copper module installed: 1 Gbit/s (not
configurable)
l With a SFP+ optical module installed: 10 Gbit/s (not
configurable)
l With a 10GE cable connected: 10 Gbit/s (not
configurable)
(Bytes)
9216
Shutdown Or Not No
Flow Control Disabled

15
Table 2-5 Default configuration of 40GE optical interfaces
Auto-negotiation l With a 40GE optical module installed: Non-auto
negotiation (cannot be set to auto-negotiation)
l With a 40GE cable connected: Auto-negotiation (cannot
be set to non-auto negotiation)
Rate l With a 40GE optical module installed: 40 Gbit/s (not
configurable)
l With a 40GE cable connected: 40 Gbit/s (not
configurable)
(Bytes)
9216
Shutdown Or Not No
Flow Control Disabled

NOTE
The CE5800 series switches do not support 10GE electrical interfaces, and the CE6800 series switches do
not support GE electrical interfaces.
The Ethernet interfaces of CE series switches all work in full-duplex mode and do not support the half-
duplex mode.
The auto-negotiation capability of 10GE optical interfaces varies according to the optical modules installed.
Therefore, the auto-negotiation mode configured on the interface may be different from the one that takes
effect. You can run the display this interface command to check the auto-negotiation mode that takes
effect on the interface.
2.4 Configuring a Port Group
Port groups can reduce interface configuration workload.
Context
To perform the same configuration on multiple Ethernet interfaces, add these Ethernet interfaces
to a port group and run commands in the port group view to configure the Ethernet interfaces in
batches. This reduces the configuration workload.
You can configure the following port groups:
l Permanent port group
l Temporary port group
If you exit from a temporary port group view, the system automatically deletes the group.
16
Procedure
l Configuring a permanent port group
1. Run:
system-view
2. Run:
port-group port-group-name
A permanent port group is created, and the port group view is displayed.
3. Run:
group-member { interface-type interface-number1 [ to interface-type
interface-number2 ] } &<1-10>
An Ethernet interface is added to the permanent port group.
4. Run:
commit
l Configuring a temporary port group
1. Run:
system-view
2. Run:
port-group group-member { interface-type interface-number1 [ to interface-
type interface-number2 ] } &<1-10>
A temporary port group is created, and the port group view is displayed.
3. Run:
commit
----End
Checking the Configuration
Run the display port-group [ all | port-group-name ] command to check information about a
permanent port group and interfaces in the group.
2.5 Configuring Ethernet Interfaces
This section describes how to configure Ethernet interface parameters, such as the interface
rate, auto-negotiation function, and network cable type.
2.5.1 Configuring the 40GE/10GE Interface Mode
Context
A 40GE interface on the CE6800 series switches can function as an independent interface or be
split into four 10GE interfaces. You only need to purchase a device to use 40GE interfaces on
the device or split a 40GE interface into four 10GE interfaces, which improves networking
flexibility and saves costs.
When you split one 40GE interface into four 10GE interfaces, the 40GE interface no longer
exists, and the four 10GE interfaces have the same configuration and features as common 10GE
17
optical interfaces except for the numbering rules. For details about interface numbering rules,
see 1.1 Interface Overview. After a local 40GE interface is split, the 40GE interface needs to
connect to the remote 40GE interface using a one-to-four cable. If the remote 40GE interface is
also split, the local and remote 40GE interfaces can have the same 40GE Quad Small Form-
Factor Pluggable Plus (QSFP+) optical modules installed and connect using a fiber. The one-
to-four cable is not required in this case.
CAUTION
40GE interfaces on the CE5800 series switches cannot be split.
The existing configuration will be deleted if you split a 40GE interface or merge the converted
10GE interfaces. Confirm your action before you perform the operations.
Procedure
l
1. Run:
system-view
2. Run:
port split interface 40ge interface-number1 [ to interface-type interface-
number2 ]
One or more 40GE interfaces are split into 10GE interfaces.
By default, a 40GE interface is used as an independent interface.
3. Run:
commit
l Merging 10GE interfaces into 40GE interfaces
1. Run:
system-view
2. Run:
undo port split interface 40ge interface-number1 [ to interface-type
interface-number2 ]
10GE interfaces are merged into 40GE interfaces.
3. Run:
commit
18
NOTE
When you finish the operation, save the configurations and restart the device for the configurations
to take effect.
After interface split is configured on a 40GE interface, the 40GE interface or 10GE interfaces
converted from the 40GE interface cannot be added to a stack interface, regardless of whether the
configuration takes effect. If a 40GE interface has been added to a stack interface, the 40GE interface
cannot be split.
When a 40GE interface on the local device is not split and connects to four 10GE interfaces on the
remote device through a one-to-four cable, the local 40GE interface cannot go Up and the indicator
is off; the four 10GE interfaces on the remote device can go Up and their indicators are steady on.
When 40GE interfaces on a stacked CE6800 switch are split into 10GE interfaces, the CE6800 switch
is removed from the stack, and a new CE6800 switch of the same model and stack ID is added to the
stack, the interface split configuration is restored on the new switch and the service configuration on
the converted 10GE interfaces is retained.The devive automatically delivers the configuration to the
new card without manual intervention. The time taken to start the card is longer than the time normally
used to start a card.
----End
2.5.2 Configuring Virtual Cable Test
Context
Virtual cable test (VCT) technology uses time domain reflectometry (TDR) to detect the cable
status. When a pulse is transmitted to the end of a cable or a failure point in the cable, some
pulse energies are reflected to the transmitting end. The VCT algorithm measures the time spent
on transmitting pulses over a cable, reaching a failure point, and returning the pulses. The
measured time is converted to the distance.
VCT can detect the fault type of a network cable and identify failure points to help locate network
cable faults.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
virtual-cable-test
The VCT function is configured.
19
NOTE
l Only electrical interfaces support the VCT configuration.
l The test result is only for reference and may be inaccurate for cables from some vendors.
l Running the virtual-cable-test command may affect services on the interface in a short period of time.
l Before performing a virtual cable test, shut down the remote interface or remove the network cable
between the local and remote interfaces. Otherwise, signals from the remote interface may make the
test result inaccurate.
----End
2.5.3 Configuring the Auto-Negotiation Function
Context
The auto-negotiation function allows interfaces on both ends of a link to select the same operating
parameters by exchanging capability information. The parameters include the duplex mode and
rate. When the negotiation succeeds, the two interfaces use the same duplex mode and work at
the same rate. In non-auto negotiation mode, the operating parameters must be set manually.
For details about the auto-negotiation configuration supported by Ethernet interfaces, see 2.2
Ethernet Interface Features.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Configure the auto-negotiation function.
l Run:
negotiation disable
The Ethernet interface is configured to work in non-auto negotiation mode.
l Run:
undo negotiation disable
The Ethernet interface is configured to work in auto-negotiation mode.
For the default auto-negotiation mode of an Ethernet interface, see 2.3 Default
Configuration.
NOTE
The interfaces on both ends of a link must have the same negotiation mode.
Step 4 Run:
commit
----End
20
2.5.4 Configuring Interface Rate
Context
For details about the rates that Ethernet interfaces support, see 2.2 Ethernet Interface
Features.
You can configure the rates of GE and 10GE electrical interfaces in auto- and non-auto
negotiation modes.
l In auto-negotiation mode, interfaces on both ends negotiate their rate. You can set the rate
auto-negotiation function to limit the negotiated rate.
l In non-auto negotiation mode, you can set interface rates.
NOTE
10GE optical interfaces and 40GE optical interfaces do not support the rate configuration.
Procedure
You can perform the following operations to configure the GE and 10GE electrical interfaces:
l In the auto-negotiation mode
1. Run:
system-view
2. Run:
The Ethernet interface view is displayed.
3. GE electrical interface
Run:
speed auto { 10 | 100 | 1000 }
*
The rate auto-negotiation function is configured for the GE electrical interface.
10GE electrical interface
Run:
speed auto { 100 | 1000 | 10000 }
*
The rate auto-negotiation function is configured for the 10GE electrical interface.
4. Run:
commit
l In the non-auto negotiation mode
1. Run:
system-view
2. Run:
3. Run:
negotiation disable
21
The Ethernet interface is configured to work in non-auto negotiation mode.
4. GE electrical interface
Run:
speed { 10 | 100 | 1000 }
The rate of the GE electrical interface is configured.
10GE electrical interface
Run:
speed { 100 | 1000 | 10000 }
The rate of the 10GE electrical interface is configured.
5. Run:
commit
By default, an Ethernet interface works at its maximum rate.
2.5.5 Configuring the Flow Control Function
Context
Network congestion causes packet loss. Flow control is a method to prevent packet loss. If
network congestion occurs on the local device, the local device sends a message to the remote
device, instructing the remote device to reduce the packet sending rate. After receiving the
message, the remote device reduces its packet sending rate, which prevents congestion.
GE and 10GE electrical interfaces support flow control and flow control auto-negotiation. The
two negotiation functions cannot be enabled simultaneously on an interface.
Procedure
l Configuring the flow control function
1. Run:
system-view
2. Run:
3. Run:
flow-control
The flow control function is enabled.
By default, flow control is disabled on an Ethernet interface.
NOTE
Flow control takes effect when the flow control function is enabled for interfaces on both ends
of a link.
4. Run:
commit
l Configuring flow control auto-negotiation for Ethernet interfaces
22
1. Run:
system-view
2. Run:
3. Run:
undo negotiation disable
The Ethernet interface is configured to work in auto-negotiation mode.
4. Run:
flow-control negotiation
Flow control auto-negotiation is enabled on the Ethernet interfaces.
By default, flow control auto-negotiation is disabled on a Ethernet interfaces.
NOTE
Flow control auto-negotiation takes effect only when the function is enabled for interfaces on
both ends of a link.
5. Run:
commit
----End
2.5.6 Configuring Interface Isolation
Context
Table 2-6 describes the interface isolation methods and application scenarios.
Table 2-6 Interface isolation methods and application scenarios
Isolation
Method
Application Scenario
Configure
unidirectio
nal
isolation
on
interfaces
l When multiple hosts connect to different interfaces of the same device and
a host with security risks sends many broadcast packets to the other hosts,
isolate the host from the other hosts unidirectionally to prevent the other
hosts from receiving packets from this host.
l Interfaces in an interface isolation group are isolated from each other, but
interfaces in different interface isolation groups can communicate. To isolate
interfaces in different interface isolation groups, configure unidirectional
isolation between these interfaces.
23
Isolation
Method
Application Scenario
Configure
an
interface
isolation
group
To implement Layer 2 isolation between interfaces, you can add interfaces to
different VLANs. This, however, wastes VLAN resources. Interface isolation
can also isolate interfaces in the same VLAN. You can add interfaces to an
interface isolation group to implement Layer 2 isolation between these
interfaces. Interface isolation provides secure and flexible networking schemes
for customers.

Procedure
l Configuring unidirectional isolation on interfaces
1. Run:
system-view
2. Run:
3. Run:
am isolate { interface-type interface-number }&<1-8>
Unidirectional isolation is configured on the Ethernet interface.
By default, the unidirectional isolation function is disabled.
NOTE
If interface A is isolated from interface B unidirectionally, packets sent from interface A cannot
reach interface B, but packets sent from interface B can reach interface A.
4. Run:
commit
l Configuring an interface isolation group
1. Run:
system-view
2. Run:
3. Run:
port-isolate enable group group-id
Interface isolation is enabled on the Ethernet interface.
By default, interface isolation is disabled.
24
NOTE
Interfaces in an interface isolation group are isolated from each other, but interfaces in different
interface isolation groups can communicate. If group-id is not specified, interfaces are added
to interface isolation group 1.
4. Run:
commit
----End
2.5.7 Configuring the IFG
Context
The inter-frame gap (IFG) differentiates two data packets. Setting a proper IFG can adjust data
packet forwarding efficiency.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface { GE | 10GE | 40GE } interface-number
Step 3 Run:
ifg ifg-value
The IFG is configured.
Step 4 Run:
commit
----End
2.5.8 Configuring an Interface to Allow Jumbo Frames
Context
Ethernet frames longer than 1518 bytes and VLAN frames longer than 1522 bytes are called
Jumbo frames.
An interface may receive Jumbo frames during high-throughput data exchange, such as a file
transfer. The device discards all Jumbo frames. When the jumbo frame function is enabled, the
system processes the received jumbo frames with the lengths within the specified range.
25
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
jumboframe enable value
Configuring the interface is configured to allow jumbo frames to pass through.
By default, the maximum frame length allowed by an interface is 9216 bytes.
Step 4 Run:
commit
----End
2.5.9 Configuring the Delay in Reporting Interface Status Changes
Context
An Ethernet interface can be in the Up or Down state. Frequent interface status changes in a
short time causes extra system costs. To avoid this problem, configure a delay in reporting
interface status changes. During the delay period, the system cannot detect interface status
changes. When the delay period times out, the physical layer notifies the system of the status
change.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
carrier { up-hold-time | down-hold-time } interval
The delay in reporting status changes is set.
By default, the delay in reporting a port-Up event and the delay in reporting a port-Down event
are both 0 milliseconds.
Step 4 Run:
commit
26
----End
2.5.10 Configuring the Alarm Thresholds of the Outbound/
Inbound Bandwidth Usage
Context
The bandwidth usage represents the load on a device. If the bandwidth usage exceeds the
threshold, bandwidth on the device is sufficient for services and needs expansion. For example,
if the bandwidth usage exceeds 95%, an alarm is generated to indicate that bandwidth resources
are used up. Services may be interrupted before system expansion. You can expand device
capacity to prevent service interruption.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
trap-threshold { input-rate | output-rate } bandwidth-in-use [ resume-rate resume-
threshold ]
The alarm thresholds for the outbound or inbound bandwidth usage on the interface are
configured.
By default, the alarm thresholds of the outbound and inbound bandwidth usage are both 100%.
Step 4 Run:
commit
----End
2.5.11 Configuring the Alarm Threshold of CRC-Error Packets
Context
When an Ethernet interface receives CRC error packets, service packet loss may occur. When
the number of CRC error packets received within a specified period exceeds the upper threshold,
an alarm is generated and sent to the NMS, which helps you rectify the fault in a timely manner.
Procedure
Step 1 Run:
27
system-view
Step 2 Run:
Step 3 Run:
trap-threshold crc-statistics threshold-value interval interval-value
The alarm threshold for the number of CRC error packets received on the interface and the
interval for sending the alarm are configured.
By default, the alarm threshold for the number of CRC error packets is 3 and the interval for
sending the alarm is 10s.
Step 4 Run:
commit
----End
2.5.12 Configuring the EEE function
Context
A device provides power for each interface. Even though an interface is idle, it consumes the
same power as working interfaces. This wastes power. After the Energy Efficient Ethernet (EEE)
function is configured on an electrical interface, the system reduces the power on the interface
when the interface is idle and restores the power when the interface starts to transmit data. This
reduces power consumption in the system.
NOTE
Only electrical interfaces support the EEE function.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
eee enable
EEE function is enabled on the electrical interface.
By default, the EEE function is disabled on an electrical interface.
28
CAUTION
This function takes effect only when it is configured on both ends of a link.
Step 4 Run:
commit
----End
2.5.13 Configuring Interface Traffic Statistics to Include Inter-frame
Gaps
Context
The system counts inter-frame gaps when calculating the traffic rate for QoS control on an
interface. However, interface traffic statistics do not include inter-frame gaps. Therefore, the
two statistics results are different. To avoid this situation, configure the interface traffic statistics
to include inter-frame gaps.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
set flow-statistics include-interframe
The interface traffic statistics include inter-frame gaps.
By default, the interface flow statistics do not include inter-frame gaps.
Step 4 Run:
commit
----End
2.5.14 Configuring the Link Flapping Protection Function
Context
Cable faults or active/standby switchovers may cause frequent status changes on an interface,
leading to network topology changes. If some Layer 2 protocols, such as STP, are configured
29
on an interface, the interface sends protocol packets, for example, TC packets, to update ARP
entries. If ARP entries are not updated immediately, user services may be interrupted. You can
configure the link flapping protection function to solve these problems.
When the device receives messages a port-Up or port-Down message, it checks the following
parameters:
l Link flapping interval
l Number of times the link status flaps
If the link status flaps the specified number of times in a specified period, the interface is error-
down. By default, an interface is error-down when its link status flaps five times in 10s.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
port link-flap trigger error-down
Link flapping protection is enabled on the interface.
By default, link flapping protection is disabled on an interface.
Step 4 (Optional) Run:
port link-flap { interval interval-value threshold threshold-value | interval
interval-value | threshold threshold-value }
The link flapping interval and the maximum number of times the link status flaps are set.
By default, the link flapping interval is 10s, the maximum number of times the link status flaps
is 5.
Step 5 Run:
commit
----End
Follow-up Procedure
By default, an interface cannot automatically restore to Up state after it is error-down. To restore
the interface, run the shutdown and undo shutdown commands on the interface in sequence.
To enable the interface to restore to the Up state automatically, run the error-down auto-
recovery cause link-flap command in the system view to set a recovery delay. After the delay,
the interface goes Up automatically.
30
2.5.15 Configuring an Interface to Transit to the Error-Down State
When the Optical Power Is Low
Context
Low optical power on an interface may cause intermittent interruption of services. To prevent
this situation, configure an optical interface to transit to the error-down state when the optical
power is too low. In this way, services can be switched to the backup link in a timely manner to
ensure normal service provisioning.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
port transceiver-power-low trigger error-down
The interface is configured to transit to the error-down state when the optical power is low.
By default, the Ethernet optical interface does not transit to the error-down state when the optical
power is low.
Step 4 Run:
commit
----End
Follow-up Procedure
By default, an interface in error-down state can only be restored manually using the
shutdown and undo shutdown commands. To configure the interface to automatically restore
to the Up state, run the error-down auto-recovery cause transceiver-power-low interval
interval-value command in the system view before the interface transitions to the error-down
state to set a recovery delay. After the delay, the interface goes Up automatically.
2.5.16 Configuring an Interface to Transit to the Error-Down State
When the Number of Received CRC Error Packets Exceeds the
Threshold
Context
If an interface receives CRC error packets, packet loss occur or other faults may occur on the
link. If a backup link is configured on an Ethernet interface, configure the interface to transit to
31
the error-down state when the number of received CRC error packets exceeds the threshold. In
this way, services can be switched to the backup link in a timely manner to ensure reliable data
transmission.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
trap-threshold crc-statistics threshold-value interval interval-value
The upper limit and alarm interval of CRC-error packets are configured.
By default, the alarm threshold of CRC-error packets is 3 and the alarm interval is 10 seconds.
Step 4 Run:
port crc-statistics trigger error-down
The interface is configured to transit to the error-down state when the number of received CRC-
error packets exceeds the threshold.
By default, an interface does not transit to the Error-down state when the number of received
CRC-error packets exceeds the threshold.
Step 5 Run:
commit
----End
Follow-up Procedure
By default, an interface in error-down state can only be restored manually using the
shutdown and undo shutdown commands. To configure the interface to automatically restore
to the Up state, run the error-down auto-recovery cause crc-statistics interval interval-
value command in the system view before the interface transitions to the error-down state to set
a recovery delay. After the delay, the interface goes Up automatically.
2.5.17 Checking the Configuration
Procedure
l Run the display interface [ interface-type [ interface-number ] ] command to check
information about an interface, including interface running status, basic interface
configuration, and packet transmitted through the interface.
l Run the display interface brief command to check brief information about interfaces,
including the physical status, protocol status, bandwidth usage in the inbound and outbound
32
directions during a certain period of time, and the number of error packets sent and received
on each interface.
l Run the display interface description [ interface-type [ interface-number ] ] command to
check the interface description.
l Run the display interface ethernet brief command to check brief information about
Ethernet interfaces, including the physical status, negotiation mode, duplex mode, rate, and
average bandwidth usage in the inbound and outbound directions on each interface within
the last period of time.
l Run the display port split [ slot slot-id ] command to check information about split of
40GE interfaces and combination of the 10GE interfaces.
l Run the display port-isolate group { group-id | all } command to check information about
interface isolation groups.
l Run the display interface interface-type interface-number virtual-cable-test command to
check the last cable test result on an Ethernet electrical interface.
l Run the display error-down recovery [ interface interface-type interface-number ]
command to check information about an error-down interface.
l Run the display interface [ interface-type [ interface-number ] ] counters [ inbound |
outbound ] command to check traffic statistics on a physical interface.
l Run the display interface [ interface-type [ interface-number ] ] counters rate
[ inbound | outbound ] command to view the inbound and outbound traffic rates on an
interface.
----End
2.6 Maintaining Ethernet Interfaces
This section describes how to maintain Ethernet interfaces, including using the loopback
function to check the interface and deleting interface statistics.
2.6.1 Configuring Loopback Detection
Context
CAUTION
l After the loopback detection is enabled on an interface using the loopback command, the
Ethernet interface or link on the interface cannot function properly. When the loopback
detection test is complete, run the undo loopback command to disable it immediately.
Loopback detection needs to be enabled for special function testing, for example, Ethernet
interface diagnosis. When loopback detection is enabled on an Ethernet interface, the interface
works in the full-duplex mode. When loopback detection is disabled, the interface restores to
the default configuration.
Table 2-7 describes the loopback detection classification.
33
Table 2-7 Loopback detection classification
Type Description
Hardware
loopback
Connect the transmit and receive ends with a cable to form a loop so that
the device receives the signals sent by itself.
Software
loopback
Remote loopback (external loopback)
The local interface does not forward packets received from the remote
interface based on their destination addresses. Instead, it sends the packets
back to the remote interface.
Local loopback (internal loopback)
Packets sent from an interface are sent back to the local device.

NOTE
An Ethernet interface does not support remote loopback.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
loopback internal
Internal loopback detection is configured on the Ethernet interface.
By default, loopback detection is disabled on an Ethernet interface.
Step 4 Run:
commit
----End
2.6.2 Clearing Interface Statistics
Context
To monitor the status of an interface or locate faults on the interface, collect traffic statistics on
the interface. Before collecting traffic statistics on an Ethernet interface, clear the existing traffic
statistics on this interface.
34
CAUTION
Interface statistics cannot be restored after they are cleared. Confirm your action before you
perform the operations.
Procedure
l Run the reset counters interface [ interface-type [ interface-number ] ] command to clear
interface statistics.
l Run the reset interface [ interface-type interface-number ] virtual-cable-test command
to clear cable test results on all interfaces.
----End
2.7 Configuring Examples
This section provides Ethernet interface configuration examples, including network
requirements, configuration roadmap, configuration procedure, and configuration files.
2.7.1 Example for Configuring Interface Isolation
Networking Requirements
As show in Figure 2-1, Server1, Server2, and Server3 belong to VLAN 10. Server1 and Server2
are not allowed to communicate with each other in VLAN10, but they are allowed to
communicate with Server3.
Figure 2-1 Networking diagram of interface isolation configuration
Switch
Server1 Server2 Server3
10GE1/0/3
1
0
G
E
1
/
0
/
2
10GE1/0/1
10.10.10.1/24 10.10.10.2/24 10.10.10.3/24
VLAN10

35
Configuration Roadmap
The configuration roadmap is as follows:
1. Add the interfaces to the specified VLAN.
2. By default, interfaces are isolated at Layer 2 but can communicate at Layer 3. You can add
interfaces to an isolation group to implement Layer 2 isolation between these interfaces.
Procedure
Step 1 Create VLAN 10 on Switch, and add interfaces to VLAN 10.
<HUAWEI> system-view
[~HUAWEI] sysname Switch
[~HUAWEI] commit
[~Switch] vlan 10
[~Switch-vlan10] quit
[~Switch] interface 10ge 1/0/1
[~Switch-10GE1/0/1] port default vlan 10
[~Switch-10GE1/0/1] quit
[~Switch] commit
Step 2 Configure interface isolation.
# Configure interface isolation for 10GE1/0/1.
[~Switch-10GE1/0/1] port-isolate enable group 1
[~Switch] commit
# Configure interface isolation for 10GE1/0/2.
[~Switch-10GE1/0/2] port-isolate enable group 1
[~Switch] commit
Step 3 Verify the configuration.
# Server1 and Server2 cannot ping each other.
# Server1 and Server3 can ping each other.
# Server2 and Server3 can ping each other.
----End
Configuration Files
Configuration files of Switch
#
sysname Switch
#
vlan batch 10
#
interface 10GE1/0/1
port default vlan 10
36
port-isolate enable group 1
#
interface 10GE1/0/2
port-isolate enable group 1
#
interface 10GE1/0/3
#
return
37
3 Logical Interface Configuration
About This Chapter
The information provided here on logical interface types, and configuration procedures can help
you make full use of logical interfaces.
3.1 Introduction to Logical Interfaces
Logical interfaces do not exist physically. They are manually configured for data exchange.
3.2 Configuring a Loopback Interface
The loopback interface is always Up to ensure network reliability.
3.3 Configuring a NULL Interface
A NULL interface is always Up once created automatically by the system. It does not forward
packet but can be used to filter packet.
Configuration Guide - Interface Management 3 Logical Interface Configuration
38
3.1 Introduction to Logical Interfaces
Logical interfaces do not exist physically. They are manually configured for data exchange.
This topic describes logical interfaces supported by CloudEngine 6800&5800 Series.
Table 3-1 Logical interfaces
Interface DescriptionConfiguration
Reference
Configuration Reference
Eth-Trunk
interface
An Eth-Trunk is formed by binding
multiple Ethernet interfaces to provide
more bandwidth and higher transmission
reliability.
For details about how to configure
an Eth-Trunk interface, see Link
Aggregation Configuration in the
CloudEngine 6800&5800 Series
Switches Configuration Guide:
LAN .
VLANIF
interface
has Layer 3 features and enables VLANs
to communicate after being assigned an
IP address.
For details about how to configure a
VLANIF interface, see VLAN
Configuration in the CloudEngine
6800&5800 Series Switches
Configuration Guide: LAN
Configuration.
Stack
interface
A stack interface is a logical interface
used to implement the stacking function.
The stacking function virtualizes
multiple switches into a logical switch to
provide massive data forwarding and
improve network reliability in data
centers.
For details about how to configure a
stack interface, see iStack
Configuration in the CloudEngine
6800&5800 Series Switches
Configuration Guide: Device
Management Configuration.
Loopback
interface
A loopback interface is always Up and
can be configured with a 32-bit subnet
mask.
-
NULL
interface
used in route filtering because any
network packets sent to this interface are
discarded.
-

3.2 Configuring a Loopback Interface
The loopback interface is always Up to ensure network reliability.
Context
The loopback interface has the following features:
l The loopback interface is always Up and has the loopback feature.
39
l The loopback interface can be configured with the mask of all 1s.
Based on the preceding features, the loopback interface has the following applications.
l The IP address of a loopback interface is specified as the source address of packets to
improve network reliability.
l When no Router ID is configured for dynamic routing protocols, the maximum IP address
of the loopback interface is configured as the router ID automatically.
l The loopback interface is configured as the source interface to send boarder gateway
protocol (BGP) packets to ensure that the BGP session functions correctly when the
physical interface is faulty.
l The loopback interface can be configured with the mask of 255.255.255.255 to save IP
address resources.
Pre-Configuration
Before configuring a loopback interface, complete the following task:
l Powering on the device and performing self-check
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface loopback loopback-number
A loopback interface is created and the loopback interface view is displayed.
You can create or delete loopback interface dynamically. After a loopback interface is created,
the link-layer protocol is always up unless the loopback interface is deleted.
Step 3 Run:
ip address ip-address { mask | mask-length }
The IP address of the loopback interface is configured.
Step 4 Run:
commit
Commit the configuration.
----End
l Run the display interface loopback [ loopback-number ] command to check the status of
a loopback interface.
3.3 Configuring a NULL Interface
A NULL interface is always Up once created automatically by the system. It does not forward
packet but can be used to filter packet.
40
Context
A NULL0 interface is created automatically. The NULL0 interface is always Up and cannot
forward packets. Any packets sent to the NULL0 interface are discarded. If the next hop of a
static route to a network segment is a null interface, all the data packets destined for this network
segment are discarded. Therefore, the packets that you want to filter out can be sent to the NULL0
interface directly without configuring the access control list.
For example, run the following static route configuration command to discard packets sent to
the network segment of 192.101.0.0.
[~HUAWEI] ip route-static 192.101.0.0 255.255.0.0 NULL 0
Pre-Configuration
Before configuring a NULL interface, complete the following task:
l Powering on the device and performing self-check
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface null 0
The NULL interface view is displayed.
The NULL interface stays in the Up state. It cannot forward data packets. You cannot configure
an IP address for it or encapsulate it with protocols.
----End
l Run the display interface null [ 0 ] command to check the status of a null interface.
41

CloudEngine 6800&5800 V100R001C00 Configuration Guide - Interface Management 04 PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CloudEngine 6800&5800 V100R001C00 Configuration Guide - Interface Management 04 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

CloudEngine 6800&5800 Series Switches

Das könnte Ihnen auch gefallen