1
00:00:00,450 --> 00:00:09,510
It's very important that you understand maps or management information bases or I.D. or object identifiers

2
00:00:10,080 --> 00:00:16,170
and performance counters within your role as a network manager and also in working with network management

3
00:00:16,170 --> 00:00:17,590
applications.

4
00:00:17,880 --> 00:00:23,270
With regards to understanding network protocols there are three key terms to understand.

5
00:00:23,370 --> 00:00:26,300
Firstly maps or management information bases.

6
00:00:26,790 --> 00:00:33,380
Secondly OJD or object identifiers and performance counters or PERF Mohn.

7
00:00:33,480 --> 00:00:40,820
Now in a lot of conversations network engineers use that term map and OED interchangeably.

8
00:00:40,860 --> 00:00:43,730
However it's important to make a distinction.

9
00:00:43,980 --> 00:00:51,860
A Meb is a larger entity than an I.D. and an I.D. is included within a mob.

10
00:00:51,930 --> 00:01:00,390
A mob is a database used for managing entities in a network using protocol such as S and P objects in

11
00:01:00,390 --> 00:01:08,970
the mob are defined using abstract syntax notation or SSN and the database is structured as a hierarchical

12
00:01:08,970 --> 00:01:11,220
database or tree structure.

13
00:01:11,250 --> 00:01:20,370
Each entry in the mob is addressed through an I.D. So as an example if a network manufacturer wanted

14
00:01:20,370 --> 00:01:26,850
to create a mob for pulling environmental statistics on a rota the writer manufacturer would include

15
00:01:26,850 --> 00:01:33,210
a mob with many different types of variables and statistics which would give you a total view of that

16
00:01:33,210 --> 00:01:41,250
type of statistic for the device was an I.D. would be used for polling a specific interfaces an example

17
00:01:41,850 --> 00:01:47,520
with a specific object identifier and that's where the term I.D. comes from.

18
00:01:47,550 --> 00:01:54,330
Here's an Irish Odyssey discussing the management information base or mob for network management of

19
00:01:54,330 --> 00:01:56,730
DCP IP based internets.

20
00:01:56,940 --> 00:02:07,140
This Irish Sea obsolete or if sea level 58 and it defines the second version of the mob to for use with

21
00:02:07,140 --> 00:02:11,410
network management protocols in a TCB IP network.

22
00:02:11,640 --> 00:02:19,440
The RF she explains in a lot of detail about some of the groups that are available in them including

23
00:02:19,440 --> 00:02:26,190
as an example the system group this contains four objects which will often see in network management

24
00:02:26,190 --> 00:02:33,960
environments CIS contact CIS name CIS location and CIS services and thus provides contact administrative

25
00:02:34,320 --> 00:02:41,070
information regarding the managed node interfaces group contains information about interfaces as an

26
00:02:41,070 --> 00:02:42,300
example.

27
00:02:42,310 --> 00:02:48,170
Now you know why shock capture information was being sent back from a managed device.

28
00:02:48,390 --> 00:02:55,230
In this case right to to the network management station and notice it includes information such as Wonder

29
00:02:55,250 --> 00:03:04,920
three or six to one or two and so forth doing a search in this RF seem to we can see information with

30
00:03:04,920 --> 00:03:12,270
that hierarchy of values one or three to six that wandered for as an example in the obsolete ID version

31
00:03:13,270 --> 00:03:22,060
of this RF C so the one that this or if C replaced we could search for information and it would include

32
00:03:22,060 --> 00:03:30,210
information such as this ISO organization Deo D Internet management system system descriptor.

33
00:03:30,490 --> 00:03:39,190
So this is appended to an instance sub identifier of 0 a value like this indicates system descriptor.

34
00:03:39,190 --> 00:03:52,730
So in this example notice the hierarchy 1 3 6 1 2 1 and then it changes to other values 2 to now it's

35
00:03:52,730 --> 00:03:56,860
very difficult to look for information in an RFP such as this.

36
00:03:57,200 --> 00:04:04,370
So it's easier to look at a browser for specific Meb or I.D. information so rather than trying to work

37
00:04:04,370 --> 00:04:08,900
this out you could use a map browser to see what this actually means.
