The LAN parties we've done around 100 peeps...we used 3x Cisco Catalyst switches for our backbone.
Central switch has the servers fed to it, as well as about 1/4 of the crowd (or a little bit more).
Fiber-giga uplinks from the central Cisco to 2x more Catalysts...each located in opposite diagonal corners of the convention room we rented. Each of those split up the remaining crowd.
Didn't bother with VLans at this size. One of the gaming servers was running DHCP for the LAN. In the "posted rules of the LAN" put on the forums, and lanparty.com ad we ran, we encouraged people to pre-configure their network settings before arriving. No NetBEUI, no IPX, and TCP set to obtain auto. NIC and TCP stack in good functional order. If you're been to LAN parties in the past, you know the guys who have IT knowledge always get stuck fixing some persons junker computer trying to get their cheap 19 dollar NIC running right. I'd rather be playing!
Computers encouraged to be virus/worm free. Network shares discouraged (I've seen too many peoples computers get hosed by pranksters at LAN parties due to having wide open shares on their C$.)
Try to avoid using home made patch cables. There is always someone who insists they know how to make cables, they whip up a couple of long runs to uplink switches 'n stuff, and you spend hours trying to figure out where all the packet loss is coming from on a certain switch. Save yourself the hassle and wasted time, purchase good cables ahead of time, or get some made up and FULLY TESTED with a quality Fluke test or something good like that ahead of time. Don't waste time with some 19 dollar "link light" tester, a link light test means jack squat when it comes to performance.
You'll want the servers running a real server OS, not a desktop operating system. Desktop OSs are optimized for up to 10 concurrent connections, after that, they start to loose efficiency. Same goes for the hardware, especially the NIC. There's a big difference between a desktop NIC, and a true server grade NIC, when it comes to performance with many concurrent connections. Trust me...you can take 2x identicle computers as far as CPU, mobo, and RAM. Install a desktop OS and desktop NIC on one of them, install a true server OS and true server grade NIC on the other. Have 75 peeps connect to each playing the same game. You'll see a difference in performance.![]()
www.blackviper.com is a good source for "tweaking and leaning out" your servers. Getting them to run lean and mean.
Make sure your servers are windows updated, and have a quality, low system impact antivirus running on them. (NOD32 *free 30 day trial*, AVG *free edition*, Symantec Corporate Edition*must have licenses*) Because surer than sh|t there will be some infected computers brought to the LAN, you don't need your server going belly up a few hours into the gaming because it wasn't protected correctly.
Check power requirements ahead of time. As our LAN parties grew, we blew a few circuits from time to time. Have your servers and switches on APCC battey backups. Spread the load well in the room. Even our more recent one at a convention room at a brand new Marriot, we dropped the circuits a few times....maintenance ran extension cords into the room, going out down the hall, to help split up the load.
Encourage headphones. Nothing worse than a few people who insist on showing off the wattage of their Klippies or Logitechs at a LAN party.![]()
Bookmarks