First Thanks to everyone for there inputs. Here is what I had to do to get
the basic VSWITCH setup going
In the PROFILE TCPIP file (TCPMAINT 198'D' disk) added
VSWITCH CONTROLLER ON 0C5C 0C5E
For each User connecting to the switch, I added this directory entry to the
corresponding USER entry in the USER DIRECT file ( MAINT 2CC 'C' disk)
NICDEF 0F00 TYPE QDIO DEVICES 3 LAN SYSTEM SWITCH01
In the SYSTEM CONFIG file (MAINT CF1 disk) I defined the Virtual Switch
Define VSWITCH SWITCH01 Controller * CONNECT
The real trick was to add some entries to the PROFILE EXEC of AUTOLOG1 or
OPERATOR to define what real address CP used to connect to the real
NETWORK, and who is authorized to connect to the switch. I added these
entries to the PROFILE EXEC in AUTOLOG1
ADDRESS COMMAND CP 'AUTOLOG TCPIP IAMANSVM '
'CP SLEEP 10 SEC'
ADDRESS COMMAND CP 'SET VSWITCH SWITCH01 RDEV 0C5C '
ADDRESS COMMAND CP 'SET VSWITCH SWITCH01 GRANT RHELAS3 '
ADDRESS COMMAND CP 'SET VSWITCH SWITCH01 GRANT REDHAT01 '
ADDRESS COMMAND CP 'SET VSWITCH SWITCH01 GRANT REDHAT02 '
ADDRESS COMMAND CP 'SET SIGNAL SHUTDOWN 60 '
After looking through the documentation, and everyone's help on this list I
have established a basic switched network. The DEFINE LAN command in the
SYSTEM CONFIG file may be a better route. I could define the Real Device and
GRANT authorization to the users and eliminate the entries in AUTOLOG1's
PROFILE EXEC.
Thanks again to all the helpers out there.
Larry Davis
-----Original Message-----
From: Dennis Musselwhite [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 13, 2004 22:28 PM
To: [EMAIL PROTECTED]
Subject: Re: VSWITCH network
Hi,
If you were trying to test connectivity between your Linux guest and the
outside world then you would need a controller and an interface (a set of
three I/O devices) on a real OSA Express in QDIO mode. Based on the first
few lines from your Query VSWITCH response:
VSWITCH SYSTEM REDHAT Type: VSWITCH Active: 2 MAXCONN: INFINITE
PERSISTENT RESTRICTED NONROUTER MFS: 8192 ACCOUNTING: OFF
State: Disconnected - operator
CONTROLLER: * IPTIMEOUT: 5 QUEUESTORAGE: 8
PORTNAME: REDHAT01 RDEV: NONE
(1) State: Disconnected - operator (the vswitch needs operator
intervention).
(2) CONTROLLER: * (this is good because you are not restricting the vswitch
to one specific controller).
(3) PORTNAME: REDHAT01 (this might be ok... it has to match the portname
used by others on this OSA card).
(4) RDEV: NONE (this is a problem... you need to DEFINE VSWITCH or SET
VSWITCH with an RDEV address).
Let's assume you have an OSA Express in QDIO mode and it presents real I/O
device addresses 2400-243F on your LPAR. You will need to pick a set of
three devices (e.g. 2408-240A) to associate with this VSWITCH. You will
also need to coordinate a portname with anybody else using the same OSA
card. The portname is up to eight characters (UPPERCASE). If you intend to
use this VSWITCH on a regular basis, you should put the DEFINE VSWITCH
statement in SYSTEM CONFIG:
DEFINE VSWITCH REDHAT RDEV 2408 PORTNAME REDHAT01
OK... That binds a real OSA interface to your VSWITCH, but you also need a
z/VM TCP/IP stack user acting as controller. The controller manages the
connection on behalf of the VSWITCH, but does NOT handle the data. You will
need at least one TCPIP user with permission to connect to the *VSWITCH
system service (add an IUCV *VSWITCH statement in the USER DIRECT file).
The PROFILE TCPIP file in the controller needs a "VSWITCH CONTROLLER ON"
statement.
Let's assume you plan to use TCPIP (the default userid for the VM stack) as
your controller. This is OK and it does not affect your existing use of
that stack.
Here are some hints for avoiding common problems in this area:
(1) DO NOT add DEVICE or LINK statements for the VSWITCH connection to your
PROFILE TCPIP. Leave those addresses (like 2408-240A in the example above)
free for use by the controller logic.
(2) DO NOT attach/dedicate the OSA devices you selected for the VSWITCH to
your stack. Let CP do that automatically. If (for example) you attached
real devices 2408-240A to TCPIP, you would block CP from activating your
VSWITCH because CP would assume you have decided to use these devices for
some other purpose.
(3) IF you want your TCPIP user to have connectivity via the VSWITCH, you
should define a virtual NIC and couple it to the VSWITCH. Please do NOT use
the same virtual address (e.g. 2408) on the DEFINE NIC (see hints 1 and 2).
And remember to grant access to TCPIP.
(4) DO make sure you define your VSWITCH and GRANT access to the appropriate
VM users before those users start logging on and trying to COUPLE.
Regards,
Dennis
----------------------------------------------------------------
Dennis Musselwhite ([EMAIL PROTECTED]) z/VM Development -- CP Network
Simulation -- IBM Endicott NY
----------------------------------------------------------------------
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
