Technical References

Specifies an expression that evaluates to a binary large object
(blob), or a string that can be used as a blob. The resulting
value groups leases that have a maximum limit on the number of
simultaneous active leases allowed. To configure the limit, use
limitation-count attribute of the policy command. See also
the over-limit-client-class attribute.
over-limit-client-class-name string
Designates the client-class used if this client is over the limit
allowed for the specified limitation-id.
override-client-id expr
Specifies the client-identity value for the specified client, using
an expression that evaluates to a binary large object (blob). The
value that is derived from the expression evaluation replaces any
client-id option value in the incoming packet (though in actual
practice, both values are retained in the lease-state database).
override-vpn nameref(VPN)
Determines the VPN to which a client is assigned regardless
of what the client provides for a VPN-ID (or vrf-name) value.
policy-name string
Names the policy that should be used for this client-class.
selection-criteria string
Lists the selection tags for this client-class. All the criteria
in this list must appear in the scope/prefix selection tags for a
scope/prefix to be considered acceptable to this client-class.
unauthenticated-client-class-name string
Names the client-class used if this client is no longer
authenticated.
user-defined string
Provides an opaque user-defined string that can be set
and queried. This property has no effect on the operation
of the DHCP server.
v6-client-lookup-id expr
Specifies the key value used to lookup the DHCPv6 client in the
client database, using an expression that evaluates to a string
or a blob that is a valid string. The lookup can be local or through
LDAP.
v6-override-client-id expr
An expression which evaluates to a blob which is used for the
client-identity value for the current DHCPv6 client. Conceptually
this value derived from the expression evaluation will replace any
client-id option value in the incoming packet (though in actual
practice, both values are retained in the lease-state database).
client-class-policy