This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (5 pts)
654 Views 4 Replies Last post: Aug 1, 2009 2:05 AM by Adaikkappan Arumugam RSS
navneetk Novice 2 posts since
Apr 24, 2008
Currently Being Moderated

Jun 16, 2009 7:34 AM

Unused interfaces alerting for status down

Hi,

 

I have a query, as soon as a filer is added to the DFM host, it does generates an alert for all the unused interfaces saying “Interface Status down” during a initial scan. Is there a way/option in DFM by which we can suppress such alerts as it's creating a lot of unnecessary events in our environment.

 

 

 

Regards,

Navneet

BrendonHiggins Guru 473 posts since
Mar 26, 2008
Currently Being Moderated
Jun 25, 2009 3:17 PM in response to: navneetk
Re: Unused interfaces alerting for status down

 

 

Hi, welcome to the communities

 

Are you still having problems with this?

 

Is the interface down because there is no cable in it or it is admin down?  I believe turning to port off within DoT will stop the alerts.

 

Hope this helps

 

Bren

BrendonHiggins Guru 473 posts since
Mar 26, 2008
Currently Being Moderated
Jun 26, 2009 1:30 AM in response to: navneetk
Re: Unused interfaces alerting for status down

Sorry it is a feature! 

Adaikkappan Arumugam NetApp Employee Virtuoso 324 posts since
Apr 1, 2008
Currently Being Moderated
Aug 1, 2009 2:05 AM in response to: navneetk
Re: Unused interfaces alerting for status down

Hi

     In generall if you  dont want to b alerted from dfm you can delete the same.

Say volume, filer, aggr, dfm stops monitoring the same and doesnt generate events.

The cli to delete is dfm volume delete dfm filer delete dfm aggr delete.

Once again if you wish to monitor and alter about the same objects you can add them back to dfm.

Using dfm volume add, etc.

Unfortuantely there is no such cli for interface for delete or add.

 

But dfm does not generate continoulsy events for the object unless the status changes from what is now.

So you would get this down event only once on the first discovey of the interface, after that not.

 

Or one more solution is to change the severity of the event.But this will affect all interace, even the active one.

 

[root@lnx~]# dfm eventtype list -C if.adminStatus
Event Name                                         Severity     Class
-------------------------------------------------- ------------ ------------------
interface-status:down                         Error        if.adminStatus
interface-status:testing                      Normal       if.adminStatus
interface-status:up                           Normal       if.adminStatus
interface_status:unknown                      Normal       if.adminStatus
[root@lnx ~]#

[root@lnx ~]# dfm eventtype modify -v information  "interface-status:down"
Modified event "interface-status:down".
[root@lnx ~]# dfm eventtype list -C if.adminStatus
Event Name                                         Severity     Class
-------------------------------------------------- ------------ ------------------
interface-status:down                         Information  if.adminStatus
interface-status:testing                      Normal       if.adminStatus
interface-status:up                           Normal       if.adminStatus
interface_status:unknown                      Normal       if.adminStatus
[root@lnx~]#

 

Regards

adai

More Like This

  • Retrieving data ...

Bookmarked By (0)