Guest

Preview Tool

Cisco Bug: CSCvv58559 - vmanage triggered alert "Could not store alarm:" resulting alarm trigger at provider.

Last Modified

Oct 13, 2020

Products (1)

  • Cisco SD-WAN

Known Affected Releases

19.2.3

Description (partial)

Symptom:
vmanage triggered alert "Could not store alarm:" resulting alarm trigger at provider.

Conditions:
In 3 cluster vmanage node having provider tenant setup, customer is getting frequent control connection down alert at provider level.
idealy we should not get alert at provider level.
Upon checking vmanage-server logs. we observed that alert triggered at provider level when vmanage triggered alert "Could not store alarm:" resulting alarm trigger at provider.
Tried to recreate the issue manually many times but unable to do nor internally nor in customer network.

05-Aug-2020 10:09:11,696 SGT WARN  [moccsr3vmng02] [LinkUpdateEventPurgeThread] (vManage-correlation-engine-link-update-dispatcher-538) |1569835905277| Could not store alarm: CorrelatedEventObject{index=4, timeOut=1596593349552, alarmTime=1596593294821, autoClear=true, correlated=true, uuid='76e9da01-1743-4796-bb24-bc3a955d0e17', linkKey='Control-node_down-local-system-ip=20.74.22.2-', message='All control connections to the node are down', matchField='new-state', severity='Critical', ruleName='node_down', ruleNameDisplay='Control_Node_Down', valuesQuery='select from [5:DeviceNode:1596593271069:14423]', event={"builtBy":"EventDataCollector","vmanage-system-ip":"169.254.10.1","entry_time":1596593289000,"eventname":"control-connection-state-change","linkupdate":true,"component":"Control","severity-level":"major","system-ip":"10.0.1.2","host-name":"moccsr3vmng02","personality":"vmanage","peer-type":"vedge","peer-system-ip":"20.74.22.2","peer-vmanage-system-ip":"0.0.0.0","public-ip":"198.19.226.165","public-port":"12406","src-color":"default","remote-color":"private4","uptime":"0:00:00:23","new-state":"down","receive_time":1596593289552,"eventId":"a8a9c92c-750e-4762-8205-dbfbf48d3224","eventCreationTime":1596593289555}, clearUUIDS={}, possibleDevice=false, identifiers=[local-system-ip], devices=[{system-ip=20.74.22.2}], timeStamp=1596593289552}:
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.