Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Pre-Upgrade Check for Potential Edge Gateway Upgrade Problems (2058977)

Details

Any upgrade of a vCloud Director 5.1.x release to vCloud Director 5.5 has the potential to cause one or more of the system's Edge Gateways to fail the upgrade procedure and log a message of the form:

Cannot upgrade vCloud Director to 5.5: Found 1 gateways backed by unsupported edge version. Please redeploy gateways or reset vApp networks backed by edge and then run upgrade again.

Redeploying the Edge Gateway does not solve this problem. To avoid it, you must query the vCloud Director database before you begin upgrading vCloud Director to determine whether any of your Edge Gateways are configured in a way that will cause this problem. If you find any problem configurations, you can run additional database operations that remove these Edge Gateways from the database (and the system).

Solution

  1. Run the following database query before you begin the upgrade:

    SELECT name, id FROM gateway WHERE backing_ref is null AND is_deployed = 1;


    Edge Gateways returned by this query will fail the upgrade procedure. In the typical case, these Edge Gateways are a result of a system in which vShield Manager had been upgraded in a previous release but one or more of the Edge Gateways had not been subsequently upgraded. If this query does no return any results, you do not need to run the remaining steps in this procedure.

  2. To discover whether a vShield Edge exists for each of the Edge Gateways returned by the query in Step 1, run the following database query:

    select gateway.name, gateway.id, portgroup_moref from gateway_interface join gateway on gateway_interface.gateway_id = gateway.id and gateway_interface.interface_type = 1 join logical_network on gateway_interface.logical_network_id = logical_network.id join real_network on logical_network.rnet_id = real_network.id where gateway.backing_ref is null AND gateway.is_deployed = 1;

  3. If a single portgroup moref is returned for an edge gateway by the query in Step 2, verify whether an edge for that portgroup exists in vShield Manager. If it exists, redeploy the Edge Gateway to upgrade the backing edge. Do this for all the Edge Gateways for which a single portgroup is returned by the query in Step 2.

  4. Run the query from Step 1 again:

    SELECT name, id FROM gateway WHERE backing_ref is null AND is_deployed = 1;

    At this point, the query will return only those edge gateways that were created incorrectly and are unusable. Execute the following SQL statements to delete these gateways from the database:

    delete from gateway_assigned_ip where gateway_interface_id in (select gateway_interface.id from gateway_interface inner join gateway on gateway.id = gateway_interface.gateway_id where gateway.id in (SELECT id FROM gateway WHERE backing_ref is null AND is_deployed = 1));

    delete from gateway_assigned_mac where gateway_id in (SELECT id FROM gateway WHERE backing_ref is null AND is_deployed = 1);

    delete from gateway_interface where gateway_id in (SELECT id FROM gateway WHERE backing_ref is null AND is_deployed = 1);

    delete from gateway_logical_resource where fo_id in (SELECT id FROM gateway WHERE backing_ref is null AND is_deployed = 1);

    delete from gateway where id in (SELECT id FROM gateway WHERE backing_ref is null AND is_deployed = 1);
 
 
 
 
 

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 3 Ratings
Actions
KB: