0:00 - 1:00

Hello everyone. My name is “student name” , and today I'm going to walk

you through my network implementation project for QTerminals Logistics and

Cargo Tracking Centre.

In this video, I'll show you the complete network I designed and implemented

using Cisco Packet Tracer. This network supports a two-story logistics facility

with four different departments handling real-time cargo tracking, customs

documentation, and logistics coordination.

Let me start by showing you what I've built here. As you can see on the

screen, this is the complete network topology. We have the internet

connection at the top, a router, a core switch in the center, and four

departments spread across two floors.

The first floor has the Customs and Documentation office with ten

workstations, and the Logistics Coordination unit, also with ten workstations.

On the ground floor, we have the Live Cargo Tracking unit with eight

workstations, and the Data Server Room with four critical servers.

The entire network uses VLAN segmentation for security. Each department is

on its own VLAN, which means their traffic is isolated from each other unless

they specifically need to communicate through the core switch.

Now, let me show you how everything works by running some tests.
PING TEST - SAME VLAN (1:00 - 2:00)

First, I'm going to test connectivity within the same department. This tests if

devices in the same VLAN can communicate with each other.

I'm opening the command prompt on PC-CUSTOMS-01, which is in the

Customs office on VLAN 10. This computer has the IP address [Link].

Now I'm going to ping another computer in the same office, PC-CUSTOMS-02,

which has the IP address [Link].

I'll type: ping [Link]

And... there we go. As you can see, we're getting replies. Reply from

[Link], and the time is 2 milliseconds. That's excellent response

time.

We sent four packets, and all four were received with zero percent packet

loss. This confirms that our switch configuration is working correctly, and

devices within the same VLAN can communicate perfectly.

The 2 millisecond latency is very fast because both computers are connected

to the same access switch, so the data only has to travel through one switch.

This is exactly what we want for our star topology design.

Now let me show you something more interesting - communication between

different VLANs. This is called inter-VLAN routing, and it's handled by our core

switch.

I'm still on PC-CUSTOMS-01 in VLAN 10. Now I want to ping a computer in a

completely different department. Let's ping PC-TRACKING-01 in the Live

Cargo Tracking unit, which is on VLAN 20 and located on the ground floor.

PC-TRACKING-01 has the IP address [Link]. Let me ping it.

I'll type: ping [Link]

Perfect! We're getting replies. The response time is 6 milliseconds, which is

still very good.

Notice the latency is slightly higher than before - that's because the data now

travels through three switches: from the Customs access switch, up to the

core switch which performs the routing between VLANs, then down to the

Tracking access switch, and finally to the destination computer.

This proves our inter-VLAN routing is configured correctly on the core switch.

Even though these departments are on different VLANs for security purposes,

they can still communicate when needed for business operations.

In a real deployment, we would add access control lists to control exactly

which departments can talk to which other departments, but for this

demonstration, inter-VLAN routing is enabled.

Now let's test connectivity to our servers. The servers are critical for

QTerminals operations - they handle file storage, database queries,

applications, and backups.

All four servers are located in the server room on the ground floor, and

they're on VLAN 99, which is our dedicated server VLAN.

Let me ping the database server, which is SRV-DB-01 at IP address

[Link]. This server handles all the cargo tracking database queries,

so it needs to be accessible from all departments.

I'll type: ping [Link]

Excellent! We have successful replies with 5 millisecond response time. This

is perfect for database operations.

Now let me show you something important about our server configuration.

The servers use link aggregation, which means they have two network cables

connected instead of one. This gives them 2 gigabits per second of

bandwidth instead of just 1 gigabit.

Let me click on the database server to show you its configuration. As you can

see here in the config tab, both FastEthernet ports are connected. This

provides both higher speed and redundancy - if one cable fails, the server

stays connected through the other cable.

departments are constantly querying it for cargo tracking information. The

extra bandwidth ensures fast response times even when many users are

working simultaneously.

WIRELESS CONNECTIVITY TEST (4:30 - 5:15)

Now let's test the wireless network. We have three wireless access points

deployed across the facility - one in the Customs office, one in the Live Cargo

Tracking unit, and one in the Logistics Coordination unit.

All wireless devices connect to VLAN 40, which is our dedicated wireless

VLAN. This keeps wireless traffic separate from the wired network for security

purposes.

Let me click on this laptop here. As you can see, it's connected wirelessly to

Access Point 01. The laptop received an IP address automatically through

DHCP - it got [Link], which is in the correct wireless subnet.

Now let me ping something from the laptop to prove it has full network

connectivity. I'll ping the file server at [Link].

I'll type: ping [Link]

Great! We're getting replies. The response time is 12 milliseconds, which is

slightly higher than wired connections, but that's normal for wireless.
Wireless has some overhead from the WiFi protocol, but 12 milliseconds is

still excellent for office applications.

This proves our wireless users can access all the servers and resources they

need. Staff can move around with laptops and handheld devices while staying

connected to the network.

The access points use WPA3 encryption for security, and they're powered

through Power over Ethernet from the switches, so we don't need separate

power adapters for them.

DHCP VERIFICATION (5:15 - 6:00)

Let me quickly show you our DHCP configuration. DHCP automatically assigns

IP addresses to devices, which makes network management much easier.

I'm going to look at one of the workstations in the Logistics department. Let

me click on PC-LOGISTICS-05 and check its IP configuration.

As you can see in the IP Configuration tab, this computer is set to DHCP, and

it automatically received the IP address [Link]. This is in the correct

range for VLAN 30, which is the Logistics Coordination VLAN.

It also got the correct subnet mask - [Link], which is a /26 subnet

giving us 62 usable IP addresses per department. The default gateway is

correctly set to [Link], which is the router interface for this VLAN.
Every VLAN has its own DHCP scope configured on the core switch. When a

computer boots up, it broadcasts a DHCP request, the core switch responds

with an IP address from the appropriate VLAN's pool, and the computer is

automatically configured. No manual IP address entry required.

This is especially helpful when QTerminals adds new workstations or when IT

staff need to troubleshoot computers - they just plug in and get an IP address

automatically.

CONCLUSION AND NETWORK OVERVIEW (6:00 - 7:00)

So let me summarize what we've accomplished with this network design.

We have a hierarchical star topology with a core switch providing inter-VLAN

routing and four access switches connecting the departments. This design is

easy to manage, easy to troubleshoot, and provides excellent performance.

We're using VLAN segmentation for security - VLAN 10 for Customs, VLAN 20

for Cargo Tracking, VLAN 30 for Logistics, VLAN 99 for Servers, and VLAN 40

for Wireless. Each VLAN has its own IP subnet, and the core switch routes

traffic between them.

All our tests passed successfully. Same-VLAN communication works with 2

millisecond latency. Inter-VLAN routing works with 6 millisecond latency.

Server connectivity is excellent at 5 milliseconds. Wireless connectivity works

perfectly at 12 milliseconds. DHCP is automatically assigning correct IP

addresses to all devices.

access points across a two-story building. It provides high availability for real-

time cargo tracking, secure handling of customs documentation, and efficient

communication for logistics operations.

All critical servers use link aggregation for 2 gigabit connectivity and

redundancy. The wireless network enables mobile operations throughout the

facility.

This network is ready to support QTerminals' logistics operations and has

plenty of room to grow as the company expands.

Thank you for watching my network implementation demonstration. This is

Yousef Al-Obaidli, and this has been the QTerminals Logistics Centre network

project.