Blogs Classifieds Downloads FlashChat Gallery Googlemap Invite Friends Links Projects Reviews Wiki
 


Our Sponsors
Want to advertise?  


Reply
 
LinkBack Thread Tools
  #1  
Old June 28th, 2006
steevojb's Avatar
steevojb Offline
Senior Member
 
Join Date: June 2006
Location: manchester, england
Posts: 194
VIO Client Mirrored Volumes

Hi There

What is the supported option for mirroring a VIO client rootvg ? At the moment I have created 2 lvols ( 2 * 18gb ) on the VIO server on seperate hdisk (72gb each) and presented these to the client. On the client I have then mirrored the hdisks. This seemed to work OK, I have booted from both sides of the mirror without any problems. Next step is to pull a hdisk from the VIO server to test the outcome

Steve
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #2  
Old June 28th, 2006
FASherman's Avatar
FASherman Offline
IBM pSeries and Storage Architect
 
Join Date: May 2006
Posts: 240
Send a message via Yahoo to FASherman
Re: VIO Client Mirrored Volumes

You've done it exactly right. The mirroring has to be done at the client or at the array. Never, ever mirror rootvg LVs on the VIO server.

Just remember when you start pulling drives that every time you do, the rootvg on the client goes stale. Give it time to resync before testing with the other drive or the results can be "unpredictable".
__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.


Fred Sherman
IBM pSeries and Storage Architect
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #3  
Old June 28th, 2006
steevojb's Avatar
steevojb Offline
Senior Member
 
Join Date: June 2006
Location: manchester, england
Posts: 194
Re: VIO Client Mirrored Volumes

Great, thanks for the reply
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #4  
Old September 6th, 2006
astralvoid's Avatar
astralvoid Offline
Junior Member
 
Join Date: August 2006
Location: Charleston, WV
Posts: 22
Smile Re: VIO Client Mirrored Volumes

I have a similar setup on my Virtual LPARs. I have my client rootvg mirrored across disks present from each VIO server.
eg. hdisk0 = viosrv1 and hdisk1 = viosrv2, On client, I mirrored hdisk0 <--> hdisk1.

The problem I have is when one VIO server is rebooted, the rootvg Lvs go STALE and the presented disk changes to 'MISSING' The only way to recover from this is to break the mirror, remove the missing hdiskx from the rootvg, rmdev, cfgmgr, extendvg, and remirror. Is there an easier way to do this such as automated scripts, etc?

Any suggestions would be greatly appreciated.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #5  
Old September 10th, 2006
chanduamar's Avatar
chanduamar Offline
Junior Member
 
Join Date: September 2006
Posts: 4
Re: VIO Client Mirrored Volumes

Hi,
This issue is common when you reboot one of the VIO server all client drives goes into missing state, At this point we have to do on client partitions is
lsdev -Cc disk | more , here you will see all the dirves comming from VIO server shows in defined state,run cfgmgr , now you will see all drives in available state, but pv status is will be sitll missing, so run synclvodm -Pv vgname this command will bring all drives into active state, but still lsvg -l vgname shows "stale" so we need to run syncvg -v vgname this will bring to syncd state.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #6  
Old November 28th, 2006
b00tsie's Avatar
b00tsie Offline
Junior Member
 
Join Date: October 2006
Posts: 26
Re: VIO Client Mirrored Volumes

Quote:
Originally Posted by FASherman
You've done it exactly right. The mirroring has to be done at the client or at the array. Never, ever mirror rootvg LVs on the VIO server.

Just remember when you start pulling drives that every time you do, the rootvg on the client goes stale. Give it time to resync before testing with the other drive or the results can be "unpredictable".
If you attach the drive again, please use varyonvg rootvg to refresh the volumegroup on the clientside. This was actually a question in test 062;-)
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #7  
Old January 9th, 2007
rvannoy's Avatar
rvannoy Offline
Junior Member
 
Join Date: December 2006
Posts: 13
Smile Re: VIO Client Mirrored Volumes

Quote:
Originally Posted by chanduamar
Hi,
This issue is common when you reboot one of the VIO server all client drives goes into missing state, At this point we have to do on client partitions is
lsdev -Cc disk | more , here you will see all the dirves comming from VIO server shows in defined state,run cfgmgr , now you will see all drives in available state, but pv status is will be sitll missing, so run synclvodm -Pv vgname this command will bring all drives into active state, but still lsvg -l vgname shows "stale" so we need to run syncvg -v vgname this will bring to syncd state.
I also use varyonvg (rootvg or vgname) on the VIO client once both vio servers are up as well and lsvg -l to check the lv stale/syncd state and in many cases this will also work.

Regards,

Rick Vannoy
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #8  
Old January 10th, 2007
astralvoid's Avatar
astralvoid Offline
Junior Member
 
Join Date: August 2006
Location: Charleston, WV
Posts: 22
Re: VIO Client Mirrored Volumes

Due to the potential issues of missing a STALE volume on the client side, I started using MPIO(Multi-path IO) as my primary method of 'mirroring' the client lpars. My mirror is handled on the SAN via whatever RAID I choose to use, so the client only sees 1 disk. This insures that no STALE volumes will ever exist. When one VIO fails over, the other Path kicks in and the client really isn't impacted. When the failed VIO comes back online, the path is automatically switch back to the primary.

The main limitation for using MPIO is that the complete physical volume must be allocated for a 1-to-1 disk from VIO to client. Since I create a new volume on my SAN for each disk, I'm not too concerned about wasting disk space. Another 'downside' to using MPIO through the VIO server is that you have to map PVID/serial numbers of disks between the client and VIO server in order to keep track of each disks 'real' location.

Any other ideas out there on this?
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #9  
Old January 10th, 2007
ross.mather's Avatar
ross.mather Offline
Senior Member
 
Join Date: January 2007
Location: Nomadic in the UK
Posts: 574
Re: VIO Client Mirrored Volumes

Astralvoid - This is exactly what I usually do. Dependent on the Storage device used you can discover the LUN id vis the Derial Number (and usually) the Z1 attribute of the disk. You can then script the connection of LUN to LPAR to work from a central location.

This also has the advantage of not needing an LVM on the VIO, so the VIO has less to do.

cheers
Ross
__________________
Ross Mather, IBM AIX IT Specialist.
That said anything I say here is my own opinion and not anything that you can ever hold against IBM.
Ohhh and don't forget that I make mistakes too....
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #10  
Old July 4th, 2009
ilikedirt's Avatar
ilikedirt Offline
Junior Member
 
Join Date: June 2008
Posts: 1
Re: VIO Client Mirrored Volumes

"I also use varyonvg (rootvg or vgname) on the VIO client once both vio servers are up as well and lsvg -l to check the lv stale/syncd state and in many cases this will also work."

This works extremely well, but first, I had to:
sysdumpdev -p /dev/sysdumpnull
... then
varyonvg rootvg (This step made hdisk1 "active")
synclvodm -Pv rootvg
syncvg -v rootvg
sysdumpdev -p /dev/hd6 (restore orig. dump device)

... just for paranoia sake, I also did
bosboot -ad hdisk1 (hdisk1 was the "missing" PV)
bootlist -o -m normal (Verify bootlist is still OK)

Since you have to go through this rigamarole with rootvg built on VIO disks backed by LV's and mirrored at the Client, building rootvg on whole SAN disks with multiple paths and MPIO is more robust, I agree.

E Hank Williamson
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Reply

Bookmarks

These are the 100 most searched terms
Search Cloud
0042-001 0042-001 nim 0042-008 nimsh: request denied 0513-001 the system resource controller daemon is not active 0513-001 the system resource controller daemon is not active. 0514-061 0514-061 cannot find a child device 0514-061 cannot find a child device. 0516-787 0516-787 extendlv 0516-787 extendlv: maximum allocation for logical volume 110000ac 3074feb7 aa00e1f3 aio aix aix aio aix freeware aix memory usage aix rsync aixif_arp_dup_addr b150f22a b181f22a b181fb53 ba010004 c1001020 d133c002 dacnone dcb47997 fcp_array_err6 fget_config gnu tar aix gtar aix hmc root password hmc vmware ibm p6 520 libpopt.a libpopt.a(libpopt.so.0) is needed by rsync-2.6.2-1 migratelv mksysb navisphere agent nim server pseriestech ptype and account type do not match rshd: 0826-813 permission is denied. rsync aix sc_disk_err4 scan_error_chrp vio server vmware hmc websm ... powered by Simple Search Cloud


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
Microsoft Windows 2003 Active Directory integration FASherman Tutorials 30 July 2nd, 2009 09:03
NIM server and client operations steevojb Tutorials 23 March 9th, 2009 15:38
load balancing on VIO client mmmzzz AIX for POWER Systems 1 April 9th, 2007 15:22
Vio Client san disk allocation datamax IBM PowerVM Editions 2 February 21st, 2007 02:43
VIO Backup Strategy steevojb AIX for POWER Systems 1 August 30th, 2006 09:38



Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Powered by vbWiki Pro 1.3 RC5. Copyright ©2006-2007, NuHit, LLC

vBulletin Skin developed by: vBStyles.com


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73