In this section, we explore the world of programming, algorithms, networks, and infrastructure
This hands-on lab configures a default gateway on a Layer 2 switch's management interface so it can be reached and managed from a remote subnet, and distinguishes this from a router's own default route used to reach networks beyond its directly connected interfaces.
This hands-on lab uses CDP to discover directly connected Cisco devices without any prior configuration knowledge of the neighboring device, and covers disabling CDP on a specific interface for security reasons while leaving it active elsewhere.
This hands-on lab enables LLDP, the vendor-neutral equivalent of CDP, on a Cisco device connected to non-Cisco equipment, and compares its verification output directly against CDP to highlight the similarities and differences between the two protocols.
This hands-on lab triggers a port security violation that places a port into err-disabled state, then configures automatic errdisable recovery so the port re-enables itself after a timeout instead of requiring manual intervention.
This hands-on lab configures inter-VLAN routing using a single router interface divided into subinterfaces, connecting to a switch trunk to route traffic between two VLANs through one physical link.
This hands-on lab configures inter-VLAN routing using Switch Virtual Interfaces on a Layer 3 switch, enabling IP routing directly on the switch itself and comparing this approach against the router-on-a-stick method from the previous lab.
This hands-on lab covers physically connecting and performing the initial configuration of a standalone wireless access point, including setting up an SSID, applying WPA3 security, and verifying wireless clients can associate and reach the wired network.
This hands-on lab performs the initial setup of a Wireless LAN Controller, joins a lightweight access point to it, and creates a centrally managed WLAN, demonstrating the controller-based architecture that scales far beyond standalone access points.
This hands-on lab configures static routes using an outgoing interface rather than a next-hop IP address, demonstrating this approach's suitability for point-to-point links and its important limitation on multi-access networks.
This hands-on lab configures static routes using a next-hop IP address rather than an outgoing interface, the generally preferred syntax, and compares the resulting routing table entry against the interface-based approach from the previous lab.
This hands-on lab configures static routes with descriptive names attached using the name keyword, improving documentation and making the routing table significantly easier to interpret for anyone reviewing the configuration later.
This hands-on lab configures a default static route on an edge router to reach the internet through an ISP connection, demonstrating how a single route can represent every otherwise-unknown destination rather than requiring individual routes for each one.
