Cisco Cisco Prime IP Express 8.3 Referencia técnica
ip6address
Specifies the address to which the service is bound. To accept
connections to any valid local address, specify :: (the all 0's
address).
If both address and ip6address are unset, the IPv4 address 0.0.0.0
will be used. However, both cannot be set. Create separate objects,
one for IPv4 and another for IPv6 to use the same port for both.
connections to any valid local address, specify :: (the all 0's
address).
If both address and ip6address are unset, the IPv4 address 0.0.0.0
will be used. However, both cannot be set. Create separate objects,
one for IPv4 and another for IPv6 to use the same port for both.
(30s-10m) default = 2m
Specifies the number of seconds of active leasequery updates that the
DHCP server will hold in memory when a connection is blocked.
If multiple listener objects are configured, the DHCP server uses the
longest time for this attribute for all its connections.
DHCP server will hold in memory when a connection is blocked.
If multiple listener objects are configured, the DHCP server uses the
longest time for this attribute for all its connections.
default = false
Specifies whether to send a message to active leasequery
clients for every write to the DHCP lease state database.
The alternative (and the default) is to optimize the traffic
over active leasequery connections and to send only updates
which are necessary to maintain accurate state in the active
leasequery client. The optimizations are largely involved
with failover updates, in an attempt to avoid redundant
active leasequery messages. However, this optimization is
only valid if the active leasequery client connects to both
failover servers. Should you have an active leasequery client
which only ever connects to one failover partner, this
optimization will prevent important data from reaching such
a client and you should enable this attribute to prevent
the optimization. Configuring any listener with this attribute
enabled will cause all active leasequery connections to send
a message for every write to the DHCP lease state database.
clients for every write to the DHCP lease state database.
The alternative (and the default) is to optimize the traffic
over active leasequery connections and to send only updates
which are necessary to maintain accurate state in the active
leasequery client. The optimizations are largely involved
with failover updates, in an attempt to avoid redundant
active leasequery messages. However, this optimization is
only valid if the active leasequery client connects to both
failover servers. Should you have an active leasequery client
which only ever connects to one failover partner, this
optimization will prevent important data from reaching such
a client and you should enable this attribute to prevent
the optimization. Configuring any listener with this attribute
enabled will cause all active leasequery connections to send
a message for every write to the DHCP lease state database.
max-connections
default = 10
Specifies the maximum number of simultaneous connections allowed
for the service.
for the service.
required,unique
Specifies the name of service. This name has no significance.
Specifies the port number on which the DHCP server listens for
TCP connections. The default port is the server-port for DHCPv4
and v6-server-port for DHCPv6.
TCP connections. The default port is the server-port for DHCPv4
and v6-server-port for DHCPv6.
dhcp-subnet
dhcp-subnet - Describes a contiguous range of IP address space
which the DHCP server has allocated to a client.
which the DHCP server has allocated to a client.
Synopsis
dhcp-subnet <dhcp-subnet-number> [show]
dhcp-subnet <subnet-number> get <attribute>
dhcp-subnet <subnet-number> get <attribute>
dhcp-subnet <subnet-number> force-available
Description
The dhcp-subnet commands manipulate subnet objects that the DHCP
server has leased to its clients. When the DHCP server receives a
request for a subnet, it creates the subnet by subdividing its
available address-blocks, and allocating the subnet to the client.
server has leased to its clients. When the DHCP server receives a
request for a subnet, it creates the subnet by subdividing its
available address-blocks, and allocating the subnet to the client.