HP BL680c XenServer Administrator's Guide 4.1.0 - Page 51

Networking Troubleshooting

Page 51 highlights

Networking xe pif-forget uuid=1ef8209d-5db5-cf69-3fe6-0e8d24f8f518 xe pif-forget uuid=829fd476-2bbb-67bb-139f-d607c09e9110 4. Use the pif-introduce command to re-introduce the devices with the desired naming: xe pif-introduce device=eth0 host-uuid= mac=00:19:bb:2d:7e:7a xe pif-introduce device=eth1 host-uuid= mac=00:19:bb:2d:7e:8a 5. Use the pif-list command again to verify the new configuration: xe pif-list params=uuid,device,MAC 6. Use the pif-reconfigure-ip command to reset the management interface IP addressing configuration. See Chapter 5, Command line interface for details on the parameters of the pif-reconfigure-ip command. xe pif-reconfigure-ip uuid=728d9e7f-62ed-a477-2c71-3974d75972eb mode=dhcp 7. Use the host-management-reconfigure command to set the management interface to the desired PIF and re-enable external management connectivity to the host: xe host-management-reconfigure pif-uuid=728d9e7f-62ed-a477-2c71-3974d75972eb 4.4. Networking Troubleshooting 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. 4.4.1. Diagnosing network corruption Some models of network cards 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. Be aware that this 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: 45

  • 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
45
xe pif-forget uuid=1ef8209d-5db5-cf69-3fe6-0e8d24f8f518
xe pif-forget uuid=829fd476-2bbb-67bb-139f-d607c09e9110
4.
Use the
pif-introduce
command to re-introduce the devices with the desired naming:
xe pif-introduce device=eth0 host-uuid=<host UUID> mac=00:19:bb:2d:7e:7a
xe pif-introduce device=eth1 host-uuid=<host UUID> mac=00:19:bb:2d:7e:8a
5.
Use the
pif-list
command again to verify the new configuration:
xe pif-list params=uuid,device,MAC
6.
Use the
pif-reconfigure-ip
command to reset the management interface IP addressing configuration.
See Chapter 5,
Command line interface
for details on the parameters of the
pif-reconfigure-ip
com-
mand.
xe pif-reconfigure-ip uuid=728d9e7f-62ed-a477-2c71-3974d75972eb mode=dhcp
7.
Use the
host-management-reconfigure
command to set the management interface to the desired
PIF and re-enable external management connectivity to the host:
xe host-management-reconfigure pif-uuid=728d9e7f-62ed-a477-2c71-3974d75972eb
4.4. Networking Troubleshooting
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.
4.4.1. Diagnosing network corruption
Some models of network cards 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. Be aware that this 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: