Create Smarts Integration
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.- Navigate toAdministration>Configuration>Collectors and Connectors>Smarts Integrations.
- In the Smarts Integration section, clickAdd.TheCreate New Smarts Integrationpage is displayed.
- Enter the following details in theIntegration Detailssection:
- Name: Provide the name of the broker.
- Description: Provide description about the broker.
- Broker Host: ProvideBroker IP.
- Broker Port: ProvideBroker port.
- Select theBroker Credentialfrom the drop-down. By defaultdefaultSmartsBrokerCredentialis populated in the drop-down.If the broker is running in NonSecure mode, then select thedefaultSmartsBrokerCredentialoption from the drop-down for Broker Credential. ThedefaultSmartsBrokerCredentialusesBrokerNonsecureas username andNonsecureas password.
- ClickNext.The Add Presentation SAM page appears, where you can add multiple Presentation SAM.
- Enter the following details:
- Presentation SAM: Select the Presentation SAM from the drop-down menu.Select SAMs that are confgured as Presentation SAM only.
- SAM Credentials: Select the SAM Credentials from the drop-down. By defaultdefaultSmartsDomainCredentialis populated in the drop-down.
- defaultSmartsDomainCredentialusesadminas username andchangemeas password.
- SAM Credentials used byVMware Telco Cloud Service Assurancemust belong to administrator profile.
- Name of Presentation SAM selected must be unique with-in list of SAM configured inVMware Telco Cloud Service Assurance. This constraint applies to SAMs across brokers configured inVMware Telco Cloud Service Assurance.
- EDAA URL: EDAA URL is automatically assigned, based on the broker selection.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 .
- EDAA Credentials:Select the EDAA credential from the drop-down. By defaultdefaultSmartsEDAACredentialcredential is popuated in the drop-down. If there is no authentication configured for EDAA, then selectNoAuthfrom the drop-down in the EDAA Credentials field.Note that, thedefaultSmartsEDAACredentialusesadminas UserName andchangemeas Password. In case if the EDAA is backed by CAS authentication, then the credential should be that of administrator.
TheShow Advanced Settingsare auto populated and optional. If you want to modify theKafka TopicandNotification List, enter the appropriate information accordingly. - To add the SAM, clickAdd SAM, and repeat the above procedure from step 5(a) to 5(d).Added SAM appears in theSAM Addedarea.In case the SSL certificate used in EDAA/CAS are not trusted, then you need to validate the certificates manually and confirm to proceed.
- ClickNext.Domain Managerpage appears, where you can add multiple Domain Managers to collect the metric data.
- Enter the following details:
- Type: Select the domain type from the drop-down menu. By default,ESMis selected in the drop-down.
- Domain Manager: Select the Domain Manager from the drop-down menu.
- Domain Credential: Select the Domain Credential from the drop-down. By default,defaultSmartsDomainCredentialis populated in the drop-down.
- ClickAdd DM.Added domain manager appears in the
- This is an optional step.
- Name of Domain Manager selected must be unique with-in list of Domain Manager configured inVMware Telco Cloud Service Assurance. This constraint applies Domain Managers across brokers configured inVMware Telco Cloud Service Assurance.
Domain Managerarea. - ClickNext.Confirmation page appears, with configured Presentation SAM and Domain Managers.
- Verify the details and clickConfirm.
- 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.
- If you want to modify any information, clickEdit.
- 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.
- By default, the EDAA runs in Non-secure mode. If you want to configure EDAA in secure mode using external CAS, then refer theConfigure Authentication for EDAAsection in. This section provides the steps to build an external CAS server and to enable authentication for EDAA using the external CAS server..VMware Telco Cloud Service AssuranceSecurity Configuration Guide for Domain Managers