On Tue, 7 Mar 2006 18:00:16 -0500, Alan Altmark [EMAIL PROTECTED]
wrote:
In general, I recommend not sharing
an OSA being used by a VSWITCH since our eventual adoption of protocols
like GVRP will cause a mismatch if others are using the OSA with differe
nt
VLAN IDs. In your case, I recommend
On Wednesday, 03/08/2006 at 04:34 CST, Brian Nielsen
[EMAIL PROTECTED] wrote:
Thanks. Since separate OSA's are scarce, would the next best thing be
to
put TCPIP on the VSWITCH? Are there any serious negatives to doing so?
That's fine. The only negative is that TCPIP cannot use a VSWITCH
On Mon, 6 Mar 2006 18:40:11 -0500, Alan Altmark [EMAIL PROTECTED]
wrote:
From the book, The defvid defines the default VLAN ID to be associated
with untagged frames received and transmitted by the Virtual Switch. Th
is
is also known as the native VLAN id in the switch. They must match.
I will
On Mon, 6 Mar 2006 18:40:11 -0500, Alan Altmark [EMAIL PROTECTED]
wrote:
From the book, The defvid defines the default VLAN ID to be associated
with untagged frames received and transmitted by the Virtual Switch. Th
is
is also known as the native VLAN id in the switch. They must match.
I
You should be able to just leave the VLAN parameter off and let it default
to VLAN UNAWARE.
Rick Barlow
Systems Engineering Consultant
Nationwide Services Co., Enterprise Business Intelligence Services
Mainframe, z/VM and zSeries Linux Support
One Nationwide
On Tuesday, 03/07/2006 at 02:58 CST, Brian Nielsen
[EMAIL PROTECTED] wrote:
So the problem is the vswitch interfering with the packets when it
thinks
VLAN 7 is for untagged traffic. I'll be taking Alan's advice and
changing
my vswitch definitions to use a defvid of 1. Presumably any unused
had a similar problem on 5.2. See if ptf UM31613 APAR VM63895 are on your
system. It corrected our problem.
David
-Original Message-
From: VM/ESA and z/VM Discussions on behalf of Brian Nielsen
Sent: Mon 3/6/2006 3:17 PM
To: VMESA-L@LISTSERV.UARK.EDU
Subject: Vswitch problem on z/VM
I think the problem is your VLAN ID on the DEFINE VSWITCH. That value
needs to match the management VLAN ID for the switch to which your OSA is
connected. The normal default is 1. Your installation may have changed
the value. You will need to talk to the group that configures your switch
On Monday, 03/06/2006 at 02:51 CST, Brian Nielsen
[EMAIL PROTECTED] wrote:
It is my understanding from the manuals that the VLAN ID on the DEFINE
VSWITCH only sets up the default VLAN ID to be used by guests that do
not
include a VLAN ID on the SET VSWITCH GRANT command. All of the guests
