HP BL680c XenServer Administrator's Guide 4.1.0 - Page 52

Recovering from a bad network configuration

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 52 highlights

Networking $ xe pif-param-set uuid= other_config:ethtool-tx=off Finally, re-plug the PIF or reboot the host for the change to take effect. 4.4.2. Recovering from a bad network configuration In some cases it is possible to render networking unusable by creating an incorrect configuration. This is particularly true when attempting to make network configuration changes on a member XenServer Host. If a loss of networking occurs, the following notes may be useful in recovering and regaining network connectivity: • It is recommended that you ensure networking configuration is set up correctly before creating a resource pool, as it is usually easier to recover from a bad configuration in a non-pooled state. • The host-management-reconfigure and host-management-disable commands affect the XenServer Host on which they are run and so are not suitable for use on one host in a pool to change the configuration of another. Run these commands directly on the console of the XenServer Host to be affected, or use the xe -s, -u, and -pw remote connection options. • When the xapi service starts, it will apply configuration to the management interface first. The name of the management interface is saved in the /etc/xensource-inventory file. In extreme cases, you can stop the xapi service by running service xapi stop at the console, edit the inventory file to set the management interface to a safe default, and then ensure that the ifcfg files in /etc/sysconfig/network-scripts have correct configurations for a minimal network configuration (including one interface and one bridge; for example, eth0 on the xenbr0 bridge). 46

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
Networking
46
$ 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.
4.4.2. Recovering from a bad network configuration
In some cases it is possible to render networking unusable by creating an incorrect configuration. This is
particularly true when attempting to make network configuration changes on a member XenServer Host.
If a loss of networking occurs, the following notes may be useful in recovering and regaining network con-
nectivity:
•
It is recommended that you ensure networking configuration is set up correctly before creating a resource
pool, as it is usually easier to recover from a bad configuration in a non-pooled state.
•
The
host-management-reconfigure
and
host-management-disable
commands affect the XenServer
Host on which they are run and so are not suitable for use on one host in a pool to change the configuration
of another. Run these commands directly on the console of the XenServer Host to be affected, or use the
xe
-s, -u, and -pw remote connection options.
•
When the xapi service starts, it will apply configuration to the management interface first. The name of the
management interface is saved in the
/etc/xensource-inventory
file. In extreme cases, you can
stop the xapi service by running
service xapi stop
at the console, edit the inventory file to set the man-
agement interface to a safe default, and then ensure that the
ifcfg
files in
/etc/sysconfig/net-
work-scripts
have correct configurations for a minimal network configuration (including one interface
and one bridge; for example, eth0 on the xenbr0 bridge).