1 / 28

Presented by Doug Stopper

Technical Vitality Seminar. Network Design II: Building A Solution (A Site Example). Presented by Doug Stopper. Purpose. To build a network solution based on the requirements gathering process (presented last week).

kaori
Télécharger la présentation

Presented by Doug Stopper

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Vitality Seminar Network Design II: Building A Solution (A Site Example) Presented by Doug Stopper

  2. Purpose • To build a network solution based on the requirements gathering process (presented last week). • To use the requirements to choose the right technologies and architectures. • To understand that there needs to be an equal balance of cost and performance when building the network architecture

  3. A Site Example • To use the LM Owego site as an example network architecture. • Parameters • Large Scale LAN upgrade • Focus on emerging technologies • Support a 5000 Node network • Provide an acceptable level of performance • Stay within cost restraints

  4. Things to Consider for the Design • Rapid Evolution of Network and Computing technology • Must remain Competitive/Productive • Need support for 5000+ nodes • Desktop technology requires higher bandwidth requirements (IPTv, Streaming Web Technologies, Email w/ attachments, Backups, etc…..

  5. Defining Requirements for LM Owego • What is the geographical coverage needed? • Local Area Network: Span one or more buildings on the campus • Approximately 45 wiring closets (LAN rooms) spread over 15 buildings • Closets Vary per building (1-9 closets)

  6. Defining Requirements for LM Owego • What is the type of traffic? • Voice • Separate Infrastructure – Stable for now • Data • All types: Mission critical, normal, non-critical • Video • IPTV based only, and Streaming Video on Network • IPTV system is tuned for LAN based traffic

  7. Defining Requirements for LM Owego • How many nodes on your network? • Need support for a minimum of 4000 nodes • Needs to be scalable to support more nodes in the future • In the form of Users & Servers

  8. Defining Requirements for LM Owego • How Many Servers need to be supported? • Servers require higher bandwidth, reliability, and redundancy • Approximately 95 Unix Servers (AFS, CAD, etc…) • Approximately 35 Intel Servers (Print Servers, File Servers, Exchange Servers) • Several OS/2 Servers (Legacy Server Environment) • Equates to High Traffic Requirements

  9. Defining Requirements for LM Owego • What facility limitations are present? • Can the walls be fitted with cables • Are there LAN rooms • Is there a backbone to a centralized area • Already an existing cable infrastructure (Token- Ring cable) • Use this existing infrastructure – can support up to 100 Mbps within distance limitations

  10. Defining Requirements for LM Owego • Can the walls be fitted with cables • Are there LAN rooms • Is there a backbone to a centralized area • LAN closets Exist • Core area Exists (just the space) • No Network Mgmnt. Area. – Needs to be created • Already an older type fiber backbone from closet to core • Older technology, Fiber Paths not labeled/documented well

  11. Defining Requirements for LM Owego • What is the term of the network? • For how long will it be in place? • Permanent configuration • No foreseeable termination of network services • Must be scalable to more nodes and newer technologies

  12. Defining Requirements for LM Owego • How secure does the network need to be? • Need a high level of network security • Firewalls (protect intranet) • Authentication servers (verify users) • Intrusion detection (prevent network penetration) • Virtual Private Networks (secure remote users)

  13. Defining Requirements for LM Owego • What services are needed? • Email Services • Domain Name Service (DNS) • IP Address management (DHCP) • LAN resource services • Backup Services • Unix Services (AFS, MCAD, etc…) • Printer Services

  14. Defining Requirements for LM Owego • What LAN access methods are available in the geographic region? • Current – Token Ring • Problems – Insufficient Bandwidth, legacy technology, more expensive • Solution – Switched Ethernet, 10/100 access • dedicated bandwidth to desktop • reasonable $$ to implement technology • Standardized and supported

  15. Defining Requirements for LM Owego • What are the cost restraints? • Must fit the budget to supply the following: • Fit-up for all PC’s Network Interface Cards • LAN Closet Switches • Any new supporting fiber backbone needed • Any other New Cabling • Core Equipment • Network Management equipment • Power backup systems • Labor – Install, configure Test • Maintenance on equipment • Any other recurring costs

  16. Approaching a Network Design • Examine all gathered statistics • Previous Slides • Educate yourself on traffic requirements • Choose the networking technologies that will best suit your needs • IP, Ethernet, ATM, MM Fiber, Cat V cable, etc…

  17. Review the LAN Architecture • Switched Ethernet Environment to Desktop • Each user has a DEDICATED 10Mbps link • New NICS/Cables/Closet Switches • Switches Scalable to 100Mbps • Switches Scalable to more users • Switches Scalable to new technologies • New ATM fiber Backbone • New Campus Fiber Backbone Installed • Runs from every LAN closet to the 101a raised floor • LAN Switch-to-Core access method ATM (OC3-155Mbps)

  18. The LAN Architecture • New Network Core (101a - Raised Floor) • Routers and ATM switching equipment • Completely fiber switched environment • Scalable to more traffic / LAN rooms • Fiber Patch termination Area • Rack System • Development area (1 of each device)

  19. The LAN Architecture • New Network Operations Center • house all management operations • Network Management Software (HP OPENVIEW) • Sniffer Software (to closely examine traffic problems) • DHCP Server – Hand out IP Addresses • Other Various monitoring tools and systems • Measure utilization, configurations, inventory, etc…

  20. Pricing the LAN Architecture • Telecom Project Cost Evaluation • Total Purchase Cost: For all HW and SW (only a fraction of the total cost) • Labor Costs: To Plan, Install, and Maintain (Outweigh product purchase cost)

  21. Pricing the LAN Architecture • Telecom Project Cost Evaluation • If the costs meet the budget IMPLENENT!!!

  22. Pricing the LAN Architecture • Telecom Project Cost Evaluation • If the costs don’t meet the budget: • Determine where to make cuts • Network Management • Cabling Infrastructure • Security • Brand Names • Outsource or not – for implementing • Re-evaluate, and make decisions

  23. Solutions - Wiring Closets

  24. Solutions - Network Core See Netscape

  25. Solutions - Network Core(Setup Table & Fiber Patches)

  26. Solutions - Network Operations Center

  27. The Future of the LMFS Network • Scalable to new networking technologies • Scalable to new business applications • Scalable to more users • Extended management capabilities • Remain competitive in the IT arena • Maintain high productivity

  28. Thank You

More Related