LMS 4.2 active-standby

[jbohnenstiehl]

Hello,

We are preparing to upgrade from LMS 3.2 where we run 2 seperate independant instances in seperate locations for redundancy.  Each instance forwards syslog traps to a seperate Openview system in the associated location.  Device updates are manually done on each system.

To reduce costs and administrative overhead we are considering switching to an active-standby environment when we upgrade to LMS 4.2 where the active system would forward traps to both Openview systems.

Doe anyone have experience with an active-standby Ciscoworks LMS 4.2 environment, specifically;

When one system becomes unavailable (due to network, system or application issues) is promoting the standby system to active automatic?

How long does it take?

Does the standby system still monitor syslog events and initiate automated actions?

Has anyone seen instances where the active system stops working or hangs and the standby system does not go active?

Are there any reliability issues with database updates or synchronization from the active system to the standby system?

Is there a way to test communications from the standby system for new device turn-ups without making it active?

I'm a long time reader but first time poster.

Thanks,

Joe

[Marvin Rhoads]

Hi Joe,

Welcome to the forum as a poster. I haven't done any HA setup of LMS installations personally and haven't seen very many inquiries about it either here or elsewhere. It is definitiely possible and is covered in the "Installing and Migrating" guide, chapters 4 and 5.

You might want to check out one of the weekly webcasts that the Cisco Prime product team holds. The folks there are very knowledgable and can advise or steer you to some resources as appropriate. These webcasts are open to both partners and customers. It's a great opportunity to see the product demonstrated by the folks who know it very well and ask questions.