- ページ 22

スイッチ HP 316095-B21 - StorageWorks Edge Switch 2/24のPDF リリースノートをオンラインで閲覧またはダウンロードできます。HP 316095-B21 - StorageWorks Edge Switch 2/24 23 ページ。 Edge switch release notes
HP 316095-B21 - StorageWorks Edge Switch 2/24 にも： 更新マニュアル (9 ページ), マニュアル (41 ページ), マニュアル (40 ページ), リリースノート (32 ページ), リリースノート (27 ページ), マニュアル (26 ページ), リリースノート (27 ページ), リリースノート (25 ページ), 取付説明書 (24 ページ), リリースノート (23 ページ), リリースノート (22 ページ), リリースノート (23 ページ), リリースノート (19 ページ), リリースノート (19 ページ), リリースノート (18 ページ), 取扱説明書 (17 ページ), リリースノート (17 ページ), アップグレード手順 (16 ページ), 取扱説明書 (16 ページ), 取付説明書 (16 ページ), リリースノート (16 ページ), リリースノート (17 ページ), リリースノート (17 ページ), リリースノート (11 ページ)

ページを印刷する
HP 316095-B21 - StorageWorks Edge Switch 2/24 リリースノート
About this document
Show Route port numbers are not always displayed
When the Show Route feature is enabled, the In Port # and Out Port #
information is not available on a Loop Device.
Wrong number of devices is displayed in the Create View dialog box
In the Create View dialog box, the number of devices in the fabric is displayed
incorrectly. Both offline and online devices are included in the count. Only online
devices should be counted.
Reporting function in Event Management may not be accurate
In some cases the Reporting function does not give accurate information about an
active SAN and HP strongly advises that you verify information after generating a
report. The Reporting function primarily has issues with the Fabric Ports Report,
where some ports are not listed or duplicate ports are listed.
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:
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.
22
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.
HP StorageWorks HA-Fabric Manager release notes