Collision and broadcast domain Computer Network

Collision Domain –
A Collision Domain is a scenario in which when a device sends out a message to the network, all other devices
which are included in its collision domain have to pay attention to it, no matter if it was destined for them or not

Broadcast Domain –
A Broadcast Domain is a scenario in which when a device sends out a broadcast message, all the devices present in its
broadcast domain have to pay attention to it. This creates a lot of congestion in the network,
HUB: All the devices connected to a hub are in a single collision and single broadcast domain.
SWITCH – we have an advantage over the hub. Every port on a switch is in a different collision domain, i.e a switch
is a collision domain separator.
ROUTER –
A router not only breaks collision domains but also breaks broadcast domains, which means it is both
collisions as well as broadcast domain separators. A router creates a connection between two networks. A
broadcast message from one network will never reach the other one as the router will never let it pass.
 IP Addressing | Classless Addressing
The default mask in different classes are :

Class A – 255.0.0.0

Class B – 255.255.0.0

Class C – 255.255.255.0

Subnetting: Dividing a large block of addresses into several contiguous sub-blocks and assigning these
sub-blocks to different smaller networks is called subnetting
Example : Given IP Address – 172.16.0.0/25, find the number of subnets and the number of hosts per
subnet. Also, for the first subnet block, find the subnet address, first host ID, last host ID and broadcast
address.

Solution : This is a class B address. So, no. of subnets = 2(25-16) = 29 = 512.

No. of hosts per subnet = 2(32-25) – 2 = 27 – 2 = 128 – 2 = 126

 Routing protocol
What is Routing Protocol
The routing protocol is a type of network protocol that is responsible for sharing routing information among the
neighbor routers and finds the best possible and reliable path to forward the packet from source to destination
network.
 Open Shortest Path First
Open Shortest Path First (OSPF) is a routing protocol for Internet Protocol (IP) networks. It uses a
link state routing (LSR) algorithm and falls into the group of interior gateway protocols (IGPs), operating within a
single autonomous system (AS).
OSPF gathers link state information from available routers and constructs a topology map of the network. The
topology is presented as a routing table to the Internet Layer for routing packets by their destination IP address.
OSPF supports Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6) networks and supports
the Classless Inter-Domain Routing (CIDR) addressing model
 Open Shortest Path First
OSPF divides the network into routing areas to simplify administration and optimize traffic and resource utilization. Areas
are identified by 32-bit numbers, expressed either simply in decimal, or often in the same octet-based dot-decimal notation
used for IPv4 addresses.
 IS-SI
IS-IS is a link-state routing protocol, which means that the routers exchange topology information with their nearest
neighbors. The topology information is flooded throughout the AS, so that every router within the AS has a complete picture
of the topology of the AS. This picture is then used to calculate end-to-end paths through the AS, normally using a variant of
the Dijkstra algorithm. Therefore, in a link-state routing protocol, the next hop address to which data is forwarded is
determined by choosing the best end-to-end path to the eventual destination.

Similarities between OSPF and ISIS

Before going into the details of differences between OSPF and ISIS, let’s explore some similarities:

OSPF and ISIS both are Link State Routing Protocols using the Dijkstra SPF Algorithm.
Both are Interior Gateway Protocols (IGP) that distribute routing information between routers belonging to a single
Autonomous System (AS).
Both use Hello packets to create and maintain adjacencies between the neighboring routers.
Both the protocols are classless protocols and support classless Inter-Domain Routing (CIDR) and Variable Subnet
Length Masking (VLSM)
Both support Authentication Mechanism
Both support multipath.
Both support IP unnumbered links.
Differences between OSPF and ISIS protocols
 BGP
Border Gateway Protocol (BGP) is a standardized exterior gateway protocol designed to exchange routing and reachability
information among autonomous systems (AS) on the Internet.BGP is classified as a path-vector routing protocol, and it
makes routing decisions based on paths, network policies, or rule-sets configured by a network administrator.

BGP path selectin criteria

Before going into the details of differences between OSPF and ISIS, let’s explore some similarities:
 MPLS
Multi Protocol Label Switching (MPLS) is an IP packet routing technique that routes IP packet through paths via labels
instead of looking at complex routing tables of routers.
MPLS uses layer 3 service i.e, Internet Protocol, and uses router as forwarding device. The traffic of different customers is
separated from each other because MPLS works somewhat like VPN. It does not work like regular VPN that encrypts the
data but it ensures packet from one customer cannot be received by another customer. An MPLS header is added to packet
that lies between layers 2 and 3. Hence, it is also considers to be Layer 2.5
 MPLS
Multi Protocol Label Switching (MPLS) is an IP packet routing technique that routes IP packet through paths via labels
instead of looking at complex routing tables of routers.
MPLS uses layer 3 service i.e, Internet Protocol, and uses router as forwarding device. The traffic of different customers is
separated from each other because MPLS works somewhat like VPN. It does not work like regular VPN that encrypts the
data but it ensures packet from one customer cannot be received by another customer. An MPLS header is added to packet
that lies between layers 2 and 3. Hence, it is also considers to be Layer 2.5
 MPLS –L3vpn
In an MPLS Layer 3 VPN, routing occurs on the service provider's routers. The provider routers route and forward VPN
traffic at the entry and exit points of the transit network. The service provider network must learn the IP addresses of
devices sending traffic across the VPN and the routes must be advertised and filtered throughout the provider network. As
a result, Layer 3 VPNs require information about customer routes and a more extensive VPN routing and forwarding
(VRF) policy configuration than a Layer 2 VPN. This information is used to share and filter routes that originate or
terminate in the VPN.
 MPLS –L2vpn
The MPLS Layer 3 VPN requires more processing power on the provider edge (PE) routers than a Layer 2 VPN, because
the Layer 3 VPN has larger routing tables for managing network traffic on the customer sites. Route advertisements
originate at the customer edge (PE) routers and are shared with the inbound PE routers through standard IP routing
protocols, typically BGP. Based on the source address, the PE router filters route advertisements and imports them into the
appropriate VRF table.
VPWS (Virtual Private Wire Service) is Point-to-Point Layer 2 MPLS VPN Service of Nokia Service Routers
It provides Point-to-Point VPN Service and from the Customer point of view, it is like a Leased Line. With VPWS two sites of
customer are like directly connected as Point-to-Point.
 MPLS –L2vpn
A VPLS service provides connectivity between two or more SAPs on one
(local service) or more (distributed service) service routers.
 Health checkup command7250
show router 4 route-table 172.18.18.83 ----check route
show service service-using vprn --to show all vrf
show log log-id 99

enviro no more -----like clipaging in switch

admin display-config ----- configuration
show port
show user
show system alarms
show system time
Show system CPU
Show system information
 Health check up command 2
Show chassis environment
show router bfd session
show router bgp summary
show router isis adjacency
show router ospf neighbor
show router bgp neighbor
show router ldp session
show router ldp status
show service service-using vpls
show chassis
show router route-table
show router vrrp instance
show router arp
admin display-config | match ntp context all
 Health check up command 3
show card

show router 100000 ospf interface

show router 300000 ospf interface

show service service-using vprn

show router 100000 vrrp instance

show router 400000 interface

show system alarms

show service id 500101 base

show router 200000 route-table

show service id 400000 arp
show lag 1 detail
show port 1/3/2 detail
Health checkup command output
Health checkup command output
Health checkup command output
Health checkup command output
Health checkup command output
Health checkup command output
Health checkup command output
Health checkup command output
Safaricom Ethiopia network
Safaricom Ethiopia network
 Safaricom Ethiopia network
POC2 routers will also connect to Leaf routers of the Controllers Datacenter .
POC1 routers will connect to Border Edge routers of the Core Data Centers.
Each POC1 site will also host: o 1 IGW router that will function as network gate
towards other Service Providers for: ▪ Internet ▪ Roaming o 1 vRR (Virtual Route
Reflector), that will function as VPN route reflector for region.
Interconnection between different regions will be on POC1 routers. o Inter-AS
option A will be used o e-BGP will be the routing protocols on each VPN between
regions.
In each region, POC1 and POC2 routers will be part of the same IGP instance (IS-
IS-1 per region) • Each POC3 ring with its POC2 terminating routers, and all
attached POC4 routers will be part of the same IGP instance (IS-IS-x) • No
redistribution is performed between different IGP instances.
• Mobile Services: 2G, 3G, 4G, 5G, OAM o Mainly transported over multiple
L3VPNs • Enterprise services: VPNs for Safaricom Ethiopia business customers
that can require either L3 or L2 VPNs
Safaricom Ethiopia network
 Safaricom Ethiopia network
Interconnection between different regions will be on POC1 routers. o Inter-AS option
A will be used o e-BGP will be the routing protocols on each VPN between regions. •
In each region, POC1 and POC2 routers will be part of the same IGP instance (IS-IS-
1 per region) • Each POC3 ring with its POC2 terminating routers, and all attached
POC4 routers will be part of the same IGP instance (IS-IS-x) •
No redistribution is performed between different IGP instances. •
Routing between different IGP instances will be performed using BGP-LU •
In each IGP instance, Segment Routing (SR-ISIS and SR-TE) will be used for MPLS
transport. o So, LDP nor RSVP are not required and will not be used.
Core Datacenter Fabric is a based on a Leaf/Spine architecture, and has the following
elements: • Leaf routers: Routers physically connecting to Servers on the Datacenter,
and logically connecting to different VNFs. • Spine routers: Aggregation layer
interconnecting different Leafs between each other and connecting them to the
Border Edge • Border Edge: is the Gateway of the Datacenter towards the outside
Safaricom Ethiopia network
Safaricom Ethiopia network
Safaricom Ethiopia network
Safaricom Ethiopia network