Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

LMS 2.5.1 and the discovery IP filters

Unanswered Question
Feb 22nd, 2006
User Badges:

It seems like the "Ip Address Range" in the "Discovery Settings" does not limit the discovery to the specified range, if a router, which is being discovered, has IP addresses on the interfaces that are not reachable for the LMS, the LMS still tries to ping them, even though those IPs are outside of the scope of the specified range. It also tries to ping the IP addresses configured in the static NAT statements on that router (?). The allowed range is specified as 10.[224-227].*.*

Maybe this is a designed behavior?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
nhabib Wed, 02/22/2006 - 20:10
User Badges:
  • Red, 2250 points or more

If you see ICMP traffic (ping), that is probably coming from Device Fault Manager, and that is a designed behavior.

DFM pings all interfaces (to check status) of managed devices.

Discovery (part of Campus Manager) does not ping, it performs SNMP polling.

The filters are for Discovery only, they are not used by DFM.

dmitry Wed, 02/22/2006 - 22:32
User Badges:

thanks for info.

I looked around the config of DFM and did not see any similar filters. There is a "rechability settings" in the "Polling Parameters" that can be disabled. Will give it a try.

One more question, the LMS 2.5.1 device support doc. for the Campus says that User Tracking functionality is supported for c1711 routers (just via ARP, there is no mac-table on 1711), there is about 80 of them on the network and no host/IP/mac info is showing for them.

Thanks again


This Discussion