|
Hi Sean,
I have been contacted by our firewall folks. Our development netview server is pinging a vendors network trying to do a discovery. I have added the subnet 192.168.*.1-100 to the netmon.seed file using the Limit by IP Address -> Exclude panel. I have configured the netmon daemon setup option “Range of automatic discovery” to “Local Subnet Only”. Netview’s address is 42.108.20.183 so should it now only be discovering 42.108.*.* addresses? Netview is still pinging 192.168.*.* every couple of minutes. It looks like it is trying a range of addresses in the same pattern every time. 192.168.90.3 192.168.10.3 192.168.70.3 192.168.254.1 192.168.30.3 Etc What else do I need to disable? I assume this has come about because we have finally been given an smnp community name for a couple of our development Cisco routers to test monitoring our Cisco network. Would netview have picked up a 192.168.*.* address from the router tables from one of these devices and is now trying to discover that subnet? I am not allowed to run NETVIEW again until I get this ship shape. L _______________________________________________ NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)
_______________________________________________ NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only) |
"Sean Lawrence" <Sean.Lawrence@cantire.com>
