EMC TPD emcpower names are changing after every reboot with VxVM 6.0.1.200

book

Article ID: 100009494

calendar_today

Updated On:

Cause

# powermt display dev=all|grep emcpower

Pseudo name=emcpower0a

Pseudo name=emcpower2558a

Pseudo name=emcpower2638a

Pseudo name=emcpower2639a

Pseudo name=emcpower2640a

Pseudo name=emcpower2641a

Pseudo name=emcpower2642a

Pseudo name=emcpower2643a

Pseudo name=emcpower2644a

...

 

After the reboot, the following pseudo names were seen:

# powermt display dev=all|grep emcpower

Pseudo name=emcpower0a

Pseudo name=emcpower100a

Pseudo name=emcpower101a

Pseudo name=emcpower102a

Pseudo name=emcpower103a

Pseudo name=emcpower105a

Pseudo name=emcpower107a

Pseudo name=emcpower109a

Pseudo name=emcpower110a

...

The issue is applicable to VxVM 5.0MP3RP3 and later, and seen with Powerpath 5.x

The PowerPath pseudo device mappings changed after every reboot, which was caused by VxVM running "powermt display unmanaged" to find unmanaged devices so that these could be skipped by the Powerpath ASL. However, VxVM issued the EMC powermt command before Powerpath had started.

To illustrate the problem, in the incident concerned, prior to the reboot, the following pseudo names were seen:

Resolution

The fix is scheduled to be built into 6.1 later in 2013. A fix is also available as a private hot-fix - please contact Veritas Technical Support for further details.

 

Applies To

6.0.1 VxVM

5.x Powerpath

Solaris 10

Issue/Introduction

The PowerPath pseudo device mappings changed on every reboot. After every reboot the mappings are re-mapped to the wrong pseudo names.