DCO - Could not communicate with the external UCS system

DCIM_Support · ‎2020-07-04

This question was originally posted on DCIM Support by Mate Fekete on 2018-02-18

I integrated more than 30 UCS Manager into DCO which are running fine. Except one which drops almost every 20-30 mins the following error message in a popup window:

Could not communicate with the external system <UCS Manager Name>. Connection failed.

The following configuration has been applied on each UCS Manager:

When I click on test of external system that particular UCS Manager shows "OK" and not reporting any communication error.

How can I check in the logs about the root cause of the communication lost?

Why it is reporting almost every 20-30 mins even if the "scanning frequency" is set to 24 hours?

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Satishkumar Shankar on 2018-02-19

Hi Mate,

As per the error message it may be issue with the network connectivity Cisco UCS and DCO application.So to check the server logs just login to the webmin page click on struxureware DataCenter operations under this click on "Download log files".

Here it gathers all log files related to the localhost,external systems in zip format.

This issue can be troubleshooted after checking the server log files.

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Mate Fekete on 2018-02-19

Hi Satishkumar,

I don't think it is a network issue because in the same site (network) I have 15 other UCS Managers which are working fine and not reporting this type of error.

How often DCO try to reach UCS Managers? Is it a default value or can I change it?

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Jef Faridi on 2018-02-22

Hi Mate,

Would it be possible to ask for the server logs?

Server logs can be collected from Webmin interface: StruxureWare DC Operation > Download Log Files > "Download log files".

I will send you an invite to my =S= box folder shortly, so the data can be safely shared with me, thanks.

Kind regards

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Mate Fekete on 2018-02-22

Hi Jef,

Thank you, I sent to you mail with the log file availability. Please let me know if you need further information.

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Jef Faridi on 2018-02-23

Thanks, Mate

I will get back to you as soon as possible,

Kind regards

DCIM_Support · ‎2020-07-04

This answer was originally posted on DCIM Support by Jef Faridi on 2018-03-02

Hi Mate,

Issue basically seems to be with the UCS manager reporting wrong info. Chassis-15 (fan-module-1-1) has wrong data, it contains a non-ascii character:

partNumber=“·3-11624-06”

the “dot” should be 7

this is the only apparent issue with that specific UCS Manager, so correcting this (similar to your previous chassis issue) should resolve the communication problem.

Kind regards

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Mate Fekete on 2018-03-03

Hi Jef,

Thanks for the investigation. In this case I have the same problem again with the non-ascii character.

Is there any way to supress or ignore the error in DCO at UCS Manager integration?

I guess it is a "hard coded" infromation in the fan module and I cannot raise TAC case at Cisco to get a new hardware because it is functioning properly.

Regards,

Mate

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by Jef Faridi on 2018-03-16

Hi Mate,

You are welcome - and the question "Is there any way to supress or ignore the error in DCO at UCS Manager integration?"

We have logged an enhancement case for this, so the possibilities can be investigated (and the possible 'improvements' may be included in a future version, I will keep you posted.)

Kind regards

DCIM_Support · ‎2020-07-04

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