40
Synchronizing the local time with an external source
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 are 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.
1.
Connect to the switch and log in using an account assigned to the admin role.
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.
switch:admin>
tsclockserver
LOCL
switch:admin>
tsclockserver "132.163.135.131"
switch:admin>
tsclockserver
132.163.135.131
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.
Switch names
Switches can be identified by IP address, Domain ID, World Wide Name (WWN), or by customized
switch names that are unique and meaningful.
Switch names can be from 1 to 30 characters long. The HP StorageWorks DC SAN Backbone Director and
HP StorageWorks DC04 SAN Director Switch naming convention is 1 to 15 characters in length. All switch
names must begin with a letter, and can contain letters, numbers, or the underscore character. It is not
necessary to use quotation marks.
Changing the switch name causes a domain address format RSCN (registered state change notification) to
be entered and may be disruptive to the fabric.
Customizing the switch name
1.
Connect to the switch and log in using an account assigned to the admin role.
2.
Enter the
switchName
command, using the following syntax:
switchname "
newname
"
where
newname
is the new name for the switch.
3.
Record the new switch name for future reference.
4.
Record the new switch name for the second domain for future reference.
Chassis names
HP recommends that you customize the chassis name for each platform. Some system logs identify devices
by platform names; if you assign meaningful platform names, logs are more useful. All chassis names have
a limit of 15 characters except for the HP StorageWorks 8/8, 8/24, 8/40, and 8/80 SAN Switches,
which is 31. Chassis names must begin with a letter, and can contain letters, numbers, or the underscore
character.
Summary of Contents for A7533A - Brocade 4Gb SAN Switch Base
Page 1: ...HP StorageWorks Fabric OS 6 2 administrator guide Part number 5697 0016 Edition May 2009 ...
Page 24: ...24 ...
Page 99: ...Fabric OS 6 2 administrator guide 99 ...
Page 100: ...100 Managing user accounts ...
Page 118: ...116 Configuring standard security features ...
Page 164: ...162 Configuring advanced security features ...
Page 234: ...232 Installing and maintaining firmware ...
Page 268: ...266 Administering advanced zoning ...
Page 284: ...282 Configuring Enterprise class platforms ...
Page 292: ...290 Routing traffic ...
Page 294: ...292 Interoperability for merged SANs ...
Page 302: ...300 Configuring the Distributed Management Server ...
Page 334: ...332 iSCSI gateway service ...
Page 340: ...338 Administering NPIV ...
Page 407: ...Fabric OS 6 2 administrator guide 405 ...
Page 408: ...406 Using the FC FC routing service ...
Page 438: ...434 Administering extended fabrics ...
Page 460: ...456 Administering ISL trunking ...
Page 516: ...512 FICON fabrics ...
Page 526: ...522 Configuring and monitoring FICON Extension Services ...
Page 540: ...536 Configuring the PID format ...
Page 544: ...540 Understanding legacy password behavior ...
Page 546: ...542 Mixed fabric configurations for non merge SANs ...
Page 550: ...546 Migrating from an MP Router to a 400 MP Router ...
Page 558: ...554 Inband Management ...
Page 572: ...568 ...