If the first stack is configured with VIPARANGE MOVEABLE NONDISRUPTIVE,
the following events occur:
- If the EZB.BINDDVIPARANGE.sysname.tcpname security
profile is defined, or if the SAF parameter is specified on the VIPARANGE
statement and the EZB.BINDDVIPARANGE.sysname.tcpname.resname security
profile is defined, the application issuing the bind() call must have
READ access to the appropriate resource. If the SAF parameter is specified
but the corresponding resource profile is not defined, then the bind
fails. If the security profile is not defined but the same VIPA range
is configured on another stack, any application on that stack can
cause the DVIPA to move there by issuing a bind() call to that DVIPA.
- The DVIPA ownership is immediately transferred to the second stack
which adds the DVIPA to its HOME list and dynamically notifies the
routers. This stack will now receive all new connections for the DVIPA.
- At the same time, the first stack notifies the routers that it
no longer is the owner of the DVIPA, and puts the DVIPA into moving status.
The DVIPA remains in moving status (and
in the first stack's HOME list) until the application closes the socket.
- Existing connections on the first stack are preserved. If the
second stack receives packets intended for existing connections, it
routes the packets to the first stack.
Notes: - To ensure preservation of existing connections on the prior owning
stack, you must define DYNAMICXCF on both stacks, on the IPCONFIG
statement for IPv4 dynamic VIPAs or on the IPCONFIG6 statement for
IPv6 dynamic VIPAs.
- NONDISRUPTIVE is the default for V2R10 and later, and is the only
option supported for IPv6.
- Both stacks must be running V2R10 or later to get non-disruptive
behavior. If either stack is running V2R8, the result will be as
described in VIPARANGE (DEFINE) MOVEABLE DISRUPTIVE.