Home / server / Questions / 648904
Accepted
CryptoJones
Asked: 2014-12-04 08:12:07 +0800 CST

XenServer Configuration Allowing Private Network to Access HyperVisor

  • 772

Within Citrix XenServer...I want an internal network, not dependent on a physical NIC, that only the HyperVisor and virtual machines can see. I believe I want to implement a "Single-Server Private Network."

How do the VMs communicated with the Hyper-Visor? If I want to manage the Hyper-Visor from one of the VMs, how do I access it?

I know the other option is having a network associated with a physical NIC, but I don't want the LAN to be able to access that Network.

xenserver

3 Answers

  1. Best Answer

    not sure about xenserver commands to achieving this

    If you want private connection between virtual machines running on the same host you can create isolated bridge network and connect necessary vNIC of virtual machines to it.[from "xl list" you can get domain id]

    if using linux-bridge

    brctl addbr isolated

    if you give same range of private ip to "isolated" then you can reach hypervisor from virtual machines using that IP.

    if using ovs

    ovs-vsctl add-br isolated

    to list vNIC details,with this combined with xl list you can get correct vNIC

     brctl show

    To add vNIC to bridge

    brctl addif isolated vNIC

    OVS

    ovs-vsctl add-port isolated vNIC

    Assign private IP inside your virtual machine and now try to connect to hypervisor using the ip assigned on "isolated"

    • 4

  2. First, citrix recommand for the management network on the xenserver to create a nic bond.

    So you are dependant on a NIC. Why, because when you have multiple xenserver they need to talk to each other via the network.

    The best way to isolate is with VLAN or dedicated switch.

    If you want only one VM to talk to the hypervisor, you add a second nic to that VM that got access to the same network.

    • 1

  3. One solution my some proposed to me off-line is using one of the spare NICs on the server, assigning the MGMT interface to that and creating what is called a loop back plug.

    To create a loopback plug, cross pin 1 (TX+) and pin 3 (RX+) together, and cross pin 2 (TX-) and pin 6 (RX-) together. You need the following equipment to create the loopback:

    A 6-inch long CAT5 cable An RJ-45 connector A crimping tool

    enter image description here

    This way you can use the physical network to bridge your connections, but it is isolated and only available to the HyperVisor and its VMs.

    • -1