cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
868
Views
0
Helpful
2
Replies

LMS 3.0.1 running in master/slave

cmartinvalle
Level 1
Level 1

Hi,

we have 2 LMS 3.0.1, one is running as master and the other one as slave. They have only one DCR (configured in the master LMS, the slave is pointing at the master DCR).

Now we have a question: if the master server fails and it cannot run, how would be affected the slave server?

We have this question because there is only one DCR and it's configured in the master server...

Thanks a lot.

2 Accepted Solutions

Accepted Solutions

Joe Clarke
Cisco Employee
Cisco Employee

This is impossible. Every LMS server must have its own DCR. In master/slave mode, the DCR data is replicated across all nodes. If the master goes down, the slave continues to operate, and all applications on the slave server will continue to use the slave's DCR data.

View solution in original post

akemp
Level 5
Level 5

As Joe pointed out, the minimum installation for a slave server includes the common services package, thats where the DCR inventory is held weather its a master or slave is immaterial, it has to exist. The role of the Master is to be the authorative source for inventory information, it syncronizes via the system identity account (really should be named cluster identity but I digress) copying and deleting devices until its an exact copy.

View solution in original post

2 Replies 2

Joe Clarke
Cisco Employee
Cisco Employee

This is impossible. Every LMS server must have its own DCR. In master/slave mode, the DCR data is replicated across all nodes. If the master goes down, the slave continues to operate, and all applications on the slave server will continue to use the slave's DCR data.

akemp
Level 5
Level 5

As Joe pointed out, the minimum installation for a slave server includes the common services package, thats where the DCR inventory is held weather its a master or slave is immaterial, it has to exist. The role of the Master is to be the authorative source for inventory information, it syncronizes via the system identity account (really should be named cluster identity but I digress) copying and deleting devices until its an exact copy.