Try D TCPIP,tcipname,N,VIPADYN (or the TSO equivalent) on each affected LPAR and verify the VIPAS are active.
Other than that, IMO, this is most likely a routing problem. BTW, this question would probably be better asked on the TCPIP list. IBM TCP/IP List <[email protected]> HTH, </snip> We have the strangest problem regarding DVIPA and communication between the plex lpars. In Production we have 2 z/OS 1.11 plex members using sysplex dist and DVIPA. In Dev and sandbox we have 2 z/OS 1.13 plex members using sysplex dist and DVIPA. Last week Production lpars stopped communication between them, we see this mostly in MQ and DB2 basically if you do a TELNET from LPAR A to LPAR B (and vice versa) you get timeout. If you do the telnet from outside it works ok. The same thing occurs on Dev plex but in SandBox everything is working. The messages we get are like these: CSQX202E #MQP2 CSQXRCTL Connection or remote listener unavailable, 166 channel TO.PRDMB00.CSQB, connection (172.31.20.57) TRPTYPE=TCP RC=00000467 (ETIMEDOUT) reason=00000000 </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
