HP 316095-B21 - StorageWorks Edge Switch 2/24 Release Note page 15

Effect of no LAN connection to HAFM appliance during boot up
If the HAFM appliance has no LAN connection while booting up, but it is connected after booting up, the
remote client sessions to the HAFM appliance are not allowed. Also, the IP address that is displayed
when you select SAN > Server Properties is possibly incorrect.
Workaround
This is corrected by restoring the LAN connection and rebooting the appliance. Rebooting the appliance
has no impact on the Fibre Channel operations of any switch or Director. Only monitoring switch
operations, logging events, and implementing configuration changes are interrupted.
Setting HAFM appliance LAN to use DHCP is activated to wrong LAN
When setting the IP configuration for an older HAFM appliance (delivered with HAFM server boot/restore
3.01.00 Rev A or earlier) using the LCD panel, setting DHCP configuration for LAN 1 causes LAN 2,
not LAN 1, to be configured for DHCP. Similarly, setting DHCP configuration for LAN 2 causes LAN 1,
not LAN 2, to be configured for DHCP.
Workaround
To configure LAN 1 for DHCP, select LAN 2 instead of LAN 1 at the start of the configuration procedure.
If you wish to configure LAN 2 for DHCP, select LAN 1 instead of LAN 2 at the start of the configuration
procedure.
New sound files are not added to Event Manager immediately
New sound files do not display in the pull down menu of the Event Manager. They cannot be selected for
inclusion in a rule. In order for the new sound files to be available, HAFM services must be stopped and
restarted, or the HAFM appliance must be rebooted. This is not disruptive to managed switches, but
monitoring and logging functions are interrupted while the appliance is rebooting.
HP-UX parameters may need to be changed before you run the HAFM client
The following two HP-UX 1 1.0 kernel parameters are set too low for most Java applications. Usually
you will see this problem as a java.lang.OutOf MemoryError:
native thread error. To resolve the issue, edit the following parameter limits:
• max_thread_proc—The maximum number of threads allowed in each process. The minimum
value (and default) is 64, which is often too low for most Java applications. Set the value of
the max_thread_proc higher than the expected maximum number of simultaneously active
threads. The maximum value is the value of nkthread.
• nkthread—The total number of kernel threads available in the system. This parameter is similar
to the nproc tunable except that it defines the limit for the total number of kernel threads
able to run simultaneously in the system. The value must be greater than nproc. The default is
approximately twice that of nproc. The maximum is 30000. The suggested value of nkthread
is 2*max_thread_proc. If you have many Java processes running and each running process
uses many threads, you should increase this value.
Ethernet port on HAFM appliance may encounter problems
When you use TightVNC to access the HAFM appliance and you are running HAFM locally on the
HAFM appliance, the Ethernet port on the HAFM appliance can appear to hang. When the Ethernet port
encounters problems, the following may occur:
• There is an apparent loss of communication to switches being managed by HAFM.
• The appliance CPU usage and memory usage display abnormally high readings.
unable to create new
HA-Fabric Manager release notes
15