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

NE40E V800R010C10SPC500 Configuration Guide - User Access 01

This is NE40E V800R010C10SPC500 Configuration Guide - User 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 IPoE

Licensing Requirements and Limitations for IPoE

Licensing Requirements

BOM

License Control Item

Description

Minimum Version Requirement

81400370

NetEngine40E PPPoE/IPoE Function License

Controllable feature:

This license controls the PPPoE/IPoE function.

V800R008

82400408

NetEngine40E PPPoE/IPoE Function License for LPUF-120

Controllable feature:

This license controls PPPoE/IPoE for NE40E LPUF-120s. One board requires one such license.

V800R008

82400413

NetEngine40E PPPoE/IPoE Function License for LPUI-120

Controllable feature:

This license controls PPPoE/IPoE for NE40E LPUI-120s. One board requires one such license.

V800R008

82400410

NetEngine40E PPPoE/IPoE Function License for LPUF-240

Controllable feature:

This license controls PPPoE/IPoE for NE40E LPUF-240s. One board requires one such license.

V800R008

82400414

NetEngine40E PPPoE/IPoE Function License for LPUI-240

Controllable feature:

This license controls PPPoE/IPoE for NE40E LPUI-240s. One board requires one such license.

V800R008

82400866

NetEngine40E PPPoE/IPoE Function License for LPUF-480

Controllable feature:

This license controls PPPoE/IPoE for NE40E LPUF-480s. One board requires one such license.

V800R009

82400881

NetEngine40E PPPoE/IPoE Function License for LPUI-480

Controllable feature:

This license controls PPPoE/IPoE for NE40E LPUI-480s. One board requires one such license.

V800R009

82400966

NetEngine40E 100G PPPoE/IPoE Port License(per 100G)

Controllable feature:

This license controls PPPoE/IPoE for a 100G interface on the CM board.

V800R009

82400922

NetEngine40E 10G PPPoE/IPoE Port License(per 10G)

Controllable feature:

This license controls PPPoE/IPoE for a 10G interface on the CM board.

V800R009

82400923

NetEngine40E 1G PPPoE/IPoE Port License(per 1G)

Controllable feature:

This license controls PPPoE/IPoE for a 1G interface on the CM board.

V800R009

Restrictions and Guidelines

Restrictions

Guidelines

Impact

Restrictions on IPv6 web authentication users:
  • Users who obtain IPv6 addresses with shared prefixes through ND are not supported.
  • vCPE users are not supported.
  • A dual-stack web user goes online in the pre-authentication domain and is switched to the authentication domain from the IPv6 stack. After the user goes offline from the IPv6 stack by sending a Release message, the user cannot be switched to the pre-authentication domain from the IPv4 stack. A dual-stack web user is switched to the authentication domain from the IPv4 stack. After the user goes offline from the IPv4 stack by sending a Release message, the user cannot be switched to the pre-authentication domain from the IPv6 stack.
  • If the IP address of the web server configured in the pre-authentication domain is the same as that of the portal server configured in the authentication domain, users are redirected to the specified portal server address for the number of times specified by the portal-server redirect-limit limit command.

None

None

When the RADIUS server delivers the Framed-Route attribute to a leased line user, user-to-network traffic does not support source IP address check (URPF).

Do not deliver the Framed-Route attribute to leased line users if you have high requirements for source IP address check.

The URPF function does not take effect.

If a DHCPv6 packet carries the IA_NA and IA_PD options at the same time, an HG cannot send two Solicit messages to obtain an IPv6 prefix and address respectively. If two Solicit messages are sent, the address type requested in the first Solicit message is assigned for the second Solicit message.

A client needs to carry IP address and prefix information at the same time.

Users fail to go online.

If a Layer 3 DHCPv6 user sends a login request carrying the IA_NA option, the user cannot be directly connected to the BAS interface and must be connected to the BAS interface through a Layer 3 device. The user can apply for an IPv6 address only.

If a client DUID is generated in LLT or LL mode, user access is supported. If a client DUID is generated in other modes, user access is supported only when the first-hop relay agent sends a DHCPv6 message in which the Option 37 carries the client's MAC address to the BRAS. User access is not supported if the preceding conditions are not met.

Clients are required to obtain IPv6 addresses through DHCPv6,

Users fail to go online.

Separate collection of statistics about IPv4 and IPv6 traffic is not supported for Layer 3 leased line users.

Do not collect statistics about IPv4 and IPv6 traffic separately for Layer 3 leased line dual-stack users.

All traffic of dual-stack Layer 3 leased line users is counted as IPv4 traffic.

WLAN user roaming switchover supports only IPoE user access (excluding static users for whom the device initiates ARP packets to trigger user login, static users with the same MAC address and different IP addresses, and all leased line users).

Plan configurations properly when deploying WLAN user roaming switchover.

Roaming procedures cannot be triggered for static users for whom the device initiates ARP packets to trigger user login and static users with the same MAC address but different IP addresses on the BAS interface with roaming switchover configured.

The interface configuration of leased line users is mutually exclusive with the roaming switchover configuration.

Roaming switchover between different interface types is not supported.

Plan configurations properly when deploying WLAN user roaming switchover.

There is a restriction on roaming switchover between different interface types.

Flexible access to a VPN supports only PPPoEv4 users, dynamic IPoEv4 users, and static IPoEv4 users.

None

Flexible access to a VPN does not take effect for users not supported.

The auto save feature supports Layer 2 DHCPv4 users with the authentication and accounting modes set to non-authentication and non-accounting, respectively.

None

The auto save function does not take effect.

The LPUI-51-L board supports basic forwarding and does not support user-side UCL and BA if it is used as a network-side board for IPoX/PPPoX access. The 50B board does not support frame-route load balancing, or load balancing when a static route is configured with the next hop being the user address.

Deploy relevant services on a non-LPUI-51-L board.

Relevant services do not take effect.

In a scenario where the next hop of a static route is the IP address of a static user, multiple next hops are not supported for the static user, that is, route load balancing is not supported.

Do not configure a static user's IP address as the next hop of a static route in load-balancing scenarios.

Load balancing does not take effect.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 17683

Downloads: 72

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