Prior to bring up vswitch, my network had routes such as:
|
|
OSA
|
|
vm TCP/IP
|
_____________________
| |
(NEWESA4 VSE) (STLESA2 VSE)
|
____________________________
| | | |
| | | |
DOSESA2 GEAC4 TSTESA4 TSTESA2
VSE VSE VSE VSE
The first phase of bringing up Vswitch, is just to have it control the
hardware. So the network now looks like:
|
|
OSA
|
|
Vswitch
|
|
vm TCP/IP
|
________________________
| |
(NEWESA4 VSE) (STLESA2 VSE)
|
____________________________
| | | |
| | | |
DOSESA2 GEAC4 TSTESA4 TSTESA2
VSE VSE VSE VSE
At this point, vswitch has the OSA hardware, and only has a single node
on it's guest lan (TCPIP, the VM stack).
All seemed to be fine. except....
No one on the LAN can get to the DOSESA2, GEAC4, etc machines. But
they can get to the STLESA2 machine. So, I took the TSTESA4 machine and
connected directly to TCPIP, instead of being routed thru the NEWESA4
machine. And now it works.
It seems to be a routing problem, but I don't understand why.
If a LAN user can be routed as:
LAN > TCPIP > NEWESA4 > TSTESA4
what difference is there when Vswitch in put in the mix as:
LAN > Vswitch > TCPIP > NEWESA4 > TSTESA4
As NEWESA4 is directly connected to TCPIP, no one has problems
connecting to it.
I would like to be able to understand just what "networking" changes
went into effect with the addition of vswitch.
I can ping from TCPIP to all the machines, which means I have active
connections. It is only when I added vswitch to the mix, that machines
that were 2 hops over from TCPIP, had problems communicating.
Thanks for any insight.
Tom Duerbusch
THD Consulting
