I'm in the process of converting a Omegamon Hub to become Highly Available. I'm reading more into DVIPA and wanted to know what's the best practice for the following statements, DVIPADYNAMIC, DVIPADEFINE, DVIPARANGE. We'll be running a single instance of OMEGAMON Hub with the started task name OMEGHAH. We'll move the started task as one LPAR goes down.

• LPARB (Acting distributor) - All the VIPA statements reside here for other started tasks. 
• LPARA (Preferred Primary for Omegamon hub)
• LPARC

Do we need the following statement in each TCPIP stack?

DYNAMICXCF x.x.x.a  255.255.255.0 1 
SYSPLEXROUTING                             

VIPADYNAMIC
 VIPADEFINE 255.255.255.0 x.x.x.V
 VIPADISTRIBUTE DEFINE DISTM HOTSTANDBY x.x.x.V
PORT xxx DESTIP
x.x.x.b  - LPAR1
 x.x.x.a - LPAR2

x.x.x.c - LPAR3
ENDVIPADYNAMIC

I would like to know more about VIPARANGE. Could you provide more details on VIPARANGE and some use case scenario?

So the answer to your question do you need this on each stack yes and no ....  

So on LPARB I would put the following 

DYNAMICXCF x.x.x.b  255.255.255.0 1 
SYSPLEXROUTING                             

VIPADYNAMIC
 VIPADEFINE 255.255.255.0 x.x.x.V
ENDVIPADYNAMIC

lpar a IS YOUR BACKUP SO code the following 

DYNAMICXCF x.x.x.a  255.255.255.0 1 
SYSPLEXROUTING                             

VIPADYNAMIC
 VIPABACKUP 150 x.x.x.V 255.255.255.255
ENDVIPADYNAMIC

on C you would just have the dynamic xcf statement unless you want to make it a back up as well

DYNAMICXCF x.x.x.c  255.255.255.0 1 

Now in an include file put your Vipadistributor and use an include file for in the following 

VIPADYNAMIC

VIPADISTRIBUTE DEFINE DISTM HOTSTANDBY x.x.x.V
PORT xxx DESTIP
x.x.x.b   PREFERRED     
x.x.x.a   BACKUP 250

x.x.x.c   BACKUP 1 
ENDVIPADYNAMIC

ENDVIPADYNAMIC

------------------------------
Thomas Cosenza
------------------------------