The VMware Cloud Foundation 2.3.2 health check reports the Uplink port connection status as RED when a custom L3 uplink configuration is used.
search cancel

The VMware Cloud Foundation 2.3.2 health check reports the Uplink port connection status as RED when a custom L3 uplink configuration is used.

book

Article ID: 316892

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

Symptoms:
  • When running the /opt/vmware/sddc-support/sos --health-check command, you see output similar to the following under the Network section:
+-----+----------------------+-----------------------------------------------------------------------------------+-------+
| SL# |         Area         |                                       Title                                       | State |
+-----+----------------------+-----------------------------------------------------------------------------------+-------+
|     |                      |                           Uplink port connection status                           |  RED  |
|     |                      |  VI : VMW-WLD1 : VLAN 3091 tagging status for network type EXTERNAL_CONNECTION    |  RED  |

Note: The preceding excerpts are only examples. Environmental variables may vary depending on your environment.
  • A custom L3 uplink configuration has been manually deployed on the TOR switches.


Environment

VMware Cloud Foundation 2.3.x

Cause

When a custom L3 uplink configuration is used, the sos utility is unable to accurately report on the health of the uplink configuration.

Resolution

To resolve this issue, use the following steps to update the sos utility.
  1. Download the attached 56518_sos-2.3.2-9032410.noarch.zip file.
  2. Use a file transfer utility to copy the 56518_sos-2.3.2-9032410.noarch.zip to the /tmp folder on the SDDC Manager Controller virtual machine.
  3. Log in to the SDDC Manager controller virtual machine as the root user.
  4. Issue the following command to extract the contents of the /tmp/56518_sos-2.3.2-9032410.noarch.zip file:
unzip -d /tmp/ /tmp/56518_sos-2.3.2-9032410.noarch.zip
  1. Issue the following command to install the updated sos utility:
rpm -Uhv /tmp/sddc-support-2.3.2-9032410.noarch.rpm
 
Note: You will see output similar to the following:
 
warning: /tmp/sddc-support-2.3.2-9032410.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID 8a6a826d: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:sddc-support-2.3.2-9032410       ################################# [ 50%]
Removed symlink /etc/systemd/system/multi-user.target.wants/sosrest.service.
/opt/vmware/sddc-support /
Start compiling all py files ...
[Tue Jul 3 14:59:35 UTC 2018]
Listing framework ...
Compiling framework/__init__.py ...

<output truncated for brevity>
Removing all py files ...
DONE
/
Created symlink from /etc/systemd/system/multi-user.target.wants/sosrest.service to /etc/systemd/system/sosrest.service.
Sddc support upgraded successfully
Cleaning up / removing...
   2:sddc-support-2.3.2-8245495       ################################# [100%]


Note: With the updated sos utility in place, the Uplink port connection status will not be displayed. The health of the VLAN tagging on the EXTERNAL_CONNECTION will be marked as YELLOW.


Attachments

56518_1_56518_sddc-2.3.2-9032410.noarch get_app