What does this info tell me ... Do I have an OSA problem?
Performance toolkit shows;
only outbound data bytes on address 0802
the 800-802 addresses as online.
A q Vswitch vwdb032a det shows no RX bytes or packets;
We (Vswitch and real switch) believe that the vlan id is 32
Why no RX data at the Vswitch level?
VSWITCH SYSTEM VWDB032A Type: VSWITCH Connected: 1 Maxconn: INFINITE
PERSISTENT RESTRICTED ETHERNET Accounting: OFF
VLAN Aware Default VLAN: 0032 Default Porttype: Trunk GVRP: Enabled
Native VLAN: 0032
MAC address: 02-BB-BB-00-00-03
State: Ready
IPTimeout: 5 QueueStorage: 8
RDEV: 0800 VDEV: 0800 Controller: VSWTCH1
VSWITCH Connection:
RX Packets: 0 Discarded: 0 Errors: 0
TX Packets: 2987 Discarded: 0 Errors: 0
RX Bytes: 0 TX Bytes: 5280536261
Device: 0802 Unit: 002 Role: DATA Port: 0001 Index: 0001
RDEV: 0C00 VDEV: 0C00 Controller: VSWTCH2 BACKUP
Adapter Connections:
Adapter Owner: AGZLS001 NIC: 0200 Name: layer2
Porttype: Trunk
RX Packets: 235 Discarded: 0 Errors: 0
TX Packets: 2621 Discarded: 0 Errors: 375
RX Bytes: 16388 TX Bytes: 5280467157
Device: 0202 Unit: 002 Role: DATA Port: 0067 Index: 0040
VLAN: 0032
Options: Ethernet Broadcast
Unicast MAC Addresses:
02-BB-BB-00-00-09 IP: 10.48.32.22
Multicast MAC Addresses:
01-00-5E-00-00-01 IP: 224.0.0.1
01-00-5E-00-00-FB IP: 224.0.0.251
33-33-00-00-00-01 IP: FF02::1
33-33-00-00-00-FB IP: FF02::FB
33-33-FF-00-00-09 IP: FF02::FF00:9
-----Original Message-----
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Alan
Altmark
Sent: Tuesday, December 23, 2008 10:46 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: VLAN tagging
On Tuesday, 12/23/2008 at 09:05 EST, עופר ברוך <offerbar...@gmail.com>
wrote:
> I configured the VSWITCH to be VLAN aware and the Linux to be unaware
> (meaning the Linux is working as if no VLAN tagging is enabled).
> I used the VLAN <default_vlan_id> parameter on the DEFINE VSWITCH
command
> and the PORTType ACCESS parameter to make the guest be unaware of VLAN
IDs.
FYI, PORTTYPE ACCESS is the default guest port type, without regard to the
specification of the VLAN keyword on DEFINE VSWITCH.
Also (clip this and put in your networking scrapbook):
1. Every VLAN-capable switch has something called a *native* VLAN id. It
has a default value of 1. Installations often change this value to avoid
accidents.
2. Every trunk port on a switch has a *default port* VLAN id that is
applied when an untagged frame is received. This defaults to the *native*
VLAN id, but can be changed by the installation on a per-port basis.
3a. z/VM 5.3 and later: On a VLAN-aware VSWITCH, the NATIVE keyword must
be used to match the *port default* VLAN id. The VLAN keyword on DEFINE
VSWITCH is used solely indicate VLAN awareness and to avoid specifying a
VLAN id on the SET VSWITCH GRANT. If you don't use the NATIVE keyword, it
acts like z/VM 5.2.
3b. z/VM 5.2 and earler: The VLAN keyword combines the functions of the
z/VM 5.3 VLAN and NATIVE functions. Be careful. It must match the port
default VLAN ID, even if that isn't the VLAN you would like to assign the
guests to. This means you always specify a VLAN id on a SET VSWITCH
GRANT.
4. Before you define a VLAN-aware VSWITCH, you should ask for a copy of
the switch configuration parameters, preferably by seeing a copy of the
switch queries, rather than trusting someone's memory. 'Cuz if the values
from step 3 don't match the physical switch configuration, you will get
anomalous results that include "doesn't work".
Alan Altmark
z/VM Development
IBM Endicott
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
