1
00:00:00,620 --> 00:00:07,670
Understanding network management protocols is an important part of your job as a network engineer and

2
00:00:07,670 --> 00:00:14,270
is also important within the role of doing network management network management protocols are also

3
00:00:14,270 --> 00:00:18,100
a key part of the solar wind's product.

4
00:00:18,110 --> 00:00:26,890
In other words solar winds management tools make use of management protocols to manage network devices.

5
00:00:26,900 --> 00:00:34,610
This video will provide an overview of how network management applications leverage network management

6
00:00:34,640 --> 00:00:35,890
protocols.

7
00:00:35,900 --> 00:00:41,060
We'll also describe the different types of network management protocols that are available and then

8
00:00:41,060 --> 00:00:46,310
explain the most common protocols when discussing network management protocols.

9
00:00:46,310 --> 00:00:50,640
We need to think about three main things before we talk about that.

10
00:00:50,780 --> 00:00:58,280
We'll look at how Orion leverages network management protocols and which types of protocols are leveraged

11
00:00:58,340 --> 00:01:04,430
for different types of monitoring solar wind's Network Performance Monitor does both fault monitoring

12
00:01:04,970 --> 00:01:08,990
as well as performance monitoring for fault management.

13
00:01:09,440 --> 00:01:18,110
Most network management systems including solar winds use ICMP or ping to detect whether a device is

14
00:01:18,110 --> 00:01:19,130
up or down.

15
00:01:19,130 --> 00:01:25,130
It's as simple as the network management system or in a mess sending out a ping request and waiting

16
00:01:25,130 --> 00:01:27,020
for a ping response.

17
00:01:27,020 --> 00:01:32,990
If the ICMP response isn't returned then a mess assumes that the device is done.

18
00:01:33,020 --> 00:01:39,080
Now I know Ryan it works slightly differently in that if a response isn't returned.

19
00:01:39,370 --> 00:01:46,280
Orion places the nodes in a mode warning stage which means that Orion is going to do a fost pull of

20
00:01:46,280 --> 00:01:55,220
the device to verify that it's really down NPM or Orion by default will monitor the device in a fast

21
00:01:55,220 --> 00:02:00,670
polling mode for 120 seconds before notifying you that the device is down.

22
00:02:00,680 --> 00:02:09,020
This is configurable under advanced settings in the NPM system manager monitoring for faults on sub

23
00:02:09,030 --> 00:02:16,500
elements like interfaces and volumes he's done differently as it's done via is an MP or simple network

24
00:02:16,500 --> 00:02:17,540
management protocol.