Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » virtualization » xenserver » xenserver_networking
Trace:
virtualization:xenserver:xenserver_networking

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
virtualization:xenserver:xenserver_networking [2014/06/09 12:03]
gcooper 		virtualization:xenserver:xenserver_networking [2019/10/30 12:19] (current)
gcooper
Line 2: Line 2:
  
 See also **[[virtualization:xenserver:xenserver_add_nic|Xenserver - Add or Replace a NIC]]** See also **[[virtualization:xenserver:xenserver_add_nic|Xenserver - Add or Replace a NIC]]**
 +
 +See also **[[networking:mtu_test|Testing MTU, Jumbo Frames and Packet Fragmentation]]**
  
 http://support.citrix.com/servlet/KbServlet/download/17424-102-671540/Xen_Networking_in_Linux_final.pdf http://support.citrix.com/servlet/KbServlet/download/17424-102-671540/Xen_Networking_in_Linux_final.pdf
 +
 +===== Management Network =====
 +
 +  * No Jumbo Frames
 +  * No VLANs
 +
 +===== Storage Networks =====
 +
 +Jumbo Frames are enabled by setting MTU to 9000 on all Storage network interfaces:
 +
 +  * ZFS Storage Server
 +  * Virtualization Hosts
 +
 +Something like:
 +
 +  - Shutdown all VM's
 +  - Remove the bond
 +  - Set the MTU to 9000 on the NIC's
 +  - Re-create the bond with MTU 9000
 +  - Start the VM's back up making sure the new bond is listed under the VM's networking
  
 ===== Helpful Commands ===== ===== Helpful Commands =====
Line 18: Line 40:
  
 ^XenServer “xe” Command                     ^Comment                                ^ ^XenServer “xe” Command                     ^Comment                                ^
-|xe network-list                            |List the networks and attributes       | +|''xe network-list''                            |List the networks and attributes       | 
-|xe pif-list                                |List interface attributes (UUID values)| +|''xe pif-list''                                |List interface attributes (UUID values)| 
-|xe vif-list                                |                                       | +|''xe vif-list''                                |                                       | 
-|xe pif-forget uuid=                        |Forgetting an interface means the Xen host no longer has control. Configure through Linux. | +|''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 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-reconfigure-ip ip=xx.xx.xx.xx uuid='' |Change the IP attributes of management interface. | 
-|xe pif-uuid=                               |                                       | +|''xe pif-uuid=''                               |                                       | 
-|xe vif-uuid=                               |There are several pif and vif commands for network setup. | +|''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 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 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 |+|''xe vm-list params=name-label,dom-id''        |Shows VMs and their dom-id to associate with VIF names |
  
 ===== VLANs ===== ===== VLANs =====
Line 62: Line 84:
  
 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. 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.
 +
 +==== XenCenter ====
 +
 +**Select Host -> NICs (tab) -> Create Bond**
 +
 +==== CLI ====
  
 <file> <file>
virtualization/xenserver/xenserver_networking.1402336996.txt.gz · Last modified: 2014/06/09 12:03 by gcooper

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki