User Tools
virtualization:xenserver:xenserver_networking
This is an old revision of the document!
Table of Contents
XenServer Networking Notes
Helpful Commands
brctl show arp -a ifconfig xenbr0
xe Examples
| XenServer “xe” | 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 |
VLANs
http://discussions.citrix.com/topic/246981-how-to-pass-a-trunked-interface-to-a-vm/
http://support.citrix.com/article/CTX123489
- VLANs allow a single physical network to support multiple logical networks.
- To use VLANs with XenServer, the host's NIC must be connected to a VLAN trunk port (switch or router).
- Creating a VLAN in XenServer is done through the process of creating additional virtual interfaces that correspond to a specific VLAN tag. This is done through the XenCenter Host Network tab by adding an External network name and assigning an NIC with a VLAN number.
- XenServer VLANs are represented by additional PIF objects representing VLAN interfaces corresponding to a specified VLAN tag.
- XenServer networks can then be connected to the PIF representing the physical NIC to see all traffic on the NIC, or to a PIF representing a VLAN to see only the traffic with the specified VLAN tag.
- When using VLANs the XenServer host handles all interpretation of the VLAN tags and strips the VLAN tags before routing packets to VMs.
- If the XenServer host has one or more VLAN networks configured on an interface or bond, it will perform the VLAN tag/untag operations for all packets that enter/leave that interface/bond.
- However, if no VLAN networks/bridges/whatever-the-term-may-be are configured on the interface/bond, then XenServer leaves 802.1q VLAN tags alone and passes the packets straight to the VM.
- If there are any VLAN interfaces configured on top of the base interface (either a simple physical interface or a non-tagged bond), XenServer strips off the tags, as it is responsible for both tagging and untagging of packets on that base interface.
- XenServer will leave 802.1q VLAN tags alone if there are no VLAN networks configured on top of your base interface, be that a single physical interface or a logical interface such as a bond.
Bonding
virtualization/xenserver/xenserver_networking.1392786609.txt.gz · Last modified: 2014/02/18 22:10 by gcooper
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
