Alan, We only have VM440. We have 14 MVS & 1 VM as guests for a HypVM. We want to be able to connect to VM 1st lvl for maintenance and to MVS and VM 2nd lvl full IP. We used CTC when we had a 7060-h70 with a card ethernet and we used 15 cards like this : DEVICE CTCSVZ1 CTC 103A LINK LNKSVZ1 CTC 1 CTCSVZ1
15 IP addresses are coded in gateway Each directory had their SPECIAL xxx CTC cards also coded. In the dtcparms we had 15 vctc defined too. It worked fine. Now that we have a z800 with OSA card, could we maintain the same config with the CTC. I can't attach the 3 OSA subchannels to our MVS since they are in use by VM TCIP 1st lvl. Hope I'm clear. Alain Le 14/04/07 22:33, « Alan Altmark » <[EMAIL PROTECTED]> a écrit : > On Saturday, 04/14/2007 at 07:35 EST, Alain Benveniste > <[EMAIL PROTECTED]> wrote: >> Our MVS lpar in prod is configured like this : >> >> PROFILE TCPIP : >> DEVICE OSA05P MPCIPA NONROUTER >> LINK SVZ1L5 IPAQGNET OSA05P >> >> MVS has 3 OSA devices. >> >> Our VM for D/R is configured like this : >> >> PROFILE TCPIP : >> DEVICE OSA82P OSD A200 >> LINK OSA82L QDIOETHERNET OSA82P >> >> VM has 3 OSA devices >> >> Everything works well. >> >> The goal is to be able to connect to our MVS in IP in D/R when it is a > guest >> of the VM above. >> >> Here are the questions : >> >> - Are we obliged to have 3 CTC devices known in MVS to be able to code >> DEVICE & LINK as CTC in the VM profile tcpip ? >> - Can?t we use the 3 OSA devices known in prod ? >> - What should be changed in the MVS IP profile ? >> - I saw we can code a SPECIAL xxx QDIO in directories. Is it what we > have to >> use ? > > I don't understand. What purpose does the CTC provide? If VM and MVS > have OSAs, they are both connected to the network. If MVS is a guest, > just attach 3 OSA subchannels to the MVS guest at the address MVS wants > them (from the OSA05P TRLE entry). No changes to the MVS IP config are > required. > > If you want to use a VSWITCH rather than dedicated OSA subchannels for > MVS, use NICDEF (not SPECIAL, please) to define virtual OSA adapters and > couple them a previously-defined VSWITCH. Do not try to connect MVS to a > Guest LAN - this will entail reconfiguring MVS. > > You don't mention your configuration limitations at the DR site, so I > assumed that (a) it's z/VM 5.2 and (b) a VSWITCH is suitable. > > Alan Altmark > z/VM Development > IBM Endicott >
