1
00:00:00,360 --> 00:00:07,770
So in this example, in our Wireshark capture, we have a MIB 1.3.6.1.2 and so forth and

2
00:00:07,770 --> 00:00:17,610
so on. In the engineer's toolkit, which I've installed on this VM, I've opened up the MIB browser and noticed

3
00:00:17,610 --> 00:00:20,790
one is ISO. So the OID is 1

4
00:00:22,300 --> 00:00:25,870
3 organization, 6

5
00:00:26,830 --> 00:00:31,960
is DOD, so 1.3.6 is ISO ORG DOD.

6
00:00:33,170 --> 00:00:38,210
1 is Internet, 2 is management, so at this point at the moment.

7
00:00:39,150 --> 00:00:46,920
Well I need to choose 1, which is MIB 2, MIB 2 is what we saw in the RFCs.

8
00:00:47,130 --> 00:00:55,290
So notice, MIB 2 this is RFC 1158 which has been obsoleted by RFC 12

9
00:00:55,290 --> 00:00:56,640
13 over here.

10
00:00:58,090 --> 00:01:01,960
So management information base for network management MIB 2.

11
00:01:03,090 --> 00:01:09,360
So that's MIB 2, their system as an example, but what we've got here

12
00:01:10,670 --> 00:01:13,070
is 31, so scrolling down

13
00:01:14,440 --> 00:01:16,050
31 is fMIB

14
00:01:17,560 --> 00:01:19,870
then we've got 1 for objects,

15
00:01:21,210 --> 00:01:25,680
1 for xtable another one for xentry

16
00:01:27,130 --> 00:01:28,420
1 for fPhase

17
00:01:29,600 --> 00:01:35,270
and then we've got a value of 2, so this is the textural name of the interface.

18
00:01:36,660 --> 00:01:42,360
This might be a text name such as LE0 or a simple number such as 1, depending on the interface

19
00:01:42,360 --> 00:01:44,160
naming Syntex of the device.

20
00:01:45,540 --> 00:01:51,570
If we have a look at another 1.3.6.1.2, so if we scroll up

21
00:01:52,970 --> 00:01:54,920
1.3.6.

22
00:01:56,500 --> 00:02:00,310
1.2.1, so we're back on MIB 2

23
00:02:01,910 --> 00:02:07,790
2 interfaces, 2 is IF table, one is an entry,

24
00:02:08,930 --> 00:02:10,070
2 is a description.

25
00:02:11,330 --> 00:02:17,750
So this is the interface description information, so the moral of the story is you can walk the MIB

26
00:02:18,170 --> 00:02:26,050
using the MIB browser in this application to work out what these OID values actually mean or referred to.

27
00:02:27,170 --> 00:02:32,210
Fortunately for us, NPM shows us in a nice graphical format.

28
00:02:32,840 --> 00:02:37,610
So you get information about the device and you also get information about the interfaces.

29
00:02:38,920 --> 00:02:42,310
So shown here in a nice, easy to read format.