Recent content by bi

Did you set path priority on the LPARs?

Those sites referenced in the other answers may have eventually gotten to this, but this is what I use: Create a link between the boot device indicated and the /dev/ipldevice file. Enter: rm ipldevice ln /dev/boot_device_name /dev/ipldevice example: ln /dev/rhdisk0 /dev/ipldevice Then run...

Check to see if the html fileset for iforls was updated. We had this problem and that was the only fileset that was missing. Run install and search for iforls in the list of available filesets, select it and install it.

And adding to DukeSSD's comment, some filesets won't even install without all the TL and SP level filesets.

It is my understanding that alt_disk_install or alt_disk_migration cannot be used to go from one TL to another. It is used to go from one version to another (5.2 to 5.3, for example) and it works great for that. There is a multi-bos function, which I tried when it first came out, but was...

That must be one huge file. The undo buffer for vi is by default /var and your /var filesystem is pretty big with lots of space still left. If you just want to look at the file, you could try using pg or cat <filename> | more. If you must edit the file, the only way I know to edit it would be...

As is usually the case, I found my problem 10 seconds after I posted. Instead of -vio, I have to use -viosEth <server names> -viosDisk. I kept dropping the s in -vios

Has anyone used the getTgtRsrc command successfully? This is a command found on NIM servers that can be used to query a managed system's vio servers through the managed system's HMC to get information about the resources on the vio servers. I am using this syntax: ./getTgtRsrc -hmc <name of...

Actually, the solution to this problem might not seem as clear cut as some think. It is not a very common error. If you run savebase -v and you get "non-bootable LV name given" try reconstucting your /dev/ipldevice file. (I believe there is a posting somewhere here that tells you how to do...

You could try cleaning up your what your NIM master thinks is exported: mv /etc/exports to a backup file. run: stopsrc -s nimesis stopsrc -s nfsd rm -rf /etc/xtab rm -rf /etc/rmtab rm -rf /var/statmon/sm rm -rf /var/statmon/sm.bak startsrc -s nfsd startsrc -s nimesis mv /etc/exports backup file...

OK. Trying to add 1 PP to a filesystem: 0516-408 allocp: Illegal logical volume identifier value.

Sorry. That was another system that also has the same problem with LVM. I only showed the migratepv error because it seemed to be the most descriptive.

Thanks. $ lsvg rootvg VOLUME GROUP: rootvg VG IDENTIFIER: 000fb1aa00004c00000001104ee9c3d5 VG STATE: active PP SIZE: 64 megabyte(s) VG PERMISSION: read/write TOTAL PPs: 1084 (69376 megabytes) MAX LVs...

I am having problems with rootvg. When trying to do anything with LVM, I get allocp errors. OS level is 5.3 TL4 SP3. The most revealing error I received was when I was trying to do a migratepv on one of the LVs. These are the errors: # migratepv -l hd3 hdisk0 hdisk4 0516-408 allocp: Illegal...

none for the APAR and none for the patch utility used to patch non-installp versions of Java.