I suspect I can add the backup MDC and configure it to access the
SAN via it's private port, but you don't get the choice for an Xsan
client. I'm therefore suspecting that these 'clients' will try & use
their public "Built-in Ethernet 1" port for Xsan traffic. Is this
likely to be the case? If so how should I prevent this?
Hm, I hit "Send" too soon -- I wanted to reply to this as well.
Basically, when you select a particular network interface on the MDC,
what that does is record the IP address of that network interface into
some configuration data on each client.
Now, because your SAN network is really private (right? :-), the IP
addresses it uses will not be reachable by your LAN network interface,
which means that the client will always choose the private network
path (i.e. "the private Ethernet interface") to reach the MDC (because
that's the only way to reach it)[*].
[*] Actually, even if it COULD reach the private IP of the MDC via
your LAN network interface, that would probably mean going through a
router, which means that path would have a higher "metric" for that
endpoint than the directly-connected path (the private Ethernet
interface). The OS X network stack will prefer a path with a smaller
metric, so the client would still pick the private Ethernet interface
for MDC communication.
In other words, regardless of what IP address is listed in the
computer list in Xsan Admin, the magic of IP routing ensures that the
clients will always do the right thing (which is why there is no
network interface picker for the clients).
HTH.
-- thorpej
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/email@hidden
