You use Smarts Integrations feature to receive event and topology data from the SAM Domain Manager.

The below procedure outlines the steps required to configure VMware Telco Cloud Service Assurance to receive Topology and Events data from SAM Presentation Server.

Procedure

  1. Navigate to Administration > Configuration > Collectors and Connectors > Smarts Integrations.
  2. In the Smarts Integration section, click Add.
    The Create New Smarts Integration page is displayed.
  3. Enter the following details in the Integration Details section:
    1. Name: Provide the name of the broker.
    2. Description: Provide description about the broker.
    3. Broker Host: Provide Broker IP.
    4. Broker Port: Provide Broker port.
    5. Select the Broker Credential from the drop-down. By default defaultSmartsBrokerCredential is populated in the drop-down.
      Note: If the broker is running in NonSecure mode, then select the defaultSmartsBrokerCredential option from the drop-down for Broker Credential. The defaultSmartsBrokerCredential uses BrokerNonsecure as username and Nonsecure as password.
  4. Click Next.
    The Add Presentation SAM page appears, where you can add multiple Presentation SAM.
  5. Enter the following details:
    1. Presentation SAM: Select the Presentation SAM from the drop-down menu.
      Note: Select SAMs that are confgured as Presentation SAM only.
    2. SAM Credentials: Select the SAM Credentials from the drop-down. By default defaultSmartsDomainCredential is populated in the drop-down.
      Note:
      1. defaultSmartsDomainCredential uses admin as username and changeme as password.
      2. SAM Credentials used by VMware Telco Cloud Service Assurance must belong to administrator profile.
      3. Name of Presentation SAM selected must be unique with-in list of SAM configured in VMware Telco Cloud Service Assurance. This constraint applies to SAMs across brokers configured in VMware Telco Cloud Service Assurance.
    3. EDAA URL: EDAA URL is automatically assigned, based on the broker selection.
      Note:
      1. All the Domain Managers underlying Presentation Servers and Presentation Server must be EDAA enabled. Additionally, the hostname populated in EDAA URL field must be resolvable by DNS. In case if the host name is not resolvable by DNS, then EDAA URL can be edited to use IP Address .
      2. The Device Name or Notification Name in underlying SAM must not include the characters + ` \ ” ’ or ., as these may cause issues in the EDAA URL.
    4. EDAA Credentials:Select the EDAA credential from the drop-down. By default defaultSmartsEDAACredential credential is popuated in the drop-down. If there is no authentication configured for EDAA, then select NoAuth from the drop-down in the EDAA Credentials field.

      Note that, the defaultSmartsEDAACredential uses admin as UserName and changeme as Password. In case if the EDAA is backed by CAS authentication, then the credential should be that of administrator.

    Note: The Show Advanced Settings are auto populated and optional. If you want to modify the Kafka Topic and Notification List, enter the appropriate information accordingly.
  6. To add the SAM, click Add SAM, and repeat the above procedure from step 5(a) to 5(d).
    Added SAM appears in the SAM Added area.
    Note: In case the SSL certificate used in EDAA/CAS are not trusted, then you need to validate the certificates manually and confirm to proceed.
  7. Click Next.
    Domain Manager page appears, where you can add multiple Domain Managers to collect the metric data.
  8. Enter the following details:
    1. Type: Select the domain type from the drop-down menu. By default, ESM is selected in the drop-down.
    2. Domain Manager: Select the Domain Manager from the drop-down menu.
    3. Domain Credential: Select the Domain Credential from the drop-down. By default, defaultSmartsDomainCredential is populated in the drop-down.
  9. Click Add DM.
    Note:
    1. This is an optional step.
    2. Name of Domain Manager selected must be unique with-in list of Domain Manager configured in VMware Telco Cloud Service Assurance. This constraint applies Domain Managers across brokers configured in VMware Telco Cloud Service Assurance.
    Added domain manager appears in the Domain Manager area.
  10. Click Next.
    Confirmation page appears, with configured Presentation SAM and Domain Managers.
  11. Verify the details and click Confirm.
    • Presentation SAM and Domain Manager Details page appears and displays the status of SAM, EDAA, Notification Collector, Topology Collector, and Metrics Collector.
    • The Notification and Topology are started and in running state to collect data from configured SAM. You can stop/restart, Events/Topology collectors attached to SAM by selecting the the respective options from the drop-down menu.
    • The Metrics Collector is started and in running state to collect data from IP Domain Manger. You can stop/restart Metrics collectors attached to IP Domain Manager by selecting the the respective options from the drop-down menu.
    Note:
    1. If you want to modify any information, click Edit.
    2. If the Broker, SAM, and EDAA details needs to be updated later, then the Smarts Integration details needs to be deleted and added again. Additionally, credentials need to be updated post configuration.
    3. By default, the EDAA runs in Non-secure mode. If you want to configure EDAA in secure mode using external CAS, then refer the Configure Authentication for EDAA section in VMware Telco Cloud Service Assurance Security Configuration Guide for Domain Managers. This section provides the steps to build an external CAS server and to enable authentication for EDAA using the external CAS server..