XenTegra - IGEL Weekly

IGEL Weekly: How to Use Buddy Update to Update IGEL OS

May 11, 2022 XenTegra / Andy Whiteside Season 1 Episode 50
XenTegra - IGEL Weekly
IGEL Weekly: How to Use Buddy Update to Update IGEL OS
Show Notes Transcript

The idea behind Buddy Update is to allow remote IGEL OS endpoints to update from a local Buddy Update Server vs. all remote devices contacting the IGEL OS UMS to download the new IGEL OS version. This results in much less bandwidth usage across slower WAN links.

Presented by Sebastian Perusat, IGEL Community FELLOW.

In this video, Sebastien will teach you how to:

  • Introduction
  • Topology
  • Create the Buddy Master role
  • Update the Buddy Master
  • Create the Buddy Slave role
  • Debug the Slave
  • Additional important information

Host: Patrick Toner
Co-host: Sebastian Perusat

WEBVTT

1
00:00:03.570 --> 00:00:17.820
Patrick Toner: Everybody welcome to the INTEGRA I Joe weekly podcast this is episode 50 I am going to be your host today filling in for Andy whiteside my name is Patrick toner and I am joined by Sebastian parasite for my Joe said I doing.

2
00:00:18.539 --> 00:00:30.330
Sebastien Perusat: i'm doing quite well um I mean wanted to start some firework but not attempt to promote because yeah number 50 or something respect i'm happy that it's a Community one, thank you for that, thank you for having me then.

3
00:00:30.930 --> 00:00:43.500
Patrick Toner: I would be very impressed that you could do fireworks via the podcasts That would be an oppressive display there but uh yeah maybe we'll do you know get to 100 maybe we'll do a firework presentation, I think that would be a good a.

4
00:00:44.670 --> 00:01:01.440
Patrick Toner: good way to kick that one off, but uh yeah you know it's a tonight we're just talking about the weather it's Nice in a moderate where we both live, we had to do some conversions from Fahrenheit to Celsius so we can understand each other there but we're both about 70 degrees.

5
00:01:02.520 --> 00:01:06.240
Patrick Toner: Fahrenheit which is nice how's everything going to have everything.

6
00:01:07.470 --> 00:01:08.340
Patrick Toner: going over there.

7
00:01:08.940 --> 00:01:17.970
Sebastien Perusat: Oh i'm pretty good at the moment, I mean we have springtime also again in Germany but it's getting any in Germany, you always complain about the weather, so if it's too cold.

8
00:01:18.180 --> 00:01:20.250
Sebastien Perusat: it's too cold it's ready, you would have.

9
00:01:20.640 --> 00:01:30.090
Sebastien Perusat: want to get Masonic because my son, you want to get moraine so i'm not complaining, we have about 29 degrees at the moment, which is apparently about 85 Fahrenheit.

10
00:01:30.780 --> 00:01:35.190
Sebastien Perusat: And now it's pretty warm but it's definitely definitely more than Okay, I mean it kind of complain, we have.

11
00:01:35.820 --> 00:01:43.830
Sebastien Perusat: Workers over the in the garden club working for for it's either making a bit of noise, if you ask any whiteside we're really at the situation where i'm at the park is on my car.

12
00:01:44.340 --> 00:01:50.220
Sebastien Perusat: Because we are working in the House this period is done now, so we are covering the government, the moment so pretty happy about that.

13
00:01:50.970 --> 00:01:59.280
Patrick Toner: There you go they got it, the only thing to complain about this time of year is allergies, you know i'm just uh, but I just load up on Desertec and i'm good, no, no issues there.

14
00:02:00.090 --> 00:02:05.400
Patrick Toner: But anyway, so we're going to be talking about you know pretty interesting topic today, one that.

15
00:02:05.910 --> 00:02:12.120
Patrick Toner: is always you know i've had many discussions with lots of different customers on this topic and that's buddy update.

16
00:02:12.720 --> 00:02:17.100
Patrick Toner: So you know before just a little kind of background before I joined I gel.

17
00:02:17.700 --> 00:02:36.150
Patrick Toner: I worked in healthcare and one of the things that I managers SEM and they had a feature still have a feature called branch caching which essentially would allow for devices to kind of become little firmware repositories i'm pushing out windows updates and pushing out large applications.

18
00:02:37.500 --> 00:02:50.100
Patrick Toner: i'd be able to use certain devices they'd be able to basically download files from each other rather than every file every device going back home and downloading a large file from the data Center wherever your servers living.

19
00:02:51.090 --> 00:02:58.410
Patrick Toner: So when I drill terminology there's a very similar feature basically almost the same thing called buddy update and.

20
00:02:59.040 --> 00:03:09.570
Patrick Toner: It said said, did a great you know, Article a video on this feature so we're going to walk through that together talk about when you might want to use it, how to use it will kind of show the video.

21
00:03:10.890 --> 00:03:12.270
Patrick Toner: said anything to add for jump in.

22
00:03:13.440 --> 00:03:29.700
Sebastien Perusat: No it's a really perfect introduction already I would maybe just the one one small site that I would like to share with you guys the actual Alex ios 1107 110 firmware is now hitting not exactly but a little bit less than three gigabytes.

23
00:03:31.200 --> 00:03:40.620
Sebastien Perusat: that's an information, I would like to share because let's imagine that you have what you just mentioned, you have range officer and you have, I would say, maybe just 10 devices or what they're.

24
00:03:41.880 --> 00:03:52.050
Sebastien Perusat: In the standard approach, you would have to transfer 10 times three gigabytes a little bit less, but still approximately three do, but if you didn't change something on the features that.

25
00:03:53.130 --> 00:04:00.840
Sebastien Perusat: We cover today how to leverage that bandwidth we use it, and I mean, even if I cannot hear that term anymore, which is a Joe.

26
00:04:01.920 --> 00:04:05.400
Sebastien Perusat: will try to be the MID module on the firmware update procedure.

27
00:04:06.630 --> 00:04:13.350
Patrick Toner: yeah and it's a great point right that that the firmware it's kind of it's the blessing, and the curse of the agile already Program.

28
00:04:13.770 --> 00:04:16.470
Patrick Toner: Right there's so many great partnerships there's so many great.

29
00:04:16.860 --> 00:04:24.360
Patrick Toner: utilities being built into the agile operating system that's obviously the approach to date that's always been the approach right build everything into the os.

30
00:04:24.690 --> 00:04:32.400
Patrick Toner: may or may not be changing in the future, but I don't know if i'm at liberty to speculate on that, but at least for now, and the foreseeable future.

31
00:04:33.630 --> 00:04:41.430
Patrick Toner: That you know because there's more agents there's more integrations that used to be under two gigs now we're nearing the three gig mark.

32
00:04:42.150 --> 00:04:50.010
Patrick Toner: And so we want to make sure that you know if you're an agile admin or more potential agile i've been there you're you're considering you know I just for your company.

33
00:04:50.880 --> 00:05:00.780
Patrick Toner: This is a great feature that can help you to plan for this and to offload some of that overhead of the devices just downloading massive files and three gigs in size.

34
00:05:02.610 --> 00:05:04.680
Patrick Toner: So yeah so let's go ahead i'm going to share this thing out.

35
00:05:06.300 --> 00:05:13.830
Sebastien Perusat: Just during your you're showing process exactly right what you've just mentioned, I mean if you think about the agile was.

36
00:05:14.430 --> 00:05:24.120
Sebastien Perusat: A couple of years ago, where we had the only point we had three different versions of the specific software and tired of our agile as well citrix workspace APP and for my time citrix this year.

37
00:05:25.020 --> 00:05:36.720
Sebastien Perusat: Just because we said that specific citrix workspace that works better in specific behavior so we said we always spent three different version 34 and operating system.

38
00:05:37.890 --> 00:05:52.560
Sebastien Perusat: Now we have zoom media credits, now we have Cisco jvm planets now we have webex we have so much different components for working good in a specific combination, but not if you are using a newer version on that side, etc, etc, and that's aware that the point where we at the moment.

39
00:05:53.310 --> 00:06:03.780
Sebastien Perusat: We have to cover every use case in one firmware and just because Patrick mentioned it, we can speculate at the moment, but I can share that it might change in the future, our statement this way.

40
00:06:04.650 --> 00:06:08.760
Patrick Toner: Very good it's very, very a politician answer right there may change in the future.

41
00:06:10.350 --> 00:06:12.540
Patrick Toner: You know, so can you see my screen Okay, the agile community.

42
00:06:12.540 --> 00:06:21.870
Patrick Toner: Yes, very good so so yeah I mean let's kick it off i'm i'm going to kind of explain what the feature is i'm going to start playing it on mute the sound here so we're not.

43
00:06:22.830 --> 00:06:30.600
Patrick Toner: You know, getting anything but, but you know you're going to you're going to basically walk through here how to configure this well let's talk about.

44
00:06:31.710 --> 00:06:40.800
Patrick Toner: You know, some things that people might want to consider right, where is this a fit said well you know i'm thinking in my mind what, if I have multiple branches.

45
00:06:41.580 --> 00:06:54.450
Patrick Toner: would have some of them, you know, in the US there's some places, especially in rural America, where you know you might have locations in those areas, and you have very low bandwidth but what are some some of those you know they come to come to mind when you think about this feature.

46
00:06:55.770 --> 00:07:07.530
Sebastien Perusat: that's causes main goal of of the process that we leverage the benefit to us but also make it more and more performant for one one template pro obviously you can.

47
00:07:07.920 --> 00:07:20.940
Sebastien Perusat: As a CCM is doing it create a local mirror of your agile related firmware and the location so we're not covering right now and the end the video, but you can, if you would like user.

48
00:07:21.690 --> 00:07:32.100
Sebastien Perusat: In external http s s ftp s or somebody share to deliver the updates to your branch office if it's already a civil war there.

49
00:07:33.030 --> 00:07:44.250
Sebastien Perusat: But sometimes you don't have a server but they're all sometimes you haven't been able to administer that that server because it's another department or maybe another network branch so that's the reason why we said.

50
00:07:45.120 --> 00:07:56.400
Sebastien Perusat: It might be a great idea to have our an automatism somewhere in our operating system that says we don't want to push the update to 510 devices so 10.

51
00:07:57.090 --> 00:08:07.680
Sebastien Perusat: Much implicated by three gigabytes but really sending it out to maybe just one device and the older devices will get the update from the master one.

52
00:08:08.580 --> 00:08:22.620
Sebastien Perusat: that's where we are already speaking about the topology because if you think about the approach to deploy that 10 times you will use bandwidth it would make the opposite slower, you will also have the risks that if something is happening on the network side.

53
00:08:23.940 --> 00:08:31.800
Sebastien Perusat: I mean we're delivering already a lot of recovery procedures and usual gets the donor cannot be fulfilled the device will be functional.

54
00:08:32.730 --> 00:08:45.300
Sebastien Perusat: But we all know that if you're doing the updates, I mean the same on my side something would break just because you're on like you have this little rainy rainy cloud over your head and that's obviously most of my side.

55
00:08:46.410 --> 00:08:57.810
Sebastien Perusat: And the device is not recoverable or, on the other hand, you have users for working in the in the location and if you push the update what project management, they cannot work anymore, because they have no bandwidth left.

56
00:08:59.070 --> 00:09:05.640
Sebastien Perusat: And that's where the body update that's our name for the product for that feature is coming in.

57
00:09:06.780 --> 00:09:13.740
Sebastien Perusat: We are choosing one or n devices in the location that's a manual process that we're covering a second.

58
00:09:15.030 --> 00:09:25.770
Sebastien Perusat: update that device and then tell the author nine device have to take over the other, not from the US, not from a public https as ftp server anymore.

59
00:09:27.180 --> 00:09:28.140
Sebastien Perusat: But from the master.

60
00:09:29.460 --> 00:09:41.520
Sebastien Perusat: That taps on one hand, to keep the update amount that the data will just transferred quite low because it just transferred, maybe one time if you're just one master or five times you are five master.

61
00:09:42.150 --> 00:09:48.720
Sebastien Perusat: But then you can deploy to 200 300 device on site without having the need to change anything.

62
00:09:50.250 --> 00:09:58.830
Sebastien Perusat: that's what Patrick is showing in in the video side that's it topology about how to set the proper expectation.

63
00:09:59.550 --> 00:10:14.760
Sebastien Perusat: There was a small hint in the body updates topology, which is extremely important because that might be a question that come up from from you guys, can I choose something else, then ftp because that's what the live to production is showing.

64
00:10:15.990 --> 00:10:17.070
Sebastien Perusat: would call that in a second.

65
00:10:18.390 --> 00:10:18.870
Patrick Toner: So.

66
00:10:19.200 --> 00:10:22.200
Patrick Toner: Step just to just to just to kind of pause for a second right so.

67
00:10:22.470 --> 00:10:22.830
Sebastien Perusat: Please.

68
00:10:23.070 --> 00:10:32.220
Patrick Toner: You know just a real simple somebody somebody looking to dystonia that maybe not quite grasping you know the concept here let's say you have you know just just so.

69
00:10:32.700 --> 00:10:38.670
Patrick Toner: we're understand this correctly let's say you have a random branch in your company, you know it's out in the middle of nowhere.

70
00:10:39.180 --> 00:10:49.230
Patrick Toner: it's got really slow Internet connection not really no options to update to a very fast bandwidth and you know you want you have 100 devices there.

71
00:10:49.920 --> 00:11:06.930
Patrick Toner: So rather than 100 devices having to download three gigabytes from your us server only one device would have to download 100 or three gigabytes from my server and then the other 99 can download from the one body updates over on on Prem so I have that right.

72
00:11:07.860 --> 00:11:08.520
Sebastien Perusat: So it's a right.

73
00:11:09.330 --> 00:11:14.700
Patrick Toner: So so it's a very great feature, and I would say it's probably one of the more underused features.

74
00:11:15.210 --> 00:11:22.110
Patrick Toner: Out there, and maybe it's just because you know bandwidth is generally pretty good on on a lot of my customers, I talked to on their network.

75
00:11:22.710 --> 00:11:28.920
Patrick Toner: But you do have these these instances, and you know you talk to people where they just you know, especially a type of business where you have a lot of different.

76
00:11:30.090 --> 00:11:33.420
Patrick Toner: Customer facing branches, you know, maybe it's in banking maybe.

77
00:11:34.440 --> 00:11:39.930
Patrick Toner: Maybe you're you know in some sort of industry, where you have a lot of customer kiosks you know people checking out.

78
00:11:40.980 --> 00:11:45.120
Patrick Toner: You know if you have them more real estate, you have more buildings you own.

79
00:11:46.620 --> 00:11:58.950
Patrick Toner: more chances you're probably going to want to use this feature because you're you're probably going to have instances where you, you have sites with low bandwidth and you're going to do it for all of them are some of them, you might as well do it for all of them, would you agree set.

80
00:11:59.640 --> 00:12:06.690
Sebastien Perusat: up so okay nothing to be almost exact description of the general use case for that perfect.

81
00:12:07.530 --> 00:12:12.810
Patrick Toner: So i'll let you kind of go ahead so here's you, Ms and you're creating the profile so.

82
00:12:12.870 --> 00:12:13.200
Sebastien Perusat: Right.

83
00:12:13.470 --> 00:12:21.960
Sebastien Perusat: Through this and that's, by the way, something that I would recommend to really keep the order that i'm using for the video way that.

84
00:12:22.890 --> 00:12:37.470
Sebastien Perusat: We already covering the use case of a bit deeper so just saying that we have to cover a specific order in how to use the body, the body master so from the term itself, the body master of the device which will get updated by humans.

85
00:12:38.610 --> 00:12:47.250
Sebastien Perusat: And with a whole the update information for all the other client on the network, so we have to enable that feature first that's why i'm creating a profile.

86
00:12:47.760 --> 00:12:56.400
Sebastien Perusat: Where on the system update firmware update you have another feature which is called body update that's where you define.

87
00:12:56.820 --> 00:13:07.470
Sebastien Perusat: That this device would hold information, as you are, you have to enable the annual updates or first and then, if needed, you can also add a username and password what does that mean.

88
00:13:08.070 --> 00:13:19.080
Sebastien Perusat: It means that every client so in our pronunciation is called body slaves were asking for an update from the body master will have to fulfill a username and password to get them.

89
00:13:19.950 --> 00:13:29.940
Sebastien Perusat: If you don't enter something the standard approach is to use the anonymous approach that mean that there was no additional authentication needed.

90
00:13:31.710 --> 00:13:42.060
Sebastien Perusat: The additional thing that I would like to share with you is the Max the Max concurrent logins what does that mean you have 20 devices in the location.

91
00:13:42.870 --> 00:13:55.980
Sebastien Perusat: And you said, the devices should get the update on shut down, and you have a job which shut down the devices every night at eight o'clock they'll try the same time to download the update from your buddy monster.

92
00:13:57.540 --> 00:14:14.310
Sebastien Perusat: just keep in mind that a data transfer is still quite demanding on memory and basically if you are using ftp sometimes also the cpu so 20 devices don't use the same files, at the same moment 10 called the body master depending from the hardware to fail.

93
00:14:15.390 --> 00:14:29.850
Sebastien Perusat: And that's the point where i'm overstating don't use 10 or 20 devices from one buddy master you can limit the amount of devices which are taking over that feature, and I would say, an average i'm feeling pretty good about five to eight, to be honest that's an average but.

94
00:14:32.040 --> 00:14:39.420
Sebastien Perusat: Then what i'm coming in the video is the order and first assigning the body master role and then assigning an update.

95
00:14:40.440 --> 00:14:41.100
Sebastien Perusat: Why that.

96
00:14:42.480 --> 00:14:51.360
Sebastien Perusat: The device can only keep the information about the update if the body master road was assigned before starting.

97
00:14:53.010 --> 00:15:02.370
Sebastien Perusat: So that's the reason why I first create the profile first assigned it to the body master then assign the firmware update and then started the update process itself.

98
00:15:03.240 --> 00:15:12.630
Sebastien Perusat: that's, something which I would say, is the most common error that you are doing their first updating the device or just assigning the profile with the body monster.

99
00:15:13.080 --> 00:15:22.860
Sebastien Perusat: That never sent an update afterwards that mean that the ftp folder the ftp server which is holding the information is empty.

100
00:15:23.460 --> 00:15:35.820
Sebastien Perusat: Because it needs to get the update and then get updated to do that so even if it's the same form well, no matter if you had the 11 oh 718 and 10 on the device, and you want to update and you want to nervous about the master feature.

101
00:15:36.600 --> 00:15:43.380
Sebastien Perusat: no big deal that's on the profile offensive firmware and even if it's already some firmware does do that, but again.

102
00:15:44.490 --> 00:15:53.160
Patrick Toner: So, so what you're saying they're just so just so we're clear if let's say you you've identified which server you want to be your your buddy update server.

103
00:15:53.310 --> 00:15:54.060
Sebastien Perusat: into branch.

104
00:15:54.120 --> 00:16:09.510
Patrick Toner: or your location and it's already running the newest firmware you can't just assign a profile saying you're the buddy update, because once it becomes the buddy update server you actually have to push a firmware in order for it to store the firmware.

105
00:16:10.560 --> 00:16:12.630
Patrick Toner: That right so it's very important.

106
00:16:13.410 --> 00:16:15.750
Patrick Toner: In order you know and i've seen that as well right you kind of.

107
00:16:16.800 --> 00:16:28.890
Patrick Toner: You know and it's in logically you really may not think that through other way but it, but you know if you're sick Oh, this is updates her, but now you have to push the update to it, so that it's their rights to kind of step and you need to do in order.

108
00:16:29.730 --> 00:16:38.370
Sebastien Perusat: Absolutely so that's I mean I will cover the the debugging steps in the second but that's something that I cannot mention enough.

109
00:16:39.300 --> 00:16:44.340
Sebastien Perusat: Because it will stand fail and every time so even if you're thinking, then, about your update strategy.

110
00:16:44.850 --> 00:16:53.160
Sebastien Perusat: You have to think about which devices should get the update have too much time never forget that your body monster is a masterpiece in your configuration for the body for the body updates.

111
00:16:54.810 --> 00:17:06.840
Sebastien Perusat: know that we covered the body mass aside, we are not covering the body slave side so we're doing now exactly the same step as from everybody master but on the update sites on a system update firmware updates.

112
00:17:08.100 --> 00:17:12.060
Sebastien Perusat: Where you would usually enter your update Informations.

113
00:17:13.110 --> 00:17:25.170
Sebastien Perusat: You have to choose a specific protocol and that's what I told you at the beginning we're speaking of the ftp protocol, not because it's the only one available on agile as well, the only one available for.

114
00:17:25.680 --> 00:17:38.010
Sebastien Perusat: The update platform So even if https and ftp s O s ftp would be better, and no question, we already had the discussion, and we might expect a change in the near future.

115
00:17:38.460 --> 00:17:49.560
Sebastien Perusat: But for the moment, only ftp is allowed, and I know that a couple of our listeners are not able to use ftp because the security audit or security.

116
00:17:50.580 --> 00:17:51.600
Sebastien Perusat: Security issues.

117
00:17:52.710 --> 00:17:58.260
Sebastien Perusat: i'm I said at the moment that the only way to live with such kind of body slave behavior.

118
00:17:59.610 --> 00:18:09.570
Sebastien Perusat: I just can say, if you would like to have another level of security, I would definitely think of using http authentication I know it's an encrypted.

119
00:18:10.290 --> 00:18:18.450
Sebastien Perusat: But it's let's say the less non secure way to to deal with the updates and just remember that, even if your device.

120
00:18:19.440 --> 00:18:37.260
Sebastien Perusat: Is non secure from the ftp site, what would happen, I mean all our petitions assigned So even if someone would try to change the update fi themselves in good faith, we will cause would check the signature of as a petition, so in my opinion, is the risk is pretty limited.

121
00:18:38.430 --> 00:18:44.130
Patrick Toner: yeah it's a great point great point I mean it's you know it's not because of some of the other checks, you have in place.

122
00:18:44.820 --> 00:18:51.900
Patrick Toner: You know this is going to be more for functionality obviously you know if you if you're in a if you're in a situation that we were describing.

123
00:18:52.530 --> 00:18:56.640
Patrick Toner: You know, you need to get that firmware updates probably less secure to keep the device.

124
00:18:57.390 --> 00:19:01.980
Patrick Toner: The devices out of firmware compliance right, you know, keep them on an old old version, you have different.

125
00:19:02.460 --> 00:19:15.900
Patrick Toner: things to come out you have all these different applications where's the browser your sister squarespace APP that have security fixes and so you know it's kind of like one of those things, the risk of not doing it is higher than you know getting those devices updated.

126
00:19:17.400 --> 00:19:18.000
Sebastien Perusat: Exactly.

127
00:19:19.110 --> 00:19:26.610
Sebastien Perusat: So just we'll just do me a small fair but I could you go about 30 seconds back to the perfect setting.

128
00:19:28.320 --> 00:19:31.590
Sebastien Perusat: Perfect because we do wasn't a bit too fast for for my explanation.

129
00:19:32.490 --> 00:19:47.220
Sebastien Perusat: One extremely important setting in that window if the username password just discussed but also this small check box at the bottom of the profit, which is called automatic body detaching you could just pause for a second Patrick.

130
00:19:47.520 --> 00:20:03.900
Sebastien Perusat: you're just would like to to explain what happened there you're not obliged to set the body detection, but it's extremely hand way that I will go a step backwards on the topology and what I would consider if you're using the body update.

131
00:20:05.580 --> 00:20:19.860
Sebastien Perusat: The body master will stay there, in his network segment and we're starting ftp so which, from a security perspective already discussed it's not perfect, but it's yeah it's it's one approach.

132
00:20:21.330 --> 00:20:27.510
Sebastien Perusat: But at the same time you have your body slaves who could be an another network segment, or maybe an older Vila.

133
00:20:29.130 --> 00:20:43.380
Sebastien Perusat: Which is not meant to be used this way of explaining what I mean the bus live has to be in the same network segment the same virtual alarm, as the big monster.

134
00:20:44.280 --> 00:20:52.950
Sebastien Perusat: Now, you may ask why that because it doesn't make sense of 100 to be down in my medication, I would have to define one buddy master bedroom yes.

135
00:20:53.880 --> 00:21:07.020
Sebastien Perusat: The reason is let's imagine that you have are distributed lamb was npls I don't know if it's the same as us, but that's how it's virtual on or over DSL let's call it this way it's an extreme.

136
00:21:08.100 --> 00:21:16.980
Sebastien Perusat: Small explanation for some complex product, but you have different finance which can be one in Chicago the other one in New York.

137
00:21:17.910 --> 00:21:28.170
Sebastien Perusat: So the body slave was not a broadcast in the network, and we see Oh, have a body master that's the first one lancer but this one could be in New York and i'm in Chicago.

138
00:21:28.830 --> 00:21:36.810
Sebastien Perusat: that's reason why we said no, we always keep the request of the UDP broadcast that we are using for the automatic detection.

139
00:21:37.410 --> 00:21:50.550
Sebastien Perusat: In one specific land segments so let's imagine you're in 192 1681 dot zero it will just charge in that specific area, so if your body slavers and put a zero.

140
00:21:51.210 --> 00:22:04.500
Sebastien Perusat: It will not be able to find the auto body master it's not an error it's not a bug some couples, because we want to keep the buddy monster and the by the state and the same network occasion to avoid some bandwidth outage.

141
00:22:06.480 --> 00:22:12.450
Patrick Toner: yeah and I, you know to that point said I think it's worth mentioning right that this, this is not going to be.

142
00:22:14.160 --> 00:22:22.590
Patrick Toner: it's not it's not the right solution may be for everyone right, I mean there's there's gonna be some customers that are going to have that way I have all these V lands at every location.

143
00:22:23.100 --> 00:22:27.810
Patrick Toner: And you might say, okay well you know I mean the beauty of the agile is is there's there's a lot of flexibility in it.

144
00:22:28.470 --> 00:22:37.500
Patrick Toner: You can you know, for example, you know people who have who use agile cloud gateway you know they have to have firmware repositories that are external facing.

145
00:22:38.280 --> 00:22:48.450
Patrick Toner: In order to to pull that down so a lot of lot of customers, I talked to you they'll either use something like you know sit centric share file or Amazon or azure you know and they'll create a public.

146
00:22:49.260 --> 00:22:58.620
Patrick Toner: Facing repository that could use an ftp server whatever, and for that, for the customer you just described that maybe they needed they maybe we take that approach right maybe they have.

147
00:22:59.040 --> 00:23:13.860
Patrick Toner: You know, an actual s ftp server in place where all the V lands can hit it, but the built in functionality is really it's going to it's basically their number one the thin client is the is the update server right so.

148
00:23:14.190 --> 00:23:19.380
Patrick Toner: you're not talking about a server you're talking about a not not a robust device.

149
00:23:20.160 --> 00:23:31.890
Patrick Toner: You know so it's designed in a way, specific be land right all the devices that are within my proximity that can can can connect with me there the devices that are there, they can update it explain that correctly I think that's.

150
00:23:32.040 --> 00:23:34.320
Sebastien Perusat: This yep just perfect again it's.

151
00:23:34.590 --> 00:23:37.770
Sebastien Perusat: Exactly what it was meant for and what I was trying to expand my fingers.

152
00:23:38.790 --> 00:23:43.920
Patrick Toner: yeah so, so I think that's you know ultimately that's that's the thing right, I mean this is, this is a great feature.

153
00:23:44.850 --> 00:23:49.770
Patrick Toner: You know it, as long as you don't have an ultra complex network, I mean it's really it's a simple solution.

154
00:23:50.610 --> 00:23:59.760
Patrick Toner: it's young to your point, maybe not the most it's not a perfect solution for everybody, but you know if if you do have you know, in your different branches and your different locations.

155
00:24:00.750 --> 00:24:12.990
Patrick Toner: devices that are on the same subnet on the same V land they can throw on the same you know they can connect they they can communicate with each other, this is a great solution to limit your bandwidth, however.

156
00:24:13.020 --> 00:24:15.330
Patrick Toner: You got to have this checked here does automatic buddy infection.

157
00:24:16.320 --> 00:24:22.500
Sebastien Perusat: It just helps I mean obviously you can you can specify in southern name, whatever body master you like so.

158
00:24:23.160 --> 00:24:31.590
Sebastien Perusat: If you would have, in theory, two different villans in your location and the first one is where you buy the master it and second one ready by the states are.

159
00:24:32.550 --> 00:24:44.580
Sebastien Perusat: Even if the ultimate political is not working there because we didn't men to give them the solution like that you can still specify and seven at the IP address of your body master.

160
00:24:45.480 --> 00:24:55.440
Sebastien Perusat: It makes it less our job because that's imagine that you have a GPS, to the http as the GPS address is changing from the body master than you would have to adapt your profile.

161
00:24:56.130 --> 00:25:01.800
Sebastien Perusat: But hey if you do a reservation and then add the IP address of the host name, maybe in the server name.

162
00:25:02.640 --> 00:25:12.420
Sebastien Perusat: Then you don't need automatic detection, I just wanted to mention it, because in a perfect world, in an agile, what I would say automatic detection sure for for 90% of our use cases.

163
00:25:13.140 --> 00:25:23.220
Sebastien Perusat: And just because we had this discussion a couple of seconds ago what happened if it doesn't work we already covered that from the proper perspective but not from the endpoint perspective.

164
00:25:23.880 --> 00:25:35.340
Sebastien Perusat: If you just can go I don't know, maybe 20 seconds later, we should see a command line on the endpoint so obviously it's not something that are a bit more than yeah perfect.

165
00:25:35.970 --> 00:25:48.240
Sebastien Perusat: So obviously it's not meant to be just an every update and just meant to be used for checking if you communication is doing well, so they come at idle updates buddy update server scam.

166
00:25:49.080 --> 00:26:01.050
Sebastien Perusat: will perform the UDP broadcast network will check if there was a body master and we'll try to retrieve information from there, so if you see them that's what you're seeing in the video and I keep coming back.

167
00:26:02.190 --> 00:26:17.910
Sebastien Perusat: You should just double check that it's really the body masa you were thinking off if you have multiple ones imaginary obviously then you're good to go yeah That means that the 13 buddy slave is able to communicate with a big monster.

168
00:26:20.160 --> 00:26:20.400
Patrick Toner: know.

169
00:26:21.570 --> 00:26:23.700
Patrick Toner: Total total side topic here on that note.

170
00:26:24.150 --> 00:26:36.690
Patrick Toner: How many like just extremely useful commands are built into the agile operating system, you know, like like that that one right there where you have you know what let me go back to it, it was a get the exact wording correct here.

171
00:26:37.740 --> 00:26:38.520
Sebastien Perusat: Actually yeah.

172
00:26:38.610 --> 00:26:51.750
Patrick Toner: I gel underscore buddy underscore update underscore server underscore scan and it's going to scan and say hey is there anybody update I think about pro port another one that's just so nice to check ache can I access a device over certain port.

173
00:26:52.950 --> 00:27:02.310
Patrick Toner: question for you, and this is really I don't actually don't know the answer to this is there a public facing document that has some of those commands in the agile community.

174
00:27:03.660 --> 00:27:08.520
Sebastien Perusat: a really good point thanks for asking, yes, but to answer the long answer is.

175
00:27:09.660 --> 00:27:16.080
Sebastien Perusat: I must give the credits to the person who created initially, so I have to be absolutely 100% honest.

176
00:27:17.220 --> 00:27:26.070
Sebastien Perusat: It was a document like this was created piloted 10 years ago by a form an agent way, which was called my mikael hotting from from Germany.

177
00:27:27.150 --> 00:27:33.390
Sebastien Perusat: Who then that agile and she's really know that's what a different story, and I said I don't know, three or four years ago hey, why not.

178
00:27:34.170 --> 00:27:38.370
Sebastien Perusat: reusing that document and adding new features checking of the features are still there.

179
00:27:39.300 --> 00:27:47.730
Sebastien Perusat: long story short answer now he has a risk it's called the agile knows command sheet sheet like cheating and she'd like an excel sheet.

180
00:27:48.390 --> 00:27:55.620
Sebastien Perusat: And you can access on the agile community.com on slack or just PM me and we'll be more than happy to send you out the link So yes, there is a list.

181
00:27:56.040 --> 00:28:02.190
Sebastien Perusat: In just a small list of extreme long list of comments we really focused on.

182
00:28:02.850 --> 00:28:16.230
Sebastien Perusat: What might be interesting for the audience, some are really agile related to specific parts of a script or binary which is just meant to be used as a part of a bigger script we didn't cover them but mostly at the command line which might be interesting for the audience.

183
00:28:16.650 --> 00:28:20.370
Patrick Toner: yeah great great great thanks for that you know I had that I have that cheat sheet.

184
00:28:21.510 --> 00:28:25.530
Patrick Toner: You know it's kind of made its way around the inner eye gel se circles, but.

185
00:28:25.560 --> 00:28:25.800
Patrick Toner: yeah.

186
00:28:26.400 --> 00:28:35.550
Patrick Toner: I wasn't sure if it was public facing it's a great document so if you're an agile administrator you need that document it's going to give you a lot of useful commands you can run from a terminal anyway.

187
00:28:35.910 --> 00:28:37.950
Patrick Toner: Back back with a topic here back to buddy up.

188
00:28:38.160 --> 00:28:38.460
yeah.

189
00:28:39.990 --> 00:28:50.550
Sebastien Perusat: So what I covered just a couple of seconds later is when we think about debugging the the process we already covered the the comment from the command line.

190
00:28:51.900 --> 00:28:56.670
Sebastien Perusat: One thing that I would like to mention, because it, it can be misleading.

191
00:28:58.380 --> 00:29:20.280
Sebastien Perusat: Is if you go back to the to our main topology window in your head, we have the discussion, where we had the body master delivering updates to the body slaves Thank you Frederick for that specific behavior we needed to assign an update component to the body, update and or profile.

192
00:29:21.810 --> 00:29:35.310
Sebastien Perusat: But that can also be an issue why let's imagine that, in the same folder where you have your body master and the body slaves you assigned the University of Findlay up that file to the folder not to the body master.

193
00:29:37.440 --> 00:29:38.940
Sebastien Perusat: something extremely.

194
00:29:40.410 --> 00:29:41.940
Sebastien Perusat: done will would happen.

195
00:29:43.140 --> 00:29:47.760
Sebastien Perusat: The uniqueness of firmware update, even if it is assigned to the folder.

196
00:29:49.230 --> 00:29:52.200
Sebastien Perusat: would override a profile that you assigned to a device.

197
00:29:53.610 --> 00:29:59.160
Sebastien Perusat: Honestly, I would I would be happy to say it's logical and it's good this way, but it isn't.

198
00:30:00.030 --> 00:30:12.990
Sebastien Perusat: It just doesn't make sense at all, I mean from a Niger in make make sense but usually if you assign something to the folder and not device, and you have a concurrent setting on the device of your profile the program device or will win.

199
00:30:14.190 --> 00:30:22.230
Sebastien Perusat: And that specific case no So if you have a feeling that your device is still downloading the update from the US.

200
00:30:23.610 --> 00:30:34.170
Sebastien Perusat: It is a highly possible that you assigned you the firmware update to the folder easy way to check take the device right click the device and us go to edit configuration.

201
00:30:34.950 --> 00:30:46.800
Sebastien Perusat: Go again to system go again to update the firmware update and double check, please, if there is a setting, which is pre setting the from the update folder and it was somewhere the ants.

202
00:30:47.430 --> 00:30:55.170
Sebastien Perusat: Patrick I don't know if you can maybe switch to the last three or four minutes, just to show where we are.

203
00:30:56.280 --> 00:30:58.620
Sebastien Perusat: yeah looks good.

204
00:30:59.880 --> 00:31:04.230
Sebastien Perusat: So that's where you're seeing the information about just reaffirmed.

205
00:31:05.220 --> 00:31:13.410
Patrick Toner: yeah I think that's probably worth repeating right the the the buddy update profile has to be applied to.

206
00:31:14.310 --> 00:31:21.540
Patrick Toner: Be buddy update server directly, not in the not in the directory lives in any of that it's got to be directly applied.

207
00:31:22.110 --> 00:31:29.790
Patrick Toner: And if it's not directly applied you're going to have issues with the process and your devices could potentially still cause network traffic issues if they're going back to you is.

208
00:31:31.140 --> 00:31:31.800
Patrick Toner: Very important.

209
00:31:33.180 --> 00:31:39.450
Sebastien Perusat: Because that's I mean there was obviously a way more things with the back, but from a pure experience point of view.

210
00:31:40.050 --> 00:31:51.210
Sebastien Perusat: If you assign the master profile, then the update them start the update on the about the monster you checked with agile body update service can that the device the slave can contact the master.

211
00:31:52.830 --> 00:32:03.480
Sebastien Perusat: You should already be pretty good if you can check that no indirect assigned us a firmware update objects, is trying to take over the road.

212
00:32:04.380 --> 00:32:19.440
Sebastien Perusat: Honestly, then you have still the possibility of something on the network is blocking the access but that's something that you can easily check them with your network to like practically mentioned was probably part with nc was paying etc just object that you're able to access.

213
00:32:20.550 --> 00:32:24.540
Sebastien Perusat: But honestly that's less than two or 3% of my customers.

214
00:32:25.860 --> 00:32:37.110
Sebastien Perusat: So that's basically it, I mean we don't have so much new information we're getting buddy updates, but like I said, we might expect a change in in your future regarding the protocols, but at the moment that's what we have.

215
00:32:38.250 --> 00:32:51.810
Patrick Toner: got it well, I think I think there's a great overview and I think this is one of those features that like I said I people I talked to you, they don't use it, or they don't know it exists it's kind of viewed maybe more in a way kind of is a legacy feature it's been around a long time.

216
00:32:52.860 --> 00:32:58.410
Patrick Toner: You know and as you know, bandwidth has gotten better and better maybe there's less of a reason to rely on it.

217
00:32:59.370 --> 00:33:07.710
Patrick Toner: But look me and we're all we all anyone who's managed any type of network or devices, you know you're always going to have this you're always going to have unless you're.

218
00:33:08.100 --> 00:33:17.970
Patrick Toner: All of your you know facilities are in a in a city that are you know high bandwidth you're probably going to consider something like this, so I think it's a great feature, and I do appreciate this video walking through it.

219
00:33:19.440 --> 00:33:28.350
Patrick Toner: You know, and where where Can somebody user guide on this too, or is this is this just the only place you know where this information lives, do you know.

220
00:33:29.310 --> 00:33:40.380
Sebastien Perusat: What if we haven't already in the video itself in the in the comments section, we have the knowledge base articles and that's I would say, one of the first thing that I would like to point out because.

221
00:33:41.610 --> 00:33:57.630
Sebastien Perusat: I didn't reinvent the wheel, I was not the person who developed that feature, so I took over the kb articles already covering most of the questions coming up regarding the feature so but, but it was showing the video is exactly what i'm referring to.

222
00:33:58.950 --> 00:34:05.490
Sebastien Perusat: But every day back steps that are just managed as described there, so we have a little gap between the written and the video form but that's.

223
00:34:05.760 --> 00:34:14.670
Sebastien Perusat: Also, the reason why we have technology detective Tuesday videos just to fill the gaps between a pure written form and spoken from about a specific topic.

224
00:34:15.510 --> 00:34:20.070
Patrick Toner: yeah that's great, and you know I see that there's links to all the kb articles, and you know.

225
00:34:20.550 --> 00:34:31.290
Patrick Toner: And you know, to be honest, I mean there's always value there's always times, where you're like I just want to be quiet and and read you know, a manual and figure this out yeah then there's also times I mean know for me i'm more visual and look my learning.

226
00:34:31.950 --> 00:34:39.750
Patrick Toner: Seeing somebody do it, it just you know just retains better so it's great that you do these so so people can have kind of both available to them that.

227
00:34:39.990 --> 00:34:41.700
Sebastien Perusat: Feedback Thank you Patrick yeah.

228
00:34:41.880 --> 00:34:50.940
Patrick Toner: Alright what's up you know I appreciate this and I think we kind of covered the the topic here, hopefully, the listeners anyone who's listening you got something out of this.

229
00:34:51.750 --> 00:35:00.000
Patrick Toner: yeah give it a shot, you know if your if your natural admin you know, and you want to kick tires on this it you don't have to have any special licensing or anything that already exist.

230
00:35:00.900 --> 00:35:10.740
Patrick Toner: You know it's worth worth checking it out seeing if it may be a solution for you, you know so and I guess we kind of wrap up here said, I think you know episode 50.

231
00:35:11.760 --> 00:35:23.700
Patrick Toner: minus the fireworks it was a pretty good topic and and I just appreciate your time on this and and for putting this out and now for everybody listening, thank you for taking the time to have any closing thoughts.

232
00:35:24.180 --> 00:35:33.750
Sebastien Perusat: Just so big thank you to extend tiger again for keeping the podcast and i'm really looking forward for the number 51 or 52 because i'm pretty sure that we have another great topic to cover them.

233
00:35:34.260 --> 00:35:39.270
Patrick Toner: Very good, very good a little teaser to end it i'm looking forward to 100 i'm really looking forward to those fireworks.

234
00:35:39.480 --> 00:35:39.810
legit.

235
00:35:41.850 --> 00:35:42.300
Patrick Toner: alright.

236
00:35:42.360 --> 00:35:46.230
Patrick Toner: Well, thank you guys everybody and have a great great day.

237
00:35:46.800 --> 00:35:48.450
Sebastien Perusat: Have a good week too bye bye.

238
00:35:48.990 --> 00:35:49.260
bye.