Start a Conversation

Unsolved

J

3 Posts

9986

August 14th, 2019 18:00

Login attempt alert for root from using REDFISH

We are getting the following warning daily from a bunch of DELL Poweredge servers.

Login attempt alert for root from using REDFISH, IP will be blocked for 600 seconds

Devices are configured for discovery using WS-MAN.

iDRAC Lifecycle log shows the following warnings.

2019-08-14T23:47:57 USR0031 Unable to log in for root from using WS-MAN

2019-08-14T23:48:00 USR0031 Unable to log in for root from using REDFISH

2019-08-14T23:48:01 USR0034 Login attempt alert for root from using REDFISH, IP will be blocked for 600 seconds

2019-08-15T00:02:40 USR0030 Successfully logged in using root, from and WS-MAN

We are running OME Essentials v2.5 on Windows Server 2012.

Any ideas on why we are getting this warning?

Thanks.

 

4 Operator

 • 

2.9K Posts

August 15th, 2019 08:00

If I were to hazard a guess, it looks like something is misconfigured, like an IP is included in your IP range that either isn't configured, or isn't supposed to be monitored. One thing you may want to do is set up so that only 1 protocol is being used, WS-MAN or Redfish. 

Do all of the target servers have OMSA installed on them?

3 Posts

August 15th, 2019 17:00

Thanks for the reply.

Servers are running ESXi so they are managed using WS-MAN (out-of-band).

I can't see any configuration options to use REDFISH in OME (only WS-MAN out-of-band option is selected).

1 Rookie

 • 

47 Posts

October 7th, 2019 13:00

We are seeing this now too. It's just one server, but every night at the same time we get this error. It's in the same discovery pool as a dozen other servers, not sure what could be different, or why it only happens on that server at that time. Looking at the logs OME has been able to log in without issue on every other attempt.

3 Posts

October 7th, 2019 16:00

As it turned out warnings were caused by incorrectly configured credentials in Configuration Inventory Schedule.

Manage > Configuration > Configuration Inventory Schedule

Hope that helps.

1 Rookie

 • 

47 Posts

October 21st, 2019 08:00

That was it, inventory schedule had the wrong credentials. Strange, I don't remember setting it up!

Thanks!

January 27th, 2023 03:00

Hello,

I have the same issue but I presume that Manage > Configuration > Configuration Inventory Schedule is from old OME version. Now we have 3.9 and I can't see anyway to change credentials for Inventory Schedule. Once I do onboarding that's the only place where I put credentials. Is there any other place where put credentials? Or is there any other solution to this case?

Moderator

 • 

3.5K Posts

January 27th, 2023 13:00

Hello

this guide can help you

DDell EMC OpenManage Enterprise 3.9 User's Guide | Dell US

 

  • In order to support discovery with domain credentials, OpenManage Enterprise (version 3.2 and later) uses the OpenSSH protocol instead of the WSMAN protocol used in the previous versions. Hence, all the Windows and Hyper-V devices discovered prior to updating the appliance have to be deleted and re-discovered using their OpenSSH credentials. Refer the Microsoft documentation to enable OpenSSH on Windows and Hyper-V.
No Events found!

Top