Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Failover Deployment – Changing the IP Address or Hostname for a Web Server and an Application Server)
Line 19: Line 19:
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Configure the Lumberjack Logging Utility|How to Configure the Lumberjack Logging Utility]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Configure the Lumberjack Logging Utility|How to Configure the Lumberjack Logging Utility]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Switch the Order of IP Addresses on the Web Server|How to Switch the Order of IP Addresses on the Web Server]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#How to Switch the Order of IP Addresses on the Web Server|How to Switch the Order of IP Addresses on the Web Server]]
 +
* [[Cisco Unified MeetingPlace Release 8.0 -- Monitoring and Maintaining the Cisco Unified MeetingPlace Web Server#Changing Server IP Addresses and Hostnames|Changing Server IP Addresses and Hostnames]]
 +
 +

Revision as of 04:29, 25 May 2013

Main page: Cisco Unified MeetingPlace, Release 8.0

Back to: Configuration

Back to: Maintenance


Note: This topic does not apply to deployments in which users schedule meetings from the Cisco WebEx site. For information about Cisco WebEx integration deployments, see the Planning Guide for Cisco Unified MeetingPlace at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.


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.



Contents

IIS File Deletion

IIS file deletion is optional. If you want to clean up the IIS web server, then understand the following:

  • Deleting the default SMTP virtual server or the Administration website in IIS does not have any effect on the Cisco Unified MeetingPlace web user portal.
  • 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.


Checking the Versions of Local Cisco Unified MeetingPlace Web Server Modules

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


Procedure
  1. Sign in to the Cisco Unified MeetingPlace web user portal.
  2. Click Admin.
  3. Click Versions.
  4. Review your module versions.
  5. Click Back to return to the main Administration screen.


How to Schedule 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



Related Topics

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
  1. Sign in to the Cisco Unified MeetingPlace web user portal with an administrator profile.
  2. Click Schedule Meeting.
  3. Enter your date, time, and duration of your maintenance window.
  4. Click More Options.
  5. Check Reserve all ports meeting.
  6. Click Submit.
  7. Click Schedule.


Optimizing the Performance of a Web Server

Procedure
  1. Sign in to the Cisco Unified MeetingPlace web user portal.
  2. Click Admin.
  3. Click Web Server.
    Scroll down to the "View" section of the page.
  4. Click the name of the Web Server that you want to configure.
    Information about this Web Server populates the "Edit" section of the page.
  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.
  6. Click Submit.


Related Topics


Rebooting the Server

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


Procedure
  1. Sign in to the Cisco Unified MeetingPlace web user portal.
  2. Click Admin.
  3. Click Reboot Server.
  4. Click OK to confirm the reboot.
    The system shuts down and restarts.


How to Monitor Cisco Unified MeetingPlace Web Server 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 the Cisco Unified MeetingPlace Web Server.


Related Topics


Using the Cisco Unified MeetingPlace Eventlog

The Eventlog application logs all activities specific to Cisco Unified MeetingPlace Web Master Service.


Procedure
  1. Right-click the Cisco Unified MeetingPlace icon in the system tray.
  2. Select Eventlog.
    A DOS command window will open that will contain a view of the latest log messages, which will update as new log messages are generated.


Running the Windows Performance Monitoring Tool

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


Procedure
  1. Click Start > Run.
    The Run window displays.
  2. Enter Perfmon.
    The Performance window displays.
  3. Click the Add (+) button.
    The Add Counters window displays.
  4. Locate the Performance object field.
  5. Select MeetingPlace Web Server.
    If your system was upgraded from Release 7.0 to Release 8.0, then select MeetingPlace Web Conferencing instead.
  6. Select to add or explain specific counters.
    • Click a counter from the list and click Explain to get more information about it.
    • Click a counter from the list and click Add to enable it.


Related Topics


Viewing an Event with the Windows Event Viewer

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


Procedure
  1. Click Start > Control Panel > Administrative Tools > Event Viewer.
  2. Select Application from the left pane.
    A list of events appear in the right pane.
  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

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 the Cisco Unified MeetingPlace Web Server

Before You Begin

Read the Lumberjack Logging Utility.


Procedure
  1. Select Start > Run.
    The Run window displays.
  2. Enter regedit.
  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 the Cisco Unified MeetingPlace Web Server software.

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

InstallLocation (String)

Used for running Gateway SIM eventlog.

Default is set by Gateway SIM.



Related Topics

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 the Cisco Unified MeetingPlace Web Server.


Procedure
  1. Right-click the Cisco Unified MeetingPlace red door icon on the Web Server.
  2. Select Capture Logs.
    The snapshot log gathering process begins.


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

This topic applies only if you upgraded from Release 7.0 to Release 8.0.


Based on the NIC binding order, the system assigns the first IP address to the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Hostname [Web Conferencing]|Hostname [Web Conferencing]]] and the second IP address to the [[Cisco Unified MeetingPlace Release 8.0 -- Web Administration References for Cisco Unified MeetingPlace#Hostname [Home Page]|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

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 instead.


Procedure
  1. On the Start menu, click Settings > Control Panel > Network Connections.
  2. Click Advanced > Advanced Settings.
  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.


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 instead.


Procedure
  1. Change the primary IP address to the virtual IP address.
  2. Change the virtual IP address to the primary IP address.


What to Do Next

Proceed to the Making the Change in the Application.


Making the Change in the Application

Before You Begin

Depending on your system, complete one of the following:


Procedure
  1. Sign in to the Cisco Unified MeetingPlace web user portal.
  2. Click Admin > Web Server.
  3. From the "View" section of the page, click the name of the web server that you want to configure.
    This populates the "Edit" section of the page with predefined settings.
  4. Change the order of the IP addresses for the Hostname [Home Page] and the Hostname [Web Conferencing].
    Note: The Hostname [Web Conferencing] field appears only if you upgraded from Release 7.0 to Release 8.0.
  5. Restart the Cisco Unified MeetingPlace Web Master Service.


Related Topics


Changing Server IP Addresses and Hostnames

This section describes how to change the IP address or a hostname for Cisco Unified MeetingPlace Application server, a Cisco Unified MeetingPlace Web Server, or a Hardware Media Server

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

Use this table to go to the procedure you need to perform to change an IP address or hostname for a Web Server and a Cisco Unified MeetingPlace Application server in an audio-only deployment. After you complete each task, return to this table to complete the next task.


Task Description For details, see

1

Remove all connections from the Web Server to the Application Server

Removing the Connection to the Application Server

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

3

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

Changing the Domain Name of the Application Server

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

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

6

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

Re-establishing a Connection to an Application Server


Related Topics


Removing the Connection to the Application Server

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


Procedure
  1. Sign in to the Web Server.
  2. Stop the web services and the Gateway SIM service, including the Replication Service and Agent Service.
  3. Choose Start > Programs > Cisco Unified MeetingPlace Configuration > Cisco Unified MeetingPlace Gateway Configuration to open the Cisco Unified MeetingPlace Gateways Configuration utility.
  4. Select the Gateway SIM tab.
  5. Delete this unit from the active Application Server.
    • Go to the lower-left pane of the Gateway SIM tab.
    • Select the name of the Application Server that you want to disconnect from.
    • Select Delete.
  6. Close the Cisco Unified MeetingPlace Gateways Configuration utility.
  7. Change the IP address or host name of the Cisco Unified MeetingPlace Web Server.
  8. Disable the usage of unused Web Server hostnames.
    • Sign in to the Administration Center.
    • Select System Configuration > Web Servers.
    • Select the Edit link of the hostname that is no longer used.
    • On the Edit Web Server dialog, set the Enabled field to no.
    • Select Save.
Related Topics


Changing the IP Address or Hostname of the Application Server

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

Procedure
  1. Sign in to the CLI of the Application Server as the mpxadmin user.
  2. Enter su - to switch to the root user.
  3. Enter net at the prompt to start the Network Configuration Utility.
  4. Enter y at the prompt to continue.
  5. Select 2 to ‘Configure Ethernet’.
  6. Select 4 to ‘Set basic IP parameters’.
  7. Enter new values for the IP address or skip to Step 9 to change the hostname.
    • (Optional) Enter a new value for the network mask.
    • (Optional) Enter a new value for the default gateway, or enter None if there is no default gateway.
  8. Select 8 to return to the main menu.
  9. Select 3 to ‘Set host name’.
  10. Enter a new host name at the prompt.
    Note: Make sure you have a DNS table entry for the new host name.
  11. Select 7 ‘Done’.
  12. Enter y at the prompt to save your changes.
  13. Enter reboot to reboot the Application Server.


Related Topics


Changing the Domain Name of the Application Server

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

Procedure
  1. Sign in to the CLI of the Application Server as the mpxadmin user.
  2. Enter su - to switch to the root user.
  3. Enter net at the prompt to start the Network Configuration Utility.
  4. Enter y at the prompt to continue.
  5. Select 4 to ‘Set domain name’.
  6. Enter new domain name at the prompt.
  7. Select 7 ‘Done’.
  8. Enter y at the prompt to save your changes.
  9. Enter reboot to reboot the Application Server.


Related Topics


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

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

Procedure
  1. Sign in to the CLI of the Application Server as the mpxadmin user.
  2. Enter su - to switch to the root user.
  3. Enter net at the prompt to start the Network Configuration Utility.
  4. Enter y at the prompt to continue.
  5. Select 5 to ‘Configure DNS service'.
    Note: You can change the IP address for up to three domain name servers.
  6. Enter a new domain name server IP address at the prompt.
  7. Select 6 to ‘Configure NTP service’.
    Note: You can change the IP address for up to three network tome protocol servers.
  8. Enter a new network time protocol server IP address at the prompt.
  9. Select 7 ‘Done’.
  10. Enter y at the prompt to save your changes.
  11. Enter reboot to reboot the Application Server.


Related Topics


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
  1. Access you domain Name Server.
  2. Change the DNS entry for the Application Server to match the address you entered in Changing the IP Address or Hostname for a Web Server and an Application Server.
  3. Change the DNS entry for the Web Server to match the address you entered in Changing the Domain Name of the Application Server.
  4. Access your Cisco Unified Communications Manager and change the SIP trunk configuration for the Application Server. See http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/integration/guide/cucm_sip/cucintcucmsip060.html.


Related Topics


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
  1. Sign in to the Web Server.
  2. Choose Start > Programs > Cisco Unified MeetingPlace Configuration > Cisco Unified MeetingPlace Gateway Configuration to open the Cisco Unified MeetingPlace Gateways Configuration utility.
  3. Select the Gateway SIM tab.
  4. Select Add.
    The MeetingPlace Server Entry window displays.
  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.

  1. Select OK.
  2. Select OK again.
  3. 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.
  4. Update the Web Server's hostname and IP addresses.
    • Sign in to the web user portal.
    • Select Admin > Web Server.
    • 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.
    • Update the IP address or hostname for the Hostname [Home Page] and the Hostname [Web Conferencing].
    • Select Submit.
    • Restart the Cisco Unified MeetingPlace Web Master Service.
  5. Update the Click-to-Attend link.
    • Sign in to the Administration Center.
    • Select System Configuration > Usage Configuration.
    • In the Click-to-Attend Link Configuration section, update the Web Server hostname entries.
    • Select Save.


What to Do Next

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


Failover Deployment – Changing the IP Address or Hostname for a Web Server and an Application Server

Use this table to go to the procedure you need to perform to change an IP address or hostname for a Web Server and a Cisco Unified MeetingPlace Application server in an failover deployment. After you complete each task, return to this table to complete the next task.


Task Description For details, see

1

Remove all connections from the Web Server to the Application Server

Removing the Connection to the Application Server

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

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

4

Turn on replication between the primary and secondary Application Servers. Then return the Application Server to activemode.

Turning on Replication

5

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

Re-establishing a Connection to an Application Server


Changing IP Addresses and Hostnames for the Replicated Application Servers

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
  1. Switch both the primary and secondary Application Servers from active to failover standby mode. See http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace/8_5/english/administration/failover_application_server_config.html#wp1155470 for more information.
  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.
  3. For the primary Application Server, complate Changing the Domain Name of the Application Server and Changing the IP Address for a Domain Name Server or a Network Time Protocol Server.
  4. Switch the secondary Application Server to single server mode.
  5. Repeat steps 2 and three for the secondary Application Server.
  6. Switch the secondary Application Server to failover standby mode. See http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace/8_5/english/administration/failover_application_server_config.html#wp1155470 for more information.


Related Topics

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, turn on replication.

Procedure
  1. Initialize replication between the primary and standby Application Servers
  2. Turn on replication between the primary and standby Application Servers
  3. Return the primary Application Server to active mode
    See http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace/8_5/english/administration/failover_application_server_config.html#wp1155470 for more information.
Related Topics

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

Rating: 0.0/5 (0 votes cast)

Personal tools