In the previous lesson, we focused on the fundamentals of EtherChannel by bundling multiple interfaces using LACP in active mode. In this lesson, we will build on that foundation by adding an additional interface to our existing EtherChannel and converting the LACP configuration to static “on.” These two tasks will help you deepen your understanding of EtherChannel’s flexibility. By following along, you will see how to expand and adapt a port-channel configuration to suit different requirements.
EtherChannel, also known as Port-Channel, is a technology that combines multiple physical switch ports into one logical interface. This bundling increases bandwidth while providing redundancy if one physical link fails. Configuration options include modes that automatically negotiate channels (such as LACP) or statically configure them. It is widely used between switches to ensure higher throughput and fault tolerance.
When you’re given a narrative like the BrightSide Graphics scenario, the goal isn’t to immediately start typing commands. Instead, you work backward from the constraints and requirements in the story to figure out the right tools and configuration.
In real life, you’ll often have to read between the lines — the boss or a client rarely says “configure PAT with overload on the interface and an inbound ACL.” They give you symptoms, policies, and limitations. Your job is to translate those into the exact features and commands that meet all needs without breaking anything else.
For this scenario, your reasoning process goes something like this:
In the previous lessons, we focused on Static NAT for inbound connections, including restricting traffic to specific services. For this lesson, we move to outbound internet access for inside users, using Port Address Translation (PAT), also known as NAT Overload.
PAT is a form of Dynamic NAT that allows multiple internal devices to share a single public IP address. It achieves this by assigning a unique port number to each connection. When a user inside the network wants to access the internet, the router changes the source IP address of the packet from the private internal address to the public external address and assigns a unique port number. This clever mechanism allows hundreds or even thousands of devices to share one public IP address, making it the most common form of NAT used in home and business networks.
Read more
In the previous lesson, we learned how to configure basic Static NAT to permanently map an internal address to a public IP so that external users can access it. That configuration allowed all ports to pass through to the inside host.
In this lesson, we take that concept further by applying port-specific static NAT so that only a single service — in this case, HTTP on TCP port 80 — is reachable from the internet. This provides more control over what is exposed while still giving outside users access to the intended service.
Previously, we set up a simple two-router lab using both iBGP and eBGP, and we also demonstrated how to verify them. Now, we'll explore how eBGP and iBGP work together to exchange routes between different Autonomous Systems (ASes), highlighting their combined role in interconnecting more complex networks.
This three-router topology connects three ASes: