1
00:00:00,300 --> 00:00:01,860
So what are the best practices.

2
00:00:02,010 --> 00:00:08,750
What should you be doing in a live environment now best practices state that you should use both.

3
00:00:08,820 --> 00:00:15,420
You should use polling based or query based as well as event based network management protocols as part

4
00:00:15,420 --> 00:00:21,650
of your network management solution doesn't help just to receive a large amount of data.

5
00:00:21,830 --> 00:00:24,620
You need to make meaningful decisions on that data.

6
00:00:25,400 --> 00:00:31,220
So you also want to build and leverage alerts and reports so that you both are notified when an issue

7
00:00:31,220 --> 00:00:38,580
occurs whether it was based on a polling based detection mechanism or an event based detection.

8
00:00:38,640 --> 00:00:44,190
And in addition you're going to want some kind of reporting capability which provide you with detail

9
00:00:44,190 --> 00:00:50,860
of performance not only in real time at this point in time but over a period of time.

10
00:00:50,910 --> 00:00:55,320
So you want historical data available so that you can make meaningful decisions.

11
00:00:56,340 --> 00:01:02,180
As an example if an interface on a rota has a utilization of 70 percent.

12
00:01:02,310 --> 00:01:09,110
Is that good or is that a bad that's difficult to know if you don't have historical data that allows

13
00:01:09,110 --> 00:01:15,700
you to build a baseline of what your network typically runs at if that interface in the last three months

14
00:01:15,700 --> 00:01:21,690
has been running at two percent utilization and now suddenly it's running at 90 percent utilization.

15
00:01:21,910 --> 00:01:27,370
You'll know that something has happened on your network that is changed to the interface utilization

16
00:01:27,370 --> 00:01:34,420
dramatically so you're going to want reports to give you performance detail over time as well as notify

17
00:01:34,420 --> 00:01:41,800
you of issues and the availability of devices in your network you're going to want to at a glance be

18
00:01:41,800 --> 00:01:48,010
able to see if there's a problem with a network device such as a router or if there's a problem with

19
00:01:48,010 --> 00:01:51,750
an individual interface on one of your routers.

20
00:01:51,770 --> 00:01:59,380
Don't forget to set the polling frequency and how granular your event notifications are.

21
00:01:59,500 --> 00:02:05,260
This will vary from one environment to another and often depends on the type of topology that you have

22
00:02:05,830 --> 00:02:12,580
the bandwidth available and the resources you have to detect and then act on the information that you're

23
00:02:12,580 --> 00:02:14,130
receiving.

24
00:02:14,130 --> 00:02:20,340
In addition you might need to make decisions on how quickly you need to react to an issue on your network

25
00:02:21,410 --> 00:02:28,430
if something happens on your network and it effects an entire building or the entire organization.

26
00:02:28,430 --> 00:02:33,680
You're going to want to act on that quickly but if something happens and it only affects a single device

27
00:02:33,710 --> 00:02:35,390
that's not important.

28
00:02:35,390 --> 00:02:41,540
It's probably not as important that you get woken up at 3:00 in the morning to tell you that the port

29
00:02:41,570 --> 00:02:42,770
on the switch has gone down.