HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

c7000, bl495c, VC-FC, QMH2462 HBA connection to Hitachi, no LUN visible.

 
tormod
Occasional Visitor

c7000, bl495c, VC-FC, QMH2462 HBA connection to Hitachi, no LUN visible.

Hi! I have a problem connecting QMH2462 to HDS 9990. SAN switch, Brocade 4400, zoning is OK, works to SUN 6140. And my zoning must be OK to HDS, because when I present disk from Hitachi I see the WWN name for the blade. But I can't see any LUNs from ESX 3.5 update4, or even from SANsurfer/fastutil... I have tried presenting existing disks, created new disks, different host mode for groups.. 19 netware, vmware, LUN0 LUN1...) Firmware VC 2.10, VC-FC 1.32. Firmware QMH2462 , 4.04.06. BIOS 2.08 Anyone know if this QMH2462 works with Hitachi. (We have SUN HDS 9990, but I guess HP XP storage will be the same.) [Updated on 5/29/2009 1:30 AM] I got this card connected to the HDS9990 by changeing FC SAN Settings in Virtual Connect Manager. It works if I change to Use the static, factory-default WWN Addresses. But the idea buying Virtual Connect is to simplyfy HW replacement. So why is the HDS 9990 not compatible with Virtual Connect assigned WWN Addresses? Anyone know why this is not working? [Updated on 6/10/2009 3:46 AM] Problem solved. Created a SUN support Case. SUN technician changed a setting on the HDS9990 controller and all started to work.
1 REPLY
jin tang
Occasional Visitor

c7000, bl495c, VC-FC, QMH2462 HBA connection to Hitachi, no LUN visible.

Hi, Just managed to connect bl460c (G1) with QMH2462 to HDS storage via Brocade 4GB switch (FOS 5.3.18), through 4GB VC module. It worked in either mode(WWPN from VC or WWPN from Qlogic). We had a strange problem initially, the uplink ports of VC-FC can connect to SAN fabric, not the blades (we even tried Emulex and Qlogic HBA). Eventually, by luck, we replaced the VC-FC pair in the enclosure, it works perfectly. We got local 1st & 2nd level HP support, plus the local VC consultants of HP, none of them could help us. Still, we have no idea why that pair of VC-FC does work. It appears there is very little troubleshooting tools and approaches HP has for VC-FC at this stage. All of the firmware (HBA, OA, VC-Enet, VC-FC and Blades) have been patched to the latest version (firmware CD 8.4).