Hi,
If you only have one NAS in your environment this would most likely be coming from the probe itself.
if you have mutiple NAS setup with replication and forwarding there is a chance this alarm got stuck in some sore of loop.
I would suggest updating all NAS to 4.80 from our support hotfix page.
CA Unified Infrastructure Management Hotfix Index - CA Technologies
When this type of thing is happening I generally will open Dr nimbus and look at the message bus.
Narrow down the filter to alarms,probe and robot in this case and see if the alarm is coming in new.
If it is then check probe and probe logs.
If it is not check nas.
Some times we see clients who do not have alarms broken out in their queues.
IE they are using a * queue or combine alarm with QOS_Messages.
This can cause a problem where alarms get backed up behind QOS and can come in at much later times
then when the problem happens.
And because of this delay may come in even after the event is over.
So just something else to check