VMware vRealize Operations Federation Management Pack | 17 OCT 2019 | Build 14844882

What's in the Release Notes

The release notes cover the following topics:

Introduction

With vRealize Operations Federation Management Pack 1.1.1 you can unify your multi-site vRealize Operations Manager deployments into a single pane of glass. You can instantiate a deployment of vRealize Operations Manager with the capability of receiving key metrics for specified objects from other vRealize Operations Manager deployment in your environment.

What's New

The vRealize Operations Federation Management Pack 1.1.1 has been upgraded to use the SDK of vRealize Operations Manager 8.0. There are no enhancements in the functionality of this Management Pack.

Compatibility

For compatibility between products, please refer to the VMware Product Interoperability Matrices.

Resolved Issues

  • When you are navigating to Federation Alerts, an error is displayed

    When you are navigating to Federation Alerts, the following error occurs:
    "Error connecting to vROps instance ..."
    Federation Solution 1.0.1 has authentication issue if the adapter instance is configured with a username containing Non-ASCII characters.

    Workaround:
    Configure Federation adapter instance with a username, which does not contain Non-ASCII characters.

  • The Federation Adapter is not able to retrieve cluster tags

    The OOTB dashboard does not display the cluster tags as the adapter cannot retrieve cluster tags.

Known Issues

  • Metrics/properties from the latest federation_config.xml does not collect data for the child vRealize Operation 6.7 earlier versions

    Metrics have been eliminated or renamed starting from vRealize Operations 6.7 later versions. If you monitor vRealize Operations 6.7 earlier versions with the latest federation config xml (with changed metric keys), the new metrics for these instances do not collect data. As a result, in the Out-of-the-Box contents like Dashboards, the new metrics for the vRealize Operations 6.7 earlier versions will not have any value.

    Workaround:
    To collect the old metrics from the vRealize Operations 6.7 earlier versions, use the specific federation config xml that contains metric keys specific to that vRealize Operations.

  • The Federation adapter instance collection status displays an error and the properties are not published

    The Federation adapter cannot retrieve properties from a child vRealize Operations Manager of version 6.7 with a read-only access. The Federation adapter log contains "AuthException: API call failed, reason = 403.
    Note: In the earlier version of vRealize Operations 7.0, "administration.api_access" was required. However, from vRealize Operations 7.0 only, "administration.api.read_access" permission is required for retrieving remote resource data.

    Workaround:
    Configure Federation adapter instance with a user who has higher privileges.

  • Metrics/properties that do not exist in the pre-upgraded vRealize Operations setup does not collect data.

    After you upgrade the vRealize Operations to 6.7 or later releases, the Federation adapter does not collect the metrics/properties that did not exist in the pre-upgraded vRealize Operations setup.

    Workaround:
    Restart the Federated Cluster

  • Accumulative summary results do not include the data for the child vRealize Operations 6.7 earlier instances

    Many of the metric-keys have been eliminated/changed in vRealize Operations 6.7. When customers use the latest federation adapter to monitor the earlier instances of vRealize Operations 6.7 with the latest federation config xml (containing the latest metric-keys), the data from these instances will not be collected. As a result, in the Out-of-the-Box dashboards where the accumulative metric values are presented, the metrics for the earlier instances of vRealize Operations 6.7 will not be included.

    Workaround:
    None

check-circle-line exclamation-circle-line close-line
Scroll to top icon