Has anyone seen this before? I'm looking for feedback on whether or not this is directly related to the VM Panorama sits on? This was the decription of an alert I received at 12:30EST today. Sure enough, Pano was rebooting. Any information provided is greatly appreciated!
What software version are you on?
I know there are quite a few memory fixes that have went into 4.1.10.
I have seen this at one of our Panorama installations that's running 5.0.1. I currently have a support case opened for this.
Have seen that the CPU usage has periodically been very high, and some reboots with the same error message as you.
I just had this error happen on an M-500 in logger mode, so I do not think it is related to your VM. I am still curious about this error though and if it is a warning of a larger problem. So far I have only seen the error once, but I am watching for more before opening a ticket.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The Live Community thanks you for your participation!