I am a bit new to this so please be gentle.
(Physical NICs must be on the same subnet as the iSCSI storage system they connect to)
/Rubeck
SAN connectivity is meant to be a layer 2 activity.
Adding a route on this network is not supported.
The overhead of going through that extra hop is something you don't want, even if you can make it work.
You really don't need an IP range from your datacenter, you should use something isolated for iSCSI.
So the CoLo is telling me this is they way they set up SAN connectivity for all of their customers. Is it safe to assume that they are incorrect (would not be the first time) or at least not using ESXi?
(Physical NICs must be on the same subnet as the iSCSI storage system they connect to)
/Rubeck
Whilst other iSCSI products may support this configuration where ESXi doesn't - it is certainly not a best practise with any product.
Kim Rubeck wrote:
(Physical NICs must be on the same subnet as the iSCSI storage system they connect to)
/Rubeck
Is it that VMWare will just reject any responses from outside of it's subnet regardless of whether or not the TCP/IP connection is properly set up?
Thanks all... I am back in the process of wrangling with the data center. Fun...
