AIX Hardware Migration w/ HACMP...Advice Needed

04-25-2016

Registered User

6,384, 2,214

Join Date: May 2005

Last Activity: 28 October 2019, 4:59 PM EDT

Location: In the leftmost byte of /dev/kmem

Posts: 6,384

Thanks Given: 143

Thanked 2,214 Times in 1,548 Posts

Quote:

Originally Posted by uzair_rock

If it's possible can you give me a complete procedure for setting up a (7.1-)-cluster that will help me a lot.

I can do that, but it will have to wait until i am back in the office to consult my documentation. i need my beauty-sleep now. ;-))

bakunin

This User Gave Thanks to bakunin For This Post:

bakunin

View Public Profile for bakunin

Find all posts by bakunin

04-25-2016

Registered User

18, 1

Join Date: Feb 2012

Last Activity: 12 June 2016, 4:07 AM EDT

Posts: 18

Thanks Given: 3

Thanked 1 Time in 1 Post

Quote:

Originally Posted by bakunin

I can do that, but it will have to wait until i am back in the office to consult my documentation. i need my beauty-sleep now. ;-))

bakunin

Absolutely! Take your time and thanks once again!

This User Gave Thanks to uzair_rock For This Post:

uzair_rock

View Public Profile for uzair_rock

Find all posts by uzair_rock

04-26-2016

Registered User

6,384, 2,214

Join Date: May 2005

Last Activity: 28 October 2019, 4:59 PM EDT

Location: In the leftmost byte of /dev/kmem

Posts: 6,384

Thanks Given: 143

Thanked 2,214 Times in 1,548 Posts

Quote:

Originally Posted by uzair_rock

If it's possible can you give me a complete procedure for setting up a (7.1-)-cluster that will help me a lot.

This is how we do it: we configure 2-node active/passive clusters ("rotating") with usually one service address and one or two RGs (i.e. DB, application). Each node has only 1 network adapter ("en0"):

- Create two NPIV-disks 1GB each and zoned to both nodes for the CAA-repositories (you need these instead of the heartbeat-disks).

- add the IPs and DNS-names for all cluster-nodes and all service-addresses to /etc/hosts and /etc/cluster/rhosts:

Code:

# cat /etc/hosts
10.1.1.1    node1
10.1.1.2    node2
10.1.1.3    service1

# cat /etc/cluster/rhosts
10.1.1.1
10.1.1.2
10.1.1.3

- switch off dead-gateway detection if applicable:

Code:

echo "!REQD en0 <default-gw>" > /usr/es/sbin/cluster/netmon.cf

- set PVid for Repo- and Spare-Disks:

Code:

root@node1 # chdev -a pv=yes -l hdisk<XX>
root@node1 # chdev -a pv=yes -l hdisk<YY>

root@node2 # cfgmgr

- start cluster-services:

Code:

root@node1/2 # startsrc -s clcomd
root@node1/2 # startsrc -s clinfoES

- create cluster itself (if that doesn't work restart the clcomd on both nodes like described below):

Code:

root@node1 # clmgr add cluster <CLUSTERNAME> \
             REPOSITORY=<hdiskXX> \
             NODES=<node1>,<node2>

root@node1/2 # stopsrc -s clcomd; sleep 2 ; startsrc -s clcomd

- First-alias distribution policy (needed for NIM to work on active cluster-node). You can do this only after defining the first cluster-network (see below)

Code:

root@node1 # clmgr mod network net_ether_01 RESOURCE_DIST_PREF=NOALI

- discover shared discs/VGs:

Code:

root@node1 # clmgr disco vg

----- So far the cluster itself, now the resource groups. Repeat the following for every RG:

- Service-IP-Label, network:

Code:

root@node1 # clmgr add service_ip <service-IP> NETWORK=net_ether_01

- create application controller (former "start-/stop-scripts"):

Code:

root@node1 # clmgr add application_controller <APP_CONTROLLER_NAME> \
                      STARTSCRIPT=</path/to/startscript> \
                      STOPSCRIPT=</path/to/stopscript>

- create resource group (the following is commented for your information, but you need to remove the comments to make the command work):

Code:

root@node1 # clmgr add rg <RG-name> \
                   NODES=<node1>,<node2>[,...] \    # nodes to serve the RG
                   STARTUP=OHN \                    # online on home node only
                   FALLOVER=FNPN \                  # fallover to the node of next priority
                   FALLBACK=NFB \                   # never fall back ("anti RG-ping-pong")
                   SERVICE_LABEL=<serviceIP> \
                   VOLUME_GROUP=<vg1>[,<vg2>,...] \
                   FORCED_VARYON=true \
                   FS_BEFORE_IPADDR=true \
                   APPLICATIONS=<APP_CONTROLLER_NAME>

- finally sync cluster (just for the nerves :-) )

Code:

root@node1 # clmgr sy cl fix=yes

- start cluster:

Code:

clmgr on node <node1>[,<node2>,...]

I hope this helps.

bakunin

Last edited by bakunin; 04-26-2016 at 10:09 AM..

This User Gave Thanks to bakunin For This Post:

bakunin

View Public Profile for bakunin

Find all posts by bakunin

04-26-2016

Registered User

18, 1

Join Date: Feb 2012

Last Activity: 12 June 2016, 4:07 AM EDT

Posts: 18

Thanks Given: 3

Thanked 1 Time in 1 Post

Quote:

Originally Posted by bakunin

I hope this helps.

bakunin

It surely will help without a doubt! Thanks a ton!

One last question, after testing the cluster and on the day of migrating data disks from the old server. How should I add those disks/VGs on the resource group and re-configure the cluster with the imported npiv disks. can you please explain?

Last edited by uzair_rock; 04-26-2016 at 03:25 PM.. Reason: Missed the quote

uzair_rock

View Public Profile for uzair_rock

Find all posts by uzair_rock

04-26-2016

Registered User

6,384, 2,214

Join Date: May 2005

Last Activity: 28 October 2019, 4:59 PM EDT

Location: In the leftmost byte of /dev/kmem

Posts: 6,384

Thanks Given: 143

Thanked 2,214 Times in 1,548 Posts

Quote:

Originally Posted by uzair_rock

How should I add those disks/VGs on the resource group and re-configure the cluster with the imported npiv disks. can you please explain?

You can configure your cluster with a single disk (visible on all cluster-nodes) as a stand-in. WIth this you test all the IP-adresses, start-/stop-scripts, etc.. You said you want to use new IP-ranges anyways, so you can test with your new production-IPs safely while the old cluster is still running.

On the day of the transition you

- zone the datadisks of your old cluster to the new cluster-nodes (you need SAN support for this)

- throw away your (test-)VG and the RG residing on it.

- run cfgmgr to see the newly discovered discs, import the VGs on all nodes (be sure to end with concurrent-capable Vgs), run a clmgr disco vg ("discover VGs") on one node to make the VGs available in HACMP and run the RG-definition from above (clmgr add rg ...) again. It is that simple.

Do yourself a favour: when importing the VGs on all nodes make sure the same VG gets the same major number on all nodes. It will work without that too, but it makes keeping track easier that way. I even try to have the same hdisk-numbers on all nodes, so that hdiskXX on node1 is also hdiskXX on node2, etc..

I hope that helps.

bakunin

This User Gave Thanks to bakunin For This Post:

bakunin

View Public Profile for bakunin

Find all posts by bakunin

05-02-2016

Registered User

18, 1

Join Date: Feb 2012

Last Activity: 12 June 2016, 4:07 AM EDT

Posts: 18

Thanks Given: 3

Thanked 1 Time in 1 Post

Thanks for the reply Bakunin.

Sorry for the delayed response, was seriously busy at work. I will be testing it out this week and will come back with the response.

Thanks once again!

uzair_rock

View Public Profile for uzair_rock

Find all posts by uzair_rock

AIX

AIX Hardware Migration w/ HACMP...Advice Needed

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need advice for project UNIX to Linux migration

Discussion started by: digioleg54

2. AIX

AIX - FC Switch migration, SAN Migration question!

Discussion started by: BG_JrAdmin

3. HP-UX

VPar hardware migration - ERRATA document

Discussion started by: cecco16

4. Solaris

Hardware to software RAID migration

Discussion started by: rock123

5. Hardware

Hardware compatibility advice wanted.

Discussion started by: Varsel

6. Hardware

Hardware issue advice

Discussion started by: DougyC

7. Linux

Scripting advice needed

Discussion started by: Wiggins

8. AIX

IY17981 fix required for aix 4.3.3 to aix 5L migration but not found

Discussion started by: astjen

9. Solaris

Storage hardware - advice needed

Discussion started by: frustrated1

10. Linux

programming advice needed....

Discussion started by: trostycp