I'm sure that Support Line has already asked, but do you have AnyNet
definitions in your host tables? Something like
SYSTEMA.APPN.SNA.IBM.COM
These will need to point to the virtual LAN addresses on all sides.
Before AnyNet will work correctly you need to be able to ping
SYSTEMA.APPN.SNA.IBM.COM and SYSTEMA and see the response from the
correct IP address. On the other side you need to be able to ping both
SYSTEMB.APPN.SNA.IBM.COM and SYSTEMB
With a STRPASTHR I'm able to qualify the route by using a 2nd parm
(LCLLOCNAME)
If you do a WRKCFGL what do you see in QAPPNLCL?
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest
-----Original Message-----
From: Hart, Doug - EI [mailto:Doug.Hart@xxxxxxx]
Sent: Wednesday, June 11, 2008 9:55 AM
To: Midrange Systems Technical Discussion
Subject: AnyNet Routing Problem
We have had AnyNet configured over our wired network connecting on
several of our systems for years. Those systems (v5r3) are now
partitions on the same box. Now I configured new setups to have AnyNet
run over the LPAR Virtual LAN (VLAN). I am having no problem with new
partitions that never had the old wired setups configured, but the old
ones do not work. I have been working with IBM Support Line and traces
show that the routing is getting "lost". It seems that the send goes
out correctly but the return "sees" the old network and gets "confused".
With a STRPASTHR I'm able to qualify the route by using a 2nd parm
(LCLLOCNAME) but I want to use the SAVRSTLIB and SAVRSTOBJ commands and
they don't have parms to qualify the routing.
Has anyone been able to get a VLAN to work with the SAVRST... commands
after already having a wired AnyNet configured to the same LPAR?
--
Douglas Hart
midrange.com
