Manually initiating takeover for an individual dynamic VIPA

There might be times when you want a takeover to occur for an individual DVIPA for temporary, operational purposes, such as dealing with temporary shifts in available capacity. An operator command, VARY TCPIP,,SYSPLEX,DEACTIVATE, is provided to deactivate an active VIPADEFINE DVIPA so that it appears to have been deleted from the stack. This enables an already-configured backup stack to takeover the DVIPA. This command also saves the original configuration definition.

When you want to move the DVIPA back to the original stack, you can issue another operator command, VARY TCPIP,,SYSPLEX,REACTIVATE, on the original stack to cause the DVIPA to be redefined with its saved configuration. This causes a VIPADEFINE DVIPA to be activated again on the original stack, and causes the backup stack to relinquish ownership of the DVIPA and return to being a backup stack.

The following example shows how to deactivate a DVIPA:

VARY TCPIP,,SYSPLEX,DEACTIVATE,DVIPA=203.1.1.99

The following example shows how to reactivate a DVIPA that has been deactivated:

VARY TCPIP,,SYSPLEX,REACTIVATE,DVIPA=203.1.1.99

Deactivating a DVIPA can be done only for DVIPAs that have been configured on the stack with VIPADEFINE or VIPABACKUP. You cannot deactivate a VIPARANGE DVIPA created by BIND, the SIOCSVIPA or SIOCSVIPA6 ioctl command, or the MODDVIPA utility. When you deactivate a DVIPA, if there are any existing connections to the DVIPA on this stack and there is another stack able to maintain the connections, the DVIPA is kept in QUIESCING status until the last connection terminates, and then the DVIPA is deactivated.

You can also use these operator commands to deactivate and reactivate a backup DVIPA. If you deactivate a DVIPA that is in backup status, it makes that stack ineligible to takeover the DVIPA. Reactivating a VIPABACKUP DVIPA makes the stack eligible again to takeover the DVIPA.

While a DVIPA is deactivated it still appears in the Netstat VIPADCFG/-F report, where it is identified as deactivated, but it does not appear in any other Netstat reports unless the DVIPA is in QUIESCING status or this stack is a target for that DVIPA from some other distributing stack.