Release 7.1
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 1998 -2012 EMC Corporation. All rights reserved.
Published July 2012
EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO
THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.
For the most up-to-date regulatory document for your product line, go to the Technical
Documentation and Advisories section on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on
EMC.com.
All other trademarks used herein are the property of their respective owners.
Corporate Headquarters: Hopkinton, MA 01748-9103
Preface.....................................................................................................5
Chapter 1: Introduction...........................................................................9
System requirements.............................................................................................10
Cautions..................................................................................................................10
User interface choices...........................................................................................10
Related information..............................................................................................11
Chapter 2: Concepts.............................................................................13
NTP..........................................................................................................................14
SNTP........................................................................................................................14
Time distribution...................................................................................................14
Select NTP servers.................................................................................................15
Clock adjustment...................................................................................................16
Time zones..............................................................................................................16
Time services..........................................................................................................17
Chapter 3: Configuring.........................................................................19
Start Data Mover time services............................................................................20
Start time services — Example 1...............................................................20
Start time services — Example 2...............................................................21
Start time services — Example 3...............................................................21
Verify the time services configuration................................................................22
Chapter 4: Managing............................................................................23
Set the Data Mover system time..........................................................................24
Update the Data Mover system time..................................................................24
Chapter 5: Troubleshooting..................................................................31
EMC E-Lab Interoperability Navigator..............................................................32
Diagnose problems................................................................................................32
Error messages.......................................................................................................33
EMC Training and Professional Services...........................................................33
Glossary..................................................................................................45
Index.......................................................................................................47
As part of an effort to improve and enhance the performance and capabilities of its product lines,
EMC periodically releases revisions of its hardware and software. Therefore, some functions described
in this document may not be supported by all versions of the software or hardware currently in use.
For the most up-to-date information on product features, refer to your product release notes.
If a product does not function properly or does not function as described in this document, please
contact your EMC representative.
Note: Emphasizes content that is of exceptional importance or interest but does not relate to personal
injury or business/data loss.
CAUTION Indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
Indicates a hazardous situation which, if not avoided, could result in death or serious injury.
DANGER Indicates a hazardous situation which, if not avoided, will result in death or serious
injury.
Note: Do not request a specific support representative unless one has already been assigned to
your particular system problem.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications.
Please send your opinion of this document to:
techpubcomments@EMC.com
Introduction
Time services configuration is one of the basic tasks that you must perform
to ensure the correct operation of VNX. This document describes how to
configure and use time services on the Data Movers in VNX. VNX System
Operations describes how to set the time zone for the system and how to
manually set the current date and time on the Control Station.
This document is part of the VNX documentation set and is intended for
use by the system administrators responsible for configuring and
maintaining the file storage and network retrieval infrastructure. This
section includes some terminology and restrictions that you should be
familiar before configuring or modifying network settings.
Topics included are:
◆ System requirements on page 10
◆ Cautions on page 10
◆ User interface choices on page 10
◆ Related information on page 11
System requirements
Table 1 on page 10 describes the EMC® VNX™ software, hardware, network, and storage
configurations.
Network To use NTP with VNX, at least one NTP server on the network must be accessible to the file server.
To use the Control Station as a time server for the Data Movers, time services must be configured and
started on the Control Station.
Cautions
If any of the following information is unclear, contact your EMC Customer Support
Representative for assistance:
◆ Do not use the Control Station as time server for the Data Movers in the VNX system.
Use standard time servers for all clients and services whenever possible.
◆ If you have configured time services on the Data Movers to use the Control Station as
the only time server, either stop time services on the Data Movers or configure additional
time servers on the Data Movers before stopping the time service on the Control Station.
Related information
The following documents provide specific information related to the features and
functionality described in this document:
Related information 11
Introduction
Concepts
The Network Time Protocol (NTP) and Simple Network Time Protocol
(SNTP) provide the mechanism for keeping the current time synchronized
on multiple systems in a network. A hierarchical structure of time servers
distributes a timestamp, which the clients use to adjust their system time.
The time distributed by the servers is expressed in coordinated universal
time (UTC) and is independent of the client’s and server’s time zone. The
network data format is identical for NTP and SNTP.
The Data Mover implements an NTP client that can synchronize the system
clock with that of an NTP or SNTP server. In all commands and in the
remaining part of this document, the term NTP server is used to refer to
either NTP or SNTP servers.
For many applications to work correctly, the client and server time must
be approximately the same. For example, Kerberos that is supported in
Windows and certain UNIX environments, requires all clients and servers
to be synchronized to within at least five minutes.
Topics included are:
◆ NTP on page 14
◆ SNTP on page 14
◆ Time distribution on page 14
◆ Select NTP servers on page 15
◆ Clock adjustment on page 16
◆ Time zones on page 16
◆ Time services on page 17
NTP
NTP is a standard time-keeping protocol used on many platforms that include Microsoft
Windows and UNIX environments. The full NTP specification uses sophisticated algorithms
for time correction and maintenance to allow time synchronization with an accuracy of
about a millisecond. This high level of accuracy is achieved even in large networks with
long network delays, or in cases where access to a time server is lost for extended time
periods.
SNTP
SNTP implements a subset of NTP for use in environments with less-stringent
synchronization and accuracy requirements. SNTP uses simple algorithms for time correction
and maintenance and is capable of accuracy to a fraction of a second. To an NTP or SNTP
client, NTP and SNTP servers are indistinguishable.
Time distribution
NTP and SNTP are implemented in a hierarchy of time servers, with public servers
synchronized with reference clocks at the top of the hierarchy and NTP clients at the bottom.
Intermediate nodes can be clients and servers. The public time servers distribute time to
clients at no cost. Typically, organizations synchronize one or a few local servers to a public
server, and then distribute the time within the organization using those local time servers.
Figure 1 on page 15 shows a simplified example of a time server distribution hierarchy.
There is no need to synchronize with a public time server for time services to work correctly
on VNX. Select NTP servers on page 15 provides more information on choosing the NTP
servers.
If you do not have a dedicated NTP infrastructure for time control, use a Windows Server
2003 or Windows 2000 domain controller as a time server for a Data Mover.
Note: By default, all Windows Server 2003 or Windows 2000 domain controllers can operate as time
servers. Furthermore, within a Windows Active Directory environment, all domain controllers operating
as time servers synchronize with the domain controller in the root domain of the forest.
If there is no need for time coordination with clients of a Data Mover, then the Control
Station can be used as a time server for the Data Mover.
CAUTION Do not use the Control Station as a time server for the Data Movers in the VNX system.
Use only standard time servers for all clients and services when possible.
Clock adjustment
A clock offset is calculated after a successful poll of the time server. The clock offset is the
difference between the local time and the time retrieved from the server. The offset can be
positive or negative, which means that the local time is either ahead of or behind the time
server. Under normal circumstances, SNTP makes time corrections by slewing the system
clock. This means instead of applying the time offset directly, the system time is gradually
increased or decreased to bring the local time into agreement with the time server. This
process ensures that the time does not change abruptly and the clock never appears to be
set behind.
The slew rate on a Data Mover is about 10 percent, which means that it takes approximately
1 hour to make a 6-minute correction in system time. Normally, system startup does not
slew the clock because the time offset is often too large to adjust in a reasonable amount of
time. However, you can force the Data Mover to slew the time correction on system startup.
To correct the system time immediately, force a new time query and immediately set the
system clock to the returned time, rather than slewing the clock. Alternatively, you can force
a query, but slew the clock to adjust it to the returned time rather than adjusting it
immediately.
Time zones
It is possible to set a time zone on a Data Mover. Each Data Mover keeps its own, separate,
universal time (GMT by default). Setting the time zone does not change the Data Mover
time. It only changes the way the Data Mover interprets that time when it needs to generate
text-time strings during processing. In other words, the Data Mover generates a time for
the set time zone.
Note: Setting a time zone on a Data Mover is not necessary unless you want an application, such as
Checkpoint Virtual File System (CVFS), Virus Checker, or File Transfer Protocol (FTP) to generate a
time based upon the local time zone.
VNX provides two optional procedures to update the time zone information on the Data
Mover:
◆ Set a time zone by using the POSIX-method on page 28 provides a procedure to manually
update the time zone information on a Data Mover by using a POSIX string as input.
The Control Station contains the time zone database with each time zone represented by
a separate file in the directory.
◆ Set a time zone by using the Linux method on page 29 provides a procedure to update
the time zone information on the Data Mover that uses simple and decipherable strings,
corresponding to the time zones available in the Control Station. It also updates the
daylight savings time in the Data Mover for the specified time zone. You might find it
more convenient to set the time zone by using this procedure.
Time services
When starting time services on a Data Mover, up to four NTP servers can be specified, using
the NTP servers’ IP addresses. These servers must run the NTP protocol.
Note: The term NTP server is used to refer to either NTP or SNTP servers.
The time services client on the Data Mover polls the specified time servers in the order
specified. After sending the polling message, the Data Mover waits for a reply. When a reply
is received, the time services client corrects the time. If no reply is received, the Data Mover
polls the next time server on the list.
If no time servers are specified, the Data Mover attempts to discover NTP servers on the
network, and then automatically configures up to four time servers.
For the Data Movers in VNX, you can do one of the following:
◆ Start time services immediately by setting the system clock to the returned value.
◆ Start time services, and begin a gradual change of the system clock to the returned value
by slewing the system time.
In either case, use the -interval option to specify the interval between polls of the time server.
Note: You cannot configure time services on a Virtual Data Mover (VDM). A VDM’s time services
configuration is based on its associated physical Data Mover.
Start Data Mover time services on page 20 describes the procedure for starting time services.
Time services 17
Concepts
Configuring
Time services are not automatically started on the Data Mover after initialization. However,
EMC recommends that you always configure time synchronization between a Data Mover
and an external time source.
Action
To start time services on a Data Mover and immediately set the system time to the value returned by the specified time
server, use this command syntax:
$ server_date <movername> timesvc start ntp [<host>[,<host>,...]]
where:
<movername> = name of the Data Mover
Example:
To start the time service on server_2 and immediately set the system time to the first value returned by the time server,
that uses the default interval between polls of the timer server to one hour, type:
$ server_date server_2 timesvc start ntp 192.168.21.250
Output
server_2 : done
Action
To start time services on a Data Mover and immediately set the system time to the value returned by the specified time
server, and to specify the interval between polls of the time server, use this command syntax:
$ server_date <movername> timesvc start ntp [-interval <hh>[:<mm>]]
[<host>[,<host>,...]]
where:
<movername> = name of the Data Mover
<hh> = hours
<mm> = minutes
Example:
To start the time service on server_2 and immediately set the system time to the first value returned by the time server,
and set the interval between polls of the time server to one hour, 30 minutes, type:
$ server_date server_2 timesvc start ntp -interval 01:30 192.168.21.250
Output
server_2 : done
Action
To start time services on a Data Mover and begin gradually modifying the system time to the value returned by the specified
time server, and specifying the interval between polls of the time server, use this command syntax:
$ server_date <movername> timesvc start ntp [-sync_delay] [-interval
<hh>[:<mm>]] [<host>[,<host>,...]]
where:
<movername> = name of the Data Mover
<hh> = hours
<mm> = minutes
Example:
To start the time service on server_2 and begin slewing the system time to match the first value returned by the time
server, and set the interval between polls of the time server to one hour, 30 minutes, type:
Action
$ server_date server_2 timesvc start ntp -sync_delay -interval 01:30 192.168.21.250
Output
server_2 : done
Example:
To display the time service configuration for server_2, type:
$ server_date server_2 timesvc
Output
server_2 :
Timeservice State
Note
If you did not start time synchronization with an external time source by issuing the server_date <movername> timesvc
start ntp command, the output is blank.
Managing
Example:
To poll the time server for the time and set the system time for server_2 to the value returned by the timer server, type:
$ server_date server_2 timesvc set ntp
Output
server_2 : done
Example:
To poll the timer server and start a gradual synchronization (slewing) of the system time on server_2 to the time returned
by the time server, type:
$ server_date server_2 timesvc update ntp
Output
server_2 : done
Action
where:
<movername> = name of the Data Mover
Example:
To stop the timer service on server_2, type:
$ server_date server_2 timesvc stop ntp
Output
server_2 : done
Action
To delete the time services configuration on a Data Mover, use this command syntax:
$ server_date <movername> timesvc delete ntp
where:
<movername> = name of the Data Mover
Example:
To delete the time services configuration for server_2, type:
$ server_date server_2 timesvc delete ntp
Output
server_2 : done
Example:
To display time services statistics for server_2, type:
$ server_date server_2 timesvc stats ntp
Output
server_2 :
Note
The output includes the list of time servers and the time offset calculated from the most recent poll, -57639 microseconds
or about 58 milliseconds.
The two fields before the IP address under Time sync hosts are the type and the priority fields. The type field determines
if the host in question was configured by an operator or if it was auto-detected (0 = operator configured, 1 = auto-detected).
The priority depends on the type. If the host was configured, the priority is 1, otherwise the priority is equal to the time
server stratem, which indicates how accurate the time server source is (1 means the greatest accuracy while a greater
number means less accuracy). When a number of hosts is auto-detected, the four fastest hosts are kept at the top. Servers
that respond later can displace only a server with a lower (numerically higher) priority. Therefore, auto-detected servers
are ordered by their priority and by how quickly they responded. As configured servers have a priority of 1, they cannot
be displaced by an auto-detected server.
<yymmddhhmm>[<ss>] = year, month, day, hour (in 24-hour system), minutes, and seconds
Example:
To manually set the time and date to 1:36 P.M. on July 16, 2004 for server_2, type:
$ server_date server_2 0407161336
Output
server_2 : done
Display the current time and date for the Data Mover
Action
To display the current time and date for the Data Mover, use this command syntax:
$ server_date <movername>
where:
<movername> = name of the Data Mover
Example:
To display the time services configuration for server_2, type:
$ server_date server_2
Output
server_2 : Thu Jul 16 13:36:13 EDT 2004
Display the current time and date for the Data Mover 27
Managing
Action
To manually set the time zone on a Data Mover, use this command syntax:
$ server_date <movername> timezone [<timezonestr>]
where:
<movername> = name of the Data Mover
Note: See the Linux man page for tzset for information about the format.
Examples:
To set the time zone for server_2 when it is unnecessary to adjust for daylight savings time, type:
$ server_date server_2 timezone CST6
To set the time zone to Central Time and adjust for daylight savings time for server_2, type:
$ server_date server_2 timezone CST6CDT5,M4.1.0,M10.5.0
Output
server_2 : done
Action
To verify the time zone for server_2, use this command syntax:
$ server_date server_2 timezone
Output
server_2 : Local timezone: CST
Note
When the time changes to daylight savings time, server_date server_2 timezone returns the daylight time abbreviation.
Instead of returning EST or CST, the command returns the time zone as EDT or CDT.
Action
To set the time zone on a Data Mover by using the Linux time zone method, use this command syntax:
$ server_date <movername> timezone -name <timezonename>
where:
<movername> = name of the Data Mover
Note: A list of valid Linux time zones is located in the /usr/share/zoneinfo directory.
Example:
To set the time zone to Central Time and adjust the daylight savings time for a Data Mover by using the Linux method,
type:
$ server_date server_2 timezone -name America/Chicago
Output
server_2 : done
Troubleshooting
Diagnose problems
To diagnose problems with time services on VNX:
◆ Check that the Data Mover or Control Station has an external IP interface configured.
◆ Type ping <timeserver>, where <timeserver> is the IP address of the time server in
question, to determine if the Control Station can communicate with the time server.
◆ Use server_ping to determine if the Data Mover can communicate with the time server.
Type server_ping <movername> <timeserver_addr>, where <movername> is the Data
Mover name and <timeserver_addr> is the IP address of the NTP server.
Note: The term NTP server is used to refer to either NTP or SNTP servers.
◆ The statistics command server_date <movername> timesvc stats ntp provides output
that indicates whether the time services received any time updates through NTP. You
can compare the output of the statistics command before and after performing either the
set ntp or update ntp commands to determine if the Data Mover is receiving NTP
responses from any configured NTP server. This does not indicate which servers have
responded. View Data Mover time services statistics on page 25 provides more
information on timesvc stats, Set the Data Mover system time on page 24 provides more
information on set ntp, and Update the Data Mover system time on page 24 provides
more information on update ntp.
◆ For UNIX time servers, from Control Station, type rdate -p <timeserver>, where
<timeserver> is the name or IP address of the remote time server.
For a Windows time server, type the following command from a Windows client net
time \\<timeserver>, where <timeserver> is the hostname or IP address of the remote
time server.
The command output shows if the NTP or SNTP service is available by displaying the
current date and time.
As a last resort, deleting and then re-creating the time services configuration on the Data
Mover could resolve the problem.
Error messages
All event, alert, and status messages provide detailed information and recommended actions
to help you troubleshoot the situation.
To view message details, use any of these methods:
◆ Unisphere software:
• Right-click an event, alert, or status message and select to view Event Details, Alert
Details, or Status Details.
◆ CLI:
• Use this guide to locate information about messages that are in the earlier-release
message format.
• Use the text from the error message's brief description or the message's ID to search
the Knowledgebase on the EMC Online Support website. After logging in to EMC
Online Support, locate the applicable Support by Product page, and search for the
error message.
Error messages 33
Troubleshooting
If you do not have a dedicated NTP infrastructure for time control, use a
Windows Server 2003 or Windows 2000 domain controller as a time server
for a Data Mover. By default, all Windows Server 2003 or Windows 2000
domain controllers can operate as time servers. Furthermore, within a
Windows Active Directory environment, all domain controllers operating
as time servers synchronize with the domain controller in the root domain
of the forest.
5. Right-click Parameters and select Modify. The Edit DWORD Value dialog box appears.
6. Select Registry ➤ Edit to close the Registry Editor and save the change.
7. From the Start menu in Windows, select Programs ➤ Administrative Tools ➤ Services.
The Services dialog box appears.
10. After the service is stopped, right-click it again and click Start.
11. After the service is restarted, close the Services dialog box.
You can use the Control Station as a time server for the Data Movers.
CAUTION Do not use the Control Station as a time server for the Data Movers
in the VNX system. Use standard time servers for all clients and services
whenever possible.
To use NTP as the time service on the Control Station, create an NTP
configuration file and start the NTP daemon.
Note: The term NTP server is used to refer to either NTP or SNTP servers.
After time services are configured and started, you can stop, disable, and
enable time services as well as verify the time services configuration.
Note: If you are using a standby Control Station, configure the time server settings
on the primary and standby Control Station so that they are the same.
5. Comment out the following line, if it exists, by inserting a # at the beginning of the line:
fudge 127.127.1.0 stratum 10
Output:
Starting ntpd: OK
4. Verify that the daemon is running by typing:
# /sbin/service ntpd status
Output:
ntpd (pid 1234) is running...
CAUTION If you configured time services on the Data Movers to use the Control Station as the
only time server, you should either stop time services on the Data Movers or configure additional
time servers on the Data Movers before stopping the time service on the Control Station.
Output:
Shutting down ntpd: OK
4. Verify that the daemon is stopped by typing:
# /sbin/service ntpd status
Output:
ntpd is stopped
This prevents the daemon from restarting when the Control Station restarts.
Output:
ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
The status for each run level (0 through 6) should be off.
Continue with step 5 if you want to immediately stop time services.
Output:
Shutting down ntpd: OK
6. Verify that the daemon is stopped by typing:
# /sbin/service ntpd status
Output:
ntpd is stopped
This restarts the NTP daemon whenever the Control Station is restarted.
Output:
ntpd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
The status for run level 3 should be on.
There might be other run levels also set to on.
If time services are not currently running and you want to immediately start them,
continue with step 5.
Output:
Starting ntpd: OK
6. Verify that the daemon is running by typing:
# /sbin/service ntpd status
Output:
ntpd (pid 1234) is running...
3. Look for lines in the ntp.conf file with the following format:
server <IP_address> minpoll 8
where:
<IP_address> = address of an NTP time server accessible to the Control Station
Example:
server 192.168.9.10 minpoll 8
Verify that the server addresses are ones you chose for the time servers.
Output:
ntpd (pid 1234) is running...
5. Verify that the daemon is enabled and configured to restart when the Control Station
restarts by typing:
# /sbin/chkconfig --list ntpd
Output:
ntpd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
The status for run level 3 should be on, which means that the daemon restarts when the
Control Station restarts. There might be other run levels also set to on.
Example:
$ server_date server_2 timesvc start ntp 192.168.1.100 192.168.2.100
Output
server_2 : done
clock offset
Difference between the local system time and the time retrieved from the time server.
slewing
Process of gradually correcting the local system time.
A error messages 33
Control Station
NTP daemon N
disabling 41 NTP
enabling 42 accuracy of 14
starting 40 ntp.conf file 40, 43
stopping 41 ntpd
ntp.conf file on 40, 43 disable 41
verifying time-services configuration 43 enabling 42
starting 40
D stopping 41
overview of 14
Data Mover server limit on Data Mover 17
system time, setting from time server 24
time and date
setting 26 S
time server server_date
automatic detection 17 setting
domain controller as 35 system time 24
limit 17 time and date 26
order 17 time zone 28, 29
time service starting time services 20, 44
verifying configuration 21 using
time slewing on 16 set ntp 16
time zone update ntp 16
setting 28, 29 verifying 21
using 16 slewing
on Data Movers 16
E overriding on Data Movers 16
overview of 16
EMC E-Lab Navigator 32 SNTP
accuracy of 14