Our VM system is still connected to the LAN
via an ESCON attached 2216.
++
|| 10.0.0.6
| VM |[2216](LAN)
|| 10.1.5.110.0.x.x
++
10.1.5.2
VM - 10.1.5.2
2216 VM side - 10.1.5.1
2216 LAN side - 10.0.0.6
LAN - 10.0.x.x
VM default gateway:
On Tuesday, 04/17/2007 at 01:40 GMT, Dusha, Cecelia CIV WHS/ITMD
[EMAIL PROTECTED] wrote:
My network knowledge is almost non-existent...
When it comes to switch mangagement, that is for your network
admins/technicians to deal with. If the OSAs are shared, you will want to
define the VSWITCH
(I am sending this a second time
because I just noticed the typo in the subject.
I really wouldn't want the whole thread
to look like that...)
Our VM system is still connected to the LAN
via an ESCON attached 2216.
++
|| 10.0.0.6
| VM |[2216](LAN)
|| 10.1.5.1
Thanks, Mark. That helped a lot. (I was looking in the wrong manual before.)
I *think* I have gotten past this.
Now, on to the next problem.
Thanks,
Jon
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Mark
Pace
Sent: Tuesday, April 17,
I have z/VM 5.1. The NOGVRP parameter is available in z/VM 5.2...
Cecelia Dusha
-Original Message-
From: Alan Altmark [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 9:22 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VSWITCHes, TCPIP and 802.1Q
On Tuesday, 04/17/2007 at 01:40
From developer Tami Zebrowski-Darrow
From MAINT user id you need to do the following for the component that you
are servicing. It assumes that you have the prereq PTFs in a
SERVLINK envelope file on MAINTs 500 disk. If you have tape then do not
use ENV option on VMFREC. Also for the
