Hi Alex,
try this:
for i in $(lsfs | grep namefs | awk '{ print $3 }'); do chfs -a type=yourtype $i;done
after that you can mount/umount your namefs filesystems with
#mount -t yourtype
#umount -t yourtype
HTH
Axel
Hi Stephane,
if you want to move the VG to another system it's enough to varyoffvg the VG on the old system and cfgmgr (to get the disks if not already done) and varyonvg on the new system.
The old system still knows the VG. If you want the old system to forget the VG run exportvg which could...
Setting a new hostname is not changing your Ethernet Adapters.
Run "smitty chinet" select the appropriate adapter and change the old IP Adress to the new IP Adress
Axel
Hi Nils,
we use a total of 4 disks for 2 VIO Server rootvg's.
In our p550 we use all 8 disk slots ( 4 x VIO rootvg,
4 x Client LPAR rootvg)
If you want to create a second VIO Server you need an additional SCSI Adapter, because you cant share the internal one.
The Feature Codes for the HW...
Log on to your HMC and run:
lshwres -r io --rsubtype slot -m <managed system>
that works on my power5 HMC.
For power4 HMC the command might be slightly different.
Axel
I think the recommendation make sense, but if you have only 2 disks in your VIO Server you can decide to mirror all data (VIO rootvg and Client LPAR rootvg) or have a single point of failure.
We have decided to use 2 disks for VIO rootvg with mirroring and 1 or 2 disks with Client LAPR...
Hi Nils,
you are right. That would be a desaster with one HMC but
that's the reason why every p5 Server can connect to two HMC's...
I just got another information from my IBM Rep. VIO with FC and HACMP will officialy be supported not before mid of this year (more likely end of this year)
Axel
Hi,
I have found something about VIO and HA Setup.
Perhaps this is the reason why MPIO is not working on your client Partition.
Here the IBM Text:
snip...
If the reserve_policy value is anything other than no_reserve, it must be changed in order to use the device in an MPIO configuration on...
Hi David,
yes dlpar is very "Name resolution" sensitive.
We haven't done a lot of performance testing yet, but what we have seen is that it is a good idea to use the uncapped option for processors from the Processor pool. (if you dont't use dedicated procs for VIO).
But of course we don't use...
Hi Debi,
the steps you used were the correct ones, but you have to use the whole name in your chfs command:
chfs -a logname=/dev/loglv03 fs
Regards
Axel
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.