Cisco Netlab

Static Routing

Objectives:

 Configure Static Routes

 Verify Connectivity Topology

 Once you have logged in, scheduled the correct lab, and hit Enter Lab you will see the following:

 If you see scroll bars around the topology, you can use them to move around the topology.

 You can click the Show Lab Content button to download the lab or you can download the lab from

Learn@Stout in Content.

 This time and for all future labs, unless specified differently, you will be configuring all of the

equipment in the topology

Static Routing

Step 1: Initial Router Configuration

Perform the initial router configurations on all routers. If you have trouble recalling how to do each step

refer to the previous lab.

 Configure Hostnames according to the topology

 Configure Enable Secret, Telnet and Console passwords. Set all of the passwords to uwstout

 Configure the interfaces with IP addresses and subnet masks according to the topology

 Configure the Clock rates on the DCE interfaces to 128000

 Configure the Bandwidth on the DCE interfaces to 128

 Remember to issue the No shutdown command on all of the interfaces

 Configure the PCs according to the topology.

Verify you have done the initial configuration correctly:

Before proceeding to the next step check that your interfaces are up, once you have completed the initial

configuration on all routers all interfaces should be up. You will use the show ip interfaces brief command

to see if your interfaces are up.

In user or privileged mode, type show ip interfaces brief and press enter.

(It is okay that the BRI interfaces are down, we didn’t configure them)

Notice that all of the interfaces configured show a status as up and the protocol is up. At this point you are

ready to move to the next step. If your interfaces are not up you will need to troubleshoot:

o Verify that you enabled the interfaces (no shutdown)

o Verify the IP address/subnet masks are correct—typos are common

o Verify the clockrate and bandwidth on the DCE

o Make sure you configured the correct interfaces.

Static Routing

Step 2: Configuring the Static Routes

Now that you have completed the initial configuration you can begin to configure routing. If you are not using a Routing protocol to route the traffic you will use administratively configure static routes to route the traffic in your network. We will be configuring static routes to route traffic in our network. When you configure a static route you are simply writing a command that says “if you want to send traffic to the xxx.xxx.xxx.xxx network send it to the yyy.yyy.yyy.yyy address” where yyy.yyy.yyy.yyy represents the next hop address. You can also configure an outgoing interface rather than a next hop address. Next hop address is the prefer method for our use because it is a more definite route—I can predict exactly where my traffic will be going assuming that interface is up.

Configure the static routes on RemoteAZ:

Configure the static routes on RemoteAZ so traffic can get to RemoteWI and Menomonie. Static routes are only configured for networks that the router isn’t directly connected to. Directly connect routes do not need any routing, they are already in the routing table. The form of the command is: ip route <destination prefix> <prefix mask> <forwarding router’s address>

Remote AZ needs to get to the 10.10.2.0 and 192.168.2.0 networks on Menomonie and the 10.10.3.0 network on RemoteWI so we will configure a static route to complete this task.

 In global configuration mode of RemoteAZ type ip route 10.10.2.0 255.255.255.0 192.168.1.2 and press enter.

 In global configuration mode of RemoteAZ type ip route 10.10.3.0 255.255.255.0 192.168.3.1 and press enter.

 In global configuration mode of RemoteAZ type ip route 192.168.2.0 255.255.255.0 192.168.1.2 and press enter.

 Type exit to get back to privileged mode and save your configuration using copy running-config startup-config command.

Configure the static routes on Menomonie:

 In global configuration mode of Menomonie type ip route 10.10.1.0 255.255.255.0 192.168.1.1 and

press enter.

 In global configuration mode of Menomonie type ip route 10.10.3.0 255.255.255.0 192.168.2.2 and press enter.

 In global configuration mode of Menomonie type ip route 192.168.3.0 255.255.255.0 192.168.2.2 and press enter.

 Type exit to get back to privileged mode and save your configuration using copy running-config startup-config command.

Static Routing

Configure static routes on RemoteWI: Configure the static routes on RemoteWI so traffic can get to the Menomonie and RemoteAZ networks.

 In global configuration mode of Menomonie type ip route 10.10.1.0 255.255.255.0 192.168.3.2 and press enter.

 In global configuration mode of Menomonie type ip route 10.10.2.0 255.255.255.0 192.168.2.1 and press enter.

 In global configuration mode of Menomonie type ip route 192.168.1.0 255.255.255.0 192.168.3.2 and press enter.

 Type exit to get back to privileged mode and save your configuration using copy running-config startup-config command.

Step 3: Verifying Connectivity Use the command show ip route to review the routing table of each router. If everything was done correctly you will see routes to all networks in the topology in the routing table, some will be Connected and some will be Static. There are six networks in the topology

In all routers:

 In privileged mode, type show ip route and press enter, to view the routing table.

Static Routing

Next, use ping to verify the connectivity between all the routers and hosts. To ping from the routers you will go into privileged mode and type ping ip address, where ip address is the IP address you are wanting to ping, you are wanting to see if you have connectivity to. If your ping is successful then you have connectivity to that network and you have done the lab correctly once you have ensured you have connectivity to all networks.

 Ping all interfaces (ip addresses) from all routers

 Ping all Computers from all routers Example: On RemoteAZ I pinged to the IP addresses on Menomonie that I wasn’t directly connected to and it was successful.

If you are unable to ping an interface or computer, verify your configurations to make sure you entered everything correctly.