Configuration Guide for Cisco Unified MeetingPlace Release 8.6
Configuring Time and Time Zones
Downloads: This chapterpdf (PDF - 162.0KB) The complete bookPDF (PDF - 7.28MB) | Feedback

Configuring Time and Time Zones

Table Of Contents

Configuring Time and Time Zones

About the System Clock

Recommendations for Time and Time Zone Configurations

Configuring the Time and Time Zone for the Application Server

Changing the Time Zone of the Application Server

Configuring NTP on the Application Server

Restrictions for Configuring NTP on the Application Server

Configuring NTP from the Application Server CLI

Synchronizing the Application Server System Clock with the NTP Server

Manually Changing the Time of the Application Server System Clock

Viewing the Application Server System Clock

Configuring the Time for the Web Server

Configuring NTP on the Web Server

Configuring NTP on a Web Server in a Domain

Pointing the Domain Controller to the External NTP Source

Changing the Registry Setting Manually on the Web Server

Synchronizing the Time Between the Web Server and the NTP Server Via the Web Master Service and Windows Time Service

Verifying That the Windows Time Service is Running

Viewing the Web Server Clock

Configuring the Time for the Hardware Media Server

Configuring NTP on the Audio Blade

Viewing the Audio Blade Clock

Configuring the Time for the Cisco WebEx Node

Viewing the Cisco WebEx Node Clock

Changing the Time of the Cisco WebEx Node Clock

Changing the Time Zone of the Cisco WebEx Node


Configuring Time and Time Zones


About the System Clock

Recommendations for Time and Time Zone Configurations

Configuring the Time and Time Zone for the Application Server

Configuring the Time for the Web Server

Configuring the Time for the Hardware Media Server

Configuring the Time for the Cisco WebEx Node

About the System Clock

Each Cisco Unified MeetingPlace Application Server has a system clock that is independent of the time zone. In a failover deployment, the system clocks on the active and standby Application Servers must be synchronized with each other.

The system clock should always be set to match UTC (also called GMT). If the system clock is not consistent with UTC, then the system will not behave as expected. To display the time and date of the system clock in UTC, enter date --utc in the Application Server CLI.


Caution Do not change the system clock to correct for time zone issues. Doing so can result in long-term system problems. If the available time zone options do not work for you, then contact Cisco TAC.

Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Changing the Time Zone of the Application Server

System Clock Does Not Match UTC

Recommendations for Time and Time Zone Configurations

Keep the following default configurations:

Web Servers and Hardware Media Servers use the Application Server as the NTP server.

(For Cisco WebEx integration) If you install a Cisco WebEx Node for MCS, then the Application Server is automatically configured to use the Cisco WebEx Node as the NTP server. This synchronizes the time between the Cisco Unified MeetingPlace system and the Cisco WebEx site.

If your deployment does not include the Cisco WebEx Node for MCS, then configure NTP for the Application Server using an accurate external time reference. The NTP server should reference an atomic clock or satellite receiver.

Configure the clocks, time zones, and NTP correctly during installation.

Post-installation changes, especially to the system clock on the Application Server, may corrupt existing meeting data on your system, such as meeting start and end times, overbook port availability, and log messages.

Related Topics

Configuring Time and Time Zones

Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html

Configuring the Time and Time Zone for the Application Server

Changing the Time Zone of the Application Server

Configuring NTP on the Application Server

Synchronizing the Application Server System Clock with the NTP Server

Manually Changing the Time of the Application Server System Clock

Viewing the Application Server System Clock

Changing the Time Zone of the Application Server

Complete this task if you physically moved your Application Server to a location in a different time zone.

Procedure


Step 1 Log in to the Application Server CLI as the root user.

Step 2 Enter date to display the current time and time zone settings. The following is an example of the output:

Thu May 24 15:37:49 UTC 2012
 
   

Step 3 Enter cd /usr/share/zoneinfo to view the list of time zone regions. Select your region.

Step 4 (Optional) Back up the previous time zone configuration by copying it to a different location. For example, enter mv /etc/localtime /etc/localtime-old.

Step 5 Create a symbolic link to the appropriate time zone from /etc/localtime. For example, enter ln -sf /usr/share/zoneinfo/Europe/Amsterdam /etc/localtime.

Step 6 Set the ZONE entry in the file /etc/sysconfig/clock file. For example, enter ZONE=Europe/Amsterdam.

Step 7 Enter /sbin/hwclock --systohc to set the hardware clock.

Step 8 Enter date to verify that the time zone has been changed.

Step 9 Log out from system.


Related Topics

Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace

Configuring NTP on the Application Server

Choose from one of the following methods:

Restrictions for Configuring NTP on the Application Server

Configuring NTP from the Application Server CLI

Restrictions for Configuring NTP on the Application Server

Do not modify the NTP configuration if your deployment includes the Cisco WebEx Node for MCS. If you install the Cisco WebEx Node for MCS, then the Application Server is automatically configured to use the Cisco WebEx Node as the NTP server.

If setting NTP shifts the time of the system clock, then any existing meeting data may be affected by the time shifts.

Related Topics

Configuring NTP on the Application Server

Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace

Configuring NTP from the Application Server CLI

Before You Begin

Read the "Restrictions for Configuring NTP on the Application Server" section.

Procedure


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

Step 2 Enter mpx_sys stop to stop the Application Server software.

Step 3 Enter net to access the network configuration utility.

The system displays the following:

1) List current configuration
2) Configure Ethernet
3) Set host name
4) Set domain name
5) Configure DNS service
6) Configure NTP service
7) Done
 
   
Select: 
 
   

Step 4 Enter 6 to configure the NTP service.

Step 5 Enter the IP address or Fully Qualified Domain Name (FQDN) of the new NTP server.

Step 6 Press Enter at the prompt to enter additional servers.

Step 7 When finished, enter 1 to verify the NTP configuration.

Step 8 Enter 7 to indicate that you are done.

Step 9 Enter y when asked if you want to save your changes.

Step 10 Enter reboot to restart the system.


Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Synchronizing the Application Server System Clock with the NTP Server

Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace

Synchronizing the Application Server System Clock with the NTP Server

Before You Begin

Read the "Restrictions for Configuring NTP on the Application Server" section.

Procedure


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

Step 2 Enter mpx_sys stop to stop the Application Server software.

Step 3 Enter ntpdate -u ntp-server to immediately synchronize the system clock with the NTP server, specified by hostname or IP address.

Step 4 Enter reboot to restart the system.


Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Configuring NTP on the Application Server

Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace

Manually Changing the Time of the Application Server System Clock


Caution Do not use this procedure to change the system clock to an earlier time. Instead, see System Clock is Wrong—Need to Set it to an Earlier Time.

Restrictions

We do not recommend using this manual method of setting the system clock. Instead, you should configure NTP to synchronize the system clock to a reliable external NTP server.

Users may not be able to attend meetings that are scheduled to begin close to when you change the time of the system clock.

The time stamps on log messages may reflect the previous system time.

If you sort log messages by time, then the messages may appear in the wrong order.

If you filter log messages by time, then some messages may be lost due to incorrect time stamps.

Procedure


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

Step 2 Enter mpx_sys stop to stop the Application Server software.

Step 3 Enter date MMDDhhmm[YYYY][.ss] to specify the month, day, hour, minute, and optionally the calendar year and seconds.

Step 4 Enter reboot to restart the system.


Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Configuring NTP on the Application Server

Viewing the Application Server System Clock

Procedure


Step 1 Sign in to the Application Server CLI.

Step 2 Enter the date command.

[root@application-server ~]# date 
Tue Sep 29 00:40:46 PDT 2009
[root@application-server ~]# 
 
   

Related Topics

Using the Command-Line Interface (CLI) on the Application Server

Configuring the Time and Time Zone for the Application Server

Configuring the Time for the Web Server


Caution Do not manually adjust the clock on the Web Server. Doing so could cause the Web Server to crash. If a one-time manual adjustment is necessary, then stop the Cisco Unified MeetingPlace Web Master Service, make the manual adjustment, and then restart the Web Master Service.

Configuring NTP on the Web Server

Configuring NTP on a Web Server in a Domain

Synchronizing the Time Between the Web Server and the NTP Server Via the Web Master Service and Windows Time Service

Viewing the Web Server Clock

Configuring NTP on the Web Server


NoteThis topic does not apply to Web Servers in a domain. If your Web Server is in a domain, then instead see Configuring NTP on a Web Server in a Domain.

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://www.cisco.com/en/US/products/sw/ps5664/ps5669/
products_implementation_design_guides_list.html
.


Cisco Unified MeetingPlace automatically sets up the Web Server to use the Application Server as the NTP server for clock synchronization. We recommend that you keep this default configuration, but if you need to synchronize the Web Server with an alternate NTP server, then use this procedure to do so.

Before You Begin

Read the "Recommendations for Time and Time Zone Configurations" section.

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 inbound in your firewall for the default NTP configuration to work. In the default configuration, the Web Server clock is synchronized 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 Application Server and Web Server perfectly synchronized with each other. If the time is not synchronized between the two servers, certain features will not work.

Procedure


Step 1 Stop the Cisco Unified MeetingPlace Web Master Service.

Step 2 Select Start > Settings > Control Panel.

Step 3 Double-click Date and Time.

Step 4 Select the Internet Time tab.

Step 5 Check the Automatically synchronize with an Internet time server check box.

Step 6 Select or enter the FQDN of the NTP server in the Server field.

Step 7 Select Update Now.

Step 8 Select OK.

Step 9 Start the Cisco Unified MeetingPlace Web Master Service.


Verifying

We highly recommend that you verify clock synchronization between the Application Server and the Web Server. To obtain the current date and time for each server:

Application Server—Use the date command.

Web Server—Double-click the displayed time at the bottom right corner of the Web Server desktop.

Related Topics

Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service

Using the Command-Line Interface (CLI) on the Application Server

Configuring Time and Time Zones

Configuring NTP on a Web Server in a Domain


NoteThis topic applies only to Web Servers that are part of a domain. If your Web Server is not in a domain, then instead see Configuring NTP on the Web Server.

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://www.cisco.com/en/US/products/sw/ps5664/ps5669/
products_implementation_design_guides_list.html
.


Complete the following tasks in the order shown:

1. Pointing the Domain Controller to the External NTP Source

2. Changing the Registry Setting Manually on the Web Server

Pointing the Domain Controller to the External NTP Source

Before You Begin

Read the "Before You Begin" section.

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

Procedure


Step 1 Open a command prompt.

Step 2 Enter net stop W32Time.

Step 3 Enter w32tm /config /manualpeerlist:NTP-server /syncfromflags:manual /reliable:yes /update

An example of an NTP server is clock.cisco.com.

Step 4 Wait for the previous command to complete successfully.

Step 5 Enter net start W32Time.

Step 6 Enter w32tm /stripchart /NTP-provider /samples:2/dataonly.

Step 7 Verify that the command output shows no difference between the local time and the external NTP provider time.


What to Do Next

Proceed to Changing the Registry Setting Manually on the Web Server.

Changing the Registry Setting Manually 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 Pointing the Domain Controller to the External NTP Source.

Export the current registry key to a flat file. The registry key is located at HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters.

Procedure


Step 1 Open a DOS command window on the Web Server.

Step 2 Enter net stop W32Time.

Step 3 Enter w32tm /unregister.

Step 4 Enter 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 net start W32Time.

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

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.


Related Topics

Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace

Stopping, Starting, or Restarting the Cisco Unified MeetingPlace Web Master Service

Synchronizing the Time Between the Web Server and the NTP Server Via the Web Master Service and Windows Time Service

At each Web Master Service restart or Web Server reboot, the Web Server software invokes the Windows Time Service to synchronize the time with the NTP server. This synchronization occurs regardless of the time difference.

Once the Web Master Service is started, the Web Server time is synchronized with the NTP server every hour, but only if the time difference is 30 seconds or less.

To synchronize the time between the Web Server and the NTP server, complete the following tasks in the order shown:

1. Verifying That the Windows Time Service is Running

2. Restarting the Web Master Service

Verifying That the Windows Time Service is Running

Procedure


Step 1 Go to the Windows Start menu on the Web Server.

Step 2 Select Settings > Control Panel > Administrative Tools > Services.

Step 3 Find the Windows Time service.

Step 4 Make sure that the Startup Type for the Windows Time service is Automatic.

If not, then do the following:

a. Double-click Windows Time.

b. Select Automatic in the Startup type field.

c. Select OK.

Step 5 Verify that the Status for the Windows Time service is Started.

Proceed only if you do not see "Started" in the Status column for the Windows Time service.

Step 6 Right-click Windows Time.

Step 7 Select Start.

Step 8 Verify that Started now appears in the Status column for the Windows Time service.


What To Do Next

If you are trying to synchronize the time between the Web Server to the NTP server, then proceed to Restarting the Web Master Service.

Viewing the Web Server Clock

Procedure


Step 1 Go to the Web Server desktop.

Step 2 Double-click the time in the bottom right-hand corner.

Step 3 The date and time is displayed.


Related Topics

Configuring Time and Time Zones

Troubleshooting Time and Time Zone Issues for Cisco Unified MeetingPlace

Configuring the Time for the Hardware Media Server

This topic applies only to deployments which include the Cisco Unified MeetingPlace Media Server.

For the Cisco Unified MeetingPlace 3515 Media Server, one audio blade is built into the chassis. For the Cisco Unified MeetingPlace 3545 Media Server, you may install multiple audio blades, each of which has a clock. Video blades do not have any clocks.

Configuring NTP on the Audio Blade

Viewing the Audio Blade Clock

Configuring NTP on the Audio Blade

Procedure


Step 1 Sign in to the Media Server Administrator (MSA) for the Hardware Media Server.

Step 2 On the left side of the MSA for the Hardware Media Server, do one of the following:

Select Board for Cisco Unified MeetingPlace 3515 Media Server

Select Device for Cisco Unified MeetingPlace 3545 Media Server

Step 3 Select the Basics tab.

Step 4 Find the Date/Time field.


Viewing the Audio Blade Clock

Procedure


Step 1 Sign in to the Media Server Administrator (MSA) for the Hardware Media Server.

Step 2 On the left side of the MSA for the Hardware Media Server, do one of the following:

Select Board for Cisco Unified MeetingPlace 3515 Media Server

Select Device for Cisco Unified MeetingPlace 3545 Media Server

Step 3 Select the Basics tab.

Step 4 Find the Date/Time field.


Configuring the Time for the Cisco WebEx Node

Viewing the Cisco WebEx Node Clock

Changing the Time of the Cisco WebEx Node Clock

Changing the Time Zone of the Cisco WebEx Node

Viewing the Cisco WebEx Node Clock

The clock on the Cisco WebEx Node for MCS is always synchronized to the Cisco WebEx site.

Procedure


Step 1 Sign in to the CLI of the Cisco WebEx Node.

Step 2 Enter the show system date command.

cisco-webex-node > show system date 
Tue Sep 29 09:00:04 GMT 2009
 
   

Related Topics

How to Sign In to the Cisco WebEx Node for MCS CLI

Changing the Time of the Cisco WebEx Node Clock

Typically, the date and time of the Cisco WebEx Node for MCS is set during installation. After installation, the clock is automatically synchronized with the Cisco WebEx site. You do not need to configure NTP.

Use this procedure only if the time was inadvertently set to a value so far from the correct time that the Cisco WebEx Node was unable to automatically synchronize time with the Cisco WebEx site.

Procedure


Step 1 Sign in to the CLI of the Cisco WebEx Node.

Step 2 Switch to the Linux terminal by entering the following command:

utils system terminal

Step 3 When prompted, enter the root password.

Step 4 Enter su to get to the root user level.

Step 5 When prompted, enter the root password.

Step 6 Enter date to display the current time and date setting.

Proceed only if you still want to change the time.

Step 7 Set the date and time by entering the date command with the month (MM), day (DD), hour (hh), and minute (mm). Entering the year (yyyy) is optional:

date MMDDhhmm[yyyy]


Changing the Time Zone of the Cisco WebEx Node

The time zone must always be set to Greenwich Mean Time (GMT). Complete this task if the time zone was inadvertently set to any value other than GMT.

Procedure


Step 1 Sign in to the CLI of the Cisco WebEx Node.

Step 2 Switch to the Linux terminal by entering the following command:

utils system terminal

Step 3 When prompted, enter the root password.

Step 4 Enter su to get to the root user level.

Step 5 When prompted, enter the root password.

Step 6 Enter date to display the current time and time zone setting.

Proceed only if the time zone is not GMT.

Step 7 Set the time zone to GMT by entering the following command:

cp /usr/share/zoneinfo/GMT/etc/localtime

Step 8 Enter date to verify that the time zone is set to GMT.