WEBVTT 00:00:00.000 --> 00:00:03.500 align:middle line:90% 00:00:03.500 --> 00:00:07.000 align:middle line:90% [AUDIO LOGO] 00:00:07.000 --> 00:00:10.000 align:middle line:90% 00:00:10.000 --> 00:00:12.400 align:middle line:90% Hello, and welcome to INE. 00:00:12.400 --> 00:00:15.070 align:middle line:84% Today in this video, we will look at section 2, dial plan, 00:00:15.070 --> 00:00:17.660 align:middle line:90% basically task 2.2. 00:00:17.660 --> 00:00:19.720 align:middle line:84% Now here in this task it says INE 00:00:19.720 --> 00:00:22.270 align:middle line:84% has decided to provide cube redundancy 00:00:22.270 --> 00:00:25.300 align:middle line:84% for inbound or outbound SIP calls. 00:00:25.300 --> 00:00:28.240 align:middle line:84% Provision this request as per the following requirements. 00:00:28.240 --> 00:00:31.930 align:middle line:84% Configure R1 and R2 to provide application redundancy 00:00:31.930 --> 00:00:33.520 align:middle line:90% for voice services. 00:00:33.520 --> 00:00:37.300 align:middle line:84% Use interface gig 3 on each router 00:00:37.300 --> 00:00:40.810 align:middle line:84% as the failover interface to exchange keepalive and state 00:00:40.810 --> 00:00:44.560 align:middle line:84% data between the active and the standby device. 00:00:44.560 --> 00:00:51.010 align:middle line:84% Use the subnet or the network 192.168.1.1/24 on R1 00:00:51.010 --> 00:00:55.420 align:middle line:90% and 192.168.1.2/24 on R2. 00:00:55.420 --> 00:00:59.170 align:middle line:84% Under normal operations, R1 should be the active node, 00:00:59.170 --> 00:01:01.420 align:middle line:90% and R2 should be the standby. 00:01:01.420 --> 00:01:05.830 align:middle line:84% You must use group ID 1 as your redundant group ID. 00:01:05.830 --> 00:01:08.440 align:middle line:84% And the active node will use the virtual IP 00:01:08.440 --> 00:01:20.230 align:middle line:84% address as 11.102.64.150 for gig 1 and 157.26.1.150 for gig 2. 00:01:20.230 --> 00:01:23.230 align:middle line:84% So let's quickly provide this application redundancy. 00:01:23.230 --> 00:01:26.170 align:middle line:84% Now if you look at the topology diagram here, 00:01:26.170 --> 00:01:27.820 align:middle line:90% I have R1 and R2 here. 00:01:27.820 --> 00:01:31.180 align:middle line:84% They both are gateway routers, voice-enabled gateway routers, 00:01:31.180 --> 00:01:32.920 align:middle line:84% but they are not-- at this point of time, 00:01:32.920 --> 00:01:35.960 align:middle line:84% they are not really providing any application redundancy, 00:01:35.960 --> 00:01:37.840 align:middle line:84% which means, let's say, if the call manager, 00:01:37.840 --> 00:01:41.980 align:middle line:84% if the HQ call manager uses R1 as the SIP gateway 00:01:41.980 --> 00:01:45.610 align:middle line:84% and if R1 goes down, all calls are going to be dropped. 00:01:45.610 --> 00:01:49.360 align:middle line:84% And then he would have to switch over to R2. 00:01:49.360 --> 00:01:52.330 align:middle line:84% With you using application-- with you doing application 00:01:52.330 --> 00:01:54.880 align:middle line:84% redundancy, your calls are not going 00:01:54.880 --> 00:01:57.520 align:middle line:84% to be dropped because they are-- because both the routers are 00:01:57.520 --> 00:02:00.220 align:middle line:84% going to act as an active standby device. 00:02:00.220 --> 00:02:04.090 align:middle line:84% And all your control plane and your data plane perspective, 00:02:04.090 --> 00:02:06.100 align:middle line:84% all your voice data is going to be 00:02:06.100 --> 00:02:10.030 align:middle line:84% replicated between the active and the standby device. 00:02:10.030 --> 00:02:13.260 align:middle line:84% So let's quickly provide this application redundancy. 00:02:13.260 --> 00:02:17.160 align:middle line:84% See, even if I go to my HQ cluster, my call manager, 00:02:17.160 --> 00:02:21.300 align:middle line:84% and I create two SIP Trunks, one to R1 and one to R2, 00:02:21.300 --> 00:02:24.870 align:middle line:84% if I'm using R1 as the primary exit or the primary voice 00:02:24.870 --> 00:02:28.680 align:middle line:84% gateway, then if R1 fails, that call information 00:02:28.680 --> 00:02:30.760 align:middle line:84% is not going to be transferred to R2. 00:02:30.760 --> 00:02:33.120 align:middle line:84% That's where the application redundancy comes in, 00:02:33.120 --> 00:02:36.460 align:middle line:84% where R1 and R2 are going to be in sync with each other 00:02:36.460 --> 00:02:40.410 align:middle line:84% so that even if one of the gateway fails, 00:02:40.410 --> 00:02:43.060 align:middle line:90% you basically don't get dropped. 00:02:43.060 --> 00:02:46.150 align:middle line:84% So let's quickly go and configure this. 00:02:46.150 --> 00:02:49.680 align:middle line:90% So as you can see here, on R1-- 00:02:49.680 --> 00:02:52.480 align:middle line:90% let's in fact access R1 first. 00:02:52.480 --> 00:02:53.520 align:middle line:90% So we have R1 here. 00:02:53.520 --> 00:02:54.880 align:middle line:90% We have R2 here. 00:02:54.880 --> 00:02:59.280 align:middle line:90% So on R1-- let's go to R1. 00:02:59.280 --> 00:03:04.090 align:middle line:84% On R1, if I do a show ip interface brief, 00:03:04.090 --> 00:03:07.590 align:middle line:84% you would see that I have three interfaces, gig 1, gig 2, 00:03:07.590 --> 00:03:09.180 align:middle line:90% and gig 3. 00:03:09.180 --> 00:03:12.240 align:middle line:84% Gig 3 is going to be used for my redundancy, 00:03:12.240 --> 00:03:16.500 align:middle line:84% for my control plane connection between the two voice gateways. 00:03:16.500 --> 00:03:20.040 align:middle line:84% And gig 1 is the LAN side going towards the switch. 00:03:20.040 --> 00:03:23.140 align:middle line:84% Gig 2 is the WAN side going towards the PSTN. 00:03:23.140 --> 00:03:26.200 align:middle line:84% So let's quickly go and achieve this. 00:03:26.200 --> 00:03:29.220 align:middle line:84% Now, for achieving this, the first thing that we would do 00:03:29.220 --> 00:03:32.710 align:middle line:84% is create a track object for each of my interfaces, 00:03:32.710 --> 00:03:35.520 align:middle line:84% which is LAN and the WAN, because we want to track 00:03:35.520 --> 00:03:37.200 align:middle line:90% that is the interface down? 00:03:37.200 --> 00:03:38.560 align:middle line:90% Or is the interface up? 00:03:38.560 --> 00:03:41.730 align:middle line:84% So I would create some track objects by saying track. 00:03:41.730 --> 00:03:43.500 align:middle line:90% Let's give-- let's say number 1. 00:03:43.500 --> 00:03:44.920 align:middle line:90% And what do we want to track? 00:03:44.920 --> 00:03:47.580 align:middle line:84% We want to track gig 1 interface. 00:03:47.580 --> 00:03:50.340 align:middle line:84% And we want to track the line protocol. 00:03:50.340 --> 00:03:53.910 align:middle line:84% We will also track the interface, 00:03:53.910 --> 00:03:59.040 align:middle line:84% let's say, track 2 interface gig 2 for line protocol. 00:03:59.040 --> 00:04:01.140 align:middle line:84% So two track objects have created 00:04:01.140 --> 00:04:06.030 align:middle line:84% track 1, which tracks the line protocol of gig 1. 00:04:06.030 --> 00:04:09.000 align:middle line:84% I have track 2 that point-- that basically tracks 00:04:09.000 --> 00:04:11.370 align:middle line:90% the line protocol of gig 2. 00:04:11.370 --> 00:04:13.500 align:middle line:84% So gig 1 was the LAN side interface. 00:04:13.500 --> 00:04:16.029 align:middle line:84% Gig 2 was the WAN side interface. 00:04:16.029 --> 00:04:17.790 align:middle line:84% The next thing that I would do is 00:04:17.790 --> 00:04:20.220 align:middle line:84% do application redundancy, which is done with the command 00:04:20.220 --> 00:04:21.180 align:middle line:90% redundancy. 00:04:21.180 --> 00:04:22.079 align:middle line:90% Hit Enter. 00:04:22.079 --> 00:04:26.070 align:middle line:84% And then we would say application redundancy 00:04:26.070 --> 00:04:27.840 align:middle line:90% and say group 1. 00:04:27.840 --> 00:04:30.030 align:middle line:84% Because the question says we need to create group 1, 00:04:30.030 --> 00:04:31.710 align:middle line:90% I would say group 1. 00:04:31.710 --> 00:04:34.720 align:middle line:84% And inside group 1, I would give a name. 00:04:34.720 --> 00:04:37.680 align:middle line:84% Let's give a name to this application redundancy group. 00:04:37.680 --> 00:04:44.200 align:middle line:84% Maybe the name could be Box-to-Box. 00:04:44.200 --> 00:04:46.170 align:middle line:84% Now this application redundancy is also 00:04:46.170 --> 00:04:48.840 align:middle line:84% called as Box-to-Box redundancy, because we actually 00:04:48.840 --> 00:04:52.780 align:middle line:84% taking two voice gateways and syncing them with each other 00:04:52.780 --> 00:04:56.040 align:middle line:84% so that all voice data information is going 00:04:56.040 --> 00:04:57.730 align:middle line:90% to be replicated between them. 00:04:57.730 --> 00:04:58.900 align:middle line:90% So just give a name. 00:04:58.900 --> 00:05:01.240 align:middle line:90% Let's say name Box-to-Box. 00:05:01.240 --> 00:05:02.610 align:middle line:90% This could be any name. 00:05:02.610 --> 00:05:03.780 align:middle line:90% We would do a preempt. 00:05:03.780 --> 00:05:04.740 align:middle line:90% We need preempt. 00:05:04.740 --> 00:05:06.630 align:middle line:84% There is no preemption by default 00:05:06.630 --> 00:05:08.220 align:middle line:84% because the question states that we 00:05:08.220 --> 00:05:11.550 align:middle line:84% need R1 to be the primary gateway and R2 00:05:11.550 --> 00:05:12.570 align:middle line:90% to be the standby. 00:05:12.570 --> 00:05:15.060 align:middle line:84% If R1 fails, R2 would become the active, 00:05:15.060 --> 00:05:16.410 align:middle line:90% and there is no preemption. 00:05:16.410 --> 00:05:18.930 align:middle line:84% So if R1 comes back up, then R1 would not 00:05:18.930 --> 00:05:20.430 align:middle line:90% become the primary gateway. 00:05:20.430 --> 00:05:23.430 align:middle line:84% So we need preemption because preemption is not 00:05:23.430 --> 00:05:25.560 align:middle line:84% on by default. So let's do preempt. 00:05:25.560 --> 00:05:27.330 align:middle line:84% Next thing we will define which interface 00:05:27.330 --> 00:05:28.830 align:middle line:90% are we going to use for control. 00:05:28.830 --> 00:05:33.870 align:middle line:84% So control interface is going to be gig 3, 00:05:33.870 --> 00:05:39.870 align:middle line:84% and the protocol is going to be the route group protocol 00:05:39.870 --> 00:05:40.893 align:middle line:90% instance name. 00:05:40.893 --> 00:05:42.060 align:middle line:90% So which was our group name? 00:05:42.060 --> 00:05:45.270 align:middle line:90% Our group name was 1, so say 1. 00:05:45.270 --> 00:05:49.060 align:middle line:84% Data traffic is going to be also using the same interface. 00:05:49.060 --> 00:05:52.500 align:middle line:84% Now again, I could use a separate interface for data, 00:05:52.500 --> 00:05:54.060 align:middle line:90% or I could use the same one. 00:05:54.060 --> 00:05:55.480 align:middle line:90% I'm going to use the same one. 00:05:55.480 --> 00:06:01.920 align:middle line:84% So data is going to be gig 3 again. 00:06:01.920 --> 00:06:12.840 align:middle line:84% And then I would say track 1 shutdown, track 2 shutdown. 00:06:12.840 --> 00:06:14.250 align:middle line:90% Exit out. 00:06:14.250 --> 00:06:16.700 align:middle line:84% So if you look at the config that I did-- 00:06:16.700 --> 00:06:27.840 align:middle line:84% let's do a show run section redundancy, do show run, 00:06:27.840 --> 00:06:31.350 align:middle line:90% show run. 00:06:31.350 --> 00:06:35.280 align:middle line:84% If you look at the commands, I said redundancy, application 00:06:35.280 --> 00:06:36.180 align:middle line:90% redundancy. 00:06:36.180 --> 00:06:38.050 align:middle line:90% I gave a group number. 00:06:38.050 --> 00:06:40.320 align:middle line:84% So group was one as per the question. 00:06:40.320 --> 00:06:43.470 align:middle line:84% We gave a name to it named Box-to-Box. 00:06:43.470 --> 00:06:44.850 align:middle line:90% Preemption was enabled. 00:06:44.850 --> 00:06:48.000 align:middle line:84% Our control connection would be using the gig 3 interface as 00:06:48.000 --> 00:06:48.840 align:middle line:90% per the question. 00:06:48.840 --> 00:06:51.660 align:middle line:84% Our data would also be using the gig 3 interface. 00:06:51.660 --> 00:06:53.790 align:middle line:84% And we are now binding that track 00:06:53.790 --> 00:06:57.340 align:middle line:84% object that we created earlier, track 1 and track 2 here. 00:06:57.340 --> 00:07:02.100 align:middle line:84% So what this basically say is that if the line protocol 00:07:02.100 --> 00:07:03.690 align:middle line:90% is up, no problem. 00:07:03.690 --> 00:07:07.200 align:middle line:84% If the line protocol is down, your track object 00:07:07.200 --> 00:07:09.582 align:middle line:84% is going to be showing a shutdown. 00:07:09.582 --> 00:07:11.040 align:middle line:84% The next thing that I'm going to do 00:07:11.040 --> 00:07:15.360 align:middle line:84% is apply this redundancy that we created 00:07:15.360 --> 00:07:17.230 align:middle line:90% to the voice application. 00:07:17.230 --> 00:07:22.560 align:middle line:84% So that's going to be done by saying voice service voip. 00:07:22.560 --> 00:07:26.940 align:middle line:84% And here I would say no IP address trusted authenticate. 00:07:26.940 --> 00:07:28.840 align:middle line:84% Again, this is enabled by default, 00:07:28.840 --> 00:07:31.290 align:middle line:90% so I'm just disabling that. 00:07:31.290 --> 00:07:34.077 align:middle line:84% You should not do this from a production perspective. 00:07:34.077 --> 00:07:36.160 align:middle line:84% But then, yeah, I mean, this is a lab environment. 00:07:36.160 --> 00:07:40.110 align:middle line:84% So we can actually disable the trusted authenticate. 00:07:40.110 --> 00:07:43.740 align:middle line:84% And then we would say mode border-element, 00:07:43.740 --> 00:07:48.870 align:middle line:84% and license capacity would be, let's say, 500. 00:07:48.870 --> 00:07:51.150 align:middle line:84% It says I need to save this and reload the router 00:07:51.150 --> 00:07:52.920 align:middle line:84% for the configuration to be effective. 00:07:52.920 --> 00:07:55.110 align:middle line:84% We will do that later and then say 00:07:55.110 --> 00:07:59.640 align:middle line:84% allow connections SIP to SIP, and lastly say 00:07:59.640 --> 00:08:03.130 align:middle line:84% redundancy, the group number that we created, 00:08:03.130 --> 00:08:05.760 align:middle line:90% which was, I think, group 1. 00:08:05.760 --> 00:08:06.300 align:middle line:90% Hit Enter. 00:08:06.300 --> 00:08:10.560 align:middle line:90% 00:08:10.560 --> 00:08:12.180 align:middle line:84% The next thing that I would do is 00:08:12.180 --> 00:08:13.930 align:middle line:90% go to my physical interfaces. 00:08:13.930 --> 00:08:16.510 align:middle line:84% So I have two physical interfaces. 00:08:16.510 --> 00:08:18.398 align:middle line:84% If you look at my gig 1 interface, 00:08:18.398 --> 00:08:19.440 align:middle line:90% that's the LAN interface. 00:08:19.440 --> 00:08:20.920 align:middle line:90% It has an IP address. 00:08:20.920 --> 00:08:22.590 align:middle line:84% I would go to my physical interface 00:08:22.590 --> 00:08:30.330 align:middle line:84% and give the command redundancy question mark. 00:08:30.330 --> 00:08:33.960 align:middle line:84% I have the redundancy interface identifier. 00:08:33.960 --> 00:08:36.370 align:middle line:84% Now, every interface needs to have a unique identifier. 00:08:36.370 --> 00:08:40.270 align:middle line:90% So let's just give rii 1. 00:08:40.270 --> 00:08:49.390 align:middle line:84% And here I would say redundancy group 1, so redundancy group 1. 00:08:49.390 --> 00:08:52.960 align:middle line:84% And the IP address, the virtual IP address 00:08:52.960 --> 00:09:00.280 align:middle line:84% is going to be 11.102.64.150 and exclusive. 00:09:00.280 --> 00:09:02.620 align:middle line:84% Same thing I would do to my gig 2 interface, 00:09:02.620 --> 00:09:06.940 align:middle line:84% but I would say redundancy rii, which 00:09:06.940 --> 00:09:09.280 align:middle line:84% is redundancy interface identifier. 00:09:09.280 --> 00:09:16.300 align:middle line:84% Just give 2, and then say a redundancy group 1. 00:09:16.300 --> 00:09:23.380 align:middle line:84% IP address would be 157.26.1.150 exclusive. 00:09:23.380 --> 00:09:26.735 align:middle line:84% And if I look at my control interface, which is gig 3, 00:09:26.735 --> 00:09:28.360 align:middle line:84% there's nothing to be configured there. 00:09:28.360 --> 00:09:31.030 align:middle line:84% The only thing that I do there is just an IP address. 00:09:31.030 --> 00:09:33.560 align:middle line:84% It already has an IP address as per the question, 00:09:33.560 --> 00:09:35.180 align:middle line:84% so I don't really have to do anything. 00:09:35.180 --> 00:09:37.120 align:middle line:90% So what have I done? 00:09:37.120 --> 00:09:40.000 align:middle line:84% The first thing I did was I created two track objects, 00:09:40.000 --> 00:09:42.550 align:middle line:84% one track object that meant that tracks the line 00:09:42.550 --> 00:09:47.080 align:middle line:84% protocol for gig 1, which is my LAN side, one track object that 00:09:47.080 --> 00:09:49.930 align:middle line:84% basically tracks the line protocol for gig 2, which 00:09:49.930 --> 00:09:51.130 align:middle line:90% is my WAN side. 00:09:51.130 --> 00:09:53.680 align:middle line:90% Then I went to-- 00:09:53.680 --> 00:09:55.990 align:middle line:84% then I created the redundancy application. 00:09:55.990 --> 00:10:03.070 align:middle line:84% I enabled that with the command redundancy 00:10:03.070 --> 00:10:06.340 align:middle line:84% by giving the redundancy application, redundancy group 00:10:06.340 --> 00:10:09.220 align:middle line:84% 1; name, Box-to-Box; preemt, control interfaces, 00:10:09.220 --> 00:10:13.030 align:middle line:84% my gig 3 interface, and my data is also gig 3. 00:10:13.030 --> 00:10:16.090 align:middle line:84% And then I applied the track objects inside that. 00:10:16.090 --> 00:10:19.210 align:middle line:84% Then I went to my physical interface, which is my gig 1, 00:10:19.210 --> 00:10:20.500 align:middle line:90% which is my LAN side. 00:10:20.500 --> 00:10:24.250 align:middle line:84% I gave a redundancy identifier, which is 1. 00:10:24.250 --> 00:10:25.510 align:middle line:90% It has to be unique. 00:10:25.510 --> 00:10:28.990 align:middle line:84% And I applied the group number, which was group 1 here 00:10:28.990 --> 00:10:31.780 align:middle line:84% and gave a virtual IP address to this interface. 00:10:31.780 --> 00:10:34.210 align:middle line:84% Same thing for the WAN interface. 00:10:34.210 --> 00:10:36.910 align:middle line:84% I gave a virtual IP address to the WAN interface 00:10:36.910 --> 00:10:41.260 align:middle line:90% with a unique identifier. 00:10:41.260 --> 00:10:44.170 align:middle line:84% Exactly the same thing I would do on-- 00:10:44.170 --> 00:10:48.730 align:middle line:84% let's in fact reboot this router in the meanwhile. 00:10:48.730 --> 00:10:50.290 align:middle line:84% We would do exactly the same thing 00:10:50.290 --> 00:10:53.170 align:middle line:84% on the other interface, which is the-- 00:10:53.170 --> 00:10:56.500 align:middle line:84% other router, which is R2, where the first thing 00:10:56.500 --> 00:10:59.350 align:middle line:90% I would say track object 1. 00:10:59.350 --> 00:11:03.310 align:middle line:84% Interface would be gig 1 line protocol. 00:11:03.310 --> 00:11:05.620 align:middle line:84% Then I would say the second track 00:11:05.620 --> 00:11:18.770 align:middle line:84% object 2, track 2 interface gig 2 line protocol. 00:11:18.770 --> 00:11:22.700 align:middle line:90% Then I would say a redundancy. 00:11:22.700 --> 00:11:25.790 align:middle line:84% But I would say application redundancy. 00:11:25.790 --> 00:11:32.700 align:middle line:84% And my name after application redundancy 00:11:32.700 --> 00:11:36.420 align:middle line:90% I would say group 1, so group 1. 00:11:36.420 --> 00:11:38.610 align:middle line:84% So group should be same on both the routers. 00:11:38.610 --> 00:11:43.230 align:middle line:90% Name should be same Box-to-Box. 00:11:43.230 --> 00:11:48.050 align:middle line:90% And then I would say preempt. 00:11:48.050 --> 00:11:50.060 align:middle line:84% And because the default priority is 100, 00:11:50.060 --> 00:11:52.790 align:middle line:90% we want R1 to be the primary. 00:11:52.790 --> 00:11:55.940 align:middle line:84% I should go back to R1 and increase his priority 00:11:55.940 --> 00:12:01.100 align:middle line:84% to at least 101, or I could go to R2 and reduce the priority. 00:12:01.100 --> 00:12:03.110 align:middle line:84% Since I didn't configure R1 with the priority, 00:12:03.110 --> 00:12:09.140 align:middle line:84% I could go and here say priority 99, so basically less than 100. 00:12:09.140 --> 00:12:11.120 align:middle line:90% So R1 becomes active. 00:12:11.120 --> 00:12:13.580 align:middle line:84% The next thing that I would say, control interface 00:12:13.580 --> 00:12:19.820 align:middle line:84% is going to be gig 3, and protocol is your group number. 00:12:19.820 --> 00:12:30.730 align:middle line:84% Data is going to be gig 3, and track 1 shutdown, track 2 00:12:30.730 --> 00:12:31.600 align:middle line:90% shutdown. 00:12:31.600 --> 00:12:35.860 align:middle line:84% So what this actually does is that if your line 00:12:35.860 --> 00:12:37.390 align:middle line:90% protocol for your line-- 00:12:37.390 --> 00:12:40.600 align:middle line:84% for your LAN side or the WAN side goes down, 00:12:40.600 --> 00:12:42.865 align:middle line:90% it reduces the track. 00:12:42.865 --> 00:12:47.560 align:middle line:84% Track basically reduces the value by 10. 00:12:47.560 --> 00:12:51.130 align:middle line:84% So I'll in fact show you that when I do a show track. 00:12:51.130 --> 00:12:52.480 align:middle line:90% Let's exit out. 00:12:52.480 --> 00:12:56.530 align:middle line:84% Let's now go to voice service voip. 00:12:56.530 --> 00:13:00.340 align:middle line:84% Say no ip address trusted authenticate 00:13:00.340 --> 00:13:07.030 align:middle line:84% and allow connections sip to sip and mode 00:13:07.030 --> 00:13:21.190 align:middle line:84% border-element license capacity 500 and redundancy group 1. 00:13:21.190 --> 00:13:22.360 align:middle line:90% Exit out. 00:13:22.360 --> 00:13:25.060 align:middle line:84% Go to your physical interface, gig 1. 00:13:25.060 --> 00:13:31.090 align:middle line:84% I would give the same identifier here, rii 1 and same IP address 00:13:31.090 --> 00:13:37.060 align:middle line:90% here, redundancy group 1 IP 1-- 00:13:37.060 --> 00:13:44.350 align:middle line:90% 11.102.64.150 exclusive. 00:13:44.350 --> 00:13:48.880 align:middle line:84% And interface gig 2 would have the identifier as 2 00:13:48.880 --> 00:13:59.410 align:middle line:84% and the IP address as 157.26.1.150 exclusive. 00:13:59.410 --> 00:14:04.180 align:middle line:84% So now both R1 and R2, R1 has the IP address. 00:14:04.180 --> 00:14:07.270 align:middle line:84% Virtual IP address has 11.102.64.150. 00:14:07.270 --> 00:14:11.200 align:middle line:84% R2 also has the same IP, 11.102.64.150 on the LAN side. 00:14:11.200 --> 00:14:14.350 align:middle line:84% But because R1 has a higher priority, R1 becomes active. 00:14:14.350 --> 00:14:17.320 align:middle line:84% And on the WAN side, R1 has the virtual IP 00:14:17.320 --> 00:14:21.130 align:middle line:84% address as 157.26.1.150, and R2 also 00:14:21.130 --> 00:14:23.980 align:middle line:90% has the same IP 157.26.1.150. 00:14:23.980 --> 00:14:26.500 align:middle line:84% But because R2 has a higher priority, R2 become-- 00:14:26.500 --> 00:14:27.970 align:middle line:90% R1 becomes active. 00:14:27.970 --> 00:14:30.520 align:middle line:90% R1 has a higher priority. 00:14:30.520 --> 00:14:35.850 align:middle line:90% So let's go and check by-- 00:14:35.850 --> 00:14:42.330 align:middle line:84% let's do show redundancy, and let's do-- 00:14:42.330 --> 00:14:43.380 align:middle line:90% hit Enter. 00:14:43.380 --> 00:14:48.690 align:middle line:84% So this should show me that there are two routers. 00:14:48.690 --> 00:14:51.340 align:middle line:84% And let's do a show redundancy group. 00:14:51.340 --> 00:14:54.145 align:middle line:90% 00:14:54.145 --> 00:14:55.520 align:middle line:84% In fact, they're still coming up. 00:14:55.520 --> 00:15:01.410 align:middle line:84% So let's do show redundancy states. 00:15:01.410 --> 00:15:15.430 align:middle line:90% 00:15:15.430 --> 00:15:18.970 align:middle line:90% Let's do application group 1. 00:15:18.970 --> 00:15:22.480 align:middle line:90% 00:15:22.480 --> 00:15:24.440 align:middle line:90% Excuse me. 00:15:24.440 --> 00:15:28.450 align:middle line:84% So if I do a show redundancy application group 1, 00:15:28.450 --> 00:15:31.000 align:middle line:90% I see the name as Box-to-Box. 00:15:31.000 --> 00:15:36.580 align:middle line:90% And it shows active. 00:15:36.580 --> 00:15:41.430 align:middle line:84% Let's go and do application question mark. 00:15:41.430 --> 00:15:44.040 align:middle line:90% 00:15:44.040 --> 00:15:46.260 align:middle line:90% Hit Enter. 00:15:46.260 --> 00:15:50.860 align:middle line:84% Let's see what information we can get, group. 00:15:50.860 --> 00:15:53.760 align:middle line:84% So yeah, so we have-- if I do a group and hit Enter, 00:15:53.760 --> 00:15:55.310 align:middle line:84% it shows me that it's Box-to-Box. 00:15:55.310 --> 00:15:56.310 align:middle line:90% That's the name we gave. 00:15:56.310 --> 00:15:57.970 align:middle line:90% It is currently active. 00:15:57.970 --> 00:16:01.410 align:middle line:84% Let's go to R1 and do exactly the same thing. 00:16:01.410 --> 00:16:05.580 align:middle line:84% Show redundancy application group. 00:16:05.580 --> 00:16:07.350 align:middle line:90% It's right now in its state. 00:16:07.350 --> 00:16:10.860 align:middle line:84% It should come up, and R1 should become active. 00:16:10.860 --> 00:16:11.880 align:middle line:90% Let's give it some time. 00:16:11.880 --> 00:16:14.790 align:middle line:90% 00:16:14.790 --> 00:16:16.490 align:middle line:90% Now it's in standby state. 00:16:16.490 --> 00:16:19.400 align:middle line:84% It should go to standby and then move to active state 00:16:19.400 --> 00:16:21.065 align:middle line:84% because R1 has a higher priority. 00:16:21.065 --> 00:16:24.000 align:middle line:90% 00:16:24.000 --> 00:16:26.370 align:middle line:84% Because as you can see here, the switcher what happened, 00:16:26.370 --> 00:16:28.560 align:middle line:84% R1 became active because of preempt. 00:16:28.560 --> 00:16:32.050 align:middle line:84% There was a re-election and R1 became the active router. 00:16:32.050 --> 00:16:33.720 align:middle line:90% So if I look at-- 00:16:33.720 --> 00:16:40.360 align:middle line:84% let's say if I go back to my topology and go to my switch 00:16:40.360 --> 00:16:44.330 align:middle line:90% and do a ping to 1-- 00:16:44.330 --> 00:16:50.140 align:middle line:84% 11.102.64.150, who should respond back to me? 00:16:50.140 --> 00:16:51.025 align:middle line:90% It should be R1. 00:16:51.025 --> 00:16:57.940 align:middle line:84% So if I do not show arp and look at the 11.102.64.150, 00:16:57.940 --> 00:17:02.230 align:middle line:84% you see that the MAC address is 5000.0010. 00:17:02.230 --> 00:17:08.050 align:middle line:84% And if I look at show arp for 64.151, 00:17:08.050 --> 00:17:13.040 align:middle line:84% which is the actual IP address of R1, that is also the same. 00:17:13.040 --> 00:17:14.920 align:middle line:84% So because the MAC address is the same, 00:17:14.920 --> 00:17:18.579 align:middle line:84% we basically know that R1 is the active router. 00:17:18.579 --> 00:17:22.810 align:middle line:84% And if I look at 152, that's R2's physical IP address. 00:17:22.810 --> 00:17:26.150 align:middle line:84% That is a different MAC address, 11. 00:17:26.150 --> 00:17:28.990 align:middle line:84% So since R1's physical IP and his virtual IP 00:17:28.990 --> 00:17:31.720 align:middle line:84% has the same MAC address, we know R1 is the active router. 00:17:31.720 --> 00:17:37.930 align:middle line:84% But we can also go back to R1 and do a show application 00:17:37.930 --> 00:17:42.150 align:middle line:90% redundancy group 1. 00:17:42.150 --> 00:17:45.130 align:middle line:90% So we can see my role is active. 00:17:45.130 --> 00:17:45.720 align:middle line:90% So I'm on R1. 00:17:45.720 --> 00:17:51.420 align:middle line:84% R1 is active, and the peer, which is R2, he is standby. 00:17:51.420 --> 00:17:55.770 align:middle line:84% And if I go to R2 and do exactly the same thing, group 1, 00:17:55.770 --> 00:17:58.860 align:middle line:84% you would see my role is standby, 00:17:58.860 --> 00:18:02.530 align:middle line:84% and the remote peer is the active router. 00:18:02.530 --> 00:18:05.850 align:middle line:84% So now we have provided Box-to-Box redundancy 00:18:05.850 --> 00:18:08.020 align:middle line:90% or application redundancy. 00:18:08.020 --> 00:18:11.430 align:middle line:84% So all your call managers, whether it's 00:18:11.430 --> 00:18:15.360 align:middle line:84% the WAN side PSTN or the LAN side site B or HQ, 00:18:15.360 --> 00:18:18.390 align:middle line:84% they all would peer with the virtual IP address. 00:18:18.390 --> 00:18:20.560 align:middle line:84% They would not peer with the physical IP. 00:18:20.560 --> 00:18:25.590 align:middle line:84% So if I look at my LAN side IP, show run interface gig 1, 00:18:25.590 --> 00:18:26.640 align:middle line:90% I have two IPs. 00:18:26.640 --> 00:18:29.880 align:middle line:84% One is my physical IP, and one is my virtual IP. 00:18:29.880 --> 00:18:32.430 align:middle line:84% So you would not peer with the physical IP anymore. 00:18:32.430 --> 00:18:34.380 align:middle line:84% You would peer with the virtual IP. 00:18:34.380 --> 00:18:36.810 align:middle line:84% So whichever router is active, that's 00:18:36.810 --> 00:18:37.890 align:middle line:90% going to be your gateway. 00:18:37.890 --> 00:18:40.400 align:middle line:84% So because R1 is active, when call manager 00:18:40.400 --> 00:18:43.350 align:middle line:84% peers with the 150 IP address, which is the virtual IP 00:18:43.350 --> 00:18:47.230 align:middle line:84% address, R1 is going to service all calls, all your SIP calls. 00:18:47.230 --> 00:18:50.260 align:middle line:84% But if R1 goes down, R2 becomes the active router. 00:18:50.260 --> 00:18:52.020 align:middle line:84% So from the call manager's perspective, 00:18:52.020 --> 00:18:56.920 align:middle line:84% your information or your gateway hasn't really changed. 00:18:56.920 --> 00:19:00.220 align:middle line:84% It's still the same IP address, the same virtual IP address. 00:19:00.220 --> 00:19:03.510 align:middle line:84% So with this, we've basically provided Box-to-Box redundancy 00:19:03.510 --> 00:19:05.670 align:middle line:90% or application redundancy. 00:19:05.670 --> 00:19:07.560 align:middle line:84% I hope this video was informative for you, 00:19:07.560 --> 00:19:10.190 align:middle line:90% and thank you for watching. 00:19:10.190 --> 00:19:11.000 align:middle line:90%