On Friday, 10/22/2010 at 11:41 EDT, Mauro Souza <thoriu...@gmail.com> wrote: > We granted access to the LNXADM on another vlan (808). Got another IP, from > lnxdb (killed to avoid ip conflict), put the ip on LNXADM, no success. > Changed PORT TYPE to ACCESS, back to VLAN 812, logoff/logon LNXADM, no > success... > Shutdown on zVM, loaded the partition with zvm540, and everything is running > fine. > > What seens VERY odd to me is that all configuration on zvm610 and zvm540 are > EXACTLY the same, and zvm610 doesn't work. And as today is Friday, and I am > flying back home in a couple hours, we will stay on zvm610 until I research > more on this.
You need to do a QUERY VSWITCH DETAILS and compare line-by-line to look for any differences, ensuring that you do things in the same order. If QUERYs are the same and the same order was followed, then open a PMR. Alan Altmark's Best Practice for VLAN-aware VSWITCHes: 1. Do not specify PORTTYPE on the DEFINE VSWITCH. [I would like to see the option go away on DEFINE/MODIFY.] If you want a guest to be VLAN aware, specify PO 2. Ensure NATIVE matches the switch native VLAN ID 3. DEFINE VSWITCH ... VLAN xxxx, where xxxx is a switch administrator-defined private VLAN that is used only to detect guests that have not been properly assigned to a VLAN. 4. Specify VLAN option for all SET VSWITCH GRANTs. If you let it default, you will get the the default (bad) VLAN specified in #3. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
