[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] XCP 1.1 Management VLAN


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Brett Westover" <bwestover@xxxxxxxxxxx>
  • Date: Thu, 17 Nov 2011 17:24:13 -0800
  • Delivery-date: Fri, 18 Nov 2011 01:28:59 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcyljxgtdE/5scQGTx+afCstgDexHgAAMbYQ
  • Thread-topic: [Xen-users] XCP 1.1 Management VLAN

>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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.