You could define enough Hipersocket devices so that each Linux machine that needs a connection to z/OS can have it's own. (the preferred way, no extra routing hop required)
You could also define a hipersocket address set to the second IP stack and also to the VSwitch. But then your VM IP stack is working as a router, which is counter-productive to one of the reasons for the VSwitch (but I would guess that this is temporary).
Kinnear, Mike wrote:
I've researched the archives and redbooks. I think I've come across every combination of implementation except the one I'm trying to do. We have a number of VSWITCH LINUX instances running under one z/VM LPAR. We have a production VM TCP/IP stack that we use for 'older' VCTC connections until we get them switched over to VSWITCH. I would like to communicate from the LINUX instances on the VSWITCH with an z/OS LPAR using HIPERSOCKETS. I don't want to 'experiment' with the production TCP/IP stack, so I am configuring a second stack to do the HIPERSOCKETS links. What I've tried complains that a virtual LAN is not present, but if I'm reading the guides correctly, I shouldn't need one. How do I get the second stack to be a HIPERSOCKETS pipe for the VSWITCH network? Any help is greatly appreciated.
Mike Kinnear Systems Programmer GuideOne Insurance
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
-- Rich Smrcina VM Assist, Inc. Main: (866)569-7378 Cell: (414)491-6001 [EMAIL PROTECTED]
Catch the WAVV! http://www.wavv.org WAVV 2005 - Colorado Springs - May 20-24, 2005
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
