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

ME60 V800R010C10SPC500 Configuration Guide - Virtual Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - Virtual Access
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 Virtual Access Solution Deployment

Licensing Requirements and Limitations for Virtual Access Solution Deployment

Licensing Requirements

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

Restrictions and Guidelines

Restrictions

Guidelines

Impact

In PWIF trunk access scenarios, user entries are delivered to boards where internal communication interfaces reside. If each board on a master has an internal communication interface to an AP, the master supports 64K access users.

If trunk member interfaces/virtual access internal communication interfaces reside on different subcards of the same board, each board supports only 64K single- or dual-stack users.

Check that each board on a master does not have an internal communication interface to an AP.

The user specification cannot be reached.

In inter-AP trunk access scenarios, the maximum number of active links is 1,

Configure LACP and set the maximum number of active links to 1 in inter-AP trunk access scenarios.

None

PWIF Trunk load balancing is implemented on masters. Two-level load balancing depends on networking and cannot ensure load balancing between internal communication interfaces. Two-level load balancing is described as follows:Load balancing is implemented between external communication interfaces to preferentially ensure downstream traffic's balancing effect on APs. After an external communication interface is selected, an internal communication interface and its logic table are selected from multiple internal communication interfaces for the external communication interface based on the total loads of the internal communication interfaces.

None

Loads between internal communication interfaces are unbalanced.

In PWIF physical access scenarios, the boards for the master's interfaces learned by the PWIF interface deliver user entries. If a customer network is not planned properly (members on all the boards on the master have physical interfaces as internal communication interfaces), the number of access users on the master is equal to the number of access users on boards.

Check that each board on a master does not have an internal communication interface to an AP.

The user specification cannot be reached.

In PWIF user access scenarios, interface information is in four-dimensional format, and must match the RADIUS and DHCP servers.

None

The RADIUS and DHCP servers fail to parse packets.

For BRAS access users' QoS/HQoS, eTM subcards must be configured on a master's internal communication interface.

Configure eTM subcards if virtual access uses QoS/HQoS services.

QoS/HQoS does not take effect.

eTM and non-eTM subcards cannot be together configured on boards where internal communication interfaces reside.

Do not configure both eTM and non-eTM subcards on a master's boards where internal communication interfaces reside.

None

A master supports LAC virtual access. When the AVP22 attribute is encapsulated into an ICRQ packet, interface information is in four-dimensional format, which is different from that for non-virtual access LAC users. If the LNS parses interface information, a four-dimensional interface must be used.

None

A master supports LAC virtual access. When the AVP22 attribute is encapsulated into an ICRQ packet, interface information is in four-dimensional format, which is different from that for non-virtual access LAC users. The LNS is required to support a four-dimensional interface.

When BAS access is configured on a master, all boards where internal communication interfaces reside must have the BAS access functions (including hardware and logic functions.some boards can support BAS access only after the license is loaded).

Load the license on all boards where internal communication interfaces reside when BAS access is configured on a master.

BAS cannot be configured on PWIF interfaces.

Virtual access multi-device backup does not support load balancing based on odd and even MAC addresses. The minimum granularity for controlling virtual access multi-device backup is PWIF interfaces without distinguishing between odd and even MAC addresses.

None

None

The limitations for IPv6 to support virtual access are as follows:
  • Does not support IGP (OSPFv3/IS-ISv6/RIP) between the CE and master device.
  • Does not support 6PE and 6VPE between the CE and master device.
  • Does not support the scenario where an AP is not directly connected to the master device.
  • Does not support protection links between master devices, or the scenario where links between master devices are protected using VSIs (that is, IPv6 BGP peers are created through BDIF interfaces).

None

The feature does not take effect.

An AP does not allow you to modify the L3VPN DiffServ mode. The default mode is uniform.

None

An AP does not perform scheduling based on the configured DiffServ mode.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059451

Views: 3760

Downloads: 18

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