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

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

3
00:00:14,290 --> 00:00:17,980
a key part of the solar wind's product.

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

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

6
00:00:34,660 --> 00:00:35,400
protocols.

7
00:00:35,830 --> 00:00:41,080
Wel'l also described the different types of network management protocols that are available and then

8
00:00:41,080 --> 00:00:46,300
explain the most common protocols.
When discussing network management protocols

9
00:00:46,300 --> 00:00:48,520
We need to think about three main things.

10
00:00:48,970 --> 00:00:56,170
Before we talk about that, we'll look at how Orion leverages network management protocols and which

11
00:00:56,170 --> 00:01:01,030
types of protocols are leveraged for different types of monitoring solutions. Splarwinds

12
00:01:01,030 --> 00:01:08,980
Network Performance Monitor does both Fault monitoring as well as performance monitoring. For fault management

13
00:01:09,370 --> 00:01:17,980
Most network management systems, including solarwinds, use ICMP or PING to detect whether a device

14
00:01:17,980 --> 00:01:18,780
is up or down.

15
00:01:19,030 --> 00:01:25,330
It's as simple as the network management system or NMS sending out a ping request and waiting for

16
00:01:25,330 --> 00:01:26,350
a ping response.

17
00:01:26,950 --> 00:01:33,970
If the ICMP response isn't returned, the NMS assumes that the device is down. Now in Orion

18
00:01:34,000 --> 00:01:42,010
it works slightly differently in that if a response isn't returned, Orion places the nodes in a mode

19
00:01:42,010 --> 00:01:48,850
warning stage, which means that Orion is going to do a fast poll of the device to verify that it's really

20
00:01:48,850 --> 00:01:49,330
down.

21
00:01:49,990 --> 00:01:58,690
NPM or Orion, by default, will monitor the device in a fast polling mode for 120 seconds before it notifies

22
00:01:58,690 --> 00:02:00,070
you that the device is down.

23
00:02:00,670 --> 00:02:06,310
This is configurable under advanced settings in the NPM system manager.

24
00:02:07,470 --> 00:02:14,280
Monitoring for faults on subelements like interfaces and volumes is done differently as it's done via

25
00:02:14,280 --> 00:02:17,520
SNMP or simple network management protocol.