On Tuesday, 02/26/2008 at 06:12 EST, Schuh, Richard [EMAIL PROTECTED]
wrote:
16:12:32 HCPSWU2843E A stall was detected for TCP/IP Controller DTCVSW1.
HCPSWU2843E It was managing device 0F00 for VSWITCH SYSTEM VM3SW1.
16:12:32 HCPSWU2830I VSWITCH SYSTEM VM3SW1 status is in error recovery.
, 2008 11:21 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VSWITCH/OSA Problem
On Tuesday, 02/26/2008 at 06:12 EST, Schuh, Richard
[EMAIL PROTECTED]
wrote:
16:12:32 HCPSWU2843E A stall was detected for TCP/IP
Controller DTCVSW1.
HCPSWU2843E It was managing device 0F00 for VSWITCH SYSTEM
: Thursday, February 28, 2008 2:41 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VSWITCH/OSA Problem
Nobody logs on to the controller, so it was likely not a MORE/HOLDING
event. It was early in our day (the 16:xx:xx time is GMT), so we were
not at a peak. The controllers have a REL 3000 share with QUICKDSP
z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Stracka, James (GTI)
Sent: Thursday, February 28, 2008 11:49 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VSWITCH/OSA Problem
We took an MIH hit on an OSA. IBM is developing APAR #
VM64398. You might consider doing an AST
: Thursday, February 28, 2008 3:06 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VSWITCH/OSA Problem
That looks to be a potential problem. I cannot directly tie my problem
to it. We had no MIH message and no users are/were in LOGOFF/FORCE
PENDING. However, it may be that ours is the same problem
On Tuesday, 02/26/2008 at 04:36 EST, Schuh, Richard [EMAIL PROTECTED]
wrote:
This morning, the following was displayed on the console of one of our
VSWITCH
controller machines (DTCVSW1 and DTCVSW2):
16:12:32 DTCOSD020E VSWITCH-OSD device VM3SW10F00DEV: Unexpected SIOCC 3
from Read
From OPERATOR:
16:12:32 HCPSWU2843E A stall was detected for TCP/IP Controller DTCVSW1.
HCPSWU2843E It was managing device 0F00 for VSWITCH SYSTEM VM3SW1.
16:12:32 HCPSWU2830I VSWITCH SYSTEM VM3SW1 status is in error recovery.
HCPSWU2830I DTCVSW2 is new VSWITCH controller.
