WEBVTT

0:00:02.960000 --> 0:00:07.300000
 In this video, I'm going to talk about
 historical to current methods of

0:00:07.300000 --> 0:00:08.880000
 network management.

0:00:08.880000 --> 0:00:13.200000
 The topics for this video are we're going
 to look at what are the definitions

0:00:13.200000 --> 0:00:16.780000
 of network management because that term
 network management can mean various

0:00:16.780000 --> 0:00:21.220000
 things to different people, some historical
 methods and some past and

0:00:21.220000 --> 0:00:25.600000
 current challenges with the historical
 and current methods.

0:00:25.600000 --> 0:00:27.540000
 So let's get right into it.

0:00:27.540000 --> 0:00:29.820000
 So what encompasses
 network management?

0:00:29.820000 --> 0:00:34.020000
 When I use that term and I say that
 to you, what do you think network

0:00:34.020000 --> 0:00:38.400000
 management is? Now that could be a very
 narrow scope to some people, it

0:00:38.400000 --> 0:00:40.920000
 could be a very wide scope
 to other people.

0:00:40.920000 --> 0:00:45.640000
 In the context of this video, network
 management means a variety of things.

0:00:45.640000 --> 0:00:49.620000
 It means the physical installation
 of new equipment, that is managing

0:00:49.620000 --> 0:00:53.180000
 your network after all is
 installing new things.

0:00:53.180000 --> 0:00:55.760000
 It could mean the initial configuration
 of equipment.

0:00:55.760000 --> 0:01:00.600000
 Some people call that the term provisioning,
 basically adding brand new

0:01:00.600000 --> 0:01:04.940000
 IP addresses, configuring your routing
 protocol for the first time, adding

0:01:04.940000 --> 0:01:09.000000
 brand new VLANs, all the things you
 would do once you take a device out

0:01:09.000000 --> 0:01:13.500000
 of its box, plug it in and access the
 command line or the GUI for the

0:01:13.500000 --> 0:01:17.280000
 first time, that's what I
 would call provisioning.

0:01:17.280000 --> 0:01:21.240000
 Network management also encompasses
 monitoring and testing of equipment.

0:01:21.240000 --> 0:01:24.580000
 Has the device learned
 of new routes?

0:01:24.580000 --> 0:01:29.820000
 Is the switch keeping our traffic separate
 based on the VLANs we've created?

0:01:29.820000 --> 0:01:33.380000
 Are the applications on the end devices
 getting through the network equipment

0:01:33.380000 --> 0:01:39.080000
 and is the quality of experience that
 the users are having acceptable?

0:01:39.080000 --> 0:01:46.300000
 Software upgrades and patches of devices
 and configuration tuning and

0:01:46.300000 --> 0:01:49.420000
 enhancements. Oh, I've just learned
 about this brand new feature that

0:01:49.420000 --> 0:01:53.020000
 lo and behold is part of my
 existing feature set in iOS.

0:01:53.020000 --> 0:01:56.340000
 Let me use this feature to make
 my network more productive.

0:01:56.340000 --> 0:01:59.820000
 That would be considered configuration
 tuning or adding enhancements to

0:01:59.820000 --> 0:02:05.420000
 your network. Now what are some past
 and present ways, actual tangible

0:02:05.420000 --> 0:02:09.120000
 ways that we can make
 this stuff a reality?

0:02:09.120000 --> 0:02:14.840000
 Well, in the past and currently, as far
 as the configuration and troubleshooting

0:02:14.840000 --> 0:02:19.680000
 of networks and the software patching
 of networks, we have typically relied

0:02:19.680000 --> 0:02:24.120000
 on getting into an individual box,
 whether it be a firewall or router

0:02:24.120000 --> 0:02:29.680000
 or switch using methods like SSH,
 Telnet or console access.

0:02:29.680000 --> 0:02:33.960000
 And you can see right here, this is a
 screenshot of secure CRT where I've

0:02:33.960000 --> 0:02:38.540000
 opened up connections via Telnet
 to four individual devices.

0:02:38.540000 --> 0:02:42.460000
 And so I'll have to go into each device
 one at a time to apply my configuration,

0:02:42.460000 --> 0:02:47.100000
 to do my troubleshooting, or if I want
 to upgrade the software on each

0:02:47.100000 --> 0:02:53.760000
 device. SNMP has been used historically
 to a very limited degree here.

0:02:53.760000 --> 0:02:58.900000
 Most people use SNMP for network monitoring,
 collecting of statistics.

0:02:58.900000 --> 0:03:03.880000
 But SNMP does give you the ability,
 depending on your platform, to push

0:03:03.880000 --> 0:03:06.160000
 commands down to devices.

0:03:06.160000 --> 0:03:09.860000
 So you can actually configure devices
 using SNMP and that has been used

0:03:09.860000 --> 0:03:11.640000
 in a limited approach.

0:03:11.640000 --> 0:03:13.820000
 The usage of scripts.

0:03:13.820000 --> 0:03:18.180000
 Scripts in this context means once you've
 logged into a router or switch

0:03:18.180000 --> 0:03:23.300000
 or a firewall, maybe that device has
 some ability built into its software

0:03:23.300000 --> 0:03:26.080000
 to provide you a scripting
 language.

0:03:26.080000 --> 0:03:30.600000
 So you can do some scripting
 right on the box itself.

0:03:30.600000 --> 0:03:34.560000
 And of course, there's notepad
 for the creation of text files.

0:03:34.560000 --> 0:03:39.720000
 A lot of people rely on notepad or some
 other similar text editor to create

0:03:39.720000 --> 0:03:44.420000
 a configuration file, save that as a
 template, and then they can use that

0:03:44.420000 --> 0:03:49.100000
 generically to apply it across multiple
 devices of the same type.

0:03:49.100000 --> 0:03:53.340000
 And from a network monitoring perspective,
 we've typically relied on SNMP

0:03:53.340000 --> 0:03:59.000000
 and NetFlow to collect our network statistics,
 and so we can analyze that

0:03:59.000000 --> 0:04:03.080000
 stuff. Now, with all of these present
 methods of management, there are

0:04:03.080000 --> 0:04:05.100000
 some challenges.

0:04:05.100000 --> 0:04:09.480000
 For example, the larger your network
 becomes, the bigger it grows, the

0:04:09.480000 --> 0:04:12.320000
 more of an IT staff you're going to
 need to manage all those different

0:04:12.320000 --> 0:04:18.500000
 devices. Frequently requires that your
 network engineers or admins know

0:04:18.500000 --> 0:04:21.620000
 multiple network operating
 systems.

0:04:21.620000 --> 0:04:27.980000
 Very few networks out there are homogenous
 and just all Cisco or all Juniper.

0:04:27.980000 --> 0:04:30.940000
 Most networks exist these days are a
 combination of different things like

0:04:30.940000 --> 0:04:37.500000
 we see here, Arista, Juniper, Cisco,
 HP, and a variety of other things.

0:04:37.500000 --> 0:04:42.420000
 So, now we've got a network that is using
 various different command lines,

0:04:42.420000 --> 0:04:44.180000
 various different languages.

0:04:44.180000 --> 0:04:45.720000
 How do we work with that?

0:04:45.720000 --> 0:04:48.300000
 Well, we could have
 silos of expertise.

0:04:48.300000 --> 0:04:50.980000
 Maybe John over here is
 our Juniper expert.

0:04:50.980000 --> 0:04:54.040000
 Whenever we need something done on the
 Juniper devices or troubleshooting,

0:04:54.040000 --> 0:04:57.760000
 we go to John. Maybe Sally over
 here is our Cisco expert.

0:04:57.760000 --> 0:05:01.040000
 So we've got these people who
 are these silos of expertise.

0:05:01.040000 --> 0:05:03.280000
 Of course, there's a clear
 problem with that.

0:05:03.280000 --> 0:05:06.700000
 What if John's out on vacation for two
 weeks and we need something done

0:05:06.700000 --> 0:05:08.200000
 on the Juniper box?

0:05:08.200000 --> 0:05:10.240000
 What if John leaves the company?

0:05:10.240000 --> 0:05:14.380000
 Now that whole silo of expertise is
 gone and we have to rebuild it in

0:05:14.380000 --> 0:05:17.960000
 somebody else. Now, you might say,
 oh, well, in our company, we prefer

0:05:17.960000 --> 0:05:21.720000
 that every network engineer,
 every admin, know everything.

0:05:21.720000 --> 0:05:24.400000
 So if you're hired into our company,
 you're eventually going to have to

0:05:24.400000 --> 0:05:28.140000
 learn Cisco, Junos, Arista,
 and everything else.

0:05:28.140000 --> 0:05:31.080000
 Well, that's all well and good, but that's
 going to lead to a huge learning

0:05:31.080000 --> 0:05:36.500000
 curve. That's going to be weeks, possibly
 months before someone's an expert

0:05:36.500000 --> 0:05:38.640000
 in all these different things.

0:05:38.640000 --> 0:05:41.100000
 And that they're not going to be as
 productive during that time while

0:05:41.100000 --> 0:05:43.300000
 they're in that learning curve.

0:05:43.300000 --> 0:05:47.700000
 Your network engineers and admins are
 also going to have to know SNMP

0:05:47.700000 --> 0:05:49.780000
 for configuration and management.

0:05:49.780000 --> 0:05:52.800000
 They're going to have to know
 the theory of how SNMP works.

0:05:52.800000 --> 0:05:55.580000
 They're going to have to know how to
 configure it via the command line

0:05:55.580000 --> 0:05:58.580000
 in Cisco and Juniper and Arista.

0:05:58.580000 --> 0:06:01.780000
 And then they're going to have to be familiar
 with some sort of SNMP manager

0:06:01.780000 --> 0:06:06.160000
 platform and that GUI and how that
 GUI works and what tab to click and

0:06:06.160000 --> 0:06:09.560000
 what drop down box to do to accomplish
 the various things they want to

0:06:09.560000 --> 0:06:13.220000
 accomplish. That also leads
 to a steep learning curve.

0:06:13.220000 --> 0:06:18.040000
 So all of this really boils down
 to box by box management.

0:06:18.040000 --> 0:06:22.700000
 And this is the main challenge with traditional
 methods of network management

0:06:22.700000 --> 0:06:26.820000
 is if I have a network composed of a
 thousand or five thousand different

0:06:26.820000 --> 0:06:31.880000
 nodes, firewalls, switches, routers,
 that's a lot of devices I'm going

0:06:31.880000 --> 0:06:36.840000
 to have to get into one at a time
 to configure or troubleshoot.

0:06:36.840000 --> 0:06:40.960000
 That's a lot of time spent
 that could be automated.

0:06:40.960000 --> 0:06:44.920000
 Now I mentioned the previous slide that
 notepad is the engineer's favorite

0:06:44.920000 --> 0:06:49.260000
 tool for coming up with configurations
 and saving as templates.

0:06:49.260000 --> 0:06:53.700000
 But there's a problem whether using
 notepad or any text editor is that

0:06:53.700000 --> 0:06:55.740000
 it's easy to make mistakes.

0:06:55.740000 --> 0:06:58.720000
 And those mistakes could be replicated
 across lots of different devices

0:06:58.720000 --> 0:07:00.880000
 before you discover your mistake.

0:07:00.880000 --> 0:07:04.880000
 What if you accidentally apply this exact
 same host name to all your different

0:07:04.880000 --> 0:07:09.760000
 routers or the exact same IP address on
 an interface across multiple routers?

0:07:09.760000 --> 0:07:12.320000
 That's not going to work and now you're
 going to go back and fix all that

0:07:12.320000 --> 0:07:15.720000
 stuff. And that text file that you just
 created that's all pristine and

0:07:15.720000 --> 0:07:17.120000
 pretty and beautiful.

0:07:17.120000 --> 0:07:18.700000
 What happens if it get lost?

0:07:18.700000 --> 0:07:22.740000
 Somebody forgets what file they stored
 it in or accidentally gets deleted.

0:07:22.740000 --> 0:07:26.340000
 That's a problem with using a text editor
 as your central point of reference

0:07:26.340000 --> 0:07:29.620000
 when coming up with configuration
 templates.

0:07:29.620000 --> 0:07:33.200000
 So this video has gone over some of
 the current and historical ways of

0:07:33.200000 --> 0:07:34.680000
 doing network management.

0:07:34.680000 --> 0:07:37.420000
 We've defined what network
 management actually is.

0:07:37.420000 --> 0:07:41.060000
 And I finished up by showing you some
 of the challenges and potential

0:07:41.060000 --> 0:07:44.160000
 problems with the current
 way of doing things.

