CiscoWorks 2000 ANI Server problem

[julian.coelho]

Every time the CW2K server is restarted, Campus Manager starts a discovery and brings down the serial links of our network for about 20 sec. On analysis, we found that the links may not actually reset but that the ANI server is sending massive amounts of traffic to the serial interfaces of the 1601 routers and the routers are reported by Device Fault Manager as they have no free memory available. In normal day-to-day operation, if Campus Manager is shut down, the routers have plenty of memory available. Any reason why the ANI server is flooding the link(interface) with traffic and hence dropping any other normal traffic from reaching? During this period of flooding, even a recurring ping gives continuous timeouts except for one or two replies. This period of traffic burst lasts for about 20 seconds after which the link/interface comes up. Strangely, even though ping fails, a telnet will work – it comes back with the password prompt after a little time though. The links are 64kbps.

Is there any way to tune Campus Manager/ANI server so that it does not send so much traffic after the server is restarted?

[rmushtaq]

What is the the version of Campus Manager and the OS?

[julian.coelho]

Hi

The version of Campus Manager is 3.2 and the OS is Windows 2000 with SP3

[rmushtaq]

SP3 is not supported with Campus 3.2 (CW2K).

[RICHARD MESSINGER]

While SP3 is not supported ie not tested, the next real question is what type of topology do you have?

Is the 1600 router the seed device for your network discovery?

Does it have a large list of CDP neighbors via its serial interfaces?

In the Settings for CiscoWorks, there is a Discovery Performance page that you can set to have CM do a more or less aggressive discovery. By resetting that to a lower level, CW will not have as many threads open to do the discovery so less will be going on and maybe will have less of an impact on the 1600, but the discovery will take a little longer. Once you change the performance metric, you will need to stop and start CiscoWorks for it to take affect.

SP3 might be causing some type of problem, but I would look at these other things first.

[julian.coelho]

Experiencing the same problem with the links/interfaces being reset. We formatted and reinstalled the entire Win 2000 server with SP2 this time. Reinstalled CW2K too. We used the discovery performance at the lowest but still the problem comes up. The seed device is a 3640 router. There are 12 routers and 1 switch in the CDP neighbours of this 3640.

[rmushtaq]

Then I'd suggest that you contact TAC to troubleshoot this problem further.