I don't know if this is a "best practice", but it's how I'm currently
doing things.
I use three NICs on the SunRay server box. The first is attached to my
regular (public) VLAN. The second is attached to a private VLAN just
for the SunRays. The third is attached to my Windows Terminal Server
box. This seems to segment the traffic nicely. There is no impact on
my public VLAN from traffic either from the SunRays or the WTS box, and
vice versa. Most new server hardware comes with a plethora of NICs
these days. I figured I might as well use them. My network
infrastructure also allows for easy segmentation like this.
Seth
Samuel Olampi wrote:
Hi all,
my question is very simple, yet I could not find a definite answer
so far.
What do you consider as the best practice when setting up SRSS in a
multi-NIC gigabit server ?
Take for instance the trusty V240 which has 4 Gb NICs.
And I mean "best" as in "most efficient" - "best performance" - "least
payload" - "best practice", in short ;)
A) using only one NICE -> the same NIC for SRSS traffic and non-SRSS
traffic (NFS & such)
In this case, SRSS would be configured with "utadm -A bge0"
B) using first NIC (bge0) for NFS & co and
third NIC (for instance-bge2) for SRSS-only traffic
In this scenario, I'd set up two separate port-based LANs
on my switches and configure SRSS with "utadm -a bge2"
C) same as B but don't bother with VLAN
D) two physical networks, separated one from another
bge0 on first switch that'll do NFS&co,
bge2 on second switch that'll do SRSS only
and I mean a recent instance of SRSS - SRSS4.1 over S10-0805 ?
Thanks !
--
Seth Galitzer
Systems Coordinator
Computing and Information Sciences
Kansas State University
[EMAIL PROTECTED]
785-532-7790
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
