cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
381
Views
0
Helpful
1
Replies

IPM and dynamic user tracking not running properly.

Hello, I've got two problems after a reinstallation of CiscoWorks LMS 3.2.

Versions of software components:
LMS-3.2
Campus Manager-5.2.1
CiscoView-6.1.9
CiscoWorks Assistant-1.2.0
CiscoWorks Common Services-3.3.0
Device Fault Manager-3.2.0
Integration Utility-1.9.0
Internetwork Performance Monitor-4.2.0
LMS Portal-1.2.0
Resource Manager Essentials-4.3.0

First probelm I have sounds pretty much like this thread:
https://supportforums.cisco.com/message/3064784#3064784
Source device is a WS-C3560-8PC - 12.2(55)SE1 - C3560-IPSERVICESK9-M

I configured a IPM collector, if I have a look at the "Collector Management" the collector is running and I can also monitor the running collector.
But if I have a look at the running config of the switch, there is no ip sla collector configuration but I can see the ip sla statistics via the show command.

#sh ip sla configuration 135123
IP SLAs, Infrastructure Engine-II.

Entry number: 135123
Owner: ipm|XXXS1077
Tag: QA-Site1-Site2
Type of operation to perform: udp-jitter
Target address/Source address: target ip address/source ip address
Target port/Source port: 2000/0
Type Of Service parameter: 0xB8
Operation timeout (milliseconds): 5000
Codec Type: g729a
Codec Number Of Packets: 1000
Codec Packet Size: 32
Codec Interval (milliseconds): 20
Advantage Factor: 12
Verify data: No
Vrf Name:
Control Packets: enabled
Schedule:
    Operation frequency (seconds): 60
    Next Scheduled Start Time: Start Time already passed
    Group Scheduled : FALSE
    Randomly Scheduled : FALSE
    Life (seconds): Forever
    Entry Ageout (seconds): 3600
    Recurring (Starting Everyday): FALSE
    Status of entry (SNMP RowStatus): Active
Threshold (milliseconds): 5000
Distribution Statistics:
    Number of statistic hours kept: 2
    Number of statistic distribution buckets kept: 1
    Statistic distribution interval (milliseconds): 20
Enhanced History:


#sh ip sla statistics

Round Trip Time (RTT) for       Index 135123
Type of operation: jitter
        Latest RTT: 45 ms
Latest operation start time: 14:36:31.759 MET Wed Mar 16 2011
Latest operation return code: OK
RTT Values
        Number Of RTT: 1000
        RTT Min/Avg/Max: 21/45/60 ms
Latency one-way time milliseconds
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0 ms
        Destination to Source Latency one way Min/Avg/Max: 0/0/0 ms
Jitter time milliseconds
        Number of SD Jitter Samples: 999
        Number of DS Jitter Samples: 999
        Source to Destination Jitter Min/Avg/Max: 0/3/15 ms
        Destination to Source Jitter Min/Avg/Max: 0/1/9 ms
Packet Loss Values
        Loss Source to Destination: 0           Loss Destination to Source: 0
        Out Of Sequence: 0      Tail Drop: 0
        Packet Late Arrival: 0  Packet Skipped: 0
Voice Score Values
        Calculated Planning Impairment Factor (ICPIF): 11
MOS score: 4.06
Number of successes: 18
Number of failures: 0
Operation time to live: Forever

#sh run all | include 135123

Any suggestions? Am I right?

The second problem is about the dynamic user tracking like these theads https://supportforums.cisco.com/message/3135881#3135881 or
https://supportforums.cisco.com/message/3195492#3195492
Access switches are configured properly, the configuration ran without any problems with the previous installation.
No changes done at the configuration, using the default trap listener port etc.
In the macuhic.log file I get entries like in the attached txt.

When I try to run a full Campus Manager Data Collection I get the following errormessage:
Failed to start acquisition: Construction of XML data required for UT is in progress.Please try after some time

Also any suggestions? Am I right, too?

Everyone's tags (2)
1 REPLY 1
Highlighted
Hall of Fame Cisco Employee

Re: IPM and dynamic user tracking not running properly.

By default IP SLA collectors installed by IPM do not appear in the running configuration.  If you want to install the collectors into the running configuration, then set the "Copy IPSLA Configuration to running-config" property under IPM > Admin > Application Settings, then delete and recreate the collector.

Your Campus problem could be CSCtd49439 (a patch is available by contacting TAC).  However, you should start a new thread for your Campus problem.

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards