Unsolved

12975

October 15th, 2020 06:00

Discovery failed

discovery failed on idrac8 of R730. both idrac and open manage applaince are in same network and no firewall involved. 
 
Messages:
Running
Discovery of target 10.10.10.10 started.
Discovery target resolved to IP 10.10.10.10 .
: ========== EEMI Code: CGEN1013 ==========
Message: Unable to connect to the device over WSMAN because a connection error occurred.
Recommended actions: Make sure that the target device is available and retry the operation.
=======================================
Task Failed. Completed With Errors.
 
we recently upgraded dell openmanage enterprise to 3.5.0.60

Moderator

 • 

4.7K Posts

October 15th, 2020 10:00

Hello Prudhviraj,

 

I'm sorry to see OME is failing to connect the R730 on discovery.

 

I have a few things you can check. A few you have already done:

 

WSMAN uses Port 443, is it open?
Is the DRAC firmware up to date?
Ensure that the path between OMEnterprise and the target device is routable
Ensure that the device can ping the OMEnterprise appliance
Ensure that ping/ICMP isn't blocked (firewall) between OME and the target device
Confirm login credentials for iDRAC are correct
Log into the device that is failing to discover to verify the credentials used for the discovery are correct for that device
Try discovery using different account credentials
If password has special characters try an account that does not have special characters

 

Please let me know what you find.

1 Rookie

 • 

1 Message

November 20th, 2020 06:00

Is there any progress on this post so We have this problem

Moderator

 • 

790 Posts

November 20th, 2020 06:00

Hi.

 

No, we didn't receive anything from the TO. So maybe you could let us know what steps have you already done?

Charles mentioned some steps in his post before - have you already done this?

 

Is it also an R730 that is affected?
How do other systems behave?

 

Let me know.

 

BR
Stefan

1 Message

November 29th, 2020 05:00

Hello, 

I am facing the same problem here, and I applied all the Charles steps successfully. 

please, what should be the next verification action here? 

 

Version: 3.5

Output:


Results:
Target System: 10.***
Messages:
Running
Discovery of target 10.*** started.
Discovery target resolved to IP 10.*** .
: ========== EEMI Code: CGEN1013 ==========
Message: Unable to connect to the device over WSMAN because a connection error occurred.
Recommended actions: Make sure that the target device is available and retry the operation.
=======================================
Task Failed. Completed With Errors.

 

November 29th, 2020 22:00

Hi we need to use below to troubleshoot.

(Network Diagnostics Using the Dell Troubleshooting Tool)

https://dell.to/3mmFcBU

1 Rookie

 • 

19 Posts

January 13th, 2021 11:00

I'm experiencing this as well [OME 3.5.0 (Build 60)] and for R#20 servers. After a mass password change, and successfully rediscovering the devices with the new credentials, most iDRAC 7 devices disconnected after a few days. I tried discovering a device using different credentials and the discovery task immediately failed.

========== EEMI Code: CGEN1013 ==========
Message: Unable to connect to the device over WSMAN because a connection error occurred.
Recommended actions: Make sure that the target device is available and retry the operation.
=======================================

The networking team says nothing is getting blocked. Where can I view more verbose and detailed logs?

Moderator

 • 

9.6K Posts

January 14th, 2021 06:00

Rgb_9,

 

 

To me it sounds like it could be a couple things. Would you do me a favor and confirm if the idracs are up to date, and have been restarted? The other thing is it sounds like there may be an issue with the network that the host OME system is on.  As far as logs you can enable Debug logs in the TUI and export them for additional information. 

 

 

Let me know what you see.

 

 

1 Rookie

 • 

19 Posts

January 14th, 2021 08:00

The iDRAC's are up and up-to-date. I reset a couple of them to test if that would fix it, and the symptoms were the same. The networking group assured me that nothing was getting dropped. I enabled Debug logs and restarted the OME services. How do I export them?

Update: I exported them from Monitor > Audit Logs > Export > Export Console Logs. Which logs do I view to see the discovery failures?

1 Rookie

 • 

19 Posts

January 14th, 2021 08:00

I'm looking in application.log but nothing is jumping out at me. These are the last lines after the IP.

[DEBUG] 2021-01-14 16:38:17.843 [ajp-bio-8009-exec-5] DiscoveryConfigManagerImpl - network range#.#.#.#  address type  IPV4 address3
[INFO ] 2021-01-14 16:38:17.843 [ajp-bio-8009-exec-5] DiscoveryConfigManagerImpl - Total no of IP in request 1
[INFO ] 2021-01-14 16:38:17.859 [ajp-bio-8009-exec-5] LocaleHelper - Locale not present in reqeust context data. Returning en_us
[DEBUG] 2021-01-14 16:38:17.859 [ajp-bio-8009-exec-5] LocaleHelper - locale string en_us failed pattern validation. Returning en_us
[INFO ] 2021-01-14 16:38:17.863 [ajp-bio-8009-exec-5] SysLoggerUtilImpl - END : sendAuditMessagetoEPSQueue : Message ID :CDIS4045
[INFO ] 2021-01-14 16:38:17.863 [ajp-bio-8009-exec-5] LocaleHelper - Locale not present in reqeust context data. Returning en_us
[DEBUG] 2021-01-14 16:38:17.863 [ajp-bio-8009-exec-5] LocaleHelper - locale string en_us failed pattern validation. Returning en_us
[INFO ] 2021-01-14 16:38:17.866 [ajp-bio-8009-exec-5] DiscoveryConfigManagerImpl -  Exit createOrUpdateDiscoveryConfigGroup
[DEBUG] 2021-01-14 16:38:17.866 [ajp-bio-8009-exec-5] BusinessMethodExecutor - End: Executing Business method: createOrUpdateDiscoveryConfigGroup
[DEBUG] 2021-01-14 16:38:17.866 [ajp-bio-8009-exec-5] GenericReturnTypeHandlerExt - Starting processReturnType...

I don't see stuff like ERROR or port numbers.

Moderator

 • 

9.6K Posts

January 14th, 2021 08:00

It should be found at application.log

1 Rookie

 • 

19 Posts

January 14th, 2021 13:00

After further investigation by the networking team, it was discovered that it was a recent change to a policy that caused the disconnections. After they added the application "dell-drac" to the policy, instead of just 443, I was able to rediscover the disconnected devices. It is odd that iDRAC 7 was affected and not iDRAC 6/8/9. It must behave a different way than the others.

Moderator

 • 

9.6K Posts

January 14th, 2021 13:00

Would you confirm if you reproduced the error after you enabled Debug? If not would you be able to and let us know what you see?

 

Thanks.

 

 

1 Rookie

 • 

9 Posts

September 12th, 2022 06:00

Hi Charles,

is ICMP required to be opened between OME and iDRAC? I'm trying to add/discover new R450 server on OME 3.9.0b55 and it fails with following message:

Network Address 172.29.200.15 is not reachable via ICMP PING.
Task Failed. Completed With Errors.

Dariusz

Moderator

 • 

4.7K Posts

September 12th, 2022 08:00

Hello Dariusz

 

Most of the time this is a network configuration issue. I have a couple other threads with similar issue you can review.

Also I'd recommend creating ga new discovery job, reference and video linked below:

 

Similar threads:

https://dell.to/3RGf1pm

 

https://dell.to/3d7rBip

 

 

Create a device discovery job page 47

https://dell.to/3RJDVVi

 

OpenManage Enterprise Discovery

https://dell.to/3QGB6To

 

(Network Diagnostics Using the Dell Troubleshooting Tool)

https://dell.to/3mmFcBU

No Events found!

Top