1
00:00:00,450 --> 00:00:06,330
In this lab I've got three Cisco routers running with ingenious three connected to a switch which in

2
00:00:06,330 --> 00:00:09,030
turn has NPM connected to it.

3
00:00:09,060 --> 00:00:10,950
Here's my NPM server.

4
00:00:11,280 --> 00:00:20,810
And as an example I can paying 10 1 101 which is write a 1 on write to one as an example I can top debug

5
00:00:20,840 --> 00:00:25,820
IP ICMP and back on NPM.

6
00:00:26,090 --> 00:00:31,950
When a ping that IP address I'm getting echo replies sent on the Rada.

7
00:00:32,090 --> 00:00:39,620
So the Rada is receiving the ICMP messages from the NPM server.

8
00:00:39,920 --> 00:00:42,810
So log in under nodes.

9
00:00:42,810 --> 00:00:49,040
Cisco I can see that I have three routers currently up.

10
00:00:49,040 --> 00:00:56,760
So as an example right a one with IP address 10 1 101 is shown as up and I can see some information

11
00:00:56,760 --> 00:00:58,800
about that device.

12
00:00:58,980 --> 00:01:06,000
Now ingenious 3 I'm going to start capturing on the link from NPM to the switch.

13
00:01:06,000 --> 00:01:14,480
I'll capture traffic on the switch interface what I'd like to point out is notice ICMP messages from

14
00:01:14,540 --> 00:01:21,530
NPM the server has an IP address of 10 1 100 100.

15
00:01:21,800 --> 00:01:29,660
That's what we're seeing as the source in the why shock capture so echo ping request and then here's

16
00:01:29,660 --> 00:01:32,630
a response from the Rada.

17
00:01:33,020 --> 00:01:38,300
So as an example I could filter for ICMP messages and what we could see.

18
00:01:38,300 --> 00:01:47,150
Here's an example is ICMP message from NPM to write it to and rather to replying.

19
00:01:47,150 --> 00:01:49,380
We can also do a search for S&P.

20
00:01:49,670 --> 00:01:56,410
So in this example we've got an S&P message from NPM to write a three opening that up.

21
00:01:56,480 --> 00:01:59,220
We can see it's a data request message.

22
00:01:59,420 --> 00:02:02,540
It's trying to get this 0 I.D. information.

23
00:02:02,660 --> 00:02:08,480
Here's a response back from the router more response information sent back.

24
00:02:08,480 --> 00:02:14,790
Notice 0 I.D. information in the background NPM is requesting information from the writers.

25
00:02:14,870 --> 00:02:19,850
In this example it's querying wrote it to and wrote it to is responding.

26
00:02:20,000 --> 00:02:23,560
Here it's querying wrote a 3 and so forth and so on.

27
00:02:23,750 --> 00:02:31,520
That information is then displayed in a nice graphical format on the NPM server.

28
00:02:31,760 --> 00:02:37,460
As an example if I click on Write a one I can see information about this device.

29
00:02:37,460 --> 00:02:44,890
I can see that it's up see its IP address see other information including a source object I.D. lost

30
00:02:44,890 --> 00:02:45,430
to boot.

31
00:02:46,100 --> 00:02:54,170
I could even click on the Telnet link and launch a telnet application to telnet directly to the device.