19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

Hot Backup<br />

<strong>Guide</strong>lines<br />

Hot Backup implements a high availability and rapid recovery solution.<br />

Two <strong>RMX</strong>’s are configured in a Master/Slave relationship: the Master MCU is active while the<br />

Slave acts as a passive, fully redundant Hot Backup of the Master MCU.<br />

All conferencing activities and configuration changes that do not require a System Reset are<br />

mirrored on the Slave MCU five seconds after they occur on the Master MCU.<br />

In the event of failure of the Master MCU, the Slave MCU transparently becomes active and<br />

assumes the activities and functions with the backed up settings of the failed Master MCU.<br />

Both dial-in and dial-out participants are automatically dialed out and reconnected to their<br />

conferences. However, the Hot Backup solution is optimized for dial-out participants as all<br />

the dial-out numbers are defined in the system and are available for redialing.<br />

The following entities are automatically backed up and updated on the Slave MCU:<br />

• Ongoing Conferences<br />

— Layout<br />

— Video Force<br />

— Participant Status (Muted, Blocked, Suspended)<br />

• Reservations<br />

• Meeting Rooms<br />

• Entry Queues<br />

• SIP Factories<br />

• Gateway Profiles<br />

• IVR services (excluding .wav files)<br />

• Recording Link<br />

• Profiles<br />

• IP Network Settings:<br />

— H.323 settings<br />

— SIP settings<br />

— DNS settings<br />

— Fix Ports (TCP, UDP) settings<br />

— QoS settings<br />

• Both Master and Slave MCUs must have the same software version installed.<br />

• The Users list and Passwords must be the same on both the Master and Slave MCUs.<br />

• There must be connectivity between the Master and Slave MCUs, either on the same<br />

network or on different networks connected through routers.<br />

• In the event of failure of the Master MCU the Slave MCU assumes the role of the Master<br />

MCU. The Master/Slave relationship is reversed: the Slave, now active, remains the<br />

Master and the previous Master MCU, when restarted, assumes the role of Slave MCU.<br />

• No changes to the Slave MCU are permitted while it is functioning as the Hot Backup.<br />

Therefore no ongoing conferences or reservations can be added manually to the Slave<br />

MCU.<br />

20-36 <strong>Polycom</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!