UNSOLVED
JG
justin gray
2 Intern
•
143 Posts
•
2 Points
0
2303
September 10th, 2021 08:00
ISM issues and errors
I'm trying to track down when this began, but all my iDRAC servers are exhibiting the following:
- Approximately every 5 hours I see the following warning in the Event Logs: ISM0007: The iDRAC Service Module communication with iDRAC has ended.
- The warning is immediately followed by three of the following events: A provider, ismserviceprovider, has been registered in the Windows Management Instrumentation namespace Root\CIMV2\DCIM to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
I'm curious if the communication issue every 5 hours is expected and what exactly is occurring. Or is this possibly a bug? It seems like a recent development in our environment, though we have not upgraded the ISM recently or changed any related configs.
Any insight appreciated.
justin gray
2 Intern
•
143 Posts
•
2 Points
1209
0
Posted September 10th, 2021 10:00
@DELL-Shine K Thanks for the reply. So far I'm noticing this on R340's and R540's. Mix of Windows 2019 Core and Standard w/GUI.
All are running the latest iDRAC firmware (5.00.00.00). ISM is the same on all servers, 3.6.0.2255.
I found that those not throwing the error show in OMEnt that ISM is not running. Though checking the server, the service is running. So those would likely error if ISM was working properly.
Is there a quick/easy way to check ISM status in OMEnt other than drilling down on each server? I suspect a number are not working properly but if the service is running on the server it's difficult to track down.
Thank you.
DELL-Charles R
Moderator
•
4730 Posts
•
25476 Points
1206
1
Posted September 10th, 2021 13:00
Hello justin gray,
Do you have OMSA installed?
It looks like this can be ignored as Informational. This description seems to match right up with what you are seeing:
Issue ID: 180859 : https://dell.to/3tuCE9b
Functional area: iSM communication restart is observed in both iDRAC Lifecycle Log files and operating system log files
Description: When both iDRAC Service Module (iSM) and OpenManage Server Administrator (OMSA) services are running on the host operating system, iSM communication with iDRAC might stop and start every 5 hours 30 minutes automatically. A warning message indicating the iSM communication restart is observed in both iDRAC Lifecycle log files and operating system log files. Log Message: ISM0007 The iDRAC Service Module communication with iDRAC has ended.
Workaround : No action is required as iSM communication is restored automatically within 1 to 2 minutes.
DELL-Charles R
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Accept as Solution’. ‘Thumbs up’ the posts you like!justin gray
2 Intern
•
143 Posts
•
2 Points
1135
0
Posted September 21st, 2021 12:00
Yes, thank you --this appears to be the issue. I do have both ISM and OMSA installed on all devices.
However, I still have an issue where the ISM service shows as running on the devices and may or may not have a running status in OMEnt.
Is there any method to pull a report that shows whether ISM is installed, what version, and status across all servers?
DELL-Chris H
7 Practitioner
•
9682 Posts
•
48046 Points
1133
0
Posted September 21st, 2021 13:00
Justin,
Built-in reports aren't going to have what version is installed in the OS, but there is a way to query it, as OM Ent has the RACADM CLI option.
You can run get iDRAC.ServiceModule.ServiceModuleVersion to run agains all the servers. That will give you the output of installed versions.
Let me know if this helps.
DELL-Chris H
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!
DELL-Shine K
6 Operator
•
3042 Posts
1214
0
Posted September 10th, 2021 09:00
Can you share Server model, Operating system on the server, iDRAC FW and iSM version? Can you also update iDRAC and iSM to latest and check the issue?