|
|
This appendix describes how to plan for a DHCP rollback, manually upgrade your database, and uninstall previous software releases of Network Registrar.
There are two ways you might set up your DHCP scopes for potential rollback to a previous software release of Network Registrar.
If you can, reserve enough available IP address space to accommodate your needs for a period of time equal to the lease-time plus grace-period plus 15-20. Upgrade your Software Release 1.2 DHCP server and the Software Release 2.0 DHCP server will use the scopes you have previously configured.
If you need to roll back to Software Release 1.2, shut down the Software Release 2.0 server, reconfigure the Software Release 1.2 server with the safe addresses (not with the same scopes and address ranges from your original Software Release 1.2 configuration), and bring it up. Do not attempt to re-use the addresses that were configured in your upgraded server until you know that all clients who might have received a lease have been given leases from the new Software Release 1.2 scopes after the roll back, or until the full lease-time plus grace-period has passed.
If you cannot segregate enough IP addresses, you can use the Software Release 1.2 Network Registrar GUI to deactivate leases that were given out by the Software Release 2.0 DHCP server.
If you decide to roll back from Software Release 2.0, reconfigure a Software Release 1.2 DHCP server, but do not start it. The Software Release 1.2 server will not know about the leases that might have been given out by the original Software Release 1.2 installation or by the Software Release 2.0 server. You can use the Software Release 1.2 Network Registrar GUI to deactivate each lease that was leased by the original Software Release 1.2 or the Software Release 2.0 DHCP server. As clients receive new addresses, their deactivated addresses can be made available again. This method requires more manual intervention than the method that uses completely separate, safe addresses for the rollback, and is riskier.
If you chose not to upgrade your database when you ran the Network Registrar Software Release 2.0 installation, you can upgrade your database in order to use it with Software Release 2.0.
The upgrade procedure, upgrade20, maintains a registrar/logs/upgrade.log. The upgrade procedure logs all errors, as well as tracing various conversion steps. It does all logging at level "INFO," in order not to show up in the system event logs.
To run upgrade20, enter:
upgrade20 -o old-installation-directory
Upgrade20 prompts you for the username and password.
On Solaris, in which the data directory may be separate from the installation base, you can specify the path to the "data" dir a "-o" option by entering:
upgrade20 -o old-installation-directory -d old-data-directory
If the database has already been upgraded, the upgrade20 program detects this, and will refuse to redo the upgrade.
If you omit the -N and -P, upgrade 20 prompts you for the administrator's name and password. While upgrade20 is not expected to be used to upgrade a password-protected database (that is, one in which the new database has a password), you can use the -u and -p options to specify a new username and password.
There are a number of minor operations, which are done during an export/import process, that are based on the textual mcdadmin format:
In addition to the above changes, upgrade20 performs the following two algorithmic operations after the data is in place in the new database:
Step 1 Become the superuser.
Step 2 Run the import command, which stops your Network Registrar servers, performs the upgrade, and restarts your Network Registrar servers:
/opt/nwreg2/bin/import
Step 1 Stop your Network Registrar servers. From the Program Manager, select Start>Settings>Control Panel>Services> AIC Server Agent 2.0 Stop.
Step 2 Bring up a DOS window and run the upgrade20 database conversion program:
C:\Network Registrar\bin\upgrade20 -O
C:\Network Registrar C:\Network Registrar\Registrar
Step 3 When prompted, supply the user name and password for your old database.
Step 4 Restart your Network Registrar servers.
From the Program Manager, select Start>Settings>Control Panel>Services> AIC Server Agent 2.0 Start Uninstalling Network Registrar.
When you are satisfied that Network Registrar Software Release 2.0 is running successfully, you can free some disk space by removing old versions of Network Registrar.
Step 1 Become superuser.
Step 2 Run the pkgrm command and specify nwreg.
/usr/sbin/pkgrm nwreg
From the Program Manager, select Start>Programs>Network Registrar>Uninstall Network Registrar.
Posted: Thu Jul 13 11:10:56 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.