Search results for query: *

I think you are over processing it. set each line to a var = echo line | wc -w You then know if you need to split the line if you need to split it split it with cut into two var's sline=echo line | cut -c 1-32 eline= echo line | cut -c 33-$[var} echo "$sline \\ " echo " $eline"...

why hook lhe ports to VIO, The whole point of them is to setup links directly to the lpars and bypass VIO control of the lhe cards.

YOu will also have to remove the cluster.es software in order to remove the ODM entries for HACMP.

AIX TCB - the TRUSTED COMPUTING base - This is just an ODM flag that enable the creation of a syschk file where it registers the OS file bit size, chksums etc. AIX TCB is not like solaris Trusted shell, its just an add on. AIX TCB will not stop TL/SP installs, it only affects migrations. (...

MOST SP's can be unapplied, when you apply a TL many times some filesets get commited. Best case, when applying a TL make a mksysb or alt_disk_clone for backout. But yes, most SP's can be unapplied..

IF you dont know the HMC name for an lpar you have to search the RSCT log files. find /var/ct -type file -exec grep -i HscHostName {} /dev/null \; example output.. /var/ct/567237452/log/mc/IBM.CSMAgentRM/trace:Slot info is...

While the route commands will work, also check the odm attributes of your sys0 , you will probably have to do a chdev on syso and adjust the route in the ODM or on next reboot, it will be a gotcha.

crfs Command Purpose Adds a file system. Syntax crfs -v VfsType { -g VolumeGroup | -d Device } [ -l LogPartitions ] -m MountPoint [ -n NodeName ] [ -u MountGroup ] [ -A { yes | no } ] [ -p {ro | rw } ] [ -a Attribute= Value ... ] [ -t { yes | no } ]

AIX is has tools for inittab edits, mkitab , rmitab . You can just remove it and readd it with a comment and stopsrc -g nfs will stop all nfs and rpc services. And yes, no nfs/rpc means no NIM. ( it will fail at least, probably should remove the nim client from inittab as well in that case )

Yeah the find -xdev trick is the first thing I do, If you still cant find the file check lsof to see if someone remove a log and the file handle is still open .

Check your new machine, the LED has a setting on all new machines , sometimes it has to be changed to allow HMC interface. Check the models manual. I had to do this for my P550's when they came. Just switch the LED from standalone to HMC controled, reboot and walla. See if thats it.

Got TCB on a 5.1 system and need to migration with nimadm's alt_disk_install. Got a tip for ya. Remove the odm setting , then migrate the nim client, then boot AIX 5.2 enable TCB then recreate /etc/security/sysck.cfg . Here is the odm twiddle: /usr/bin/odmget -q attribute=TCB_STATE PdAt |...

IF you install on a mirrored set of disks on the rootvg, you can not go back. You updated both disks. If you have broken the mirror ( with alt_disk_vg or manually ) then you could have. Restore it with mksys is best suggestion then use alt_disk_install if able. The old manual way works but is...

I worked on an IBM account that used TSM and ondemand for check imaging. There is a OnDemand API that talks to TSM. Much like the API's for the oracle and sql TDP solutions for TSM.

NIM is still the standard, but we use alt_install_vg's for Regattas and P5's. Why ? Well, it so easy now to swap disks on these large systems - keep a lpar in a system and alt_vg it. Then we keep our mksysimages on an NFS. If a system needs restored - we diag down the disks so we can remove...

Old link still good. http://aixdoc.urz.uni-heidelberg.de/doc_link/en_US/local/Redbooks/pdf/sg245962.pdf

$ ps -ef | grep pts/ | grep -vE "grep| ps -ef " maestro 25418 36136 0 16:10:34 pts/2 0:00 /usr/bin/ksh maestro 26566 25418 0 16:10:44 pts/2 0:00 telnet mptwst ts39461 28682 29008 0 14:21:46 pts/0 0:00 /usr/bin/ksh $ ps -ef | grep...

hm, You could use the alt_disk_isntall if you had a mirrored rootvg. Just make sure to run it staggared and alter the new Vg's PP size, then restore a mkssyb to it and wake it and boot, If all goes well youll have a new PP size for your Rootvg and can wipe the old one.

This is run in order to make the cfgmgr run serial over the childern, it help keep scsi id order on devices added. Normally used when you want to keep the same device id's assigned to the same ODM devices. Case example, I want to configure all the fiber drives on one adapter first, cfgmgr -S...

strange dont know why you wouldn't do do this find <my dir> -name "*sstring*" -mtime +30 -type f -xdev -ls -exec rm {} \; if you have more than one dir loop it in a for