cc/td/doc/product/rtrmgmt/ciscoasu/nr/nr3.0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for Cisco Network Registrar 3.0R

Release Notes for Cisco Network Registrar 3.0R

These release notes describe the caveats and new features for Cisco Network Registrar 3.0R0.

Warning The upgrade procedures for Solaris have changed from earlier revisions. Read "Upgrading From Previous Releases" section before proceeding. Do not run the Solaris pkgrm command before reviewing these instructions. The pkgrm command will delete your data.

This document contains the following sections:

Introduction

The release of Network Registrar 3.0 contains the following components:

Network Registrar includes Windows® NT servers, CLI, and GUI, and Solaris® servers, CLI, and a Motif® GUI.

You can run the servers and the associated user interfaces on the appropriate platform, or you can run the servers on one platform and the user interfaces on another.

System Requirements

Network Registrar 3.0 runs on Windows NT 4.0, Solaris 2.5.1, and Solaris 2.6. Network Registrar's 3.0 GUI also runs on Windows 95.

For all OS platforms, Cisco recommends that you install the current service pack (Windows) or recommended patch cluster (Solaris).


Table 1: Solaris 2.5.1 Patches

103461-20

103558-11

103566-25

103582-15

103594-13

103603-06

103612-38

103622-09

103630-09

103640-17

103663-09

103680-01

103686-02

103690-05

103696-03

103738-05

103743-01

103817-02

103866-05

103879-04

103900-01

103901-08

103934-06

103959-06

104010-01

104166-03

104212-09

104246-05

104266-01

104283-03

104317-01

104331-04

104334-01

104338-02

104433-06

104516-03

104533-03

104613-01

104650-02

104654-03

104692-01

104708-09

104736-03

104776-02

104795-02

104893-01

104935-01

104956-04

104958-01

104960-01

104968-02

104976-03

105004-09

105050-01

105092-01

105251-01

105299-01

105344-01

105352-01

105520-01

Solaris 2.6 has been tested with the recommended patch cluster that was current on February 11, 1998. In particular, Solaris 2.6 was tested with these patches installed:


Table 2: Solaris 2.6 Patches

105216-01

105393-01

105518-01

105615-02

105621-01

105665-01

105667-01

105379-01

105786-01

105669-02

105558-01

105375-03

105357-01

105356-01

105407-01

Software Compatibility

Network Registrar 3.0 is compatible with the following:

There is a known problem on Solaris that may cause the DHCP server to hang during initialization. The problem is described by Sun RFE 4071167. The deadlock in the Solaris name resolver client can be encountered by installing a linked set of patches from Sun, including 103663-08, and disabling host name caching in "nscd" (to improve name resolver client performance), which is recommended by Sun in RFE 1243174.

To avoid this problem, do one of the following:

User Interface and Server Interoperability

The following table describes the typical outcome when you run different versions of the user interface and the servers:


Table 3: Network Registrar Interoperability
GUI and CLI Server Outcome

3.0

2.5

Network Registrar runs successfully.

2.5

3.0

Network Registrar UI displays the error message "Unsupported version number." The server is unaffected.

What's New in This Release

Cisco Network Registrar Release 3.0 offers many new features:

Installing Network Registrar on Solaris

If you are installing Network Registrar 3.0 for Solaris for the first time, follow the instructions in the Getting Started with Network Registrar guide, but instead of specifying pkgadd -d <CD-ROM>, where <CD-ROM> is the CD-ROM's mount point, specify pkgadd -d <CD-ROM>/solaris/see_readme_before_using.

For additional information, see the file README.solaris in the top-level directory of the CD-ROM.

Upgrading From Previous Releases

When you upgrade from a previous release of Network Registrar, you can choose to save your database or overwrite it. If you overwrite your database you lose all information about your zones, scopes and leases.

Upgrading From CNR Release 1.x

To upgrade from any Network Registrar release numbered 1.x, you must first upgrade to release 2.0 before upgrading to release 3.0. Contact the Technical Assistance Center if you need additional information.

Upgrading from CNR Release 2.x Solaris

Warning The upgrade procedures for Solaris have changed from earlier revisions. Do not run the Solaris pkgrm command before reviewing these instructions. The pkgrm command will delete your data.

To upgrade from Network Registrar release 2.x, you must run the program upgrade_cnr in the solaris subdirectory of the CD-ROM. If you use the standard configuration of the Solaris automounter, this program will be located in the directory /cdrom/nr_3_0r0/solaris/upgrade_cnr.

The upgrade program does the following:

Note You can not use the upgrade program to install a new version of Network Registrar in new location. You can not use the upgrade program to select options such as Complete, Server, and GUI. The upgrade program only upgrades the options that were previously installed.

To upgrade from Network Registrar 2.x to Network Registrar 3.0 on a Solaris server and to preserve your database, do the following:

Step 1 Login as root.

Step 2 Run the /cdrom/nr_3_0r0/solaris/upgrade_cnr program.

        # /cdrom/nr_3_0r0/solaris/upgrade_cnr

If you mount the CD-ROM manually or have a non-standard automounter configuration, then replace /cdrom/nr_3_0r0 with the directory on which the CD-ROM is mounted.

Step 3 Follow the instructions on the screen.

This completes the procedure for upgrading from Network Registrar 2.x to Network Registrar 3.0 on a Solaris server. When the upgrade is complete, Network Registrar's services will start automatically.

Upgrading from CNR Release 2.x Windows NT Server

To upgrade from Network Registrar 2.x to Network Registrar 3.0 on a Windows NT server and to preserve your database, do the following:

Step 1 Run SETUP.EXE.

Step 2 Follow the instructions that appear on your screen.

Answer Yes to the question about upgrading your existing installation. This will preserves the data in your database.

To upgrade from Network Registrar 2.x to Network Registrar 3.0 on a Windows NT server without preserving your database, do the following:

Step 1 Run the uninstall program.

Step 2 Perform an initial installation as described in the "Installing Network Registrar on Windows" section on page 1-8 of the Getting Started Guide.

Note To non-interactively upgrade a previous release of Network Registrar, see the instructions in the text file \i386\UPGRADE2.ISS on the Network Registrar CD.

Using Network Registrar

If you plan to use failover on a machine with multiple interfaces, you must explicitly configure the local server's name or IP address. Remember, only if the machine has a single interface, can you omit the name or IP address for the local server.

For instance, to configure server A as main and server B as backup in a situation in which each has only one interface, you would do the following:

Step 1 On server A specify the name of the backup server, by typing:

    nrcmd> dhcp set failover-backup-server=serverb

Step 2 On server B specify the name of the main server, by typing:

    nrcmd> dhcp set failover-main-server=servera

In this case, the lack of configuration for a main server on server A and the existence of the configuration for a backup server causes server A to assume it is a main server. Since server A has only one IP address and name, it uses that interface and IP address to communicate with server B.

If, however, server A has multiple interfaces and multiple IP addresses (and presumably multiple DNS names, one per IP address and interface), then the situation is more complicated.

For instance, if server A has two interfaces with the two DNS names servera and serverprime, and you were to configure server A as above, it would choose (unpredictably) a single interface from which to communicate with server B.

The correct way to configure a main server that has two interfaces is to explicitly name the interface on which you wish it to communicate with the backup server:

Step 1 On server A, specify the backup server, by typing:

    nrcmd> dhcp set failover-backup-server=serverb

Step 2 On server A, specify the main server, by typing:

    nrcmd> dhcp set failover-main-server=servera

This specifies which interface server A needs to use to communicate with server B, and ensures that failover will initialize correctly.

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:

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

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@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.

Resolved Bugs

100 OK - 100 OK
It should only print "100 OK" once. [CSCai03086]
If you enter the fully qualified domain name, the interface will create an improperly named subzone which cannot be removed using the Remove button on the Subzones tab. The subzone will appear to have been removed, but its resource records will not be removed and, after reloading, the subzone will reappear in the list on the Subzones tab. If this happens, go to the Resource Records tab and delete the relevant resource records individually. [CSCai03757]

Unresolved Bugs

Furthermore, if you double-click on the lease again, the "reservations" check box is empty, and the address you typed into the "MAC Address" edit control now shows up in the "Leased to MAC address" edit box.
To avoid this problem, add the "reservation" check and reload the server, then choose "deactivate." [CSCai01059]
If a DHCP server logs an error containing "80010023," the server's socket buffer may be filling up. To solve this problem, increase the "min-buffer-size" DHCP interface setting using nrcmd. For example:
    nrcmd> session set visibility=3 
100 OK 
visibility=3
    
nrcmd> dhcp-interface default get min-buffer-size 
100 OK 
min-buffer-size=32768
    
nrcmd> dhcp-interface default set min-buffer-size=65536 
100 OK 
min-buffer-size=65536
    
nrcmd> dhcp reload 
100 OK
[CSCai01366]
This problem does occur with the boot-file option. In that case, if the string becomes too large after substitution to fit into a DHCP option (255 bytes), then the option is returned to its pre-substitution state and a log message is generated. [CSCai01809]
This only occurs when there are two DHCP servers servicing the same subnet (typically for reliability). It is also only the case when the two different operating systems that are being used have the same host name (which is configurable) and the same client-id (which would be the case for Windows 95 and Window NT 4.0 running on the same hardware).
One workaround is to make sure that each operating system on a machine is configured with a different host name. [CSCai01820]
To work around this problem, make the graphical user interface's top-level window and the Server Manager window as large as possible, which may make the second vertical scrollbar disappear. If it does not, scroll to the bottom of both scrollbars to reach the bottom of the data. [CSCai02465]
You may now see garbage text for that lease entry.
If this happens, exit the DHCP Scope Properties dialog (using "OK") and re-open it to synchronize the display with your changes. If, instead, you click "Cancel" and then disconnect from the cluster or exit from the user interface, you will see a dialog stating that the DHCP server has configuration data that has not been saved. If you click "Yes" or hit Return to indicate that you want to save the data, then the lease will be removed as you intended. If you click on "No," the lease will not be removed. In either case, the user interface display will be correct when you reconnect to the cluster. [CSCai02690]
03/24/1998 17:26:59 name/dhcp/1 Warning Configuration 0 While processing a packet from Client MAC: '1,6,01:55:55:55:55:55', an unrecognized host name token '@st-name-jreio' was found in the client. Packet dropped'.
Do not configure a host name with a '@' on a DHCP client, and be sure when configuring host name tokens that they are correctly formatted. [CSCai02707]
The set command will cause the change to be persistent. For example, to enable an interface 10.1.1.1/24, you would use the command:
    nrcmd> dhcp-interface 10.1.1.1/24 set ignore=false
To disable this interface, use the command:
    nrcmd> dhcp-interface 10.1.1.1/24 set ignore=true
[CSCai03064]
This is different from other commands, which print "100 OK" only once. [CSCai03088]
Under normal circumstances, you should never encounter BIND files with 64-character names. Consult RFC 1035 sections 2.3.1 and 2.3.4 (available at http://www.ietf.org/rfc/rfc1035.txt) for the definitive specification of name length limits. You should avoid importing BIND files with too-long names, because they may cause database corruption. [CSCai03098]
The address provided is not a valid MAC address. Please provide an address in the form xx:xx:xx where x is a hexidecimal digit.
This error message is insufficient for two reasons: 
secondary/net-171-78-star.zone: line 1675: database format error (foo.com.) 
Line 1675 was: 
97 IN PTR gilligan .foo.com.
Note the whitespace between the host name, "gilligan," and its zone name, ".foo.com.." To avoid this problem, do not create host names with spaces in them. [CSCai03132]
Note that disabling this feature later will prevent all clients who send client IDs from renewing their leases. The DHCP server will have to assign them new addresses. [CSCai03207]
You can avoid this situation by being careful not to delete any scopes that have secondary scopes. If you do get into the situation where you are unable to uncheck a scope's "Make this scope a secondary" checkbox, do the following: create a temporary, empty scope; make the temporary scope the new primary scope of the problem scope; save the data and reload the server; uncheck the "Make this scope a secondary" checkbox of the problem scope; save and reload the server again; and delete the temporary scope. [CSCdk90451] 
312 Unexpected response from server - (0x1)
The message should state more clearly that the requested command could not be executed because of the current state of the server; however, there is no real loss in server functionality. To eliminate the spurious errors, resolve the problem that is causing the low server health. [CSCdm16250]
When this occurs, it is usually associated with a backup server which is overloaded and cannot keep up with the volume of updates being offered to it by the main server. The backup server needs to get considerably behind in its processing of failover updates for this to occur.
When a client interacts with the main server, this problem will typically resolve itself. However, when a client is no longer present on the network and has allowed its lease to expire or has explicitly released its lease, and if the backup server was very busy when this happened, then sometimes a lease will get stuck in the pending-available state.
You can recover a lease stuck in the pending-available state by forcing it available using either the graphical user interface or nrcmd. You should force it available on the server that believes that it has more recent binding information and is NAKing the other server, which will almost always be the backup server. [CSCdm23864]
If you encounter this situation, run the "Rebuild Resource Record Indexes" command from the Advanced tab of DNS Server Properties dialog in the user interface (ignore the warning message). It is then safe to add, delete, or modify hosts. [CSCdm24250]
Currently, Network Registrar does not notify the administrator of such configuration errors. We will soon be releasing a utility to compare the failover configurations on two servers and report on any discrepancies. A notice will be sent to all registered customers at that time. [CSCdm24264] .




hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Nov 18 12:34:15 PST 1999
Copyright 1989-1999©Cisco Systems Inc.