Unsolved
1 Message
0
628
Can't connect/mount to other volumes (Dell Equal Logic SAN Headquarters)
Investigating an older server/disk array. The server has Dell EqualLogic SAN Headquarters. In Group Manager I can see 5 out of 7 volumes as online/active. I can see the different disk usage stats for the various volumes as well.
When I do an auto-config via ISCSI initiator (Windows 2008 R2), it only mounted 1 of the 5 to the server.
When I do "iscsicli.exe ListTargets" it only shows two entries one related to the volume that mounted and another with "-vss-control".
Where are all the other targets/volumes?
I'm not seeing any obvious differences in the settings between the different volumes in Group Manager that would cause the others not to mount.
Any ideas/suggestions are most welcome. Not super familiar with Dell Equal Logic SAN HQ.
DellEMCSupport
Moderator
Moderator
•
631 Posts
0
January 12th, 2023 19:00
Hello, I would suggest that you install this. (Please note this requires an account.)
Dell EqualLogic Host Integration Tools
dwilliam62
3 Apprentice
3 Apprentice
•
1.5K Posts
0
January 13th, 2023 18:00
Hello,
A couple of terms to help decode what's going on.
SANHQ, is an application used to monitor EQL groups. Providing detailed statitics.
The Group Manager is the actualy management application.
The vss-control-volume is used by Microsoft Volume Shadow Servce to create and manage snapshots from the application layer. It's optional and not required for normal IO.
Each volume will have an "Acess control List" associated with it. This will specify which servers have access to individual volumes. It's important that more than one server does NOT connect to a volume unless a clustering filesystem is in place. Otherwise, data corruption WILL occur.
So the server you are using only has acces to the volumes you current see.
If you go to the group manager and select that volume you can see, under the access tab you will see what access policy is being used. For example it could list the IPs on the NICs on that server used for iSCSI traffic. It could use the iSCSI initiator name, or use a CHAP username and password. It could even use a combination of all three!
If you are SURE that no other servers will be accessing those other volumes. You can ADD in the same access info on the ohter volumes you want to connect to. When you do a refresh in the MS iSCSI initiator client those other volumes should show up. You can then connect to them. I would do it one at a time. If those volumes were part of a cluster then they will NOT show up on a server not running the MS clustering service. I.e. if the volume were used for MS Hyper-V for example, or SQL cluster, etc..
There are videos on YouTube on how to connect to volumes, set access control, etc... If you search for Equallogic you will find them.
Regards,
Don
#iworkfordell
Origin3k
4 Operator
4 Operator
•
1.9K Posts
0
January 14th, 2023 00:00
Each EQL volume have its own set of ACLs which controls which Server have access to a given volume or not. So check the ACLs and keep an eye to the monitoring log within GrouMgr.
Regards,
J.B
Praveen.Singh
3 Apprentice
3 Apprentice
•
472 Posts
0
March 11th, 2023 22:00
Suggested to check ACLs