This action might not be possible to undo. Are you sure you want to continue?
Version 5.0.0 and Point Releases
P/N 300-003-593 Rev A09 June 17, 2008
These release notes contain supplemental information about EMC PowerPath, versions 5.0.0, 5.0.1, and 5.0.2. Topics include:
◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆
Product description.............................................................................. 2 New features and changes .................................................................. 2 Fixed problems ..................................................................................... 6 Environment and system requirements .......................................... 12 Known problems and limitations .................................................... 17 Technical notes .................................................................................... 32 Documentation ................................................................................... 41 Software media, organization, and files.......................................... 43 Installation ........................................................................................... 44 Troubleshooting and getting help .................................................... 44
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®, EMC Invista®, IBM ESS, Hitachi Lightning, Hitachi TagmaStore, HP StorageWorks xp, EVA, EMA, and MA storage systems. PowerPath 5.0.x supports iSCSI and Fibre Channel environments.
New features and changes
This section describes new features and changes in PowerPath 5.0.x releases.
PowerPath 5.0.2 is a stand-alone, full package release that includes:
All functionality included in PowerPath 5.0.0 and PowerPath 5.0.1 Enhancements to the emcpadm utility, as described in “emcpadm enhancements” on page 33 Bug fixes, as described in “Fixed problems” on page 6.
You do not need to install PowerPath 5.0.0 or 5.0.1 before installing PowerPath 5.0.2. You can also upgrade directly to PowerPath 5.0.2 from earlier versions of PowerPath, as described in the PowerPath 5.0 for Solaris Installation and Administration Guide. PowerPath 5.0.2 for Solaris addresses a potential device persistence issue when upgrading from PowerPath 4.x to PowerPath 5.0.0. While the PowerPath 5.0.1 patch also fixes the device persistence issue, upgrading directly to PowerPath 5.0.2 provides a simpler solution.
PowerPath 5.0.1 is a required patch release. If you are running PowerPath 5.0 for Solaris, download this patch from the Powerlink™ website (http://Powerlink.EMC.com), and follow the installation instructions in the ReadMe.txt file posted with the patch.
Note: You must install PowerPath 5.0.0 before installing PowerPath 5.0.1.
EMC PowerPath for Solaris Version 5.0.0 and Point Releases Release Notes
New features and changes
PowerPath 5.0.1 has the following new features and changes:
Support for CLARiiON iSCSI storage systems. “PowerPath support with iSCSI” on page 35 contains more information on iSCSI configurations. Support for R1/R2 boot environments on Solaris SPARC hosts. Several bug fixes, as described in “Fixed problems” on page 6.
PowerPath 5.0.0 for Solaris has the following new features and changes:
Support for AMD Opteron Processors. The next section, “AMD Opteron support” on page 5, lists more information on support for Opteron hosts. Support for PowerPath Migration Enabler. PowerPath Migration Enabler is a host-based migration tool that requires a separate product license. For more information about PowerPath Migration Enabler, refer to the PowerPath Migration Enabler Release Notes and the PowerPath Migration Enabler User’s Guide, available on the Powerlink website (http://Powerlink.EMC.com).
New powermt commands. A brief description of each command follows. For more information, refer to the PowerPath 5.0 Product Guide. • powermt disable hba — Disables an HBA port, and closes all devices configured through the port. The port disable command disables only the devices configured on the virtual bus, and not the devices for the entire port. • powermt display hba_mode — Displays HBA information, including whether an HBA is enabled or disabled. • powermt display latency — Displays path latency information, including the last and the longest I/O completion times on each path. • powermt display nonvirtual — Displays information about the physical device associated with an Invista Virtual Volume. • powermt display port_mode — Displays storage system port information, including whether a port is enabled or disabled. • powermt enable hba— Enables an HBA port that was disabled previously, and resumes I/O on the port.
EMC PowerPath for Solaris Version 5.0.0 and Point Releases Release Notes
New features and changes
• powermt set path_latency_monitor — Turns path latency monitoring on or off. • powermt set path_latency_threshold — Sets the path latency threshold. When the latency time exceeds the threshold value, a message is sent to the log file. • powermt set port_disable — Enables or disables a storage system port and closes all devices configured through the port.
Changed powermt commands. A brief description of the changes follows. For more information, refer to the PowerPath 5.0 Product Guide. • powermt display options — Includes new output on path latency monitoring, including whether path latency monitoring is enabled and the value of the latency threshold, if one is set. • powermt manage — Is now supported on EMC storage systems (Symmetrix, CLARiiON, and Invista systems). Previously, it was supported only on third-party storage systems. • powermt unmanage — Is now supported on EMC storage systems (Symmetrix, CLARiiON, and Invista systems). Previously, it was supported only on third-party storage systems. • powermt display — Contains the new arguments wide|width=columns, where wide sets a range for the column width of the display; width sets the display width to a constant value within the range of 80 to 160 columns.
Support for the CLARiiON CX3 Series storage systems. Support for the following HP StorageWorks array and array code: • HP StorageWorks Enterprise Virtual Array (EVA) 8000 • Virtual Control Software (VCS) version 4.x on HP StorageWorks Enterprise Virtual Array (EVA) 3000 and 5000
Note: The HP StorageWorks EVA 8000 systems and the EVA 3000/5000 systems with VCS 4.x are managed with the hpxp class, and not with the hphsx class. However, the HP StorageWorks EVA 3000/5000 systems with VCS 3.x are managed with the hphsx class.
Refer to “powermt class arguments with HP StorageWorks EVA arrays” on page 38 for more information.
EMC PowerPath for Solaris Version 5.0.0 and Point Releases Release Notes
Currently. Device names are different than SPARC device names. one of which can be the Solaris partition. emcpmpap. the fmthard command can manage all 16 slices. The following storage systems are supported: • EMC arrays • Hitachi Lightning and Hitachi TagmaStore storage systems (no other third-party arrays are supported) ◆ PowerPath requires the Entire Solaris Software Group version of Solaris 10. The naming convention cXtYdZ[p1–p4] is used to access blocks from defined partitions. Other Solaris software groups.0 and Point Releases Release Notes 5 .0.0 by the emcpmpx extension. each disk can have up to four partitions. ◆ Device naming On the Solaris Opteron platform.0 compatibility with AMD Opteron hosts: ◆ ◆ PowerPath Migration Enabler is not supported. The emcpower naming convention that accommodates all 16 slices is: emcpower#[a-p] EMC PowerPath for Solaris Version 5. On Opteron hosts. The Opteron platform uses a VTOC with 16 slices per disk. Refer to “powermt class arguments with HP StorageWorks EVA arrays” on page 38 for more information. and emcpmpaa extensions present in previous PowerPath releases have been replaced in PowerPath 5. slices are set up differently than on the SPARC platform. such as the Core System Support Software Group. this change applies only to HP StorageWorks EVA 3000 or 5000 arrays with VCS 3. The naming convention cXtYdZ[s0–s15] is used to access blocks from VTOC slices. active-passive arrays now use basic failover (bf) as the default load balancing and failover policy—instead of no redirect (nr).New features and changes ◆ Non-EMC. as explained in the next section. The operating system uses the naming convention cXtYdZp0 to access the entire disk. emcpmpc. The format utility can manage only 10 slices. ◆ AMD Opteron support Note the following regarding PowerPath 5.x. The emcpmp. are not supported by PowerPath.
0.0 and Point Releases Release Notes .0.0. and you are using HighRoad 3. Effective with HighRoad version 4. End-of-life announcement Please be aware that EMC has announced end-of-life (EOL) for PowerPath Volume Manager (PPVM) functionality for Solaris.EMC.0.2 or earlier. This is effective with the release of PowerPath 4.5.2” on page 7 “PowerPath 5.0. PowerPath 4.5 for HP-UX. or 5.com 6 EMC PowerPath for Solaris Version 5. EMC has also announced its intention to end-of-service-life PPVM functionality for Solaris. EMC HighRoad PowerPath 5.1” on page 9 “PowerPath 5. refer to E-Lab Issue Tracker on Powerlink.0” on page 11 For the most up-to-date fix information for EMC products. you need to upgrade to HighRoad version 4. To access blocks from the fdisk partition or use the fdisk command. native device names must be used. AIX and HP-UX environments.0. Fixed problems This section describes the fixed problems in each release of PowerPath 5. back up that data and destroy all PPVM volume groups before installing PowerPath 4. Discontinued features in PowerPath This section includes information about discontinued features in PowerPath.0. disk protection for Symmetrix is included in the HighRoad software. If you want to upgrade to PowerPath 184.108.40.206.Fixed problems Note: PowerPath does not provide pseudo-device name support for the Opteron fdisk partitions (native device names cXtYdZ[p0-p4]). It includes these subsections: ◆ ◆ ◆ “PowerPath 5. and PowerPath 4.0 or later before upgrading to PowerPath 5.4 for AIX release.4.0 does not include intrinsic disk protection for EMC HighRoad® disks on Symmetrix storage systems.4 for Solaris.x for Solaris.0. 4. AIX and HP-UX effective March 2006.0. If you have any data on PPVM volumes. http://Powerlink.
255639 232883 245213 A panic occurs in the emcpIoctlGuts for the DKIOCINFO ioctl.1 Resolved in version 5.2 5.0.2 Table 1 Table 1 describes the fixed problems in PowerPath 5. EMC Knowledgebase Solution emc159584 also addresses this issue.2 5.2 for Solaris Found in version 5. Renaming emcpower devices to include four or fewer digits is supported.0 on a Solaris 10 host may cause a host panic.0.2 5. 256521 The powermt set port_disable command does not persist across reboots for Hitachi/HPXP devices.2 5.0.1 5.0.1 for Solaris.0 and Point Releases Release Notes 7 .0.2 5.1 220.127.116.11. the powermt display command aborts. 254674 Installing PowerPath 5.0 5.0.2 Description 259113 With PowerPath 5. 255342 With PowerPath 18.104.22.168 on a Solaris 10 U3 or Solaris 10 U4 host.0. 255284 A TimeFinder split operation fails when you use the -ppath option. a host panic occurs when using emcpadm to rename a pseudo device to a value of 4095 or greater (for example. 257350 The PowerPath 5.2 EMC PowerPath for Solaris Version 5.0.0 powermt watch paths class=clariion command displays Clariion in the result.1 5. renaming emcpower devices to include five or more digits may cause a host panic. 254631 When a Clariion LUN is removed from a Storage Group.1 5.0.0. Fixed problems in PowerPath 5. rebooting the host can take from 2 to 4 hours.Fixed problems PowerPath 22.214.171.124 5.1 126.96.36.199.1 on a Solaris host.2 5.2 5. PowerPath logs the following message: Volume ID has changed 5.0. emcpower4095).2 for Solaris.2 5.1 5.0. The powermt display port_mode command will not display "Disabled" for Hitachi/HPXP array ports even though it may indeed be disabled.0.1 5. A value between 0 and 4094 does not cause a host panic. This breaks the automation scripts on all the OS platforms.0. 255269 With PowerPath 188.8.131.52.0.0.0. 257340 257867 After upgrading to PowerPath 5.
5.5.0 5. followed by a host reboot.2 5.1 5. 254232 The powermt command display ports dev=<Clariion device> displays the paths as 'unlicensed and alive (u.1 Resolved in version 5.0.0 in a Symmetrix environment does not support Veritas Cluster Server with I/O fencing (also called disk fencing). 252057 Failover time with PowerPath 5. This change is related to issue 230614.0.0 5.0 5.0.2 for Solaris (continued) Found in version 5. 252308 When a Fibre Channel cable is disconnected.2 184.108.40.206.1 and Solaris 10 is slower than expected. the failure detection occurs for paths through which IO is happening.0.0. PowerPath reports the path as Degraded.0.0.0. or • Any Solaris 10 system with Sun patch 118833-36 or later 245709 The Recover All option should be checked during a clean shutdown of PowerPath. 252928 With Powerpath 5.0.2 5.0. 248747 The System volume mirroring of Fujitsu's Volume Manager GDS is not supported on hosts with PowerPath and: • Solaris 10 Update 3. 250029 PowerPath no longer writes to the PowerPath configuration file when you run the powermt display command.0. 235369 PowerPath 5.Fixed problems Table 1 Fixed problems in PowerPath 5.1 5. PowerPath may take from 10 minutes to 24 hours to reacquire the path.0.0 and Point Releases Release Notes .0.0 5. causes a Solaris zettabyte file system (ZFS) storage pool to lose connection to PowerPath pseudo devices.2 4.2 5. 254242 254656 256288 253417 A trespass from one SP to another on a CLARiiON system.1 5.2 5.2 8 EMC PowerPath for Solaris Version 5.0.0. in which information related to booting from a LUN was removed from a PowerPath configuration file.0.v)' when it should be 'active and alive (a.1 installed ion a Solaris host.0. the CD-ROM automount function no longer works if a CD disk is not present when the system boots.2 Description 254310 When periodic autorestore is set to OFF for all classes.0 5.2 220.127.116.11.2 5.v)'. When the cable is reconnected.1 5.
1 Description 247441 The emcpower device mappings may change when a host reboots. 240457 PowerPath on Solaris Opteron hosts does not support 64-bit libraries with Solutions Enabler and CLARiiON Navisphere.1 5.1 EMC PowerPath for Solaris Version 5.1 5.0 Resolved in Version 5.0. 244235 Added broadcast clear service action (0x3) to all paths to a logical volume in agreement with Symmetrix microcode team. 18.104.22.168 5.2 PowerPath 5.0.0 5. 241481 After upgrading from PowerPath 4. Please wait.2 Description 227060 After installing PowerPath 4. This fix is also included in PowerPath 5. 240176 After installing PowerPath.5 to PowerPath 5.1 for Solaris. Please wait.0.0.0.5.0.0.1 for Solaris Found in Version 4. Fixed problems in PowerPath 22.214.171.124 or PowerPath 5. a boot from SAN configuration with pseudo devices does not work.0 5.1 Table 2 Table 2 describes the fixed problems in PowerPath 5.0 5.Fixed problems Table 1 Fixed problems in PowerPath 5.0.0 Resolved in version 5.0. This issue has been fixed in PowerPath 5.0.0 and Point Releases Release Notes 9 .0.2. 5. 241164 The powermt set periodic_autorestore=off class=<class> command does not affect only the specified storage system class. the following error messages appear when the host reboots: Configuring /dev and /devices Configuring the /dev directory (compatibility devices) //catalog: No such file or directory Setting up paths The system is coming up.0.0 5.0. the following messages appear on the console at boot time: Configuring /dev and /devices Configuring the /dev directory (compatibility devices) //catalog: No such file or directory Setting up paths The system is coming up.126.96.36.199.2 for Solaris (continued) Found in version 4.0.1 5.0.
0. 235890 R1/R2 boot environments are unsupported in PowerPath 5. 5.0.0 5.0 5.0 in a Symmetrix environment does not support Veritas Cluster Server with I/O fencing (also called disk fencing).0.com emcp: [ID 801593 Assigned volume 60060160969B16006502B40174BDDA11 to Jul 26 12:22:02 lclc018.0 5. 237890 232631 On some hosts.0.1 5.emc.5.0.0 and Point Releases Release Notes .1 5. or powermt display concurrently with the Solaris scswitch command.0 5. when you enter powermt display dev=<device>.0.notice] Info: SPB 5.0 for Solaris Installation and Administration Guide.0. available on the Powerlink website. when you disconnect a cable from the default CLARiiON SP.0.0 to PowerPath 5.1 Description 238694 On Opteron hosts with an unlicensed version of PowerPath and the failover policy set to basic failover (bf). pseudo-device mappings are lost.0.5.0. the output shows the LUNs as trespassed to SPB on the CLARiiON.0.0. 235369 PowerPath 5. the following extraneous messages appear when you reboot a CLARiiON SP: Jul 26 12:22:01 lclc018.0 5.0. 238652 On a Solaris Opteron host with an unlicensed version of PowerPath. Refer to the PowerPath 5.0. However.Fixed problems Table 2 Fixed problems in PowerPath 5.1 5. powermt config.lss.1 (Output truncated) 238378 236155 You cannot uninstall PowerPath from the host when enclosure-based device naming is used (with VxVM). 238355 227783 Sun Dynamic Reconfiguration (DR) operations are unsupported with PowerPath 5.0.0 Resolved in Version 5.1 for Solaris (continued) Found in Version 5.0.0. for more information on R1/R2 boot support with PowerPath.0.0 5.1 10 EMC PowerPath for Solaris Version 5.1 4.1 5.0 5.0. messages informing you of LUN trespassing do not appear.0.0.emc.com emcp: [ID 801593 Assigned volume 60060160969B16006502B40174BDDA11 to kern.0. 237877 On Opteron hosts in a Sun Cluster environment.notice] Info: SPA kern. when you upgrade from PowerPath 4. a Sun Cluster host panics when you run powermt remove.lss.
Solutions Enabler storapid crashes intermittently. 231976 226256 powermt core dumps on issuing powermt config or powermt display if the host is connected to 16 or more arrays. and Solutions Enabler 6.0 5.0.0. the node comes up cleanly afterwards.Fixed problems Table 2 Fixed problems in PowerPath 5. This can cause a delay in the completion of I/O and possibly cause unnecessary failovers. 246764 An attempt to thaw a file system using the BCV split command fails.1 Description 233971 In a Sun Cluster 3.1 environment with VxVM 4.1.1 for Solaris (continued) Found in Version 5.0 and Point Releases Release Notes 11 .0.5.0 5.x.0. 188.8.131.52.0 4.0.0 5.0 Resolved in Version 184.108.40.206.1 PowerPath 5.0. Path latency monitoring is a new feature in which PowerPath monitors paths and reports slow paths by sending a message to the log file.0 Product Guide for detailed information on these commands.3.0 for Solaris. 215189 Path degradation resulting from a hardware issue causes HBAs and the sd driver to retry I/Os. Refer to “New features and changes” on page 2 for a the list of the new powermt commands and to the PowerPath 5. Leadville drivers. switching all resources from one node to another causes a failfast panic on the source node.0.0 EMC PowerPath for Solaris Version 5.0 4.3. This fix is also available for PowerPath 4.0 Resolved in Version 5.4. 232368 230229 The Solaris sd driver b_failfast feature is unsupported with PowerPath installed. and the cluster regains full functionality.0 for Solaris Found in Version 4.0.0 Table 3 Table 3 describes the fixed problems in PowerPath 5.0 Description 248638 217622 On Solaris hosts with PowerPath 4.0 5. However.0 as a hotfix.0 4.5.0. Fixed problems in PowerPath 5.5. 4.3.
software. refer to the E-Lab™ Interoperability Navigator (formerly ESN Builder).0 Product Guide for detailed information on these commands. It also includes information about supported host models. and connectivity devices.EMC.0 Resolved in Version 5. such as online HBA replacements and switch firmware updates.0 for Solaris (continued) Found in Version 4. such as information about the hardware. To access the E-Lab Interoperability Navigator: 1. E-Lab Interoperability Navigator For interoperability information. New powermt commands allow you to disable an HBA or storage-system port. This capability supports hardware service procedures.3. 12 EMC PowerPath for Solaris Version 5. Note: Information in E-Lab Navigator takes precedence over the information in this release notice. host bus adapters.0 Description 209560 You can now disable specified storage and HBA ports in PowerPath.Environment and system requirements Table 3 Fixed problems in PowerPath 5.0.com).0 and Point Releases Release Notes .0. Environment and system requirements This section describes where to find interoperability and host configuration information. available on the Powerlink website (http://Powerlink. Interoperability information PowerPath interoperability information appears in the E-Lab Navigator as described in the next section. available on Powerlink. Go to Powerlink at http://Powerlink.0. operating system revisions. Refer to “New features and changes” on page 2 for a list of the new powermt commands and to the PowerPath 5. and includes notes not found in other sources.EMC.com. You can also find configuration information in the EMC Host Connectivity Guide for Sun Solaris. and networked storage components that are tested and compatible with both EMC storage systems and third-party storage systems.
Consult these resources before you undertake any of the following common system or network management tasks: EMC PowerPath for Solaris Version 5. Scroll down to the Infrastructure Software heading. d. Select the operating system and model. Note: Information in the host connectivity guide takes precedence over the information in this release notice. EMC Host Connectivity Guide (EMC storage arrays) The EMC Host Connectivity Guide for Sun Solaris describes the features and setup procedures for host interfaces to EMC Symmetrix and CLARiiON storage systems. and click the PowerPath PDF. b. Changing any system component can change the way PowerPath manages storage paths. or when changing system components. For interoperability information on PowerPath with third-party arrays: a. and then select the product version. the EMC Host Connectivity Guide for Sun Solaris. From the Support menu.0 and Point Releases Release Notes 13 . consult the E-Lab Navigator. 3. b. click the Combined Results link to view the interoperability information for the PowerPath software you selected. Before you install PowerPath. In the Results section on the right side of the page. Click the PDFs and Guides tab. c. e. From the pull-down menu at the top right of the page. Click the Wizards tab. 4. select Interoperability/Compatibility/Configuration> E-Lab Interoperability Navigator. Select PowerPath from the Product list.Environment and system requirements 2. Host connectivity guides are updated quarterly and published on the Powerlink website.0. For interoperability information on PowerPath with EMC arrays: a. Click Launch E-Lab Interoperability Navigator. and the PowerPath for Solaris Installation and Administration Guide. select Software Support Wizard.
or the host bus adapter. switches) of your network configuration.0. Using improper settings can cause erratic failover behavior or extended response time for system I/O. Change components (for example. Change the storage network zoning or device assignments. their supporting firmware versions. or adapter cable on the system that hosts PowerPath.0 and Point Releases Release Notes . (Refer specifically to the Application Software chapter for your storage system model. Change or replace a host bus adapter type. To properly install PowerPath on a host 14 EMC PowerPath for Solaris Version 5. EMC storage systems This section includes information on EMC arrays with PowerPath that is not included in the E-Lab Interoperability Navigator. Change the array or storage system connected to the host. and other network components using the manufacturer’s directions and the settings specified in the E-Lab Interoperability Navigator. ◆ ◆ ◆ ◆ ◆ Disk space requirements The following table shows minimum disk space requirements for Solaris.Environment and system requirements ◆ Upgrade or change the host OS.) Change the model of the system that hosts PowerPath. Table 4 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 Connectivity requirements Install host bus adapters (HBAs). CLARiiON support PowerPath installation is an integral part of a CLARiiON setup and configuration procedure.
Note: CLARiiON customers receive PowerPath with the CLARiiON Utility Kits that ship with CLARiiON CX.0. Refer only to these documents for prescribed installation information when using AX-Series storage systems. and FC-Series Storage Systems. referred to as PowerPath SE.Environment and system requirements with a CLARiiON array. EMC PowerPath for Solaris Version 5. and troubleshooting documents are located on the AX100 or AX150 support website. You can download the Platform Kit from the HP website. planning.and CX3-series storage systems.0 and Point Releases Release Notes 15 . HP Platform Kits HP requires installation of a host Platform Kit. you must execute the following command on the host (to allow other VxVM commands to be used): vxddladm addjbod vid=EMC pid=Invista pagecode=0x83 Note: Refer to Symantec documentation for license requirements and other details. which contains the drivers supported with the specific storage system. CLARiiON AX-Series installation. Please refer to Important Information About PowerPath SE for more information on the CLARiiON configurations supported by PowerPath SE. refer to the support documentation that shipped with your storage system. Before creating Invista Virtual Frames that will be accessed by the host. CX-Series. For information on accessing the site. Invista storage virtualization VxVM interaction with Invista requires PowerPath on the host. provides basic failover for single HBA host configurations without the use of a license key. This version of PowerPath. AX-Series. Third-party storage systems This section includes information on third-party arrays with PowerPath that is not included in the E-Lab Interoperability Navigator. There you will find step-by-step instructions for installing PowerPath and other CLARiiON software. refer to the EMC Installation Roadmap for CX3-Series. Symmetrix support There are no configuration notes for Symmetrix storage systems.
HBA driver settings The following table describes changes to the default driver configuration files required by PowerPath 5. You can download the ASL from the VERITAS website.0.0.0 and Point Releases Release Notes . you must install the VERITAS Array Support Library (ASL) for your particular storage system after you install VxVM.Environment and system requirements Interoperability with VxVM For PowerPath 5.0.x for Solaris SPARC with third-party storage systems.x for Solaris SPARC to fully interoperate with VERITAS Volume Manager (VxVM) on third-party arrays. Solaris SPARC: HBA driver settings—third-party storage systems PowerPath setting HBA driver Emulex Parameter automap linkdown-tmo lun-queue-depth num-iocbs tgt-queue-depth no-device-delay Default setting 0 30 30 1024 0 0 Setting 0 60 20 2048 512 0 Required for All third-party systems All third-party systems All third-party systems All third-party systems All third-party systems All third-party storage systems Table 5 16 EMC PowerPath for Solaris Version 5.
Verify the NFS mount is accessible: df -k 5. the installation proceeds as expected. Workaround Run powermt(1) to determine which paths/ports failed.0.0 on a Solaris Opteron host. Known problems in PowerPath version 5. If you encounter this problem: 1.1 — 258139 When installing PowerPath 5.0 Resolved in Version — Description 277717 PowerPath logs the wrong port name when paths fail for EVA arrays managed through the hpxp LAM (EVA8000 and EVA3000/EVA5000 running with VCS firmware 4. Known problems Table 6 Table 6 shows known problems in PowerPath 5. 5.x for Solaris Found in Version 5.0. the NFS service goes offline if the customer has existing NFS mount points and fails to restart.0. Kill the NFS mount/mountall commands started by the NFS start service.0 — EMC PowerPath for Solaris Version 5.Known problems and limitations Known problems and limitations This section describes the known problems and limitations in PowerPath 5. SUN has developed the following patches: • For a SPARC processor.0. A reboot is required after the installation of the 2 new patches. • For Opteron. If the package name is provided as part of the pkgadd command.0 and Point Releases Release Notes 17 .1. Enable the NFS client service: svcadm enable -r nfs/client 5. the patch numbers are 125551-02 and 119042-11.x for Solaris. if you do not include the package name as part of the installation command (pkgadd -d <package name>).0. Disable the NFS client service: svcadm disable nfs/client 3.x).0.x is installed before Veritas Volume Manager.x for Solaris. 4. Verify the NFS client service is offline. Enter: svcs | grep nfs 2. the patch number is 125552-02.0. 259100 Solaris 10 hangs at boot time if Powerpath 5.0.
2 Change the timeout_seconds value from 30 to 120 in the following configuration files: • /var/svc/manifest/sy stem/filesystem/vol fs.0 and Point Releases Release Notes . 259869 Periodic autorestore does not automatically restore dead paths to a device on AMD Opteron host. Workaround 5. the volume management file system service.2 on AMD Opteron hosts disables volfs. the line in which this parameter would be set is omitted. I/O fails when the owner SP of a LUN is changed (for example.0. Run the powermt restore command to restore the paths.xml • svcadm enable volfs — 18 EMC PowerPath for Solaris Version 5. repeat the line in which the parameter is set. 259516 Installing PowerPath 5. Use the highest value you can find in /etc/system. 258316 PowerPath adds parameter settings at the end of /etc/system . 255066 If a CLARiiON disk is pulled when I/O is running. If another product sets these parameters to a higher value.0. This can occur with both SPs. No I/O failure is detected when the same is tried when the LUN belongs to the original owner SP (here SPA). and the LCC of the current owner (SPB) is pulled.x for Solaris Found in Version 5. The parameter is then missing when you try to uninstall the other product.0.Known problems and limitations Table 6 Known problems in PowerPath version 5.2 — 5. The system log continuously shows the following message: emcp:Mpx:Info: Unable to follow volume 600601601CD41400945828858BEDDB11 to SPA 257893 The VxVM plexattach operation takes much longer with PowerPath than with Sun MPxIO.0.0.0.2 Resolved in Version — Description 255118 In a CLARiiON environment.0. when you install PowerPath.2 — If you find a parameter required for PowerPath in /etc/system that has a value higher than PowerPath would set.0.0. from SPA to SPB).xml • svcadm disable volfs • svccfg delete volfs • svccfg import /var/svc/manifest/s ystem/filesystem/vo lfs. the device failure does not get detected.2 — 5.2 — 5. 5.
0. PowerPath does not see the emcpower devices after rebooting 258514 On executing the powermt remove dev=all.0.1.5.1 Resolved in Version — Description 259112 On Solaris10 U4 b11.1 — Uninstall PowerPath and reinstall so that PowerPath is installed after Veritas Volume Manager.0 is installed before Veritas Volume Manager on a Solaris 10 host. Reboot the host to apply the configuration changes.0 — EMC PowerPath for Solaris Version 5. and init 6 commands.0. touch /reconfigure. emc134813 (EMC Knowledgebase solution) After installing Solaris 10 U1. EMC Knowledgebase Solution emc165079 contains more information. This issue is caused by Sun MPxIO behavior.0.x — 4. 5. This may occur.0 and Point Releases Release Notes 19 . 5. for example. To disable MPxIO globally. if you have PowerPath and Veritas installed. the host hangs upon reboot.e g:name="fp" parent="/pci@6. MPxIO automatically manages CLARiiON arrays. 251773 On PowerPath 5.Known problems and limitations Table 6 Known problems in PowerPath version 5. lock congestion occurs when the SRDF link is down and a large number of processes are issuing sequential I/Os with block size=2k. 259100 When PowerPath 5. the system hangs during reboot 253421 ZFS resource groups take about seven minutes on a host (with over 60 devices) to switch over to the second node.0. edit the /kernel/drv/fp.1 — 5.qlc@2" port=0 mpxio-disable="yes".conf file to include: mpxio-disable="yes".0. and you uninstall and reinstall Veritas to apply recommended patches.0. add to the /kernel/drv/fp.x for Solaris Found in Version 5.0. Workaround Run the powermt config command after rebooting PowerPath. To disable multipathing on an HBA port.2000/S UNW.conf file the following: name="fp" parent="parent name" port=port-number mpxio-disable="yes".1 — 5.
0.0. Add the devices to the disk group. Initialize the PowerPath devices as simple devices. Edit the /kernel/drv/fp. Enter: /sbin/vxdg –g <DG> adddisk <[disk=]device> Option 2 1. Enter: /etc/vx/bin/vxdiskset up –fi <device> format=simple 2. a host panic may occur when you install PowerPath 5.1.0. complete one of the following procedures. If MPxIO is enabled and managing CLARiiON arrays.0 and Point Releases Release Notes .0.1 cannot co-exist with MPxIO on Opteron hosts.conf file to include: mpxio-disable="yes". VxVM removes the fdisk partition.1 — 20 EMC PowerPath for Solaris Version 5. Enter: • vxddladm set namingscheme=osn • vxdmpadm setattr enclosure <enclosure_name> tpdmode=native 244891 PowerPath 5.0 Resolved in Version — Description 254503 The Solaris format command requires fdisk on native devices but not on PowerPath pseudo devices. Change the PowerPath pseudo devices to native devices. Create non-CDS disk groups.x for Solaris Found in Version 5. Option 1 1. In a VxVM environment.1. disable MPxIO globally before you install PowerPath 5. The following EMC Knowledgebase Solutions also address this topic: emc158473 emc164551 emc159577 Workaround Refer to “Running fdisk on Opteron hosts” on page 33.0. if MPxIO is enabled and managing CLARiiON arrays.Known problems and limitations Table 6 Known problems in PowerPath version 5. Enter: /sbin/vxdg init <DG> cds=off <options> <device> 3.0. Reboot the host to apply the configuration changes.0. 5. With VxVM on Opteron hosts.
To fix this issue: 1.0 and Point Releases Release Notes 21 . you see the following message when you run vxdisk list : VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible 242924 When there are unlabeled devices. Enter: powermt unmanage dev=<device> 2.0. and then retry the vxdisk list command. 5. Format and label the devices.0. 3.1 Resolved in Version — Description 244656 After removing PowerPath 5. Unmanage each of the unlabeled devices.0.Known problems and limitations Table 6 Known problems in PowerPath version 5.0.0 from a host where VERITAS Volume Manager is installed. Re-manage each of the devices: powermt manage dev=<device> 5.0.x for Solaris Found in Version 5. VxVM continues to report that the removed devices belong to the Symmetrix or CLARiiON array.1 — 244111 After unmanaging Symmetrix or CLARiiON devices with the powermt unmanage command.1 — EMC PowerPath for Solaris Version 5. the format command takes a long time to execute and many copies of the following message appear in /var/adm/messages: corrupt label wrong magic number Workaround Reboot the host after removing PowerPath.
1.0 — 22 EMC PowerPath for Solaris Version 5. 5. To determine the current dump device. For example: # dumpadm -d /dev/dsk/c2t5d0s1 The new dump device can be a device under PowerPath control as long as a native path is used to specify the device.0 and Point Releases Release Notes . The pkgrm command fails with the following error.0.1. though no devices except the boot device are in use: message Error: PowerPath pseudo(s) still in-use. Change the dump device to the native device you identified.1. Identify the underlying native device associated with the pseudo dump device. before uninstalling PowerPath.0.1 — 5. Workaround When switching to a native boot device.x for Solaris Found in Version 5. 240702 A soft hang may occur when you initialize a VxVM disk on a PowerPath pseudo device using vxdisksetup -i with Veritas Volume Manager 5.0 MP1 for Solaris when using PowerPath with Veritas Volume Manager 5. This is a known issue with Hitachi arrays that are managed by HDLM. (output truncated) If the dump device is a pseudo device: 1. Enter: powermt unmanage class=<class> Install Veritas Storage Foundation 5. ensure the dump device is not a pseudo device. After installing PowerPath 5.0.1 Resolved in Version — Description 242477 PowerPath cannot be removed from a SAN boot device (when booting off a native device).0 are automatically managed when you install PowerPath 220.127.116.11.0.0. enter: # dumpadm Output: Dump content: kernel pages Dump device: /dev/dsk/emcpower0a (swap) This may occur when you switch from booting from a pseudo-named device to booting from a native-named device. busy or mounted. 241978 When you install PowerPath 5. the Hitachi arrays that were unmanaged in PowerPath 5.0. unmanaged arrays may become managed by PowerPath. manually unmanage the array class. 2.0.Known problems and limitations Table 6 Known problems in PowerPath version 5.
0. Run powermt config. Failure to use unique host IDs breaks the cluster disk-fencing scheme.x to PowerPath 4.0 — 238211 On Opteron hosts in a Symmetrix environment.x. devices come up as unmanaged on all arrays.0.0.0. the powermt display command displays the disconnected HBA as UNKNOWN.x for Solaris Found in Version 5.0 — EMC PowerPath for Solaris Version 5. nor can you uninstall PowerPath. 2. before installing PowerPath in a VCS or Sun Cluster verify that each node has a unique host ID. the command powermt manage class=hpxp does not fail with an error message. 5. do a fresh installation of PowerPath 5.0 Resolved in Version — Description 238554 With VxVM 5. 5. Run powermt remove dev=all to remove all devices.0.0. or before using emcpadm to swap pseudo device names.x to 5. Upgrade from 4.0.0. you cannot use emcpadm to swap names of pseudo devices. and then upgrade from 4. Workaround Before upgrading to PowerPath 5. Or. do not try to manage these devices with PowerPath.5 (which does not require a host reboot).0 and Point Releases Release Notes 23 . this method does not preserve emcpower device numbering. disable dmp_cache_open. and then rebooting the system. To display host IDs.5 to 5. 5.0.0. as occurs with other arrays.0 — 237710 After upgrading from 18.104.22.168. If MPxIO is enabled for the EVA 8000 or EVA 3000/5000 arrays. 238016 After removing a Fibre Channel cable from the host. enable the parameter. remove the EVA arrays from explicit MPxIO management. when dmp_cache_open is set to on (the default). Devices are opened by VxVM when this parameter is set to on.0.0. 5. Enter: dmp_cache_open: vxdmpadm settune dmp_cache_open=on To remove UNKNOWN from powermt display output: 1. Alternatively. enter the following command on each node in the cluster: hostid Contact Sun customer support for instructions on creating unique host IDs.0 — 237483 With MPxIO explicitly enabled for the EVA8000 or EVA3000/5000 with VCS4.Known problems and limitations Table 6 Known problems in PowerPath version 5. Enter: vxdmpadm settune dmp_cache_open=off After upgrading PowerPath or swapping pseudo names.
reboot the host.0 — Use IBM SDD version 1. If you cannot label the disks. an error message appears.0.6 64 bit is compatible with PowerPath 5.0 on Solaris 10 hosts causes a host panic when I/O requests are sent to vpath devices.x for Solaris Found in Version 5.147. IBM SDD version 1.0.483.0 Resolved in Version — Description 237040 Unmanaging Symmetrix devices with the powermt unmanage class=symm command requires a host reboot before re-managing them. write-protected Symmetrix devices are present. 5.0 and VxVM 4. Workaround 4.Known problems and limitations Table 6 Known problems in PowerPath version 5.0 — 24 EMC PowerPath for Solaris Version 5. In a Symmetrix environment. When you unmanage IBM ESS devices.647.4 with PowerPath 5.6 on Solaris 10 hosts.1 and VxVM 5. then zone the unlabeled disks so the PowerPath host cannot see them.0. in a CLARiiON environment. you see a message similar to the following: message: Segmentation Fault (core dumped) This problem does not occur with IBM SDD version 1.0 on Solaris 9 hosts.0 are unsupported with EFI disks. 235730 Numerous corrupt label console messages appear when an array LUN cannot be labeled. 236825 234389 Pseudo-named devices with PowerPath 5.0 — 235871 When you enter a value for the powermt set path_latency_threshold command that is invalid. 235231 PowerPath does not prevent you from disabling with the powermt disable hba command the last available HBA in your environment. However.5. ensure you do not disable the last available HBA. 5.0.0 and Point Releases Release Notes . 235248 235253 IBM SDD version 1. Set the threshold to a value within this range.4 with PowerPath 5. label the unlabeled disks. and then run the showvpath command. this involves masking the disks.0. 5. but the message does not include the range of acceptable values. remove them from the Storage Group. you see the corrupt label messages. The range of acceptable values is 0 to 22.214.171.124 on Solaris 10 hosts. even when no devices are being kept open by applications. 5. when unlabeled. For example.0 — If possible.0 — When you use the powermt disable command.
Follow the prompts to update the boot archive.0.0. you see the following message.0 — To fix this issue: 1. For example: metaset -s mset0 -d c3t2d25 5.0. even though a PowerPath Migration Enabler migration is not running: lclc231 console login: Apr 25 12:15:50 lclc231 PPME: API: Info: Beginning AUTOMATIC RECOVERY Apr 25 12:15:51 lclc231 PPME: API: Info: Finished AUTOMATIC RECOVERY Workaround You can safely disregard these messages. 233195 In a Solaris 10 Opteron environment.0. You must use the native device name. 2.0 Resolved in Version — Description 234128 When you reboot the host. Enter: svcadm clear system/boot-archive 5. using the pseudo-device name causes an error. a message similar to the following appears: WARNING . EMC PowerPath for Solaris Version 5. the pkgadd -R command fails when the host and the mounted disk referenced by the -R option contain different versions of the Solaris 10 operating system. Use the rm command to remove the links. Reboot and select Solaris failsafe options from the boot menu. Remove the /dev/dsk or /dev/rdsk device links when devices are purposefully removed from a host. when adding a device to a Sun Volume Manager metaset.x for Solaris Found in Version 5.Known problems and limitations Table 6 Known problems in PowerPath version 5. 3. 232620 After entering the pkgadd –R command and rebooting the host.0. when you unmap devices on the array and the /dev/rdsk or /dev/dsk links are not removed.0 — 233005 Due to a Sun limitation.The following files in / differ from the boot archive: /etc/system /etc/name_to_major /etc/driver_aliases /etc/driver_classes 5. or use a combination of cfgadm and devfsadm -C commands to unconfigure the devices and remove the links.0 — Due to differences in the Solaris 10 03/05 and 01/06 releases. host reboots may take longer than usual. Use the native device name when adding a device to a Sun Volume Manager metaset.0 and Point Releases Release Notes 25 .0.
4.0. a system hang may occur upon reboot after installing PowerPath. If you do not disable MPxIO. enter the following line in the /kernel/drv/fp.1” on page 38.Known problems and limitations Table 6 Known problems in PowerPath version 5.emc. Refer also to EMC Knowledgebase Solution emc126617.com Workaround Manually disable MPxIO globally.0 — 4. 227775 R1/R2 boot support is not supported with PowerPath 4.5.5 and 5.x for Solaris Found in Version 5. Refer to “Inconsistent pseudo device mappings with VxVM 4.0 and the Leadville driver (also called the Sun native driver).0 and Point Releases Release Notes . disable MPxIO before installing PowerPath.lss.0.0 Resolved in Version — Description 231422 231946 When installing PowerPath on an AMD Opteron host with MPxIO enabled.conf file: mpxio-disable="yes" 229447 Pseudo device mappings in VERITAS Volume Manager Version 4.0.0 — 26 EMC PowerPath for Solaris Version 5. and messages similar to the following appear: WARNING: forceload of drv/ssd failed WARNING: forceload of misc/emcpsapi failed WARNING: forceload of misc/emcpcg failed WARNING: forceload of drv/ssd failed WARNING: forceload of misc/emcpsapi failed WARNING: forceload of misc/emcpcg failed Hostname: lclc015.5.1 may become inconsistent with PowerPath pseudo device mappings under certain conditions.
Reconnect the paths. then reboot the system to remove the duplicate entries.1.0 and Point Releases Release Notes 27 . EMC PowerPath for Solaris Version 5.x for Solaris Found in Version 4. Run vxddladm stop eventsource 2. Run vxddladm start eventsource. to avoid duplicate entries: 1. and VERITAS VxVM 4.Known problems and limitations Table 6 Known problems in PowerPath version 5.1 has of these devices. The PowerPath pseudo device links will be available during the second reboot. — When mapping/zoning new LUNS to the host.0. It can also happen if a new LUN is mapped or zoned to a host and VxVM had prior knowledge of this device. Map/zone the new LUNS to the host. Run powermt config.4. — When duplicate entries are seen. if PowerPath requested the reboot.0 Resolved in Version — Description 221084 With PowerPath and VxVM 4. — When a host is rebooted with a path down. Dynamically recreate the LUN device (either using cfgadm routines or HBA-specific routines to dynamically create the device nodes). 3. a second reboot will clear the duplicates. — If vxddladm commands were not run. the command vxdisk list may display multiple entries for the same device. eventsource. Run vxddladm stop. 2. to avoid duplicates: 1. Run vxddlam start. 4. 4. Workaround — When upgrading or reinstalling PowerPath. This usually occurs when PowerPath is uninstalled and reinstalled without clearing the knowledge VxVM 4. Run powermt config to discover and create the pseudo device links. The issue occurs because PowerPath pseudo device links are unavailable during boot. 5. This may occur following a reboot where PowerPath has just been installed or new devices have been mapped or zoned to a host. 3. eventsource.1 depends on these links before they can be created. reboot after the initial package remove.0.
info] /email@example.com. For Solaris 10.x for Solaris Found in Version 4.0.9.qlc@1/fp@0. Ignore the messages.qlc@firstname.lastname@example.org — 4.0 Resolved in Version — Description 210941 In a Solaris environment with PowerPath and a Leadville driver.4.1 cluster and is also connected to EVA devices generates volume assign/restore messages and path dead/alive messages.info] NOTICE: Qlogic qlc(1): Link ONLINE Oct 12 12:03:53 db026ops scsi: [ID 243001 kern. 4.0 (fcp1): Oct 12 12:03:53 db026ops Lun=0 for target=614313 disappeared Oct 12 12:03:58 db026ops qlc: [ID 686697 kern. 203121. causing data corruption. 204709 Running the powermt remove dev=all and powermt config commands on a host that has mounted the SnapView LUN makes the snapshot inactive. For Solaris 8 or 9 install SAN 4.Known problems and limitations Table 6 Known problems in PowerPath version 5.4.4. 203123 Rebooting a PowerPath host that is a node in a Sun 3.0 — 28 EMC PowerPath for Solaris Version 5.0 (fcp1): Oct 12 12:03:53 db026ops Lun=0 for target=615313 disappeared Oct 12 12:03:53 db026ops scsi: [ID 243001 kern.600000/SUNW. running SYMCLI commands generates the following errors in /var/adm/messages: Oct 12 12:03:53 db026ops qlc: [ID 686697 kern. install Sun patch 119130-17. These messages are also seen during node failover.0 and Point Releases Release Notes . EMC Knowledgebase solution emc108113 also addresses this issue.info] /email@example.com] NOTICE: Qlogic qlc(2): Loop OFFLINE Workaround Install the appropriate SUN T-patch.600000/SUNW.
deactivate the session.1. etc. an admsnap operation (start. Update the system configuration settings as appropriate. For applications or scripts that rely on the exit status from admsnap. You see the following message when you unmanage a boot device: WARNING: One or more boot devices have been unmanaged.0 and Point Releases Release Notes 29 .0 1. 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 stop operations that failed to complete. Cannot remove device that is in use: <emcpowerx> — EMC PowerPath for Solaris Version 5.) reports the error 0xE10080A3. For deactivate operations that failed to complete. 4.x for Solaris Found in Version Resolved in Version — Description 197626 Very infrequently. For activate operations that failed to complete. Before you reboot the host. use Navisphere instead of Admsnap to perform the operation. no action is required.0 for Solaris Installation and Administration Guide for more information. No further action is required. update the system configuration in the /etc/system and /etc/vfstab files to use native devices. If this problem persists. stop the session. Workaround 4.3. stop the session on the devices and retry the admsnap command. a non-zero exit status is returned to the application or script. and determine whether the admsnap command completed the operation for all devices specified on the command line. No further action is required. Refer to the PowerPath 5.0 165579 Using the powermt unmanage class=<class> command to unmanage third-party arrays when the host is booted from a pseudo device prevents the system from coming up after you reboot. stop. deactivate the session on the devices and retry the admsnap command.Known problems and limitations Table 6 Known problems in PowerPath version 5. 3. If it did.0. 2. Query the CLARiiON storage array using Navisphere.0. 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.
/test is deleted. Enter: emcpreg -f /directory/filename -edit • If you neglect to specify the full pathname. Workaround • If your PowerPath registration file is the default file (/etc/emcp_registra tion).0 — 30 EMC PowerPath for Solaris Version 5. the SMF (Service Management Facility) related to PowerPath does not start after installation or after every reboot. do not use the -f option with emcpreg.x for Solaris Found in Version 3. if your PowerPath registration file is in the /test directory and you execute the command emcpreg -f /test -edit. 276520 (EMC Knowledgebase Solution emc184051) On a Solaris 10 update 4 host. A message similar to the following appears in the host messages file after reboot: Mar 1 21:17:03 (hostname) emcp: [ID 801593 kern.0.xml #svcadm enable powerstartup #svcadm enable powershift #svcadm enable powerconfigcgs • Upgrade to PowerPath 5.0 and Point Releases Release Notes . Delete it? If you answer y (yes) to the prompt.) For example. (The default parent directory is /etc. be sure to specify the full pathname. do on e of the following: • Run the following commands: #svccfg import/var/svc/manife st/system/emcpower/po werpath_services. answer n (no) to the prompt: EMCP registration file is corrupt. causing the CLARiiON LUNs to trespass upon reboot.0. you see the following prompt: EMCP registration file is corrupt.notice] Info: Assigned volume 600601F6A508000040F2EF119B51D711 to SPB 5.Known problems and limitations Table 6 Known problems in PowerPath version 5.1 SP1 or later. To avoid this issue in the future.0.notice] Info: Assigned volume 600601602C740800C0D8F64A6B72D911 to SPB Mar 1 21:17:03 (hostname) emcp: [ID 801593 kern. Delete it? If you encounter this issue: Run the powermt restore command to restore the LUNs to their original CLARiiON SP owner.3 Resolved in Version — Description 124857 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.notice] Info: Assigned volume 600601602C740800D7D8F64A6B72D911 to SPB Mar 1 21:17:03 (hostname) emcp: [ID 801593 kern. • Otherwise.
Refer to the powermt set policy command description in the PowerPath Product Guide for more information.Known problems and limitations Limitations This section includes limitations in PowerPath 5.0 does not support Sun X6767A and X6768A HBAs (Leadville driver).0. such as dev_info. ◆ PowerPath cannot failover path-specific requests.x. IBM Subsystem Device Driver (SDD). and EVA 3000/5000 systems with VCS 3. or HP StorageWorks environment. MA. as described in known issue 244891.x for Solaris and limitations in third-party software that affect PowerPath operation. the disabled port state persists across host reboots. PowerPath cannot co-manage devices with third-party path management software. HP StorageWorks Secure Path. ◆ ◆ ◆ ◆ PowerPath 5. • R1/R2 boot support hosts must be connected directly to the Symmetrix system.0 for Solaris does not support zettabyte file systems (ZFS) with HP StorageWorks EMA. this does not guarantee the complete suppression of I/O from the host to the array port during early boot. In an R1/R2 boot support environment: • PowerPath 5. they cannot be connected through the fabric.x can coexist with third-party path management software such as Hitachi Dynamic Link Manager (HDLM). If you deploy any such applications.0. When you disable a port with the powermt set port_disable command in an R1/R2 environment.0. Hitachi Lightning.0. Hitachi TagmaStore.x does not support load balancing and failover for applications that use the SCSI-2 Reserve/Release or Solaris MHIOCTKOWN IOCTL command set in an IBM ESS. the disabled port does not persist through a failover or failback.0. When you disable a port with the powermt set port_disable command.0 and Point Releases Release Notes 31 . ◆ PowerPath 5. or HP StorageWorks Auto Path XP Virtual Array. EMC PowerPath for Solaris Version 5. ◆ PowerPath 5. Note: PowerPath 5.1 cannot co-exist with MPxIO on Opteron hosts. you must set the load balancing and failover policy to nr (No redirect). However.
use this command syntax: vxdmpadm setattr enclosure <enclosure> tpdmode=native This limitation applies also to any EMC devices in a mixed array environment.1 on SPARC Solaris 9 and 10 platforms with VxVM 4.0. ◆ The following is an issue with Sun’s native driver. when using Sun's native driver: 1.1 and VxVM 4. You can use either native names or enclosure-based names.1.1 MP1 RP4 (121755-08) or later is installed. To change the VxVM third-party driver mode (tpdmode) to native. Technical notes This section contains additional information on PowerPath not covered in the core documents.0. 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.1 or later does not support PowerPath pseudo device names with third-party arrays. Reboot the host.Technical notes ◆ The following limitations apply to a VERITAS Volume Manager environment or a VERITAS Cluster Server environment: • PowerPath 5. When using Sun's qlc driver. • Due to a known problem in VERITAS Volume Manager 4. • Due to a VERITAS limitation. VxVM 4.1 only when VERITAS patch 4.0 and Point Releases Release Notes . PowerPath on Solaris 10 does not support root device encapsulation with VxVM 4. 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.1 supports Sun Cluster 3. Add the following line to the /etc/system file: set fcp:ssfcp_enable_auto_configuration=1 2. The following sections are included: 32 EMC PowerPath for Solaris Version 5. • VERITAS Volume Manager 4.1. or you can run powermt restore to restore them.1 MP1 with Leadville adapters support only enclosure-based device naming. To avoid this situation.
Use prtvtoc to determine the sector count for the device: prtvtoc /dev/rdsk/cxtxdxp0 4. Run newfs against the cxtxdxsx device. emcpadm enhancements PowerPath 5. The new emcpadm commands simplify the process of renaming pseudo devices in a cluster environment.0 and Point Releases Release Notes 33 . 2.0.1” on page 38 “powermt class arguments with HP StorageWorks EVA arrays” on page 38 “HP StorageWorks controller and port names” on page 40 ◆ ◆ Running fdisk on Opteron hosts Problem The Solaris format command on AMD Opteron hosts requires fdisk on native disks but not on emcpower devices. Use fmthard to create desired slices on the partition: fmthard -d part:tag:flag:start:size -n volname /dev/rdsk/cxtxdxp0) 5. The usage of fdisk on PowerPath pseudo devices destroys the partitions created by the Solaris format command. Use fdisk to create a Solaris MBR partition on the native device: fdisk -B/dev/rdsk/cxtxdxp0 3. Run powermt config and ensure all paths to devices are present and alive. Mount and proceed normally using either the appropriate pseudo or native devices. you can export the device EMC PowerPath for Solaris Version 5. For example. Present blank LUNs to the host.0. Workaround 1.Technical notes ◆ ◆ ◆ ◆ ◆ “Running fdisk on Opteron hosts” on page 33 “emcpadm enhancements” on page 33 “PowerPath support with iSCSI” on page 35 “Exporting emcpower devices to Non-Global zones” on page 36 “Inconsistent pseudo device mappings with VxVM 4.2 includes enhancements to the emcpadm command that allow you to preserve and restore PowerPath pseudo-device-to-array logical-unit bindings.
The current mappings are those configured on the node where you run this command. 34 EMC PowerPath for Solaris Version 5. emcpadm check_mappings [-v ] -f <pseudo device/LU mappings file> Compares the currently configured mappings with the mappings in <pseudo device/LU mappings file>. Arguments -f <mappings_file> Specifies the file name and location for <mappings_file>. If a conflict occurs between the existing mappings and the file mappings.0 Product Guide. By default this environment variable is not set. and import the mappings on other cluster nodes. emcpadm import_mappings [-v ] -f <pseudo device/LU mappings file> Replaces the currently configured mappings with the mappings in <pseudo device/LU mappings file>. ECMPADM_DBG=<value> Setting this environment variable to any value enables debugging. <pseudo device/LU mappings file> contains the mappings previously exported to the specified file. emcpadm print_mappings [-p | -f <pseudo device/LU mappings file>] Displays the current mappings or the mappings in <pseudo device/LU mappings file>. available on the Powerlink website.Technical notes mappings configured on one node in a cluster. Environment variables This section describes the new environment variables associated with enhancements to the emcpadm command. Command syntax and description This section describes briefly the new emcpadm commands. emcpadm export_mappings -f <pseudo device/LU mappings file> Saves the currently configured mappings to <pseudo device/LU mappings file>. refer to the PowerPath 5. EMCPADM_ERR=<value> Setting this environment variable to any value enables error logging. By default this environment variable is not set.0 and Point Releases Release Notes . the content in <pseudo device/LU mappings file> takes precedence.0. Configuring nodes in this manner ensures consistent emcpower device-naming across a cluster. For more information and examples.
the path shows as degraded rather than dead when you run powermt display. Consequently. if you disable a path in a CLARiiON environment. the path change is recognized in less than one minute.0. if you use the iscsiadm utility. PowerPath cannot correctly recognize path status when path status is changed with the ifconfig command. The following configuration requirements apply in a PowerPath iSCSI environment: ◆ ◆ Only one iSCSI session is allowed per target. Limitations In a configuration where the host is connected to an array through an iSCSI data channel port: ◆ For both NICs on a host. For example. Due to an issue with the iSCSI driver. However. available on the Powerlink website. Instead. When you disable or enable an iSCSI port.0 and Point Releases Release Notes 35 . ◆ ◆ Configuration requirements Note: For the most up-to-date interoperability information. or disable it on the switch. it takes five minutes for the path to show up as dead in the powermt display command. Hosts can connect to an iSCSI storage system using a Layer 2 (switched) or Layer 3 (routed) network. The presence of VLANs in the network should be transparent to the array and are supported as long as the network quality is adequate. Refer to “powermt display examples” on page 36 for sample output. refer to the E-Lab Interoperability Navigator. when a path fails. the iSCSI initiator presents a single iSCSI instance to PowerPath. This section includes configuration notes for PowerPath hosts connected through iSCSI. Only hosts connected through Network Interface Cards (NICs) are supported. Do not use the ifconfig command to disable a NIC port. HBA configurations are not supported at this time.Technical notes PowerPath support with iSCSI PowerPath 5.1 supports storage systems connected through iSCSI data channel ports. manually remove the cable from the port.0. PowerPath’s recognition of the path failover is delayed due to an issue with the Sun iSCSI initiator. ◆ EMC PowerPath for Solaris Version 5.
the path shows as degraded rather than dead.Stor -.-----. powermt display Symmetrix logical device count=0 CLARiiON logical device count=4 Hitachi logical device count=0 Invista logical device count=0 HP xp logical device count=0 Ess logical device count=0 HP HSx logical device count=0 ============================================================================== ----. queued-IOs=0 Owner: default=SP A. priority=0.Host Bus Adapters --------.Host --------------.Technical notes ◆ You cannot boot a Solaris host using an iSCSI disk volume provided by a software iSCSI initiator. as follows: powermt display dev=all Pseudo name=emcpower3a CLARiiON ID=HK192201138 [aaqa23] Logical device ID=600601601AC01800CE9CB0584573DB11 [LUN 200] state=alive.Stats --### HW Path I/O Paths Interf.0 and Point Releases Release Notes .-----. policy=CLAROpt.I/O Paths ----. Mode State Q-IOs Errors ============================================================================== 4608 iscsi c3t11d0s0 SP B1 active alive 0 0 4608 iscsi c3t14d0s0 SP B0 active dead 0 0 4608 iscsi c3t17d0s0 SP A0 active dead 0 1 4608 iscsi c3t20d0s0 SP A1 active alive 0 1 (Output truncated) Exporting emcpower devices to Non-Global zones Note: This section applies to PowerPath 5. powermt display examples The iSCSI initiator presents a host NIC to PowerPath as one iSCSI instance. Consequently.I/O Path .0 with Solaris 10. This section describes how to export PowerPath pseudo devices (emcpower devices) to Non-Global Zones (also called NG Zones). 36 EMC PowerPath for Solaris Version 5.Stats -----### HW Path Summary Total Dead IO/Sec Q-IOs Errors ============================================================================== 4608 iscsi degraded 16 8 82 24 When you run the powermt display dev=all command in the same scenario. you see the two dead paths.-.0. current=SP B ============================================================================== ---------------. when a path fails and you run the powermt display command.
you can create filesystems from the NG Zones.tab file. enter these lines in the /etc/devlink. or you can use them through volume managers.name=emcp. To export emcpower devices to NG Zones: 1.minor=a. EMC PowerPath for Solaris Version 5.tab file.minor=a. Note: —For each pseudo device to be exported.name=emcp.addr=1.0.minor=a. After rebooting the host.addr=0.minor=a. ensure the NG Zones are not in a booted condition. the NG Zone is zone1. 3.raw type=ddi_pseudo.Technical notes After you export the pseudo devices. the tab appears between blk and dsk in the first sample entry.blk type=ddi_pseudo. Manually enter the pseudo device names in the /etc/devlink. and then make configuration changes be entering the following commands: Note: In this example. # zonecfg zoone1 zonecfg:zone1> add device zonecfg:zone1:device> set match=/dev/rdsk/emcpower0a zonecfg:zone1:device> end zonecfg:zone1> add device zonecfg:zone1:device> set match=/dev/dsk/emcpower0a zonecfg:zone1:device> end zonecfg:zone1> exit # zoneadm –z zone1 boot 4.name=emcp. Boot the NG Zone (zone1 in this example) and then enter the EMC inq command or the Solaris format command to verify that the emcpower device (emcpower0a in the example) is visible on the NG Zone you created.0 and Point Releases Release Notes 37 .addr=1. Adding spaces instead of tabs causes the entries to be ignored.blk type=ddi_pseudo. create two entries: one for the raw device and one for the block device. reboot the host.tab: type=ddi_pseudo. For example.raw dsk/emcpower\A0\M1 rdsk/emcpower\A0\M1 dsk/emcpower\A0\M1 rdsk/emcpower\A0\M1 2. After you modify the /etc/devlink. For example. —You must enter a single tab between the two fields in each line.name=emcp.addr=0.
their corresponding class arguments.1 The pseudo device mappings in VERITAS Volume Manager Version 4. VxVM loses the pseudo device mapping. Enter: echo > /etc/vx/disk. rather than through the hphsx class.info 3. use this procedure to correct the mappings: 1. Enter: vxconfigd -k powermt class arguments with HP StorageWorks EVA arrays PowerPath 5.Technical notes Inconsistent pseudo device mappings with VxVM 4.0 introduces support for HP StorageWorks Enterprise Virtual Array (EVA) 8000 systems and EVA 3000/5000 systems with VCS 4.0 and Point Releases Release Notes .) Table 7 shows the HP Storage Works EVA systems supported.1 may become inconsistent with PowerPath pseudo device mappings under the following conditions: ◆ If you uninstall VxVM and then reinstall it after a configuration change.info /etc/vx/disk. This information may be different from the current PowerPath mappings and configuration. (The class argument limits a powermt command to the specified type of storage system. and their default load balancing and failover policies with and without a PowerPath license.info. PowerPath support for these systems differs from previous releases in that PowerPath manages the newly supported EVA arrays through the hpxp class in the powermt command. When you rename an emcpower device instance using the emcpadm command.0.x. VxVM maps pseudo devices according to information saved before you uninstalled the software. For more 38 EMC PowerPath for Solaris Version 5. ◆ When inconsistent mappings of pseudo devices occur.old 2. Enter: cp /etc/vx/disk.
x.700000/fibre-channel@2. This behavior has not changed from previous PowerPath releases. Example The following example shows the powermt display output for PowerPath 5.0 and an HP StorageWorks EVA 8000 system.700000/fibre-channel@2 optimal 16 0 0 0 1281 pci@1f. In this example.Stats -----### HW Path Summary Total Dead IO/Sec Q-IOs Errors ================================================================================ 1280 pci@1f. priority=0. Pseudo name=emcpower2a HP HSx ID=50001FE15000B020 Logical device ID=600508B4000146870007000000710000 state=alive. The class argument limits a powermt command to the specified type of storage system. is set. powermt display dev=all class=hphsx | more The following output is truncated. Table 7 Support for HP StorageWorks EVA systems Default Policy With a PowerPath License Adaptive (ad) Adaptive (ad) Storage System powermt Class Argumenta Default Policy Without a PowerPath License Basic failover (bf) No redirect (nr) HP StorageWorks EVA 3000 or 5000 with VCS 3. the new default policy. HP StorageWorks xp arrays are also managed through the hpxp class. b.Technical notes information about class arguments or load balancing and failover policies.Host Bus Adapters -------------. queued-IOs=0 Controller: HSV110 Controller A: 4889ILY028 Controller B: 4889ILZ020 EMC PowerPath for Solaris Version 5.x hphsx HP StorageWorks EVA 3000 or 5000 with VCS 4. policy=BasicFailover.0 Product Guide. basic failover. powermt display Symmetrix logical device count=0 CLARiiON logical device count=0 Hitachi logical device count=0 Invista logical device count=0 HP xp logical device count=8 Ess logical device count=0 HP HSx logical device count=0 ================================================================================ ----.0 and Point Releases Release Notes 39 .x hpxpb HP StorageWorks EVA 8000 a.I/O Paths ----.0.1 optimal 16 0 0 0 Basic failover policy The following example shows the powermt display output for an HP StorageWorks EVA array with VCS 3.-----. refer to the PowerPath 5.
PowerPath port numbers are one lower than Command View EVA port numbers. Names are mapped as follows: Command View EVA name A-1 A-2 B-1 B-2 PowerPath name A-0 A-1 B-0 B-1 HP StorageWorks HSG80 PowerPath names the bottom controller A and the top controller B.-.0 c2t50001FE15000B029d1s0 A 1 unlic alive 0 3072 firstname.lastname@example.org c3t50001FE15000B028d1s0 A 0 active alive 0 3073 pci@4.I/O Path .1/fp@0. PowerPath port numbers are one lower than HSG Element Manager port numbers.1/fp@0. Names are mapped as follows: HSG Element Manager name Bottom-1 Bottom-2 Top-1 Top-2 PowerPath name A-0 A-1 B-0 B-1 40 EMC PowerPath for Solaris Version 5. HP StorageWorks EVA names PowerPath identifies controllers A and B exactly as Command View EVA does.0 c3t50001FE15000B02Dd1s0 B 1active alive 0 0 0 0 0 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.Technical notes Default owner=A Current owner=A ================================================================================== ---------------.0.0 and Point Releases Release Notes .Stor -.4000/fibre-channel@email@example.comfirstname.lastname@example.org/fibre-channel@email@example.com c2t50001FE15000B02Cd1s0 B 0 unlic alive 0 3073 pci@4. Mode State Q-IOs Errors ================================================================================== 3072 firstname.lastname@example.org/fibre-channel@2.Host --------------. This section describes the differences.Stats --### HW Path I/O Paths Interf.
planning. Electronic versions of all PowerPath manuals are available on the Powerlink website: http://Powerlink. PowerPath documentation The following table lists the PowerPath documentation set. EMC Navisphere Manager Version 6.0 for Solaris Release Notes EMC PowerPath 5. AX-Series.EMC. and the updated manuals are posted on the Powerlink website. refer also to the EMC host connectivity guides. Refer only to these documents for prescribed installation information when using AX100-Series storage systems.X Administrator’s Guide ◆ ◆ EMC PowerPath for Solaris Version 5. and FC-Series Storage Systems CLARiiON AX100-Series installation. all manuals are available from EMC Corporation.0 for Solaris.0 Product Guide Related documentation If your environment includes Symmetrix storage systems. and troubleshooting documents.Documentation Documentation This section provides a list of the documentation that supports PowerPath 5. If your environment includes CLARiiON storage systems. These manuals are updated periodically.com.0 and Point Releases Release Notes 41 . Name EMC PowerPath 5.0 for Solaris Installation and Administration Guide EMC PowerPath 5. CX-Series.0. which are available on the Powerlink website. located on the AX100 support website. refer to the support documentation that shipped with your storage system. refer also to the following manuals: ◆ ◆ EMC host connectivity guides EMC Installation Roadmap for CX3-Series. For information on accessing the site.
42 EMC PowerPath for Solaris Version 5. refer to the appropriate documentation from your vendor.Documentation ◆ Important Information About PowerPath SE — contains information about the PowerPath version that ships in CLARiiON Utility Kits If your environment includes other vendors’ storage systems.0 and Point Releases Release Notes .0.
refer to Appendix A.0 for Solaris Installation and Administration Guide.0 PowerPath 5.b0xx.5. EMC PowerPath for Solaris Version 5.gz where xx = the build number ◆ For Opteron hosts: EMCPower.0.tar.0.0.Patch. “Files Changed By PowerPath.0.1 PowerPath 5. and files This section contains information about the PowerPath 5.1.0. Files For information on files added by PowerPath 5.0.tar.0.2 PowerPath 5.SOLARIS_i3126.96.36.199. Media and organization PowerPath 5.” in the PowerPath 5.gz where xx = the build number PowerPath 5.bxxx.Software media.0 is distributed on a CD.5.5. The following files are available for download: ◆ For SPARC hosts: EMCPower.Z — Compressed tar file that contains the PowerPath and PowerPath Migration Enabler packages.x media and files.Patch.0.0.2 is a stand-alone full package release. organization. PowerPath 5.b0xx. It is available on the Powerlink website and is distributed as a compressed tar file.1.SOLARIS.0.GA. organization. where xxx = the build number PowerPath 5. which has the following structure: ◆ ◆ /UNIX/SOLARIS — Contains all files in the PowerPath package.0 package is also distributed on Powerlink in the compressed tar file format. and files Software media.0 and Point Releases Release Notes 43 .tar.SOLARIS.1 is a patch release available as a compressed file on the Powerlink website.0. /UNIX/SOLARIS/EMCPower.0.
x. follow the instructions in the ReadMe. Technical support — For technical support. For the new user PowerPath 5.0 for Solaris Installation and Administration Guide.txt file posted with the patch on Powerlink. 44 EMC PowerPath for Solaris Version 5.0 for Solaris Installation and Administration Guide.0.0 To install PowerPath 5. Review the patch ReadMe files to determine which patches (if any) you want to install after PowerPath.0. licensing. refer to the EMC Powerlink website (registration required) at: http://Powerlink. Upgrading from a previous revision To upgrade to PowerPath 5.com The Powerlink website contains current information. and information about EMC products.0 for Solaris Installation and Administration Guide for instructions on installing PowerPath.Installation Installation Refer to the PowerPath 188.8.131.52. go to EMC WebSupport on Powerlink.0. you must be a WebSupport customer.0. follow the instructions in the PowerPath 5. Patches and upgrades — You can download PowerPath patch software from Powerlink. follow the instructions in the PowerPath 5. release notes.0. follow the instructions in the PowerPath 5. such as: Product information — You can find documentation.2. PowerPath 5. PowerPath 5.2 To install PowerPath 5. To open a case on EMC WebSupport.EMC. Troubleshooting and getting help For additional information on EMC products and services available to customers and partners. Information about your site configuration and the circumstances under which the problem occurred is required. software updates.0.0 for Solaris Installation and Administration Guide.1 To install PowerPath 5. and service.0.0 and Point Releases Release Notes .
To access E-Lab Issue Tracker on Powerlink. run the emcgrab utility. Workarounds for existing bugs. You can search Issue Tracker to find: ◆ Descriptions of PowerPath bugs existing on any PowerPath-supported host platform. If you are running PowerPath Migration Enabler and you encounter a problem.0 and Point Releases Release Notes 45 .Troubleshooting and getting help and whether those patches have prerequisites for installing PowerPath. To obtain patches. click Support > Downloads and Patches > Downloads D-R > PowerPath for UNIX.0. E-Lab Issue Tracker — A Powerlink application that allows you to search for fix information for EMC product issues. ◆ E-Lab Issue Tracker is updated regularly between scheduled releases and patch releases. EMC PowerPath for Solaris Version 5.0. Reporting a problem If you find a problem in PowerPath 5. Choose the following links: Support > Support and Diagnostic Tools > Grab Utilities. to EMC Customer Support. and submit the generated tar file. You can download emcgrab from the Powerlink website. The emcgrab utility does not collect Migration Enabler data. refer to the PowerPath Migration Enabler Release Notes for instructions on gathering troubleshooting information. click Support >E-Lab Issue Tracker Information > E-Lab Issue Tracker. along with any other supporting material.
and distribution of any EMC software described in this publication requires an applicable software license. 46 EMC PowerPath for Solaris Version 5. EMC believes the information in this publication is accurate as of its publication date. copying. AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use.Troubleshooting and getting help Copyright © 2008 EMC Corporation.0 and Point Releases Release Notes . The information is subject to change without notice.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION. see EMC Corporation Trademarks on EMC.com.0. All other trademarks used herein are the property of their respective owners. For the most up-to-date listing of EMC product names. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS. All rights reserved.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.