This question was originally posted on DCIM Support by Olegas Domanskis on 2019-03-22
Hello
OID 1.3.6.1.4.1.318.1.2.2.1.4.0 returns value 13, but in documentation there is only values from 1 to 5 (https://sxwhelpcenter.ecostruxureit.com/display/public/UADCO8x/DCO+SNMP+status+codes)
What does that value mean? 😀
(CID:141265959)
This comment was originally posted on DCIM Support by Ed Tarento on 2019-03-22
Hi
what device is it and what FW version?
(CID:141267498)
This comment was originally posted on DCIM Support by Olegas Domanskis on 2019-03-22
It's DCO server itself
StruxureWare Data Center Operation Server: 8.2.12-80089-33a247
(CID:141267500)
This comment was originally posted on DCIM Support by Ed Tarento on 2019-03-23
A mystery to me too.
General and essential services (OID .1.3.6.1.4.1.318.1.2.2.1.4.0)May Jef Faridi can shed some light
(CID:141267502)
This answer was originally posted on DCIM Support by Jef Faridi on 2019-03-25
Hi Olegas (& Ed),
DCO only knows those status codes described here: https://sxwhelpcenter.ecostruxureit.com/display/public/UADCO8x/DCO+SNMP+status+codes
and the rest might be specific to ddf.
Kind regards
---
Update:
Hi Olegas & Andrew,
Both issues, eg OID 1.3.6.1.4.1.318.1.2.2.1.4.0 returning 13 and the mis-notification of DCO in DCE, are related and fixed in the next release version (expected release within a few weeks time)
Thanks
Kind regards
(CID:141266497)
This comment was originally posted on DCIM Support by Olegas Domanskis on 2019-03-25
But how we can monitor DCO General and Essential services if it returns unknown code? To what ddf the value is specific?
(CID:141266513)
This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-25
Hi Olegas,
I'm currently looking into this - will get back to you soon, thanks,
Kind regards
(CID:141266614)
This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-26
Hi Olegas,
Many thanks for the clarification - I was assuming that you were getting 13 different status codes. However, done some investigations and tests, this seems to be a bug that's fixed in the next release version. (release date is not known yet, but expected to be within a few weeks time).
Kind regards
(CID:141267176)
This comment was originally posted on DCIM Support by Olegas Domanskis on 2019-03-26
Hello
Thanks. But before the release how can we interpret status 13? As something bad or ignore it?
(CID:141267191)
This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-26
Hi Olegas,
In my tests, it reruns 13 both when the application status is running and also when it is down. I would not ignore it, but preferably would check the DCO webmin interface that would display correctly the server status.
Kind regards
(CID:141267198)
This comment was originally posted on DCIM Support by Olegas Domanskis on 2019-03-26
you mean these statuses?
(CID:141267210)
This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-26
Yes, that's right.
Kind regards
(CID:141267214)
This comment was originally posted on DCIM Support by Andrew Stoakes on 2019-03-27
I have the same issue. I have added my DCO server to DCE to monitor but it is always showing in error. The status code that i get is 13 for OID .1.3.6.1.4.1.318.1.2.2.1.4.0 (Status).
All 3 services are running and showing as "Running" in DCE but the status in the DCE console shows as "Error".
I also note that the backup status is 13 which is also not a listed value
(CID:141267504)
This comment was originally posted on DCIM Support by Jef Faridi on 2019-03-27
Hi Andrew,
The next release of DCO will contain the fix (please see my answer below), thanks.
Kind regards
(CID:141267511)
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!