UCS Blades Discovery

Ben42
Tera Contributor

‎04-30-2019 09:17 AM

Hi Experts,

We are running UCS devices discovery, And we are using snmp community string. The issue is, We are able to discover Cisco Equipment and Switches but not blade servers, And credentials were all same for those devices. Any thoughts ?

Thanks,

Ben,

Labels:
0 Helpfuls
  • 1,489 Views
4 REPLIES 4

sachin_namjoshi
Kilo Patron
Kilo Patron

‎04-30-2019 09:34 AM

Please check below for setting up UCS blade discovery.

 

https://community.servicenow.com/community?id=community_question&sys_id=13ac0be5db9cdbc01dcaf3231f961953

 

Regards,

Sachin

0 Helpfuls

Ben42
Tera Contributor

‎04-30-2019 10:27 AM

Yes, I have provided SNMP cred and also applicative creds for blades. The applicative creds for blades are not being used. Even the applicative credentials for chassis and equipment are also not being used though there is being discovered from "networks discovery schedule".

0 Helpfuls

sachin_namjoshi
Kilo Patron
Kilo Patron
In response to Ben42

‎04-30-2019 11:31 AM

i will suggest to create HI incident for this since configuration looks good to me.

 

Regards,

Sachin

0 Helpfuls

Dave Ainsworth
ServiceNow Employee
ServiceNow Employee

‎04-30-2019 03:30 PM

Hi Ben,

For the applicative credentials, I think you only need to define the applicative credentials for the Cisco UCS Equipment table and this should get all the information back from the UCS API including chassis, blades etc. However, it sounds like you have these defined so this should be fine.

The fact that you are discovering some information via a scheduled scan of the subnet might mean that discovery via the virtual IP is not working. When you discover the whole subnet in a schedule, the UCS might be being discovered by one of the real IPs so you could try a targeted discovery on one of the real IPs to see if this is the case.

I also saw one problem recently where no results were being returned by the call to the API to retrieve blade IP addresses which was causing an issue discovering the blades however the chassis was being discovered ok.

In case it is of any use, we found that the section of the UCS pattern that requests the blade IP addresses (step 17) from UCS retrieved no results. Then in step 20 (Update Blades table with IP), unmatched values is set to 'Remove' and this is likely to mean that if the attempt to get IP addresses fails, it will then discard any blade information it has discovered and not create the CIs.

If you are able to do so, you could try to debug the pattern to see if the get IP command or any other command fails and discuss with a UCS admin why this might be. Changing the parsing strategy in the pattern step to 'Keep' might mean that you do then get the blade records but with some information missing (e.g. IP addresses).

But as suggested, a Hi ticket is probably the way to go.

Regards,

Dave