HP Deskjet 812c Instruction Manual

HP StorageWorks B-series Data Center
Fabric Manager Enterprise
V10.1.4 release notes
Part number: 5697-0085
First edition: July 2009

Legal and notice information
© Copyright 2009 Hewlett-Packard Development Company, L.P.
© Copyright 2009 Brocade Communications Systems, Incorporated.

Version
10.1.4
Effective date
July 2009
Description
HP StorageWorks B-series Data Center Fabric Manager (DCFM) is HP's next-generation fabric
management application and the successor to its legacy fabric management application, HP
StorageWorks Fabric Manager (FM).
DCFM 10.1.0 integrated the following features:
•HP StorageWorks DC04 SAN Director added as a new hardware platform
•New software features:
• Virtual Fabrics
• Port Fencing support for B-series hardware
•Enhancements to existing features:
• Performance Management:
• Top Talkers support
• Additional FCIP statistics
• FICON Management:
• Enhancements to PDCM to support Port Groups
• Cascaded FICON Merge Wizard (various options to resolve failures)
• Request Node Identification (RNID) support for M-series hardware
•Pathinfo support for Fibre Channel Routing (FCR) links
• Zoning enhancements, such as removing or replacing offline devices, and TI zone support for
Virtual Fabrics
• Technical Support Data and Firmware Download with support for SCP
DCFM 10.1.2 added support for the B-series Encryption SAN Switch and B-series Encryption Blade.
DCFM 10.1.4 adds support for the following:
•Call Home for HP StorageWorks 2408 FCoE Converged Network Switches
•SNMP traps for HP StorageWorks 2408 FCoE Converged Network Switches
Update recommendation HP recommends that you upgrade to DCFM 10.1.4 to benefit from the
fixes included in this release.
HP StorageWorks B-series Data Center Fabric Manager Enterprise 3

IMPORTANT:
DCFM 10.1.2 or later is required in order to manage the B-series Encryption products with DCFM.
Existing EFCM and FM customers with valid licenses and maintenance contracts that have not already
migrated to DCFM are encouraged to do so. The migration path is from EFCM 9.6. x or 9.7. x direct
to DCFM 10.1.4, or from FM 5.4. x or 5.5. x direct to DCFM 10.1.4.
NOTE:
New B-series switches introduced by HP will be supported in DCFM only (no support will be provided
in EFCM or FM).
Supported switches and firmware
Table 1 lists versions of firmware and associated switches supported by this DCFM release. This does
not imply that all firmware versions listed in the left column are still supported by HP, but rather that
those are the firmware streams on which the corresponding switches are, or were, supported. It also
does not imply that all the listed firmware streams are supported on each of the corresponding switches.
HP recommends using the latest software versions to get the greatest benefit from the SAN.
4

Table 1 Supported switches and firmware
Switch/DirectorSwitch firmware
HP StorageWorks SAN Switch 2/32 (Brocade 3900)
HP StorageWorks SAN Switch 2/8V (Brocade 3250)
HP StorageWorks SAN Switch 2/16V (Brocade 3850
HP StorageWorks SAN Switch 4/32 (Brocade 4100)
HP StorageWorks 400 Multi-Protocol Router (Brocade 7500)1
HP StorageWorks 4/8, 4/16 SAN Switch (Brocade 200E)
HP StorageWorks SAN Switch 4/64 (Brocade 4900)2
HP StorageWorks SAN Switch 4/32B (Brocade 5000)3
HP StorageWorks 8/8, 8/24 SAN Switch (Brocade 300)4
HP StorageWorks 8/40 SAN Switch (Brocade 5100)4
HP StorageWorks 8/80 SAN Switch (Brocade 5300)4
HP StorageWorks Core Switch 2/64 (Brocade 12000)
HP StorageWorks SAN Director 2/128 (Brocade 24000)
HP StorageWorks 4/256 SAN Director (Brocade 48000)
•HP StorageWorks 4/256 SAN Director 16 Port 4Gb Blade (FC4-16)
•HP StorageWorks 4/256 SAN Director 32 Port 4Gb Blade (FC4-32)
•HP StorageWorks 4/256 SAN Director 48 Port 4Gb Blade (FC4-48)2
•HP StorageWorks iSCSI Director Blade (FC4-16IP)2
•HP StorageWorks Multi-Protocol Router Blade (FR4-18i)1
•HP StorageWorks SAN Director 6 Port 10Gb FC ISL Blade (FC10-6)5
HP StorageWorks DC SAN Backbone Director (Brocade DCX)6
•HP StorageWorks DC SAN Director 16 Port 8Gb FC Blade (FC8-16)
•HP StorageWorks DC SAN Director 32 Port 8Gb FC Blade (FC8-32)
•HP StorageWorks DC SAN Director 48 Port 8Gb FC Blade (FC8-48)
•HP StorageWorks Multi-Protocol Router Blade (FR4-18i)
•HP StorageWorks DC SAN Director 6 Port 10Gb FC ISL Blade (FC10-6)
•HP DC Switch Encryption FC Blade
HP StorageWorks Encryption SAN Switch
HP StorageWorks DC04 SAN Director (Brocade DCX-4S) 7
•HP StorageWorks DC SAN Director 16 Port 8Gb FC Blade (FC8-16)
•HP StorageWorks DC SAN Director 32 Port 8Gb FC Blade (FC8-32)
•HP StorageWorks DC SAN Director 48 Port 8Gb FC Blade (FC8-48)
•HP StorageWorks Multi-Protocol Router Blade (FR4-18i)
•HP StorageWorks DC SAN Director 6 Port 10Gb FC ISL Blade (FC10-6)
•HP DC Switch Encryption FC Blade
HP StorageWorks 2408 FCoE Converged Network Switch8
FOS 5.0.x, 5.1.x, 5.2.x, 5.3.x,
6.0.x, 6.1.x, and 6.2.x
Brocade 4Gb SAN Switch for HP c-Class BladeSystem (Brocade 4024)9
Brocade 4Gb SAN Switch for HP p-Class BladeSystem (Brocade 4012)
HP StorageWorks EVA4400 Embedded Switch Module (Brocade 5410)10
Brocade 8Gb SAN Switch for HP BladeSystem c-Class (Brocade 5480)11
FOS 5.2.x, 5.3.x, 6.0.x, 6.1.x,
and 6.2.x
HP StorageWorks B-series Data Center Fabric Manager Enterprise 5

Switch/DirectorSwitch firmware
HP StorageWorks Director 2/64, 2/140 (Brocade M6064 and M6140)
HP StorageWorks Edge Switch 2/16 (Sphereon 3216)
HP StorageWorks Edge Switch 2/32 (Sphereon 3232)
HP StorageWorks Edge Switch 2/12 (Sphereon 4300)
Sphereon 4400 (Brocade 4400)
Sphereon 4700 (Brocade 4700)
M-EOSc 9.6.x, 9.7.x, 9.8x,
and 9.9
Intrepid 10000 Director (Brocade Mi10K)M-EOSn 9.6.x, 9.7.x, 9.8.x,
and 9.9
1Requires FOS V5.1.0 or later
2Requires FOS V5.2.0 or later
3Requires FOS V5.2.1b or later
4Requires FOS V6.1.0a or later
5Requires FOS V5.3.0 or later
6Requires FOS V6.0.0b or later
7Requires FOS V6.2.0a or later
8Requires FOS V6.1.2_cee1 or later. Support for this switch in DCFM V10.1.xis for discovery only.
9Requires FOS V5.3.1 or later
10Requires FOS V6.1.0_8e or later
11Requires FOS V6.1.0_8e1 or later
Supported operating systems
DCFM 10.1.xis supported on the operating systems listed in Table 2.
Table 2 Supported operating systems
VersionsOperating system
•XP Professional SP2, SP3, (x86 32-bit)
•2003 Server SP2 (x86 32-bit)
•Vista Business Edition (x86 32-bit)
•2008 Server (x86 32-bit)
Windows
10 (SPARC-platform)Solaris
•Red Hat AS 4.0 (x86 32-bit)
•Red Hat Enterprise Linux 5 Advanced (x86 32-bit)
•SUSE Linux Enterprise Server 10 SP1 (x86 32-bit)
Linux
Important notes
This section lists information that you should consider before you use DCFM V10.1.x. See the Data
Center Fabric Manager Enterprise User Manual for full details on the following notes. This document
can be downloaded from the following HP website:
http://h18006.www1.hp.com/products/storageworks/dc_fabricmgr/index.html
Under Support, click Support for your product, and then click Manuals.
6

NOTE:
Be sure to install the DCFM application on a dedicated machine that is not running any other server
applications, such as another database server.
Using M-EOSc switches with SNMPv3 enabled
DCFM 10.1.3 or later does not support managing M-EOSc switches with SNMPv3 enabled. If SNMPv3
is enabled on M-EOSc switches, SNMPv1 is automatically disabled. DCFM 10.1.3 or later uses
SNMPv1 to manage M-EOSc switches; therefore, the manageability link cannot be established if
SNMPv3 is enabled. HP recommends that you disable SNMPv3 using the CLI.
Remote Client fails to launch with Web Start Exception
Not running JRE 1.6.0 Update5 can cause a known issue where the remote client fails to launch. This
JRE version is bundled with the DCFM Server. If your system does not already have JRE 1.6.0, when
launching the remote client the browser will have a link to download the JRE installer. If your system
already contains JRE 1.6.0, you must run 1.6.0 Update5. This can be validated by running java
–version from the command prompt. If the version displays as 1.6.0_05, you are running the
correct version. If it is not the correct version, remove the incorrect version and point your web browser
to the DCFM Server IP address to download the correct version.
NOTE:
If you installed JRE 1.6.0 Update5, do not use Java’s auto-updater, as this will change the JRE version.
Incorrect error message displayed when FCIP license is missing
If a switch without a FCIP license is selected when creating a FCIP tunnel, the following error message
is displayed:
The switch does not have any free tunnels.
This error message is displayed instead of:
The switch does not have a FCIP license.
VEX_Port not disabled after FICON parameter values added
VEX_Port is not disabled after you enter FICON parameters in advanced settings in the FCIP
configuration wizard.
User action and product audit events not generated from port fencing actions
When port fencing policies are assigned to M-EOS switches in a mixed fabric, user action and product
audit events are not generated. User action events are not generated when unassigning a policy from
a M-EOS switch.
Incorrect information is listed in Compare or Merge dialog
If multiple zones are defined in a single zone configuration, the Host-to-Storage and Storage-to-Host
information will be listed incorrectly in the Compare/Merge dialog.
HP StorageWorks B-series Data Center Fabric Manager Enterprise 7

DCFM Pro services do not auto-start on Linux and Solaris
After a restart, DCFM Pro services need to be manually started on both Linux and Solaris. Until Pro
services are started, the DCFM client will fail to launch.
FC Address field displays incorrect in the Port Connectivity View
The FC address is listed incorrectly when using the Port Connectivity View. The correct FC address is
available in the Properties dialog.
Duplicate entries in Call Home notification for M-model switches
With Virtual Fabrics enabled, the Call Home notification dialog displays duplicate entries for M-model
switches.
Event priority mismatch
Error-level policies can occasionally be triggered by warning-level events.
Remote Client unable to be launched using web browser on Windows systems
If the administrator password is changed from the client and then the client is re-launched from a web
browser, the client may fail to launch.
Error when opening Zoning dialog with no message
When a user with read-only permissions for Zoning Offline launches the Zoning dialog, an error
message with no text is displayed. Add the Read-Only Zoning Online permission to the user role in
order to not see the error message dialog box.
Configdownload fails for Firmware and ALL parameters
When Configdownload is attempted from one virtual switch to another virtual switch when the
Fabric IDs are not identical and the Firmware and ALL parameters are selected, the download will
fail.
Switch name update delay
When changing the name of a switch from outside of DCFM, the new name for the switch does not
appear within DCFM for up to 15 minutes depending on SAN Size selection.
Incorrect message shown in Master Log for end-to-end monitors
Messages in the Master Log are incorrectly generated when the end-to-end monitors dialog is opened
and closed without modification, or when an end-to-end pair creation fails.
Element manager fails to launch on i10k
If the admin partition (partition 0) is removed and then reattached to a managed fabric, the element
manager no longer launches from DCFM until the DCFM services are restarted.
Tunnel ports shown instead of GigE ports
In the topology view, tunnel ports are shown instead of Gigabit Ethernet ports.
8

Deleting Logical Switches with GigE ports causes errors
When deleting a Logical Switch that has Gigabit Ethernet ports without first moving the GigE ports
to the default Logical Switch, an error message may be displayed and the delete fails.
Blank graph displayed for FCIP tunnels
When FCIP tunnels are selected from the Picker dialog in the Historical Graph, the tunnels will initially
appear as blank until the Apply button in the dialog is clicked.
Domain port index and port WWNs unavailable in Add Member dialog
The port index and port WWNs are grayed out when using the Add Member dialog. The port index
can still be selected by choosing the appropriate devices in the device tree and then moving them to
the right.
Event-based file actions fail
DCFM event actions fails to run scripts on Windows remote-mounted filesystems.
EX_Port disabled when configuring Routing Domain IDs
After selecting an edge fabric and launching the routing domain IDs dialog, if you select all of the
front domains and Xlate domains and then add appropriate domain IDs, clicking OK disables the
EX_Ports with the following message:
EX_PORT ISOLATE
E_Port information missing in EOS edge switch
When opening a graph of an E_Port to EX_Port connection, the E_Port labels are blank but the data
graphed is corrected.
Access Gateways connected to M-EOS switches not discovered
Access Gateways connected to M-EOS fabrics are not discovered by DCFM. Only Access Gateways
attached to FOS-based switches are currently able to be discovered.
Incorrect title of Top Talkers dialog
When the Top Talkers dialog is selected, the title incorrectly displays as “Realtime Port Selector.”
WWNs not shown in Fabric Binding dialog
After two FOS fabrics in interop mode 0 are merged, the member's WWN is missing and the Fabric
Binding Status is listed as Unknown in the Fabric Binding dialog.
SNMP trap registration
If the discovery status displays the message Not registered for SNMP Trap, manually add
the server IP entry in the SNMP trap registration table from the switch CLI using the following command:
snmpconfig --set snmpv3
HP StorageWorks B-series Data Center Fabric Manager Enterprise 9

FCIP/GigE Performance Graphs
If there are no FCIP/GigE performance graphs shown for a switch, verify that the server IP address
is properly registered in the SNMP trap registration table. To verify the IP address, enter the CLI
command snmpconfig --show snmpv3 and verify that the SNMPv3 credentials exactly match
the SNMPv3 user that the DCFM server is registered with for traps.
Management of M-series/McDATA switches requires a B-series switch
DCFM management accesses the switches through one B-series switch in each fabric. To use DCFM
to manage M-series or McDATA switches, at least one B-series switch must be connected to the fabric.
At this time, only the HP StorageWorks 4/256 SAN Director (Brocade 48000) and HP StorageWorks
DC SAN Backbone Director (Brocade DCX) are supported for interoperability with M-series switches.
For the latest support information, see the HP StorageWorks Fabric interoperability: Merging fabrics
based on M-series and B-series Fibre Channel switches application note at http://spock.corp.hp.com/
Pages.internal/spock2Html.aspx?htmlFile=an_fabric_interoperability.internal.html.
Removing switches
If you plan to segment and remove more than two switches from a fabric and you have historical
performance collection enabled, HP recommends that you accept changes after each switch
segmentation from the client.
DCFM clients
To free up server resources and as best practice, HP recommends that you shut down clients that are
not actively used. In some scenarios, if duplicate entries are displayed in the Product List, restart the
client.
Secure FOS fabrics cannot be discovered from DCFM
DCFM does not support Secure FOS (SFOS). If you attempt to discover an SFOS fabric, DCFM displays
the message Discovery Failed. To recover, you must remove the SFOS settings and set normal
fabric settings.
Performance Data Aging tab has been removed from Server Management
Console
You cannot configure the Performance Data Aging settings in DCFM 10.1.4. The tab has been removed
from Server Management Console (SMC). The default configuration settings are as follows:
•288 samples in a 5-minute period (1 day)
•144 samples in a 30-minute period (3 days)
•84 samples in a 2-hour period (1 week)
•90 samples in a 1-day period (3 months)
•606 total samples
When migrating from an earlier release to DCFM 10.1.4, all historical data will be truncated with
respect to the default samples, and the aging configuration will not be migrated.
SNMPv3 credentials for FOS switches when migrating from EFCM
When migrating from EFCM to DCFM, the SNMPv3 credentials for the FOS switches are incorrectly
assigned to the user ID (Discovery Dialog > IP Address tab > User ID). You must clear the user ID
manually before you can discover and manage the FOS switches.
10