Release Notes P/N Rev A02

Transcription

1 EMC PowerPath for Solaris Version Release Notes P/N Rev A02 June 2, 2006 These release notes contain supplemental information about EMC PowerPath, version Topics include: Product Description... 2 New Features and Changes... 2 Fixed Problems... 3 Environment and System Requirements... 4 Known Problems and Limitations Technical Notes Documentation Software Media, Organization, and Files Installation Troubleshooting and Getting Help

2 Product Description Product Description EMC PowerPath software is a server-resident, performance and application availability enhancing software solution. PowerPath combines multiple path I/O capabilities, automatic load balancing, and path failover functions into one integrated package. PowerPath supports servers, including cluster servers, connected to EMC Symmetrix, EMC CLARiiON, IBM ESS, Hitachi Lightning, Hitachi TagmaStore, HP StorageWorks xp, EVA, EMA, and MA storage systems. PowerPath supports Fibre Channel for both switched fabric and arbitrated loop environments. New Features and Changes PowerPath for Solaris adds support for the following new and enhanced features: EMC Invista network storage virtualization Note: PowerPath supports EMC Invista devices. A new class, INVISTA, lets you manage Invista devices using the powermt utility. Refer to the PowerPath 4.5 Product Guide for more information. Hitachi TagmaStore storage systems Note: The existing HITACHI class lets you manage Hitachi TagmaStore devices using the powermt utility. Refer to the PowerPath 4.5 Product Guide for more information. HP StorageWorks XP12000 storage systems Note: The existing HPXP class lets you manage HP StorageWorks XP12000 devices using the powermt utility. Refer to the PowerPath 4.5 Product Guide for more information. Discontinued Features in PowerPath This section includes information about discontinued features in PowerPath. EMC HighRoad Please be aware that the next release of PowerPath (post-4.5) will not include intrinsic disk protection for EMC HighRoad disks on Symmetrix storage systems. This is a change from PowerPath 4.5 and 2 EMC PowerPath for Solaris Version Release Notes

3 Fixed Problems earlier, in which disk protection for HighRoad disks is included in the PowerPath software. Effective with HighRoad version 4.0, disk protection for Symmetrix is included in the HighRoad software. If you are using PowerPath 4.5 or earlier with HighRoad 4.0 or earlier, you do not need to take any action at this time. In the future, if you want to upgrade to a version of PowerPath later than 4.5 (and you have HighRoad 3.2 or earlier), you will need to upgrade first to HighRoad version 4.0 or later before upgrading PowerPath. End-of-Life Announcement CLARiiON FC4700 As of PowerPath 4.5.0, EMC announced end-of-life (EOL) for CLARiiON FC4700 support. Effective with the release of PowerPath for Solaris, PowerPath will no longer support CLARiiON FC4700 storage systems. PowerPath Volume Manager Please be aware that EMC has announced end-of-life (EOL) for PowerPath Volume Manager (PPVM) functionality for Solaris, AIX and HP-UX environments. This is effective with the release of PowerPath 4.4 for Solaris in March 2005, the PowerPath 4.4 for AIX release, and PowerPath 4.5 for HP-UX. EMC has also announced its intention to end-of-service-life PPVM functionality for Solaris, AIX and HP-UX effective March Therefore, if you have any data on PPVM volumes, back up that data and destroy all PPVM volume groups before installing PowerPath or Fixed Problems Table 1 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.5.0: Solaris Description Found in Version Resolved in Version A PowerPath installation overwrites and changes host semaphore settings on Solaris servers. This is a remnant of PowerPath Volume Manager, for which end-of-life notification was announced with the release of PowerPath EMC PowerPath for Solaris Version Release Notes 3

4 Environment and System Requirements Table 1 Resolved Problems in PowerPath Version 4.5.0: Solaris (continued) Description Found in Version Resolved in Version After a double fault (for example, pulling two disks of out a RAID1 device) on a CLARiiON LUN, all other LUNs on the array show dead paths In pre-4.3 releases, powermt does not handle CLARiiON LUN names containing colons properly. In those earlier releases, powermt truncates CLARiiON LUN names at the point at which a colon is encountered. For example, the command powermt display dev=device all shows LUN 123:abc as LUN 123. In PowerPath 4.3.x (or later), this problem has been partially resolved. With this release, the command powermt load [file=older_file] fails to complete if the configuration file contains data for CLARiiON pseudo devices with colon-containing LUN names. This results in CLARiiON volumes and third-party volumes being set with default load balancing and failover policies , The powervxvm init script corrupts the VxVM rootdg created on external devices managed by PowerPath. The powervxvm init script now automatically protects disk groups (including rootdg), which prevents it from destroying any previously existing disk group. A warning appears near the end of the script to indicate which devices were not initialized Environment and System Requirements Before you install PowerPath, or whenever you make changes to the host or storage environment where PowerPath operates, consult the resources described in this section. These resources will help you configure an environment in which all components, including PowerPath, can operate optimally. EMC Support Matrix (all storage systems) The EMC Support Matrix provides detailed information about the hardware, software, and networked storage components that are tested and compatible with both EMC storage systems and third-party storage systems. (For information about third-party storage systems, see the chapter entitled Non-EMC Storage.) The EMC Support Matrix describes supported host models, operating system revisions, host bus adapters, and connectivity devices. The EMC Support Matrix, which is updated every month, is published at the Powerlink website: 4 EMC PowerPath for Solaris Version Release Notes

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

6 Environment and System Requirements Host Configuration Table 2 The following table shows the Solaris operating systems supported. Solaris: Supported Operating Systems Supported OS Sun patches required Sparc Solaris 7 (32 and 64 bit) (X6541 HBA only) (X1062A and X1065A HBAs only) Sparc Solaris 8 (32 and 64 bit) (X6541 HBA only) (X106A2 & X1065A HBAs only) Sparc Solaris 9 (32 and 64 bit) Sparc Solaris (X6767A and X6768A HBAs only) The following table shows minimum disk space requirements for Solaris. Table 3 Solaris: Disk Space Required File System or Directory Installation directory (the default is /opt) Root file system /usr /var Minimum Space Requirements 40 MB 16 MB 12 MB 1 MB 6 EMC PowerPath for Solaris Version Release Notes

7 Environment and System Requirements Supported HBAs: PowerPath for Solaris With Third-Party Storage Systems This section describes the HBA models and driver versions supported for PowerPath for Solaris with third-party storage systems. The section also describes changes to the default driver configuration files required by PowerPath for Solaris. Consult the EMC Support Matrix for HBA models and driver versions supported with Symmetrix and CLARiiON systems. Supported HBAs: IBM ESS, Hitachi Lightning, Hitachi TagmaStore, HP xp Systems PowerPath for Solaris has been tested and qualified for use with IBM ESS, Hitachi Lightning, Hitachi TagmaStore, and HP xp storage systems using the HBA models and driver versions shown in the following table. Table 4 Solaris: Supported HBAs IBM ESS, Hitachi Lightning, HP xp Systems Manufacturer Model Driver Versions Supported with Arrays IBM ESS Hitachi Lightning Hitachi TagmaStore HP xp Arrays Emulex LP8000 LP9000 LP9002LDC LP10000 EMC 5.02c EMC 6.01f LP9802 EMC 5.02c EMC 6.01f Supported HBAs: HP StorageWorks EVA, EMA, and MA Systems PowerPath 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. EMC PowerPath for Solaris Version Release Notes 7

8 Environment and System Requirements Note: HP requires installation of the Platform Kit on every host connected to these storage systems. The Platform Kit contains the drivers that are supported with the storage system. You can download the Platform Kit from the HP website. Table 5 Solaris: Supported HBAs HP StorageWorks EVA, EMA, MA systems Manufacturer Model Driver Versions QLogic QLA 2312 QLogic V4.11 SG-XPCIFC2-QF2 SUNWqlc SUNWqlcx SUNWqlcx Emulex LP8000 EMC 5.01e EMC 5.02c EMC 6.01f LP-9002 EMC 5.02c EMC 6.01f LP10000 EMC 6.01f 8 EMC PowerPath for Solaris Version Release Notes

9 Environment and System Requirements HBA Driver Settings The following table describes changes to the default driver configuration files required by PowerPath for Solaris with third-party storage systems. Table 6 Solaris: HBA Driver Settings Third-Party Storage Systems HBA Driver Parameter Default Setting PowerPath Setting Setting Required for Emulex automap 0 0 All third-party systems linkdown-tmo All third-party systems lun-queue-depth All third-party systems num-iocbs All third-party systems tgt-queue-depth All third-party systems no-device-delay 0 0 All third-party storage systems Heterogeneous Connections PowerPath for Solaris supports heterogeneous connections to different storage arrays from the same HBA only with the following HBA model numbers: Sun X6767A(SG-XPCI1FC-QF2) Sun X6768A (SG-XPCI2FC-QF2) LP8000 LP9002 LP9802 LP10000 Note: The heterogeneous connections allowed by third-party vendors may conflict with those allowed by EMC. In that case, the third-party vendor s requirements take precedence. EMC PowerPath for Solaris Version Release Notes 9

10 Environment and System Requirements Interoperability With VxVM on HP xp Arrays For PowerPath for Solaris to fully interoperate with VERITAS Volume Manager (VxVM) on third-party arrays, you must install the VERITAS Array Support Library (ASL) for your particular storage system after you install VxVM. You can download the ASL from the VERITAS website. Storage Array Configuration Symmetrix Storage Systems 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. 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. Microcode versions tested Paths per device Boot support 5x67, 5x68, 5x69, 5x70, 5x71 32 Solaris 7, 8, 9, 10 Note: For information about LUN configuration and limits see the EMC host connectivity guide, available on the Powerlink website. Once a host and Symmetrix system are properly configured, you can install or upgrade PowerPath. See the PowerPath for Solaris Installation and Administration Guide for installation details. CLARiiON Storage Systems PowerPath installation is an integral part of a CLARiiON setup and configuration procedure. To properly install PowerPath on a host with a CLARiiON array, refer to the EMC Installation Roadmap for CX-Series and FC-Series Storage Systems. There you will find step-by-step instructions for installing PowerPath and other CLARiiON software. To obtain the latest versions of CLARiiON CX-series documentation, log in to the Powerlink website ( 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 10 EMC PowerPath for Solaris Version Release Notes

11 Environment and System Requirements documents for prescribed installation information when using AX100-Series storage systems. The following table shows the minimum revision of FLARE supported by PowerPath for Solaris. CLARiiON Storage System AX100 AX100SC CX200 CX300 CX400 CX500 CX600 CX700 Minimum Supported FLARE Version IBM ESS Storage Systems 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. Model Array code/firmware required Paths per device Boot support F10/F Solaris 7, 8, 9, /800T Once a host and IBM ESS system are properly configured, you can install or upgrade PowerPath. See the PowerPath for Solaris Installation and Administration Guide for installation details. Hitachi Lightning Storage 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 EMC PowerPath for Solaris Version Release Notes 11

12 Environment and System Requirements logical device, and support for booting from a Hitachi Lightning device. Model Qualified Array code/firmware Paths per device Boot support 9970V/9980V (or higher) 32 Solaris 7, 8, 9, / (or higher) Once a host and Hitachi Lightning system are properly configured, you can install or upgrade PowerPath. See the PowerPath for Solaris Installation and Administration Guide for installation details. Hitachi TagmaStore The following table shows the requirements and specifications for a PowerPath host connected to a Hitachi TagmaStore system: model numbers and firmware supported, maximum number of paths per logical device, and support for booting from a Hitachi TagmaStore device. Model Qualified Array code/firmware Paths per device Boot support USP / Solaris 8, 9, 10 Hewlett-Packard StorageWorks 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 12 EMC PowerPath for Solaris Version Release Notes

13 Environment and System Requirements logical device, and support for booting from an HP StorageWorks device. Model Minimum array code or firmware required Paths per device Boot support HP StorageWorks Disk Array xp 128/1024 HP StorageWorks Disk Array xp 48/ Solaris 8, 9, HP StorageWorks Enterprise Virtual Array (EVA) 3000/5000 VCS3.0, PowerPath does not support VCS4.001 or later 32 Not supported. HP StorageWorks Enterprise Modular HP StorageWorks MA8000/EMA12000 ACS HP StorageWorks HPXP Solaris 8, 9, 10 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. Note: Install host bus adapters (HBAs), their supporting firmware versions, and other network components using the manufacturer s directions and the settings specified in the EMC Support Matrix. Using improper settings can cause erratic failover behavior or extended response time for system I/O. EMC PowerPath for Solaris Version Release Notes 13

14 Known Problems and Limitations Known Problems and Limitations This section describes the known problems and limitations in PowerPath for Solaris. Table 7 Known Problems in PowerPath Version 4.5.0: Solaris Description Workaround Found in Version Resolved in Version powermt core dumps on issuing powermt config or powermt display if the host is connected to 16 or more arrays. Log in to the Powerlink website and download the powermt.solaris b170.tar file and follow the steps mentioned in powermt.solaris b170.readme SYMCLI functionality degrades after uninstalling PowerPath VxVM 4.1 pseudo device mappings (emcpower mappings) may become inconsistent with PowerPath pseudo device mappings. Circumstances that may cause inconsistencies include: VxVM 4.1 is uninstalled and reinstalled after a LUN configuration change. VxVM maps pseudo devices based on device information saved before the uninstall, and these mappings may differ from the current PowerPath mappings and configuration. A pseudo device instance is renamed using emcpadm, which causes VxVM 4.1 to lose the pseudo device mapping. 1. Remove PowerPath. Refer to PowerPath 4.5 for Solaris Installation and Administration Guide. 2. Confirm the no reboot required message appears. 3. Enter: symcfg discover To fix inconsistent device mappings: 1. Enter: cp /etc/vx/disk.info /etc/vx/disk.info.old 2. Enter: echo > /etc/vx/disk.info 3. Enter: vxconfigd -k EMC PowerPath for Solaris Version Release Notes

15 Known Problems and Limitations Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued) Description Workaround Found in Version Resolved in Version In a Sun Cluster 3.1 environment with VxVM 4.1, removing PowerPath with the pkgrm command may fail with the following message: EMCpower Removal: Error: PowerPath pseudo(s) still in-use, busy or mounted. Please stop all I/Os and make sure all volumes are not mounted then retry removing the package pkgrm: ERROR: preremove script did not complete successfully Removal of <EMCpower> failed When you upgrade to PowerPath 4.5 from an older version of PowerPath, third-party arrays that are not supported on the older version of PowerPath will come up as unmanaged in PowerPath In a PowerPath environment with a Leadville driver, MPXIO enabled and managing third-party devices, and the Naviagent running, a system crash occurs when you remove PowerPath from the host. Refer to Uninstalling PowerPath in an Environment With Sun Cluster 3.1 and VxVM 4.1 on page 30 for the workaround instructions. Manually manage the unmanaged array classes after you upgrade. Enter: powermt manage class=<class> Refer to the PowerPath Product Guide for more information on the powermt manage command. Stop Naviagent before you uninstall PowerPath A path to a Hitachi storage system is managed by both MPxIO and PowerPath. If your host is connected to a Hitachi storage system, and the parameter mpxio-disable is set to no (mpxio-disable=no), PowerPath will try to manage the path that is already managed by MPxIO. You can verify the status of the Hitachi storage system class by running the command powermt display options. If the status is managed, then manually unmanage the path, as described in the Workaround column. To unmanage the path: 1. Enter: powermt remove dev=all 2. Enter: powermt unmanage class=hitachi 3. Enter: powermt config EMC PowerPath for Solaris Version Release Notes 15

16 Known Problems and Limitations Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued) Description Workaround Found in Version Resolved in Version When performing a Solaris Live Upgrade from Solaris 9 to Solaris 10, you need to manually mount the /usr and /var directories. (When you perform a Solaris Live Upgrade from Solaris 8 to 9, this step is not necessary.) Manually mount the /usr and /var directories. Refer to the PowerPath 4.5 for Solaris Installation and Administration Guide for more information on the Live Upgrade procedure EMC PowerPath for Solaris Version Release Notes

17 Known Problems and Limitations Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued) Description Workaround Found in Version Resolved in Version With PowerPath 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 With SAN in a CLARiiON basic failover environment, PowerPath does not trespass LUNs when a Fibre Channel cable is pulled from the SP port. When upgrading or reinstalling PowerPath, reboot after the initial package remove, if PowerPath requested the reboot. When duplicate entries are seen, a second reboot will clear the duplicates. The PowerPath pseudo device links will be available during the second reboot. When mapping/zoning new LUNS to the host, to avoid duplicate entries: 1. Run vxddladm stop. eventsource. 2. Map/zone the new LUNS to the host. 3. Dynamically recreate the LUN device (either using cfgadm routines or HBA-specific routines to dynamically create the device nodes). 4. Run powermt config to discover and create the pseudo device links. 5. Run vxddladm start eventsource. When a host is rebooted with a path down, follow this procedure to avoid duplicate entries: 1. Run vxddladm stop eventsource 2. Reconnect the paths. 3. Run powermt config. 4. Run vxddlam start. eventsource. If vxddladm commands were not run, then reboot the system to remove the duplicate entries. Remove SAN and install SAN EMC PowerPath for Solaris Version Release Notes 17

18 Known Problems and Limitations Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued) Description Workaround Found in Version Resolved in Version R1/R2 boot support in a Symmetrix 5x71 environment does not work when the Symmetrix SPC2 flag is set to ON In a CLARiiON storage system environment, upgrading to PowerPath 4.5 when pseudo devices are in use causes a failure. File system corruption occurs during the host reboot When 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 PowerPath 4.5 with Solaris 10 is incompatible with volume managers such as VxVM 4.1 that encapsulate the root device, due to a known problem in VERITAS Volume Manager VERITAS Volume Manager 4.1 does not support PowerPath pseudo device naming with third-party arrays. Ensure that the SPC2 flag is set to OFF if your configuration includes R1/R2 boot support and Symmetrix 5x71. By default, this setting is ON. 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 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 EMC PowerPath for Solaris Version Release Notes

19 Known Problems and Limitations Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued) Description Workaround Found in Version Resolved in Version In a Solaris environment with PowerPath and a Leadville driver, running SYMCLI commands generates the following errors in /var/adm/messages: Oct 12 12:03:53 db026ops qlc: [ID kern.info] NOTICE: Qlogic qlc(1): Link ONLINE Oct 12 12:03:53 db026ops scsi: [ID kern.info] /pci@8,600000/sunw,qlc@1/fp@0,0 (fcp1): Oct 12 12:03:53 db026ops Lun=0 for target= disappeared Oct 12 12:03:53 db026ops scsi: [ID kern.info] /pci@8,600000/sunw,qlc@1/fp@0,0 (fcp1): Oct 12 12:03:53 db026ops Lun=0 for target= disappeared Oct 12 12:03:58 db026ops qlc: [ID kern.info] NOTICE: Qlogic qlc(2): Loop OFFLINE Install the appropriate SUN T-patch, or install SAN Refer to the EMC Knowledgebase solution emc for more information Sun 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 After 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) Running the powermt remove dev=all and powermt config commands on a host that has mounted the SnapView LUN makes the snapshot inactive, causing data corruption. Run the following commands before you reboot: powermt set policy=so powermt save , Rebooting a PowerPath host that is a node in a Sun 3.1 cluster and is also connected to EVA devices generates volume assign/restore messages and path dead/alive messages. These messages are also seen during node failover. Ignore the messages EMC PowerPath for Solaris Version Release Notes 19

20 Known Problems and Limitations Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued) Description Workaround Found in Version Resolved in Version 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 With third-party arrays in a cluster, reconfiguration reboot does not recover paths that are down at boot In 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 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. Use either the boot or reboot command. Do not use the boot -r or reboot -- -r command. Ignore this message. The custom settings are loaded EMC PowerPath for Solaris Version Release Notes

21 Known Problems and Limitations Table 7 Known Problems in PowerPath Version 4.5.0: Solaris (continued) Description Workaround Found in Version Resolved in Version powermt restore restores all paths to third-party arrays when periodic autorestore is set to off. This includes, among others, HPXP and Hitachi Lightning devices Using the powermt unmanage class=hitachi command to unmanage third-party arrays when the host is booted from a pseudo device prevents the system from coming up after you reboot. You see the following message when you unmanage a boot device: WARNING: One or more boot devices have been unmanaged. Update the system configuration settings as appropriate. Cannot remove device that is in use: <emcpowerx> LUNs are trespassed when the HBAs are removed one by one using the powermt remove hba=# command PowerPath installation or removal fails if pkgadd or pkgrm is interrupted Executing 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. Before you reboot the host, update the system configuration in the /etc/system and /etc/vfstab files to use native devices. Refer to the PowerPath 4.5 for Solaris Installation and Administration Guide for more information. Reboot the host and then rerun pkgadd or pkgrm. If your PowerPath registration file is the default file (/etc/emcp_registra tion), 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? EMC PowerPath for Solaris Version Release Notes 21

22 Known Problems and Limitations Limitations PowerPath for Solaris has the following limitations: In an R1/R2 boot support environment: PowerPath 4.5 does not support Sun HBAs X6767A and X6768A. R1/R2 boot support hosts must be connected directly to the Symmetrix system; they cannot be connected through the fabric. VERITAS Volume Manager does not support PowerPath pseudo device naming with third-party arrays. You can change the VxVM third-party driver mode (tpdmode) to native by entering: vxdmpadm setattr enclosure <enclosure> tpdmode=native This change also applies to any EMC devices in a mixed array environment. PowerPath cannot co-manage devices with third-party path management software such as Hitachi Dynamic Link Manager (HDLM), IBM Subsystem Device Driver (SDD), HP StorageWorks Secure Path, or HP StorageWorks Auto Path XP Virtual Array. During installation of PowerPath 4.5.0, the installation script tests for the presence of third-party path management software on the system. If such software is installed on the system, the PowerPath installation script disables support for the corresponding array type in PowerPath: If this software is present HDLM SDD HP StorageWorks Secure Path HP StorageWorks Auto Path XP Virtual Array Support for this array type is disabled in PowerPath Hitachi Lightning, Hitachi TagmaStore IBM ESS HP StorageWorks EVA, EMA, MA HP StorageWorks xp Since PowerPath coexistence is not supported by third-party array path management products, when you enable PowerPath (powermt manage class=<class>) for a class that is being managed by a third-party product, multipathing behavior is undefined. 22 EMC PowerPath for Solaris Version Release Notes

23 Known Problems and Limitations 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: If this software is present HDLM SDD HP StorageWorks Secure Path HP StorageWorks Auto Path XP Virtual Array Multipathing behavior is undefined if you execute this command powermt manage class=hitachi powermt manage class=ess powermt manage class=hphsx powermt manage class=hpxp 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 is already installed, you should disable any support by PowerPath for the relevant third-party array devices using a powermt unmanage class= command: Before you install this software HDLM SDD HP StorageWorks Secure Path HP StorageWorks Auto Path XP Virtual Array Execute this command powermt unmanage class=hitachi powermt unmanage class=ess powermt unmanage class=hphsx powermt unmanage class=hpxp PowerPath does not support load balancing and failover for applications that use the SCSI-2 Reserve/Release or Solaris MHIOCTKOWN IOCTL command set in an EMC Invista, IBM ESS, Hitachi Lightning, Hitachi TagmaStore, or HP StorageWorks environment. EMC PowerPath for Solaris Version Release Notes 23

24 Known Problems and Limitations If you deploy any such applications, you must set the load balancing and failover policy to nr (No redirect). Refer to the powermt set policy command description in the PowerPath Product Guide for more information on setting load balancing and failover policies. The following is an issue with Sun s native driver. When using Sun's qlc driver, you might see the following message on the system console at boot: emcp: info: Not all paths to <array_type> <array_number> vol <volume_number> are dead. Any application configured to use the devices too soon (vfstab mounts for instance) will fail to open its device. Note: The paths will be autorestored in time, or you can run powermt restore to restore them. To avoid this situation, when using Sun's native driver: 1. Add the following line to the /etc/system file: set fcp:ssfcp_enable_auto_configuration=1 2. Reboot the host. Using PowerPath pseudo names under VxVM 4.0 is subject to several limitations. Refer to VxVM 4.0 and PowerPath Pseudo Names on page 27 for details. PowerPath cannot failover path-specific requests, such as dev_info. 24 EMC PowerPath for Solaris Version Release Notes

25 Technical Notes Technical Notes This section contains additional information on PowerPath not covered in the core documents. This section includes the following subsections: Upgrading From PowerPath 3.0.x on page 25 Upgrading From PowerPath 4.0.x on Symmetrix Systems on page 25 VxVM 4.0 and PowerPath Pseudo Names on page 27 Pseudo Names With VxVM 4.1 and PowerPath on page 28 Uninstalling PowerPath in an Environment With Sun Cluster 3.1 and VxVM 4.1 on page 30 HP StorageWorks Controller and Port Names on page 30 Removing HP StorageWorks Secure Path on page 31 Upgrading From PowerPath 3.0.x When upgrading from PowerPath 3.0.x to PowerPath 4.x, run the chmod +r /etc/powermt.custom.saved command to enable all read permissions on the saved version of the powermt.custom file after uninstalling 3.0.x and before installing 4.x. If you do not enable read permissions on the powermt.custom.saved file, PowerPath may not be able to perform an upgrade installation, depending on the version and patch level of Solaris running on the host. Upgrading From PowerPath 4.0.x on Symmetrix Systems Note: In the vast majority of cases, upgrading from PowerPath 4.0.x to PowerPath 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, HK ), contact Customer Support before upgrading to PowerPath Customer EMC PowerPath for Solaris Version Release Notes 25

26 Technical Notes Support will provide you with a tool and procedure to follow to safely upgrade your server. If you remove PowerPath 4.0.x and install PowerPath without contacting Customer Support, the upgrade to PowerPath will stop with the following message: emcp_registration version 402 detected. emcpupgrade: error - configuration files corrupted. emcpupgrade: Detected inconsistency with saved Symmetrix serial numbers * EMCpower Installation: * * Can not upgrade at this time. * There is a problem with the saved powerpath config files. * Please contact customer service to complete UPGRADE * EMCpower Installation: * * Configuration files conversion unsuccessful!!! * The PowerPath 4.5 Package was successfully installed, but there is a known * issue with your configuration files. * * In order to upgrade your configuration, please contact EMC Customer Service * for assistance. Do not reboot. Do not restart your applications. * Consult the 4.5 Release Notes All trademarks used herein are the property of their respective owners. Installation of <EMCpower> was successful. In addition to the console output, the following will appear in the system log: date and time system Can[16107]: [ID daemon.notice] not upgrade at this time. There is a problem with the saved powerpath config files. date and time system Contact[16434]: [ID daemon.notice] Customer Service. Do not reboot. Do not restart your applications. Consult the 4.5 Release Notes. If this happens, we strongly recommend that you: 1. Remove PowerPath 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 emc EMC PowerPath for Solaris Version Release Notes

27 Technical Notes VxVM 4.0 and PowerPath Pseudo Names You can use the powervxvm install utility to make PowerPath pseudo device names available under VxVM 4.0. Be aware that both native device names and PowerPath pseudo device names will be visible to VxVM 4.0. Both names will be reported in vxdisk list output, which typically looks like this: c3t2d1s2 auto:none - - online invalid emcpower0c simple - - online invalid Both devices represent the same LUN. To avoid confusion, you can use the VxVM vxdiskadm utility to exclude the native devices (in the example above, c3t2d1s2) from the VxVM view. Refer to VxVM vxdiskadm documentation for details. Upgrading to VxVM 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 Place PowerPath pseudo device names under VxVM 4.0 using powervxvm. You can do this for all emcpower devices, or for individually selected devices: For all devices, run the following command: powervxvm define For individual devices: a. Run the following command: powervxvm install Note: Important: Use powervxvm install and not powervxvm init. powervxvm init corrupts the rootdg for some versions of VxVM. b. Select Option 3 Install one device at a time. c. For each device to be used under VxVM 4.0, select Option 2 to define. EMC PowerPath for Solaris Version Release Notes 27

28 Technical Notes! CAUTION Do not initialize the emcpower disks if they currently contain VxVM volumes. 2. Re-import previously existing disk groups/volumes. The simplest way to do this it to reboot using the following command: shutdown -i6 However, if you cannot reboot, use the following procedure: a. Request that VxVM re-import any disk groups by restarting vxconfigd; run the following command: vxdctl enable b. For each disk group that was rediscovered, request that all volumes on that disk group be restarted; run the following command: vxvol g diskgroup startall Limitations PowerPath pseudo devices are identified as simple disks by VxVM. Thus: VERITAS CDS (common-disk-schema) is not supported with PowerPath pseudo device names. The cds attribute must be disabled when creating the disk group. Run a command like the following: vxdg init symmdg disk=emcpower0c cds=off The default for VxVM 4.0 disk groups is CDS=ON. Therefore, if you have existing VxVM 4.0 disk groups/volumes (without PowerPath) you cannot use powervxvm scripts to migrate to PowerPath pseudo devices. Pseudo Names With VxVM 4.1 and PowerPath When you install VxVM 4.1 in a PowerPath environment, VxVM converts any EMC Symmetrix and CLARiiON devices with native names to pseudo names (emcpower names). EMC recommends using the default naming convention (pseudo names) for EMC storage devices. However, it is possible to configure native names (c#t#d# names) for EMC devices, as described in this section. 28 EMC PowerPath for Solaris Version Release Notes

29 Technical Notes Note: The powervxvm utility does not support pseudo device names for third-party devices in the VERITAS device list. The following error message appears when you try to bring third-party device s into the VxVM device list: VxVM vxdisk ERROR V Device emcpower3s2: init failed: device path not valid. Pseudo device names for third-party arrays are not supported with VxVM 4.1. You can only use pseudo device names for Symmetrix and CLARiiON devices. Changing EMC Devices to Native Device Names Note: Use the procedure in this section only if the default disk-naming scheme is set to operating system based naming, and the TPD-controlled enclosure does not contain fabric disks. To change EMC storage devices from the default pseudo names to native names: 1. View the pseudo device names that appear after installing VxVM 4.1. Enter: # vxdisk list Output: DEVICE TYPE DISK GROUP STATUS emcpower10s2 auto:sliced disk1 mydg online emcpower11s2 auto:sliced disk2 mydg online emcpower12s2 auto:sliced disk3 mydg online emcpower13s2 auto:sliced disk4 mydg online emcpower14s2 auto:sliced disk5 mydg online emcpower15s2 auto:sliced disk6 mydg online emcpower16s2 auto:sliced disk7 mydg online emcpower17s2 auto:sliced disk8 mydg online emcpower18s2 auto:sliced disk9 mydg online emcpower19s2 auto:sliced disk10 mydg online 2. Change the pseudo names to native names. Enter: # vxdmpadm setattr enclosure <enclosure> tpdmode=native Where <enclosure> is the enclosure name of the EMC device. Example: # vxdmpadm settattr enclosure EMC0 tpdmode=native 3. List the device names and note the different naming convention in the Device column. Enter: EMC PowerPath for Solaris Version Release Notes 29

30 Technical Notes # vxdisk list Output: DEVICE TYPE DISK GROUP STATUS c6t0d10s2 auto:sliced disk1 mydg online c6t0d11s2 auto:sliced disk2 mydg online c6t0d12s2 auto:sliced disk3 mydg online c6t0d13s2 auto:sliced disk4 mydg online c6t0d14s2 auto:sliced disk5 mydg online c6t0d15s2 auto:sliced disk6 mydg online c6t0d16s2 auto:sliced disk7 mydg online c6t0d17s2 auto:sliced disk8 mydg online c6t0d18s2 auto:sliced disk9 mydg online c6t0d19s2 auto:sliced disk10 mydg online If tpdmode is set to native, the subpath with the smallest device number is displayed. Uninstalling PowerPath in an Environment With Sun Cluster 3.1 and VxVM 4.1 If you attempt to remove PowerPath in a Sun Cluster 3.1 with VxVM 4.1 environment, and pkgrm fails, enter the following commands. Then retry pkgrm. # cd /dev/rdsk # for path in `ls emcpower*c` do /usr/sbin/vxdmpadm -f disable path=${path} done # Uninstall PowerPath following the directions in the PowerPath 4.5 for Solaris Installation and Administration Guide. HP StorageWorks Controller and Port Names PowerPath names for HP StorageWorks EVA and HSG80 controllers and ports differ from the names in the array GUIs. This section describes the differences. HP StorageWorks EVA Names PowerPath identifies controllers A and B exactly as Command View EVA does. PowerPath port numbers are one lower than Command View EVA port numbers. 30 EMC PowerPath for Solaris Version Release Notes

31 Technical Notes Names are mapped as follows: Command View EVA name PowerPath name A-1 A-0 A-2 A-1 B-1 B-0 B-2 B-1 HP StorageWorks HSG80 PowerPath names the bottom controller A and the top controller B. PowerPath port numbers are one lower than HSG Element Manager port numbers. Names are mapped as follows: HSG Element Manager name PowerPath name Bottom-1 A-0 Bottom-2 A-1 Top-1 B-0 Top-2 B-1 Removing HP StorageWorks Secure Path After you remove HP StorageWorks Secure Path from a system that has JNI/AMCC FCA-1063 HBAs configured, the powermt display command shows only one HBA, or no HBAs. 1. Remove Secure Path bindings from the HBA configuration (.conf) file and sd.conf. Establish PowerPath static bindings as follows: LPFC: Add to lpfc.conf: EMC PowerPath for Solaris Version Release Notes 31

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 Bindings target4_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: # EVA5000 name="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 32 EMC PowerPath for Solaris Version Release Notes

33 Documentation Documentation PowerPath Documentation This section provides a list of the documentation that supports PowerPath for Solaris. The following table lists the PowerPath documentation set; all manuals are available from EMC Corporation. Electronic versions of all PowerPath manuals are available on the Powerlink website: These manuals are updated periodically, and the updated manuals are posted on the Powerlink website. Name PowerPath 4.5 for Solaris Installation and Administration Guide EMC PowerPath 4.5 for Solaris Release Notes PowerPath 4.5 Product Guide EMC PowerPath 4.5 Quick Reference Related 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 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. EMC PowerPath for Solaris Version Release Notes 33