×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

PowerHA IP migration

PowerHA IP migration

PowerHA IP migration

(OP)
Hi AIX gurus

A client has decided to create a separate (production) network for their application which runs in a WPAR in a VIO environment. VIOS version is 2.2.5.20. This means new ip addresses for the cluster which has five resource groups.

I am totally new to PowerHA and have never migrated IP addresses in a cluster before so I would like your expertise regarding the procedure and any gotchas to watch out for.

Some questions for clarification:
1. would I have to modify the PVID of a virtual adapter?
2. I guess I need to completely Redo the network configuration of the WPAR and the cluster Resource groups.

I would appreciate some tips and shared experience.

Here's some basic info about the environment (from the primary site).

[PROD] root@NODE41:/root# clRGinfo
----------------------------------
Group Name Group State Node
------------------------------------
RG_atlas00 ONLINE NODE41
OFFLINE NODE42

RG_regal00_tws ONLINE NODE41
OFFLINE NODE42

RG_sideral0 ONLINE NODE41
OFFLINE NODE42

RG_siderald0 ONLINE NODE41
OFFLINE NODE42

RG_sitar0 ONLINE NODE41
OFFLINE NODE42


[PROD] root@NODE41:/root# ifconfig -a
en0: flags=1e084863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
inet XX.XX.242.202 netmask 0xfffffe00 broadcast XX.XX.243.255
inet XX.XX.242.199 netmask 0xfffffe00 broadcast XX.XX.243.255
inet XX.XX.242.221 netmask 0xfffffe00 broadcast XX.XX.243.255
inet XX.XX.242.198 netmask 0xfffffe00 broadcast XX.XX.243.255
inet XX.XX.242.97 netmask 0xfffffe00 broadcast XX.XX.243.255
inet XX.XX.242.184 netmask 0xfffffe00 broadcast XX.XX.243.255
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1


/etc/hosts

# Internet Address Hostname # Comments
# 192.9.200.1 net0sample # ethernet name/address
# 128.100.0.1 token0sample # token ring name/address
# 10.2.0.2 x25sample # x.25 name/address
127.0.0.1 loopback localhost
XX.XX.242.197 lucairu100 LUCAIRU100 LUCAIRU100.prod.lux.DOMAIN.com

#*****************************************************************************
# ********************** Application labels
#*****************************************************************************
XX.XX.242.198 lhsitar0 # service ip label for db2sitar0
XX.XX.242.199 lhsideral0 # service ip label for db2sideral0
XX.XX.242.221 lhsiderald0 # service ip label for db2siderald0 CBD
XX.XX.242.97 vh-atlas00 # service ip label for WPAR vh-atlas00
XX.XX.242.184 vh-regal00-tws # service ip label for WPAR vh-regal00-tws
#*****************************************************************************
# ********************** Node 1 of cluster (NODE41)
#*****************************************************************************
XX.XX.242.202 NODE41 NODE41 NODE41_pers.prod.lux.DOMQIN.com NODE41B1

#*****************************************************************************
# ********************** Node 2 of cluster (NODE42)
#*****************************************************************************
XX.XX.242.185 NODE42 NODE42 NODE42_pers.prod.lux.DOMAIN.com NODE41B2

#192.XX.XX.250 daccessing.inforsud-editique.com daccessing.edokial.com
10.244.29.33 daccessing.inforsud-editique.com daccessing.edokial.com

::1 localhost loopback
XX.XX.114.111 cacvlclux001.DOMAIN.com soclog
XX.XX.242.115 cacnimlux001
hosts: END


Cluster status


clstat - HACMP Cluster Status Monitor
-------------------------------------

Cluster: cluster23 (1548455541)
Mon May 13 15:09:19 CEST 2019
State: UP Nodes: 2
SubState: STABLE


Node: NODE41 State: UP
Interface: NODE41 (2) Address: XX.XX.242.202
State: UP
Interface: hdisk17_01 (0) Address: 0.0.0.0
State: UP
Interface: hdisk18_01 (1) Address: 0.0.0.0
State: UP
Interface: lhsitar0 (2) Address: XX.XX.242.198
State: UP
Interface: lhsideral0 (2) Address: XX.XX.242.199
State: UP
Interface: lhsiderald0 (2) Address: XX.XX.242.221
State: UP
Resource Group: RG_atlas00 State: On line
Resource Group: RG_regal00_tws State: On line
Resource Group: RG_sideral0 State: On line
Resource Group: RG_siderald0 State: On line
Resource Group: RG_sitar0 State: On line

Node: NODE42 State: UP
Interface: NODE42 (2) Address: XX.XX.242.185
State: UP
Interface: hdisk17_02 (0) Address: 0.0.0.0
State: UP
Interface: hdisk18_02 (1) Address: 0.0.0.0
State: UP


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close