HIT for VMware on vSphere 5 / Storage Capabilities view

Oops, uploaded the same screenshot twice, here the correct one (can't seem to edit my post)

Can't find it now. Maybe it was shown from EMC and just mentioned that HP and Dell have that too. But shouldn't it show SOMETHING rather than n/a ?

I meant would've fine if it 'does not' show the raid level :)

Thanks.

This was indeed the way I had the ISCSI initiator configured.

The steps I have taken now

1. Remove CHAP from Discovery settings

2. Add CHAP to General settings

3. Rescan adapter

4. Rescan storage view

5. Resync VASA Provider

6. Waited 10 minutes

7. Refreshed Storage View

= Storage Capability = n/a

8. Remove CHAP settings altogether

9. Remove IPs from ISCSI Initiator (Discovery / Targets)

10. Rescan adapter

11. Change access settings to be IP based rather than CHAP based

12. Re-add EQL IPs to initiator without any CHAP

13. Rescan adapter

14. Rescan / Refresh storage view

15. Resync VASA Provider

16. Wait 10 minutes

17. Refresh Storage View

= Storage Capability = n/a

18. Rebooted VASA appliance

19. Rebooted vCenter

= Storage Capability = n/a

Not sure what else to try to be honest.

Also opened an SR yesterday but so far no response yet

Hiya,

SR# 843406228

Right, forwarded the logs to Donald again with the fileexchanger login details.. Hope that helps :)

Already send those through, thanks Don :)

They have already been submitted when the ticket was submitted ...  (uploaded to https://fileexchanger.dell.com ), now I was requested to upload them to https://dtxdropbox.dell.com - does that mean 3rd line support doesn't have access to fileexchange and I need to re-upload ?

Just thought I update this with the solution .... We finally found out what the problem was. In our environment we allow access to the LUNs via IP. In our case the two vmkernel IPs participating in multipathing.

However, in addition to the LUN connection, the vcenter has to have access as well. In our case the vcenter was on the same network as the managment of the SAN. Adding the IP of the vcenter does not work, you have to allow the IQN of the software initiator access to the LUN as well.

One Re-scan later we finally got the informations displayed in vcenter :)

Thank you to all people from L1-3 and engineering who were involved in solving this :)

I am having the same problems getting VASA to work properly.  What iSCSI software initiator did you add to the Access tab on Volumes?  From your post it sounds like the Microsoft iSCSI Software Initiator name from the vCenter server.  So I installed it and it sees the Volumes but that didn't help get VASA working.  Or did you mean the vSphere iSCSI Software Adapter initiator names from your vSphere hosts?  I currently have my iSCSI network defined as having access to the volumes using a wildcard for the last octet....192.168.55.*....because I have 5 hosts with 4 NIC's each connected to the SAN.  Should I add the 5 IQN names from each of my hosts to each volume?

Thanks.

I am reporting back that changing my Volume ACL's to the IQN names from the hosts worked.

Thanks.

I will change all the Volumes to the IQN names from the hosts and report back.   At one point this SAN was only dedicated to the vSphere hosts and the iSCSI network was isolated from the rest of the network so using wildcards was OK.  It has since morphed to be routable to the whole network to get the volumues replicated to the DR site and SRM working.  Also the VM's inside of vSphere have access to the SAN using the MS iSCSI initiator in order to get the ASM working with Exchange and SQL.  I see your point.  Why do they even give the option of wildcards?

Just wanted to post back and let others know that this resolved the issue for me as well (converting volume ACL from IP to IQN). Dell/EQL support was asking for logs, glad it was a simple fix/workaround. Defnitely sounds like a firmware bug to me.