HP StorageWorks 2/140 fw 04.01.02 and sw 06.03.01 ha-fabric manager release no - Page 10

Effect of No LAN Connection to HAFM Server During Boot Up, HP-UX - Potential Conflict Between

Get HP StorageWorks 2/140 - Director Switch PDF manuals and user guides View all HP StorageWorks 2/140 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 10 highlights

Known Issues Effect of No LAN Connection to HAFM Server During Boot Up If the HAFM server has no LAN connection while booting up, but is connected after booting up, the IP address that appears in the HAFM Product View window title bar may be incorrect. Workaround This can be corrected by exiting out of HAFM application, restarting the HAFM application, and logging back in. HP-UX - Potential Conflict Between Command View and ioscan There is an issue involving a conflict between the Command View host agent and the UNIX command ioscan. When this conflict is encountered, ioscan may erroneously report that storage LUNs have been lost (ioscan output results in report of "NO_HW"). There is no actual impact on any of the servers, storage, or any fibre channel data transfers. When encountered, re-running ioscan after a short time will yield correct results. The OpenView Storage Area Manager (OVSAM) Command View Host agent on HP-UX has a discovery agent (diald) which periodically checks the system for new I/O devices including HBAs. The default polling cycle is 19 minutes but is user configurable from 1 minute to 24 hours. The Command View products use this host agent component for discovery of XP and VA arrays. Workaround On a stable system after the diald software has run for a few cycles the discovery information will remain unchanged. In order to minimize the opportunity for this conflict to occur with any programs using ioscan, you can modify the polling period to a larger value. To do this, the entry "DIAL_DISCOVERY_DELAY" in the file /opt/sanmgr/hostagent/config/dial.cfg should be changed. The polling period value should be specified in minutes, e.g. a value of 60 would result in a 1 hour discovery poll cycle. The polling period value should be modified considering the time and frequency that ioscans are being run, in order to avoid diald and ioscan being executed simultaneously. This issue will be corrected in the next release of director and edge switch firmware. 10 HA-Fabric Manager Release Notes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
Known Issues
10
HA-Fabric Manager Release Notes
Effect of No LAN Connection to HAFM Server During Boot Up
If the HAFM server has no LAN connection while booting up, but is connected
after booting up, the IP address that appears in the HAFM Product View window
title bar may be incorrect.
Workaround
This can be corrected by exiting out of
HAFM
application, restarting the
HAFM
application, and logging back in.
HP-UX - Potential Conflict Between Command View and ioscan
There is an issue involving a conflict between the Command View host agent and
the UNIX command ioscan. When this conflict is encountered, ioscan may
erroneously report that storage LUNs have been lost (ioscan output results in
report of “NO_HW”). There is no actual impact on any of the servers, storage, or
any fibre channel data transfers. When encountered, re-running ioscan after a
short time will yield correct results.
The OpenView Storage Area Manager (OVSAM) Command View Host agent on
HP-UX has a discovery agent (diald) which periodically checks the system for
new I/O devices including HBAs. The default polling cycle is 19 minutes but is
user configurable from 1 minute to 24 hours. The Command View products use
this host agent component for discovery of XP and VA arrays.
Workaround
On a stable system after the diald software has run for a few cycles the discovery
information will remain unchanged. In order to minimize the opportunity for this
conflict to occur with any programs using ioscan, you can modify the polling
period to a larger value. To do this, the entry
“DIAL_DISCOVERY_DELAY”
in the file
/opt/sanmgr/hostagent/config/dial.cfg
should be changed. The polling period value should be specified in minutes, e.g. a
value of 60 would result in a 1 hour discovery poll cycle. The polling period value
should be modified considering the time and frequency that ioscans are being run,
in order to avoid diald and ioscan being executed simultaneously.
This issue will be corrected in the next release of director and edge switch
firmware.