300 003 593 Powerpath for Solaris Rn

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 .................................................... 16◆ Technical notes .................................................................................... 32◆ Documentation ................................................................................... 40◆ Software media, organization, and files.......................................... 41◆ Installation........................................................................................... 42◆ Troubleshooting and getting help .................................................... 43

EMC® PowerPath®

for SolarisVersion 5.0.0 and Point Releases

Release NotesP/N 300-003-593

Rev A05

August 6, 2007

1

2

Product description

Product descriptionEMC® PowerPath® software is a server-resident, performance and application availability enhancing software solution. PowerPath combines multiple path I/O capabilities, automatic load balancing, and path failover functions into one integrated package. PowerPath supports servers, including cluster servers, connected to EMC Symmetrix®, EMC CLARiiON®, 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 changesThis section describes new features and changes in PowerPath 5.0.x releases.

PowerPath 5.0.2 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 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

http://powerlink.emc.com

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

3EMC PowerPath for Solaris Version 5.0.0 and Point Releases Release Notes


4


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



◆ Non-EMC, active-passive arrays now use basic failover (bf) as the default load balancing and failover policy—instead of no redirect (nr). Currently, this change applies only to HP StorageWorks EVA 3000 or 5000 arrays with VCS 3.x. Refer to “powermt class arguments with HP StorageWorks EVA arrays” on page 38 for more information.

◆ The emcpmp, emcpmpc, emcpmpap, and emcpmpaa extensions present in previous PowerPath releases have been replaced in PowerPath 5.0 by the emcpmpx extension.

AMD Opteron supportNote the following regarding PowerPath 5.0 compatibility with AMD Opteron hosts:

◆ PowerPath Migration Enabler is not supported.

◆ The following storage systems are supported:

• EMC arrays

• Hitachi Lightning and Hitachi TagmaStore storage systems (no other third-party arrays are supported)

◆ The device naming format differs, as explained in the next section.

Device naming On the Solaris Opteron platform, slices are set up differently than on the SPARC platform. On Opteron hosts, each disk can have up to four partitions, one of which can be the Solaris partition. The operating system uses the naming convention cXtYdZp0 to access the entire disk. The naming convention cXtYdZ[p1–p4] is used to access blocks from defined partitions.

The Opteron platform uses a VTOC with 16 slices per disk. The naming convention cXtYdZ[s0–s15] is used to access blocks from VTOC slices. The format utility can manage only 10 slices; the fmthard command can manage all 16 slices.

The emcpower naming convention that accommodates all 16 slices is: emcpower#[a-p]

Note: PowerPath does not provide pseudo-device name support for the Opteron fdisk partitions (native device names cXtYdZ[p0-p4]). To access blocks from the fdisk partition or use the fdisk command, native device names must be used.


6

Fixed problems

Discontinued features in PowerPathThis section includes information about discontinued features in PowerPath.

EMC HighRoad PowerPath 5.0 does not include intrinsic disk protection for EMC HighRoad® disks on Symmetrix storage systems. Effective with HighRoad version 4.0, disk protection for Symmetrix is included in the HighRoad software. If you want to upgrade to PowerPath 5.0, and you are using HighRoad 3.2 or earlier, you need to upgrade to HighRoad version 4.0 or later before upgrading to PowerPath 5.0.

End-of-life announcementPlease 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, PowerPath 4.4 for AIX release, and PowerPath 4.5 for HP-UX.

EMC has also announced its intention to end-of-service-life PPVM functionality for Solaris, AIX and HP-UX effective March 2006. If you have any data on PPVM volumes, back up that data and destroy all PPVM volume groups before installing PowerPath 4.4.0, 4.5.0, or 5.0.0.

Fixed problemsThis section describes the fixed problems in each release of PowerPath 5.0.x for Solaris. It includes these subsections:

◆ “PowerPath 5.0.2” on page 7



For the most up-to-date fix information for EMC products, refer to E-Lab Issue Tracker on Powerlink.

http://Powerlink.EMC.com



Fixed problems

PowerPath 5.0.2 Table 1 describes the fixed problems in PowerPath 5.0.2 for Solaris.

Table 1 Fixed problems in PowerPath 5.0.2 for Solaris

DescriptionFound inversion

Resolved in version

259113 With PowerPath 5.0.2 on a Solaris 10 U3 or Solaris 10 U4 host, the powermt display command aborts.

5.0.1 5.0.2

257350 The PowerPath 5.0 powermt watch paths class=clariion command displays Clariion in the result. This breaks the automation scripts on all the OS platforms.

5.0.1 5.0.2

257340257867After upgrading to PowerPath 5.0.1, rebooting the host can take from 2 to 4 hours.

5.0.1 5.0.2

256521 The powermt set port_disable command does not persist across reboots for Hitachi/HPXP devices. The powermt display port_mode command will not display "Disabled" for Hitachi/HPXP array ports even though it may indeed be disabled.

5.0.1 5.0.2

255639232883245213A panic occurs in the emcpIoctlGuts for the DKIOCINFO ioctl.

5.0.1 5.0.2

255342With PowerPath 5.0.1 on a Solaris host, renaming emcpower devices to include five or more digits may cause a host panic. Renaming emcpower devices to include four or fewer digits is supported.

5.0.1 5.0.2

255284A TimeFinder split operation fails when you use the -ppath option.EMC Knowledgebase Solution emc159584 also addresses this issue.

5.0.1 5.0.2

255269With PowerPath 5.0.1 for Solaris, a host panic occurs when using emcpadm to rename a pseudo device to a value of 4095 or greater (for example, emcpower4095). A value between 0 and 4094 does not cause a host panic.

5.0.1 5.0.2

254674Installing PowerPath 5.0.0 on a Solaris 10 host may cause a host panic.

5.0.0 5.0.2

254631When a Clariion LUN is removed from a Storage Group, PowerPath logs the following message: Volume ID has changed

5.0.1 5.0.2


8

Fixed problems

254310 When periodic autorestore is set to OFF for all classes, the failure detection occurs for paths through which IO is happening.

5.0.1 5.0.2

254242 254656256288253417A trespass from one SP to another on a CLARiiON system, followed by a host reboot, causes a Solaris zettabyte file system (ZFS) storage pool to lose connection to PowerPath pseudo devices.

5.0.0 5.0.2

254232 The powermt command display ports dev=<Clariion device> displays the paths as 'unlicensed and alive (u,v)' when it should be 'active and alive (a,v)'.

5.0.1 5.0.2

252928 With Powerpath 5.0.1 installed ion a Solaris host, the CD-ROM automount function no longer works if a CD disk is not present when the system boots.

5.0.1 5.0.2

252308When a Fibre Channel cable is disconnected, PowerPath reports the path as Degraded. When the cable is reconnected, PowerPath may take from 10 minutes to 24 hours to reacquire the path.

5.0.0 5.0.2

252057Failover time with PowerPath 5.0.1 and Solaris 10 is slower than expected.

5.0.1 5.0.2

250029PowerPath no longer writes to the PowerPath configuration file when you run the powermt display command. This change is related to issue 230614, in which information related to booting from a LUN was removed from a PowerPath configuration file.

4.5.0 5.0.2

248747The System volume mirroring of Fujitsu's Volume Manager GDS is not supported on hosts with PowerPath and: • Solaris 10 Update 3, or• Any Solaris 10 system with Sun patch 118833-36 or later

5.0.0 5.0.2

245709 The Recover All option should be checked during a clean shutdown of PowerPath.

5.0.1 5.0.2

235369PowerPath 5.0 in a Symmetrix environment does not support Veritas Cluster Server with I/O fencing (also called disk fencing).

5.0.0 5.0.2

Table 1 Fixed problems in PowerPath 5.0.2 for Solaris (continued)


Resolved in version


Fixed problems


227060After installing PowerPath 4.5 or PowerPath 5.0, the following messages appear on the console at boot time:Configuring /dev and /devicesConfiguring the /dev directory (compatibility devices)//catalog: No such file or directorySetting up pathsThe system is coming up. Please wait.

4.5.0 5.0.2

244235Added broadcast clear service action (0x3) to all paths to a logical volume in agreement with Symmetrix microcode team.

5.0.1 5.0.2



Resolved in version


DescriptionFound inVersion

Resolved in Version

247441The emcpower device mappings may change when a host reboots. This issue has been fixed in PowerPath 5.0.1. This fix is also included in PowerPath 5.0.2.

4.5.0 5.0.1

241164The powermt set periodic_autorestore=off class=<class> command does not affect only the specified storage system class.

5.0.0 5.0.1

241481After upgrading from PowerPath 4.5 to PowerPath 5.0, a boot from SAN configuration with pseudo devices does not work.

5.0.0 5.0.1

240457PowerPath on Solaris Opteron hosts does not support 64-bit libraries with Solutions Enabler and CLARiiON Navisphere.

5.0.0 5.0.1

240176After installing PowerPath, the following error messages appear when the host reboots:Configuring /dev and /devicesConfiguring the /dev directory (compatibility devices)//catalog: No such file or directorySetting up pathsThe system is coming up. Please wait.

5.0.0 5.0.1


10

Fixed problems

238694On Opteron hosts with an unlicensed version of PowerPath and the failover policy set to basic failover (bf), when you disconnect a cable from the default CLARiiON SP, messages informing you of LUN trespassing do not appear. However, when you enter powermt display dev=<device>, the output shows the LUNs as trespassed to SPB on the CLARiiON.

5.0.0 5.0.1

238652On a Solaris Opteron host with an unlicensed version of PowerPath, the following extraneous messages appear when you reboot a CLARiiON SP:Jul 26 12:22:01 lclc018.lss.emc.com emcp: [ID 801593 kern.notice] Info: Assigned volume 60060160969B16006502B40174BDDA11 to SPAJul 26 12:22:02 lclc018.lss.emc.com emcp: [ID 801593 kern.notice] Info: Assigned volume 60060160969B16006502B40174BDDA11 to SPB

(Output truncated)

5.0.0 5.0.1

238378236155You cannot uninstall PowerPath from the host when enclosure-based device naming is used (with VxVM).

5.0.0 5.0.1

238355227783Sun Dynamic Reconfiguration (DR) operations are unsupported with PowerPath 5.0.

4.5.0 5.0.1

237890232631On some hosts, when you upgrade from PowerPath 4.5.0 to PowerPath 5.0.0, pseudo-device mappings are lost.

5.0.0 5.0.1

237877On Opteron hosts in a Sun Cluster environment, a Sun Cluster host panics when you run powermt remove, powermt config, or powermt display concurrently with the Solaris scswitch command.

5.0.0 5.0.1

235890R1/R2 boot environments are unsupported in PowerPath 5.0.0. Refer to the PowerPath 5.0 for Solaris Installation and Administration Guide, available on the Powerlink website, for more information on R1/R2 boot support with PowerPath.

5.0.0 5.0.1

235369PowerPath 5.0 in a Symmetrix environment does not support Veritas Cluster Server with I/O fencing (also called disk fencing).

5.0.0 5.0.1



Resolved in Version


Fixed problems


233971In a Sun Cluster 3.1 environment with VxVM 4.1, switching all resources from one node to another causes a failfast panic on the source node.However, the node comes up cleanly afterwards, and the cluster regains full functionality.

5.0.0 5.0.1

232368230229The Solaris sd driver b_failfast feature is unsupported with PowerPath installed.

4.3.0 5.0.1



Resolved in Version



Resolved in Version

248638217622On Solaris hosts with PowerPath 4.5.0, Leadville drivers, and Solutions Enabler 6.3.x, Solutions Enabler storapid crashes intermittently.

4.5.0 5.0.0

246764An attempt to thaw a file system using the BCV split command fails.This fix is also available for PowerPath 4.5.0 as a hotfix.

4.4.0 5.0.0

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

4.5.0 4.5.05.0.0

215189Path degradation resulting from a hardware issue causes HBAs and the sd driver to retry I/Os. This can cause a delay in the completion of I/O and possibly cause unnecessary failovers. Path latency monitoring is a new feature in which PowerPath monitors paths and reports slow paths by sending a message to the log file. Refer to “New features and changes” on page 2 for a the list of the new powermt commands and to the PowerPath 5.0 Product Guide for detailed information on these commands.

4.3.0 5.0.0


12

Environment and system requirements

Environment and system requirementsThis section describes where to find interoperability and host configuration information, and includes notes not found in other sources.

Interoperability informationPowerPath interoperability information appears in the E-Lab Navigator as described in the next section. You can also find configuration information in the EMC Host Connectivity Guide for Sun Solaris, available on Powerlink.

E-Lab Interoperability NavigatorFor interoperability information, such as information about the hardware, software, and networked storage components that are tested and compatible with both EMC storage systems and third-party storage systems, refer to the E-Lab™ Interoperability Navigator (formerly ESN Builder), available on the Powerlink website (http://Powerlink.EMC.com). It also includes information about supported host models, operating system revisions, host bus adapters, and connectivity devices.

Note: Information in E-Lab Navigator takes precedence over the information in this release notice.

To access the E-Lab Interoperability Navigator:

1. Go to Powerlink at http://Powerlink.EMC.com.

209560You can now disable specified storage and HBA ports in PowerPath. This capability supports hardware service procedures, such as online HBA replacements and switch firmware updates. New powermt commands allow you to disable an HBA or storage-system port. Refer to “New features and changes” on page 2 for a list of the new powermt commands and to the PowerPath 5.0 Product Guide for detailed information on these commands.

4.3.0 5.0.0



Resolved in Version





2. From the Support menu, select Interoperability/Compatibility/Configuration> E-Lab Interoperability Navigator.

3. Click Launch E-Lab Interoperability Navigator.

4. For interoperability information on PowerPath with EMC arrays:

a. Click the Wizards tab.

b. From the pull-down menu at the top right of the page, select Software Support Wizard.

c. Select PowerPath from the Product list, and then select the product version.

d. Select the operating system and model.

e. In the Results section on the right side of the page, click the Combined Results link to view the interoperability information for the PowerPath software you selected.

For interoperability information on PowerPath with third-party arrays:

a. Click the PDFs and Guides tab.

b. Scroll down to the Infrastructure Software heading, and click the PowerPath PDF.

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. Host connectivity guides are updated quarterly and published on the Powerlink website.

Note: Information in the host connectivity guide takes precedence over the information in this release notice.

Before you install PowerPath, or when changing system components, consult the E-Lab Navigator, the EMC Host Connectivity Guide for Sun Solaris, and the PowerPath for Solaris Installation and Administration Guide. Changing any system component can change the way PowerPath manages storage paths. Consult these resources before you undertake any of the following common system or network management tasks:


14


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

Disk space requirements

The following table shows minimum disk space requirements for Solaris.

Connectivity requirementsInstall host bus adapters (HBAs), their supporting firmware versions, and other network components using the manufacturer’s directions and the settings specified in the E-Lab Interoperability Navigator. Using improper settings can cause erratic failover behavior or extended response time for system I/O.

EMC storage systemsThis section includes information on EMC arrays with PowerPath that is not included in the E-Lab Interoperability Navigator.

CLARiiON support PowerPath installation is an integral part of a CLARiiON setup and configuration procedure. To properly install PowerPath on a host

Table 4 Solaris: Disk space required

File System or Directory Minimum Space Requirements

Installation directory (the default is /opt) 40 MB

Root file system 16 MB

/usr 12 MB

/var 1 MB



with a CLARiiON array, refer to the EMC Installation Roadmap for CX3-Series, CX-Series, AX-Series, and FC-Series Storage Systems. There you will find step-by-step instructions for installing PowerPath and other CLARiiON software.

CLARiiON AX-Series installation, planning, and troubleshooting documents are located on the AX100 or AX150 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 AX-Series storage systems.

Note: CLARiiON customers receive PowerPath with the CLARiiON Utility Kits that ship with CLARiiON CX- and CX3-series storage systems. This version of PowerPath, referred to as PowerPath SE, provides basic failover for single HBA host configurations without the use of a license key. Please refer to Important Information About PowerPath SE for more information on the CLARiiON configurations supported by PowerPath SE.

Invista storage virtualizationVxVM interaction with Invista requires PowerPath on the host. Before creating Invista Virtual Frames that will be accessed by the host, 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.

Symmetrix support There are no configuration notes for Symmetrix storage systems.

Third-party storage systemsThis section includes information on third-party arrays with PowerPath that is not included in the E-Lab Interoperability Navigator.

HP Platform Kits HP requires installation of a host Platform Kit, which contains the drivers supported with the specific storage system. You can download the Platform Kit from the HP website.


16

Known problems and limitations

Interoperability with VxVMFor PowerPath 5.0.x for Solaris SPARC 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.

HBA driver settings The following table describes changes to the default driver configuration files required by PowerPath 5.0.x for Solaris SPARC with third-party storage systems.

Known problems and limitationsThis section describes the known problems and limitations in PowerPath 5.0.x for Solaris.

Table 5 Solaris SPARC: HBA driver settings—third-party storage systems

HBA driver ParameterDefault setting

PowerPath setting

Setting Required for

Emulex automap 0 0 All third-party systems

linkdown-tmo 30 60 All third-party systems

lun-queue-depth 30 20 All third-party systems

num-iocbs 1024 2048 All third-party systems

tgt-queue-depth 0 512 All third-party systems

no-device-delay 0 0 All third-party storage systems



Known problems Table 6 shows known problems in PowerPath 5.0.x for Solaris.

Table 6 Known problems in PowerPath version 5.0.x for Solaris

Description WorkaroundFound inVersion

Resolved in Version

258139When installing PowerPath 5.0.0 on a Solaris Opteron host, if you do not include the package name as part of the installation command (pkgadd -d <package name>), the NFS service goes offline if the customer has existing NFS mount points and fails to restart. If the package name is provided as part of the pkgadd command, the installation proceeds as expected.

If you encounter this problem:1. Verify the NFS client service is

offline. Enter:svcs | grep nfs

2. Disable the NFS client service:svcadm disable nfs/client

3. Kill the NFS mount/mountall commands started by the NFS start service.

4. Verify the NFS mount is accessible: df -k

5. Enable the NFS client service:svcadm enable -r nfs/client

5.0.0 —

255118 In a CLARiiON environment, I/O fails when the owner SP of a LUN is changed (for example, from SPA to SPB), and the LCC of the current owner (SPB) is pulled. No I/O failure is detected when the same is tried when the LUN belongs to the original owner SP (here SPA). This can occur with both SPs.

5.0.2 —

255066 If a CLARiiON disk is pulled when I/O is running, the device failure does not get detected. The system log continuously shows the following message: emcp:Mpx:Info: Unable to follow volume 600601601CD41400945828858BEDDB11 to SPA

5.0.2 —

257893 The VxVM plexattach operation takes much longer with PowerPath than with Sun MPxIO.

5.0.2 —


18


258316 PowerPath adds parameter settings at the end of /etc/system . If another product sets these parameters to a higher value, when you install PowerPath, the line in which this parameter would be set is omitted. The parameter is then missing when you try to uninstall the other product.

If you find a parameter required for PowerPath in /etc/system that has a value higher than PowerPath would set, repeat the line in which the parameter is set. Use the highest value you can find in /etc/system.

5.0.2 —

259869 Periodic autorestore does not automatically restore dead paths to a device on AMD Opteron host.

Run the powermt restore command to restore the paths.

5.0.2 —

259516Installing PowerPath 5.0.2 on AMD Opteron hosts disables volfs, the volume management file system service.

Change the timeout_seconds value from 30 to 120 in the following configuration files: • /var/svc/manifest/system/filesystem/volfs.xml

• svcadm disable volfs

• svccfg delete volfs

• svccfg import /var/svc/manifest/system/filesystem/volfs.xml

• svcadm enable volfs

5.0.2 —

259112On Solaris10 U4 b11, PowerPath does not see the emcpower devices after rebooting

Run the powermt config command after rebooting PowerPath.

5.0.1 —

258514On executing the powermt remove dev=all, touch /reconfigure, and init 6 commands, the system hangs during reboot

5.0.1 —

253421ZFS resource groups take about seven minutes on a host (with over 60 devices) to switch over to the second node.

5.0.1 —

251773On PowerPath 5.0.1, lock congestion occurs when the SRDF link is down and a large number of processes are issuing sequential I/Os with block size=2k.

5.0.1 —



Resolved in Version



emc134813 (EMC Knowledgebase solution)After installing Solaris 10 U1, MPxIO automatically manages CLARiiON arrays. This issue is caused by Sun MPxIO behavior.

To disable MPxIO globally, edit the /kernel/drv/fp.conf file to include: mpxio-disable="yes";

To disable multipathing on an HBA port, add to the /kernel/drv/fp.conf file the following: name="fp" parent="parent name" port=port-number mpxio-disable="yes";eg:name="fp" parent="/pci@6,2000/SUNW,qlc@2" port=0 mpxio-disable="yes";

Reboot the host to apply the configuration changes.

4.5.0 —



Resolved in Version


20


254503The Solaris format command requires fdisk on native devices but not on PowerPath pseudo devices. With VxVM on Opteron hosts, VxVM removes the fdisk partition.The following EMC Knowledgebase Solutions also address this topic:emc158473emc164551emc159577

Refer to “Running fdisk on Opteron hosts” on page 32.In a VxVM environment, complete one of the following procedures.Option 11. Initialize the PowerPath devices

as simple devices. Enter:/etc/vx/bin/vxdisksetup –fi <device> format=simple

2. Create non-CDS disk groups. Enter:/sbin/vxdg init <DG> cds=off <options> <device>

3. Add the devices to the disk group. Enter:/sbin/vxdg –g <DG> adddisk <[disk=]device>

Option 21. Change the PowerPath pseudo

devices to native devices. Enter:

• vxddladm set namingscheme=osn

• vxdmpadm setattr enclosure <enclosure_name> tpdmode=native

5.0.0 —

244891PowerPath 5.0.1 cannot co-exist with MPxIO on Opteron hosts; if MPxIO is enabled and managing CLARiiON arrays, a host panic may occur when you install PowerPath 5.0.1.

If MPxIO is enabled and managing CLARiiON arrays, disable MPxIO globally before you install PowerPath 5.0.1. Edit the /kernel/drv/fp.conf file to include: mpxio-disable="yes";

Reboot the host to apply the configuration changes.

5.0.1 —



Resolved in Version



244656After removing PowerPath 5.0 from a host where VERITAS Volume Manager is installed, you see the following message when you run vxdisk list :VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible

Reboot the host after removing PowerPath, and then retry the vxdisk list command.

5.0.1 —

242924When there are unlabeled devices, 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

To fix this issue:1. Unmanage each of the

unlabeled devices. Enter:powermt unmanage dev=<device>

2. Format and label the devices.3. Re-manage each of the

devices:powermt manage dev=<device>

5.0.1 —

244111After unmanaging Symmetrix or CLARiiON devices with the powermt unmanage command, VxVM continues to report that the removed devices belong to the Symmetrix or CLARiiON array.

5.0.1 —



Resolved in Version


22


242477PowerPath cannot be removed from a SAN boot device (when booting off a native device). The pkgrm command fails with the following error, though no devices except the boot device are in use: message Error: PowerPath pseudo(s) still in-use, busy or mounted.

This may occur when you switch from booting from a pseudo-named device to booting from a native-named device.

When switching to a native boot device, before uninstalling PowerPath, ensure the dump device is not a pseudo device.To determine the current dump device, enter:# dumpadm

Output:Dump content: kernel pagesDump device: /dev/dsk/emcpower0a (swap)

(output truncated)If the dump device is a pseudo device:1. Identify the underlying native

device associated with the pseudo dump device.

2. Change the dump device to the native device you identified. 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.

5.0.1 —

241978When you install PowerPath 5.0.1, unmanaged arrays may become managed by PowerPath. This is a known issue with Hitachi arrays that are managed by HDLM; the Hitachi arrays that were unmanaged in PowerPath 5.0 are automatically managed when you install PowerPath 5.0.1.

After installing PowerPath 5.0.1, manually unmanage the array class. Enter:powermt unmanage class=<class>

5.0.1 —

240702A soft hang may occur when you initialize a VxVM disk on a PowerPath pseudo device using vxdisksetup -i with Veritas Volume Manager 5.0.

Install Veritas Storage Foundation 5.0 MP1 for Solaris when using PowerPath with Veritas Volume Manager 5.0.

5.0.0 —



Resolved in Version



238554With VxVM 5.0, when dmp_cache_open is set to on (the default), you cannot use emcpadm to swap names of pseudo devices, nor can you uninstall PowerPath. Devices are opened by VxVM when this parameter is set to on.

Before upgrading to PowerPath 5.0, or before using emcpadm to swap pseudo device names, disable dmp_cache_open. Enter:vxdmpadm settune dmp_cache_open=off

After upgrading PowerPath or swapping pseudo names, enable the parameter. Enter:dmp_cache_open:

vxdmpadm settune dmp_cache_open=on

5.0.0 —

238016After removing a Fibre Channel cable from the host, and then rebooting the system, the powermt display command displays the disconnected HBA as UNKNOWN.

To remove UNKNOWN from powermt display output:1. Run powermt remove dev=all to remove all devices.

2. Run powermt config.

5.0.0 —

238211On Opteron hosts in a Symmetrix environment, before installing PowerPath in a VCS or Sun Cluster verify that each node has a unique host ID. Failure to use unique host IDs breaks the cluster disk-fencing scheme.

To display host IDs, enter the following command on each node in the cluster:hostid

Contact Sun customer support for instructions on creating unique host IDs.

5.0.0 —

237710After upgrading from 4.0.x to 5.0.0, devices come up as unmanaged on all arrays.

Upgrade from 4.0.x to PowerPath 4.5 (which does not require a host reboot), and then upgrade from 4.5 to 5.0.Or, do a fresh installation of PowerPath 5.0; this method does not preserve emcpower device numbering.

5.0.0 —

237483With MPxIO explicitly enabled for the EVA8000 or EVA3000/5000 with VCS4.x, the command powermt manage class=hpxp does not fail with an error message, as occurs with other arrays.

If MPxIO is enabled for the EVA 8000 or EVA 3000/5000 arrays, do not try to manage these devices with PowerPath. Alternatively, remove the EVA arrays from explicit MPxIO management.

5.0.0 —



Resolved in Version


24


237040Unmanaging Symmetrix devices with the powermt unmanage class=symm command requires a host reboot before re-managing them, even when no devices are being kept open by applications.

5.0.0 —

236825234389 Pseudo-named devices with PowerPath 5.0 and VxVM 4.1 and VxVM 5.0 are unsupported with EFI disks.

4.5.0 —

235730Numerous corrupt label console messages appear when an array LUN cannot be labeled. For example, when unlabeled, write-protected Symmetrix devices are present, you see the corrupt label messages.

If possible, label the unlabeled disks.If you cannot label the disks, then zone the unlabeled disks so the PowerPath host cannot see them.In a Symmetrix environment, this involves masking the disks; in a CLARiiON environment, remove them from the Storage Group.

5.0.0 —

235871When you enter a value for the powermt set path_latency_threshold command that is invalid, an error message appears, but the message does not include the range of acceptable values.

The range of acceptable values is 0 to 2,147,483,647. Set the threshold to a value within this range.

5.0.0 —

235248235253IBM SDD version 1.6 64 bit is compatible with PowerPath 5.0 on Solaris 10 hosts. However, IBM SDD version 1.4 with PowerPath 5.0 on Solaris 10 hosts causes a host panic when I/O requests are sent to vpath devices. When you unmanage IBM ESS devices, reboot the host, and then run the showvpath command, you see a message similar to the following:message: Segmentation Fault (core dumped)This problem does not occur with IBM SDD version 1.4 with PowerPath 5.0 on Solaris 9 hosts.

Use IBM SDD version 1.6 on Solaris 10 hosts.

5.0.0 —

235231PowerPath does not prevent you from disabling with the powermt disable hba command the last available HBA in your environment.

When you use the powermt disable command, ensure you do not disable the last available HBA.

5.0.0 —



Resolved in Version



234128When you reboot the host, you see the following message, even though a PowerPath Migration Enabler migration is not running: lclc231 console login: Apr 25 12:15:50 lclc231 PPME: API: Info: Beginning AUTOMATIC RECOVERYApr 25 12:15:51 lclc231 PPME: API: Info: Finished AUTOMATIC RECOVERY

You can safely disregard these messages.

5.0.0 —

233195In a Solaris 10 Opteron environment, when you unmap devices on the array and the /dev/rdsk or /dev/dsk links are not removed, host reboots may take longer than usual.

Remove the /dev/dsk or /dev/rdsk device links when devices are purposefully removed from a host.Use the rm command to remove the links, or use a combination of cfgadm and devfsadm -C commands to unconfigure the devices and remove the links.

5.0.0 —

233005Due to a Sun limitation, when adding a device to a Sun Volume Manager metaset, using the pseudo-device name causes an error. You must use the native device name.

Use the native device name when adding a device to a Sun Volume Manager metaset. For example:metaset -s mset0 -d c3t2d25

5.0.0 —

232620After entering the pkgadd –R command and rebooting the host, a message similar to the following appears:WARNING - The following files in / differ from the boot archive:/etc/system/etc/name_to_major/etc/driver_aliases/etc/driver_classes

Due to differences in the Solaris 10 03/05 and 01/06 releases, 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.

To fix this issue:1. Reboot and select Solaris

failsafe options from the boot menu.

2. Follow the prompts to update the boot archive.

3. Enter: svcadm clear system/boot-archive

5.0.0 —



Resolved in Version


26


231422231946When installing PowerPath on an AMD Opteron host with MPxIO enabled, disable MPxIO before installing PowerPath.If you do not disable MPxIO, a system hang may occur upon reboot after installing PowerPath, and messages similar to the following appear:WARNING: forceload of drv/ssd failedWARNING: forceload of misc/emcpsapi failedWARNING: forceload of misc/emcpcg failedWARNING: forceload of drv/ssd failedWARNING: forceload of misc/emcpsapi failedWARNING: forceload of misc/emcpcg failedHostname: lclc015.lss.emc.com

Manually disable MPxIO globally, enter the following line in the /kernel/drv/fp.conf file: mpxio-disable="yes"

5.0.0 —

229447Pseudo device mappings in VERITAS Volume Manager Version 4.1 may become inconsistent with PowerPath pseudo device mappings under certain conditions.

Refer to “Inconsistent pseudo device mappings with VxVM 4.1” on page 37.Refer also to EMC Knowledgebase Solution emc126617.

4.5.0 —

227775R1/R2 boot support is not supported with PowerPath 4.5 and 5.0 and the Leadville driver (also called the Sun native driver).

4.5.0 —



Resolved in Version



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

— When upgrading or reinstalling PowerPath, reboot after the initial package remove, if PowerPath requested the reboot. — When duplicate entries are seen, a second reboot will clear the duplicates. The PowerPath pseudo device links will be available during the second reboot. — When mapping/zoning new LUNS to the host, to avoid duplicate entries:1. Run vxddladm stop.

eventsource.2. Map/zone the new LUNS to the

host.3. Dynamically recreate the LUN

device (either using cfgadm routines or HBA-specific routines to dynamically create the device nodes).

4. Run powermt config to discover and create the pseudo device links.

5. Run vxddladm start eventsource.

— When a host is rebooted with a path down, to avoid duplicates:1. Run vxddladm stop eventsource

2. Reconnect the paths.3. Run powermt config.4. Run vxddlam start.

eventsource.— If vxddladm commands were not run, then reboot the system to remove the duplicate entries.

4.4.0 —



Resolved in Version


28


210941In 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 686697 kern.info] NOTICE: Qlogic qlc(1): Link ONLINEOct 12 12:03:53 db026ops scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp1):Oct 12 12:03:53 db026ops Lun=0 for target=615313 disappearedOct 12 12:03:53 db026ops scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp1):Oct 12 12:03:53 db026ops Lun=0 for target=614313 disappearedOct 12 12:03:58 db026ops qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(2): Loop OFFLINE

Install the appropriate SUN T-patch. For Solaris 8 or 9 install SAN 4.4.9. For Solaris 10, install Sun patch 119130-17.EMC Knowledgebase solution emc108113 also addresses this issue.

4.4.0 —

204709Running the powermt remove dev=all and powermt config commands on a host that has mounted the SnapView LUN makes the snapshot inactive, causing data corruption.

4.4.0 —

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

Ignore the messages. 4.4.0 —



Resolved in Version



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

1. Query the CLARiiON storage array using Navisphere, and determine whether the admsnap command completed the operation for all devices specified on the command line. If it did, no action is required.

2. If the admsnap command failed to complete the operation for all of the devices specified on the command line:For start operations that failed to complete, stop the session on the devices and retry the admsnap command.For activate operations that failed to complete, deactivate the session on the devices and retry the admsnap command.For stop operations that failed to complete, stop the session. No further action is required.For deactivate operations that failed to complete, deactivate the session. No further action is required.

3. If this problem persists, use Navisphere instead of Admsnap to perform the operation.

4.3.0 —

165579Using 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. You see the following message when you unmanage a boot device:WARNING: One or more boot devices have been unmanaged. Update the system configuration settings as appropriate. Cannot remove device that is in use: <emcpowerx>

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

4.1.0 —



Resolved in Version


30


Limitations This section includes limitations in PowerPath 5.0.x for Solaris and limitations in third-party software that affect PowerPath operation.

◆ PowerPath 5.0 for Solaris does not support zettabyte file systems (ZFS) with HP StorageWorks EMA, MA, and EVA 3000/5000 systems with VCS 3.x.

◆ When you disable a port with the powermt set port_disable command, the disabled port state persists across host reboots. However, this does not guarantee the complete suppression of I/O from the host to the array port during early boot.

◆ When you disable a port with the powermt set port_disable command in an R1/R2 environment, the disabled port does not persist through a failover or failback.

◆ In an R1/R2 boot support environment:

• PowerPath 5.0 does not support Sun X6767A and X6768A HBAs (Leadville driver).

• R1/R2 boot support hosts must be connected directly to the Symmetrix system; they cannot be connected through the fabric.

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

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

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

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

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

3.0.3 —



Resolved in Version



◆ PowerPath 5.0.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, Hitachi Lightning, Hitachi TagmaStore, or HP StorageWorks environment.

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.

◆ PowerPath cannot failover path-specific requests, such as dev_info.

◆ PowerPath 5.0.x can coexist 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; PowerPath cannot co-manage devices with third-party path management software.

Note: PowerPath 5.0.1 cannot co-exist with MPxIO on Opteron hosts, as described in known issue 244891.

◆ The following limitations apply to a VERITAS Volume Manager environment or a VERITAS Cluster Server environment:

• PowerPath 5.0.1 supports Sun Cluster 3.1 on SPARC Solaris 9 and 10 platforms with VxVM 4.1 only when VERITAS patch 4.1 MP1 RP4 (121755-08) or later is installed.

• VERITAS Volume Manager 4.1 or later does not support PowerPath pseudo device names with third-party arrays. You can use either native names or enclosure-based names. To change the VxVM third-party driver mode (tpdmode) to native, use this command syntax:

vxdmpadm setattr enclosure <enclosure> tpdmode=native

This limitation applies also to any EMC devices in a mixed array environment.

• Due to a VERITAS limitation, VxVM 4.1 and VxVM 4.1 MP1 with Leadville adapters support only enclosure-based device naming.

• Due to a known problem in VERITAS Volume Manager 4.1, PowerPath on Solaris 10 does not support root device encapsulation with VxVM 4.1.


32

Technical notes

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

Technical notesThis section contains additional information on PowerPath not covered in the core documents. The following sections are included:

◆ “Running fdisk on Opteron hosts” on page 32

◆ “emcpadm enhancements” on page 33

◆ “PowerPath support with iSCSI” on page 34

◆ “Exporting emcpower devices to Non-Global zones” on page 36

◆ “Inconsistent pseudo device mappings with VxVM 4.1” on page 37

◆ “powermt class arguments with HP StorageWorks EVA arrays” on page 38

◆ “HP StorageWorks controller and port names” on page 39

Running fdisk on Opteron hosts

ProblemThe Solaris format command on AMD Opteron hosts requires fdisk on native disks but not on emcpower devices. The usage of fdisk on PowerPath pseudo devices destroys the partitions created by the Solaris format command.


Technical notes

Workaround

1. Present blank LUNs to the host. Run powermt config and ensure all paths to devices are present and alive.

2. Use fdisk to create a Solaris MBR partition on the native device:

fdisk -B/dev/rdsk/cxtxdxp0

3. Use prtvtoc to determine the sector count for the device:

prtvtoc /dev/rdsk/cxtxdxp0

4. Use fmthard to create desired slices on the partition:

fmthard -d part:tag:flag:start:size -n volname /dev/rdsk/cxtxdxp0)

5. Run newfs against the cxtxdxsx device.

Mount and proceed normally using either the appropriate pseudo or native devices.

emcpadm enhancementsPowerPath 5.0.2 includes enhancements to the emcpadm command that allow you to preserve and restore PowerPath pseudo-device-to-array logical-unit bindings. The new emcpadm commands simplify the process of renaming pseudo devices in a cluster environment. For example, you can export the device mappings configured on one node in a cluster, and import the mappings on other cluster nodes. Configuring nodes in this manner ensures consistent emcpower device-naming across a cluster.

Command syntax and descriptionThis section describes briefly the new emcpadm commands. For more information and examples, refer to the PowerPath 5.0 Product Guide, available on the Powerlink website.

emcpadm check_mappings [-v ] -f <pseudo device/LU mappings file>Compares the currently configured mappings with the mappings in <pseudo device/LU mappings file>.

emcpadm export_mappings -f <pseudo device/LU mappings file>Saves the currently configured mappings to <pseudo device/LU mappings file>.

emcpadm import_mappings [-v ] -f <pseudo device/LU mappings file>


34

Technical notes

Replaces the currently configured mappings with the mappings in <pseudo device/LU mappings file>. If a conflict occurs between the existing mappings and the file mappings, the content in <pseudo device/LU mappings file> takes precedence.

emcpadm print_mappings [-p | -f <pseudo device/LU mappings file>]Displays the current mappings or the mappings in <pseudo device/LU mappings file>. The current mappings are those configured on the node where you run this command. <pseudo device/LU mappings file> contains the mappings previously exported to the specified file.

Arguments

-f <mappings_file>Specifies the file name and location for <mappings_file>.

Environment variables This section describes the new environment variables associated with enhancements to the emcpadm command.

ECMPADM_DBG=<value>

Setting this environment variable to any value enables debugging. By default this environment variable is not set.

EMCPADM_ERR=<value>

Setting this environment variable to any value enables error logging. By default this environment variable is not set.

PowerPath support with iSCSIPowerPath 5.0.1 supports storage systems connected through iSCSI data channel ports. This section includes configuration notes for PowerPath hosts connected through iSCSI.

Limitations In a configuration where the host is connected to an array through an iSCSI data channel port:

◆ For both NICs on a host, the iSCSI initiator presents a single iSCSI instance to PowerPath. Consequently, when a path fails, the path shows as degraded rather than dead when you run powermt display. Refer to “powermt display examples” on page 35 for sample output.

◆ When you disable or enable an iSCSI port, PowerPath’s recognition of the path failover is delayed due to an issue with the Sun iSCSI initiator. For example, if you disable a path in a


Technical notes

CLARiiON environment, it takes five minutes for the path to show up as dead in the powermt display command. However, if you use the iscsiadm utility, the path change is recognized in less than one minute.

◆ Do not use the ifconfig command to disable a NIC port. Instead, manually remove the cable from the port, or disable it on the switch. Due to an issue with the iSCSI driver, PowerPath cannot correctly recognize path status when path status is changed with the ifconfig command.

Configuration requirements

Note: For the most up-to-date interoperability information, refer to the E-Lab Interoperability Navigator, available on the Powerlink website.

The following configuration requirements apply in a PowerPath iSCSI environment:

◆ Only one iSCSI session is allowed per target.

◆ Only hosts connected through Network Interface Cards (NICs) are supported; HBA configurations are not supported at this time.

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

◆ You cannot boot a Solaris host using an iSCSI disk volume provided by a software iSCSI initiator.

powermt display examplesThe iSCSI initiator presents a host NIC to PowerPath as one iSCSI instance. Consequently, when a path fails and you run the powermt display command, the path shows as degraded rather than dead.

powermt displaySymmetrix logical device count=0CLARiiON logical device count=4Hitachi logical device count=0Invista logical device count=0HP xp logical device count=0Ess logical device count=0HP HSx logical device count=0==============================================================================----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------### HW Path Summary Total Dead IO/Sec Q-IOs Errors==============================================================================


36

Technical notes

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, as follows:

powermt display dev=allPseudo name=emcpower3aCLARiiON ID=HK192201138 [aaqa23]Logical device ID=600601601AC01800CE9CB0584573DB11 [LUN 200]state=alive; policy=CLAROpt; priority=0; queued-IOs=0Owner: default=SP A, current=SP B==============================================================================---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---### HW Path I/O Paths Interf. Mode State Q-IOs Errors==============================================================================4608 iscsi c3t11d0s0 SP B1 active alive 0 04608 iscsi c3t14d0s0 SP B0 active dead 0 04608 iscsi c3t17d0s0 SP A0 active dead 0 14608 iscsi c3t20d0s0 SP A1 active alive 0 1

(Output truncated)

Exporting emcpower devices to Non-Global zones

Note: This section applies to PowerPath 5.0 with Solaris 10.

This section describes how to export PowerPath pseudo devices (emcpower devices) to Non-Global Zones (also called NG Zones). After you export the pseudo devices, you can create filesystems from the NG Zones, or you can use them through volume managers.

To export emcpower devices to NG Zones:

1. Manually enter the pseudo device names in the /etc/devlink.tab file.

Note: —For each pseudo device to be exported, create two entries: one for the

raw device and one for the block device.—You must enter a single tab between the two fields in each line. For

example, the tab appears between blk and dsk in the first sample entry. Adding spaces instead of tabs causes the entries to be ignored.

For example, enter these lines in the /etc/devlink.tab:

type=ddi_pseudo;name=emcp;addr=0;minor=a,blk dsk/emcpower\A0\M1type=ddi_pseudo;name=emcp;addr=0;minor=a,raw rdsk/emcpower\A0\M1type=ddi_pseudo;name=emcp;addr=1;minor=a,blk dsk/emcpower\A0\M1


Technical notes

type=ddi_pseudo;name=emcp;addr=1;minor=a,raw rdsk/emcpower\A0\M1

2. After you modify the /etc/devlink.tab file, reboot the host.

3. After rebooting the host, ensure the NG Zones are not in a booted condition, and then make configuration changes be entering the following commands:

Note: In this example, the NG Zone is zone1.

# zonecfg zoone1zonecfg:zone1> add device zonecfg:zone1:device> set match=/dev/rdsk/emcpower0azonecfg:zone1:device> endzonecfg:zone1> add device zonecfg:zone1:device> set match=/dev/dsk/emcpower0azonecfg:zone1:device> endzonecfg:zone1> exit# zoneadm –z zone1 boot

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

Inconsistent pseudo device mappings with VxVM 4.1The pseudo device mappings in VERITAS Volume Manager Version 4.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, VxVM maps pseudo devices according to information saved before you uninstalled the software. This information may be different from the current PowerPath mappings and configuration.

◆ When you rename an emcpower device instance using the emcpadm command, VxVM loses the pseudo device mapping.

When inconsistent mappings of pseudo devices occur, use this procedure to correct the mappings:

1. Enter:

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

2. Enter:


38

Technical notes

echo > /etc/vx/disk.info

3. Enter:vxconfigd -k

powermt class arguments with HP StorageWorks EVA arraysPowerPath 5.0 introduces support for HP StorageWorks Enterprise Virtual Array (EVA) 8000 systems and EVA 3000/5000 systems with VCS 4.x. 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, rather than through the hphsx class. (The class argument limits a powermt command to the specified type of storage system.)

Table 7 shows the HP Storage Works EVA systems supported, their corresponding class arguments, and their default load balancing and failover policies with and without a PowerPath license. For more information about class arguments or load balancing and failover policies, refer to the PowerPath 5.0 Product Guide.

ExampleThe following example shows the powermt display output for PowerPath 5.0 and an HP StorageWorks EVA 8000 system.

powermt displaySymmetrix logical device count=0CLARiiON logical device count=0Hitachi logical device count=0Invista logical device count=0HP xp logical device count=8Ess logical device count=0

Table 7 Support for HP StorageWorks EVA systems

Storage Systempowermt Class Argumenta

Default Policy Without a PowerPath License

Default Policy With a PowerPath License

HP StorageWorks EVA 3000 or 5000 with VCS 3.x hphsx Basic failover (bf)

Adaptive (ad)

HP StorageWorks EVA 3000 or 5000 with VCS 4.xHP StorageWorks EVA 8000

hpxpb No redirect (nr)

Adaptive (ad)

a. The class argument limits a powermt command to the specified type of storage system.

b. HP StorageWorks xp arrays are also managed through the hpxp class. This behavior has not changed from previous PowerPath releases.


Technical notes

HP HSx logical device count=0

================================================================================----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------### HW Path Summary Total Dead IO/Sec Q-IOs Errors================================================================================1280 pci@1f,700000/fibre-channel@2 optimal 16 0 - 0 01281 pci@1f,700000/fibre-channel@2,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.x. In this example, the new default policy, basic failover, is set.

powermt display dev=all class=hphsx | more

The following output is truncated.

Pseudo name=emcpower2aHP HSx ID=50001FE15000B020Logical device ID=600508B4000146870007000000710000state=alive; policy=BasicFailover; priority=0; queued-IOs=0Controller: HSV110 Controller A: 4889ILY028 Controller B: 4889ILZ020Default owner=A Current owner=A==================================================================================---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---### HW Path I/O Paths Interf. Mode State Q-IOs Errors==================================================================================3072 pci@4,4000/fibre-channel@2/fp@0,0 c2t50001FE15000B029d1s0 A 1 unlic alive 0 03072 pci@4,4000/fibre-channel@2/fp@0,0 c2t50001FE15000B02Cd1s0 B 0 unlic alive 0 03073 pci@4,4000/fibre-channel@2,1/fp@0,0 c3t50001FE15000B028d1s0 A 0 active alive 0 03073 pci@4,4000/fibre-channel@2,1/fp@0,0 c3t50001FE15000B02Dd1s0 B 1active alive 0 0

HP StorageWorks controller and port namesPowerPath names for HP StorageWorks EVA and HSG80 controllers and ports differ from the names in the array GUIs. This section describes the differences.

HP StorageWorks EVA namesPowerPath identifies controllers A and B exactly as Command View EVA does. PowerPath port numbers are one lower than Command View EVA port numbers.

Names are mapped as follows:

Command View EVA name PowerPath name

A-1 A-0


40

Documentation

HP StorageWorks HSG80PowerPath names the bottom controller A and the top controller B. PowerPath port numbers are one lower than HSG Element Manager port numbers.

Names are mapped as follows:

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

PowerPath documentationThe following table lists the PowerPath documentation set; all manuals are available from EMC Corporation. Electronic versions of all PowerPath manuals are available on the Powerlink website: http://Powerlink.EMC.com. These manuals are updated

A-2 A-1

B-1 B-0

B-2 B-1

Command View EVA name PowerPath name

HSG Element Manager name PowerPath name

Bottom-1 A-0

Bottom-2 A-1

Top-1 B-0

Top-2 B-1



Software media, organization, and files

periodically, and the updated manuals are posted on the Powerlink website.

Related documentationIf 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 CX3-Series, CX-Series, AX-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

◆ 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, refer to the appropriate documentation from your vendor.

Software media, organization, and filesThis section contains information about the PowerPath 5.0.x media and files.

Name

EMC PowerPath 5.0 for Solaris Installation and Administration Guide

EMC PowerPath 5.0 for Solaris Release Notes

EMC PowerPath 5.0 Product Guide


42

Installation

Media and organization

PowerPath 5.0.2PowerPath 5.0.2 is a stand-alone full package release. It is available on the Powerlink website and is distributed as a compressed tar file.

PowerPath 5.0.1PowerPath 5.0.1 is a patch release available as a compressed file on the Powerlink website. The following files are available for download:

◆ For SPARC hosts: EMCPower.SOLARIS.5.0.1.Patch.b0xx.tar.gz

where xx = the build number

◆ For Opteron hosts: EMCPower.SOLARIS_i386.5.0.1.Patch.b0xx.tar.gz

where xx = the build number

PowerPath 5.0.0PowerPath 5.0.0 is distributed on a CD, which has the following structure:

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

◆ /UNIX/SOLARIS/EMCPower.SOLARIS.5.0.0.GA.bxxx.tar.Z — Compressed tar file that contains the PowerPath and PowerPath Migration Enabler packages.

where xxx = the build number

PowerPath 5.0.0 package is also distributed on Powerlink in the compressed tar file format.

Files For information on files added by PowerPath 5.0.0, refer to Appendix A, “Files Changed By PowerPath,” in the PowerPath 5.0 for Solaris Installation and Administration Guide.

InstallationRefer to the PowerPath 5.0 for Solaris Installation and Administration Guide for instructions on installing PowerPath.


Troubleshooting and getting help

For the new user PowerPath 5.0.2To install PowerPath 5.0.2, follow the instructions in the PowerPath 5.0 for Solaris Installation and Administration Guide.

PowerPath 5.0.1To install PowerPath 5.0.1, follow the instructions in the ReadMe.txt file posted with the patch on Powerlink.

PowerPath 5.0.0To install PowerPath 5.0.0, follow the instructions in the PowerPath 5.0 for Solaris Installation and Administration Guide.

Upgrading from a previous revision To upgrade to PowerPath 5.0.x, follow the instructions in the PowerPath 5.0 for Solaris Installation and Administration Guide.

Troubleshooting and getting helpFor additional information on EMC products and services available to customers and partners, refer to the EMC Powerlink website (registration required) at:


The Powerlink website contains current information, such as:

Product information — You can find documentation, release notes, software updates, and information about EMC products, licensing, and service.

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

Patches and upgrades — You can download PowerPath patch software from Powerlink. Review the patch ReadMe files to determine which patches (if any) you want to install after PowerPath, and whether those patches have prerequisites for installing PowerPath. To obtain patches, click Support > Downloads and Patches > Downloads D-R > PowerPath for UNIX.

E-Lab Issue Tracker — A Powerlink application that allows you to search for fix information for EMC product issues.



44

Troubleshooting and getting help

To access E-Lab Issue Tracker on Powerlink, click Support >E-Lab Issue Tracker Information > E-Lab Issue Tracker.

You can search Issue Tracker to find:

◆ Descriptions of PowerPath bugs existing on any PowerPath-supported host platform.

◆ Workarounds for existing bugs.

E-Lab Issue Tracker is updated regularly between scheduled releases and patch releases.

Reporting a problemIf you find a problem in PowerPath 5.0, run the emcgrab utility, and submit the generated tar file, along with any other supporting material, to EMC Customer Support. You can download emcgrab from the Powerlink website. Choose the following links: Support > Support and Diagnostic Tools > Grab Utilities.

If you are running PowerPath Migration Enabler and you encounter a problem, refer to the PowerPath Migration Enabler Release Notes for instructions on gathering troubleshooting information. The emcgrab utility does not collect Migration Enabler data.

Copyright © 2007 EMC Corporation. All rights reserved.

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

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

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

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


Date post:	19-Jan-2016
Category:	Documents
Upload:	giraiadoinferno
View:	16 times
Download:	0 times

300 003 593 Powerpath for Solaris Rn

Documents