To cross the partition border from VM LPAR to z/OS LPAR you can use
hipersockets, which you are doing, or
OSA devices (they can be shared), or real CTCAs - different types of chpids can
be configured as CTCAs - and
you can get a bunch of CTCAs from one channel. If you are running into
hipersocket limitations consider sharing your
FDR traffic with your other traffic.
NICDEFs and SPECIAL statements refer to using guest lans - a completely virtual
network - the lan is virtual and so are the adapters. Setup via CP commands
and/or directory statements. TCPIP is TCPIP is TCPIP - doesn't know or care
that the
network is virtual - Every effort should be made to connect virtual machines
within one LPAR via guest lans. It's not
virtual IP addressing - that's another topic.
Hope this helps - send a picture of your network offline if you like.
David
________________________________
From: Linux on 390 Port on behalf of Ranga Nathan
Sent: Wed 12/1/2004 9:07 PM
To: [EMAIL PROTECTED]
Subject: Re: 127 device limitation for hipersockets
__________________________________________
Ranga Nathan / CSG
Systems Programmer - Specialist; Technical Services;
BAX Global Inc. Irvine-California
Tel: 714-442-7591 Fax: 714-442-2840
Adam Thornton <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
12/01/2004 05:16 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: 127 device limitation for hipersockets
On Dec 1, 2004, at 7:09 PM, Ranga Nathan wrote:
> currently we have two hipersockets defined per guest, one with 64k mtu
> block size and one with 8k mtu block size. We use the one smaller mtu
> size
> hipersocket to talk among the other guests from guest to guest and to
> do
> authentication to a USS LDAP server under MVS. The 64k mtu block size
> hipersocket is being used for backups through fdr upstream on the mvs
> side
> and notice a nice improvement on speed for backups. The problem we are
> running into is the 127 device limitation.
> I dont recall this limitation. Is this a Hipersockets limitation? Do
> you
> mean 127 x 4 addresses?
Um, you mean you're using a real Hipersockets dedicated per guest?
Don't do that.
Define them as SPECIALS or with NICDEF and virtualize 'em.
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.
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
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
