Mark,
I am pretty sure they are,
but I do know the FAIL OVER works fine.
If I find out different I will let you know.
munson
201-418-7588
Mark Pace <mpac...@gmail.com>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
04/26/2010 11:40 AM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: VSWITCH & OSA-Express 3
Bill -
are 643 & 613 on the same OSA port? It appears that your Layer 3
fail-over address and Layer 2 are on the same port, but not your Layer 3
primary addresses.
On Mon, Apr 26, 2010 at 11:26 AM, Bill Munson <william.mun...@bbh.com>
wrote:
here is our Sys Config for both Layer 2 and Layer 3 on the same z/VM
system
/**********************************************************************/
/* Layer 3 Vswitch Definition and Access */
/**********************************************************************/
DEFINE VSWITCH VM3SWTCH RDEV 643 610 PORTNAME PORT643 PORT610
/**********************************************************************/
/* Layer 2 Vswitch Definition and Access */
/**********************************************************************/
DEFINE VSWITCH VM3AWTCH RDEV 613 ETHERNET
good luck
munson
201-418-7588
Mark Pace <mpac...@gmail.com>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
04/26/2010 11:11 AM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
VSWITCH & OSA-Express 3
Can you run both a Layer 2 vswitch and a Layer 3 vswitch in a z/VM LPAR
using the same OSA-Express 3 port on a z10? Obviously different real
addresses, but on the same OSA port.
I've read the OSA-Express Customer?s Guide and Reference and I'm confused.
>From the system config
DEFINE VSWITCH VSWTCH1 RDEV 0604 CONTR * ETH
Define VSWITCH VSWTCH3 RDEV 0608 CONTR * IP
I am getting random errors on this OSA in z/OS and z/VM.
What is interesting here is that z/OS detects errors, or at least reports
them, before z/VM. z/VM doesn't have an issue until the CU is reset.
Also, z/OS recovers nicely. z/VM, not so much. I have to issue an SET
VSWITCH vswtchname CONNECT to get it working again.
>From z/OS
10114 02:41:11.90 STC00075 00000090 IOS050I CHANNEL DETECTED ERROR ON
0600,**,**,**04
10114 02:41:11.90 STC00075 00000090 IOS050I CHANNEL DETECTED ERROR ON
0602,**,**,**04
10114 02:41:11.90 STC00067 00000090 EZZ4310I ERROR: CODE=80100040
REPORTED ON DEVICE MPCIPA1. DIAGNOSTIC
CODE:
03
10114 02:41:11.90 STC00067 00000090 EZZ4309I ATTEMPTING TO RECOVER DEVICE
MPCIPA1
10114 02:41:11.90 STC00075 00000090 IST1222I DATA DEVICE 0602 IS
INOPERATIVE, NAME IS MPCIPA1 325
325 00000090 IST1578I DEVICE INOP DETECTED FOR
MPCIPA1 BY ISTTSCMA CODE = 104
325 00000090 IST314I
END
10114 02:41:13.60 00000090 IOS208I CONTROL UNIT FOR (0601,02)
SUCCESSFULLY RECOVERED
10114 02:41:14.09 STC00075 00000090 IST1578I SOFT INOP DETECTED FOR
MPCIPA1 BY ISTTSCMA CODE = 102
10114 02:41:44.47 STC00067 00000090 EZZ4313I INITIALIZATION COMPLETE FOR
DEVICE MPCIPA1
>From z/VM
02:41:13 HCPSWU2830I VSWITCH SYSTEM VSWTCH3 status is
restarting.
HCPSWU2830I DTCVSW2 is VSWITCH controller for device
0608.P00.
02:41:13 HCPSWU2832E Connection 0608.P00 for VSWITCH SYSTEM VSWTCH3 is not
acti
HCPSWU2832E Device is detached from
DTCVSW2.
02:41:13 OSA 0608 DETACHED DTCVSW2 0608 BY
DTCVSW2
02:41:13 OSA 0609 DETACHED DTCVSW2 0609 BY
DTCVSW2
02:41:13 HCPSWU2830I VSWITCH SYSTEM VSWTCH1 status is
restarting.
HCPSWU2830I DTCVSW1 is VSWITCH controller for device
0604.P00.
02:41:13 OSA 060A DETACHED DTCVSW2 060A BY
DTCVSW2
02:41:13 HCPSWU2832E Connection 0604.P00 for VSWITCH SYSTEM VSWTCH1 is not
acti
HCPSWU2832E Device is detached from
DTCVSW1.
02:41:13 OSA 0604 DETACHED DTCVSW1 0604 BY
DTCVSW1
02:41:13 OSA 0605 DETACHED DTCVSW1 0605 BY
DTCVSW1
02:41:13 OSA 0606 DETACHED DTCVSW1 0606 BY DTCVSW1
--
Mark Pace
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
*************************** IMPORTANT
NOTE*****************************-- The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
********************************************************************************
--
Mark Pace
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
