1
00:00:00,000 --> 00:00:07,760
I think the next thing I wanted to show then was jobs and how to schedule things.

2
00:00:08,000 --> 00:00:09,860
So you see here I have an empty set of jobs.

3
00:00:10,760 --> 00:00:16,300
What we did before was we backed up devices manually and we clicked a button that said Backup Now, all that good stuff.

4
00:00:17,000 --> 00:00:20,820
But you probably never want to say have to backup manually again.

5
00:00:20,840 --> 00:00:21,940
You just want to run that on schedule.

6
00:00:21,940 --> 00:00:25,460
So you'd go into the Jobs tab and create a new job.

7
00:00:25,940 --> 00:00:31,980
I'm going to create a backup job that's called my Nightly Backup.

8
00:00:32,660 --> 00:00:34,580
I'll put it in a group just called Nightlies.

9
00:00:37,880 --> 00:00:38,280
Okay.

10
00:00:38,580 --> 00:00:44,500
And so the first thing we do here is select the devices that are going to be part of this backup job.

11
00:00:44,580 --> 00:00:46,960
And we can create a static list of devices here.

12
00:00:47,700 --> 00:00:51,080
But what you probably want to do is do some sort of search criteria.

13
00:00:51,800 --> 00:00:55,180
And so I'm going to backup all my Austin devices, let's say.

14
00:00:55,600 --> 00:00:58,160
And all I did was say use the search from the devices view.

15
00:00:58,340 --> 00:01:00,520
So whatever you did up here, it's just going to plug into here.

16
00:01:01,160 --> 00:01:05,560
So I'm on a schedule and you get the same schedule control that we saw before.

17
00:01:05,860 --> 00:01:06,080
Right.

18
00:01:06,460 --> 00:01:12,040
I'm going to backup all of these devices, let's say nightly at midnight, some off time.

19
00:01:12,680 --> 00:01:16,240
And so this is how you would go in and do that sort of thing.

20
00:01:18,560 --> 00:01:21,240
And the other types of jobs there, you can schedule a report.

21
00:01:22,120 --> 00:01:25,460
So we have configuration change reports, which is another popular one.

22
00:01:25,780 --> 00:01:32,480
You know, every morning I want to see an email that gives me the configuration changes that happened the previous day, that type of thing.

23
00:01:32,800 --> 00:01:35,940
It's like your BlackBerry driving commute goody time.

24
00:01:36,360 --> 00:01:36,520
Yeah.

25
00:01:37,480 --> 00:01:37,960
Exactly.

26
00:01:38,360 --> 00:01:40,180
You can schedule a tool as well.

27
00:01:40,420 --> 00:01:44,180
So everything we did before, like we changed the login banner on devices.

28
00:01:44,180 --> 00:01:50,940
If you didn't want to run that now, you'd create a new job and schedule, you know, your login banner should change at 10 p.m. tonight, let's say.

29
00:01:51,220 --> 00:02:01,240
Okay, so sort of through that avenue, since adapters can add different tools and you could actually have different types of jobs that you would run based on what adapters have contributed.

30
00:02:02,100 --> 00:02:02,540
Correct.

31
00:02:02,840 --> 00:02:05,760
So I showed you, I'll give you a little hint on the reports there.

32
00:02:05,920 --> 00:02:08,100
I can give you a quick peek at reports, too.

33
00:02:09,020 --> 00:02:17,760
So we have two ins for reports, and one is these quick reports, which run against devices, all of the devices in your inventory, and I'll run one here.

34
00:02:18,000 --> 00:02:19,100
We'll take a look at what it is.

35
00:02:20,300 --> 00:02:30,940
And while this is loading up, we run our report, we write our reports against the BERT reporting framework, which is an open source framework for reporting.

36
00:02:30,940 --> 00:02:36,780
The tool framework, or the report framework, just like tools and adapters, extensible as well.

37
00:02:36,980 --> 00:02:47,080
So if you know what BERT is, and you can write a BERT report, you can drop it in our system, and it'll show up in wherever you want to put it, in the quick reports or from the devices view.

38
00:02:47,820 --> 00:02:57,160
So this software summary report that came up is just, you know, going against our flat database and tells me all the different vendor types that I have and the operating systems of each vendor.

39
00:02:57,520 --> 00:02:59,100
Let's give another example here.

40
00:03:01,260 --> 00:03:04,380
Let's say I want to see my network hardware summary.

41
00:03:05,900 --> 00:03:10,100
This will give me a similar output, but in a more graphical format.

42
00:03:13,600 --> 00:03:16,900
You can see these are my breakdown of hardware vendors.

43
00:03:17,180 --> 00:03:17,440
All right.

44
00:03:17,440 --> 00:03:19,240
And then the device types as well.

45
00:03:19,580 --> 00:03:29,740
So I can see that I have so many, you know, I've got 62 routers, 55 switches, and, you know, a slew of other device types in my network, too.

46
00:03:29,820 --> 00:03:32,680
So I can just get kind of a quick view of what I actually have.

47
00:03:32,920 --> 00:03:33,200
Right.

48
00:03:33,680 --> 00:03:42,440
And along with this, you know, if you want to see what you actually have for software and you don't allow, like, 1125P code out there, you can come in here and make sure no one's running it in your network.

49
00:03:43,100 --> 00:03:43,320
Right.

50
00:03:43,440 --> 00:03:45,240
No one wants that 1125P code.

51
00:03:45,480 --> 00:03:45,760
No.

52
00:03:46,800 --> 00:03:57,560
Along with the ARP cache and all the other neighbor type stuff we store, we have this neighbors button here that gives you a quick view of what's attached to each device.

53
00:03:58,260 --> 00:04:00,700
So I brought up the neighbors for my 7206.

54
00:04:00,960 --> 00:04:09,860
And I see that I have, you know, eight or so OSPF neighbors and several BGP neighbors and several CDP neighbors and some IPv6 NDP neighbors.

55
00:04:10,920 --> 00:04:13,400
So this just presents it in a nice table for you.

56
00:04:13,780 --> 00:04:15,460
And you kind of walk what you'd expect.

57
00:04:15,460 --> 00:04:20,380
So let's say I want to walk through my BGP neighbors.

58
00:04:21,160 --> 00:04:24,680
I'm on this 20.213 device.

59
00:04:24,840 --> 00:04:27,620
I'm going to double-click on this 20.215 device.

60
00:04:28,080 --> 00:04:31,580
Now it pops up that guy's neighbors, this DAL M5.

61
00:04:33,020 --> 00:04:34,980
And you can walk to another device from there.

62
00:04:35,080 --> 00:04:38,140
And you see this table is kind of refreshing with each guy's new neighbors.

63
00:04:38,140 --> 00:04:43,940
So you can sort of use this sort of drilling down table to walk across your network's neighborhoods, if you will.

64
00:04:44,140 --> 00:04:44,620
Yeah, yeah.

65
00:04:44,680 --> 00:04:45,580
It's almost the replacement.

66
00:04:45,800 --> 00:04:48,640
I would say it's a replacement for, like, a visual topology.

67
00:04:48,840 --> 00:04:49,100
Right.

68
00:04:49,640 --> 00:04:54,360
So, you know, a visual topology in itself isn't useful, I would say.

69
00:04:55,500 --> 00:05:01,180
You know, things that use a topology kind of framework, like event correlation, those things are useful.

70
00:05:01,300 --> 00:05:06,620
But just to see it, you know, I'd rather just see what's directly connected to this device and then this device and this device.

71
00:05:06,700 --> 00:05:06,880
Right.

72
00:05:06,880 --> 00:05:08,580
So we've kind of simplified that view for you.

73
00:05:08,700 --> 00:05:14,200
It's obviously easier to pack a lot more information into these tables than the visual representation.

74
00:05:14,700 --> 00:05:14,860
Yeah.

75
00:05:14,960 --> 00:05:24,660
And we can say, you know, beyond the traditional here's what you have type of map, we've actually said, well, here's what you have and here's why you have it.

76
00:05:24,660 --> 00:05:27,420
So, you know, this guy's your neighbor via CDP.

77
00:05:27,960 --> 00:05:29,820
This guy's your OSPF neighbor.

78
00:05:30,240 --> 00:05:36,960
So to be able to say this is your OSPF neighbor versus this is your BDP neighbor is, you know, it's a good amount of data, too.

79
00:05:37,760 --> 00:05:46,420
Through the UI, one of the primary integration points might be your launchers, which is just a simple open a web page from here type of thing.

80
00:05:46,780 --> 00:05:51,020
And can you pass, like, attributes to it or something so that you might be cross-launching into something else?

81
00:05:51,020 --> 00:05:51,380
Exactly.

82
00:05:51,620 --> 00:05:51,760
Yeah.

83
00:05:51,920 --> 00:05:59,060
So I put up a dummy one just called eBay, right, which is not really an integration, but it allows me to show you what you can do with those attributes.

84
00:06:00,020 --> 00:06:02,660
And so let's say this 3750 went down.

85
00:06:02,660 --> 00:06:12,100
And I might click on here and click on my eBay launcher, and this will pop another window if its Internet connection is working all right.

86
00:06:13,980 --> 00:06:19,640
You see here it did an eBay search for this make and model of device, and it didn't find anything on eBay.

87
00:06:20,300 --> 00:06:21,460
So you better hold on to that one.

88
00:06:21,760 --> 00:06:22,040
Yeah.

89
00:06:22,460 --> 00:06:23,480
And I can't replace.

90
00:06:23,940 --> 00:06:25,580
See if another one does anything.

91
00:06:27,060 --> 00:06:30,720
But, hey, I can find a couple 7206s on eBay if I need to.

92
00:06:31,680 --> 00:06:36,720
But, anyway, so you see there it passed the make and the model of the device through to the eBay URL.

93
00:06:37,020 --> 00:06:42,060
If you want to configure those, you can do this through our API or you can do it through the UI like this.

94
00:06:43,160 --> 00:06:49,480
And so you would say, so let's say you wanted to create a Xenos integration.

95
00:06:50,920 --> 00:06:57,260
So you see here you're presented with all these variables on the right, so you can put in the host name or the IP address.

96
00:06:57,380 --> 00:06:57,620
Right.

97
00:06:57,760 --> 00:06:57,880
Yeah.

98
00:06:58,100 --> 00:07:00,320
Whatever variables you want to substitute in your URL.

99
00:07:00,320 --> 00:07:05,940
So you can basically start treating the URL sort of like an interesting interface into another system.

100
00:07:06,340 --> 00:07:06,680
Yeah.

101
00:07:07,420 --> 00:07:14,480
And it's actually a pretty easy way to, as long as you can figure out the right parameters, it's an easy way to integrate between two different things.

102
00:07:14,840 --> 00:07:15,000
Yeah.

103
00:07:15,300 --> 00:07:16,620
And we have users that do this.

104
00:07:16,760 --> 00:07:26,540
So they may set up an SSH launcher and they'll put SSH in there and then configure their Firefox to know what to do with it, the SSH protocol, that type of thing.

105
00:07:26,800 --> 00:07:28,060
So you can do quite a bit with it.

106
00:07:28,880 --> 00:07:35,680
You know, it's very simple to kind of maintain and use, but it's a strong integration point if you're looking to integrate as a third party.

107
00:07:35,940 --> 00:07:38,980
We also, you know, standard SNMP traps that we have.

108
00:07:38,980 --> 00:07:44,860
So, you know, we have a trap that we send out for when we add a device.

109
00:07:45,000 --> 00:07:56,160
So if you wanted to use us for discovery and just respond to our added device and delete device traps, you can do that and, you know, never maintain your inventory on your secondary NMS.

110
00:07:56,380 --> 00:07:57,440
Just maintain it through us.

111
00:07:57,920 --> 00:08:01,940
You know, we also have our API that is kind of a strong integration point.

112
00:08:03,040 --> 00:08:04,360
A couple of things we've done.

113
00:08:05,620 --> 00:08:09,480
There's an event correlator out there called Simple Event Correlator, SCC.

114
00:08:09,820 --> 00:08:12,600
And if you look at the docs on ziptie.org, you'll see this.

115
00:08:13,520 --> 00:08:16,700
But so they're like a log watcher, basically.

116
00:08:16,820 --> 00:08:20,560
They'll look at a syslog and look for interesting things and do something on it.

117
00:08:21,160 --> 00:08:25,940
And so we have an integration using that so you could put them on your syslog server.

118
00:08:26,540 --> 00:08:31,840
And any time you see someone log in or log out of a device, you could tell ziptie to back up that device.

119
00:08:32,200 --> 00:08:35,520
So, like you were saying, ziptie is an open source project.

120
00:08:35,940 --> 00:08:39,940
And so, like what, and you've mentioned a few different languages and interfaces.

121
00:08:40,140 --> 00:08:43,800
I mean, what are the different languages and technologies that are used underneath it?

122
00:08:44,520 --> 00:08:46,580
So this server is a Java server.

123
00:08:47,640 --> 00:08:49,700
And it's built on the Equinox framework.

124
00:08:49,700 --> 00:08:53,160
It's an OSGI server, so it's bundle-based, plug-in-based.

125
00:08:54,100 --> 00:09:00,160
And this kind of allows us to, you know, do things like the tools plug-in is easier and the report plug-in is easier.

126
00:09:00,900 --> 00:09:02,240
So the server is Java.

127
00:09:02,620 --> 00:09:03,820
The adapters are Perl.

128
00:09:04,660 --> 00:09:09,160
And so, you know, each adapter is a bundle with a bunch of Perl modules in it.

129
00:09:09,780 --> 00:09:16,780
And we chose Perl because Perl seemed to be the, you know, if you were a network engineer and you did any programming, you probably did Perl or Shell, right?

130
00:09:16,780 --> 00:09:20,680
And so that's why we've written all our adapters in Perl.

131
00:09:20,860 --> 00:09:23,480
And we have all of our connection modules and everything like that in Perl.

132
00:09:24,200 --> 00:09:29,320
Now, the communication between our server and the client has always been SOAP.

133
00:09:29,680 --> 00:09:36,060
And so we, like Michael mentioned earlier, we replaced our Eclipse-based RCP client with this Flex client.

134
00:09:36,560 --> 00:09:38,740
Both of them talked SOAP to the server.

135
00:09:38,740 --> 00:09:46,220
So, you know, we didn't have to do much server work to get this new interface in because it was a standardized, you know, communication at that point.

136
00:09:46,640 --> 00:09:57,060
But the web front end is written in Flex and ActionScript, and it plays through the Adobe Flash player or through a Flash player.

137
00:09:57,060 --> 00:10:06,360
So, as I mentioned before, the idea behind open sourcing a lot of these was that it made the code accessible and very easy to extend.

138
00:10:06,640 --> 00:10:18,040
And so the biggest things that we see extended are either adapters to add some new functionality or just to create a brand new adapter or tools to actually create a viewer or automate some change out there.

139
00:10:18,180 --> 00:10:27,440
And because we do have people in our community that are creating a lot of these things, we created the Zipforge as a repository to hold all of those bits of open content.

140
00:10:28,020 --> 00:10:32,960
And, you know, some people have even called them like a currency in the network management world.

141
00:10:33,980 --> 00:10:35,520
And so you can actually go through.

142
00:10:35,780 --> 00:10:46,540
And so, you know, if you need to go out and manage a Juniper device, you can do a search on the Zipforge for all of the adapters and tools that we have for your Juniper hardware.

143
00:10:46,540 --> 00:10:51,220
ZipTie, out of the box, does a large number of things.

144
00:10:51,340 --> 00:10:54,580
It has 40 adapters and manages a wide variety of devices.

145
00:10:54,740 --> 00:10:57,260
But it's always extensible, so you can always add more functionality.

146
00:10:57,940 --> 00:11:01,560
And not only that, not only can you do it yourself, but somebody may have already done it.

147
00:11:01,660 --> 00:11:05,420
So go snoop around the Zipforge to see what's out there.

148
00:11:05,760 --> 00:11:16,420
And obviously feel free to contribute to the Zipforge as well because the biggest goal here was to not have network engineers continue to create the same tools

149
00:11:16,420 --> 00:11:21,420
over and over again, but instead give them a place where they could share ideas and content to make their jobs easier.

150
00:11:21,420 --> 00:11:25,980
In the top, you have like a lot of commercial sort of contributors that you have.

151
00:11:26,200 --> 00:11:31,180
Like what's the mix between companies you have contributing and individuals that you have contributing?

152
00:11:33,100 --> 00:11:38,220
The companies that we have contributing are largely hardware manufacturers.

153
00:11:38,660 --> 00:11:48,980
So they tend to contribute a lot of adapters so that their devices can be managed with AlterPoint products, be that the entire network authority.

154
00:11:49,780 --> 00:12:06,460
The tools that are contributed, I would say, are a little bit more split evenly between end users in the community, people here at AlterPoint who needed to create a tool to do some particular thing, or those device manufacturers.

155
00:12:06,660 --> 00:12:09,200
So the tools kind of come from all over the place.

156
00:12:09,200 --> 00:12:17,380
The adapters are generally created from scratch by some of these commercial partners.

157
00:12:18,840 --> 00:12:25,380
And while they're created from scratch by those guys, they tend to be modified or enhanced out there in the field.

158
00:12:25,580 --> 00:12:31,120
And so if you find an adapter that you want, like what's the process of adding it into your ZipTie instance?

159
00:12:31,860 --> 00:12:36,020
Right now you just go up to the ZipForge and you search for it every one.

160
00:12:36,140 --> 00:12:38,460
And so let's say you wanted this Silver Peak adapter.

161
00:12:39,340 --> 00:12:41,780
I clicked on the Silver Peak and here's the adapter.

162
00:12:42,600 --> 00:12:45,460
And you go here and you're able to download a Zip file.

163
00:12:45,960 --> 00:12:48,880
Just unzip it in your server's home directory and you're good to go.

164
00:12:48,980 --> 00:12:50,820
And it puts the plug-ins where they need to be.

165
00:12:52,060 --> 00:12:53,080
And that's pretty much it.

166
00:12:53,640 --> 00:12:57,160
And each one has deployment instructions on it so you can kind of see what you need to do.

167
00:12:57,160 --> 00:12:57,560
Okay.

168
00:12:58,100 --> 00:13:03,000
And then since it's like a web application server-based thing, you really only have to unzip it one place.

169
00:13:03,100 --> 00:13:06,040
There's not a bunch of agents or anything you have to update and all that.

170
00:13:06,200 --> 00:13:06,640
You got it.

171
00:13:06,700 --> 00:13:06,860
Yep.

172
00:13:07,040 --> 00:13:07,220
Right.

173
00:13:07,460 --> 00:13:07,640
Yep.

174
00:13:07,700 --> 00:13:08,960
Put it on the server and you're good to go.

175
00:13:09,140 --> 00:13:09,500
Well, great.

176
00:13:09,580 --> 00:13:11,580
Well, thanks for spending the time to show us this.

177
00:13:11,700 --> 00:13:12,580
And just one last thing.

178
00:13:12,660 --> 00:13:15,460
I mean, we can kind of figure out the URL from what we're looking at here.

179
00:13:15,540 --> 00:13:18,360
But if people wanted to use ZipTie, where do they go to get it?

180
00:13:19,520 --> 00:13:20,400
ZipTie.org.

181
00:13:22,680 --> 00:13:24,720
And they can just say hello to the giraffe there.

182
00:13:25,120 --> 00:13:25,640
That's right.

183
00:13:27,160 --> 00:13:32,140
And since it's open source, there's not any licensing concerns or money to pay for it.

184
00:13:32,760 --> 00:13:33,340
That's right.

185
00:13:33,440 --> 00:13:36,320
It is free to download, install, and use.

186
00:13:36,680 --> 00:13:37,760
We do have support packages.

187
00:13:38,660 --> 00:13:44,340
So you can get premium support or standard support, which gives you somebody to call any time of day or night.

188
00:13:45,200 --> 00:14:01,900
And then all of it, all of ZipTie's license under the Mozilla public license, which gives a lot of liberty to people to go out and extend it and doesn't have, you know, some of the, you know, quote, unquote, polluting clauses in it that other licenses do.

189
00:14:01,900 --> 00:14:12,200
So we wanted to do something that was a no-brainer so that this could get adopted into the enterprise and used without fear of some strange license repercussions.

190
00:14:12,760 --> 00:14:12,860
Right.

191
00:14:13,020 --> 00:14:13,760
That makes sense.

192
00:14:13,860 --> 00:14:14,140
Well, great.

193
00:14:14,240 --> 00:14:16,060
Well, thanks for taking the time to show this to us today.

194
00:14:16,600 --> 00:14:17,140
Thank you, Coté.

195
00:14:17,420 --> 00:14:17,780
Thanks.
