Meher_Pophali
asked on
LUN's are not visible on host and host is not discovered in HP P2000 G3
Hi
In my HP P2000 G3 a particular Blade is not getting discovered, I am able to add that host manually but then i couldn't see presented LUN's on that host if go back in P2000 and click on that host it says (Discovered no and Host Type undefined) however for other Hosts/Blades it says (Discovered yes and Host Type FC) My setup is as follows
C-7000 Blade Enclosure
BL460c G6 Blades (qty 4 and all are having Emulex LPe-1205 8gb Dual Port HBA)
Blade San Switches in C-7000 Enclosure
HP P2000 G3 Dual controller
Additional Info:
1. I am able to see P2000 G3 is connected and discovered on that host ( cat /proc/scsi/scsi)
2. On Board administrator shows HBA is present in that Blade and also shows details of the HBA like wwn, connected on port no 4 etc.
3. Zoning is not configured.
4. Other Blades are discovered and Luns are visible on hosts.
5. I am using RHEL 5.5 x86_64
6. Proliant Support Pack is installed on the Blade.
In my HP P2000 G3 a particular Blade is not getting discovered, I am able to add that host manually but then i couldn't see presented LUN's on that host if go back in P2000 and click on that host it says (Discovered no and Host Type undefined) however for other Hosts/Blades it says (Discovered yes and Host Type FC) My setup is as follows
C-7000 Blade Enclosure
BL460c G6 Blades (qty 4 and all are having Emulex LPe-1205 8gb Dual Port HBA)
Blade San Switches in C-7000 Enclosure
HP P2000 G3 Dual controller
Additional Info:
1. I am able to see P2000 G3 is connected and discovered on that host ( cat /proc/scsi/scsi)
2. On Board administrator shows HBA is present in that Blade and also shows details of the HBA like wwn, connected on port no 4 etc.
3. Zoning is not configured.
4. Other Blades are discovered and Luns are visible on hosts.
5. I am using RHEL 5.5 x86_64
6. Proliant Support Pack is installed on the Blade.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Hi Philip,
Thanks for your reply
BIOS and firmwares versions were same but in an attempt to solve this issue i have updated BIOS/firmwares to latest version before posting here.
Thanks for your reply
BIOS and firmwares versions were same but in an attempt to solve this issue i have updated BIOS/firmwares to latest version before posting here.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Solved the problem by restoring P2000 to factory defaults!
Just make sure that after restoring to defaults, that the settings are put back the way they were. Were they documented?
Check any connections and reseat the problematic blade to make sure that there is nothing going on with them as well.
Thanks for that. :)
Philip
Check any connections and reseat the problematic blade to make sure that there is nothing going on with them as well.
Thanks for that. :)
Philip
ASKER
It was a new installation and hence the configuration was for testing only. Anyways thanks for your comments.
Philip