Product Documentation

Networking Troubleshooting

Jun 13, 2017
Networking Troubleshooting
Prev Chapter 4. Networking Next

If you are having problems with configuring networking, first ensure that you have not directly modified any of the control domain ifcfg-* files directly. These files are directly managed by the control domain host agent, and changes will be overwritten.

Some network card models require firmware upgrades from the vendor to work reliably under load, or when certain optimizations are turned on. If you are seeing corrupted traffic to VMs, then you should first try to obtain the latest recommended firmware from your vendor and apply a BIOS update.

If the problem still persists, then you can use the CLI to disable receive / transmit offload optimizations on the physical interface.

Warning

Disabling receive / transmit offload optimizations can result in a performance loss and / or increased CPU usage.

First, determine the UUID of the physical interface. You can filter on the device field as follows:

xe pif-list device=eth0

Next, set the following parameter on the PIF to disable TX offload:

xe pif-param-set uuid=pif_uuid other-config:ethtool-tx=off

Finally, re-plug the PIF or reboot the host for the change to take effect.

Incorrect networking settings can cause loss of network connectivity, and a XenServer host may become inaccessible via XenCenter or remote SSH. Emergency Network Reset provides a simple mechanism to recover and reset a host's networking.

This feature is available from the Command Line Interface (CLI) using the xe-reset-networking command and within the Network and Management Interface section of xsconsole.

Incorrect settings which could cause a loss of network connectivity could include renaming network interfaces, creating bonds or VLANs, or mistakes when changing the management interface (for example, entering the wrong IP address). In addition, you may want to run this utility if a rolling pool upgrade, manual upgrade, hotfix installation or driver installation causes a lack of network connectivity, or if a Pool master or host in a resource pool is unable to contact with other hosts.

This utility should only be used in an emergency as it will remove the configuration for all PIFs, Bonds, VLANs and tunnels associated with the host. Guest Networks and VIFs are preserved. As part of this utility, VMs will be shutdown forcefully, where possible before running this command, VMs should be cleanly shutdown. Before applying a reset, users can make changes to the management interface and specify which IP configuration, DHCP or Static, should be used.

If the Pool Master requires a network reset, it must be carried out before a network reset of any other pool members. It should then be followed a network reset on all remaining hosts in the pool to ensure that the pool's networking configuration is homogeneous. This is a particularly important factor for XenMotion.

Note

If the Pool Master's IP address (the management interface) changes, as a result of a network reset or xe host.management_reconfigure, you must also apply the network reset command to other hosts in the pool, so that they can reconnect to the Pool Master on its new IP address. In this situation, the IP address of the Pool Master must be specified.

Network reset is NOT supported if High Availability (HA) is enabled. To reset network configuration in this scenario, you must first manually disable HA, and then run the network reset command.

After specifying the configuration mode to be used after the network reset, xsconsole and the CLI will display the settings which will be applied after host reboot. This offers a final chance to make any modifications before applying the emergency network reset command. After reboot, the new network configuration can be verified in XenCenter and xsconsole. In XenCenter, with the host selected, click the Networking tab, this displays the new network configuration. In xsconsole, this information is displayed in the Network and Management Interface section.

Note

Emergency Network Reset should also be applied on other pool members to replicate bonds, VLANs or tunnels from the Pool Master's new configuration.

The following table shows the available optional parameters which can be used with the xe-reset-networking command.

Warning

Users are responsible for ensuring the validity of parameters for the xe-reset-networking command, check the parameters carefully. If invalid parameters are specified, network connectivity and configuration will be lost. In this situation, Citrix advises customers to re-run the command xe-reset-networking without using any parameters.

Resetting the networking configuration of a whole pool must begin on the Pool Master, and should then be followed by network reset on all remaining hosts in the pool.

ParameterRequired/OptionalDescription
-m,  --master OptionalIP address of the Pool Master's management interface. Defaults to the last known Pool Master's IP address.
--deviceOptionalDevice name of the management interface. Defaults to the device name specified during installation.
--mode=staticOptional

Enables the following four networking parameters for static IP configuration for the management interface. If not specified, networking will be configured using DHCP.

--ipRequired if mode=staticIP address for the host's management interface. Only valid if mode=static.
--netmaskRequired if mode=staticNetmask for the management interface. Only valid if mode=static.
--gatewayOptionalGateway for the management interface. Only valid if mode=static.
--dnsOptionalDNS Server for the management interface. Only valid if mode=static.

Examples of commands that could be applied on a Pool Master:

To reset networking for DHCP configuration: 

xe-reset-networking

To reset networking for Static IP configuration: 

xe-reset-networking --mode= static --ip=ip-address \ 
  --netmask=netmask --gateway=gateway \ 
  --dns=dns

To reset networking for DHCP configuration if another interface became the management interface after initial setup: 

xe-reset-networking --device=device-name

To reset networking for Static IP configuration if another interface became the management interface after initial setup: 

xe-reset-networking --device=device-name --mode=static \ 
  --ip=ip-address --netmask=netmask \ 
  --gateway=gateway --dns=dns

All previous examples also apply to pool members. Additionally the Pool Master's IP address can be specified (which will be necessary if it has changed.)

To reset networking for DHCP configuration: 

xe-reset-networking

To reset networking for DHCP if the Pool Master's IP address was modified: 

xe-reset-networking --master=master-ip-address 

To reset networking for Static IP configuration, assuming the Pool Master's IP address didn't change: . 

xe-reset-networking --mode=static --ip=ip-address --netmask-netmask \ 
  --gateway=gateway --dns=dns 

To reset networking for DHCP configuration if the management interface and the Pool Master's IP address was modified after initial setup: . 

xe-reset-networking --device=device-name --mastermaster-ip-address 

Prev Up Next
Managing Networking Configuration Home Chapter 5. Storage