• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Search network equipments for network design
 

Search network equipments for network design

on

  • 1,670 views

 

Statistics

Views

Total Views
1,670
Views on SlideShare
1,670
Embed Views
0

Actions

Likes
1
Downloads
10
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Search network equipments for network design Search network equipments for network design Presentation Transcript

    • Tutorial of Network Design and Practice to Search Network Devices
      • Learn network design principles from this presentation and network design chapter.
      • According to requirements in your coursework 1, search network devices from the Internet.
      • It takes 5 weeks to design a network and submit your design in the end of week 5.
      • Some websites for manufactures are listed in following slide.
    • Some of Network Devices Manufacturers Cisco: http://www.cisco.com/ 3Com: http://www.3com.com/ Huawei: http://www.huawei.com/ Star-Net: http://www.star-net.cn/en/index.asp D-link: http://www.dlink.co.uk Nortel: http://products.nortel.com/go/product_content.jsp?segId=0&parId=0&prod_id=8548
    • Cisco Small Business Smart Switch SLM2008 £93.4 Interfaces/Connections : 7 x network - Ethernet 10Base-T/100Base-TX/1000Base-T - RJ-45 1 x network / power - Ethernet 10Base-T/100Base-TX/1000Base-T - RJ-45 Data Transfer Rate : 1 Gbps MAC Address Table Size : 8K entries Remote Management Protocol : HTTP Features : Layer 2 switching, auto-sensing per device, auto-negotiation, VLAN support, auto-uplink (auto MDI/MDI-X), IGMP snooping, port mirroring, store and forward, Broadcast Storm Control, firmware upgradable, Quality of Service (QoS) Dimensions (WxDxH) / Weight : 13 cm x 13 cm x 2.9 cm / 420 g Manufacturer Warranty : 5 years warranty
    • Network Design
      • Design goals
      • Design choices
      • Design approaches
      • The design process
      • Capacity planning
    • Design goals
      • Good designs should:
        • Deliver services requested by users
        • Deliver acceptable throughput and response times
        • Be within budget and maximise cost efficiencies
        • Be reliable
        • Be expandable without major redesign
        • Be manageable by maintenance and support staff
        • Be well documented
    • Design Choices
      • Balance of distribution
      • Level of transparency
      • Security
      • Connectivity technology
    • Design approaches
      • Two typical methods
        • Traditional analytic design
        • Building block approach
      • Both use a similar iterative approach
    • The traditional design process
    • Design Stages - Agree requirements
      • Engage end users
      • Translate requirements
        • Business objectives –> technical specification
      • Phasing the requirements
        • Right level of detail at each design stage
      • Designing the requirements
    • Design Stages - Designing the requirements
      • Aim for completeness
      • Prioritise with a hierarchical system such as
          • [M] - Mandatory
          • [H] – Highly desirable
          • [D] - Desirable
          • [N] - Note
    • Design Stages - Assessing requirements
      • Consider all aspects
        • E.g. support & maintenance, depreciation, commissioning costs, project management fees, hardware & software upgrade costs, backup devices costs, consultancy charges – over the lifetime of the network
      • Weighted matrix multipliers
        • M=100, H=10, D=1, N=0
        • Produce scores and rank suppliers
    • Design Stages - Information gathering
      • Need to find details of user behaviour, application use and location information for example:
        • User: location, numbers, services used, typical access
        • Sites: number, location, constraints on traffic (security, political or cost)
        • Servers and services: location, level of distribution
        • WAN/backbone predicted link traffic
        • Protocol support: bridged, routed or switched – Gateways needed?
        • Legacy support: equipment, protocols or services
        • Specific availability needs? 24-hour/backup links etc
        • Five-year plan – changes to population or business requirements
        • Budgetary constraints
        • Greenfield or existing site
      • Information is refined and leads to a requirements database and capacity plan
    • Design Stages - Site constraints
      • Greenfield or
        • Greenfield sites have no legacy constraints but…
        • It is difficult to determine the real network loads and stresses
        • Needs more detail of application use and underlying protocols
        • Could use simulation to predict performance
      • Existing site
        • Limited access
        • Access to live network could be restricted but…
        • Bottlenecks more obvious
        • Can use traffic/network analysis tools
    • Design Stages - Planning
      • Uses information on
        • Hosts, users, services, and their internetworking needs
      • Iterative process of
        • Conceptual design
        • Analysis
        • Refinement
      • Involving
        • Brainstorming, design reviews, modelling tools
      • Leading to final draft design
    • Design Stages - Design specification
      • Detailed document of the design
        • Acts as a benchmark for design changes
        • Final design choices and changes need justification and documenting
        • Should include change history to aid maintenance
        • Used for the implementation
    • Design Stages - Implementation
      • Needs a project plan to include
        • Phased introduction of new technology
        • Educating the users (what to expect)
        • Pilot installation (test for possible problems)
        • Acceptance testing (to prove performance meets requirements)
        • Deployment (provide support on going live and provide fallback position)
    • Connectivity options
      • Technology choices
        • LANs (Ethernet, Token ring, ATM)
        • MANs (FDDI, SMDS, ATM, SONET/SDH)
        • WANS (Frame relay, ATM, ISDN, X.25, PDCs, Satellite)
        • Wireless (802.11, Bluetooth, GPRS, GSM)
        • Dial-up lines
        • Serial links
      LAN(Local area network, MAN (metropolitan area network), WAN (wide area network )
    • Connectivity option determinants
      • Packet, cell or circuit switching
      • Wired or wireless
      • Distance
      • Performance
      • Bandwidth
      • Quality of Service
      • Availability
    • Media and bandwidth choices
    • Capacity Planning - Outline
      • Concerned with
        • User response times
        • Application behaviour and performance characteristics
        • Network utilisation
      • Needed to
        • Minimise downtime
        • Maximise service to customers
        • Minimise costs of procurement and maintenance
        • Avoid unscheduled maintenance or re-design
        • Avoid costly upgrades and bad publicity
    • Capacity Planning - Stages
      • Form a discussion group (involve users etc.)
      • Quantify user behaviour
      • Quantify Application behaviour
      • Baseline existing network
        • Traffic profiles
      • Make traffic projections
      • Summarize input data for design process
      • Assess other data (environmental, location restrictions, deployment constraints etc)
    • Capacity Planning – Step 1
      • Form a discussion group (involve users etc.)
        • Needs wide representation
        • Users, network managers, application groups
      • To elicit
        • What uses find acceptable and unacceptable
        • Map of services and details of user behaviour
      • Quantify items using
        • User and service sizing data
        • Snapshots from data capture and network management tools
        • Traces of key services using protocol analysers
        • Pilot network implementation
    • Capacity Planning – Step 2
      • Quantify user behaviour
        • Need to know population and and location of users
        • Summary of major user groups
        • Application use by user group
        • Site location data (country, grid ref., town, postcode, telephone exchange)
        • Planned changes
    • Capacity Planning – Step 3
      • Quantify Application behaviour
        • Need to identify
          • Applications that could affect performance
          • Location and performance of servers and clients
          • Key constraints on performance (response times, buffer sizes etc
        • And define
          • Application behaviour under fault conditions (lost data)
          • Addressing mechanisms( broad/multi/unicast)
          • Packet characteristics (frame sizes and direction)
          • Routable and non-routable services (IP, NETBIOS)
      • Undefined applications allow choice of distribution balance
    • Capacity Planning – Step 4
      • Baseline existing network
        • Baselining – a behavioural profile of the network obtained from
          • Packet traces, transaction rates, event logs and stats
          • Router ACLs(access control list ), firewall rulebases
          • Inventory of hardware and software revisions
        • Traffic profiles -Capture data for a stable working network with details of
          • bandwidth utilization by packet type and protocol
          • Packet/frame size distribution
          • Background error rates
          • Collision rates
        • Various tools can be used
          • Network and protocol analysers, SNMP data, RMON probes, OS tools, traceroute, ping etc
    • Capacity Planning – Step 5
      • Make traffic projections using some, or all of:
        • Hand calculation
        • Commercial analytical tools to project network utilisation
        • Simulation tools (most detail)
    • Capacity Planning – Step 6
      • Summarize input data for design process
        • Budget
        • Database of sites, user populations,
        • List of key applications and their behaviour
        • Traffic matrix
      • Need to consider
        • Static or dynamic bandwidth allocation
        • Max. Delay and Max. hops between sites
        • Resilience, Availability, degree of meshing
        • Design constraints and trade-off
          • (e.g. delay v cost)
    • The building-block design process (an alternative)
    • Summary
      • Good design
        • Is an iterative process of continuous refinement
        • Is logical and consistent
        • Should deliver acceptable performance and cost metrics (trade-off)
        • Is more than choosing the technology!