OPERATIONAL DEFECT DATABASE
...
...
3-Oct-2023 09:31:02,055 CDT INFO [] [AlarmsDAO] (vManage-akka.actor.default-dispatcher-5) || AlarmsDAO::addAlarm() - Tenant default, Adding alarm {devices=[{"system-ip":"1.1.1.4"}], uuid="14ae0e01-b50b-496d-92cb-a9a1670170aa", values=[{"system-ip":"1.1.1.4"}], message="Analytics is enabled but relevant license is not present", rule_name_display="Analytics is enabled but relevant license is not present ", component="System", component="System", cleared_events=null, active=true, entry_time=1697207462055} "25/Oct" : 25-Oct-2023 09:31:02,053 CDT INFO [] [AlarmsDAO] (vManage-akka.actor.default-dispatcher-2) || AlarmsDAO::addAlarm() - Tenant default, Adding alarm {devices=[{"system-ip":"1.1.1.4"}], uuid="624f36e1-5bb7-40b9-ab15-bdaefacb4fcb", values=[{"system-ip":"1.1.1.4"}], message="Analytics is enabled but relevant license is not present", rule_name_display="Analytics is enabled but relevant license is not present ", component="System", component="System", cleared_events=null, active=true, entry_time=1698244262053}
changed the used license for these 2 devices to Tier3 , and then synced , we can see the Vmanage recognize them , but same issue.
If vMonitoring and vAnalytics are not being used, the issue can be solved by opening a TAC case to have a TAC engineer disable this feature completely. If vMonitoring is being used and vAnalytics is not, the issue can be solved by upgrading to a fixed release.
Why Vmanage is raising this alarm, how can stop it.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
