cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
417
Views
5
Helpful
3
Replies

Server architecture for LMS 3.1

philip.r.hayes
Level 1
Level 1

I'm having trouble finding good white papers on the architecture of LMS 3.1.

On the pricing page I saw that to run LMS 3.1 requires two servers. Is that because RME and CM are installed on two separate servers or that the architecure is to have two RME servers running with a master/slave or replication or hot swap standby... or what?

Does anyone have any links on LMS 3.1 server architecture design for the 10,000 device license?

Also, if two RME servers are required does that mean you have purchase two LMS 3.1 licenses? (10,000 devices)

3 Replies 3

Joe Clarke
Cisco Employee
Cisco Employee

For the most part, this guide will help you out:

http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6504/ps6528/ps2425/ps7196/prod_white_paper0900aecd80695cad.pdf

It covers LMS 3.0, but all of the aspects are the same. LMS 3.1 added more virtualization support, and more CPU support.

One RME server can manage 10,000 devices if that's what you want. If you purchase a 10K license, you can build as many servers as you want as long as the total managed device counter per application does not exceed 10K.

In the white paper, it states that the device limit for CM is 5,000. Since the LMS license is for 10,000 does that mean that each CM server you bring up can only handle 5,000?

Does that also mean the CM (under a single LMS 3.1 - 10,000 device license) can be installed on as many servers as you need to just as long as each server does not exceed 5,000?

It would seem to be the only logical conclusion based upon the white paper.

Yes, one license will allow you to build two CM servers each managing up to 5,000 devices. You could also install multiple CM servers provided the total device count does not exceed 10,000.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: