offset time zone settings. The tsTimeZone command includes an option to revert to the prior time zone format. For more information about the --old option, see the Fabric OS command reference manual.
You can set the time zone for a switch using the tsTimeZone command. The TimeZone command allows you to perform the following tasks: ? Display all of the time zones supported in the firmware.
? Set the time zone based on a country and city combination or based on a time zone ID, such as PST.
? You can view the time zone settings. However, only those with administrative permissions can set the time zones.
? The tsTimeZone setting automatically adjusts for daylight savings time.
? Changing the time zone on a switch updates the local time zone setup and is reflected in local time calculations.
8Gb SAN Switch hardware reference manual 43
? By default, all switches are in the GMT time zone (0,0). If all switches in a fabric are in one time zone, it is possible for you to keep the time zone setup at the default setting. ? System services that have already started will reflect the time zone changes only after the next reboot.
? Time zone settings persist across failover for high availability.
Set the time zone IMPORTANT:
The following procedure describes how to set the time zone for a switch. You must perform the procedure on all switches for which the time zone must be set. However, you only need to set the time zone once on each switch, because the value is written to nonvolatile memory.
1. Log in to the switch using the default password, (password). 2. Enter the tsTimeZone command as follows switch:admin> tstimezone [--interactive]/ [, timezone_fmt]
Use timezone_fmt to set the time zone by Country/City or by time zone ID, such as PST. The following example shows how to change the time zone to US/Central: switch:admin>
tstimezone
Time
Zone
:
US/Pacific
switch:admin> tstimezone US/Central switch:admin>
tstimezone Time Zone : US/Central To set the time zone using interactive mode: 1. Type the tsTimeZone command:
switch:admin> tstimezone --interactive 2. You are prompted to select a general location.
Please identify a location so that time zone rules can be set correctly.
3. Enter the appropriate number or Ctrl-D to quit. 4. At the prompt, select a country location.
5. At the prompt, enter the appropriate number to specify the time zone region or Ctrl-D to quit.
Synchronizing local time using Network Time Protocol (NTP)
You can synchronize the local time of the principal or primary Fabric Configuration Server (FCS) switch to a maximum of eight external NTP servers. To keep the time in your SAN current, it is recommended that the principal or primary FCS switch has its time synchronized with at least one external NTP server. The other switches in the fabric will automatically take their time from the principal or primary FCS switch.
All switches in the fabric maintain the current clock server value in nonvolatile memory. By default, this value is the local clock server
switch:admin> tsClockServer ―
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 “
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 LOCLx
switch:admin> tsClockServer \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
\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.
Verify the configuration
To confirm that the switch is configured and ready for use:
1. Check the LEDs to verify that all components are functional. For information about LED patterns, see Table 10.
2. Issue the switchshow command from the workstation. This command provides information about the switch and port status.
3. Issue the fabricshow command from the workstation. This command provides general information about the fabric.
Back up the configuration
HP recommends regular backups to ensure that a recent configuration is available. To back up the switch configuration to an FTP server: 1. Issue the configupload command.
2. Follow the prompts.
The command uploads the switch configuration to the server, making it available for downloading to a replacement switch, if necessary. For detailed instructions on backing up the configuration, see the HP StorageWorks Fabric OS administrator guide.
第四部分: 附 Brocade 光纤交换机划分 Zone 的案例及纠错
(一) 原因：通过光纤接入集中备份系统的Sun平台主机系统日志(/var/adm/messages)频繁报错，报错信息如下：
?????????????????..
Apr 14 16:15:34 cq97data1 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to ca0e00 failed state=Packet Transport error, reason=No Connection
Apr 14 16:15:34 cq97data1 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to c90400 failed state=Packet Transport error, reason=No Connection
Apr 14 16:15:34 cq97data1 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to c90500 failed state=Packet Transport error, reason=No Connection
Apr 14 16:15:34 cq97data1 fp: [ID 517869 kern.info] NOTICE: fp(0): PLOGI to c90900 failed state=Packet Transport error, reason=No Connection ?????????????????..
(二) 要求：在集中备份系统SAN环境中的三个SAN Switch上建立Zone，把 HP，
IBM和SUN的主机隔离起来。 (三) 实施前交换机情况：
三台光纤交换机（A：HP SW SAN Switch 2/16 PowerPak；B：两台Brocade Silk- Worm 3800）都没有配置Zone，所有端口之间都可以互相访问。
其中，IBM设备使用了一台Brocade SilkWorm 3800（SwitchName:3800_up, DomainID：201）上的port 10和11；
SUN设备使用了一台Brocade SilkWorm 3800（SwitchName:3800_up, DomainID： 201）上的port 1，2，12和13；
HP设备使用了一台Brocade SilkWorm 3800（SwitchName:3800_up, DomainID： 201）上的port 0，3，4，5，6，7，8，9和14及另一台Brocade SilkWorm 3800（SwitchName:3800_down, DomainID：202）上的port 0，1和14。
另外，Brocade SilkWorm 3800（SwitchName:3800_up, DomainID：201）上的port 15与大坪的交换机HPSW SAN Switch 2/16 PowerPak连接，port 7与另一台
Brocade SilkWorm 3800（SwitchName:3800_down, DomainID：202）上的port 7连接；另一台Brocade SilkWorm 3800（SwitchName:3800_down, DomainID：202）上的 port 15与大坪的交换机HPSW SAN Switch 2/16 PowerPak连接。 (四) 实施过程：
建立三个Zone(HP_Zone_201，SUN_Zone_201和IBM_Zone_201)，把属于不同系统的设备按系统类型划分到这三个Zone里面。然后让Zone生效。
aliCreate \
\\\aliCreate
\ ,14\
zonecreate \zoneAdd \ zonecreate \zoneAdd \ zonecreate \zoneAdd \zoneAdd \
cfgcreate \cfgenable \ (五) 实施后交换机情况：
不同系统的设备按系统类型划分到三个Zone里面，下面列出三个Zone所包含的端口： Zone_HP
1,0;1,14;1,15 （注：Domain ID 为1的Port 0,14和15，下面同理可得） 201,15;201,0;201,3;201,4;201,5;201,6;201,7;201,8;201,9;201,14 202,0;202,1;202,7;202,14;202,15 Zone_SUN
1,0;1,14;1,15
201,15;201,1;201,2;201,12;201,13
Zone_IBM
1,0;1,14;1,15
201,15;201,10;201,11
从此，各个Zone之间无法互相访问，则Sun平台主机系统无法存取不在同一个Zone 的交换机其他端口，报错信息不再出现，问题得以解决。
附：以下为ＳＵＮ主机无法找到以前可以访问的ＨＰ设备所报信息： ?????????????????..
Apr 14 16:29:42 cq97data2 fctl: [ID 517869 kern.warning] WARNING: 66211=>fp(0)::N_x Port with D_ID=c90300, PWWN=50060b0000229fee disappeared from fabric
Apr 14 16:29:42 cq97data2 fctl: [ID 517869 kern.warning] WARNING: 66215=>fp(0)::N_x Port with D_ID=c90800, PWWN=50060b0000229e10 disappeared from fabric
Apr 14 16:29:42 cq97data2 fctl: [ID 517869 kern.warning] WARNING: 66219=>fp(0)::N_x Port with D_ID=c90900, PWWN=50060b0000229ff0 disappeared from fabric
Apr 14 16:29:42 cq97data2 fctl: [ID 517869 kern.warning] WARNING: 66224=>fp(0)::N_x Port with D_ID=c90500, PWWN=50060b0000229fb4 disappeared from fabric ?????????????????..
总结： 在一个SAN环境下的所有San Switch上划分Zone，只需要所有交换机都有相关的License，在其中任意一台划分好并将配置应用后，其他所有的交换机都会将此配置应用到它们上面去。