With old versions you needed to follow this procedure to remove devices from the host:
1. Perform a powermt remove for each device that is being unmapped. (This updates the information in the Powerpath0 driver).
2. Perform an rmdev –dl for each PowerPath device that is being removed from the host. (This deletes the old entries and characteristics from the ODM).
3. Perform an rmdev –dl the underlying hdisks for these devices. (This step is not necessary but is recommended).
4. At this point issue a savebase –v command. (This updates the phase 1 device attributes in the boot logical volume.)
5. The decommissioned device can be removed from the host now.
6. At this point it is safe to add additional storage to the host and run cfgmgr and powermt config.
What xxx do I use? I expected the hdiskpower name to be listed when i did the powermt display unmanaged, but it wasn't.
I actually deleted the line from /etc/emc/mpaa.excluded and now the device doesn't show up again when I do a powermt manage even after the savebase -v and the cfgmgr/powermt config. Putting the line back in the mpaa.excluded file at least brings the device back as unmanaged.
dynamox
9 Legend
•
20.4K Posts
0
September 9th, 2013 06:00
did you run cfgmgr after rmdev to rediscover it again ?
Y1Udba1GsO12085
71 Posts
0
September 9th, 2013 06:00
Hi Tim,
What PowerPath version are you running?
With old versions you needed to follow this procedure to remove devices from the host:
1. Perform a powermt remove for each device that is being unmapped. (This updates the information in the Powerpath0 driver).
2. Perform an rmdev –dl for each PowerPath device that is being removed from the host. (This deletes the old entries and characteristics from the ODM).
3. Perform an rmdev –dl the underlying hdisks for these devices. (This step is not necessary but is recommended).
4. At this point issue a savebase –v command. (This updates the phase 1 device attributes in the boot logical volume.)
5. The decommissioned device can be removed from the host now.
6. At this point it is safe to add additional storage to the host and run cfgmgr and powermt config.
Regards
timdaley
4 Posts
0
September 10th, 2013 10:00
# powermt display unmanaged
CLARiiON ID=APM00111702746
Logical device ID=600601600BC12C00962DA1176516E311
Vendor ID=DGC ; Product ID=RAID 0
===============================================
-------------------- Host ---------------------
HW Path I/O Paths
===============================================
fscsi0 hdisk116
fscsi2 hdisk120
fscsi2 hdisk146
fscsi0 hdisk3
# rmdev -Rdl hdisk116
hdisk116 deleted
# rmdev -Rdl hdisk120
hdisk120 deleted
# rmdev -Rdl hdisk146
hdisk146 deleted
# rmdev -Rdl hdisk3
hdisk3 deleted
# powermt display unmanaged
No unmanaged devices found.
# savebase -v
saving to '/dev/hd5'
541 CuDv objects to be saved
5115 CuAt objects to be saved
121 CuDep objects to be saved
478 CuVPD objects to be saved
841 CuDvDr objects to be saved
4 CuPath objects to be saved
0 CuPathAt objects to be saved
0 CuData objects to be saved
0 CuAtDef objects to be saved
Number of bytes of data to save = 700489
Compressing data
Compressed data size is = 114813
bi_start = 0x3600
bi_size = 0x1a20000
bd_size = 0x1a00000
ram FS start = 0x917590
ram FS size = 0x10a75f8
sba_start = 0x1a03600
sba_size = 0x20000
sbd_size = 0x1c081
Checking boot image size:
new save base byte cnt = 0x1c081
Wrote 114817 bytes
Successful completion
# powermt config
# powermt display unmanaged
No unmanaged devices found.
# cfgmgr
# powermt config
# powermt display unmanaged
CLARiiON ID=APM00111702746
Logical device ID=600601600BC12C00962DA1176516E311
Vendor ID=DGC ; Product ID=RAID 0
===============================================
-------------------- Host ---------------------
HW Path I/O Paths
===============================================
fscsi0 hdisk116
fscsi2 hdisk120
fscsi2 hdisk146
fscsi0 hdisk3
#
What now?
Y1Udba1GsO12085
71 Posts
0
September 10th, 2013 10:00
Hi again Tim,
I should have probably asked this before, but have you tried a "powermt manage" command?
powermt manage dev=xxx
Regards
Y1Udba1GsO12085
71 Posts
0
September 10th, 2013 11:00
In your case it should be "dev=600601600BC12C00962DA1176516E311"
Y1Udba1GsO12085
71 Posts
1
September 10th, 2013 11:00
I would suggest that you open a case with EMC support.
It might be that the status of the Clariion class is "manage_incomplete" or "unmanage_incomplete" which would require further troubleshooting.
Regards
timdaley
4 Posts
0
September 10th, 2013 11:00
What xxx do I use? I expected the hdiskpower name to be listed when i did the powermt display unmanaged, but it wasn't.
I actually deleted the line from /etc/emc/mpaa.excluded and now the device doesn't show up again when I do a powermt manage even after the savebase -v and the cfgmgr/powermt config. Putting the line back in the mpaa.excluded file at least brings the device back as unmanaged.
timdaley
4 Posts
0
September 10th, 2013 11:00
# powermt display unmanaged
CLARiiON ID=APM00111702746
Logical device ID=600601600BC12C00962DA1176516E311
Vendor ID=DGC ; Product ID=RAID 0
===============================================
-------------------- Host ---------------------
HW Path I/O Paths
===============================================
fscsi0 hdisk116
fscsi2 hdisk120
fscsi2 hdisk146
fscsi0 hdisk3
# powermt manage dev=600601600BC12C00962DA1176516E311
Error: manage of device 600601600BC12C00962DA1176516E311 failed
#
christopher_ime
4 Operator
•
2K Posts
0
September 13th, 2013 16:00
Tim,
Could you run the following on each?
lsdev -Cc disk | grep hdisk3
lsdev -Cc disk | grep hdisk116
lsdev -Cc disk | grep hdisk120
lsdev -Cc disk | grep hdisk146