This is an old revision of the document!
See also Xenserver - Add or Replace a NIC
Jumbo Frames are enabled by setting MTU to 9000 on all Storage network interfaces:
Something like:
brctl show arp -a ifconfig xenbr0
XenServer “xe” Command | Comment |
---|---|
xe network-list | List the networks and attributes |
xe pif-list | List interface attributes (UUID values) |
xe vif-list | |
xe pif-forget uuid= | Forgetting an interface means the Xen host no longer has control. Configure through Linux. |
xe pif introduce hostuuid= mac= device= | Introducing an interface means all configuration should go through Xen. |
xe pif-reconfigure-ip ip=xx.xx.xx.xx uuid= | Change the IP attributes of management interface. |
xe pif-uuid= | |
xe vif-uuid= | There are several pif and vif commands for network setup. |
xe pif-param-set other-config:ethtool-duplex=“full” uuid= | Usually used to set adapter specific attributes. |
xe host-set-hostname-live host-name=<fqdn> host-uuid= | Change the FQDN of the host. |
xe vm-list params=name-label,dom-id | Shows VMs and their dom-id to associate with VIF names |
http://discussions.citrix.com/topic/246981-how-to-pass-a-trunked-interface-to-a-vm/
http://support.citrix.com/article/CTX123489
http://support.citrix.com/article/CTX137599
http://support.citrix.com/servlet/KbServlet/download/34969-102-704897/reference.pdf
Whenever possible, create NIC bonds as part of initial resource pool creation prior to joining additional hosts to the pool or creating VMs. Doing so allows the bond configuration to be automatically replicated to hosts as they are joined to the pool and reduces the number of steps required.
Adding a NIC bond to an existing pool requires one of the following:
If you are not using XenCenter for NIC bonding, the quickest way to create pool-wide NIC bonds is to create the bond on the master, and then restart the other pool members. Alternatively, you can use the service xapi restart command. This causes the bond and VLAN settings on the master to be inherited by each host. The management interface of each host must, however, be manually reconfigured.
xe network-list xe network-create name-label="Pool-wide network associated with bond0" xe pif-list xe bond-create network-uuid=<UUID> pif-uuids=<PIF-UUID-1>,<PIF-UUID-2> reboot
If you are using bonding for resiliency for your storage traffic, you may want to consider using LACP instead of the Linux bridge bonding. To use LACP bonding, you must configure the vSwitch as your networking stack. For more information, see Section 4.2, “vSwitch Networks”.