cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1120
Views
10
Helpful
8
Replies

AniStaticConfigException - DeviceDiscovery

david.fernandes
Level 1
Level 1

Hi all,

Running Cworks LMS 2.6 w/ CM 4.0.7. DeviceDiscovery is not starting up, immediating failing after attempting a discovery. The following is the error I've gotten in the log:

2006/10/16 09:01:34 main DiscoveryMain: Loading mib values...complete

2006/10/16 09:01:34 main DiscoveryMain: Loading communities values...complete

2006/10/16 09:01:34 main ERROR DiscoveryMain: AniStaticConfigException: Time base name Devdiscovery not not valid for SMFDefinition com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFCreateSeedDevice

Has anyone else come across this error? If so, what was the resolution?

1 Accepted Solution

Accepted Solutions

Don't remove anything. The first example above is fine. Order is really unimportant in these files.

View solution in original post

8 Replies 8

David Stanford
Cisco Employee
Cisco Employee

have a look at your DeviceDiscovery.properties file and check for the following entry:

DEVICESROOT=

DEVICESPACKAGE=com.cisco.nm.ani.server.devices

DeviceConfigFile=devices.xml

If it is this way above, it needs to be changed to:

DEVICESROOT=D:\\CSCOpx\\campus\\lib\\classpath

DEVICESPACKAGE=com.cisco.nm.ani.server.devices

DeviceConfigFile=devices.xml

Also, if this does not work you may want to contact the TAC as you could have a corrupted DevdiscoverySMFEnd.class file

Looks about the same. I've got a TAC case open but was wondering if others had a similar problem.

# Device factory properties

#

DEVICESROOT=C:\\PROGRA~1\\CSCOpx\\campus\\lib\\classpath

DEVICESPACKAGE=com.cisco.nm.ani.server.devices

DeviceConfigFile=devices.xml

Joe Clarke
Cisco Employee
Cisco Employee

Look at NMSROOT/campus/etc/cwsi/DeviceDiscovery.properties, and look for lines that being with TimeBase. There should be three. Something like:

TimeBase.Devdiscovery.Type=Periodic

TimeBase.Devdiscovery.Schedule=1073741823

TimeBase.Devdiscovery.ThreadPool=Devdiscovery

Hmm. What I have is a bit different. Could this be a new format for the file with w/ LMS 2.6 being installed?

# Thread

TimeBase.Devdiscovery.ThreadPool=Devdiscovery

ThreadPool.Devdiscovery.priority=HIGH

ThreadPool.Devdiscovery.count=48

No, this is wrong. Add the following two lines, and you'll be set:

TimeBase.Devdiscovery.Type=Periodic

TimeBase.Devdiscovery.Schedule=1073741823

Before I pop these in, do I add these lines before what's already there so it becomes:

# Thread

TimeBase.Devdiscovery.Type=Periodic

TimeBase.Devdiscovery.Schedule=1073741823

TimeBase.Devdiscovery.ThreadPool=Devdiscovery

ThreadPool.Devdiscovery.priority=HIGH

ThreadPool.Devdiscovery.count=48

Or do I remove the ThreadPool.Devdiscovery lines and have it just like this:

# Thread

TimeBase.Devdiscovery.Type=Periodic

TimeBase.Devdiscovery.Schedule=1073741823

TimeBase.Devdiscovery.ThreadPool=Devdiscovery

Don't remove anything. The first example above is fine. Order is really unimportant in these files.

Thanks! Discovery is back up and running.

Dave

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco