Comments for Jim March http://resume.jimmarch.com Senior Microsoft Systems Engineer Thu, 11 Mar 2010 13:55:52 +0000 http://wordpress.org/?v=2.7.1 hourly 1 Comment on iSCSI setup with Openfiler and Windows Server 2008 by landon http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-25 landon Sat, 29 Aug 2009 05:53:04 +0000 http://resume.jimmarch.com/?p=88#comment-25 I messed with openfiler for hours and couldn't get it to work...couldn't ever find any real helpful info out there either. Your video was PERFECT! Thanks for the great info! I messed with openfiler for hours and couldn’t get it to work…couldn’t ever find any real helpful info out there either. Your video was PERFECT! Thanks for the great info!

]]> Comment on Windows Storage Server 2008 RC Default Password by Admin Password für Storage Server 2008 « Denis´s Blog http://resume.jimmarch.com/2009/05/windows-storage-server-2008-rc-default-password/comment-page-1/#comment-24 Admin Password für Storage Server 2008 « Denis´s Blog Wed, 05 Aug 2009 19:13:38 +0000 http://resume.jimmarch.com/?p=152#comment-24 [...] Blog gefunden hat, wo das Password publiziert wurde. Hier erstmal der Link zu Denis seinem Blog und hier die Quelle des [...] [...] Blog gefunden hat, wo das Password publiziert wurde. Hier erstmal der Link zu Denis seinem Blog und hier die Quelle des [...]

]]> Comment on iSCSI setup with Openfiler and Windows Server 2008 by Jim http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-22 Jim Tue, 30 Jun 2009 16:44:32 +0000 http://resume.jimmarch.com/?p=88#comment-22 <a href="#comment-21" rel="nofollow">@tgopinath </a> Two nodes should not be sharing the same volume, UNLESS they are clustered. Which will not currently work in Windows 2008 Server, but should work in earlier versions of Windows. http://resume.jimmarch.com/2009/03/windows-server-2008-clustering-openfiler-iscsi-fail/ The reason is that iSCSI is block level storage, and unlike normal SMB file transfers, only 1 node can control the resource at any given time. This is handled by the cluster service in a clustered environment. On another note, Openfiler DOES support NFS and CIFS filesharing. So if you are looking to share FILES between nodes, that is something to look into. iSCSI can be used to share STORAGE between nodes, but that is for clustering purposes. @tgopinath
Two nodes should not be sharing the same volume, UNLESS they are clustered.

Which will not currently work in Windows 2008 Server, but should work in earlier versions of Windows.
http://resume.jimmarch.com/2009/03/windows-server-2008-clustering-openfiler-iscsi-fail/

The reason is that iSCSI is block level storage, and unlike normal SMB file transfers, only 1 node can control the resource at any given time. This is handled by the cluster service in a clustered environment.

On another note, Openfiler DOES support NFS and CIFS filesharing. So if you are looking to share FILES between nodes, that is something to look into. iSCSI can be used to share STORAGE between nodes, but that is for clustering purposes.

]]> Comment on iSCSI setup with Openfiler and Windows Server 2008 by tgopinath http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-21 tgopinath Mon, 29 Jun 2009 20:48:12 +0000 http://resume.jimmarch.com/?p=88#comment-21 Thank you very much for your responses. I was able to successfully connect two or more initiators to this openfiler share. let us say I create a folder/ file named "test" using the initiator share from machine 1. i'm unable to see the folder on accessing the share from initiator in Machine 2. Is it because the ext3 filesystem or the iscsi is not a shared type that can be accessed on two initiators at the same time? Thank you very much for your responses.
I was able to successfully connect two or more initiators to this openfiler share. let us say I create a folder/ file named “test” using the initiator share from machine 1. i’m unable to see the folder on accessing the share from initiator in Machine 2.
Is it because the ext3 filesystem or the iscsi is not a shared type that can be accessed on two initiators at the same time?

]]> Comment on iSCSI setup with Openfiler and Windows Server 2008 by Jim http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-20 Jim Fri, 26 Jun 2009 14:27:02 +0000 http://resume.jimmarch.com/?p=88#comment-20 <a href="#comment-18" rel="nofollow">@tgopinath </a> Multipath would only be required if you had multiple paths to your storage. i.e. Multiple nics on your machince connecting to a clustered Openfiler instance. As for the network ACL issue, you should really be running your iSCSI stuff on a seperate netowork from you regular traffic. So the NIC used to connect to the iSCSI box should be on a different subnet at a minimum, but prefereably on a dedicated switch. If both NICs are on the same subnet, the binding order in the Advanced Network properties determines which interface the traffic will originate from. @tgopinath
Multipath would only be required if you had multiple paths to your storage.
i.e. Multiple nics on your machince connecting to a clustered Openfiler instance.

As for the network ACL issue, you should really be running your iSCSI stuff on a seperate netowork from you regular traffic. So the NIC used to connect to the iSCSI box should be on a different subnet at a minimum, but prefereably on a dedicated switch.

If both NICs are on the same subnet, the binding order in the Advanced Network properties determines which interface the traffic will originate from.

]]> Comment on iSCSI setup with Openfiler and Windows Server 2008 by tgopinath http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-19 tgopinath Fri, 19 Jun 2009 16:38:31 +0000 http://resume.jimmarch.com/?p=88#comment-19 Jim, One more question, do you think having a 64 bit openfiler target and a 32bit openfilter target will make any difference? Thanks, Gopi. Jim,

One more question,
do you think having a 64 bit openfiler target and a 32bit openfilter target will make any difference?

Thanks,
Gopi.

]]> Comment on iSCSI setup with Openfiler and Windows Server 2008 by tgopinath http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-18 tgopinath Fri, 19 Jun 2009 16:29:30 +0000 http://resume.jimmarch.com/?p=88#comment-18 <a href="#comment-17" rel="nofollow">@Jim </a> Jim, Thank you so much for your inputs. I beleive the problem was with the Network ACL Authentication. My initiator machine has two NIC cards, so i added both the IP addresses and set it to "allow" in openfiler. Initiator was still unable to discover the target. Again i changed the ACL with a 24 bit subnet mask to allow all machines in the subnet and it worked!!!! Initiator was able to discover the target. I have no idea on why it did not work the first time. Also do you think "Multipath I/O" Feature is required on win 2008 server to establish iscsi connection? Thank you once again. Gopi. @Jim
Jim,

Thank you so much for your inputs.
I beleive the problem was with the Network ACL Authentication.
My initiator machine has two NIC cards, so i added both the IP addresses and set it to “allow” in openfiler. Initiator was still unable to discover the target.

Again i changed the ACL with a 24 bit subnet mask to allow all machines in the subnet and it worked!!!! Initiator was able to discover the target.

I have no idea on why it did not work the first time.
Also do you think “Multipath I/O” Feature is required on win 2008 server to establish iscsi connection?

Thank you once again.
Gopi.

]]> Comment on iSCSI setup with Openfiler and Windows Server 2008 by Jim http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-17 Jim Fri, 19 Jun 2009 14:08:50 +0000 http://resume.jimmarch.com/?p=88#comment-17 Are you able to discover your target with NO Authentication? I would start there and then add layers of security one at a time to see where your problem is occuring. Also, make sure that you use a different Username and Different Password for each portion of the CHAP Authentication. Are you able to discover your target with NO Authentication?

I would start there and then add layers of security one at a time to see where your problem is occuring.

Also, make sure that you use a different Username and Different Password for each portion of the CHAP Authentication.

]]> Comment on iSCSI setup with Openfiler and Windows Server 2008 by tgopinath http://resume.jimmarch.com/2009/03/iscsi-setup-with-openfiler-and-windows-server-2008/comment-page-1/#comment-16 tgopinath Thu, 18 Jun 2009 15:40:00 +0000 http://resume.jimmarch.com/?p=88#comment-16 Jim, Thank you very much for your efforts in doing this video. This is really helpful. I did exactly as you showed in the video but i am unable to discover my target from iscsi initiator...after adding my openfiler server information and CHAP authentication for discovery, when i go to the targets tab i do not see my target discovered....the list is empty. Any inputs in resolving this issue would be much appreciated... Jim,

Thank you very much for your efforts in doing this video. This is really helpful. I did exactly as you showed in the video but i am unable to discover my target from iscsi initiator…after adding my openfiler server information and CHAP authentication for discovery, when i go to the targets tab i do not see my target discovered….the list is empty.
Any inputs in resolving this issue would be much appreciated…

]]> Comment on Windows Storage Server 2008 RC Default Password by mauirixxx http://resume.jimmarch.com/2009/05/windows-storage-server-2008-rc-default-password/comment-page-1/#comment-15 mauirixxx Wed, 17 Jun 2009 01:46:53 +0000 http://resume.jimmarch.com/?p=152#comment-15 thanks for this post, I fired it up today in a VM environment and thought I had messed up the install somehow. Did you happen to find an explanation as to why this previously set? thanks for this post, I fired it up today in a VM environment and thought I had messed up the install somehow. Did you happen to find an explanation as to why this previously set?

]]>