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-M2 V800R010C10SPC500 Feature Description - User Access 01

This is NE40E-M2 V800R010C10SPC500 Feature Description - 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).
IPv4 Address Management

IPv4 Address Management

Address Pool

The NE40E can manage IPv4 addresses in the local address pool, remote address pool, or relay address pool:

  • Local Address Pool

  • A local address pool is managed by the NE40E. The NE40E allocates, renews the lease, and reclaims the IP addresses that belong to the local address pool.

  • Remote Address Pool

  • A remote address pool is a mapping of the remote DHCP or BOOTP server. No actual IP address is configured in the remote address pool. It maps the DHCP or BOOTP server to the address pool.

  • When a remote address pool is used, the NE40E initiates a request for a user or relay a user's request. In this way, the NE40E applies for an IP address, requests the DHCP or BOOTP server to renew the lease of the IP address, or requests the DHCP or BOOTP server to reclaim the IP address.

Address Protection

Address protection prevents IP addresses in an address pool from being allocated or used. The following address protection methods are available:

  • Locking the IP address pool

  • An IP address pool can be locked through the command line interface. Once an address pool is locked, IP addresses in it cannot be allocated any more.

  • This method is usually used when users already use certain IP addresses in the address pool. After the address pool is locked, no more IP address is assigned. After all the users log out and the occupied IP addresses are released, the address pool can be deleted.

  • Excluding the IP address

  • This method is applicable to a complex network where some of the IP addresses need to be excluded.

  • Setting the conflict flag

  • If an IP address in the address pool cannot be used because it conflicts with the IP address of a device, the flag of the IP address can be set to Conflict. When the conflict is cleared, the flag of the IP address can be reset manually.

  • Reclaiming the IP address

  • If an IP address in the address pool is deadlocked, that is, if the IP address is in the "Occupied" state but no user uses it at all, the IP address can be reclaimed through the command line interface.

Address Lease

Address reservation implies a dynamic allocation of fixed addresses.
  • Lease-based reservation: An IP address is dynamically allocated to a client in priority. After the client goes offline, the binding relationship between the IP address and client retains until the lease time elapses. During the lease time, the IP address can be allocated only to this client other than other users.

  • MAC-based reservation: An IP address is dynamically allocated to a client in priority. After the client goes offline, the binding relationship between the IP address and client retains and cannot be allocated to any other users.

Address Overlap

The IP addresses of address pools in different VPN instances can overlap each other.

Address Pool Selection Policy

In a user online scenario, an address pool needs to be selected from the address pool list bound to the user domain for further address allocation.

Currently, multiple policies are available for selecting an address pool. By default, a local address pool is selected preferentially. If required, the user can configure the policy of selecting a remote address pool prior to a local address pool in the user domain. Additionally, a user can configure a policy of allocating IP addresses from a public address pool and selecting an address pool from a local address pool prior to a remote address pool. After such a policy is configured, if the public address pool contains both a local address pool and a remote address pool, the local address pool is selected preferentially. If no public address pool is available, IP addresses are allocated from a private address pool, and a local private address pool is selected prior to a remote private address pool. If multiple local address pools are available, an address pool is selected based on the configuration order of these address pools. If multiple remote address pools are available, an address pool is selected based on the number of DHCP server response failures. The remote address pool that has a smaller number of DHCP server response failures has a higher priority.

For DHCP access users, an address pool can also be selected based on the Option60 field. If the Option60 field fails to match any address pool, other policies are used for address pool selection.

Download
Updated: 2019-01-02

Document ID: EDOC1100058415

Views: 12136

Downloads: 8

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