Fabricante : HP Arquivo Tamanho: 226.64 kb Arquivo Nome : Língua de Ensino:

Ir para baixar

The issue arises because either LAN connection on the HAFM appliance 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 at empts to access the HAFM
appliance via a remote client session and is unknowingly using what has been designated as the private
LAN, the remote session is not al owed. The IP address that the HAFM appliance has determined to
be the public LAN which supports remote client access, displays HAFM which displays after selecting
SAN > Server Properties.
HAFM 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 is not guaranteed.
For a dual LAN configuration, both LANs must be connected when the HAFM appliance is booted up. If
only one is connected, HAFM interprets this as a single LAN configuration, and the connected LAN is
designated as the LAN for remote client sessions.
Workaround
There are two ways to ensure the public and private designations of the LANs.
• If you use a private LAN IP address, this causes this LAN to be designated as the private LAN.
You must also have the public LAN connection active when the HAFM appliance is booting up, or
else HAFM interprets this as a single LAN connection configuration, and the 10.x.x.x LAN is
designated as the LAN for remote client sessions.
• You can configure a specified Ethernet interface on the HAFM appliance to be the public LAN (to
listen for remote client connections). To configure this feature, you must manual y edit a file on the
HAFM appliance to explicitly specify which IP address HAFM should use as the public LAN.
For detailed instructions, see HP StorageWorks HA-Fabric Manager User Guide.
If the public LAN IP address of the HAFM appliance is ever changed, this file must be edited again to
reflect the new IP address.
Support for speed Auto-Negotiate
Auto-negotiate is supported. However, HP recommends that the port speed for E_Ports (for Interswitch
links, or ISLs) be set to a specific port speed (1Gb/sec, 2Gb/sec, or 4GB/sec as appropriate for the
speed of the Directors or Edge Switches being connected) instead of to Negotiate. Using a specific
port speed decreases the time for a fabric build in response to some perturbation event in the fabric.
Similarly, set ing a specific port speed for N_Ports also decreases fabric build time. However, setting a
specific port speed for N_Ports is not required.
There are a few older HBA devices that do not always succeed in logging in to a switch port when
the port speed is set for auto-negotiate.
Workaround
If an older HBA has difficulty logging into a switch port that has its port speed configured as Negotiate,
configure that port speed to 1Gb/sec, 2Gb/sec, or 4GB/sec according to the operation speed of the
HBA connected to that port.
Losing LAN connection to the HAFM appliance when logged in to HAFM
If the LAN connection to the HAFM appliance is lost while you are logged in to HAFM, the application
may stop.
Workaround
The LAN connection must be restored. Stopping HAFM has no impact on the Fibre Channel operations
of any Edge Switch or Director. Monitoring switch operations, logging events, and implementing
configuration changes are interrupted only while the LAN is not connected.
14

---

...

Este manual também é adequado para os modelos :
dados de dispositivos de processamento - HP StorageWorks Edge Switch 2/24 (226.64 kb)
dados de dispositivos de processamento - HP StorageWorks Edge Switch 2/32 (226.64 kb)
dados de dispositivos de processamento - McDATA 4Gb SAN Switch (226.64 kb)
dados de dispositivos de processamento - HP StorageWorks Director 2/140 (226.64 kb)

Baixe o seu

Para fazer o download, introduza 2 dígitos :