Configuration and Maintenance Guide for MeetingPlace 7.1 - Monitoring and Maintaining Cisco Unified MeetingPlace Web Conferencing [Cisco Unified MeetingPlace]

Table Of Contents

Monitoring and Maintaining Cisco Unified MeetingPlace Web Conferencing

IIS File Deletion

Configuring the Web Server to Synchronize with an NTP Server

How to Manually Synchronize the Web Server with an NTP Server

Querying Which NTP Server You Are Using

Setting the NTP Server

Checking the Delta Between the Local PC Clock and the NTP Server

Manually Synchronizing the Web Server with the NTP Server

How to Manually Synchronize the Web Server in a Domain

Pointing the Domain Controller to the External NTP Source

Changing the Registry Setting on the Web Server

Configuring the Application Server to Point to a Different NTP Server

Changing the Time Zone

Checking Which Conferences Are Currently Running

Checking the Versions of Local Cisco Unified MeetingPlace Web Conferencing Services

How to Schedule a Maintenance Window

Reserve All Ports Meetings

Scheduling a Maintenance Window

Optimizing the Performance of a Web Server

Rebooting the Server

How to Monitor Cisco Unified MeetingPlace Web Conferencing Activities

Using the Cisco Unified MeetingPlace Eventlog

Running the Windows Performance Monitoring Tool

Viewing an Event with the Windows Event Viewer

How to Configure the Lumberjack Logging Utility

Lumberjack Logging Utility

Configuring Lumberjack on a Cisco MCS Server

Manually Generating a Lumberjack Snapshot

How to Switch the Order of IP Addresses on the Web Server

Changing the Binding Order for a System with One IP Address on Each NIC

Changing the Binding Order for a System with Two IP Addresses on One NIC

Making the Change in the Application

Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

Removing the Connection to the Application Server

Changing the IP Address or Hostname of the Application Server

Changing the Domain Name of the Application Server

Changing the IP Address for a Domain Name Server or a Network Time Protocol Server

Updating DNS Entries

Re-establishing a Connection to an Application Server

Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

Changing IP Addresses and Hostnames for the Replicated Application Servers

Turning on Replication

Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

Entering Updated Hostnames and IP Addresses on Cisco WebEx Node for MCS

Updating the Cisco WebEx Site

Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Turning Off SSL on Internal and External Cisco Unified MeetingPlace Web Servers

Turning Off SMA for Cisco Unified MeetingPlace Web Server

Turning On SMA for Cisco Unified MeetingPlace Web Server

Monitoring and Maintaining Cisco Unified MeetingPlace Web Conferencing

Release 7.1

Revised: May 30, 2013 10:51 am

We recommend that you monitor heavily used systems at short intervals, such as biweekly or weekly. Monitor systems with lighter use less frequently, such as once a month.

•IIS File Deletion

•Configuring the Web Server to Synchronize with an NTP Server

•How to Manually Synchronize the Web Server with an NTP Server

•How to Manually Synchronize the Web Server in a Domain

•Changing the Time Zone

•Checking Which Conferences Are Currently Running

•Checking the Versions of Local Cisco Unified MeetingPlace Web Conferencing Services

•How to Schedule a Maintenance Window

•Optimizing the Performance of a Web Server

•Rebooting the Server

•How to Monitor Cisco Unified MeetingPlace Web Conferencing Activities

•How to Configure the Lumberjack Logging Utility

•How to Switch the Order of IP Addresses on the Web Server

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

IIS File Deletion

Deleting the default SMTP virtual server or the Administration website in IIS does not have any effect on Cisco Unified MeetingPlace Web Conferencing web pages.

Subfolders under wwwroot, such as images, _private, _vti_cnf, _vti_log, _vti_pvt, _vti_script and _vti_txt folders all come from Microsoft FrontPage. Deleting these subfolders can cause difficulty with Microsoft FrontPage when publishing to that server.

Parent Paths are enabled in the Default website, the MPWeb virtual directory and the cgi-bin virtual directory. Enabling Parent Paths allows anonymous users to use `..' to move from the current directory to the parent. Disable this function to prevent such users from traversing the directory tree.

Configuring the Web Server to Synchronize with an NTP Server

Cisco Unified MeetingPlace Web Conferencing automatically sets up the Windows operating system to use the Windows Time Service to synchronize its clock with the NTP server. This keeps the Web Server synchronized with the Cisco Unified MeetingPlace Application Server.

You can also configure the Web Server to synchronize with an alternate NTP server. However, we recommend that all components in a Cisco Unified MeetingPlace system use the Application Server as their NTP time source.

Caution Do not manually adjust the clock on the Web Server computer. Doing so could cause the Web Server to crash. To make a one-time manual adjustment, stop the Cisco Unified MeetingPlace Web Conferencing master service and restart it.

Note If the time is not properly synchronized between the Web Server and the Application Server, web recordings may be either completely silent or the audio and web conferencing portions of a web recording will not be timed correctly.

Before You Begin

•Stop the Cisco Unified MeetingPlace Web Conferencing master service. See Stopping All Web Conferencing Services in the Managing Cisco Unified MeetingPlace Web Conferencing Services module.

•Be aware of the following:

–By default, NTP uses UDP port 123. If your Web Server is in the DMZ and your Application Server is not, you will have to open UDP port 123 in your firewall for the default NTP configuration to work. The default configuration is the Web Server synchronizing with the Application Server as the NTP server.

–If you decide to use an alternate NTP server for your Web Server time synchronization, make sure that your NTP setup keeps the Cisco Unified MeetingPlace Application Server and Web Server perfectly synchronized. If the two servers are not time synchronized, certain features will not work.

–When you restart the Web Server, all manual changes made to the registry are lost.

Restrictions

Do not adjust the clock on the Windows computer while the web conferencing application is running.

Procedure

Step 1 Double-click the Window Time icon on the Windows system tray.

Step 2 Select the Internet Time tab.

Step 3 Select to automatically synchronize with an Internet time server.

Step 4 Specify your server name inside the Server: field.

Related Topics

•Cisco Unified MeetingPlace Web Conferencing Service and NTP Servers in the Managing Cisco Unified MeetingPlace Web Conferencing Services module

What to Do Next

We highly recommend that you manually verify that the clocks on the Cisco Unified MeetingPlace Application Server and your Web Server are synchronized. Use the date command on the Application Server to obtain the current date and time.

How to Manually Synchronize the Web Server with an NTP Server

Complete the following procedures in the order shown.

Note We recommend that all components in a Cisco Unified MeetingPlace system use the Application Server as their NTP time source.

•Querying Which NTP Server You Are Using

•Setting the NTP Server

•Checking the Delta Between the Local PC Clock and the NTP Server

•Manually Synchronizing the Web Server with the NTP Server

Querying Which NTP Server You Are Using

Procedure

Step 1 Open a DOS command window.

Step 2 Enter the following command: net time /querysntp

What to Do Next

Proceed to the "Setting the NTP Server" section.

Setting the NTP Server

Procedure

Step 1 Open a DOS command window.

Step 2 Enter the following command: net time /setsntp:xyz where xyz = the ip address or hostname of the NTP server.

What to Do Next

Proceed to the "Checking the Delta Between the Local PC Clock and the NTP Server" section.

Checking the Delta Between the Local PC Clock and the NTP Server

Before You Begin

•Complete the "Setting the NTP Server" section.

•Make sure that the Windows Time Service in the Services Control Panel is started.

Procedure

Step 1 Open a DOS command window.

Step 2 Enter the following command: w32tm /monitor /computers:xyz where xyz is an NTP source.

What to Do Next

Proceed to the "Manually Synchronizing the Web Server with the NTP Server" section.

Manually Synchronizing the Web Server with the NTP Server

Before You Begin

•Complete the "Checking the Delta Between the Local PC Clock and the NTP Server" section.

•Make sure that the Windows Time Service in the Services Control Panel is started.

Procedure

Step 1 Open a DOS command window.

Step 2 Enter the following command: w32tm /resync

How to Manually Synchronize the Web Server in a Domain

Complete the following tasks in the order presented to synchronize the time between your Cisco Unified MeetingPlace Application Server and Cisco Unified MeetingPlace Web Server if your Web Server machine is part of a domain.

•Pointing the Domain Controller to the External NTP Source

•Changing the Registry Setting on the Web Server

•Configuring the Application Server to Point to a Different NTP Server

Pointing the Domain Controller to the External NTP Source

Before You Begin

•This procedure is completed on the Domain Controller that includes the Cisco Unified MeetingPlace Web Server as part of its domain.

•Use export to save all of the registry settings to a flat file.

Procedure

Step 1 Open a command prompt.

Step 2 Enter the following command: net stop W32Time

Step 3 Point the domain controller to the external NTP source:

•Run the following command: w32tm /config /manualpeerlist:<NTP provider> /syncfromflags:manual /reliable:yes /update

•An example of an NTP provider is clock.cisco.com.

Step 4 If the previous command completed successfully, enter the following command: net start W32Time

Step 5 Verify that the external NTP source is active:

•Run the following command: w32tm /stripchart /<NTP provider> /samples:2/dataonly

•The output should show the local time and the external NTP provider time. Compare the two times to confirm that there are not any differences between them.

What to Do Next

Proceed to the "Changing the Registry Setting on the Web Server" section.

Changing the Registry Setting on the Web Server

Before You Begin

•This procedure is completed on the Cisco Unified MeetingPlace Web Server that is part of the domain.

•Complete the "Pointing the Domain Controller to the External NTP Source" section.

•Use export to save all of the registry settings to a flat file.

Procedure

Step 1 Open a command prompt.

Step 2 Enter the following command: net stop W32Time

Step 3 Run the following command: w32tm /unregister

Step 4 Run the following command: w32tm / register

Step 5 Change the value of the registry setting "HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type" to NT5DS

Initially, this will be set to NTP.

Step 6 Enter the following command: net start W32Time

Step 7 Run w32tm /dumpreg to verify that all of the registry settings are correct.

Note If you upgrade or reboot the Web Server, all manual changes made to the registry by the W32Time command are lost.

Note Do not expect the Web Server to match the external NTP source immediately after starting the w32time service. Synchronizing the time between the two systems will occur gradually.

What to Do Next

Proceed to the "Configuring the Application Server to Point to a Different NTP Server" section.

Configuring the Application Server to Point to a Different NTP Server

The Application Server currently points to the NTP server on the Application Server itself. Complete this procedure to point the Application Server to the NTP server referred to by the domain controller.

Before You Begin

•This procedure is completed on the Cisco Unified MeetingPlace Application Server that the Web Server points to.

•Complete the "Changing the Registry Setting on the Web Server" section.

Procedure

Step 1 Sign in to the Cisco Unified MeetingPlace Application Server by using SSH with valid credentials.

Step 2 Run the Net command and choose option 1 to list the current configuration.

The current configuration should point to the NTP server that is on the Application Server.

Step 3 Select option 6 to configure the NTP Service.

Step 4 When finished, select option 1 again to verify that the NTP provider is set correctly.

Changing the Time Zone

If the Windows time zone does not match the Cisco Unified MeetingPlace Web Server time zone, you must correct this discrepancy. The time zones may not match because you forgot to set the correct Windows time zone before installing Web Conferencing or because you have to relocate your Web Server from one time zone to another and you need to change the Windows time zone as part of this relocation.

To determine whether the time zones match, open the Web Conferencing log, called GWSIM_eventlog_XXX.txt, and search for the string "time zone".

If the time zones are the same, you will see a message similar to this:
Information: CompareTimeZone: Time Zones are the same between Cisco Unified MeetingPlace 
Web Conferencing and Breeze. Cisco Unified MeetingPlace Web Conferencing: (GMT-08) Pacific 
Standard Time and Breeze: (GMT-08:00) Pacific Time (US)
If the time zones are not the same, the system logs an error and you see a message similar to this:
MasterSvc Error: **** Time Zones are NOT matching between Cisco Unified MeetingPlace Web 
Conferencing and Breeze. Time Zone Offset-- Cisco Unified MeetingPlace Web Conferencing: 
GMT:+01 Breeze: GMT:-08 
To change the time zone, follow these instructions:

Procedure

Step 1 Stop the Cisco Unified MeetingPlace Web Conferencing master service on all Cisco Unified MeetingPlace Web Servers that use the same database.

Step 2 Open the SQL Server Query Analyzer on the computer where the Web Conferencing SQL database is located by following these steps:

a. Select Start > Programs > Microsoft SQL Server > Query Analyzer.

b. In the SQL Server field, select (local).

c. Select SQL Server authentication.

d. Enter the login name of "sa" and the password.

e. Select OK.

Step 3 Select Query > Change Database.

Step 4 Highlight the name of the slave database (such as MPWEB_XXXX_XXXX), and select OK.

Step 5 Enter the following SQL string:
select * from PPS_ENUM_TIME_ZONES 
Step 6 Select Execute Query.

Step 7 Look through the time zone records and find your time zone ID from the TIME_ZONE_ID field.

Step 8 Clear the command window by entering:
UPDATE PPS_ACL_PREFERENCES SET TIME_ZONE_ID = < local_machine_timezone_id > 
where <local_machine>timezone_id> is the time zone ID of the local machine.

Step 9 Select Execute Query.

Step 10 Start the Cisco Unified MeetingPlace Web Conferencing service on all Cisco Unified MeetingPlace Web Servers.

Checking Which Conferences Are Currently Running

Complete this procedure as a debugging tool to check which conferences are currently running on the Web Server.

Procedure

Step 1 Sign in to the end-user web interface.

Step 2 Select Admin.

Step 3 Select Web Conferences.

A list of currently running web conferences displays with the following properties:

•Name—A text identifier made up of the meeting subject and the dialable meeting ID.

•Current User Count—Lists the total number of web participants who are currently attending the conference. (Users dialed in to the meeting without an associated web session are not counted here.)

•Peak User Count—Lists the highest number of web participants who are concurrently attending the conference at any point since it began. (Users dialed in to the meeting without an associated web session are not counted here.)

•Active Server—The origin server that is hosting the meeting.

•Duration—Lists the elapsed time since the conference began.

Step 4 (Optional) Select Back to return to the main Administration screen.

Checking the Versions of Local Cisco Unified MeetingPlace Web Conferencing Services

Complete this procedure to check the release number of most local Cisco Unified MeetingPlace Web Conferencing modules. Releases of all listed modules, with the exception of Gateway SIM, must match, that is, 7.1.x.x, where x.x is the same across all modules.

Procedure

Step 1 Sign in to the end-user web interface.

Step 2 Select Admin.

Step 3 Select Versions.

Step 4 Review your module versions.

Step 5 Select Back to return to the main Administration screen.

How to Schedule a Maintenance Window

•Reserve All Ports Meetings

•Scheduling a Maintenance Window

Reserve All Ports Meetings

When you need to schedule time to perform upgrades or other maintenance activities to the Cisco Unified MeetingPlace system, schedule a Reserve All Ports meeting. When you schedule a Reserve All Ports meeting, the Cisco Unified MeetingPlace system performs the following actions:

•Reserves all available ports, or the maximum number of user licenses available in the system

•Blocks out all new callers for the duration of the scheduled meeting

•Prohibits the extension of in-session meetings that began before the Reserve All Ports meeting begins

Reserve All Ports meetings are scheduled, private meetings. The meeting attributes are the same as for scheduled meetings, with the exceptions described in the following table.

Attribute

Value

Frequency

Once

# of calling sites

SysMaintenance

Record meeting?

No

Meeting name

SysMaintenance

Meeting type

All Speaker

Scheduling a Maintenance Window

Caution As a system administrator, it is your responsibility to ensure that no regular meetings are scheduled before scheduling a Reserve All Ports meeting.

Caution Reserve All Ports meetings prevent the system from scheduling any meetings. Also, during a Reserve All Ports meeting, no prompts are played to alert users to the situation. For these reasons, we strongly recommend that you schedule Reserve All Ports meetings during the lowest usage times. In addition, be sure to cancel any Reserve All Ports meetings that you later determine you do not need.

Before You Begin

Remember the following information:

•You cannot extend a scheduled Reserve All Ports meeting, but you can reschedule the meeting.

•Only one Reserve All Ports meeting can be scheduled at a time (one Reserve All Ports meeting must be finished or deleted before another can be scheduled).

•If a Reserve All Ports meeting overlaps another scheduled meeting that is then canceled, the Reserve All Ports meeting reserves the ports released by the other meeting.

•Scheduled Reserve All Ports meetings appear in the server exception log, and any changes to a meeting (such as deleting or rescheduling) are shown in the log.

•If callers dial in to the server while a Reserve All Ports meeting is in session (and all ports are reserved), they hear nothing (silence).

•The meeting ID for a Reserve All Ports meeting cannot be changed.

Procedure

Step 1 Sign in to the end-user web interface with an Administrator profile.

Step 2 Select Schedule Meeting.

Step 3 Enter your date, time, and duration of your maintenance window.

Step 4 Select More Options.

Step 5 Check Reserve all ports meeting.

Step 6 Select Submit.

Step 7 Select Schedule.

Optimizing the Performance of a Web Server

Procedure

Step 1 Sign in to the end-user web interface.

Step 2 Select Admin.

Step 3 Select Web Server.

Scroll down to the "View" section of the page.

Step 4 Select the name of the Web Server that you want to configure.

Information about this Web Server populates the "Edit" section of the page.

Step 5 Select the setting that best describes your conferencing environment for Performance Tuning.

Note Setting this parameter to the highest level on a computer with inadequate hardware results in poor user performance.

Step 6 Select Submit.

Related Topics

•Field Reference: Web Server Specific Fields

Rebooting the Server

Complete the following procedure to shut down and restart the Web Server computer from the web interface.

Procedure

Step 1 Sign in to the end-user web interface.

Step 2 Select Admin.

Step 3 Select Reboot Server.

Step 4 Select OK to confirm the reboot.

The system shuts down and restarts.

Note When you restart the Web Server, all manual changes made to the registry are lost.

How to Monitor Cisco Unified MeetingPlace Web Conferencing Activities

The Windows Event Viewer application and the Cisco Unified MeetingPlace Eventlog application both log all Web Server activities. You can use these logs to monitor or troubleshoot Cisco Unified MeetingPlace Web Conferencing.

•Using the Cisco Unified MeetingPlace Eventlog

•Running the Windows Performance Monitoring Tool

•Viewing an Event with the Windows Event Viewer

Related Topics

•Using Alarms and Logs on Cisco Unified MeetingPlace module

•How to Configure the Lumberjack Logging Utility

Using the Cisco Unified MeetingPlace Eventlog

The Eventlog application logs all activities specific to Cisco Unified MeetingPlace Web Conferencing services.

Procedure

Step 1 Right-click the Cisco Unified MeetingPlace icon in the system tray.

Step 2 Select Eventlog.

Step 3 Pull the eventlog from the Gateway SIM through the Cisco Unified MeetingPlace Application Server.

Running the Windows Performance Monitoring Tool

Complete this procedure to monitor the Cisco Unified MeetingPlace Web Conferencing performance object in the Windows performance monitoring tool.

Procedure

Step 1 Select Start > Run.

The Run window displays.

Step 2 Enter Perfmon.

Step 3 Select OK.

The Performance window displays.

Step 4 Select the Add (+) button.

The Add Counters window displays.

Step 5 Locate the Performance object field.

Step 6 Select Cisco MeetingPlace Web Conferencing.

A list of counters appear.

Step 7 Select to add or explain specific counters.

•Select a counter from the list and select Explain to get more information about it.

•Select a counter from the list and select Add to enable it.

Related Topics

•Counters Available in the Cisco Unified MeetingPlace Performance Object

Viewing an Event with the Windows Event Viewer

The application log provides detailed information about Cisco Unified MeetingPlace Web Conferencing services. For more information about the Windows Event Viewer, see your Windows documentation.

Procedure

Step 1 Select Start > Control Panel > Administrative Tools > Event Viewer.

Step 2 Select Application from the left pane.

A list of events appear in the right pane.

Step 3 Double-click the event to view it.

How to Configure the Lumberjack Logging Utility

Lumberjack is a logging utility that runs as a background thread. Lumberjack periodically dumps several logs at 24-hour intervals and stores those logs, as well as a specified number of older logs, in a configurable location. All the configuration settings are stored in the registry and worked in to the current registry setting structure of Cisco Unified MeetingPlace. Performance monitor logging configuration settings are stored in definition INI file, so counter list and logging interval can be easily changed.

•Lumberjack Logging Utility

•Configuring Lumberjack on a Cisco MCS Server

•Manually Generating a Lumberjack Snapshot

Lumberjack Logging Utility

Upon startup of the master service, a new thread for Lumberjack begins. Lumberjack reads the configuration values from the registry and INI file to determine behavior. If a performance monitor definition INI file does not exist, Lumberjack automatically creates a file with a predefined counter list and logging interval by using the Lumberjack default values.

Every 24 hours, Lumberjack creates a new Gateway SIM event log for a 24-hour window. If the eventlog terminates before midnight, Lumberjack restarts it. If the event log runs past midnight of the day that the first call was made, Lumberjack terminates that process. During routing log gathering, Lumberjack also acquires the following information:

•Performance monitor (24-hour window)

•NT Application and System eventlog

•Registry snapshots

•IIS Log

When the master service is running and Lumberjack is enabled, it detects stopped (crashed) services. and collects the following information in a temp folder in the windows temp directory:

•GWSIM eventlog (24 hour window)

•NT Application and System eventlog

•Registry snapshots

•IIS log

•DrWtsn.log and User.dmp

•.exe, .map, and .pdb of downed services

•binaries for authfilt.dll (if downed IIS)

After the information is collected, Lumberjack bundles the files by using pkzipc.exe. This executable file is distributed with MPWEB and located in the DataSvc folder.

The naming convention for the file is lumberjack_timestamp.zip for routine logs and lumberjackCrash_timestamp.zip for crash logs, where timestamp is the time the log gathering started for routine logs and the time of the detected crash for crash logs.

If the master service is simply stopped, the temp directory that is created for routine logs is not deleted so that the logs for one day are bundled together if there is a restart of the master service. This functionality enables the logs that are captured to be reviewed without having to open a zip file and allows for a quicker shutdown and restart of master service because the service does not have to wait to zip files and remove the directory.

Configuring Lumberjack on a Cisco MCS Server

Before You Begin

Read the "Lumberjack Logging Utility" section.

Procedure

Step 1 Select Start > Run.

The Run window displays.

Step 2 Enter regedit.

Step 3 Change your registry settings for key HKLM\Software\Latitude\MeetingPlace WebPublisher\General\ and for key HKLM\Software\Latitude\MeetingPlace Gateway SIM\General\ as shown in the following table:

Name (Type)

Description

Data and Default

Key: HKLM\Software\Latitude\MeetingPlace WebPublisher\General\

Server Logging (DWORD)

Enables and disables Lumberjack.

0 - Disabled

1 - Enabled

Default is 1.

Log Crash History (DWORD)

Specifies the number of old crash logs to store.

Default is 10.

Log History (DWORD)

Specifies the number of old routine logs to store.

Default is 15.

Log Location (String)

Specifies where to store the .zip files containing logs.

Default is install-location\Cisco Systems\LogFiles.

InstallLocation (String)

Used for gathering .dll, .exe, .map, and .pdb files.

Default is set by Cisco MeetingPlace Web Conferencing.

Key: HKLM\Software\Latitude\MeetingPlace Gateway SIM\General\

InstallLocation (String)

Used for running Gateway SIM eventlog.

Default is set by Gateway SIM.

Manually Generating a Lumberjack Snapshot

Logs gathered because of a manual snapshot request have the format lumberjackSnapshot__timestamp.zip.

You can locate these logs either in the default LogFiles folder or in the folder that you specified when you completed the "Configuring Lumberjack on a Cisco MCS Server" section.

Before You Begin

This procedure is completed on the Web Server.

Procedure

Step 1 Right-click the Cisco Unified MeetingPlace red door icon.

Step 2 Select Capture Logs.

The snapshot log gathering process begins.

How to Switch the Order of IP Addresses on the Web Server

Based on the NIC binding order, the system assigns the first IP address to the Hostname [Web Conferencing] and the second IP address to the Hostname [Home Page].

Note If you ever change an IP address to a hostname or FQDN, be sure that you replace it with the hostname or FQDN corresponding to that IP address. Do not switch the order of the IP addresses or hostnames as this will cause problems.

If you want to switch the order of the IP addresses, complete the following in the order presented. Select the first or second topic based on your system configuration:

•Changing the Binding Order for a System with One IP Address on Each NIC

•Changing the Binding Order for a System with Two IP Addresses on One NIC

•Making the Change in the Application

Changing the Binding Order for a System with One IP Address on Each NIC

Complete this procedure if you have one IP address on each NIC. If you do not, complete the "Changing the Binding Order for a System with Two IP Addresses on One NIC" section instead.

Procedure

Step 1 On the Start menu, select Settings > Control Panel > Network Connections.

Step 2 Select Advanced > Advanced Settings.

Step 3 Change the order of the IP addresses/NICs by using the up and down arrows.

What to Do Next

Proceed to the "Making the Change in the Application" section.

Changing the Binding Order for a System with Two IP Addresses on One NIC

Complete this procedure if you have two IP addresses on a single NIC. If you do not, complete the "Changing the Binding Order for a System with One IP Address on Each NIC" section instead.

Procedure

Step 1 Change the primary IP address to the virtual IP address.

Step 2 Change the virtual IP address to the primary IP address.

What to Do Next

Proceed to the "Making the Change in the Application" section.

Making the Change in the Application

Before You Begin

Depending on your system, complete one of the following:

•Changing the Binding Order for a System with One IP Address on Each NIC

•Changing the Binding Order for a System with Two IP Addresses on One NIC

Procedure

Step 1 Sign in to the end-user web interface.

Step 2 Select Admin > Web Server.

Step 3 From the "View" section of the page, select the name of the web server that you want to configure.

This populates the "Edit" section of the page with predefined settings.

Step 4 Change the order of the IP addresses for the Hostname [Web Conferencing] and the Hostname [Home Page].

Step 5 Restart all Cisco Unified MeetingPlace Web Conferencing services.

Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

Note This table includes links to sections within this chapter. Each of these sections provides detailed information on the specific task. After you complete each task, return to this table to complete the next task.

Task

Description

For details, see

Step 1

Remove all connections from the Web Server to the Application Server.

Removing the Connection to the Application Server

Step 2

On the Application Server you can change the hostname and IP address using the net command.

Changing the IP Address or Hostname of the Application Server

Step 3

You can change the domain name of the Application Server using the net command.

Changing the Domain Name of the Application Server

Step 4

On the Cisco Unified MeetingPlace Web Server, you can change the IP address for the Domain Name Server or a Network Time Protocol Server.

Changing the IP Address for a Domain Name Server or a Network Time Protocol Server

Step 5

You can update your Domain Name Server and Cisco Unified Call Manager with the new hostname and IP address of Application Server and Cisco Unified MeetingPlace Web Server.

Updating DNS Entries

Step 6

Reconnect the Cisco Unified MeetingPlace Web Server to the Application Server.

Re-establishing a Connection to an Application Server

Related Topics

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Removing the Connection to the Application Server

This procedure is completed on the Cisco Unified MeetingPlace Web Server.

Procedure

Step 1 Sign in to the Web Server.

Step 2 Stop the web services and the Gateway SIM service, including the Replication Service and Agent Service.

Step 3 Choose Start > Programs > Cisco Unified MeetingPlace Configuration > Cisco Unified MeetingPlace Gateway Configuration to open the Cisco Unified MeetingPlace Gateways Configuration utility.

Step 4 Select the Gateway SIM tab.

Step 5 Delete this unit from the active Application Server.

a. Go to the lower-left pane of the Gateway SIM tab.

b. Select the name of the Application Server that you want to disconnect from.

c. Select Delete.

Step 6 Close the Cisco Unified MeetingPlace Gateways Configuration utility.

Step 7 Change the IP address or host name of the Cisco Unified MeetingPlace Web Server.

Step 8 Disable the usage of unused Web Server hostnames.

a. Sign in to the Administration Center.

b. Select System Configuration > Web Servers.

c. Select the Edit link of the hostname that is no longer used.

d. On the Edit Web Server dialog, set the Enabled field to no.

e. Select Save.

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Changing the IP Address or Hostname of the Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

Changing the IP Address or Hostname of the Application Server

This procedure is completed on the Cisco Unified MeetingPlace Application Server.

Procedure

Step 1 Sign in to the CLI of the Application Server as the mpxadmin user.

Step 2 Enter su - to switch to the root user.

Step 3 Enter net at the prompt to start the Network Configuration Utility.

Step 4 Enter y at the prompt to continue.

Step 5 Select 2 to `Configure Ethernet'.

Step 6 Select 4 to `Set basic IP parameters'.

Step 7 Enter new values for the IP address or skip to Step 9 to change the hostname.

a. (Optional) Enter a new value for the network mask.

b. (Optional) Enter a new value for the default gateway, or enter None if there is no default gateway.

Step 8 Select 8 to return to the main menu.

Step 9 Select 3 to `Set host name'.

Step 10 Enter a new host name at the prompt.

Note Make sure you have a DNS table entry for the new host name.

Step 11 Select 7 `Done'.

Note Contact the Cisco Technical Assistance Center to implement database changes. Otherwise, you may experience operational issues with Adobe Breeze.

Step 12 Enter y at the prompt to save your changes.

Step 13 Enter reboot to reboot the Application Server.

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Changing the Domain Name of the Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Changing the Domain Name of the Application Server

This procedure is completed on the Cisco Unified MeetingPlace Application Server.

Procedure

Step 1 Sign in to the CLI of the Application Server as the mpxadmin user.

Step 2 Enter su - to switch to the root user.

Step 3 Enter net at the prompt to start the Network Configuration Utility.

Step 4 Enter y at the prompt to continue.

Step 5 Select 4 to `Set domain name'.

Step 6 Enter a new domain name at the prompt.

Step 7 Select 7 `Done'.

Step 8 Enter y at the prompt to save your changes.

Step 9 Enter reboot to reboot the Application Server.

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Changing the IP Address for a Domain Name Server or a Network Time Protocol Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Changing the IP Address for a Domain Name Server or a Network Time Protocol Server

Complete this procedure on the Cisco Unified MeetingPlace Web Server.

Procedure

Step 1 Sign in to the CLI of the Application Server as the mpxadmin user.

Step 2 Enter su - to switch to the root user.

Step 3 Enter net at the prompt to start the Network Configuration Utility.

Step 4 Enter y at the prompt to continue.

Step 5 Select 5 to `Configure DNS service'.

Note You can change the IP address for up to three domain name servers.

Step 6 Enter a new domain name server IP address at the prompt.

Step 7 Select 6 to `Configure NTP service'.

Note You can change the IP address for up to three network time protocol servers.

Step 8 Enter a new network time protocol server IP address at the prompt.

Step 9 Select 7 `Done'.

Step 10 Enter y at the prompt to save your changes.

Step 11 Enter reboot to reboot the Application Server.

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Updating DNS Entries

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Updating DNS Entries

When you change an IP address or host name for an Application Server or a Web Server, you should update the appropriate DNS entries on your Domain Name Server and Cisco Unified CallManager Express.

Procedure

Step 1 Access your Domain Name Server.

Step 2 Change the DNS entry for the Application Server to match the address you entered in "Changing the IP Address or Hostname of the Application Server" section.

Step 3 Change the DNS entry for the Web Server to match the address you entered in "Changing the Domain Name of the Application Server" section.

Step 4 Access your Cisco Unified Communications Manager and change the SIP trunk configuration for the Application Server. See Setting Up a Cisco Unified Communications Manager 8.x and 9.x SIP Trunk Integration with Cisco Unity Connection for more details.

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Re-establishing a Connection to an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Re-establishing a Connection to an Application Server

After changing IP parameters, you should re-establish the connection between the Web Server and the Application Server.

Procedure

Step 1 Sign in to the Web Server.

Step 2 Choose Start > Programs > Cisco Unified MeetingPlace Configuration > Cisco Unified MeetingPlace Gateway Configuration to open the Cisco Unified MeetingPlace Gateways Configuration utility.

Step 3 Select the Gateway SIM tab.

Step 4 Select Add.

The MeetingPlace Server Entry window displays.

Step 5 Enter the new configuration information as follows:

Parameter

Action

Server Name

Enter the hostname of the Cisco Unified MeetingPlace Application Server.

Note If you use an IP address instead of a hostname for the Application Server, you will have to update the IP address on the Web Server whenever you change the IP address on the Application Server.

Shadow Server

Leave this field as is.

Client IP Address

Enter the IP address of the computer on which the Gateway SIM is installed.

Transfer Destination

Leave this field as is.

Link Encryption Disabled

Leave this box unchecked to maintain encrypted communications between the Gateway SIM and the Application Server.

Encryption uses a 56-bit DES algorithm with a secret key.

Step 6 Select OK.

Step 7 Select OK again.

Step 8 Restart the Gateway SIM service and the Cisco Unified MeetingPlace Web Master Service.

If other Web Servers share the database with the server, restart the services on those servers as well.

Step 9 Update the Web Server's hostnames and IP addresses.

a. Sign in to the end-user web interface.

b. Select Admin > Web Server.

c. From the View section, select the name of the Web Server you want to update.

This populates the Edit section of the page with the pre-defined settings.

d. Update the IP address or hostname for the Hostname [Home Page] and the Hostname [Web Conferencing].

e. Select Submit.

f. Restart the Cisco Unified MeetingPlace Web Master Service.

Step 10 Update the Click-to-Attend link.

a. Sign in to the Administration Center.

b. Select System Configuration > Usage Configuration.

c. In the Click-to-Attend Link Configuration section, update the Web Server hostname entries.

d. Select Save.

What to Do Next

•Sign in a root user and restart the Application Server by entering the mpx_sys restart command.

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

Note This table includes links to sections within this chapter. Each of these sections provides detailed information on the specific task. After you complete each task, return to this table to complete the next task.

Task

Description

For details, see

Step 1

Remove all connections from the Web Server to the Application Server.

Removing the Connection to the Application Server

Step 2

Tear down replication between the primary and secondary Application Server. Then you can change the hostname and IP address using the net command.

Changing IP Addresses and Hostnames for the Replicated Application Servers

Step 3

You can update your Domain Name Server and Cisco Unified Call Manager with the new hostname and IP address of Application Server and Cisco Unified MeetingPlace Web Server.

Updating DNS Entries

Step 4

Turn on replication between the primary and secondary Application Servers. Then return the Application Servers to active mode.

Turning on Replication

Step 5

Reconnect the Cisco Unified MeetingPlace Web Server to the Application Server.

Re-establishing a Connection to an Application Server

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Re-establishing a Connection to an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Changing IP Addresses and Hostnames for the Replicated Application Servers

Before you can change the IP address or hostname of the primary (active) and secondary (standby) Application Servers, complete the following tasks:

Procedure

Step 1 Switch both the primary and secondary Application Servers from active to failover standby mode. See Performing Application Server Failover for information.

Step 2 Change the IP address or hostname of eth0 (referred to as Ethernet Port 1(device eth0)) of the primary Application Server using the net command. See "Changing the IP Address or Hostname of the Application Server" section.

Step 3 For the primary Application Server, complete "Changing the Domain Name of the Application Server" section and "Changing the IP Address for a Domain Name Server or a Network Time Protocol Server" section.

Step 4 Switch the secondary Application Server to single server mode.

Step 5 Repeat steps 2 and 3 for the secondary Application Server.

Step 6 Switch the secondary Application Server to failover standby mode. See Performing Application Server Failover for instructions.

Related Topics

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Updating DNS Entries

Turning on Replication

After you change IP addresses and hostnames for the primary and secondary Application Servers, and return the secondary server to the failover standby mode, complete the following tasks:

Procedure

Step 1 Initialize replication between the primary and standby Application Servers

Step 2 Turn on replication between the primary and standby Application Servers

Step 3 Return the primary Application Server to active mode

See Performing Application Server Failover for instructions.

Related Topics

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Re-establishing a Connection to an Application Server

Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

Note This table includes links to sections within this chapter. Each of these sections provides detailed information on the specific task. After you complete each task, return to this table to complete the next task.

Task

Description

For details, see

Step 1

Before you change the hostname or an IP address of a Application Server in a multinode deployment, you must remove the server from the multinode deployment and place it in standby mode.

Step 2

On the Application Server you can change the hostname and IP address using the net command.

Changing the IP Address or Hostname of the Application Server

Step 3

You can change the domain name of the Application Server using the net command.

Changing the Domain Name of the Application Server

Step 4

On the Cisco Unified MeetingPlace Web Server, you can change the IP address for the Domain Name Server or a Network Time Protocol Server.

Changing the IP Address for a Domain Name Server or a Network Time Protocol Server

Step 5

You can update your Domain Name Server and Cisco Unified Call Manager with the new hostname and IP address of Application Server and Cisco Unified MeetingPlace Web Server.

Updating DNS Entries

Step 6

After your system is up and running, add the Application Server back as part of the multinode deployment.

Step 7

If you have multiple Cisco WebEx Node for MCS in your deployment, and you have changed the Hostname or the IP address of your Primary or Secondary MBD, you'll need to reflect these changes at your Cisco WebEx Nodes.

Entering Updated Hostnames and IP Addresses on Cisco WebEx Node for MCS

Step 8

If you do not have a Cisco WebEx Node for MCS as part of your deployment, you need to update the Cisco WebEx site with the changed hostname or IP address.

Updating the Cisco WebEx Site

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Entering Updated Hostnames and IP Addresses on Cisco WebEx Node for MCS

Complete this procedure on each Cisco WebEx Node for MCS in your deployment.

Note Contact the administrator of the Cisco WebEx Node Management System if you want to change the hostname or IP address of a Cisco WebEx Node for MCS. This type of change must be updated on the Cisco WebEx Node Management System, and the Cisco WebEx Node must be reconfigured with new parameters.

Procedure

Step 1 Sign in to the CLI of each Cisco WebEx Node for MCS as the mpxadmin user.

Step 2 Enter service webex stop and wait until all services have stopped.

Step 3 Enter set webex mbd Primary Meeting Director hostname,Secondary Meeting Director hostname.

Note When you enter the Primary and Secondary Meeting Director node hostnames or IP addresses, make sure you enter a comma with no space between the two node names.

Step 4 Enter service webex start and to start the services.

Related Topics

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

Updating the Cisco WebEx Site

Complete this procedure on the active Meeting Director Broker (MBD) node.

Note Cisco Unified MeetingPlace does not automatically update hostname and IP address information on the Cisco WebEx site.

Procedure

Step 1 To update hostnames and IP addresses on the Cisco WebEx site, go to Cisco WebEx Configuration > Cisco WebEx Site Configuration page.

Step 2 Select Configure WebEx.

Related Topics

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Note This table includes links to sections within this chapter. Each of these sections provides detailed information on the specific task. After you complete each task, return to this table to complete the next task.

Task

Description

For details, see

Step 1

If SSL is installed and turned on, disable SSL on the internal and external Web Servers.

Turning Off SSL on Internal and External Cisco Unified MeetingPlace Web Servers

Step 2

Disable SMA on the Web Server before you change an IP address or hostname for an Application Server.

Turning Off SMA for Cisco Unified MeetingPlace Web Server

Step 3

On the Application Server you can change the hostname and IP address using the net command.

Changing the IP Address or Hostname of the Application Server

Step 4

You can change the domain name of the Application Server using the net command.

Changing the Domain Name of the Application Server

Step 5

On the Cisco Unified MeetingPlace Web Server, you can change the IP address for the Domain Name Server or a Network Time Protocol Server.

Changing the IP Address for a Domain Name Server or a Network Time Protocol Server

Step 6

You can update your Domain Name Server and Cisco Unified Call Manager with the new hostname and IP address of Application Server and Cisco Unified MeetingPlace Web Server.

Updating DNS Entries

Step 7

Enable SMA for the Cisco Unified MeetingPlace Web Servers to the Application Server.

Turning On SMA for Cisco Unified MeetingPlace Web Server

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Turning Off SSL on Internal and External Cisco Unified MeetingPlace Web Servers

If the internal and external (DMZ) Cisco Unified MeetingPlace Web Servers have SSL configured, you must turn off SSL before you turn off SMA or change an IP address or hostname for an Application Server.

Note A certificate authority issues a certificate for a particular hostname. Therefore, when you change the hostname, the SSL certificate becomes invalid.

Procedure

Step 1 Toggle SSL to OFF on all internal Cisco Unified MeetingPlace Web Servers.

Step 2 Reboot all internal Web Servers.

Step 3 Toggle SSL to OFF on all external Web Servers.

Step 4 Reboot all external Web Servers.

Related Topics

•Turning Off SMA for Cisco Unified MeetingPlace Web Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Turning Off SMA for Cisco Unified MeetingPlace Web Server

You need to disable SMA on the Cisco Unified MeetingPlace Web Server before you change the IP address or hostname for the Application Server.

Prerequisite

If the internal or external (DMZ) Web Servers have SSL configured, you must turn off SSL before you turn off SMA on the Web Servers.

Procedure

Step 1 Sign in to the end-user web interface.

Step 2 Select Admin.

Step 3 Select Site.

Step 4 Select the underlined site name.

Step 5 For the field named "DMZ Web Server," make sure the value is set to -none-.

Step 6 Select Submit.

Related Topics

•Changing the IP Address or Hostname of the Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname

Turning On SMA for Cisco Unified MeetingPlace Web Server

You need to enable SMA on the Cisco Unified MeetingPlace Web Server after you change the IP address or hostname for the Application Server.

Procedure

Step 1 Sign in to the end-user web interface on the internal Web Server.

Step 2 Select Admin.

Step 3 Select Web Server.

Step 4 From a blank "Web Server Name" field, enter the name of a new Web Server to represent your designated external Web Server.

Step 5 Enter the fully qualified domain name (FQDN) of your external Web Server in the Hostname field as hostname.domain. If your Web Server is not in a Domain Name Server (DNS), enter the IP address instead.

Note You must be able to resolve this hostname from the internal Web Server.

Note If you are using SSL, make sure the hostname of the SSL certificate resolves to the external Web Server IP address.

Note If you are using SSL and a segmented DNS, make sure the DNS name and the SSL certificate name are different.

Step 6 Select Submit to add this Web Server to the database.

Related Topics

•Audio-only Deployment - Changing the IP Address or Hostname for a Web Server and an Application Server

•Failover Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Multinode Deployment - Changing the IP Address or Host Name for a Web Server and an Application Server

•Web Server with Segmented Meeting Access - Changing the IP Address or Hostname