Enterprise Infrastructure and Cloud Technologies

Networking Fundamentals

• Enterprise Infrastructure and Cloud Technologies overviewed across the transcript as the umbrella topic.

• Data Communication basics are presented with steps and the core elements: Protocol, Message, Medium, Sender, Receiver. The transcript lists Step 1, Step 2, Step 3, but does not provide explicit details for these steps in the copied content.

Data Communication and Protocols (Overview)

• Protocol, Message, Medium, Sender, Receiver are core concepts in data communication.

• When two devices exchange data, they do so over a transmission medium (wired or wireless) using a protocol to structure the data and control communication.

NETWORKS: Core Concepts

• A network is the interconnection of devices capable of communication.

• Devices in a network can be:

  • Hosts / end systems: e.g., large computer, desktop, laptop, workstation, cellular phone, security system.

  • Connecting devices: router (connects networks), switch (connects devices), modem (modulator-demodulator) and others.

• Transmission media can be wired or wireless (cable or air).

• A home plug-and-play router can create a network, even if small.

Network Criteria

• A network must meet key criteria: Performance, Reliability, Security.

Performance

• Measured by transit time and response time:

  • Transit time: time for a message to travel from one device to another.

  • Response time: elapsed time between an inquiry and a response.

• Performance depends on factors such as: number of users, type of transmission medium, hardware capabilities, software efficiency.

• Metrics often used: throughput and delay. High throughput is desirable, low delay is desirable. Trade-offs exist: increasing data can improve throughput but may increase delay due to congestion.

• Symbolically: throughput and delay are often inversely related in congested networks.

Reliability

• Reliability metrics include: frequency of failure, recovery time of a link, and network robustness in catastrophes.

Security

• Security concerns include: protecting data from unauthorized access, protecting data from damage/theft/loss, and implementing recovery policies after breaches or data losses.

Network Devices

• Network devices are physical devices that enable communication among hardware on a network.

• Common devices include: hubs, repeaters, bridges, switches, routers, gateways, and brouters.

• Roles range from simple forwarders to complex routers; they control data transfer, boost signals, and link networks.

Common Types of Network Devices (List)

• Hub, Router, Gateway, NIC, Modem, VPN, Repeater, WAP, Firewall, IDPS (Intrusion Detection/Prevention System), VPN (listed again in some slides)

Functions of Network Devices

• Send and receive data between devices.

• Enable devices to connect to the network efficiently and securely.

• Improve network speed and manage data flow.

• Protect the network by access control and threat prevention.

• Extend network range and mitigate signal problems.

Common Networking Devices and Their Uses

• Access Point, Modems, Firewalls, Repeater, Hub, Bridge, Switch, Routers, Gateway, Brouter, NIC.

Access Point and Modems (Key Roles)

• Access Point: Enables wireless devices (smartphones, laptops) to connect to a wired network; creates a Wi‑Fi network to communicate with the internet or other devices.

• Modem: Converts digital signals to analog (and vice versa) for transmission; used by customers to access the internet via an ISP.

Firewalls

• A firewall monitors and controls data flow between a computer/network and the internet.

• Acts as a barrier to block unauthorized access while allowing trusted data through.

• Can be hardware, software, or cloud-based (SaaS, public cloud, or private cloud).

Repeater and Hub

• Repeater: Operates at the physical layer; amplifies/regenerates signals to extend transmission distance (bit-by-bit copy).

• Hub: A multiport repeater; connects multiple wires in a star topology. Cannot filter data; broadcasts to all connected devices; lacks intelligence to find optimal data paths.

Bridge and Switch

• Bridge: Operates at the data link layer; a repeater with MAC-address-based filtering; interconnects two LANs using the same protocol.

• Switch: A multiport bridge with buffering; operates at the data link layer; can perform error checking and forward only error-free packets to the correct port; improves efficiency.

Router and Gateway

• Router: Routes data packets based on IP addresses; primarily a Network Layer device; connects LANs and WANs; maintains a dynamic routing table.

• Gateway: A conduit between networks that may operate on different networking models; acts as a protocol converter; can operate at any layer and is more complex than switches/routers.

Brouter and NIC

• Brouter (bridging router): Combines features of bridge and router; can operate at data link layer or network layer; routes across networks and filters LAN traffic when acting as a bridge.

• NIC (Network Interface Card): Network adapter that connects a computer to the network; has a unique hardware ID; works at Layer 2 (physical and data link layers).

OSI Model (Layered View of Networking)

• 7 layers from bottom to top with brief descriptions:

  • 1 Physical: Encodes signals, cabling and connectors; physical specifications.

  • 2 Data Link: Assigns local addresses to interfaces, delivers information locally; MAC method.

  • 3 Network: Assigns global addresses to interfaces and determines the best routes through different networks.

  • 4 Transport: Transmits data using transmission protocols including TCP & UDP.

  • 5 Session: Establishes, manages, and terminates sessions between end nodes.

  • 6 Presentation: Encrypts, encodes and compresses usable data.

  • 7 Application: The closest layer to the user; provides application services.

OSI Model Summary and Legacy Context

• The OSI model is a historical framework developed by ISO to standardize how different computer systems communicate over a network.

• It provides a reference for layering network functions and guidance for designing interoperable systems.

LAN vs WAN and Network Scope

• LAN (Local Area Network): Private ownership; short propagation delay; confined to a building or campus.

• WAN (Wide Area Network): Covers large geographic areas (country/continent); may be public or private; uses PSTN or satellite media; higher cost and longer propagation delays.

IPv4: Addressing and Routing Fundamentals

What is IPv4?

• Internet Protocol version 4 (IPv4) is the most widely used system for identifying devices on a network.

• Addresses are 32-bit integers written in decimal dot notation, e.g., 192.168.0.1.

• IPv4 was the primary production version in ARPANET in 1983.

IP Addressing Purposes

• Identification: uniquely identifies a device on a network.

• Location Addressing: indicates where a device is located within a network to enable routing.

IPv4 Addressing Structure

• Consists of four octets (eight bits each) separated by periods (dot-decimal notation).

• Each octet ranges from 0 to 255: 0 ext{ to } 255.

• Example addresses shown in the transcript include: 104.244.42.129, 151.101.65.140, 108.174.10.10.

IPv4 Parts

• Network Part: identifies the network portion.

• Host Part: identifies the specific host within the network.

• Subnet Number (optional): divides large networks into subnets.

Address Classes (IPv4 Classification)

• Class A: first bit 0; range 0.0.0.0 to 127.255.255.255; 8 network bits, 24 host bits.

• Class B: first two bits 10; range 128.0.0.0 to 191.255.255.255; 16 network bits, 16 host bits.

• Class C: first three bits 110; range 192.0.0.0 to 223.255.255.255; 24 network bits, 8 host bits.

• Class D: first four bits 1110; multicast usage; reserved for multicast groups.

• Class E: first four bits 1111; experimental use; range 240.0.0.0 to 255.255.255.255.

IPv4 Addressing Modes

• Unicast: single sender to single receiver (e.g., accessing a website).

• Broadcast: for all devices on the local network.

• Multicast: group delivery to multiple devices (e.g., streaming to multiple devices).

IPv4 Header (Key Fields; typical list)

• Version, IHL (Header Length), Type of Service, Total Length, Identification, Flags, Fragment Offset, Time to Live, Protocol, Header Checksum, Source IP Address, Destination IP Address, Options (0–40 bytes).

• Minimum header size: 20 ext{ bytes}; maximum header size: 60 ext{ bytes}.

• Fragmentation-related fields (DF, MF, Fragment Offset) and routing-related fields (TTL, Protocol) are important for routing and reliability.

IPv4 Advantages and Limitations (as listed)

• Advantages: scalable routing and addressing; supports simple network design; suitability for multicast.

• Limitations: finite address space; complex routing configurations; security, QoS, mobility, multi-homing, multicasting concerns; IPv4 requires NAT for many deployments.

IPv4 Limitations Context

• Worlds’ IPv4 address space is finite and depleting; motivates IPv6 adoption.

IPv4 Addressing and Routing Context

• RIP and other routing protocols are used at the routing layer.

• DHCP or manual configuration is used for address assignment.

IPv6: Next-Generation Addressing

• IPv6 is designed to replace IPv4 due to address space exhaustion and to improve features at the network layer.

• Address space: 128-bit address space; theoretical maximum of about 3.40 imes 10^{38} addresses (340 undecillion).

• IPv6 provides features like built-in autoconfiguration, improved routing efficiency, and better security integration (IPsec).

• IPv6 address length and format: eight groups of four hexadecimal digits separated by ':'; total length 128 bits; example address format: 2001:0DC8:E004:0001:0000:0000:0000:FOOA (groups shown as 16-bit blocks).

IPv6 Address Structure (Key Parts)

• Global Routing Prefix: first 48 bits identifying a specific network/subnet.

• Subnet ID / Student ID: next 16 bits used within an organization to identify subnets.

• Interface ID / Host ID: last 64 bits identifying a specific interface/host.

• Example annotation: the first 48 bits are the Global Routing Prefix, next 16 bits for subnet/student identification, last 64 bits for host/interface.

IPv6 Address Types

• Unicast: a single interface identified by the address.

• Multicast: a group of interfaces; used as a destination for multicast delivery.

• Anycast: multiple interfaces share the same address; the packet is delivered to the nearest one among the group (no single recipient address ownership).

IPv6 Advantages

• Faster speeds through multicast delivery (no broadcast); stronger security with built-in IPsec; improved routing efficiency and reliability; autonomous address configuration; easier prefix aggregation; better support for growing networks.

IPv6 Disadvantages

• Dual-stack transition challenges with IPv4.

• Direct IPv4 and IPv6 devices cannot communicate natively without translation or tunneling.

• Migration complexity and not backward compatible in a single upgrade step.

IPv6 vs IPv4: Quick Differences

• Address length: IPv6 128-bit vs IPv4 32-bit.

• Address representation: hexadecimal groups with ':' in IPv6 vs decimal dot notation in IPv4.

• Header checksums: IPv6 does not maintain a checksum field (unlike IPv4).

• Header size: IPv6 header fixed at 40 bytes; IPv4 header 20–60 bytes depending on options.

• Subnetting: IPv6 supports simple aggregation of prefixes; IPv4 uses Variable Length Subnet Mask (VLSM).

IPv4 Datagram Header (Summary)

• IPv4 header contains fields for routing, fragmentation, and quality of service, with a fixed header length and a variable options field.

Data Center and Storage Concepts

What is a Data Center?

• A data center is a physical facility hosting critical applications and data.

• Key components include routers, switches, firewalls, storage systems, servers, and application-delivery controllers.

Modern Data Center Characteristics

• Shift from on-premises physical servers to virtual networks.

• workloads span across pools of physical infrastructure and multi-cloud environments.

• Data and applications exist across multiple sites (on-premises, edge, public/private clouds).

• Cloud providers supply data center resources for hosted applications.

Why Data Centers Matter for Business

• Support for core business applications: Email/File sharing, productivity apps, CRM, ERP/databases, big data/AI/ML, virtual desktops, collaboration services.

Core Data Center Components

• Network infrastructure: routers, switches, firewalls; connects servers, storage, services, and end users.

• Storage infrastructure: storage systems for data storage and access.

• Computing resources: servers providing processing, memory, storage, and network connectivity.

Data Center Operations and Security

• Security appliances like firewalls and intrusion protection to safeguard data.

• Application delivery assurance via load balancing and automatic failover.

Server and Storage Types in Modern Infrastructures

Storage Types

• DAS (Direct Attached Storage): storage directly connected to a server (SATA/SAS/USB/Thunderbolt).

  • Pros: simple, inexpensive, low latency for a single server.

  • Cons: limited sharing/scalability, harder to manage in multi-server environments.

• NAS (Network Attached Storage): file-level storage accessible over a network; shared file access.

  • Pros: easy setup, cross-OS file sharing, scalable.

  • Cons: network traffic affects performance, may not suit high-performance apps.

• SAN (Storage Area Network): dedicated high-speed network for block-level storage access to multiple servers.

  • Pros: high performance, low latency, scalable, centralized management.

  • Cons: more complex and expensive than DAS/NAS.

RAID: Redundant Array of Independent Disks

• Purpose: combine multiple disks into a single logical unit for reliability and performance.

• RAID Levels:

  • RAID 0 (Striping): data striped across disks for speed; no redundancy.

  • RAID 1 (Mirroring): exact copy on another disk; redundancy.

  • RAID 5 (Striping with Parity): data + parity across disks; performance + redundancy.

  • RAID 6 (Striping with Double Parity): like RAID 5 with two parity blocks; higher fault tolerance.

  • RAID 10 (Mirroring + Striping): combines mirroring and striping; high performance and redundancy.

Storage Protocols for SANs

• Fibre Channel (FC): high-speed dedicated SAN protocol.

• iSCSI: SCSI commands over TCP/IP over Ethernet; uses existing Ethernet hardware.

• Fibre Channel over Ethernet (FCoE): FC frames encapsulated in Ethernet for converged networks; requires CNAs and a Converged Enhanced Ethernet (CEE) network.

File Systems and Storage Landscape

What is a File System?

• A logical/physical system for organizing, managing, and accessing files/directories on storage media (SSD/HDD/optical, etc.).

• Enables OS to distinguish files and provide metadata like size, creation date, location, etc.

Common File System Types

• FAT (File Allocation Table): old, simple, widely compatible; limitations on file/volume sizes.

• NTFS (New Technology File System): Windows default; features include security, reliability, larger files/volumes, journaling, compression, encryption, quotas.

• ReFS (Resilient File System): Microsoft file system for data integrity in large datasets; copy-on-write, resilience to corruption.

• EXT3/EXT4: Linux file systems; EXT3 adds journaling; EXT4 adds performance/scalability improvements (extents, delayed allocation).

How File Systems Work

• Store and organize data; provide a directory hierarchy (paths); maintain metadata (size, date, location).

• Directories form an inverted hierarchical tree with a root directory at the top.

Operating Systems: Server vs Client

What is an Operating System (OS)?

• System software that manages hardware and software resources and provides services to programs.

• Bridges user and hardware; enables efficient use of the system.

Server Operating System (Server OS)

• Designed to run on servers and provide essential services to clients over a network.

• Built for reliability, performance, secure multi-user operations.

• Key characteristics:

  • Multi-user support, resource sharing, network services (DNS, DHCP, web, email, Active Directory), security, scalability, remote management.

• Common server OS examples: Windows Server, Ubuntu Server, Red Hat Enterprise Linux (RHEL), CentOS/Rocky Linux, SUSE SLES, macOS Server (deprecated).

• Typical roles: Active Directory Domain Controller, File Server, Web Server (IIS/Apache/NGINX), Email Server, Database Server, Virtualization Host.

Client Operating System (Client OS)

• Designed for end-user devices (desktops, laptops, tablets, smartphones).

• User-focused, single-user environments, application-centric.

• Key characteristics:

  • User-friendly GUI, multimedia support, limited network services, lighter security features, automatic updates.

• Common client OS examples: Windows 11/10/8.x, macOS, Linux Desktop (Ubuntu/KDE, etc.), Chrome OS; mobile: Android, iOS.

Server OS vs Client OS: Quick Comparison

• Purpose: Server OS -> manage network resources/services; Client OS -> end-user tasks.

• User access: Server OS supports multiple remote sessions; Client OS for a single user.

• Resource management: Server OS handles heavy workloads; Client OS optimized for individual use.

• Security: Server OS offers advanced security features (AD, Group Policy, DNS/DHCP, RADIUS); Client OS basic security.

• Licensing: Server OS often involves CALs; Client OS generally pre-installed and cheaper.

• GUI: Server OS often minimal or remote management; Client OS full GUI.

• Update cycle: Server OS updates are enterprise-focused; Client OS updates are frequent for consumer devices.

Windows Server and Client Ecosystem (Selected Highlights)

• Windows Server versions span from early NT-based servers to modern LTSC releases; major milestones include the introduction of Active Directory (Windows 2000 Server), Server Core, Hyper-V, Storage Spaces, Windows Admin Center, Secured-core, TLS 1.3, Azure integration, and more.

• Windows Client OS lineage includes Windows 1.0 through Windows 11, with notable milestones like Windows 95 introducing Start Menu/plug-and-play, Windows XP long support, Windows 7 stability, Windows 8/8.1 Metro UI, Windows 10 as Windows as a Service, and Windows 11 modern UI with TPM 2.0 requirements.

Server OS Versions: Selected Milestones (Examples)

• Windows NT 3.1 Advanced Server (1993): First server OS based on NT; basic file/print services.

• Windows NT 4.0 Server (1996): GUI similar to Windows 95; IIS web hosting introduced.

• Windows 2000 Server (2000): Introduced Active Directory; Group Policy; Kerberos; NTFS improvements.

• Windows Server 2003 / 2003 R2 (2003/2005): Improved AD, file replication, branch office improvements.

• Windows Server 2008 / 2008 R2 (2008/2009): Server Core, Hyper-V, RODC, BitLocker, Failover Clustering.

• Windows Server 2012 / 2012 R2 (2012/2013): Modern UI, Storage Spaces, IPAM; Hyper-V Replica; NIC teaming.

• Windows Server 2016: Nano Server, Shielded VMs, Docker support, Storage Spaces Direct, JEA.

• Windows Server 2019: Hybrid cloud, System Insights, Storage Migration Service, ATP protection.

• Windows Server 2022: Secured-core server, TLS 1.3, Azure integration, faster networking, nested virtualization, SMB encryption.

• Windows Server 2025 (Upcoming): LTSC with emphasis on Azure hybrid features and management APIs.

• Client OS key milestones mirror consumer-focused evolution (Windows 1.0 → Windows 11) with features like Start Menu, GUI improvements, security enhancements, and ongoing updates.

Common Roles in Server OS Versions

• Active Directory Domain Services (AD DS)

• DNS, DHCP

• File and Storage Services

• Hyper-V (virtualization)

• Web Server (IIS)

• Remote Desktop Services (RDS)

• Print Services

Networking and Security: Event Monitoring and Management (Server-Side)

Server Management Portals (Out-of-Band Management)

• IPMI (Intelligent Platform Management Interface): Open standard for managing server hardware; foundation for iDRAC/iLO; supports monitoring, event logging, and FRU reporting.

• iDRAC (Integrated Dell Remote Access Controller): Dell’s IPMI-based remote management; web interface; features like virtual console/media, power control; variants include Express/Enterprise.

• iLO (Integrated Lights-Out): HPE’s IPMI-based remote management; similar capabilities to iDRAC for HPE ProLiant.

• Out-of-band management allows admin tasks even when OS is down or unavailable; enables remote power control, console access, firmware updates, and health monitoring.

Key Features of Out-of-Band Management

• Remote access to hardware health and console regardless of OS state.

• Centralized control over multiple servers from a single interface.

• Hardware monitoring: fan speeds, temperatures, power status.

Server Management Events

• A broad set of activities related to servers: performance, security, software updates, and more.

• Effective monitoring helps maintain server health and availability.

System Event Categories (Examples)

• System Events: Performance monitoring (CPU, memory, disk I/O, network); hardware events (temperature, fans, power); software events (installations, configurations, errors); service events (start/stop of services).

• Security Events: Login attempts (success/failure), account changes (creation, enabling/disabling), security policy changes, intrusion detection.

• Software Update Events: Patch management; software installation/removal.

• Backup and Recovery Events: Backup success/failure; restore operations.

• Other Events: Event forwarding; server configuration changes.

Tools for Monitoring Server Events

• Event Viewer (Windows): View/manage event logs.

• Server Manager (Windows): Central console for server roles/configurations.

• Extended Events (SQL Server): Monitoring/troubleshooting SQL Server events.

• Security Event Manager (SolarWinds): Centralized security event management.

• EventLog Analyzer (ManageEngine): Log monitoring/analysis.

• Third-party monitoring tools: Broad category of tools for comprehensive monitoring.

Why Monitoring is Important

• Proactive issue identification: Early detection reduces downtime.

• Improved security: Detects unauthorized access and threats.

• Compliance: Demonstrates adherence to regulations/policies.

• Performance optimization: Identifies bottlenecks and optimizes resources.

• Troubleshooting: Logs help identify root causes.

Common Event IDs (Windows) — Examples

• 4624: Successful account log on

• 4625: Failed account log on

• 4634: An account logged off

• 4648: Logon attempt with explicit credentials

• 4719: System audit policy changed

• 4964: Special group assigned to a new logon

• 1102: Audit log cleared

• 4720: User account created

• 4722: User account enabled

• 4723: Attempt to change password

• 4725: User account disabled

• 4728/4732/4756/ etc.: Privileged group membership changes

• 4738: User account changed; 4740: User account locked out; 4767: User account unlocked

• 4735/4737/4755: Privileged group modified

• 4772/4777: Kerberos/credential validation events

• 4782: Password hash accessed

• 4616: System time changed

• 4657: Registry value changed

• 4697–4702: Service-related events

• 4946–4954: Firewall rule changes/settings

• 5025: Windows Firewall service stopped

• 5031: Firewall blocked app

• 5152, 5153, 5155, 5157: Windows Filtering Platform events

• 5447: WFP filter changed

Storage, File Systems, and Data Management Practices

What is Storage?

• DAS, NAS, SAN are three primary storage architectures:

  • DAS: Direct Attached Storage connected to a single server.

  • NAS: Network Attached Storage providing file-level access over a network.

  • SAN: Storage Area Network offering block-level access over a dedicated network.

• RAID: Redundant Array of Independent Disks improves reliability and performance by combining multiple disks into a single unit.

File Systems: Characteristics and Use Cases

• FAT: Simple, widely compatible; limited large-file support.

• NTFS: Rich features (security, journaling, large volumes); Windows default.

• ReFS: Data integrity-focused, scalable for large datasets; Windows Server environments.

• EXT3/EXT4: Linux file systems; EXT4 adds performance features (extents, delayed allocation).

Data Center and Storage Architecture (Recap)

• DAS/NAS/SAN balance cost, performance, and scalability depending on application needs.

• RAID levels provide trade-offs among speed, redundancy, and capacity.

• SAN protocols include FC, iSCSI, FCoE; FC is dedicated, iSCSI uses TCP/IP over Ethernet, FCoE consolidates traffic on Ethernet.

Key Takeaways for Exam-Readiness

• Understand the purpose and roles of common network devices and how they differ by OSI layer.

• Be able to describe the 7 OSI layers and assign typical protocols/services to each layer.

• Distinguish LAN vs WAN characteristics, and identify typical use cases for each.

• Compare IPv4 and IPv6 in terms of address length, notation, and major design goals; know unicast/broadcast/multicast/anycast concepts for IPv6.

• Recognize storage architectures (DAS/NAS/SAN) and RAID level trade-offs; understand SAN protocols (FC, iSCSI, FCoE).

• Identify core data center components and the shift toward virtualized/multi-cloud environments.

• Distinguish between Server OS and Client OS, including typical roles, features, and examples.

• Appreciate the importance of out-of-band management (IPMI/iDRAC/iLO) and what information these interfaces provide.

• Understand common server management events and the importance of monitoring for security, compliance, and performance.

• Know examples of common Windows Server and Windows Client OS milestones and roles, as well as typical server roles like AD DS, DNS, DHCP, File/Print, Web, and RDS.

32-bit IPv4 addresses, 128-bit IPv6 addresses, 8-bit octets, and 60-byte maximum IPv4 header have been used in the content. Real-world equivalents follow standard networking practice (e.g., IPv6 uses eight groups of four hex digits separated by colons and a 40-byte header; IPv4 headers commonly range up to 60 bytes with a 20-byte minimum). The addresses and bit-lengths cited above reflect the material in the transcript and are aligned with standard networking concepts.