Re: [Xen-users] XCP 1.1 Management VLAN

[George Shuklin <george.shuklin@xxxxxxxxx>]

We've using management+san traffic together. You can use tags for SAN 
traffic (if your switches support hybrid ports (tagged+untagged 
traffic), or you can use them even without creating vlan. Both traffic 
is very sensitive for stranger eye (f.e. all SAN traffic is 
unencrypted), so hiding it in isolated network is nice idea.
Management interface of xapi is somehow not 'for internet use'. F.e. XCP 
shall not be updated from centos repos (it will break patches of LVM 
package and may be some other stuff), so putting management interface 
(ssh and so on) to the internet is bad idea.
In short: hide them both in private network.

On 18.11.2011 05:24, Brett Westover wrote:
> > No, sorry. You can try to hack the xcp/xapi underlying configuration,
> > but this require significant understanding of xapi internals (and, of
> > cause, every your change will be your own problem without community
> > support).
> > But outside this you can not use tagged vlans for management interface
> > of xapi.
> Do you know the reason for this restriction? It seems like a matter of a
> settings change in openvswitch to allow any interface to accept tagged
> frames. I must be misunderstanding some requirement of xapi.
>
>
> So what does one do in my situation? Since I only have two interfaces,
> and one essentially gets eaten up for management only, do I put both the
> LAN and SAN traffic on the same interface?
>
>
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users