Microsoft SCCM & SCOM OpenManage Integrations

[Thorsten_S]

Hi,

we monitor several Dell iDrac using the OMIMSSC for Operations Manager to show their status in SCOM. This morning I found out that one of the servers is phyiscally unavailable (potential network outage) but the health state in SCOM still shows green for that device.

We are using SCOM 2019 UR2, OMIMSSC 7.2, in scalable feature mode

Green health information in SCOM:Status in SCOM

Monitoring task on the OMIMSSC running ok:Monitoring task in OMIMSSC

Ping timing out, iDrac site is unavailable:Ping test

Discovery job in OMIMSSC showing error:Discovery task in OMIMSSC

Thanks
Thorsten

[DiegoLopez]

Hello @Thorsten_S,

Good to see you back in the Dell Community!

In the past I have seen an issue similar to this one and it was solved on the newest firmware updates on the server side. Please, could you let me know the iDRAC and BIOS firmware of the PowerEdge R740xd

Do you know if you currently have any open case with the System Engineer team regarding OMIMSSC?

Regards.

[Thorsten_S]

Hi@DiegoLopez 

this is the information of the iDRAC:

Manufacturer	Dell Inc.
	Model	PowerEdge R740xd
	Server Generation	14G Monolithic
	Chassis Service Tag	45xxxR2
	BIOS Version	1.4.9

I struggle to see why the firmware version would have an influence on that. I rather think there is a problem with the monitoring process and/or the management pack defintions in SCOM. The system is not accessible so the firmware version cannot play a role here.

And yes, we have a case open on a different topic with support engineers.

Thanks
Thorsten

[DiegoLopez]

Hey @Thorsten_S,

Thanks, but I am missing to see the iDRAC firmware level. Can you obtain it? 

I suspect this was issue because I saw an error with Devices discovered running iDRAC 4.00.00.00 firmware are dropping from Dell EMC Server state view. I think this issue was resolved with a fix available in iDRAC firmware version 4.10.10.10 that was scheduled for February 2020 release.

I will try to contact the SME already assigned to your case and explain him this issue too. 

Regards.

[Thorsten_S]

Hi @DiegoLopez 

here is the firmware information:

BIOS Version	1.4.9
iDRAC Firmware Version	4.20.20.20

Still, I think this is not related as the iDrac was unavailable over the weekend and should have triggered an alert in SCOM.

Thanks for reaching out to the SME
Thorsten

[Thorsten_S]

Hi @DiegoLopez 

do you have any more ideas on this ? Our firmware is apparently up to date and as mentioned shouldn't matter as the device was unavailable at the time anyway.

Thanks
Thorsten

[DiegoLopez]

Hello @Thorsten_S,

I am afraid not yet. I am contacting the team and the SME who are working on the other case. I hope to get an answer from them soon to see if the same SME can engage on this case.

Otherwise, a new escalaton will be required.

I will keep you updated.

Regards.

[DiegoLopez]

Hello again @Thorsten_S,

This is just to let you know that I was in contact with the System Engineer team and the person who has handling your previous case.

He confirme me the way how SCOM monitoring works is that either the appliance or the watcher node is doing the monitoring of the iDRACs. So it is not the iDRAC sending the information but the watcher node pulling the information from there. Therefore the monitor should able to report on the status of remote device and if it is accessible or not.

His best bet was that maybe it’s it is not interpreting it as a status change so it doesn’t sync it downstream The system engineer will open a new case and contact back to you when he has more information.

Regards.