vCloud Director Extender | 31 JAN 2019 | Build 1813450

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Resolved Issues

  • Providing an incorrect root password multiple times in an API does not lock the root account

    Using the API, you can provide an incorrect password for the Replicator or Replication manager multiple times without locking your root account. 
    This might expose potential security risk for brute force attacks.

Known Issues

  • NEW The configuration of network extension completes with status Dropped

    After the DC extension process completes, the tunnel appears with a Dropped status under the DC Extensions tab.

    If the cloud VDC edge contains two or more listener IP addresses, the first listener IP addresses is marked as the Primary address. When you configure a network extension, the vCloud Director Extender selects the Primary listener IP address. If the on-premise VDC edge cannot reach the Primary listener IP address, the network extension results in a Dropped state. 

    Workaround: Change the Primary listener IP address of the cloud VDC edge to an existing listener IP address.

    1. Contact and request the configuration files​.
      • ​​​​
      • vcdConfig
    2. Save the ​​​​​​​ file and the vcdConfig file in the same directory.
    3. Open and edit the values in the vcdConfig file by using a text editor.
      "vcdUrl": "<VCD IP>",
      "userName": "<Org Username>",
      "password": "<Org Password>",
      "uplinkIp": "<New VDC Edge Ip>",
      "edgeId": "<VCD Edge Id>",
      "orgName": "<Org Name>",
      "vcdVersion": "<Vcd Version>",
      "nsxOnPrem": <false/true>
    4. Save the updated vcdConfig file as a JSON file.
    5. Establish an SSH connection to the on-premise vCloud Director appliance, login as root, and navigate to the vCloud Director Extender mobility service.
    6. To verify that the updated configuration values are saved, run the command. 
      cat vcdConfig
      The uplinkIp address must match one of the listener IP addresses of the cloud VDC edge. 
      To verify the listener IP address of the edge, navigate to VDC Edge > Configure Services > VPN > L2VPN > Server Global > Listener IP drop down menu.
    7. To update the listener IP address for the network extension configuration, run the python script, and wait for 5 minutes for the script to complete.
      If you have an on-premise NSX Manager configured, you are prompted to enter the NSX Manager Edge IP address.
      Enter On-Prem NSX edge ip.
    8. Verify if the script execution completed successfully.
      • To verify that listener IP address is updated with the uplinkIp value from the vcdConfig file, refresh the DC Extensions tab. The status updates in about 5 minutes.
      • To verify that on-premise NSX Edge server IP address is updated, run the commands.
        ssh admin@<OnPrem-NsxEdgeIP> / Password: ‘VMware1!VMware1!’
        show configuration l2vpn
        Verify the listener IP address in the output JSON l2vpn > serverAddress.
      • To verify that the primary listener IP is updated, navigate to VDC Edge > Configure Services > VPN > L2VPN > Server Global > Primary Listener IP.
check-circle-line exclamation-circle-line close-line
Scroll to top icon