EMC PowerPath for Solaris Version 4.4.0 Release Notes · PDF fileEFI disk label PowerPath 4.4.0 provides multipathing support for Extensible Firmware Interface (EFI) disk labels with

These release notes contain supplemental information about EMC PowerPath, version 4.4.0. Topics include:

◆ Product Description ............................................................................. 2◆ New Features and Changes ................................................................ 2◆ Environment and System Requirements .......................................... 3◆ Known Problems and Limitations ................................................... 13◆ Technical Notes ................................................................................... 27◆ Documentation ................................................................................... 33◆ Software Media, Organization, and Files........................................ 35◆ Installation........................................................................................... 36◆ Troubleshooting and Getting Help .................................................. 37

EMC PowerPathfor SolarisVersion 4.4.0

Release NotesP/N 300-002-311

Rev A04

December 06, 2005

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, and 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.4.0 for Solaris adds support for the following new and enhanced features:

◆ Solaris 10

PowerPath 4.4.0 is supported with the Solaris 10 operating system.

◆ EFI disk label

PowerPath 4.4.0 provides multipathing support for Extensible Firmware Interface (EFI) disk labels with Solaris 9 and 10 systems.

◆ Sun Cluster 3.x

PowerPath 4.4.0 adds support for Sun Cluster 3.x with HP StorageWorks EVA 3000 and EVA 5000 arrays.

◆ VCS 4.0

PowerPath 4.4.0 adds support for VERITAS Cluster Server (VCS) 4.0 with HP StorageWorks EVA 3000 and EVA 5000 arrays.

◆ AX100

PowerPath 4.4.0 provides full AX100 support with or without a PowerPath license.

EMC PowerPath for Solaris Version 4.4.0 Release Notes

Environment and System Requirements

Discontinued Features in PowerPath 4.4.0Please 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 and for the next releases of PowerPath for AIX and 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.

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.

CAUTION!Before you perform a fresh installation of a licensed version of PowerPath 4.4, you must manually add the emcp_registration file to the /etc directory. The emcp_registration file is the registration database where the emcpreg command stores license keys.

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

EMC PowerPath for Solaris Version 4.4.0 Release Notes 3


4


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 in the EMC Support Matrix and quarterly in the EMC host connectivity guides. In the event of discrepancies, information in the EMC Support Matrix or host connectivity guide takes precedence over the information in these sections.



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

The following table shows minimum disk space requirements for Solaris.

Supported HBAs: PowerPath 4.4.0 for Solaris with Third-Party Storage SystemsThis section describes the HBA models and driver versions supported for PowerPath 4.4.0 for Solaris with third-party storage systems. The section also describes changes to the default driver configuration files required by PowerPath 4.4.0 for Solaris.

Consult the EMC Support Matrix for HBA models and driver versions supported with Symmetrix and CLARiiON systems.

Solaris: Supported Operating Systems

Supported OS Sun patches required

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

Sparc Solaris 8 (32 and 64 bit) 108528-29117000-05117350-19108974-42109885-16 (X6541 HBA only)109657-10 (X106A2 & X1065A HBAs only)

Sparc Solaris 9 (32 and 64 bit) 112233-12112834-04113277-26117171-15

Sparc Solaris 10 (32 and 64 bit)

Solaris: Disk Space Required

File System or Directory Minimum Space Requirements

Installation directory (the default is /opt) 8 MB

Root file system 5 MB

/usr 1 MB


6


Supported HBAs: IBM ESS, Hitachi Lightning, HP xp Systems

PowerPath 4.4.0 for Solaris has been tested and qualified for use with IBM ESS, Hitachi Lightning, and HP xp storage systems using the HBA models and driver versions shown in the following table.

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

Manufacturer Model Driver Versions Supported with Arrays

IBM ESS Hitachi Lightning HP xp Arrays

QLogic QLA 2310/2340 QLogic V4.13 ✔ ✔ ✔

SG-XPCIFC2-QF2 SUNWqlcSUNWqlcx 11.8.0SUNWqlcx 11.9.0

✔ ✔ ✔

Emulex LP8000LP9000LP9002LDCLP10000

EMC 5.02cEMC 6.01f

✔ ✔ ✔

LP9802 EMC 5.02cEMC 6.01f

✔



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

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

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 down load the Platform Kit from the HP website.

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

Manufacturer Model Driver Versions

JNI/AMCC FC64-1063 CPQ V2.5.9.03

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


8


HBA Driver Settings

The following table describes changes to the default driver configuration files required by PowerPath 4.4.0 for Solaris with third-party storage systems.

Solaris: HBA Driver Settings—Third-Party Storage Systems

HBA Driver ParameterDefault Setting

PowerPath Setting

Setting Required for

JNI/AMCC FCA failover 0 60 All third-party systems

scsi_probe_delay 1500 3500 (fcaw.conf)5000 (fca-pci.conf)

HP StorageWorks EVA, EMA, MA systems

JNI/AMCC JNIC FailoverDelay 180 60 All third-party systems

JNI/AMCC JNIC146

FailoverDelay 120 60 All third-party systems

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



Heterogeneous Connections

PowerPath 4.4.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◆ LP9002LDC◆ LP10000

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 ArraysFor PowerPath 4.4.0 for Solaris to fully interoperate with VERITAS Volume Manager (VxVM) on HP xp arrays, you must install the VERITAS HPXP Array Support Library (ASL) after you install VxVM. You can download the HPXP ASL from the VERITAS website.

Storage Array Configuration

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.

For information about LUN configuration and limits see the EMC host connectivity guide, available on the Powerlink website.

Microcode versions tested Paths per device Boot support

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


10


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 and FC-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.4.0 for Solaris.

CLARiiONStorage System

Minimum SupportedFLARE Version

AX100AX100SC

02.16

CX200CX300CX400CX500CX600CX700

02.07

FC4700 8.51.10




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

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

ModelQualified Array code/firmware


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

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


12


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

Connectivity Requirements

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.

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 7, 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 32 Not supported.

HP StorageWorks Enterprise Modular

ACS 8.7-3

HP StorageWorks MA8000/EMA12000


Known Problems and Limitations

Known Problems and LimitationsThis section describes the known problems and limitations in PowerPath 4.4.0 for Solaris.

Known Problems The following table shows known problems in PowerPath 4.4 for Solaris.

Known Problems in PowerPath Version 4.4.0: Solaris

Description WorkaroundFound inVersion

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 requested by PowerPath.— When duplicate entries are seen, a second reboot clears 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

(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, 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 —


14


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.4.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 —

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 Primus case emc108113 for more information.

4.4.0 —

206065On Solaris 10, renaming a PowerPath pseudo device leaves the original device name in an inconsistent state. If a subsequent iteration of the emcpadm getfreepseudos command encounters that device name, it returns an error.

Use the emcpadm getusedpeudos command to list used devices, and then select a device that is not included in the list as the free device.

4.4.0 —

Known Problems in PowerPath Version 4.4.0: Solaris (continued)


Resolved in Version



205723Upgrading to PowerPath 4.4 from version 4.x on a host connected to third-party arrays places all previously unmanaged storage classes under PowerPath control (that is, managed).

Run the powermt unmanage command to exclude specific storage classes from PowerPath control.

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 —

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.

Run the powermt restore command. All paths return to the alive state (other than the path that is supposed to be dead.)

4.4.0 —

205055After upgrading to PowerPath 4.4 from version 3.0.x on a host in a Sun cluster that includes systems configured wit VxVM, all third-party storage classes are unmanaged (when they should be managed by default).

Run the powermt manage command to place third-party storage classes under PowerPath control.

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 —

204525The PowerPath installation may return a warning that a required patch is not installed on the host when a patch that supersedes the indicated patch is already installed on the host.

Ignore the warning after making sure that the patch or its superseding patch is installed on the host.

4.4.0 —

204505When upgrading from PowerPath 3.x to 4.4, the user is not given the option of preserving the current configuration.

Refer to Upgrading from PowerPath 3.0.x on page 27 for a workaround.

4.4.0 —



Resolved in Version


16


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

Ignore the messages. 4.4.0 —

203121Rebooting a PowerPath host that is a node in a Sun 3.1 cluster and is also is connected to EVA devices generates path dead/alive messages.

Ignore the messages. 4.4.0 —

200660If you run the powermt remove dev=all command and the last path to be removed is dead, the command appears to succeed. However, after restoring the paths, the file system mounted on the emcpower device is corrupt.

Use the following sequence of commands to remove paths:powermt remove dev=<path>powermt remove dev=allpowermt remove hba=<hba>powermt remove hba=all

4.4.0 —

190762For the Sun qlc adapter, the format of the native device name is different from the traditional c*t*d* format. This makes the Powerpath 4.4.0 powermt display command output difficult to read.

4.4.0 —

193421In a Symmetrix environment, if you install a PowerPath patch with a valid license and then remove PowerPath, the load balancing and failover policy defaults to bf (basic failover) instead of so (Symmetrix optimization).

Reset the policy to so. 4.3.1 —



Resolved in Version



197626 (DIMS 116808)Very 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 —

186235, 185281powervxvm init corrupts the VxVM rootdg created on external devices managed by PowerPath.

Use powervxvm install instead of powervxvm init.

4.3.0 —

186230pkgrm may succeed in removing PowerPath but fail to remove some PowerPath modules, resulting in the following error message:can't unload the module: Unknown error

Unload of modules failed...

4.3.0 —



Resolved in Version


18


186033vxddladm rmforeign succeeds in undefining emcpower devices that are part of a VxVM DG while the DG is online (imported state) and volumes are mounted.Once the VxVM DG is deported, you cannot import it unless VxVm 4.0 defines the same emcpower devices again using powervxvm or the vxddladm -n l 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 —

182916In a VCS cluster, removing all adapters on a node using the powermt remove dev=all command results in cluster fault during failover to that node.

4.3.0 —

179087The powermt manage class command may return an initialization error if multiple instances of the command are running simultaneously.

Rerun the command. 4.3.0 —

175725powermt restore restores all paths to third-party arrays when periodic autorestore is set to off.

4.2.0 —

174802The command powervxvm install fails to initialize emcpower devices on VERITAS VxVM 4.0 and returns the following message:vxdisk -f init emcpower0c VxVM vxdisk ERROR V-5-1-5433 Device emcpower0c: init failed: Device path not valid.

4.2.0 —

169443HP xp and Hitachi Lightning devices are auto-restored when periodic autorestore is set to off.

4.2.0 —



Resolved in Version



167621Unmanaging a class when a device has just been added results in "unmanage incomplete" even if no I/O is running to the device.

Execute another powermt unmanage class= command. This causes the class to be successfully unmanaged. You can then manage and unmanage the class repeatedly without further problems.

4.2.0 —

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

4.2.0 —

165614Due to changes in licensing, third party arrays use the same license keys used to enable PowerPath Symmetrix and CLARiiON features. However, the error messages have not been updated to specify that a license is missing for a third party array.

Contact your EMC representative to obtain a valid license.

4.1.0 —

165579Using the powermt unmanage class=hitachi command to unmanage Hitachi Lightning arrays when the host is booted from a Hitachi pseudo device prevents the system from coming up again.

At the ok prompt:1. Run the command printenv

boot-device, and note the hardware path.

2. If the hardware path is aliased, run the devalias command.

3. Run the boot cdrom -s command.

After the system boots up from the CD-ROM:4. Run the fsck command.5. Run the following command: mount

/dev/dsk/c#t#d#s0 /mnt

6. Change to the /mnt/etc directory.7. In the /etc/system file:

Change emcpower to c#t#d#s#

Delete the rootdev definition8. Change the file system in

/etc/vfstab to convert pseudo devices to native devices.

9. Reboot.

4.1.0 —



Resolved in Version


20


165510You may see the messageWarning: forceload drv/ssd failed

even though the /kernel/drv/ssd driver is available.

Ignore the message. 4.1.0 —

160126The powermt manage class command takes an unusually long time to complete when all paths to the Hitachi Lightning or HP xp array are physically disconnected.

4.1.0 —

156938Due to a Sun limitation, the partition operation fails if you execute format on a specific pseudo device, for example, if you run the following command:format /dev/rdsk/emcpower15c

Do one of:• Run format using relative paths:

Change to the directory /dev/rdisk and then run format specifying the pseudo device.

• Run format and choose the device from the devices listed.

4.1.0 —

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

Reboot the host and then rerun pkgadd or pkgrm.

4.1.0 —

138235When you install PowerPath for the first time (that is, no version of PowerPath has ever been installed on the host), you see the following message:Warning: unable to open the configuration file, /etc/powermt.custom

You can safely ignore this warning. 4.0.0 —



Resolved in Version



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 —

132422 Installing or upgrading PowerPath in a Sun Cluster 2.2 can be slow unless cluster services are either running on all nodes or stopped on all nodes.

Before installing or upgrading PowerPath, stop cluster services on all nodes in the cluster.

3.0.0 —



Resolved in Version


22


Resolved Problems The following table shows resolved problems that were reported as known problems in earlier versions of PowerPath for Solaris.

Resolved Problems in PowerPath Version 4.4.0: Solaris

DescriptionFound inVersion

Resolved in Version

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

172405When a path to a third-party storage system fails, the number of errors displayed by the powermt display class= command may not be accurate.

4.2.0 4.4.0

167046If you specify symm or clariion as the class, the powermt unmanage class= command fails with the return value of 0 instead of 1.

4.2.0 4.4.0

167022The powermt manage and powermt unmanage commands return 0 instead of 1 when executed without the class or dev option specified.

4.2.0 4.4.0

185607Running vxfentsthdw in a Symmetrix environment may cause PowerPath to crash.

4.3.0 4.3.1

184571PowerPath takes too long to initiate a LUN trespass when a CLARiiON SP hangs. The failover times are affected by the sd_retry_count and sd_timeout values. The default values can be tuned depending upon the customer installation.

3.0.4 4.3.1

175417When booting off a pseudo device in an R1/R2 configuration, if you add a new device and then run powermt load, you see the following error message:Error occurred loading saved driver state from file /etc/powermt.custom

Ignore the message. powermt load completes successfully.

4.2.0 4.3.0



175313Upgrading in a cluster will hang if the /etc/rem_name_to_major file contains a different major number for the PowerPath driver, emcp, than that specified by the user during the upgrade. Normally this would not happen, since the same major number would be specified during a cluster node upgrade. However, if a system is being upgraded and brought into a cluster simultaneously, with no intervening reboot, /etc/rem_name_to_major and the installation can disagree about the major number for emcp, and this hang can occur.

4.2.0 4.3.0

175295You may see the following error message during reboot of a cluster node, even when no paths are dead:Info: Not all paths to vol lun_ID are dead

4.2.0 4.3.0

175081When installing PowerPath on a native boot device on a third-party array, you see the following message:global:version:4.2.0

You can ignore the message.

4.2.0 4.3.0

145345Rebooting a node in a Sun Cluster 3.x may cause an unnecessary trespass. Any nonpersistent Snapshot sessions in progress with LUNs that are part of the cluster will be terminated when the trespass occurs.

4.0.0 4.3.0

136057Some HBA drivers use the ssd driver, instead of the sd driver, for attached devices. (For example, QLogic and socal drivers use the ssd driver.) When the ssd driver is used for CLARiiON or Symmetrix devices, the /etc/system file must contain the statement forceload: drv/ssd.

4.0.0 4.1.1

141589You may not be able to boot off a native path to a Symmetrix or CLARiiON device when the instance number of the native path is higher than 4096.

Note: To obtain the instance number:

1. Obtain the minor number using the commandls -lL /dev/dsk/cxtxdxs0.

2. Divide the minor number by 8.

4.0.0 4.1.0

121862Installing or removing PowerPath 4.x when the system is booted from the CD-ROM is not supported.

4.0.0 4.1.0

Resolved Problems in PowerPath Version 4.4.0: Solaris (continued)


Resolved in Version


24


Limitations PowerPath 4.4.0 for Solaris has the following limitations:

◆ PowerPath 4.4.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.4.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:

211620Installing VERITAS Volume Manager on the same host as PowerPath 4.1.0 or later may cause the system to panic. The location of the ssd driver within the /etc/system file may be the cause; the ssd driver must be initialized before the emcp driver. To resolve this issue, update the /etc/system file so that the line forceload: drv/ssd appears before forceload: drv/emcp.

4.1.0 —

Resolved Problems in PowerPath Version 4.4.0: Solaris (continued)


Resolved in Version

If this software is presentSupport for this array type is disabled in PowerPath

HDLM Hitachi Lightning

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.4.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.4.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 IBM ESS, Hitachi Lightning, 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


26


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:

Error: 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.

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.4.0 for Solaris Pseudo Names on page 29 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 describes:

◆ Upgrading from PowerPath 3.0.x

◆ Upgrading from PowerPath 4.0.x on Symmetrix systems

◆ VxVM 4.0 and PowerPath 4.4.0 for Solaris pseudo names

◆ HP StorageWorks controller and port names

◆ Removing HP StorageWorks Secure Path

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

In the vast majority of cases, upgrading from PowerPath 4.0.x to PowerPath 4.4.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.4.0. Customer 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.4.0 without contacting Customer Support, the upgrade to PowerPath 4.4.0 will stop with the following message:


28

Technical Notes

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.4 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.4 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.4 Release Notes.

If this happens, we strongly recommend that you:

1. Remove PowerPath 4.4.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.4.0 for Solaris 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

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”.

CAUTION!Do not initialize the emcpower disks if they currently contain VxVM volumes.


30

Technical Notes

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.

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.

PowerPath Documentation

The following table lists the PowerPath for Solaris 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.

Related Documentation

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

To obtain the latest versions of CLARiiON CX-series and FC-series documentation, log in to the Powerlink website (http://powerlink.emc.com). Then click Support > Document Library.

Part Number Name

300-002-308 PowerPath Product Guide

300-002-309 PowerPath for Solaris Installation and Administration Guide

300-002-310 PowerPath Quick Reference

300-002-311 PowerPath for Solaris Release Notes




34

Documentation

◆ 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 FilesThis section describes the contents of the PowerPath 4.4.0 for Solaris CD.

Media The PowerPath 4.4.0 for Solaris software is distributed on a CD, P/N 053-001-383.

Organization The PowerPath 4.4.0 for Solaris CD has the following structure:

◆ /UNIX/SOLARIS/EMCPOWER — Contains all files in the PowerPath package.

◆ /UNIX/SOLARIS/EMCpower.SOLARIS.4.4.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.4 for Solaris Installation and Administration Guide.


36

Installation

InstallationRefer to the PowerPath 4.4 for Solaris Installation and Administration Guide, P/N 300-002-309, for complete instructions on installing PowerPath.

For the New User Follow the instructions in the section entitled Installing PowerPath 4.4 in Chapter 1, “Installing PowerPath”, of the PowerPath 4.4 for Solaris Installation and Administration Guide.

Upgrading from a Previous Revision

Follow the instructions in the section entitled Upgrading to PowerPath 4.4 in Chapter 1, "Installing PowerPath," of PowerPath 4.4 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:


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.



38

Troubleshooting and Getting Help

Copyright © 2005 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.

Trademark Information


EMC PowerPath for Solaris Version 4.4.0 Release Notes · PDF fileEFI disk label PowerPath 4.4.0 provides multipathing support for Extensible Firmware Interface (EFI) disk labels with

Documents