Search results for query: *

If my memory serves me correctly, mksysb structure is in 4 parts. the 4th, or last part, is you backup data and is in backup/restore format. You may be able to try the following to see if it's still readable: restore -s4 -Tvf <file> or <device> example if it's your tape drive: restore -s4...

you can put the TL you downloaded into a directory on an AIX servers. From there, you can do the following: bffcreate -c -d /directory/where/TL/is Then you can run your inutoc. the -c changes the image names to package names. Regards, Chuck

yes, you can, although I'm wondering why you only have a single path to your VIO servers. How are you going to recover if you have issues with that path? As far as the mapping from the VIO servers, you can use the same adapters that are being used for SAN boot with not issues. For example, if...

Why don't you migrate by cloning the systems? You do have mksysb's of your systems I presume? Regards, Chuck

df -g |awk -F" " '{sub(/blocks/,"");if (length($1) > 15 ){printf("%s\t%s\t%s\t%s\t%s\n",$1,$2,$3,$4,$5)} else {printf("%s\t\t%s\t%s\t%s\t%s\n",$1,$2,$3,$4,$5)} } ' Regards, Chuck

All the additional "paths" might be coming from PATH being set in /etc/environment. All the following does: export PATH=$PATH:/usr/java6 is append /usr/java6 on the end of the original PATH variable being set somewhere else (i.e. /etc/environment). You can try to edit /etc/environment and...

Go command line... First, run the following and locate the route you want to delete: lsattr -El inet0 Then, remove the route with the following: chdev -l inet0 -a delroute="<route_info>" example: # lsattr -El inet0 authm 65536...

Maybe this article will help: https://www.ibm.com/developerworks/mydeveloperworks/blogs/aixpert/entry/shared_ethernet_adapter_sea_failover_with_load_balancing198?lang=en Regards, Chuck

Check for your default gateway. Seems like after the power failure you might have lost that from the routing table. Regards, Chuck

most common way: lsvg -p <volume_group> Regards, Chuck

Really, there's not much to the configuration. You assign the corresponding virtual adapters on the VIO server and VIO clients (LPAR's), then you map the vfchost adapters (VIO server adapters) to the physical adapters on the VIO server. Depending on Firmware levels of the manage system (is...

Are they mapping the virtual HBA's (vfchost adapters) on the VIO server to the physical HBA's? Regards, Chuck

Unless someone here has some handy scripts already written, this won't be as simple/fast as you probably want. First, you'll want to grab the hardware setup. Easiest is to run a series of lssyscfg and lshwres commands from your HMC similar to: lssyscfg -r sys -m <managed_system_name>...

What about in /etc/multipath.conf? If that file exists, check in there for the WWID's. Regards, Chuck

Try: scsi_id -g -u -s /block/sdd scsi_id -g -u -s /block/sda3 ... and so on for each disk. Regards, Chuck

Check your /etc/exclude.oradbvg file and see what's being excluded in there. If you'd rather have everything backed up, exclude the '-e' flag from your command. Regards, Chuck

No, but I have one AIX 7.1 LPAR running on an old Power5 system... 9113-550. The other AIX 7.1 LPAR's I have are running on Power7. Haven't seen really any negative issues with it. Regards, Chuck

what about: hospitable and inhospitable Regards, Chuck

Just re-read your post and one thing to note, GoAnywhere Director software is seamless when it comes to upgrades. It's both simple and fast. Regards, Chuck

Sounds more like you need a managed file transfer type system. Have a look at GoAnywhere Director: GoAnywhereMFT We use this at our company and I have to say, it will meet all your requirements and then some. They have trial/demo software you can install so you can review it yourself...