Cisco UCS Discovery Credentials

tlegler · ‎01-17-2018

We are attempting to discovery Cisco UCS devices. I have credentials that should be admin on the UCS Manager. So far, our SN instance has been able to identify that the IP is a Cisco UCS via SNMP. Discovery then launches the UCS - HD pattern, but is unable to log in. The error message received is "2018-01-16 15:39:29: setAttribute(login, <aaaLogout cookie="" response="yes" errorCode="555" invocationResult="unidentified-fail" errorDescr="Session not found"> </aaaLogout>)".

My question is what credentials are necessary to allow the pattern to discover the UCS equipment? The online docs do not provide any guideance on this (that I could find ).

Thanks in advance for anyone's help on this!

-Trevor

tlegler · ‎02-02-2018

Jon-

I just figured this out today and answered my own question. The CiscoUCS discovery requires SSH credentials, but the need to be put in a specific way for UCS to recognize them.

For instance, if you have an account on UCS called 'admin' with local logon rights to UCS, the account needs to be set up in ServiceNow as ucs-local\admin. Here is a link to where I found the requirements for SSH login: https://supportforums.cisco.com/t5/unified-computing-system/ucs-ldap-and-native-authentication/td-p/....

-Trevor

View solution in original post

William Mo · ‎01-30-2020

regarding the credential, please be aware it should be Applicative Credential not the normal SSH one.

and if you UCS is in HA, the discovery should target to the real IP behind the web console IP.

BH10 · ‎12-01-2020

Hello,

Did you get success in running discovery for cisco-ucs. i am trying to understand the what components get from OOTB discovery and its relationship.

could you please share dependency view of cisco-ucs CI's/componets. like-chassis, server, rack, port, interface, device manager, etc. And relationships info. plz.

thanks in advance.

jimmillet · ‎01-17-2023

We are at Tokyo version and trying this "UCS - HD" pattern for the first time to discover Cisco UCS devices. We done the following so far:
1. Created SSH credential using domain name structure mentioned above and did credential test and that passed.

2. Created applicative credential for "ucs_equipment" CI class using same ID & PW as the SSH credential record.

3. Horizontal discovery shows the following: SSH, SNMP, HTTP, and HTTPS ports are detected by Shazzam, but none of the classifiers worked, so discovery ended and pattern never started.

I looked at the pattern code and it seems to be using REST API calls and NOT SSH or SNMP to do the discovery. Discovery code calls a MidServer Script Include named "UCSRestXmlApiClient" where you can see the details. The documentation for this pattern in the SN docs is missing a lot of details. I never asked the device team to us to make REST API calls. I will ask them. Curious if others have run into this.......

Kiran Gundap5 · ‎03-15-2024

Hello @jimmillet ,

I am facing same issue for UCS. Please guide me to resolve this issues.