Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,210 --> 00:00:04,510
In the section we're going to talk about h is R P protocol
2
00:00:07,060 --> 00:00:09,510
a first up redundancy protocol.
3
00:00:09,570 --> 00:00:16,050
F H R P is a computer networking protocol which is designed to predict the default gateway used on a
4
00:00:16,050 --> 00:00:22,740
summer work by allowing two or more others to provide backup for the address in the event of a failure
5
00:00:22,740 --> 00:00:30,000
of an active rather the backup brother will take over the address usually within a few seconds.
6
00:00:30,060 --> 00:00:37,410
In practice such protocols can also be used to protect other services operating on a single IP address
7
00:00:37,620 --> 00:00:39,480
not just Rather's
8
00:00:42,830 --> 00:00:49,910
hot standby rather protocol HSR AP is a running protocol that allows host computers on the Internet
9
00:00:49,910 --> 00:00:56,570
to use multiple roles that act as a single virtual rather maintaining the connectivity even if the first
10
00:00:56,570 --> 00:01:03,780
hop rather fails because other others are on standby and they're ready to go.
11
00:01:03,830 --> 00:01:12,520
Rachel IP and MAC addresses are shared between the two brothers and there is no load balancing and verified
12
00:01:12,650 --> 00:01:19,370
by the show stand by comment as you can see that in our figure we have two brothers and their rather
13
00:01:19,370 --> 00:01:33,810
one and rather two and please pay attention that I am using SRP to protect the default gateway for here
14
00:01:34,290 --> 00:01:39,400
and here if there is a problem in the brothers.
15
00:01:39,470 --> 00:01:45,680
This interface or if that rather fails completely.
16
00:01:45,760 --> 00:01:54,010
For example we can have an power problem or we can have a cable problem in the end interface connecting
17
00:01:54,010 --> 00:02:04,640
between switch and the rather if this rather is the active one the HSR IP protocol will switch the traffic
18
00:02:04,640 --> 00:02:06,960
to the standby rather.
19
00:02:07,910 --> 00:02:13,520
This is actually what HSR is doing but there is no load balancing.
20
00:02:13,520 --> 00:02:21,840
As I said for example if this one is the active rather rather one is the active further the traffic
21
00:02:21,840 --> 00:02:29,840
flows in that direction and there is no packet in here.
22
00:02:30,240 --> 00:02:36,990
When this guy fails the traffic is switched to this direction.
23
00:02:40,270 --> 00:02:44,200
And if I configure preemption on rather one
24
00:02:50,080 --> 00:02:57,580
for example let's say that I have fixed the power unit problem and if I configured preemption as well
25
00:02:58,150 --> 00:03:01,350
this rather will become the active Gateway again.
26
00:03:01,360 --> 00:03:04,920
And this guy will act as a standby
27
00:03:07,410 --> 00:03:15,280
so let's take a look how we select the active and the standby gateways in the HSR pit.
28
00:03:15,840 --> 00:03:23,310
As you can see that in the figure we have two others again and the rather with the highest IP address
29
00:03:23,310 --> 00:03:25,380
will be active by default.
30
00:03:25,530 --> 00:03:33,480
But the selection can be changed with the H S IP priority value the rather with the highest HSR P prior
31
00:03:33,480 --> 00:03:41,760
to Wally becomes active and default prior to value is one hundred the active and the standby rather
32
00:03:41,760 --> 00:03:47,670
send the help packets to the H SRP group multicast others in three seconds.
33
00:03:47,670 --> 00:03:54,890
If the hell a packet does not arrive in 10 seconds the standby rather becomes active.
34
00:03:54,960 --> 00:04:07,960
Okay let's say that this guy is active again and this guy is standby if I want to change the roles if
35
00:04:07,960 --> 00:04:23,740
I want to make this guy as an active I need to increase the price to only off this rather when I increase
36
00:04:23,740 --> 00:04:36,460
the prior to early this guy will be active and traffic will flow in this direction instead of this direction
37
00:04:37,240 --> 00:04:49,390
in HSR PD the active Gateway propagates this Michael risks and says that hey guys use this mac address
38
00:04:51,200 --> 00:05:03,550
Widget X X is the HSR p group identifier to reach the this IP address which is H S IP standby IP
39
00:05:06,650 --> 00:05:15,920
let's talk about the topology now we have a P.C. in here which has an IP address of 10 that more hundreds
40
00:05:17,470 --> 00:05:21,070
the gateway address of the P.C. is turned up 1.
41
00:05:21,100 --> 00:05:33,980
And please pay attention that that's the HSR P IP so I'm at I'm gonna attach this IP address to this
42
00:05:33,980 --> 00:05:41,720
interface of the rather one and I'm going to attach this IP address to this interface of rather too
43
00:05:42,050 --> 00:05:49,630
and I'm going to attach a standby IP for both of them and that's gonna be turned up 1.
44
00:05:49,760 --> 00:05:54,520
And I'm going to define the gateway as ten that one.
45
00:05:54,590 --> 00:06:01,930
So what do the thing about this for example why I'm not attaching the tender to as Gateway let's say
46
00:06:01,930 --> 00:06:12,950
that the gateways tend up to if the gate they will be turned up to I would follow this line to send
47
00:06:12,950 --> 00:06:23,090
the packets to wider network read but when this rather fails if this if there's a problem with the structure
48
00:06:23,090 --> 00:06:23,960
in the network
49
00:06:26,610 --> 00:06:28,950
because of the 10 that too will fail.
50
00:06:28,980 --> 00:06:39,810
Also I wouldn't go to why they're in network but if I configure this one whenever this rather fails
51
00:06:41,400 --> 00:06:51,590
rather to will be the active rather and take the traffic onto it and I'm going to reach the wider network
52
00:06:52,580 --> 00:06:55,600
again without any interruption.
53
00:06:55,630 --> 00:06:59,010
Let's take a look to the HSR preemption feature.
54
00:06:59,200 --> 00:07:06,400
If the active rather fails the standby rather is activated and it remains active even if the previous
55
00:07:06,610 --> 00:07:09,210
active Raptor is returned.
56
00:07:09,310 --> 00:07:14,760
Pre-emption process forces rather to a new age SRP selection
57
00:07:17,710 --> 00:07:20,790
and here are the states of the HSR brothers.
58
00:07:20,800 --> 00:07:25,880
We have six six states and the first state is initial.
59
00:07:25,960 --> 00:07:27,640
This is the beginning state.
60
00:07:27,700 --> 00:07:30,150
It indicates HSR SRP is not running.
61
00:07:30,160 --> 00:07:37,030
It happens when the configuration changed or the interface is first turned on in the lone state through
62
00:07:37,050 --> 00:07:38,250
other has not detriment.
63
00:07:38,290 --> 00:07:45,310
The virtual IP address and has not yet seen an authenticated hallow message from the active rather in
64
00:07:45,310 --> 00:07:53,470
the state the rather will still wait to hear from the active rather in the lizard state through other
65
00:07:53,470 --> 00:08:02,020
nodes both IP and make addresses of the virtual runner but it's not the active or standby in this big
66
00:08:02,020 --> 00:08:02,840
state.
67
00:08:02,870 --> 00:08:10,630
The rather sends periodic H.S. IP hellos and participates in the selection of active or standby rather
68
00:08:11,860 --> 00:08:18,640
in the standby state through other monitors how the packets from the active rather and it will take
69
00:08:18,640 --> 00:08:26,740
the active state when the current active rather fails and in the active state rather forward packets
70
00:08:26,740 --> 00:08:30,250
that are sent to the H IP group.
71
00:08:30,410 --> 00:08:30,930
The.
72
00:08:30,950 --> 00:08:34,030
Also sends periodic Hello message
73
00:08:36,930 --> 00:08:47,160
and here is the configuration of the HSR IP first I it to fix the IP addresses for my configuration
74
00:08:48,060 --> 00:08:50,580
the IPL this in here is
75
00:08:53,500 --> 00:09:02,620
turn it up to and here is 30 that three and my gateway s
76
00:09:06,400 --> 00:09:10,890
third it up 1 and my HSR IP is also
77
00:09:14,650 --> 00:09:23,550
what I do in the configuration as I'm going under the interface mode and I'm assigning the IP addresses
78
00:09:25,630 --> 00:09:40,650
at thirty two and 30 that 3 to the physical interfaces these are for here and for here then I'm going
79
00:09:40,650 --> 00:09:44,960
to attach the stand by IP by using standby.
80
00:09:46,260 --> 00:09:54,890
And standby group no and IP and the IP address okay.
81
00:09:55,050 --> 00:10:06,590
And then the same thing on rather two to I just have two different configurations for either one in
82
00:10:06,590 --> 00:10:12,220
here sent by one prior to one hundred and fifty.
83
00:10:12,230 --> 00:10:23,540
This line shows me that rather one is the active rather for this HSR P topology because of the default
84
00:10:23,570 --> 00:10:30,600
loli of the project is 100 if I choose the one hundred and fifty.
85
00:10:30,820 --> 00:10:39,510
This guy will be the active one and here as you can see that I types them by 1 pre-empt comment.
86
00:10:41,060 --> 00:10:45,710
Which means I have configured the pre-emption.
87
00:10:45,710 --> 00:10:48,860
For example if this rather fails
88
00:10:51,860 --> 00:11:02,350
this guy will be the active front but when this rather is back this guy will be standby again and rather
89
00:11:02,350 --> 00:11:12,440
one will be active because I configure the pre-emption to verify DHS IP configuration.
90
00:11:12,490 --> 00:11:21,500
I'm using the show standby command and I can see the group no state active virtual mac address and standby
91
00:11:21,550 --> 00:11:31,140
Rather's IP as well by typing this show standby by command I can use different gateways for different
92
00:11:31,140 --> 00:11:38,040
villains in HSR P2 and this is what multi Group H SRP is doing for me.
93
00:11:39,330 --> 00:11:54,350
For example for villain Sim and realign 20 I'm using this guy as primary and I'm using this guy as the
94
00:11:54,440 --> 00:11:58,300
secondary for villain to an end villain 10.
95
00:11:58,850 --> 00:12:08,650
Then I'm getting under the interface villain for example interface villain 10 I'm attaching a lower
96
00:12:08,650 --> 00:12:17,890
priority for v lantern and higher priority for villain 20 which means this is gonna be active for villain
97
00:12:18,160 --> 00:12:23,380
to any and this is gonna be in Sam by mode for the villain.
98
00:12:23,560 --> 00:12:23,890
10
99
00:12:28,490 --> 00:12:36,060
SRP has another great feature that is known as HSR interface tracking.
100
00:12:36,680 --> 00:12:45,580
As I told you in the first slide HSR P always is responsible for protecting the default gateway these
101
00:12:45,580 --> 00:12:58,690
interfaces but when I try to connect to Internet I have also this interfaces as well.
102
00:12:59,070 --> 00:13:11,670
So what HSR P is doing with interface tracking HSR P is watching that if this interface is up or not
103
00:13:13,500 --> 00:13:16,550
is the interface fails for example.
104
00:13:16,620 --> 00:13:27,090
If serial 0 0 interface fails well the HSR is doing.
105
00:13:28,450 --> 00:13:37,230
This is Dick demanding the private label for either one and rather B is becoming the active brother.
106
00:13:37,260 --> 00:13:44,710
So I'm not having an interruption so traffic is flowing in this direction
107
00:13:49,460 --> 00:13:54,120
so another thing that SRP can do is object tracking.
108
00:13:54,200 --> 00:14:03,890
For example let's say that I have no problem in this in this interface to and everything is OK in my
109
00:14:03,890 --> 00:14:05,330
local area network.
110
00:14:05,360 --> 00:14:07,220
Here is my local area network.
111
00:14:07,280 --> 00:14:14,950
My brother is working fine and mostly there is no problem in this interface or this interface.
112
00:14:14,960 --> 00:14:20,300
Everything is OK but there may be a problem on the
113
00:14:24,120 --> 00:14:34,820
ISP network maybe I have our central rudder in here that I am collecting to traffic from the branch
114
00:14:34,820 --> 00:14:40,240
offices but HAARP object tracking does.
115
00:14:40,380 --> 00:14:51,250
I can ping here this interface of my HQ rather and if pink fails to the HQ rather
116
00:14:54,490 --> 00:15:03,640
I can change the traffic's pattern again and maybe I can use another ISP and another central rather
117
00:15:03,730 --> 00:15:12,330
and so that my traffic won't interrupt here's the object traffic configuration as well.
118
00:15:13,950 --> 00:15:25,160
I'm defending an IP solely and I'm trying to pin this IP address as you can see that I have a local
119
00:15:25,160 --> 00:15:29,590
area network switch and I rather went and a rather two and on the other side.
120
00:15:29,600 --> 00:15:34,990
I have a core rather which has an IP address of somewhat
121
00:15:38,610 --> 00:15:48,520
then I'm defining it for a frequency which means that I'm gonna ping here each 5 seconds then I'm defining
122
00:15:48,970 --> 00:15:52,910
the study of the finished time of the HSR.
123
00:15:53,260 --> 00:15:58,870
I'm sorry IP silly then I'm tracking this IP SLA
124
00:16:02,890 --> 00:16:07,710
at the end whenever there is a problem I'm going to Dickerman.
125
00:16:09,090 --> 00:16:14,820
The pride truly and the other rather will switch as a active
126
00:16:19,730 --> 00:16:27,920
HS IP pro as the following two types of authentication and their plaintext and they and the five.
127
00:16:27,920 --> 00:16:34,850
If you want to configure and the five you can use the standby group authentication and the five key
128
00:16:34,850 --> 00:16:43,060
string and the key string number and this strength the group number is arbitrary you can choose anything
129
00:16:43,070 --> 00:16:51,620
that you up if you want to configure it plaintext you can use them by for example 1 authentication and
130
00:16:51,710 --> 00:17:01,410
you can use the string that you want all rather is in a HSR pick group send help packets by default
131
00:17:01,470 --> 00:17:06,770
the helo timer is set to 3 seconds and that timer is set to 10 seconds.
132
00:17:06,930 --> 00:17:13,650
It means that a helo packet is sent between the HSR please stand by group devices every two seconds
133
00:17:13,980 --> 00:17:20,760
and the stand by the W becomes active in a helo packet has not been set for 10 seconds.
134
00:17:20,850 --> 00:17:29,820
If you want to modify the helo and hold on time you can use standby standby group number timers and
135
00:17:29,910 --> 00:17:35,260
helo time or hold time command.
136
00:17:35,320 --> 00:17:41,200
There are two versions of the H SRP and their version one and the version to version 1 is the default
137
00:17:41,200 --> 00:17:49,900
version of the protocol H is IP version 2 allows group numbers of up to 4000 and 9 is 6 thus allowing
138
00:17:49,900 --> 00:17:53,170
you to use villain number as the group number.
139
00:17:53,260 --> 00:17:59,200
Although as in an HSR IP group must have the same version configured otherwise dialup messages are not
140
00:17:59,510 --> 00:18:00,290
unders to.
15835
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.
Afrikaans
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bengali
Bosnian
Bulgarian
Catalan
Cebuano
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Finnish
French
Frisian
Galician
Georgian
German
Greek
Gujarati
Haitian Creole
Hawaiian
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Kazakh
Khmer
Korean
Kurdish (Kurmanji)
Kyrgyz
Lao
Latvian
Lithuanian
Luxembourgish
Macedonian
Malagasy
Malay
Maltese
Maori
Mongolian
Myanmar (Burmese)
Nepali
Norwegian
Pashto
Polish
Romanian
Russian
Samoan
Serbian
Sesotho
Shona
Sinhala
Slovak
Slovenian
Somali
Spanish
Swahili
Swedish
Tajik
Thai
Turkish
Ukrainian
Urdu
Uzbek
Vietnamese
