Remove dependency for FQDN as suffix in Account Name when configuring NSX-T account in VMware Aria Operations

[bhumitra]

Code of Conduct

• I have read and agree to the project's Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Encountered When?

When you setup HRM for the first time and if the name of the cloud account configured for NSX-T does not include the FQDN of NSX Manager, then the NSX related data will not show up on dashboards. Hence you must follow the below steps to resolve this issue.

Description

For the python script to send data to vRealize Operations, it is needed that the name of the cloud account configured for NSX-T must include the FQDN of NSX Manager. e.g if your name is NSX MGMT Domain, then it needs to be updated to NSX MGMT Domain - sfo-m01-nsx01.sfo.rainpole.io where sfo-m01-nsx01.sfo.rainpole.io is the FQDN of NSX Manager.

If the name of the cloud account already has FQDN, then you don't need to do anything.

Updating the name can be performed by:

1. Log in to the vRealize Operations Manager operations interface at https://<vrealize_operations_manager_fqdn>​ with a user assigned the Administrator​ role.
2. On the left pane navigate to Data Sources > Integrations
3. Expand NSX-T, and select the Management Domain account from the list.
4. On the Add Account - NSX-T page, update the Name by adding the FQDN as suffix.
   e.g if your name is NSX MGMT Domain, then it needs to be updated to NSX MGMT Domain - sfo-m01-nsx01.sfo.rainpole.io where sfo-m01-nsx01.sfo.rainpole.io is the FQDN of NSX Manager.
5. Click Save
6. Repeat the above steps for Workload Domain NSX account as well.

Below is an example of how the name should look like.

Use Case(s)

When running send-data-to-vrops.py python script, above steps are needed so that the script can send data to NSX objects on vRealize Operations.

Potential Configuration

No response

References

No response

[tenthirtyam]

Any update on this item @bhumitra ?

[bhumitra]

No update yet. A customer will still have to follow the workaround as mentioned in the description.