IfDown Events not showing up in DFM

Unanswered Question
Sep 10th, 2007
User Badges:

Hi,

I have verified by running Ethereal on the DFM Server that it is receiving IfDown Traps from various switches but these events are not being shown\coming up in the "Alerts and Activities" ? All these interfaces were put in "Un-Managed" state by default.


Does an Interface has to be in the "Managed State" before DFM will act on any Trap specific to that interface ?


If Yes then How can I make a Bulk Change to convert all the "Trunk Interfaces\Ports" to Managed State ?


What criteria does DFM follow, when discovering an interface and putting it into a Managed state instead of Un-Managed ?


Thanks,

Naman


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Loading.
Joe Clarke Mon, 09/10/2007 - 09:34
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Yes, an interface must be in a managed state before DFM will process any new events for that interface. Bulk management is not easily doable in DFM 2.x. In LMS 3.0, DFM 3.0 comes with bulk manage/unmanage scripts. For now, you will have to use the Detailed Device View, and go through each interface one-by-one.

mnlatif Mon, 09/10/2007 - 10:01
User Badges:

Thanks. That sure is a lot of work with around 600 switches..!

Though I would think that it might have been more logical to at least put the Trunk Ports in Managed state by default.


\\ Naman

Joe Clarke Mon, 09/10/2007 - 10:04
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Trunk ports are put in a managed state by default. However, a DFM trunk port is not the same as a dot1q or ISL trunk port. DFM considers a port to be a trunk port if it is connected to another device that DFM is managing.

mnlatif Mon, 09/10/2007 - 12:27
User Badges:

Absolutely true...!

That will make things a lot easier.


\\ Naman

Actions

This Discussion