Practical-1

Construction of Straight-through and cross-over cable:

 Introduction to Networking Cabling:

Network cabling is the foundation of communication in networks, enabling efficient data

transmission. It includes copper cables, fiber optics, and wireless connections, ensuring
reliability, speed, and minimal errors. A strong cabling system is crucial for homes,
businesses, and data centers.

 Types of Network Cables:

1. Straight-Through Cable
o Definition: Uses the same wiring standard (T568A or T568B) on both ends.
o Use Case: Connects different devices (e.g., computer to switch/router).
2. Crossover Cable
o Definition: One end follows T568A, the other T568B.
o Use Case: Connects similar devices (e.g., computer to computer, switch to
switch).

 Objective of the Practical:

Understand network cabling basics, differentiate between cable types, and gain hands-on
experience in creating and testing cables for proper network connections.

 Materials and Equipment:

1. Ethernet Cables (Cat5e, Cat6, Cat6a): Twisted-pair cables for data transmission,
varying in speed and crosstalk reduction.
2. RJ45 Connectors: 8-pin connectors for Ethernet cable termination, enabling device
connections.
3. Crimping Tool: Secures RJ45 connectors by pressing pins into cable wires.
4. Cable Stripper/Cutter: Strips Ethernet cable insulation for proper wire arrangement.
5. Cable Tester: Checks Ethernet cable functionality, detecting faults like miswiring.

 Methodology:
 Steps for Cable Construction:

 Straight-Through Cable:

1. Strip Jacket: Remove 1–2 inches of outer insulation without damaging wires.
2. Untwist & Arrange Wires: Follow T568A or T568B (same on both ends).
 o T568B Order: Orange/White, Orange, Green/White, Blue, Blue/White,
Green, Brown/White, Brown.
3. Trim Wires: Cut evenly, leaving 0.5 inches exposed.
4. Insert into RJ45: Ensure correct slot alignment and firm placement.
5. Crimp Connector: Use a crimping tool to secure wires.
6. Repeat for Other End: Match the chosen wiring standard.

 Crossover Cable:

1. Understand Wiring: T568A on one end, T568B on the other.

o T568A Order: Green/White, Green, Orange/White, Blue, Blue/White,
Orange, Brown/White, Brown.
2. Strip Jacket: Remove outer insulation from both ends.
3. Untwist & Arrange Wires: Follow T568A on one end, T568B on the other.
4. Trim Wires: Cut evenly, leaving 0.5 inches exposed.
5. Insert into RJ45: Align properly with their respective standards.
6. Crimp Connector: Securely crimp both ends.
7. Test Cable: Use a cable tester for continuity and proper wiring.

 Figures:
 Observations and Results:
 Observation:

1. Testing Process

 Continuity Test: Cables were tested using a cable tester. Both ends were connected
to check wire continuity and alignment.
 LED Indicators: Verified correct wiring (T568A or T568B) through LED signals.

2. Challenges & Resolutions

 Improper Crimping: Loose connections due to weak crimping.

o Fix: Re-crimped with consistent pressure.
 Wire Misalignment: Incorrect wire order before insertion.
o Fix: Rearranged and trimmed wires properly.
 Wire Damage: Nicks due to excessive force while stripping.
o Fix: Used a stripper carefully to avoid damage.

 Result:

 After corrections, cables passed testing with proper continuity.

 Both straight-through and crossover cables functioned correctly, ensuring stable
network connections.

 Discussion:

 Straight-Through vs. Crossover Cables:

Straight-through uses the same standard on both ends for connecting different devices
(PC to switch), while crossover has T568A on one end and T568B on the other for
similar devices (PC to PC). Correct cable selection ensures proper Tx/Rx alignment,
though Auto-MDI/MDIX reduces dependency. Hands-on practice reinforced wiring
precision, crimping, testing, and troubleshooting.

 Conclusion:
Network cabling is fundamental for stable and efficient communication in networking.
Practical-2
Setup of Cisco Packet Tracer:

 Introduction:
Cisco Packet Tracer is a cost-effective network simulator for virtual design,
configuration, and troubleshooting, supporting various devices and protocols. It aids
CCNA preparation, simulates real-world scenarios, and provides instant error analysis.

 Download:
Steps to Download Cisco Packet Tracer

1. Visit Website: Go to Cisco Networking Academy.

2. Log In / Sign Up: Create a Cisco account or log in.
3. Find Packet Tracer: Navigate to the Resources section.
4. Download Page: Locate the Packet Tracer download link.
5. Select Version: Choose based on OS:
o Windows: .exe
o macOS: .dmg
o Linux: .deb/.tar.gz
6. Install: Download and follow OS-specific setup instructions.

 Setting Up an Account:
Steps to Create a Cisco Account

1. Visit Website: Open Cisco Networking Academy.

2. Sign Up: Click "Sign Up" on the homepage.
3. Fill Form: Enter required details:
o Full Name, Email, Password, Country, Date of Birth (if needed).
o Accept terms and conditions.
4. Verify Email: Click the confirmation link sent to your inbox.
5. Log In: Return to the site and enter credentials.
6. Access Resources: Navigate to "Resources" for Cisco Packet Tracer, courses,
and tools.

 Installation Process:
1. Locate Installation File:

o Find the downloaded file (PacketTracer_.exe/.dmg/.deb/.tar.gz).

2. Run Installer:
 o Double-click to start installation, allow permissions if prompted.

3. Follow Prompts:

o Accept terms, choose installation directory (default recommended), wait for

completion.

4. Launch Packet Tracer:

o Open from Start Menu (Windows) or Applications (macOS).

5. Log In & Activate:

o Use Cisco Networking Academy credentials to log in and activate.

o Demo given below:

Fig: Login Interface

 Conclusion:
Cisco Packet Tracer was installed and set up, enabling hands-on network design,
configuration, and troubleshooting.
Practical-3
Setup P2P and Client Server Network and verifying it, using Cisco
Packet Tracer:

 Introduction:

Networking enables seamless device communication. This practical explores P2P and
Client-Server models, focusing on setup, configuration, and connectivity testing.

 P2P vs. Client-Server Networks:

 P2P: Decentralized, no central server, simple, cost-effective, limited

scalability/security (e.g., file sharing between PCs).
 Client-Server: Centralized, scalable, better security, higher cost/complexity
(e.g., corporate file sharing).

 Practical Objectives:

1. Set Up P2P: Direct connection, share resources.

2. Set Up Client-Server: Configure a server for multiple clients.
3. Verify Connectivity: Use ping/shared resources.

 Materials and Software:

1. Cisco Packet Tracer:

 Purpose: Simulates network design, configuration, and testing.

 Features: Supports P2P & Client-Server setups, offers networking devices, and
aids troubleshooting.

2. Basic IP Addressing:

 IP Address: Unique 32-bit identifier (IPv4) with Network & Host ID (e.g.,
192.168.1.1).
 Why IPv4? Common in small networks, uses private IP ranges (e.g.,
192.168.x.x).

 Methodology:
 P2P Network Setup:

1. Create Topology: Add two PCs, connect via crossover cable.

2. Configure IPs:
 o PC1: 192.168.1.1 / 255.255.255.0
o PC2: 192.168.1.2 / 255.255.255.0
3. Verify Connectivity: Run ping 192.168.1.2 on PC1.

 Client-Server Network Setup:

1. Create Topology: Add a PC (Client), a Server, connect via switch using a

straight-through cable.
2. Assign Static IPs:
o Server: 192.168.1.100 / 255.255.255.0
o Client: 192.168.1.10 / 255.255.255.0
3. Enable Server Services: Activate HTTP/FTP in Server's Services tab.
4. Verify Connectivity:
o Ping Server (ping 192.168.1.100).
o Access http://192.168.1.100 in Client's browser.

 Observations and Results:

 Observation:

 P2P and Client-Server networks were set up using necessary devices.

 P2P used manual IP assignment; Client-Server used DHCP.
 Proper cables were used (crossover/straight-through).
 Connectivity verified via ping.
 P2P enabled direct communication; Client-Server allowed resource access via the
server.

 Result:

 P2P: Successful direct communication via assigned IPs.

 Client-Server: Clients obtained IPs via DHCP, ping verified connectivity, and server
resources were accessible.

 Discussion:

P2P vs. Client-Server: P2P allows direct device communication with static IPs, suited
for small networks and local file sharing. Client-server uses a centralized model with
DHCP, scaling efficiently for large networks with centralized resource access. P2P is
used in LAN gaming and file sharing, while client-server supports corporate networks,
web hosting, and cloud storage.

 Conclusion:

P2P suits small, informal setups, while Client-Server is ideal for scalable, structured
networks.
Practical-4
Observing IP address and MAC address using commands in
command prompt, setting IP address and default gateway in PC,
using Cisco Packet Tracer:

 Introduction:

This practical covers networking essentials: analyzing IP/MAC addresses, configuring

static IPs, and setting gateways using Command Prompt and Cisco Packet Tracer.

 Objectives of the practical:

Use ipconfig & getmac to check IP/MAC, set static IPs for servers, and configure
gateways for inter-network communication. Simulate in Packet Tracer, then
troubleshoot with ping & tracert to verify connectivity.

 Materials and Software:

 Hardware: Computer, network cables, devices, or Cisco Packet Tracer for

simulation.
 Command Prompt: ipconfig for IP details, getmac for MAC address.
 Cisco Packet Tracer: Simulate, configure, and test networks.

 Methodology:
 Steps:

1. Observe IP/MAC:
o Open Command Prompt (cmd), run ipconfig /all.
2. Set IP/Gateway:
o In Packet Tracer, configure IP: 192.168.1.10, Subnet: 255.255.255.0,
Gateway: 192.168.1.1.
3. Verify Changes:
o Run ipconfig to confirm settings.
4. Configure in Packet Tracer:
o Connect PC, Switch, Router, set Router IP to 192.168.1.1.
5. Test Connectivity:
o Ping 192.168.1.1 to confirm connection.
  Figures:

Fig: Observing IP and MAC Address

Fig: Setup Interface

 Observations and Results:

 Observations:

 IP & MAC Address Check: ipconfig /all displayed the assigned IP, subnet mask
(255.255.255.0), default gateway (e.g., 192.168.1.1), and MAC address.
 IP & Gateway Configuration: A static IP (e.g., 192.168.1.10) and gateway
(192.168.1.1) were set in Cisco Packet Tracer, verified using ipconfig.
  Connectivity Test: A successful ping 192.168.1.1 confirmed proper
communication with the router.

 Results: Network settings were correctly applied, verified, and functional, ensuring
seamless connectivity.

 Discussion:

This practical covered IP/MAC observation, static IP setup, and connectivity testing
using Cisco Packet Tracer and Command Prompt. Proper configuration ensured seamless
communication, reinforcing key networking skills.

 Conclusion:

This practical reinforced IP configuration, MAC roles, connectivity troubleshooting, and

essential networking tools.
Practical-5
Configuration of network using HUB and observing the working of
HUB, Using Cisco Packet Tracer:

 Introduction:

In this practical, we configure a simple network with a HUB in Cisco Packet Tracer to
observe data flow and understand basic networking concepts. It highlights HUBs'
broadcast nature and limitations in modern networking.

 Objectives of the practical:

1. HUB operation: Learn how a HUB broadcasts data to all devices.

2. Network configuration: Set up a HUB network in Cisco Packet Tracer.
3. Data transmission: Observe how HUB sends data and device responses.
4. Comparison: Understand HUB limitations vs. switches/routers.
5. Traffic behavior: Explore issues like congestion and security in HUB networks.
6. Topologies: Study how star topology impacts performance.

 Materials and Software:

1. Hardware: Computers/Laptops (meeting Cisco Packet Tracer's system requirements)

and virtual Ethernet cables for device connections.
2. Software: Cisco Packet Tracer for designing, simulating, and configuring network
topologies, including HUBs and devices.
3. Network Devices:
a. HUB: Connects multiple devices in a LAN, broadcasting data at the physical
layer.
b. PCs/Laptops: End-user devices for testing network configuration and
observing data transmission.
c. Ethernet Cables: Virtual cables for connecting devices within Packet Tracer.

 Methodology:

1. Network Design and Setup:

 Open Cisco Packet Tracer and create a new project.

 Add a HUB and connect at least three PCs/laptops to it using straight-through
Ethernet cables.
2. IP Configuration:

 Assign unique IP addresses and subnet masks to each PC.

 Set the Default Gateway to the HUB's IP if needed.

3. Verifying Connections:

 Use Simulation Mode to send a ping command from one PC to another.

 Check if the HUB broadcasts packets to all devices.

4. Observing Data Transmission:

 While pinging, observe the HUB broadcasting packets to all connected devices.
 Monitor packet details (source, destination) in the Simulation Panel.

5. Troubleshooting and Analysis:

 If ping fails, check IP settings, connections, and cable types.

 Analyze network traffic for collisions or delays, typical of a HUB’s shared
bandwidth.

 Figures:

Fig: Hub Connection Interface

 Observations and Results:

 Observations:

1. Network Setup: HUB connected multiple PCs, each with a unique IP.
2. Data Transmission: HUB broadcasted packets to all devices, not just the
recipient.
3. Impact: Non-target PCs ignored packets; collisions caused delays.
4. Traffic Simulation: Simulation confirmed successful but inefficient
communication.
5. HUB Limitations:
o Bandwidth Sharing: Slower performance.
o Collisions: Frequent retransmissions.
o Security Risk: Data visible to all.
6. Comparison: Unlike switches/routers, HUB lacks intelligent data forwarding.

 Results:

HUB's inefficiency, collisions, and security risks highlight the need for advanced
networking devices.

 Discussion:

 HUB Behavior in Networking:

1. Broadcasting: Sends data to all devices, causing unnecessary traffic and

inefficiency.
2. Collisions & Bandwidth: Shared medium leads to frequent collisions, delays,
and reduced efficiency.
3. Security Risk: Data is exposed to all devices, making interception easy.
4. Switch/Router Comparison: Switches prevent collisions by forwarding data
intelligently; routers manage inter-network traffic.

 Conclusion:

HUBs cause congestion, collisions, and security risks, making them unsuitable for
modern networks compared to switches and routers.
Practical-6

Configuration of network using Switch and observing the

working of Switch, Using Cisco Packet Tracer:

 Introduction:

This practical configures a network using a Switch in Cisco Packet Tracer. Unlike a
HUB, the Switch forwards data only to the intended recipient, improving efficiency,
reducing collisions, and enhancing performance.

 Objectives of the practical:

Configure switch networks, understand MAC forwarding, and compare

switches with hubs. Analyze performance, congestion, and explore large-scale
network use.

 Materials and Software:

1. Hardware & Software:

o Computer/Laptop (meeting minimum requirements) to run Cisco Packet
Tracer (a network simulation tool for designing and analyzing network
topologies).
2. Network Devices (within Packet Tracer):
o Switch (Layer 2 device) for forwarding data based on MAC addresses.
o PCs/Laptops (end-user devices) assigned unique IPs for network testing.
o Ethernet Cables (virtual) to connect devices and enable data transmission.

 Methodology:

1. Network Setup:
o Create a project in Packet Tracer, add a Switch and 3 PCs, connect with
Ethernet cables.
2. IP Configuration:
o Assign IPs:
 PC1: 192.168.2.1/255.255.255.0
 PC2: 192.168.2.2/255.255.255.0
 PC3: 192.168.2.3/255.255.255.0
3. Connectivity Test:
o Use ping (e.g., ping 192.168.2.2 from PC1).
4. Switch Observation:
o Enable Simulation Mode, observe MAC forwarding.
o Check MAC table with show mac-address-table.
o
 5. Efficiency:
o Verify collision-free forwarding, compare with Hub.
6. Troubleshooting:
o Ensure correct IP configuration and cable connections, re-test.

 Figures:

Fig: Switch Connection Interface

 Observations and Results:

 Observations:

Switch efficiently transmits data to intended recipients using a MAC address table,
preventing collisions and ensuring security. It optimizes bandwidth, reduces congestion,
and allows connectivity verification via ping tests.

 Results:

 Switch provides efficient, secure, and collision-free communication, superior to

HUBs.

 Discussion:

This practical demonstrated a switch's superiority over a HUB, with efficient data
forwarding, collision-free communication, and enhanced security. Switches learn MAC
addresses for intelligent traffic management, ensuring scalability and reliability.

 Conclusion:

The experiment demonstrated the switch's ability to efficiently manage network traffic,
prevent collisions, and enhance security, making it a vital component in modern networks.
Practical-7
Configuration of network using Router and observing the
working of DHCP, Using Cisco Packet Tracer:

 Introduction:

This practical demonstrates configuring a router as a DHCP server in Cisco Packet Tracer
to automatically assign IP addresses, simplifying network management and preventing IP
conflicts. It highlights the router's role in directing data and automating IP allocation.

 Objectives of the practical:

1. Router Function: Understand how a Router directs data at Layer 3 (Network

Layer) between networks.
2. Network Configuration: Set up a network using a Router in Cisco Packet Tracer
across different subnets.
3. DHCP Configuration: Configure a Router to assign dynamic IP addresses via
DHCP.
4. Analyze DHCP Process: Observe IP assignment, lease duration, and renewal.
5. Static vs Dynamic IP: Compare DHCP advantages over static IP addressing.
6. Network Troubleshooting: Use tools like ping and IP checks to verify network
connectivity.
7. Subnet Communication: Explore Router-based communication between
different subnets.

 Materials and Software:

 Hardware: Computer/Laptop, Ethernet cables (virtual).

 Software: Cisco Packet Tracer, supported OS (Windows/macOS/Linux).
 Devices: Router (DHCP server), Switch, PCs/Laptops.
 Tools: Command Prompt, Simulation Mode.
 Addressing: IP Pool, Subnet Mask, Gateway, DNS.

 Methodology:

1. Network Setup:
o Open Cisco Packet Tracer, create a project, and add a Router (DHCP server),
Switch, and PCs.
o Connect Router's GigabitEthernet 0/0 to the Switch and the Switch to PCs
using Ethernet cables.
2. Configure Router as DHCP Server:
o Assign IP to Router's GigabitEthernet 0/0:
 o Router> enable
o Router# configure terminal
o Router(config)# interface GigabitEthernet 0/0
o Router(config-if)# ip address 192.168.1.1 255.255.255.0
o Router(config-if)# no shutdown
3. Enable DHCP:
o Configure DHCP pool:
o Router(config)# ip dhcp pool LAN
o Router(dhcp-config)# network 192.168.1.0 255.255.255.0
o Router(dhcp-config)# default-router 192.168.1.1
o Router(dhcp-config)# dns-server 8.8.8.8
o Exclude reserved addresses:
o Router(config)# ip dhcp excluded-address 192.168.1.1
4. Configure PCs for DHCP:
o Set each PC's IP configuration to DHCP to receive IP from the Router.
5. Test Connectivity:
o Verify IPs using ipconfig and run ping tests between PCs and the Router
(192.168.1.1).
6. Observe DHCP Process in Simulation Mode:
o Watch the DHCP Discover, Offer, Request, and Acknowledge process.
7. Troubleshooting:
o Ensure the router’s interface is active, check cable connections, and verify PCs
are set to DHCP.

 Figures:

Fig: Router Connection and DHCP Enable Interface

 Observations and Results:

 Observations:

 PCs received automatic IPs via DHCP (e.g., PC1: 192.168.1.2).

 DHCP process (Discover, Offer, Request, Acknowledge) was observed.
 Ping tests confirmed successful communication.
 Router managed IP pool and assigned IPs with no manual setup.
 Simulation showed DHCP packet exchange, preventing conflicts.

 Results:

 Router successfully automated IP assignment, improving network efficiency.

 Seamless communication with no manual configuration required.

 Discussion:
 DHCP Efficiency: DHCP automates IP address assignment, reducing manual
configuration and providing necessary network settings (IP, subnet, gateway,
DNS).
 DHCP Discovery: The four-step process (Discover, Offer, Request,
Acknowledge) ensures smooth client-server interaction for IP assignment.
 Error Prevention: Excluding reserved addresses prevents IP conflicts.
 Router as DHCP Server: The router manages dynamic IP allocation and routes
data, verified using the show ip dhcp binding command.
 Large Networks: DHCP simplifies IP management in large, dynamic networks.
 Connectivity: Ping tests confirmed proper network setup with minimal delays.
 Static vs. Dynamic IPs: DHCP offers scalability and automation, unlike static IP
configuration.

 Conclusion:

The practical demonstrated DHCP’s role in simplifying IP management and enhancing

network efficiency. Configuring the router as a DHCP server ensures seamless setup,
scalability, and conflict-free operation in modern networks.
Practical-8
Configuration of DHCP server and verifying it, releasing the leased
IP, renew of the IP, Using Cisco Packet Tracer:

 Introduction:

This practical sets up a DHCP server in Cisco Packet Tracer for automatic IP assignment,
including pools, gateways, and DNS. It also covers verification, lease management, and
troubleshooting.

 Objectives of the practical:

Configure DHCP on a Cisco router with an IP pool, subnet mask, gateway, and DNS.
Verify functionality using commands, check bindings, and demonstrate IP
release/renewal. Troubleshoot issues with commands like "show ip dhcp binding"
and "debug dhcp."

 Materials and Software

 Hardware (Simulated in Cisco Packet Tracer): Router (DHCP server), Switch,
End devices (PCs/laptops).
 Software: Cisco Packet Tracer, OS commands (ipconfig).
 Network Info: Subnet details, DNS, CLI access.

 Methodology:
1. Setup Network:
o Open Cisco Packet Tracer, add router, switches, and PCs.
o Connect devices using straight-through cables.
2. Configure DHCP Server:
o Access router CLI: enable, configure terminal.
o Define DHCP pool: ip dhcp pool <pool_name>, network <network_address>
<subnet_mask>, default-router <gateway>, dns-server <dns>.
o Exclude IPs for static devices: ip dhcp excluded-address <start_ip> <end_ip>.
3. Verify Configuration:
o Check settings: show running-config, show ip dhcp binding.
4. Test DHCP:
o Configure PCs to use DHCP: Desktop → IP Configuration → DHCP.
o Verify with ipconfig in Command Prompt.
5. Release/Renew IP:
o Release: ipconfig /release.
o Renew: ipconfig /renew.
 o Verify new IP with ipconfig.
6. Troubleshoot:
o Check binding table: show ip dhcp binding.
o Debug: debug dhcp detail.
o Resolve issues like misconfigurations or conflicts.

 Figures:

Fig: Router Connection and DHCP Configuration Interface

 Observations and Results:

 Observations:

DHCP server correctly allocated IPs, subnet, gateway, and DNS, with successful
release/renewal. Binding verification showed MAC-IP pairs and lease times in the
DHCP table.

 Results:

DHCP server functioned correctly, ensuring smooth IP allocation and

communication.

 Discussion:

DHCP automates IP allocation for scalability, reducing manual work and conflicts.
Proper configuration of IP pools, gateways, and DNS ensures smooth operation with
efficient lease management.

 Conclusion:

DHCP automates network management, essential for all network sizes, with future
improvements possible in failover configurations.
Practical-9
Configuration of FTP, HTTP, DNS and e-mail server, Using Cisco
Packet Tracer:

 Introduction:

This practical focuses on configuring FTP, HTTP, DNS, and Email servers in Cisco
Packet Tracer, simulating their functionality within a LAN environment. It highlights
their importance in file transfers, website hosting, domain resolution, and email
communication in real-world networking.

 Objectives of the practical:

1. FTP: Configure for file transfers and test uploads/downloads.

2. HTTP: Set up for web hosting and test client access.
3. DNS: Configure for domain resolution and test name-based access.
4. Email: Set up for email communication and test functionality.
5. Integration: Verify server-client interaction and simulate tasks.
6. Troubleshooting: Use tools to resolve configuration issues.
This practical covers the configuration and testing of key network services.

 Materials and Software:

To perform the practical, you'll need:

 Hardware (Packet Tracer):

 Servers (FTP, HTTP, DNS, Email)

 Switches, End devices (PCs/laptops), Router (if needed)

 Software:

 Cisco Packet Tracer

 OS commands for testing (FTP: ftp, HTTP: Browser, DNS: nslookup, Email: Built-in
clients)
  Configuration:

 FTP: Files, credentials

 HTTP: HTML pages
 DNS: Domain-IP mapping
 Email: User accounts

 Methodology:

Step 1: Network Setup

 Add and connect devices: Server (for FTP, HTTP, DNS, Email), switches, and
client PCs.
 Assign static IP to the server, dynamic IP for clients.

Step 2: FTP Server Configuration

 Enable FTP service on the server, add username/password.

 Upload files for client interaction.

Step 3: HTTP Server Configuration

 Enable HTTP, upload HTML pages.

 Test web access from client browser.

Step 4: DNS Server Configuration

 Enable DNS, map domain names to IPs.

 Test domain resolution with nslookup.

Step 5: Email Server Configuration

 Enable Email service, create email accounts.

 Configure clients to send/receive emails.

Step 6: Testing and Verification

 FTP: Test file transfer via command prompt (ftp <server_ip>).

 HTTP: Access webpage using server IP/domain.
 DNS: Use nslookup for domain resolution.
 Email: Test sending/receiving emails.

Step 7: Troubleshooting

 Ping for connectivity, verify configurations, use Packet Tracer’s simulation tools.
 Figures:

Fig: Device Configuration Interface

1. FTP Server:

Fig: FTP Server Configuration and Verification

2. HTTP Server:

Fig: HTTP Server Configuration and Verification

3. DNS Server:

Fig: DNS Server Configuration and Verification

 4. Email Server:

Fig: Email Server Configuration and Verification

 Observations and Results:

 Observations:

FTP server enabled file transfers with secure authentication, HTTP hosted a
webpage, DNS resolved domain names, and email service allowed successful
sending/receiving of emails.

 Results:

FTP enabled successful file transfers, HTTP displayed content via IP/domain,
DNS resolved domain names to IPs, and email functionality was confirmed with
successful sending/receiving.

 Discussion:
This practical covered FTP, HTTP, DNS, and Email server setup in Cisco Packet Tracer,
highlighting their roles in file sharing, web hosting, domain resolution, and
communication.

 Conclusion:

All services (FTP, HTTP, DNS, Email) were configured and tested successfully in Cisco
Packet Tracer.
Practical-10
Static routing and Dynamic routing (RIP, OSPF, EIGRP, BGP),
Using Cisco Packet Tracer:

 Introduction:

This practical involves configuring static and dynamic routing (RIP, OSPF, EIGRP, BGP) in
Cisco Packet Tracer to simulate real-world network scenarios. Static routing uses manual
path setup, while dynamic routing adapts automatically to network changes, enhancing traffic
management.

 Objectives of the practical:

Configured and tested static routes for manual path selection and dynamic protocols
(RIP, OSPF, EIGRP, BGP) for automatic route sharing. Analyzed routing tables to
understand route learning and maintenance.

 Materials and Software:

1. Hardware Components (Simulated in cisco packet tracer):

 Routers, switches, and PCs/laptops for connectivity and testing.

2. Software & Tools:

 Cisco Packet Tracer for network simulation & router configuration.

 Ping, traceroute, show commands for connectivity testing &
verification.

 Methodology:

Step 1: Network Setup

1. Add Devices: Place routers (2+ for static, 3+ for dynamic), optional switches, and
PCs/laptops.
2. IP Addressing: Assign static IPs to router interfaces and PCs (manual/DHCP).

Step 2: Static Routing

1. Configuration:
o ip route <destination_network> <subnet_mask> <next_hop_ip> on all
routers.
 2. Verification:
o show ip route, ping <destination_ip>, traceroute <destination_ip>.

Step 3: RIP Configuration

1. Enable RIP:
o router rip → version 2 → network <network_address>.
2. Verification:
o show ip route, show ip rip database, ping, traceroute.

Step 4: OSPF Configuration

1. Enable OSPF:
o router ospf <process_id> → network <network_address>
<wildcard_mask> area <area_id>.
2. Verification:
o show ip route ospf, show ip ospf neighbor, ping, traceroute.

Step 5: EIGRP Configuration

1. Enable EIGRP:
o router eigrp <as_number> → network <network_address> → no auto-
summary.
2. Verification:
o show ip route eigrp, show ip eigrp neighbors, ping, traceroute.

Step 6: BGP Configuration

1. Enable BGP:
o router bgp <asn> → network <network_address> mask <subnet_mask>.
2. Verification:
o show ip route bgp, show ip bgp summary, ping, traceroute.

Step 7: Routing Table Analysis

 Use show ip route to confirm learned routes and correct forwarding paths.

Step 8: Troubleshooting & Verification

1. Check Configurations: show ip protocols, show ip route.

2. Test Connectivity: ping, traceroute.
 Figures:

Fig: Router Configuration Interface

1) Static Routing:

Fig: Static Routing Configuration and Verifying Connectivity

2) Dynamic Routing:

a) RIP (Routing Information Protocol):

Fig: RIP Configuration and Verifying Connectivity

b) OSPF (Open Shortest Path First):

Fig: OSPF Configuration and Verifying Connectivity

c) EIGRP (Enhanced Interior Gateway Routing Protocol):

Fig: EIGRP Configuration and Verifying Connectivity

 d) BGP (Border Gateway Protocol):

Fig: Three Router Configuration Interface for BG

 Observations and Results:

 Observations:

Static routing required manual setup, verified via ping & traceroute, while dynamic
routing auto-propagated routes (RIP, OSPF, EIGRP, BGP) with protocol-specific
metrics. Routing tables updated dynamically, with static being manual-intensive and
dynamic offering scalability.

 Results:

Static routing was manually configured, while dynamic routing (RIP, OSPF, EIGRP,
BGP) auto-adjusted for connectivity. Routing metrics varied, with ping & traceroute
verifying reachability; static suited stable networks, dynamic enabled scalability.

 Discussion:

This practical covered Static and Dynamic Routing (RIP, OSPF, EIGRP, BGP),
comparing scalability and efficiency. Testing with ping and traceroute verified routing
functionality and protocol behavior.

 Conclusion:

The practical demonstrated static and dynamic routing (RIP, OSPF, EIGRP, BGP),
verifying functionality and connectivity. Dynamic routing excelled in automation and
scalability, while static routing offered simplicity and control for small networks.