Actually, that's what I did.
My NAS has two nic. And my two mail server front ends also have two nic. So
in total - 6 nic.
------
| NAS |
------
1| |2
| |
------ | | ------
| MS1 | | | | MS2 |
------ | | ------
2| |1___| |__1| |2
| |
| |
Configured individual ip address for each of the nic at the NAS.
And then have the mail server front-ends each taking one nic to mount the
directoty. That, theoretically should double the network bandwidth, right?
NAS is using two 1Gig NIC cards. While the MS1/2 are using normal 100BaseT
NIC. Switch used is 10/100 type. I will be upgrading to Gig switch soon -
see if that solve the problem.
Regards,
/shaoming
-----Original Message-----
From: Bill Shupp [mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2003 10:38 AM
To: [EMAIL PROTECTED]
On Sunday, September 21, 2003, at 07:07 PM, John Johnson wrote:
> I would put a second NIC in the systems and put the NFS on it's own
> Network that way it will not cause as many problems. Use a fake
> 192.168.250 class for example on the second nics and have them on
> there own equipment that should deal with the network traffic problem.
>
> -John
This is exactly what I always do, and probably why I haven't seen the
problem described. Besides, I wouldn't want nfs traffic going over a
public network anyway in this context.
Regards,
Bill
