This procedure applies to both SAM and SAM with Notification Cache Publishing. It includes some additional steps for SAM with Notification Cache Publishing.

To configure an Active SAM:

  1. Disable topology synchronization in the Active location so that the Active SAM does not synchronize with the underlying Domain Managers while the Domain Managers are still starting up. The Failover Manager synchronizes the Active SAM with the underlying Domain Managers.

  2. In the installation area where the Active SAM is running, go to the BASEDIR/smarts/bin directory and open the bootend.conf file. Type: 

    ./sm_edit conf/ics/bootend.conf

  3. Change the value of suspendTopologyManager to TRUE. The value is FALSE by default.

  4. Save the file and exit.

  5. For Active SAM with Notification Cache Publishing only, use sm_edit to open the <BASEDIR>/smarts/bin/local/runcmd_env.sh file and add the VMware Smart Assurance environment variables listed in Environment variables specified for Host A in the runcmd_env.sh file.

Table 1. Environment variables specified for Host A in the runcmd_env.sh file

Environment variable

Description

SM_EDAA_NAME

Identifies the EDAA for Host A. For example: 

SM_EDAA_NAME=SMARTS-EDAA-A

Each EDAA has a name. The value specified for SM_EDAA_NAME should match the value used in the sm_service command. By default, the name for the EMC Data Access API (EDAA) is SMARTS-EDAA.

SM_CAS_SERVER

Identifies the VMware M&R host. For example: 

SM_CAS_SERVER=http://<M&RHostName>:58080

SM_TOMCAT_SERVER

Is the name of the host where Smarts EDAA is running which is the same host as SAM with Notification Cache Publishing. For example: 

SM_TOMCAT_SERVER=http://<smarts_tomcat_hostname>:8080

  1. Install the service for the Active SAM on an Active server (host A).

    Example for Active SAM without Notification Cache Publishing: 

    ./sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-sam-server' \
 '--description=EMC Smarts Service Assurance Manager Server' \
 '/<BASEDIR>/SAM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-SA' \
 '--config=ics' \
 '--port=1751' \
 '--ignore-restore-errors' \
 '--noregister'\
 '--output'
./sm_service install --force  --unmanaged  --startmode=runonce 
--name=ic-sam-server-pres 
--description=”EMC Smarts Service Assurance Manager Server (notification cache publishing)” 
/<BASEDIR>/SAM/smarts/bin/sm_server 
-n INCHARGE-SA-PRES 
--config=ics 
--port=1751
--edaa=sam-presentation/2.0@SMARTS-EDAA-A
--bootstrap=bootstrap-amqp.conf
--ignore-restore-errors
--output
--noregister

  2. For Active SAM with Notification Cache Publishing only, if you did not install the services for smarts-tomcat, smarts-rabbitmq, and smarts-elasticsearch during the SAM installation, you need to manually install them. The VMware Smart Assurance Installation Guide for SAM, IP, ESM, MPLS, NPM, OTM, and VoIP Managers describes how to manually install these services.

  3. For Active SAM with Notification Cache Publishing only, use sm_edit to open the <BASEDIR>/smarts/conf/local/clientConnect.conf file.

    These sections are configured with default admin/changeme credentials. If the VMware M&R or EDAA user name and passwords have been changed from the defaults, update the values in this file and save the file. When sm_edit is used again, passwords will be encrypted.

    In the Webservices Access section, specify the credentials for VMware M&R frontend (Tomcat) and VMware M&R Webservice Gateway.

    In the Smarts EDAA Access section, provide the Broker information as credentials to access the VMware Data Access API (smarts-edaa). Replace the default password (changeme) with the Broker password. The EMC Data Access API (EDAA) uses this information during a Broker failover. 

    #################### Webservices Access ###################
# Credentials to access MNR.
# This is used by Failover Manager.
# You should change the password!
*:http\://*\:58080/*:admin:<E-1.0>94DA919F35977FF903035AB67EDDFC2CACA24EDEAF8D0DB8D5760141A005D8CE
# Credentials to access MNR webservice-gateway.
# This is used by Failover Manager.
# You should change the password!
*:https\://*\:48443/*:admin:<E-1.0>94C6DAE69612883C06CBDB4683BC906DA2C272D2FF3426BCD70D1989BDB02594
#################### SMARTS EDAA Access ###################
# Credentials to access the smarts-edaa.
# This is used by the Failover Manager to update
# the broker location when the broker fails over.
# You should change the password!
*:http\://*/smarts-edaa/*:admin:<E-1.0>949CEFC1B9C785EA00C9C50AE399F0B0D1CC0A53F55EBC61F22911BDE169060F
*:https\://*/smarts-edaa/*:admin:<E-1.0>949E62F64CE41435C58105E530A1DCA5A0D6B7CC8A74B1650DC344E6F0C716A3

  4. Start the Active SAM service in “Start the services for SAM, Adapter Platform, and BIM” on page 27.

    For Active SAM with Notification Cache Publishing, in addition to the SAM service, you need to start the services for smarts-tomcat, smarts-rabbitmq, and smarts-elasticsearch.

  5. Attach a Global Console to the Active SAM by specifying “<FQDN hostA>:<portA>/<ServerName>” in the Manager Name field of the Attach Manager Dialog Box. For example, itops-tco-217.lss.emc.com:1751/INCHARGE-SA.

  6. From the menu, select Configure > Global Manager Administration Console.

  7. For the Active Service Assurance Manager, define the Active Adapter Platform and the Active BIM as sources.

  8. Add the Active Adapter Platform details under ICS Configuration > IC Domain Configuration . Right-click Domains and select New Domain.

  9. Specify the Active Adapter Platform domain name, leaving this connection initially enabled.

  10. In the Domain Creation Wizard, under Copy existing drop-down list, select INCHARGE-OI, and click Finish.

  11. Add Active BIM details under ICS Configuration > IC Domain Configuration . Right-click Domains and select New Domain.

  12. Specify the Active BIM domain name and leave the Enabled checkbox selected for this connection. Specify the domain name in the format hostname:port/domain (for example, itops-tco-223.lss.emc.com:1612/INCHARGE-MBIM). The hostname specified here should match the hostname in the entry of the failover.conf file.

  13. In the Domain Creation Wizard, under Copy existing drop-down list, select INCHARGE-MBIM, and click Finish.

  14. For the Active Service Assurance Manager, define the other Active Domain Managers like IP Manager as sources. Configure sources for Active Service Assurance Manager provides a list.

Table 2. Configure sources for Active Service Assurance Manager

Product

Go to

IP Manager

“Configure the IP Manager as a source for SAM” on page 29

MPLS Manager

“Configure the MPLS Manager as a source for SAM” on page 31

Server Manager (ESM)

“Configure the Server Manager as a source for SAM” on page 33

NPM

“Configure the Network Protocol Manager as a source for SAM” on page 39

VoIP Availability Manager

“Configure the VoIP Availability Manager as a source for SAM” on page 46

  1. Apply the configuration change and reconfigure the Service Assurance Manager.

    Note:

    Configurations such as underlying Domain Managers (sources), user groups, notification lists, and escalation policies only need to be configured on the Active Service Assurance Manager. During synchronization between Active and Standby Service Assurance Managers, the Failover Manager creates these configurations in the Standby Service Assurance Manager.