iSCSI question

[maximillianrg]

I have an old Drobo Pro that connects to my Plex Server via iSCSI. This is a direct connection meaning one end of the cat5e cable goes into the drobo and other into the NIC on the server and this has worked great for years. I also have a T-Link 48-port switch.

Drobo says if I unplug the end of the cable going into the server and plug it into the switch AND I run a new cable from the iscsi configured NIC on the server to another open port on the switch this is a supported configuration and will work.

Before doing this I have 2 questions.

1. Will I need to change any settings in the Drobo or iscsi setting on the server which is running Windows Server 2012 R2.

2. Does anyone see any issues with this change in configuration?

thank you

Max

 

[Heracles]

Hey Maxim,

Not that I see problem, but neither do I see any benefit... Usually, you keep iSCSI physically separate to ensure max performance, max stability and insulate it completely because there is not much security on most of the iSCSI components.

 

[maximillianrg]

than you. at present my server and drobo are in a 32u cabinet but I may rebuild the server and move it to a different room hence the question. thank you again.

 

[eshwayri]

I have an old Drobo Pro that connects to my Plex Server via iSCSI. This is a direct connection meaning one end of the cat5e cable goes into the drobo and other into the NIC on the server and this has worked great for years. I also have a T-Link 48-port switch.

Drobo says if I unplug the end of the cable going into the server and plug it into the switch AND I run a new cable from the iscsi configured NIC on the server to another open port on the switch this is a supported configuration and will work.

Before doing this I have 2 questions.

1. Will I need to change any settings in the Drobo or iscsi setting on the server which is running Windows Server 2012 R2.

2. Does anyone see any issues with this change in configuration?

thank you

Max

iSCSI uses standard unicast TCP. You can connect and route it as any other IP protocol. I've x-connected it, routed it, and trunked it over VLANs. I could probably even send it over a VPN if i wanted to. A x-connect might provide you the fastest speed, but you lose to the ability to use it's LUNs on multiple computers. The best feature of iSCSI is it's ability to create LUNs that can be shared between multiple computers like VMWare ESXi datastores or a shared Windows Cluster resource. There is a whole wide world beyond x-connects for a single server.