Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Device conversion - AIX 4.2.1 to 4.3.3

Status
Not open for further replies.

WildCow

MIS
Nov 2, 1998
6
0
0
US
Hello,

I have a customer converting from a 7025-F40 running
AIX Version 4.2.1 to a 7025-6F1 running 4.3.3. They have many
serial devices and I was wondering if there's a straightforward way to convert the devices from the 4.2.1
ODM to 4.3.3. Thank you!!!


Tom
 
1)You could upgrade the f40 to 4.3.3 first.....
then use the mksysb plus the CD to get all the new devices?

2)Some have done the odmget and delete stuff with mixed reviews
Some succeeded ..........some did not......depends on what you have
etc.
On the old machine create...and move the odm.out file to the new machine
Execute the following commands:
odmget -q "name like cxia*" CuDv >>odm.out
odmget -q "name like cxia*" CuAt >>odm.out
odmget -q "name like cxpa*" CuDv >>odm.out
odmget -q "name like cxpa*" CuAt >>odm.out
odmget -q "name like cxma*" CuDv >>odm.out
odmget -q "name like cxma*" CuAt >>odm.out
odmget -q "name like sa*" CuAt >>odm.out
odmget -q "name like sa*" CuDv >>odm.out
odmget -q "name like tty*" CuAt >>odm.out
odmget -q "name like tty*" CuDv >>odm.out
odmget -q "name like lp*" CuAt >>odm.out
odmget -q "name like lp*" CuDv >>odm.out
----------------------------save to file then delete then restore............

odmdelete -o CuAt -q "name like cxia*"
odmdelete -o CuDv -q "name like cxia*"
odmdelete -o CuAt -q "name like cxpa*"
odmdelete -o CuDv -q "name like cxpa*"
odmdelete -o CuAt -q "name like cxma*"
odmdelete -o CuDv -q "name like cxma*"
odmdelete -o CuAt -q "name like sa*"
odmdelete -o CuDv -q "name like sa*"
odmdelete -o CuDv -q "name like tty*"
odmdelete -o CuAt -q "name like tty*"
odmdelete -o CuDvDr -q "value3 like tty*"
odmdelete -o CuAt -q "name like lp*"
odmdelete -o CuDv -q "name like lp*"
odmdelete -o CuDvDr -q "value3 like lp*"

Add the saved information to the new ODM.(new machine)
odmadd odm.out
savebase
Reboot the system. Upon reboot, missing/dev and /etc/inittab entries
will be created.
sync;sync;sync
shutdown -Fr

PROBLEM is that printers are included in this....you could leave out the lp stuff...
Some have had luck with the printers, some have not....

Migrating printers to another machine
(REMEMBER when I say copy, I only mean the files listed...not the entire VAR directory...............

Here are the instructions I received from IBM. NOTE: Be advised that IBM
claims they do not support this through IBM.

Migrating Print Queues:
1. copy the /etc/qconfig (make a copy of the original before)
2. Copy the following files:
/var/spool/lpd/pio/@local/custom files
/var/spool/lpd/pio/@local/dev files
/var/spool/lpd/pio/@local/ddi files
3. change the permissions on the copied files to 664 chmod 664 filename
4. redigest the queue's
enq -d

(you may have to do the following you may not)
5. run the chvirprt command on each queue
chvirprt -q -d
Note; If you have a lot of queues, the best thing is to create a short script to
do this for you. I grab the queue name and device name by running lsallq -c
and saving it to a file.
(have to do this step)
6. cycle the printer subsystem
stopsrc -cg spooler
startsrc -g spooler
------------------------------------

3) Make a paper copy of your settings so it can be redone manually.
Cut and paste this script...add whatever else you want...
run it after you change the perms to 755...
then send to a file and
Print to paper and keep

# saveyosys.sh
# This is a script that creates important input
# for your system in case of a major disaster
# It should be run periodically, whenever a
# change is made to the system, or new equipment
# added. The output should be printed out and
# saved offsite and on site.
# It is suggested that you have a mksysb, backups
# and bootable disks or install media in addition
# to this script output. We do not guarantee
# this script will give you everything you
# will need in the event of a disaster.
# It is a tool to assist you in gathering needed
# data and information. Hope it helps.

dat=`date +%m%d%y`
exec > saveyosys.$dat
echo `date`
echo `hostname` ; echo "command: hostname"
echo `ifconfig en0` ; echo "command: ifconfig en?"
echo `ifconfig et0`
echo "command oslevel"
echo `oslevel`
echo ""
echo "paging space currently on system command: lsps -a"
lsps -a
echo ""
echo "Physical volume ids command: ipl_varyon -i"
ipl_varyon -i
echo ""
echo "Volume groups"
lsvg
echo "status of volume groups command: lsvg volumegrp"
for VG in `lsvg`
do
lsvg $VG
echo ""
echo "Physical volumes in $VG command: lsvg -p volumegrp "
lsvg -p $VG
echo ""
echo "Logical Volumes and filesystems in $VG command: lsvg -l vg"
echo ""
lsvg -l $VG
done
echo ""
echo "Physical Volume command: lspv | awk print 1 "
for PV in `lspv | awk '{print $1}'`
do
echo ""
echo "Physical status of $PV command: lspv phyical volume"
lspv $PV
echo ""
echo "LV details on $PV command: lspv -p physical volume"
lspv -p $PV
done
echo ""
echo "Filesystems"
lsfs
echo ""
echo "details"
grep -v "#" /etc/filesystems
echo ""
echo "List devices"
echo "lsattr -F attribute value -l device"
for DEVICE in `lsdev -C | grep -v "Logical volume"| grep -v \
"Volume group" | awk '{print $1}'`
do
echo "$DEVICE"
lsattr -F "description attribute value" -l $DEVICE
echo ""
done
echo ""
echo " inittab file"
grep -v "#" /etc/inittab
echo ""
echo " printer file"
grep -v "#" /etc/qconfig
echo ""
echo "passwords"
grep -v "#" /etc/passwd
echo "hosts"
grep -v "#" /etc/hosts
echo ""
echo "services"
grep -v "#" /etc/services
echo ""
echo "scsi devices "
lsdev -Cs scsi
echo " "

-------------------

Easiest is to migrate the F40 to 4.3.3........ but if that is impossible, make sure you have a good paper copy so you can redo if you have to delete printers and recreate...


4)ALWAYS make a copy (mksysb) of the NEW AIX 4.3.3 that is currently installed on your new machine before you play with any of this. If you have to go back you have all the drivers, you have all the stuff you need to get the new machine up....in a virgin state. You can place your eggs on the cd that comes with the machine...but you never know...you have an a new running machine...and it can be restored from a mksysb should all this fail so you can manually do what you have to.

5) Migrating Users.

6)128 port settings restore document

7) Migration doc...some of the checks may help you?

My opinion..............my opinion only..........good luck
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top