Delay over a distributed DVIPA when takeback occurs by the primary stack.
A sysplex distributed DVIPA moved to a backup stack during takedown of the primary stack. Though the TCPIP profile of the primary stack contained GLOBALCONFIG SYPLEXMONITOR DELAYJOIN, a delay of a minute or more was seen in activity over the DVIPA when the primary stack took back the distributed DVIPA.
VIPAROUTE was specified in the VIPADYNAMIC definitions in the TCPIP profile, which allows distributed packets to flow over a non-XCF interface (for example, OSA) rather than the XCF links. Because the GLOBALCONFIG SYSPLEXMONITOR DELAYJOIN statement was coded, the primary stack joined the sysplex and took back the DVIPA as soon as OMPROUTE was active. Though OMPROUTE was active, the dynamic routes were not yet active and DVIPA connections were delayed until the dynamic routes became active.
Resolving the problem
Code GLOBALCONFIG SYSPLEXMONITOR MONINTERFACE DYNROUTE on the GLOBALCONFIG profile statement and MONSYSPLEX on the LINK or INTERFACE statements for the links used for VIPAROUTEs.
MONINTERFACE will turn on interface monitoring. MONSYSPLEX will specify what interfaces to monitor and DYNROUTE will delay sysplex processing and the takeover of the DVIPA until dynamic routes are established over the monitored interfaces.
More support for:
z/OS Communications Server
Software version: 1.9, 1.10, 1.11, 1.12, 1.13, 2.1, 2.2
Operating system(s): z/OS
Reference #: 1410357
Modified date: 10 December 2012
Translate this page: