We just upgraded to ontap 8 on our FAS3240, and are now using vfilers.
I ran in a problem today when I created a new sql server, and wanted to use some volumes on the fas3240.
I created the volumes in the oncommand system mananger.
In putty, I changed the vfiler context to the vfiler where the volumes are placed, and created an igroup to the iscsi initiator name on the sql server.
Now I would like to establish a connection with snapdrive using iSCSI management on the sql server, but the vfiler interface with the iSCSI on the fas3240 are not showing up , only the default interface on the fas3240.
I would like to establish a connection to the vfiler with the iSCSI protocol.
What configuration am I missing ? Do I have to add the igroup to some port ?
When I try to create a disk I'm notified that there is no iSCSI connection to the specified system, so I can see the qtree I've created.
Help would be very much appreciated 🙂
Solved! See The Solution
I've added the igroup in the correct vfiler context. I can see the other igroups created for the other sql servers using storage on the vfiler.
The httpd must be enabled because the other sql servers are up and running with access to the fas3240 volumes.
Can snapdrive create a new small trst drive in the vFiler? It will create an igroup And Lun. If other servers can see Luns in the vFiler it must be network or something on this one specific host.
No when I create a disk with snapdrive I'm notified by the wizard that I have to create an new iSCSI connection to the storage system. So I can't create a disk.
I can ping the vfiler iSCSI interface, but it is not showing up when I try to create a new iSCSI connection.
There is no access list on the vfiler, but it looks like i'm missing the membership of a group or something like that.
vf_ISCSI105@fasdc02> igroup show
sv-sqls-007 (iSCSI) (ostype: windows):
iqn.1991-05.com.microsoft:sv-sqls-007.systematicgroup.local (logged in on: ig_10gportA-105)
viaRPC.iqn.1991-05.com.microsoft:sv-sqls-001.systematicgroup.local (iSCSI) (ostype: windows):
iqn.1991-05.com.microsoft:sv-sqls-001.systematicgroup.local (logged in on: ig_10gportA-105)
viaRPC.iqn.1991-05.com.microsoft:sv-sqls-002.systematicgroup.local (iSCSI) (ostype: windows):
iqn.1991-05.com.microsoft:sv-sqls-002.systematicgroup.local (logged in on: ig_10gportA-105)
viaRPC.iqn.1991-05.com.microsoft:sv-sqls-003.systematicgroup.local (iSCSI) (ostype: windows):
iqn.1991-05.com.microsoft:sv-sqls-003.systematicgroup.local (logged in on: ig_10gportA-105)
viaRPC.iqn.1991-05.com.microsoft:sv-sqls-004.systematicgroup.local (iSCSI) (ostype: windows):
iqn.1991-05.com.microsoft:sv-sqls-004.systematicgroup.local (logged in on: ig_10gportA-105)
It is the igroup sv-sqls-007 I got a problem connecting to from the sql server