Cisco AS5400XM not manageable on LMS 3.1

benjo.rulloda · ‎04-28-2009

Hi All,

We have a Ciscoworks LMS 3.1 installed in our client and is managing a Cisco AS5400XM. We encountered a problem with DFM version 3.1.0 wherein the device was stuck at Learning state and discovery progress of 10%. We already did some troubleshooting steps like, stop and start of the following processes: EssMonitor, InventoryCollector, TISServer, and Interactor all on separate occasions, but the status was still the same. The main purpose of having the Ciscoworks LMS 3.1 is just to manage the AS5400XM and nothing else. We have to make the device manageable so that we can utilize the email notification feature which is important to the client. Do we need to upgrade the DFM version for it to be manageable? Other modules such as RME and CM do not have any problem with AS5400XM, just the DFM. I noticed one line on the logs that shows:

Apr 28 09:56:54.719: AAA/MEMORY: free_user (0x633F126C) user='NULL' ruser='NULL'

port='tty4' rem_addr='10.0.191.85' authen_type=ASCII service=ENABLE priv=15 vrf

= (id=0)

Where 10.0.191.85 is the IP address of Ciscoworks server. Does this log pertain to the problem we are encountering with DFM?

Appreciate your help on this. Thanks in advance.

Joe Clarke · ‎04-28-2009

Are other devices being managed by DFM correctly? At what percent in the learning process is this device?

benjo.rulloda · ‎04-28-2009

There are no other devices, just the AS5400XM. For about 15 hours, the device is still at Learning state and 10% discovery progress.

Will an upgrade of DFM resolve the issue?

Joe Clarke · ‎04-28-2009

Maybe, but you may be seeing a known bug which currently has no fix. Make sure the fully-qualified domain name of this server is resolvable. That name is the one found on the Computer Name tab of the system properties screen next to "Full computer name".

Also, check to see how many instances of the DLLs msvcm80.dll, msvcp80.dll, and msvcr80.dll are on the system. Where are they, and at what version are they?

benjo.rulloda · ‎04-28-2009

What do you mean when you say the name of the server is resolvable? How can I tell if it is resolvable? Can I test it?

Here are the instances of DLLs we found on the server:

msvcr80.dll

C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap

E:\Ciscoworks\objetcs\smarts\bin

E:\Ciscoworks\objetcs\smarts\lib

E:\Ciscoworks\objetcs\smarts\bin\system

msvcp80.dll

C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap

E:\Ciscoworks\objetcs\smarts\bin

E:\Ciscoworks\objetcs\smarts\lib

E:\Ciscoworks\objetcs\smarts\bin\system

msvcm80.dll

C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

E:\Ciscoworks\objetcs\smarts\bin

E:\Ciscoworks\objetcs\smarts\lib

E:\Ciscoworks\objetcs\smarts\bin\system

We tried to upgrade the DFM version from 3.1.0 to 3.1.2 but there was a warning message that we lack swap space. The swap space that we have is 4096MB while the required one is 7396MB. Is it ok to proceed with the upgrade just having 4096MB swap space?

Joe Clarke · ‎04-28-2009

You can use the nslookup command to test the hostname resolvability.

What are the versions of the DLLs in the WinSxS directory?

No, you need 8 GB of swap space. Just configure another 4 GB.