|
Posted by Trendkill on July 21, 2008, 5:53 pm
If you were Registered and logged in, you could reply and use other advanced thread options > There is no drawback to having too many subnets when routing with a 6500!=
!!!
> Layer 2 switching is not any faster than layer 3 switching and smaller
> subnets means a smaller broadcast domain. =A0If you are running windows, =
than
> smaller broadcast domains are good because windows workstations send out
> quite a bit of broadcast traffic.
>
> I never ever, ever use subnets bigger than a /24, and most subnets usuall=
y
> have an average of only about 60 workstations. =A0On my network, each and
> every wiring closet has its own subnet, plus a voice subnet if it is a Vo=
IP
> is being used.
>
>
>
.
> >> we have a 400 node network running on multple 3750 stackable switches
> >> at access layer and a 6509 at the core. We are talking about
> >> subnetting the network. 8 different subnets have been proposed. I
> >> agree that vlan subnetting has it's advantages(i.e reducing broadcast
> >> domains). But i am wondering at what point it's too much. Or what is
> >> the drawback of having too many subnets and would 8 be considered that
> >> on a 400 node network. Thanks
>
> >It all depends on the nature of the traffic. =A0If these are all user
> >stations, I have seen many times where a /22 is used (1000+
> >addresses), and 4-500 are active during regular usage. =A0If its a mixed
> >use vlan with real-time traffic (such as video or voice, which would
> >not be good architecture anyway), then subnetting to smaller subnets
> >makes more sense. =A0In short, 8 segments for 50 nodes each is
> >overkill. =A0I would personally not do smaller than /25, and /24 in most
> >cases, unless of course the network is a retail or small site network
> >which will never get larger than that space, or there are special vlan
> >or traffic requirements. =A0When you are talking modern gig speed
> >networks, broadcast traffic is minimal unless you have an issue (ie
> >bad worm or virus), or a network design problem.
>
> The speed of the interface has nothing to do with the amount of broadcast
> traffic, that is a function of the number of devices in the broadcast
> domain. =A0Each and every broadcast packet is sent to, and processed by, =
every
> device in the broadcast domain.
I agree, but in the days of 10/half interfaces, broadcast could easily
overwhelm a link or subnet. Today, it would take one hell of a
broadcast storm to overwhelm a modern backbone or LAN link. While I
don't disagree with your subnet solution (can't really go wrong here,
and have to design to your requirements), my experience is in two
global Fortune 50 companies, and when you have dozens of datacenters,
subnetting like that adds up quick on wasted addresses. That being
said, I would not go larger than a /22. And, always subnet real time
traffic if possible, particularly VoIP since the requirements/
segmentation work nicely.
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map