Portal Home > Knowledgebase > VMware Knowledge Base > Configuring vCenter Server Support Tools to work in a Wide Area Network

Configuring vCenter Server Support Tools to work in a Wide Area Network

Purpose

This article provides steps to configure vCenter Server Support Tools to work in a Wide Area Network (WAN) when protected by vCenter Server Heartbeat.

Resolution

When deployed in a WAN with different IP address on the servers in the cluster, you must perform additional configuration to allow vCenter Server Support Tools to operate properly.

To configure for vCenter Server Support Tools:
 
Note: Perform these steps immediately after vCenter Server Heartbeat installation with the Primary server active, the Secondary server passive, and the servers replicating.
  1. On the Secondary server, if VMware vSphere Authentication Proxy is installed, open the IIS Manager and change the IP bindings for the Computer Account Management Web Site. By default this runs on the Primary Principal (Public) IP address and should be changed to the Secondary Principal (Public) IP address.

  2. Restart the World Wide Web Publishing Service (W3SVC).

  3. On the Primary server, for each of the vCenter Support Tools installed, edit these .xml files by replacing the IP address with the Service Fully Qualified Domain Name (FQDN) in the   node:

    Component NameFile Name
    VMware vSphere Autodeployvmconfig-autodeploy.xml
    vSphere Authentication Proxyvmconfig-cam.xml
    extension.xml (in the  item), parameter.js (in the )
    VMware Syslog Collectorvmconfig-syslog.xml
    VMware ESXi Dump Collectorvmconfig-netdump.xml


    Note: The .xml files can be found in CSIDL_COMMON_APPDATA\VMware\ directory. For example:
    • On Windows 2008, the directory is C:\ProgramData\VMware\.
    • On Windows 2003, the directory is C:\Documents and Settings\All Users\Application Data\VMware\.

  4. Configure VMware Auto Deploy:

    1. Navigate to the Auto Deploy install location (this can be found in HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\ “InstallPath”) and run the command:

      autodeploy-register.exe --register --address=FQDN --user=username --password=password --force --setupfile=autodeploy_setup_file

      Note: The autodeploy_setup_file is the .xml file modified in step 3.

  5. Configure VMware ESXi Dump Collector (Netdump), VMware vSphere Authentication Proxy and VMware Syslog Collector:

    1. Launch a web browser and navigate to http:///mob
    2. Click Content.
    3. Click Extension Manager.

  6. In the Properties pane, identify the value extensionlist[]:

    Componentextension_name
    VMware ESXi Dump Collector (Netdump)com.vmware.netdump
    VMware vSphere Authentication Proxycom.vmware.cam.
    VMware Syslog Collectorcom.vmware.syslog


  7. For the component VMware ESXi Dump Collector (Netdump):

    1. In the Methods pane, click the Update Extension option. A new window appears.
    2. Paste this script in the Value field, overwriting the existing one:

      Note: The extension_name is c om.vmware.netdump.




      Describes the configuration of the Network Coredump Server

      com.vmware.netdump
      VMware, Inc.
      1.0.0


      http://*:8000/extension.xml


      Describes the configuration of the Network Coredump Server

      VMware, Inc.
      com.vmware.vim.viClientScripts

      noreply@vmware.com



      2011-06-29T09:20:17.129999Z


    3. Click Invoke Method. The response should be:

      Method Invocation Result: void

  8. For the component VMware vSphere Authentication Proxy:
    1. In the Methods pane, click the UpdateExtension option. A new window appears.
    2. Paste this script in the Value field, overwriting the existing one:

      Note: The extension_name is com.vmware.cam..

      Important: For VMware vSphere Authentication Proxy, the .xml script below must be updated with the extension name identified in step 6 , namely the  tag. Additionally, change the  and node values if you are not using the default values.




      Support joining ESXi server to Active Directory Domain

      com.vmware.cam.PUBLIC_SERVICE_NAME
      VMware, Inc.
      1.0.0


      http://*:51914/extension.xml


      Support joining ESXi server to Active Directory Domain

      VMware, Inc.
      com.vmware.vim.viClientScripts

      noreply@vmware.com



      2011-06-29T09:37:29.41Z


    3. Click Invoke Method. The response should be:

      Method Invocation Result: void

  9. For the component VMware Syslog Collector:

    1. In the Methods pane, click the UpdateExtension option. A new window appears.
    2. In the Value field, paste this script:

      Note: The extension_name is com.vmware.syslog.




      Describes the configuration of the remote syslog collector service

      com.vmware.syslog
      VMware, Inc.
      1.0.0


      http://*:8001/extension.xml


      Describes the configuration of the remote syslog collector service

      VMware, Inc.
      com.vmware.vim.viClientScripts

      noreply@vmware.com



      2011-06-29T09:22:39.789999Z

    3. Click Invoke Method. For each method, the response should be:

      Method Invocation Result: void

  10. Restart the vSphere Client and verify that all the extensions are operating properly.

Based on VMware KB 2004376

Also Read

Language: