No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE20E-S2 V800R010C10SPC500 Configuration Guide - System Management 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - System Management
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Licensing Requirements and Limitations for VS--S2E

Licensing Requirements and Limitations for VS--S2E

Licensing Requirements

This feature is a basic feature and is not under license control.

Restrictions and Guidelines

Restrictions

Guidelines

Impact

VSs except Admin-VS share system memory resources with each other. Memory resources cannot be separately allocated to the VSs.

None

None

The system determines VS 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.

If the memory of the master main control board is greater than or equal to 8 GB but less than 16 GB, the system supports a maximum of four VSs.

If the memory of the master main control board is greater than or equal to 16 GB, the system supports a maximum of eight VSs.

Plan VS resources properly.

None

After a device is upgraded from the unified VS mode to the independent VS mode with existing configurations, data in all non-Admin-VSs is lost.

Before the upgrade, save the configuration files of a non-Admin-VS separately. After the upgrade, copy the saved configuration files to the non-Admin-VS directory for configuration restoration.

Configuration information of a non-Admin-VS will be lost.

Each independent management VS allows the private VB function to be enabled on a maximum of three target hosts.

None

For an independent maNonegement VS, only up to three target hosts can be adapted to Huawei proprietary NMSs.

Configurations cannot be concurrently committed for Admin-VS and non-Admin-VSs.

Configurations can be concurrently committed for multiple non-Admin-VSs. However, if configurations that affect Admin-VS are modified for a non-Admin-VS, configurations cannot be committed for other non-Admin-VSs during configuration commission for this non-Admin-VS.

None

Configurations may fail to be committed for some VSs, and you need to try again in this case.

Labels in the system are unique and cannot conflict with each other even in different VSs.

Do not configure the same label for different non-Admin-VS VSs.

None

All VSs except Admin-VS do not support .dat configuration files.

None

A non-Admin-VS does not support fast startup in DAT mode.

Forwarding plane performance alarms and flow creation rate control are performed at the board level, not at the VS granularity.

None

None

Creating a VS does not change the service specifications of the device or boards.

For example: Before a VS is created, the device supports n BGP peers. After a VS is created, the number of BGP peers is still n.

None

None

If the memory of the master main control board is inconsistent with that of the slave main control board, a master/slave main control board switchover or device restart occurs, which may cause VS configurations to be lost.

If the memory of the master main control board is inconsistent with that of the slave main control board, increase the memory of the master or slave main control board to achieve memory consistency.

VS configurations may be lost.

The device can deliver the configurations for up to 21 users. The configurations of all other users can only be queried. Users of non-Admin-VSs are in preemption mode.

None

None

A non-Admin-VS does not support the maintenance assistance function. Admin-VS collects information uniformly.

None

None

KPI files generated through the KPI diagnosis function are not independently saved by VS.

None

None

The display diagnostic-information command can be run in the Admin-VS 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.

None

The execution efficiency of the one-click diagnostic command is affected.

When an interface and its sub-interfaces are deployed in different VSs, ESI route negotiation is not supported.

Deploy an interface and its sub-interfaces in the same VS.

If an interface and its sub-interfaces are deployed in different VSs and an ESI is configured on the interface, the sub-interfaces fail to forward packets.

The clock service can be configured only in Admin-VS.

None

Configurations will fail to be committed for VSs.

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

None

None

The group-mac of L2TP and BPDU tunnels can be configured only in Admin-VS.

None

None

An ATM bundle interface can be created Admin-VS or VSn. An ATM bundle interface in Admin-VS cannot be bound to VSn.

None

None

ATM bundle interfaces, IMA sub-interfaces, serial sub-interfaces, and global IMA-group sub-interfaces can be created in VSn but cannot be migrated from Admin-VS to VSn.

None

None

IMA, serial, trunk serial, MP-group, global MP-group, global IMA-group, virtual serial, and PHY-serial interfaces can be created in Admin-VS. These interfaces cannot be created in VSn but can be migrated from Admin-VS to VSn.

None

None

E1, E3, T1, T3, CPOS, and CPOS-Trunk interfaces can be created only in Admin-VS. These interfaces cannot be created in VSn or migrated from Admin-VS to VSn.

None

None

The Controller's interfaces can be configured only in Admin-VS and cannot be allocated to VSn.

None

None

An MLPPP interface can be created only in Admin-VS.

None

None

A serial main interface can be created only in Admin-VS.

None

None

A CPOS-Trunk interface can be created only in Admin-VS. A CPOS-Trunk interface in Admin-VS cannot be bound to VSn.

None

None

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

None

None

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

None

None

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

None

None

An IMA-group sub-interface 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.

None

None

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

None

None

A global IMA-group main interface can be created only in Admin-VS.

None

None

Different VSs cannot be configured with the same PWE3 static VC label.

None

None

The EVPN supports multiple VSs, but the ESI-ID is unique on a device.

Do not configure the same ESI-ID for different non-Admin-VS VSs.

None

The function of filtering DHCP packets based on the whitelist does not support multiple VSs.

Configure the whitelist function only in Admin-VS.

None

The CPU-defend policy 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.

None

None

Layer 2 loop detection must be configured in the slot view. It can only be configured in Admin-VS command and take effect in all VSs.

None

None

Layer 3 loop detection can be configured and takes effect only in Admin-VS. It does not take effect in VSn.

None

None

The SOC, including the commands in the SOC view, can be configured only in Admin-VS and takes effect in all VSs.

None

None

Host-CAR does not support multiple VSs.

None

None

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

None

None

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

None

None

802.1X port-based authentication does not support multiple VSs. (802.1X port-based authentication can be configured only in the Admin-VS.)

None

None

Different names and IDs must be configured for NAT instances, service-locations, service instance groups on different VSes.

Configure different names and IDs for NAT instances, service-locations, service instance groups on different VSes.

NAT instances, service-lcoations, service instance groups on different Vses cannot have the same name or ID.

After port mirroring is configured on a main interface, the port mirroring configuration becomes ineffective on its sub-interface, regardless of whether the main interface and its sub-interface belong to the same independent VS.

N/A

After port mirroring is configured on a main interface, the port mirroring configuration becomes ineffective on its sub-interface, regardless of whether the main interface and its sub-interface belong to the same independent VS.

The virtual access and VS functions are exclusive.

None

Virtual access 2.0 and VC cannot co-exist.

A non-Admin-VS does not support independent system software. That is, Admin-VS and non-Admin-VSs can only use system software of the same version.

None

None

A non-Admin-VS does not support an independent PAF or license file.

None

None

A non-Admin-VS does not support serial ports.

To operate a non-Admin-VS through a serial port, log in to the Admin-VS and then to the non-Admin-VS.

None

A non-Admin-VS does not support the NTP function.

None

None

A non-Admin-VS does not support the DCN function.

None

None

A non-Admin-VS does not support master/slave switchovers.

None

None

Patches cannot be loaded in the view of a non-Admin-VS.

None

None

A non-Admin-VS does not support system time configuration. Only system time and time zone information can be queried.

None

None

A non-Admin-VS does not support system monitoring configuration. Only CPU and memory usage information can be queried.

None

None

A non-Admin-VS does not support IP FPM measurement flags.

None

None

The destination IP address 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.

None

None

A non-Admin-VS does not support management plane protection.

None

None

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055400

Views: 20240

Downloads: 30

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next