Mantra:
It matters not how much bandwidth you have if you do not manage it proactively.
The following pages will lead you through the evolution of Bullard ISD's network and the monitoring tools that help manage bandwidth in the district to maximize access for educational purposes.
 Bullard ISD's network August 2002-- fiber backbone - multi-mode and single-mode; poor termination
-- flat network
-- approximately 350 computers
-- OS: Windows 95 & XP Home
-- Two servers
-- all print jobs were processed through a central server
-- DHCP handed out through the router
-- Two Class C IP ranges
-- To track IP to machine, there was no expiration date on IPs
-- Biggest "feature": Each network device was a 10/100 Intel hub
-- Not auto-sensing
-- If a 10MB node was connected, the switch had to be physically set to 10MB
 Network monitoring phase 1 August 2002-October 2002-- Sneaker net
-- Feature: Network meltdown 10-12 times a day; hubs had to be manually rebooted
-- Flat network + hubs = large collision domain
-- Fiber backbone grossly under-utilized
 Network design phase 1 October 2002-May 2003-- All XP Home to XP Pro
-- All replacement computers with W2000 or XP Pro
-- Active Directory Domain structure
-- DHCP server with two Class C IP subnets per campus
-- Segmented network: Layer 3 core switch
-- Replace all hubs with 10/100 auto sensing Layer 2 switches
| 
