1
00:00:01,060 --> 00:00:07,689
To start Kiwi Syslog server just click, start Kiwi Syslog server like you would

2
00:00:07,689 --> 00:00:09,460
any other Windows application.

3
00:00:11,670 --> 00:00:15,240
In this case, I want to continue using the trial, so I'm going to click close.

4
00:00:16,910 --> 00:00:21,650
Now, notice under display there are various options, display 1

5
00:00:22,950 --> 00:00:24,090
up to 24.

6
00:00:25,480 --> 00:00:28,420
I'm going to leave it as display 00 the default

7
00:00:30,170 --> 00:00:31,910
but notice in the RFC

8
00:00:33,340 --> 00:00:40,840
we have what are called facilities and severity values. So facilities and severity values are not normative

9
00:00:40,840 --> 00:00:47,980
but are often used, they are described in the following tables for information purposes only, facility values

10
00:00:47,980 --> 00:00:51,400
values must be in the range 0 to 23 inclusive.

11
00:00:52,090 --> 00:00:57,880
This allows you to filter your Syslog messages, so as an example kernel

12
00:00:57,880 --> 00:01:00,300
messages could use numerical code

13
00:01:00,310 --> 00:01:08,850
0 mail systems could use 2, user-level messages 1 FTP 11 and so forth and so on.

14
00:01:09,490 --> 00:01:17,620
So if you are collecting Syslog messages from many devices, you may want to filter your Syslog messages

15
00:01:17,620 --> 00:01:19,890
based on a facility.

16
00:01:20,680 --> 00:01:22,810
For now, I'm just going to set it at the default.

17
00:01:24,130 --> 00:01:25,330
Now on this PC, 

18
00:01:27,170 --> 00:01:33,620
I'm using an IP address of 192.168.1.108 and the router is configured with

19
00:01:33,620 --> 00:01:36,590
an IP address of 192.168.1.254.

20
00:01:37,720 --> 00:01:45,870
I've connected it to FastEthernet 1/0 on this router, so on router 1 interface f1/0.

21
00:01:46,810 --> 00:01:53,230
So I'm going to specify an IP address of 192.168.1.254 the default

22
00:01:53,230 --> 00:01:57,520
gateway as configured on the PC.

23
00:01:59,500 --> 00:02:06,520
Now, that overlaps with an IP address used to connect to the outside world, so shut that interface

24
00:02:06,520 --> 00:02:10,060
down, go back onto f1/0, 

25
00:02:11,250 --> 00:02:13,020
configure the IP address.

26
00:02:14,270 --> 00:02:15,290
Can it ping

27
00:02:16,950 --> 00:02:17,730
the server?

28
00:02:18,810 --> 00:02:23,700
At the moment, not that I forget the obvious, yes, I did.

29
00:02:24,630 --> 00:02:27,990
So interface f1/0 no shut, 

30
00:02:30,250 --> 00:02:31,060
try again,

31
00:02:33,070 --> 00:02:34,540
I can ping the server now.

32
00:02:35,780 --> 00:02:39,500
On the PC ping, 192.168.1.254,

33
00:02:41,070 --> 00:02:44,070
can it ping router 2 loopback?

34
00:02:44,130 --> 00:02:45,120
Yes, it can.

35
00:02:47,790 --> 00:02:56,790
So this server can ping the loopback of router 2 which is being advertised through OSPF. I'll remove this

36
00:02:56,790 --> 00:02:59,460
link for now because we're not using

37
00:03:01,190 --> 00:03:07,690
the cloud, so my network looks as follows, I've got my Syslog server and my two routers.

38
00:03:08,450 --> 00:03:10,250
So now let's configure Syslog.