Cisco Registrar 3.0 User Manual
Text Part Number:
78-6880-01
Release Notes for Cisco Network
Registrar 3.0(1)T
These release notes describe the caveats and new features for Cisco Network Registrar 3.0(1)T.
Warning The upgrade procedures for Solaris have changed from earlier revisions. Read
“Upgrading From Previous Releases” section on page 5 before proceeding. Do not run the Solaris
pkgrm command before reviewing these instructions. The pkgrm command may delete your
data.
This document contains the following sections:
• Introduction 2
• System Requirements 2
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
Copyright © 1999
Cisco Systems, Inc.
All rights reserved.
• Software Compatibility 3
• User Interface and Server Interoperability 4
• What’s New in This Release 4
• Cisco Network Registrar Release 3.0(1)T 4
• Cisco Network Registrar Release 3.0T 4
• Upgrading From Previous Releases 5
• Upgrading From CNR Release 1.x 5
• Upgrading from CNR Release 2.x or 3.x Solaris 5
• Upgrading from CNR Release 2.x Windows NT Server 6
• Cisco Connection Online 6
• Special Considerations 7
• Reverting to a Previous Version from Release 3.0(0.2)T or higher 7
• Resolved and Unresolved Bugs for 3.0(1)T 7
1
Introduction
Introduction
The release of Network Registrar 3.0(1)T contains the following components:
• CD-ROM containing the software
• Network Registrar Concepts Guide
• Getting Started with Network Registrar
• Network Registrar CLI Reference Guide
• Network Registrar User’s Guide
• Cisco Network Registrar 3.0 AIX Installation
• Cisco Network Registrar 3.0 HP-UX Installation
• Network Registrar Web GUI Installation Instructions
• Release Notes for Network Registrar 3.0(1)T
Network Registrar includes WindowsNT servers, CLI, and GUI, and Solarisservers, CLI, and a
Motif GUI, and AIX and HP-UX servers and CLI.
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(1)T runs on Windows NT 4.0, Solaris 2.5.1, and Solaris 2.6. Network
Registrar’s 3.0(1)T 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).
• Windows NT 4.0 must be run with service pack 3, or for Y2K compliance, on service pack 4.
• Solaris 2.5.1 has been tested with the recommended patch cluster that was current on February
11, 1998. In particular, it was tested with these patches installed:
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
2 Release Notes for Cisco Network Registrar 3.0(1)T
Software Compatibility
Table 1 Solaris 2.5.1 Patches (Continued)
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 beentestedwiththerecommended 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(1)T is compatible with the following:
• DHCP clients—All RFC 1954, 2132, and 2133 compliant DHCP and BOOTP clients
• DNS servers—Any DNS server compliant with RFC 2136 Dynamic DNS Updates and RFC
1995 and 1996 (IXFR and NOTIFY)
• LDAP servers—Any LDAP v2 or v3 server, including servers from Netscape, Sun
Microsystems, and Lucent Technologies
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. You can encounter the deadlock in the Solaris name
resolver client 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:
• Do not install the linked patch set.
• Do not disable “nscd” host name caching.
• Install patch 103663-11 (Solaris 2.5.1) or 105755-01 (Solaris 2.6).
Release Notes for Cisco Network Registrar 3.0(1)T 3
Loading...