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

  • Download
  • Add to my manuals
  • Print
  • Page
    / 204
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 180
VMware, Inc. 181
13
This chapter includes the following topics:
“Troubleshooting Unexpected Behaviors” on page 181
“Two Active Servers” on page 181
“Two Passive Servers” on page 183
“Synchronization Failures” on page 184
“Registry Status is Out of Sync” on page 186
“Channel Drops” on page 186
“Subnet or Routing Issues ” on page 190
“MaxDiskUsage Errors” on page 190
“MaxDiskUsage Error Messages” on page 191
Troubleshooting Unexpected Behaviors
The following unexpected behaviors illustrate symptoms, causes and resolution for a given scenario.
Two Active Servers
When two identical active servers are live on the same network, vCenter Server Heartbeat refers to the
condition as split-brain syndrome. Two active servers do not occur by design and when detected, must be
resolved immediately.
Symptoms
Split-brain syndrome is identified by the following symptoms:
Both servers in the pair are running and in an active state. The task bar icons display P / A (Primary and
active) and S / A (Secondary and active).
An IP address conflict occurs on a server pair running vCenter Server Heartbeat on the Principal (Public)
IP address.
A name conflict occurs on a server pair running vCenter Server Heartbeat. In a WAN environment the
Primary and Secondary servers connect to the network using different IP addresses. However, if the
servers are running with the same name and are visible to each other across the WAN, a name conflict
occurs.
Clients (for example, Outlook) cannot connect to the server running vCenter Server Heartbeat.
Troubleshooting
13
Page view 180
1 2 ... 176 177 178 179 180 181 182 183 184 185 186 ... 203 204

Comments to this Manuals

No comments