HP Storage SAN Visibility 6.0 release notes

• In case of host discovery and data collection, collecting data from the host where HP Storage
SAN Visibility 6.0 is installed may not collect HBA related data always. For such host, the
processed report may not have completed the compatibility analysis.
To resolve this issue, HP Storage SAN Visibility 6.0 tool can be installed on a different host,
and then the host under question can be targeted for discovery and data collection.
• Reports generated from HP Storage SAN Visibility 5.1 or earlier, may have all the components
under "Incomplete Data" in "Compatibility Analysis" link.
• In the HP Storage SAN Visibility processed report in Excel format, you may observe formatting
issues on data entries in cells in the ‘Recommendations’ sheet. The text may not be clearly
visible since the cell width is not proportional to the cell’s content, though the data is present,
and can be viewed by clicking on the cell. If this issue is seen, as a workaround, select HTML
as the report format during the data collection.
Limitations
Following are the limitations in this release of SAN Visibility:
• Host discovery and data collection with Internet Protocol version 6 (IPv6) is not supported on
non- Windows OS.
• For physical and virtual hosts, only the mandatory details are displayed in the report.
The mandatory details of physical hosts are:
◦ IP Address
◦ Type of host
◦ OS Information
◦ Host name
◦ Unique ID
◦ HBA Port WWN
The mandatory details of virtual hosts are:
ESX
◦ vmName
◦ vm OSInformation
◦ vm uuid
HyperV
◦ vmName
◦ vm uuid
• SAN Visibility does not support explicit data collection from Cisco N_Port Virtualization (NPV)
mode switches and from HP 4Gb Virtual Connect Fibre Channel (VC-FC) module switches.
However, SAN Visibility can identify NPIV created by Cisco NPV and HP VC-FC mode switches
in a normal NPIV enabled FC switch.
• Brocade switches running FOS6.2.0a may show improper NPIV device information from the
name server which may result SAN Visibility to incorrectly identify the physical and virtual
HBAs. In such cases, the workaround is to collect data using SMI-S.
• Cisco FCoE switches at times may display incorrect Gateway IP address in the processed SAN
Visibility report.
Limitations 7