Sponsored Content
Operating Systems AIX Inherited VIO server an LPARs Post 302493274 by rbatte1 on Wednesday 2nd of February 2011 09:31:44 AM
Old 02-02-2011
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. Smilie

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? Smilie



Robin
Liverpool/Blackburn
UK
 

10 More Discussions You Might Find Interesting

1. SCO

Inherited server - need help

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

Virtual Ethernet VIO HMC LPARs

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

vio server and vio client

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

Identifying the vio server names

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

VIO server on p520

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

vio server ethernet to vio client ethernet(concepts confusing)

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

Mirroring vio server

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

VIO Server

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

How to identify the blade from VIO server?

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

Need to replace a broken PV in a VIO VG used for client LPARs (and it won't release the old one)

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
volrecover(8)						      System Manager's Manual						     volrecover(8)

NAME
volrecover - Performs volume recovery operations SYNOPSIS
/sbin/volrecover [-g diskgroup] [-sb] [-o options] [volume | medianame...] OPTIONS
Options that can be specified to volrecover are: Starts disabled volumes that are selected by the operation. Volumes will be started before any other recovery actions are taken. Volumes will be started with the -o delayrecover start option. This requests that any opera- tions that can be delayed in starting a volume will be delayed. In other words, only those operations necessary to make a volume available for use will occur. Other operations, such as mirror resynchronization, attaching of stale plexes and subdisks, and recovery of stale RAID5 parity will normally be delayed. Performs recovery operations in the background. With this option, volrecover will put itself in the back- ground to attach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID5 parity. If this is used with -s, volumes will be started before recovery begins in the background. Performs no recovery operations. If used with -s, volumes will be started, but no other actions will be taken. If used with -p, the only action of volrecover will be to print a list of startable volumes. Prints the list of selected volumes that are startable. For each startable volume, a line is printed containing the following information: the volume name, the disk group ID of the volume, the volume's usage type, and a list of state flags pertaining to mirrors of the volume. State flags and their meanings are: One of the mirrors was detached by an I/O failure One of the mirrors needs recovery, but the recovery is related to an administrative operation, not an I/O failure Neither kdetach nor stale is appropriate for the volume. Displays information about each task started by volrecover. For recovery operations (as opposed to start operations), a completion status is printed when each task completes. Displays commands that volrecover would execute without actually executing them. Lim- its operation of the command to the given disk group, as specified by disk group ID or disk group name. If no volume or medianame operands are given, all disks in this disk group will be recovered; otherwise, the volume and medianame operands will be evaluated relative to the given disk group. Without the -g option, if no operands are given, all volumes in all imported disk groups will be recovered; otherwise, the disk group for each medianame operand will be determined based on name uniqueness within all disk groups. Passes the given option argu- ments to the -o options for the volplex att and volume start operations generated by volrecover. An option argument of the form pre- fix:options can be specified to restrict the set of commands that the -o option should be applied to. Defined prefixes are: Applies to all invocations of the volume utility (volume starts, mirror resynchronizations, RAID5 partity rebuilds, and RAID5 subdisk recoveries) Applies to all invocations of the volplex utility (currently used only for attaching plexes) Applies specifically to plex attach operations applies specifically to volume start operations Applies to subdisk recoveries Applies to mirror resynchronization and RAID5 parity recovery DESCRIPTION
The volrecover program performs plex attach, RAID5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (medianame). If no medianame or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). If -s is specified, disabled volumes will be started. With -s and -n, volumes are started, but no other recovery takes place. Recovery operations will be started in an order that prevents two concurrent operations from involving the same disk. Operations that involve unrelated disks will run in parallel. EXAMPLES
To recover, in the background, any detached subdisks or plexes that resulted from replacement of a specified disk, use the command: # volrecover -b medianame If you want to monitor the operations, use the command: # volrecover -v medianame SEE ALSO
volintro(8), volplex(8), volume(8) volrecover(8)
All times are GMT -4. The time now is 02:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy