I have used eLab Navigator and it seems that version 4.51 of Powerpath supports the latest RHEL4 Update 4, even with the latest kernel updates, at least in our case, so should I install 4.51 or wait untill the 5 is released?
i have been running into the same problem. i can not figure out if the version of powerpath is based upon the redhat update or the kernel version running on the machine. we have a redhat 4 AS u4 loaded on a machine that is still using the kernel from the original redhat install cd's. we can't seem to make anything work. some of the release notices seem to suggest that they assume that when you load the lasted redhat update, you should load the latest kernel and the version of powerpath and other software listed for that update is based upon the latest kernel. does anybody have any idea how to figure if the software (powerpath, etc.) is based upon the update number or the kernel version? please help if you can! i've been fighting this for two weeks now and can not get a good answer from anyone. THANKS!
1) failed installation text exactly as it appears 2) kernel identification (I think its uname -r and the /etc/redhat-release file) 3) powerpath version
kernel 2.6.9-5ELsmp release Red Hat Enterprise Linus AS release 4 (Nahant Update 4) naviagent 6.24.0.6.13-1 powerpath 4.4.0-343.rhel.i386
this is no error message as such. everything appears to load right, but when the agent is restarted, it just hangs. it never finishes starting. the system says the process is running but it is not. it also will not let us clean up all the rpm's. we have had to reload the OS several times.
we have also tried 6.24.1.5.0-1 and i believe a version of 4.5. the hba is a qlogic 2460 and with this we have tried v8.01.00-3 and a v8.00 variety. it always hangs the same way. that is why i am thinking that keeping the low kernel version with the higher updates may be confusing the rpm's we are trying to load.
Thanks! i looked thru the reference guide. based on what i saw, i guess i can assume that what really matters in determining the needed software levels is not the actual upgrade level but the level of the kernel that you are running on that upgrade level. is this a valid statement? i have been fighting this so long, i would appreciate a short explaination if possible.
JasonBailey
147 Posts
0
January 29th, 2007 13:00
Availablity mentioned in other thread: http://forums.emc.com/forums/thread.jspa?threadID=47682&tstart=0
ESI2
1 Message
0
January 30th, 2007 01:00
Thanks in advance
Message was edited by:
ESI
JasonBailey
147 Posts
0
February 8th, 2007 22:00
Documented in eLab Navigator "PDFs and Guides tab" -> "Infrastructure Software" -> "Powerpath"
https://elabnavigator.emc.com/emcpubs/elab/esm/pdf/EMC_PowerPath.pdf
alfman
3 Posts
0
April 7th, 2007 13:00
JasonBailey
147 Posts
0
April 7th, 2007 16:00
1) failed installation text exactly as it appears
2) kernel identification (I think its uname -r and the /etc/redhat-release file)
3) powerpath version
Thanks
alfman
3 Posts
0
April 8th, 2007 11:00
release Red Hat Enterprise Linus AS release 4 (Nahant Update 4)
naviagent 6.24.0.6.13-1
powerpath 4.4.0-343.rhel.i386
this is no error message as such. everything appears to load right, but when the agent is restarted, it just hangs. it never finishes starting. the system says the process is running but it is not. it also will not let us clean up all the rpm's. we have had to reload the OS several times.
we have also tried 6.24.1.5.0-1 and i believe a version of 4.5. the hba is a qlogic 2460 and with this we have tried v8.01.00-3 and a v8.00 variety. it always hangs the same way. that is why i am thinking that keeping the low kernel version with the higher updates may be confusing the rpm's we are trying to load.
JasonBailey
147 Posts
0
April 8th, 2007 16:00
So you should open a case with EMC Support, as your configuration is supported.
alfman
3 Posts
0
April 8th, 2007 17:00
i looked thru the reference guide. based on what i saw, i guess i can assume that what really matters in determining the needed software levels is not the actual upgrade level but the level of the kernel that you are running on that upgrade level. is this a valid statement? i have been fighting this so long, i would appreciate a short explaination if possible.
thanks again!!!
JasonBailey
147 Posts
0
April 9th, 2007 06:00