|
|
Sponsored Content
Operating Systems
AIX
Inherited VIO server an LPARs
Post 302493274 by rbatte1 on Wednesday 2nd of February 2011 09:31:44 AM
02-02-2011
Moderator
Inherited VIO server an LPARs
Lucky me, someone has installed a server and got it running with the best intentions, but leaving me a headache. 
We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too.
The other two disks form a volume group each (VIO storage pools). The plan was to ensure that disk allocated to the LPARs would be made in pairs, one from each user-volume group so that we would be confident at the LPAR that the hdisk definitions presented would be from different real media. The problem I now have is that we are adding more real disk (another 16x300Gb in a separate CEC) and add more LPARs.
So, should I create more volume groups on the VIO server (storage pools) on a one-disk-one-pool rule, or should I approach this another way. What would be nice would be a way to present the LPAR with a single device made from a mirror at the VIO server and enforcing strictness on the VIO server to make sure that the mirrors are on different real disks.
I feel that if/when we have a disk failure, I'm going to have a huge mess of failed hdisks in the various LPARs we will have and a huge overhead in logging and maintaining disk separation for all these LPAR hdisks and mirrors making sure that LPAR mirrors do not inadvertently end up on the same real disk as the primary copy, albeit a different hdisk that the LPAR sees.
Big question/headache I know. Any suggestions?
Robin
Liverpool/Blackburn
UK
We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too.
The other two disks form a volume group each (VIO storage pools). The plan was to ensure that disk allocated to the LPARs would be made in pairs, one from each user-volume group so that we would be confident at the LPAR that the hdisk definitions presented would be from different real media. The problem I now have is that we are adding more real disk (another 16x300Gb in a separate CEC) and add more LPARs.
So, should I create more volume groups on the VIO server (storage pools) on a one-disk-one-pool rule, or should I approach this another way. What would be nice would be a way to present the LPAR with a single device made from a mirror at the VIO server and enforcing strictness on the VIO server to make sure that the mirrors are on different real disks.
I feel that if/when we have a disk failure, I'm going to have a huge mess of failed hdisks in the various LPARs we will have and a huge overhead in logging and maintaining disk separation for all these LPAR hdisks and mirrors making sure that LPAR mirrors do not inadvertently end up on the same real disk as the primary copy, albeit a different hdisk that the LPAR sees.
Big question/headache I know. Any suggestions?
Robin
Liverpool/Blackburn
UK
|
|
10 More Discussions You Might Find Interesting
1. SCO
I have inherited admin duties on an old server running SCO Open Server 5. No changes have been made to this thing for a very long time. The server has started randomly disconnecting itself from the network. I have to reboot the server to get it to find the network again. It happens about once a... (3 Replies)
Discussion started by: jmickens
3 Replies
2. AIX
Hi,
I am little confused about the virtual Ethernet configuration on VIO and Client Partitions. There is alot of info on the internet but it gets more confusing....
If I have LHEA, it is very simple. Just assign LHEA (logical host ethernet adapter) to client partition -> run smitty tcpip and... (10 Replies)
Discussion started by: filosophizer
10 Replies
3. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. AIX
Hi
My vio client is getting its virtual Ethernet services from dual vio servers. What command if I execute on the vio
client will get me the names of the vio servers ? (2 Replies)
Discussion started by: samsungsamsung
2 Replies
5. AIX
trying to put VIO server software into this p520, firmware upgraded to the latest and greatest..SF240_415_318 , I think
a few questions, on this practice AIX machine on AIX 7.1
VIO can only be installed if ASMI or HMC is running ???
if so, perhaps ASMI is much simpler, since I will need to... (2 Replies)
Discussion started by: ppchu99
2 Replies
6. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
7. AIX
Hi,
I would like to know installing vio server on local disk and mirroring rootvg,
if I am creating AIX VIO CLIENT(lpar),
and any of single local hard disk failuare.
will it affect lpars? will lpars able to boot.
what needs to be done? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
8. AIX
Hi,
I am facing an issue in vio server. When I run
bosboot -ad /dev/hdisk0
I am getting an error
trustchk: Verification of attributes failed: /usr/sbin/bootinfo
: accessauths
regards,
vjm
Please use code tags next time for your code and data. (8 Replies)
Discussion started by: vjm
8 Replies
9. UNIX for Advanced & Expert Users
Hello,
I would like to identify the blade or/and bladecenter from the hosted VIO server.
I prefer the "command line" solution. May be kdb.
Like, I want to ask the child about his father.
Thank you (1 Reply)
Discussion started by: x41
1 Replies
10. AIX
I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
2 Replies
LEARN ABOUT OSF1
volreattach
volreattach(8) System Manager's Manual volreattach(8) NAME
volreattach - Reattaches disk drives that have once again become accessible SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...] /usr/sbin/volreattach -c accessname OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the disk can be reattached is displayed. DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment. This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical Storage Manager is started, causing disks to enter the failed state. If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. The volreattach command is called from the voldiskadm menus as part of disk recovery. The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists. EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned. SEE ALSO
volintro(8), voldiskadm(8), volrecover(8) volreattach(8)