6.6

Solution
The installation process manually assigns the correct IP addresses to each NIC on the Secondary node. If no
VMware Channel connection occurs between the nodes, verify the configuration of the IP addresses on the
Secondary's channel NICs. Check the settings for the Public NIC. The configuration error can remain
unrecognized until a failover occurs.
To capture the identities of all of the NICs on the Secondary prior to installing vCenter Server Heartbeat, open
a Windows Command Prompt on that node 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 to a file called ipconfig.txt, which is present on that node 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.
Incorrect or Mismatched Disk Configuration
When vCenter Server Heartbeat starts, it checks the complete set of file filters for consistency.
Problem
If any entry points to a non-existent drive letter or to a non-NTFS partition, the list of file filters resets to the
default value of C:\Protected\**. This is a safety measure as vCenter Server Heartbeat requires the same drive
letter configuration on the Primary and the Secondary nodes, and only supports protection of NTFS partitions.
Cause
Different partition structures on Primary and Secondary nodes, such that one or more file filters point to drives
that cannot be protected on both nodes. For example:
■
The Primary has drive G:, a valid NTFS partition, but no corresponding drive exists on the Secondary.
■
The Primary has drive G:, a valid NTFS partition. The equivalent drive on the Secondary is a CD or DVD
drive, or a FAT or FAT32 partition that cannot be protected.
In either scenario, if you configure a file filter to protect a directory on drive G:, the entire filter set is rejected
and the filters are reset to the default value of <Windows drive>\Protected\**.
Solution
◆
Follow the steps documented in knowledge base article 1008458 – Troubleshooting a set of File Filters
that is reset to C:\Protected\**.
Passive Node Has Less Available Space than Active Node
Inadequate available disk space on the passive node can cause replication to cease.
Problem
Replication stops with the following error:
[N27]Failed to write information for the file: {filename} to the disk. Either the disk is full or the quota (for the SYSTEM account)
was exceeded.
84 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide