Digi Release Notes P/N 93000691A for AIX RealPort Migration Tools (v2 --> v3) Software Component P/N 80006838A May 10, 1999 I. Description One of the differences between existing AIX RealPort device drivers (version 2.x.x.x, hereafter referred to as v2) and the new AIX RealPort driver package (version 3.x.x.x, hereafter referred to as v3) is the minor device numbering scheme. As a result of this difference, existing configuration information (such as defined tty devices) will not directly be supported by the new driver. Without external tools, the only option for a system manager is to delete all existing configurations, replace the v2 driver with a v3 driver, and then reconfigure all devices. This manual process is the safest means available, but can become rapidly cumbersome as the number of devices grows. To minimize the impact of the minor numbering change, Digi has created tools to automate much of the migration process. These tools are referred to here as the "RealPort Migration Tools". Using these tools, most system administrators will be able to smoothly transition from the v2 drivers to the v3 drivers, as the names and configurations of existing devices will be preserved. NOTE: It is suggested that (as with ANY installation process) a system backup be made before executing the migration procedure, in case the system needs to be restored due to some catastrophic error. II. Requirements There are a number of guidelines which should all be met before running these migration procedures. The migration tools attempt to notify the user when they are not met, but it is best to be prepared in order to get a clean run as quickly as possible. The requirements are: 1. Root user. The tools must be run as the "root" user. 2. File system space. There must be enough file system space where the scripts are run to hold all of the temporary and log files generated by the procedure. It is suggested that one have 5-10 megabytes of space available to be safe even with the largest configurations. There must also be file system space enough to allow for the execution of the "bosboot" procedure. One can determine how much space is needed (and for which filesystem) by executing the command "bosboot -vq". 3. Migration tool installation. There are two key files associated with the migration tools: "nts_migrate" and "nts_chgodmdev". These two files must be placed in the same directory, and the migration process must be initiated while in this directory. 4. "Defined" devices. The migration process may not be initiated on "Available" devices. There are a number of ways to get the configured devices to the "Defined" state, a number of which are described by the migration tools if one attempts to execute them with "Available" devices. Three methods are described below; only ONE of the these methods should be used! o Execute the command: odmdelete -q"rule LIKE *nts*" -o Config_Rules and then reboot. This will prevent the autoconfig. of the PortServer devices and ports. Due to its simplicity, this is the preferred method. o Shutdown into single-user mode. o By hand, disable all of the ports for login, kill all applications using any PortServer ports, and then execute "rmdev -Rl" for each PortServer (sa) device. 5. Old driver required. For what is hoped are obvious reasons, the tools will not run if they detect that they have already been run, or if a v3 driver is already installed. If one has already installed a new driver and devices that were configured under the old driver still exist and are broken, one should contact Digi for migration help. III. Use The migration tools are distributed as a single "tar" file. It is suggested that one extract these files to their own directory. An example, assuming the "tar" file is named "/migrate_tools.tar": cd /tmp mkdir migrate cd migrate tar xvf /migrate_tools.tar There are two executable files associated with the migration tools, but only one should be executed by the user directly, "nts_migrate". An example which would be a continuation from above: cd /tmp/migrate ./nts_migrate The "nts_migrate" script (with no parameters) will attempt to do the migration, and will log its efforts to the standard output device and to a log file named "migrate.log". NOTE: If you need to save the results of a previous run, you must copy the contents of "migrate.log" by hand... the tools will not save these results for you. The log is re-created from scratch for each run of "nts_migrate". NOTE: If you encounter any problems with the migration process, you should have your "migrate.log" file available when you contact a Digi technical support representative. IV. Example Run # # NOTE: It should be understood that the details below (like exact # filenames, revision numbers, etc., will probably be different # for each installation. This example run is supplied in order # to give one an idea of what it should look like, for reference. # login: root root's Password: # # It is assumed that the migration tools have been downloaded and # renamed "/migrate_tools.tar" # $ lsdev -C -c nts sa5 Defined Digi PortServer II 16 sa6 Defined Digi PortServer II 16 $ cd /tmp $ mkdir migrate $ cd migrate $ tar xvf /migrate_tools.tar x nts_chgodmdev, 5105 bytes, 10 media blocks. x README, 25 bytes, 1 media blocks. x nts_migrate, 12831 bytes, 26 media block. # # Note: the numbers above are NOT accurate, and serve only # to complete the example. # $ ./nts_migrate Beginning migration procedure... Checking space requirements... 33504 blocks free... done. Checking installed revision... done. Checking the integrity of the script and it's associated binaries... done. Confirm that all PortServer devices are in the defined state... done. Determining the PortServer major numbers... 54 and 55 ==> 54... done. Uninstalling the original driver... +-----------------------------------------------------------------------+ Pre-deinstall Verification... +-----------------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------- Filesets listed in this section passed pre-deinstall verification and will be removed. Selected Filesets ----------------- digiasync.ncxa.obj 2.5.0.0 # Digi PortServer Driver << End of Success Section >> FILESET STATISTICS ------------------ 1 Selected to be deinstalled, of which: 1 Passed pre-deinstall verification ---- 1 Total to be deinstalled +----------------------------------------------------------------------+ Deinstalling Software... +----------------------------------------------------------------------+ installp: DEINSTALLING software for: digiasync.ncxa.obj 2.5.0.0 0518-307 odmdelete: 3 objects deleted. 0518-307 odmdelete: 60 objects deleted. 0518-307 odmdelete: 88 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 9 objects deleted. 0518-307 odmdelete: 3 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 3 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 6 objects deleted. 0518-307 odmdelete: 6 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 2 objects deleted. Finished processing all filesets. (Total time: 8 secs). +------------------------------------------------------------------+ Summaries: +------------------------------------------------------------------+ Installation Summary -------------------- Name Level Part Event Result --------------------------------------------------------------------------- digiasync.ncxa.obj 2.5.0.0 ROOT DEINSTALL SUCCESS digiasync.ncxa.obj 2.5.0.0 USR DEINSTALL SUCCESS done. Migrating ODM entries and generating scripts of /dev changes... done. Deleting obsolete ODM entries... 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. 0518-307 odmdelete: 1 objects deleted. done. Removing existing device files... done. Creating compatible device files... done. The migration of the existing configuration information is now complete. At this point, you should install the new driver package and then reboot.