Tools and articles for what you want to do
Choose a topic and read in order, starting with its introduction. Links to background reading and further exploration are listed separately. You can also find articles from our series here, so you can read just what you need or continue through the whole book.
Topics
// TOPICSIP addresses// TOPIC · three branches
How packets find their destination
Compare your address and the destination address using the same criteria, then calculate a subnet size that fits the number of devices you need.
Branch 2 2 articlesAssign addresses to devices and connect them to the internetSeparate the steps: a device uses DHCP to receive an address and its gateway settings, then communicates with the internet through NAT.
Branch 3 2 articlesManage internal and public addresses without overlapPlan the enterprise's private address space, then see why public address allocation and registration are separate responsibilities from advertising internet routes.
Enterprise network design// TOPIC · four branches
Layers and redundancy for growth and resilience
First, see why you would separate the functions combined in a router. Identify who uses each service and how much downtime they can tolerate. Then compare those needs with Cisco's reference designs and the roles of Access, Distribution, and Core.
Branch 2 3 articlesChoose equipment and plan addresses for a small siteCompare when one router is enough with when you need separate switches and APs. Check ports, PoE, wireless requirements, and the gateway, and plan addresses that will not overlap when you connect to branches or the cloud.
Branch 3 3 articlesSet link capacity, failure domains, and L2/L3 boundariesCalculate the capacity needed both during normal operation and on the paths left after a failure. Distinguish the effects of shared power and cable pathways from equipment failures. Then decide how far to extend each VLAN and where to separate networks with routing.
Branch 4 3 articlesConnect wiring closets and buildings with redundancyStart with a two-tier design that aggregates access switches. Then examine failure detection and path switching for switches, gateways, and routers. Finally, decide when you need a separate Core to connect multiple distribution blocks.
Routing// TOPIC · four branches
How paths between networks are chosen
Distinguish the routing table from the information used for forwarding, and learn how to detect failures beyond a directly connected link.
Branch 2 1 articleCalculate routes from connectivity within an organizationFollow OSPF neighbor formation, link-state exchange, route calculation, and updates to forwarding information, in that order.
Branch 3 2 articlesApply policy to routes learned from other networksExamine BGP route attributes and policies. Track the source of redistributed routes and control which ones are allowed, so they do not cause problems by reentering their original network.
Branch 4 1 articleUse routing controls to limit the impact of attacksDecide where to act before the link becomes saturated. Distinguish how blocking, observation, and traffic scrubbing affect normal service.
Switching// TOPIC · four branches
How frames travel across a local network
Distinguish a destination on the same network from the gateway used to reach another network. See what the ARP table tells you and what a switch's MAC address table tells you.
Branch 2 1 articleSeparate communication domains on the same switchUse VLANs to separate local communication domains, and see how a trunk carries multiple VLANs to another switch.
Branch 3 2 articlesUse redundant links safelySTP prevents loops by limiting active paths; EtherChannel distributes separate traffic flows across links. Learn why these are different functions.
Branch 4 1 articleConnect different VLANsFollow the round trip: a device sends data to its gateway, which forwards the packet to another network after a route lookup and creation of a new frame. See how it reaches the other VLAN and how traffic returns.
How a topic takes shape
// HOW A TOPIC FORMSTopics take shape in two ways. Sometimes we start with an outline and fill it in. Other times, separate tools and articles come together under one name. Either way, we do not force a topic into existence.
Start with a topic people need
Some broad topics come up again and again in IT work, such as dividing address space or concealing and verifying values. We start with those topics and build them out with articles explaining the principles and tools you can use.
Find the topic connecting separate pieces
As you use different tools and read articles across several subjects, you start to see connections. Bringing those tools and articles together under one topic helps you understand how they fit together—something you might miss when viewing each one on its own.
Both approaches lead to the same result: a topic opens when it has 2 tools and 3 articles. We do not set up empty sections in advance, so you never click into a topic only to find nothing there.