> So consider doing the disk configuration on the console.
...unless you're using SnapDrive.
> -----Original Message-----
> From: Michel Geldenhuys [mailto:michel@geldenhuys.com]
> Sent: Thursday, January 08, 2004 10:58 PM
> To: toasters(a)mathworks.com
> Subject: RE: iSCSI HOWTO question
>
> Hi,
>
> Just beware that is you do the stuff through a Terminal
> Server connection, you might not see the new disk devices in
> disk administrator.
> So consider doing the disk configuration on the console.
>
> Kind regards,
> Michel Geldenhuys
>
> > -----Original Message-----
> > From: owner-toasters(a)mathworks.com
> [mailto:owner-toasters@mathworks.com]
> > On Behalf Of Haber, David J.
> > Sent: jeudi 8 janvier 2004 18:43
> > To: toasters(a)mathworks.com
> > Subject: RE: iSCSI HOWTO question
> >
> > Once the Lun is created and properly set up on the Windows (2000?)
> > server, you should be able to do a scan of your drives in
> disk manager
> > and it will show up. Then format and your good to go.
> >
> > -----Original Message-----
> > From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com]
> > Sent: Thursday, January 08, 2004 11:59 AM
> > To: toasters
> > Subject: iSCSI HOWTO question
> >
> > I am new to the SAN environment, and most especially to
> the iSCSI
> > way of doing things. I have the iSCSI protocol enabled on my filer,
> and
> > I have the Microsoft iSCSI initiator downloaded and installed on my
> PC.
> > From the filer, I have created a couple LUNs on my filer, I have
> > created igroups, mapped the LUNs to the igroups, set the
> create_ucode
> > option to on, and started the iSCSI service. On the
> Windows system, I
> > have added the target portal, logged on, and I can see an active
> > session. I think I have all the basics under control.
> > What I can't seem to figure out is how the LUNs now show up as
> being
> > somehow connected to my Windows computer. I'm sure I've missed
> > something, but I can't figure out what. I've tried reading
> the "ONTAP
> > SysAdmin Block Access Management Guide" and working through the
> examples
> > step by step, still to no avail.
> > Some details:
> >
> > Host (initiator): Windows 2000
> > ONTAP version 6.4.3
> > toaster> iscsi show adapter
> > Adapter: iswta
> > Slot: N/A
> > Description: NetApp Software Implementation
> > Status: Online
> > Target Portal Groups:
> > portal group 1: inet 192.168.1.3 port 3260
> >
> > toaster> igroup show
> > windows-igroup0 (iSCSI) (ostype: windows):
> > iqn.1992-08.com.netapp:sn.123456789
> >
> > toaster> lun show -v
> > /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w,
> online,
> > mapped)
> > Comment: "iSCSI test lun0"
> > Serial#: HPlwFYo6bJoZ
> > Share: none
> > Space Reservation: enabled
> > Multiprotocol Type: windows
> > Maps: windows-igroup0=0
> > /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w,
> online,
> > mapped)
> > Comment: "iSCSI test lun1"
> > Serial#: HPlwFYo6bQDV
> > Share: none
> > Space Reservation: enabled
> > Multiprotocol Type: windows
> > Maps: windows-igroup0=1
> >
> > toaster> iswt interface show
> > Interface e0 enabled
> >
> > toaster> iscsi nodename
> > iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789
> >
> >
> >
> > Any help would be greatly appreciated.
> >
> > Thanks,
> >
> > Geoff Hardin
> > geoff.hardin(a)dalsemi.com
> >
> >
> >
> >
> >
> > Confidentiality Notice:
> > This message, and any attachments, may contain information that is
> > confidential, privileged, and/or protected from disclosure
> under state
> and
> > federal laws that deal with the privacy and security of medical
> > information. If you received this message in error or through
> > inappropriate means, please reply to this message to notify
> the Sender
> > that the message was received by you in error, and then permanently
> delete
> > this message from all storage media, without forwarding or
> retaining a
> > copy.
>
>