Unsolved
This post is more than 5 years old
2 Posts
0
2938
March 26th, 2018 06:00
SCOM Agent Proxy not Enabled for Non-Dell Systems due to Dell.Discovery.Sink
Hello,
Ever since upgrading the dell mp we have installed on our scom 2016 management server we are seeing alerts for non-dell systems, i.e. hyper-v virtual machines, that the agent proxy is not enabled and the HealthService should not generate data about this managed object (Dell.Discovery.Sink) whenever the systems are rebooted. I've seen the other thread in this forum where it is suggested to override the agent proxy auto-resolve alert setting however that does not solve the issue for us. I've also tried flushing the SCOM agent cache on one of the virtual machines to no avail. We are currently running Dell MP 7 and SCOM 2016 UR4.
Any thoughts on this issue?
No Events found!
FredHudzinski
2 Posts
0
March 28th, 2018 12:00
Chris, thanks for taking your time on this and for taking a while to get back to you:
What version of Dell Server Management Pack did you update from?
v6.3
Do you happen to have iSM installed on the VMs? Are you enabling monitoring of those VMs via WMI / and are you monitoring the VMs using SCVMM connected to SCOM?
iSM should not be installed, however if you have a way of verifying I can do that. The hosts these VMs are on are managed by SCVMM which is monitored/has a connection to SCOM.
Check if the update processed correctly by checking the management Dashboard and ensure that Dell Features that show "in Use " are 7.0, is this displaying correctly?
Yes, I've attached a screenshot.
If you would be able to provide a screenshot of the Feature Management Dashboard, as well as the actual text or screenshot of the alert / error it would be helpful as well.
I've attached a screenshot.
Would you please clarify the server type by private messaging me the svc tag for the system, this will also let me verify the hardware installed?
The systems that are generating these alerts are not dell systems, rather hyper-v virtual machines. As such there is no service tag to provide.
Also we get 2 alerts that have the same description. I've also attached a screenshot an error log that is generated on our SCOM server.