HP StorageWorks 2/140 FW 07.01.02/HAFM SW 08.06.00 HP StorageWorks HA-Fabric M - Page 31

HP-UX parameters may need to be changed before you run the HAFM client

Page 31 highlights

Workaround When a switch has been added to HAFM for management, or firmware has been upgraded, observe the switch being shown as discovered by HAFM. Check the event log of the switch to ensure there were no faults that occurred during the short time when HAFM was in the process of discovering the switch. 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 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 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. Client HAFM Login dialog box is not displayed after logging out In some cases, when the client has logged out, the Log In dialog box is not displayed. If you get inconsistent behavior or an error message, restart the client. SAN data is not affected when you restart the client. HAFM appliance may shut down following a firmware download The HAFM appliance may shut down following a firmware download. If this occurs, you have to restart the HAFM appliance to recover. This is an issue with Java Virtual Machine 1.3.1_07, which is used in the application. This is only an issue when running firmware 06.00.01 or earlier. HA-Fabric Manager release notes 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32

Workaround
When a switch has been added to HAFM for management, or
rmware has been
upgraded, observe the switch being shown as discovered by HAFM. Check the event
log of the switch to ensure there were no faults that occurred during the short time when
HAFM was in the process of discovering the switch.
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 be selected for inclusion in a rule. In order for the new sound
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 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 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 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 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 each
running process uses many threads, you should increase this value.
Client HAFM Login dialog box is not displayed after logging out
In some cases, when the client has logged out, the Log In dialog box is not displayed.
If you get inconsistent behavior or an error message, restart the client. SAN data is
not affected when you restart the client.
HAFM appliance may shut down following a
rmware download
The HAFM appliance may shut down following a
rmware download. If this occurs,
you have to restart the HAFM appliance to recover. This is an issue with Java Virtual
Machine 1.3.1_07, which is used in the application. This is only an issue when running
rmware 06.00.01 or earlier.
HA-Fabric Manager release notes
29