1 00:00:00,000 --> 00:00:03,944 [AUDIO LOGO] 2 00:00:03,944 --> 00:00:07,890 3 00:00:07,890 --> 00:00:10,830 So now we've configured our routing protocol, 4 00:00:10,830 --> 00:00:13,230 we've configured our prefix SIDs, 5 00:00:13,230 --> 00:00:16,230 and we've configured our devices to prefer 6 00:00:16,230 --> 00:00:20,460 segment routing over using the traditional LDP labels. 7 00:00:20,460 --> 00:00:23,580 So at this point, since we've verified 8 00:00:23,580 --> 00:00:27,450 that we have full reachability just with segment routing, 9 00:00:27,450 --> 00:00:30,520 well, we should no longer need LDP. 10 00:00:30,520 --> 00:00:33,210 So the next step, it would make logical sense 11 00:00:33,210 --> 00:00:36,690 to just turn off LDP in our migration 12 00:00:36,690 --> 00:00:38,290 over to segment routing. 13 00:00:38,290 --> 00:00:40,780 So that's what we're going to be doing in this video. 14 00:00:40,780 --> 00:00:43,200 Now, of course, once we turn it off, 15 00:00:43,200 --> 00:00:45,870 we will still want to verify that everything is still 16 00:00:45,870 --> 00:00:48,370 functional, and that we are, of course, 17 00:00:48,370 --> 00:00:50,400 still using segment routing, which there's 18 00:00:50,400 --> 00:00:51,630 no reason we shouldn't be. 19 00:00:51,630 --> 00:00:53,610 But we always want to verify when 20 00:00:53,610 --> 00:00:56,440 we're turning off or disabling a feature. 21 00:00:56,440 --> 00:00:58,560 So we'll bring up the topology just 22 00:00:58,560 --> 00:01:00,600 as a reminder of how everything's configured. 23 00:01:00,600 --> 00:01:03,000 There's really not much to see this time. 24 00:01:03,000 --> 00:01:05,462 But we'll take a look at it just for your reference. 25 00:01:05,462 --> 00:01:07,170 And then we'll jump into the command line 26 00:01:07,170 --> 00:01:09,265 and we'll turn off LDP. 27 00:01:09,265 --> 00:01:12,100 28 00:01:12,100 --> 00:01:15,390 So still on MPLS topology 1. 29 00:01:15,390 --> 00:01:20,160 What we're going to be doing now is disabling LDP 30 00:01:20,160 --> 00:01:23,170 on all of the devices in the core. 31 00:01:23,170 --> 00:01:28,440 So this is going to be routers 1, 2, 3, 4, and 5. 32 00:01:28,440 --> 00:01:31,710 Once this is disabled, we'll verify that we still 33 00:01:31,710 --> 00:01:33,010 have reachability. 34 00:01:33,010 --> 00:01:38,370 So we'll check reachability from router 6 over to router 5, 35 00:01:38,370 --> 00:01:42,720 and from router 8 to router 1 just 36 00:01:42,720 --> 00:01:47,710 to make sure everything is still reachable once we turn off LDP. 37 00:01:47,710 --> 00:01:52,410 So let's jump on to the command line and do just that. 38 00:01:52,410 --> 00:01:54,350 So again we'll start off with that trace 39 00:01:54,350 --> 00:01:56,360 to router 5's loopback. 40 00:01:56,360 --> 00:01:59,570 And there are, of course, a few things we're looking for here. 41 00:01:59,570 --> 00:02:02,540 First is that, of course, it's working 42 00:02:02,540 --> 00:02:04,650 and we have connectivity. 43 00:02:04,650 --> 00:02:07,850 The second is if we look at the second hop, 44 00:02:07,850 --> 00:02:11,850 we see that we are doing MPLS label switching. 45 00:02:11,850 --> 00:02:15,050 So we're not just routing traffic without a label. 46 00:02:15,050 --> 00:02:18,110 And finally, that label that we're using 47 00:02:18,110 --> 00:02:20,250 is the segment routing label. 48 00:02:20,250 --> 00:02:22,760 So this is exactly what we want this to look 49 00:02:22,760 --> 00:02:26,130 like after we disable LDP. 50 00:02:26,130 --> 00:02:29,360 So let's disable LDP and make sure we still 51 00:02:29,360 --> 00:02:30,830 have reachability. 52 00:02:30,830 --> 00:02:35,310 Let's go over to router 1, we'll go into configuration mode. 53 00:02:35,310 --> 00:02:38,720 We can simply type no MPLS LDP. 54 00:02:38,720 --> 00:02:40,460 And say commit. 55 00:02:40,460 --> 00:02:46,040 That's all it takes to turn off MPLS LDP on IOS XR. 56 00:02:46,040 --> 00:02:51,920 So let's go ahead and do this on routers 2, 3, and 4 as well. 57 00:02:51,920 --> 00:03:02,670 So that takes care of router 2, router 3, and router 4. 58 00:03:02,670 --> 00:03:06,010 As usual, IOS XE is a little bit different. 59 00:03:06,010 --> 00:03:08,280 So let's go take a look at router 5. 60 00:03:08,280 --> 00:03:10,950 As we can see here, LDP neighborships 61 00:03:10,950 --> 00:03:12,700 are already going down. 62 00:03:12,700 --> 00:03:15,090 But let's go ahead and just turn it off here on router 5 63 00:03:15,090 --> 00:03:15,840 as well. 64 00:03:15,840 --> 00:03:18,550 To do this, we go into our interfaces. 65 00:03:18,550 --> 00:03:21,930 So in this case, it's interface gigabit 1.3. 66 00:03:21,930 --> 00:03:24,960 We say no MPLS IP. 67 00:03:24,960 --> 00:03:28,620 We do the same thing for gigabit 1.4. 68 00:03:28,620 --> 00:03:31,090 And we can exit configuration. 69 00:03:31,090 --> 00:03:33,660 So let's go ahead and do some verification. 70 00:03:33,660 --> 00:03:37,260 Let's start with a show MPLS forwarding table. 71 00:03:37,260 --> 00:03:40,470 Notice that the only labels left here 72 00:03:40,470 --> 00:03:44,080 are the adjacency labels which are, of course, 73 00:03:44,080 --> 00:03:48,270 still being pulled out of the dynamic pool and the segment 74 00:03:48,270 --> 00:03:51,900 routing labels for the prefix SIDs. 75 00:03:51,900 --> 00:03:54,610 All the other labels are gone. 76 00:03:54,610 --> 00:03:58,050 If we do a show mpls ldp binding, 77 00:03:58,050 --> 00:04:02,180 we're told that TIB is not enabled. 78 00:04:02,180 --> 00:04:05,050 Now that actually means tag information base 79 00:04:05,050 --> 00:04:07,900 because Cisco used to call this tag switching. 80 00:04:07,900 --> 00:04:10,480 But nonetheless essentially what it's telling us 81 00:04:10,480 --> 00:04:13,060 is we're asking to see LDP bindings, 82 00:04:13,060 --> 00:04:15,830 and that protocol is not even enabled. 83 00:04:15,830 --> 00:04:19,690 However, if we were to say show isis database, 84 00:04:19,690 --> 00:04:23,330 we'll ask for verbose and we'll ask for this router. 85 00:04:23,330 --> 00:04:27,220 So router 5.00.00. 86 00:04:27,220 --> 00:04:33,650 What we see here is that for our loopback address 10.5.5.5/32. 87 00:04:33,650 --> 00:04:37,180 we are, in fact, still creating a prefix SID, 88 00:04:37,180 --> 00:04:40,720 and that means this is being sent to the other routers. 89 00:04:40,720 --> 00:04:43,630 Also note that this has the n flag on it 90 00:04:43,630 --> 00:04:48,080 as well, indicating that this is also a node set. 91 00:04:48,080 --> 00:04:50,410 We could also look at this from the perspective 92 00:04:50,410 --> 00:04:53,170 of looking at all of the SIDs that we have in our database. 93 00:04:53,170 --> 00:04:55,540 We could just say include SID. 94 00:04:55,540 --> 00:04:58,690 And here we see the different SID values that we're actually 95 00:04:58,690 --> 00:05:00,400 getting from all of the different routers 96 00:05:00,400 --> 00:05:02,030 in our environment. 97 00:05:02,030 --> 00:05:04,720 So let's go over and do a little bit of verification on router 1 98 00:05:04,720 --> 00:05:05,900 as well. 99 00:05:05,900 --> 00:05:08,590 So we can do this by looking at some of the same commands. 100 00:05:08,590 --> 00:05:12,100 We'll start with our show mpls forwarding table. 101 00:05:12,100 --> 00:05:16,810 Once again, we see nothing but prefix and adjacency SIDs. 102 00:05:16,810 --> 00:05:20,620 So this is clearly using just segment routing. 103 00:05:20,620 --> 00:05:23,680 If we do our show mpls ldp binding, 104 00:05:23,680 --> 00:05:25,750 we can just say it doesn't necessarily 105 00:05:25,750 --> 00:05:28,720 tell us that LDP is not enabled, but it definitely 106 00:05:28,720 --> 00:05:30,850 has zero entries. 107 00:05:30,850 --> 00:05:35,650 If we do a show mpls ldp neighbor, we have no neighbors. 108 00:05:35,650 --> 00:05:39,680 If we do our show mpls label table detail, 109 00:05:39,680 --> 00:05:42,760 we see that all of the labels that are currently in use 110 00:05:42,760 --> 00:05:47,140 are either part of the SRGB or they are adjacency 111 00:05:47,140 --> 00:05:49,940 SIDs for other devices. 112 00:05:49,940 --> 00:05:52,510 And finally, we could look at a show isis 113 00:05:52,510 --> 00:05:54,910 segment routing label table. 114 00:05:54,910 --> 00:05:57,310 And what we see here is simply that we're still 115 00:05:57,310 --> 00:06:01,660 learning all of the prefixes for our environment, which 116 00:06:01,660 --> 00:06:06,010 of course, is as expected because LDP wasn't carrying 117 00:06:06,010 --> 00:06:07,540 these labels anyway. 118 00:06:07,540 --> 00:06:10,720 So it just makes sense that this is all still working. 119 00:06:10,720 --> 00:06:14,530 The real question is, is the data plane and our packet 120 00:06:14,530 --> 00:06:16,750 forwarding still operational? 121 00:06:16,750 --> 00:06:18,970 So let's go back over to router 6 now 122 00:06:18,970 --> 00:06:23,830 that we've turned off LDP, and make sure that our trace still 123 00:06:23,830 --> 00:06:24,910 functions. 124 00:06:24,910 --> 00:06:28,960 As we see from this trace, this is still functioning exactly 125 00:06:28,960 --> 00:06:29,960 as it should. 126 00:06:29,960 --> 00:06:33,820 So turning off LDP has not affected the functionality 127 00:06:33,820 --> 00:06:36,940 of our environment in any way now that we're 128 00:06:36,940 --> 00:06:39,640 doing segment routing. 129 00:06:39,640 --> 00:06:44,490 So in this video, we saw that we can easily turn off LDP 130 00:06:44,490 --> 00:06:48,550 once our segment routing is fully up and operational. 131 00:06:48,550 --> 00:06:51,630 So there's no problem with packet forwarding. 132 00:06:51,630 --> 00:06:53,820 No problem with label distribution. 133 00:06:53,820 --> 00:06:55,620 Everything works fine. 134 00:06:55,620 --> 00:06:58,260 Really it just comes down to LDP is no longer 135 00:06:58,260 --> 00:07:01,060 required for segment routing. 136 00:07:01,060 --> 00:07:05,760 Now this whole time we've been doing this using ISIS 137 00:07:05,760 --> 00:07:07,680 as our IGP. 138 00:07:07,680 --> 00:07:09,930 But we really should take a look at what 139 00:07:09,930 --> 00:07:13,420 changes if we use OSPF instead. 140 00:07:13,420 --> 00:07:16,360 And that's exactly what we're going to do next. 141 00:07:16,360 --> 00:07:19,770 Until then, I hope this has been informative for you. 142 00:07:19,770 --> 00:07:22,910 And I'd like to thank you for viewing. 143 00:07:22,910 --> 00:07:27,000