1 00:00:00,000 --> 00:00:04,730 [AUDIO LOGO] 2 00:00:04,730 --> 00:00:07,100 3 00:00:07,100 --> 00:00:12,920 So we've mentioned IS-IS network type broadcast, or LAN, 4 00:00:12,920 --> 00:00:14,570 quite a few times now. 5 00:00:14,570 --> 00:00:17,520 We've talked a little bit about its hellos and such. 6 00:00:17,520 --> 00:00:20,300 And in a previous video, we also did, in fact, 7 00:00:20,300 --> 00:00:22,760 mention that it uses something called 8 00:00:22,760 --> 00:00:28,580 a Designated Intermediate System or a D-I-S or a DIS. 9 00:00:28,580 --> 00:00:33,980 This is very similar to OSPF's DR, or designated router. 10 00:00:33,980 --> 00:00:36,590 The purpose of this is to prevent 11 00:00:36,590 --> 00:00:40,820 the mass flooding of updates on a multi-access segment. 12 00:00:40,820 --> 00:00:43,610 It's going to be far more efficient to have 13 00:00:43,610 --> 00:00:46,700 all of the updates sent to 1 central source, 14 00:00:46,700 --> 00:00:50,480 and then that central source disseminates that information 15 00:00:50,480 --> 00:00:53,780 out to all of the other neighborships on the LAN. 16 00:00:53,780 --> 00:00:57,890 So let's jump in and take a look at how the DIS actually 17 00:00:57,890 --> 00:01:00,050 operates in IS-IS. 18 00:01:00,050 --> 00:01:04,489 And then we'll jump into both Wireshark and the command line, 19 00:01:04,489 --> 00:01:08,570 and get a look at what this looks like, both on the wire 20 00:01:08,570 --> 00:01:13,100 and in our show commands and so on in the iOS. 21 00:01:13,100 --> 00:01:16,460 Let's jump in and get started. 22 00:01:16,460 --> 00:01:20,170 So, as we've mentioned, on a broadcast, 23 00:01:20,170 --> 00:01:24,230 or we would also call it multi-access network type, 24 00:01:24,230 --> 00:01:25,750 such as what we're showing over here 25 00:01:25,750 --> 00:01:28,930 in our diagram as an Ethernet segment, 26 00:01:28,930 --> 00:01:36,350 IS-IS will elect a DIS, or that Designated Intermediate System. 27 00:01:36,350 --> 00:01:42,520 Now, the job of the DIS is to actually be responsible for 28 00:01:42,520 --> 00:01:45,790 and handle the pseudonode. 29 00:01:45,790 --> 00:01:49,540 The pseudonode is being represented over 30 00:01:49,540 --> 00:01:53,290 in our diagram by this sort of grayed out router 31 00:01:53,290 --> 00:01:54,890 here in the middle. 32 00:01:54,890 --> 00:01:58,150 So the way this works is the pseudonode 33 00:01:58,150 --> 00:02:00,520 is created by the DIS. 34 00:02:00,520 --> 00:02:03,850 It's not, of course, a real entity. 35 00:02:03,850 --> 00:02:06,580 However, it acts as a virtual router 36 00:02:06,580 --> 00:02:10,940 to be connected to all the other nodes. 37 00:02:10,940 --> 00:02:14,260 So the first thing to note is that the pseudonode 38 00:02:14,260 --> 00:02:18,100 will be logically connected to the other nodes. 39 00:02:18,100 --> 00:02:21,610 And again, that's being shown by these neighborships 40 00:02:21,610 --> 00:02:24,370 here, where each of the other nodes 41 00:02:24,370 --> 00:02:27,670 is connecting to the pseudonode regardless 42 00:02:27,670 --> 00:02:30,310 of the actual physical underlay. 43 00:02:30,310 --> 00:02:32,920 The whole purpose of this pseudonode 44 00:02:32,920 --> 00:02:36,010 is to represent the LAN Itself. 45 00:02:36,010 --> 00:02:39,550 The idea here is, again, we have one device 46 00:02:39,550 --> 00:02:42,400 acting on behalf of the network segment, 47 00:02:42,400 --> 00:02:45,200 rather than all of these devices, 48 00:02:45,200 --> 00:02:47,830 all having to exchange databases with each other. 49 00:02:47,830 --> 00:02:51,290 It's just a much more organized system. 50 00:02:51,290 --> 00:02:54,430 Some other things to note about this device DIS 51 00:02:54,430 --> 00:02:59,620 is it can be different for the level 1 and the level 2 52 00:02:59,620 --> 00:03:00,950 databases. 53 00:03:00,950 --> 00:03:08,800 So just as an example, maybe this router is the DIS level 1, 54 00:03:08,800 --> 00:03:14,110 and maybe this router is for level 2. 55 00:03:14,110 --> 00:03:18,440 Again, they can be different for the two different databases. 56 00:03:18,440 --> 00:03:20,930 So the next question might be, well, 57 00:03:20,930 --> 00:03:24,107 how do each of these routers get elected as the DIS 58 00:03:24,107 --> 00:03:25,430 to begin with? 59 00:03:25,430 --> 00:03:31,070 Well, the DIS is elected based on three criteria. 60 00:03:31,070 --> 00:03:34,780 The first criteria is that the router actually 61 00:03:34,780 --> 00:03:36,550 has to have adjacencies. 62 00:03:36,550 --> 00:03:39,310 You are not going to be a DIS if you 63 00:03:39,310 --> 00:03:40,840 don't have any neighborships. 64 00:03:40,840 --> 00:03:42,580 So in other words, if it were just 65 00:03:42,580 --> 00:03:45,550 a single router on a segment, it's 66 00:03:45,550 --> 00:03:49,300 not going to elect itself as a DIS. 67 00:03:49,300 --> 00:03:55,060 Next, it will go to the highest interface priority. 68 00:03:55,060 --> 00:03:57,610 The default is 64. 69 00:03:57,610 --> 00:04:01,771 So if you wanted to force which router would be the DIS, 70 00:04:01,771 --> 00:04:04,720 the easiest thing to do would be to raise 71 00:04:04,720 --> 00:04:10,480 that router's interface priority to be above 64. 72 00:04:10,480 --> 00:04:14,530 If all of the devices have the same interface priority, 73 00:04:14,530 --> 00:04:18,399 it will then use the subnetwork point of attachment, 74 00:04:18,399 --> 00:04:22,820 or the SNPA, as the tiebreaker. 75 00:04:22,820 --> 00:04:28,370 Now, so far, this might sound a whole lot like an OSPF DR. 76 00:04:28,370 --> 00:04:30,080 And while the fact of the matter is, 77 00:04:30,080 --> 00:04:32,210 we've said it a few times now, it 78 00:04:32,210 --> 00:04:35,090 is very similar, both in concept and in 79 00:04:35,090 --> 00:04:36,890 how it actually operates. 80 00:04:36,890 --> 00:04:41,420 However, it does have two fundamental differences, which 81 00:04:41,420 --> 00:04:42,920 are our last two points here. 82 00:04:42,920 --> 00:04:44,800 Let's take a look. 83 00:04:44,800 --> 00:04:47,226 So the first of these is that the DIS 84 00:04:47,226 --> 00:04:50,230 is a preemptive process. 85 00:04:50,230 --> 00:04:53,460 That means that if a new router comes online 86 00:04:53,460 --> 00:04:57,010 that would win based on these criteria, 87 00:04:57,010 --> 00:05:00,900 it will actually take over and become the DIS. 88 00:05:00,900 --> 00:05:07,500 Keep in mind that the DR in OSPF does not do preemption. 89 00:05:07,500 --> 00:05:10,920 So this is not something that happens with OSPF. 90 00:05:10,920 --> 00:05:15,810 If a new router comes on in OSPF, maybe it becomes the BDR, 91 00:05:15,810 --> 00:05:18,840 maybe it becomes nothing, but it does not 92 00:05:18,840 --> 00:05:22,530 take over just because based on the scenario it theoretically 93 00:05:22,530 --> 00:05:27,840 should be the DR. It's not preemptive where the DIS is. 94 00:05:27,840 --> 00:05:29,760 And, of course, the other big one 95 00:05:29,760 --> 00:05:34,860 here is there is no backup DIS. 96 00:05:34,860 --> 00:05:37,440 Of course, we know that in OSPF we 97 00:05:37,440 --> 00:05:41,340 have the BDR, which is the Backup Designated Router. 98 00:05:41,340 --> 00:05:47,730 And again, we're just saying no such equivalency here in IS-IS. 99 00:05:47,730 --> 00:05:49,710 It's just the DIS. 100 00:05:49,710 --> 00:05:54,480 And if the DIS fails, we simply elect another one. 101 00:05:54,480 --> 00:05:57,500 So now that we've seen a bit about how this works. 102 00:05:57,500 --> 00:06:02,000 Let's actually jump into the command line and Wireshark, 103 00:06:02,000 --> 00:06:04,670 and take a look at this in a little bit more detail 104 00:06:04,670 --> 00:06:06,530 in its actual operation. 105 00:06:06,530 --> 00:06:09,840 Let's start by looking at our topology, 106 00:06:09,840 --> 00:06:12,193 so we know what's connected to what, and well, 107 00:06:12,193 --> 00:06:13,610 theoretically, which router should 108 00:06:13,610 --> 00:06:15,330 be the DIS to begin with. 109 00:06:15,330 --> 00:06:20,090 And again, we'll jump in and see how that's working. 110 00:06:20,090 --> 00:06:21,830 Again, for this demonstration, we 111 00:06:21,830 --> 00:06:25,340 will be using IS-IS Basic Topology, 112 00:06:25,340 --> 00:06:29,570 and this is simply our five routers, 1 through 5, 113 00:06:29,570 --> 00:06:32,120 all connected, as shown here. 114 00:06:32,120 --> 00:06:34,500 For this particular demonstration, 115 00:06:34,500 --> 00:06:41,270 we will be focusing on the LAN segment between R1, R3, and R5. 116 00:06:41,270 --> 00:06:45,560 Now, given that nothing has been configured as far as priority, 117 00:06:45,560 --> 00:06:50,960 all of these should right now have a 64 for their interface 118 00:06:50,960 --> 00:06:54,530 priority, because, again, that's the default. 119 00:06:54,530 --> 00:06:58,940 That means it's going to come to the SNPA for the tiebreaker. 120 00:06:58,940 --> 00:07:03,230 That means that router 5 should be our current DIS 121 00:07:03,230 --> 00:07:05,030 on this segment. 122 00:07:05,030 --> 00:07:07,920 Let's jump into the command line and check it out. 123 00:07:07,920 --> 00:07:10,340 And again, like we said, we'll take a look at Wireshark 124 00:07:10,340 --> 00:07:12,310 as well. 125 00:07:12,310 --> 00:07:14,820 So we'll start off here on router 1. 126 00:07:14,820 --> 00:07:18,810 Let's start with a show isis adjacency detail now 127 00:07:18,810 --> 00:07:22,860 router 2 here, of course, is a point-to-point link going over 128 00:07:22,860 --> 00:07:23,550 to router 2. 129 00:07:23,550 --> 00:07:25,440 That's not our concern right now. 130 00:07:25,440 --> 00:07:31,110 We're concerned with the gigabit 0001 interface going to router 131 00:07:31,110 --> 00:07:33,270 3 and router 5. 132 00:07:33,270 --> 00:07:37,410 And, as we can see here, we see that the DIS priority 133 00:07:37,410 --> 00:07:40,290 is currently 64 for both of these, 134 00:07:40,290 --> 00:07:43,920 the local priority on each of them is also 64, 135 00:07:43,920 --> 00:07:47,070 and the neighbor priority is 64. 136 00:07:47,070 --> 00:07:49,350 So they're all the defaults. 137 00:07:49,350 --> 00:07:50,280 However. 138 00:07:50,280 --> 00:07:55,710 We can also see here that router 5 has won the DIS selection, 139 00:07:55,710 --> 00:07:59,160 because it says right here, under the neighbor priority, 140 00:07:59,160 --> 00:08:02,205 that this is, in fact, the DIS. 141 00:08:02,205 --> 00:08:05,430 So let's jump into Wireshark real quick. 142 00:08:05,430 --> 00:08:09,510 And see what this actually looks like on the wire in the hellos. 143 00:08:09,510 --> 00:08:14,040 So we'll just capture on gigabit 0001 on router 1, 144 00:08:14,040 --> 00:08:17,160 and let's see what we can see. 145 00:08:17,160 --> 00:08:19,170 So here in our Wireshark capture, 146 00:08:19,170 --> 00:08:22,410 well just look at packet 1 here, which is 147 00:08:22,410 --> 00:08:25,515 a hello coming from router 3. 148 00:08:25,515 --> 00:08:29,350 Now, if we open up the ISIS HELLO field on this, 149 00:08:29,350 --> 00:08:33,690 we can see here under System ID that the designated 150 00:08:33,690 --> 00:08:38,220 IS, or the DIS, is in fact router 5. 151 00:08:38,220 --> 00:08:40,530 Let's actually look at a hello from router 5, 152 00:08:40,530 --> 00:08:42,240 and see if that looks any different. 153 00:08:42,240 --> 00:08:44,170 That would be packet 3. 154 00:08:44,170 --> 00:08:47,700 Notice that with packet 3 highlighted, the fields update, 155 00:08:47,700 --> 00:08:49,950 but it's still showing the system 156 00:08:49,950 --> 00:08:53,400 ID of the designated IS as 5. 157 00:08:53,400 --> 00:08:55,140 And, of course, we wouldn't expect 158 00:08:55,140 --> 00:08:56,920 that to be any different. 159 00:08:56,920 --> 00:08:59,790 If we look at a hello from router 1, which in this case 160 00:08:59,790 --> 00:09:03,990 would be packet 7, we see this looks the same. 161 00:09:03,990 --> 00:09:06,360 And, of course, that's absolutely critical 162 00:09:06,360 --> 00:09:09,240 because, at the moment, everybody agrees 163 00:09:09,240 --> 00:09:12,660 who the DIS is, router 5. 164 00:09:12,660 --> 00:09:16,230 Now, of course, we could verify this on router 5, as well. 165 00:09:16,230 --> 00:09:19,500 The commands a little bit different, since it's IOS XE. 166 00:09:19,500 --> 00:09:22,570 So let's jump over and check there. 167 00:09:22,570 --> 00:09:26,620 So if we do a show clns is neighbors detail, 168 00:09:26,620 --> 00:09:29,110 we can get a little bit of a look here. 169 00:09:29,110 --> 00:09:32,140 Notice for the gigabit 1 interface, 170 00:09:32,140 --> 00:09:37,720 both from router 1 and router 3, they're listing the circuit ID 171 00:09:37,720 --> 00:09:41,260 as router 5.01. 172 00:09:41,260 --> 00:09:44,350 And, again, this is because the DIS is 173 00:09:44,350 --> 00:09:46,250 responsible for this segment. 174 00:09:46,250 --> 00:09:49,300 So this is another indicator that router 5 175 00:09:49,300 --> 00:09:52,515 is, in fact, the DIS. 176 00:09:52,515 --> 00:09:56,245 But let's take some control of this and let's make router 1 177 00:09:56,245 --> 00:09:57,860 the DIS on this segment. 178 00:09:57,860 --> 00:10:00,660 So on router 1, we'll go into configuration. 179 00:10:00,660 --> 00:10:03,520 We're going to do our router is-is process 180 00:10:03,520 --> 00:10:04,960 into the interface. 181 00:10:04,960 --> 00:10:07,220 And let's set the priority. 182 00:10:07,220 --> 00:10:11,170 You can see here that the range is 0 to 127. 183 00:10:11,170 --> 00:10:14,090 And we know that the default is 64, 184 00:10:14,090 --> 00:10:17,230 so let's just pick something like 120. 185 00:10:17,230 --> 00:10:19,250 We'll commit our changes. 186 00:10:19,250 --> 00:10:21,370 We'll exit configuration mode. 187 00:10:21,370 --> 00:10:25,180 And let's do the show ISIS adjacency detail again. 188 00:10:25,180 --> 00:10:28,630 Now notice under router 3 and router 5, 189 00:10:28,630 --> 00:10:32,620 the DIS priority is listed as 120, which is what we just 190 00:10:32,620 --> 00:10:34,456 set router 1 to. 191 00:10:34,456 --> 00:10:37,540 And notice it's saying that our local priority 192 00:10:37,540 --> 00:10:43,110 towards that neighbor is 120, and therefore we are the DIS. 193 00:10:43,110 --> 00:10:47,050 Notice It's saying that the DIS is local. 194 00:10:47,050 --> 00:10:51,260 Both of those neighbors have a priority of 64. 195 00:10:51,260 --> 00:10:55,996 So this is an indicator that router 1 is, in fact, the DIS. 196 00:10:55,996 --> 00:11:00,210 Now, let's go back to Wireshark and see if it agrees. 197 00:11:00,210 --> 00:11:05,280 So packet 1 on this capture is actually a Hello from router 1. 198 00:11:05,280 --> 00:11:09,730 Let's go ahead and expand the ISIS HELLO header. 199 00:11:09,730 --> 00:11:14,350 And what we see here is that the system ID of the designated IS 200 00:11:14,350 --> 00:11:16,530 is now router 1. 201 00:11:16,530 --> 00:11:18,780 Of course, all the routers should agree. 202 00:11:18,780 --> 00:11:23,010 Let's look at packet 5, which is from router 5. 203 00:11:23,010 --> 00:11:27,000 We see that also agrees that the DIS is router 1. 204 00:11:27,000 --> 00:11:30,300 And let's also verify router 3. router 3 205 00:11:30,300 --> 00:11:35,880 also shows the system ID of the designated IS as router 1. 206 00:11:35,880 --> 00:11:42,230 So we have successfully switched over our DIS to be router 1. 207 00:11:42,230 --> 00:11:45,470 So in this video, we took a closer look 208 00:11:45,470 --> 00:11:51,080 at the Designated Intermediate System or DIS operation 209 00:11:51,080 --> 00:11:52,700 in IS-IS. 210 00:11:52,700 --> 00:11:56,990 We actually saw how it was pretty similar to OSPF's DR 211 00:11:56,990 --> 00:11:58,230 concept. 212 00:11:58,230 --> 00:12:01,200 However, it does have some differences. 213 00:12:01,200 --> 00:12:04,820 One of which being, if you notice during our little lab 214 00:12:04,820 --> 00:12:08,150 demonstration here, we made a change to the priority 215 00:12:08,150 --> 00:12:13,830 on router 1, and it immediately took over as the DIS. 216 00:12:13,830 --> 00:12:17,180 So, clearly, it's a preemptive process. 217 00:12:17,180 --> 00:12:18,950 Then, of course, we took a look at what 218 00:12:18,950 --> 00:12:20,870 this looks like on the wire, and we 219 00:12:20,870 --> 00:12:23,900 can see how all of the routers on that segment 220 00:12:23,900 --> 00:12:26,880 agree who the DIS is. 221 00:12:26,880 --> 00:12:29,090 I hope this has been informative for you. 222 00:12:29,090 --> 00:12:32,170 And I'd like to thank you for viewing. 223 00:12:32,170 --> 00:12:35,000