DCO 8.0.1 - Cisco UCS Manager intergration best practices

[DCIM_Support]

I would like to get more information about Cisco UCS Manager intergration best practices. My questions are:

• what type of details can be collected (e.g. blade serial, power consumption, memory, CPU, etc...)
• how increase DCO server load this data acquisition (storage, memory requirement)
• is there any formula which shows the number of UCS Manager and polling time interval?

The reason is why I am asking it because I would like to integrate almost 30 UCS Manager into DCO and in version 7.5 I experienced some issues.

(CID:109446963)

[DCIM_Support]

I am also interested in what info you can collect. I had some issues with 7.5 data collections in the past.

(CID:109447226)

[DCIM_Support]

1. The data we query is the vendor, revision, model, serial number, number of CPUs, number of cores, total memory, available memory and average power usage.
2. We have no numbers on how the load of DCO is affected.
3. I don't quite understand what kind of formula you ask about. Each UCS Manager integration runs in a separate process and should not affect each other. Average power is queried at the configured interval. 

We have not tested with that amount of UCS Managers but since each integration runs in a separate process a sufficiently powerful server for DCO should be able to handle this. I am interested in what issues you experienced with 7.5. Was it the UCS Manager or DCO that had issues?

The way we query the UCS Manager have not changed between 7.5 and 8.0.1.

(CID:109447624)

[DCIM_Support]

Hi Kresten, Thank you for your response. Here you can find more information about my issues on 7.5: DCO 7.5 SP4 - Application status starting or non responding We are using UCS Manager version 2.2 It is possible that refresh interval was two low (15 minutes) and it generated too many data history. This is why I would like to find some kind of best practice at least about with this settting.

(CID:110004078)

[DCIM_Support]

Mate Fekete - With the integration of UCS Manager do you get the chassis names, and the service profiles name auto populated? 

(CID:128747139)

[DCIM_Support]

Hi Fernando,

You won't get non of these attributes with UCS integration. You will get the UCS chassis serial number and based on that you can use the batch association if you already have the S/N in DCO.

Unfortunately the service profiles are not in scope of UCS integration. I asked here in another which "API methods and functions are in use" in the integration.

Regards,

Mate

(CID:128747202)

[DCIM_Support]

Mate Fekete ,

Thanks for your reply. That really sucks. It makes the UCS-M integration useless when managing multiple UCS-M's and Service Profiles/Servers move across multiple chassis. Do you know if a feature request has been made?

(CID:128747221)

[DCIM_Support]

I didn't raise this request. As you can see the API methods you get couple if information from the blade. This is what I usually use and you can trace the physical location of the server if it is moving in or accross chassis.

(CID:128747283)

[DCIM_Support]

So how do you get the API information such as the server to display in DCO?

(CID:128747312)

[DCIM_Support]

What you can see in DCO is that what DCO collect from UCS and described in API methods. E.g.:

• chassis serial
• blade serial
• blade CPU core
• blade memory
• chassis & blade model/type

etc... 

(CID:128748051)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.