Re: Campus Manager Device Discovery

smebbin · ‎05-19-2005

I started a device discovery wih campus manager on May 11th. It keeps on running. How do I get the discovery to stop permananetly. I have tried restarting the server but once the ANI server starts back up it picks up back at where is was before the reboot (Running device discovery). Is this a bug?

nhabib · ‎05-19-2005

Try going to CSCOpx/bin and execute the command:

pdshow DeviceDiscovery

If it says "Never Started" or "Transient Terminated"

then issue the command:

pdexec DeviceDiscovery

smebbin · ‎05-20-2005

Okay. I issued the pdshow command and it does in fact show transient terminated. So upon seeing this I followed your guidance and issued the "pdexec DeviceDiscovery" command. Then I reissued the pdshow command to verify that it is in normal opertion and doesn't still say "transient terminated". It doesn't. So I went back into Device Discovery in campus manager and it still says "running". I have attached a screenshot with what I am referring to. Notice in the screenshot how everything else is updated today but device discovery was last uodated on the 11th of May.

Current Status Refresh

Operation Last Completion Time Result Status Action

Device Discovery 11 May 2005, 11:14:31 PDT 951 Devices Running Start Device Discovery

Campus Data Collection 20 May 2005, 04:10:00 PDT 1028 Devices Idle Start Campus Data Collection

User Tracking Acquisition 19 May 2005, 14:24:54 PDT 1670 End Hosts

0 IP Phones Idle Start UT Acquisition

nhabib · ‎05-20-2005

Check your DeviceDiscovery.log file for any error messages

Also, do you have Multiple Community Strings option enabled?

smebbin · ‎05-20-2005

Muliple Community Strings was on. I took it off and hit apply. Still no change. Then I tried rebooting, still no change.

Attached is the log out as you requested. I couldn't see anything concerning or that would lead me to the problem.

nhabib · ‎05-20-2005

It says that messages will be logged in discovery.log

Anything in there?

smebbin · ‎05-24-2005

I left the box completely alone for 3 days and came back. After doing so it hasn't exhibited the same problem.. weird. No fix action for it. I will consult the other negineers and post to the forum if they did something but I highly doubt it.

nhabib · ‎05-24-2005

glad to hear that all is running fine now

u346874_2 · ‎05-25-2005

I have excastly same problem now on.

Discovery is running and i cant stop it.

I have open TAC case and now waiting answer what can i do.

jdwilson · ‎05-25-2005

Could you please post the TAC responses here, I have the same problem as well.

lwhalley · ‎05-27-2005

I don't know that this is the solution that you need, but I had a similar problem with UT discovery taking up to 12 hours. I issued a TAC on it last week and what they recommended worked. My discovery is now under 2 hours (for about 300 managed devices). So here is the info that I got from the TAC:

This looks like it could be CSCsa18525: ANI discovery runs out of file descriptors.

ANI, particularly User Tracking, discoveries may fail to discover certain elements, or may report that all file descriptors have been exhausted. This problem can occur in large networks where there are many network elements (i.e. network devices and end stations or IP phones) whose IP addresses do not resolve to hostnames.

Add the following to the ANIServer.properties file at

\CSCOpx\campus\etc\cwsi:

Ani.resolve=false

This property will still enable ANI to resolve IP addresses to hostnames; however, it will only do so using the internal system resolver.

After modifying ANIServer.properties, restart the daemon manager from the

CLI:

net stop crmdmgtd

(wait 5 minutes)

net start crmdmgtd

(wait 5 minutes)

So, you may want to look up the Bug ID for more info or ask the TAC if this solution might be the one that you are looking for.

Regards.

u346874_2 · ‎06-01-2005

In our case the DeviceDiscovery.properties file was corrupted. Tac solution below.

The DeviceDiscovery.properties is corrupted and all the important information has been removed which could be the cause of discovery issue.

Do the following:

c:\net stop crmdmgtd

DeviceDiscovery.properties.orig has got the required information. Please copy the orig file to DeviceDiscovery.properties and restart the daemons. Start discovery again.

c:\net start crmdmgtd