VMware vCenter Server Heartbeat - How to Configure Management IP Addressing and Routing

Follow

Summary

This Knowledgebase article provides information on how to configure a management IP address in a vCenter Server Heartbeat environment.


More Information

The management IP address for each server should be set up on a network card that is virtually or physically connected to the Principal (Public) network. This may be on the Principal (Public) network card itself or an additional network card when present. The management IP address should be a unique static IP address in a different subnet from the hosting server’s Principal (Public) address and should be unique to each server.

On Windows 2003, to allow the server to route successfully through the management address, it must be the first address specified on the card with all other Principal (Public) addresses acting as secondary addresses.

Procedure

To configure a management address:

  1. Open Network Connections .
  2. Right-click the required Principal (Public) network connection and click on Properties .
  3. Under the TCP/IP protocol, click Properties .
  4. The first IP address of the NIC is then displayed.
  5. Note the first IP address and then adjust the first IP address of the card to the management IP address.
  6. To add the Principal (Public) IP address (old first address) back in as a secondary address, click the Advanced button and click Add .

    Note: For Windows Server 2008, the order of addresses is unimportant.
  7. Specify the Principal (Public) address and clear the Register this connection in DNS check box from the DNS tab.
  8. Static DNS entries must now be added to the DNS server in order to maintain connectivity, as this was previously carried out dynamically. Please consult appropriate Microsoft Documentation on how to Add Static Host and PTR records as required.
  9. From a command prompt, run c:>route print to verify the main Principal (Public) IP address does not appear in the Interface column - only the MANAGEMENT address, addresses on other NICs, and 127.0.0.1 should appear in this column.

    Note: Normal TCP/IP troubleshooting commands can be used to verify connectivity, for example c:>ping 10.0.0.1


Applies To

All Versions


Related Information

None

KBID-1668

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.