Alarms are generated on Avaya Aura® Device Services, and user profiles are appropriately created and assigned, but System Manager does not show these alarms.
This issue is not applicable if Avaya Aura® Device Services is deployed in an environment without Avaya Aura®.
Solution
Procedure
Log in to the Avaya Aura® Device Services.
Go to the /var/net-snmp directory.
Memorize the timestamp of the snmpd.conf file.
Log in to the System Manager web console and navigate to Home > Services > Inventory > Manage Serviceability Agents > Serviceability Agents.
From the agents list, select the Avaya Aura® Device Services node for which alarms are not displayed on System Manager.
On the Serviceability Agents page, select Avaya Aura® Device Services and click Manage Profiles.
On the next page, click Commit.
The timestamp of the snmpd.conf file should be updated.
If the timestamp of the snmpd.conf file was not updated, perform the remaining steps.
If the timestamp was updated, then you do not need to do anything else.
Log in to System Manager as the root user using SSH.
Run the locate recoverAgent.sh command to obtain the full path to the recoverAgent.sh script.
The command might fail when restarting snmpd. This is the expected behavior.
Stopping existing snmpd service...
Stopping snmpd (via systemctl): [ OK ]
Restarting snmpd (via systemctl): Job for snmpd.service failed because the control process exited with error code. See "systemctl status snmpd.service" and "journalctl -xe" for details.
[FAILED]
Setting the reinitialized property to true
