Chapter 15. Manually directing traffic using the IP routing table

 

Connecting two switches that are in the same physical location is easy. All you have to do is string a couple of Ethernet cables between them, configure the interfaces, and you’re finished. But now imagine that your switches sit in separate offices hundreds of miles apart. How do you connect them?

In chapter 8 I said that you have a few options when it comes to connecting geographically separated sites. Private T1/E1 lines and MPLS virtual private networks (VPNs) are two popular methods. With both of these methods, the telecom carrier provides you physical connectivity between your sites. But it’s still up to you to configure IP routing between those sites.

In the last chapter, you got a glimpse of how IP routing works when you set up your “router-on-a-stick” topology. Figure 15.1 illustrates the topology you have right now.

Figure 15.1. The router-on-a-stick physical topology

Recall that you didn’t have to explicitly tell Router1 how to route between IP subnets. All you had to do was create a couple of subinterfaces, configure an IP address on each one, and the router took care of the rest.

But that’s with just one router. When you connect geographically separated sites, you’ll have multiple routers. Take a look at figure 15.2; you’ll reconfigure your network to look like this in this chapter.

Figure 15.2. Switch1 and Switch2 connected via Router1

15.1. Connecting Router1 to Switch2

15.2. Configuring transit subnets

15.3. Removing the trunk link between switches

15.4. Configuring default gateways

15.5. Creating a DHCP pool for the Executives subnet

15.6. Commands in this chapter

15.7. Hands-on lab