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

VMware, Inc. 115

Chapter 5 Configuring vCenter Server Heartbeat

Configuring the Machine Identity

To change the machine identity

1Click the Machine tab and select a Physical Hardware Identity for the local machine.

2Click Next or Finish.

Configuring the Server Role

To change the server role, click the Machine tab, select the Current Role of the local machine, and click Next

or Finish.

Configuring the Client Connection Port

Clients such as the vCenter Server Heartbeat Console use the Client Connection Port to connect to vCenter

Server Heartbeat. Do not change this port unless another application is using it. To change the Client

Connection Port, click the Machine tab, edit the default entry (52267) and click Next or Finish.

Configuring Channel IP Routing

Channel IP routing defines the IP addresses used to communicate between the Primary and Secondary

servers. Each link has a pair of addresses, one for the Primary, and one for the Secondary.

To add an additional VMware Channel after installing the NICs and configuring them

1Click the Channel tab. Click Add Row to add the new IP addresses for both the Primary and Secondary

server to the VMware Channel IP Routing table.

2 Use the drop-down menu to view a list of available IP addresses on the local server.

CAUTION The machine Identity should only be changed when directed to do so by VMware Support or

when instructed to by a knowledge base article. vCenter Server Heartbeat is designed not to allow two

passive or two active servers to connect.

NOTE Before changing the role of the local server, verify that the other (remote) server in the pair is not already

performing the same role.

1 2 ... 110 111 112 113 114 115 116 117 118 119 120 ... 203 204

No comments

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