EMC Powerpath 300 002 908

EMC PowerPath
for Solaris
Version 4.5.0
Release Notes
P/N 300-002-908
Rev A02
June 2, 2006
These release notes contain supplemental information about EMC

PowerPath, version 4.5.0. Topics include:
◆ Product Description ............................................................................. 2
◆ New Features and Changes ................................................................ 2
◆ Fixed Problems ..................................................................................... 3
◆ Environment and System Requirements .......................................... 4
◆ Known Problems and Limitations ................................................... 14
◆ Technical Notes ................................................................................... 25
◆ Documentation ................................................................................... 33
◆ Software Media, Organization, and Files........................................ 34
◆ Installation ........................................................................................... 34
◆ Troubleshooting and Getting Help .................................................. 35
1
Product Description
Product Description
EMC® PowerPath® software is a server-resident, performance and
application availability enhancing software solution. PowerPath
combines multiple path I/O capabilities, automatic load balancing,
and path failover functions into one integrated package. PowerPath
supports servers, including cluster servers, connected to EMC
Symmetrix®, EMC CLARiiON®, IBM ESS, Hitachi Lightning, Hitachi
TagmaStore, HP StorageWorks xp, EVA, EMA, and MA storage
systems. PowerPath supports Fibre Channel for both switched fabric
and arbitrated loop environments.
New Features and Changes

PowerPath 4.5.0 for Solaris adds support for the following new and
enhanced features:
◆ EMC Invista™ network storage virtualization
Note: PowerPath 4.5.0 supports EMC Invista devices. A new class,

INVISTA, lets you manage Invista devices using the powermt utility.
Refer to the PowerPath 4.5 Product Guide for more information.
◆ Hitachi TagmaStore storage systems
Note: The existing HITACHI class lets you manage Hitachi TagmaStore
devices using the powermt utility. Refer to the PowerPath 4.5 Product
Guide for more information.
◆ HP StorageWorks XP12000 storage systems
Note: The existing HPXP class lets you manage HP StorageWorks

XP12000 devices using the powermt utility. Refer to the PowerPath 4.5
Product Guide for more information.
Discontinued Features in PowerPath

This section includes information about discontinued features in
PowerPath.
EMC HighRoad Please be aware that the next release of PowerPath (post-4.5) will not
include intrinsic disk protection for EMC HighRoad® disks on
Symmetrix storage systems. This is a change from PowerPath 4.5 and
2 EMC PowerPath for Solaris Version 4.5.0 Release Notes

Fixed Problems
earlier, in which disk protection for HighRoad disks is included in the

PowerPath software. Effective with HighRoad version 4.0, disk
protection for Symmetrix is included in the HighRoad software. If
you are using PowerPath 4.5 or earlier with HighRoad 4.0 or earlier,
you do not need to take any action at this time. In the future, if you
want to upgrade to a version of PowerPath later than 4.5 (and you
have HighRoad 3.2 or earlier), you will need to upgrade first to
HighRoad version 4.0 or later before upgrading PowerPath.
End-of-Life CLARiiON FC4700

Announcement As of PowerPath 4.5.0, EMC announced end-of-life (EOL) for
CLARiiON FC4700 support. Effective with the release of PowerPath
4.5.0 for Solaris, PowerPath will no longer support CLARiiON
FC4700 storage systems.
PowerPath Volume Manager

Please be aware that EMC has announced end-of-life (EOL) for
PowerPath Volume Manager (PPVM) functionality for Solaris, AIX
and HP-UX environments. This is effective with the release of
PowerPath 4.4 for Solaris in March 2005, the PowerPath 4.4 for AIX
release, and PowerPath 4.5 for HP-UX.
EMC has also announced its intention to end-of-service-life PPVM
functionality for Solaris, AIX and HP-UX effective March 2006.
Therefore, if you have any data on PPVM volumes, back up that data
and destroy all PPVM volume groups before installing PowerPath
4.4.0 or 4.5.0.
Fixed Problems
The following table shows resolved problems that were reported as
known problems in earlier versions of PowerPath for Solaris.
Table 1 Resolved Problems in PowerPath Version 4.5.0: Solaris
Found in Resolved
Description Version in Version
223401 4.4.0 4.5.0

A PowerPath installation overwrites and changes host semaphore settings on Solaris servers.
This is a remnant of PowerPath Volume Manager, for which end-of-life notification was announced with
the release of PowerPath 4.4.0.
EMC PowerPath for Solaris Version 4.5.0 Release Notes 3

Environment and System Requirements
Table 1 Resolved Problems in PowerPath Version 4.5.0: Solaris (continued)
Found in Resolved
Description Version in Version
205579 4.4.0 4.5.0

After a double fault (for example, pulling two disks of out a RAID1 device) on a CLARiiON LUN, all other
LUNs on the array show dead paths.
186233 4.3.0 4.4.0

In pre-4.3 releases, powermt does not handle CLARiiON LUN names containing colons properly. In
those earlier releases, powermt truncates CLARiiON LUN names at the point at which a colon is
encountered. For example, the command powermt display dev=device|all shows LUN
123:abc as LUN 123.
In PowerPath 4.3.x (or later), this problem has been partially resolved. With this release, the command
powermt load [file=older_file] fails to complete if the configuration file contains data for
CLARiiON pseudo devices with colon-containing LUN names. This results in CLARiiON volumes and
third-party volumes being set with default load balancing and failover policies.
186235, 185281 4.3.0 4.5.0

The powervxvm init script corrupts the VxVM rootdg created on external devices managed by
PowerPath.
The powervxvm init script now automatically protects disk groups (including rootdg), which
prevents it from destroying any previously existing disk group. A warning appears near the end of the
script to indicate which devices were not initialized.

Before you install PowerPath, or whenever you make changes to the
host or storage environment where PowerPath operates, consult the
resources described in this section. These resources will help you
configure an environment in which all components, including
PowerPath, can operate optimally.
EMC Support Matrix (all storage systems)
The EMC Support Matrix provides detailed information about the
hardware, software, and networked storage components that are
tested and compatible with both EMC storage systems and
third-party storage systems. (For information about third-party
storage systems, see the chapter entitled Non-EMC Storage.) The EMC
Support Matrix describes supported host models, operating system
revisions, host bus adapters, and connectivity devices.
The EMC Support Matrix, which is updated every month, is published
at the Powerlink™ website:
http://Powerlink.EMC.com

The support matrix is available in two formats:

◆ The EMCLink E-Lab™ Navigator (formerly ESN Builder) link is a
Web-based, searchable database configurator.
◆ The Download link (within E-Lab Navigator) lets you download
the EMC Support Matrix as an Adobe .pdf file.
EMC host connectivity guide (EMC storage systems only)
The EMC host connectivity guides describe the features and setup
procedures for host interfaces to EMC Symmetrix and CLARiiON
systems. Host connectivity guides are updated quarterly and are
published on the Powerlink website.
Consult the Before You Install section of your installation and
administration guide; the EMC Support Matrix; and, for CLARiiON or
Symmetrix systems, the EMC Host Connectivity Guide for Sun Solaris
before you install PowerPath. In addition, since changing any system
component can change the way PowerPath manages storage paths,
you should consult these resources before you undertake any of the
following common system or network management tasks:
◆ Upgrade or change the host OS, or the host bus adapter. (Refer
specifically to the Application Software chapter for your storage
system model.)
◆ Change the model of the system that hosts PowerPath.
◆ Change or replace a host bus adapter type, or adapter cable on the
system that hosts PowerPath.
◆ Change components (for example, switches) of your network
configuration.
◆ Change the storage network zoning or device assignments.
◆ Change the array or storage system connected to the host.
The information in the following sections is accurate at the time of
publication. However, information about qualified hardware and
software is revised and published monthly on the Powerlink website
and quarterly in the EMC host connectivity guides. In the event of
discrepancies, information in E-Lab Navigator, the EMC Support
Matrix, or the host connectivity guide takes precedence over the
information in these sections.

Host Configuration The following table shows the Solaris operating systems supported.
Table 2 Solaris: Supported Operating Systems
Supported OS Sun patches required
Sparc Solaris 7 (32 and 64 bit) 106541-38

106541-41
106925-11 (X6541 HBA only)
106924-11 (X1062A and X1065A HBAs only)

117000-05
117350-27
108974-45
109885-18 (X6541 HBA only)
109657-11 (X106A2 & X1065A HBAs only)

112834-06
113277-35
117171-17
118558-11
Sparc Solaris 10 118822-11

119374-04
119130-08 (X6767A and X6768A HBAs only)
The following table shows minimum disk space requirements for

Solaris.
Table 3 Solaris: Disk Space Required
File System or Directory Minimum Space Requirements
Installation directory (the default is /opt) 40 MB
Root file system 16 MB
/usr 12 MB
/var 1 MB

Supported HBAs: PowerPath 4.5.0 for Solaris With Third-Party

Storage Systems
This section describes the HBA models and driver versions
supported for PowerPath 4.5.0 for Solaris with third-party storage
systems. The section also describes changes to the default driver
configuration files required by PowerPath 4.5.0 for Solaris.
Consult the EMC Support Matrix for HBA models and driver versions
supported with Symmetrix and CLARiiON systems.
Supported HBAs: IBM ESS, Hitachi Lightning, Hitachi TagmaStore,

HP xp Systems
PowerPath 4.5.0 for Solaris has been tested and qualified for use with
IBM ESS, Hitachi Lightning, Hitachi TagmaStore, and HP xp storage
systems using the HBA models and driver versions shown in the
following table.
Table 4 Solaris: Supported HBAs—IBM ESS, Hitachi Lightning, HP xp Systems
Manufacturer Model Driver Versions Supported with Arrays
Hitachi Hitachi HP xp
IBM ESS Lightning TagmaStore Arrays
Emulex LP8000 EMC 5.02c ✔ ✔ ✔ ✔

LP9000 EMC 6.01f
LP9002LDC
LP10000
LP9802 EMC 5.02c ✔

EMC 6.01f
Supported HBAs: HP StorageWorks EVA, EMA, and MA Systems

PowerPath 4.5.0 for Solaris has been tested and qualified for use with
HP StorageWorks EVA, EMA, and MA storage systems using the
HBA models and driver versions shown in the following table.

Note: HP requires installation of the Platform Kit on every host connected to

these storage systems. The Platform Kit contains the drivers that are
supported with the storage system. You can download the Platform Kit from
the HP website.
Table 5 Solaris: Supported HBAs—HP StorageWorks EVA, EMA, MA systems
Manufacturer Model Driver Versions
QLogic QLA 2312 QLogic V4.11
SG-XPCIFC2-QF2 SUNWqlc
SUNWqlcx 11.8.0
SUNWqlcx 11.9.0
Emulex LP8000 EMC 5.01e
EMC 5.02c
EMC 6.01f
LP-9002 EMC 5.02c
EMC 6.01f
LP10000 EMC 6.01f

HBA Driver Settings

The following table describes changes to the default driver
configuration files required by PowerPath 4.5.0 for Solaris with
third-party storage systems.
Table 6 Solaris: HBA Driver Settings—Third-Party Storage Systems
PowerPath Setting
Default
HBA Driver Parameter Setting Setting Required for
Emulex automap 0 0 All third-party

systems
linkdown-tmo 30 60 All third-party

systems
lun-queue-depth 30 20 All third-party

systems
num-iocbs 1024 2048 All third-party

systems
tgt-queue-depth 0 512 All third-party

systems
no-device-delay 0 0 All third-party

storage systems
Heterogeneous Connections
PowerPath 4.5.0 for Solaris supports heterogeneous connections to
different storage arrays from the same HBA only with the following
HBA model numbers:
◆ Sun X6767A(SG-XPCI1FC-QF2)
◆ Sun X6768A (SG-XPCI2FC-QF2)
◆ LP8000
◆ LP9002
◆ LP9802
◆ LP10000
Note: The heterogeneous connections allowed by third-party vendors may
conflict with those allowed by EMC. In that case, the third-party vendor’s
requirements take precedence.

Interoperability With VxVM on HP xp Arrays

For PowerPath 4.5.0 for Solaris to fully interoperate with VERITAS
Volume Manager (VxVM) on third-party arrays, you must install the
VERITAS Array Support Library (ASL) for your particular storage
system after you install VxVM. You can download the ASL from the
VERITAS website.
Storage Array Before you install PowerPath, set up connections between a storage
Configuration system and a host. Refer to the EMC Host Connectivity Guide for Sun
Solaris for information on setting up connections for Symmetrix and
CLARiiON systems. For information on setting up connections for
third-party storage systems, refer to your vendor’s documentation.
Symmetrix Storage The following table shows requirements and specifications for a
Systems PowerPath host connected to a Symmetrix system: maximum
number of paths per logical device, Enginuity™ microcode levels
supported, and support for booting from a Symmetrix device.
Microcode versions tested Paths per device Boot support
5x67, 5x68, 5x69, 5x70, 5x71 32 Solaris 7, 8, 9, 10
Note: For information about LUN configuration and limits see the EMC host
connectivity guide, available on the Powerlink website.
Once a host and Symmetrix system are properly configured, you can
install or upgrade PowerPath. See the PowerPath for Solaris Installation
and Administration Guide for installation details.
CLARiiON Storage PowerPath installation is an integral part of a CLARiiON setup and

Systems configuration procedure. To properly install PowerPath on a host
with a CLARiiON array, refer to the EMC Installation Roadmap for
CX-Series and FC-Series Storage Systems. There you will find
step-by-step instructions for installing PowerPath and other
CLARiiON software.
To obtain the latest versions of CLARiiON CX-series documentation,
log in to the Powerlink website (http://Powerlink.EMC.com). Then
click Support > Document Library.
CLARiiON AX100-Series installation, planning, and troubleshooting
documents are located on the AX100 support website. For
information on accessing the site, refer to the support documentation
that shipped with your storage system. Refer only to these

documents for prescribed installation information when using

AX100-Series storage systems.
The following table shows the minimum revision of FLARE™
supported by PowerPath 4.5.0 for Solaris.
CLARiiON Minimum Supported

Storage System FLARE Version
AX100 02.16
AX100SC
CX200 02.07
CX300
CX400
CX500
CX600
CX700
IBM ESS Storage The following table shows the requirements and specifications for a
Systems PowerPath host connected to an IBM ESS system: model numbers
and firmware supported, maximum number of paths per logical
device, and support for booting from an IBM ESS device.
Array code/firmware Paths per

Model required device Boot support
F10/F20 2.2.0.593 32 Solaris 7, 8, 9, 10
800/800T 2.3.0.465
Once a host and IBM ESS system are properly configured, you can
install or upgrade PowerPath. See the PowerPath for Solaris Installation
and Administration Guide for installation details.
Hitachi Lightning The following table shows the requirements and specifications for a
Storage Systems PowerPath host connected to a Hitachi Lightning system: model
numbers and firmware supported, maximum number of paths per

logical device, and support for booting from a Hitachi Lightning

device.
Paths
Qualified per
Model Array code/firmware device Boot support
9970V/9980V 21-05-27 (or higher) 32 Solaris 7, 8, 9, 10
9910/9960 01-19-41 (or higher)
Once a host and Hitachi Lightning system are properly configured,

you can install or upgrade PowerPath. See the PowerPath for Solaris
Installation and Administration Guide for installation details.
Hitachi TagmaStore The following table shows the requirements and specifications for a
PowerPath host connected to a Hitachi TagmaStore system: model
logical device, and support for booting from a Hitachi TagmaStore
device.
Paths
Qualified per
Model Array code/firmware device Boot support
USP1100 50-03-69-00/00 32 Solaris 8, 9, 10

50-03-71
Hewlett-Packard The following table shows the requirements and specifications for a
StorageWorks Arrays PowerPath host connected to an HP StorageWorks system: model

logical device, and support for booting from an HP StorageWorks

device.
Minimum array Paths

code or firmware per
Model required device Boot support
HP StorageWorks 21-05-27 32 Solaris 8, 9, 10

Disk Array xp
128/1024
HP StorageWorks 01-17-26
Disk Array xp 48/512
HP StorageWorks VCS3.0, 3.010 32 Not supported.

Enterprise Virtual
Array (EVA) PowerPath does
3000/5000 not support
VCS4.001 or later
HP StorageWorks ACS 8.7-3

Enterprise Modular
HP StorageWorks
MA8000/EMA12000
HP StorageWorks 50-03-69 32 Solaris 8, 9, 10

HPXP12000
Once a host and HP StorageWorks system are properly configured,

you can install or upgrade PowerPath. See the PowerPath for Solaris
Installation and Administration Guide for installation details.
Connectivity Refer to the EMC Support Matrix for information about the
Requirements requirements for fibre channel and switched fabric configurations
and components that can be used with PowerPath.
Note: Install host bus adapters (HBAs), their supporting firmware versions,
and other network components using the manufacturer’s directions and the
settings specified in the EMC Support Matrix. Using improper settings can
cause erratic failover behavior or extended response time for system I/O.

Known Problems and Limitations

This section describes the known problems and limitations in
PowerPath 4.5.0 for Solaris.
Table 7 Known Problems in PowerPath Version 4.5.0: Solaris
Found in Resolved
Description Workaround Version in Version
231976 Log in to the Powerlink website and 4.5.0 —

powermt core dumps on issuing ‘powermt config’ or ‘powermt download the
display’ if the host is connected to 16 or more arrays. powermt.SOLARIS.4.5.0
.b170.tar file and follow the
steps mentioned in
powermt.SOLARIS.4.5.0
.b170.README.
230471 1. Remove PowerPath. Refer to 4.4.0 —

SYMCLI functionality degrades after uninstalling PowerPath PowerPath 4.5 for Solaris
4.4.0. Installation and Administration
Guide.
2. Confirm the no reboot
required message
appears.
3. Enter: symcfg discover
229447 To fix inconsistent device 4.5.0 —

VxVM 4.1 pseudo device mappings (emcpower mappings) may mappings:
become inconsistent with PowerPath pseudo device mappings. 1. Enter:
Circumstances that may cause inconsistencies include: cp /etc/vx/disk.info
• VxVM 4.1 is uninstalled and reinstalled after a LUN /etc/vx/disk.info.old
configuration change. VxVM maps pseudo devices based on 2. Enter:
device information saved before the uninstall, and these echo >
mappings may differ from the current PowerPath mappings /etc/vx/disk.info
and configuration. 3. Enter:
• A pseudo device instance is renamed using emcpadm, vxconfigd -k
which causes VxVM 4.1 to lose the pseudo device mapping.

Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued)
Found in Resolved
224939 Refer to “Uninstalling PowerPath in 4.5.0 —

In a Sun Cluster 3.1 environment with VxVM 4.1, removing an Environment With Sun Cluster
PowerPath with the pkgrm command may fail with the following 3.1 and VxVM 4.1” on page 30 for
message: the workaround instructions.
EMCpower Removal:
Error: PowerPath pseudo(s) still in-use,
busy or mounted.
Please stop all I/Os and make sure all
volumes are not mounted then retry removing
the package.
--------------------------------------------
pkgrm: ERROR: preremove script did not
complete successfully
Removal of <EMCpower> failed.
223915 Manually manage the unmanaged 4.5.0 —

When you upgrade to PowerPath 4.5 from an older version of array classes after you upgrade.
PowerPath, third-party arrays that are not supported on the older Enter:
version of PowerPath will come up as unmanaged in PowerPath powermt manage
4.5. class=<class>
Refer to the PowerPath Product
Guide for more information on the
powermt manage command.
221934 Stop Naviagent before you 4.5.0 —

In a PowerPath 4.5.0 environment with a Leadville driver, MPXIO uninstall PowerPath.
enabled and managing third-party devices, and the Naviagent
running, a system crash occurs when you remove PowerPath
from the host.
221782 To unmanage the path: 4.5.0 —

A path to a Hitachi storage system is managed by both MPxIO 1. Enter:
and PowerPath. powermt remove
If your host is connected to a Hitachi storage system, and the dev=all
parameter mpxio-disable is set to no 2. Enter:
(mpxio-disable=no), PowerPath will try to manage the powermt unmanage
path that is already managed by MPxIO. class=hitachi
You can verify the status of the Hitachi storage system class by 3. Enter:
running the command powermt display options. If powermt config
the status is managed, then manually unmanage the path, as
described in the Workaround column.

Found in Resolved
221125 Manually mount the /usr and 4.5.0 —

When performing a Solaris Live Upgrade from Solaris 9 to Solaris /var directories. Refer to the
10, you need to manually mount the /usr and /var directories. PowerPath 4.5 for Solaris
(When you perform a Solaris Live Upgrade from Solaris 8 to 9, Installation and Administration
this step is not necessary.) Guide for more information on the
Live Upgrade procedure.

Found in Resolved
221084 — When upgrading or reinstalling 4.4.0 —

With PowerPath 4.4.0 or later and VxVM 4.1, the command PowerPath, reboot after the initial
vxdisk list may display multiple entries for the same package remove, if PowerPath
device. This may occur following a reboot where PowerPath has requested the reboot.
just been installed or new devices have been mapped or zoned to — When duplicate entries are
a host. seen, a second reboot will clear the
The issue occurs because PowerPath pseudo device links are duplicates. The PowerPath pseudo
unavailable during boot, and VERITAS VxVM 4.1 depends on device links will be available during
these links before they can be created. This usually occurs when the second reboot.
PowerPath is uninstalled and reinstalled without clearing the — When mapping/zoning new
knowledge VxVM 4.1 has of these devices. It can also happen if a LUNS to the host, to avoid
new LUN is mapped or zoned to a host and VxVM had prior duplicate entries:
knowledge of this device. 1. Run vxddladm stop.
eventsource.
2. Map/zone the new LUNS to the
host.
3. Dynamically recreate the LUN
device (either using cfgadm
routines or HBA-specific
routines to dynamically create
the device nodes).
4. Run powermt config to
discover and create the pseudo
device links.
5. Run vxddladm start
eventsource.
— When a host is rebooted with a
path down, follow this procedure to
avoid duplicate entries:
1. Run vxddladm stop
eventsource
2. Reconnect the paths.
3. Run powermt config.
4. Run vxddlam start.
eventsource.
— If vxddladm commands
were not run, then reboot the
system to remove the duplicate
entries.
220814 Remove SAN 4.4.5 and install SAN 4.5.0 —

With SAN 4.4.5 in a CLARiiON basic failover environment, 4.4.6 .
PowerPath 4.5.0 does not trespass LUNs when a Fibre Channel
cable is pulled from the SP port.

Found in Resolved
220574 Ensure that the SPC2 flag is set to 4.5.0 —

R1/R2 boot support in a Symmetrix 5x71 environment does not OFF if your configuration includes
work when the Symmetrix SPC2 flag is set to ON. R1/R2 boot support and
Symmetrix 5x71.
By default, this setting is ON.
220378 4.5.0 —
In a CLARiiON storage system environment, upgrading to
PowerPath 4.5 when pseudo devices are in use causes a failure.
File system corruption occurs during the host reboot.
217792 Remove the device from 4.1.0 —

When you run the syminq command, sometimes the wrong PowerPath and then add it back.
director may be returned from Symmetrix devices. For example, a Enter:
device returns FA 13aA when you run syminq, but PowerPath 1.powermt remove
returns FA 13dB. This can occur when the PowerPath cache is dev=<device>
not updated after a recent device reconfiguration on the 2.powercf –q
Symmetrix system. 3.powermt save
4. powermt config
216195 4.5.0 —
PowerPath 4.5 with Solaris 10 is incompatible with volume
managers such as VxVM 4.1 that encapsulate the root device,
due to a known problem in VERITAS Volume Manager 4.1.
212419 Change the VxVM third-party 4.4.0 —

VERITAS Volume Manager 4.1 does not support PowerPath driver mode (tpdmode) to native by
pseudo device naming with third-party arrays. entering:
vxdmpadm setattr
enclosure <enclosure>
tpdmode=native
This change also applies to any
EMC devices in a mixed-array
environment.

Found in Resolved
210941 Install the appropriate SUN 4.4.0 —

In a Solaris environment with PowerPath 4.4.0 and a Leadville T-patch, or install SAN 4.4.7.
driver, running SYMCLI commands generates the following errors Refer to the EMC Knowledgebase
in /var/adm/messages: solution emc108113 for more
Oct 12 12:03:53 db026ops qlc: [ID 686697 information.
kern.info] NOTICE: Qlogic qlc(1): Link
ONLINE
Oct 12 12:03:53 db026ops scsi: [ID 243001
kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0
(fcp1):
Oct 12 12:03:53 db026ops Lun=0 for
target=615313 disappeared
Oct 12 12:03:53 db026ops scsi: [ID 243001
kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0
(fcp1):
Oct 12 12:03:53 db026ops Lun=0 for
target=614313 disappeared
Oct 12 12:03:58 db026ops qlc: [ID 686697
kern.info] NOTICE: Qlogic qlc(2): Loop
OFFLINE
205610 Move pseudo devices to native 4.4.0 —

Sun Volume Manager metadatabases created on PowerPath devices before upgrading.
pseudo devices may not persist after upgrading to PowerPath 4.4.
204912 Run the following commands 4.4.0 —

After a fresh installation of PowerPath 4.4 on a Solaris 10 host before you reboot:
with a valid license connected to a Symmetrix storage system, the powermt set policy=so
load balancing policy is set to "bf" (basic failover) after the host powermt save
reboots. The policy should be set to "so" (Symmetrix optimized).
204709 4.4.0 —
Running the powermt remove dev=all and powermt
config commands on a host that has mounted the SnapView
LUN makes the snapshot inactive, causing data corruption.
203121, 203123 Ignore the messages. 4.4.0 —

Rebooting a PowerPath host that is a node in a Sun 3.1 cluster
and is also connected to EVA devices generates volume
assign/restore messages and path dead/alive messages. These
messages are also seen during node failover.

Found in Resolved
197626 1. Query the CLARiiON storage 4.3.0 —

Very infrequently, an admsnap operation (start, stop, etc.) array using Navisphere, and
reports the error 0xE10080A3. This error indicates that the determine whether the
specified admsnap operation may not have completed on all of admsnap command
the devices specified on the command line due to an internal completed the operation for all
operation failing to complete properly to the array. For applications devices specified on the
or scripts that rely on the exit status from admsnap, a non-zero command line. If it did, no
exit status is returned to the application or script. action is required.
2. If the admsnap command
failed to complete the operation
for all of the devices specified
on the command line:
For start operations that
failed to complete, stop the
session on the devices and
retry the admsnap command.
For activate operations
that failed to complete,
deactivate the session on the
devices and retry the
admsnap command.
For stop operations that
failed to complete, stop the
session. No further action is
required.
For deactivate operations
that failed to complete,
deactivate the session. No
further action is required.
3. If this problem persists, use
Navisphere instead of
Admsnap to perform the
operation.
180770 Use either the boot or reboot 4.3.0 —

With third-party arrays in a cluster, reconfiguration reboot does command. Do not use the
not recover paths that are down at boot. boot -r or reboot -- -r
command.
183863 Ignore this message. The custom 4.3.0 —

In an R1/R2 boot situation, after failover/failback, the following settings are loaded.
console error message appears after booting from the R2 host:
Error occurred loading saved driver
state from file /etc/powermt.custom.
Loading continues...

Found in Resolved
175725 4.2.0 —
169443
powermt restore restores all paths to third-party arrays
when periodic autorestore is set to off.
This includes, among others, HPXP and Hitachi Lightning
devices.
165579 Before you reboot the host, update 4.1.0 —

Using the powermt unmanage class=hitachi the system configuration in the
command to unmanage third-party arrays when the host is /etc/system and
booted from a pseudo device prevents the system from coming /etc/vfstab files to use
up after you reboot. You see the following message when you native devices.
unmanage a boot device: Refer to the PowerPath 4.5 for
WARNING: One or more boot devices have been Solaris Installation and
unmanaged. Update the system configuration Administration Guide for more
settings as appropriate. Cannot remove information.
device that is in use: <emcpowerx>
162224 4.2.0 —
LUNs are trespassed when the HBAs are removed one by one
using the powermt remove hba=# command.
156582 Reboot the host and then rerun 4.1.0 —

PowerPath installation or removal fails if pkgadd or pkgrm is pkgadd or pkgrm.
interrupted.
124857 • If your PowerPath registration 3.0.3 —

Executing emcpreg -f -edit without specifying the file is the default file
PowerPath registration filename (the default is (/etc/emcp_registra
emcp_registration) could cause deletion of the tion), do not use the -f
registration file’s parent directory. (The default parent directory is option with emcpreg.
/etc.) • Otherwise, be sure to specify
For example, if your PowerPath registration file is in the /test the full pathname. Enter:
directory and you execute the command emcpreg -f
emcpreg -f /test -edit, /directory/filename
you see the following prompt: -edit
EMCP registration file is corrupt. • If you neglect to specify the full
Delete it? pathname, answer n (no) to the
If you answer y (yes) to the prompt, /test is deleted. prompt:
EMCP registration
file is corrupt.
Delete it?

Limitations PowerPath 4.5.0 for Solaris has the following limitations:

◆ In an R1/R2 boot support environment:
• PowerPath 4.5 does not support Sun HBAs X6767A and
X6768A.
• R1/R2 boot support hosts must be connected directly to the
Symmetrix system; they cannot be connected through the
fabric.
◆ VERITAS Volume Manager does not support PowerPath pseudo
device naming with third-party arrays. You can change the VxVM
third-party driver mode (tpdmode) to native by entering:
vxdmpadm setattr enclosure <enclosure> tpdmode=native
This change also applies to any EMC devices in a mixed array
environment.
◆ PowerPath 4.5.0 cannot co-manage devices with third-party path
management software such as Hitachi Dynamic Link Manager
(HDLM), IBM Subsystem Device Driver (SDD), HP StorageWorks
Secure Path, or HP StorageWorks Auto Path XP Virtual Array.
During installation of PowerPath 4.5.0, the installation script tests
for the presence of third-party path management software on the
system. If such software is installed on the system, the PowerPath
installation script disables support for the corresponding array
type in PowerPath:
Support for this array type is

If this software is present disabled in PowerPath
HDLM Hitachi Lightning, Hitachi

TagmaStore
SDD IBM ESS
HP StorageWorks Secure Path HP StorageWorks EVA, EMA, MA
HP StorageWorks Auto Path XP Virtual Array HP StorageWorks xp
Since PowerPath coexistence is not supported by third-party

array path management products, when you enable PowerPath
(powermt manage class=<class>) for a class that is being
managed by a third-party product, multipathing behavior is
undefined.

Since PowerPath is not supported in third-party path

management environments when the corresponding storage
system class type is in the managed state, multipathing behavior
for any attached arrays in the corresponding class is undefined if
you subsequently execute a powermt manage class= command:
Multipathing behavior is undefined if you

If this software is present execute this command
HDLM powermt manage class=hitachi
SDD powermt manage class=ess
HP StorageWorks Secure Path powermt manage class=hphsx
HP StorageWorks Auto Path XP powermt manage class=hpxp

Virtual Array
Since PowerPath and the third-party software cannot co-manage

devices, do not initiate co-management by executing this
command on third-party array class machines. As long as this
command is not executed, support for the relevant third-party
arrays will remain disabled across reboots.
Similarly, before you install third-party path management
software on a system on which PowerPath 4.5.0 is already
installed, you should disable any support by PowerPath for the
relevant third-party array devices using a powermt unmanage
class= command:
Before you install this software Execute this command
HDLM powermt unmanage class=hitachi
SDD powermt unmanage class=ess
HP StorageWorks Secure Path powermt unmanage class=hphsx
HP StorageWorks Auto Path XP powermt unmanage class=hpxp

Virtual Array
◆ PowerPath 4.5.0 does not support load balancing and failover for
applications that use the SCSI-2 Reserve/Release or Solaris
MHIOCTKOWN IOCTL command set in an EMC Invista, IBM
ESS, Hitachi Lightning, Hitachi TagmaStore, or HP StorageWorks
environment.

If you deploy any such applications, you must set the load
balancing and failover policy to nr (No redirect). Refer to the
powermt set policy command description in the PowerPath
Product Guide for more information on setting load balancing and
failover policies.
◆ The following is an issue with Sun’s native driver.
When using Sun's qlc driver, you might see the following
message on the system console at boot:
emcp: info: Not all paths to <array_type> <array_number> vol <volume_number> are
dead.
Any application configured to use the devices too soon (vfstab
mounts for instance) will fail to open its device.
Note: The paths will be autorestored in time, or you can run powermt
restore to restore them.
To avoid this situation, when using Sun's native driver:

1. Add the following line to the /etc/system file:
set fcp:ssfcp_enable_auto_configuration=1
2. Reboot the host.
◆ Using PowerPath pseudo names under VxVM 4.0 is subject to
several limitations. Refer to “VxVM 4.0 and PowerPath 4.5.0
Pseudo Names” on page 27 for details.
◆ PowerPath cannot failover path-specific requests, such as
dev_info.

Technical Notes
Technical Notes
This section contains additional information on PowerPath not
covered in the core documents. This section includes the following
subsections:
◆ “Upgrading From PowerPath 3.0.x” on page 25
◆ “Upgrading From PowerPath 4.0.x on Symmetrix Systems” on
page 25
◆ “VxVM 4.0 and PowerPath 4.5.0 Pseudo Names” on page 27
◆ “Pseudo Names With VxVM 4.1 and PowerPath 4.5.0” on page 28
◆ “Uninstalling PowerPath in an Environment With Sun Cluster 3.1
and VxVM 4.1” on page 30
◆ “HP StorageWorks Controller and Port Names” on page 30
◆ “Removing HP StorageWorks Secure Path” on page 31
Upgrading From PowerPath 3.0.x

When upgrading from PowerPath 3.0.x to PowerPath 4.x, run the
chmod +r /etc/powermt.custom.saved command to enable all read
permissions on the saved version of the powermt.custom file after
uninstalling 3.0.x and before installing 4.x. If you do not enable read
permissions on the powermt.custom.saved file, PowerPath may not
be able to perform an upgrade installation, depending on the version
and patch level of Solaris running on the host.
Upgrading From PowerPath 4.0.x on Symmetrix Systems
Note: In the vast majority of cases, upgrading from PowerPath 4.0.x to

PowerPath 4.5.0 on a Solaris host in a Symmetrix environment succeeds
without incident. In the rare circumstance that a Symmetrix system matches
the configuration described below, take special care when upgrading,
following the instructions in this section.
If your Solaris host is running any version of PowerPath 4.0.x and is

attached to a Symmetrix system with a serial number with 8 or 9 as
the fifth number from the right (for example, HK187990167), contact
Customer Support before upgrading to PowerPath 4.5.0. Customer

Technical Notes
Support will provide you with a tool and procedure to follow to

safely upgrade your server.
If you remove PowerPath 4.0.x and install PowerPath 4.5.0 without
contacting Customer Support, the upgrade to PowerPath 4.5.0 will
stop with the following message:
emcp_registration version 402 detected.
emcpupgrade: error - configuration files corrupted.
emcpupgrade: Detected inconsistency with saved Symmetrix serial numbers.
-----------------------------------------------------------------------------
* EMCpower Installation:
*
* Can not upgrade at this time.
* There is a problem with the saved powerpath config files.
* Please contact customer service to complete UPGRADE
----------------------------------------------------------------------------
----------------------------------------------------------------------------
* EMCpower Installation:
*
* Configuration files conversion unsuccessful!!!
* The PowerPath 4.5 Package was successfully installed, but there is a known
* issue with your configuration files.
*
* In order to upgrade your configuration, please contact EMC Customer Service
* for assistance. Do not reboot. Do not restart your applications.
* Consult the 4.5 Release Notes.
----------------------------------------------------------------------------
All trademarks used herein are the property of their respective owners.
Installation of <EMCpower> was successful.
In addition to the console output, the following will appear in the

system log:
date and time system Can[16107]: [ID 702911 daemon.notice] not upgrade at this
time. There is a problem with the saved powerpath config files.
date and time system Contact[16434]: [ID 702911 daemon.notice] Customer
Service. Do not reboot. Do not restart your applications. Consult the 4.5
Release Notes.
If this happens, we strongly recommend that you:

1. Remove PowerPath 4.5.0.
2. Reinstall the version of 4.0.x that you were running previously.
3. Reboot the host.
4. Contact Customer Support for further instructions; reference
EMC Knowledge Base article emc77259.

Technical Notes
VxVM 4.0 and PowerPath 4.5.0 Pseudo Names

You can use the powervxvm install utility to make PowerPath
pseudo device names available under VxVM 4.0.
Be aware that both native device names and PowerPath pseudo
device names will be visible to VxVM 4.0. Both names will be
reported in vxdisk list output, which typically looks like this:
c3t2d1s2 auto:none - - online invalid
emcpower0c simple - - online invalid
Both devices represent the same LUN.

To avoid confusion, you can use the VxVM vxdiskadm utility to
exclude the native devices (in the example above, c3t2d1s2) from the
VxVM view. Refer to VxVM vxdiskadm documentation for details.
Upgrading to After upgrading to VxVM 4.0 from a VxVM 3.5 (or earlier)
VxVM 4.0 installation that was configured to use PowerPath pseudo device
names, use the following procedure to reintroduce PowerPath
pseudo device names in VxVM 4.0.
1. Place PowerPath pseudo device names under VxVM 4.0 using
powervxvm. You can do this for all emcpower devices, or for
individually selected devices:
For all devices, run the following command:
powervxvm define
For individual devices:
a. Run the following command:
powervxvm install
Note: Important: Use powervxvm install and not

powervxvm init. powervxvm init corrupts the rootdg for some
versions of VxVM.
b. Select Option 3 “Install one device at a time”.

c. For each device to be used under VxVM 4.0, select Option 2
“to define”.

Technical Notes
! CAUTION
Do not initialize the emcpower disks if they currently contain
VxVM volumes.
2. Re-import previously existing disk groups/volumes.

The simplest way to do this it to reboot using the following
command:
shutdown -i6
However, if you cannot reboot, use the following procedure:
a. Request that VxVM re-import any disk groups by restarting
vxconfigd; run the following command:
vxdctl enable
b. For each disk group that was rediscovered, request that all
volumes on that disk group be restarted; run the following
command:
vxvol –g diskgroup startall
Limitations PowerPath pseudo devices are identified as simple disks by VxVM.

Thus:
◆ VERITAS CDS (common-disk-schema) is not supported with
PowerPath pseudo device names. The cds attribute must be
disabled when creating the disk group. Run a command like the
following:
vxdg init symmdg disk=emcpower0c cds=off
◆ The default for VxVM 4.0 disk groups is CDS=ON. Therefore, if you
have existing VxVM 4.0 disk groups/volumes (without
PowerPath) you cannot use powervxvm scripts to migrate to
PowerPath pseudo devices.
Pseudo Names With VxVM 4.1 and PowerPath 4.5.0

When you install VxVM 4.1 in a PowerPath environment, VxVM
converts any EMC Symmetrix and CLARiiON devices with native
names to pseudo names (emcpower names). EMC recommends using
the default naming convention (pseudo names) for EMC storage
devices. However, it is possible to configure native names (c#t#d#
names) for EMC devices, as described in this section.

Technical Notes
Note: The powervxvm utility does not support pseudo device names for
third-party devices in the VERITAS device list. The following error message
appears when you try to bring third-party device s into the VxVM device list:
VxVM vxdisk ERROR V-5-1-5433 Device emcpower3s2: init
failed: device path not valid.
Pseudo device names for third-party arrays are not supported with
VxVM 4.1. You can only use pseudo device names for Symmetrix and
CLARiiON devices.
Changing EMC Devices to Native Device Names

Note: Use the procedure in this section only if the default disk-naming
scheme is set to operating system–based naming, and the TPD-controlled
enclosure does not contain fabric disks.
To change EMC storage devices from the default pseudo names to

native names:
1. View the pseudo device names that appear after installing VxVM
4.1. Enter:
# vxdisk list
Output:
DEVICE TYPE DISK GROUP STATUS
emcpower10s2 auto:sliced disk1 mydg online
2. Change the pseudo names to native names. Enter:

# vxdmpadm setattr enclosure <enclosure> tpdmode=native
Where <enclosure> is the enclosure name of the EMC device.

Example:
# vxdmpadm settattr enclosure EMC0 tpdmode=native
3. List the device names and note the different naming convention
in the Device column. Enter:

Technical Notes
# vxdisk list
Output:
DEVICE TYPE DISK GROUP STATUS
c6t0d10s2 auto:sliced disk1 mydg online
If tpdmode is set to native, the subpath with the smallest device

number is displayed.
Uninstalling PowerPath in an Environment With Sun Cluster 3.1 and VxVM 4.1
If you attempt to remove PowerPath in a Sun Cluster 3.1 with
VxVM 4.1 environment, and pkgrm fails, enter the following
commands. Then retry pkgrm.
# cd /dev/rdsk
# for path in `ls emcpower*c`
do
/usr/sbin/vxdmpadm -f disable path=${path}
done
#
Uninstall PowerPath following the directions in the PowerPath 4.5 for

Solaris Installation and Administration Guide.
HP StorageWorks Controller and Port Names

PowerPath names for HP StorageWorks EVA and HSG80 controllers
and ports differ from the names in the array GUIs. This section
describes the differences.
HP StorageWorks EVA Names

PowerPath identifies controllers A and B exactly as Command View
EVA does. PowerPath port numbers are one lower than Command
View EVA port numbers.

Technical Notes
Names are mapped as follows:
Command View EVA name PowerPath name
A-1 A-0
A-2 A-1
B-1 B-0
B-2 B-1
HP StorageWorks HSG80
PowerPath names the bottom controller A and the top controller B.
PowerPath port numbers are one lower than HSG Element Manager
port numbers.
Names are mapped as follows:
HSG Element Manager name PowerPath name
Bottom-1 A-0
Bottom-2 A-1
Top-1 B-0
Top-2 B-1
Removing HP StorageWorks Secure Path

After you remove HP StorageWorks Secure Path from a system that
has JNI/AMCC FCA-1063 HBAs configured, the powermt display
command shows only one HBA, or no HBAs.
1. Remove Secure Path bindings from the HBA configuration
(.conf) file and sd.conf. Establish PowerPath static bindings as
follows:
LPFC: Add to lpfc.conf:

Technical Notes
fcp-bind-WWPN="50001fe10010f621:lpfc0t0",
"50001fe10010f622:lpfc0t1",
"50001fe10010f623:lpfc1t2",
"50001fe10010f624:lpfc1t3",
"50001fe15002f00d:lpfc0t4",
"50001fe15002f00c:lpfc0t5",
"50001fe15002f009:lpfc1t6",
"50001fe15002f008:lpfc1t7";
Qlogic: Add to qlaxxxx.conf:

hba0-SCSI-target-id-4-fibre-channel-port-name="50001fe15000b028";
hba0-SCSI-target-id-6-fibre-channel-port-name="50001fe15000b02c";
hba0-SCSI-target-id-7-fibre-channel-port-name="50001fe15000b02d";
hba1-SCSI-target-id-6-fibre-channel-port-name="50001fe15000b02c";
hba1-SCSI-target-id-7-fibre-channel-port-name="50001fe15000b02d";
JNIs: fcaw.conf and fca-pci.conf
#EVA Bindings
target4_hba="fcaw0";
target4_wwpn="50001fe15000b028";
target5_wwpn="50001fe15000b02d";
target6_wwpn="50001fe15000b029";
target7_wwpn="50001fe15000b02c";
2. Add the following to sd.conf:

# EVA5000
name="sd" class="scsi" target=4 lun=0;
3. List the above entries for each target you have defined in the HBA
configuration (.conf) file.
4. Finally, reboot the host:
reboot -- -r

Documentation
Documentation
This section provides a list of the documentation that supports
PowerPath for Solaris.
PowerPath The following table lists the PowerPath documentation set; all
Documentation manuals are available from EMC Corporation. Electronic versions of
all PowerPath manuals are available on the Powerlink website:
http://Powerlink.EMC.com. These manuals are updated
periodically, and the updated manuals are posted on the Powerlink
website.
Name
PowerPath 4.5 for Solaris Installation and Administration Guide
EMC PowerPath 4.5 for Solaris Release Notes
PowerPath 4.5 Product Guide
EMC PowerPath 4.5 Quick Reference
Related If your environment includes Symmetrix storage systems, refer also

Documentation to the EMC host connectivity guides, which are available on the
Powerlink website.
If your environment includes CLARiiON storage systems, refer also
to the following manuals:
◆ EMC host connectivity guides
◆ EMC Installation Roadmap for CX-Series and FC-Series Storage
Systems
◆ CLARiiON AX100-Series installation, planning, and
troubleshooting documents, located on the AX100 support
website. For information on accessing the site, refer to the support
documentation that shipped with your storage system. Refer only
to these documents for prescribed installation information when
using AX100-Series storage systems.
◆ EMC Navisphere Manager Version 6.X Administrator’s Guide
If your environment includes other vendors’ storage systems, refer to
the appropriate documentation from your vendor.

Software Media, Organization, and Files
Software Media, Organization, and Files

This section describes the contents of the PowerPath 4.5.0 for Solaris
CD.
Media The PowerPath 4.5.0 for Solaris software is distributed on a CD,

P/N 053-001-505.
Organization The PowerPath 4.5.0 for Solaris CD has the following structure:
◆ /UNIX/SOLARIS/EMCPOWER — Contains all files in the PowerPath
package.
◆ /UNIX/SOLARIS/EMCpower.SOLARIS.4.5.0.tar.z —
Compressed tar file that contains the PowerPath package.
Files Refer to the section entitled Files Created by PowerPath Installation in

Appendix A, “Files Changed By PowerPath,” in the PowerPath 4.5 for
Solaris Installation and Administration Guide.
Installation
Refer to the PowerPath 4.5 for Solaris Installation and Administration
Guide for complete instructions on installing PowerPath.
For the New User Follow the instructions in the section entitled Installing PowerPath 4.5
in Chapter 1, “Installing PowerPath”, of the PowerPath 4.5 for Solaris
Installation and Administration Guide.
Upgrading From a Follow the instructions in the section entitled Upgrading to PowerPath
Previous Revision 4.5 in Chapter 1, "Installing PowerPath," of PowerPath 4.5 for Solaris
Installation and Administration Guide.

Troubleshooting and Getting Help

For additional information on EMC products and services available
to customers and partners, refer to the EMC Powerlink website at:
http://Powerlink.EMC.com
The Powerlink website contains current information, such as:
❑ PowerPath documentation — We update PowerPath
documentation, including these release notes, when we release
new features with a patch or when documentation errors are
reported.
❑ Patches and upgrades — You can download PowerPath patch
software from Powerlink. Review the patch ReadMe files to
determine which patches (if any) you want to install after
PowerPath, and whether those patches have any added
prerequisites that must be met before you install PowerPath. To
obtain patches: on Powerlink, click Support > Downloads and
Patches > Downloads D-R > PowerPath for UNIX.
❑ EMC Issue Tracker— EMC Issue Tracker is an application that
allows you to search for known problems and defects in EMC
software. To access Issue Tracker, on Powerlink click Support >
Self-Help Tools > Issue Tracker Information > Issue Tracker.
You can use Issue Tracker to find:
• Descriptions of PowerPath bugs existing on any
PowerPath-supported host platform
• Workarounds for existing bugs
We update this database regularly between scheduled releases
and patch releases.
Reporting a Problem If you find a problem in PowerPath 4.5.0, run the emcgrab utility, and
submit the generated tar file, along with any other supporting
material, to EMC Customer Support.
You can download emcgrab from the Powerlink website.
Choose the following links: Community > Customer > Tools >
Service Tools > EMC Grab Utilities.

Copyright © 2006 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION

MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE
INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on
EMC.com.
All other trademarks used herein are the property of their respective owners.

EMC Powerpath 300 002 908

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

EMC Powerpath 300 002 908

Caricato da

Copyright:

Formati disponibili

EMC PowerPath

These release notes contain supplemental information about EMC

New Features and Changes

Note: PowerPath 4.5.0 supports EMC Invista devices. A new class,

◆ Hitachi TagmaStore storage systems

◆ HP StorageWorks XP12000 storage systems

Note: The existing HPXP class lets you manage HP StorageWorks

Discontinued Features in PowerPath

2 EMC PowerPath for Solaris Version 4.5.0 Release Notes

earlier, in which disk protection for HighRoad disks is included in the

End-of-Life CLARiiON FC4700

PowerPath Volume Manager

Table 1 Resolved Problems in PowerPath Version 4.5.0: Solaris

223401 4.4.0 4.5.0

EMC PowerPath for Solaris Version 4.5.0 Release Notes 3

Table 1 Resolved Problems in PowerPath Version 4.5.0: Solaris (continued)

205579 4.4.0 4.5.0

186233 4.3.0 4.4.0

186235, 185281 4.3.0 4.5.0

Environment and System Requirements

4 EMC PowerPath for Solaris Version 4.5.0 Release Notes

The support matrix is available in two formats:

EMC PowerPath for Solaris Version 4.5.0 Release Notes 5

Table 2 Solaris: Supported Operating Systems

Supported OS Sun patches required

Sparc Solaris 7 (32 and 64 bit) 106541-38

Sparc Solaris 8 (32 and 64 bit) 108528-29

Sparc Solaris 9 (32 and 64 bit) 112233-12

Sparc Solaris 10 118822-11

The following table shows minimum disk space requirements for

Table 3 Solaris: Disk Space Required

File System or Directory Minimum Space Requirements

Installation directory (the default is /opt) 40 MB

Root file system 16 MB

6 EMC PowerPath for Solaris Version 4.5.0 Release Notes

Supported HBAs: PowerPath 4.5.0 for Solaris With Third-Party

Supported HBAs: IBM ESS, Hitachi Lightning, Hitachi TagmaStore,

Table 4 Solaris: Supported HBAs—IBM ESS, Hitachi Lightning, HP xp Systems

Manufacturer Model Driver Versions Supported with Arrays

Emulex LP8000 EMC 5.02c ✔ ✔ ✔ ✔

LP9802 EMC 5.02c ✔

Supported HBAs: HP StorageWorks EVA, EMA, and MA Systems

EMC PowerPath for Solaris Version 4.5.0 Release Notes 7

Note: HP requires installation of the Platform Kit on every host connected to

Table 5 Solaris: Supported HBAs—HP StorageWorks EVA, EMA, MA systems

Manufacturer Model Driver Versions

QLogic QLA 2312 QLogic V4.11

Emulex LP8000 EMC 5.01e

LP-9002 EMC 5.02c

LP10000 EMC 6.01f

8 EMC PowerPath for Solaris Version 4.5.0 Release Notes

HBA Driver Settings

Table 6 Solaris: HBA Driver Settings—Third-Party Storage Systems

Emulex automap 0 0 All third-party

linkdown-tmo 30 60 All third-party

lun-queue-depth 30 20 All third-party

num-iocbs 1024 2048 All third-party

tgt-queue-depth 0 512 All third-party

no-device-delay 0 0 All third-party

EMC PowerPath for Solaris Version 4.5.0 Release Notes 9

Interoperability With VxVM on HP xp Arrays

Microcode versions tested Paths per device Boot support

5x67, 5x68, 5x69, 5x70, 5x71 32 Solaris 7, 8, 9, 10