One possibility is that your network and SUSESP2 are configured to use 

VLAN's.  They'll work fine with a real OSA but when you stick a VSWITCH i
n 
you need to GRANT SUSESP2 authorithy to access the VLAN it belongs to.

Brian Nielsen

On Thu, 2 Oct 2008 08:47:34 -0700, Daniel Allen <[EMAIL PROTECTED]> wrote
:

>If I DEDicate the 3 OSA addresses and comment out the NICDEF, I can ping

>the SUSESP2 machine.
> 
>If I use the NICDEF statement and comment out the DEDicated OSA
>addresses, I can not ping the SUSESP2 machine.
> 
>In either instance, SUSESP2 is re-IPL'd to affect the change.
>
>________________________________
>
>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
>Behalf Of Dean, David (I/S)
>Sent: Thursday, October 02, 2008 8:36 AM
>To: [email protected]
>Subject: Re: Issue with VSWITCH and SuSE Linux
>
>
>
>What if you LEAVE SUSE2P in and define the 3 OSA addresses?  I am not
>sure the two are related.  I am GUESSING the 3 OSA's work but nicdef 340

>does not.
>
> 
>
> 
>
> 
>
>David Dean
>
>Information Systems
>
>*bcbstauthorized*
>
> 
>
> 
>
> 
>
>________________________________
>
>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
>Behalf Of Daniel Allen
>Sent: Thursday, October 02, 2008 11:12 AM
>To: [email protected]
>Subject: Issue with VSWITCH and SuSE Linux
>
> 
>
>We are running z/VM 5.2 service level 0602.
>
> 
>
>I have issued the following commands:
>
> 
>
>DEFINE VSWITCH SWITCH1 RDEV 203 CONNECT
>
> 
>
>SET VSWITCH SWITCH1 GRANT SUSESP2
>
> 
>
>In the SUSESP2 directory entry, I have the following:
>
> 
>
>NICDEF 340 TYPE QDIO DEV 3 LAN SYSTEM SWITCH1 
>
> 
>
>When I bring up the SUSESP2 machine, I see the message that device 340
>has been defined.
>
> 
>
>The SUSESP2 machine comes up normally.
>
> 
>
>Here is the output from the Q VSWITCH DET command:
>
> 
>
> 
>
>q vswitch det
>
>VSWITCH SYSTEM SWITCH1  Type: VSWITCH Connected: 1    Maxconn: INFINITE
>
>  PERSISTENT  RESTRICTED    NONROUTER                 Accounting: OFF
>
>  VLAN Unaware
>
>  State: Ready
>
>  IPTimeout: 5         QueueStorage: 8
>
>  Portname: UNASSIGNED RDEV: 0203 Controller: DTCVSW2  VDEV:  0203
>
>    VSWITCH Connection:
>
>      RX Packets: 205        Discarded: 293        Errors: 0
>
>      TX Packets: 0          Discarded: 0          Errors: 0
>
>      RX Bytes: 106924               TX Bytes: 0
>
>      Device: 0203  Unit: 000   Role: DATA
>
>    Adapter Owner: SUSESP2  NIC: 0340  Name: UNASSIGNED
>
>      RX Packets: 205        Discarded: 0          Errors: 0
>
>      TX Packets: 29         Discarded: 0          Errors: 0
>
>      RX Bytes: 106924               TX Bytes: 2268
>
>      Device: 0342  Unit: 002   Role: DATA
>
>      Options: Broadcast Multicast IPv6 IPv4 VLAN
>
>        Unicast IP Addresses:
>
>          10.35.11.183         MAC: 02-00-00-00-00-01
>
>          FE80::200:0:100:1    MAC: 02-00-00-00-00-01 Local
>
>
>        Multicast IP Addresses:              
                       
>          224.0.0.1            MAC: 01-00-5E-00-00-01       
        
>          224.0.1.22           MAC: 01-00-5E-00-01-16       
        
>          239.255.255.253      MAC: 01-00-5E-7F-FF-FD       
        
>          FF02::1              MAC: 33-33-00-00-00-01 Local     
    
>          FF02::1:FF00:1       MAC: 33-33-FF-00-00-01 Local     
    
>Ready; T=0.01/0.01 08:09:01               
                         
 
>
> 
>
>However, I cannot ping the machine SUSESP2.
>
> 
>
>If I take SUSESP2 out of the VSWITCH and use 3 OSA addresses, I can ping

>the machine SUSESP2.
>
> 
>
>What am I doing wrong ?
>
> 
>
>**********************************************************************
>
>This email and any files transmitted with it are confidential and
>intended solely for the use of the individual or entity to whom they are

>addressed. Any unauthorized review, use, disclosure or distribution is
>prohibited. If you are not the intended recipient, please contact the
>sender by reply e-mail and destroy all copies of the original message. 

>
>**********************************************************************
>
> 
>
>Please see the following link for the BlueCross BlueShield of Tennessee
>E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
>

Reply via email to