CIS 192

Introduction to
Networking Introduction to
Networks v6 Companion
Module 11 Guide

Build a Small Network Cisco Press

CLO: Identify the main topics of concern in a modern office environment.

Fall
2024
Module Objectives

Module Objective: Implement a network design for a small network to include a router, a switch, and
end devices.

Topic Title Topic Objective

Devices in a Small Network Identify the devices used in a small network.

Small Network Applications and Protocols Identify the protocols and applications used in a small network.

Scale to Larger Networks Explain how a small network serves as the basis of larger networks.

Use the output of the ping and tracert commands to verify connectivity
Verify Connectivity
and establish relative network performance.
Use host and IOS commands to acquire information about the devices
Host and IOS Commands
in a network.

Troubleshooting Methodologies Describe common network troubleshooting methodologies.

Troubleshooting Scenarios Troubleshoot issues with devices in the network.

2
Small Network Topologies

• A small network design is usually

simple.
• Typically have a single WAN
connection provided by DSL, cable,
or an Ethernet connection.
• One to few subnets

• Small networks can be managed by a local IT technician or a

contracted professional.
• Large networks need an IT department for maintenance, security, troubleshooting, and
data protection.
• Both large and small networks require planning and design to meet
user needs.
3
Devices

• End user devices (wired, wireless, remote access)

• Servers and peripherals (printers, security cameras)
• Intermediary devices (switches, access points)

Factors to consider when

selecting network devices:
• cost
• speed and types of
ports/interfaces
• expandability
• operating system features
and services

4
IP Addressing
• Plan, create and implement a unique IP
addressing scheme for all network
devices.
• Document and maintain the IP
addressing scheme by device type for
easier identification and troubleshooting.

5
Redundancy in a Small Network

• Duplicate equipment and add additional links in critical

areas
• Eliminate single points of failure
• Ensure reliability

6
Remote Access
• Network administrators may
require remote access to network
devices and servers.
• The common remote access
solutions are Telnet and Secure
Shell (SSH).
• SSH is a secure alternative to
Telnet.
• Network device & Server must
support SSH

7
Remote Access
Enable Telnet client
Try
• telnet towel.blinkenlights.nl
• telnet freechess.org 5000

8
Applications and protocols
• Prefer secure protocols (e.g.,
SSH, SFTP, HTTPS) for better
security.

9
Real-Time Applications and Traffic Management
Examples: VoIP, IP Telephony
• IP Telephony uses dedicated servers for call management.
• VoIP offers cost savings but may compromise quality.

Considerations for Real-Time Applications:

• Infrastructure Capacity
• Supporting Protocols: e.g. RTP and RTCP
• Quality of Service (QoS): to minimize
latency for real-time applications.

 Routers and switches should be

configured using QoS.
 Priority queuing has four queues,
with the high-priority queue emptied
first.
10
Scale to Larger Networks

Growth Alignment:
• Network must grow alongside business.
• Timely decisions by the network administrator are essential.

Elements Required for Scaling:

• Network Documentation: Physical and logical topology.
• Device Inventory: Comprehensive list of network devices.
• Traffic Analysis: Document protocols, applications, and traffic requirements
• Budget: Detailed IT budget, including equipment procurement.

11
Protocol Analysis
• Determine traffic flow patterns
and Network Utilization:
• Capture traffic during peak
times for accurate data.
• Analyze various network
segments as traffic may differ.
• Evaluate traffic based on
source, destination, and type.
• Utilize findings to optimize
traffic management.
• A simple protocol analyzer such
as Wireshark can be used

12
Verify Connectivity - Ping
• Ping command, Internet Control Message Protocol (ICMP)
• Extended Ping: allows the administrator to adjust parameters related to the command

13
Verify Connectivity - Traceroute
• Traceroute can help locate Layer 3 problem areas in a
network.
• Extended traceroute allows the administrator to adjust
parameters related to the command operation

Note: Use Ctrl-C to interrupt a tracert in Windows

14
Network Baseline
• Establish a network baseline for monitoring and troubleshooting performance.
• Start by saving results from commands (ping, trace) in timestamped text files.
• Record error messages and response times for host comparisons.
• Corporate networks require extensive baselines; consider professional software tools for
management.

15
Troubleshooting Methodologies - Basic Troubleshooting Approaches

Step Description

Step 1. Identify the Problem Use tools, talk to the user

Step 2. Establish a Theory of
Identify few probable causes to the problem.
Probable Causes

Step 3. Test the Theory to •Apply a quick fix to test and see if it solves the problem.
Determine Cause •If a quick fix does not correct the problem, research the problem further

Step 4. Establish a Plan of Action Establish a plan of action to resolve the problem and implement the
and Implement the Solution solution.
Step 5. Verify Solution and •After you have corrected the problem, verify full functionality.
Implement Preventive Measures •If applicable, implement preventive measures.

Step 6. Document Findings,

This is very important for future reference.
Actions, and Outcomes

16
Troubleshooting Methodologies - Resolve or Escalate?

• In some situations, it may not be possible to resolve the problem immediately.

• A problem should be escalated when it requires a manager decision, some specific
expertise, or network access level unavailable to the troubleshooting technician.
• A company policy should clearly state when and how a technician should escalate a
problem.

17
Troubleshooting Scenarios
•Duplex Operation and Mismatch
• Requirement: Ethernet interfaces should match duplex modes (full vs. half).
• Mismatch Effects: Communication continues, but performance degrades.
• Autonegotiation: Minimizes misconfigurations by selecting the best link performance.

•IP Addressing Issues on IOS Devices

• Common Causes: Manual mistakes or DHCP issues.
• Verification: Use show ip interface or show ip interface brief commands.

•End Device IP Addressing

• APIPA: Windows assigns 169.254.0.0/16 when DHCP fails, causing communication
issues.
• Verification: Use ipconfig to check IP on Windows devices.

18
Troubleshooting Scenarios
•Default Gateway Issues
• Function: The gateway forwards traffic to remote networks.
• Causes: Misconfiguration or DHCP failures.
• Verification:
• Windows: Use ipconfig.
• Router: Use show ip route to check the routing table.

•DNS Troubleshooting
• Common Mistakes: Users may confuse DNS issues with internet connectivity.
• DNS Server Assignment: Can be manual or through DHCP.
• Verification:
• Windows: Use ipconfig /all to see the DNS server.
• Command-Line Tool: Use nslookup for DNS queries and responses.
• OpenDNS: Cisco's secure DNS service (208.67.222.222, 208.67.220.220).

19
Activity

Refer to the exhibit.

Ōltus is not able to connect to PCB and he suspects a problem with router R1, What
are the connectivity test commands that could verify his assumption?

Ōltus: An Indigenous name comes from Harrison Lake. ( 20

http://digitalsqewlets.ca/stames/languages-langues-eng.php )
Host and IOS Commands - Revisited
•IP Configuration on Windows Host
• Access IP settings via Network and Sharing Center or run ipconfig command.
• Use ipconfig /all to view MAC address and Layer 3 details.
• For DHCP clients, renew IP with ipconfig /release and ipconfig /renew.
• Utilize ipconfig /displaydns to view cached DNS entries.

•IP Configuration on Linux Host

• GUI verification varies by distribution; use ifconfig for current interface status on command line.
• The ip address command displays and manages IP addresses; syntax may differ by distribution.

•IP Configuration on macOS Host

• View IP settings in GUI: Network Preferences > Advanced.
• Use ifconfig on command line for IP configuration checks.
• Useful commands: networksetup -listallnetworkservices and networksetup -getinfo
<network service>.

21
Host and IOS Commands - Revisited

The arp Command

• arp Command: Executed in Windows, Linux, or Mac command prompt; lists devices in
ARP cache.
• arp -a Command: Displays IP and MAC address bindings; shows only recently
accessed devices.
• Populating ARP Cache: Ping a device to create an entry in the ARP table.
• Clearing ARP Cache: Use `netsh interface ip delete arpcache` to repopulate with
updated info.
• Note: Administrator privileges may be required to execute the cache deletion command.

22
Host and IOS Commands - Revisited
Common show Commands
Command Description
show running-config Verifies the current configuration and settings
show interfaces Verifies the interface status and displays any error
messages
show ip interface Verifies the Layer 3 information of an interface
show ip interface brief provides a summary of the key information for all the
network interfaces on a router
show arp Verifies the list of known hosts on the local Ethernet LANs
show ip route Verifies the Layer 3 routing information
show protocols Verifies which protocols are operational
show version Verifies the memory, interfaces, and licenses of the device

23
Host and IOS Commands - Revisited

The show cdp neighbors command provides the following information about each CDP
neighbor device:
• Device identifiers - The configured host name of a switch, router, or other device
• Address list - Up to one network layer address for each protocol supported
• Port identifier - The name of the local and remote port in the form of an ASCII character
string, such as FastEthernet 0/0
• Capabilities list - Whether a specific device is a Layer 2 switch or a Layer 3 switch
• Platform - The hardware platform of the device.

24
Host and IOS Commands - The debug Command
• Function: Displays OS processes, protocols, and event messages in real-time.
• Access: Entered in privileged EXEC mode.
• Usage: Only for troubleshooting specific issues.
• Use debug ? to view command options.
• You can narrow output to relevant features or sub-features.
• Disable a specific debugging feature: Use no debug or undebug .
• Turn Off All: Use undebug all.

• Caution: debug can generate substantial output,

impacting system resources and performance.
• Remote Logging: Debug output not displayed on
remote (vty) connections.

• Terminal Monitor: Use terminal monitor to display log

messages on a terminal. To stop logging messages on
a terminal, use the terminal no monitor command.

25