1
00:00:00,360 --> 00:00:06,720
When you deploy a network management system it's typically going to add an overhead to your network.

2
00:00:06,720 --> 00:00:12,930
This is especially true if you're using a query based system that's polling the network using a very

3
00:00:12,930 --> 00:00:14,610
short interval.

4
00:00:14,690 --> 00:00:20,580
So you should determine the scope and impact on the network that the network management system will

5
00:00:20,580 --> 00:00:27,080
have so as mentioned one of the things you need to think about is polling frequency.

6
00:00:27,080 --> 00:00:32,200
This means how often you're going to pull devices to collect data.

7
00:00:32,240 --> 00:00:37,670
The more often that you polled devices the more granular and the more detailed your statistics are going

8
00:00:37,670 --> 00:00:38,060
to be.

9
00:00:39,070 --> 00:00:45,640
However on the flip side that means that it's going to have a larger impact on your network because

10
00:00:45,640 --> 00:00:48,710
there's more traffic being transmitted on the network.

11
00:00:48,880 --> 00:00:53,320
The network management system is polling the network on a more frequent basis which puts more traffic

12
00:00:53,320 --> 00:00:54,480
on the network.

13
00:00:54,760 --> 00:01:00,280
And in addition there's a higher load on your network devices because they have to reply back to the

14
00:01:00,280 --> 00:01:06,640
network management station with information that you're trying to gather from that network device.

15
00:01:06,640 --> 00:01:14,830
So more polling equates to more detail and quicker detection of issues but it puts a higher load on

16
00:01:14,830 --> 00:01:18,790
both the network and the devices in your network.

17
00:01:18,790 --> 00:01:25,600
Now once again the advantage of more polling is that you have more detail and it's quicker to detect

18
00:01:25,600 --> 00:01:26,660
issues.

19
00:01:26,770 --> 00:01:33,770
However on the flip side it can create extra traffic on the network now most modern network management

20
00:01:33,770 --> 00:01:41,450
systems and a lot of modern network devices can handle a larger amount of network management traffic

21
00:01:41,690 --> 00:01:43,980
than was possible in the past.

22
00:01:44,060 --> 00:01:49,760
The processing power of your network devices and the speed of interfaces are a lot greater today than

23
00:01:49,760 --> 00:01:56,870
they were a few years ago so it's not as much of a problem as it may have once been this is another

24
00:01:56,870 --> 00:02:02,330
reason that you want to leverage both event based network management protocols as well as query based

25
00:02:02,390 --> 00:02:10,310
network management protocols event based protocols once again offer real time unsolicited feedback from

26
00:02:10,310 --> 00:02:12,080
your network devices.

27
00:02:12,080 --> 00:02:18,800
A road is going to inform the network management station when an interface goes down with polling based

28
00:02:18,800 --> 00:02:20,710
or query based protocols.

29
00:02:20,720 --> 00:02:28,580
There's a query and response in other words the mess is querying a device for information and it's responding

30
00:02:28,610 --> 00:02:37,030
or answering back to that query now less polling equates to less bandwidth utilization.

31
00:02:37,090 --> 00:02:44,560
But in addition equates to smaller storage requirements which is another important thing to think about.

32
00:02:45,600 --> 00:02:50,610
If you're collecting a large amount of data you need to think about your disk requirements for your

33
00:02:50,610 --> 00:02:58,530
sequel server which is where NPM stores data large amounts of data equate to bigger scale databases

34
00:02:58,770 --> 00:03:01,110
which in turn means that you need more disk space.