Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SAN problem

Status
Not open for further replies.

mart1

MIS
Sep 24, 2001
14
FR
hi,

I have a problem with an AIX 5.2 server connected to a SAN, the SAN is a EMC CX500.
We have merged two swtiches ot make a fabric with 2 switch, since then all the servers connected to the SAN have some LUNZ devices. I have tried to remove them on one of the servers but they come back as soon as I do a cfgmgr.
So I decided to remove all disk configuration but that where the real problem starts.
I have been able to remove all the hdisk associated with the hdispower device but I was not able to remove the hdiskpower device itself. I tried to remove it with some odmdelete but it the device comes back as soon as I do a cfgmgr and I cannot use it anymore nor delete it.
When I tried a rmdev -dl hdiskpower I get :
Method error (/etc/methods/ucfgpowerdisk):
With no other messages.
I don't know how to get out of here and be able to use the volumes on the again.
 
Try removing the fibercard and its children.

example:
rmdev -dl fsci0 -R
 
I already try that but as the hdiskpowerO is a child device of the fiber card it is not possible do delete it this way.
 
try removein gthe underlaying hdisk for the power device first
 
Here is my "rmemc.ksh" script I use to remove all EMC devices (we use one DMX3000, one DMX 800, one CX600 and two CX700's as well as a number of Sharks). This script works for all EMC storage. Just remember to VARYOFF your VG's FIRST. Then do this:

#!/bin/ksh

powermt remove hba=all # Remove all HBA's from powerpath

lsdev -Ctpower* -cdisk -Fname | xargs -n1 rmdev -dl #remove all power devices from ODM

lsdev -CtSYMM* -cdisk -Fname | xargs -n1 rmdev -dl #remove all Symmetrix devices (including DMX) from ODM

lsdev -CtCLArray* -cdisk -Fname | xargs -n1 rmdev -dl #remove all CLARiiON devices from ODM

rmdev -dl powerpath0 #Remove the powerpath device

rmdev -dl fcs0 -R #remove hba and all attached devices
rmdev -dl fcs1 -R
#rmdev -dl fcs2 -R
#rmdev -dl fcs3 -R
#rmdev -dl fcs4 -R


This should remove all of your LUNZ, which as explained to me by EMC are created as a placeholder the first time Clariion devices are attached to an AIX box. Apparently, the first time Clariion Luns are masked to an AIX box the first lun will not come in until a reboot is done, all successive luns will come in except for the first one. The way I've gotten around it without having to reboot is to do a "short cable pull" which can be either "Blocking" the hba port for about 5 seconds and then running cfgmgr again, or you can actually physically pull the f/c cable at the switch for about 5 seconds and running cfgmgr, and powermt config. Should clear you up.


There are 10 types of people in the world: those who understand binary, and those who don't.
 
Thanks guys for the answers.

In fact the main problem is I cannot delete the hdiskpower0, here is what append :
rmdev -dl hdiskpower0
Method error (/etc/methods/ucfgpowerdisk):
With no other messages. And the device is still there
I cannot rmdev the fiber cards because of the hdiskpower0.
It seems that the configuration of the device in the ODM is completely messed up.
When I do a powermt display dev=all things get even worst :
Pseudo name=hdisk8
CLARiiON ID=CK200052000302 [L2FRWMDBPRD2]
Logical device ID=60060160552A1500E2DE6C193BE3D911 [LUN 33]
state=alive; policy=BasicFailover; priority=0; queued-IOs=0
Owner: default=SP B, current=SP A
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
1 fscsi1 hdisk11 SP B0 active alive 0 0
1 fscsi1 hdisk4 SP A0 active alive 0 0

The pseudo device is not a hdiskpower but a hdisk !!!
I try to use the hdsk mention above but it fails with some error in the errorlog.

I feel like I am stuck in the twilight zone.
 
The problem is solved.
I had to desinstall and reinstall powerpath and now I get my volumes backup.
All the informations are correct after that.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top