Configure Services in EDAA Mode

In this topic, you can find information about commands to start domain managers in service way in EDAA mode.

You need to run the following commands for the respective domain managers to start the services in EDAA mode.

Note: Starting from the VMware Telco Cloud Service Assurance 2.3.1.0 onwards all domain manager services are automatically enabled with EDAA by default. There is no need to configure EDAA explicitly. However, if upgrading from versions prior to 2.3.1.0, ensure to update the definitions as outlined below.

IP:

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-am-pm-server' \
 '--description=IP Availability & Performance Manager' \
 '/opt/InCharge/IP/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-AM-PM' \
 '--config=icf' \
 '--bootstrap=bootstrap-am-pm.conf' \
 '--edaa=ip/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-am-server' \
 '--description=IP Availability & Performance Manager' \
 '/opt/InCharge/IP/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-AM' \
 '--config=icf' \
 '--bootstrap=bootstrap-am.conf' \
 '--edaa=ip/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-ip-configuration-edaa' \
 '--description=IP Configuration Manager for EDAA' \
 '/opt/InCharge/IP/smarts/bin/sm_server' \
 '--name=INCHARGE-CM' \
 '--config=icf-c' \
 '--bootstrap=bootstrap.conf' \
 '--port=0' \
 '--edaa=ip/2.0' \
 '--ignore-restore-errors' \
 '--nodx' \
 '--output'

SAM:

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-sam-pres-server' \
 '--description=Service Assurance Manager Server (notification cache publishing)' \
 '/opt/InCharge/SAM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-SA-PRES' \
 '--config=ics' \
 '--edaa=sam-presentation/2.0' \
 '--bootstrap=bootstrap-amqp.conf' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-sam-server' \
 '--description=Service Assurance Manager Server' \
 '/opt/InCharge/SAM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-SA' \
 '--config=ics' \
 '--edaa=sam-presentation/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-icoi-server' \
 '--description=SAM Adapter Platform Server' \
 '/opt/InCharge/SAM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-OI' \
 '--config=icoi' \
 '--edaa=oi/2.0' \
 '--ignore-restore-errors' \
 '--output'

ESM:

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-esm-server' \
 '--description=ESM Server' \
 '/opt/InCharge/ESM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-ESM' \
 '--config=esm' \
 '--edaa=esm/2.0' \
 '--ignore-restore-errors' \
 '--output'

NPM:

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-eigrp-server' \
 '--description=VMware Smart Assurance EIGRP Server' \
 '/opt/InCharge/NPM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-EIGRP' \
 '--config=eigrp' \
 '--edaa=eigrp/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-bgp-server' \
 '--description=VMware Smart Assurance BGP Server' \
 '/opt/InCharge/NPM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-BGP' \
 '--config=bgp' \
 '--edaa=bgp/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-ospf-server' \
 '--description=VMware Smart Assurance OSPF Server' \
 '/opt/InCharge/NPM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-OSPF' \
 '--config=ospf' \
 '--edaa=ospf/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-isis-server' \
 '--description=VMware Smart Assurance ISIS Server' \
 '/opt/InCharge/NPM/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-ISIS' \
 '--config=isis' \
 '--edaa=isis/2.0' \
 '--ignore-restore-errors' \
 '--output'

MPLS:

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-mpls-topo-server' \
 '--description=VMware Smart Assurance mpls-t Server' \
 '/opt/InCharge/MPLS/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-MPLS-TOPOLOGY' \
 '--config=mpls-t' \
 '--edaa=mpls-topology/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-mpls-analysis-server' \
 '--description=VMware Smart Assurance mpls-a Server' \
 '/opt/InCharge/MPLS/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-MPLS-ANALYSIS' \
 '--config=mpls-a' \
 '--edaa=mpls-analysis/2.0' \
 '--ignore-restore-errors' \
 '--output'

sm_service install --force  --unmanaged  --startmode=runonce \
 '--name=ic-mpls-mon-server' \
 '--description=VMware Smart Assurance mpls-m Server' \
 '/opt/InCharge/MPLS/smarts/bin/sm_server' \
 '-n' \
 'INCHARGE-MPLS-MONITORING' \
 '--config=mpls-m' \
 '--edaa=mpls-monitoring/2.0' \
 '--ignore-restore-errors' \
 '--output'

Note: 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.