Network Design and Performance

Lecture 1

Agenda
Walk though Syllabus
Introduction to material to be
covered
Introduction to a simulation tool
OPNET IT Guru/ Modeler

Assessment components and grading

Phase I - Analyzing Business Goals
and Constraints
2

Course Overview
Learn to identify customer needs
Learn to assess business goals
Map to network goals

Study/understand/analyze performance of a
given network
Design a network / upgrade as per needs
Combine WAN technologies with LAN technologies
Learn to evaluate the security goals of the network
and to integrate these goals in the design (after /
before?)
This course is NOT about learning different
network protocols or using OPNET.
3

Class Details
Date and Time:
Every M, W, F - 9-10 AM
Instructor:
Name: Nirmala Shenoy
Office: E0033
Office Hours:
Thursday 12-1
Tuesday 10.30 11.30

Email:

Nirmala.Shenoy@snu.edu.in

Teaching Assistant: Mr. Narendra Shukla

4

Communication
Email through SNU account
Check Blackboard for announcements,
assignments, quizzes, templates etc.

Course Description
This course will examine the design and
performance of networks.
Students will learn to design networks based on
identified needs and analyze the performance of
that network.
The designs include site, campus, and enterprise.
WAN technologies will be combined with LAN
technologies in the design of enterprise networks.
Students will learn to assess the business goals and
their application to the network goals. Students will
learn to evaluate the security goals of the network
and to integrate these goals in the design.

Laptop / Electronic Devices Usage

All Electronic items including mobile phones/tablets will not be allowed with
the students during lectures and labs. Students bringing them due to
unavoidable circumstances will have to keep it switched off in their bag and
the bag should be kept at a designated place in the room, and certainly not
with the students. Allowing laptops will be at the discretion of the
instructor, based on the needs of the course.
If a student is found violating this rule, following action will be taken
against the student:
On First Instance:
No attendance will be given to the student for that lecture/lab.
Written apology will be taken from the student.
On Second and future Instances:
No attendance will be given to the student for that lecture/lab.
Penalty of two points (on a 100 point scale) per incident for the student.
Student will have to immediately keep away the electronic item following
the incident.

Attendance
Make sure you sign your name in each class.
You may miss two lectures without penalty.
For subsequent absences, you will lose 1 point (out
of your total Attendance points) for each absence.
Missing Class Practices will be subjected to penalty unless
there is an emergency. If you become seriously ill or have
a family emergency, it is your responsibility to
communicate with the Professor as soon as you are able,
preferably before class. The Professor reserves the right
to require documentation.
8

Course Policies
Maintain a notebook and keep notes for every
lecture.
No social Networking/non relevant sites should
be opened during the class.
No food and drinks allowed in the class.
Lecture slides will be regularly posted.
Class practice assignments (based on certain
modules) should be completed by students in
class.
See Announcement Section regularly for other
information.
9

Cheating Policies
Any attempt to pass of someone elses work as
your own or to assist someone else in such an
effort is considered cheating. The penalty for a
first offence will be a score of zero on the
evaluation component in question for all
involved students. A second offence will result
in a failing grade for the course.
Please familiarize yourself with the University
policy on Unfair Means & Plagiarism.
Proxy attendance will be considered as a
cheating event
10

Grading Scheme
Evaluation Weight
Instrument age
Midterm
15%
Test I ??
Assignment
20%
s
Project
20%

Time

Comment

1 hour

Closed Book, In
Class
Open Book,
Submit Online
Presentation and
report

Attendance

10%

Comprehen
sive Exam

35%

-- See
Attendance and
Participation
3 hours
Closed Book, In
Class

By due
date
By due
date and
time

11

Grading Policy
Scores obtained in all the
components of Evaluation shall be
totaled and the final score will be
converted into letter grades as per
University policy.
Students taking this course to
improve their earlier grade are
reminded that this grade replaces
the previous grade (regardless of
which is higher).
12

Make Up Policy
No make-up will be granted for any component of
evaluation unless
(a) you have emailed the instructor with the necessary
reason(s) as soon as possible before the date of
evaluation and a make-up date has been agreed upon,
OR
(b) unforseeable circumstances prevent you from
keeping the original date. In either case, you may
need to submit supporting documents.
The decision of the Course Instructor-in-charge in all
these matters shall be final.
13

Material to be covered

14

Reading
Required Text:
Oppenheimer, Pricilla. Top-Down
Network Design, Second Edition/ Third
edition. Cisco Press, Indianapolis, IN,
2004.
- Second or Third Edition

15

Useful References

McCabe, James D. Network Analysis, Architecture, and

Design, Third Edition, Morgan Kaufmann; 3 edition (June
15, 2007): # ISBN-10: 0123704804, # ISBN-13: 9780123704801.

Hummel, Shaun, Network Planning and Design Guide,

Shaun Lloyd Hummel (May 25, 2006): # ISBN-10:
0973379804, # ISBN-13: 978-0973379808.

Olifer, Natalia and Olifer, Victor, Computer Networks:

Principles, Technologies and Protocols for Network Design,
Wiley (January 11, 2006): # ISBN-10: 0470869828, # ISBN13: 978-0470869826.

DiMarzio, Jerome, Network Architecture & Design "A Field

Guide for IT Professionals, Sams (May 21, 2001): # ISBN10: 0672320827, # ISBN-13: 978-0672320828
16

Course Material

Phase I

Analyzing Business Goals and Constraints

Analyzing Technical Goals and Tradeoff
Characterizing the Existing Network
Characterizing Network Traffic

Phase II

Designing a Network Topology

Designing Models for Addressing and Naming
Selecting switching and Routing Protocols
Developing Network Security Strategies
Developing Network Management Strategies

Phase III

Selecting Technologies and Devices for Campus Networks

Selecting Technologies and Devices for Enterprise Networks

Phase IV

Testing, Optimizing, and Documenting Your Network Design

17

OPNET SIGNIFICANCE

18

Why OPNET?

Networking technology
has become too complex
for traditional analytical
methods or rules of thumb
to yield an accurate
understanding of
system behavior

19

Blue Chip Customers

Manufacturers
3Com Corporation
NEC
Advanced Micro Devices Mitsubishi Electric
Alcatel
Newbridge
Ascom
Nokia
Boeing
Nortel
CableLabs
Onex
Cisco Systems
Panasonic Tech.
Comsat
Philips
Conexant Systems
Qualcomm
Ensemble Commns
Raytheon
Ericsson
Rockwell
Fujitsu
Sharp Labs
General Instruments
Siemens
GTE
Sony
Harris Communications Sun Microsystems
Hewlett Packard
Telcordia
Hughes
Telia
ilotron
Tellabs
Intel
Tellium
ITT
Terawave
Lockheed Martin
Texas Instruments
Lucent Technologies
Thomson
Magnavox
Toshiba
Marconi
Tropic Networks
Matsushita
TRW
Microsoft
Vitesse SemiConductor
MITEL
WirelessHome
Motorola
Zaffire

Enterprises
Abbott Labs
ABN AMRO
Accenture
Aerospatiale
Atofina Petrochemicals
AG Edwards
Bank of Oklahoma
Booz-Allen & Hamilton
CACI Federal
Cal Fed
Capital One
Charles Schwab & Co.
Citicorp
Compaq Global Services
CSC
Cummins Engine Co.
CVS Pharmacy
DaimlerChrysler
Dell Computers
DHL
DirecTV
Entergy
Enterprise Rent a Car
Ernst & Young
FBI
Federal Reserve Bank
Fidelity Investments
First American
First Citizen

First Union National Bank

General Dynamics
IBM Global Services
Ingram Micro
Inovant
Intermedia Communications
Internal Revenue Service
Kemper Insurance
NASDAQ
National Semiconductor
NCR
Newport News Shipbuilding
Oracle
Predictive Systems
Prudential
RR Donnelley
SAP
Schneider Electric
Sears
Seattle Times
Schlumberger
SIAC
Siebel Systems
Spiegel
State Street Bank
TXU
Unisys
Visa International
VSP

Service Providers
AirTouch
AT&T
AT&T Wireless
Belgacom
Bell Canada
BellSouth
British Telecom
Cable & Wireless
Chunghwa Telecom
Compuserve
Deutsche Telekom
Dolphin Telecom
Enron
France Telecom
Hungarian Telecom
Hutchison 3G
ITALTEL SpA
Indonesia Telecom
Infonet
Inmarsat
Intelsat
KDDI
Korea Telecom
LG TeleCom
Network Access Slns
Nextel
NTT DoCoMo

NTT Group
Omnitel
One 2 One
Orange PCS
Orbital Sciences
Polish Telecom
PT Comunicacoes
QoS Networks
Qwest
SBC
SK Telecom
Sprint
SWIFT
Swisscom
Telekom Austria
Telecom Italia
Telecom Italia Mobile
Teledesic
Telefonica
Telenor
TELUS
Telstra
UUNET
Verizon
Vodafone
Williams
WIND SpA
WorldCom

20

OPNET Confidential Not for release to third parties

2001 OPNET Technologies, Inc. All rights reserved. OPNET and OPNET product names are trademarks of OPNET Technologies, Inc.

Federal Customers
DoD
Army Research
Laboratories (ARL)
CIA
Defense Information
Systems Agency (DISA)
Joint Staff (J6)
National Communication
System
National Ground
Intelligence Center
National Guard
National Institute Mapping
Agency (NIMA)
National Security Agency
NATO
Naval Information
WarfareCenter
Naval Postgraduate School
Naval Research
Laboratories (NRL)
Naval Surface
Warfare Center (NSWC)
Naval Underwater
Warfare Center (NUSC)

Civilian
NRaD/NCCOSC
Tri-Service Information
Management Program
Office (TIMPO)
US Army CECOM
US Army Combined
Arms Center
US Army HQDA/DISC4
US Army Missile
Command
US Army Signal Center
US Army Signal
Command
US Marine Corps
US Military Academy
US AirForce SSG
US Air Force ESC
US Air Force AFCA
US Air Force HQ 38th EIW
US Air Force Information
Warfare Center
US Air Force PAC
US Air Force RADC

Coast Guard
Department of Agriculture
Department of Commerce
Department of State
FAA
FBI
Federal Railroad
Administration
IRS
Idaho National
Engineering &
Environmental Lab
Jet Propulsion
Laboratory
Lawrence Livermore
National Lab
Lincoln Labs

Contractors/Partners
NASA- Ames
Research Center
NASA- Goddard Space
Flight Center
NASA- Glenn
Research Center
National Simulation
Center
National Institutes
of Health
Oak Ridge National Labs
Sandia National Labs
Tennessee Valley
Authority
US Agency for
International Development
US Senate

Aerospace Corporation
Adroit Systems
ARINC
AT&T Bell Laboratories
Booz-Allen & Hamilton
BBN
BDM
Boeing
BTG
Computer Sciences
Corp.
CACI Federal Systems
Dyncorp
GEC Marconi
General Dynamics
GTE
Harris
Hazeltine
Hughes
IITRI
IITRI
ITT
KPMG

Lockheed Martin
Logicon
Magnavox
MIT Lincoln Labs
MITRE
Motorola
Nichols Research
Northop Gruman
PRC
PSC
Rand
Raytheon
Rockwell
SAIC
Space Systems
Spectral Systems
SRI
TASC
Techno-Sciences
Trident Systems
TRW
Westinghouse
Veridian

21

What is Network Design?

What is Network Performance?
What is the significance of the two?
What goes into Network Design?
How do you assess NW performance?
Why do we need to asses NW
performance?
Related Topics
Network management, Business
Impacts
22

Designing Networks
Before designing a network you must gather
data and understand the data : customer needs
business goals
business climate
Government and Industry Regulations

23

Design Fundamentals
Two Basic Designs techniques
Top Down
Bottom Up

24

Design Fundamentals - Bottom-Up

Establish where network access is
needed
Edge

Design infrastructure
Choose the devices needed to
support the infrastructure
Select the desired protocols needed
Configure devices to support traffic
needs.
25

Network Architecture /
Topology ?

26

The Abilities from a Network Perspective

Scalability
Capability
Availability
Usability
Manageability
Adaptability
Affordability
Compatibility
Maintainability

Not the Business goals

27

Design Fundamentals - Top Down

Identify customer needs

Identify applications that will be running
BIG PICTURE
Identify corporate goals, policies, constraints
Determine traffic patterns

Determine infrastructure and device configuration

needed to support the traffic
Select protocols needed
Test the design /infrastructure

28

Design Fundamentals
Which one is the best?
And the answer is ..
Depends
On what

How many bottoms-up you have had during the design stage.

29

Design Fundamentals
Actually depends upon circumstances
Bottom up
Temporary network
Short notice, small change
You know customer needs do you?

Top down
Permanent network, time to study and analyze
Larger network design
Dont understand customer need or corporate
goals
30

Top-Down Network Design

Network design should be
a complete process that
matches business needs to available
technology
to deliver a system that will maximize
an organizations success

OPTIMIZING !!
31

Design Fundamentals
Bottom up
Temporary network
Short notice, small change
You know customer needs or do you?

Top down
Permanent network, time to study and analyze
Larger network design
Dont understand customer need or corporate
goals

32

Top-Down Network Design

Network design should be
a complete process that
matches business needs to available
technology
to deliver a system that will maximize
an organizations success

OPTIMIZING !!
33

Top-Down Network
Design
Phase I Chapter 1
Analyzing Business Goals and Constraints

34

Road Map
Use a systematic top-down process to
design the network
Analyze the customers business goals
Identify network applications
Address business objectives,

Understand business constraints

budget, personnel, timeframe

Understand workplace politics

The eight layer of the OSI model -

35

Top-Down Network Design Methodology

A systematic methodology
Recognize customer requirements
Includes business and technical goals
Scalability, availability, affordability, security, manageability
People for whom the network will provide services
Get information from them satisfy?

Iterative process
Get overall view of customer expectation from the network
Later gather details on scalability, protocols, technology
preferences

ITERATIVE

Explore divisional and group structures

Logical model and physical design may change

More information is gathered
Network performance is assessed
36

Structured Systems Analysis >

Requirements

To accurately ?? represent customer needs

Manageable modules
All modules top-down approach

Use techniques /models

to characterize existing system,
new user requirements,
structure for the future system
Data flow, data types, and processes that access or change
the data.

Identify/understand
location and needs of user communities that access or
change data and processes.

Develop a logical model the structure of the

system
the basic building blocks - divided by function,

37

DERIVE SPECIFICATIONS FROM THE

REQUIREMENTS GATHERED

Focus on Layer 7 and above

first

38

Top-Down Network Design

Steps
Analyze
requirements

Monitor and
optimize
network
performance

Develop
logical
design

Develop
physical
design

Implement
and test
network
Test, optimize,
and document
design

39

Network Design Steps

Phase 1 Analyze Requirements
Analyze business goals and constraints
Analyze technical goals and tradeoffs
Characterize the existing network
Characterize network traffic
INPUT TO NETWORK DESIGN - > LOGICAL
DESIGN
40

Network Design Steps

What is the best architecture?
Design a network topology
Design models for addressing and naming
Select switching and routing protocols
Develop network security strategies
Develop network management strategies

GETTING THE SPECIFICATIONS

ON PAPER > PHYSICAL DESIGN

Afterthoug
ht?

Phase 2 Logical Network Design

41

Network Design Steps

Phase 3 Physical Network Design
Select technologies and devices for
campus networks
Select technologies and devices for
enterprise networks
Gather DATA on current technologies/
equipment / price / vendor credibility
Go to pre- implementation phase
42

Network Design Steps

Phase 4 Testing, Optimizing, and
Documenting the Network Design
Test the network design
Optimize the network design
Document the network design

NOT THE REAL NETWORK YET!

43

Additional Steps
If the customer buys the design two
additional steps result
Implement and test the network
Manage (Monitor and Optimize
network performance, adds, deletes,
changes, maintenance)

44

The PDIOO Network Life

Cycle
Plan

Design
Retire
Optimize

Implement
Operate

45

Systems Development Life

Cycles
SDLC: Systems Development Life
Cycle?
Typical systems are developed and
continue to exist over a period of
time, often called a systems
development life cycle (SDLC)

46

47

Analyzing Business Goals

Increase revenue
Reduce operating costs
Improve communications
Shorten product development cycle
Expand into worldwide markets
Build partnerships with other companies
Offer better customer support or new
customer services
ANY OR ALL PRIORITIZE
48

Recent Business Priorities

nd
(2
Ed)
Mobility

Security
Resiliency (fault tolerance)
Business continuity after a disaster
Network projects must be prioritized based
on fiscal goals
Networks must offer the low delay required
for real-time applications such as VoIP
Cost reduction is critical

49

More recent Business Priorities(3 rd

Ed)
Network redundancy
Modularity in network designs
The Cisco SAFE security reference
architecture
The Rapid Spanning Tree Protocol (RSTP)
Internet Protocol version 6 (IPv6)
Ethernet scalability options, including 10Gbps Ethernet and Metro Ethernet
Network design and management tools
50

Prep Before the First Meeting

Before meeting with the client, collect
some basic business-related information
Such as
Products produced/Services supplied
Financial viability
Customers, suppliers, competitors
Competitive advantage

Eventual strengthen the customers

status in the customers own industry
51

Meet With the Customer

Obtain
A business oriented statement
that highlights the business
purpose of the new network
Why the project?
How will it be used?
How will it help in being successful
in their business?
What is the customers criteria for
success?

52

Meet With the Customer

What will happen if the project is a
failure?
Is this a critical business function?
How visible is the project to upper
management /executives?
How much will it disrupt business
operations?

53

Meet With the Customer

Discover any biases
For example
Will they only use certain companys
products?
Do they avoid certain technologies?
Do the data people look down on the
voice people or vice versa?

Talk to the technical and

management staff

54

Meet With the Customer

Get a copy of the organization chart

general structure of the organization

users to account for
geographical locations to account for
privileges

55

Security
Get a copy of the security policy
Policy affects the new design?
New design affect the policy?
Viable policy

Cataloging network assets to secure

Hardware, software, applications, and data
Less obvious, but still important, intellectual
property, trade secrets, and a company's
reputation

Privacy?

56

Does the Customer know

what HE/SHE wants?

57

The Scope of the Design

Project
Small in scope?
Allow some people to access network via a VPN

Large in scope?
An entire redesign of an enterprise network

Use the OSI model to clarify the scope

New financial reporting application versus new
routing protocol versus new data link (wireless, for
example)

Does the scope fit the budget, capabilities of

staff and consultants, schedule?
58

Networks Today
Difficult to predict data flow traffic
flow
Mobile user proliferation
Data travel paths changes with user
movement

Security and Network resiliency

Service availability 99.999%?
Impact of service disruption

Disaster recovery
Systematic and modular design

59

Analyzing Business
Constraints

60

Business Constraints

Budget
Staffing
Schedule
Politics and policies

61

Politics and Policies

Listen learn
Biases, turf wars, hidden agendas ++++
Earlier attempts success/failures ++++
Who is supporting the project?
Job eliminations?
Unifying voice and data
Tolerance to risk
Forbidden technology +++
Do not step in others toes
Boss knows it all !! ++++
62

Budgetary and Staffing

Constraints
Budget includes equipment
purchase, licenses, maintenance and
support, testing, training, staffing

New project
In-house networking staff
How to provide for extra staffing

Contain costs
63

Time frame of the Project

64

65

66

67

68

69

Renewal and Replacement

Planning
A staged plan to replace hardware or
software in defined cycles.
Requires multi-year budget planning
Takes into account
Demand and performance
Maintenance cost
Product life cycles

Fits corporate network environments

70

Gather More Detailed

Information
Start with Applications
Now and after the project is completed
Include both productivity applications and
system management applications

User communities
Data stores
Protocols
Current logical and physical architecture
Current performance
71

Network Applications
Name of
Type of
Application Application

New
Criticality
Application?

Comments

72

Network Applications
Name of
Type of
Application Application

Registration
Accounting
Payroll
Billing

New
Criticality
Application?

student records

no

financial
employee pay
financial

no
Yes

critical

defined cycles

semi critical
very critical

No

Comments

monthly cycles
bi weekly and bi monthly

very critical

Defined Cycles

73