Contribution by Each Member:

Inamul Haque: Designed the physical and Logical Topology, Analyzed the traffic flow, proposed the
Topological model and Architectural Model, Multicasting Configuration, Security Analysis and
implementation, Test cases and Troubleshooting.

Dharnidhar Vairagi: Analyze the company requirements, Proposal for the Architecture, Planning the
IP addresses, created the Autonomous system's considering the fulfillment of company’s
requirements, OSPF configuration, BGP configuration.

Chapter: 1

1.1 Problem Statement

1.2 Functional
1.2.1Non-Functional Requirements
1.3 Constraints
1.4 Risks
1.5 Protocols
1.1 Problem Statement: For its technological consulting services, Deep Tech Inc. wants a reliable
and expandable computing and networking infrastructure. To accommodate two more
branches, the current LAN infrastructure, which consists of a headquarters and a branch, must
be expanded. Deep Tech plans to implement multicasting, cloud services, VoIP, IoT, and WAN
connectivity to satisfy client expectations. With this growth, Deep Tech will be able to provide
cutting-edge solutions to its clients and promote fluid cooperation between staff members and
partners. It will also ensure seamless real-time communication, secure data management, and
efficient operations.

1.2 Functional requirements:

a. Multicasting: Enable effective distribution of real-time data for improved communication,
including video conferencing and multimedia streaming.
b. Cloud Services: For data analytics, scalable storage, and application hosting, connect to
various cloud service providers.
c. VoIP: Use VoIP technology to provide feature-rich and cost-effective telephony services, such
as VoIP phones and unified communications solutions.
d. Internet of Things: Use IoT devices to automate and monitor processes. These devices need
network access and administration to send data securely.
e. WAN Services: Set up an appropriate WAN solution to link various offices and remote
workers.

1.2.1 Non-Functional Conditions:

a. Security: Protect against cyber threats, implement strong access control, and ensure data
security.
b. Scalability: Create the network with the ability to accommodate future client and service
growth without sacrificing performance.
c. Reliability: To ensure network availability and reduce downtime, implement redundancy and
failover mechanisms.
d. Network performance should be optimized to cut down on latency and provide smooth real-
time communication.
e. Manageability: Offer effective network administration tools for simple monitoring and setup.
1.3 Constraints:
a. To meet financial constraints, the project must stay within the allotted budget.
b. Timeline: In order to satisfy corporate goals and customer needs, the network expansion
must be finished within the allotted time frame.
c. Integration with Existing Infrastructure: The design must work with the current leased line
connection and LAN infrastructure.

1.4 Risks:
a. Integration Challenges: Adding new services to an existing network can present compatibility
problems and necessitate careful planning.
b. Security Vulnerabilities: Setting up IoT devices and connecting to cloud services can pose
security issues that need to be addressed.
b. Network Performance: If left unattended, poor network performance may have an impact on
real-time communication and user experience.

The following architectural choices are made:

a. OSPF and BGP: Use OSPF as the underlay protocol for effective intra-domain routing and BGP
as the overlay protocol for inter-domain communication and internet connectivity.
b. VLANs: Use VLANs to logically segment your network, improving both security and
performance.
c. Addressing: For end-user devices and essential network components, employ dynamic
addressing and static addressing, respectively, to ensure scalability and stability.
d. QoS: Implement quality of service to give real-time traffic priority and guarantee high-quality
communication services.
 Hierarchical
Architecture

FlowNet, Service
Data’s privacy Provider,
Central DC

Architecture
Model

Rationale:
a. OSPF and BGP were selected because they are effective for intra- and inter-domain routing,
respectively, ensuring the best network performance.
b. By isolating traffic, VLANs offer network segmentation, boosting security and performance.
c. Critical equipment are given stability through static addressing, but end-user devices are
given flexibility and scalability through dynamic addressing.
d. Real-time traffic is given priority by QoS, guaranteeing that internal teams and clients receive
dependable and effective communication.
1.5 Protocols
OSPF: (why we are using ): OSPF (Open Shortest Path First) is an interior gateway protocol (IGP)
used in computer networks for efficient routing within an autonomous system (AS). OSPF
employs a link-state algorithm to calculate the shortest paths to different destinations, ensuring
optimal packet forwarding. By exchanging link-state advertisements (LSAs), OSPF routers build a
topological database, allowing them to respond quickly to network changes and converging on
the best paths. OSPF supports route summarization, load balancing, and hierarchical area
structures, making it scalable and well-suited for large networks. Its fast convergence,
multicasting, and security features make OSPF a reliable choice for Deep Tech's network
expansion, providing robust and adaptive routing.

BGP: (why we are using) : BGP (Border Gateway Protocol) is an exterior gateway protocol used
in Deep Tech's network expansion. It serves as the backbone of the internet, facilitating
communication between different autonomous systems (AS). BGP enables routers in different
ASes to exchange routing information, allowing data to traverse multiple networks, ensuring
global reachability, and enabling internet connectivity for Deep Tech's clients. By using BGP,
Deep Tech can establish reliable inter-domain routing, manage traffic efficiently between ASes,
and connect to various ISPs and cloud service providers, enabling seamless data exchange,
scalability, and robust network connectivity for its growing technology consulting services.
IOT: (why we are using): IoT (Internet of Things) refers to a network of interconnected devices
and objects that can collect, exchange, and process data over the internet. In Deep Tech, IoT
plays a crucial role in their network expansion. By deploying IoT devices for monitoring and
automation purposes, Deep Tech enhances operational efficiency and facilities management.
IoT devices securely gather real-time data, enabling remote monitoring and control, optimizing
operations, and offering cutting-edge services to clients. The data collected from IoT devices can
be analyzed for insights, providing strategic guidance to clients and supporting data-driven
decision-making. IoT's integration in Deep Tech's network empowers them to provide innovative
technology solutions and deliver seamless and intelligent services.

Multicasting: (why we are using): The act of simultaneously delivering data from one source to
numerous recipients is referred to as multicasting. Multicasting is crucial for effectively
disseminating real-time data, such video conferencing and multimedia streaming, in Deep
Tech's network expansion. Deep Tech guarantees efficient one-to-many or many-to-many
communication employing multicasting capabilities, reducing network congestion and
maximizing bandwidth utilization. This makes it possible to give real-time communication
services of the highest caliber to clients and internal teams. Since multicasting offers a wide
range of applications, such as multimedia streaming for webinars, virtual meetings, and online
collaboration tools, Deep Tech is able to provide its broad clients with feature-rich and cutting-
edge technological solutions. The act of simultaneously delivering data from one source to
numerous recipients is referred to as multicasting. Multicasting is crucial for effectively
disseminating real-time data, such video conferencing and multimedia streaming, in Deep
Tech's network expansion. Deep Tech guarantees efficient one-to-many or many-to-many
communication employing multicasting capabilities, reducing network congestion and
maximizing bandwidth utilization. This makes it possible to give real-time communication
services of the highest calibers to clients and internal teams. Since multicasting offers a wide
range of applications, such as multimedia streaming for webinars, virtual meetings, and online
collaboration tools, Deep Tech is able to provide its broad clients with feature-rich and cutting-
edge technological solutions.
CHAPTER: 2
2.1 IP Addressing Scheme
2.2 Physical and Logical Topology Diagram
2.3 Configuration steps for Layer 2 and Layer 3 protocols

2.1 IP Addressing Scheme

IP addressing is a foundational aspect of networking architecture that enables devices to
communicate with each other across networks. It ensures data packets are sent to the correct
destination, and it forms the basis for efficient and scalable network communication in both
local and global contexts.
Each device connected to a network is given a specific number label through IP addressing. This
label, sometimes referred to as an IP address, serves as the device's location and identification.
IP addresses are used by devices to identify the source and destination of data when they want
to share it.
Uniqueness: Every device connected to a network needs a different IP address. Data is
transferred to the intended recipient without interference because to this uniqueness.
Logical Addressing: IP addresses are logical addresses, meaning they are assigned based on the
network's logical structure, independent of the physical hardware of the devices. This
abstraction allows networks to be organized efficiently and makes routing of data possible.
Subnetting: IP addresses are often divided into subnets, which are smaller, logically grouped
segments of a larger network. Subnetting allows for better network management, security, and
efficient use of IP address space.
Routing: Routers play a crucial role in IP-based networks. They examine the IP addresses of
incoming data packets and use routing tables to determine the best path for forwarding the
packets to their intended destinations.
2.2 Physical and Logical Topology Diagram

2.3 Configuration steps for Layer 3 protocols

Assignment of IP addresses:
Router1: 155.1.2.1, 155.1.3.1, 155.1.4.1, 150.1.1.1
Reouter2: 155.1.2.2, 155.1.3.2, 155.1.4.2, 150.1.2.2
Router3: 155.1.2.3, 155.1.3.3, 150.1.3.3
Router4: 155.1.2.4, 155.1.3.4, 155.1.4.4, 150.1.4.4
Router5: 155.1.2.5, 155.1.3.5, 150.1.5.5
Router6: 155.1.2.6, 155.1.3.6, 150.1.6.6
Router7: 155.1.2.7, 155.1.3.7, 155.1.4.7, 150.1.7.7
Router8: 155.1.2.8, 155.1.3.8, 155.1.4.8, 150.1.8.8
Router9: 155.1.2.9, 155.1.3.9, 155.1.4.9, 150.1.9.9

Switch S1: 15 vlan trunk port

Switch S2: 10 vlan trunk port
Switch S3: 15 vlan trunk port
Switch S4: 10 vlan trunk port
Switch S5: 15 vlan trunk port
Switch S6: 10 vlan trunk port

Interfaces Configuration:

Router1:
Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.1 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.1 255.255.255.0
int g1.4
encapsulation dot1q 4
ip address 155.1.4.1 255.255.255.0
interface loopback 0
ip address 150.1.1.1 255.255.255.255
Router ospf 1
Router-id 150.1.1.1
Network 150.1.1.1 0.0.0.0 area 0
Network 155.1.2.1 0.0.0.0 area 0
Network 155.1.3.1 0.0.0.0 area 0
Network 155.1.4.1 0.0.0.0 area 0

Router bgp 111

Bgp router-id 150.1.1.1
No synchronization
No auto-summary
Neighbor 150.1.2.2 remote-as 111
Neighbor 150.1.2.2 update-source lo0
Neighbor 150.1.2.2 next-hop-self
Neighbor 150.1.3.3 remote-as 111
Neighbor 150.1.3.3 update-source lo0
Neighbor 150.1.3.3 next-hop-self
Neighbor 155.1.2.7 remote as 222
Neighbor 155.1.2.4 remote as 333

IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode
int g1.4
ip pim sparse-mode

Router2:

Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.2 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.2 255.255.255.0
int g1.4
encapsulation dot1q 4
ip address 155.1.4.2 255.255.255.0
interface loopback 0
ip address 150.1.2.2 255.255.255.255

Router ospf 1
Router-id 150.1.2.2
Network 150.1.2.2 0.0.0.0 area 0
Network 155.1.2.2 0.0.0.0 area 0
Network 155.1.3.2 0.0.0.0 area 0
Network 155.1.4.2 0.0.0.0 area 0

Router bgp 111

Bgp router-id 150.1.2.2
No synchronization
No auto-summary
Neighbor 150.1.1.1 remote-as 111
Neighbor 150.1.1.1 update-source lo0
Neighbor 150.1.1.1 next-hop-self
Neighbor 150.1.3.3 remote-as 111
Neighbor 150.1.3.3 update-source lo0
Neighbor 150.1.3.3 next-hop-self

IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode
int g1.4
ip pim sparse-mode

ip pim rp address 150.1.1.1

Int g1.4
Ip igmp join-group 224.1.1.1
Router3:
Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.3 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.3 255.255.255.0
interface loopback 0
ip address 150.1.3.3 255.255.255.255

Router ospf 1
Router-id 150.1.3.3
Network 150.1.2.3 0.0.0.0 area 0
Network 155.1.2.3 0.0.0.0 area 0
Network 155.1.3.3 0.0.0.0 area 0

Router bgp 111

Bgp router-id 150.1.3.3
No synchronization
No auto-summary
Neighbor 150.1.1.1 remote-as 111
Neighbor 150.1.1.1 update-source lo0
Neighbor 150.1.1.1 next-hop-self
Neighbor 150.1.2.2 remote-as 111
Neighbor 150.2.2 update-source lo0
Neighbor 150.1.2.2 3 next-hop-self

IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode

ip pim rp address 150.1.1.1

Int g1.3
Ip igmp join-group 224.1.1.1

Router4:

Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.4 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.4 255.255.255.0
int g1.4
encapsulation dot1q 4
ip address 155.1.4.4 255.255.255.0
interface loopback 0
ip address 150.1.4.4 255.255.255.255

Router ospf 1
Router-id 150.1.4.4
Network 150.1.4.4 0.0.0.0 area 0
Network 155.1.2.4 0.0.0.0 area 0
Network 155.1.3.4 0.0.0.0 area 0
Network 155.1.4.4 0.0.0.0 area 0

Router bgp 111

Bgp router-id 150.1.4.4
No synchronization
No auto-summary
Neighbor 150.1.5.5 remote-as 333
Neighbor 150.1.5.5 update-source lo0
Neighbor 150.1.5.5 next-hop-self
Neighbor 150.1.6.6 remote-as 333
Neighbor 150.1.6.6 update-source lo0
Neighbor 150.1.6.6 next-hop-self
Neighbor 155.1.3.1 remote-as 111
IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode
int g1.4
ip pim sparse-mode

Router5:

Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.5 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.5 255.255.255.0
interface loopback 0
ip address 150.1.5.5 255.255.255.255
Router ospf 1
Router-id 150.1.5.5
Network 150.1.5.5 0.0.0.0 area 0
Network 155.1.2.5 0.0.0.0 area 0
Network 155.1.3.5 0.0.0.0 area 0
Network 155.1.4.5 0.0.0.0 area 0

Router bgp 111

Bgp router-id 150.1.5.5
No synchronization
No auto-summary
Neighbor 150.1.4.4 remote-as 333
Neighbor 150.1.4.4 update-source lo0
Neighbor 150.1.4.4 next-hop-self
Neighbor 150.1.6.6 remote-as 333
Neighbor 150.1.6.6 update-source lo0
Neighbor 150.1.6.6 next-hop-self
IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode

ip pim rp address 150.1.4.4

Int g1.3
Ip igmp join-group 224.1.1.1

Router6:
Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.6 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.6 255.255.255.0
interface loopback 0
ip address 150.1.6.6 255.255.255.255

Router ospf 1
Router-id 150.1.2.2
Network 150.1.2.2 0.0.0.0 area 0
Network 155.1.2.2 0.0.0.0 area 0
Network 155.1.3.2 0.0.0.0 area 0
Network 155.1.4.2 0.0.0.0 area 0

Router bgp 333

Bgp router-id 150.1.6.6
No synchronization
No auto-summary
Neighbor 150.1.4.4 remote-as 333
Neighbor 150.1.4.4 update-source lo0
Neighbor 150.1.4.4 next-hop-self
Neighbor 150.1.5.5 remote-as 333
Neighbor 150.1.5.5 update-source lo0
Neighbor 150.1.5.5 next-hop-self

IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode

ip pim rp address 150.1.4.4

Int g1.3
Ip igmp join-group 224.1.1.1

Router7:
Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.7 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.7 255.255.255.0
int g1.4
encapsulation dot1q 4
ip address 155.1.4.7 255.255.255.0
interface loopback 0
ip address 150.1.7.7 255.255.255.255

Router ospf 1
Router-id 150.1.7.7
Network 150.1.7.7 0.0.0.0 area 0
Network 155.1.2.7 0.0.0.0 area 0
Network 155.1.3.7 0.0.0.0 area 0
Network 155.1.4.7 0.0.0.0 area 0

Router bgp 111

Bgp router-id 150.1.2.2
No synchronization
No auto-summary
Neighbor 150.1.8.8 remote-as 222
Neighbor 150.1.8.8 update-source lo0
Neighbor 150.1.8.8 next-hop-self
Neighbor 150.1.9.9 remote-as 222
Neighbor 150.1.9.9 update-source lo0
Neighbor 150.1.9.9 next-hop-self
Neighbor 155.1.4.1 remote-as 111

IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode
int g1.4
ip pim sparse-mode
Router8:

Router1:
Interface g1
no shutdown
int g1.2
encapsulation dot1q 2
ip address 155.1.2.8 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.8 255.255.255.0
int g1.4
encapsulation dot1q 4
ip address 155.1.4.8 255.255.255.0
interface loopback 0
ip address 150.1.8.8 255.255.255.255

Router ospf 1
Router-id 150.1.8.8
Network 150.1.8.8 0.0.0.0 area 0
Network 155.1.2.8 0.0.0.0 area 0
Network 155.1.3.8 0.0.0.0 area 0
Network 155.1.4.8 0.0.0.0 area 0

Router bgp 222

Bgp router-id 150.1.8.8
No synchronization
No auto-summary
Neighbor 150.1.7.7 remote-as 222
Neighbor 150.1.7.7 update-source lo0
Neighbor 150.1.7.7 next-hop-self
Neighbor 150.1.8.8 remote-as 222
Neighbor 150.1.8.8 update-source lo0
Neighbor 150.1.8.8 next-hop-self

IP multicasting-routing distributed
Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode
int g1.4
ip pim sparse-mode

ip pim rp address 150.1.7.7

Int g1.4
Ip igmp join-group 224.1.1.1

Router9:

Router1:
Interface g1
no shutdown

int g1.2
encapsulation dot1q 2
ip address 155.1.2.9 255.255.255.0
int g1.3
encapsulation dot1q 3
ip address 155.1.3.9 255.255.255.0
interface loopback 0
ip address 150.1.9.9 255.255.255.255

Router ospf 1
Router-id 150.1.9.9
Network 150.1.9.9 0.0.0.0 area 0
Network 155.1.2.9 0.0.0.0 area 0
Network 155.1.3.9 0.0.0.0 area 0

Router bgp 222

Bgp router-id 150.1.9.9
No synchronization
No auto-summary
Neighbor 150.1.8.8 remote-as 222
Neighbor 150.1.8.8 update-source lo0
Neighbor 150.1.8.8 next-hop-self
Neighbor 150.1.7.7 remote-as 222
Neighbor 150.1.7.7 update-source lo0
Neighbor 150.1.7.7 next-hop-self
IP multicasting-routing distributed

Int g1.2
ip pim sparse-mode
int g1.3
ip pim sparse-mode
ip pim rp address 150.1.1.1

Int g1.3
Ip igmp join-group 224.1.1.1

Troubleshooting:

Using these commands allows network administrators to quickly access and review the OSPF
and BGP configurations, making it easier to identify any misconfigurations, discrepancies, or
potential issues that may be impacting OSPF or BGP operations. By comparing the actual
configurations to the desired configurations, administrators can pinpoint the root cause of the
problem and take appropriate troubleshooting steps to resolve it.
Sh run | sec ospf
Sh run | sec bgp

Validation:

Commands are used for validation:

Ping R1 to R2 and R3 to check connectivity.

Ping R4 to R5 and R6 to check connectivity.
Ping R7 to R8 and R9 to check connectivity.

By executing these ping commands, Deep Tech Inc. can validate the connectivity between
specific routers and ensure that the network expansion has been properly implemented. If any
ping tests fail, further troubleshooting and investigation would be required to identify and
resolve the connectivity issues.

Sh ip route
Sh ip ospf
Sh ip ospf neighbor
Sh ip ospf database
Sh ip bgp
Sh ip route bgp
Sh ip mroute
Sh ip pim neighbor
Sh ip pim interface

Router# show run | sec bgp

router bgp 111

bgp log-neighbor-changes
neighbor 192.168.1.1 remote-as 65002
neighbor 192.168.1.1 description Neighbor_to_RouterB
neighbor 192.168.1.1 next-hop-self
neighbor 192.168.1.2 remote-as 65003
neighbor 192.168.1.2 description Neighbor_to_RouterC
maximum-paths 4
redistribute connected
redistribute static
no synchronization
no auto-summary

ip route 10.0.0.0 255.0.0.0 Null0

ip route 192.168.1.0 255.255.255.0 192.168.2.1
ip route 192.168.1.0 255.255.255.0 192.168.3.1