If you are adding
more complex option values such as for suboptions, use a parenthesized string
format. The format requires that you:
- Enclose each option level
(option, suboption, subsuboption) in parentheses.
- Separate multiple values
with commas.
- Separate data fields for
packed data (missing the suboption code or length) with semicolons.
For example, the
cablelabs-client-configuration option (122) normally has 10
suboptions as well as some subsuboptions. This example shows the syntax to set
the suboption 1, 2, 3, and 4 data values, and includes the two subsuboptions
for suboption 3 and the three subsuboptions for suboption 4 (which are packed
data and have no code numbers):
(primary-dhcp-server 1 10.1.1.10)
(secondary-dhcp-server 2 10.2.2.10)
(provisioning-server 3 (flag 0; provisioning-server server.example.com.))
(as-backoff-retry 4 (as-backoff-retry-initial-time-ms 10;
as-backoff-retry-max-time 10s; as-backoff-retry-count 100))
The suboption name
(such as primary-dhcp-server) is optional. Hence, it is often safer to use just
the code number and data value (or just the data value for packed data) to
minimize typographical errors and parsing failures. The compacted (and
preferred) version of the previous example that strips out the suboption names
is:
(1 10.1.1.10) (2 10.2.2.10) (3 (0;server.example.com.)) (4 (10;10s;100))
Even if you use
numerical code values, Cisco Prime
IP Express always includes the equivalent names when it
displays the suboptions (see
Creating DHCP Option Definition Sets and Option Definitions).
To include suboptions
that include enterprise IDs (such as for option 125), use the following format,
for example, when entering in the policy option value:
(enterprise-id 1((1 10.1.1.1) (2 10.2.2.2) (3 www.cisco.com)))
The parentheses
surround the enterprise ID itself, the suboptions as a group, and each
suboption.