Cisco Unified MeetingPlace Release 6.1 -- About Restoring the Web Server After Boot Failure
(Created page with "Cisco Unified MeetingPlace Release 6.1 > Web Conferencing > ...")
Newer edit →
Revision as of 16:15, 21 January 2011
The Cisco Unified MeetingPlace Web Conferencing SQL database is created from information that is replicated from the Cisco Unified MeetingPlace Audio Server. The Cisco Unified MeetingPlace Replication Service continues to update this SQL database in real-time as changes occur in the Audio Server database.
The Cisco Unified MeetingPlace Gateway SIM is a common component of the Cisco Unified MeetingPlace gateway products. Gateway SIM functions as the channel through which gateways communicate with the Audio Server. The Gateway SIM allows you to add and delete units from the Audio Server.
Once a unit (gateway server) is attached to a Audio Server, you should only detach it for the following reasons:
- You are replacing an old gateway server with a new server.
- In this case, detach the old gateway server from the Audio Server to decommission it.
- You are replacing the Audio Server with a brand new machine.
- The new Audio Server uses the same database from the old server.
- The new Audio Server uses a brand new database.
- You are testing the gateway server in a lab against a lab Audio Server.
- When the gateway is ready to be put into production, detach it from the lab Audio Server and re-attach it to a production Audio Server.
Web Conferencing stores the hostname of the Audio Server in its SQL database. This hostname is the value you entered when you installed Web Conferencing. To prevent SQL database corruption, when the web server boots up, it compares this hostname with the hostname of the Audio Server that is configured in the Gateway SIM. If they do not match, Web Conferencing considers the Audio Server to have changed and fails to boot up.
To restore the Cisco Unified MeetingPlace web server after boot failure, see the How to Restore the Web Server After Boot Failure.