""Scott Roberts"" wrote in message news:[EMAIL PROTECTED] > I guess I'm the only one with the problem of that many then. I'll take your > words for it that it works OK, but I still keep thinking back to that one > study (don't recall its name), and can't help but think effiecency would go > by some noticeable degree. anybody can through switch and hubs around, > we're supposed to do it right, not just "to get by". > > I mean if 700 is ok, then why not 1000? at some point you have to agree > there is going to be a performance hit. hasn't any manufacturor thought to > retest this performance issue with the newer equipment?
to bring a bit of real world into this, I am working with a couple of large organizations, for projects that involve good sized campus switched networks. Several of my coworkers are involved in similar projects. We are finding places where there may well be a couple thousand ddevices in a single broadcast domain. The IT folks in these orgs do know that sometimes there are problems. However, most also say that in general, they don't have a great deal of problems. an apocryhal story, but a couple of years back I interviewed with a large bank in this area. They were looking for detailed sniffer experience ( which I did not have ) because, they said, they had as many as 1000 stations on a segment, and whenever there were network performance issues, they sniffed like crazy, swapped out any nic that they considered "over the edge" and in general did everything they could to limit things that might adversely effect the ability of their users to do what they had to do, much of which was to get wire ( money ) transfers completed quickly and accurately. I worked in brokerage a few years. In that business, broadcast IS the business. About 200 stations in a shared hub domain was too much. Moving folks to 24 stations on a hub, with the hubs connected to switch ports, was quite effective. in terms of reduction of performance complaints. I would never do it this way these days. As for the manufacturers, all they care about is selling equipment, so of course they are going to promote thresholds which support the selling of more equipment. > > scott > > ""Priscilla Oppenheimer"" wrote in message > news:[EMAIL PROTECTED] > > Great answer Chuck. It sounds like you figured out his/her basic needs, > > though we would need more detail to provide a detailed design, of course, > > and payment for design services. :-) Well, actually your idea of asking a > > vendor to do an RFP might mean a free design (that would be biased toward > > the vendor, of course, but still a good start.) > > > > I'm not in disagreement that today 700 nodes in one broadcast domain might > > be OK. In other words, I would probably recommend no VLANs as a start. > VLANs > > complicate matters. If the network admins are somewhat new to networking, > > they should avoid VLANs to start. > > > > The reason 700 nodes in one broadcast domain could work is because NICs > and > > CPUs are really not bothered by broadcasts like they were in the > mid-1990s. > > They are much fast, have better buffers, etc. Some would argue they never > > were affected as much as Cisco claimed! > > > > I help out once in a while on a city-wide school network with that many > > nodes in one broadcast domain. It has all the risk factors: > > > > Lots of AppleTalk traffic > > Lots of Novell traffic > > Lots of NetBIOS traffic > > Lots of IP traffic > > Ancient PCs with slow CPUs > > > > There are no performance issues. > > > > Priscilla > > > > The Long and Winding Road wrote: > > > > > > ""ferry ferry"" wrote in message > > > news:[EMAIL PROTECTED] > > > > I need a scheme of network.It need seven hundreds > > > points.please give me > > > some > > > > advice on how to design it.It include that how to select > > > network > > > > product,product configuration.They are seted in a building.It > > > have twenty > > > > layers. > > > > > > > > > Let's see if I understand you correctly. > > > > > > A company is located in a multistory building. There are 700 > > > users spread > > > out among 20 floors. So on average there are 35 users per floor. > > > > > > I'm going to assume a single data center with your servers and > > > internet > > > connection. > > > > > > Got fiber running from your data center to the various floors? > > > How is this > > > structured? how far from the dataccenter to each of the floors? > > > > > > the answer to this will help determine if you use a collapsed > > > backbone or if > > > you connect your switches in series. > > > > > > do you have groups of users who should logically be separated > > > from > > > eachother. Some companies like their payroll department to be > > > on a separate > > > network from other departments, for example. are there some > > > services that > > > need to be separated and unavailable to some users? > > > > > > These days, 700 uses, particularly in a switched environment, > > > is not such a > > > large braodcast domain ( stop grinding your teeth, Priscilla > > > ;-> ) but > > > still, you might just want to separated out logical groups into > > > vlans. or > > > maybe do it by grouping a couple of florrs together into vlans. > > > > > > my knee jerk thought, not knowing too much about the > > > particulars, is > > > determine your port counts per floor, determine connectivity - > > > fiber runs > > > between closets, and where those runs terminate. if it's > > > copper, you got > > > troubles :-> > > > > > > determine your logical / vlan structures. who needs to see what > > > and when. > > > > > > Then go through the provisioning process. > > > > > > Don't be afraid to call in a couple of vendors to help you. ask > > > for > > > proposals. If you have a vendor who works closely with you and > > > wants to help > > > educate you, that's your guy ( or gal, for the politically > > > correct ) > > > > > > hope this helps you get started. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=64758&t=64422 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
