DCE-7.6.0: Unknown device alarms group for many devices?

DCIM_Support · ‎2020-07-05

This question was originally posted on DCIM Support by spezialist on 2018-12-10

Hi support team,

It seems that I discovered a bug, that I had never seen: after upgrading to version DCE-7.6.0 for many native and 3rd party devices, some Device Alarms have an Unknown group. For example, as in my screenshot for ATS AP7721:

Can someone confirm this?

With respect.

DCIM_Support · ‎2020-07-05

This answer was originally posted on DCIM Support by Steven Marchetti on 2018-12-10

Hi Spezialist,

I've replicated this with my 7721 on firmware 3.9.0 for the ATS as well as after upgrading to 3.9.2. The issue is possibly in DCE but more likely the essential alerts DDF that is downloaded from the device itself. That's where the alarm configurations come from on APC devices. I'll let the engineers know.

Thanks,

Steve

DCIM_Support · ‎2020-07-05

This comment was originally posted on DCIM Support by spezialist on 2018-12-10

Dear Steven Marchetti,

Ok, thanks for confirming the above bug. I hope it will be fixed soon.

Very thanks for the support.

DCIM_Support · ‎2020-07-05

This comment was originally posted on DCIM Support by Steven Marchetti on 2018-12-10

Welcome...I put it in the system so we'll have to wait and see.

Steve

DCIM_Support · ‎2020-07-05

This comment was originally posted on DCIM Support by spezialist on 2018-12-10

Ok, anyway thanks for the support.

DCIM_Support · ‎2020-07-05

This answer was originally posted on DCIM Support by Brian Behbehani on 2018-12-10

Hi spezialist,

Thanks for posting this. DCE 7.6 was recently changed to show Alarm Configuration entries even when they are missing a valid category. In that case, they map to Unknown instead of being ignored altogether, which was happening with some devices. We felt that it was better to show them with a generic category, then to not show them at all. I believe that is what is happening here, though we can confirm locally looking at the DDFs listed in your screenshot. In that case, we can work with the appropriate internal teams to get these resolved such that they map to the correct categories as expected. If these alarms were previously categorized correctly, then we can look into that as a bug that is likely related to the change I mentioned.

Thanks again,

Brian Behbehani

DCIM_Support · ‎2020-07-05

This comment was originally posted on DCIM Support by spezialist on 2018-12-11

Dear Brian Behbehani,

I hope this bug will be fixed soon, as it affects a lot of native and 3rd party devices. Look, for example, on my screenshot of a medium site with the number of Unknown group device alarms:

Very thanks for the support.

DCIM_Support · ‎2020-07-05

This comment was originally posted on DCIM Support by Brian Behbehani on 2018-12-11

Hi spezialist,

I see what you mean. In at least some of these cases, I would expect that these alarms were previously filtered out altogether and can now be configured, which is an incremental step forward.

Still, I have seen some instances where alarms may have been previously mapped to a known category and are now being mapped to 'Unknown' as per this recent change. In both instances, the ability to configure the details of the alarm behavior is unaffected though it can make finding the alarms more difficult.

This can be due to firmware issues as Steven mentioned, but we'll look into improving this mapping in a future release to ensure that all alarms are configurable and with an appropriate category.

Thank you for the feedback as always,

Brian Behbehani

DCIM_Support · ‎2020-07-05

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