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].*.*
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.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...