Multi-Subnet UFM

The Multi-Subnet UFM feature allows for the management of large fabrics, consisting of multiple sites, within a single product, namely Multi-Subnet UFM.

This feature is comprised of two layers: UFM Multi-Subnet Provider and UFM Multi-Subnet Consumer.

The UFM Provider functions as a Multi-Subnet Provider, exposing all local InfiniBand fabric information to the UFM consumer. On the other hand, the UFM Consumer acts as a Multi-Subnet Consumer, collecting and aggregating data from currently configured UFM Providers, enabling users to manage multiple sites in one place. While UFM Consumer offers similar functionality to regular UFM, there are several behavioral differences related to aggregation.

In /opt/ufm/files/conf/gv.cfg, fill in the section named [Multisubnet] for UFM Multi-Subnet Provider and Consumer.

To set up UFM as a MultI-Subnet Provider, perform the following:

  • Set multisubnet_enabled to true

  • Set multisubnet_role to provider

  • Set multisubnet_site_name (optional, if not set, it will be randomly generated); e.g., provider_1

  • Start UFM

To set up UFM as a Multi-Subnet Consumer, perform the following:

  • Set multisubnet_enabled to True

  • Set multisubnet_role to consumer

  • Start UFM

It is important to note that UFM Multi-Subnet Consumer can be configured on a machine or VM without an established InfiniBand connectivity. Additionally, users may customize UFM Provider and Consumer using optional configuration parameters found in the [Multisubnet] section of /opt/ufm/files/conf/gv.cfg.

  1. Following the initial launch of the Consumer, the Dashboard view is devoid of data, and a message containing a hyperlink leading to the Provider Management section is displayed.

    MULTI-SUBNET1-version-1-modificationdate-1707037689667-api-v2.png

    mullti-subnet1a-version-1-modificationdate-1707037680483-api-v2.png

  2. As shown in the below snapshot, a new section for Provider Management has been added, enabling users to configure UFM Providers.

    multi-subnet2-version-1-modificationdate-1707037689377-api-v2.png

    1. To add a provider, the user is required to enter its IP address and credentials. Unless there are multiple instances of UFM providers on a single machine, the advanced section parameters should be set with default values. However, if there are multiple instances, the advanced parameters may be set per Provider and then be configured in the Providers Management view.

      multi-subnet2a-version-1-modificationdate-1707037689107-api-v2.png

    2. By editing the Provider view, you can change Provider's credentials.

      multi-subnet2b-version-1-modificationdate-1707037688783-api-v2.png

    3. The "Delete Provider" function removes the selected Provider from the Consumer. Please note that this action may take some time to complete, and changes may only be reflected in the view after approximately 30 seconds.

      multi-subnet2c-version-1-modificationdate-1707037688547-api-v2.png

  3. A general filter has been added to the top right corner of the page, enabling users to filter displayed data by site.

    multi-subnet3-version-1-modificationdate-1707037688187-api-v2.png

    multi-subnet3a-version-1-modificationdate-1707037687907-api-v2.png

    multi-subnet3b-version-1-modificationdate-1707037687593-api-v2.png

    multi-subnet3c-version-1-modificationdate-1707037687233-api-v2.png

  4. Network map contains “clouds” for each provider.

    multi-subnet4-version-1-modificationdate-1707037686903-api-v2.png

    multi-subnet4a-version-1-modificationdate-1707037686563-api-v2.png

  5. A "Site Name" column is present in all Managed Elements sections. The column is disabled (hidden) by default.

    multi-subnet5a-version-1-modificationdate-1707037686020-api-v2.png

    multi-subnet5-version-1-modificationdate-1707037686267-api-v2.png

    multi-subnet5b-version-1-modificationdate-1707037685687-api-v2.png

  6. The "Group" and "Telemetry" sections include "Site" filters.

    multi-subnet6-version-1-modificationdate-1707037685353-api-v2.png

  7. The filter in "Groups" impacts the Members table only.

    multi-subnet7a-version-1-modificationdate-1707037684797-api-v2.png

    multi-subnet7-version-1-modificationdate-1707037685067-api-v2.png

  8. In the System Health tab, subsections for Consumer and Provider are available.

    1. Consumer System Health tab contains sections applicable to Consumer UFM specifically (e.g., logs from Consumer UFM).

      ulti-subnet8a-version-1-modificationdate-1707037682527-api-v2.png

    2. Provider System Health contains sections applicable to one or multiple providers (e.g., Fabric Health Report can be triggered on multiple Providers from the Consumer).

      ulti-subnet8b-version-1-modificationdate-1707037682203-api-v2.png

  9. UFM Health tab contains sub report tables for each provider.

    multi-subnet9-version-1-modificationdate-1707037684477-api-v2.png

  10. Fabric Health contains sub report tables for each provider.

    multi-subnet10-version-1-modificationdate-1707037684137-api-v2.png

  11. Daily Reports:

    1. Consumer Daily reports display consumer reports.

      ulti-subnet11a-version-1-modificationdate-1707037681917-api-v2.png

    2. Providers Daily reports display reports from all providers.

      ulti-subnet11b-version-1-modificationdate-1707037681633-api-v2.png

  12. The "Fabric Validation" tab contains sub report tables for each provider.

    ulti-subnet12-version-1-modificationdate-1707037681237-api-v2.png

  13. In "UFM Logs" Tab:

    1. Consumer logs:

      ulti-subnet13a-version-1-modificationdate-1707037680890-api-v2.png

    2. Providers logs display providers log separately, displaying logs for all providers is not supported.

      mullti-subnet13b-version-1-modificationdate-1707037690037-api-v2.png

  14. In the "System Dump" tab:

    1. "Consumer System Dump" collects system dump for consumer

      multi-subnet14b-version-1-modificationdate-1707037683550-api-v2.png

    2. "Providers System Dump" collect system dumps for one or all providers and mergeS them into one folder

      multi-subnet14a-version-1-modificationdate-1707037683843-api-v2.png

  15. Under "Settings", subsections for Consumer and Provider are available.

    1. "Consumer Settings" contain sections applicable to Consumer UFM specifically (e.g., creation of access tokens for UFM consumer authentication);

      multi-subnet15b-version-1-modificationdate-1707037682917-api-v2.png

    2. "Provider Settings" contain sections applicable to one or multiple providers (e.g., Event Policies can be changed for multiple Providers at once from the Consumer).

      multi-subnet15a-version-1-modificationdate-1707037683253-api-v2.png

© Copyright 2023, NVIDIA. Last updated on Feb 8, 2024.