In article <bvtolp$82k$1$(E-Mail Removed)>,
paul <(E-Mail Removed)> wrote:
>Al Dykes wrote:
>> In article <bvtgu8$okn$1$(E-Mail Removed)>,
>> paul <(E-Mail Removed)> wrote:
>>
>>>Hi Cameron,
>>>
>>>Thanks for helping a newbie out. Would I be right in thinking that I
>>>don't need a managed swith a simple <30 machine renderfarm network...?
>>>
>>>The lo-end solution will still be many times fast than my present 100M hub?
>>>
>>>Regards,
>>>
>>>Paul
>>>
>>
>>
>> IMHO managed vs non-managed depends on how costly downtime (and your
>> time) is. If you need to solve a fault or performace problem ASAP I'd
>> go for a managed switch. It also gives you the flexibility to use a
>> sniffer on network traffic. It doesn't have to be fancy, I like a
>> built-into the switch that lets you see all sorts of statistics and
>> make settings from any browser.
>>
>
>Ohh- that all sounds too complex for me. Network sniffers and the such.
> I tempted to go for the unmanaged switch. I know my way around linux
>pretty well - but am I complete networking novice. I think I should
>keep it simple (and cheap) for starters...
>
>Many thanks for all your help,
YOu don't _have to_ use a sniffer, but if you get an unmanaged hub
you'll never have the option.
The procurve switches I'm familiar with were really easy to manage.
When it boots it gets an IP address. From any desktop on your LAN you
browse to http:\\nn.nn.nn.nn (whatever IP # dhcp assigns it.) (For
extra credit you can figure out how to tell your dhcp server how to
always assign a static IP address to the switch, based on the MAC
address.)
The first time your company's ISP connection seems to die you'll be
able to see if one of your desktops has one of the blaster viruses
that swamps the uplink bandwidth in 60 seconds, instead of having to
unjack each desktop at the patch panel and wait and see if the problem
clears up. Last year I had a client with unmanaged switches catch a
virus on one of his desktops and it cost him a couple thousand in my
time, plus lots of distruption, to find the offending PC.
--
Al Dykes
-----------
(E-Mail Removed)