300-011-782

These release notes contain information about features, system requirements,and limitations in PowerPath Version 5.6 and its minor releases for Linux.

◆ Revision history .................................................................................... 2◆ Product description.............................................................................. 3◆ New features and changes .................................................................. 4◆ Fixed problems ..................................................................................... 8◆ Environment and system requirements............................................ 8◆ Known problems and limitations .................................................... 17◆ Technical notes.................................................................................... 25◆ Documentation ................................................................................... 35◆ Software media, organization, and files.......................................... 38◆ Installation........................................................................................... 39◆ Troubleshooting and getting help.................................................... 41

EMC® PowerPath® Family for LinuxVersion 5.6 and Minor Releases

Release NotesP/N 300-011-782

Rev A07

March 07, 2012

1

2

Revision history

Revision historyThe following table presents the revision history of this document.

Revision Date Description

A01 April 4, 2011 First release of this document for PowerPath 5.6 forLinux.

A02 June 13, 2011 Updated the “New features and changes” section withthe following:• PowerPath Viewer support information• VPLEX 5.0 support information

A03 September 30, 2011 Updated for PowerPath 5.6 P01 on Oracle Linux andOracle VM 3.0 Server.• Updated the “New features and changes” section

on page 4.• Updated the “Support changes” section on page 7.• Updated the “Support Summary” section on

page 10.• Updated the “Supported Linux

distributions”section on page 13.• Added the “PowerPath and VMAX/VMAXe series

devices” section on page 26.

A04 November 16, 2011 Depreciation announcement of support for Linux32-bit operating systems. See “Support changes” onpage 7.

A05 December 16, 2011 Release of Linux 5.6 P02. See “PowerPath 5.6 P02”on page 5.

A06 December 28, 2011 Updated the “Support Summary” table on page 10with VPLEX and Geosynchrony support.

A07 March 07, 2012 Removed Oracle VM 3.0 Server related information.

EMC PowerPath Family for Linux Version 5.6 and Minor Releases Release Notes

Product description

Product descriptionThe EMC® PowerPath® family of products includes:

◆ PowerPath multipathing software for physical environments, asdescribed in “PowerPath multipathing” on page 3.

◆ PowerPath Migration Enabler®, as described in “PowerPathMigration Enabler” on page 3.

◆ PowerPath Encryption with RSA®, as described in “PowerPathEncryption with RSA” on page 4.

Your license type determines the extent PowerPath functionality isavailable. PowerPath Migration Enabler for Encapsulation, HostCopy, Open Replicator, and TimeFinder/Clone® require a separatelicense key. PowerPath Encryption with RSA requires a separatelicense key. If you have questions about your license, contact yourEMC Customer Support Representative.

PowerPath multipathingPowerPath is a server-resident software solution designed to enhanceperformance and application availability. PowerPath combinesautomatic load balancing, path failover, and multiple path I/Ocapabilities into one integrated package.

PowerPath enhances application availability by providing loadbalancing and automatic path failover and recovery functionality.

PowerPath supports servers, including cluster servers, connected toEMC and third-party arrays.

PowerPath Migration EnablerEMC PowerPath Migration Enabler is a host-based migration toolthat allows you to migrate data between storage systems, or in thecase of EMC TimeFinder/Clone, between devices within an EMCSymmetrix® storage system. PowerPath Migration Enabler uses thePowerPath filter driver, in conjunction with an underlyingtechnology, to provide nondisruptive or minimally disruptive datamigrations.

3EMC PowerPath Family for Linux Version 5.6 and Minor Releases Release Notes

4

New features and changes

The underlying technologies for Migration Enabler are EMCEncapsulation, EMC Open Replicator for Symmetrix, EMC HostCopy (host-based copy), and EMC TimeFinder/Clone. Migrationscan be non-disruptive when pseudo device names are used. Whennative names are used, a minor disruption may be necessary toreconfigure the applications to use the target native name. PowerPathMigration Enabler works independently of PowerPath multipathing.However, PowerPath must be installed. The EMC PowerPathMigration Enabler User Guide provides additional information.

PowerPath Encryption with RSAPowerPath Encryption with RSA is host-based software distributedwith the PowerPath package and requiring a separate productlicense. PowerPath Encryption provides the following securitybenefits:

◆ Ensures the confidentiality of data on a disk drive that isphysically removed from a data center.

◆ Prevents anyone who gains unauthorized access to the disk fromreading or using the data on that device.

PowerPath Encryption uses strong encryption protocols to safeguardsensitive data on disk devices. It transparently encrypts data writtento a disk device and decrypts data read from it. The EMC PowerPathEncryption with RSA User Guide provides additional information.

RSA Key Manager The RSA Key Manager provides key management and automaticprovisioning of encryption keys for PowerPath hosts. The RSA KeyManager consists of two main elements: a central RKM appliance anddistributed key manager clients (integrated into the PowerPath host).The RSA Key Manager Appliance Operations Guide provides additionalinformation on the RKM appliance.

New features and changesThis section describes new features and changes by product, asfollows:

◆ “License ordering and activation” on page 5

◆ “PowerPath multipathing” on page 5

◆ “PowerPath Migration Enabler” on page 7



◆ “PowerPath Encryption with RSA” on page 7

◆ “Support changes” on page 7

Note: Earlier versions of PowerPath for Linux may be qualified with theproduct versions listed in this section. The E-Lab InteroperabilityNavigator™ provides complete, up-to-date qualification information.

License ordering and activationEffective February 15, 2011, instead of the physical Right To Use(RTU), the default delivery method for PowerPath licenses iselectronic. An electronic License Authorization Code (LAC) is sent byemail in order to redeem the license key on the Powerlink Licensingportal. This does not affect upgrades because PowerPath retainsexisting license information.

Physical RTU cards are still available as an option. EMC GlobalSupport, at 1-800-svc4emc or 1-800-782-4362, can provide moreinformation. The EMC PowerPath Family Electronic License OrderingProcess Technical Notes, available on Powerlink, provides moreinformation about the PowerPath license electronic ordering process.

PowerPath multipathing

PowerPath 5.6 P02 PowerPath 5.6 P02 is released to support Oracle Linux 5.x UEK kernelon x86_64 only. Other Linux platforms are not supported.

PowerPath 5.6 P02 is a full-package installation.

◆ Boot from SAN support is not available on Oracle Linux 5.xrunning UEK kernel.

PowerPath 5.6 P01 PowerPath 5.6 P01 is released to support only Oracle Linux with UEKkernels on x86_64. Other Linux platforms are not supported.

PowerPath 5.6 P01 is a full-package installation that includes supportfor the following features:

◆ Support for Oracle Linux 5.6, 6.0, and 6.1 (UEK kernels only)


6


Note: Before installing PowerPath 5.6 P01 on a host, ensure thatdm-multipath is disabled on the host. Otherwise, system instability couldoccur. EMC recommends that you blacklist all non-local devices on a host onwhich PowerPath will be installed; this action enables multipathing on thosedefault devices.

◆ Support for Boot from SAN on Oracle Linux 6.0 and 6.1.

The Boot from SAN support is not available on Oracle Linux 5.xrunning UEK kernel.

PowerPath 5.6 PowerPath 5.6 is released to support only the Red Hat, Asianux, andOracle Linux platforms. Other Linux platforms such as SUSE are notsupported.

PowerPath has the following new features:

◆ Support for EMC Symmetrix VMAXe™ arrays with Enginuity™version 5875.198.148.e.

◆ Support for VNX™ Operating Environment (OE) arrays seriesmodels

◆ Support for VNXe™ Operating Environment (OE) arrays seriesmodels

◆ Support for RHEL 6.0 (x86, x86_64), and RHEL 5.6 (x86, x86_64)

◆ Support for Symmetrix Enginuity 5875 support

◆ Support for Invista 2.4 SP1

◆ Support for HP StorageWorks Enterprise Virtual Array 8400

◆ Support for Open-FCoE initiator in RHEL 6.0

Note: The Boot from SAN option is an exception for the Open-FCoE featuresupport.

◆ Cluster support:

• Support for Veritas Cluster Server 5.1, 5.1 SP1, 5.1 SP1 PR2

• Support for Veritas Storage Foundation 5.1 SP1

◆ Support for VPLEX 5.0 with GeoSynchrony 5.0

◆ Support for PowerPath Viewer.

Note: PowerPath Viewer supports only RHEL and SLES. Therefore, it is notavailable on PowerPath 5.6 P01, which supports only Oracle Linux platforms.



PowerPath Migration Enabler

PowerPath 5.6 P02 ◆ Support for Oracle Linux 5.7 UEK kernel on x86_64 only

PowerPath 5.6 P01 ◆ Support for Oracle Linux 5.6, 6.0, and 6.1 UEK kernels

PowerPath 5.6 ◆ Support for RHEL 6.0 (x86, x86_64), and RHEL 5.6 (x86, x86_64)

PowerPath Encryption with RSA

PowerPath 5.6 P02 PowerPath Encryption with RSA is not supported.

PowerPath 5.6 P01 PowerPath Encryption with RSA is not supported.

PowerPath 5.6 PowerPath Encryption with RSA has the following new features:

◆ Support for RHEL 5.6 (x86_64) and RHEL 6.0 (x86_64)

Support changesThis section includes changed behavior, end-of-life announcements,and other support changes.

◆ Operating System support: PowerPath 5.6 P01 supports OracleLinux (UEK kernels only). It does not support Red Hat compliantkernels in Oracle Linux 5.6, 6.0, and 6.1.

Deprecations◆ PowerPath 5.6 and minor releases is the last version of PowerPath

for Linux to include qualified support for 32-bit operatingsystems, and subsequent PowerPath for Linux releases will notsupport it. Earlier PowerPath for Linux versions will continue tosupport 32-bit operating systems.

◆ PowerPath 5.5 is the last version to support IA64 and PPC64.Earlier PowerPath for Linux versions will continue to supportthem.

◆ PowerPath 5.5 is the last version to support Veritas StorageFoundation 4.1. Earlier PowerPath for Linux version willcontinue to support it.


8

Fixed problems

Fixed problemsThis section lists fixed problems by product, as follows:


PowerPathmultipathing

Table 1 on page 8 shows fixed problems in PowerPath multipathing.

Environment and system requirementsThis section lists interoperability and host configuration informationnot found in other sources, and it provides references where you canfind additional information.

This section includes the following topics:

◆ “E-Lab Interoperability Navigator” on page 9

◆ “Support Summary” on page 10

◆ “Connectivity requirements” on page 15

◆ “PowerPath Migration Enabler support” on page 15

Table 1 PowerPath multipathing: fixed problems

DescriptionFound inVersion

Fixed inVersion

384897On RHEL 5.3 server (x86_64), upgrading PowerPath in a boot-from-SAN configuration showserror messages.

5.3 5.6 P01

376255emcp_mond always starts without -S option even when snmpd is configured on the RHEL host.

5.6 5.6 P02

358815, 359057, 361734Upgrading PowerPath directly from versions prior to 5.1.x and earlier to version 5.3 SP1 P02fails. The upgrade fails because PowerPath Linux 5.3 SP1 P02 uses the powermt versionformat=legacy command that is not available on older versions.

5.3 SP1 P02 5.6

342843Starting PowerPath Linux 5.3 SP1 P01 HF01 b001 throws a warningabout an extra line in /etc/modprobe.conf.pp. The warning is: modprobe: WARNING:/etc/modprobe.conf.pp line 7: ignoring bad line startingwith 'ffffffff80154d70

5.3 SP1 5.6


Environment and system requirements

E-Lab Interoperability NavigatorFor interoperability information, such as information about thehardware, software, and networked storage components that aretested and compatible with both EMC storage systems andthird-party storage systems, refer to the E-Lab InteroperabilityNavigator, available on the Powerlink website. It also includesinformation about supported host models, operating systemrevisions, host bus adapters, and connectivity devices.

Note: The information in E-Lab Interoperability Navigator takes precedenceover the information in this release notice in case of inconsistency.

The E-Lab Interoperability Navigator is available in two formats:

◆ The E-Lab Interoperability Navigator link is a web-based,searchable database of configuration information. SelectSoftware Support Wizard to view support information forPowerPath and EMC arrays.

◆ The PDFs and Guides tab (within E-Lab InteroperabilityNavigator) lets you view support information in Adobe PDFformat. Use this format to view support information forPowerPath and third-party arrays.


10


Support SummaryTable 2 on page 10 summarizes support for PowerPath, PowerPathMigration Enabler, and PowerPath Encryption with RSA.

Table 2 Support summary (page 1 of 3)

Supportcategory Technology PowerPath Migration Enabler PowerPath

Encryption1

Clusterenvironments

Veritas Cluster Server (VCS)2 Yes Yes

Note: PowerPathMigration EnablerUser Guide providesdetails of a VCSenvironment and themigration procedure.

Yes

File systemsEXT2, EXT3EXT4 (RHEL 6.0, and Oracle Linux 6.0 and 6.1 only)

Yes Yes Yes



Hostoperatingsystems

RHEL 5.0 to 5.4 Yes Yes No

RHEL 5.5 to 5.6 Yes Yes Yes

RHEL 6.0 Yes Yes

Note: Native devicesare not supported.

Yes

Asianux 3.0 GM, SP1, SP2, SP3 Yes Yes No

Oracle Linux 5.1–5.5 Yes Yes No

Oracle Linux3 5.6

Note: PowerPath 5.6 P01 only.

Yes Yes


No

Oracle Linux3 5.7


Yes Yes


No

Oracle Linux3 6.0 and 6.1


Yes Yes


No

Host softwareSolutions Enabler 6.5.3 or later for Open Replicator Yes Yes N/A

Solutions Enabler 6.5.3 or later for TimeFinder/Clone

Minimumrequired diskspace

120 MB

Note: This disk space is the total value required forPowerPath, Migration Enabler, and PowerPathEncryption.

Yes Yes Yes



Encryption1


12


Physical andVirtualStoragesystems

EMC storage systems2 Yes Yes Yes

EMC Invista 2.3 and later Yes Yes Yes

EMC VPLEX with GeoSynchrony 5.0.xEMC VPLEX with GeoSynchrony 4.x

Note: The information in EMC Simple Support Matrixfor EMC VPLEX and GeoSynchrony, available onPowerlink, takes precedence over the information in thisrelease notice.

Yes Yes4 Yes

Third-party storage arrays2 Yes Yes4 Yes

Protocol

Fibre Channel Yes Yes Yes

iSCSI Yes Yes4 Yes

FCoE Yes Yes4 Yes

RKM

RSA Key Manager (RKM) Appliance version 2.7 SP1• Requires RSA hot fix KMA-876 to support

multi-clusters across distance.• RKM server supports 1000 Identities, which is

equivalent to PowerPath hosts.

N/A N/A Yes

Virtuallyprovisioned(thin) devices

Thin device support requires:• Symmetrix Enginuity Operating Environment 5773

or later.• VNX OE and CLARiiON with FLARE version

04.28.000.5.5xx or later and the Virtual Provisioningenabler.

Yes Yes Yes

Volumemanagers

Veritas Volume Manager (VxVM)2

Note: Not supported on Oracle Linux 5.6, 6.0, and 6.1.

Yes Yes Yes

Linux LVM2 Yes Yes Yes

1. x86_64 only

2. Refer to the EMC E-Lab Interoperability Navigator for details

3. Only the UEK kernels are supported

4. Host Copy only



Encryption1



Supported Linuxdistributions

Table 3 on page 13 provides a quick overview of each supportedkernel and its corresponding PowerPath release.

Kernel support Table 4 on page 13 lists the supported Linux kernels.

Table 3 Supported Linux distributions

PowerPathRelease

RHEL4.2 -4.8

RHEL5.0 -5.6

RHEL6

SLES 10SP2 - 10SP4

SLES 11 -11 SP1

OracleLinux5.6

OracleLinux5.7

OracleLinux6.0 - 6.1

5.6 P02 No No No No No No Yes No

5.6 P01 No No No No No Yes1 No Yes1

5.6 No Yes Yes No No No No No

1. UEK kernels only.

Table 4 PowerPath 5.6 supported kernels (page 1 of 2)

Distribution1 Architecture Minimum kernel and kernel type

RHEL 6 x86 kernel- 2.6.32-71.el6.i686

x86_64 kernel- 2.6.32-71.el6.x86_64

RHEL 5.6 x86 kernel-2.6.18-238.el5.i686kernel-xen-2.6.18-238.el5.i686kernel-PAE-2.6.18-238.el5.i686

x86_64 kernel-2.6.18-238.el5.x86_64kernel-xen-2.6.18-238.el5.x86_642

RHEL 5.5 x86 kernel-2.6.18-194.el5.i686kernel-xen-2.6.18-194.el5.i6862

kernel-PAE-2.6.18-194.el5.i686

x86_64 kernel-2.6.18-194.el5.x86_64kernel-xen-2.6.18-194.el5.x86_64

RHEL 5.4 x86 default-2.6.18-164.el5PAE-2.6.18-164.el5xen-2.6.18-164.el5

x86_64 default-2.6.18-164.el5xen-2.6.18-164.el5


14


Storage system configurationBefore you install PowerPath, set up connections between a storagesystem and a host. The EMC Host Connectivity Guide for Linuxdescribes the features and setup procedures for host interfaces toEMC Symmetrix, VNX OE and CLARiiON, Invista, and VPLEXsystems. For information on setting up connections for third-partystorage systems, refer to your vendor’s documentation.

Refer to the E-Lab Interoperability Navigator on Powerlink forsupported EMC and third-party storage systems and firmwareversions.







Oracle Linux 5.6 x86_64 uek-2.6.32-100.26.2.el5

Oracle Linux 5.7 x86_64 uek-2.6.32-200.13.1.el5uek

Oracle Linux 6.0 x86_64 uek-2.6.32-100.28.5.el6

Oracle Linux 6.1 x86_64 uek-2.6.32-100.34.1.el6uek

1. Refer to the E-Lab Interoperability Navigator for the supported kernel revisions within this update/servicepack.

2. On Xen kernel, PowerPath is supported only on the Hypervisor; and, not on the guests.

Table 4 PowerPath 5.6 supported kernels (page 2 of 2)

Distribution1 Architecture Minimum kernel and kernel type



CLARiiON support CLARiiON customers receive PowerPath with the CLARiiON UtilityKits that ship with CLARiiON CX, CX3, CX4, and CX5-series storagesystems. This version of PowerPath, referred to as PowerPath SE,provides basic failover for single HBA host configurations withoutthe use of a license key. Important Information About PowerPath SEcontains more information on the CLARiiON configurationssupported by PowerPath SE.

Connectivity requirementsInstall HBAs, supported firmware versions, and other networkcomponents using the manufacturer’s directions and the settingsspecified in the E-Lab Interoperability Navigator. Using impropersettings can cause erratic failover behavior or extended response timefor system I/O.

PowerPath Migration Enabler supportThis section includes support information for PowerPath MigrationEnabler.

Topics include:

◆ “Migration scenarios” on page 15

Migration scenarios Table 5 on page 15 describes supported migration scenarios forPowerPath Migration Enabler.

Table 5 Supported migration scenarios (page 1 of 2)

Source logical unit Target logical unit Technology Objects

Pseudo-device name Pseudo-device name Invista EncapsulationHost Copy

—

TimeFinder/CloneOpen Replicator

Requires SolutionsEnabler 6.5.3 or later


16


Native-device name1 Pseudo-device name Invista EncapsulationHost Copy2


—

Thick plaintext Thin plaintext Host Copy2


Requires• Symmetrix

EnginuityOperatingEnvironment 5773or later on theSymmetrix DMXseries arrays

• SymmetrixEnginuityOperatingEnvironment 5874SR on the VMAXseries arrays

• VNX OE andCLARiiON FLAREversion04.28.000.5.5xx orlater and theVirtual Provisioningenabler

Migration Enablerdetects thin devices bydefault and preservesthe thin deviceallocation savings.

Thin plaintext Thick plaintext

Thin plaintext device Thin plaintext device

Thick plaintext device Thick plaintext device Host Copy2


Encrypted pseudo-devicename


Host Copy2 PowerPath Encryptionuses the Host Copytechnology to movedata to and fromencrypted devices.


Plain text pseudo-device name

Plaintext pseudo-device name Encrypted pseudo-devicename

1. Migrations between pseudo devices is supported on all platforms that support PowerPath Migration Enabler. However,migrations from native devices to pseudo devices is supported only on RHEL 5.x.

2. On Host Copy, migrations are independent of the Symmetrix, CLARiiON, or other operating environments.

Table 5 Supported migration scenarios (page 2 of 2)

Source logical unit Target logical unit Technology Objects


Known problems and limitations

Known problems and limitationsThis section describes known problems and limitations in PowerPathVersion 5.6 and its minor releases for Linux. Each table indicates theproblem description, workaround, and the version in which theproblem was discovered.

This section includes the following topics:

◆ “Known problems” on page 17

◆ “Limitations” on page 24

Known problemsThis section includes the following tables:


◆ “Known interoperability problems” on page 21


◆ “PowerPath Encryption with RSA: Known problems” on page 24

PowerPathmultipathing

Table 6 on page 18 shows the known problems in PowerPathmultipathing.


18


Table 6 PowerPath multipathing: known problems (page 1 of 3)

Description WorkaroundFound inversion

388072While installing PowerPath 5.6 on RHEL 6.2, the following errormessage is shown:emcp module is older than RHEL 6.2 ...applying fixups

No work-around. It is safe to ignore themessage.

5.6

368200Boot from SAN not supported on Oracle Linux 5.6 and 5.7 UEK.This issue is documented in EMC Knowledgebase Solutionemc270933 and in Oracle Linux Bugzilla 12499

None. 5.6

367442Oracle Linux 5.6 (kernel-uek-2.6.32-100) does not show correctinformation during target cable pull in a QLogic iSCSIinfrastructure.The "powermt display dev=all" command shows paths as alivewhile the target cablepull is done against the owner SP.

None 5.6

363943Data corruption observed on source, target, or both after LVMoperations (striping, mirroring, or snapshots) when PowerPathEncryption is in use.This issue is documented in EMC Knowledgebase Solutionemc266117.

Do not use PowerPath encryption if you planto use LVM striping, mirroring, and/orsnapshots.

5.5

356395After upgrading from RHEL 5.5 to RHEL 6, and from PowerPath5.5 to PowerPath 5.6, warning messages about configurationfiles appear. These warning messages appear only whenstarting PowerPath for the first time.

No action is required. 5.6

355935The PowerPath startup script activates LVM Volume Groupsthat were previously inactive. This issue is documented in EMCKnowledgebase Solution emc188678.

Add the tag tag to a physical volume, volumegroup, or a logical volume.

5.6

343806Unlicensed VPLEX LUNs set to BasicFailover policy, show asActive in the CLI. All but two paths should show as unlicensed.

None 5.5

342292Paths may not recover from front end failure in certainscenarios.

Run the following command for the HBA torediscover the remote ports:

# echo "1" > /sys/class/fc_host/host<hostno>/issue_lip

5.5



336725During a SP Hang, Call Trace messages are logged in the logfile. After the SP comes up, a few paths remain dead even aftera powermt restore.

Perform the following steps as a workaround:1. Execute the following command for all the

dead paths:# echo running >/sys/block/<sda>/device/state

2. Execute the powermt restore command.

5.5

334723For those installations booting from R2 Symmetrix devices only,PowerPath uses the INQ tool to infer SRDF pairs from systemnative devices information. This INQ tool requires a systemsemaphore sets threshold to be increased. The requirement isthe same as described in Solutions Enabler documentation,Refer to “Semaphores Requirement” in the EMC SolutionsEnabler Installation Guide for additional information.

None 5.5

333834On a RHEL5 boot-from-SAN setup, if the initrd image isrecreated after a PowerPath installation, and if the native devicename of the root disk changes, then the host will not boot up.This issue is documented in EMC Knowledgebase Solutionemc249231.

After PowerPath's installation on any RHELhost, perform the following steps:

1. Make a copy of the original ramdiskimage found in /boot folder. Make surethat the LVM filter in the image accepts alldevices.[root@libl044 ~]# cp /boot/initrd-2.6.18-194.el5.img/boot/initrd-2.6.18-194.el5.img.original

2. Create a new entry in /boot/grub/menu.lstfile with the 'original' ramdisk imagecreated in step 1 above.Now if the issue is ever encountered, thenthis new grub entry can be selected sothat the host can boot. Then the followingneeds to be done so that the host canboot properly on subsequent reboots:

a. Identify the new native device nameof the root device.b. Recreate the default ramdisk image.

3. Recreate the default ramdisk image.4. Reboot the host.

5.5




20


333231After rebooting an Invista switch, one of the native device pathsfails to come back online.

1. Run the following command for all thedead paths:echo running >/sys/block/<sda>/device/state2. Run the following command:powermt restore

5.5

326019In the /proc/diskstats file, IO statistics are not updated properlyon partition devices for native paths.

None 5.5

310459Powermt load generates warning messages when there aredead paths or if the native device names get changed afterfailover.

None 5.3 SP2

308967Running the powermt display every=seconds when a path hasfailed and then restored may continue to display UNKNOWN.

Stopping the powermt display commandand then starting a new session will show theupdated information.

5.3 SP2

281284A file system cannot be mounted after a LUN trespass and thena host reboot. PowerPath does not update the operating systempartition table for the LUN because the partition table doesn’tcontain entries for passive paths.

Run blockdev -rereadpt on the device afterthe host reboot.

5.3

269464, 268353LCC Card & Disk Pull related issues: Paths toggle betweendead and alive states before being marked dead.

If a rare situation does occur where the LUNtoggles between dead and alive statecontinuously, a powermt restore commandcan be run to mark the device as dead.

5.1





Known interoperabilityproblems

Table 7 on page 21 summarizes the known interoperability problemsthat affect PowerPath.

Table 7 Known interoperability problems (page 1 of 2)

Description WorkaroundSeen inversion

366796Error message is shown with LVM snapshots when the dmsetup tabledm device command is run after starting either PowerPath or its host.Different format expected for the device-mapper script on RHEL6,SLES 11, or SLES 11 SP1 causes this error. This issue is documentedin EMC Knowledgebase Solution emc268701.

1. Visit the EMC Knowledgebase Solutionemc268701.

2. Download thepp_reset_dm_deps.sh script fromthe Knowledgebase Solution.

3. Replace the same script in the/etc/opt/emcpower directory withthe downloaded script.

4. Follow the relevant procedure in theKnowledgebase Solution.

5.5

356286, 355111In non-SRDF setup, starting PowerPath 5.6 consumes more than theexpected time. This issue is found only when VPLEX or Invista devicesare connected to the host.

Replace the pp_inq script with a script thatcontains ‘exit 0’.

5.6

353911On RHEL 6.0 and 6.1, because each calls to the udevadm settlecommand requires three minutes to complete, uninstalling PowerPathconsumes a longer time.

Install the following Selinux patches:

selinux-policy-targeted-3.7.19-93.el6.noarchlibselinux-python-2.0.94-5.el6.x86_64selinux-policy-mls-3.7.19-93.el6.noarchlibselinux-2.0.94-5.el6.x86_64libselinux-devel-2.0.94-5.el6.x86_64selinux-policy-minimum-3.7.19-93.el6.noarchselinux-policy-3.7.19-93.el6.noarchlibselinux-utils-2.0.94-5.el6.x86_64

5.6

337328, 340760An issue has occurred on RHEL 5.5 with both Solutions Enabler 7.1.0and 7.1.1. There is a problem releasing the locked semaphores. Whenrunning symcfg discover, the following error message is shown:The gatekeeper device (while using the BaseDaemon) has an error.

Upgrade to Solution Enabler V7.1.1.26 withT7.2.0.507.

5.5

333917When migrating data from a thick to a thin device withTimeFinder/Clone on a Symmetrix VMAX with Enginuity 5874, thepowermig query command displays an inaccurate value for PercentInSync. This occurs because the Percent InSync value includes thearea of the source device that will not be copied to the target.

Upgrade to Symmetrix Enginuity version 5875. 5.3 SP1


22


355022, 353108, 357284On RHEL 6.0, there are slow path warnings and errors in log files foreach device when restoring reconnected paths.

You can ignore the error messages. 5.6

336484In a Veritas Cluster Server setup with two or more nodes, the pseudonames of the shared devices must be the same across all the nodes inthe cluster.

When the pseudo names are not the same,perform the following steps:1. Run the emcpadm export_mappings

command on the shared VxVM emcpowerdevice.

2. Delete the disk.info and disk.info.old fromthe /etc/vx directory.

3. Import the PowerPath mapping from theother host running the emcpadmimport_mappings command.

4. Perform vxdisk scandisks.An error should not occur.

5.5

285139When running scandisks for Oracle ASM volumes on PowerPath 5.1.x,the host hangs. This issue is seen with a larger number of volumes.

The workaround is to execute the asmscan.shscript. This issue is documented in the EMCKnowledgebase solution emc198046.

5.1

Table 7 Known interoperability problems (page 2 of 2)

Description WorkaroundSeen inversion



PowerPath MigrationEnabler

Table 8 on page 23 shows the known problems in PowerPathMigration Enabler.

Table 8 PowerPath Migration Enabler: known problems


359574Running the vxdisk scandisks command after a Host Copy migrationat VxVM controlled devices shows an error message; in addition, thecommand does not recognize newly added LUNs.

1. Remove the migrated LUNs fromVxVM control.

2. Add the new LUNs on the host, ifrequired.

3. Rescan VxVM to get new LUNsand migrated LUNs in VxVMcontrol.

Hint:Scanning the VxVMenvironment or a planned rebootresults in application downtime.Performing both of them togethercould prevent additionalapplication downtime.

5.6

358794, 358464In the Open Replicator and TimeFinder/Clone migrations on RHEL6with ext4 filesystems, the powermig commands show the followingerror message upon a host crash:The SYMAPI database file is invalid orcorrupted

1. Replace the corrupted SYMAPIdatabase file with valid databasefile:# mv/var/symapi/db/symapi_db.bin/var/symapi/db/symapi_db.bin.old

2. To use the new SYMAPIdatabase, run:# symcfg discover

5.6

313430With devices involved in an Open Replicator migration, when all theports of VNX OE and CLARiiON are disabled, the paths of theSymmetrix devices involved in the migration might also go dead.

None 5.3 SP1

288991When setting up a TimeFinder/Clone migration from a standard deviceto meta device, the following error message gets displayed:PPME_SYMCLONE error(182): A configuration mismatch was detected among members of your META devices.Any target Meta device selected results in the error.

None 5.3


24


PowerPath Encryptionwith RSA

Table 9 on page 24 shows the known problems in PowerPathEncryption with RSA.

LimitationsThis section describes limitations by product:

◆ “PowerPath Multipathing” on page 24



PowerPath MultipathingPowerPath 5.6 P02 does not support the following:

◆ Boot from SAN on Oracle Linux 5.7.

◆ Veritas Volume Manager on Oracle Linux 5.7

PowerPath 5.6 P01 does not support the following:

◆ Boot from SAN on Oracle Linux 5.6.

◆ Veritas Volume Manager on Oracle Linux 5.6, 6.0, and 6.1

Table 9 PowerPath Encryption with RSA: Known problems


363943, 365713Although the source data is not corrupt, mounting the snapshot, striped, ormirrored logical volume on an encrypted LUN corrupts some files on thesource, target, or both. However, the error is not logged.This issue is documented in EMC Knowledgebase Solution emc266117.

None 5.5

353758Logical Volumes on an encrypted device do not get activated whenuninstalled PowerPath is reinstalled and encryption is activated.

Manually activate the LogicalVolumes on encrypted devices afterreinstalling PowerPath.

5.6

312559/312287Automount of encrypted devices and Logical volumes created out ofencrypted devices may not happen on hosts with /usr as a separatepartition. This is because PowerPath encryption requires few libraries suchas libstdc++ which are available only in /usr partition and these may not beavailable when PowerPath starts during system bootup.

Manually mount the encrypteddevices after the boot. Thisworkaround is required only inconfigurations where the /usrpartition is in a different disk orvolume.

5.3 SP1


Technical notes

PowerPath Migration EnablerThis section includes the limitations in PowerPath Migration Enabler.

◆ The following limitations apply only to Host Copy migrations:

Host Copy supports migrating devices that exist on differenttransports (Fibre Channel and iSCSI software initiator) or iSCSIsoftware initiator.

However, when migration involves iSCSI devices either assource, target, or both, host reboots are not supported. If a rebootdoes occur, the migration session must be aborted and thenrestarted.

Reboots are not supported with migrations involving iSCSIdevices to or from encrypted devices. (Host Copy is theunderlying technology used with PowerPath Encryption).

PowerPath Encryption with RSAThis section includes the limitations in PowerPath Encryption withRSA:

◆ PowerPath 5.6 P02 does not support PowerPath Encryption onOracle Linux 5.7

◆ PowerPath 5.6 P01 does not support PowerPath Encryption onOracle Linux.

◆ LUN shrink is not supported with PowerPath Encryptionenabled.

A LUN shrink operation performed with encrypted devices maylead to a Data Unavailable/Data Loss scenario.

Technical notesThis section includes technical notes on the following topics, whichare arranged as follows:





26

Technical notes

PowerPath multipathingThis section includes the following topics:

◆ “PowerPath and VMAX/VMAXe series devices” on page 26

◆ “PowerPath and VNX series devices” on page 26

◆ “Setting periodic_autorestore to off still restores dead paths” onpage 27

◆ “Paths not released in a cluster or LVM environment” on page 27

◆ “Placing Celerra iSCSI devices under PowerPath control” onpage 27

◆ “PowerPath and the CLARiiON admsnap utility” on page 28

◆ “Supporting more than 256 storage devices” on page 28

◆ “Symmetrix Enginuity Operating Environment” on page 30

◆ “VNX OE and CLARiiON FLARE Operating Environment” onpage 30

◆ “iSCSI devices” on page 31

◆ “Running the powermt load command may give false warningmessages” on page 31

◆ “Mode not reflecting properly across a reboot” on page 31

◆ “Mount option in the /etc/fstab” on page 32

◆ “Expanding the file system on a pseudo-device” on page 32

◆ “PowerPath licenses in a CLARiiON AX and CX configuration”on page 32

◆ “PowerPath Viewer support” on page 32

PowerPath and VMAX/VMAXe series devicesVMAX and VMAXe devices are managed under the symm storageclass. This means that in powermt display, any VMAX or VMAXedevices you may have under PowerPath management appear asSymmetrix devices. Similarly, the default and licensed failover andload-balancing policies are bf for unlicensed devices and SymmOptfor licensed devices.

PowerPath and VNX series devicesVNX OE devices are managed under the clariion storage class. Thismeans that in powermt display, any VNX OE devices that you mayhave under PowerPath management appear as CLARiiON devices.


Technical notes

Similarly, the default unlicensed and licensed failover andload-balancing policies are the same for VNX OE devices as forCLARiiON; that is, Basic Failover for unlicensed devices andCLARopt for licensed devices. VNX devices behave like CLARiiONdevices on PowerPath with respect to multipathing andfailover/failback.

VNXe devices are managed under the generic storage class. Inpowermt display, any VNXe devices that you may have underPowerPath management appear as Celerra devices. The defaultunlicensed failover and load-balancing policy is Basic Failover; forlicensed devices, the policy is Adaptive. More information isavailable on the VNX OE Storage System Support website(www.emc.com/vnxsupport).

Setting periodic_autorestore to off still restores dead pathsOn some Linux platforms, when the powermt setperiodic_autorestore command is set to off, PowerPath will continueto test and restore dead paths. This is an expected behavior on OracleLinux Versions 5.6, 5.7, 6.0, and 6.1, and RHEL 6.0 kernels.

Paths not released in a cluster or LVM environmentIn a cluster or LVM environment, host software may hold referencesto PowerPath or native devices. In such a situation, PowerPathcannot release one or more paths despite the device is removed orrenamed. Reboot PowerPath for the host software to release thesereferences.

Placing Celerra iSCSI devices under PowerPath controlPowerPath treats EMC Celerra iSCSI devices as generic devices.Enable generic Loadable Array Module (LAM) support so thatPowerPath can recognize and manage Celerra iSCSI devices.

Note: For VNXe devices same procedure is applicable, including genericLoadable Array Module (LAM) support.

Managing Celerra iSCSI targetsTo place Celerra iSCSI devices under PowerPath control:

1. Add the following line to the /etc/emc/mpaa.lams file:

managed:generic:EMC:Celerra

2. Run powermt init.


www.emc.com/vnxsupport

28

Technical notes

3. Run powermt config.

4. Run the /etc/init.d/PowerPath stop and /etc/init.d/PowerPathstart command sequence to restart PowerPath or reboot the host.

Unmanaging Celerra iSCSI targetsTo remove Celerra iSCSI devices from PowerPath control:

1. Remove the following line from the /etc/emc/mpaa.lams file:

managed:generic:EMC:Celerra

2. Run powermt init.


4. Run the /etc/init.d/PowerPath stop and /etc/init.d/PowerPathstart command sequence to restart PowerPath or reboot the host.

PowerPath and the CLARiiON admsnap utilityTake note of the following if you use the CLARiiON admsnap utilitywith PowerPath devices.

◆ For all versions of the admsnap utility, set thePP_SHOW_CLAR_OWNING_SP environment variable to falseto suppress the display of default and current SP data:

PP_SHOW_CLAR_OWNING_SP=false

◆ For admsnap utility version 2.4.0.0.3 or less:

• Set the PP_DEFAULT_STORAGE_SYS environment variableto VNX OE and CLARiiON to restrict the class of devicesdisplayed by the powermt utility to VNX OE and CLARiiONdevices:

PP_DEFAULT_STORAGE_SYS=CLARiiON

• Use a native PowerPath name (for example, /dev/sde) to startor activate an admsnap session when a file system is mountedon a PowerPath device. You cannot use a PowerPath pseudodevice name (for example, /dev/emcpowere) to start oractivate a session when a file system is mounted on aPowerPath device.

Supporting more than 256 storage devicesComplete the following steps to support more than 256 storagedevices on a host.


Technical notes

Emulex HBAsIf you using Emulex HBAs, set the lpfc_max_luns parameter to 1024,2048, or 4096.

QLogic HBAsIf you using QLogic HBAs, change the system parameters under/sys/module/scsi_mod/max_luns and max_report_luns to therecommended value.

For more information, refer to the EMC Host Connectivity Guide forLinux or to the vendor website.

Making the parameter settings permanent across rebootTo make the parameter settings permanent across reboot on Emulexor QLogic HBAs:

On RHEL 5.x

1. Edit the /etc/modprobe.conf file and set the lpfc_max_lunsparameter to 1024, 2048, or 4096.

2. Recreate the initrd.

3. Point the initrd to the new initrd when booting.

On RHEL 6.x

1. Create the lpfc.conf file in the /etc/modprobe.d/ directory.

2. Edit the file and set the lpfc_max_luns parameter to 512.

3. Recreate the initramfs by running the dracut -f command.

4. Reboot the host.

For more information, refer to the EMC Host Connectivity Guide forLinux or to the vendor website.

Unmanaging more than 256 LUNs causes PowerPath loadingfailures.To resolve the PowerPath loading failure:

1. Type mv /etc/init.d/PowerPath /etc/init.d/PowerPath.orig

2. Restart the host.

3. Remove /etc/emc/mpaa.excluded.

4. Edit /etc/modprobe.conf.pp to remove the excludedvolumesmodule parameter and its associated arguments.

5. Type mv /etc/init.d/PowerPath.orig /etc/init.d/PowerPath


30

Technical notes

6. Type /etc/init.d/PowerPath start.

7. Unmanage the devices (up to 256).

Configuring 256 devices in a boot-from-SAN environmentIn a boot-from-SAN SLES environment, PowerPath configures only256 device paths, though more device paths are available to thesystem.

Perform the following:

1. Run /sbin/udevstart to repopulate the device directory.


3. Run chkconfig boot.udev on to configure udev to start upautomatically on subsequent reboots.

4. Run chkconfig boot.udev to confirm the change.

Symmetrix Enginuity Operating EnvironmentTake note of the following issues regarding the Symmetrix EnginuityOperating Environment.

Enginuity Operating Environment 5568 reservation andpre-emption commandsThe Reservation and pre-emption commands in EnginuityOperating Environment 5568 are not working according to the SCSI-3specification. This issue is seen both with PowerPath and withoutPowerPath on a host. This is not a PowerPath issue.

Enginuity Operating Environment 5773 and VxVMWith Symmetrix Enginuity Operating Environment 5773 and VxVM,Symmetrix patch 5773.130.90 or later is required. This patch fixes anissue where the vxfentsthdw utility fails while testing a SCSI-3persistent group reservation enabled LUN.

VNX OE and CLARiiON FLARE Operating EnvironmentTake note of the following issue regarding the VNX OE andCLARiiON FLARE Operating Environment.

FLARE Operating Environment 04.28 and over-provisioningAfter over-provisioning the thin pool on a VNX OE and CLARiiONarray with FLARE version 04.28.000.5.706, the hosts connected to theVNX OE and CLARiiON receives SCSI related errors and does notsee all the thin LUNs after a host reboot. This is a VNX OE andCLARiiON issue that has been fixed in FLARE version 04.29.


Technical notes

iSCSI devicesTake note of the following issues regarding native iSCSI devicesusing the software initiator in a PowerPath environment.

Configuring iSCSI to start on host bootEMC recommends configuring your iSCSI initiator service to startautomatically when the host boots. Run chkconfig to enable theiSCSI service.

Note: If you stop PowerPath and then the device configuration changes,when you restart PowerPath you may see a message that PowerPath failed tostart. You can ignore this message.

Stopping iSCSI on a PowerPath hostAlways stop PowerPath before stopping iSCSI on a host with iSCSIdevices under PowerPath control.

Note: Ensure that anything that has an iSCSI device open has closed the iSCSIdevice before shutting down iSCSI. This includes file systems, volumemanagers, and user applications.

To stop iSCSI on a PowerPath host:

1. Type /etc/init.d/PowerPath stop.

2. Type /etc/init.d/iscsi stop.

Adding or removing iSCSI devices"Dynamic LUN addition and removal" in the EMC PowerPath forLinux Installation and Administration Guide provides more informationon adding or removing iSCSI devices.

Running the powermt load command may give false warning messagesWith iSCSI Celerra devices, running powermt load gives a "Erroroccurred loading saved driver state from file /etc/powermt.custom"warning message although the configuration is restored. Because theconfiguration is restored, ignore the warning message.

Mode not reflecting properly across a rebootWhen a PowerPath load balancing and failover mode is changed, themode may not reflect properly after the reboot. This is caused by thenative device name sometimes changing during the reboot, creatingan incorrect configuration and is Linux operating system behavior.


32

Technical notes

Mount option in the /etc/fstab

RHEL 5.x and RHEL 6.x PowerPath devices should use the _netdev mount option in the/etc/fstab file for both FC, FCoE, and iSCSI devices. This will ensurethat fsck is run later in the boot sequence.

Expanding the file system on a pseudo-deviceTo expand the file system on a pseudo device, follow the steps below:

Note: For encrypted devices, refer to "Expanding the encrypted LUN fromthe array side,” in the PowerPath 5.6 Encryption with RSA User Guide.

1. Expand the LUN on the array.

2. Unmount the file system if it is mounted.

3. Run blockdev --rereadpt /dev/<Pseudo device> to re-readthe partition table of the pseudo device.

4. Follow the operating system’s recommended steps to resizethe file system: resize2fs –p /dev/<Pseudo device> for the ext2,ext3, or ext4 file system.

5. Run mount /dev/<Pseudo device> <Mount point>.

PowerPath licenses in a CLARiiON AX and CX configurationWhen running PowerPath without a license on a host attached toboth CLARiiON AX and CX arrays, PowerPath does not display awarning about the missing license for the CX array. This behaviormay be unexpected as PowerPath does display a missing licensewarning when connected to CX arrays when no AX array is present.Without a license, only the AX array has full PowerPath functionality;the CX array will not have failover support.

In a configuration with both CLARiiON AX and CX arrays, ensure avalid license is present for the CX array by entering emcpreg -list.

PowerPath Viewer supportPowerPath 5.6 and its minor releases for Linux are supported onEMC PowerPath Viewer. PowerPath Viewer can monitor the status ofhosts running PowerPath 5.6 for Linux environments.

EMC PowerPath Viewer is a centralized monitoring utility thatprovides a consolidated display of events, and allows you to viewand monitor up to 500 PowerPath hosts through a graphical userinterface (GUI). With EMC PowerPath Viewer, you can view hosts,


Technical notes

host groups, LUNs, individual paths to each LUNs, and buses.PowerPath Viewer also provides email alerts about any changes inthe status of PowerPath devices.

PowerPath Viewer includes two components: PowerPath ViewerConsole, which is the interface that displays information and alertsabout PowerPath custom-tailored devices shown in windows andpanes; and the PowerPath Management Component, which is thehost-based software that monitors host, LUNs, data path, and busevents and sends information and alerts to the Viewer Console overIP.

PowerPath Viewer is available as a separate download in thePowerPath software downloads section of Powerlink.

The PowerPath Viewer 1.0 and Service Pack Releases Release Notes,available on Powerlink, provides more information.

PowerPath Migration EnablerThis section includes the following topics:

◆ “Source/target LU faults with kexec service” on page 33

◆ “Symmetrix gatekeeper devices” on page 33

Source/target LU faults with kexec serviceWhen kexec is enabled, Host Copy migrations with PowerPathMigration Enabler result source/target LU faults. Host that could notdo a full reboot causes these faults.

Therefore, when performing a Host Copy migration, if you have thekexec service running, type # chkconfig -s kexec off to disable it.

Symmetrix gatekeeper devicesLogical units involved in a migration should not be used asSymmetrix gatekeeper devices. To ensure that migration devices areNOT used as gatekeepers, choose at least one non-migration deviceand add it to the SYMAPI gkselect file (multiple gatekeeper devicescan be added). This ensures that SMAPI will only use those devicesas gatekeepers. The EMC Solutions Enabler Symmetrix BaseManagement CLI Product Guide contains more information aboutgatekeeper devices.


34

Technical notes

PowerPath Encryption with RSAThis section includes the following topics:

◆ “Performance in migrations with encrypted devices” on page 34

◆ “Compression issues with encrypted data for RecoverPoint” onpage 34

◆ “BCV device encryption” on page 34

Performance in migrations with encrypted devicesMigrating data to or from encrypted devices increases the CPU loadon a PowerPath Encryption host since it must handle the processingload of encrypting or decrypting the data that is being migrated inaddition to the normal application processing load. For informationabout monitoring and controlling the performance of migrations,refer to the PowerPath Migration Enabler User Guide.

Compression issues with encrypted data for RecoverPointPowerPath Encryption with RSA works with fabric-based SANTapand RecoverPoint running on a VNX OE and CLARiiON storagedevice. If RecoverPoint is used for remote replication, dataencryption will make compression ineffective and hence a higherbandwidth will be required for encrypted devices that are beingremotely replicated.

BCV device encryptionThe following step overcomes the problem of BCV device’s inabilityto get encrypted after the split operation with the encrypted standarddevice.

Note: After a TimeFinder operation, updating of the BCV device encryptionstate is necessary.

Run powervt update -dev <device_to_be_updated> to re-key the BCVdevice. Once the command is executed, the device would becomeencrypted and will be usable.


Documentation

DocumentationTable 10 on page 35 lists the PowerPath documentation set; allmanuals are available from EMC Corporation.

Localized versions of the EMC PowerPath for Linux Installation andAdministration Guide are available in French, German, Italian,Japanese, Korean, Portuguese, simplified Chinese, and Spanishlanguages.

PowerPath/VE for VMware vSphere is covered in the PowerPath forVMware vSphere documents, available on Powerlink.

Electronic versions of all PowerPath manuals are available on thePowerlink website. These manuals are updated periodically, and theupdated manuals are posted on the Powerlink website.

Related DocumentationThe following are related documentation for Symmetrix, and VNXOE and CLARiiON storage systems.

Table 10 PowerPath Family documentation set

Part Number Title

PowerPath Family

300-006-627 EMC PowerPath Family Version 5.2, 5.3, 5.5, and 5.6 Product Guide

300-011-783 EMC PowerPath Version 5.6 CLI and System Messages Reference

300-011-782 EMC PowerPath Family for Linux Version 5.6 and Service Pack Releases ReleaseNotes (this document)

PowerPath multipathing

300-011-781 EMC PowerPath for Linux Version 5.6 Installation and Administration Guide

PowerPath Migration Enabler

300-011-785 EMC PowerPath Migration Enabler Version 5.6 User Guide

PowerPath Encryption with RSA

300-011-784 EMC PowerPath Encryption with RSA Version 5.6 User Guide


36

Documentation

Symmetrix storagesystems

If your environment includes Symmetrix storage systems, refer to thefollowing:

EMC Host Connectivity Guide for Linux, which provides basicinformation about the features and setup procedures for hostinterfaces to Symmetrix systems.

VNX OE and CLARiiONstorage systems

If your environment includes VNX OE and CLARiiON storagesystems, refer to the following:

◆ EMC Host Connectivity Guide for Linux, which provides basicinformation about the features and setup procedures for hostinterfaces to VNX OE and CLARiiON systems.

◆ CLARiiON Support home page: www.emc.com/clariionsupport

◆ VNX OE Support home page: www.emc.com/vnxsupport

◆ EMC Host Connectivity Guides, which provides basic informationabout the features and setup procedures for host interfaces toVNX OE and CLARiiON systems.

Note: CLARiiON customers receive PowerPath with the CLARiiON UtilityKits that ship with CLARiiON CX- and CX3-series storage systems. Thisversion of PowerPath, referred to as PowerPath SE, provides basic failoverfor single HBA host configurations without the use of a license key. TheImportant Information about PowerPath SE document, available on thePowerlink website, provides additional information on the CLARiiONconfigurations supported by PowerPath SE.

A subset PowerPath functions are available through the UnisphereTM

application for VNX OE systems. Refer to the VNX OE StorageSystem Support website (www.emc.com/vnxsupport).

A subset of PowerPath functions are available through theNavisphere® and the Unisphere applications for CLARiiON systems.Refer to CLARiiON Storage-System Support website(www.emc.com/clariionsupport).

RSA Key Manager The following documents describe the RSA Key Manager software:

◆ RSA Key Manager Server Release Notes

◆ RSA Key Manager Server Administrator’s Guide

The following documents describe the RSA Key Manager appliance:

◆ RSA Key Manager Appliance Release Notes

◆ RSA Key Manager Appliance Quick Start Guide


http://www.EMC.com/clariionsupport

http://www.EMC.com/clariionsupport



www.emc.com/clariionsupport

Documentation

This documentation is available on the product CD.

If your environment includes other vendors’ storage systems, refer tothe appropriate documentation from your vendor.

End of service dates and extended supportEMC has a standard software support duration policy whichspecifies that a major version will reach End of Service Life (EOSL) aminimum of 36 months following the General Availability (GA).EOSL may be followed by an Extended Support period during whichcustomers may elect to pay an additional fee to extend their supportcoverage rather than migrate to a current software version.

Once a software product reaches EOSL, EMC Technical Support is nolonger available under base support/maintenance agreements.Customers interested in uninterrupted support must upgrade to acurrent release or contract for Extended Support (ES).

Powerlink contains a list of documents that provide end-of-serviceand extended support information for EMC software and hardwareproducts.

To access these documents on Powerlink:

1. Go to Powerlink.

2. Enter the following text in the Search box and click Search:

EMC software release end of service life

3. Find the EMC Software Release and End of Service LifeNotifications document in the results.

4. Open it and search for your product and version.

This document provides EOSL dates for EMC software products.

Note: This policy is in effect for select releases and will be phased in as newversions are made available. In cases where a software release is not eligiblefor Extended Support, the previous policy, which specifies product supportand maintenance under Continuous Coverage Product Maintenance(CCPM), terms still apply.


38

Software media, organization, and files

Software media, organization, and filesThis section contains information about the PowerPath 5.6 media andfiles.

EMC PowerPath Version 5.6 and its minor releases for Linux is a fullrelease available on CD and for download from the Powerlink andEMC.com websites.

Media and releases The PowerPath Version 5.6 and its minor releases for Linux softwareCD has the following structure:

./LINUX:

pp5.5.xpp5.6.xVNX

./LINUX/pp5.5.xEMCPower.LINUX.5.5.GA.b275.tar.gz

./LINUX/pp5.5.x/rhelEMCPower.LINUX-5.5.0.00.00-275.RHEL5.i386.rpmEMCPower.LINUX-5.5.0.00.00-275.RHEL5.IA64.rpmEMCPower.LINUX-5.5.0.00.00-275.RHEL5.x86_64.rpmEMCPower.LINUX-5.5.0.00.00-275.RHEL5.PPC64.rpm

./LINUX/pp5.5.x/slesEMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.i386.rpmEMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.IA64.rpmEMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.x86_64.rpmEMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.PPC64.rpmEMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.i386.rpmEMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.x86_64.rpmEMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.IA64.rpmEMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.PPC64.rpm

./LINUX/pp5.6.xEMCPower.LINUX.5.6.GA.b143.tar.gz

./LINUX/pp5.6.x/rhelEMCPower.LINUX-5.6.0.00.00-143.RHEL5.i386.rpm

EMCPower.LINUX-5.6.0.00.00-143.RHEL5.x86_64.rpm

EMCPower.LINUX-5.6.0.00.00-143.RHEL6.i386.rpm

EMCPower.LINUX-5.6.0.00.00-143.RHEL6.x86_64.rpm

./LINUX/pp5.6.x/oel


Installation

EMCPower.LINUX-5.6.0.01.00-005.OL56.x86_64.rpmEMCPower.LINUX-5.6.0.01.00-005.OL6.x86_64.rpm

./LINUX/pp5.6.x/ovsEMCPower.LINUX-5.6.0.01.00-005.OVS3.x86_64.rpm

./LINUX/VNX/PowerPath Encryption VNX Security and Compliance Suite

README

Table 11 on page 39 summarizes the PowerPath 5.6 package andreleases.

Files For information about files added by PowerPath 5.6, refer to “FilesChanged By PowerPath,” in the PowerPath 5.6 for Linux Installationand Administration Guide.

InstallationThis section includes the following topics:

◆ “PowerPath Configuration Checker” on page 40

◆ “Installing PowerPath multipathing” on page 40

◆ “Installing PowerPath Migration Enabler” on page 40

◆ “Installing PowerPath Encryption with RSA” on page 40

Table 11 PowerPath Version 5.6 for Linux package and releases

PowerPath release/description Package/Part number Build

EMC PowerPath, PowerPath MigrationEnabler, and PowerPath Encryption withRSA version 5.6 for Linux software CD.

053-002-357 A01 N/A

PowerPath Version 5.6 EMCPower.LINUX.5.6.GA.b143.tar.gz b143

PowerPath Version 5.6 P01 EMCPower.LINUX.5.6.P01_b005.tar.gz b005

PowerPath Version 5.6 P02 EMCPower.LINUX.5.6.P02_b001.tar.gz b001


40

Installation

PowerPath Configuration CheckerPowerPath Configuration Checker (PPCC) is a software program thatverifies that a host is configured to E-Lab Interoperability Navigatorstandards with the hardware and software required for PowerPathmultipathing features (failover and load-balancing functions,licensing, and policies). PPCC is available for download onPowerlink.

Prior to installing or upgrading PowerPath, download the latestversion of EMC Grab available on Powerlink and then run PPCC.This ensures that the system version used by PPCC includes the latestconfiguration information.

For installation information, the EMC PowerPath Configuration CheckerUser Guide, available on Powerlink, provides additional information.

Installing PowerPath multipathingTo install PowerPath follow the instructions in the EMC PowerPath forLinux Installation and Administration Guide, available on Powerlink.

Upgrading PowerPathPowerPath 5.6 for Linux supports the following upgrades from:

◆ PowerPath 5.x to 5.6

◆ RHEL 5.x to RHEL 6.0

Installing PowerPath Migration EnablerTo install PowerPath Migration Enabler on Linux hosts:

1. If you have not done so already, install PowerPath Version 5.6.The EMC PowerPath for Linux Installation and Administration Guideprovides additional information.

2. Install the PowerPath Migration Enabler license key andconfigure the Migration Enabler host. The EMC PowerPathMigration Enabler User Guide provides additional information.

Installing PowerPath Encryption with RSATo install PowerPath Encryption with RSA on Linux hosts:


Troubleshooting and getting help

1. If you have not done so already, install PowerPath Version 5.6.The EMC PowerPath for Linux Installation and Administration Guideprovides additional information.

2. Install the PowerPath Encryption with RSA license key andconfigure the Encryption host. The EMC PowerPath Encryptionwith RSA User Guide provides additional information.

Troubleshooting and getting helpEMC support, product, and licensing information can be obtained asfollows:

Product information — For documentation, release notes, softwareupdates, or for information about EMC products, licensing, andservice, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC WebSupporton Powerlink. To open a case on EMC WebSupport, you must be aWebSupport customer. Information about your site configuration andthe circumstances under which the problem occurred is required.

Service packs and upgrades — You can download PowerPathservice pack software from Powerlink. Determine which servicepacks (if any) you want to install after PowerPath, and whether thoseservice packs have any additional installation prerequisites. To obtainservice packs on Powerlink, select Support > Software Downloadsand Licensing > Downloads P-R > PowerPath for Linux.

Reporting a problemIf you find a problem in PowerPath, run the emcgrab utility, whichcollects system and software configuration information. Submit thegenerated tar file, along with any other supporting material, to EMCCustomer Support.

EMC Grab 3.9 or later is required to collect information aboutPowerPath Encryption with RSA or Host Copy migrations. EMCGrab version 3.7 or later collects information about PowerPathMigration Enabler for Open Replicator or Invista.


http://powerlink.emc.com

42

Troubleshooting and getting help

You can download emcgrab from the Powerlink website. SelectSupport > Product and Diagnostic Tools > Grab Utilities. Refer tothe emcgrab ReadMe.txt file on Powerlink for prerequisiteinformation and instructions on using the utility.

Copyright © 1997-2012 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information issubject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation andAdvisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.All other trademarks used herein are t property of their respective owners.


300-011-782

Documents

lab interoperability

bit operating

series storage

sourcetarget

veritas volume

party storage

parameter

type mv