Not only want, need to control. VLAN tagging from the mainframe will require close coordination with the router/switch networking administrators. For example, If VLAN 436 is configured within the mainframe, then the router/switch networking administrators will need to configure VLAN 436 in their equipment as well. IP subnet assignments to the VLAN will also have to match the external network. VLAN numbers are global within a VTP domain (if you are using Cisco external switches for your network) and so the exact numbers used may need to be tightly managed and assigned by the external network administrators to avoid global conflicts. Your life and theirs will be easier if you do NOT configure VLAN trunking (8021q framing) to the external network. Although OSPF in general is a good thing, whether it is in your case is a separate question.
Harold Grovesteen
Rob van der Heij wrote:
Lionel Dyck wrote:
Vic - thanks.
You said that if using vswitch that vlan was not needed if all the guests were on the same subnet. How would you connect the guests then?
He probably meant to say 'same VLAN' The port on the outboard switch can be configured to treat all hosts connected to that port as VLAN unaware, and anything you do with VLAN in the VSWITCH or in the connected Linux guests is just smoke and mirrors and does not do much for real. The port can also be configured as a trunk to another VLAN capable switch. In that case the VLAN tagging done by CP and the OSA microcode can be used to isolate Linux guests connected to the same VSWITCH and OSA port, based on their VLAN ID. The owner of the outboard switches will probably want some control over what the VM administrators do with the VLAN tagging.
Rob
---------------------------------------------------------------------- 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
---------------------------------------------------------------------- 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
