I believe that you were correct in your original email. You will need
to set you metadata controllers to host their service on the private
net. As long as all of the clients are then connected to that network
you should be all set.
If you are running firewalls on the servers you may need to open up
the private net. When initially setting up an Xsan 1.0 install long
ago I had some strange behavior. I never quite identified what ports
need to be open, but rather just always add a rule that allows all
traffic on the en1 interface. Others may have more details about what
exact ports are needed, if you want more granularity. I wasn't too
concerned since it is a dedicated private network.
Regards,
David
Information Technology, MSU Main Library
Developer, MSU Digital Evolution Laboratory
http://programerror.com ...iPhone 3G TX OK.
On Jul 3, 2009, at 7:51 PM, Andy Sykes <a.sykes@xxxxxxxxx> wrote:
(whoops, didn't hit reply to list)
Should be as simple as shutting down the SAN, plugging the cables
into the new switch, and starting the SAN back up.... i think.
Haven't actually done this myself, but I don't foresee any problems.
And just to be clear, all SAN clients must be on the MD network,
not just the MDCs.
So they'll automagically realise they're supposed to use the second
ethernet interface to talk to the SAN? Cos they're all connected
together through the primary interface to the other (public, rest of
the department) switch as well - how do they know the difference?
The private network won't have DHCP so I have to set interface
addresses.
Nothing that comes to mind... Were you doing any VLAN magic on the
old switch?
Nothing under my control - our whole subnet is VLAN'ed by the
university networks folks, but I can't see it having an effect.
Andy.
--
Andy Sykes
IT Support Officer
UCL Museums & Collections /
Media Services
a.sykes@xxxxxxxxx
Museums:-
Mon/Tues/Wed AM
Tel: 0207 679 7667 | x37667
Media:-
Wed PM/Thurs/Fri
Tel: 0207 679 9164 | x09164
--
"If computers get too powerful, we can organize them into a
committee. That will do them in."
--
On 4 Jul 2009, at 00:44, Peter Beninate wrote:
Hi all,
A previous administrator intended to set up a private metadata
network for our Xsan setup, but never got around to it. It was a
small setup back then, so it wasn't a big deal.
I'd like to sort this out, and have a dumb gigabit switch for the
purpose.
How do you go about switching the clients and MDCs over to a
private network? I take it that it's as simple as setting the
second ethernet interface on all the machines to have a static IP
in one of the private ranges, and then using Xsan Admin on each
machine to flip it over to using the second interface.
Should be as simple as shutting down the SAN, plugging the cables
into the new switch, and starting the SAN back up.... i think.
Haven't actually done this myself, but I don't foresee any problems.
And just to be clear, all SAN clients must be on the MD network,
not just the MDCs.
Is there anything I need to watch out for?
Nothing that comes to mind... Were you doing any VLAN magic on the
old switch?
I'm running Xsan 1.4.2.
Andy.
Peter Beninate
Systems Engineer
Mac Network Consulting
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (Xsan-Users@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/brysonda%40mac.com
This email sent to brysonda@xxxxxxx
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (Xsan-Users@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/maillists%40codeha.us
This email sent to maillists@xxxxxxxxx
