When you are done configuring the telephony parameters, restart the shadow server by entering restart .

Configuring the MeetingTime Values for the Shadow Server

When you entered the restore command in the Restoring the Database Backup, you copied most of the MeetingTime values from the primary server to the shadow server. Use MeetingTime to manually change any values that were not copied from the primary server to the shadow server.

To Configure MeetingTime Values for the Shadow Server

Log in to the shadow server in MeetingTime.

Go to the Configure tab.

Select Telephony Access from the left pane.

Click Query . Values appear in the right pane.

Verify that the main telephone number and any other applicable parameters are the same for the shadow server as for the primary server. Change any values that are not the same.

Click Save Changes .

Click Server Configuration in the left pane.

Click Query . Values appear in the right pane.

Verify that all values are accurate.

Verify that the Max Recording Space (min.) field is set appropriately for the current configuration.

Verifying that Languages Copied to the Shadow Server

Verify that all languages installed on the primary server are also installed on the shadow server.

Configuring Gateway Routing for the Shadow Server

Configure the gateway routing in one of the following two ways:

If your Cisco Unified MeetingPlace system has a set of backup gateway machines, install and connect them before bringing the shadow server online configured as a shadow server. Set up and connect the backup gateways while the shadow server is in standalone server mode. See Installing and Configuring Cisco Unified MeetingPlace Network Backup Gateway for gateway installation procedures.

When you convert a primary server to a shadow server, the gateways are down. After you convert the shadow server to the primary server, the gateways reconnect.

This section describes how to configure the primary Cisco Unified MeetingPlace Audio Server to automatically accept gateway re-attachment after the Audio Server changes from the shadow server to the primary server.

After you have installed all the gateway software, the gateways appear as a unit attached to the primary Cisco Unified MeetingPlace Audio Server. Each gateway server is automatically assigned a number between 10 and 32.

On the primary Audio Server, use the net command to retrieve all of the network information for each of the gateway units, as in the following example.

bigrock-lat:tech$ net

1) View the server & site configuration

2) Modify the server configuration

3) Select another server (current unit = #0)

99) Quit

Select: 3

Unit: 16

1) View the server & site configuration

2) Modify the server configuration

3) Select another server (current unit = #16)

99) Quit

Select: 1

Current server configuration:

Unit: #16 (MPWeb-SFcisco)

Active: YES

Description:

Kind: Gateway server

IP Address: 172.27.15.158

Ethernet address: 000043388c48

Site: #0 (Home Site)

Site subnet mask: 255.255.254.0

Site broadcast addr: 172.27.7.255

Site default gateway: 172.27.6.1

1) View the server & site configuration

2) Modify the server configuration

3) Select another server (current unit = #16)

99) Quit

Select:

On the shadow server, use the net command to set up network information for all of the gateway units from Step 3. Match the unit number by selecting the same unit number that the gateway appeared under the primary Audio Server database. The network information for each unit must also be set up exactly the same on the shadow Audio Server as on the primary Audio Server.

Note: If you get a warning about site configuration, such as site information is undefined or the site mask is incompatible with the IP address you have assigned to this unit, you can ignore those warnings. Site information is not used in establishing connectivity between gateway and Audio Server.

After the shadow server has been configured with the appropriate network information for the gateways, go back to the gateway server and configure the gateway SIM with the host name of your shadow server. Follow these steps:

Enter the host name of your shadow server in the Shadow Server Name field.

Click OK .

Reboot your gateway server.

If you have more than one gateway unit, repeat Step 3 through Step 5 for each remaining gateway unit.

Switching Behaviors When the Primary Server Fails and the Shadow Server Becomes the Primary Server

Although the Cisco Unified MeetingPlace system supports the concept of primary and shadow servers, with the shadow server as a backup when the primary server fails, the shadow server does not automatically switch from shadow server mode into primary server mode.

Do the following procedure to automatically switch from shadow server mode to primary server mode.

To Switch Behaviors When the Primary Server Fails and the Shadow Server Becomes the Primary Server

Take the primary server offline.

Shut down all gateway units.

Switch the shadow server into primary server mode.

Reboot all gateway units. Gateway units will reattach themselves to the new primary server (formerly the shadow server) when they come up.

Note: Even though the server name listed in the Shadow Server Name field is now functioning as the primary Audio Server, you do not need to modify the values in the Server Name and Shadow Server Name fields in the Server Entry configuration window.

Configuring FlexMenus for the Shadow Server

If the primary server is configured with FlexMenus, configure the shadow server with FlexMenus.

Configuring Custom Prompts for the Shadow Server

If the primary server is configured with custom prompts, configure the shadow server with the same custom prompts.

Configuring Translation Tables for the Shadow Server

The translation tables for the primary server and shadow server may be different, especially if the shadow server is in a different location. The translation tables for the primary server are not replicated, so you need to configure the shadow server translation table to match the primary server translation table.

Restarting the Shadow Server

After configuring the parameters for the shadow server, restart the shadow server.

To Restart the Shadow Server

Access the CLI.

Log in as a technician. The tech$ prompt appears.

At the tech$ prompt, enter restart enable .

Confirm that you want to restart the shadow server by entering y .

Testing the Shadow Server Configuration

The following steps must be done while the shadow server is still in standalone server mode.

Changing the Shadow Server to Act as a Shadow Server

This section explains how to change the shadow server from standalone mode to shadow server mode.

Note: The net command overwrites the setup configuration. Therefore, if you run the net command after you run the setup command, you must run the setup command again.

To Change the Shadow Server to Act as a Shadow Server

Access the CLI.

Log in as a technician. The tech$ prompt appears.

At the tech$ prompt, enter down .

Confirm that you want to bring down the shadow server by entering y .

After the shadow server is down, enter setup . The following example appears:

meetingplace:tech$ setup

This program determines the basic personality of this unit.

Current unit class = SINGLE

Current site class = LOCAL

Select the unit class:

1) MeetingPlace -- Standalone (SINGLE).

5) Shadow Network Server (SHADOW).

99) Quit.

Select:

Select shadow network server by entering 5 . See the following example:

Select: 5

You will now be prompted for host name and IP address of the primary

server.

This information is used to establish the network connection. Please,

when prompted for a host name, enter a proper Internet host name, with

no spaces or funny characters, not the IP address.

Host name of the primary server []:

The Cisco Unified MeetingPlace system prompts you to enter the primary server host name. Enter the proper Internet host name with no spaces, not the IP address.

Continue following the prompts to enter the other necessary information. At the end of the setup, you see an indication that the site class is "REMOTE" and a prompt to update the initialization file as in the preceding example.

Note: The site class is always set to "REMOTE," even if the shadow server is physically located at the same site as the primary server.

Update the initialization file by entering y .

You have selected a new configuration for this unit.

Unit class = SHADOW

Site class = REMOTE

Update the initialization file (y/[n])? y

DONE

NOTE: Changes take effect with the next restart of the unit.

Unit class = SHADOW/REMOTE

Bring the shadow server back up by entering restart enable .

Checking the Configuration

To Check the Configuration

Access the primary server CLI.

Log in as a technician. The tech$ prompt appears.

Enter swstatus .

Verify that the shadow server, unit 9, is connected.

Access the shadow server's CLI.

Enter swstatus .

Verify that the shadow server is connected to the primary server, unit 0.

Wait at least 15 minutes.

If there are meetings taking place on the primary server, log in to the shadow server by using the CLI, then enter cptrace .

If the data is replicating properly, you will see data being logged from the call traces. If there is nothing in the trace, contact Cisco TAC.

Exit the cptrace command by entering q .

Access the primary server CLI.

Enter alarm .

Make a note of any alarms.

Note: While the shadow server is operating in shadow server mode, the telephony interfaces are not active. A connected PBX sees a red T1 alarm on all spans.