why ciscoworks ping switches?

[zhichao]

Hi

Do you know which componenet of ciscoworks is ping network devices?

Our network is linked to a partner network with 10.x.x.x. We found CW LMS is ping their 10.x.x.x network.

We then disabled CDP on the link, but the ping still going on. Any idea?

Thanks!

[steve.busby]

Many of the components of CW2K use ICMP to test connectivity, response time, availability, etc.

If you want to keep CW2K out of your partner network, you'll need to remove those devices from ANI, RME, DFM, etc. Then goto Server Configuration>Setup>Discovery Settings, under Filtering Criteria (Optional), add the IP Address Range for your partner network. If you still find CW2K trying to access areas it shouldn't, you could create appropriate ACLs.

[zhichao]

Hi

Under ANI server admin->discovery settings->filtering criteria (optional), we have select

'discover devices only in these ranges':192.168.*.*

After we turn on this, CW2K is still ping 10.x.x.x

Where else can we change the settings?

Thanks

[steve.busby]

Try it this way:

In "Discovery Settings", put one of your routers in as a seed device and deselect "Jump Router Bounderies". Then in the filter area, use the drop down box and change it from "Discover devices only in these ranges" to "Do not discover devices in these ranges", then put your partner's IP range in the ip range box.

[georg.tresselt]

I'd rather take RME's availability poller for the culprit.

[steve.busby]

I agree and that's why I suggested he remove the partner's devices from all CW2K compontent DBs. The last steps were to put some filters on ANI so it doesn't discover in areas it's not suppose to.

[nawas]

cisco Works pings devices in 3 areas

1. Availaibilty polling

2. Inventory Poller

3. UT ping sweep