What's new

Separate Networks (some redundancy), in ISP connection

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

PaulTech

New Around Here
Need help on setting up the following:

> Create two (2) networks (no more than 8 computers on each) each with access to the Internet but not to each other.
> Create a static route to a Network printer for use by both Networks.

Build redundancy below the ISP (Modem level) > Multiple routers and / or switches such that any one device failing does not interrupt the network.

What would you recommend keeping the hardware to a minimum? All the hardware will be new as the equipment is old and starting to fail.

(And, one of the routers that failed was a sub-router with the WAN port looped back to the LAN port on the router, why?)

I searched on the Internet and couldn't find any links that helped much. If you know some that would be wonderful too! :) Thanks for the help.
 
At this stage of the network, you don't need redundancy, you need a good warranty.

Many Dell PowerConnect switches come with a lifetime warranty. Make a 3524 or 3548 your site switch. Spend a whopping $21 and get a 3-year next business day warranty. Switch-level redundancy isn't really an access switch thing, but having a cold spare handy is. Best is having another switch of the same model, second best is having a cheap unmanaged switch, next best is keeping the old hardware on hand.

The difference in capabilities determines how your network will be set up. If you split up your network, then your spare hardware needs to support it. Complexity is a liability when it comes to resiliency.

I don't have any particular recommendations for the site gateway, but you should look at warranty service and number of VLANs supported. UTM capability may also matter to your organization. Fallback device can be a cheap SOHO router, provided the loss of capability/mandatory network reconfiguration is acceptable.

Printer should be managed by a server. Server has a presence on each VLAN; problem solved. Don't have a server? Your network isn't big enough to separate, much less worry about redundancy. Go with a flat network and harden your workstations instead.
 
Similar threads

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top