RSA enVision Enhanced Availability integration with NetApps Filer
I have had an issue when trying to setup enVision EA with NetApps Filer - FAS2020.
It failed when at step 8 of the lsconfigurationwizard. The lsconfigurationwizard log doesn't tell much on what's the problem.
Does this have anything to do with ISCSI support on Windows 2003 Enterprise Server?
Has anyone successfully implemented this kind of environment?
When I look at the Microsoft website, it mentioned that Windows 2003 Enterprise Server doesn't have ISCSI driver by default.
However the ISCSI initiator can be downloaded from Microsoft website for free.
I am not sure whether enVision version 3.5.1 that comes with hardened Windows 2003 Enterprise Server actually has ISCSI initiator build-in.
Your advice is greatly appreciated.
Thankyou and best regards,
As far as I understand the Step #8 of the lsconfigurationwizard first looks for the nie-oe.dat files on the connected appliances. This file contains the information about the OS, hardware, IP address, Role that the appliance will be playing in the site and a lot more info. It then proceeds to locate the NAS which is in your case 'NetApps Filer - FAS2020'. The IP address by which it tries to locate the NAS device is 10.203.2.101. This is default, it cannot be changed. So first make sure that if it is a shared NAS, you have created a CIFS share with this IP. After this the wizard joins the appliances to the cluster, and it completes.
If you are still facing this problem, I would like to see the log file for STEP #8.
One most important thing that you should note is that ISCSI should be configured on NAS. Now it uses port 3260, so make sure this port is not used by any other service.
Okay, I managed to make it works.
During the re-installation, I did make sure that system clock on each LS appliances are in sync, by the setting the clock on each of the appliances. And make sure you are creating LS role, and DS role with their own IP addresses.
Make sure that IQNs in NAS can be seen by the appliances.
I've reviewed this thread with one of the RSA professional services guys, and I wanted to post a notification to all:
Enhanced Availability (EA) configuration is not supported by RSA unless deployed and configured by professional services. Please contact your account rep or reseller for more details.
I am having a problem with the time stamp on the files on our NAS. They are roughly 30 minutes into the FUTURE! I have verified all timing on all the servers and NAS are synced. What could be going on here???????
Also stuck at Step 8 in the lsconfiguration wizzard. I checked further and realized this is caused by the Q drive (Quorum) not available in this CA. While the iSCSI managed to connect succesfully to NAS IP (I can see the connection log in the EMC Celerra), somehow the quorum drive (Q) becomes an unread-able and unknown drive on my CA (under drive management of the computer management).
Since the cluster addition of this CA will fail (no resource on CA to host the quorum because Q drive is not up), Step 8 will fail.
Anybody had this experience, how did you resolve this?