Hi 

I cleared the hurdle on the XAUTOLOG AUTOLOG RACF error. I had to turn
on the VMXEVENT CLASS and do an 'rac rdef vmxevent events1' followed by
'rac ralt vmxevent events1 addmem(xautolog/noctl). The problem is I
still do not see my updates to my VSWITCH definitions after the XAUTOLOG
is complete. Is there something else I need to do to get my changes in?

Thank You,
 
Terry Martin
Lockheed Martin - Information Technology
z/OS & z/VM Systems - Performance and Tuning
Cell - 443 632-4191
Work - 410 786-0386
[EMAIL PROTECTED]

-----Original Message-----
From: Martin, Terry R. (CMS/CTR) (CTR) 
Sent: Tuesday, July 08, 2008 3:48 PM
To: 'The IBM z/VM Operating System'
Subject: RE: VSWITCH

Hi

I have my VSWITCH defines in my AUTOLOG2 and I am trying to XAUTOLOG
AUTOLOG2 to bring in my changes and I am receiving the error message in
the attachment. Anyone know what this means. It is not letting me bring
in my new VSWITCH defines.




Thank You,
 
Terry Martin
Lockheed Martin - Information Technology
z/OS & z/VM Systems - Performance and Tuning
Cell - 443 632-4191
Work - 410 786-0386
[EMAIL PROTECTED]

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Tuesday, July 08, 2008 11:59 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VSWITCH

On Tuesday, 07/08/2008 at 10:44 EDT, "Martin, Terry R. (CMS/CTR) (CTR)" 
<[EMAIL PROTECTED]> wrote:
> I am setting up VSWITCH for the first time and I am a little confused
on 
all I 
> need to get it defined. I have been doing a lot of reading but still a

little 
> confused.

This is normal.  :-)  The more you read, the more confused you will 
become.  Often, confusion about VSWITCHes comes from "knowing too much" 
about the rest of VM.

> I am running z/VM 5.3 and trying to set up a VSWITCH between this and
my 

> z/Linux guests. I am confused on just what needs to be defined in my 
TCP/IP 
> profile and in the DTCPARMS and just what definitions I need in the 
DIRECTORY 
> for the user. I have defined the CONTROLLERS and they appear to be 
active. 
> Actually these are the default controllers (DTCVSW1/2). If someone is 
willing 
> to give me call it would be much appreciated and probably would save a

lot of 
> time and emails. I would update the list on what I did to get it
working 
at the 
> end. My contact numbers are below.

I'll post here, so that others can benefit.

1. XAUTOLOG DTCVSW1 & 2.  You did that.
2. Do not change any PROFILE TCPIP anywhere.  If you have a CONTROLLER 
statement in your production PROFILE TCPIP, remove it.
3. DEFINE VSWITCH, specifying one or more available OSAs.  Those OSAs
(a) 
SHOULD NOT be shared with any other stack or LPAR, and (b) MUST all go
to 
the same LAN segment.
4. SET/MODIFY VSWITCH to authorize the Linux guests.
5. Add a NICDEF statement to each Linux user directory entry.  It is ok 
that each user reference the same virtual address.
6. Recycle the Linux guests (logoff/logon).

Whatever default gateway the Linux guests are using must be defined in
the 
physical switch.

Alan Altmark
z/VM Development
IBM Endicott

Reply via email to