OME 1.3 - dsm essentials network monitor service stopped
The dsm essentials network monitor service stops every time I perform a discovery scan of a range of IPs. Is there anything I can do to resolve this issue or to troubleshoot it? perhaps any hotfix avaliable for solving that issue?
I can restart DSM Network service, but issue comes again with each discovery.
I am running OME 1.3.0.1533 on server 2008 r2 with 32gb ram and 16 cores, with a remote sql 2008 database.
Hotfix HF1006.1.3 for heart bleed is not installed. Issue occurs after update from OME version 1.2.0.3441
With a small IP range (only 4 IPs) issue occurs too, not only with bigger IP ranges. Issue occurs with no specific IP ranges.
Generally, when we see this process stop it is attributed to a particular device that is 'problematic'. Not that that's any excuse for the process to stop, but it is often the cause.
The good news is that you say you only have 4 ip addresses in the range, is that right? And does the Dell Troubleshooting Tool (on your OME desktop) ping these ok?
What protocols did you select in the discovery wizard?
Can you disable the discover range (right click disable) and then create a new disc range with just one of the four IP addresses, run discovery, observe, etc.? (I know you said no specific ip...)
There is a new OME 2.0 release (see the sticky post in the forum). But let's look at this 1.3 install first before going there.
We have 300 ip addresses in many ranges (not duplicated ranges). Issue occurs with Discovery, Inventory, and Status Polling tasks, and it occurs with a small ip range (4) or with a bigger ip range.
We have a status polling for all ip ranges scheduled per each hour.
Dell Troubleshooting tool ping all ip addresses ok. When we restart the service all devices are with status ok and they send traps correctly to ome.
We use snmp protocol for Windows and Linux servers and wsman for esxi hosts and dracs.
DELL-Rob C
4 Apprentice
•
2843 Posts
909
0
Posted October 3rd, 2014 11:00
Hi and thanks for the question.
Generally, when we see this process stop it is attributed to a particular device that is 'problematic'. Not that that's any excuse for the process to stop, but it is often the cause.
The good news is that you say you only have 4 ip addresses in the range, is that right? And does the Dell Troubleshooting Tool (on your OME desktop) ping these ok?
What protocols did you select in the discovery wizard?
Can you disable the discover range (right click disable) and then create a new disc range with just one of the four IP addresses, run discovery, observe, etc.? (I know you said no specific ip...)
There is a new OME 2.0 release (see the sticky post in the forum). But let's look at this 1.3 install first before going there.
Rob
delltechcenter.com/ome