HP StorageWorks Fabric Manager 5.X Release Notes (AA-RUR2F-TE, September 2005)

Important notes8
Important notes
See the HP StorageWorks Fabric Manager 5.x administrator guide for details regarding the features
specified in Table 2.
Table 2 Important notes
Issue Description
MP Router as
launch switch
Do not use the MP Router as the launch switch unless it is the only switch in your fabric. If you do
use the MP Router as the launch switch, physical inventory data for all other switches in that
fabric will be incomplete.
Call Home
executable cannot
launch
Issue: If the folder you use to store a Call Home executable file has more than one space
between the words “Call” and “Home,” the executable does not launch.
Workaround: Ensure that the folder name has no more than one space between the
words “Call” and “Home.”
Call Home
triggers multiple
e-mails with single
switch event
On some switches running Fabric OS 2.6.2, 3.1.2, or 4.2.0, the Health Status changes before
the Status Reason is populated. An e-mail is triggered because the switch health changes, but the
e-mail contains a blank status reason. When the status reason is populated on the switch
backend, another e-mail is triggered. For Fabric OS 3.1.2 or 4.2.0, you should upgrade to a
version later than 3.1.2x or 4.2.1x to eliminate the problem.
Callhomehistory
log
All qualifying events trigger a Call Home action and the status of each Call Home action is
recorded in the callhomehistory.log. This information is not in the HP StorageWorks
Fabric Manager 5.x administrator guide.
Changing printers
in Fabric
Manager
Issue: If you have multiple printers configured, selecting a non-default printer on the page setup
dialog box in Fabric Manager might crash the Fabric Manager client when you click OK. This
occurs on some Windows hosts.
Workaround: To prevent the Fabric Manager client from crashing, do not change the
printer from the page setup dialog box. Change the printer either from the print dialog
box or change the default printer on Windows and then close and relaunch the Fabric
Manager client. Then print the selected views.
Device tables;
Topology view
If the launch switch is running Fabric OS 2.6.x, proxy devices do not appear in device tables or
in Topology view for any edge fabrics that are importing devices.
End-to-end
monitors between
physical and
imported devices
View Set Monitors: In the view set monitors dialog box, the imported device information is
displayed if the edge fabric from which the device is imported is discovered in Fabric Manager.
In Fabric Manager 4.4, if the edge fabric from which the device is imported is not discovered in
Fabric Manager, the monitor is not displayed in the view set monitors dialog box, even though it
is set in the fabric.
Advanced Performance Monitoring Reports: In the end-to-end performance reports,
switch details for imported devices are not displayed, whether or not the edge fabric
from which the device is imported is discovered in Fabric Manager.