On Tuesday, 12/23/2008 at 11:26 EST, "Ayer, Paul W" <[email protected]> wrote: > What does this info tell me ... Do I have an OSA problem? > > 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?
"Belief" isn't really sufficient. You need to verify it. > 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 : > VSWITCH Connection: > RX Packets: 0 Discarded: 0 Errors: 0 > TX Packets: 2987 Discarded: 0 Errors: 0 > RX Bytes: 0 TX Bytes: 5280536261 The fact that you have NATIVE and DEFAULT vlan ids the same worries me. (If I had my way, CP would reject that as a configuration error.) > Adapter Owner: AGZLS001 NIC: 0200 Name: layer2 > Porttype: Trunk > RX Packets: 235 Discarded: 0 Errors: 0 > TX Packets: 2621 Discarded: 0 Errors: 375 Since you are using a virtual trunk port, did you configure the guest to be VLAN aware (vconfig, etc.)? All of those errors are probably due to mis-tagged frames. (If the guest only needs access to a single VLAN on a VSWITCH, leave it as a virtual ACCESS port.) That said, if you DID enable the guest to use VLAN 32, CP will say "It's the same as the native VLAN" and will, IIRC, REMOVE the tag. If the port default VLAN id is NOT actually VLAN 32, then the data will drift off into Never-Never Land. The other likely problem is that the physical port is actually in ACCESS mode, not TRUNK, with its default port VLAN id set to 32. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
