How To Synchronize Local Time With An External Source; Maintaining Licensed Software Features - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

How to synchronize local time with an external source

1. Connect to the switch and log in with 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.
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.

Maintaining licensed software features

If you purchase an HP StorageWorks Power Pack switch model, optional software licenses are included
with the licensed Power Pack supplied with the switch software.
If you did not purchased an HP StorageWorks Power Pack switch model, you can purchase licenses
separately from HP. HP then provides you with keys to unlock the optional software features.
License keys are provided on a per-chassis basis and per-feature basis. Each switch or domain within a
fabric will need its own licensing.
NOTE: To preserve licenses on your switch, perform a configupload prior to upgrading or
downgrading your Fabric OS. If you downgrade Fabric OS 5.3.0 to a previous version, licenses associated
with specific features of 5.3.0 will not work on previous versions of Fabric OS.
Licenses can be associated with a feature version or a blade type.
• If a feature has a version-based license, that license is valid only for a particular version of the feature.
If you want a newer version of the feature, you need to purchase a new license.
Version upgrade: For example, a zoning license that is for Fabric OS version 4.4 is added. You can
add another zoning license with version greater than 4.4 and above without removing the zoning
license for Fabric OS v4.4. Upgrading is allowed, but downgrading is not supported.
If a license is not version-based, then it is valid for all versions of the feature.
• If a license is associated with a blade type, the licensed feature can be used only with the associated
blade; if you want to use the feature on a second blade, you must purchase an additional license.
36 Performing basic configuration tasks