Citrix XenServer 6.0.2 Emergency Network Reset Published Wednesday, 29 February 2012 1.0 Edition
Citrix XenServer 6.0.2 Emergency Network Reset Copyright 2012 Citrix Systems. Inc. All Rights Reserved. Version: 6.0.2 Citrix, Inc. 851 West Cypress Creek Road Fort Lauderdale, FL 33309 United States of America Disclaimers This document is furnished "AS IS." Citrix, Inc. disclaims all warranties regarding the contents of this document, including, but not limited to, implied warranties of merchantability and fitness for any particular purpose. This document may contain technical or other inaccuracies or typographical errors. Citrix, Inc. reserves the right to revise the information in this document at any time without notice. This document and the software described in this document constitute confidential information of Citrix, Inc. and its licensors, and are furnished under a license from Citrix, Inc. Citrix Systems, Inc., the Citrix logo, Citrix XenServer and Citrix XenCenter, are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. All other trademarks and registered trademarks are property of their respective owners. Trademarks Citrix XenServer XenCenter
Contents Resetting XenServer Networking Configuration in an Emergency... 1 Verifying the Network Reset... 1 Using the CLI for Network Reset... 2 Pool Master Command Line Examples... 2 Pool Member Command Line Examples... 3 iii
Resetting XenServer Networking Configuration in an Emergency 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 Primary 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 Primary 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. Verifying the Network Reset 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. 1
Using the CLI for Network Reset 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 Parameter Required/Optional Description -m, --master Optional IP address of the Pool Master's primary management interface. Defaults to the last known Pool Master's IP address. --device Optional Device name of the primary management interface. Defaults to the device name specified during installation. --mode=static Optional Enables the following four networking parameters for static IP configuration for the primary management interface. If not specified, networking will be configured using DHCP. --ip Required if mode=static --netmask Required if mode=static IP address for the host's primary management interface. Only valid if mode=static. Netmask for the primary management interface. Only valid if mode=static. --gateway Optional Gateway for the primary management interface. Only valid if mode=static. --dns Optional DNS Server for the primary management interface. Only valid if mode=static. Pool Master Command Line Examples 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 primary management interface after initial setup: xe-reset-networking --device=<device-name> To reset networking for Static IP configuration if another interface became the primary management interface after initial setup: 2
xe-reset-networking --device=<device-name> --mode=static \ --ip=<ip-address> --netmask=<netmask> \ --gateway=<gateway> --dns=<dns> Pool Member Command Line Examples 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 primary management interface and the Pool Master's IP address was modified after initial setup: xe-reset-networking --device=<device-name> --master<master-ip-address> 3