Networking Fundamentals and CompTIA Network+ Study Notes

Networking Concepts and Network Infrastructure Overview

  • Definition of a Network: A network consists of two or more computer systems linked by a transmission medium and sharing one or more protocols that enable them to exchange data.
  • Nodes and Links:
    • Nodes: Devices that send, receive, and forward data. These are categorized into:
    • Intermediate Nodes: Perform a forwarding function (e.g., switches, routers).
    • End Systems: Nodes that send and receive data traffic, often referred to as hosts.
    • Links: The communications pathways between nodes.
  • Client-Server vs. Peer-to-Peer Networks:
    • Client-Server Network: Some nodes (PCs, laptops, smartphones) act as clients and consume services provided by more powerful computers called servers. Application services and resources are centrally provisioned, managed, and secured. Even in this model, a host can be both; for example, a web application server is a server to browser clients but a client to database services.
    • Peer-to-Peer (P2P) Network: Every host acts as both a client and a server. This is a decentralized model where provision, management, and security are distributed. Small P2P networks are called workgroups. Business/Enterprise networks are typically client-server, while residential networks are often peer-to-peer.

Networking Appliances, Applications, and Functions

  • Appliances: Specialized platforms designed for a particular network role (unlike general-purpose Windows or macOS systems). Examples include:
    • Switches and Routers: Forward data.
    • Wireless Access Points (APs): Facilitate wireless connectivity.
    • Firewalls and Intrusion Detection Systems (IDS): Enforce security rules.
    • Load Balancers and Proxies: Improve network performance.
    • Deployment: Can be physical hardware (dedicated CPU, memory, storage) or virtual appliances (deployed as a virtual machine on a hypervisor).
  • Applications: Shared services that allow the network to perform useful work, such as file sharing or email.
  • Functions: Additional properties configured in a network, such as:
    • Virtual Private Network (VPN): Security properties allowing remote devices to join a local network.
    • Quality of Service (QoS): Functionality to optimize the network for time-sensitive applications like voice or video.

Network Types by Size and Scope

  • Network Size: Measured by the number of nodes.
  • Network Scope: Refers to the area over which nodes sharing the same network address are distributed.
  • Local Area Network (LAN): Confined to a single geographical location. All nodes/segments connect directly with cables or short-range wireless. Infrastructure is usually owned and managed by a single organization.
    • Home/Residential Network: Internet router, a few computers, mobile devices, consoles, and printers.
    • Small Office/Home Office (SOHO) Network: Business-oriented, might use a central server but still relies on a single router/switch/access point.
    • Small and Medium-sized Enterprise (SME) Network: Supports dozens of users; uses structured cabling and multiple switches/routers.
    • Enterprise LAN: Large network with hundreds or thousands of servers and clients; requires enterprise-class appliances.
  • Wide Area Network (WAN): A network of networks connected by long-distance links. WANs can link branch offices globally or connect datacenters. They often use leased network devices and links managed by service providers.
  • Datacenter: A network hosting only servers and storage, not end-user client devices.

Network Topologies: Physical and Logical

  • Physical Topology: Describes the placement of nodes and how they are connected by transmission media.
  • Logical Topology: Describes the flow of data through the network. Two networks can have different physical connections but the same logical layout.
  • Point-to-Point Topology: A 1:1 relationship between two nodes. Only two devices share the connection, guaranteeing bandwidth.
    • Physical Point-to-Point: Connected by a single cable.
    • Logical Point-to-Point: Two routers on a WAN might be linked via many intermediate networks but can only address each other directly.
    • Communication Modes:
    • Half-Duplex: A node cannot transmit and receive at the same time.
    • Full-Duplex: Nodes can transmit and receive simultaneously.
  • Star Topology: Each endpoint node is connected to a central forwarding appliance (concentrator) like a switch or router. It is the most widely used physical topology.
    • Hub vs. Switch: A hub (repeater) sends signals to all ports indiscriminately. A modern switch/router tracks addresses and switches communication paths point-to-point.
    • Advantages: Easy to reconfigure and troubleshoot; central management; faults are easily isolated to a specific cable or node.
    • Disadvantage: The central concentrator is a single point of failure.
    • Hub-and-Spoke: Same physical layout as star but common in WANs with remote sites.
  • Mesh Topology: Commonly used in WANs and public networks like the Internet.
    • Fully Connected Mesh: Every node has a point-to-point link with every other node.
    • Link Requirement Formula: n(n−1)2\frac{n(n-1)}{2}, where nn is the number of nodes. Example: 4 nodes require 6 links; 40 nodes require 780 links.
    • Partial Mesh: A hybrid approach where only important devices are interconnected. This offers redundancy and fault tolerance without the cost of a full mesh.
  • Legacy Topologies:
    • Bus Topology: A trunk cable with nodes attached via drop cables. A terminator is required at both ends to absorb signals and prevent reflection. A single break in the cable disrupts the whole network.
    • Ring Topology: Connects nodes in a circular loop. Signals travel in one direction, with each device acting as a repeater. A manifold failure or break disrupts signal flow beyond that point.

The OSI Reference Model

  • Developer: International Organization for Standardization (ISO).
  • Purpose: A functional guideline for designing protocols, software, and appliances and for troubleshooting.
  • Data Encapsulation and Decapsulation:
    • Encapsulation: The process by which a protocol adds header fields (and sometimes trailers) to a payload arriving from a higher layer on the sending node. This forms a Protocol Data Unit (PDU).
    • Decapsulation: The reverse process on the receiving node where headers are stripped to extract the original data.
    • Same Layer Interaction: Communication between identical layers on two different nodes.
    • Adjacent Layer Interaction: A layer providing services to the layer above and using services from the layer below on the same node.

OSI Model Layers and PDUs

  • Layer 7: Application: Provides an interface for software programs (web browsing, email, directory lookup). PDUs are simply called data or Application PDUs.
  • Layer 6: Presentation: Transforms data formats (e.g., character set conversion like ASCII to Unicode), compression, and encryption.
  • Layer 5: Session: Administers sessions or dialogs (establishing, managing, and tearing down communication).
  • Layer 4: Transport: Identifies application types using port numbers (e.g., Port 80 for HTTP, Port 25 for SMTP, Port 445 for SMB, Port 5061 for Voice). Responsible for end-to-end data delivery and reliability. PDU: Segment.
  • Layer 3: Network: Responsible for internetworking and moving data between different networks using logical addresses (IP). Routers operate here. Includes basic firewalls/ACLs. PDU: Packet or Datagram.
  • Layer 2: Data Link: Responsible for transferring data between nodes on the same logical segment using hardware/MAC addresses. Bridges, switches, and access points operate here. PDU: Frame.
  • Layer 1: Physical: Responsible for the transmission and receipt of signals representing bits. Includes cables, wireless transceivers, repeaters, hubs, and media converters. PDU: Bits.

SOHO Network Implementation and Components

  • SOHO Router: An integrated appliance performing multiple functions:
    • Physical Layer Functions: RJ45 LAN ports (usually 4), Radio antennas for Wi-Fi, and a WAN port (RJ45 for fiber/Ethernet, RJ11 for DSL, or F-connector coax for cable).
    • Data Link Layer Functions: An internal Ethernet switch connecting LAN ports and an internal bridge connecting the wireless access point to the switch.
    • Network Layer Functions: Performed via IP addresses. It uses a DHCP (Dynamic Host Configuration Protocol) Server to allocate unique private addresses (e.g., in the range 192.168.1.100192.168.1.100 to 192.168.1.199192.168.1.199) to local hosts.
    • Transport/Application Layer Security: Firewall rules based on port numbers (e.g., blocking SMB/Port 445 on the WAN interface). Management interface security requires a strong passphrase.
  • Internet Connectivity Terms:
    • Customer Premises Equipment (CPE): Termination/routing equipment at the customer site.
    • Local Loop: Cabling from the premises to the local exchange.
    • Demarcation Point (Demarc): Where the telco's cabling enters the premises.

Addressing and Standards Organizations

  • Internet Assigned Numbers Authority (IANA): Manages IP addresses and top-level domains. Run by ICANN.
  • Internet Engineering Task Force (IETF): Develops standards published as Requests for Comments (RFCs).
  • Internet Model (TCP/IP model): A 4-layer simplified hierarchy:
    • Link Layer (OSI 1-2)
    • Internet Layer (OSI 3)
    • Transport Layer (OSI 4-5)
    • Application Layer (OSI 6-7)
  • Numbering Systems:
    • Decimal (Base 10): Values 0-9. Value of 255 is (2×10×10)+(5×10)+5(2 \times 10 \times 10) + (5 \times 10) + 5.
    • Binary (Base 2): Values 0 and 1. 8 bits equal one byte or octet. Binary 11111111 equals 255.
    • Hexadecimal (Base 16): Values 0-9 and A-F. Used for MAC addresses. One hex digit equals a nibble (4 bits). Decimal 255 is expressed as 0xFF0xFF.

CompTIA Troubleshooting Methodology

  1. Identify the Problem:
    • Gather information from tickets or monitoring systems.
    • Question users (Open vs. Closed questions).
    • Identify symptoms and determine if anything has changed ("Did it ever work?", "What happened at 9:00 a.m.?").
    • Duplicate the problem if possible.
    • Approach multiple problems individually.
  2. Establish a Theory of Probable Cause:
    • Question the obvious (is it plugged in?).
    • Use OSI Model approaches (Top-to-Bottom or Bottom-to-Top).
    • Divide and Conquer: Start at the most likely layer and work up or down.
  3. Test the Theory to Determine Cause:
    • If confirmed, plan resolution.
    • If not, establish a new theory or escalate (refer to senior tech, manager, or third party due to scope, warranty, or difficulty).
  4. Establish a Plan of Action:
    • Solutions involve: Repair, Replace, or Accept (workaround).
    • Use "known good" duplicates for substitution testing.
    • Identify potential effects on the rest of the system.
  5. Implement the Solution or Escalate:
    • Follow change management plans.
    • Conduct implementation during non-disruptive times.
    • Use sandbox environments for trials.
    • Back up data/configurations before proceeding.
  6. Verify Full System Functionality:
    • Validate the fix and ensure no new problems were created.
    • Implement preventive measures (e.g., labeling jacks, setting up failover).
  7. Document Findings, Actions, and Outcomes:
    • Record in the ticket system (description, findings, solution).
    • Conduct lessons learned to improve network design and procedure.