Tenant-Agnostic Data Collectors

In a standard tenant deployment, each tenant has a dedicated Data Collector. For multiple tenants that reside in the same IP routing space, capm can be configured to use fewer Data Collectors.
HID_Tenant-Agnostic-DC
In a standard tenant deployment, each tenant has a dedicated Data Collector. For multiple tenants that reside in the same IP routing space,
DX NetOps Performance Management
can be configured to use fewer Data Collectors.
The following diagram illustrates the basic architecture of a tenant-agnostic Data Collector:
Multi-tenant Data Collector Architecture
Multi-tenant Data Collector Architecture
The Data Collector is associated with the proxy IP domain. This domain represents the IP domain of the managed environment, meaning that IP addresses must be unique across all tenants in the environment.
The IP proxy domain is the only new object to create this feature. You must create this object through REST.
Multiple IP domains are associated with the Data Collector within the proxy IP domain. Each IP domain is associated with a single tenant. The Data Collector sends requests to the managed devices defined in each tenant.
In this article:
2
Limitations
A tenant-agnostic Data Collector configuration has the following limitations:
  • IP addresses in tenant IP domains cannot overlap. IP addresses must be unique across all tenants.
    The owner of the environment is responsible for ensuring IP address uniqueness. Without unique IP addresses, tenants can monitor and manage devices that belong to other tenants. To ensure IP address uniqueness, enforce limited IP ranges in discovery profiles.
  • Devices cannot be migrated between tenants.
  • Existing tenant deployments cannot be migrated to tenant-agnostic Data Collectors.
  • Tenant-agnostic Data Collectors cannot host
    DX NetOps Mediation Manager
    (CAMM) or
    DX NetOps Virtual Network Assurance
    (VNA). For each tenant, a separate Data Collector is required for CAMM and VNA.
Configure the Data Collector Though REST
To configure a tenant-agnostic Data Collector, use REST to create the required items and associations. The following process uses
NetOps Portal
and Data Aggregator REST:
If you script these steps, account for synchronization time between steps. Synchronization can take up to 5 minutes.
3
Get Item IDs
Several item IDs are required to configure the Data Collector for multiple tenants. Get the item IDs before you begin configuration. Use the GET method with your preferred REST client for the following item IDs:
  • Data Collector ID
    http://
    da_host
    :8581/rest/dcms
  • Pseudo Tenant ID
    http://
    da_host
    :8581/rest/pseudotenants
    The pseudo tenant proxy (Pseudo Tenant Proxy) is predefined. The pseudo tenant works with the proxy IP domain to support multiple tenants and IP domains on a single Data Collector.
Configure the Data Collector
Configure the Data Collector to handle multiple tenants. Complete this procedure for each tenant-agnostic Data Collector.
For the bold IDs, use the IDs from the previous step.
Follow these steps:
  1. Create a proxy IP domain:
    • Method:
      POST
    • Endpoint:
      http://
      da_host
      :8581/rest/tenant/
      {pseudo_Tenant_ID}
      /proxyipdomains/
    • Body:
      <ProxyIPDomain version="0.0.0">
      <IPDomain version="0.0.0">
      <Name>
      Proxy IP Domain
      </Name>
      <Description>
      Description for Proxy IP Domain
      </Description>
      <DNSProxyEnabled>false</DNSProxyEnabled>
      <DNS1Address>0.0.0.0</DNS1Address>
      <DNS2Address>0.0.0.0</DNS2Address>
      <DNS1Port>0</DNS1Port>
      <DNS2Port>0</DNS2Port>
      </IPDomain>
      </ProxyIPDomain>
  2. Get and note the proxy IP domain ID:
    • Method:
      GET
    • Endpoint:
      http://
      da_host
      :8581/rest/proxyipdomains
  3. Associate the proxy IP domain with the Data Collector:
    • Method:
      PUT
    • Endpoint:
      http://
      da_host
      :8581/genericWS/dcm/
      {DataCollectorID}
    • Body:
      <DCM>
      <IP_DOMAIN_ID>
      {proxyDomainId}
      </IP_DOMAIN_ID>
      </DCM>
Add Tenants to the Proxy IP Domain
Create tenants and assign those tenants to the Data Collector. Complete this procedure once for each tenant.
For more information about the tenant and IP domain XML, see Automate Tenant Configuration with REST Web Services.
You can create the required tenants and the IP domains in those tenants, through the
NetOps Portal
UI. For more information see Manage Tenants and IP Domains. If you create these items in the UI, start this procedure from step 4.
Follow these steps:
  1. Create the tenant:
    • Method:
      POST
    • Endpoint:
      http://
      pc_host
      :8181/pc/center/webservice/tenants/
    • Body:
      <tenant>
      <tenantName>
      Tenant name
      </tenantName>
      <tenantDesc>
      Tenant description
      </tenantDesc>
      <accountIdentifier>
      AccountNumber
      </accountIdentifier>
      <status>Enabled</status>
      <removable>false</removable>
      <theme>CA-Blue</theme>
      <defaultCulture>en-US</defaultCulture>
      </tenant>
  2. Get and note the tenant ID:
    • Method:
      GET
    • Endpoint:
      http://
      pc_host
      :8181/pc/center/webservice/tenants/tenantName/
      tenant_name
  3. Create the tenant IP domain:
    • Method:
      POST
    • Endpoint:
      http://
      pc_host
      :8181/pc/center/webservice/domains/
    • Body:
      <domain>
      <itemDesc>
      IP domain description
      </itemDesc>
      <itemName>
      IP domain name
      </itemName>
      <TenantID>
      {tenantID}
      </TenantID>
      <primaryDNSAddress>0.0.0.0</primaryDNSAddress>
      <primaryDNSPort>0.0.0.0</primaryDNSPort>
      <secondaryDNSAddress>0.0.0.0</secondaryDNSAddress>
      <secondaryDNSPort>0.0.0.0</secondaryDNSPort>
      <isDnsProxyEnabled>false</isDnsProxyEnabled>
      </domain>
  4. Get the tenant IP domain ID:
    • Method:
      GET
    • Endpoint:
      http://
      da_host
      :8581/rest/ipdomains
  5. Associate the proxy IP domain with the tenant IP domain:
    • Method:
      PUT
    • Endpoint:
      http://
      da_host
      :8581/rest/ipdomains/
      {
      tenantIPDomainID
      }
    • Body:
      <IPDomain version="0.0.0">
      <ProxyIPDomain>
      {proxyIpDomainID}
      </ProxyIPDomain>
      </IPDomain>
Configure the Tenant
Use the standard methods to configure monitoring in the tenant space.