Filter
Top Products
22-7
Cisco CNS Network Registrar User’s Guide
OL-6240-02
Chapter 22 Advanced DHCP Server Properties
Integrating Windows System Management Servers
As a complication, the server also keeps track of the time when it last heard from the client. Known as
the last transaction time, sites sometimes use this information as a debugging aid. Maintaining this time
robustly requires a write to the database on every client interaction. The last-transaction-time-
granularity attribute is the one to set. (See the attribute description in Table 22-1 on page 22-4.) Because
it is primarily a debugging aid, the value need not be entirely accurate. Furthermore, because the
in-memory copy is always accurate, you can use export leases -server to display the current
information, even if the data is not up to date in the database.
Integrating Windows System Management Servers
You can have the DHCP server interact with the Microsoft System Management Server (SMS) so that
SMS is current with DHCP changes. Normally, SMS pulls updated data through a DHCPDISCOVER
request from the server about any new clients that joined the network. Network Registrar, however,
pushes these updates to SMS when you use dhcp updateSms. Before you do, verify that:
• SMS client installation and initialization step is complete.
• Network Registrar Server Agent is set to run under a login account with sufficient privileges.
• SMS site ID is correct and matches that of the SMS server.
These steps describe how to integrate Windows SMS into Network Registrar.
Step 1 Install the Microsoft BackOffice 4.5 Resource Kit on the same machine as the Network Registrar DHCP
server. Follow the installation instructions and choose the default settings.
Step 2 After the installation, modify the User Variable search path on the Environment tab of the System control
panel to:
\program files\ResourceKit\SMS\diagnose
Step 3 If the DHCP and SMS servers are on different machines, install the SMS client on the same machine as
the DHCP server. The SMS library has the necessary API calls to communicate with the SMS server.
You must assign the correct site code from the DHCP server machine. In your Network Neighborhood,
go to the path \\SMS-servername\SMSLOGON\x86.bin\00000409\smsman.exe.
Run the program and follow the instructions, using the default settings. The program creates two icons
that you can use later from the control panel, marked SMS and Remote Control.
Step 4 Stop and then restart the Network Registrar server agent under a trusted domain account with sufficient
privileges. Both the DHCP and SMS servers must be aware of this account. Use this short procedure:
a. Stop the local cluster server agent process.
b. Configure the account under which the Network Registrar services run. Create an account name that
is a member of both the trusted SMS site server group and a member of the DHCP server machine’s
administrator group, with the corresponding password.
c. Restart the local cluster server agent process.
Step 5 Use dhcp set sms-library-path (or the sms-library-path attribute under the Microsoft Systems
Management Server category on the Edit DHCP Server page of the local cluster Web UI) to configure
the DHCP server to push lease information to SMS. Include the full path to the SMSRsGen.dll. If you
omit a value, the path defaults to the internal server default location of this file. For example:
nrcmd> dhcp set sms-library-path /conf/dll