1 00:00:00,000 --> 00:00:02,832 [MUSIC PLAYING] 2 00:00:02,832 --> 00:00:07,090 3 00:00:07,090 --> 00:00:13,570 Next up, let's have a quick discussion about NSF and NSR. 4 00:00:13,570 --> 00:00:17,230 This is Non-Stop Forwarding and Non-Stop Routing. 5 00:00:17,230 --> 00:00:20,140 Both of these sort of do the same job. 6 00:00:20,140 --> 00:00:24,400 Although, NSR does it in a slightly different way. 7 00:00:24,400 --> 00:00:27,100 And because they're basically doing the same thing, 8 00:00:27,100 --> 00:00:29,030 we really don't need both. 9 00:00:29,030 --> 00:00:31,870 So we're going to be using one or the other, 10 00:00:31,870 --> 00:00:35,513 where NSR is sort of the newer way to do it. 11 00:00:35,513 --> 00:00:37,180 So let's jump in and take a look at some 12 00:00:37,180 --> 00:00:38,680 of the details on these. 13 00:00:38,680 --> 00:00:41,320 And then we'll take a look at what the defaults are 14 00:00:41,320 --> 00:00:46,340 on IOS XE and IOS XR. 15 00:00:46,340 --> 00:00:49,430 So Non-Stop Forwarding and Non-Stop Routing 16 00:00:49,430 --> 00:00:53,480 are both here to pretty much handle the exact same issue. 17 00:00:53,480 --> 00:00:57,980 Again, they're both technologies that aid with stability, 18 00:00:57,980 --> 00:01:01,920 or you could say, convergence during route processor 19 00:01:01,920 --> 00:01:03,080 switchovers. 20 00:01:03,080 --> 00:01:07,100 So if you have a router with multiple route processors, 21 00:01:07,100 --> 00:01:10,670 one of them fails, and we failover to the other one. 22 00:01:10,670 --> 00:01:13,940 These two technologies help with the stability 23 00:01:13,940 --> 00:01:16,880 of things like our database and our neighborship 24 00:01:16,880 --> 00:01:18,770 during that failover. 25 00:01:18,770 --> 00:01:21,980 So let's start by talking about Non-Stop Forwarding. 26 00:01:21,980 --> 00:01:25,440 Non-Stop Forwarding has been around for quite some time. 27 00:01:25,440 --> 00:01:28,730 And what this does is it allows that forwarding 28 00:01:28,730 --> 00:01:33,600 to continue using already known routes. 29 00:01:33,600 --> 00:01:36,980 So routes that are installed on our neighbors, routes 30 00:01:36,980 --> 00:01:40,910 that are installed on our local line cards, things like this, 31 00:01:40,910 --> 00:01:43,500 we continue forwarding traffic. 32 00:01:43,500 --> 00:01:45,110 Now, there are two versions of this. 33 00:01:45,110 --> 00:01:49,220 There is a Cisco version, which pretty much came along first. 34 00:01:49,220 --> 00:01:53,580 And then the IETF released an industry standard version 35 00:01:53,580 --> 00:01:57,270 so that other vendors could participate in this as well. 36 00:01:57,270 --> 00:02:01,380 Now, NSF routers generally fall into three categories. 37 00:02:01,380 --> 00:02:05,960 The first is an NSF capable router. 38 00:02:05,960 --> 00:02:08,509 You could say this is the router actually doing 39 00:02:08,509 --> 00:02:09,919 the non-stop forwarding. 40 00:02:09,919 --> 00:02:11,480 One of its requirements is it has 41 00:02:11,480 --> 00:02:13,430 to have dual route processors. 42 00:02:13,430 --> 00:02:15,660 If there aren't redundant processors, 43 00:02:15,660 --> 00:02:17,750 well then there's nothing to failover too. 44 00:02:17,750 --> 00:02:19,670 And if we lose our route processor, 45 00:02:19,670 --> 00:02:21,530 well then we're just down. 46 00:02:21,530 --> 00:02:25,940 One of its jobs then is to relearn the OSPF neighbors 47 00:02:25,940 --> 00:02:29,540 without causing any neighbor resets. 48 00:02:29,540 --> 00:02:32,600 We don't want our neighbors to completely wipe out 49 00:02:32,600 --> 00:02:35,030 their databases with our information, 50 00:02:35,030 --> 00:02:37,250 and have our neighbors start over. 51 00:02:37,250 --> 00:02:41,150 It's then going to reaquire the link state database. 52 00:02:41,150 --> 00:02:43,160 In order for all of this to work, 53 00:02:43,160 --> 00:02:46,040 it uses signaling, which is actually 54 00:02:46,040 --> 00:02:50,480 done with a link local LSA to the other routers, 55 00:02:50,480 --> 00:02:53,480 telling them that a failover is occurring. 56 00:02:53,480 --> 00:02:56,270 Now, in order for that to work, we 57 00:02:56,270 --> 00:02:58,230 need our second category of routers, 58 00:02:58,230 --> 00:03:01,430 which is the NSF aware routers. 59 00:03:01,430 --> 00:03:05,030 These are routers that are going to actually recognize 60 00:03:05,030 --> 00:03:08,850 that signal coming from the failing router. 61 00:03:08,850 --> 00:03:10,490 So, the router above. 62 00:03:10,490 --> 00:03:13,130 What they're going to do in response to this 63 00:03:13,130 --> 00:03:16,760 is they're going to preserve the OSPF link state 64 00:03:16,760 --> 00:03:20,730 database, as well as their own routing tables. 65 00:03:20,730 --> 00:03:26,780 We also allow the failing router to rebuild its neighborships, 66 00:03:26,780 --> 00:03:29,990 again, without doing a full reset. 67 00:03:29,990 --> 00:03:34,610 The whole idea here is we rebuild everything with OSPF 68 00:03:34,610 --> 00:03:38,660 while we are continuing to use the old information that we 69 00:03:38,660 --> 00:03:39,950 had from OSPF. 70 00:03:39,950 --> 00:03:42,230 Now, the third type of router is one 71 00:03:42,230 --> 00:03:45,260 that is simply not NSF aware. 72 00:03:45,260 --> 00:03:47,480 And the problem with this is, of course, it's 73 00:03:47,480 --> 00:03:50,780 not going to participate in NSF at all. 74 00:03:50,780 --> 00:03:53,960 And after this failover occurs, we're 75 00:03:53,960 --> 00:03:57,997 going to have to just reconverge OSPF the normal way. 76 00:03:57,997 --> 00:04:00,080 We're going to have to re-establish neighborships, 77 00:04:00,080 --> 00:04:02,120 re-exchange databases. 78 00:04:02,120 --> 00:04:05,690 They're just not participating in NSF. 79 00:04:05,690 --> 00:04:10,880 Now, in fairness, most routers today do support NSF. 80 00:04:10,880 --> 00:04:12,770 Again, they may not all be capable 81 00:04:12,770 --> 00:04:15,290 because they don't have dual route processors. 82 00:04:15,290 --> 00:04:18,680 But most routers are NSF aware. 83 00:04:18,680 --> 00:04:20,930 The big question we have to worry about 84 00:04:20,930 --> 00:04:26,510 is, are they IETF aware or are they Cisco only aware? 85 00:04:26,510 --> 00:04:28,610 And that could affect our decisions 86 00:04:28,610 --> 00:04:30,390 as far as what to use. 87 00:04:30,390 --> 00:04:34,970 So the second technology here is NSR, or Non-Stop Routing. 88 00:04:34,970 --> 00:04:39,890 This also allows for the failover process restart 89 00:04:39,890 --> 00:04:44,750 or in-service software update, without affecting neighbors. 90 00:04:44,750 --> 00:04:49,880 And this is where NSR is a bit better than NSF. 91 00:04:49,880 --> 00:04:54,920 This uses something called warm standby extensions, which 92 00:04:54,920 --> 00:05:02,000 essentially runs a standby OSPF process on the standby RP. 93 00:05:02,000 --> 00:05:06,260 That is then kept synchronized with the OSPF process 94 00:05:06,260 --> 00:05:08,270 on the primary RP. 95 00:05:08,270 --> 00:05:11,210 So now, when there's an RP failover, 96 00:05:11,210 --> 00:05:17,210 the standby OSPF process simply takes over on the standby RP, 97 00:05:17,210 --> 00:05:20,450 and we keep going as if nothing ever happened. 98 00:05:20,450 --> 00:05:23,840 That's why this does not affect the neighbors. 99 00:05:23,840 --> 00:05:25,460 That makes this a better solution. 100 00:05:25,460 --> 00:05:27,500 Because now, the neighbors don't have 101 00:05:27,500 --> 00:05:33,120 to be NSR aware, or NSF capable, or anything else. 102 00:05:33,120 --> 00:05:37,700 This is all done in-house on this NSR capable router. 103 00:05:37,700 --> 00:05:40,340 And again, since this does the exact same job, 104 00:05:40,340 --> 00:05:43,040 but does it in-house, this completely 105 00:05:43,040 --> 00:05:46,720 alleviates the requirement for NSR. 106 00:05:46,720 --> 00:05:49,400 We don't need to have both at the same time. 107 00:05:49,400 --> 00:05:51,920 So let's take a look at these on the command line. 108 00:05:51,920 --> 00:05:53,860 We'll look at the topology real briefly, 109 00:05:53,860 --> 00:05:56,090 just to see which routers we're going to look at. 110 00:05:56,090 --> 00:05:58,300 But it really doesn't matter where they are in the topology. 111 00:05:58,300 --> 00:06:00,675 We're just going to be looking at their default settings. 112 00:06:00,675 --> 00:06:05,380 So we are going to want to look at both IOS XR and IOS XE. 113 00:06:05,380 --> 00:06:08,590 So we will simply be taking a look at Router 1, 114 00:06:08,590 --> 00:06:10,510 which is running IOS XR. 115 00:06:10,510 --> 00:06:14,710 And then we'll look at Router 5, which is running IOS XE. 116 00:06:14,710 --> 00:06:18,970 So we'll start by taking a look at Router 1. 117 00:06:18,970 --> 00:06:23,690 So real simply here on Router 1, we'll do a show IP OSPF. 118 00:06:23,690 --> 00:06:27,380 And we see right here, that it says NSR Non-Stop 119 00:06:27,380 --> 00:06:29,430 Routing is enabled. 120 00:06:29,430 --> 00:06:34,250 So this feature is enabled by default on IOS XR. 121 00:06:34,250 --> 00:06:38,300 Since this supports NSR, there would really be no reason 122 00:06:38,300 --> 00:06:40,100 to ever go back to NSF. 123 00:06:40,100 --> 00:06:42,780 However, that feature is available 124 00:06:42,780 --> 00:06:44,360 if you wanted to enable it. 125 00:06:44,360 --> 00:06:46,970 Now let's take a look at Router 5. 126 00:06:46,970 --> 00:06:49,310 Again, if we do our show IP OSPF, 127 00:06:49,310 --> 00:06:52,400 this actually lists it down towards the bottom more. 128 00:06:52,400 --> 00:06:55,610 But we can see here that the IETF NSF helper 129 00:06:55,610 --> 00:07:00,530 support is enabled, as well as the Cisco NSF helper support. 130 00:07:00,530 --> 00:07:05,390 Now, the helper support means that this router is NSF aware. 131 00:07:05,390 --> 00:07:08,240 This router, of course, is not NSF capable 132 00:07:08,240 --> 00:07:11,390 because it does not have dual route processors. 133 00:07:11,390 --> 00:07:14,150 Since it doesn't have dual route processors, 134 00:07:14,150 --> 00:07:18,680 there's also really no good reason to turn on NSR. 135 00:07:18,680 --> 00:07:22,020 However, if you do need it or want it just 136 00:07:22,020 --> 00:07:24,000 to look at it for whatever reason, 137 00:07:24,000 --> 00:07:25,910 you can certainly turn it on. 138 00:07:25,910 --> 00:07:29,720 Simply go into router OSPF and type NSR. 139 00:07:29,720 --> 00:07:30,980 It'll now be enabled. 140 00:07:30,980 --> 00:07:33,270 We do our show epos OSPF again. 141 00:07:33,270 --> 00:07:36,080 We see here now, Non-Stop Routing is enabled. 142 00:07:36,080 --> 00:07:38,750 Again, it won't actually do anything on this router 143 00:07:38,750 --> 00:07:44,330 because this router is not a dual route processor device. 144 00:07:44,330 --> 00:07:48,000 In this video, we talked about two, well, 145 00:07:48,000 --> 00:07:50,570 sort of competing or redundant things 146 00:07:50,570 --> 00:07:54,320 that we can do on our routers to aid in the event of a route 147 00:07:54,320 --> 00:07:55,880 processor failover. 148 00:07:55,880 --> 00:07:59,600 The first is NSF, or Non-Stop Forwarding, 149 00:07:59,600 --> 00:08:01,820 which actually involves the neighbors, 150 00:08:01,820 --> 00:08:05,030 and has them basically negotiate this capability, 151 00:08:05,030 --> 00:08:08,780 so that we can keep forwarding traffic in the event of a route 152 00:08:08,780 --> 00:08:10,580 process switchover. 153 00:08:10,580 --> 00:08:15,600 Then we looked at NSR, its newer replacement, if you will, 154 00:08:15,600 --> 00:08:18,350 that allows it to do all of that in-house. 155 00:08:18,350 --> 00:08:21,050 It simply fails over to the other route processor, 156 00:08:21,050 --> 00:08:24,230 keeps right on going as if nothing happened. 157 00:08:24,230 --> 00:08:27,080 Not affecting the neighbors at all. 158 00:08:27,080 --> 00:08:29,120 I hope this has been informative for you, 159 00:08:29,120 --> 00:08:32,200 and I'd like to thank you for viewing. 160 00:08:32,200 --> 00:08:35,000