Ciscoworks2000 problems... 1

[InDenial]

Hi,

We are using Cisco Works 2000 and we are having this weird problem...

We have this configuration database wich consists of component information. From this database and another one wich consist of security related information (passwords, comm strings) we build a file wich we import into CiscoWorks.

We also put a seed device in the list and let it discover the network.

This works great the first time... after that when we ad new components to the database wich we export again and import again into teh database, CiscoWorks just won;t discover the new devices. The seed device will end up unknown and unreachable in topology services.

The only thing that helps is resetting all the processes.

Anyone ever experienced this? if so.. what was the solution to it?..

I have to add that I am not the one managing this machine.. I am just someone who is a user and frustrated about this... it interferes with my work...

CCNA

 

[aayman]

The easy way is to modify the hosts file of the server with all the cisco devices X.X.X.X Host Name
Go to CiscoWork log in as adinn to server configuration\setup\ANI Server Admin\SNMP setting and modify
The file 10.*.*.*ublic:::::rivate if all the devices are in the same subnet use a wildcard address 10.*.*.* make sue that the community names are the same as the devices need to be discovered.

then go to server configuration\setup\ANI Server Admin\Discovery setting and add the seed address and gain if the devices are in the same subnet then select Filter using IP Addresses and puldown menu and select Discover Devices only in these ranges 10.*.*.* and apply to start the discovery.

Ayman

 

[InDenial]

aayman,

Add on info:

our file is created using a script that exports data from a SQL database. The file it creates has the devices in it wich are in our network (3000). The ip ranges we use are a lot.. lets say about 10 switches per subnet will leave us with about 300 subnets. Within these subnets are different kind of devices wich have different usernames passwords and community strings.

So I think you might understand that we are not able to put subnets using wildcards in our file since one device within the subnet would have another community string than another type of device...

From what you are saying I understand that the problem might be that our file is too big and that cw2000 chokes on it.

If that is the case we might have to change our username password and community string policy. Wich I think is possible but would totaly screw up the link with the database we have from wich we create the file we use as the import file.

InD.

CCNA