To configure Smarts Server Manager to communicate with Orchestartor, specify the Orchestartor administrator credentials and the IP address of the Orchestartor host.

Prerequisites

For this task, when you use the console, you need to have Smarts administrator credentials to open the Configure menu where you specify the Orchestartor credentials.

Procedure

  1. Open the Service Assurance Manager Global Console attached to the Server Manager (INCHARGE-ESM, by default).
  2. In the Topology Browser Console, select Configure > Domain Manager Administration Console.
  3. Right-click the ESM server in the left pane and select Configure ESM credentials.
  4. In the Configure ESM credentials dialog box, select Orchestrator for the host type.
  5. Type values in the following fields:

    Field

    Value

    Host

    IP address of the Orchestrator(Cloudify) host

    User ID

    Orchestrator(Cloudify) user name

    Password

    Orchestrator(Cloudify) password

    Port

    Orchestrator(Cloudify) port (Default value is 80)

  6. Click Apply credential with/without testing.
  7. Verify that orchestrator credentials are accepted for the orchestrator by checking the status indicator in the Configure ESM credentials dialog box.

    A green Passed test status indicates that the credentials are accepted for the orchestrator.

    If the orchestrator credentials are not accepted, confirm that the credentials are correct and enter them again in the Configure ESM credentials dialog box.

    You can also check the log file: #GUID-EA4A87EA-7942-411C-B0B9-B45BE18A24F0

  8. Click Close.
  9. In the Domain Manager Administration Console, select your IP Manager and select Topology > Discover All to discover VIO and Orchestrator. At the end of the IP Manager discovery process, the Server Manager discovery process is automatically started.
    Note: Configure Kafka/Kafka Cluster and DCF Controller details in clientConnect.conf and esm-param.conf, refer Configuring Edge Kafka/Edge Kafka Cluster and Telco Cloud Operator Data Collector.
    After the topology for your virtual network has been discovered, to continue to monitor and analyze your network, use the Service Assurance Global Console.