Here is VM01:
VM TCP/IP Netstat Level 430
Device OSAVM1 Type: OSD Status: Ready
Queue size: 0 Address: 0100 Port name: PORTVM1
Router Type: NonRouter
Link OSA100 Type: QDIOETHERNET Net number: 0
Broadcast Capability: Yes
Multicast Capability: Yes
Group Members
----- -------
224.0.0.1 1
Here is VM02:
VM TCP/IP Netstat Level 520
Device [EMAIL PROTECTED] Type: OSD Status: Ready
Queue size: 0 CPU: 0 Address: 0200 Port name: PORTVM2
IPv4 Router Type: Primary Arp Query Support: Yes
Link OSAVM2 Type: QDIOETHERNET Net number: 0
BytesIn: 198045 BytesOut: 377427
Forwarding: Enabled MTU: 1492 IPv6: Disabled
Broadcast Capability: Yes
Multicast Capability: Yes
Group Members
----- -------
224.0.0.1 1
Daniel Allen
Sr. System Programmer
Serena Software, Inc.
13713 Pinto Lane
Lodi, CA 95240
800-457-3736 ext. 11241
[EMAIL PROTECTED]
Serena Software, Inc.
www.serena.com
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Edward M. Martin
Sent: Friday, August 24, 2007 12:06 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: TCP/IP problem with two z/VM systems
Hello Daniel Allen,
We have a z890 with the QDIO being used by Both z/VM and VSE
systems.
The VSE system had a parameter (removed now that we are on QDIO) of
STOPLAN=YES/NO.
The STOPLAN=yes was the default. We had to have STOPLAN=NO.
>From what I learned, a 3172 (or equivalent) could be shutdown and a
Stoplan instruction would be issued to the device. When I shutdown
TCPIP using a logical device on an OSA-2 card, it would shutdown that
card, therefore we had to code the STOPLAN=NO on all devices in the VSE
systems.
It seems that something is issuing a STOPLAN instruction to both
of your z/VM system cards.
Would you do a NETSTAT DEVLINK on your z/VM systems and send the
output here? (Are you allowed to?)
here is my output.
netstat devlink
VM TCP/IP Netstat Level 430
Device OSDD20 Type: OSD Status: Ready
Queue size: 0 Address: 0D20 Port name: P140
Router Type: NonRouter
Link GBED20 Type: QDIOETHERNET Net number: 0
Broadcast Capability: Yes
Multicast Capability: Yes
Group Members
----- -------
224.0.0.1 1
Ed Martin
Aultman Health Foundation
330-588-4723
[EMAIL PROTECTED]
ext. 40441
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
> Behalf Of Daniel Allen
> Sent: Friday, August 24, 2007 2:51 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: TCP/IP problem with two z/VM systems
>
> Our z/OS guest is actually a OS/390 2.10 system. When I force/xautolog
> TCPIP on VM01, the OS/390 2.10 system works.
>
> When this problem first started, we had VM01 using 100-102, VM02 using
> 103-105 and OS/390 2.10 using 104-106. We moved VM02 to use 200-202.
>
> We also moved a new cable from port 21 to port 15 on the hub/switch.
>
>
> Daniel Allen
> Sr. System Programmer
> Serena Software, Inc.
> 13713 Pinto Lane
> Lodi, CA 95240
> 800-457-3736 ext. 11241
> [EMAIL PROTECTED]
> Serena Software, Inc.
> www.serena.com
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
> Behalf Of Rich Smrcina
> Sent: Friday, August 24, 2007 11:37 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: TCP/IP problem with two z/VM systems
>
> Is anything happening to z/OS?
>
> Is all of this on one card (with two ports)?
>
> Is someone messing around with the switch or hub that these are
plugged
> in to? Is it on flaky power or something?
>
> Daniel Allen wrote:
> > We are experiencing a TCP/IP with two z/VM systems.
> >
> > Background:
> >
> > One z/VM system using OSA 100-102. One z/OS guest using OSA 104-106.
> >
> > Another z/VM system using OSA 200-202.
> >
> > One z/VM system TCPIP machine dies with the following:
> >
> > ***** 08/24/07 *****
> > 01:23:44 DTCOSD309W Received adapter-initiated Stop Lan
> > ***** 08/24/07 *****
> > 01:23:44 DTCOSD082E OSD shutting down:
> > 01:23:44 DTCPRI385I Device OSAVM1:
> > 01:23:44 DTCPRI386I Type: OSD, Status: Ready
> > 01:23:44 DTCPRI387I Envelope queue size: 0
> > 01:23:44 DTCPRI388I Address: 0100
> > 01:23:44 DTCQDI001I QDIO device OSAVM1 device number 0102:
> > 01:23:44 DTCQDI007I Disable for QDIO data transfers
> >
> > Another z/VM system TCPIP machine dies with the following:
> >
> > ***** 08/24/07 *****
> > 01:23:44 DTCOSD309W Received adapter-initiated Stop Lan
> > ***** 08/24/07 *****
> > 01:23:44 DTCOSD082E OSD shutting down:
> > 01:23:44 DTCPRI385I Device [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>:
> > 01:23:44 DTCPRI386I Type: OSD, Status: Ready
> > 01:23:44 DTCPRI387I Envelope queue size: 0
> > 01:23:44 DTCPRI388I Address: 0200
> > 01:23:44 DTCQDI001I QDIO device [EMAIL PROTECTED] <mailto:[EMAIL
> > PROTECTED]> device
> number
> > 0202:
> > 01:23:44 DTCQDI007I Disable for QDIO data transfers
> >
> > We have had IBM replace the OSA for CHPID 01.
> >
> > Where do we look now ?
> >
> > Daniel Allen
> > Sr. System Programmer
> > Serena Software, Inc.
> > 13713 Pinto Lane
> > Lodi, CA 95240
> > 800-457-3736 ext. 11241
> > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Serena Software, Inc.
> > www.serena.com <http://www.serena.com/>
> >
> >
> >
**********************************************************************
> >
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. Any unauthorized review, use, disclosure or
> > distribution is prohibited. If you are not the intended recipient,
> > please contact the sender by reply e-mail and destroy all copies of
> the original message.
> >
> >
**********************************************************************
> >
> >
> >
>
> --
> Rich Smrcina
> VM Assist, Inc.
> Phone: 414-491-6001
> Ans Service: 360-715-2467
> rich.smrcina at vmassist.com
> http://www.linkedin.com/in/richsmrcina
>
> Catch the WAVV! http://www.wavv.org
> WAVV 2008 - Chattanooga - April 18-22, 2008
