From the release 10.2.2,
DX NetOps Spectrumsupports multitenancy for
DX NetOps Spectrum-CA UIM integration that is configurable in the Spectrum Gateway (spectrumgtw) probe.
The Multitenancy model in CA UIM is based on the Origin tag (Ownership).
DX NetOps Spectrum-CA UIM integration leverages this origin tag information. The spectrumgtw probe allows you to map Origin with Landscape. Mapping CA UIM origins to
DX NetOps Spectrumlandscapes, ensures that the inventory belonging to a specific origin is modeled in the landscape it is mapped to.
To enable and configure multitenancy, you need to install spectrumgtw probe v8.64 on CA UIM 8.51 or 8.51 SP1 This capability is not supported by previous versions of the probe. You also need to deploy the webservices_rest package version 8.51 or later on the same robot where UMP is deployed.
The following diagram outlines the process to enable multitenancy in
DX NetOps Spectrum.
In deployments where there is a clear distinction in terms of CA UIM and
DX NetOps Spectruminstallation setups, i.e. one UIM hub and one SpectroSERVER per tenant (where the tenant has one origin), simply mapping origin to landscape is enough.
However, for deployments where there are multiple origins per tenant (with overlapping IP addresses that need to be modeled in same landscape), or where entities of multiple UIM tenants have to be modeled in the same landscape, you need to configure Secure Domain Connectors on the landscape and map the SDC + landscape combination to an origin.
The probe retrieves the list of origins in your CA UIM environment. You can then map your
DX NetOps Spectrumlandscapes to CA UIM origins.
While you can map multiple origins to the same landscape, the same origin cannot be mapped to multiple landscapes.
How multitenancy works in the
DX NetOps Spectrum-CA UIM integration
Once you manually map the origins to landscapes, using REST calls provided by
DX NetOps Spectrum, spectrumgtw probe sends the Origin to Landscape mapping. These mappings are sent to
DX NetOps Spectrumevery time
DX NetOps SpectrumOneClick server or spectrumgtw probe restarts. Once the mappings are in place, Spectrum ensures that entities belonging to an origin are modeled on the landscape, its origin is mapped to.
The spectrumgtw probe restarts every time you change mapping and save the configuration
When spectrumgtw probe gets alarms from
DX NetOps Spectrum, the probe determines the landscape for each alarm and fetches the corresponding origin (by checking against the mapping and filling the origin in the alarm) before sending it to CA UIM.
Until 10.2.2, at the most two UIM Event admin models were created (one in selected landscape and another in MLS if the selected SS is down) to handle alarms coming from CA UIM. When origins are mapped to landscapes then one UIM event Admin model is created per landscape as specified in the map. This allows the segregation of alarms into their respective landscapes.
Event models are created for alarms whose IP or hostname are not present in
DX NetOps Spectrum. In cases like overlapping IPs or duplicate hostnames, chances are that same event model is used as a place holder for asserting such alarms. Now origin in the alarm will be used to identify the correct event model to assert the alarm.
Configuring Multitenancy for
DX NetOps Spectrum-CA UIM Integration
To enable multitenancy, follow these steps:
- In the probe Admin Console, navigate to the spectrumgtw probe configuration interface/ GUI.
- In theUMP Connection Detailssection, enable theConfigure multitenancyoption, update the UMP details and save the configuration.The probe configuration interface displays theMultitenant Mappingnode.
- In theMultitenant Mappingnode >Landscape Mappingsection, clickNewto create a new landscape to origin mapping.
- Map CA UIM Origins toDX NetOps SpectrumLandscapes, from the list of options displayed and save the mapping changes.
- In the OneClick Administration web server, click the Administration tab and navigate to the UIM Configuration page.
- Update the integration configuration details, enable the integration(s).
- Test and Save integration.