Cisco Cisco Network Registrar 7.1 릴리즈 노트
11
Release Notes for Cisco Network Registrar 7.1.1
OL-21835-01
New and Changed Features
New and Changed Features
This following are the topics covered in this section:
•
•
New and Changed Features in CNR Release 7.1.1
This following are the topics covered in this section:
•
•
VMWARE Support
CNR now supports running in a VMWARE (ESX Server 3.5) environment for Linux RedHat 4.0, Linux
5.0, and Windows Server 2003.
5.0, and Windows Server 2003.
Changes to Dynamic Lease Notification
The dynamic lease notification feature is modified to include the following:
•
Changing the processing of active leasequery sessions on reload in order to reduce or remove the
necessity for the dynamic lease notification client to issue a bulk leasequery when the server returns
to service. The detailed description is given in the
necessity for the dynamic lease notification client to issue a bulk leasequery when the server returns
to service. The detailed description is given in the
•
Allowing extensions to control the sending of active leasequery packet to the dynamic lease
notification client. The detailed description is given in the
notification client. The detailed description is given in the
.
Avoiding Bulk Leasequery for Active Leasequery Client After DHCP Reload
In CNR 7.1, a DHCP server reload required an active leasequery client to issue a bulk leasequery to
capture any changes between the time the server was shutting down and the client reconnected to the
server after the server restarted.
capture any changes between the time the server was shutting down and the client reconnected to the
server after the server restarted.
While a client can still do this, the DHCP server is enhanced as follows to reduce the need for this bulk
leasequery.
leasequery.
•
On server shutdown or reload, the DHCP server examines the queue of leases which it has queued
up for each active leasequery connection. If the queue is empty, it means that all the notifications
for that connection have been sent, at least into the TCP connection and are not waiting on the DHCP
server. So, if the queue is empty and the TCP connection is not blocked, the DHCP server will send
a DHCPLEASEQUERYSTATUS message with a status-code of QueryTerminated. This
DHCPLEASEQUERYSTATUS message includes a base-time of the server's shutdown time. The
client, when it reconnects to the server, should then issue an active leasequery request with a
query-start-time of this base-time.
up for each active leasequery connection. If the queue is empty, it means that all the notifications
for that connection have been sent, at least into the TCP connection and are not waiting on the DHCP
server. So, if the queue is empty and the TCP connection is not blocked, the DHCP server will send
a DHCPLEASEQUERYSTATUS message with a status-code of QueryTerminated. This
DHCPLEASEQUERYSTATUS message includes a base-time of the server's shutdown time. The
client, when it reconnects to the server, should then issue an active leasequery request with a
query-start-time of this base-time.