[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: Fri, 18 Nov 2011 08:04:18 -0800
  • Delivery-date: Fri, 18 Nov 2011 16:06:21 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcylmkOu6uiQS7EQSwy2VrksW7xaPwAcJ1GQ
  • Thread-topic: [Xen-users] XCP 1.1 Management VLAN

>The  trick to have the management interface work on this setup is to have your
>switch port configured with a native non-tagged vlan.  A slight security issue,
>just make sure you restrict your vm's to only the tagged interfaces. There's 
>even an example on the manual for this. Hope this helps.

>-Javier

Thanks I'll try this. I am curious about the security issue though. What is it?

My management vlan, is the highest security domain in the network. It can reach 
any lower level security domain, but next to nothing can get INTO the 
management vlan if it didn't start there.

If I make that VLAN untagged on the switch port that XCP is plugged into, and 
set the PVID (default vlan) to the same, then XCP can 'natively' be on that 
vlan. Then I can also send tagged vlans to that same interface, so I can have 
VMs using other vlans over the same interface. Is that right?

Finally, if I want to make a "management" VM, couldn't I just tie it to the 
physical interface, instead of one of my VLANs, and then it would be on the 
management VLAN as well? Would this work? Is there a security risk involved?

Thanks for your help

Brett Westover


_______________________________________________
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®.