Sorry for the way the e-mails are coming across. I don't have direct access to
my e-mail account during the day.
I tried using VSE/ESA 2.6 and I believe had to apply VSE PTF's to get it to
recogize the OSA switch. VSE 2.3 will have some for sure if it is at all
supported.
"OSA > Vswitch/Guest LAN > TCPIP > NEWESA4 > DOSESA2 didn't work, but only for
DOSESA2. It seems Vswitch/Guest LAN could do
2 hops to NEWESA4 but not the third hop to DOSESA2. If Guest LAN required
nodes to be directly connected, then why does NEWESA4 work just fine? "
NEWESA4 works because TCPIP and NEWESA4 are all on the same level.
OSA
|
VSWITCH
|
NEWESA4 TCPIP (STLESA2 VSE) and then you added TSTESA4
Newesa4 does not go through TCPIP vm. IT is a drop/connection just like TCPIP
and the other two.
Hans
Right...eventually, I was going to have all the VSE systems as well as the
TCPIP machine, attach directly to the Guest LAN that the Vswitch is on.
However, I was trying to do "baby steps". Something I could easily back out
of. Also, I'm not sure of OSA support with TCP/IP 1.5 B running on VSE/ESA
2.3.2. My older machines use so little IP, that I was going to leave them
VCTCA to TCPIP until they die.
Origionally I had:
OSA > TCPIP > NEWESA4 > DOSESA2
which worked fine.
Then:
OSA > Vswitch/Guest LAN > TCPIP > NEWESA4 > DOSESA2 didn't work, but only for
DOSESA2. It seems Vswitch/Guest LAN could do
2 hops to NEWESA4 but not the third hop to DOSESA2. If Guest LAN required
nodes to be directly connected, then why does NEWESA4 work just fine?
Of course I agree that nodes should be directly connected. That is one of the
purposes of Guest LANs is to reduce complexity and eliminate routing overhead,
but....baby steps...
And yep, I might have to take bigger steps. In this case:
OSA > Vswitch/Guest LANs > TCPIP > NEWESA4
DOSESA2
etc.
Tom Duerbusch
THD Consulting
________________________________________________________________
Sent via the WebMail system at hmrconsultants.com
[This E-mail scanned for viruses]
