EMC Powerpath 300 002 908

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

EMC PowerPathfor SolarisVersion 4.5.0

Release NotesP/N 300-002-908

Rev A02

June 2, 2006

1

2

Product Description

Product DescriptionEMC® 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 ChangesPowerPath 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 PowerPathThis 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

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-LifeAnnouncement

CLARiiON FC4700As 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 ManagerPlease 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 ProblemsThe 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

DescriptionFound inVersion

Resolved in Version

223401A 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.

4.4.0 4.5.0

EMC PowerPath for Solaris Version 4.5.0 Release Notes 3

4

Environment and System Requirements

Environment and System RequirementsBefore 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

205579After 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.

4.4.0 4.5.0

186233In 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.

4.3.0 4.4.0

186235, 185281The 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.

4.3.0 4.5.0

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

DescriptionFound inVersion

Resolved in Version


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.


6


Host Configuration The following table shows the Solaris operating systems supported.

The following table shows minimum disk space requirements for Solaris.

Table 2 Solaris: Supported Operating Systems

Supported OS Sun patches required

Sparc Solaris 7 (32 and 64 bit) 106541-38106541-41106925-11 (X6541 HBA only)106924-11 (X1062A and X1065A HBAs only)

Sparc Solaris 8 (32 and 64 bit) 108528-29117000-05117350-27108974-45109885-18 (X6541 HBA only)109657-11 (X106A2 & X1065A HBAs only)

Sparc Solaris 9 (32 and 64 bit) 112233-12112834-06113277-35117171-17118558-11

Sparc Solaris 10 118822-11119374-04 119130-08 (X6767A and X6768A HBAs only)

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 SystemsThis 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 SystemsPowerPath 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.

Supported HBAs: HP StorageWorks EVA, EMA, and MA SystemsPowerPath 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.

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

Manufacturer Model Driver Versions Supported with Arrays

IBM ESS Hitachi Lightning

Hitachi TagmaStore

HP xp Arrays

Emulex LP8000LP9000LP9002LDCLP10000

EMC 5.02cEMC 6.01f

✔ ✔ ✔ ✔

LP9802 EMC 5.02cEMC 6.01f

✔


8


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 SettingsThe following table describes changes to the default driver configuration files required by PowerPath 4.5.0 for Solaris with 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.

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

HBA Driver ParameterDefault Setting

PowerPath 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


10


Interoperability With VxVM on HP xp ArraysFor 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 ArrayConfiguration

Before you install PowerPath, set up connections between a storage 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 StorageSystems

The following table shows requirements and specifications for a 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.

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 StorageSystems

PowerPath installation is an integral part of a CLARiiON setup and 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

Microcode versions tested Paths per device Boot support

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




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.

IBM ESS StorageSystems

The following table shows the requirements and specifications for a 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.

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 LightningStorage Systems

The following table shows the requirements and specifications for a PowerPath host connected to a Hitachi Lightning system: model numbers and firmware supported, maximum number of paths per

CLARiiONStorage System

Minimum SupportedFLARE Version

AX100AX100SC

02.16

CX200CX300CX400CX500CX600CX700

02.07

ModelArray code/firmwarerequired

Paths per device Boot support

F10/F20 2.2.0.593 32 Solaris 7, 8, 9, 10

800/800T 2.3.0.465


12


logical device, and support for booting from a Hitachi Lightning device.

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 numbers and firmware supported, maximum number of paths per logical device, and support for booting from a Hitachi TagmaStore device.

Hewlett-PackardStorageWorks Arrays

The following table shows the requirements and specifications for a PowerPath host connected to an HP StorageWorks system: model numbers and firmware supported, maximum number of paths per

ModelQualified Array code/firmware


9970V/9980V 21-05-27 (or higher) 32 Solaris 7, 8, 9, 10

9910/9960 01-19-41 (or higher)

ModelQualified Array code/firmware


USP1100 50-03-69-00/0050-03-71

32 Solaris 8, 9, 10



logical device, and support for booting from an HP StorageWorks device.

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.

ConnectivityRequirements

Refer to the EMC Support Matrix for information about the 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.

Model

Minimum array code or firmwarerequired


HP StorageWorks Disk Array xp 128/1024

21-05-27 32 Solaris 8, 9, 10

HP StorageWorks Disk Array xp 48/512

01-17-26

HP StorageWorks Enterprise Virtual Array (EVA) 3000/5000

VCS3.0, 3.010

PowerPath does not support VCS4.001 or later

32 Not supported.

HP StorageWorks Enterprise Modular

ACS 8.7-3

HP StorageWorks MA8000/EMA12000

HP StorageWorks HPXP12000

50-03-69 32 Solaris 8, 9, 10


14

Known Problems and Limitations

Known Problems and LimitationsThis 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

Description WorkaroundFound inVersion

Resolved in Version

231976powermt core dumps on issuing ‘powermt config’ or ‘powermt display’ if the host is connected to 16 or more arrays.

Log in to the Powerlink website and download the powermt.SOLARIS.4.5.0.b170.tar file and follow the steps mentioned in powermt.SOLARIS.4.5.0.b170.README.

4.5.0 —

230471SYMCLI functionality degrades after uninstalling PowerPath 4.4.0.

1. Remove PowerPath. Refer to PowerPath 4.5 for Solaris Installation and Administration Guide.

2. Confirm the no reboot required message appears.

3. Enter: symcfg discover

4.4.0 —

229447VxVM 4.1 pseudo device mappings (emcpower mappings) may become inconsistent with PowerPath pseudo device mappings. Circumstances that may cause inconsistencies include: • VxVM 4.1 is uninstalled and reinstalled after a LUN

configuration change. VxVM maps pseudo devices based on device information saved before the uninstall, and these mappings may differ from the current PowerPath mappings and configuration.

• A pseudo device instance is renamed using emcpadm, which causes VxVM 4.1 to lose the pseudo device mapping.

To fix inconsistent device mappings:1. Enter:

cp /etc/vx/disk.info /etc/vx/disk.info.old

2. Enter:echo > /etc/vx/disk.info

3. Enter:vxconfigd -k

4.5.0 —



224939In a Sun Cluster 3.1 environment with VxVM 4.1, removing PowerPath with the pkgrm command may fail with the following message: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.

Refer to “Uninstalling PowerPath in an Environment With Sun Cluster 3.1 and VxVM 4.1” on page 30 for the workaround instructions.

4.5.0 —

223915When you upgrade to PowerPath 4.5 from an older version of PowerPath, third-party arrays that are not supported on the older version of PowerPath will come up as unmanaged in PowerPath 4.5.

Manually manage the unmanaged array classes after you upgrade. Enter:powermt manage class=<class>

Refer to the PowerPath Product Guide for more information on the powermt manage command.

4.5.0 —

221934In a PowerPath 4.5.0 environment with a Leadville driver, MPXIO enabled and managing third-party devices, and the Naviagent running, a system crash occurs when you remove PowerPath from the host.

Stop Naviagent before you uninstall PowerPath.

4.5.0 —

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

To unmanage the path:1. Enter:powermt remove dev=all

2. Enter:powermt unmanage class=hitachi

3. Enter:powermt config

4.5.0 —

Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued)


Resolved in Version


16


221125When performing a Solaris Live Upgrade from Solaris 9 to Solaris 10, you need to manually mount the /usr and /var directories. (When you perform a Solaris Live Upgrade from Solaris 8 to 9, this step is not necessary.)

Manually mount the /usr and /var directories. Refer to the PowerPath 4.5 for Solaris Installation and Administration Guide for more information on the Live Upgrade procedure.

4.5.0 —



Resolved in Version



221084With PowerPath 4.4.0 or later and VxVM 4.1, the command vxdisk list may display multiple entries for the same device. This may occur following a reboot where PowerPath has just been installed or new devices have been mapped or zoned to a host.The issue occurs because PowerPath pseudo device links are unavailable during boot, and VERITAS VxVM 4.1 depends on these links before they can be created. This usually occurs when PowerPath is uninstalled and reinstalled without clearing the knowledge VxVM 4.1 has of these devices. It can also happen if a new LUN is mapped or zoned to a host and VxVM had prior knowledge of this device.

— When upgrading or reinstalling PowerPath, reboot after the initial package remove, if PowerPath requested the reboot. — When duplicate entries are seen, a second reboot will clear the duplicates. The PowerPath pseudo device links will be available during the second reboot. — When mapping/zoning new LUNS to the host, to avoid duplicate entries: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.

4.4.0 —

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

Remove SAN 4.4.5 and install SAN 4.4.6 .

4.5.0 —



Resolved in Version


18


220574R1/R2 boot support in a Symmetrix 5x71 environment does not work when the Symmetrix SPC2 flag is set to ON.

Ensure that the SPC2 flag is set to OFF if your configuration includes R1/R2 boot support and Symmetrix 5x71. By default, this setting is ON.

4.5.0 —

220378In 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.

4.5.0 —

217792When you run the syminq command, sometimes the wrong director may be returned from Symmetrix devices. For example, a device returns FA 13aA when you run syminq, but PowerPath returns FA 13dB. This can occur when the PowerPath cache is not updated after a recent device reconfiguration on the Symmetrix system.

Remove the device from PowerPath and then add it back. Enter:1.powermt remove dev=<device>

2.powercf –q

3.powermt save

4. powermt config

4.1.0 —

216195PowerPath 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.

4.5.0 —

212419VERITAS Volume Manager 4.1 does not support PowerPath pseudo device naming with third-party arrays.

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.

4.4.0 —



Resolved in Version



210941In a Solaris environment with PowerPath 4.4.0 and a Leadville driver, running SYMCLI commands generates the following errors in /var/adm/messages:Oct 12 12:03:53 db026ops qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(1): Link ONLINEOct 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 disappearedOct 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 disappearedOct 12 12:03:58 db026ops qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(2): Loop OFFLINE

Install the appropriate SUN T-patch, or install SAN 4.4.7.Refer to the EMC Knowledgebase solution emc108113 for more information.

4.4.0 —

205610Sun Volume Manager metadatabases created on PowerPath pseudo devices may not persist after upgrading to PowerPath 4.4.

Move pseudo devices to native devices before upgrading.

4.4.0 —

204912After a fresh installation of PowerPath 4.4 on a Solaris 10 host with a valid license connected to a Symmetrix storage system, the load balancing policy is set to "bf" (basic failover) after the host reboots. The policy should be set to "so" (Symmetrix optimized).

Run the following commands before you reboot:powermt set policy=sopowermt save

4.4.0 —

204709Running 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.

4.4.0 —

203121, 203123Rebooting 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.

Ignore the messages. 4.4.0 —



Resolved in Version


20


197626Very infrequently, an admsnap operation (start, stop, etc.) reports the error 0xE10080A3. This error indicates that the specified admsnap operation may not have completed on all of the devices specified on the command line due to an internal operation failing to complete properly to the array. For applications or scripts that rely on the exit status from admsnap, a non-zero exit status is returned to the application or script.

1. Query the CLARiiON storage array using Navisphere, and determine whether the admsnap command completed the operation for all devices specified on the command line. If it did, no 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.

4.3.0 —

180770With third-party arrays in a cluster, reconfiguration reboot does not recover paths that are down at boot.

Use either the boot or reboot command. Do not use the boot -r or reboot -- -r command.

4.3.0 —

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

Ignore this message. The custom settings are loaded.

4.3.0 —



Resolved in Version



175725169443powermt restore restores all paths to third-party arrays when periodic autorestore is set to off. This includes, among others, HPXP and Hitachi Lightning devices.

4.2.0 —

165579Using the powermt unmanage class=hitachi command to unmanage third-party arrays when the host is booted from a pseudo device prevents the system from coming up after you reboot. You see the following message when you unmanage a boot device:WARNING: One or more boot devices have been unmanaged. Update the system configuration settings as appropriate. Cannot remove device that is in use: <emcpowerx>

Before you reboot the host, update the system configuration in the /etc/system and /etc/vfstab files to use native devices.Refer to the PowerPath 4.5 for Solaris Installation and Administration Guide for more information.

4.1.0 —

162224LUNs are trespassed when the HBAs are removed one by one using the powermt remove hba=# command.

4.2.0 —

156582PowerPath installation or removal fails if pkgadd or pkgrm is interrupted.

Reboot the host and then rerun pkgadd or pkgrm.

4.1.0 —

124857Executing emcpreg -f -edit without specifying the PowerPath registration filename (the default is emcp_registration) could cause deletion of the registration file’s parent directory. (The default parent directory is /etc.)For example, if your PowerPath registration file is in the /test directory and you execute the command emcpreg -f /test -edit,you see the following prompt:EMCP registration file is corrupt. Delete it?

If you answer y (yes) to the prompt, /test is deleted.

• If your PowerPath registration file is the default file (/etc/emcp_registration), do not use the -f option with emcpreg.

• Otherwise, be sure to specify the full pathname. Enter:emcpreg -f /directory/filename -edit

• If you neglect to specify the full pathname, answer n (no) to the prompt:EMCP registration file is corrupt. Delete it?

3.0.3 —



Resolved in Version


22


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:

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.

If this software is presentSupport for this array type is 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 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:

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:

◆ 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 this software is presentMultipathing behavior is undefined if you 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 Virtual Array

powermt manage class=hpxp

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 Virtual Array

powermt unmanage class=hpxp


24


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 NotesThis 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.xWhen 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


26

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 NamesYou 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 invalidemcpower0c 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 toVxVM 4.0

After upgrading to VxVM 4.0 from a VxVM 3.5 (or earlier) 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”.


28

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.0When 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 emcpower11s2 auto:sliced disk2 mydg online emcpower12s2 auto:sliced disk3 mydg online emcpower13s2 auto:sliced disk4 mydg online emcpower14s2 auto:sliced disk5 mydg online emcpower15s2 auto:sliced disk6 mydg online emcpower16s2 auto:sliced disk7 mydg online emcpower17s2 auto:sliced disk8 mydg online emcpower18s2 auto:sliced disk9 mydg online emcpower19s2 auto:sliced disk10 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:


30

Technical Notes

# vxdisk list

Output:

DEVICE TYPE DISK GROUP STATUS c6t0d10s2 auto:sliced disk1 mydg online c6t0d11s2 auto:sliced disk2 mydg online c6t0d12s2 auto:sliced disk3 mydg online c6t0d13s2 auto:sliced disk4 mydg online c6t0d14s2 auto:sliced disk5 mydg online c6t0d15s2 auto:sliced disk6 mydg online c6t0d16s2 auto:sliced disk7 mydg online c6t0d17s2 auto:sliced disk8 mydg online c6t0d18s2 auto:sliced disk9 mydg online c6t0d19s2 auto:sliced disk10 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.1If 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 NamesPowerPath 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 NamesPowerPath 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:

HP StorageWorks HSG80PowerPath 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:

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:

Command View EVA name PowerPath name

A-1 A-0

A-2 A-1

B-1 B-0

B-2 B-1

HSG Element Manager name PowerPath name

Bottom-1 A-0

Bottom-2 A-1

Top-1 B-0

Top-2 B-1


32

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-5-fibre-channel-port-name="50001fe15000b029";hba0-SCSI-target-id-6-fibre-channel-port-name="50001fe15000b02c";hba0-SCSI-target-id-7-fibre-channel-port-name="50001fe15000b02d";

hba1-SCSI-target-id-4-fibre-channel-port-name="50001fe15000b028";hba1-SCSI-target-id-5-fibre-channel-port-name="50001fe15000b029";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 Bindingstarget4_hba="fcaw0";target4_wwpn="50001fe15000b028";target5_hba="fcaw0";target5_wwpn="50001fe15000b02d";target6_hba="fcaw1";target6_wwpn="50001fe15000b029";target7_hba="fcaw1";target7_wwpn="50001fe15000b02c";

2. Add the following to sd.conf:

# EVA5000name="sd" class="scsi" target=4 lun=0;name="sd" class="scsi" target=4 lun=1;name="sd" class="scsi" target=4 lun=2;name="sd" class="scsi" target=4 lun=3;name="sd" class="scsi" target=4 lun=4;name="sd" class="scsi" target=4 lun=5;name="sd" class="scsi" target=4 lun=6;name="sd" class="scsi" target=4 lun=7;

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

DocumentationThis section provides a list of the documentation that supports PowerPath for Solaris.

PowerPathDocumentation

The following table lists the PowerPath documentation set; all 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.

RelatedDocumentation

If your environment includes Symmetrix storage systems, refer also 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.

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



34

Software Media, Organization, and Files

Software Media, Organization, and FilesThis 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.

InstallationRefer 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 aPrevious Revision

Follow the instructions in the section entitled Upgrading to PowerPath 4.5 in Chapter 1, "Installing PowerPath," of PowerPath 4.5 for Solaris Installation and Administration Guide.


Troubleshooting and Getting Help

Troubleshooting and Getting HelpFor 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.



36

Troubleshooting and Getting Help

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.


Documents

EMC Powerpath 300 002 908