HP StorageWorks HA-Fabric Manager Release Notes, V08.09.01 (AA-RUR6J-TE, October 2006)

ManualsBrandsHP ManualsSoftwareHP HA Fabric Manager Software Upgrade Kit

Effect of no LAN c

onnection to HAFM appliance during boot up

If the H A FM appli

ance has no LAN connection while b ooting up, but it is connected after booting up, the

remote client sessions to the HA FM 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 o perations of a ny switch or Director. O nly monitoring switch

operations, logg ing events, and implementing conﬁguration changes are interrupted.

Setting HAF M a

ppliance LAN to use DHCP is activated to wrong LAN

When setting t

he IP conﬁguration for an older HAFM appliance (delivered with HAFM server b oot/restore

3.01.00 Rev A

or ea rlier) using the LCD panel, setting DH CP conﬁguration for LAN 1 causes LAN 2,

not LAN 1, to b

econﬁgured for DHC P. Similarly, setting DHCP conﬁguration for LAN 2 causes LAN 1,

not LAN 2, to

be conﬁgured for DHCP.

Workaround

To conﬁgure LAN 1 for DHCP, select LAN 2 instead of LAN 1 at the start of the conﬁguration procedure.

If you wish to con ﬁgure LAN 2 for DHCP, select LAN 1 instead of LAN 2 at the start of the conﬁguration

procedure.

New sound ﬁles are not added to Event Manager immediately

New sound ﬁles do not display in the pull down menu of the Event Manager. They cannot b e selected for

inclusioninarule.Inorderforthenewsoundﬁles 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

monitori

ng 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 11.0 kernel parameters are set too low for most Java applications. Usually

you will see this problem as a java.lang.OutOf MemoryError: unable to create new

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 tha n the expected maximum number of simultaneously active

threads. Themaximumvalueisthevalueofnkthread.

• nkthread—The total number of kernel threads available in the system. This parameter is similar

to the nproc tunable except that it deﬁnes 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 e ach 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

enco

unters problems, the following may occur:

• There is an apparent loss of communication to switches being managed by HAFM.

• The appliance CPU usage and memor y usage display abnormally high readings.

HA-Fabric Manager release notes