Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DFM "incorrect" interface grouping ???

Hi:

We are using CW LMS 2.6, and specifically DFM 2.0.10 for monitoring a network like the one described in the attachment.

We are trying to tune A&A.

We found out that DFM has automatically located ports and interfaces under:

1) System Defined Groups/Inteface Groups/Others

Routers and switches interfaces

2) System Defined Groups/Inteface Groups/10 MB-100MB Ethernet

Routers Ethernet interfaces

3) System Defined Groups/Inteface Groups/Dial-On-Demand

Routers Serial interfaces

This "incorrect" grouping has compelled us to configure some "incorrect" Polling and Threshold options to avoid "false positives". For instance, disabling ExceededMaximumUptime, because the serial links are not Dial-On-Demand nor Backup interfaces.

How does DFM create this groups?

We would likely consider that serial interfaces could be contained by Interface Groups/Serial; switch access interfaces by Access Port Groups/10MB-100MB Ethernet; and 802.1q trunk ports by Trunk port Groups/10MB-100MB Ethernet.

As long as it is not possible to modify this system groups, then I assume that the way to "fix" this is creating custom groups and modifying their priorities, isn`t it?

Every suggestion is highly appreciated.

Thank you very much for your support.

Julio

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: DFM "incorrect" interface grouping ???

DFM considers access ports and trunk ports slightly differently than the industry norm.  A trunk port in DFM speak is a switch port connected to another device managed by DFM.  This could be an 802.1q trunk, or it could be a port configured as an access port.  A DFM access port is any switch port that is not connected to another device that DFM manages.

DFM will map PPP interfaces to dial-on-demand interfaces.  Other serial interfaces will be grouped as serial interfaces.

Typically, we recommend that you configure some of the customizable groups in order to change the way DFM handles certain interfaces and ports.  It sounds like you have a good handle on how to do that (with setting priorities and applying changes).

2 REPLIES
Cisco Employee

Re: DFM "incorrect" interface grouping ???

DFM considers access ports and trunk ports slightly differently than the industry norm.  A trunk port in DFM speak is a switch port connected to another device managed by DFM.  This could be an 802.1q trunk, or it could be a port configured as an access port.  A DFM access port is any switch port that is not connected to another device that DFM manages.

DFM will map PPP interfaces to dial-on-demand interfaces.  Other serial interfaces will be grouped as serial interfaces.

Typically, we recommend that you configure some of the customizable groups in order to change the way DFM handles certain interfaces and ports.  It sounds like you have a good handle on how to do that (with setting priorities and applying changes).

New Member

Re: DFM "incorrect" interface grouping ???

Thanks a lot: terrific, as usual, Joseph. Quick and accurate.

Your answers are a great help.

Thank you and best regards

Julio

347
Views
0
Helpful
2
Replies
CreatePlease to create content