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).
Configuring a DHCPv6 Relay Agent on the User Side

Configuring a DHCPv6 Relay Agent on the User Side

When independent DHCPv6 servers allocate and manage addresses, the NE40E can be configured as the relay agent to implement redundancy backup and load balancing among the remote DHCPv6 servers.

Usage Scenario

When users access the NE40E, it functions as a DHCPv6 relay agent and forwards user address requests to the remote DHCPv6 servers. Configuring multiple DHCPv6 servers is recommended to perform redundancy backup and load balancing among the remote servers. The DHCPv6 server group must be bound to the remote address pool. This binding shields the interactions between NE40E and DHCPv6 servers from the client.

Figure 5-1 Networking diagram of the NE40E as a DHCPv6 relay agent on user side

Pre-configuration Tasks

The remote DHCPv6 servers have been deployed.

Configuration Procedures

Figure 5-2 Flowchart for configuring a DHCPv6 relay agent on the user side

Configuring a Remote IPv6 Prefix Pool

When the NE40E functions as a DHCPv6 relay agent, a remote IPv6 prefix pool must be configured to manage the prefixes.

Context

Perform the following steps on the NE40E.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ipv6 prefix prefix-name remote

    A remote IPv6 prefix pool is created and the IPv6 prefix pool view is displayed.

  3. Run link-address ipv6-address / prefix-length

    The link address is configured.

    When the remote server allocates addresses or prefixes, link addresses must be configured on the relay.

  4. (Optional) Run lock

    The IPv6 prefix pool is locked.

    No prefix in the locked IPv6 prefix pool can be allocated, preventing new users from getting online using the IPv6 prefix pool.

    This command applies to a scenario where the IPv6 prefix pool cannot be deleted because it is being used by online users. Lock the IPv6 prefix pool first to stop it from allocating prefixes. The prefixes in the IPv6 prefix pool will be released when the users get offline. Then the IPv6 prefix pool can be deleted.

  5. (Optional) Run vpn-instance vpn-instance-name

    The VPN instance is configured for the prefix pool.

  6. Run remote-ip lease manage

    The lease management function is enabled for the remote ipv6 prefix pool.

  7. Run commit

    The configuration is committed.

Configuring a Remote IPv6 Address Pool

Configuring an IPv6 remote address pool including binding the prefix pool to the remote address pool and configuring priority of the address pool and the route advertisement of the address pool.

Context

Perform the following steps on the NE40E.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ipv6 pool pool-name bas remote

    An IPv6 address pool is created, and the IPv6 address pool view is displayed.

  3. Run prefix prefix-name

    The IPv6 address pool is bound to the IPv6 prefix pool.

  4. (Optional) Run preference preference-value

    A priority value is set for the IPv6 address pool.

  5. Run export host-route

    Advertisement of the routes in the remote address pool is enabled.

  6. (Optional) Configure the device to assign addresses from IPv6 remote address pools based on weights of the address pools.

    1. Run weight weight-valuecommit

      A weight is configured for the IPv6 address pool.

    2. Run commit

      The configuration is committed.

    3. Run quit

      Return to the system view.

    4. Run ipv6-pool algorithm loading-share remote

      The device is configured to assign addresses from IPv6 remote address pools based on their weights.

      NOTE:
      This function applies only to IPv6 remote address pools and local rui-slave address pools.

  7. Run commit

    The configuration is committed.

Configuring a DHCPv6 Server Group

DHCPv6 server groups are required only when the remote address pool is used to assign IPv6 addresses to BAS-side users.

Context

Perform the following steps on router:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run dhcpv6-server group group-name

    A DHCPv6 server group is created and the DHCPv6 server group view is displayed.

  3. Run dhcpv6-server { destination ipv6-address [ vpn-instance vpn-instance ] | interface interface-type interface-number } [ weight weight-value ]

    The IPv6 address or outbound interface of a DHCPv6 server is configured.

    A maximum of eight DHCPv6 servers can be configured in a DHCPv6 server group.

  4. (Optional) Run dhcpv6-server algorithm { loading-share | master-backup | polling }

    Load balancing or redundancy backup is configured.

    This command takes effect only when there are multiple DHCPv6 servers in a DHCPv6 server group.

    • Load balancing: The NE40E distributes the traffic based on the weights of DHCPv6 servers.
    • Master/backup: The NE40E specifies one server as the master server and the others as the backup server.
    • Polling: When multiple servers are configured, the NE40E sends Solicit, Request, Rebind, and Confirm messages to all servers and selects the server that first responds to the messages for subsequent message exchanges.

  5. (Optional) Run release-agent

    The DHCPv6 release agent function is configured.

    With the DHCPv6 release agent function, the NE40E sends DHCPv6 Release packets to DHCPv6 servers for the users when they get offline.

  6. (Optional) Run dhcpv6-server source { interface interface-type interface-name | link-address }

    The source address or source interface for packets to be sent to the DHCPv6 server group is configured.

  7. Run quit

    The system view is displayed.

  8. (Optional) Enable the DHCPv6 relay agent to add the Option 18 and Option 37 attributes in OSP format to a Relay-Forward message sent to a DHCPv6 server.
    1. Run interface interface-type interface-number

      The system view is displayed.

    2. Run dhcpv6 relay option-insert mode type1 [ remote-id { neba | vula } ]

      The DHCPv6 relay agent is enabled to add the Option 18 and Option 37 attributes in OSP format to a Relay-Forward message sent to a DHCPv6 server.

      NOTE:
      • The dhcpv6 relay option-insert mode type1 [ remote-id { neba | vula } ] and dhcpv6 relay option-insert { interface-id mode { cn-telecom | tr-101 } | remote-id } commands are mutually exclusive.
      • The dhcpv6 relay option-insert mode type1 command takes effect in real time. After the command is run on an interface, the command configuration takes effect for online users on the interface.

    3. Run quit

      Return to the system view.

  9. (Optional) Run dhcpv6-server [ ipv6-address [ vpn-instance vpn-instance ] ] { dead-count dead-count | timeout timeout-value | dead-time dead-time } *

    The threshold of status (Up/Down) switchover for a DHCPv6 server are configured.

  10. (Optional) Run dhcpv6-server { ipv6-address [ vpn-instance vpn-instance-name ] | interface interface-type interface-number } send-solicit-speed packet-number time

    The rate at which Solicit packets are sent to the DHCPv6 server is configured.

  11. Run commit

    The configuration is committed.

Associating an Address Pool with a DHCPv6 Server Group

Associating an address pool with a DHCPv6 server group is required only when the remote IPv6 address pool is used.

Context

Perform the following steps on NE40E.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ipv6 pool pool-name bas remote

    The remote address pool view is displayed.

  3. Run dhcpv6-server group group-name

    An address pool is associated with a DHCPv6 server group.

  4. Run commit

    The configuration is committed.

Binding an IPv6 Remote Address Pool to a Domain

Users in the domain can obtain addresses from the address pool only after an IPv6 address pool is bound to a domain.

Prerequisites

The address pool to be bound has been created and bound to a prefix pool.

Context

Perform the following steps on router.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run aaa

    The AAA view is displayed.

  3. Run domain domain-name

    A domain is created and the domain view is displayed.

  4. Run ipv6-pool pool-name

    The IPv6 remote address pool is bound to the domain.

  5. (Optional) Run ipv6-warning-threshold threshold-value

    The threshold for the usage of IPv6 addresses and prefixes is configured.

  6. Run commit

    The configuration is committed.

(Optional) Enabling a Device to Insert the Option 18 and Option 37 Attributes into Messages to Be Sent to the DHCPv6 Server

This section describes how to enable a device to insert the self-defined Option 18 and Option 37 attributes into the Relay-forward messages to be sent to the DHCPv6 server when IPv6 addresses are assigned from a remote IPv6 address pool.

Context

When IPv6 addresses are assigned from a remote IPv6 address pool, you can configure the device to insert the self-defined Option 18 and Option 37 attributes into Relay-forward messages to be sent to the DHCPv6 server.

Option 18 identifies the interface on which client messages are received on a DHCP relay agent, facilitating the forwarding of Relay-reply messages. The DHCP server can also assign addresses/prefixes based on the Option 18 attribute, which plays a similar role as the circuit-id sub-attribute carried in the Option 82 attribute of DHCP messages.

A DHCP relay agent inserts additional information about remote users into the Option 37 attribute, which plays a similar role as remote-id sub-attribute carried in the Option 82 attribute of DHCP messages.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number [ .subinterface-number ]

    The interface view is displayed.

  3. Run bas

    The BAS interface view is displayed.

  4. Run dhcpv6 option-18 rebuild self-define self-define-value send-to-server

    The device is enabled to insert the self-defined Option 18 attribute into a Relay-forward message to be sent to the DHCPv6 server.

    The dhcpv6 option-18 rebuild self-define self-define-value send-to-server command is configured in the BAS interface view, whereas the dhcpv6 relay option-insert interface-id mode { cn-telecom | tr-101 } and dhcpv6 relay option-insert mode type1 commands are configured in the interface view. If the commands configured in the two views are both run, the command configured in the BAS interface view takes effect.

  5. Run dhcpv6 option-37 rebuild self-define self-define-value send-to-server

    The device is enabled to insert the self-defined Option 37 attribute into a Relay-forward message to be sent to the DHCPv6 server.

    The dhcpv6 option-37 rebuild self-define self-define-value send-to-server command is configured in the BAS interface view, whereas the dhcpv6 relay option-insert remote-id and dhcpv6 relay option-insert mode type1 commands are configured in the interface view. If the commands configured in the two views are both run, the command configured in the BAS interface view takes effect.

Verifying the DHCPv6 Relay Agent Configuration

After the DHCPv6 relay agent is configured, you can check the DHCPv6 server group configurations, including the DHCPv6 server DUID and the address pool bound to the domain.

Procedure

  • Run the display ipv6 pool [ pool-name ] command to check the IPv6 address pool configurations.
  • Run the display ipv6 prefix [ prefix-name [ all | used ] ] command to check the IPv6 prefix pool configurations.
  • Run the display dhcpv6-server statistics { ipv6-address [ vpn-instance vpn-instance ]| interface interface-type interface-number }command to check packet statistics on a DHCPv6 server.
  • Run the display dhcpv6-server item { ipv6-address [ vpn-instance vpn-instance ] | interface interface-type interface-number } command to check information about the DHCPv6 server.
  • Run the display ipv6-pool max-ratio domain command to check information about IPv6 address pool or prefix pool usage in all domains on the device.
  • Run the display ipv6-pool pool-usage { upper-threshold | lower-threshold | all-threshold } command to check information about domains whose IPv6 address pool or prefix pool usage exceeds a specified threshold.
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 17775

Downloads: 72

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