Re: Problem with SDD upgrade on AIX 5.3 server using ESS 2105 SAN
- From: djdavies <dandavies@xxxxxxxxxxxxx>
- Date: 19 Apr 2007 07:37:13 -0700
On 19 Apr, 09:55, djdavies <dandav...@xxxxxxxxxxxxx> wrote:
On 18 Apr, 23:30, 0xDEADABE <n...@xxxxxxxxxxx> wrote:
djdavies wrote:
Hi all,
First post and its a right pain in the a$$ one lol
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg
setup on our ESS 2105 SAN.
Once i had done this i've then set about upgrading the SDD software on
the AIX box since it had devices.sdd.43.rte installed and needed
devices.sdd.53.rte.
will doing this i have then also upgraded the ibm2105.rte host
attachment script software from 32.6.100.18 up to 32.6.100.25
also: devices.fcp.disk.ibm2105.rte from 32.6.100.18 to 32.6.100.29
and devices.scsi.disk.ibm2105.rte from 32.6.100.18 to 32.6.100.29
i followed the pdf's supplied by IBM regarding the upgrade process -
unmounting filesystems on SAN, varyoff vg, rmdev on the vpaths and
hdisks, running the upgrades, then cfgmgr the devices back.
However while i can get the vg online and mount the filesystems, view
files etc etc the actual setup of the vpaths seems to have changed.
here is the lsvpcfg from before the upgrade of the SDD software:
vpath0 (Avail ) 10D23296 = hdisk5 (Avail pv ) hdisk68 (Avail
pv )
vpath1 (Avail ) 20D23296 = hdisk6 (Avail pv ) hdisk72 (Avail
pv )
vpath2 (Avail ) 30D23296 = hdisk7 (Avail pv ) hdisk76 (Avail
pv )
vpath3 (Avail pv crm_train_vg) 00623296 = hdisk63 (Avail ) hdisk88
(Avail )
vpath4 (Avail pv crm_train_vg) 00723296 = hdisk64 (Avail ) hdisk89
(Avail )
vpath5 (Avail pv crm_train_vg) 00823296 = hdisk65 (Avail ) hdisk90
(Avail )
vpath6 (Avail pv crm_train_vg) 10723296 = hdisk66 (Avail ) hdisk91
(Avail )
vpath7 (Avail pv crm_train_vg) 10823296 = hdisk67 (Avail ) hdisk92
(Avail )
vpath8 (Avail pv crm_train_vg) 20723296 = hdisk69 (Avail ) hdisk93
(Avail )
vpath9 (Avail pv crm_train_vg) 20823296 = hdisk70 (Avail ) hdisk94
(Avail )
vpath10 (Avail pv crm_train_vg) 20923296 = hdisk71 (Avail ) hdisk95
(Avail )
vpath11 (Avail pv crm_train_vg) 30723296 = hdisk73 (Avail ) hdisk96
(Avail )
vpath12 (Avail pv crm_train_vg) 30823296 = hdisk74 (Avail ) hdisk97
(Avail )
vpath13 (Avail pv crm_train_vg) 30923296 = hdisk75 (Avail ) hdisk98
(Avail )
and here is the output afterwards
vpath0 (Def ) 00623296 = hdisk2 (Avail pv crm_train_vg) hdisk16 (Avail
pv crm_tr
ain_vg)
vpath1 (Def ) 00723296 = hdisk3 (Avail pv crm_train_vg) hdisk17 (Avail
pv crm_tr
ain_vg)
vpath2 (Def ) 00823296 = hdisk4 (Avail pv crm_train_vg) hdisk18 (Avail
pv crm_tr
ain_vg)
vpath3 (Def ) 10723296 = hdisk5 (Avail pv crm_train_vg) hdisk19 (Avail
pv crm_tr
ain_vg)
vpath4 (Def ) 10823296 = hdisk6 (Avail pv crm_train_vg) hdisk20 (Avail
pv crm_tr
ain_vg)
vpath5 (Def ) 10D23296 = hdisk7 (Avail pv ) hdisk21 (Avail
pv )
vpath6 (Def ) 20723296 = hdisk8 (Avail pv crm_train_vg) hdisk22 (Avail
pv crm_tr
ain_vg)
vpath7 (Def ) 20823296 = hdisk9 (Avail pv crm_train_vg) hdisk23 (Avail
pv crm_tr
ain_vg)
vpath8 (Def ) 20923296 = hdisk10 (Avail pv crm_train_vg) hdisk24
(Avail pv crm_t
rain_vg)
vpath9 (Def ) 20D23296 = hdisk11 (Avail pv ) hdisk25 (Avail
pv )
vpath10 (Def ) 30723296 = hdisk12 (Avail pv crm_train_vg) hdisk26
(Avail pv crm_
train_vg)
vpath11 (Def ) 30823296 = hdisk13 (Avail pv crm_train_vg) hdisk27
(Avail pv crm_
train_vg)
vpath12 (Def ) 30923296 = hdisk14 (Avail pv crm_train_vg) hdisk28
(Avail pv crm_
train_vg)
vpath13 (Def ) 30D23296 = hdisk15 (Avail pv ) hdisk29 (Avail pv )
I cannot seem to move the vpaths from DEF to AVAIL. while everything
still seems to work its worrying me a bit. Also all the hdisk numbers
have changed although im still viewing the same data when i go into
the vg.
I've tried rebooting, redoing the SDD config by deleting the vpaths/
hdisks and going again. I've also tried removing and add data paths
from the device menu in smit.
Finally the last wierd problem is that within smit > devices > data
path devices
if i try to select "display data path device adapter status" it shows
"no device file found" thats really worrying me ! lol....
Anyway if anyone can help or offer some ideas i'd really welcome them.
It might be a test box but i need to be careful with the SAN and i
want to know how to fix this.
Thanks in advance
D
Do your varyoffvg's and rmdev's again, but also do a "rmdev -dl dpo".
You shouldn't need to reboot, just do another cfgmgr after that and
hopefully that clears it up. Also, before the cfgmgr, do either an
"lsdev|grep hdisk" or "lscfg|grep hdisk" and see if you have any latent
hdisk definitions in your ODM. You will need to rmdev them as well.
These will show up in either of the above outputs (I can't remember
which) but won't show up with "lspv".
If you don't want to put up with the vpath/hdisk mess, take a look at
SDDPCM. I went with it in my last go around of upgrades and it has
proven to be very beneficial. Everything shows up as a single hdisk
instead of 8 hdisks per vpath (or whatever). The commands distributed
with the driver give you the details of the paths.
Hope this helps,
SG- Hide quoted text -
- Show quoted text -
cheers for the info SG,
I didnt realise that SDDPCM did that. Are there any trade offs with
using the SDDPCM rather than just SDD?? I'm not even that sure of the
difference between the two at the moment , will do some research now.
Will try what you recommend and see.
I think my main problem is that the datapath query adapter returns
"device file not found" which i cannot understand as the FCS and FSCSI
adapters are available and as far as i can tell working in SMIT- Hide quoted text -
- Show quoted text -
sorted it now.
basically i managed to find version 1.6.0.0 of the devices.sdd.53.rte
software on ibm site - i was using the newest which was 1.6.2.0.
anyway same procedure - removed everything unistalled 1.6.2.0 then
installed 1.6.0.0, cfgmgr -vl fcsX on the fcs adapters and then
cfallvpath and "wooooo" it works .
all vpaths are now avail not just def. and the datapath query adapter
command displays the correct data.
a simple version conflict then - although im not sure why yet. hope
this can help someone else in the future
.
- References:
- Problem with SDD upgrade on AIX 5.3 server using ESS 2105 SAN
- From: djdavies
- Re: Problem with SDD upgrade on AIX 5.3 server using ESS 2105 SAN
- From: 0xDEADABE
- Re: Problem with SDD upgrade on AIX 5.3 server using ESS 2105 SAN
- From: djdavies
- Problem with SDD upgrade on AIX 5.3 server using ESS 2105 SAN
- Prev by Date: botched migration from 5.1 to 5.3 on a p615
- Next by Date: Newbie - User add failure
- Previous by thread: Re: Problem with SDD upgrade on AIX 5.3 server using ESS 2105 SAN
- Next by thread: Does P510 , P550 and P560 support AIX OS V 5.2 ML 4
- Index(es):
Relevant Pages
|
|