Changing the DHCPv6 Option Code for Interconnection Between Huawei and Non-Huawei Devices

On the NetEngine 8000 F, the vendor-class attribute is carried in DHCPv6 Option 16. The option code probably differs with that on a non-Huawei device. The DHCPv6 option code can be changed for interconnection between Huawei and non-Huawei devices.

Context

If the mapping between the vendor-class attribute and a DHCPv6 option code is configured in both system and BAS interface views, the configuration in the BAS interface view takes effect.

Procedure

Configure a mapping between the vendor-class attribute and a DHCPv6 option code in the system view.
1. Run system-view
  The system view is displayed.
2. Run vendor-class dhcpv6 { option-code option-code | offset offset } ^*
  The mapping between the vendor-class attribute and a DHCPv6 option code as well as the offset value are configured. After the configuration is complete, the BRAS uses the offset value to obtain the desired contents in the Value field of the DHCPv6 option.
3. Run commit
  The configuration is committed.
Configure a mapping between the vendor-class attribute and a DHCPv6 option code in the BAS interface view.
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
  A BAS interface is created, and the BAS interface view is displayed.
4. Run any of the following commands:
  - To set the access type to Layer 2 subscriber access and configure the attributes of this access type, run the access-type layer2-subscriber [ bas-interface-name bname | default-domain { pre-authentication predname | authentication [ force | replace ] dname } ^* | accounting-copy radius-server rd-name ] ^* command.
  - To set the access type to Layer 3 subscriber access and configure the attributes of this access type, run the access-type layer3-subscriber [ default-domain { [ pre-authentication predname ] authentication [ force | replace ] dname } ] command.
  - When setting the access type of a BAS interface, you can set the service attributes of the access users at the same time. You can also set these attributes in later configurations.
  - To specify the IP address segment for Layer 3 common users, run layer3-subscriber start-ip-address end-ip-address [ vpn-instance instance-name ] domain-name domain-name
  - To specify the authentication domain for Layer 3 common users, run layer3-subscriber ip-address any domain-name domain-name
  - To configure a mask so that an IPv4 address segment and an authentication domain name are specified for Layer 3 static users, run layer3-subscriber subnet-session start-ip-address { mask-address | mask-length } [ vpn-instance instance-name ] [ domain-name domain-name ] [ routed [route-preference preference-value ] ]
  - The access type cannot be configured on the Ethernet interface that is added to an Eth-Trunk interface. You can configure the access type of such an Ethernet interface only on the associated Eth-Trunk interface.
  - When configuring static routes for Layer 3 users, specify the next hop as the user IP address and do not specify the outbound interface. Otherwise, network-to-user traffic may fail to be forwarded.
5. Run vendor-class dhcpv6 { option-code option-code | offset offset-length }^*
  The mapping between the vendor-class attribute and a DHCPv6 option code as well as the offset value are configured. After the configuration is complete, the BRAS uses the offset value to obtain the desired content in the Value field of the DHCPv6 option.
6. Run commit
  The configuration is committed.