Table of Contents

Conversion Scenarios
Conversion Components
Pre-Conversion Checklist
Converting CDDM to CNR 2.5R1 on a Single Server
Converting CDDM to CNR 2.5R1 on Multiple Servers
Post-Conversion Tasks
Caveats
Cisco Connection Online
Documentation CD-ROM

Converting from Cisco DNS/DHCP Manager to Cisco Network Registrar 2.5R1

This document describes how to convert from the Cisco DNS/DHCP Manager (CDDM) to Cisco Network Registrar (CNR) 2.5R1.

This document includes the following:

• Conversion Scenarios 2

• Conversion Components 3

• Pre-Conversion Checklist 4

• Converting CDDM to CNR 2.5R1 on a Single Server 5

• Converting CDDM to CNR 2.5R1 on Multiple Servers 5

• Post-Conversion Tasks 7

• Caveats 7

Conversion Scenarios

When converting from CDDM to CNR 2.5R1, there are two types of conversion scenarios:

• Single server running CDDM

In this scenario, all CDDM services (DNM, DNS, and DHCP) run on a single server. When the server is converted to CNR, all services except DNM run on the same server (see Figure 1).

In this scenario, DHCP services run on one server and DNM/DNS services run on a different server. When converted to CNR, DHCP services run on the DHCP server and DNS services run on the other server. Any CDDM secondary DNS servers are also converted into secondary DNS servers in CNR (see Figure 2).

Conversion Components

When converting from CDDM to CNR 2.5R1, the following components are included:

• cddm2cnr

This is the wrapper program that manages the overall conversion process, calls the other component programs, converts DNS zone information, and loads the information collected from CDDM into CNR.

• read_config

This is the DHCP conversion program. This program reads the configuration files (dhcp-server.cnf, service.cnf, and bootp.server.cnf) and the dhcp-state.dat file and generates files containing appropriate nrcmd commands in two files: convert-dns.txt and convert-dhcp.txt. nrcmd is the command line interface for CNR. It also reads the lease information from CDDM and creates a convert-lease.txt file, which contains the lease information in the CNR dump/load format for importing leases.

• Input	Description
  dhcp-server.cnf	DHCP configuration file in CDDM
  dhcp-state.dat	DHCP lease file
  Output	Description
  convert-dns.txt	nrcmd commands to create dynamic zones. These commands are targeted for the DNS server in CNR.
  convert-dhcp.txt	nrcmd commands to create scopes and policies. These commands are targeted at the DHCP server in CNR.
  convert-lease.txt	Lease information from CDDM in CNR dump/load format
  dynamic-domainname.txt	The dynamic (forward) zone name from CDDM
  dnm-server.txt	Name of the DNM/DNS server in CDDM. This is assumed to be the target DNS server in CNR.

  dnmcl32

This utility retrieves zone information from the DNM server. This is used during the conversion process to verify whether a CDDM secondary zone is a DNM-secondary (i.e., transfers zone information from the DNM server rather than a standard DNS server).

• srvconv

This utility removes DNM, DNS, and DHCP service entries from the CDDM configuration file service.cnf. The new service file contents are written to the standard output. The wrapper program saves this in a temporary file, renames the old service.cnf files, and renames the temporary file as service.cnf.

Pre-Conversion Checklist

Before you convert from CDDM to CNR 2.5R1, verify the following:

• The correct CNR software has been installed on the server. For more information, refer to the Getting Started with Network Registrar publication.

• A cluster has been created.

• The license key is installed.

• The DNS and DHCP services from the Cisco Service Manager (CSM) have been stopped to prevent changes from occurring during the conversion. This also allows the DNS and DHCP services to be started from CNR.

• You have the admin user id and password for both DNM and CNR.

• You have performed a complete backup of CDDM.

Converting CDDM to CNR 2.5R1 on a Single Server

To convert a single server running all CDDM services (DNM, DNS, and DHCP) to CNR 2.5R1 with DNS and DHCP running on the same server, follow these steps:

Step 1 Shut down the DHCP and DNS services on all machines running CDDM, regardless of whether or not they provide DHCP or DNM services.

Step 2 Run cddm2cnr.exe as Administrator in a DOS window on NT.

Run cddm2cnr.sh as root from a shell or command prompt in Solaris.

Step 3 When the program prompts you at each step, press Enter (or Return) to continue.

Step 4 When prompted, enter the CNR admin user id and password, then press Enter. The program extracts the DHCP, DNM, and DNS information from CDDM and loads it into CNR.

Step 5 When the conversion is finished, a message appears instructing you to open the log file (cddm2cnr.log) and check for possible errors.

Step 6 Log into the CNR cluster(s) and check all entries for DNS and DHCP.

Converting CDDM to CNR 2.5R1 on Multiple Servers

To convert multiple servers running all CDDM services (DNM, DNS, and DHCP) to CNR 2.5R1, follow these steps:

Step 1 Shut down the DHCP and DNS services on all machines running CDDM, regardless of whether or not they provide DHCP or DNM services.

---

Note CNR must be up and running on the DNM server.

---

Step 2 On the machine running the DHCP services, run cddm2cnr.exe as Administrator in a DOS window on NT.

Run cddm2cnr.sh as root from a shell or command prompt in Solaris.

This converts the DHCP scopes locally and creates the dynamic zones in CNR on the DNM server.

It will also import leases from CDDM into CNR on the DHCP server. If dynamic DNS is enabled for some scopes, importing leases can cause CNR to try to update the DNS server in CNR on the DNM server. This may fail if DNS is not disabled under CDDM on the DNM server since only one DNS server at a time can be active on a machine. See Caveats 7.

Step 3 When the program prompts you at each step, press Enter (or Return) to continue.

Step 4 When prompted, enter the CNR admin user id and password, then press Enter. The program extracts the DHCP, DNM, and DNS information CDDM and loads it into CNR.

Step 5 When the conversion is finished, a message appears instructing you to open the log file (cddm2cnr.log) and check for possible errors.

Step 6 On the machine running the DNM services, run cddm2cnr.exe in NT, or cddm2cnr.sh for Solaris, as described in steps 2, 3, and 4.

This converts the static DNS zones.

Step 7 When the conversion is finished, a message appears instructing you to open the log file (cddm2cnr.log) and check for possible errors.

Step 8 Log into the CNR cluster(s) and check all entries for DNS and DHCP.

---

Note All files created or modified during the conversion process are backed up. The file extension is replaced by a number from 001 to 099. For example, service.cnf is renamed to service.001.

---

Post-Conversion Tasks

To use CDDM to provide other services, such as NTP, follow these steps:

Step 9 Restart the CSM.

Step 10 Select the Master Server.

Step 11 Click Restart.

This restarts all other services.

Caveats

There are several caveat you should pay attention to while converting:

• If you are converting from CDDM to CNR 2.5R1 on Windows NT with DNM and DHCP on separate servers, a Dr. Watson error in read_config.exe might occur. This happens when there are no scopes with an IP address range. It might happen under other circumstances when there is no data in CDDM's DHCP server.

This can be ignored.

• If CNR encounters an error while importing leases, it stops importing, ignoring the remaining leases in the convert-leases.txt file. There are two workarounds for this problem:

  • Fix the problem that caused the import to fail. You can locate the problem in the name_dhcp_1_log file in the CNR logs directory.

  • Manually import the remaining leases into CNR as follows:

(a) Disconnect from the cluster in the CNR GUI (ntwkreg), or close the GUI to release the lock on the cluster.

(b) Before importing leases, set the DHCP server to import mode to prevent the server from issuing leases. nrcmd is in the CNR install directory \bin.

(c) Import leases.

(d) Disable import mode after importing.

(e) Restart the CNR DHCP and DNS servers.

One known problem that causes importing leases to fail is inconsistencies in subnet continuation ("sc" tags) in CDDM. In CNR, the "sc" tag gets converted to "primary scope" in the Advanced tab on the DHCP scope. Make sure this information is valid

• The conversion utility on NT may "hang" when trying to import leases from CDDM. This could be due to an invalid primary/secondary scope configuration where primary and secondary scopes are on different physical subnets. When this happens, abort the conversion process (Ctrl-C), reconfigure the physical and secondary scopes to ensure that they are on the same physical subnet using CDDM, and rerun the conversion utility.

• If CNR displays the error, "Error Server local top port 53 already in use. There may be a name server already running." The cause could be:

  • On NT or Solaris the CDDM DNS server may still be running. To determine which process is using port 53 on Solaris, use the following command:

• On NT only, the Microsoft DNS server may be running.

You must terminate the DNS server process and stop/start the CNR servers using the following commands:

See "Getting Started with Network Registrar" for more information.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

• WWW:  http://www.cisco.com

• WWW:  http://www-europe.cisco.com

• WWW:  http://www-china.cisco.com

• Telnet:  cco.cisco.com

• Modem:  From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

Posted: Thu Jul 13 11:59:38 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.