All switches in the fabric maintain the current clock server value in non-volatile
memory. By default, this value is the local clock server <LOCL> of the principal or
primary FCS switch. Changes to the clock server value on the principal or primary
FCS switch are propagated to all switches in the fabric.
For more information on using an NTP server, and IPv6 considerations, see the
Fabric OS Administrator’s Guide.
1. If you are not already logged into the switch; do so now using the default
password, which is password.
2. Enter the tsClockServer command:
switch:admin> tsclockserver "<ntp1;ntp2>"
where ntp1 is the IP address or DNS name of the first NTP server, which the
switch must be able to access. The second ntp2 is the second NTP server and is
optional. The operand “<ntp1;ntp2>” is optional; by default, this value is
LOCL, which uses the local clock of the principal or primary switch as the
clock server.
The tsClockServer command accepts multiple server addresses in either IPv4, IPv6,
or DNS name formats. When multiple NTP server addresses are passed,
tsclockserver sets the first obtainable address as the active NTP server. The rest
will be stored as backup servers that can take over if the active NTP server fails.
The principal or primary FCS switch synchronizes its time with the NTP server
every 64 seconds.
switch:admin> tsclockserver
LOCL
switch:admin> tsclockserver "132.163.135.131"
switch:admin> tsclockserver
132.163.135.131
switch:admin>
The following example shows how to set up more than one NTP server using a
DNS name:
switch:admin> tsclockserver "10.32.170.1;10.32.170.2;ntp.localdomain.net"
Updating Clock Server configuration...done.
Updated with the NTP servers
Changes to the clock server value on the principal or primary FCS switch
are propagated to all switches in the fabric.
20 SAN24B-4 Installation, Service, and User Guide
To Next Page
Loading...
Need help?
General