On Dec 1, 2004, at 8:07 PM, Ranga Nathan wrote:
I am losing you. For each Linux guest we had to allocate distinct addresses and aliased them like so, for hipersockets to work: 'ATT EC08 * EC00 ' 'ATT EC09 * EC01 ' 'ATT EC0A * EC02 ' 'ATT ED08 * ED00 ' 'ATT ED09 * ED01 ' 'ATT ED0A * ED02 '
Thus for each guest we needed 8 addresses plus 4 for z/VM itself. The nicdef in DTCPARMS seems to be an appendix. There are big gaps in my understanding. Help appreciated.
Yeah: create a guest LAN under VM (you're at z/VM 4.3 or later, aren't you? I seem to recall that you said 4.4); call that GLAN1 owned by system. As MAINT, 'CP DEF LAN GLAN1 OWNER SYSTEM TYPE HIPERS' (my syntax may be wrong; check HELP CP DEFINE LAN to find out). Put this in SYSTEM CONFIG on CF1 to make it persist across IPLs.
For TCPIP and each of your Linux guests, either put a SPECIAL statement (or a NICDEF statement) in the directory entry giving it a virtual QDIO device, or define it in PROFILE DTCPARMS for TCPIP and PROFILE EXEC for the Linux guests (presuming they IPL CMS first and then IPL the Linux DASD after doing any CMS setup). Do that like:
'CP DEF NIC EC08 TYPE HIPER' 'CP COUPLE EC08 SYSTEM GLAN1'
Then you need to also give TCPIP an address on the (real) Hipersocket, tell all the Linux guests to route through TCPIP's address on the Guest LAN, tell z/OS to route all the Linux guests through TCPIP's address on the Hipersocket, and everything will be peachy (you could also use MPROUTE, in conjunction either with Zebra/Quagga or static routing on the Linux guests, if that fits your network infrastructure better). Yeah, there will be more load on TCPIP, and all Linux traffic will need to hop through it, but on the other hand, you won't have to burn up real Hipersockets on your Linux guests.
Adam
---------------------------------------------------------------------- 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
