Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1101
Views
0
Helpful
4
Replies

LMS 2.6 Performance

6tschraml
Level 1
Level 1

‎10-19-2006 02:43 AM

I would like to ask a question concerning the network discovery performance of LMS 2.6. A couple of customers have reported that after upgrading from 2.5.1 to 2.6 it takes LMS twice the time to discover the network. Especially major aquisition runs very long. Can you confirm that behaviour? In fact we are not sure if we have a problem with these installations or if LMS just lost performance. I have to mention that the underlying network has not changed after upgrading to 2.6.

Thanks in advance.

Thomas Schraml

Labels:
0 Helpful
4 Replies 4

Joe Clarke
Cisco Employee
Cisco Employee

‎10-19-2006 05:43 AM

I know of no changes in Campus Manager 4.0.6 that would dramatically increase the time to discover the network or perform UT major acquisition. However, UT acquisitions can take a long time on Windows if the end host IP addresses are not resolvable. This is due to the way name resolution works on Windows. This has been the case since the very beginnging, however (see CSCsd58215).

0 Helpful

rpsunbeam
Level 1
Level 1

‎11-07-2006 01:24 PM

I have noticed the same thing, discovery is quick but data collection runs for hours and hours, this morning i watched it run for four+ hours.. on 350 nodes. dunno what it is doing, but that is very long compared to what i'm used to.

0 Helpful

Joe Clarke
Cisco Employee
Cisco Employee
In response to rpsunbeam

‎11-07-2006 03:10 PM

With Data Collection, you can enable various debugs to see what's going on. In particular, framework, frontend, vlad, corex, and core are good choices. Off the top of my head, besides the Windows name resolution problem, you may be running into a delay due to STP fetching. For STP, we need to use community string indexing (v1/v2c) or SNMP contexts (v3). If SNMP is improperly configured, or you're running into a related bug, that could delay Data Collection.

In any event, more information is needed.

0 Helpful

6tschraml
Level 1
Level 1
In response to rpsunbeam

‎11-08-2006 05:05 AM

... in the meanwhile I found bug id CSCsd58215 that describes problems in the DNS environment of UT. But I am not sure that this bug really applies. Currently we have our focus on CM 4.0.7 that has just been released with some interesting statements concerning UT performance improvements in the release note. We are currently checking that out.

Thomas Schraml

0 Helpful
Customers Also Viewed These Support Documents