Chapter 8 - Network Analysis and Design Flashcards
Network Architecture Components
- 7 components max:
– LAN (Ch. 7)
– Building BBN (Ch. 8)
– Campus BBN (Ch.8)
– Data center (special purpose LANs covered in Ch. 7)
– Enterprise edge - WAN/MAN (Ch. 9)
- Internet access (Ch. 10)
- e-commerce edge (Ch. 7)
Core layer not needed when:
Network limited to one building
Core layer and distribution layer combined:
Two-tier model can be suitable for small to medium-size campus networks
The traditional approach: NDLC (Similar to SDLC(Software Development Life Cycle)
– Planning + Analysis + Design + Implementation + Maintenance
– Limitations:
* (Precise) planning is time consuming and not necessary: Networks need to be upgraded / replaced more frequently than IS, some networking technology change rapidly and network traffic grows rapidly
* Maintenance: Responsibility of network manager not network designer
The building Block Process
Uses standard components to simplify design and management
Has three phases:
– Needs analysis
– Technology design
– Cost assessment
To reach the final design:
– Perform Needs Analysis & Technology Design phases
– Complete initial cost assessment
* Over budget? Refine the needs analysis THEN cycle through all three phases again AND when the design meets requirements and fits budget send RFP to vendor(s)
* Within budget? Send RFP to vendor(s)
Needs analysis
Purpose: Analyze network users’ needs and define the requirements of network applications
Baselining Task:
Measure / record features of existing network over periods of time to create metrics of current operations to compare new design against.
Questions: Which metrics should be created? What if this a newly founded organization?
Network architecture components Task:
Break the network into access, distribution and possibly core layers, MAN/WAN, Internet access, e-Commerce Edge and data center.
Application systems Task:
Identify applications used in /required for the new network
Network users Task:
Identify who uses which applications, how they access them (i.e., using wired or
wireless LANs), their location, effect on level of traffic
Needs categorization:
- Assess traffic in each segment: Typical (100 Mbps) v/s high (or multimedia, 1000Mbps)
- Organize network applications requirements: Mandatory v/s desirable v/s wish list
Deliverable: The logical network design
– Describes what network elements will be needed to meet organization’s needs
– Shows categorized applications, layers and traffic
Design Clients and Servers:
Application architecture (C/S vs Host-based), type of C/S architecture, type of “clients” and “servers”, their configuration
- Determine hardware and software requirements for workstations and servers used on network
- Selecting appropriate operating systems, applications, and hardware components…
Design circuits:
- Decide on LAN technology (Ethernet or Ethernet-compatible), topologies (switches and APs), form of BBNs (switches, routers, VLAN switches) and type of cabling (TP vs Fiber)
- Do capacity planning i.e, decide on nominal data rates (100Mbps, 1Gbps etc.). This requires assessing circuit loading i.e., the amount of data transferred across a circuit currently and in the future in terms of average traffic vs peak traffic (and designing for peak traffic is ideal!).
Traffic typically increases more than anticipated (turnpike effect) and precision may not be a major concern due to the “stair step” nature of nominal data rates available for Ethernet (100Mbps, 1Gbps) BUT cost increases SHARPLY after 1Gbps
Should network designers plan for excess capacity? Upgrading costs 50-80% more than designing for higher capacity the first time but cost increases sharply after 1Gbps
Modeling (and documenting):
Designers create diagrams of existing or proposed networks