Cisco Cisco StadiumVision Mobile Maintenance Manual
© 2011 Cisco Systems, Inc. All rights reserved.
Page 3 of 6
Introduction
This document describes how to promote the secondary SVD server to be the
primary server in case of failure. For information about backups and how to restore
them, please reference the Backing Up and Restoring StadiumVision Director
document.
primary server in case of failure. For information about backups and how to restore
them, please reference the Backing Up and Restoring StadiumVision Director
document.
This document also includes instructions when the backup CUAE server needs to
be put into service.
be put into service.
Overview
This process takes the secondary server and makes it the primary and removes the
old primary from the network. In doing so, the secondary server takes the IP
address of the primary. Services on the secondary started up, and if in the middle
of an event, a new script must be run to control the DMPs with the secondary
server. This will cause a disruption in service.
old primary from the network. In doing so, the secondary server takes the IP
address of the primary. Services on the secondary started up, and if in the middle
of an event, a new script must be run to control the DMPs with the secondary
server. This will cause a disruption in service.
Assumptions
The backup StadiumVision Director server is on the same subnet as the primary.
The backup CUAE server is configured to work with the primary StadiumVision
Director server.
StadiumVision Director is using Eth0 and CUAE is using Nic 1.
The CUAE c:\phoneImages directory should have the same content on both
servers.
Failover procedures requires root access to StadiumVision.
Caveats and Limitations
This process is not automatic and requires a minimum of 30 minutes to complete.
After the steps are completed, a script push will be required if you are in an active
event, which can take up to 40 minutes. When pushing the script again, there will
be a service interruption.
After the steps are completed, a script push will be required if you are in an active
event, which can take up to 40 minutes. When pushing the script again, there will
be a service interruption.