Cisco Cisco Prime IP Express 8.3 Technical References
Sets an authentication expiration date, using date format or the
forever keyword. Dates can be in the 2h (two hours ago, for
example) or month day hour:minute[:second] year format.
Formats for the date are:
+
Time in the future, where num is a decimal number and unit
is s, m, h, d, or w for seconds, minutes, hours, days or
weeks, respectively.
:[:]
Month, day, 24-hour time, and 2-or-4-digit-year.
For example: Jun 30 20:00:00 2007. Enter the time that is
local to the nrcmd process.
forever
Does not expire the authentication for this client.
forever keyword. Dates can be in the 2h (two hours ago, for
example) or month day hour:minute[:second] year format.
Formats for the date are:
+
Time in the future, where num is a decimal number and unit
is s, m, h, d, or w for seconds, minutes, hours, days or
weeks, respectively.
:[:]
Month, day, 24-hour time, and 2-or-4-digit-year.
For example: Jun 30 20:00:00 2007. Enter the time that is
local to the nrcmd process.
forever
Does not expire the authentication for this client.
client-class-name
(0)
Identifies the client-class to which a client belongs. If the client
is not a member of a client-class, then the DHCP server uses the
default client-class properties.
is not a member of a client-class, then the DHCP server uses the
default client-class properties.
default-vpn
Names the VPN to assign to clients that do not already have a
vpn-id or vrf-name value.
vpn-id or vrf-name value.
Gives the domain name (which must be a zone) to use when performing
DNS updates. Places the client's A record in this DNS domain.
This feature is maintained for compatibility with prior versions.
Additional options to specify the forward zone are provided on
the client policy (or embedded policy) and its referenced
DNSUpdateConfig objects.
DNS updates. Places the client's A record in this DNS domain.
This feature is maintained for compatibility with prior versions.
Additional options to specify the forward zone are provided on
the client policy (or embedded policy) and its referenced
DNSUpdateConfig objects.
(0)
Specifies the embedded policy object for this client.
Specifies the hostname. Use this string to replace any hostname
DHCP option that the DHCP client sends. The two forms for
specifying the hostname are:
1. A string that does not start with an at (@) sign. This form
of host-name value is used to override the DHCP client
request host name. When you enter a valid name, you cause
the DHCP server to ignore any host-name specified by this
client, and, instead, use this client-entry attribute. The
actual value of the hostname option in the client's DHCP
packet is ignored. You can use any valid DNS name. You
cannot use underscores (_)in the hostname.
2. A string that starts with an at (@) sign. Network Registrar
uses this form of hostname value to signal the following
special handling:
@host-name-option
Causes the server to use whatever hostname option the
client sent. This is the default behavior if there is no
entry for hostname in either the client or client-class.
@no-host-name-option
Causes the server to drop the hostname option that the
client sent, and not replace it. If you have disabled DNS
name synthesis, then the client will have no name placed
into DNS.
@use-macaddress
Causes the server to synthesize a hostname for the
client that is derived from its MAC address, and is
thus unique. This token is used to ensure that a
client has a valid name in DNS.
This feature is maintained for compatibility with earlier versions.
Additional options for hostname synthesis are provided on the
DNSUpdateConfig object referenced by the policy hierarchy.
DHCP option that the DHCP client sends. The two forms for
specifying the hostname are:
1. A string that does not start with an at (@) sign. This form
of host-name value is used to override the DHCP client
request host name. When you enter a valid name, you cause
the DHCP server to ignore any host-name specified by this
client, and, instead, use this client-entry attribute. The
actual value of the hostname option in the client's DHCP
packet is ignored. You can use any valid DNS name. You
cannot use underscores (_)in the hostname.
2. A string that starts with an at (@) sign. Network Registrar
uses this form of hostname value to signal the following
special handling:
@host-name-option
Causes the server to use whatever hostname option the
client sent. This is the default behavior if there is no
entry for hostname in either the client or client-class.
@no-host-name-option
Causes the server to drop the hostname option that the
client sent, and not replace it. If you have disabled DNS
name synthesis, then the client will have no name placed
into DNS.
@use-macaddress
Causes the server to synthesize a hostname for the
client that is derived from its MAC address, and is
thus unique. This token is used to ensure that a
client has a valid name in DNS.
This feature is maintained for compatibility with earlier versions.
Additional options for hostname synthesis are provided on the
DNSUpdateConfig object referenced by the policy hierarchy.
over-limit-client-class-name