1 / 16

XenClient Enterprise 4.5

XenClient Enterprise 4.5. Engine Network Addressing Modes. Table of Contents. Internal and External Networks. All XCE VMs have two virtual network adapters. Xen Net Device: Connects to external network. Internal Network Device: Connects to internal network. External Network 10.1.0.0/22.

arien
Download Presentation

XenClient Enterprise 4.5

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. XenClient Enterprise 4.5 Engine Network Addressing Modes

  2. Table of Contents

  3. Internal and External Networks • All XCE VMs have two virtual network adapters. • Xen Net Device: Connects to external network. • Internal Network Device: Connects to internal network. External Network 10.1.0.0/22 Win7 VM WinXP VM Internal Network 192.168.200.0/28

  4. Internal Network • The internal network only exists within the Engine. • Can be used to access: • The Dock file share. • The Engine iSCSI target (for the optical drive). • Cannot be used to access: • Other Virtual Machines (VMs) running on the same computer. • Purposely disabled to promote isolation between VMs. Engine iSCSI Target Dock File Share Engine Win7 VM Internal Network 192.168.200.0/28

  5. External Network • This is the network the computer is connected to. • Could be a wired, wireless, or broadband connection. • Used by VMs to access external network resources. • The word “external” means “outside the Engine”. • It could be an intranet or other private network. Local Network Resources Internet External Network 10.1.0.0/22 Engine Win7 VM

  6. Network Addressing Modes Two modes for connecting VMs to the external network. • Bridged Mode: Virtual Switch • Virtual Machine (VM) connects to external network through a virtual switch. • VM gets an IP address from DHCP services in the external network. External Network 10.1.0.0/22 External Network 10.1.0.0/22 Virtual Switch Virtual Router DHCP DHCP • NAT Mode: Virtual Router • VM connects to the internal network. • Internal network connects to the external network through a virtual router. • VM gets an IP address from DHCP services in the internal network. VM 10.1.1.220 VM 192.168.200.3 Engine Engine Internal Network 192.168.200.0/28

  7. Network Addressing Mode Comparison

  8. NAT Mode Request To External Network The VM generates a request packet for delivery to the computer in the external network. Request src=192.168.200.3 dest=10.1.1.6 The virtual network interface in the VM delivers the request packet to the internal network. Request src=10.1.1.170 dest=10.1.1.6 External Network 10.1.0.0/22 Request src=10.1.1.170 dest=10.1.1.6 The Engine NAT layer intercepts the packet and sets the source IP address to the Engine. Internal Network 192.168.200.0/28 Engine 10.1.1.170 VM 192.168.200.3 Engine delivers the modified packet to the external network where its routed to the destination computer. The external network host receives the request. It appears as if it came from the Engine, not the VM.

  9. NAT Mode Response From External Network The external network host generates a response packet. It is sent to the Engine, not the VM. Response src=192.168.200.3 dest=10.1.1.6 The response packet is received by the external network and routed to the Engine. External Network 10.1.0.0/22 Response src=10.1.1.6 dest=10.1.1.170 Response src=10.1.1.6 dest=192.168.200.3 Engine receives the response packet and sets the destination IP address to the VM. Internal Network 192.168.200.0/28 VM 192.168.200.3 Engine 10.1.1.170 Engine submits the modified response packet to the internal network. The virtual network adapter in the VM receives the response from the internal network.

  10. Virtual Machine Connections To and From External Network Engine External Network Computer Connections from the external network computer to the Engine itself work in NAT and bridged mode. NAT and Bridged VM Connections from the VM to computers in the external network work in NAT and bridged mode. NAT and Bridged RDP VNC VNC Client RDP But connections from computers in the external network to the VM only work in bridged mode. Engine VNC Service Remote Desktop Client Remote Desktop Service Remote Desktop Service Remote Desktop Client Bridged Only

  11. Why Use NAT Mode? • NAT mode is the only supported network addressing mode for wireless LAN and wireless broadband network connections. • NAT mode only requires one IP address from DHCP services in the external network. Bridged mode requires one IP address for the Engine and one for each VM. • NAT mode provides a layer of network protection for the VMs since they can not be addressed from the external network.

  12. Virtual Machine Network Configuration: Bridged Mode • External Network Device • IP address and other configuration comes from DHCP services in the external network. • Uses network gateway and DNS services in the external network. • Other computers in the external network should be able to connect to this IP address via ping, RDP, etc. External Network 10.1.0.0/22 • Internal Network Device • IP address and other configuration comes from DHCP services hosted by the Engine on the internal network. • No network gateway or DNS servers. • Can only be used to access resources on the internal network by IP address. • Other computers in the external network will not be able to connect to this IP address. Internal Network 192.168.200.0/28

  13. Virtual Machine Network Configuration: NAT Mode • External Network Device • IP address and other configuration comes from DHCP services hosted by the Engine on the internal network. • The Engine also acts as a DNS server and network gateway. Network requests are routed to the external network. • Other computers in the external network cannot connect to this interface. • Internal Network Device • Same configuration as for bridged mode. • IP address in the same range as external network device. Both come from the internal network. • But there is no network gateway or DNS server set so it can not be used to access the external network. Internal Network 192.168.200.0/28 Internal Network 192.168.200.0/28

  14. Network Addressing Mode in Engine Control Panel The network addressing mode can be viewed or changed in the Engine control panel. Start the Engine networking control panel applet. Select the Wired network connection. Click the “Connection Details” link to view the current addressing mode. Click the “Change Address Mode” link to change the addressing mode. Bridged mode is only supported for wired network connections.

  15. Network Addressing Mode in Engine Policy • The default addressing mode for wired network connections is NAT. • The default can be set to bridged mode in Engine policy. • This only applies to wired network connections. Locate the Engine policy in Synchronizer console. Select the network section. Set the address mode to “bridged”. The setting control should be set to one of the “yes” values.

  16. Internal Network Range of IP Addresses • The range of IP addresses for the internal network is configurable in Engine policy. • Default range in CIDR notation: 192.168.200.0/28 • Should be changed if this range conflicts with external network IP addresses. • This can only be done in Synchronizer policy, not in the Engine control panel. Locate the Engine policy in Synchronizer console. The setting control should be set to one of the “yes” values. Select the network section. Set the base address and netmask length for the internal network.

More Related