Setup citrix xenserver

1. Setup Xenserver từ source ISO bình thường. (link http://www.citrix.com/tv/#videos/103 hoặc http://www.citrix-tips.com/438/citrix-xenserver-installation-guide-2/ )


2. Lưu ý:

XenServer VLAN Networking

Citrix XenServer is connected to a switch trunk port when you want to use VLANs. VLANs allow a network administrator to segregate traffic for bandwidth or security purposes.

The following are good knowledge to have, but not necessary:

• Network Fundamentals

• Citrix XenServer Administration Knowledge

• Cisco IOS Switch Familiarity

• Windows Server 2003 Networking Skills

Components and Definitions

The following components and acronyms are used throughout this document:

• XenServer - The host machine running XenServer software

• Virtual Machine (VM) - Software implementation of a computer

• Network Interface Card (NIC) - Physical network interface card attached to the host

• Switch - Device used to join multiple computers together

• Trunk Port - Port designated to handle many VLAN’s

• Virtual LAN - Group of hosts with a common broadcast domain

About XenServer Networking

Refer to the XenServer Administrators Guide Version for creating VLAN’s networks through XenCenter. XenServer allows a single physical network to support multiple logical VLAN networks used as broadcast domains.

Creating a VLAN in XenServer is done through the process of creating additional virtual interfaces that corresponding to a specific VLAN tag. This is done through the XenCenter Host Network tab by adding an External network name and assigning a NIC with a VLAN number.

XenServer VM’s can be assigned to a specific VLAN by adding the VLAN network created for the host.

Configuring the XenServer management interface on a VLAN network is not supported. The VLAN should be set on the switch as shown in the following screen shot.

Procedure

To configure the switch on a VLAN network, you must configure it as follows:

• Port connected to XenServer on the switch must be configured as trunk port.

• Port on the switch must be configured for 802.1q encapsulation.

• Port security cannot be set on the trunk port.

• Port designated as trunk should be assigned a native VLAN; use 1 as default.

Note: If a Native VLAN is used on the switch trunk port, then you cannot assign that VLAN number to a VM on the XenServer. Refer to the example below for a working tested model.

Example Cisco Configuration

This is a lab setup for a XenServer to support VLAN’s with a Cisco 2950 Catalyst switch. The setup is as follows:

• Server running XenServer.

• XenServer has two physical NICs (Network Interface Cards) installed on the XenServer (eth0 and eth1).

• Cisco Catalyst 2950 configuration displayed.

• One port (Port 4) on switch is used for management and second (Port 9) is being used as trunk port.

Using XenServer we isolated the WinSrv2003 VM to VLAN 181 with the following example. In XenServer (Fig. 1) we have two physical network interfaces labeled eth0 and eth1. The NICs are used for two different functions; management communication and VLAN 181 traffic. We have built a Windows 2003 VM with a VLAN network created on the host labeled New Network that is assigned VLAN 118. Upon creation of the network and dedicating it a NIC the XenServer application automatically configured the appropriate bridge (Fig. 2) by adding the interface eth1.181 that is designated for VLAN 181.

Through the use of bridges XenServer can communicate with VLAN’s in a production environment by creating bridges to correspond to each Physical interface and mapping it to the appropriate VLAN.

It is possible to capture the VLAN tags that are transmitted across the switch to the XenServer with the use of packet sniffing software with NICs that allow VLAN tags to be displayed.

Muốn VLAN hoạt động tốt (không chạy được) thì phải setup thêm soft trên xenserver:
Here's the final steps needed to resolve this issue:

Enable the epel repo:
rpm -ivh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm

Install ebtables:
yum install ebtables

Install the following filter (replace eth1 with the interface you're using for your VM VLANs):
ebtables -t broute -A BROUTING -p 802.1Q -i eth1 -j DROP

Enable ebtables at startup:
chkconfig --levels 2345 ebtables on

Check the current "broute" table rules:
ebtables -t broute --list

Save the tables for next start
/etc/init.d/ebtables save

###########

Có thể tham khảo thêm về "Understanding XenServer Networking – The Linux Perspective" tại http://support.citrix.com/article/CTX117915

www.studyall.co.cc