FW 07.00.00/HAFM SW 08.06.00 HP StorageWorks HA-Fabric Manager User Guide (AA-RS2CF-TE, March 2005)

HAFM overview20
NOTE: Although products can perform normal operations without an HAFM appliance, the HAFM
appliance should operate at all times to monitor product operations, report failures, log event
changes, and log configuration changes.
HAFM application
The application is composed of two parts: the appliance (which runs only on the HAFM appliance)
and the client. The server is installed on one HAFM appliance and stores storage area network
(SAN)-related information; it does not have a user interface. To view SAN information through a
user interface, you must log in to the server running on the appliance through a client.
NOTE: The server and clients may reside on the same machine, or on separate machines.
Client communication
In most configurations, the server calls the client whenever it has new data.
In some cases, a network may utilize virtual private network (VPN) or firewall technology, which
can prohibit communication between the server application running on HAFM appliances and
clients. In this situation, the application automatically detects the network configuration and runs
the client in polling mode. See ”Configuring HAFM through a firewall” on page 169.
Dual LANs on the HAFM appliance
When two LANs are connected at the HAFM appliance, Microsoft Windows and the HAFM
application designate one as the public LAN, and the other as the private LAN.
• The private LAN is for communication between the HAFM appliance and the directors and edge
switches that the HAFM appliance manages.
• The public LAN is for communication between the HAFM appliance and computers seeking
remote client access to the HAFM appliance.
Either LAN connection on the HAFM appliance can be the public LAN or the private LAN. The
directors and edge switches can be managed via either LAN; however, only the public LAN
supports remote client access.
The title bar of the main window of the HAFM application shows the IP address of the public LAN.
Public and private LAN designations
In a dual LAN configuration, both LANs must be connected when the HAFM appliance boots. If
only one is connected, the HAFM appliance interprets this as a single LAN configuration, and the
connected LAN is designated as the public LAN.
The HAFM application designates the public LAN as the first LAN detected whose IP address is not
the reserved private subnet 10.x.x.x. Thus, if neither IP address is 10.x.x.x, the first LAN detected by
the HAFM application is designated as the public LAN. This order of detection is influenced by
Microsoft Windows and not guaranteed.