Hi,
We have following problem.
When we try to connect to a existing LUN on the Netapp storage with SnapDrive 6.1.3R1 (using the connect disk function) we recieve following error:
------------------------- SnapDrive Operation Start ---------------------------------
Disk connect operation on server - SERVER10 failed for reason
A timeout of 120 secs elapsed while waiting for volume arrival notification from the operating system.
--------------------- The complete operation list is shown as follows -------------------
********************* Server Name: SERVER10*********************
1. Checking input parameters
2. Checking access control
3. Checking policies
4. Turning on space reservation
5. Connecting to the LUN
6. A timeout of 120 secs elapsed while waiting for volume arrival notification from the operating system.
------------------------------------------ Operation Done ---------------------------------------
In the Event Log we have EventID 116 for SnapDrive with this message:
Failed to connect to LUN. Failure in connecting to the LUN.
LUN Name = test_lun
Storage Path = /vol/server10/
Protocol Type = LUN
Storage System Name = sto02
Requested Mount Point = E
Assigned Mount Point = E
Error code : A timeout of 120 secs elapsed while waiting for volume arrival notification from the operating system.
On the storage, we see that the igroup is mapped but we receive no disk on the Windows system.
When we try to create a new LUN on the Netapp, this works without any problem. The LUN is mapped and visible in SnapDrive.
Enviroment:
DataONTAP 7.3.4
SnapDrive for Windows 6.3.1R1
Windows 2008 R2 SP1
VMWare vCenter Server 4.1.0
Someone an idea about is problem? Why we can not connect to an existing LUN.
We need to do it as we are doing some migrations from fysical to virtual and we want also to use SnapManager for Exchange and SQL
We have this problem on 2 different servers in the same enviroment.