Re: How Do You Configure a 2nd VSWITCH?

[Heinz-Josef Glaser]

Dear George,

I see in your 'Query OSA' that the address 9005 is now attached to DTCVSW2.
If you need a second VSWITCH, you must use a free OSA-Address (maybe 9007
is free). You can dynamically define your VSWITCH (e.g. in Userid Maint)
and attatch him to your Linux-System, before you put this in your System
Config. Best is, you make your definitions in the profile exec of your
VM-User Autolog1 instead of System Config.

Mit freundlichen Grüssen / Best regards
Heinz-Josef Glaser
Systemspezialist z/OS, z/VM, z/VSE
Global Technology Services
GE Server Services SPL8 Manag Serv Sys Z
IBM Deutschland
Rathausstrasse 7
09111 Chemnitz
Tel.: +49 371 6978 2876
Fax: +49 371 6978 2280
Mobile: +49 172 668 3018
E-Mail: hjgla...@de.ibm.com

IBM Deutschland Infrastructure Technology Services GmbH
Geschäftsführung: Ulrike Hetzel
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 727973


   
  From:   George Henke/NYLIC 
   
  To: IBMVM@LISTSERV.UARK.EDU  
   
  Date:   09.09.10 15:42   
   
  Subject:How Do You Configure a 2nd VSWITCH?  
   
  Sent by:The IBM z/VM Operating System   
   






We currently have a functioning VSWITCH, LNXVSW1, related to a VSWITCH
controller, DTCVSW2 at OSA 9004.

Q VSWITCH

09:14:01 VSWITCH SYSTEM LNXVSW1  Type: VSWITCH Connected: 3Maxconn:
INFINITE
09:14:01   PERSISTENT  RESTRICTEDNONROUTER Accounting:
OFF
09:14:01   VLAN Unaware

09:14:01   MAC address: 02-00-00-00-00-01

09:14:01   State: Ready

09:14:01   IPTimeout: 5 QueueStorage: 8

09:14:01   RDEV: 9004.P00 VDEV: 9004 Controller: DTCVSW2

We are trying to understand how LNXVSW1 is related to the VSWITCH
controller, DTCVSW2 so that we can configure a second VSWITCH, LNXVSW2, for
redundancy and improved throughput.

We believe it is related through our DEFINE in SYSTEM CONFIG:

/* vswitch definitions*/
define vswitch lnxvsw1 portname lnxvsw1 rdev 9004
/* end of vswitch definition */

and our subsequent OSA ATTACH of 9004 to DTCVSW2:


Q OSA

09:14:46 OSA  9000 ATTACHED TO TCPIP9000 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9001 ATTACHED TO TCPIP9001 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9002 ATTACHED TO TCPIP9002 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9004 ATTACHED TO DTCVSW2  9004 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9005 ATTACHED TO DTCVSW2  9005 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  9006 ATTACHED TO DTCVSW2  9006 DEVTYPE OSA CHPID D4
OSD
09:14:46 OSA  903F ATTACHED TO SY92TEST 902F DEVTYPE OSA CHPID 0B
OSD
09:14:46 OSA  907F ATTACHED TO SY91TEST 906F DEVTYPE OSA CHPID 0F
OSD
09:14:46 OSA  90D0 ATTACHED TO VTAM 90D0 DEVTYPE OSA CHPID D1
OSE
09:14:46 OSA  9100 ATTACHED TO TCPIP9100 DEVTYPE OSA CHPID D5
OSD
09:14:46 OSA  9101 ATTACHED TO TCPIP9101 DEVTYPE OSA CHPID D5
OSD

Is this correct?

If so, then to configure a second VSWITCH, we should be able to DEFINE a
second VSWITCH, LNXVSW2, in SYSTEM CONFIG as 9005 and ATTACH the OSA 9005
TO DTCVSW1.

Is this correct?

CAVMEN Meeting on Thursday, October 28, 2010

[Chicago Area VM (and Linux) Enthusiasts]

The fourth quarter meeting of the Chicago Area VM (and Linux) 
Enthusiasts will be held on Thursday, October 28, 2010.


We are scheduled to meet in room M2 off the cafeteria, it is right 
next to room M3 where we frequently meet.


NOTE:  We have a very full agenda for this meeting, and we will be 
starting promptly at 9:00AM.


If you are planning to attend the IBM System z Technical University 
in Boston, and have not yet enrolled, CAVMEN members are eligible for 
a 10% discount.  See the CAVMEN home page for details: 
http://cavmen.home.comcast.net/~cavmen/index.html



--

Meeting Location:

This quarter's meeting will be held at the Hewitt Associates 'East 
Campus' located at 100 Half Day Road, in Lincolnshire, IL. We will 
meet in Conference Room 100-M2, in Building 100, just off the cafeteria.


If you have not attended a meeting at this location before, or you 
are not familiar with the area, 
Click here for 
additional information on directions, maps, lodging and dining.



--

Attendance:

We would like to request a count of expected attendees by the Monday 
before the meeting, so that we may plan appropriately for arranging 
the facilities, and for refreshments and lunch, should one of the 
vendors wish to provide them. If you are planning to attend, PLEASE 
send an E-Mail by that date to 
cav...@comcast.net with a subject line of 
"Meeting Attendance".


This is meant to be a facilities planning aid and should not be 
interpreted as a registration requirement. If you suddenly become 
available at the last minute, please feel free to attend even if you 
have not responded.


Thank you in advance for your cooperation in this matter.


--

Meeting Agenda:

9:00 AM z/VM Platform Update

This session will provide you with the latest & greatest information 
about z/VM. We will discuss the recently announced updates to z/VM 
V5.4 and z/VM 6.1, including support for the IBM zEnterprise System, 
as well as the Statements of Direction for Single-System Image and 
Live Guest Relocation.


The speaker will be John Franciscovich of the IBM Corporation.

10:05 AMCoffee Break

10:15 AMz/VM Single System Image and Guest Mobility Preview

IBM has issued a Statement of Direction describing its intent to 
permit multiple z/VM Systems to collaborate in a Single System Image 
cluster, and to allow a running guest to be moved from one member of 
a cluster to another with Live Guest Relocation. This presentation 
provides a preview of these enhancements.


The speaker will be John Franciscovich of the IBM Corporation.

11:30 PMLunch Break

12:30 PMAdministration and Vendor Announcements

12:45 PMLinux on z Update

The speaker will present a brief update of recent developments in the 
Linux under z/VM area.


The speaker will be Paul Augustyniak of the IBM Corporation.

1:00 PM CSL-WAVE - Linux / z/VM Virtual Server Management

CSL-WAVE, is very unique in the sense that it provides complete 
freedom to our users to operate z/VM-based virtual server farms while 
eliminating the need for the Linux sys-admins to develop a z/VM skill 
set. CSL-WAVE abstracts the z/VM resources and knowhow via its 
intuitive GUI and architecture to the point that CSL-WAVE users do 
not need to resort to the z/VM system programming dept for help for 
any of their day-to-day infrastructure management nor for even more 
advanced activities such as storage or network management. All within 
the scope and permissions that are dictated by the site-level 
CSL-WAVE administration function (Usually the z/VM system programmer).


The product handles all aspects of the virtual server farm: Virtual 
server management, provisioning, storage managed at the server and 
z/VM instance level, Network (GLANs and VSwitches), even script 
management across the virtual server farm.


The speaker will be Sharon Chen, Founder and CEO of CSL-International.

2:15 PM Coffee Break

2:30 PM What's new from IBM for automating operations on z/VM 
and Linux on System z


As the Linux on System z environment continues to grow, the need for 
software and solutions to manage this environment also grows. IBM 
continues to enhance a set of software solutions to assist customers 
with automated operations, system management, and storage management. 
This session will focus on automated operations and what's new in 
Operations Manager for z/VM V1.4, announced and available in 
September 2010. Live demos will be included.


The speaker will be Tracy Dean of the IBM Corporation.

3:30 PM Coffee Break and Prize Drawing

3:45 PM What's new from IBM for tape management on z/VM

As the Linux on System z environment continues to grow, the need for 
software and solutions to manage this environment also grows. IBM 
continues to enhance a set of software solutions to assist customers 
with automated ope

Re: How Do You Configure a 2nd VSWITCH?

[Alan Altmark]

On Thursday, 09/09/2010 at 10:30 EDT, George Henke/NYLIC 
 wrote:
> Are the 3 OSA addresses below (9004, 9005, 9006) used for 1 connection 
> (Read/Write/ Data)? 

I'm not sure what you're driving at, George.  Every OSA requires one or 
more data transfer connections per Read/Write control pair, and the 
VSWITCH uses only one data transfer connection per OSA.

The number of data connections to the physical OSA has nothing to do with 
the number of virtual NICs or the number of virtual data connections used 
by guests.  E.g. a z/OS guest with DEFINE NIC DEVICES 10, will have a r/w 
control pair and 8 IP stacks, each using one data connection.  All of that 
traffic will travel over the single physical data connection.

Alan Altmark
z/VM Development
IBM Endicott

Re: Trying to build CMSBAM segment

[Alain Benveniste]

Hi,

I just got the same problem today. Never had before...
I am in zVM530 rsu 1001 and I would like to know if a ptf was brought in 
a rsu ?

Alain

Re: How Do You Configure a 2nd VSWITCH?

[George Henke/NYLIC]

ty

Also, an academic question:

Are the 3 OSA addresses below (9004, 9005, 9006) used for 1 connection 
(Read/Write/ Data)?

Here is our LNX Config file data from LNXMAINT's 191:

From RHEL53 VLINUX2 on LNXMAINT’s 191:
HOSTNAME="vlinux2.newyorklife.com" 
DASD="100-101,200" 
NETTYPE="qeth" 
IPADDR="172.28.3.136" 
SUBCHANNELS="0.0.d000,0.0.d001,0.0.d002" 
PORTNAME="LNXVSW1" 
BROADCAST="172.28.3.255" 
NETWORK="172.28.3.0" 
NETMASK="255.255.255.192" 
SEARCHDNS="newyorklife.com" 
GATEWAY="172.28.3.129" 
DNS="172.28.100.100" 
MTU="1500" 



Alan Altmark  
Sent by: The IBM z/VM Operating System 
09/09/2010 10:16 AM
Please respond to
The IBM z/VM Operating System 


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: How Do You Configure a 2nd VSWITCH?






On Thursday, 09/09/2010 at 09:42 EDT, George Henke/NYLIC 
 wrote:
> We currently have a functioning VSWITCH, LNXVSW1, related to a VSWITCH 
> controller, DTCVSW2 at OSA 9004. 
> 
> We are trying to understand how LNXVSW1 is related to the VSWITCH 
controller, 
> DTCVSW2 so that we can configure a second VSWITCH, LNXVSW2, for 
redundancy and 
> improved throughput. 
> 
> We believe it is related through our DEFINE in SYSTEM CONFIG: 
> 
> /* vswitch definitions*/ 
> define vswitch lnxvsw1 portname lnxvsw1 rdev 9004 
> /* end of vswitch definition */ 

Get rid of the PORTNAME LNXVSW1.  (Another PORTNAME bites the dust!)
 
> and our subsequent OSA ATTACH of 9004 to DTCVSW2: 
>
> Is this correct? 

No.  You don't ATTACH or DETACH anything; the system handles it.  Just 
DEFINE VSWITCH.

> If so, then to configure a second VSWITCH, we should be able to DEFINE a 

second 
> VSWITCH, LNXVSW2, in SYSTEM CONFIG as 9005 and ATTACH the OSA 9005 TO 
DTCVSW1.
> 
> Is this correct? 

No.  Just defines your second (third, fourth, ...) VSWITCH and don't worry 

about controller selection.  The only time to worry about the controller 
is when the Support Center asks you to do it.

Alan Altmark
z/VM Development
IBM Endicott

Re: DEVICES Statement in SYSTEM CONFIG

[Vic Cross]

Marcy Cortes wrote:

Yep, just don't forget your consoles, osa's, fcp's,   ctc's,  tapes.
"q all all" might be useful to do first.

Lesson learned: if you're using EDEVices for your system volumes, 
*those* have to be in your Online_At_IPL list as well -- not just the 
FCPs they're attached through.  Can't quite remember how I fixed that, 
but "540RES VOLUME NOT MOUNTED" (or text to that effect) and a disabled 
wait at IPL was not much fun...


They do show up in the output of "q all all", which is good...  but 
don't be tempted to leave them out of your online list because they're 
"not real"!  :-)


Cheerio,
Vic Cross

Re: How Do You Configure a 2nd VSWITCH?

[Alan Altmark]

On Thursday, 09/09/2010 at 09:42 EDT, George Henke/NYLIC 
 wrote:
> We currently have a functioning VSWITCH, LNXVSW1, related to a VSWITCH 
> controller, DTCVSW2 at OSA 9004.  
> 
> We are trying to understand how LNXVSW1 is related to the VSWITCH 
controller, 
> DTCVSW2 so that we can configure a second VSWITCH, LNXVSW2, for 
redundancy and 
> improved throughput. 
> 
> We believe it is related through our DEFINE in SYSTEM CONFIG: 
> 
> /* vswitch definitions*/ 
> define vswitch lnxvsw1 portname lnxvsw1 rdev 9004   
> /* end of vswitch definition */ 

Get rid of the PORTNAME LNXVSW1.  (Another PORTNAME bites the dust!)
 
> and our subsequent OSA ATTACH of 9004 to DTCVSW2: 
>
> Is this correct? 

No.  You don't ATTACH or DETACH anything; the system handles it.  Just 
DEFINE VSWITCH.

> If so, then to configure a second VSWITCH, we should be able to DEFINE a 
second 
> VSWITCH, LNXVSW2, in SYSTEM CONFIG as 9005 and ATTACH the OSA 9005 TO 
DTCVSW1.
> 
> Is this correct? 

No.  Just defines your second (third, fourth, ...) VSWITCH and don't worry 
about controller selection.  The only time to worry about the controller 
is when the Support Center asks you to do it.

Alan Altmark
z/VM Development
IBM Endicott

Re: How Do You Configure a 2nd VSWITCH?

[Rich Smrcina]

 If you have supporting hardware, you can potentially get better throughput with link 
aggregation.


But, using your method just define the new Vswitch.  You do not need to 'attach' 
anything, CP handles the device mechanics.  Depending upon how much traffic you are 
pumping through the OSA on D4 you may want to pick a different OSA CHPID.  These are 
some of the things that should be determined with monitoring.


On 09/09/2010 08:42 AM, George Henke/NYLIC wrote:


We currently have a functioning VSWITCH, LNXVSW1, related to a VSWITCH controller, 
DTCVSW2 at OSA 9004.


Q VSWITCH
09:14:01 VSWITCH SYSTEM LNXVSW1  Type: VSWITCH Connected: 3Maxconn: INFINITE
09:14:01   PERSISTENT  RESTRICTEDNONROUTER Accounting: OFF
09:14:01   VLAN Unaware
09:14:01   MAC address: 02-00-00-00-00-01
09:14:01   State: Ready
09:14:01   IPTimeout: 5 QueueStorage: 8
09:14:01   RDEV: 9004.P00 VDEV: 9004 Controller: DTCVSW2

We are trying to understand how LNXVSW1 is related to the VSWITCH controller, DTCVSW2 
so that we can configure a second VSWITCH, LNXVSW2, for redundancy and improved 
throughput.


We believe it is related through our DEFINE in SYSTEM CONFIG:

/* vswitch definitions*/
define vswitch lnxvsw1 portname lnxvsw1 rdev 9004
/* end of vswitch definition */

and our subsequent OSA ATTACH of 9004 to DTCVSW2:


Q OSA
09:14:46 OSA  9000 ATTACHED TO TCPIP9000 DEVTYPE OSA CHPID D4 OSD
09:14:46 OSA  9001 ATTACHED TO TCPIP9001 DEVTYPE OSA CHPID D4 OSD
09:14:46 OSA  9002 ATTACHED TO TCPIP9002 DEVTYPE OSA CHPID D4 OSD
09:14:46 OSA  9004 ATTACHED TO DTCVSW2  9004 DEVTYPE OSA CHPID D4 OSD
09:14:46 OSA  9005 ATTACHED TO DTCVSW2  9005 DEVTYPE OSA CHPID D4 OSD
09:14:46 OSA  9006 ATTACHED TO DTCVSW2  9006 DEVTYPE OSA CHPID D4 OSD
09:14:46 OSA  903F ATTACHED TO SY92TEST 902F DEVTYPE OSA CHPID 0B OSD
09:14:46 OSA  907F ATTACHED TO SY91TEST 906F DEVTYPE OSA CHPID 0F OSD
09:14:46 OSA  90D0 ATTACHED TO VTAM 90D0 DEVTYPE OSA CHPID D1 OSE
09:14:46 OSA  9100 ATTACHED TO TCPIP9100 DEVTYPE OSA CHPID D5 OSD
09:14:46 OSA  9101 ATTACHED TO TCPIP9101 DEVTYPE OSA CHPID D5 OSD

Is this correct?

If so, then to configure a second VSWITCH, we should be able to DEFINE a second 
VSWITCH, LNXVSW2, in SYSTEM CONFIG as 9005 and ATTACH the OSA 9005 TO DTCVSW1.


Is this correct?







--
Rich Smrcina
Velocity Software, Inc.
Mobile: 414-491-6001
Office: 262-392-3717
http://www.velocitysoftware.com

Catch the WAVV! http://www.wavv.org
WAVV 2011 - April 15-19, 2011 Colorado Springs, CO

How Do You Configure a 2nd VSWITCH?

[George Henke/NYLIC]

We currently have a functioning VSWITCH, LNXVSW1, related to a VSWITCH 
controller, DTCVSW2 at OSA 9004. 

Q VSWITCH  
09:14:01 VSWITCH SYSTEM LNXVSW1  Type: VSWITCH Connected: 3Maxconn: 
INFINITE
09:14:01   PERSISTENT  RESTRICTEDNONROUTER Accounting: 
OFF 
09:14:01   VLAN Unaware  
09:14:01   MAC address: 02-00-00-00-00-01  
09:14:01   State: Ready  
09:14:01   IPTimeout: 5 QueueStorage: 8  
09:14:01   RDEV: 9004.P00 VDEV: 9004 Controller: DTCVSW2

We are trying to understand how LNXVSW1 is related to the VSWITCH 
controller, DTCVSW2 so that we can configure a second VSWITCH, LNXVSW2, 
for redundancy and improved throughput.

We believe it is related through our DEFINE in SYSTEM CONFIG:

/* vswitch definitions*/ 
define vswitch lnxvsw1 portname lnxvsw1 rdev 9004 
/* end of vswitch definition */

and our subsequent OSA ATTACH of 9004 to DTCVSW2:


Q OSA  
09:14:46 OSA  9000 ATTACHED TO TCPIP9000 DEVTYPE OSA CHPID D4 
OSD
09:14:46 OSA  9001 ATTACHED TO TCPIP9001 DEVTYPE OSA CHPID D4 
OSD
09:14:46 OSA  9002 ATTACHED TO TCPIP9002 DEVTYPE OSA CHPID D4 
OSD
09:14:46 OSA  9004 ATTACHED TO DTCVSW2  9004 DEVTYPE OSA CHPID D4 
OSD
09:14:46 OSA  9005 ATTACHED TO DTCVSW2  9005 DEVTYPE OSA CHPID D4 
OSD
09:14:46 OSA  9006 ATTACHED TO DTCVSW2  9006 DEVTYPE OSA CHPID D4 
OSD
09:14:46 OSA  903F ATTACHED TO SY92TEST 902F DEVTYPE OSA CHPID 0B 
OSD
09:14:46 OSA  907F ATTACHED TO SY91TEST 906F DEVTYPE OSA CHPID 0F 
OSD
09:14:46 OSA  90D0 ATTACHED TO VTAM 90D0 DEVTYPE OSA CHPID D1 
OSE
09:14:46 OSA  9100 ATTACHED TO TCPIP9100 DEVTYPE OSA CHPID D5 
OSD
09:14:46 OSA  9101 ATTACHED TO TCPIP9101 DEVTYPE OSA CHPID D5 
OSD

Is this correct?

If so, then to configure a second VSWITCH, we should be able to DEFINE a 
second VSWITCH, LNXVSW2, in SYSTEM CONFIG as 9005 and ATTACH the OSA 9005 
TO DTCVSW1.

Is this correct?




 

Re: PROP RTABLE and HCPCRC8082I

[Frank M. Ramaekers]

Agreed.Thanks all for your input.

 
Frank M. Ramaekers Jr.
 
 

-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Rob van der Heij
Sent: Wednesday, September 08, 2010 4:29 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: PROP RTABLE and HCPCRC8082I

On Wed, Sep 8, 2010 at 10:59 PM, Tom Huegel  wrote:
> But will this help Frank get started?

I would think so. I took the effort of actually coding the RTABLE and
showed that it works, and I pointed out the difference with his RTABLE
(that his original post wanted the full 80 chars to consist only of
that message)

The discussion on whether that was obvious from the documentation is
probably less interesting.

| Rob

_
This message contains information which is privileged and confidential and is 
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any 
review, disclosure,
copying, distribution, or use of the contents of this message is strictly 
prohibited. If you have
received this in error, please destroy it immediately and notify us at 
privacy...@ailife.com.