UNIVERSITY ON NAIROBI Backbone Network Proposal

1
UNIVERSITY ON NAIROBI Backbone Network Proposal

• UON ICT Center
• By H. N. Njeru, May-2006

2
Backbone Network ProposalContents

• Background
• Current Challenges
• Backbone Network Objectives
• Design Criteria
• Design Architecture
• Design Requirements
• Proposal Specification
• Other Proposal Requirements

3
Existing Backbone Network Core Backbone,
Chiromo-Main
4
Existing Backbone Network Inter-Campus Wireless
Network
5
Existing Backbone Network Inter-Campus
Wireless Network
6
Existing Backbone Network Chiromo Campus Network
7
Existing Backbone Network CHS Campus Network
8
Existing Backbone Network CAVS Campus Network
9
Existing Backbone NetworkCEES Campus Network
10
Existing Backbone Net Challenges

• Policy, Standards and Management 3-Tier model,
  IP over Ethernet
• Security VLANs, Firewall, IDS/IPS, IPSec, SSL,
  SSH
• Frequent Down-Times and Low QOS on Inter-Campus
  Network
• Equipment Redundancy
• Route Diversity

11
Backbone Network Objectives

• Network infrastructure plays a key role in
  delivery of ICT services in any organization
• Achieve network resiliency, availability, and
  stability through infrastructure consolidation
  and virtualization on Ethernet and IP
  technologies
• Deliver a reliable, available, scalable, and
  protected solution that enables growth without
  business interruption

12
Backbone Network Objectives..

• Network infrastructure plays a key role in
  delivery of ICT services in any organization..
• Support growth with a scalable and adaptive
  network infrastructure that enables flexibility
  and support for emerging technology adoption
• Improve security, manageability and quality of
  service

13
Backbone Network Design Principles

• Based on Modular Design
• Simplifies Management
• Hierarchical Network Design
• Enhance Security
• Three Tier Model
• Core layer
• Distribution layer
• Access layer

14
Backbone Network Design Architecture

• Hierarchical Design Model
• Core Layer
• Distribution Layer
• Access Layer

15
Backbone Network Design Architecture

• Hierarchical Design Model
• Hierarchy Each layer has specific role.
• Modularity Networks are built using building
  blocks, which are easy to replicate, redesign,
  and grow
• The hierarchical design model divides network
  into three (3) functional tiers as follows
• Core
• Distribution
• Access

16
Backbone Network Design Architecture

• Core layer Provides high-speed transport between
  distribution-layer devices and to core resources
• Distribution layer Implements the organization's
  policies, and provides connections between
  workgroups and between the workgroups and the
  core
• Access layer Provides user and workgroup access
  to the resources of the network

17
Backbone Network Design Architecture
The Hierarchical Network Design Model Separates
the Network into Three Functions
18
Backbone Network Design Architecture

• Core Layer Functions
• The core layer provides a high-speed backbone.
  Functions and attributes of the core layer
  include the following
• Providing high-speed, low-latency links and
  devices for quick transport of data across the
  backbone.
• Providing a highly reliable and available
  backbone. This is accomplished by implementing
  redundancy in both devices and links so that no
  single points of failure exist.
• Adapting to network changes quickly by
  implementing a quick-converging routing protocol.
  The routing protocol can also be configured to
  load-balance over redundant links so that the
  extra capacity can be used when no failures
  exist.
• Filtering is not performed at this layer,
  because it would slow processing. Filtering is
  done at the distribution layer.

19
Backbone Network Design Architecture

• Distribution/Aggregation Layer Functions
• The distribution layer interfaces between the
  core and access layers, and between access layer
  workgroups. Functions include
• Implementing policies by filtering, and
  prioritizing and queuing traffic.
• Routing between the access and core layers
• Performing route summarization
• Providing redundant connections, both to access
  devices and to core devices.
• Aggregating multiple lower-speed access
  connections into higher-speed core connections

20
Backbone Network Design Architecture

• Access Layer Functions
• The access layer is where users access the
  network. Users can be local or remote.
• Local users typically access the network through
  connections to a switch.
• Remote users might access the network through the
  Internet, RAS using VPN connections
• The access layer must also ensure that only users
  who are authorized to access the network are
  admitted (Security-NAS).

21
Backbone Network Design Architectural
Requirements

• Availability
• Security
• Quality Of Service
• Manageability
• Performance
• Scalability
• Inter-Operability

22
Backbone Network Design Architectural
Requirements

• Availability
• HA design to ensure network has no single points
  of
• failure on critical links or systems, and should
  failover
• in a way that is transparent to users.
• Availability Level
• MTBF
• Redundancy
• Redundant hardware
• Redundancy software features
• Automatic procedures network paths fail -over

23
Backbone Network Design Architectural
Requirements

• AvailabilityRedundancy
• While redundancy is crucial to designing a highly
  available network, too much redundancy can
  actually prove detrimental to a network.
• The bidder shall explain how the bidded device
  resolves issues of convergence such as the
  networks ability to recover from bad link.
• Too much redundancy can complicate
  troubleshooting and management. The Bidder shall
  explain how the devices will avoid this.

24
Backbone Network Design Architectural
Requirements

• Security
• Routing instead of switching (VLAN)
• Firewalls
• IDS/IPS
• VPN IPSec
• SSL

25
Backbone Network Design Architectural
Requirements

• Security Routing at Core
• While VLAN organizes physically separate users
  into the same broadcast domain t it is not as
  effective as routing.
• Routing at Core improves performance, security,
  and flexibility.
• Also decreases the cost of arranging users
  because no extra cabling is required

26
Backbone Network Design Architectural
Requirements

• Quality of Service (QOS)
• In converged networks, real time traffic must
• be given preferential treatment over regular
• data traffic through QOS in these areas
• Packet Loss, Delay and Jitter
• Admission Control
• Traffic Classification and marking
• Traffic Policing and Shaping
• IP Multicast and MPLS

27
Backbone Network Design Architectural
Requirements

• QOS IP Multicast
• IP multicast technology allows data to be
  transmitted from a single source to multiple
  destinations simultaneously.
• Unlike broadcast traffic, which indiscriminately
  transmits data to all users on a network, IP
  multicast only transmits data to a defined group
  of intended recipients identified by a single IP
  address)

28
Backbone Network Design Architectural
Requirements

• QOS MPLS
• Packet forwarding technology
• Integrates performance and traffic management
  Advantages
• Improving the L3 (IP) services by switching
• Improve packet forwarding By using Label instead
  of Lookup tables
• Support QoS for service differentiation
• Supports network scalability
• Help build interoperable networks

29
Backbone Network Design Architectural
Requirements

• QOS Oversubscription
• Oversubscription occurs when there are more
  traffic generating endpoints than the network can
  accommodate at a single time. Most networks are
  built with some amount of oversubscription.
• When this occurs QoS should be used to ensure
  real-time traffic such as voice and video, or
  critical data is not dropped or delayed

30
Backbone Network Design Architectural
Requirements

• Manageability
• Network management is key to reducing
• the overall Total cost of Ownership (TCO)
• Performance Management
• Configuration Management
• Security Management
• Fault Management
• Remote management
• NMS Inter-Operability

31
Backbone Network Design Architectural
Requirements

• Performance
• The Network Backbone must have the ability to
  provide high speed and low-latency that is
  critical to business continuance.
• Scalability
• A system whose performance improves after adding
  hardware, proportionally to the capacity added.

32
Backbone Network Design Architectural
Requirements

• Inter-Operability
• Conformance to recognised international relevant
  standards in the area of networking
• The offered system shall offer IP Version 6 as
  well as the current used IPv4.
• IPv6 shall meet future demand for globally unique
  IP addresses, eliminates NAT, inbuilt IPSec,
  hierarchical support..

33
Proposed Network BackboneCore Backbone Net
Access
UON CORE BACKBONE
MAIN CAMPUS
10GE
SWA
CHIROMO CAMPUS
34
Proposed Network BackboneCore Backbone Net
Access
35
Proposed Network BackboneCore Backbone Network

• Provide High Availability 10 GE IP Routing
  Backbone
• Diversity Fibre Route as follows
• Main Campus Chiromo Campus
• Chiromo-UNES-UHS-SWA-Main Campus
• Enhance Core BB Fibre Network from 4-core to
  12Core to also carry Data Center traffic
• Install 12-Core Fibre between Chiromo-UNES-SWA
  and Use Existing SWA-Main Campus and ADD-Main
  Campus Fibre to SWA get 8-Core

36
Proposed Network BackboneCore Backbone Network

• Install 3 High Performance Core Routers at Main,
  Chiromo and SWA, with redundant modules
• Provide Distributed Security on Core Inter-VLANs
  Firewalls, IDS/IPS, Distributed DOS, Secure
  Sockets Layer Services, SSL and IPSec on VPN
  Termination
• A Core that is highly Manageable

37
Proposed Network BackboneMain Campus Backbone
Net
38
Proposed Network BackboneMain Campus Backbone
Net

• Provide Traffic Aggregation at convenient points
  in Every Building in Main Campus
• Provide Gateway to Remote Campuses
• Provide Internet Access Point
• Provide Access to Disaster Recovery Data Center

39
Proposed Network BackboneChiromo Backbone
Network
40
Proposed Network BackboneChiromo Campus
Backbone Net

• Provide Traffic Aggregation at convenient points
  in All Buildings in Chiromo Campus
• Provide Access to Primary Data Center

41
Proposed Network BackboneSWA Backbone Network
42
Proposed Network BackboneChiromo Backbone
Network

• Provide Traffic Aggregation at convenient points
  in all Buildings around SWA
• Provide Diversity Route between Chiromo and Main
  Campus

43
Proposed Network BackboneUpper Lower Kabete
Link
44
Proposed Network Backbone Upper Lower Kabete
BBLink

• Provide Fibre Link Between two Campuses
• Will Reduce cost of Access to Core UON Backbone
• Only one route through Upper Kabete that is
  better placed for WAN Connectivity

45
Proposed Network BackboneDigital ?-Wave Net
Topology
46
Proposed Network BackboneDigital ?-Wave Net
Topology
47
Proposed Network BackboneDigital ?-Wave Net
Topology
CEES NETWORK
CVS NETWORK
LKC NETWORK
CHIROMO
MAIN
10 GE
CHS MICROWAVE STATION
SWA
CHS NETWORK
PARKLANDS NETWORK
CORE BACKBONE
48
Proposed Network BackboneDigital ?-Wave Network

• Remote Campuses Connectivity Network
• Provide High Capacity Digital Microwave Network
  between Main Campus and 5 Large Campuses
• Five Campuses CHS, CAVs, CEES, Commerce and Law
  (Parklands)
• Provide repeater station at CHS to facilitate
  Line-Of-Sight
• Link Capacities of Ethernet at 1 Gbps to each of
  the 5 Campuses that connect to Core BB at Main
  Campus

49
Proposed Network BackboneSpecification

• Core Switches
• Distribution Switches
• Fiber Cabling
• Gateway Router
• Digital Microwave Equipment

50
Proposed Network BackboneOther Proposal
Requirements

• Bidder and Equipment Assessment
• Training
• Project Implementation
• Maintenance and Support

51
Thank You All