Highlighted
Micro Focus Expert
Micro Focus Expert
251 views

(UCMDB SUPPORT TIP) - Cisco UCS Connection job fails to connect

When attempting to run Cisco UCS discovery. Have set up a credential and tried to run the Cisco UCS Connection job.

However it fails with "All credentials have been tried. No credential can connect to UCS by ip".

Partial content of the Communication Log:

137.15.91.14144428a731fdc3bddad12103ca8e5eb49Execution current time:2018/11/12 14:26:50Begin trying credential id:3317_1_CMSSetting for port:8443Setting for useHttps:trueTry connect url:https://137.15.91.141:8443/nuovaSetting for trustAllCert:trueEnable trust all certsEnable trust all certsTraceback (most recent call last): File "ucs_connection_main", line 53, in DiscoveryMain File "ucs_connection_data_manager", line 103, in getClient File "ucs_client", line 225, in login File "ucs_client", line 217, in post File "ucs_client", line 70, in proxy File "ucs_client", line 145, in wrapper File "ucs_client", line 179, in requestHTTPError: HTTP Error 404: Not FoundCan not connection by credential:3317_1_CMSAll credentials have been tried. No credential can connect to UCS by ip 137.15.91.141Execution current time:2018/11/12 14:26:50Note one line from the communication log: Try connect url:https://137.15.91.141:8443/nuova

When putting this url into a browser, a Cisco splash screen is rendered with the following message:

HTTP Status 404 - /nuova/type: Status report message: /nuova/ description: The requested resource is not available.

Local Cisco team does not know what the nuova resources is either.

The Cisco UCS system version is 10.5.2.12901-1

 

WORKAROUND:

Check to make sure http[s]://:/nuova can be accessed via IE Browser on probe machine.
The host_ip is the target IP of the UCS device. Since MF R&D are not Cisco expert, have no idea how to enable the /nuova in UCS or if the /nuova has been deprecated for some specific Cisco UCS.
Please note, the current Cisco UCS Connection/Topology/Manual jobs are relay on the Cisco UCS Manager XML API (/nuova URL can be accessed), otherwise the discovery is not supported.



Try connect url:https://137.15.91.140:8443/nuova

Setting for trustAllCert:true
Enable trust all certs

=============Init Trust All Cert==================

Enable trust all certs



Traceback (most recent call last):

File "ucs_connection_main", line 53, in DiscoveryMain

File "ucs_connection_data_manager", line 103, in getClient

File "ucs_client", line 225, in login

File "ucs_client", line 217, in post

File "ucs_client", line 70, in proxy

File "ucs_client", line 145, in wrapper

File "ucs_client", line 179, in request

HTTPError: HTTP Error 404: Not Found



Can not connection by credential:3317_1_CMS

All credentials have been tried. No credential can connect to UCS by ip 137.15.91.140
Execution current time:2018/11/13 07:50:52

MICRO FOCUS Software Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Please hit the Kudo botton, if you find this post useful.
Tags (1)
0 Likes
1 Reply
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: (UCMDB SUPPORT TIP) - Cisco UCS Connection job fails to connect

I am having the same issue. Do we know why this has not been fixed yet? I found this on another forum post:

https://community.cisco.com/t5/unified-computing-system/ucs-ldap-and-native-authentication/td-p/2475829

can R&D look at this information? 

Doesn't seem right that we are supposed to be able to discover UCS but it doesn't work.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.