This section describes how to enable a device to insert Sub-option 2 (remote ID) into the Option 82 attribute or replace Sub-option 2 carried in the Option 82 attribute of a message to be sent to the DHCP server based on a fixed format.
When IP addresses are assigned from a remote address pool to Layer 2 access users, the DHCP server identifies a carrier based on the remote ID carried in the Option 82 attribute of a DHCP message. Therefore, you need to configure a device to insert Sub-option 2 (remote ID) into the Option 82 attribute or replace Sub-option 2 carried in the Option 82 attribute of a message to be sent to the DHCP server based on a fixed format. Self-defined character strings can be encapsulated into Sub-option 2.
The system view is displayed.
The interface view is displayed.
The BAS interface view is displayed.
To enable the device to encapsulate the Option 82 attribute into a message to be sent to the DHCP server in a fixed format, run dhcp option82 rebuild version3 send-to-server [ remote-id { neba | vula } ]
In this format, self-defined content cannot be encapsulated into the Option 82 attribute.
The dhcp option82 rebuild version3 send-to-server command has a higher priority than the dhcp option-82 agent-remote-id strip command.
To enable the device to encapsulate the Option 82 attribute in the format of sysname:interface-name:svlan-cvlan into a message to be sent to the DHCP server, run dhcp option82 rebuild version4 send-to-server
To enable the device to encapsulate the Option 82 attribute into a message to be sent to the DHCP server based on the fixed OSP format, run dhcp option82 rebuild self-define { circuit-id circuit-id-value | out-vlan out-vlan-value | inner-vlan inner-vlan-value | remote-id remote-id-value } * send-to-server
In this format, self-defined content can be encapsulated into the Option 82 attribute.
The dhcp option82 rebuild send-to-server command takes effect only after DHCP proxy is enabled on the BAS interface.
The configuration is committed.