Published on 12 Nov 2013
This document aims to explain this concept by using examples of DHCPv6 embedded options in Broadband Command Center. It is aimed at:
- Broadband Command Center customers interested in using embedded options for DHCPv6 provisioning
- Users with no basic knowledge of how to use embedded options for IPv6 in Broadband Command Center
- Users who want to know which basic IPv6 options can be used to successfully provision a v6 device
Importantly, this document is not intended to be:
- An introduction to all IPv6 options
- Instructions for users who want to know how to provision a vendor-specific IPv6 device
Broadband Command Center Embedded Options
In Broadband Command Center, embedded options are DHCPv4/DHCPv6 settings that are associated to a classifier object (such as Client Class, Device Classifier, and Rules). These options are used by the DHCP of Broadband Command Center for configuration file generation.
How to Use JIMC to Set Embedded Options
To set IPv4 or IPv6 embedded options, you will first need to create a client class/rule object or a Classified Network Settings link through the Broadband Command Center GUI. Currently, as of BCC 6.3 latest GA, these are the only objects with embedded settings implemented in them.
To be more specific, you can access:
Embedded DHCPv6 Options in -> Client Class object, Classified Network Settings (the link between a Client Class and Device Classifier object)
Embedded DHCPv4 Options in -> Client Class object, Rule objects, and Classified Network Settings
From the edit/view windows for these objects, you can view and edit the embedded options in the “Embedded DHCPv4/DHCPv6 options” tab.
Example: Accessing Client Class Embedded Settings in JIMC
To access Client Class embedded settings, you would follow the steps below:
-
Create a Client Class. Once you click create, JIMC will bring you to the edit/view Client Class window
-
Go to the “Embedded v4/v6 option settings”
-
Configure — for example, DHCPv4 option 67
How to Use CLI to set the Embedded Options
To set IPv4 or IPv6 embedded options, you will first need to create a client class/rule object or a Classified Network Settings link through the Broadband Command Center GUI. Currently, as of BCC 6.3 latest GA, these are the only objects with embedded settings implemented in them.
To be more specific, you can access:
Embedded DHCPv6 Options in -> Client Class object, Classified Network Settings (the link between a Client Class and Device Classifier object)
Embedded DHCPv4 Options in -> Client Class object, Rule objects, and Classified Network Settings
Example: Accessing Client Class Embedded Settings in CLI
For Client Classes:
-
Create a Client Class
-
Go to “modify mode” of the Client Class to edit the embedded v4/v6 option settings
-
Configure — for example, DHCPv4 option 67
-
Save the changes
The prompt is like the following (after you successfully login):
172.20.0.239> add clientclass testing222
Object saved.
172.20.0.239> modify clientclass testing222
172.20.0.239[ClientClass:testing222]–> add DHCPOPTION 67
172.20.0.239[ClientClass:testing222]–> set DHCPOPTION 67 data ‘test’
172.20.0.239[ClientClass:testing222]–> save
Object saved.
172.20.0.239[ClientClass:testing222]–> show DHCPOPTION
Insufficient parameters
172.20.0.239[ClientClass:testing222]–> list DHCPOPTION
OPTNUM: 67
NAME: Bootfile Name
DATATYPE: DT_FILE_NAME_CREATION_MASK
DATA: “test”
SIZE: 6
TOTAL DHCPOPTION COUNT: 1
172.20.0.239[ClientClass:testing222]–>
DHCPv4 and DHCPv6 Embedded Options Backward Incompatibility
The specification of IPv4 and IPv6 embedded options does not allow backward compatibility, as the message exchanges involved are drastically different. Hence, when transitioning from IPv4 to IPv6, you are expected to specify a new set of IPv6 options in order for IPv6 provisioning to work.
Advantages of Embedded Options for Migration to DHCPv6
-
Faster Migration
-
Although embedded options from IPv4 to IPv6 are backwards incompatible, the idea of embedded options usage has helped quicken the process of getting a Broadband Command Center stack ready for IPv6 provisioning. This is because you no longer need to spend time linking templates to desired classifier objects.
-
More Organized Structure
