Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
vsp_41_esx_server_config.pdf
Скачиваний:
10
Добавлен:
06.02.2016
Размер:
2.67 Mб
Скачать

ESX Configuration Guide

Troubleshooting

You might encounter host networking issues that require troubleshooting. In many cases, host networking can be restored with only a few configuration changes.

Troubleshooting Service Console Networking

If certain parts of the service console’s networking are misconfigured, you cannot access your ESX host with the vSphere Client.

If your host’s service console loses network connectivity, you can reconfigure networking by connecting directly to the service console and using service console commands.

nesxcfg-vswif -l

Provides a list of the service console’s current network interfaces. Check that vswif0 is present and that the current IP address and netmask are correct.

nesxcfg-vswitch -l

Provides a list of the current virtual switch configurations. Check that the uplink adapter configured for the service console is connected to the appropriate physical network.

nexscfg-nics -l

Provides a list of the current network adapters. Check that the uplink adapter configured for the service console is up and that the speed and duplex are both correct.

nesxcfg-nics -s <speed> <nic>

Changes the speed of a network adapter.

nesxcfg-nics -d <duplex> <nic>

Changes the duplex of a network adapter.

nesxcfg-vswif -I <new ip address> vswifX

Changes the service console’s IP address.

nesxcfg-vswif -n <new netmask> vswifX

Changes the service console’s netmask.

nesxcfg-vswitch -U <old vmnic> <service console vswitch>

Removes the uplink for the service console.

nesxcfg-vswitch -L <new vmnic> <service console vswitch>

Changes the uplink for the service console.

If you encounter long waits when using esxcfg-* commands, DNS might be misconfigured. The esxcfg-* commands require that DNS be configured so that localhost name resolution works properly. This requires that the /etc/hosts file contain an entry for the configured IP address and the 127.0.0.1 localhost address.

Rename Network Adapters by Using the Service Console

If you lose service console connectivity after adding a new network adapter, you must use the service console to rename the affected network adapters. Adding a new network adapter can cause loss of service console connectivity and manageability by using the vSphere Client because of network adapters are renamed.

Procedure

1Log in directly to the ESX host’s console.

74

VMware, Inc.

Chapter 6 Networking Best Practices, Scenarios, and Troubleshooting

2Use the esxcfg-nics -l command to see which names are assigned to the network adapters.

3Use the esxcfg-vswitch -l command to see which vSwitches are now associated with device names no longer shown by esxcfg-nics.

4Use the esxcfg-vswitch -U <old vmnic name> <vswitch> command to remove any network adapters that were renamed.

5Use the esxcfg-vswitch -L <new vmnic name> <vswitch> command to add the network adapters again, giving them the correct names.

Troubleshooting Physical Switch Configuration

You might lose vSwitch connectivity when a failover or failback event occurs. This causes the MAC addresses that the virtual machines associated with that vSwitch to appear on a different switch port.

To avoid this problem, put your physical switch in PortFast or PortFast trunk mode.

Troubleshooting Port Group Configuration

Changing the name of a port group when virtual machines are already connected to that port group causes an invalid network configuration for the virtual machines that are configured to connect to that port group.

The connection from virtual network adapters to port groups is made by name, and the name is the identifier that is stored in the virtual machine configuration. Changing the name of a port group does not cause a mass reconfiguration of all the virtual machines connected to that port group. Virtual machines that are already powered on continue to function until they are powered off, because their connections to the network are already established.

Avoid renaming networks after they are in use. After you rename a port group, you must reconfigure each associated virtual machine by using the service console to reflect the new port group name.

VMware, Inc.

75

ESX Configuration Guide

76

VMware, Inc.

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]