Questions on LMS master-slave pairing

yjdabear · ‎11-20-2008

Premise: Two LMS servers with identical set of applications (DCR/CS, RME, CM, and IPM).

Would the master-slave setup work across different versions of LMS, say one 2.6 and one 3.1?

What else gets synchronized, outside of the DCR? Do NetConfig jobs scheduled on the master get sync'ed to the slave, or vice versa?

Provided two LMS servers were formerly standalone, what happens to its local collections (device configs inventory info, NetConfig jobs, UT jobs, reports, etc.) if one LMS server is made a slave to the other?

Do master-slave pairs continue to perform their own independent collections/polling/NetConfig ops?

Joe Clarke · ‎11-20-2008

DCR master/slave works just fine across disparate versions of LMS provided the master is always running the highest version (3.1 in this case). I will say, though, that due to bugs I recommend both servers run 3.1 if you are going to integrate with ACS.

As for what is synchronized, it will only be DCR. No other data will be shared. When a standalone server is demoted to a slave, you have the option of sending its devices to the master. However, in either case, since the DCR IDs will change, the inventory, config archive, etc. on the slave will be lost.

The master and slave will continue to do their own polling, and run their own jobs.

yjdabear · ‎11-21-2008

If you don't mind sharing, are there any plans to make NetConfig jobs synchronized across multiple master/slave servers?

Joe Clarke · ‎11-21-2008

Not in the near future. More advanced HA is one of the discussion topics for our next generation NMS platform.