shouldn't there be a modify/grant statement in the SYSTEM CONFIG after the 
vswitch define ?

MODIFY VSWITCH VM3SWTCH GRANT MLXESS1S 

Bill Munson 




Hans Rempel <[email protected]> 
Sent by: The IBM z/VM Operating System <[email protected]>
08/13/2009 11:16 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: Configuring and Using a VSWITCH






Martin. In the event you are not aware your TCPIP stack is not using the
VSWITCH but since they are both on the same OSA card the VSWITCH and all
NICs coupled to the VSWITCH will be on the same LAN segment as the TCPIP
stack provided you are not using network VLANs.  That means your LINUX 
guest
will have IP addresses/mask of the subnet used by the TCPIP stack and will
also use the same gateway address. Check Linux network configuration 
and/or
provide the list with your Linux IP configuration.

Even if this is all correct you must be sure the Linux guest NIC couples 
to
the VSWITCH. In your case the couple of Linux NIC to VSWITCH should be
automatic when you logon because of the Directory entry NIC statement and
the VSWITCH has authorized userid to connect. Do you have a VM security
product in place that may require some granting of VSWITCH access?

A quick check to insure the couple works is to look for any error message 
at
logon as Dave suggest or issue the Q VSWITCH detail and you should see
something like this. LINUX01 is my Linux guest. 

Adapter Connections:
 Adapter Owner: LINUX01  NIC: EB00.P00 Name: dontcare
   RX Packets: 66         Discarded: 0          Errors: 0
   TX Packets: 111        Discarded: 0          Errors: 0
   RX Bytes: 5548                 TX Bytes: 11313
   Device: EB02  Unit: 002   Role: DATA       vPort: 0067  Index: 0067
  Options: Broadcast Multicast IPv6 IPv4 VLAN
    Unicast IP Addresses:
      142.214.154.41       MAC: 02-00-00-00-00-04
      FE80::200:0:100:4    MAC: 02-00-00-00-00-04 Local
    Multicast IP Addresses:
      FF02::1              MAC: 33-33-00-00-00-01 Local
      FF02::1:FF00:4       MAC: 33-33-FF-00-00-04 Local

Can you provide the LINUX IP configuration.

Lastly, I believe this is not a problem as long as you use 3 consecutive
addresses for your nic/OSA card but your skipped 703 OSA card address
 

Hans
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Dave Jones
Sent: August 13, 2009 5:24 PM
To: [email protected]
Subject: Re: Configuring and Using a VSWITCH

OK, that all looks good to me. What does a Linux guest report when you 
log it on; are there any CP error messages about coupling the NIC to the 
VSWITCH?

Kline, Martin wrote:
> We are attempting to configure a proof of concept z/VM and Linux 
> configuration, and I have spent several days futzing around with the 
> vswitch. It just plain does not work. Linux says the LAN is offline. 
> 
> Maybe someone could be so kind as to point out the error of my ways?
> 
> Our real OSA address is 0700. It works just fine. I can use a TN3270 
> emulator to connect to VM. But, when the guests try to access the 
vswitch,

> it's a totally different story.
> 
> Here are some of the related configuration files as they currently 
exist:
> 
> q vswitch acc 
> VSWITCH SYSTEM VSWITCH1 Type: VSWITCH Connected: 0    Maxconn: INFINITE
>   PERSISTENT  RESTRICTED    NONROUTER                 Accounting: OFF 
>   VLAN Unaware 
>   MAC address: 02-00-01-00-00-01 
>   State: Ready 
>   IPTimeout: 5         QueueStorage: 8 
>     Authorized userids: 
>       OZLXDEV1 OZLXINIT OZLXORA1 OZLXSINI SYSTEM 
>   RDEV: 0704.P00 VDEV: 0704 Controller: DTCVSW1 
> 
> ---------------------------------------------------
> 
> from SYSTEM CONFIG
> 
> DEFINE VSWITCH VSWITCH1 RDEV 0704
> VMLAN MACPREFIX 020001 
> 
> ---------------------------------------------------
> 
> q osa 
> OSA  0700 ATTACHED TO TCPIP    0700 DEVTYPE OSA         CHPID 80 OSD
> OSA  0701 ATTACHED TO TCPIP    0701 DEVTYPE OSA         CHPID 80 OSD
> OSA  0702 ATTACHED TO TCPIP    0702 DEVTYPE OSA         CHPID 80 OSD
> OSA  0704 ATTACHED TO DTCVSW1  0704 DEVTYPE OSA         CHPID 80 OSD
> OSA  0705 ATTACHED TO DTCVSW1  0705 DEVTYPE OSA         CHPID 80 OSD
> OSA  0706 ATTACHED TO DTCVSW1  0706 DEVTYPE OSA         CHPID 80 OSD
> 
> ---------------------------------------------------
> 
> USER DIRECT:
> 
> ******************************
> * 
> PROFILE TCPCMSU 
>   IPL CMS 
>   MACH ESA 
>   SPOOL 000C 2540 READER * 
>   SPOOL 000D 2540 PUNCH A 
>   SPOOL 000E 1403 A 
>   CONSOLE 009 3215 T 
>   LINK MAINT 0190 0190 RR 
>   LINK MAINT 019D 019D RR 
>   LINK MAINT 019E 019E RR 
>   LINK MAINT 0402 0402 RR 
>   LINK MAINT 0401 0401 RR 
>   LINK MAINT 0405 0405 RR 
>  . . .
> ****************************** 
> * 
> PROFILE LNXDFLT 
>   MACHINE ESA 2 
>   CPU 00 BASE 
>   CPU 01 
>   IPL 200 
>   CONSOLE 009 3215 
>   NICDEF 300 TYPE QDIO LAN SYSTEM VSWITCH1
>   SPOOL 000C 2540 READER * 
>   SPOOL 000D 2540 PUNCH A 
>   SPOOL 000E 1403 A 
>  . . .
> ****************************** 
> * 
> USER DTCVSW1  DTCVSW1  32M  128M G 
>  INCLUDE TCPCMSU 
>  OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 
>  IUCV *VSWITCH MSGLIMIT 65535 
>  LINK 5VMTCP40 491 491 RR 
>  LINK 5VMTCP40 492 492 RR 
>  LINK TCPMAINT 591 591 RR 
>  LINK TCPMAINT 592 592 RR 
>  LINK TCPMAINT 198 198 RR 
>  MDISK 191 3390 2354 005 VMWK02  MR ******** ******** ********
>  . . .
> ****************************** 
> *LINUX 2-PACK 
> USER OZLXINIT OZLXINIT 1G 2G G 
>   INCLUDE LNXDFLT 
>   MDISK 200 3390 1 END LX2E77 M 
>   MDISK 201 3390 1 END LX2E78 M 
>   MDISK 202 3390 1 END LX2E7A M 
>   MDISK 203 3390 1 END LX2E80 M 
> ****************************** 
> *LINUX SERVER OZLXORA1 
> USER OZLXORA1 OZLXORA1 1G 2G G 
>   INCLUDE LNXDFLT 
>   MDISK 200 3390 1 END LX2E75 M 
>   MDISK 201 3390 1 END LX2E79 M 
>   MDISK 202 3390 1 END LX2E81 M 
> --------------------------------------------------
> 
> 
> SYSTEM DTCPARMS:
> 
> .********************************************************
> .* SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 3 Dec 2008
> .* Configuration program run by MAINT at 13:04:37 
> .********************************************************
> :nick.TCPIP    :type.server 
>                :class.stack 
>                :attach.0700-0702 
> :nick.DTCVSW1  :type.server    :class.stack 
> 
> ---------------------------------------------------
> 
> From PROFILE TCPIP
> 
>   DEVICE VDEV1     VIRTUAL 0 
>   LINK VLINK1      VIRTUAL 0 VDEV1 
> ; ----------------------------------------------------------------------
> DEVICE d...@0700  OSD 0700   NONROUTER 
> LINK OSA0700 QDIOETHERNET d...@0700  PATHMTU MTU 1492 IP 
> ; (End DEVICE and LINK statements) 
> ; ----------------------------------------------------------------------
> ; ----------------------------------------------------------------------
> HOME 
> 10.0.102.47 255.255.255.0 OSA0700 
> 10.0.219.1  255.255.255.0 VLINK1 
> ; (End HOME Address information) 
> ; ----------------------------------------------------------------------
> GATEWAY 
> ; Network       Subnet          First           Link             MTU 
> ; Address       Mask            Hop             Name             Size 
> ; ------------- --------------- --------------- ---------------- ----- 
> DEFAULTNET                      10.0.102.4      OSA0700          1492 
> ; (End GATEWAY Static Routing information) 
> ; ----------------------------------------------------------------------
> START d...@0700

-- 
Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544


*************************** IMPORTANT
NOTE***************************** The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
************************************************************************

Reply via email to