Chapter 1: Network Architecture

Network Architecture
Designing a Network Topology
Hierarchical vs. Flat Topology
Mesh vs. Hierarchical Topology

Sem 1-1617
1
Course objective
• Describe the network architecture and the reference model.
• Describe the type of network topology.
• Describe techniques and recommendations for designing a network
that is scalable.
• Describe the use of a hierarchical network for both campus and
enterprise WAN.
• Describe the use of redundant network design (mesh) topologies and
topologies that meet security goal.
• Describe the type of internetworking devices that are required for
both campus and enterprise WAN

Sem 1-1617 2
Network Architecture
Network architecture, is the logical and structural layout of the network consisting
of transmission equipment, software and communication protocols and
infrastructure (wired or wireless) transmission of data and connectivity between
components.

3
Network Architecture
• Layout of the network- logical & structural layout
• Components :
Hardware
software,
 connectivity
communication protocols
mode of transmission - wired or wireless.
• Learn the types of network – LAN, WAN, MAN
• Learn the network topologies – star, bus, ring , mesh

4
http://en.kioskea.net/faq/2761-what-is-network-architecture
Network Architecture-reference model
TCP/IP network architecture
• Used in Internet - an open network architecture and it is adopted as a
worldwide network standard
• Widely deployed in
• LAN
Types of networks
• WAN
• small and large enterprises
Network Architecture-reference model
OSI reference model Network
Architecture
• An open standard for communication in the
network across different equipment and
applications by different vendors.
• Not widely deployed- however it is considered
as the primary network architectural model for
inter-computing and inter-networking
communications.
• Network architecture provides only a
conceptual framework for communications
between computers.
• Actual communication is defined by various
communication protocols.
6
Network Architecture – other reference
models
• IBM SNA (Systems Network Architecture),
• Digital Equipment Corporation (DEC; now part of HP)
• DNA (Digital Network Architecture)
• Apple computer's AppleTalk,
• Novell's NetWare.

7
Designing a Network
Topology

Sem 1-1617 8
 Introduction to Network Topologies
Topology: a map of an internetwork that indicates network segments,
interconnection points and user communities. Map – geometry of
network (not technical implementation, not physical geography).

• Layout of connected equipment/devices and computers

• Can be illustrated as physically or logically.
• Physical topology = the placement of the network’s components and cabling
• Logical topology = flow of data within a network regardless of its physical
design.
• Mapping the data flow between the components determined the logical
topology of the network.
9
Example of Network Topologies
Both physical and network topologies can be categorized into five basic
models:
Bus Topology:
• All the devices/nodes are connected
sequentially to the same backbone or
transmission line.
• This is a simple, low-cost topology, but
its single point of failure presents a
risk.
• Mesh Topology:
• The topology in each node is directly
connected to some or all the other nodes
present in the network.
• This redundancy makes the network
highly fault tolerant but the escalated
costs may limit this topology to highly
critical networks.
10
Continue…
• Star Topology:
• All the nodes in the network are connected to
a central device like a hub or switch via
cables.
• Failure of individual nodes or cables does not
necessarily create downtime in the network
but the failure of a central device can.
• This topology is the most preferred and
popular model.
• Ring Topology:
• All network devices are connected
sequentially to a backbone as in bus
topology except that the backbone
ends at the starting node, forming a
ring.
• Ring topology shares many of bus
topology's disadvantages so its use is
limited to networks that demand high
throughput.
11
 Continue..
• Tree Topology / Hierarchical Topology:
• A root node is connected to two or more
sub-level nodes, which themselves are
connected hierarchically to sub-level nodes.
• Physically, the tree topology is similar to bus
and star topologies; the network backbone
may have a bus topology, while the low-level
nodes connect using star topology.
• HYBRID Topology
• It is two different types of
topologies which is a mixture of
two or more topologies.
• For example if in an office in one
department ring topology is used
and in another star topology is
used, connecting these topologies
will result in Hybrid Topology (ring
topology and star topology).
12
Network Design Methodology
• The 1st Step in Top-down network design methodology:
• Designing a network topology –for scalability and adaptability. During the
topology design phase:
• you identify networks and interconnection points
• the size and scope of networks,
• And the types of internetworking devices that will be required but not the actual
devices.
• This chapter provides tips for both campus and enterprise WAN
network design and focuses on hierarchical network design, which is a
technique for designing scalable campus and WAN networks using a
layered, modular model.

AAB-updated Sem 2-1516 13

Designing a Network Topology
• Network design is an art, not a science
• There are no rules
• There are no precisely correct formulas
• It always depends on requirements /needs

14
Hierarchical Network Design
• Design network in discrete layers. Enterprise WAN Core Layer
Backbone
• Each layer focused on specific Campus A Campus B
functions-which allow the
organization to choose the right Campus C
systems and features for the layer.
• Use high speed WAN routers to Campus C Distribution
carry traffic across the enterprise Backbone Layer
backbone.
• Middle-speed routers can connect Access
buildings at each campus and Layer
switches connects user devices
and servers within building.

Building C-1 Building C-2

15
Hierarchical Topology:
• A core layer of high-end routers and switches (MLS- catalyst 3800 and
above) that are optimized for availability and speed.
• A distribution layer of routers and switches (MLS- catalyst 3560 and
above) that implement policies and segment traffic.
• An access layer that connects users via lower end switches (catalyst
2960- 24 or 48 port), and wireless AP.

16
Hierarchical Network Levels
 Access
 The access layer is where workstations connect to hubs/switches
 The access layer can include router, switches, bridges, shared-
media hubs, wireless access point.
 For internetworks that include small branch offices, the access
layer can provide access into the corporate
 VLANs may be used to create separate broadcast domains at this
level
 With a layered design, a failure in an access layer device will only
affect those devices directly attached to it
 In multistory building for example, each floor would be isolated
this way

17
Hierarchical Network Levels
• Distribution
• Is the separation point between the access and core layers of
the network.
• Has many roles –
• control access to resource for security reason
• control network traffic that traverses the core for performance reason.
• This layer defines broadcast domain.
• Allow the core layer to connect sites that run different protocols.
• To improve routing protocol performance, this layer can
summarize routes from the access layer.

18
Hierarchical Network Levels
• Core
• The high-speed backbone of the internetwork.
• It is critical for connectivity- need to design with redundancy.
• When configure routers in this layer- should use routing features that
optimize packet throughput.
• Should avoid packet filters that will slow down the packet.

19
Why Use a Hierarchical Model?
• Reduces workload on network devices
• Avoids devices having to communicate with too many other devices
• The workload required of the CPUs on the devices can be burdensome.
• Example in large flat (switched) network , broadcast packets are giving trouble- broadcast
packet interrupts the CPU on each device within the broadcast domain and demands
processing time on every device
• Design a modular topology that limits the number of communicating routers-reduce router
advertisements.
• Minimize costs- purchase the appropriate devices for each layer of the hierarchy
• Enable accurate capacity planning within each layer of the hierarchy-reducing wasted bandwidth.
• Modularity enables user to design network with simple and easy to understand .
• Simplicity – minimize the need for extensive training for network operation.
• Facilitates changes- as elements in a network require change, the cost pf upgrading the network may
just be based on one small subset out of the overall network.

20
Hierarchical vs. Flat Topology

Sem 1-1617 21
Flat Network
• With a flat network design, there is no hierarchy.
• In a flat network all connecting devices are on the same level

22
Flat Network design
• No hierarchy
• Flat is adequate for a very small network
• Each interconnecting device has essentially the same job
• The network is not divided into layers or modules
• Easy to design and implement, maintain as long as it is small.
• Not suit for big network since lack of hierarchy make troubleshooting
difficult- need to inspect entire network

23
 Flat Versus Hierarchy
Flat WAN topologies:
• WAN for small company can have few sites connected in a loop.
• Each site has a WAN router that connects to 2 other adjacent sites via
point-to-point links.
• When more than 1 link fails, some sites will be isolated.
Headquarters in
Headquarters in Grants Pass
Medford
Medford Branch Office

Klamath Falls Ashland

Grants Pass Klamath Falls Ashland White City
Branch Office Branch
Branch Branch Office Branch Branch Office
Office
Office Office
24
Flat Loop Topology Hierarchical Redundant Topology
LAN Flat topology:
The typical architecture for a small LAN is workstations, printers, and
servers attached to one or more hubs or to a small switch in a flat topology.

25
Flat LAN
• The workstations, printers, and servers here use a MAC process, and handles a data
type known as frames. When a frame is received, it is amplified and then
transmitted on to the port of the destination PC.
• Network devices at LAN:
• Hubs (dumb device) work at physical layer (Layer 1) –
• broadcast to every one of its ports.
• A lot of traffic on the network and lead to poor network response times (degrade
performance). i.e 100Mbps hub must share its bandwidth with each and every one
of its ports
• COLLISION DOMAINS
• Switches (intelligence device) work at data link layer (Layer 2) –
• MAC addresses table of all the devices connected to it. Thus, when a frame is
received, it knows exactly which port to send it to.
• allocate a full 100Mbps to each of its ports the network is segmented into
• BANDWIDTH DOMAINS
26
Mesh vs. Hierarchical Topology

Sem 1-1617 27
 Mesh topologies
• Network designer recommend mesh topology to meet availability
requirements. 2 types of mesh topologies:
Full mesh Partial mesh
Every router /switch is connected to every other Has fewer connection
router/switch
Provide complete redundancy, good
performance

28
Problem with mesh topology – if NOT
designed carefully
• Expensive to deploy and maintain
• Hard to optimize, troubleshoot and upgrade if NOT design with simple
hierarchical model.
• Have scalability limits for groups of routers that broadcast routing updates.
• Rule of thumb- ND should keep broadcast traffic at less than 20% of the traffic on
each link.
• This rule limits the number of adjacent routers that can exchange routing tables and
routing updates.

**A hierarchal design, by its very nature, limits the number of router
adjacencies.

29
A Partial-Mesh Hierarchical Design

Headquarters
(Core Layer)

Regional
Offices
(Distribution
Layer)

Branch Offices (Access Layer)

30
A classic hierarchical and redundant enterprise design for a routed network
Guidelines for Hierarchical Network Design
• 1st Guideline –
Control the diameter of a hierarchical enterprise network topology.
• In most cases, 3 major layers are sufficient.
• Core, Distribution, Access
• Why need to control the diameter?
• It will provides low and predictable latency.
• Help predicting the routing paths, traffic flows and capacity requirements.
• It also make troubleshooting and network documentation easier.

31
 Continue..
• 2nd Guideline –
Strict control of the network topology at the
access layer should be maintained.
• The access layer is the most susceptible to
violations since user have a tendency to add
networks to the internetwork inappropriately. E.g.:
1. A network admin at a branch office might connect the
branch network to another branch, adding a fourth
layer (aka adding a chain), a common mistake.
2. A backdoor is a connection between devices in the
same layer (can be extra router, switch or bridge) to
connect two network. It can cause unexpected routing
and switching problem and make network
documentation and troubleshooting more difficult.
32
Continue..
• Finally- design the access layer first, followed by distribution layer
then the core layer.
• Why access layer?
• Can accurately perform capacity planning for the distribution and core layers.
• Can also recognize the optimization techniques you will need for the
distribution and core layers.

33
 Redundant Network Design Topologies
• Redundant Network - Meet network
availability requirement
• How ?
• Duplicating the network elements (duplicate
equipment and redundant path)
• The goal for redundancy – to eliminate any
single point of failure on the network by
duplicate any required component whose
failure could disable critical applications.
• Components: core router , switch , a link
between two switches , a power supply
etc….
34
Where to implement RNDT
• Inside campus networks
• Meet availability goals for users
accessing local services
• Between layers of the
hierarchical model
• On the edge of the enterprise
network to ensure high
availability for Internet, extranet
and VPN access.

35
Drawback of redundancy
• Add complexity
• To the network topology
• To network addressing
• To routing

36
Why Redundant Network
BACKUP PATH
• Need to have backup path for packet to travel when primary link is down.
• Backup path have duplicates devices and link as in primary path.
• 2 aspects of the backup path that we need to look into:
• How much capacity the backup path supports
• How quickly the network will begin to use the backup path

LOAD SHARING
• Second goal for redundant network is to improve performance by supporting
load sharing across parallel links.
• Load sharing/load balancing – allows two or more paths to share the traffic
load.
37
Internetworking Devices

Sem 1-1617 38
Switch Platforms
• Select form factor:
• Fixed
• Modular
• Stackable
• Non-stackable
• Port density
• Forwarding rate –
24-port Gigabit Ethernet switch capable to
switching 24Gb/s of traffic
• Power over Ethernet
• MLS –
• Deployed in the core and distribution
layers of an organization’s switched
network.
• Can build a routing table, support a few
routing protocols, and forward IP packets.
Router Requirements
Role of routers:
• Interconnect multiple sites
• Provide redundant paths
• Connect ISPs
• Translate between media types
and protocols
Devices and Domain
• Routers separate broadcast and collision domain.
• Switches separate collision domains.
• Hubs belong to one collision domain
• Switches and hubs both belong to one broadcast domain

41
Example : BD and CD
• Draw in class – Wednesday activity