Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Device Discovery Seed Connect Problem

Hi

we were on network one . now after migration we are on other network A.B.26.*. but our seed devices are on other network A.B.25.*

every time i try to start device discovery on LMS 2.6 i get this error (from log)

2010/02/05 12:46:14 main ERROR SMFFactoryLoader: java.lang.NullPointerException
2010/02/05 12:46:14 main ERROR DiscoveryMain: AniStaticConfigException: Error accessing devices--root path , packageName com.cisco.nm.ani.server.devices

complete log attached

BR

8 REPLIES
Cisco Employee

Re: Device Discovery Seed Connect Problem

Exactly what version of Campus Manager do you have?

New Member

Re: Device Discovery Seed Connect Problem

Cisco Employee

Re: Device Discovery Seed Connect Problem

You should really consider upgrading to LMS 2.6 SP1 which includes RME 4.0.6, CS 3.0.6, and Campus 4.0.12.  These upgrades are available from Common Services > Software Center > Software Update.

For this issue, post the NMSROOT/campus/etc/cwsi/DeviceDiscovery.properties.

New Member

Re: Device Discovery Seed Connect Problem

I want to upgrade but every time i connect this server to internet and try update in the log i see that my name/password is not ok but it is ok. (i dont understand why cant update)

DeviceDiscovery.properties

AniName=DeviceDiscovery
Server.version=5.0
Server.copyright=Copyright (C) 1997-2004 Cisco Systems, Inc., All rights reserved
TimeBase.Devdiscovery.Type=Periodic
TimeBase.Devdiscovery.Schedule=1073741823
ServiceModuleList=Devdiscovery
ServiceModulePackage=com.cisco.nm.ani.server
ServiceModule.Devdiscovery=com.cisco.nm.ani.server.devdiscovery.DevdiscoveryServiceModule
TimeBase.Devdiscovery.ThreadPool=Devdiscovery
ThreadPool.Devdiscovery.priority=HIGH
ThreadPool.Devdiscovery.count=48
snmp.maxRows=50000
snmp.threads.min=15
snmp.threads.max=48
snmp.maxRetry=1
snmp.timeoutSecs=6
snmp.retryPolicy=com.cisco.nm.lib.snmp.lib.ExpRetryPolicy
snmp.defaultReadCmty=public
snmp.defaultWriteCmty=private
snmp.getBulkSize=10
snmp.encryptCommunity=false
snmp.EnableMultiple=false
snmp.version2c=on
MibInfo=mibinfo.dat
CommunityFile=discoverysnmp.conf
DEVICESROOT=
DEVICESPACKAGE=com.cisco.nm.ani.server.devices
DeviceConfigFile=devices.xml
DeviceAppConfigFile=anidevices.xml
DB.driver=com.sybase.jdbc2.jdbc.SybDriver
DB.url=jdbc:sybase:Tds:localhost:43443?SERVICENAME=aniDb
DB.dsn=ani
DB.Connection.Timeout=60000
DB.Connection.MinIdleTime=60000
DB.ReaperSleepTime=30000
AniDBNullColumnValidation=false
Ani.sendEvents=false
DB.WriteClassListToDb=false
nameserver.usedns=false
nameserver.useloopbackaddress=false
nameserver.resolveByName=false
nameserver.resolveBySysName=false
nameserver.updateDCRDisplayName=false
nameserver.updateDomainNameSuffix=false
Discovery.router=on
Discovery.seed=157.206.25.190:157.206.25.189:157.206.26.50:157.206.26.51:157.206.26.34:157.206.26.54
LogMsg.logfile=D:\\CW-LMS\\log\\discovery.log
LogMsg.state=enable
LogMsg.threadStamp=true
LogMsg.timeStamp=true
LogMsg.deviceId=false
LogMsg.logFileSize=1000000
Discovery.subnets.include=157.206.26.*:157.206.25.*
LogMsg.deviceList=
LogMsg.trace=frontend:framework:devdiscovery:devices:devices.AccessPoint:devices.AppHost:devices.C1200:devices.C2800:devices.C2900XL:devices.C2900XL.C2900XL_11_2_8_SA4:devices.C2900XL.C2900XL_12_0_5_XP:devices.C2900XL.C2950:devices.C3900:devices.C3K:devices.C5K:devices.C5K.C3750:devices.C5K.C4K:devices.C5K.C4K.C4KIOS:devices.C5K.C4K.C4KIOS.C4KIOS_12_1_13_EW1:devices.C5K.C4K.C4K_5_2_1:devices.C5K.C4K.C4K_5_5_1:devices.C5K.C5500:devices.C5K.C5500.C5500_2_2_1:devices.C5K.C5500.C5500_2_4_3:devices.C5K.C5500.C5500_3_1_0:devices.C5K.C5500.C5500_4_1_0:devices.C5K.C5500.C5500_4_4_1:devices.C5K.C5500.C5500_5_2_1:devices.C5K.C5500.C5500_5_5_1:devices.C5K.C5500.C6K:devices.C5K.C5500.C6K.C3550:devices.C5K.C5500.C6K.C3550.C3550_12_1_11_EA1:devices.C5K.C5500.C6K.C6KIOS:devices.C5K.C5500.C6K.C6K_5_2_1:devices.C5K.C5500.C6K.C6K_5_5_1:devices.C5K.C5500.C6K.C6K_6_1_0:devices.C5K.C5K_2_2_1:devices.C5K.C5K_2_4_3:devices.C5K.C5K_3_1_0:devices.C5K.C5K_4_1_0:devices.C5K.C5K_4_4_1:devices.C5K.C5K_5_5_1:devices.CSS11K:devices.Hub:devices.ICS7750:devices.LS1010:devices.MSS:devices.MSS.IgxBpx:devices.NetScout:devices.Router:devices.Router.C2611:devices.Router.C4224:devices.Router.CE:devices.Router.DSL:devices.Router.MDS:devices.Router.ONS:devices.Router.RSM:devices.Unknown:devices.C5K.C5K_5_2_1:
LogMsg.debug=frontend:framework:devdiscovery:devices:devices.AccessPoint:devices.AppHost:devices.C1200:devices.C2800:devices.C2900XL:devices.C2900XL.C2900XL_11_2_8_SA4:devices.C2900XL.C2900XL_12_0_5_XP:devices.C2900XL.C2950:devices.C3900:devices.C3K:devices.C5K:devices.C5K.C3750:devices.C5K.C4K:devices.C5K.C4K.C4KIOS:devices.C5K.C4K.C4KIOS.C4KIOS_12_1_13_EW1:devices.C5K.C4K.C4K_5_2_1:devices.C5K.C4K.C4K_5_5_1:devices.C5K.C5500:devices.C5K.C5500.C5500_2_2_1:devices.C5K.C5500.C5500_2_4_3:devices.C5K.C5500.C5500_3_1_0:devices.C5K.C5500.C5500_4_1_0:devices.C5K.C5500.C5500_4_4_1:devices.C5K.C5500.C5500_5_2_1:devices.C5K.C5500.C5500_5_5_1:devices.C5K.C5500.C6K:devices.C5K.C5500.C6K.C3550:devices.C5K.C5500.C6K.C3550.C3550_12_1_11_EA1:devices.C5K.C5500.C6K.C6KIOS:devices.C5K.C5500.C6K.C6K_5_2_1:devices.C5K.C5500.C6K.C6K_5_5_1:devices.C5K.C5500.C6K.C6K_6_1_0:devices.C5K.C5K_2_2_1:devices.C5K.C5K_2_4_3:devices.C5K.C5K_3_1_0:devices.C5K.C5K_4_1_0:devices.C5K.C5K_4_4_1:devices.C5K.C5K_5_5_1:devices.CSS11K:devices.Hub:devices.ICS7750:devices.LS1010:devices.MSS:devices.MSS.IgxBpx:devices.NetScout:devices.Router:devices.Router.C2611:devices.Router.C4224:devices.Router.CE:devices.Router.DSL:devices.Router.MDS:devices.Router.ONS:devices.Router.RSM:devices.Unknown:devices.C5K.C5K_5_2_1:

Cisco Employee

Re: Device Discovery Seed Connect Problem

Your upgrade issue is most likely CSCsg47200.  You will need to manually get the CS 3.0.6 upgrade from http://www.cisco.com/cgi-bin/tablebuild.pl/cd-one-3des .

As for the Discovery issue, I need you to attach the file, not post it inline.

New Member

Re: Device Discovery Seed Connect Problem

many thanks for that link we were not able to find it

for that device discovery:

DeviceDiscovery.properties attached (it without comments - i deleted them in our original file)

Cisco Employee

Re: Device Discovery Seed Connect Problem

Try this file.  Replace your existing DeviceDiscovery.properties with this one.

New Member

Re: Device Discovery Seed Connect Problem

I owe you so many bears

update is great and discovery is working perfectly

MANY THANKS

367
Views
0
Helpful
8
Replies
CreatePlease to create content