Can not inject alarms via Rest Interface

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

"EDAA root <SAM> not found" error when creating notification or performing any action using EDAA API query

curl -k -u <username>:<password> -XPOST -H 'Content-Type: application/json' http://<SAM_IP/FQDN>:8080/smarts-edaa/msa/<DOMAIN_NAME>/instances/ICS_NotificationFactory::ICS-NotificationFactory/action/makeNotification?alt=json -d '

{
    "arguments": {
        "className": "Router",
        "instanceName": "Test",
        "eventName": "Down"
    }
}'

 

Below error seen in smarts-edaa.log

2025-12-08 12:27:42,071 INFO  MSADMTMetadataUpdater updateQ:3 All:<SAM>::Update <SAM> failed in 0.198s

2025-12-08 12:27:42,484 ERROR MSADMTSubscriptionManager eventQ: <SAM> checkDomain:(re)connect

com.smarts.remote.SmRemoteException: JAVA-E-JE_LOGIN_FAILED-Login failed.; in file "SmHttpEngine.java" at line 414

 JAVA-JE_ATTACH_FAILED-Could not attach.; in file "SmHttpEngine.java" at line 56
 
        at com.smarts.remote.SmHttpEngine.httpPost(SmHttpEngine.java:414) ~[skclient-10.1.9.jar:?]

        at com.smarts.remote.SmHttpEngine.attach(SmHttpEngine.java:52) ~[skclient-10.1.9.jar:?]

        at com.smarts.remote.SmRemoteDomainManager.attach(SmRemoteDomainManager.java:602) ~[skclient-10.1.9.jar:?]

        at com.smarts.remote.SmRemoteDomainManager.attach(SmRemoteDomainManager.java:325) ~[skclient-10.1.9.jar:?]

        at com.smarts.remote.SmRemoteDomainManager.attach(SmRemoteDomainManager.java:246) ~[skclient-10.1.9.jar:?]

        at com.emc.msa.dmt.dmpool.MSADMTWrapper.getHandler(MSADMTWrapper.java:236) ~[classes/:?]

        at com.emc.msa.dmt.MSADMTSubscriptionManager.checkDomain(MSADMTSubscriptionManager.java:178) ~[classes/:?]

        at com.emc.msa.dmt.MSADMTSubscriptionManager.run(MSADMTSubscriptionManager.java:285) ~[classes/:?]

Caused by: com.emc.cmp.dmt.exception.JI_Exception$JI_ExChained: JAVA---JE_ATTACH_FAILED-Could not attach.; in file "SmHttpEngine.java" at line 56

Environment

All supported release of Smarts

Cause

Entry for _edaa user account was commented in serverConnect.conf

Resolution

Make sure entry for _edaa user is uncommented in serverConnect.conf under <BASEDIR_SAM>/SAM/smarts/local/conf

# _edaa has Impersonate access.  This means All access, plus the ability to
# invoke operations on behalf of other users.
# You should change this password!
*:_edaa:changeme:Impersonate