Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

31300

June 4th, 2015 01:00

Question about "omeAlertUnknownStatus"

Dear Colleagues,

We have a frequent Alert messages about "omeAlertUnknownStatus"

We are worried about this messages, suspecting PE server should have a issue.

Or, OME Alert function have a issue.

I attached Alert image, and discover/inventory schedule.

Please let me know;

1. What means "omeAlertUnknownStatus" ? We have a problem about this devices?

2. how to prevent this message?

2 Intern

 • 

1K Posts

June 10th, 2015 02:00

Hi Lee,

Thanks for the reply. 10 mins of status pool cycle is too aggressive. I would recommend a poll cycle of an hour. That is what is set as default. I am sure the cycle would have been changed to 10 minutes anytime before. Though, changing the polling cycle should not change the behavior. This is possible when the device status is not getting retrieved during status poll. You can set a more realistic poll cycle such as an hour so that the polling tasks also don't overlap and let us know if that helps.

2 Intern

 • 

1K Posts

June 4th, 2015 01:00

Hi,

This alert is generated in OME when the health of the device changes to unknown during discovery/status pool.

  • Is the health of the server under concern changing to unknown during status poll or scheduled rediscovery?
  • These issues sometime happen due to lag in a network. Can you confirm there is no intermittent lag? You can increase the number of retries during discovery to avoid lag issues.
  • If you don't want to see an OME generated alert, you can deselect the internal health alerts from Alert settings under Preferences tab. But that would be done for all the internal health changes. So, be aware that OME will not be notifying you for a health change happening on any of your devices through an alert unless alert destinations are set on the managed servers.

1 Rookie

 • 

26 Posts

June 10th, 2015 01:00

Dear Pupul, thanks for answer.

- I checked OME inventory,device status is all O.K.

- We cheked ping test from ome server to devices, but we can not see network lag. 

- I found there are status check schedule, I modified 10 min(default) to 20 min, and the symptom was reduced dramatically. how about this? 

1 Rookie

 • 

26 Posts

June 10th, 2015 03:00

Thanks Pupul,

I could not reach cycle was changed, I surprised.

I suspect somebody changed status pool cycle for any reason(at delivery stage).

Many Thanks for your solution.

I'll guide customer, and I'll report results  after 1 week monitoring.

No Events found!

Top