HP StorageWorks 2/140 FW 05.01.00 and SW 07.02.00 hp StorageWorks HA Fabric Ma - Page 18

Issue Concerning HAFM Remote Client Access to the HAFM Server with Dual LAN Configuration

Get HP StorageWorks 2/140 - Director Switch PDF manuals and user guides View all HP StorageWorks 2/140 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 18 highlights

Known Issues Issue Concerning HAFM Remote Client Access to the HAFM Server with Dual LAN Configuration When using a single public LAN connection at the HAFM server for all Ethernet communications to: ■ Directors and edge switches that the HAFM server manages ■ Computers seeking remote client access to the HAFM server ■ SAN management applications such as hp OpenView SAN Area Manager the single LAN connection operates correctly for all these functions. When using two LAN connections (public and private) at the HAFM server, Microsoft Windows and the HAFM application determine the following: ■ Which LAN is to be the private LAN for communication between the HAFM server, and the directors and edge switches that the HAFM server manages. ■ Which LAN is to be the public LAN for communication between the HAFM server and computers seeking remote client access to the HAFM server. The issue arises because either LAN connection on the HAFM server can be the public LAN or the private LAN. Though the directors and edge switches can be managed via either LAN, the public LAN is the only one that can support remote client access. Thus, if one attempts to access the HAFM server via a remote client session and is unknowingly using what has been designated as the private LAN, the remote session will not be allowed. The IP address that the HAFM server has determined to be the public LAN which supports remote client access, displays in the title bar of the main window of the HAFM application which displays after logging into the HAFM application. 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 HAFM is designated as the public LAN. This order of detection is influenced by Microsoft Windows and not guaranteed. For a dual LAN configuration, both LANs must be connected when the HAFM server is booted up. If only one is connected, the HAFM server interprets this as a single LAN configuration, and the connected LAN will be designated as the LAN for remote client sessions. 18 HA-Fabric Manager Release Notes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
Known Issues
18
HA-Fabric Manager Release Notes
Issue Concerning HAFM Remote Client Access to the HAFM Server with
Dual LAN Configuration
When using a single public LAN connection at the HAFM server for all Ethernet
communications to:
■
Directors and edge switches that the HAFM server manages
■
Computers seeking remote client access to the HAFM server
■
SAN management applications such as hp OpenView SAN Area Manager
the single LAN connection operates correctly for all these functions.
When using two LAN connections (public and private) at the HAFM server,
Microsoft Windows and the
HAFM
application determine the following:
■
Which LAN is to be the private LAN for communication between the HAFM
server, and the directors and edge switches that the HAFM server manages.
■
Which LAN is to be the public LAN for communication between the HAFM
server and computers seeking remote client access to the HAFM server.
The issue arises because either LAN connection on the HAFM server can be the
public LAN or the private LAN. Though the directors and edge switches can be
managed via either LAN, the public LAN is the only one that can support remote
client access. Thus, if one attempts to access the HAFM server via a remote client
session and is unknowingly using what has been designated as the private LAN,
the remote session will not be allowed. The IP address that the HAFM server has
determined to be the public LAN which supports remote client access, displays in
the title bar of the main window of the
HAFM
application which displays after
logging into the
HAFM
application.
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 HAFM is designated as the
public LAN. This order of detection is influenced by Microsoft Windows and not
guaranteed.
For a dual LAN configuration, both LANs must be connected when the HAFM
server is booted up. If only one is connected, the HAFM server interprets this as a
single LAN configuration, and the connected LAN will be designated as the LAN
for remote client sessions.