Re: VLAN config with XEN
Serg,
the first thing would be to reconfigure xen to not change the network config during it's startup. That is done by modifying the /etc/xen/xend-config.sxp. Change the line "(network-script allianz-network-bridge.sh)" from whatever it looks like to simply "(network-script )". Therefor you also no longer need to have a special network config script in /etc/xen/scripts if you have one.
After that is done, you best would restart the server to get a clear network configuration. You can start with the xen hypervisor but will need to shutdown the xend daemon afterwards (rcxend stop) to use yast to configure the network.
Run ifconfig to notice the mac address of your currently used network card.
Then open yast and jump into the network config.
Select your configured interface and delete it.
The interface itself should not disappear, it should only be changed to be not configured.
Then add a new interface with the type virtual lan and enter the vlan number. In the next screen choose the card with the mac address you use before. Once back in the network adapter list, add another card with type virtual lan and assign it to the same physical nic.
After that we need to create two bridges (one for each virtual interface). The problem is that the current yast version does not let you assign the bridges to virtual lan interfaces. therefor configure the bridge simply to the physical nic with the previously noticed mac address.
After all changes are done, leave yast and chnage in a console session to /etc/sysconfig/network. You will have there two files for your bridges called ifcfg-br... Edit them and change the interface they are assigned to to the vlan interface names like vlan100 or whatever number you used. Do that for both bridges, that each one points to one of the vlan interfaces. After that restart the server and verify the network configuration when it is up. You should see two bridges and "brctl show" should show you that the vlan interfaces are conencted to the bridge and both vlan interfaces point to the same physical nic (not visible in the brctl output).
Once that is all done, reconfigure the domUs to use the specific bridge.
Rainer
|