General Discussion

Unused port alerts on the dashboard

CODNCHIPS
5,319 Views

Unused ports produce alerts on the dashboard.

How can I clear this as we have no intention of using those ports?

We are running Clustered ontap 9.3P8

This seems like a really stupid question, but there's no obvious way of clearing this.  You can't do anything in the dasboard and they don't feature under the "system alerts" section.

8 REPLIES 8

Ontapforrum
5,310 Views

Hi,

 

Yes, I see this on my 9.1 Filers as well, looks like you can do nothing about it unless you upgrade to 9.4 as per this kb. We also have ports which are un-used but purposely administratively down but they still show up as down.

 

OnCommand System Manager 9.0 and newer report administratively down interfaces under the Dashboard:
https://kb.netapp.com/app/answers/answer_view/a_id/1070568


Symptom:
In OnCommand System Manager 9.0 and later, the UI is changed. As part of this change, when a user logs into OnCommand System Manager, it will take them to the dashboard for the cluster. The dashboard will display warning level and critical alerts and notifications. As part of this, it can report ports that are down. This issue will be seen under the Alerts and Notifications section in the OnCommand System Manager Dashboard. Here you will see where it reports X ports down under the critical section.

 

Cause: BUG-956352
This is caused by OnCommand System Manager not checking the administrative status of the port and only checking if it is up or down.


Solution
Upgrade to Ontap 9.4 or later to resolve this issue.

 

Thanks!

CODNCHIPS
5,305 Views

Hiya,

Thanks for your response.

What a crappy bug - that's really silly isn't it!  What a long way round to resolve such a simple thing!

It's so claringly obvious, I just don't see how that didn't get caught during QA\Testing!!

AlexDawson
5,239 Views

Hi there! 

 

Our bug tracking tool is called BURT, and it is used for tracking both feature enhancements and product defects. This is classified as a request for enhancement (RFE) per the KB article. It is not due to unintended functionality - it's just the outcome of where we were able to spend development effort prior to release. 

 

Yes, it was silly. But it's fixed now. If it's a big issue, please update to 9.5P10 - all platforms which support 9.3 will support 9.5 (unless you have IOM3 disk shelves)

Stephen_Pea
5,061 Views

Running 9.6P3,,,, 12 ports down notification still there! bit hard to explain to a non technical manager why the dashboard of a VERY expensive storage system is showing alerts 24/7. Getting to the point where ill just have to say "yea sorry, Netapp systems development cant see to get that bit right! wonder what else might be broken" Come on people its been 5+ years, let us have a clean bill of Dashboard health 😞 

 

"System alerts" is clean.

bmccullough
5,030 Views

Elevate you privilege from admin to advanced and you will have an option to ignore the down ports

 

cluster::> set -privilege advanced

cluster::*> network port modify -node [node] -port [port] -ignore-health-status true -up-admin false

 

It is on of the first things I do when standing up a new cluster is to down and ignore un-cabled ports.

Stephen_Pea
5,000 Views

Nice one 

Worked a treat on 9.6P3!

Didnt work on 9.1P3, but thats expected.

WEdwards
2,315 Views

"Bug" is still present at 9.10.1P7 release. The confusing part is it only alerted on a single port on one node, when there are at least 7 unused ports in down and status and the ignore-health-status is false with up-admin true.  Addressed the single port as you have on both nodes and will wait and see if the others alert.

Public