HP StorageWorks 2/128 - SAN Director Switch Release Note page 15

Table 5: Fabric OS Area Information (Continued)
Fabric OS Area
Fabric Device
Management Interface
(FDMI)
Fabric OS: CLI
commands, failover,
and port disable
Fabric OS: commands
Fabric OS: switch
beaconing
Fabric OS: switch
reboot and blade
repair
Fabric routing, Fabric
Manager: domain
overlap
Fabric Watch: e-mail
alert error message
Firmware download
SAN Director 2/128 Fabric OS 4.2.x Release Notes
An HBA will be allowed to register even though the originating port is not
on the HBA's registered port list. This is intended behavior, included to test
error cases.
Changing port configurations during a failover might cause ports to be
disabled. Reissue the command after the failover is complete to bring the
ports online.
Under the root account, issuing Fabric OS commands in parallel through
scripts could cause the kernel task to consume excessive memory.
Workaround: When using scripts to issue Fabric OS commands, wait for
one command to finish before issuing another.
Switch beaconing is not preserved across a failover. If you start beaconing,
a failover causes all lights to stop flashing.
Workaround: If this occurs, reissue the command to resume switch
beaconing.
Switch reboot will fail in the SAN Director 2/128 if there are faulty port
blades.
Note: Verify that all blades are in working order before performing a
switch reboot. Switch reboot is meant to be issued after all repairs are
complete. If you perform a switch reboot and find a faulty blade, remove the
blade and reboot will continue.
Workaround: Identify and remove the faulty blade, using the slotshow
command.
Issuing a configdefault command followed by reboot or switch disable
or enable can cause the fabric to segment due to possible domain overlap.
Workaround: Before rebooting the fabric, ensure that all switches are
properly configured to avoid domain overlap between the logical switches.
If an event occurs while Fabric Watch e-mail alerts are being enabled, the
message ErrLog: Error Level=3 [(null)] is captured to the
system error log. This message is from SMTP and can be ignored.
During a firmware download, rebooting or power cycling the CPs could
corrupt the compact flash.
CAUTION: Do not attempt to power off the CP board during firmware
download, to avoid high risk of corrupting your flash.
Description
Important Notes
15