Recent content by flatwater

Check the setup server log in /tmp because it has not successfully completed.

nim -o bos_inst -a source=mksysb -a mksysb=mksysbName -a lpp_source=lpp_sourceName -a spot=spotName -a boot_client=no serverName As for the bootp it is typical of NIM and PSSP when the remote server is not reachable.

Yes. But if the LV is across multiple disks then you will have more than 3 lines. I would do it this way: lslv -l hd2 | grep hdisk | awk '{print $1}'

Outsourcing is a great media hype and I am sick of this horse being beat again and again in this forum, regardless if this article is positive, because it will generate negative comments.

either the lv (/dev/backuplv) or /backupfs don't exist.

I thought it was rather comical that so many were asking for the script. Unless the systems were new there should have been a documentation process in place. Of course, maybe it was a better solution that what others have been using, but it was amusing seeing the clamor for it. Either the...

Also use: oslevel oslevel -r oslevel -r -q as well as: instfix -i | grep ML

It could be because of an incorrect block size and probably has nothing to do with physical memory.

prtconf

"I downloaded gcc-2.95.1 from sunfreeware.com..." This was probably developed specifically for a Solaris installation. OpenSSH will compile successfully on AIX 4.3.3 without errors, so get it from openssh.org or it should be on the Bull software download site or the UCLA Public Domain...

If the disk is completely mirrored, then to replace hdisk1 from an hdisk0/hdisk1 mirror: 1. unmirror rootvg hdisk1 (remove copies from disk) 2. chpv -c hdisk1 (clear boot image so it doesn't try to boot) 3. bosboot -ad /dev/hdisk0 (create new boot image) 4. bootlist -m normal hdisk0 (boot only...

Recreate hd5 lv (boot) by following the instructions below: rmlv hd5 chpv –c hdisk## ---- for ALL disks (clears the boot record) mkboot –cd /dev/hdisk## --- use this if the above (chpv) command fails mklv –y hd5 –t boot –a e rootvg 1 hdisk## bosboot –ad /dev/hdisk## sync;sync;sync...

Go ahead.

This will restore your mksysb image on node7 (bos.obj.f1n7.012804 – or whatever name) to node3. You will have to restore your data in whatever method you use for recovery, e.g., TSM, savevg, etc. spchvgobj -r rootvg -p PSSP-3.2 -v aix433 -i bos.obj.ssp.432 –c 1 -l 3 spbootins -s no -r install...

That was my first answer! [bigsmile]