1 Rookie
•
41 Posts
0
771
May 26th, 2023 07:00
Poweredge OME Ansible DNS issue
Hi,
I have a weird problem that I'm hoping has an easy solution I"m not seeing.
I have 80 poweredge servers that I'm using the OME Ansible modules with.
Out of those 80 servers 3 of them do not allow me to connect to the iDRAC via the Ansible modules by using the DNS name of the iDRAC. The IP address works no problem.
With those 3 servers, I'm able to:
- ping the iDRAC using the DNS name
- ssh to the iDRAC using the DNS name
- go to the Web UI using the DNS name.
However, for some reason, I get the following error using the Ansible Module:
changed: [idrac16.prod.int -> jumphost.prod.int]
fatal: [idrac18.prod.int -> jumphost.prod.int]: FAILED! => {"ansible_job_id": "568485823367.2834900", "changed": false, "finished": 1, "msg": "Unable to communicate with iDRAC iloidrac18.prod.int. This may be due to one of the following: Incorrect username or password, unreachable iDRAC IP or a failure in TLS/SSL handshake."}
changed: [idrac17.prod.int -> jumphost.prod.int]
fatal: [esx19 -> jumphost]: FAILED! => {"ansible_job_id": "921771635463.2836497", "changed": false, "finished": 1, "msg": "Unable to communicate with iDRAC iloidrac19.prod.int. This may be due to one of the following: Incorrect username or password, unreachable iDRAC IP or a failure in TLS/SSL handshake."}
fatal: [idrac20.prod.int -> jumphost.prod.int]: FAILED! => {"ansible_job_id": "540443383173.2837443", "changed": false, "finished": 1, "msg": "Unable to communicate with iDRAC iloidrac20.prod.int. This may be due to one of the following: Incorrect username or password, unreachable iDRAC IP or a failure in TLS/SSL handshake."}
As you can see from this example, 16 and 17 work but 18-20 do not.
Thanks for any help on figuring this out. I know its got to be something I'm missing.
thanks.
glenn.
gdny
1 Rookie
1 Rookie
•
41 Posts
0
May 26th, 2023 11:00
Turns out the issue is known. And the solution is highlighted here:
https://www.dell.com/support/kbdoc/en-us/000193619/http-https-fqdn-connection-failures-on-idrac9-firmware-version-5-10-00-00
Still not sure why this was different only on 3 of the 80 servers, but this solved my issue so I'm good.
Thanks Zac for helping me with the issue.
glenn.