On Wed, Apr 22, 2009 at 16:29, Alan Altmark <alan_altm...@us.ibm.com> wrote:
> Are you sure you're on a trunk port and are you sure that the physical > switch is configured to use VLAN 999 as the *native* VLAN ID? According to the QUERY VSWITCH command I made, yes. I'll have to chat with the team that are in charge of the network to confirm. > It is normally VLAN 1 and it is unusual to put VLAN-aware host traffic on > the native VLAN ID. Since your default and native VLAN IDs are the same, CP > will strip all VLAN 999 tags from outbound traffic. This happens to yield a > working configuration if the OSA is really plugged into an access port, but > breaks the instant the port is reconfigured for trunk mode with a native > VLAN ID that isn't actually VLAN 999. Interesting. In any case, don't forget to authorize the guest to use VLAN 96. That's done and the server is working fine normally, but cannot reach the network once IPL'ed in rescue mode. Which points to what Mark told in his reply about 802.1q . > </yellow alert> > Thanks for your input. ---------------------------------------------------------------------- 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
