YT YouTube2Text

YouTube2Text → Transcripts → SRWE M15 IP Static Routing

SRWE M15 IP Static Routing — Transcript

by Santelmo · 7,671 words · 1,523 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:16Hi. Hello there.
0:17Welcome to IP static routing.
0:20There are so many different ways to
0:22dynamically route a packet that you
0:24might wonder why anybody would take time
0:27to manually configure static route.
0:30It is kind of like hand washing all your
0:32clothes when you have perfectly good
0:34washing machine.
0:36But, you know that some clothing items
0:38cannot go in the washing machine.
0:40Some items benefit from being washed by
0:42hand.
0:44There is a similarity in networking.
0:47As it turns out, there are many
0:49situations where a manually configured
0:51static route is your best option.
0:54There are different kinds of static
0:56routes and each is perfect for solving
0:59or avoiding a specific type of network
1:01problem.
1:03So, many networks use both dynamic and
1:06static routing.
1:07So, network administrators need to know
1:10how to configure, verify, and
1:13troubleshoot static routes.
1:16You are taking this course because you
1:18want to become a network administrator.
1:20Or maybe you want to improve your
1:22existing network administrator skills.
1:26So, you will be glad you took this
1:28module
1:29because you will use these skills
1:31frequently.
1:33And because this module is about
1:34configuring static routes, there will be
1:37a demo video associated with this.
1:43Now, the module title is IP static
1:45routing.
1:47And at the end of this module or video
1:49lecture, you should be able to configure
1:51IPv4 and IPv6 static routes.
1:55Also, part of this video lecture
1:59are discussions on static routes.
2:02Configure IP static routes,
2:04configure IP default static routes,
2:07configure floating static routes, and
2:09configure static host routes.
2:13This video lecture is associated with a
2:15video demo on how to configure IP static
2:18route.
2:24Okay. So, let's begin with the first
2:26section,
2:27static routes.
2:30Okay? So, types of static routes.
2:34So, static routes are commonly
2:35implemented on network.
2:38This is true even when there is a
2:40dynamic routing protocol configured. For
2:43instance, an organization could
2:45configure a default static route
2:47to the service provider and advertise
2:49this route to other corporate routers
2:52using the dynamic routing protocols.
2:55So, static routes can be configured for
2:57IPv4 and IPv6.
3:01Okay, so both protocols supports the
3:03following types of static routes. So,
3:06you've got a standard static route,
3:08default static route,
3:10floating static route, and summary
3:12static route.
3:14Static routes are configured using the
3:17IP route command
3:19and IPv6 route
3:22global configuration commands.
3:26Okay, so the next one would be the next
3:28hop options.
3:30So, when configuring a static route, the
3:32next hop can be identified by an IP
3:35address, exit interface, or both.
3:39So, how the destination is specified
3:41creates one of the three of the
3:42following types of static route.
3:44So, the first one would be your first or
3:47the next hop route. Okay?
3:50Only the next hop IP address is
3:52specified.
3:54You also have the directly connected
3:56static routes.
3:57So, only the router exit interface is
4:00specified.
4:02And then the third one is the fully
4:04specified static route.
4:06So, the next hop IP address and exit
4:08interface are specified.
4:15Okay? So, the IPv4 static route command.
4:19So, IPv4 static routes are configured
4:22using the following global configuration
4:24command. So, this is the syntax whenever
4:27you want to configure a static routing
4:29on your router.
4:31Okay? So, that would be on the global
4:33config, you have to type in IP route
4:37followed by the network address. Okay?
4:40Subnet mask,
4:42IP address,
4:44exit interface IP address,
4:47and the optional distance. So, either
4:50the IP address or the exit interface or
4:53the IP address and the exit interface
4:55parameters must be configured.
4:59All right? Now, what are these
5:01parameters that we have here?
5:03So, again, the syntax would be IP route.
5:06So, what is this network address?
5:08The network address identifies the
5:10destination IPv4 network address of the
5:14remote network to add to the routing
5:16table.
5:18So, the next one would be the subnet
5:20mask.
5:21So, it identifies the subnet mask of the
5:23remote network.
5:25So, the subnet mask can be modified to
5:28summarize a group of networks and create
5:31a summary static route.
5:34So, the next one would be an IP address.
5:37It identifies the next hop router IPv4
5:40address. So, typically used with
5:43broadcast networks like the Ethernet.
5:46Okay? It could also create a recursive
5:49static route when the router performs an
5:51additional lookup to find the exit
5:53interface.
5:55Next would be
5:57the exit interface.
5:59Okay? So, it identifies the exit
6:01interface to forward packets. So, it
6:04creates a
6:05directly connected static route,
6:07typically used in a point-to-point
6:09configuration.
6:11Okay?
6:12So, next would be the exit interface IP
6:16address.
6:17It creates a fully specified static
6:20route because it specifies the exit
6:22interface and the next hop IPV4 address.
6:27Now, distance here is optional command
6:29that can be used to assign an
6:31administrative distance value from 1 to
6:33255.
6:34So, typically used to configure a
6:37floating static route
6:38by setting an administrative distance
6:41that is higher than a dynamically
6:42learned route.
6:44Okay? So, now that you know the syntax
6:47on how to use
6:49IP route, now you can go ahead and
6:51configure it.
6:53Okay? Give it a try on the Packet
6:55Tracer.
6:59Now, on the IPV6 static route command,
7:01so this would be the syntax. So, it's
7:03almost the same.
7:04All right? So, the syntax would be IPV6
7:08route. Okay? IPV6 prefix or the prefix
7:12length.
7:13IPV6 address, exit interface or the IPV6
7:17address and the distance.
7:20Okay?
7:20Now, similar with IPV4,
7:23so let's start with
7:26the IPV6 prefix or the prefix length.
7:29Okay? So, for the IPV6 prefix, it
7:32identifies the destination IPV6 network
7:35address of the remote network to add to
7:38the routing table.
7:40Now, the prefix length, it identifies
7:43the prefix length of the remote network.
7:47Next would be IPv6 address. It
7:50identifies the next hop router IPv6
7:53address.
7:54So, this is typically used when
7:56broadcast networks like the Ethernet.
7:59So, could create a recursive static
8:02route where the router performs an
8:04additional lookup to find exit
8:06interface, similar with that of the
8:08IPv4.
8:11You also have the exit interface here.
8:13It identifies the exit interface to
8:15forward packets.
8:17And it creates a directly connected
8:19static route.
8:20So, typically
8:22this is used in a point-to-point
8:24configuration.
8:26All right?
8:27So, you also have the exit interface,
8:31okay, IPv6 address.
8:33It creates a fully specified static
8:36route because it is specifies the exit
8:39interface and the next hop IPv6 address.
8:44Now, you also have distance on IPv6.
8:48Okay, so this is also optional command
8:50that can be used to assign an
8:51administrative distance value
8:54from 1 to 255.
8:56So, typically
8:57this is used to configure a floating
8:59static route
9:01by setting an administrative distance
9:03that is higher than the dynamically
9:05learned route.
9:07Okay? So, take note that the IPv6
9:11unicast routing global configuration
9:13command must be configured
9:16to enable the router to forward IPv6
9:19packet.
9:22All right? So, most of the parameters
9:24are identical with that of IPv4.
9:26It's just that you have to include a V6,
9:29okay, on the IPv6 route command
9:33versus that of IPv4, which is simply an
9:36IP route command.
9:44All right. So, we will be using this
9:47even on my demonstration. Okay, so this
9:49topology is what you call a dual stack
9:52topology.
9:53So, this figure shows a dual stack
9:56network topology. So, currently no
9:58static routes are configured for either
10:01IPv4 or IPv6.
10:04Okay? So, this is the same topology that
10:06I'm going to use on demonstrating how to
10:10configure IP static routing.
10:13All right. So, you've got here three
10:15router configurations.
10:17You've got a combinations of IPv4 and
10:19IPv6 addressing.
10:21Also, please see the video demonstration
10:25about how to configure the IP static
10:28routing.
10:32Okay. So, IPv4 starting routing tables.
10:38So, each router has entry only for
10:41directly connected networks and
10:44associated local addresses.
10:47Okay? So,
10:49R1 can ping R2. Okay, on this
10:52demonstration. Now, going back to our
10:54topology,
10:55all right. So, this is the topology that
10:58we're going to use on the demonstration.
11:01Now, for the sake of
11:03video lecture, okay, so assuming that
11:06this has been configured completely with
11:08IP static routing, okay? And we are
11:11about to ping, okay, so from R1
11:16to R2,
11:17which are directly connected to each
11:19other.
11:20Okay? So, none of the routers have
11:23knowledge of any networks beyond the
11:25directly connected interfaces. So, this
11:28means each router
11:30can only reach directly connected
11:32networks.
11:34So, as demonstrated in the following
11:36ping tests,
11:37a ping from R1
11:39to the serial interface serial 010 of R2
11:44should be successful.
11:47Okay?
11:48So, that would be
11:50because it is a directly connected
11:52networks.
11:55All right? So, again, going back to the
11:57topology,
11:58on R1, we are pinging 172.16.2.2.
12:03And 172.16.
12:052.2
12:08is this interface here.
12:11Okay? So, which is the interface of R2
12:14pinging from PC1.
12:17Okay? So, we can ping that because that
12:20is directly connected
12:22on R1.
12:23But,
12:24a ping on three,
12:27okay? Or a ping on router three LAN
12:31is not possible.
12:32Okay? So, from the topology,
12:35192.168.2.1,
12:38okay? Is the LAN of R3 here. And pinging
12:41from PC1
12:43would lead to
12:44request timeout.
12:47All right? So, because
12:49router one is not aware about R3.
12:53Okay? So, that is because we have not
12:55configured yet
12:57the routing protocol.
13:00Okay?
13:06Next,
13:08how about R2 IPv4 routing table? Now,
13:12looking at the R2 IPv4 routing table, if
13:15you will observe here,
13:17all it displays
13:18are the directly connected networks. So,
13:21C here indicates directly connected
13:23networks.
13:25Whereas L,
13:26this are the IP address configured on
13:29the specific interface.
13:31Now evaluating the routing table, okay?
13:35So, we can see that on R2, okay? Going
13:40back on R2,
13:41on R2,
13:43we can see
13:45three directly connected networks. So,
13:47these are 172.16.2.0,
13:51192.168.1.0,
13:53and 172.16.1.0
13:56here.
13:57So, if you try to look at the
14:02routing table, okay? So, for R2, it
14:05shows three Cs here.
14:07Right? So, 172.16.1.0,
14:112.0, and 192.168.1.0.
14:15So, all of it are directly connected to
14:18R2.
14:21All right?
14:22Now also on R3, okay? It only shows or
14:25displays directly connected networks to
14:29R3.
14:30And if you'll observe, you have two
14:33directly connected networks to it. And
14:35these are 192.168.1.0
14:38and 192.168.
14:402.0. Now referring that to the topology,
14:44okay? So, it's in here.
14:45R3,
14:46you've got directly connected networks,
14:48192.168.1.0,
14:51and 192.168.2.0
14:53here.
14:54Okay? So, initially, after the
14:57configurations
14:58of the IP addresses on the interfaces
15:01and without the IP static routing,
15:05okay? So, we can only see the directly
15:08connected networks on the routing table.
15:12All right?
15:15Okay.
15:16So, each router
15:19has an entries only for directly
15:21connected networks and associated local
15:24addresses. So that's denoted by
15:27L. Now, same thing with IPv4. Now this
15:30time this has been configured with IPv6
15:32IP addresses.
15:34Okay? So as usual, R1 can ping R2.
15:39Okay, because they are directly
15:40connected, but R1 cannot ping the R3
15:43LAN.
15:44Okay? So pinging R1 or pinging R3 from
15:49the R1 is not possible. That is because
15:52R1 does not have an entry in its routing
15:54table for that network.
15:58All right? So again, this will be shown
16:00on the demonstration associated with
16:02this video lecture.
16:06Next, you also have the R2 IPv6 routing
16:09table. Again, if you will observe, same
16:11thing. We have three directly connected
16:14networks and no remote networks yet
16:17defined on the routing table.
16:19So it's impossible
16:21for R2 directly connected devices to
16:24reach any of the remote network directly
16:26connected devices.
16:28Okay? On the other routers.
16:32Okay? Now this is the router three IPv6
16:36routing table. Again, you'll see here
16:38directly connected networks. Okay? So
16:41that is 2001 DB8 cafe one and cafe two.
16:49Okay.
16:51Now that we're done with the basics of
16:53static or IP static routing, let's go
16:56ahead and see configuring IP static
16:59routes on this section.
17:06Okay, so let's talk about the IPv4 next
17:09hop static route.
17:11So the commands to configure the static
17:14uh these the standard static routes they
17:16slightly between IPv4 and IPv6. So, this
17:19topic shows how to configure the
17:21standard next-hop, directly connected,
17:24and the fully specified static routes
17:27for both IPv4 and IPv6.
17:30Okay?
17:31Now, in a next-hop static route,
17:34only the next-hop IP address is is
17:36specified.
17:37The exit interface is derived from the
17:40next hop. For example,
17:43three next-hop IPv4 static routes are
17:45configured on R1 using the IP address of
17:49the next hop of R2.
17:51Okay?
17:52Now, referring to the topology that we
17:54have earlier,
17:56okay? So, if I am on R1,
17:59the first thing that you need to do is
18:00to identify the directly connected
18:02networks to R1.
18:04Okay? And from here,
18:06the directly connected networks from R1
18:08would be the 3.0 here and the 2.0 of
18:12172.16.
18:15Okay? So, identifying the directly
18:17connected networks will leave
18:19172.16.1.0,
18:22192.168.1.0,
18:24and 192.168.2.0
18:26be the remote networks.
18:28Now, in configuring the IP static
18:30routing, we care only about the remote
18:33networks.
18:34So, when we define it,
18:36we defined the remote networks. So, if
18:39you will observe on this uh
18:41configuration here for R1,
18:44the remote networks would be 172.16.1.0.
18:48Okay? So, which is this network here.
18:52All right?
18:53So, to define it, so it should be IP
18:56route 172.16.1.0.
19:01That's /24, so that would that would be
19:02255.255.255.0.
19:06Now, the next one would be the
19:09next-hop IP address.
19:11So, if I am from Let me change my
19:13pointer here.
19:15So, if I am from
19:18R1, okay, this is me.
19:21The next hop IP address to reach the
19:23remote network is this.
19:27All right? And that is 172.16.2.2.
19:31That's why you'll have it here.
19:33All right? So, to reach 172.16.1.0,
19:38192.168.1.0,
19:40and 192.168.2.0,
19:42you need to pass through 172
19:45172.16.2.2
19:47as the next hop IP address. So, all of
19:50this here
19:52would be the next hop IP address of the
19:55remote networks.
19:56So, that is why on the configuration,
19:59you're going to have here IP route
20:00172.16.1.0,
20:03subnet mask, which is 255.255.255.0,
20:07and you're going to have here the exit
20:09interface.
20:11All right? So, same thing with the
20:12second remote network, which is
20:15IP route 192.168.1.0.
20:19So, you've got 255.255.255.0
20:23via 172.16.2.2.
20:27So, the third remote network is
20:30192.168.2.0
20:33here.
20:34So, defining it on R1, that would be IP
20:37route 192.168.2.0
20:40255.255.255.0
20:46via the next hop IP address, which is
20:49172.16.2.2.
20:53All right?
20:55Now, after the configuration, so you
20:57might want to check the entry
21:00Okay, or the routing table entries on
21:02R1. And that would be possible via show
21:05IP route.
21:06Okay, or you can have the option or the
21:08more specific show IP route pipeline
21:11begin gateway. So, that means that would
21:13start
21:15with the word gateway here.
21:18Now, from the routing table,
21:20we could see that
21:23the remote networks that we have defined
21:25here
21:27is denoted by S on the routing table.
21:30All right? So, you've got 1.0,
21:33192.168.1.0
21:35and 192.168.2.0.
21:37These three here
21:39are the remote networks that we defined
21:41on the configuration using IP route.
21:45All right? So, aside from the directly
21:47connected networks,
21:50which is automatically detected by R1,
21:53since we already have defined the remote
21:55networks using IP route, so we can see
21:58here all the remote networks and the
22:00directly connected networks to R1.
22:05All right?
22:12Okay. So, how about the IPv6 next hop
22:15static route?
22:17So, it works the same with that of IPv4.
22:20Okay? So, again, considering this uh
22:22topology here.
22:24So, the commands to configure R1 with
22:26the IPv6 static routes to the three
22:29remote networks are as follows. So,
22:31again, we have to identify, so we are
22:33from R1.
22:35This is where we're going to configure
22:37the IP route.
22:38We first need to identify the remote
22:40networks. And the remote networks would
22:42be This is your first remote network,
22:45your second remote network, and your
22:48third remote network.
22:51All right? So, when we define it,
22:54so in IPv6, we have to use
22:57IPv6 unicast routing.
23:00So, every time you configure a router
23:02for IPv6, so you need to start or
23:05initialize IPv6 unicast routing.
23:08Don't forget this, otherwise you won't
23:10be able to configure any IPv6
23:13configuration commands on a router.
23:17Okay? So, we need to start or to begin
23:19with IPv6 unicast routing. So,
23:22afterwards, we can now do the routing.
23:25Now, assuming that we have already
23:27configured
23:28all the IP addresses on each of the
23:30interfaces with IPv6, we can now proceed
23:34with routing.
23:36All right. So, the syntax, which was
23:39shown earlier, would be IPv6
23:41All right, and then route.
23:43This is your remote network, which is
23:472001 DB8 acad 1/64.
23:53Okay?
23:54So,
24:00This is on R1, right? Okay. So, this is
24:03the first remote network, and still this
24:05is our
24:07exit interface.
24:09Okay, so therefore, from R1, to reach
24:13172.16.1.0/24,
24:16we need to pass through 2001
24:19DB8 acad 2
24:232.
24:24All right. So, this would be our
24:27exit interface. If you will observe,
24:29that is common to all the remote
24:31networks.
24:33Okay, so we need to pass through this to
24:35reach remote networks 1, 2, and 3.
24:40Okay? Now, let us define the second
24:42network. So, that would be IPv6 route
24:442001 DB8 cafe:1:64
24:50via 2001 DB8 acad 2.
24:55All All that 2.
24:58And then, let us define also the last
25:00one, which is the third remote network
25:02from R1.
25:03So, that would be IPv6 route
25:052001:db8:cafe:2
25:08Okay, colon colon {slash} 64
25:11traversing via 2001:db8:acad:2
25:15colon colon 2.
25:17Okay? So, after defining this route so,
25:20you might want to visit the routing
25:22table. So, the command would be show
25:24IPv6 routes. And if you will observe
25:27here
25:28we already have seen
25:30the three remote networks we just
25:33recently defined using the IPv6 route
25:35command.
25:37All right?
25:45Okay, so next would be the IPv4 directly
25:48connected static route.
25:51Okay?
25:52So when configuring a static route,
25:55another option is to use the exit
25:57interface to specify the next hop
26:00address.
26:01So, the figure shows the topology again
26:03that we use on the demonstration.
26:06All right? So, the IPv4 routing table
26:10for R1 shows that when a packet is
26:13destined for 192.168.2.0
26:16network, which is denoted by S here
26:19right, so this means this is a remote
26:21network.
26:22Okay? So, R1 looks for a match in the
26:25routing table.
26:27And finds that it can forward a packet
26:29out of serial 010 interface. So, take
26:33note that this is your exit interface
26:36here.
26:37Okay?
26:38Note that using a next hop address is
26:40generally recommended.
26:43Okay? What we did earlier
26:45we used
26:47the next hop IP address instead of the
26:49exit interface.
26:52All right?
26:53So, take note.
26:55This is a very important note here. So,
26:58using the next hop address is generally
27:00recommended. Directly connected static
27:03routes should only be used
27:06with a point-to-point serial interfaces
27:09as in this example.
27:10So, take note that we can use exit
27:12interface here because we only have
27:15point-to-point connection here.
27:17Okay?
27:18Whenever we connected routers using the
27:20serial interfaces, we could make use of
27:23the exit interface.
27:25All right?
27:26Now, let us evaluate this. This is the
27:28same configurations that we've made
27:30using the next hop IP address. The only
27:32difference is
27:34with this one, we use the exit
27:36interface.
27:39All right? So, how are going to use
27:41this? Where is the exit interface? Okay?
27:44If I am referring to R1, for instance,
27:47we are viewing it in the perspective of
27:49R1. Okay?
27:51So,
27:52192 or 172.16.2.2
27:55here would be our next hop IP address.
27:58And when you say exit interface, we are
28:00pertaining to this.
28:03All right? So, from the perspective of
28:06R1,
28:08we can leave the networks of R1 via
28:10serial 010 here. So, that is why in
28:13here, you've got serial 010.
28:16Now, to reach the remote networks like
28:18172.16.1.0,
28:21okay? We need to use
28:23serial 010 as the exit interface. Same
28:26thing,
28:26to reach the remote networks
28:28192.168.1.0,
28:30all right? We have to use also the
28:32serial 010 as the exit interface.
28:35That also applies to remote networks
28:38192.168.2.0
28:41using
28:42the serial 010 exit interface.
28:47All right?
28:48So, again, this is the second method of
28:51defining
28:52static IP routing. So, it's either you
28:54use the next hop IP address or the exit
28:57interface. But, the use of the exit
28:59interface is applicable only when you
29:02are using serial connections between
29:04these routers. All right? Or when you
29:06have a point-to-point connection only
29:09between the two routers.
29:11All right?
29:19All right. So, now you might be asking,
29:21"Is that also applicable on IPv6?"
29:24Yes.
29:25Okay? So, the IPv6 routing table for R1,
29:30okay?
29:30In the example, okay? Shows that when a
29:33packet is destined
29:35for 2001:cafe
29:382/64,
29:39so this is the S here. This is what
29:42we're pertaining to.
29:44Okay? So, R1 looks for a match in the
29:47routing table
29:48and finds that it can forward a packet
29:51out of the serial 010 here.
29:55Which is denoted by directly connected,
29:58this one.
29:59Okay? So, take note, same with IPv4,
30:03using the next hop IP address
30:06is generally recommended.
30:08Directly connected static routes should
30:10only be used only when you use the
30:13point-to-point connection or when you
30:16use serial interfaces between two
30:18routers.
30:20Okay? So, it's the same thing. So, IPv6
30:22route,
30:23this is your remote network one, okay?
30:26And this is our exit interface here.
30:29So, remote network two,
30:32all right? And then, the exit interface.
30:35And then, remote network three,
30:37and then, the exit interface.
30:40All right.
30:45Okay, so the third one would be IPv4
30:49fully specified static route.
30:51So, in a fully specified static route,
30:54both the exit interface and the next hop
30:57IP address are specified.
30:59So, this form of a static route is used
31:02when the exit interface is a
31:04multi-access interface,
31:06and it is necessary to explicitly
31:08identify the next hop.
31:11So, the next hop must be directly
31:13connected to the specified exit
31:14interface.
31:16So, using an exit interface is optional.
31:19However, it is necessary to use the next
31:21hop address.
31:23All right. So, suppose that the network
31:25link between R1 and R2 is an Ethernet
31:28link,
31:30and that the Gigabit Ethernet 001
31:32interface of R1 is connected to the
31:34network as shown in the figure here.
31:37Okay?
31:37The difference between an Ethernet
31:39multi-access network and a
31:41point-to-point serial network is that a
31:44point-to-point serial network has only
31:46one other device on the network.
31:49Okay, so this is a point-to-point serial
31:51network here.
31:52And this one here,
31:55okay? So, this is the Ethernet link.
31:58Okay?
32:00So, with the Ethernet networks, there
32:02may be different devices sharing the
32:05same multi-access network, including
32:07hosts or even multiple routers.
32:10So, it is recommended that when the exit
32:13interface is an Ethernet network,
32:16okay? So, that the static route
32:19includes a next hop address.
32:22You can also use a fully specified
32:24static route that includes both the exit
32:26interface and the next hop address.
32:31All right.
32:36Okay, so in a fully specified IPv6
32:39route, both the exit interface and the
32:41next hop IPv6 address are specified.
32:45Okay? So, there is a situation in IPv6
32:49when a fully specified static route must
32:51be used.
32:52So, if the IPv6 static route uses an
32:56IPv6 link local address as the next hop
32:59address, we use a fully specified static
33:02route.
33:03Okay? So, the figure shows
33:06an example of a fully specified IPv6
33:09static route using an IPv6 link local
33:11address as the next hop address.
33:14Now, in the example, a fully specified
33:16static route is configured using a link
33:18local address of R2 as the next hop
33:22address.
33:23So, notice that the iOS requires an exit
33:26interface be specified.
33:29Okay? So, this is how we do it. Okay, so
33:31IPv6 route,
33:33right? Same command.
33:35This is our remote network.
33:38This would be your exit interface, and
33:40this would be your next hop IP address.
33:42So, you specified both the exit
33:45interface and the next hop IP address.
33:48This is known as the fully specified
33:51static route.
33:53Okay? So, the first one also,
33:56okay? So, IP route, remote network,
34:00okay?
34:01This is your
34:03uh exit or the next hop IP address.
34:07Right? So, this is the traditional way
34:09of doing it.
34:10But, with a fully specified, this is
34:12another option.
34:15Okay?
34:16Now, going back to the IP before here,
34:20how is it done? Same thing. So, IP
34:22route, this would be our remote
34:25networks, all right? So,
34:28with R1 being our source or the
34:30perspective of R1,
34:32You've got the subnet mask here.
34:35Okay? Take a look at this. This would be
34:37your exit interface.
34:41All right. And
34:43you have here your
34:46next hop IP address.
34:50All right? So, this is a fully specified
34:54static route.
35:00Okay. So, the reason a fully specified
35:03static route must be used is because
35:05IPv6 link local address are not
35:08contained in the IPv6 routing table.
35:11Okay? So, link local addresses are only
35:14unique on a given link or network.
35:17So, the next hop link local address may
35:19be valid address on multiple networks
35:22connected to the router. So, therefore,
35:25it is necessary that the exit interface
35:28be included.
35:30Okay?
35:31Now, in here, the following example
35:33shows the IPv6 routing table entry for
35:35this route. So, notice that both the
35:38next hop link local address
35:41and the exit interface are included.
35:44Okay? So, this is your next hop address
35:47and this is your exit interface.
35:50So, that means to reach
35:522001:db8:acad:1::/64,
35:57we can reach it via Okay?
36:01The next hop IP address here
36:05and
36:06the serial 010 here as exit interface.
36:11All right? So, that's it.
36:17Next, how do we verify a static route?
36:20So, along with the show IP route, show
36:22IPv6 route, Okay? Ping and trace route
36:27are there command to verify static
36:29routes also includes show IP route
36:31static.
36:33Okay.
36:34You also have the show IP route network.
36:37Show running config. Okay.
36:39Pipeline section IP route.
36:43Okay. And for IPv6, when we just need to
36:46replace IP with IPv6.
36:49Okay. And that would work the same.
36:57All right. So, verifying a static route.
37:00So, again, using the topology that we
37:02have earlier. Okay. So, display only
37:05IPv4 static route.
37:07So, this output shows only the IPv4
37:10static routes in the routing table.
37:12Also note where the fighter will the
37:15filter begins the output.
37:18Okay. Excluding all the codes. So,
37:21something like show IP route static.
37:24Okay. Pipeline begin gateway. So, that
37:25means your output would start with your
37:28configuration
37:29gateway.
37:31All right. And this would be the
37:33static routes configured.
37:36All right.
37:39Next. How about displaying a specific
37:41IPv4 network? So, you can also do that.
37:43You can filter the output. Okay. So,
37:46this command will show output for only
37:49the specified network in the routing
37:51table.
37:52So, you specify the network to be
37:54192.168.2.1.
37:57Okay. So, that would be show IP route
37:59192.168.2.1.
38:02So, that would display routing entry for
38:042.0.
38:06And this is it.
38:07Okay. So, known via static.
38:09The administrator administrative
38:11distance is one. Take note that the AD
38:14for the static route is one and the
38:15metric is zero.
38:18All right.
38:20Next.
38:21How about displaying the IP before
38:23static route configuration?
38:25Okay, section IP route here.
38:28So, with this one, this command filters
38:30the running configuration for only IPV4
38:33static routes.
38:35Okay, so show running config pipeline
38:38section IP route. So,
38:40all configurations on the show run or on
38:44the running config having the IP route
38:47will be displayed.
38:48Okay, so rather than using just the show
38:51run which displays everything. So, if
38:53you just want to see on your screen a
38:55specific output that you desire, then
38:58you could make use of this filter
39:00options here, the pipeline, section,
39:02begin, and so on.
39:04All right.
39:07Next, display only IPV6 static routes.
39:11So, that would be show IPV6 route
39:14static. This output shows only the IPV6
39:17static routes in the routing table.
39:20Also, note where the filter begins the
39:22output excluding all the codes.
39:25All right. So, show IP route static.
39:31Next, how about displaying a specific
39:34IPV6 network?
39:36So, for instance, show IPV6 route 2001
39:40DB8 cafe colon two colon colon. So, this
39:45command will show output for only those
39:47specified network in the routing table.
39:50Similar with that of IPV4 that we have
39:52presented earlier.
39:55Next would be displaying the IPV6 static
39:57route configuration.
39:59So, something like section IPV6 route,
40:01so that would be displayed on your
40:03screen. So, see, you have a filtered
40:05output for your show run commands.
40:14All right, so on this section, configure
40:17IP default static routes, we will be
40:19dealing
40:20how to configure a default static route.
40:28Okay, so let's talk about default static
40:30route.
40:31This topic shows how to configure a
40:33default route for IPv4 and IPv6.
40:37So, it also explains the situation in
40:40which a default route is a good choice.
40:43So, a default route is a static route
40:45that matches all packets. So, instead of
40:48router storing routes for all the
40:50networks in the internet,
40:52they can store a single default route
40:55to represent any network that is not in
40:58the routing table.
41:00Okay, so take note that the default
41:01behavior of a router when it counters a
41:04packet not on the routing table is to
41:06drop the packet.
41:09Now, if you don't want if you don't want
41:10to do that because you want these
41:12packets be forwarded
41:15to a certain destination, then we have
41:17to use a default route, which is also
41:20known as the gateway of last resort.
41:23All right? So, routers commonly use
41:25default routes that are either
41:27configured locally
41:29or learned from other router using
41:32dynamic routing protocol.
41:34So, a default route does not require any
41:37far left bits to match between the
41:40default route and the destination IP
41:41address.
41:42So, the default route is used when no
41:45other routes in the routing table exist.
41:49Okay, so that matches the destination IP
41:51address of the packet. So, in other
41:53words,
41:54if more specific match does exist or
41:57does not exist,
41:59then the default route is used as the
42:01gateway of last resort.
42:04Okay? So, default static routes are
42:06commonly used when connecting an edge
42:09router to the service provider network
42:12or a stop router. So, when you say stop
42:15router, okay, so this one here is a stop
42:17router.
42:19So, a stop router is a router with only
42:22one upstream neighbor.
42:24Or neighboring now router. So, which is
42:28the ISP here.
42:30Okay? So, the figure shows a typical
42:33default static route scenario.
42:35So, R1 only needs to know about directly
42:39connected networks. For all the networks
42:42or for all other networks, it can use
42:44default static route pointing to R2 or
42:47to the ISP for instance in this case.
42:53Okay?
42:54So, let's talk about the syntax. Default
42:57static route syntax. So, the command
42:59syntax for IPv4 default static route is
43:02similar to any other IPv4 static route
43:05except that the network address
43:08is at 0.0.0.0.
43:13And the subnet mask is also 0.0.0.0.
43:18Okay? So, the quad zeros here, all
43:22right, quad zeros,
43:24in the route will match any network
43:26address.
43:28Okay? So, take note that an IPv4
43:31default static route is commonly
43:33referred to as quad zero route.
43:36All right? So, the basic syntax or the
43:40command syntax for an IPv4 default
43:42static route is IP route.
43:45You have got the quad zero, okay, quad
43:48zero,
43:49IP address
43:51or the next hop IP address or the exit
43:54interface.
43:57All right? Now, for IPv6, we have the
44:00same. So, the command syntax for IPv6
44:03default route is is similar to any other
44:06IPv6 static route, except that
44:09the IPv6 prefix or prefix length is
44:15colon colon
44:17zero.
44:18Which matches all routes. So, the syntax
44:21would be IPv6 route colon colon zero.
44:25You've got the next hop IP address, IPv6
44:27address, or the exit interface.
44:31All right?
44:34Okay, so configure a default static
44:36route.
44:38So, in figure one
44:40or in in the figure here, okay? So, our
44:42topology
44:44So, R1 could be configured with three
44:47static routes.
44:49One to reach
44:50each of the remote networks in the
44:52example topology, like what we did
44:54earlier.
44:55However,
44:56R1 is a stub router because it only has
44:59one connection.
45:02Okay? Or because it is only connected to
45:04R2.
45:06So, therefore,
45:07it would be more efficient to configure
45:09a single route
45:11on this router.
45:14All right?
45:17So, how do we configure this?
45:20Okay, so using the IPv4, again, the
45:23syntax would be IP route. You've got
45:25equal zero
45:27followed by
45:28the next hop IP address. Okay? So, which
45:31is This is again your next hop. All
45:33right? So, which is
45:36172.16.2.2.
45:39So, all traffic from R1 will be
45:42forwarded
45:44to 19 172.16.2.2.
45:49Okay? So, same thing, if you're going to
45:51configure R1
45:53with IPv6 default route, so that would
45:56be IPv6 route
45:58colon colon backslash zero.
46:01Okay? So, the next stop IP address,
46:03which is 2001 db8 acad
46:07two
46:09two.
46:12All right?
46:13So, that's configuring a default static
46:16route.
46:19Okay, so how would we verify
46:21the default static route?
46:23So, we can use the command show IP route
46:26static.
46:27Okay? So, the show IP route static
46:29command output from R1 displays the
46:31contents of the static routes in the
46:33routing table. So, take note that you've
46:36got an asterisk there.
46:40All right?
46:41So, the asterisk next to the route with
46:44code S
46:46Okay? So, the asterisk indicates that
46:48this is the static route.
46:51Okay? And it's a candidate default
46:53route.
46:54So, which is why it is elected as the
46:56gateway of last resort. So, if you'll
46:58observe here,
46:59also you'll have here gateway of last
47:01resort, which is at 172.16
47:052.2.
47:07Okay?
47:08To network any network.
47:12Okay? So, notice that the static default
47:14route configuration uses the backslash
47:17zero mask for IPv4 default routes.
47:20So, remember that IPv4 subnet mask in a
47:23routing table determines how many bits
47:25must match between the destination IP
47:27address
47:28of the packet and the route in the
47:30routing table.
47:32Okay? So, the slash zero mask indicates
47:34that none of the bits are required to
47:36match
47:37as long as a more specific match does
47:39not exist, the default static route
47:42matches all packets.
47:44All right?
47:50Okay.
47:51So, another thing is on IPv6, Okay?
47:55So, the example shows the IPv6 or show
47:58IPv6 route static command. Okay? So, to
48:01display the content of the routing table
48:03here. So, again, we have here an S.
48:06Okay? So, notice that the static default
48:09route configuration uses the colon colon
48:11zero prefix for IPv6 default route.
48:16All right?
48:17So, remember that the IPv6 prefix length
48:20in the routing table determines how many
48:23bits must match between the destination
48:26IP address of the packet and the route
48:28in the routing table.
48:29So, the colon colon slash zero prefix
48:32indicates that none of the bits are
48:34required to match. So, as long as a more
48:37specific match does not exist,
48:40the default static route matches all
48:42packets. Okay? So, other distinction
48:45than that of IPv4 is that we don't have
48:47an asterisk here on IPv6.
48:51All right?
48:56Okay. So, on this section, okay? So,
48:59configure a floating static route. What
49:01is a floating static route?
49:04Okay? So, have you heard of this
49:06floating static route before?
49:08Okay? So, as with the other topics in
49:11this module,
49:12you will learn how to configure an IPv4
49:16and IPv6 floating static routes and when
49:19to use them.
49:21Okay? So, another type of static route
49:23is the floating static route.
49:25Floating static routes are static routes
49:28that are used to provide a backup path
49:31to a primary static or dynamic route in
49:33the event of link failure.
49:36Okay? So, the floating static route is
49:39only used when the primary route is not
49:41available.
49:43So, to accomplish this, the floating
49:45static route is configured with a higher
49:47administrative distance than that of the
49:50primary route.
49:52So, the administrative distance
49:53represents the level of trustworthiness,
49:56all right, we're talking about on the
49:58last topics, okay? So, if multiple paths
50:01to the destination exists,
50:04the router will choose the path with the
50:06lowest administrative distance.
50:09So, for example,
50:11okay? So, assume that the administrator
50:14wants to create a floating static route
50:16as a backup
50:18to an EIGRP learned route.
50:23So, the floating static route must be
50:24configured with a higher administrative
50:27distance
50:28than that of EIGRP.
50:31So, EIGRP has an administrative distance
50:34of 90.
50:35So, if the floating static route is
50:37configured,
50:39okay? So, with an administrative
50:42distance, say 95,
50:44okay? The dynamic route learned through
50:47EIGRP is preferred
50:50to the floating static route having 95
50:52as administrative distance.
50:55So, if the EIGRP learned route is lost,
50:58the floating static route is used in its
51:01place.
51:02So, that is what we call backup.
51:04Okay?
51:09All right.
51:10So, in the figure here,
51:13okay? So, the branch router
51:17typically forwards all traffic to the
51:20headquarters router
51:22over
51:23a private
51:25WAN link.
51:27So, in this example, the routers
51:29exchange route information using EIGRP.
51:32For instance, this one here uses EIGRP.
51:40All right.
51:43So, this is the primary link.
51:47Okay? So, a floating static route with
51:50an administrative distance of 91
51:54Okay? So, if this uses 90
51:56Okay?
51:57And we are going to assign here, for
52:00instance, the administrative distance of
52:0191.
52:03So, whenever this private one fails
52:06All right? So, therefore, the connection
52:09to the internet having the
52:10administrative of 91 will become an
52:13active.
52:15Okay? So, if the private one link fails
52:18and the EIGRP route disappears, for
52:20instance, from the routing table
52:22the router selects the floating static
52:24route as the best path to reach the
52:28headquarter here.
52:30Okay? So, that's when we use the
52:33floating static route. So, if the
52:35primary thing or if the primary link
52:38fails
52:39you've got the secondary link.
52:41Okay? So, that will capture and continue
52:44the operation
52:45of the organization.
52:48All right? So, again, that's how we use
52:51and when we use the floating static
52:53routes.
52:56Okay? So, how about configuring IPv4 and
52:59IPv6 floating static route?
53:02So, IP floating static routes are
53:04configured by using the distance
53:06argument to specify an administrative
53:09distance. So, take note that earlier on
53:12the configuration of our
53:15um static routes, we did not specify
53:19the
53:22Okay? So, we did not specify the
53:26administrative distance.
53:28All right?
53:29So
53:31if no administrative distance is
53:33configured, like what we have here, no?
53:35Right? So, there would be no
53:36administrative distance configured
53:38there. That would be your primary link.
53:41Otherwise, if we have the administrative
53:44distance configured, that would be our
53:47floating static routes or the backup
53:49link.
53:51All right? So, refer to the topology in
53:53the figure.
53:54The IP route and IPv6 route commands,
53:58okay?
53:59are issued on R1.
54:05Okay? So, take note that this time our
54:08R1 is connected to R3
54:10and R1 also is connected to R2.
54:13Okay?
54:15So, R1 is configured IPv4 and IPv6
54:19default static routes pointing to R2.
54:24Because no administrative distance is
54:26configured, the default value is one.
54:30All right? So, take note that
54:32we have here,
54:34okay? We did We did not specify the
54:36administrative distance here and the
54:38default value is one.
54:41All right? That is for both IPv4 and
54:43IPv6.
54:46Okay? So,
54:49R1 also configured with IPv4 and IPv6
54:52floating static default routes pointing
54:54to R3.
55:01Okay?
55:02Now,
55:04take a look at the value of the
55:06administrative distance there.
55:08So, you've got administrative distance
55:10of five, okay? Both for IPv4 and IPv6.
55:16This value is greater than the value of
55:19one and therefore this route floats and
55:23is not present in the routing table
55:25unless the preferred route fails.
55:30All right? So, the show IP route
55:33command,
55:34okay? And the show IPv6 route output
55:37verifies the default routes to R2 are
55:39installed in the routing table.
55:41So, note that IPv4 floating static route
55:44to R3 is not present in the routing
55:46table.
55:47Okay?
55:48So, you'll have it here.
55:50Okay? So, IP route static, this is on
55:53R1.
55:54Okay? So, something like
55:57it's via 172 16
56:012.2.
56:03Okay?
56:04So, that means the active link is from
56:07R1.
56:09Okay?
56:10Going to R2.
56:12Going to R3.
56:13Going to for instance to PC trigger.
56:17But, if this link fails,
56:19that should traverse.
56:21Okay? So, from R1 R3.
56:24Take a look at also your
56:27next up IP address on IPv6.
56:30That's 2001 db8 acad.
56:33Okay? So, 2.2. Which is also this one.
56:36So, this is your primary
56:38link.
56:39Okay? So, that is why we cannot see the
56:41routing table.
56:43Okay? So, this link here because this
56:46one is active. Now, if this goes down,
56:48all right, that's the time
56:50this will be going up and you can see it
56:52on the routing table.
56:54All right?
57:00Okay? So, we use the show run command to
57:02verify the floating static routes
57:05are in the configuration.
57:08Okay?
57:09So, this would be
57:11our default
57:14or floating static routes.
57:16Okay? So, shown in the config.
57:18All right? So, for example, the
57:21following command output verifies that
57:23both IPv6 static default routes are in
57:26the running configuration.
57:28So, again, since there is no indicated
57:31um administrative distance here. This is
57:33our
57:36primary link or default. The default
57:37value is one. And once this goes down,
57:40this would be our backup here.
57:45All right?
57:49Okay, so next, test the floating static
57:53route. How are we going to test it?
57:55So, in the figure, what would happen if
57:57R2 fails? For instance, this R2 here
58:01goes down.
58:03What do you think will happen?
58:04Okay?
58:05So, basically, what will happen is
58:08this network here will not be able to
58:11reach other remote networks.
58:15All right?
58:17So, without doing other things, okay,
58:20you could simply shut down, okay,
58:24uh R2, both of its serial interfaces.
58:27So, that would simulate that the network
58:29is down. So, R1 automatically generates
58:31a syslog message for the link going
58:34down, right?
58:35So, a look at R1's routing table would
58:37show that the secondary route is being
58:40used. Okay, so assuming
58:43we have the link here.
58:47All right? So, assuming that we have the
58:48link there.
58:50Okay?
58:54All right. So, what would happen if R2
58:57fails? This is basically what you see.
59:00Okay? So, you're going to have
59:01notifications that
59:04the
59:06interface and the protocol went down.
59:09So, notice that at R1 automatically
59:12generates messages indicating that the
59:15serial interface to R2 is down.
59:20Okay?
59:22You'll have this.
59:27Okay. So, a look at the IP routing
59:29tables for R1 verifies that the floating
59:32static route default routes are now
59:34installed as the default routes and are
59:36pointing to R3 as the next hop router.
59:39So, you'll have it this
59:42time. Okay? So, our backup path.
59:47All right?
59:49So, that's how we test it. You could
59:51intentionally shut down the interface or
59:53your primary link and then see it on the
59:56routing table that it has changed to
59:57your
59:58floating static route.
1:00:05So, next section would be configure a
1:00:08static host routes.
1:00:10So, this topic shows how to configure
1:00:13an IPv4 and IPv6 static route or host
1:00:16route
1:00:18when to use them.
1:00:20A host route is an IPv4
1:00:24address with a 32-bit mask or an IPv6
1:00:29address with 128-bit
1:00:32mask.
1:00:34So, the following shows the three ways,
1:00:36okay?
1:00:38A host route can be added to the routing
1:00:41table. So, first would be
1:00:44automatically installed
1:00:47when an IP address is configured on the
1:00:49router.
1:00:51Configured as static host route
1:00:54and host route automatically obtained
1:00:57through other methods. Okay, so which
1:01:00will be discussed later in the courses.
1:01:05Okay?
1:01:06So, automatically installed host routes.
1:01:09So, Cisco IOS automatically installs a
1:01:11host route, also known as the local host
1:01:13route denoted by L,
1:01:15all right, on the routing table.
1:01:16So, when an interface address is
1:01:18configured on the router, the host route
1:01:21allows for a more efficient process for
1:01:24packets that are directed to the router
1:01:27itself, rather than for packet
1:01:29forwarding.
1:01:31So, this is in addition to the connected
1:01:34route.
1:01:35Designated with C
1:01:37in the routing table for the network
1:01:39address of the interface.
1:01:42So, when an active interface on a router
1:01:45is configured with an IP address,
1:01:47a local host route is automatically
1:01:50added to the routing table.
1:01:53So, the local routes are marked with
1:01:55letter L
1:01:56in the output
1:01:58of the routing table. Like what you have
1:02:00seen earlier on the past demonstration
1:02:02or the past
1:02:03um diagrams presented.
1:02:06All right?
1:02:11Okay, so for example, refer to the
1:02:14topology in the figure.
1:02:17The IP address assigned to branch serial
1:02:200 1 0,
1:02:24okay?
1:02:26are 198
1:02:2951
1:02:30100 .1
1:02:33/30.
1:02:35And that would be 2001
1:02:38DB8 acad 1,
1:02:41okay? colon colon 1 /64.
1:02:46Now, the local routes for the interface
1:02:48are installed by the IOS in the IPv4 and
1:02:52IPv6 routing tables.
1:02:54Okay?
1:02:56So, it's in here.
1:02:58All right? So, it's denoted by L.
1:03:01Okay?
1:03:03There.
1:03:06So, the IP address assigned to the
1:03:07branch, okay? So, take note, we're
1:03:09indicated onto the
1:03:12routing table. So, denoted here by
1:03:14letter L. Okay?
1:03:18Now, a host route can be manually
1:03:20configured with a static route to direct
1:03:23traffic to a specific destination
1:03:25device, such as the server shown in the
1:03:27figure here.
1:03:29The static route uses the destination IP
1:03:31address 255.255.255/32
1:03:36mask.
1:03:37That would be for IPv4 host routes. And
1:03:41a /128 prefix length for the IPv6 host
1:03:45routes.
1:03:47Okay? So, in here, you'll observe you've
1:03:49got IP route.
1:03:51That would be 209.165.200.238.
1:03:56Okay?
1:03:57255.255.255.255.
1:04:0219198.51.100.2.
1:04:08Okay? So, for IPv6,
1:04:10that would be IPv6 route
1:04:122001:db8:acad:2.
1:04:15Okay? So, colon colon 238.
1:04:192001
1:04:21db8:acad:1:colon:colon:2.
1:04:25All right?
1:04:29Okay, so how do we verify a static host
1:04:31route?
1:04:33So, a review of both IPv4 and IPv6 route
1:04:35tables verifies that the routes are
1:04:37active.
1:04:39Okay? So, it's in here.
1:04:48Okay?
1:04:49Now, for IPv6 static routes, the next
1:04:52hop address can be
1:04:54the link-local address of the adjacent
1:04:56router. However,
1:04:58you must specify an interface type and
1:05:01an interface number when using
1:05:03link-local address as the next hop.
1:05:06As shown in the example here.
1:05:08So, first, the original IPv6 static host
1:05:12is removed.
1:05:13Okay?
1:05:15Then a fully specified route configured
1:05:17with IPv6 address of the server and the
1:05:20IPv6 link local address of the ISP
1:05:23router.
1:05:25All right?
1:05:31So, that ends up this video lecture.
1:05:34Please see the video demo on how to
1:05:36configure
1:05:38IP static routing.
1:05:40Thank you very much. Thanks for watching
1:05:41and listening. Have a great day.

About this transcript

This page contains the full transcript of SRWE M15 IP Static Routing by Santelmo, generated from the public captions YouTube serves with the video. The transcript has 7,671 words across 1,523 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.