On 06/03/99 13:44:32 you wrote:
Hi Ya'll,
This is probably one of those questions for which there's no true correct answer, but I'm interested in peoples opinion.
Okay. Just for the record, my opinion is based on a balance of administrative ease and flexibility with the need for high performance.
- In setting up a NetApp, is it better to use one big/wide
connection (say gigabit ethernet) as opposed to a bunch of narrow connections (say, 4 100mbps ethernet in a etherchannel). (Note that for this discussion I'm ignoring the redundancy in a etherchannel.)
One big connection, say Gigabit, is ideal for your primary data backbone. You can still use other, smaller connections for other smaller networks.
- On a Unix system that will be doing heavy NFS work to a NetApp,
is it better to use separate mounts on separate but smaller ethernet connections (100mbps ethernet), or, run all mounts through one wide ethernet connection (gigabit ethernet)?
Again I would recommend running all the mounts from a particular machine to one filer through one particular large network connection. This is going to be administratively advantageous in the long run. Even on a network with lots of networks for data access with lots of different purposes (and I have no objection with such a configuration), I'd still recommend keeping all of the mounts from a given dataless client over the same network to the filer(s), unless there is some very specific reason not to (like dedicated remote backup networks).
Bruce
This is probably one of those questions for which there's no true correct answer, but I'm interested in peoples opinion.
....snip...
One big connection, say Gigabit, is ideal for your primary data backbone. You can still use other, smaller connections for other smaller networks.
One comment which failed to appear in all the responses thus far, is that of 'redundancy'. If you plan to setup a pair of servers in an H/A environment, you should seriously consider two network interfaces.
- Christoph
On Sun, 6 Jun 1999, Christoph Doerbeck A242369 wrote:
One comment which failed to appear in all the responses thus far, is that of 'redundancy'. If you plan to setup a pair of servers in an H/A environment, you should seriously consider two network interfaces.
Not only that, but you should consider at least two data paths to your systems. That means duplicating the hubs, switches, and routers or at least ensuring that they have redundant power and that failure of one card/port on these does not affect another card/port. The same goes for backplanes of this net hardware; they should have multiple independent data paths. This is the second part (meaning) of trunking.
Tom