Has anyone resolved a problem with LMS 2.5.1 (DFM) creating false alerts for 'unreachable' interfaces. My switches have redundant 1 & 2 gig etherchannels running over a campus wide LAN. The network seems fine, our other monitoring software never picks up a problem. Yet DFM constantly sends alerts stating that an interface is unreachable. I have extended the polling parameters to 240 seconds with 1500 msec time-outs and although the fault has improved, alerts still appear. We have 400 stacks of 3750s.
That is a bit spooky. If it works for you on the console, why wouldn't it work for DFM. Can you make a trace to see what goes wrong? Is it Ciscoworks not getting a response or DFM not taking the response into account.
This would give you something to get cisco to open a case with SMARTS.
I guess another way to get rid of these alarms is to disable the "Reachability settings"
I think it will make DFM only SNMP poll the device interfaces via the management IP address, so you will get notified that an interface is down.
It's just a bit annoying that the scope of disabling this is a bit large. (All router, All switches, etc)
It would be great if DFM would only ping interfaces that were discovered to be reachable. That would help you ofcourse.
The problem with disabling "Reachability settings" is I have quite a lot of layer 3 switches with loopback addresses and redundant uplinks. If only one uplink interface fails the loopback will remain "up" and DFM wont flag the problem.
Nice idea though, it might work well on my access layer.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...