Solved

AIX vary off/vary on on cluster node

Posted on 2015-02-09
7
278 Views
Last Modified: 2015-02-27
We  need to install VCS cluster on AIX server, but we need to pre-resting.

IF we map Disks from VIO server to 2 LPARs,  in first node you will create the VG and will add those disk to VG and vary on the VG , and mount the FS

If you go to scond node,  you just need to import the  disk on the VG right? After unmount and vary of from node1 ?
0
Comment
Question by:mokkan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 40599634
Right!

Please take care to create the PVIDs already on VIOS (chdev -dev hdiskX -attr pv=yes) before mapping the disks, instead of letting the PVIDs be created automatically during mkvg/extendvg on the LPAR.

If VCS supports concurrent mode VGs (I only know PowerHA) then in the future (i.e. once both nodes know the VG) you just need to run "importvg -L ..." on the second node after making changes/adding disks on the first node. No more varyoff required.
0
 

Author Comment

by:mokkan
ID: 40600446
Thank you for the update. do you need to import the disks all the time or can you just vary on?
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 40600461
When a disk has been added to the VG on node A you must run on node B

importvg -L <vgname> <hdiskname>

where <hdiskname> is the name of a disk already known to node B, not the name of the new disk!

The volume group must be varied on on node A and thus must not be varied on on node B (where the "importvg -L ..." command is run).

Notes:

- Take care to run "cfgmgr" on node B before running "importvg", so that the new disk is actually known to the OS of node B
- It might be necessary to unlock the volume group's disks on node A to run "importvg -L ..." successfully on node B. To unlock run on node A: "varyonvg -b -u <vgname>".  This can be done while the VG is varied on. The VG and its disks will remain active and useable.

- I made a mistake in my first comment: "importvg -L .." works also on non-concurrent VGs, sorry!

VGs varied on in concurrent mode require a cluster process to monitor VG/LV states and accesses. This process will also make new hdisks and LVs known to all nodes in the cluster, provided that the disks have been made available and known to all nodes via "cfgmgr" before running "extendvg" on the primary node.

"importvg -L ..." is then only needed to make new filesystems known to the respective node. At least under PowerHA the cluster process ("gsclvmd") will not see new filesystems.
0
The Ultimate Checklist to Optimize Your Website

Websites are getting bigger and complicated by the day. Video, images, custom fonts are all great for showcasing your product/service. But the price to pay in terms of reduced page load times and ultimately, decreased sales, can lead to some difficult decisions about what to cut.

 

Author Comment

by:mokkan
ID: 40600470
Thano you.  Once you imported the disk. OS should know about the disks and you can just vary on the vg and mount the F'S right? You don't need to import all the time?
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 40600476
If nothing has changed (no new disks, LVs or filesystems!)  you can just varyoff the VG on node A and varyon on node B. No import required, just mounting the FS's.
0
 

Author Comment

by:mokkan
ID: 40600483
Awesome thank you.  If you want to remove the hdisk from both nodes, you can unmapped from vios  and if you run cfgmgr  it should go away right?
0
 
LVL 68

Accepted Solution

by:
woolmilkporc earned 500 total points
ID: 40600499
Not quite right.

Of course you'll have to get rid of the filesystesms and logical volumes on the hdisks first.
On node A remove the LVs and FSs and run reducevg,  then run importvg -L on all other nodes.
The above makes the disks "free" and, after unmapping from VIOs, you can run

rmdev -dl hdiskN

on every node for every disk you want to remove.

Just "cfgmgr" is not sufficient!
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In tuning file systems on the Solaris Operating System, changing some parameters of a file system usually destroys the data on it. For instance, changing the cache segment block size in the volume of a T3 requires that you delete the existing volu…
I promised to write further about my project, and here I am.  First, I needed to setup the Primary Server.  You can read how in this article: Setup FreeBSD Server with full HDD encryption (http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/A_3660-S…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question