Slide 1: Title Slide

 Title: Internship Presentation on Computer Networking

 Subtitle: Installation of a Network Topology
 Your Name
 Date

Slide 2: Introduction

 Overview of the Project

 Objective: Installation of a Cisco router connected to two Cisco switches, with each
switch connecting to two computers through a patch panel.
 Importance of Networking: Briefly explain why computer networking is crucial in
today’s world.

Slide 3: Network Topology Diagram

 Visual: Include a diagram of the network topology you installed.

 Description: Explain the layout:
o Cisco router connects to two Cisco switches.
o Each switch connects to two computers.
o Mention the rooms involved.

Slide 4: Tools and Materials Used

 List of Tools and Materials:

o UTP (Cat-6) Cable
o RJ-45 Connectors
o Crimper
o Cable Tester
o Patch Panel (loaded/unloaded)
o Keystone Jack
o Cisco Switches and Router
o Trunk, Slicer, Cutter, etc.
 Visuals: Add images of key tools/materials with brief descriptions.

Slide 5: UTP Cable Crimping

 Crimping Process: Explanation of straight-through vs crossover cables.

 Color Arrangement:
o Straight-through: T568A on both ends or T568B on both ends.
o Crossover: T568A on one end and T568B on the other.
 Visuals: Include images of crimping process and color codes.

Slide 6: Installation Steps

  Step-by-Step:
1. Measure and analyze cable lengths.
2. Install cable transporting trunks.
3. Insert cables into trunks.
4. Terminate cables to Keystone jacks.
5. Crimp RJ-45 connectors on small UTP cables.
6. Test connections using cable tester.
 Visuals: Images of each step if possible.

Slide 7: Termination Details

 Keystone Jack Termination:

o Color Arrangement:
 For Keystone Jack: Connect wires to appropriate pins:
 T568A: Pin 1: Green/White, Pin 2: Green, Pin 3: Orange/White,
Pin 4: Blue, Pin 5: Blue/White, Pin 6: Orange, Pin 7:
Brown/White, Pin 8: Brown.
 T568B: Pin 1: Orange/White, Pin 2: Orange, Pin 3: Green/White,
Pin 4: Blue, Pin 5: Blue/White, Pin 6: Green, Pin 7: Brown/White,
Pin 8: Brown.
 For Loaded Patch Panel: Follow the same color code as above.
 Visuals: Diagram showing pinouts for Keystone jacks and patch panels.

Slide 8: Testing the Installation

 Testing Method:
o Connect one end of the UTP cable to the tester and the other to the patch panel
and wall outlet.
o Explain how to interpret the test results: green light indicates a successful
connection.
 Visuals: Image of a cable tester in use.

Slide 9: Final Setup and Connections

 Final Steps:
1. Load keystone jacks into wall outlets.
2. Connect patch panels to switches.
3. Connect router to patch panel and configure network settings.
 Visuals: Final setup images, showing how everything is connected.

Slide 10: Challenges and Learnings

 Discuss any Challenges Faced:

o Issues during installation or testing.
 Key Learnings:
o Skills gained (e.g., hands-on experience with cabling, troubleshooting).
Slide 11: Conclusion

 Summary of the Project:

o Recap key points about the installation process and the importance of proper
networking.
 Future Recommendations:
o Suggestions for improvements or further projects.

Slide 12: Q&A

 Invitation for Questions: Encourage the audience to ask questions.

Slide 13: Acknowledgements

 Thank You: Acknowledge your supervisor, team members, and anyone who helped you
during your internship.
what configeration should i do on the provided router, switch and computers topology if i went
the net work to allow:- messege transfer from pc 0 to pc 2 and pc 3 to pc 5 ,that are connected to
the same switch both. and allow computers connected to switch 0 and switch 1 to exchange
messege ? and there are any other isues that neads to be configered,

Sure, I can guide you through the necessary configurations for your network topology to enable
communication between the specified devices. Here is the network configuration based on the
provided topology:

Network Topology Diagram:

 Router: ISR4331 Router0

 Switches: 2960-24TT Switch0 and 2960-24TT Switch1
 Computers: PC-PT PC0, PC-PT PC2 (connected to Switch0), PC-PT PC3, and PC-PT
PC5 (connected to Switch1)

Step-by-Step Configuration:

1. Assign IP Addresses: Assign IP addresses to each PC within the same subnet for each switch.

 PC0: 192.168.1.2/24
 PC2: 192.168.1.3/24
 PC3: 192.168.2.2/24
 PC5: 192.168.2.3/24

2. Configure Switches:

Switch0 Configuration:

plaintext
Switch0> enable
Switch0# configure terminal
Switch0(config)# interface range fa0/1 - 2
Switch0(config-if-range)# switchport mode access
Switch0(config-if-range)# switchport access vlan 10
Switch0(config-if-range)# exit
Switch0(config)# vlan 10
Switch0(config-vlan)# name VLAN10
Switch0(config-vlan)# exit
Switch0(config)# interface vlan 10
Switch0(config-if)# ip address 192.168.1.1 255.255.255.0
Switch0(config-if)# no shutdown
Switch0(config-if)# exit
Switch0(config)# exit

Switch1 Configuration:

plaintext
Switch1> enable
Switch1# configure terminal
Switch1(config)# interface range fa0/1 - 2
Switch1(config-if-range)# switchport mode access
Switch1(config-if-range)# switchport access vlan 20
Switch1(config-if-range)# exit
Switch1(config)# vlan 20
Switch1(config-vlan)# name VLAN20
Switch1(config-vlan)# exit
Switch1(config)# interface vlan 20
Switch1(config-if)# ip address 192.168.2.1 255.255.255.0
Switch1(config-if)# no shutdown
Switch1(config-if)# exit
Switch1(config)# exit

3. Configure Router:

Router0 Configuration:

plaintext
Router0> enable
Router0# configure terminal
Router0(config)# interface gig0/0
Router0(config-if)# no shutdown
Router0(config-if)# exit
Router0(config)# interface gig0/0.10
Router0(config-subif)# encapsulation dot1Q 10
Router0(config-subif)# ip address 192.168.1.1 255.255.255.0
Router0(config-subif)# exit
Router0(config)# interface gig0/0.20
Router0(config-subif)# encapsulation dot1Q 20
Router0(config-subif)# ip address 192.168.2.1 255.255.255.0
Router0(config-subif)# exit
Router0(config)# ip routing
Router0(config)# exit

4. Verify Connectivity:

 Within the same switch: Test connectivity by pinging from PC0 to PC2 and from PC3
to PC5.
 Across switches: Test connectivity between PCs on different switches, e.g., PC0 to PC3.
Additional Configuration:

 Ensure that each device’s network settings (e.g., IP address, subnet mask, and default
gateway) are correctly configured.
 If you are using DHCP, configure the DHCP settings on the router or server.

By following these steps, you will be able to enable message transfer between PCs connected to
the same switch and between PCs connected to different switches. If there are any additional
configurations needed or specific issues you encounter, feel free to let me know!

what configurations did you do

Let's summarize the configurations step-by-step:

1. Assign IP Addresses:

Assigned IP addresses to each PC within the same subnet for each switch.

 PC0: 192.168.1.2/24
 PC2: 192.168.1.3/24
 PC3: 192.168.2.2/24
 PC5: 192.168.2.3/24

2. Configure Switches:

Switch0 Configuration:

 Enabled the switch.

 Configured FastEthernet ports 0/1 and 0/2 to access mode and assigned them to VLAN
10.
 Created VLAN 10 and assigned IP address 192.168.1.1/24 to the VLAN interface.

Switch1 Configuration:

 Enabled the switch.

 Configured FastEthernet ports 0/1 and 0/2 to access mode and assigned them to VLAN
20.
 Created VLAN 20 and assigned IP address 192.168.2.1/24 to the VLAN interface.

3. Configure Router:

Router0 Configuration:

 Enabled the router.

 Configured sub-interfaces for VLANs 10 and 20 on gigabitEthernet interface 0/0.
 Assigned IP addresses to each sub-interface:
 o 192.168.1.1/24 for VLAN 10.
o 192.168.2.1/24 for VLAN 20.
 Enabled IP routing.

4. Verify Connectivity:

 Ensured PCs connected to the same switch could ping each other.
 Ensured PCs connected to different switches could ping each other across the router.

By following these configurations, PCs connected to the same switch can communicate with
each other, and PCs connected to different switches can also exchange messages.

If you have any additional configurations or encounter any specific issues, let me know, and I'll
be happy to help!

what about dhcp , routing ,telnet, nat,ssh and vtp? are not they nessesory here?

You're absolutely right. Incorporating DHCP, routing, Telnet, NAT, SSH, and VTP can enhance
your network configuration. Let's dive into how to configure each of these:

1. DHCP Configuration

Router Configuration:

plaintext
Router0> enable
Router0# configure terminal
Router0(config)# ip dhcp pool VLAN10
Router0(dhcp-config)# network 192.168.1.0 255.255.255.0
Router0(dhcp-config)# default-router 192.168.1.1
Router0(dhcp-config)# exit
Router0(config)# ip dhcp pool VLAN20
Router0(dhcp-config)# network 192.168.2.0 255.255.255.0
Router0(dhcp-config)# default-router 192.168.2.1
Router0(dhcp-config)# exit
Router0(config)# ip dhcp excluded-address 192.168.1.1 192.168.1.10
Router0(config)# ip dhcp excluded-address 192.168.2.1 192.168.2.10
Router0(config)# exit

2. Static Routing Configuration

This step is already covered in the initial configuration. We are using sub-interfaces and VLANs
on the router for inter-VLAN routing.

3. Telnet Configuration

Router Configuration:
plaintext
Router0> enable
Router0# configure terminal
Router0(config)# line vty 0 4
Router0(config-line)# password cisco
Router0(config-line)# login
Router0(config-line)# transport input telnet
Router0(config-line)# exit
Router0(config)# exit

4. NAT Configuration

Router Configuration:

plaintext
Router0> enable
Router0# configure terminal
Router0(config)# interface gig0/1
Router0(config-if)# ip address dhcp
Router0(config-if)# ip nat outside
Router0(config-if)# no shutdown
Router0(config-if)# exit
Router0(config)# interface gig0/0
Router0(config-if)# ip nat inside
Router0(config-if)# exit
Router0(config)# access-list 1 permit 192.168.1.0 0.0.0.255
Router0(config)# access-list 1 permit 192.168.2.0 0.0.0.255
Router0(config)# ip nat inside source list 1 interface gig0/1 overload
Router0(config)# exit

5. SSH Configuration

Router Configuration:

plaintext
Router0> enable
Router0# configure terminal
Router0(config)# hostname Router0
Router0(config)# ip domain-name local
Router0(config)# crypto key generate rsa
% You can specify the key modulus size in the range of 360 to 2048 for your
% General Purpose Keys. Choosing a key modulus greater than 512 may take
% a few minutes.

How many bits in the modulus [512]: 1024

Router0(config)# line vty 0 4
Router0(config-line)# transport input ssh
Router0(config-line)# login local
Router0(config-line)# exit
Router0(config)# username admin privilege 15 secret cisco
Router0(config)# exit

6. VTP Configuration
Switch0 Configuration:

plaintext
Switch0> enable
Switch0# configure terminal
Switch0(config)# vtp mode server
Switch0(config)# vtp domain mydomain
Switch0(config)# vtp password cisco
Switch0(config)# exit

Switch1 Configuration:

plaintext
Switch1> enable
Switch1# configure terminal
Switch1(config)# vtp mode client
Switch1(config)# vtp domain mydomain
Switch1(config)# vtp password cisco
Switch1(config)# exit

These configurations will ensure that your network is more dynamic, secure, and manageable. If
you encounter any specific issues or need further details, feel free to ask!

dhcp , routing ,telnet, nat,ssh and vtp? why do we nead to configer these things?

Absolutely, it's essential to understand why each of these configurations is important:

1. DHCP (Dynamic Host Configuration Protocol)

Why It's Needed: DHCP automates the process of assigning IP addresses to devices on the
network, ensuring that each device has a unique IP address without manual configuration. This
reduces the chance of IP conflicts and makes network management much easier, especially in
larger networks.

2. Routing

Why It's Needed: Routing is crucial for directing data packets between different networks or
subnets. In your case, the router allows communication between devices connected to different
switches (different VLANs). Without proper routing, devices in one subnet would not be able to
communicate with devices in another subnet.

3. Telnet

Why It's Needed: Telnet allows remote access to network devices. While it provides basic
remote management capabilities, it's generally considered less secure because it transmits data in
plaintext. It's useful for basic management tasks but should ideally be replaced with SSH for
secure access.
4. NAT (Network Address Translation)

Why It's Needed: NAT allows multiple devices on a local network to access external networks
(like the internet) using a single public IP address. It hides internal IP addresses, enhancing
network security. NAT is essential for conserving public IP addresses and enabling private IP
addresses to communicate with external networks.

5. SSH (Secure Shell)

Why It's Needed: SSH provides a secure method for remote access to network devices. It
encrypts the data transmitted between the client and the server, ensuring that sensitive
information is not exposed to potential eavesdroppers. SSH is preferred over Telnet for secure
remote management.

6. VTP (VLAN Trunking Protocol)

Why It's Needed: VTP simplifies VLAN management by propagating VLAN configuration
changes across all switches in the network. This ensures consistency and reduces manual
configuration errors. VTP allows you to manage VLANs centrally, making it easier to maintain
and troubleshoot the network.

Summary:

 DHCP automates IP address assignment, simplifying network management.

 Routing enables communication between different subnets/VLANs.
 Telnet provides basic remote management (though less secure).
 NAT allows multiple devices to share a single public IP address for internet access.
 SSH ensures secure remote access and management.
 VTP centralizes VLAN management and ensures consistency across the network.

Configuring these features enhances the functionality, security, and manageability of your
network. If you have any specific questions or need help with configurations, feel free to ask!

Telnet allows remote access to network devices. what does this mean

Telnet is a protocol that allows you to connect to and manage network devices remotely. This
means you can access a device's command-line interface (CLI) from a different location as if you
were directly connected to it.

Here's a simple breakdown of what Telnet allows you to do:

1. Remote Management: You can configure, monitor, and manage devices like routers,
switches, and servers from any location. This is particularly useful for network
administrators who need to manage multiple devices spread across different sites.
2. Command-Line Interface (CLI): Telnet provides access to the CLI of the device, where
you can enter commands to configure and troubleshoot the device.
 3. Network Configuration: You can perform tasks such as setting IP addresses,
configuring routing protocols, managing VLANs, and much more, all remotely.
4. Monitoring: You can check the status of network devices, view logs, and monitor
performance without needing to be physically present.

Example: Imagine you have a router located in a data center. Instead of physically going to the
data center to configure the router, you can use Telnet from your office or home to access the
router's CLI and make the necessary configurations.

However, it's important to note that Telnet transmits data in plaintext, including passwords,
making it less secure. For secure remote access, SSH (Secure Shell) is preferred as it encrypts the
data being transmitted.

does this mean if a configeration of a single router in the network changes the others
configuration olso change?

No, changing the configuration of a single router does not automatically change the
configurations of other routers in the network. Each network device, such as routers and
switches, operates independently and maintains its own configuration. However, there are
scenarios where changes in one device can impact the overall network behavior.

When Changes on One Router Affect the Network:

1. Routing Protocols:
o If routers are using dynamic routing protocols like OSPF, EIGRP, or BGP, a
change in the configuration of one router (e.g., adding a new network, modifying
routing metrics) can influence the routing tables of other routers. These changes
are dynamically propagated across the network.
2. DHCP Configuration:
o If you configure a DHCP server on a router and change its settings (e.g., IP
address ranges, lease times), it affects how devices on the network obtain their IP
addresses, but it doesn't change the configurations of other routers.
3. Network Services (e.g., NAT, Firewall):
o Enabling or modifying services like NAT or firewall rules on a router can impact
how traffic flows through the network, but other routers maintain their existing
configurations.
4. Telnet/SSH Access:
o Changes in Telnet or SSH configurations (e.g., enabling/disabling access,
changing credentials) affect only the specific device and how administrators can
remotely access it.

When Device Configurations Remain Independent:

1. Static Configurations:
o Static IP addresses, static routes, and manual VLAN configurations are
independent and must be individually updated on each device.
 2. Device-Specific Settings:
o Each device has its unique configuration settings (e.g., hostname, interface
settings) that do not automatically propagate to other devices.

Centralized Management:

 In enterprise environments, network management tools like Cisco DNA Center or

SolarWinds can provide centralized management and configuration capabilities, allowing
administrators to push configurations to multiple devices simultaneously. However, this
requires specific management platforms and is not inherent to the basic operation of
network devices.

 Assign VLANs:

 On Switch0:

plaintext

enable
configure terminal
vlan 10
name VLAN10
exit
interface range fa0/1-2
switchport mode access
switchport access vlan 10
exit

 On Switch1:
 plaintext

enable
configure terminal
vlan 20
name VLAN20
exit
interface range fa0/1-2
switchport mode access
switchport access vlan 20
exit

 Configure DHCP:

 On the Router:

plaintext

enable
configure terminal
ip dhcp pool VLAN10
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 8.8.8.8
exit
ip dhcp pool VLAN20
network 192.168.2.0 255.255.255.0
default-router 192.168.2.1
dns-server 8.8.8.8
exit
interface Gig0/0/1
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
interface Gig0/0/2
ip address 192.168.2.1 255.255.255.0
no shutdown
exit

 Configure Routing:

 On the Router:

plaintext

enable
configure terminal
ip routing
interface Gig0/0/1
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
interface Gig0/0/2
 ip address 192.168.2.1 255.255.255.0
no shutdown
exit

 Configure SSH:

 On the Router:

plaintext

enable
configure terminal
hostname Router
ip domain-name example.com
crypto key generate rsa
modulus 1024
ip ssh version 2
username admin privilege 15 secret adminpassword
line vty 0 4
login local
transport input ssh
exit

 Configure VTP:

 On Switch0 (Server Mode):

plaintext

enable
configure terminal
vtp mode server
vtp domain example
vtp password vtp_password
exit

 On Switch1 (Client Mode):

plaintext

enable
configure terminal
vtp mode client
vtp domain example
vtp password vtp_password
exit