Hi all,
I have a vswitch problem (like it says in the subject).
I started with this:

   LAN----OSA----VM---VSE

Where the VM acts as virtual router to the VSE,
and defines the link on the OSA as primary router.

Then I changed that to this:

   LAN---OSA---VSWITCH---VM---VSE

where the vswitch is now PRIROUTER, and
VM couples via VNIC. No other changes I can
think of.

The VSE has a VCTC connecting it to VM TCPIP,
as its default gateway, and the LAN considers VM
as the gateway to the VSE.

Here are the profile statements I changed:
OLD method, NO vswitch:
; LINK THROUGH QDIO OSA B2 TO MAIN 10.0.0.0/16 LAN
DEVICE OSA-B2   OSD       B200 PORTNAME OSAQDB2 PRIROUTER 
LINK LAN10    QDIOETHERNET  OSA-B2
START OSA-B2

NEW method, WITH vswitch:

; LINK THROUGH QDIO NIC F00 TO VSW1 - TO MAIN 10.0.0.0/16 LAN
DEVICE NIC-F00  OSD        F00     PORTNAME VSWNIC1 
LINK LAN10    QDIOETHERNET  NIC-F00
START NIC-F00

My assumption was that this would be a piece of cake, 
unfortunately it simply doesn't work.

Not only can the LAN no longer reach the VSE behind the VM, 
I can't even get a ping response from VM itself.

The vswitch itself is defined like this:
'CP DEFINE VSWITCH VSW1 RDEV B20D B30D PRIROUTER' 
'CP SET    VSWITCH VSW1 GRANT TCPIP'

The stack is from z/VM 4.3, but the CP component is
4.4, as are the vswitch controller virtual machines.

Thanks,
Shimon

-- 
**********************************************************************
**
Shimon Lebowitz                mailto:[EMAIL PROTECTED]
VM System Programmer           .
Israel Police National HQ.     
Jerusalem, Israel              phone: +972 2 542-9877  fax: 542-9308
**********************************************************************
**

Reply via email to