A vhost adapter on a VIOS is mapped to an LparID/VirtualSlotNumber
And lsmap -all shows for each vhost to which LparID it is connected (the number is in hex). So you'll need some nifty scripting to get the lsmap output squeezed into the format you want. VIOS doesn't know Lpar names based on...
And it won't boot in normal mode? If so, go to oem_setup_env, then shutdown -m. Or if you have an appropriate DVD, boot it in maint mode from DVD?
HTH,
p5wizard
Ask the network guys to disable two of the three ports and boot off the third port.
Or if you have someone on site, have them unplug two of the three network cables and boot off the one adapter that is plugged in.
Or if the ports are on different adapters, build an LPAR profile with just one...
> Only one person has access to the HMC and he is unavailable.
bad decision... [banghead]
Make him/her available again, that will be your only solution.
HTH,
p5wizard
That depends on how your zoning is set up. I use for each server a zone with its HBA (or HBAs) and the SANserver/controller ports that it needs to reach. So if I need to re-zone a server, only one zone needs a change (two if you have two separate fabrics). The rest of the zone set(s) remain(s)...
If the LV is mirrored in a 2-disk mirrored rootvg, then just this will do:
chfs -asize=1G /mkcd
The LVM subsystem will ensure that the underlying LV will be extended in a mirrored fashion.
No reboot or whatever. It's likely a jfs2 filesystem, so you can shrink it back to 0.5GB afterwards if...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.