DELL status pooling update on "unknown server" category
Hi All,
this was a July issue not answered, but this time I can be more accourate since I'ts always reproducible
On dell OME 1.3, fresh installation on a dedicated server WS 2012 R2, default installation configuration
a) The Status spooling is not updating server status for "unknown servers" via ICMP, therefore i don't recieve "system up" o "down" updates for the "unkonwn" servers and devices. If an "unkonwn server" is OFF the server is again displayed as ON
b) Dell trubleshooting tools tells that there are no problems with ICMP test (the unkwon server is not pingable id is OFF and is pingable if is ON)
c) the "unknown server" status (ON or OFF) updates correctly if i run manually the "refesh inventory" task on that server. The status correctly changes and the email alerts are generated.
d) the server recognised are correctly updated on status ppoling
e) the issue is Always reproducible for LAN and WAN devices
I do not have an OME handy right now but i think we can start with this thread:
Is the internal health alert and internal connection status alert, both enabled. By default, the internal connection status alert option is disabled. This setting is under Preferences >> Alert settings.
When you refresh inventory, you get the new status. What happens when you refresh status manually?
Are you getting these internal connection state change alerts populated for servers or any other devices?
1) ok now the internal alert and internal connection status are both enabled; nothing changes
2) If I refresh manually the inventory I get the new status; if I refresh manually the status the server status remains unchanged.
3) I get correcly status changes only for recognised devices. The "unknown" devices seems to be out of the status pooling control.
4) No network delay, The OME server and the target are connected on gigabit network.
The "unkown device" status changes correctly only if i manually run on the device the "Refresh Inventory" refresh task (right click), in the Manage - Device view. It's Always reproducible.
It sounds like you are saying the network connection is pretty solid. That's usually the root cause for these symptoms.
Did adjusting the retry or timeout on the first page of the discovery wizard make any difference in how often you saw this behavior? (assuming you are SNMP, but if WSMan also, you'd need to adjust timeout on that page too maybe).
Is it possible to install a quick OME 2.0 VM just for testing purposes to see if the behavior is any different?
Otherwise, we'd need a support ticket to try and get some logs of that 1.3 box (800-945-3355).
Yeah, you can just install OME 2.0 on top of OME 1.3 and it will upgrade ok. There are a few notes in the user guide on delltechcenter.com/ome that discuss upgrade.
Be sure to back up your OME 1.3 SQL Server database using Microsoft best practices, etc.
upgraded OME from 1.3 to 2.0 in my production machine and now I can confirm that it works.
Only one thning that I might suggest is to update the help on line in order to explain how to install the SQL2012 management console since it's necessary for backing up the OME databse and it's not included in the OME installation.
DELL-Pupul M
2 Intern
•
1004 Posts
912
0
Posted October 22nd, 2014 09:00
Hi,
I do not have an OME handy right now but i think we can start with this thread: