Transcript Top-Down Network Design

CH
9
LOGICAL NETWORK
DESIGN
1
Network Topology
Addressing and Naming
 Switching and Routing Protocols
Network Security Strategies
 Management Strategies
9.1
DESIGNING A
NETWORK TOPOLOGY
2
Copyright 2010 Cisco Press & Priscilla Oppenheimer
NETWORK TOPOLOGY DESIGN THEMES
 Hierarchy
•
•
•
(opposite to flat or mesh network)
Core layer
Distribution layer
Access layers
 Redundancy
 Modularity
 Well-defined
entries and exits
 Protected areas
3
WHY USE A HIERARCHICAL MODEL?
 Reduces


workload on network devices
Avoids devices having to communicate with too
many other devices (reduces “CPU adjacencies”)
Constrains broadcast domains
 Minimize
costs. Only buy appropriate
devices for each layer
 Facilitates changes easy and cheap
 Good for modularity and scalability
4
5
HIERARCHICAL NETWORK DESIGN
Enterprise WAN
Backbone
Campus A
Core Layer
Campus B
Campus C
Campus C Backbone
Distribution
Layer
Access Layer
Building C-1
Building C-2
6
CISCO’S HIERARCHICAL DESIGN
MODEL
A
core layer of high-end routers and
switches that are optimized for
availability and speed
A
distribution layer of routers and
switches that implement policies and
segment traffic
 An
access layer that connects users via
hubs, switches, and other devices
7
UTILIZE THE HIERARCHICAL DESIGN MODEL TO
DEVELOP A COST-EFFECTIVE NETWORK DESIGN
Access Layer
requirements:
 Connectivity for existing
devices and new devices
 VLANs to separate voice,
security, wireless, and
normal data services
 Redundancy
 QoS
UTILIZE THE HIERARCHICAL DESIGN MODEL TO
DEVELOP A COST-EFFECTIVE NETWORK DESIGN
Distribution layer
requirements:
 Redundant components
and links
 High-density routing
 Traffic filtering
 QoS implementation
 High-bandwidth
connectivity
 Fast convergence
 Route summarization
UTILIZE THE HIERARCHICAL DESIGN MODEL TO
DEVELOP A COST-EFFECTIVE NETWORK DESIGN
Core Layer
requirements:
 High-speed
connectivity
 Routed
interconnections
 High-speed
redundant links
FLAT VERSUS HIERARCHY
Headquarters in
Medford
Headquarters in
Medford
Grants Pass
Branch Office
Klamath Falls
Branch Office
Ashland
Branch
Office
Flat Loop Topology
Grants Pass
Branch
Office
Klamath Falls
Branch Office
Ashland
Branch
Office
White City
Branch Office
Hierarchical Redundant Topology
11
MESH DESIGNS
Partial-Mesh Topology
Full-Mesh Topology
12
A PARTIAL-MESH HIERARCHICAL DESIGN
Headquarters
(Core Layer)
Regional
Offices
(Distribution
Layer)
Branch Offices (Access Layer)
13
A HUB-AND-SPOKE HIERARCHICAL
TOPOLOGY FOR SMALL COMPANY
Corporate
Headquarters
14
Branch Office
Home Office
Branch Office
AVOID CHAINS AND BACKDOORS
Chain: extra layer
Back door:
connection between
devices in the same
layer, makes
unexpected routing
and switching
problems.
Core Layer
Distribution Layer
Access Layer
Backdoor
Chain
15
CAMPUS TOPOLOGY DESIGN
 Use
a hierarchical, modular approach
 Minimize the size of collision domains
 Minimize the size of broadcast domains
 Provide redundancy
16
A SIMPLE CAMPUS REDUNDANT DESIGN
Host A
LAN X
Switch 1
Switch 2
LAN Y
Host B
17
BRIDGES/SWITCHES USE SPANNING-TREE
PROTOCOL (STP) TO AVOID LOOPS
Host A
LAN X
X Switch 2
Switch 1
LAN Y
Host B
18
VIRTUAL LANS (VLANS)
VLANS VERSUS REAL LANS
Switch A
Station A1
Station A2
Network A
Switch B
Station A3
Station B1
Station B2
Station B3
Network B
Two switches that are not connected to each other in any
way. When Station A1 sends a broadcast, Station A2 and
Station A3 receive the broadcast, but none of the stations in
Network B receive the broadcast
19
A SWITCH WITH VLANS
Through the configuration of
the switch there are now two
virtual LANs implemented in
a single switch. The
broadcast, multicast, and
unknown-destination traffic
originating with any member
of VLAN A is forwarded to
all other members of VLAN
A, and not to a member of
VLAN B. VLAN A has the
same properties as a
physically separate LAN
bounded by routers.
VLAN A
Station A1
Station B1
Station A2
Station B2
Station A3
Station B3
20
VLAN B
VLANS SPAN SWITCHES
VLAN A
Station A1
Station A2
VLAN A
Station A3
Station A4
Station A5
Switch A
Station B1
Station A6
Switch B
Station B2
Station B3
Station B4
VLAN B
Station B5
Station B6
VLAN B
VLANs can span multiple switches.
21
INCORPORATE WIRELESS CONNECTIVITY INTO
THE LAN DESIGN
Factors influencing availability in a wireless
network:
 Location of the AP
 Signal strength of the AP
 Number of users
 Dynamic
reconfiguration
 Centralization
WLANS AND VLANS
A
wireless LAN (WLAN) is often implemented
as a VLAN
 WLAN should be a separate subnet
LSBU, WLAN: 172. 20.X.X LAN 136.148.X.X
 Clients roaming but Users remain in the same
VLAN and IP subnet as they roam, so there’s
no need to change addressing information
 Also makes it easier to set up filters
ACL(Access Control Lists) to protect the wired
network from wireless users.
23
SECURITY TOPOLOGIES
Enterprise
Network
DMZ
Internet
Web, File, DNS, Mail Servers
24
DMZ
DMZ: demilitarized zone: is a physical or
logical subnetwork that contains and exposes an
organization's external-facing services to a larger
untrusted network, usually the Internet.
The purpose of a DMZ is to add an additional layer of
security to an organization's local area network (LAN);
an external attacker only has access to equipment in the
DMZ, rather than any other part of the network.
In a computer network, the hosts most vulnerable to
attack are those that provide services to users outside of
the local area network, such as e-mail, web and Domain
25
Name System (DNS) servers.
SECURITY TOPOLOGIES
Firewall:
boundary
between two or
more networks
Internet
Firewall
DMZ
Enterprise Network
26
Web, File, DNS, Mail Servers
FIREWALL
A
firewall can either be software-based
or hardware-based and is used to help
keep a network secure. Its primary
objective is to control the incoming and
outgoing network traffic by analyzing the
data packets and determining whether it
should be allowed through or not, based
on a predetermined rule set.
27
SUMMARY
 Use
a systematic, top-down approach
 Plan the logical design before the physical
design
 Topology design should feature hierarchy,
redundancy, modularity, and security
28
REVIEW QUESTIONS
 Why
are hierarchy and modularity important
for network designs?
 What are the three layers of Cisco’s
hierarchical network design?
 What are the major components of Cisco’s
enterprise composite network model?
 What are the advantages and disadvantages
of the various options for multihoming an
Internet connection?
29
9.2
DESIGNING MODELS FOR ADDRESSING
AND NAMING
30
Copyright 2010 Cisco Press & Priscilla Oppenheimer
GUIDELINES FOR ADDRESSING
NAMING
AND
 Use
a structured model for addressing and
naming
 Assign addresses and names hierarchically
 Decide in advance
31
ADVANTAGES OF STRUCTURED MODELS
FOR ADDRESSING & NAMING
 It






makes it easier to
Read network maps
Operate network management software
Recognize devices in protocol analyzer traces
Meet goals for usability
Design filters on firewalls and routers
Implement route summarization
32
PUBLIC IP ADDRESSES
Managed by the Internet Assigned Numbers Authority
(IANA)
 Users are assigned IP addresses by Internet Service
Providers (ISPs).
 ISPs obtain allocations of IP addresses from their
appropriate Regional Internet Registry (RIR)
 Public address is essential for web server or other
servers that external users access. But not necessary
for all internal hosts and networks. Private address is
ok.
 Addressing for internal host that need access to
outside services can be handled by NAT (Network
Address Translation) gateway.

33
REGIONAL INTERNET REGISTRIES (RIR)
 American
Registry for Internet Numbers (ARIN)
serves North America and parts of the Caribbean.
 RIPE Network Coordination Centre (RIPE NCC)
serves Europe, the Middle East, and Central Asia.
 Asia-Pacific Network Information Centre (APNIC)
serves Asia and the Pacific region.
 Latin American and Caribbean Internet Addresses
Registry (LACNIC) serves Latin America and
parts of the Caribbean.
 African Network Information Centre (AfriNIC)
serves Africa.
34
PRIVATE ADDRESSING
An enterprise network administrator assigns to internal
networks and hosts without any coordination from an
ISP or RIRs.
10.0.0.0
– 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255
Advantages:
 Security. Private network numbers are not advertised.
 Flexibility. Easy to change to new ISP.
35
 Save IP address resources.
DESIGNING NETWORKS WITH SUBNETS
 Determining
subnet size
 Computing subnet mask
 Computing IP addresses
36
SUBNETS
Subnetting is the process to divide a network into
several smaller networks.
 Within a subnet, all the hosts have the same
network ID in their IP addresses.
 With subnets, a physical network can be divided
into logical units.
 The hosts in each unit can directly communicate
with each other and use the same router to
communicate with the hosts in the other subnets.
 Local broadcasting is limited within a subnet.
37
REASONS FOR USING SUBNETS
To efficiently use IP addresses
 To reduce the number of collisions
 To reduce broadcasting traffic
 To strengthen network security control
 To implement the network structure at the site,
building, department, and office levels
 To reduce the cost of paying the ISP for public IP
addresses

38
ADDRESSES TO AVOID WHEN
SUBNETTING
A
node address of all ones (broadcast)
 A node address of all zeros (network)
 A subnet address of all ones (all subnets)
 A subnet address of all zeros (confusing)
39
GUIDELINES FOR ASSIGNING NAMES
 Names
should be
Short
 Meaningful
 Clear
 Distinct
 Case insensitive

 Avoid

names with unusual characters
Hyphens, underscores, asterisks, and so on
40
DOMAIN NAME SYSTEM (DNS)
 Maps
names to IP addresses
 Supports hierarchical naming

example: eent3.lsbu.ac.uk
A
DNS server has a database of resource
records (RRs) that maps names to addresses in
the server’s “zone of authority”
 Client queries server


Uses UDP port 53 for name queries and replies
Uses TCP port 53 for zone transfers
41
SUMMARY
 Use
a systematic, structured, top-down
approach to addressing and naming
 Assign addresses in a hierarchical fashion
 Distribute authority for addressing and
naming where appropriate
 IPv6 looms in our future
42
REVIEW QUESTIONS
 Why
is it important to use a structured model
for addressing and naming?
 When is it appropriate to use IP private
addressing versus public addressing?
 When is it appropriate to use static versus
dynamic addressing?
 What are some approaches to upgrading to
IPv6?
43
9.3
SELECTING SWITCHING AND
ROUTING PROTOCOLS
44
Copyright 2010 Cisco Press & Priscilla Oppenheimer
SWITCHING AND ROUTING CHOICES
 Switching
Layer 2 transparent bridging (switching)
 Multilayer switching
 Spanning Tree Protocol enhancements
 VLAN technologies

 Routing
Static or dynamic
 Distance-vector and link-state protocols
 Interior and exterior
 Etc.

45
SELECTION CRITERIA FOR SWITCHING
AND ROUTING PROTOCOLS
 Network
traffic characteristics
 Bandwidth, memory, and CPU usage
 The number of peers supported
 The capability to adapt to changes quickly
 Support for authentication
46
EXAMPLE DECISION TABLE
47
SELECTING ROUTING PROTOCOLS
A routing protocol lets a router dynamically learn how
to reach other networks and exchange this
information with other routers.
 They all have the same general goal:
 To share network reachability information
routers
among
 They differ in many ways:
 Interior versus exterior
 Metrics supported
 Dynamic versus static and default
 Distance-vector versus link-sate
 Classful versus classless
 Scalability
48
INTERIOR VERSUS EXTERIOR
ROUTING PROTOCOLS
 Interior
routing protocols are used within
one organization. The current lead Interior
Routing Protocol is OSPF. Other Interior Protocols
include IS-IS, RIP, and EIGRP.
 Exterior
routing protocols are used
between organizations. The current lead Exterior
Gateway Protocol is BGP. The current revision of
BGP is BGP4. There are no other Exterior Gateway
Routing protocols in current competition with
BGP4.
49
ROUTING PROTOCOL METRICS
 Metric:
the determining factor used by a
routing algorithm to decide which route to a
network is better than another
 Examples of metrics:






Bandwidth - capacity
Delay - time
Load - amount of network traffic
Reliability - error rate
Hop count - number of routers that a packet
must travel through before reaching the
destination network
Cost - arbitrary value defined by the protocol or
50
administrator
51
SUMMARY
 The
selection of switching and routing protocols
should be based on an analysis of
Goals
 Scalability and performance characteristics of the
protocols

 Transparent

bridging is used on modern switches
But other choices involve enhancements to STP and
protocols for transporting VLAN information
 There
are many types of routing protocols and
many choices within each type
52
REVIEW QUESTIONS
 What
are some options for enhancing the
Spanning Tree Protocol?
 What factors will help you decide whether
distance-vector or link-state routing is best for
your design customer?
 What factors will help you select a specific
routing protocol?
 Why do static and default routing still play a
role in many modern network designs?
53
9.4
DEVELOPING NETWORK
SECURITY STRATEGIES
54
Copyright 2010 Cisco Press & Priscilla Oppenheimer
NETWORK SECURITY DESIGN
THE 12 STEP PROGRAM
1.
2.
3.
4.
5.
6.
Identify network assets
Analyze security risks
Analyze security requirements and
tradeoffs
Develop a security plan
Define a security policy
Develop procedures for applying
security policies
ch2
ch8
55
THE 12 STEP PROGRAM (CONTINUED)
7.
8.
9.
10.
11.
12.
Develop a technical implementation
strategy
Achieve buy-in from users, managers, and
technical staff
out
Train users, managers, and technical staff
Implement the technical strategy and
security procedures
Test the security and update it if any
ch12
problems are found
ch8
Maintain security
56
NETWORK ASSETS
 Hardware
 Software
 Applications
 Data
 Intellectual
property
 Trade secrets
 Company’s reputation
57
SECURITY RISKS
 Hacked
network devices
Data can be intercepted, analyzed, altered, or
deleted
 User passwords can be compromised
 Device configurations can be changed

 Reconnaissance
attacks (gather information )
 Denial-of-service attacks (make a computer
resource unavailable to its intended users)
58
SECURITY TRADEOFFS
 Tradeoffs
must be made between security
goals and other goals:





Affordability
Usability
Performance
Availability
Manageability
Security adds to management work (user ID, passwords ),
and affects network performance. Encryption consume
upto 15% of CPU power on a router or network
throughput.
59
A SECURITY PLAN
 High-level
document that
proposes what an organization
is going to do to meet security
requirements
 Specifies time, people, and
other resources that will be
required to develop a security
policy and achieve
implementation of the policy
60
A SECURITY POLICY
A

security policy is a
“Formal statement of the rules by which people
who are given access to an organization’s
technology and information assets must abide.”
 The

policy should address
Access, accountability, authentication, privacy,
and computer technology purchasing guidelines
61
SECURITY MECHANISMS
 Physical
security
 Authentication
 Authorization
 Accounting (Auditing)
 Data encryption
 Packet filters
 Firewalls
 Intrusion Detection Systems (IDS)
 Intrusion Prevention Systems (IPS)
62
MODULARIZING SECURITY DESIGN
 Security

defense in depth
Network security should be multilayered with
many different techniques used to protect the
network
 Belt-and-suspenders

approach
Don’t get caught with your pants down
63
MODULARIZING SECURITY DESIGN
 Secure







all components of a modular design:
Internet connections
Public servers and e-commerce servers
Remote access networks and VPNs
Network services and network management
Server farms
User services
Wireless networks
64
SECURING INTERNET CONNECTIONS
 Physical
security
 Firewalls and packet filters
 Audit logs, authentication, authorization
 Well-defined exit and entry points
 Routing protocols that support
authentication
65
SECURING PUBLIC SERVERS
 Place
servers in a DMZ that is protected via
firewalls
 Run a firewall on the server itself
 Enable DoS protection

Limit the number of connections per timeframe
 Use
reliable operating systems with the
latest security patches
 Maintain modularity

Front-end Web server doesn’t also run other
services (FTP services not run on the same server as
Web services, e-commerce database should not be on the
web server.)
66
SECURING REMOTE-ACCESS AND
VIRTUAL PRIVATE NETWORKS (VPN)
 Physical
security
 Firewalls
 Authentication, authorization, and auditing
 Encryption
 One-time passwords
 Security protocols
CHAP
 RADIUS
 IPSec

67
SECURING NETWORK SERVICES
 Treat
each network device (routers, switches,
and so on) as a high-value host and harden it
against possible intrusions
 Require login IDs and passwords for accessing
devices

Require extra authorization for risky configuration
commands
 Use
SSH rather than Telnet
 Change the welcome banner to be less
welcoming
68
SECURING SERVER FARMS
 Deploy
network and host IDSs to monitor server
subnets and individual servers
 Configure filters that limit connectivity from the
server in case the server is compromised
 Fix known security bugs in server operating
systems
 Require authentication and authorization for
server access and management
 Limit root password to a few people
 Avoid guest accounts
69
SECURING USER SERVICES
 Specify
which applications are allowed to run
on networked PCs in the security policy
 Require personal firewalls and antivirus
software on networked PCs

Implement written procedures that specify how the
software is installed and kept current
 Encourage
users to log out when leaving their
desks
 Consider using 802.1X port-based security on
switches
70
SECURING WIRELESS NETWORKS
 Place
wireless LANs (WLANs) in their own
subnet or VLAN

Simplifies addressing and makes it easier to
configure packet filters
 Require
all wireless (and wired) laptops to run
personal firewall and antivirus software
 Disable beacons that broadcast the SSID, and
require MAC address authentication
71
VPN SOFTWARE ON WIRELESS CLIENTS
 Safest
way to do wireless networking for
corporations
 Wireless client requires VPN software
 Connects to VPN concentrator at HQ
 Creates a tunnel for sending all traffic
 VPN security provides:



User authentication
Strong encryption of data
Data integrity
72
SUMMARY
 Use
a top-down approach
Chapter 2 talks about identifying assets and risks
and developing security requirements
 Chapter 5 talks about logical design for security
(secure topologies)
 Chapter 8 talks about the security plan, policy, and
procedures
 Chapter 8 also covers security mechanisms and
selecting the right mechanisms for the different
components of a modular network design

73
REVIEW QUESTIONS
 How
does a security plan differ from a security
policy?
 Why is it important to achieve buy-in from
users, managers, and technical staff for the
security policy?
 What are some methods for keeping hackers
from viewing and changing router and switch
configuration information?
 How can a network manager secure a wireless
network?
74
9.5
DEVELOPING NETWORK
MANAGEMENT STRATEGIES
75
Copyright 2010 Cisco Press & Priscilla Oppenheimer
NETWORK MANAGEMENT
 Helps
an organization achieve availability,
performance, and security goals
 Helps an organization measure how well
design goals are being met and adjust
network parameters if they are not being
met
 Facilitates scalability

Helps an organization analyze current network
behavior, apply upgrades appropriately, and
troubleshoot any problems with upgrades
76
NETWORK MANAGEMENT DESIGN
 Consider
scalability, traffic patterns, data
formats, cost/benefit tradeoffs
 Determine which resources should be
monitored
 Determine metrics for measuring
performance
 Determine which and how much data to
collect
77
PROACTIVE NETWORK MANAGEMENT
 Plan
to check the health of the network
during normal operation, not just when
there are problems
 Recognize potential problems as they
develop
 Optimize performance
 Plan upgrades appropriately
78
NETWORK MANAGEMENT PROCESSES
ACCORDING TO THE ISO
 Fault
management
 Configuration management
 Accounting management
 Performance management
 Security management
79
NETWORK MANAGEMENT COMPONENTS
A
managed device is a network node that
collects and stores management information
 An agent is network-management software
that resides in a managed device
 A network-management system (NMS)
runs applications to display management
data, monitor and control managed devices,
and communicate with agents
85
NETWORK MANAGEMENT ARCHITECTURE
NMS
Agent
Agent
Agent
Management
Database
Management
Database
Management
Database
Managed
Devices
86
ARCHITECTURE CONCERNS
 In-band

versus out-of-band monitoring
In-band control passes control data on the same
connection as main data. Out-of-band control
passes control data on a separate connection
from main data. In-band is easier to develop, but
results in management data being impacted by
network problems
 Centralized

versus distributed monitoring
Centralized management is simpler to develop
and maintain, but may require huge amounts of
information to travel back to a centralized
network operations center (NOC)
87
REVIEW QUESTIONS
 Why
is network management design
important?
 Define the five types of network management
processes according to the ISO.
 What are some advantages and disadvantages
of using in-band network management versus
out-of-band network management?
 What are some advantages and disadvantages
of using centralized network management
versus distributed network management?
88
89