VMware Smart Assurance SMARTS: How to Configure EDAA for Smarts NPM domains (Smarts 9.3 and above)
search cancel

VMware Smart Assurance SMARTS: How to Configure EDAA for Smarts NPM domains (Smarts 9.3 and above)

book

Article ID: 323808

calendar_today

Updated On:

Products

VMware

Issue/Introduction

There are two variants of the Smarts EDAA, the Smarts 9.2.x EDAA and the Smarts 9.3 EDAA.  One big difference between the Smarts 9.2.x EDAA and the Smarts 9.3 EDAA is how they are delivered.  

The Smarts 9.2.x EDAA is delivered with the Smarts 9.2.x Console software while the Smarts 9.3 EDAA is delivered with the Smarts 9.3 Service Assurance Manager.  

Please make sure you are using the correctly KB article for the deployment you have.  This article is for the Smarts 9.3.x EDAA and above


Symptoms:
To query the NPM domain managers via EDAA requires domains like INCHARGE-BGP, INCHARGE-OSPF, INCHARGE-ISIS, INCHARGE-EIGRP to be enabled with EDAA mode and then configure it to be able to successfully communicate with the EDAA hosted on the SAM server (remote or local)

Environment

VMware Smart Assurance - SMARTS

Resolution

Please follow the steps to setup the NPM domain managers and use the existing SAM EDAA as follows:
  • Start the NPM services in EDAA Mode
Example:
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'
------------------------------------------------------------------
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'

Reference : Configure SMARTS Services in EDAA Mode

  • Make a note of the Models defined (as highlighted above) as this will be crucial in definitions in the MSA sources.
  • Edit the msa-sources.xml file located in the SAM installation in /smarts/tomcat/webapps/smarts-edaa/WEB-INF/classes (or smarts/local/ copy based on the deployment) to add entries for your NPM Managers.
    • Add the entry key information: 
      <entry key="Insert NPM Domain name Here"
value-ref="MsaDMTDataSource__Insert NPM Domain name Here" />
      Example for BGP as per the above definition in step #1
<entry key="INCHARGE-BGP"
value-ref="MsaDMTDataSource__INCHARGE-BGP" />
    • Add the corresponding bean id information.
<bean id="MsaDMTDataSource__Insert NPM Domain name Here" class="com.emc.msa.dmt.dmpool.MSADMTContext"> 
<property name="brokerContext" ref="MsaDMTDataSource__Broker" /> 
<property name="dmtName" value="Insert NPM Domain name Here" /> <property name="dataSourceName" value="Insert NPM Domain name Here" /> 
<property name="modelName" value="Insert NPM Model Name Here" /> 
<property name="modelVersion" value="2.0" /> <property name="useTLS" value="true" /> 
<property name="disableKeepalives" value="true" /> 
<property name="lockBoxSupport" value="false" /> 
<property name="excludeClasses" ref="IP-ExcludeClassesDefault"/> 
<property name="excludeAttributes" ref="IP-ExcludeAttrsDefault"/> </bean>

Example for BGP as per the above definition in step #1
<bean id="MsaDMTDataSource__INCHARGE-BGP" class="com.emc.msa.dmt.dmpool.MSADMTContext">
<property name="brokerContext" ref="MsaDMTDataSource__Broker" />
<property name="dmtName" value="INCHARGE-BGP" />
<property name="dataSourceName" value="INCHARGE-BGP" />
<property name="modelName" value="bgp" />
<property name="modelVersion" value="2.0" />
<property name="useTLS" value="true" />
<property name="disableKeepalives" value="true" />
<property name="lockBoxSupport" value="false" />
<property name="excludeClasses" ref="IP-ExcludeClassesDefault"/>
<property name="excludeAttributes" ref="IP-ExcludeAttrsDefault"/>
</bean>

Use the full domain name as it is registered with the Broker (for example, INCHARGE-BGP and not BGP). The entry key parameter value should match the data-source name. 

The value of the bean id parameter must match the value-ref parameter value. The dmtName property value and the dataSourceName property value must match the entry key value. 

  • Once the bean is defined, we would also have to add the NPM under the <SAM-BASEDIR>/smarts/conf/edaaClientConnect.conf file for connectivity via EDAA as follows:
  • Add an entry for the NPM domain using the format
#*:<DOMAINNAME>:admin:changeme.
*:Insert NPM Domain names Here:admin:changeme
::_edaa:changeme
  • Restart the tomcat service and confirm there are no start-up errors in the catalina.out logs.


Additional Information

For AMPM Domains, please review KB: https://kb.vmware.com/s/article/79585?lang=en_US


Powered by Wolken Software