01-02 Vs Configuration

HUAWEI NetEngine40E Universal Service Router
Configuration Guide - System Management 2 VS Configuration
2 VS Configuration
About This Chapter
Virtual systems (VSs) are managed by administrators that are granted with corresponding
authority. A physical system (PS) administrator can manage all VSs which belong to the PS; a
VS administrator can perform operations only on the managed VS, including starting and
stopping the allocated services.
2.1 Overview of VSs

Virtual system (VS) partitioning helps manage networks by layer.
2.2 Limitations for VS Management
2.3 Managing VSs by a PS Administrator
A Physical System (PS) administrator has the authority to manage Virtual Systems (VSs),
including configuring VSs, allocating resources to VSs, and configuring services on VSs.
2.4 Maintaining VSs
This section describes how to reset a VS when a VS needs to be upgraded or the diagnostics
system is abnormal.
2.5 Configuration Examples for VSs
This section provides VS configuration examples.
2.1 Overview of VSs

Virtual system (VS) partitioning helps manage networks by layer.
Background
As the demand on various types of network services is growing, network management
becomes more complex. Requirements for service isolation, system security, and reliability
are steadily increasing. The virtual private network (VPN) technique can be used to isolate
services on a PS. If a module failure occurs on the PS, all services configured on the PS will
be interrupted.
Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 5

To prevent service interruptions, the VS technique is used to partition a PS into several VSs.
Each VS functions as an independent network element and uses separate physical resources to
isolate services.
Further development of the distributed routing and switching systems allows VS technique to
fully utilize the service processing capability of a single PS. The VS technique helps simplify
network deployment and management, and strengthen system security and reliability.
Relationship Between a PS and VSs

As shown in Figure 2-1, a physical router, which can be regarded as a PS, is partitioned into
several VSs. Each VS functions as an independent router to process services.
Figure 2-1 VS partitioning
The PS administrator has the authority to manage all VSs. The VS administrator has the authority to
query VSs but cannot manage them.
Basic Concepts
Figure 2-2 shows VS concepts.

Figure 2-2 VS concepts
Table 2-1 VS concept descriptions

Concept Description
PS Physical system
VS A VS is a virtual system on both software

and hardware planes. Each VS performs
independent routing tasks.
VSs share all resources, such as MBs, LCs,
and chassis, except interfaces. That is, VSs
can share the main control board and
interface board resources. Each VS has its
own primary VS main board (PVMB) and
configuration management instance.
Generally, the routing management system
and configuration management system work
on the PVMB.
NOTE
Each PS has a default VS named Admin-VS. All
unassigned interfaces belong to this VS.
All VSs in a PS must use the same system
software. Each VS is configured with its own
configuration management system and routing
protocols.
MB Main boards (MBs) are used to carry tasks

on the management control plane.
In a VS, the MB refers to a common MB,
that is, the MB is not a master main board
(MMB) or PVMB.

Concept Description
PVMB A VS has many MBs, two of which manage

the entire VS. The two MBs are PVMBs.
2.2 Limitations for VS Management

Limitations
Restrictions Guidelines Impact
Forwarding plane None None

performance alarms and
flow creation rate control
are performed at the board
level, not at the VS
granularity.
The function of filtering Configure the whitelist None

DHCP packets based on the function only in Admin VS.
whitelist does not support
multiple VSs.
After port mirroring is N/A After port mirroring is

configured on a main configured on a main
interface, the port mirroring interface, the port mirroring
configuration becomes configuration becomes
ineffective on its sub- ineffective on its sub-
interface, regardless of interface, regardless of
whether the main interface whether the main interface
and its sub-interface belong and its sub-interface belong
to the same independent VS. to the same independent VS.
If the memory of the master If the memory of the master VS configurations may be
main control board is main control board is lost.
inconsistent with that of the inconsistent with that of the
slave main control board, a slave main control board,
master/slave main control increase the memory of the
board switchover or device master or slave main control
restart occurs, which may board to achieve memory
cause VS configurations to consistency.
be lost.
The clock service can be None Configurations will fail to

configured only in Admin be committed for VSs.
VS.
Multicast NAT does not Plan services properly. Multicast NAT does not
support multiple VSs. support multiple VSs.

After a pre-splitting 100GE None Interface usage is under

interface or post-splitting restriction.
10GE interface is added to a
VS (non-admin VS),
interface splitting is not
supported and can be
configured only after the
interface is removed from
the VS.
When an interface and its Deploy an interface and its If an interface and its sub-
sub-interfaces are deployed sub-interfaces in the same interfaces are deployed in
in different VSs, ESI route VS. different VSs and an ESI is
negotiation is not supported. configured on the interface,
the sub-interfaces fail to
forward packets.
The group-mac of L2PT and None None

BPDU tunnels can be
configured only in Admin
VS.
The destination IP address None None

or UDP port number cannot
be configured for the output
NetStream flows in the view
of a non-Admin VS.
The NetStream service
processing board cannot be
configured for an interface
board in the view of a non-
Admin VS.
The DAA service does not None DAA service activation

support multi-VS and can be fails.
deployed only on the
Admin-AS.
The BOD service does not None BOD service activation

Admin-AS.
The EDSG service does not None EDSG service activation

Admin-AS.

Different names and IDs Configure different names NAT instances, service-
must be configured for NAT and IDs for NAT instances, locations, service instance
instances, service-locations, service-locations, service groups on different Vses
service instance groups on instance groups on different cannot have the same name
different VSes. VSes. or ID.
Different names and IDs Configure different names DS-Lite instances, NAT64
must be configured for DS- and IDs for DS-Lite instances, service-locations,
Lite instances, NAT64 instances, NAT64 instances, service instance groups on
instances, service-locations, service-locations, service different Vses cannot have
service instance groups on instance groups on different the same name or ID.
different VSes. VSes.
For a subcard that allows None The switching mode of port

two 50G ports with 0 on the subcard 2-Port
consecutive port numbers to 50GBase/1-Port 100GBase-
be switched to a 100G port, QSFP28 FlexE Flexible
when the port with an odd Card (P120) is affected.
port number is added to a
service VS:
l If the port with an even
port number is
configured to work in
manual mode using the
switch-mode manual
command, the port-speed
100GE command cannot
be run on the port to
forcibly switch the port
to 100GE.
l If the port with an even
port number is
configured to work in
auto-negotiation mode
using the switch-mode
auto command and a
100GE optical module is
inserted into port 0, auto-
negotiation fails.
A standard Ethernet None A standard Ethernet

interface that has been interface that has been
added to VSn cannot be added to VSn cannot be
switched to the FlexE mode. switched to the FlexE mode.
After a standard Ethernet None After a standard Ethernet

interface is added to VSn, interface is added to VSn,
the interface rate does not the interface rate does not
support auto-negotiation support auto-negotiation
against an optical module. against an optical module.

A FlexE physical interface None A FlexE physical interface

cannot be added to VSn. cannot be added to VSn.
A FlexE logical interface None A FlexE logical interface

can be created only in cannot be created in VSn.
Admin VS.
An ATM bundle interface None None

can be created Admin VS or
VSn. An ATM bundle
interface in Admin VS
cannot be bound to VSn.
The Controller's interfaces None None

can be configured only in
Admin VS and cannot be
allocated to VSn.
An MLPPP interface can be None None

created only in Admin VS.
A serial main interface can None None

be created only in Admin
VS.
A CPOS-Trunk interface None None

can be created only in
Admin VS. A CPOS-Trunk
A trunk serial main interface None None

can be created only in
Admin VS.
A global MP-group main None None

interface can be created only
in Admin VS.
An IMA-group main None None

in Admin VS.
An IMA-group sub-interface None None

can be created in Admin VS
or VSn. An IMA-group
main interface and its sub-
interfaces must be in the VS.
An IMA-group sub-interface
in Admin VS cannot be
bound to VSn.

A serial sub-interface can be None None

created in Admin VS or
VSn. A serial main interface
and its sub-interfaces must
be in the VS. A serial sub-
A global IMA-group main None None

in Admin VS.
The CPU-defend policy None None

needs to be configured in
the slot view. Many security
functions can be configured
only in Admin VS and take
effect in all VSs, including
CP-CAR, attack source
tracing, TCP/IP attack
defense, application layer
association, GTSM, and
MA-defend.
The MA-defend policy can
be configured only in
Admin VS. The policy can
be applied to a device, a
board, or an interface. The
device and board policies
can be based on Admin VS.
Only the interface policy
can be applied based on the
VSn.
If ARP invalid packet None None

filtering or ARP destination
address detection is
configured on a main
interface, the corresponding
configuration is also
delivered to its sub-
interfaces that reside in VSs
different from the main
interface's VS.
The command for Layer 2 None None

loop detection can be
configured only in the
admin VS and takes effect
for all VSs.

The command for Layer 3 None None

loop detection can be
admin VS and takes effect
for all VSs.
The SOC, including the None None

commands in the SOC view,
can be configured only in
Admin VS and takes effect
in all VSs.
Host-CAR does not support None None

multiple VSs.
RADIUS services do not None None

support multiple VSs.
(RADIUS services can be
deployed only in Admin
VS.)
BRAS services do not None None

(BRAS services can be
deployed only in Admin
VS.)
802.1X port-based None None

authentication does not
(802.1X port-based
authentication can be
Admin VS.)

1. The local discriminator None None

(MD) of BFD is unique in
all VSs. That is, if BFD with
MD=200 is configured in
VS
l when BFD with
MD=200 is configured in
VS
l an error message is
displayed.
2. The special commands
default-ip and process-
mode (involved only in
NE5000Es) can be
admin VS (also called
Admin-VS or LR) and
take effect for all VSs.
default-ip-
addressdefault-ip-value;
undodefault-ip-address;
process-
modecentralized-
slotcentralSlotID[slot-
id2];
undoprocess-mode

l IP FPM supports None None

multiple VSs. However,
the following commands
can be run only in
Admin-VS but take
effect in all VSs. If a
coloring bit conflicts
with the QoS
configuration and needs
to be modified, you must
modify the configuration
in Admin-VS, rather than
in VSn.
(1) color-flagloss-
measure{tos-bitbit|flags-
bit0}delay-measure{tos-
bitbit|flags-bit0};
(2) color-flagloss-
measure{tos-bitbit|flags-
bit0}delay-measurenone;
(3) undocolor-flag
l Only the instance
statistics in Admin-VS
can be sent to the PM.
The system determines VS Plan VS resources properly. None

specifications based on the
memory of the master main
control board.
If the memory of the master
main control board is less
than 8 GB, creating multiple
VSs is not supported.
main control board is greater
than or equal to 8 GB but
less than 16 GB, the system
supports a maximum of four
VSs.
main control board is greater
than or equal to 16 GB, the
system supports a maximum
of eight VSs.

Non-Admin VSs share None None

system memory resources
with each other. Memory
resources cannot be
separately allocated to the
VSs.
After a device is upgraded Before the upgrade, save the The configuration
from the unified VS mode to configuration file of a non- information of the non-
the independent VS mode Admin-VS VS. After the Admin VS is lost.
with existing configurations, upgrade, save the
data in all VSs except configuration file to the non-
Admin-VS is lost. Admin VS directory for
configuration restoration.
All VSs except Admin-VS None Non-Admin VSs do not

do not support .dat support fast startup in DAT
configuration files. mode.
A device allows a maximum None None

of 21 users to deliver
configurations. Other users
can only perform the query
operation. The users in non-
Admin VSs are in
preemption mode.
Configurations cannot be None Configurations may fail to

concurrently committed for be committed for some VSs,
Admin-VS and non-Admin- and you need to try again in
VS VSs. this case.
Configurations can be
concurrently committed for
multiple non-Admin-VS
VSs. However, if
configurations that affect
Admin-VS are modified for
a non-Admin VS,
configurations cannot be
committed for other non-
Admin-VS VSs during
configuration commission
for this non-Admin-VS VS.
VSs except Admin-VS do None None

not support independent
NTP.
KPI files generated through None None

the KPI diagnosis function
are not independently saved
by VS.

The maintenance assistant None None

function does not apply to
non-Admin VSs. Admin-VS
collects information
uniformly.
DCN can be enabled only in None None

Admin-VS.
IP FPM measurement flags None None

cannot be configured for
VSs except Admin-VS.
The BFD local descriptor None None

(MD) is unique on a device.
Different VSs cannot be
configured with the same
local descriptor.
Different VSs cannot be None None

configured with the same
PWE3 static VC label.
The EVPN supports Do not configure the same None

multiple VSs, but the ESI- ESI-ID for different non-
ID is unique on a device. Admin VSs.
GRESM labels in the system Do not configure the same None

are unique and cannot GRESM label for different
conflict with each other non-VS0 VSs.
even in different VSs.
The sampling mode and None None

destination address are
configured in the Slot view
and can only be configured
in Admin-VS.

The display diagnostic- None The execution efficiency of

information command can the one-click diagnostic
be run in the Admin-VS command is affected.
view to collect diagnostic
information of all VSs. If
the command is run in the
VSn view, only diagnostic
information of the current
VS is collected. Each VS
can have only one piece of
task collector diagnostics
information. Therefore,
when the command is run in
the Admin-VS view to
collect global diagnostic
information and a VSn has
an information collection
task being executed, the
diagnostic information if
this VSn will not be
collected.
Each independent None For an independent

management VS allows the management VS, only up to
private VB function to be three target hosts can be
enabled on a maximum of adapted to Huawei
three target hosts. proprietary NMSs.
The function of filtering Configure the whitelist Hardware does not support
DHCP packets based on the function only in Admin-VS. this feature.
whitelist does not support
multiple VSs.
2.3 Managing VSs by a PS Administrator

A Physical System (PS) administrator has the authority to manage Virtual Systems (VSs),
including configuring VSs, allocating resources to VSs, and configuring services on VSs.
Usage Scenario
To fully utilize hardware resources and share board resources, a PS can be divided into
multiple VSs. Each VS can bear a new type of service independently.
Pre-configuration Tasks
Before configuring VSs, complete the following tasks:
l Install the PS and power it on properly.
l Ensure that the PS administrator has the authority to create VSs.

2.3.1 Creating a VS
A Physical System (PS) administrator can create Virtual Systems (VSs) on the PS, but cannot
create, or delete the Admin-VS. The Admin-VS is the default VS on a PS and manages the
entire PS. The Admin-VS is automatically created when a PS is being started. All the
unassigned resources on a PS belong to the Admin-VS by default. A VS is started as soon as
it is created.
Procedure
Step 1 Run system-view
The system view is displayed.
Step 2 Run admin
The admin view is displayed.
Step 3 Run virtual-system vs-name
A VS is created and started.
Step 4 (Optional) Run port-mode port [ resource-template template-name ]
A port mode is configured for the VS.
You cannot delete the port mode that has been configured for a VS.
Step 5 (Optional) Run description description
The description of a VS is displayed.
The network administrator can configure a description for the VS to describe the service type
or usage.
Step 6 Run commit
The configuration is committed.
In the VS creation process, the NetStream function becomes unavailable in two minutes.
----End
2.3.2 Configuring Hardware Resources for the VS

A Physical System (PS) administrator can allocate board and interface resources to Virtual
Systems (VSs) so that the VSs can carry services, or delete board and interface resources so
that the services on the VSs can be stopped.
Context
The Admin-VS is the default VS in a PS and manages the PS. All unallocated resources in the
PS belong to the Admin-VS by default.

The Admin-VS has all board and interface resources of a PS, and the board and interface
resources of the Admin-VS cannot be added to or deleted.
Only in the virtual cluster scenario, hardware resources can be configured for the VS.
This configuration process is supported only on the Admin-VS.
Procedure
Step 1 Run system-view
Step 2 Run admin
Step 3 Run virtual-system vs-name
The VS view is displayed.
Step 4 (Optional) Run port-mode port [ resource-template template-name ]
Step 5 Run assign interface interface-type interface-number]
Interface resources are allocated to the VS.
Interface allocation must comply with the following rules:

l The board and interface resources of a VS can be allocated by a PS administrator only.
l A VS administrator only has the authority to perform operations on the managed VS but
not the other VSs.
l When an interface in the admin VS is allocated to a VS, all configurations on the
interface are cleared.
l Each VS can be allocated a maximum of two PVMB resources.
l The slot resources deleted from a VS are automatically allocated to the Admin-VS, and
the Admin-VS takes over services carried using these slot resources.
Step 6 (Optional) Run resource cpu weight weight-limit
A CPU weight value is assigned to the VS.
You can run this command to change the default CPU weight value.
Step 7 Run commit

In the VS creation process, the NetStream function becomes unavailable in two minutes.
----End
2.3.3 (Optional) Configuring Logical Resources for the VS

A Physical System (PS) administrator can allocate logical resources to Virtual Systems
through two methods.
Context
PS administrator can assign a logical resource to a VS each time, or use a resource template to
assign multiple logical resources to a VS in a batch.
Procedure
l Assign a logical resource to a VS each time.
a. Run system-view
b. Run admin
c. Run virtual-system vs-name
d. Run port-mode port [ resource-template template-name ]
e. In virtual system view, run resource { m4route | m6route | u4route | u6route |
vpn-instance } upper-limit resource-limit
Logical resources are assigned to the VS.
f. Run commit
l Assign multiple logical resources to a VS in a batch.
a. Run system-view
b. Run admin
c. Run virtual-system vs-name


d. Run port-mode port [ resource-template template-name ]
e. Run resource-template template-name
A resources template is created.
f. In resource template view, run resource { m4route | m6route | u4route | u6route |
vpn-instance } upper-limit resource-limit
Resource items are added to the resource template.
g. Run assign resource-template template-name
The resource template is assigned to the VS.
h. Run commit
----End
2.3.4 (Optional) Switching a VS

A Physical System (PS) administrator can switch from one Virtual System (VS) to another.
Context
Procedure
l Run switch virtual-system vs-name
The administrator is switched to a target VS.
The VS name is displayed in the Name field in the display virtual-system command
output.
----End
2.3.5 Verifying the VS Configuration

Verify the VS configuration as a PS administrator.
Prerequisites
All VS configurations are complete.
Procedure
l Run the display virtual-system [ name vs-name ] [ verbose ] command to check basic
VS information.

l Run the display virtual-system [ name vs-name ] resource command to check resource
information about a specified VS or all VSs of a PS.
The parameter name is supported only on the Admin-VS.

l Run the display virtual-system resource-template command to check resource
template information about a specified VS or all VSs of a PS.
l Run the display virtual-system configuration state command to check the VS
configuration status.
----End
2.4 Maintaining VSs

This section describes how to reset a VS when a VS needs to be upgraded or the diagnostics
system is abnormal.
2.4.1 Resetting a VS
When updating VS configurations or diagnosing faults, you can reset the VS.
Context
When a VS is being reset, all interfaces of the VS switch to the Down state, and all services are interrupted.
Exercise caution when running reset command. For details on precautions of this command, see reset
virtual-system.
Procedure
l Run the reset virtual-system to reset a VS.
----End
2.5 Configuration Examples for VSs

This section provides VS configuration examples.
2.5.1 Example for Creating VSs

This section provides an example for creating VSs and allocating resources to the VSs.
Networking Requirements
This configuration example is supported only on the Admin-VS.
On the network shown in Figure 2-3, the main control board of a PS processes all services
offered by an SP. If a service failure on the PS causes a PS failure, other services running on

the PS cannot be properly forwarded. To prevent this problem, configure different VSs on the
PS to independently carry services to improve network security.
As shown in Figure 2-3, different VSs can be created on a PS. The VSs carry their own
services that are mutually isolated. Services can be quickly differentiated by VS, and physical
interfaces can be shared between the VSs, saving physical links and reducing networking
costs.
Figure 2-3 Creating VSs
Precautions
When creating VSs, note the following points:
l A VS starts after it is created.
l The VS slot resources can be allocated only by the PS administrator.
l The same slot resources can be allocated to multiple VSs.
l An interface can be allocated only to a single VS.
l The slot resources deleted from a VS are automatically allocated to the Admin-VS, and
the Admin-VS takes over services carried using these slot resources.
Configuration Roadmap
The configuration roadmap is as follows:
1. Create VSs and configure PVMBs for each VS so that the VSs can start.
2. Allocate interfaces to VSs to allow the VSs to forward services.
Data Preparation
To complete the configuration, you need the following data:
l Names of the VSs to be created: vs1, vs2, and vs3
l Interface number allocated to each VS
Procedure
Step 1 Create and start VSs.
<HUAWEI> system-view
[~HUAWEI] admin
[~HUAWEI-admin] virtual-system vs1
[*HUAWEI-admin-vs:vs1] port-mode port

[*HUAWEI-admin-vs:vs1] description vs1

[*HUAWEI-admin-vs:vs1] quit
[*HUAWEI-admin] commit
Step 2 Allocate resources to the VSs.

[*HUAWEI-admin-vs:vs1] assign interface gigabitethernet 3/0/2
[*HUAWEI-admin-vs:vs2] assign interface gigabitethernet 3/0/3
[*HUAWEI admin-vs:vs3] assign interface gigabitethernet 3/0/4
[*HUAWEI admin] commit
Step 3 Configure different services or features on the VSs.

For configuration details, see the related feature configurations. For example, to configure a
routing protocol on VS1, see the chapter "IP Routing" in the NE40E Configuration Guide - IP
Routing.
Step 4 Verify the configuration.
Run the display virtual-system command on the PS. The command output shows that vs1,
vs2, and vs3 have been created and started.
[*HUAWEI-admin] display virtual-system
---------------------------------------------------------------
Name Status Description
---------------------------------------------------------------
Admin-VS running admin-vs
vs1 running vs1
vs2 running vs2
vs3 running vs3
---------------------------------------------------------------
Run the display virtual-system [ name vs-name ] [ verbose ] command on the PS. The
following example uses vs1 configurations.
[~HUAWEI-admin] display virtual-system name vs1 verbose
Name : vs1
Status : running
Description :
Create time : 2017-03-13 21:24:27+09:30 DST
Port mode : port
System MAC : 00-e0-fc-12-34-56
Assigned slot(s)
pvmb : 6
pvmb : 7
CPU(s)
slot 6 : 4%
slot 7 : 4%
fcard:/VS_huawei: 0%, 16/41943040 (Used Kbytes/Max Kbytes)
Assigned interface(s)
GE3/0/0, slot 3
Assigned resource(s)
u4route : 10000(Max)
m4route : 1000(Max)
u6route : 1000(Max)
m6route : 1000(Max)

vpn-instance : 256(Max)
cpu : 5(weight)
Run the display virtual-system configuration state command on the PS to check whether
VS configurations have been saved.
[~HUAWEI-admin] display virtual-system configuration state
-----------------------------------------------------------------
Name Saved-configuration
-----------------------------------------------------------------
Admin-VS not saved
vs1 not saved
vs2 not saved
vs3 not saved
-----------------------------------------------------------------
----End
Configuration Files
PS configuration files
#
admin
virtual-system vs1
assign interface GigabitEthernet3/0/2
virtual-system vs2
virtual-system vs3

01-02 Vs Configuration

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01-02 Vs Configuration

Uploaded by

Copyright:

Available Formats

HUAWEI NetEngine40E Universal Service Router

Configuration Guide - System Management 2 VS Configuration

About This Chapter

2.1 Overview of VSs

2.1 Overview of VSs

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 5

Relationship Between a PS and VSs

Figure 2-1 VS partitioning

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 6

Figure 2-2 VS concepts

Table 2-1 VS concept descriptions

VS A VS is a virtual system on both software

MB Main boards (MBs) are used to carry tasks

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 7

PVMB A VS has many MBs, two of which manage

2.2 Limitations for VS Management

Forwarding plane None None

The function of filtering Configure the whitelist None

After port mirroring is N/A After port mirroring is

The clock service can be None Configurations will fail to

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 8

Restrictions Guidelines Impact

After a pre-splitting 100GE None Interface usage is under

The group-mac of L2PT and None None

The destination IP address None None

The DAA service does not None DAA service activation

The BOD service does not None BOD service activation

The EDSG service does not None EDSG service activation

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 9

Restrictions Guidelines Impact

For a subcard that allows None The switching mode of port

A standard Ethernet None A standard Ethernet

After a standard Ethernet None After a standard Ethernet

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 10

Restrictions Guidelines Impact

A FlexE physical interface None A FlexE physical interface

A FlexE logical interface None A FlexE logical interface

An ATM bundle interface None None

The Controller's interfaces None None

An MLPPP interface can be None None

A serial main interface can None None

A CPOS-Trunk interface None None

A trunk serial main interface None None

A global MP-group main None None

An IMA-group main None None

An IMA-group sub-interface None None

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 11

Restrictions Guidelines Impact

A serial sub-interface can be None None

A global IMA-group main None None

The CPU-defend policy None None

If ARP invalid packet None None

The command for Layer 2 None None

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 12

Restrictions Guidelines Impact

The command for Layer 3 None None

The SOC, including the None None

Host-CAR does not support None None

RADIUS services do not None None

BRAS services do not None None

802.1X port-based None None

Issue 02 (2019-09-30) Copyright © Huawei Technologies Co., Ltd. 13

Restrictions Guidelines Impact