LMS 3.2 : Campus Manager - User Tracking problem

[Alexander Pickar]

Hi,

We are using LMS 3.2.1 with SP1 and Campus Manager 5.2.2.

Server runs Windows 2003 R2.

Everything runs fine except for User Tracking on two Catalyst 6500 switches running CatOS. These devices are discovered, reachable, SNMP works fine, neighbors seen. But when we try to launch acquisition, the UT utility complains with this error message:

"Failed to start acquisition: Device unreachable. Please enter a valid device."

When we wanted to add ports via Device Trap Configuration, LMS has fired a different error message:

"There are no ports to configure for the selected device(s).Check whether you have selected any router(s)."

I have checked the portsData.xml file, which doesn't have any ports included for the two devices:

    <switch dcrid="22" devicename="idf" imageversion="8.6(4)"

        managed_ip="172.16.YY.XX" oid="1.3.6.1.4.1.9.5.50" os="cat-os" type="C6513">

        <timeInfo>

            <refTime refTimeStamp="1319234509132"/>

        </timeInfo>

        <ips>

            <ip address="172.16.YY.XX"/>

        </ips>

    </switch>

We have tried to exclude / include the switches in the data collection, but that didn't help.

Have you got any idea what is the cause of this problem?

Regards,

Alexander

[Vinod Arya]

What is the CatOS version? And share the sysObjectID of the device as well.

[Alexander Pickar]

Hi,

One of the boxes has outdated CatOS 8.2(2), the other one has a pretty new CatOS 8.6(4).

The sysObjectID, as seen from the CiscoWorks is this:

The following is a SNMP walk of device 172.16.0.81 starting from .1.3.6.1.2.1.1.2

SNMP Walk Output

--------------------------------------------------------------------------------

.1.3.6.1.2.1.1.2

RFC1213-MIB::sysObjectID.0 = OID: CISCO-STACK-MIB::wsc6513sysID

I have tried to set manually the Device Identity via SNMP [Catalyst 6513 with CatOS,

OID: 1.3.6.1.4.1.9.5.50 (Catalyst)], which didn't help.

We have another Catalyst with the same supervisor in our lab, so that I've also tried the older CatOS version 8.2(2) and CiscoWorks 3.2 in the lab, but there everything works fine

I have tried to search some possible causes and perhaps we are hitting bug  CSCtd49439 -  Bug Details

Data Collection never completes, and UT acquisition cannot run?

[Alexander Pickar]

The problem was solved after contacting Cisco TAC.

After some troubleshooting, which was mainly based on the ani.log file, they provided me with updated java classes which finally fixed the problem.