1
00:00:01,110 --> 00:00:06,030
Before you rush out and deploy a network management system in a production environment.

2
00:00:06,030 --> 00:00:12,080
Think about network management planning in a lab such as with genius 3.

3
00:00:12,120 --> 00:00:18,470
This is perhaps not as important but it's very important when doing this in the real world network management

4
00:00:18,470 --> 00:00:27,090
planning includes translating business requirements into monitoring needs thresholds and Network Performance

5
00:00:27,090 --> 00:00:35,020
Monitor or NPM configurations other things to consider with network management planning include building

6
00:00:35,020 --> 00:00:42,190
and leveraging reports that meet the needs of the various stakeholders as well as determining and monitoring

7
00:00:42,880 --> 00:00:46,390
scope and impact on the network.

8
00:00:46,420 --> 00:00:54,100
And don't forget about the network topology having an impact on the actual monitoring system translating

9
00:00:54,100 --> 00:01:01,840
business requirements means doing things such as surveying key stakeholders and departments for their

10
00:01:01,840 --> 00:01:04,650
monitoring and reporting needs.

11
00:01:04,650 --> 00:01:10,920
It also means documenting goals for your network management system and this really needs to be stressed.

12
00:01:10,950 --> 00:01:17,770
It's very important that you document the goals of your network management system otherwise how do you

13
00:01:17,770 --> 00:01:24,860
determine if the network management system deployment has achieved what you set out to do.

14
00:01:25,060 --> 00:01:30,530
An organization may have the goal of increasing the availability of the network.

15
00:01:31,210 --> 00:01:38,290
However if you don't document those goals and don't base line your network before you deploy your network

16
00:01:38,290 --> 00:01:44,740
management system how will you determine if the network management system has had a positive effect

17
00:01:45,220 --> 00:01:53,660
on the network and what it was originally intended to do it's important that your goals be documented

18
00:01:53,660 --> 00:01:59,060
before you deploy and in addition make sure that you have a baseline of the network.

19
00:01:59,060 --> 00:02:04,820
In other words you have an indication of what the network looks like in its current form before you

20
00:02:04,820 --> 00:02:06,620
deploy the network management system.

21
00:02:07,790 --> 00:02:14,450
If you don't do that how will you know three months from today or six months from today whether the

22
00:02:14,570 --> 00:02:21,410
network management system has had a positive effect on the network and has accomplished what it was

23
00:02:21,410 --> 00:02:23,310
originally intended to do.

24
00:02:24,190 --> 00:02:27,830
Key measures also include things like data granularity.

25
00:02:28,060 --> 00:02:34,400
In other words how granular or detailed should the data be that you're collecting.

26
00:02:34,450 --> 00:02:40,720
For example if you are looking at bandwidth utilization on an interface how often are you importing

27
00:02:40,720 --> 00:02:41,950
that data.

28
00:02:41,950 --> 00:02:46,150
Is it once every five minutes or once every five seconds.

29
00:02:46,210 --> 00:02:52,120
If you only look at the bandwidth utilization of an interface every five minutes you may miss a spike

30
00:02:52,390 --> 00:02:54,760
during that five minute interval.

31
00:02:54,760 --> 00:03:01,150
On the flip side if you are collecting data every second you may end up storing a very large amount

32
00:03:01,150 --> 00:03:02,650
of data.

33
00:03:02,710 --> 00:03:08,890
Another thing to keep in mind when translating business requirements into monitoring needs is data retention

34
00:03:09,610 --> 00:03:11,050
data retention means.

35
00:03:11,050 --> 00:03:17,200
How long are you going to keep the data that your network management system collected before it's either

36
00:03:17,200 --> 00:03:20,000
deleted or summarized.

37
00:03:20,100 --> 00:03:27,660
In other words how long are you going to keep detailed records of your network before it's deemed unnecessary

38
00:03:27,660 --> 00:03:29,140
to keep that data.

39
00:03:29,250 --> 00:03:35,400
Or at least that level of detail of the data other things you're going to want to do in documenting

40
00:03:35,400 --> 00:03:43,440
these monitoring needs is to define both the needs of the teams involved in projects and the thresholds

41
00:03:44,000 --> 00:03:51,810
now what thresholds mean is the level at which you want to start seeing errors states or paying more

42
00:03:51,810 --> 00:04:00,450
attention if an interface is running at 25 percent utilization and then goes up to 50 percent utilization.

43
00:04:00,570 --> 00:04:07,560
You may not want to be notified of that but when it goes to 90 percent utilization you may want to be

44
00:04:07,560 --> 00:04:11,090
informed that something's happened on your network.

45
00:04:11,340 --> 00:04:18,270
So you need to decide the thresholds before you get notified of possible problems on your network.

46
00:04:18,330 --> 00:04:25,020
This becomes important when you build your alerts and configure the different reports available in NPM

47
00:04:25,680 --> 00:04:32,130
NPM of course has many options and settings that you can change based on your network as well as your

48
00:04:32,130 --> 00:04:33,390
business requirements.