VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Specifications download pdf (Page 189)

VMware, Inc. 189

Chapter 13 Troubleshooting

During installation, vCenter Server Heartbeat configures the VMware Channel NICs with user-provided

information. Incorrect information or incorrectly modifying the VMware Channel NIC configuration after

installation causes the VMware Channel to fail communicating.

On rare occasions, if the Primary and Secondary servers have NICs of the same type in a different order, both

the name and IP address of a VMware Channel NIC on the Primary server can transfer to the Principal (Public)

NIC on the Secondary or the name and IP address of the Principal (Public) NIC can transfer to a VMware

Channel NIC. Similarly, the names of the VMware Channel NICs can reverse on the Secondary server. You

must reconcile the names of the NICs with their physical identities and assign the correct IP address to each

NIC on the Secondary server.

Resolutions

The installation process manually assigns the correct IP addresses to each NIC on the Secondary server. If no

VMware Channel connection occurs between the servers, verify the configuration of the IP addresses on the

Secondary server's channel NICs. Check the settings for the Principal (Public) NIC. The configuration error can

remain unrecognized until you perform a switchover or a failover occurs.

To capture the identities of all of the NICs on the Secondary server prior to installing vCenter Server Heartbeat,

open a Windows Command Prompt on that server and execute the following command:

ipconfig /all > ipconfig.txt

The output of this command saves the name, TCP/IP configuration, and MAC address of each NIC on the

Secondary server to a file called ipconfig.txt, which is present on that server after the PnP phase of the vCenter

Server Heartbeat install completes. Compare the pre-install and post-install state of each NIC by running

ipconfig /all from a Windows command prompt and compare the output of this command with the

content of ipconfig.txt.

The MAC address of each NIC is connected to the physical identity of each card and never changes. You can

identify each NIC by its MAC address and determine its original name and network configuration, even if this

was updated by the PnP process.

VMware vCenter Server Heartbeat Packet Filter Is Enabled on the Channel

NIC(s)

Proper configuration requires that the packet filter be disabled on the VMware Channel NIC. When the packet

filter is enabled on the channel NICs, the following symptoms are encountered.

Symptom

Interference with network traffic across the VMware Channel results in an intermittent channel connection or

no channel connection at all.

Cause

During installation, the VMware vCenter Server Heartbeat Packet Filter is installed and enabled on all NICs

on both the Primary and Secondary servers. The Packet Filter on the VMware Channel NICs on each server is

disabled later in the installation of vCenter Server Heartbeat. If the vCenter Server Heartbeat Packet Filter is

left enabled on one or more channel NICs after installation completes, it can interfere with network traffic

across the VMware Channel.

Resolution

Click the Properties tab for each Channel NIC on both servers and verify that the check box for vCenter Server

Heartbeat Packet Filter is cleared, so that the Packet Filter is disabled on that NIC.

1 2 ... 184 185 186 187 188 189 190 191 192 193 194 ... 203 204

Comments to this Manuals

No comments

VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Specifications Page 189

Comments to this Manuals

Related products and manuals for Servers VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1