HP 3000 Manuals HP 3000 Manuals
Using NETUtil to Migrate Profiles Before Installing HP-UX 10.0 [REV BEG] If you are installing NETUtil for the first time on your system or have no MPE/iX to HP-UX ALLBASE/NET connections, you can skip this section, and go to the section "Using NETUtil."
WARNING Cross-System Users: Do not upgrade to HP-UX 10.0 until G.0 is installed on your MPE/iX system.
Beginning with HP-UX 10.0, ARPA Services will be the only valid datacomm type for new and existing applications that run on the HP 9000 S700 or S800 client and/or server through ALLBASE/NET. Therefore, you must change the alias profiles in the AliasDB file on the client and the user profiles in the NETUsers file on the HP-UX server. You can use the migration commands MIGRATE ALIAS and MIGRATE USER to change profiles where the client and/or server is an HP9000 S700 or S800 and the datacomm type is NS. You must have SM capability or log on as MANAGER.SYS to use the migration commands. The MIGRATE ALIAS command can be executed with either the automatic or manual option. The automatic option changes all the alias profiles. The manual option prompts you for changes to each alias profile.[REV END][REV BEG] Listed below are the requirements for executing MIGRATE ALIAS for automatic migration on the HP 9000 S700 and S800. If the requirements are not met, you can use the manual migration option of the MIGRATE ALIAS command. 1. Automatic migration must occur before HP-UX 10.0 is installed on client and/or server machines. The implementation of the MIGRATE ALIAS command for the HP 9000 S700 and S800 will use NetIPC calls, and will require a connection to the server. If HP-UX 10.0 is installed on either client or server, the NetIPC calls won't exist. 2. Patch releases are available on HP-UX 9.0 and must be installed on the HP 9000 S700 or S800 client. The patch release numbers are phne_3502 (for S700) and phne_2288 (for S800). 3. Remote loopback must be enabled on the server machine for the conversion of NS node name to ARPA host name to work. The implementation of the MIGRATE ALIAS command on the HP 9000 S700 and S800 makes a connection to the remote loopback service on the server. To setup remote loopback on an HP 9000 S700 or S800, the remote loopback daemon, /etc/rlbdaemon, should be started in the /etc/netlinkrc startup script. For more information on the rlbdaemon, refer to the HP-UX Reference - Vol 3. On an HP 3000, loopback should already be started. If not, issue the command NETCONTROL START;NET=LOOP. For more information see the HP 3000/iX Network Planning and Configuration Guide. [REV END][REV BEG] The migration commands create two files, a migration log file and a server list file.[REV END] Migration Log File [REV BEG] Every time you execute and save the changes from MIGRATE ALIAS, MIGRATE USER, MIGRATE ALIAS BACKWARD, OR MIGRATE USER BACKWARD, the migrate log file HPDAMIG.PUB.SYS is appended. If the file does not exist it is created. After migration is successfully, you can delete the following temporary files: DAALFMBK.PUB.SYS TMPALMBK.PUB.SYS DAUSFMBK.PUB.SYS TMPUSMBK.PUB.SYS HPDAMIG.PUB.SYS TMPMIG.PUB.SYS DASVRLST.PUB.SYS DASVRMBK.PUB.SYS TMPSVMBK.PUB.SYS Here is a sample log file for a client. The MIGRATE ALIAS BACKWARD command returns the AliasDB file to its state before the 3:35 PM migration. TUE, APR 20, 1993, 3:35 PM: MIGRATE ALIAS Alias: testdb1 Migrated Server : snode.sdomain.sorg -> snode Cannot migrate alias (testdb2) for server (node1.dom.org) (DBERR 28029) Alias: testdb3 Migrated Server : hana.dom.org -> hana1.site1.co1.domain1 Alias: testdb40 Migrated Server : merc.dom.org -> merc2 Alias: testdb41 Migrated Server : mach1.dom1.org1 -> mach1.site1.co1.dom1 Migration complete. 4 alias(es) migrated successfully. 1 alias(es) NOT migrated successfully - see above for error information. TUE, APR 20, 1993, 3:40 PM: MIGRATE ALIAS BACKWARD Here is a sample log file for a server. The MIGRATE USER BACKWARD command returns the NETUsers file to its state before the 3:41 PM migration. TUE, APR 20, 1993, 3:40 PM: MIGRATE USER Migrated Client : Umach.Udom.Uorg -> Umach.Usite.Uco.Udom Login Name : user1.somegrp.someacct Login Name : user2.somegrp.someacct Migration complete. 2 user(s) migrated successfully. 0 user(s) NOT migrated successfully - see above for error information. TUE, APR 20, 1993, 3:41 PM: MIGRATE USER Migrated Client : mach2.dom.org -> mach2.site.co.domain Login Name : user3.somegrp.someacct Migration complete. 1 user(s) migrated successfully. 0 user(s) NOT migrated successfully - see above for error information. TUE, APR 20, 1993, 3:45 PM: MIGRATE USER BACKWARD [REV END][REV BEG] Server List File Each alias profile that was changed to show a different datacomm type requires that all corresponding user profiles on the server be changed also. If you use MIGRATE ALIAS to change an alias profile, a server list file, DASVRLST.PUB.SYS, is created and lists all affected corresponding servers for the client. At the top of the file, the NS value and ARPA value (if it can be determined by ALLBASE/NET) for the client node name are displayed. Here is a sample server list file. Client Node Name (NS value) : cnode.cdom.corg Client Node Name (ARPA value) : chost.site.co.domain Server Node Name List (NS value, ARPA value) : (snode.sdomain.sorg, snode) (hana.dom.org, hana) (merc.dom.org, merc2) (mach1.dom1.org1, mach1) [REV END]