The database must contain less that 100,000 end hosts to be supported. If you have more than this, you will need to split the network across two instances of Campus Manager. You should also consider upgrading to LMS 2.6 with Campus Manager 4.0.7. A bug was fixed in the 2.6 release that could cause UT to fail due to memory exhaustion even when running with a supported number of end hosts.
If after upgrading, and after reducing the number of end hosts to <= 100,000, you still see a problem, take a look at the ut.log file to see if there are any errors or exceptions.
do you mean by "split the network across two instances of Campus Manager", installing a second copy of CM on another server, and setup a certain number of devices on the first CM server and the rest on the second, in order to have 100,000 UT entry maximum in each database?
Correct. You will need Campus Manager to manage X number of devices in Server 1 and Y number of devices on Server 2. Here, X and Y are numbers of network devices that will yield a number of end hosts <= 100,000. But you must upgrade as well. The memory fixes that went into CM 4.0.6 are vital for a network of such a size.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...