Post the results of a q vswitch details, please. And also "route" and "ifconfig" from linux.
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of KEETON Dave * OR SDC Sent: Monday, November 24, 2008 2:30 PM To: [email protected] Subject: Re: [IBMVM] VLAN-Aware VSWITCH & Linux Guest Thanks, Alan. To answer your question, I am now able to ping the TCPIP stack address (after making the change you recommended). I am still unable to ping the gateway, however. I suppose I'll go back to beating my head against the wall... Dave -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, November 24, 2008 11:07 AM To: [email protected] Subject: Re: VLAN-Aware VSWITCH & Linux Guest On Monday, 11/24/2008 at 01:54 EST, KEETON Dave * OR SDC <[EMAIL PROTECTED]> wrote: > I've been beating my head against the wall for a week now trying to figure out > what I'm doing wrong, but I can't get it figured out, so I'm appealing to the > fine folks on this list for help. > > I have a new OSA port all to myself and it's connected to a trunk port on the > network switch. I've talked to the network guys and they know what it > is that I > want, so I'm pretty sure that part is set up correctly. > > I've configured TCPIP and the stack is up. From TCPMAINT, I can ping > the > gateway. I have a connection to the network. I built the VSWITCH with the > following command and added it to SYSTEM CONFIG. Addresses have been changed > for security: > > DEF VSWITCH VSS3000 RDEV 1234 2234 PORTT TRUNK VLAN 1234 As you suggest below, get rid of the PORTTYPE TRUNK. Only a guest that needs access to multiple VLANs on the VSWITCH need be granted PORTTYPE TRUNK (VLAN-aware). The others shouldo remain VLAN-unaware (PORTTYPE ACCESS). Even VM TCP/IP. > (For RDEV, there are two links for fail-over) > > Next, I coupled the guest to the vswitch: > > SET VSWITCH VSS3000 GRANT SLES10 VLAN 1234 > > Then, I built a SLES10-SP2 guest and configured the network with YaST. > I cannot > ping outside the guest. Here are the steps I've taken and info I've verified in > an effort to troubleshoot: > > 1. Log on to the guest VM and from CMS, ping the gateway. This works. > I can > ping devices outside the z10. > 2. Tried configuring SLES10 using either VLAN-aware method (Novell doc > indicates manual reconfiguration of adapter & create ifcfg-vlanxxxx file). This > doesn't work. I can't ping outside the VM. > > 3. Tried making the guest VLAN-unaware (ACCESS 1234 option for SET VSWITCH) and > configure SLES interface as normal (eth0). Doesn't work either. Cannot ping > outside the VM. > > I am no expert on VLANs and I appear to be stuck. I would appreciate anyone's > input on this one. The ony thing that comes to mind is that the IP address/subnet/gateway on the guests doesn't match what's in the switch. Can the Linux guest ping VM TCP/IP? Alan Altmark z/VM Development IBM Endicott
