Dave,
I'm new to this stuff- but hope this helps.

Sample IOCP(why stop at 5 devices):

         CNTLUNIT CUNUMBR=3C01,PATH=(3C),UNIT=OSA
IO1000   IODEVICE ADDRESS=(4000,064),UNITADD=00,CUNUMBR=3C01,          X
               UNIT=OSA
IO1040   IODEVICE ADDRESS=(4040,016),UNITADD=40,CUNUMBR=3C01,          X
               UNIT=OSA
IO10FE   IODEVICE ADDRESS=(40FE,001),UNITADD=FE,CUNUMBR=3C01,          X
               UNIT=OSAD

Sample commands to define vswitch:
"DEFINE VSWITCH VSWITCH1 RDEV 4000  CON CONTR * PORT MYPORT"
"SET VSWITCH VSWITCH1 GRANT TCPIP    VLAN ANY"

Sample statements from TCPIP config:
DEVICE DEV4000 OSD   4000 PORTNAME MYPORT
LINK   LNK4000 QDIOETHERNET DEV4000


David Booher wrote:

> So, my current IOCP has:
>
>    CNTLUNIT CUNUMBR=0100,PATH=(00),UNIT=OSA
>    IODEVICE ADDRESS=(0100,03),CUNUMBR=(0100),UNIT=OSA,           X
>          UNITADD=00
>    IODEVICE ADDRESS=(010F),CUNUMBR=(0100),UNIT=OSAD,             X
>          UNITADD=FE
>
> Should I generate more OSA IODEVICE addresses, say 0103, 0104, and 0105  and use 
> 0103 as the RDEV for the VSWITCH?  What's confusing is that VSWITCH RDEV wants a 
> REAL device, so is it possible to generate more addresses for the real OSA?
>
> Dave
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Ferguson, Neale
> Sent: Thursday, April 08, 2004 3:50 PM
> To: [EMAIL PROTECTED]
> Subject: Re: VSWITCH question
>
> The VSWITCH OSA devices are attached to no one. CP will drive them but use
> the VM TCPIP stack to initialize the devices. CP uses the *VSWITCH IUCV
> service to talk with the stack. The stack will issue the necessary CCWs to
> get the OSAs initialized. From that point on CP will drive the devices
> itself and the stack is "out of the loop".
>
> So the answer is: use OSA devices not currently in use.
>
> Alan Altmark gave an extremely interesting and detailed presentation on just
> this issue at today's Hillgang meeting.
>
> Neale
>
> ----------------------------------------------------------------------
> 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

Reply via email to