1
00:00:08,180 --> 00:00:17,390
There are tons of ways where we can grab information on our systems tell us where we are only at the

2
00:00:17,390 --> 00:00:25,960
beginning but still we can see some valuable information some of it will not mean anything to us currently

3
00:00:26,540 --> 00:00:33,490
but later on as we progress the information will become much more clearer.

4
00:00:33,500 --> 00:00:40,850
We can use the do we interface to grab information using their log and report traffic that is passing

5
00:00:41,270 --> 00:00:49,340
through the different interfaces traffic that is being handled by the 40 gate itself but we can also

6
00:00:49,340 --> 00:00:54,580
use this CLIA the command line to grab some valuable information.

7
00:00:54,650 --> 00:01:07,370
So the first command is the get system status where we can see our version which is currently 6 point

8
00:01:07,400 --> 00:01:17,300
0 point to the build number we can see if our virus or IP s database are up to date.

9
00:01:17,300 --> 00:01:20,100
We can also see our hostname.

10
00:01:20,360 --> 00:01:29,210
We can see if we are using a hard disk to log any event on our 48 and there are devices that come with

11
00:01:29,210 --> 00:01:37,590
the hardest there are devices that stored their logs too as a special device called the 40 analyzer

12
00:01:38,150 --> 00:01:44,550
and there are those devices that use their flash memory for log recording.

13
00:01:44,570 --> 00:01:54,350
We can also see if we are working on in a chain mode in a chain mode is a high availability mode where

14
00:01:54,350 --> 00:01:56,490
we use another 40.

15
00:01:56,490 --> 00:02:04,050
It is a redundant for the gate in case that one of our 48 stops working.

16
00:02:04,100 --> 00:02:10,400
We can both work on both modes whether it is a passive mode or an active mode.

17
00:02:10,400 --> 00:02:15,960
We will look at the high availability modes later on.

18
00:02:16,040 --> 00:02:18,470
You can also look at the system time.

19
00:02:18,470 --> 00:02:28,100
Now let's see the interfaces that we have on our 40 gig so we'll use the show system interface and there

20
00:02:28,100 --> 00:02:28,670
we have it.

21
00:02:28,670 --> 00:02:31,500
We have the different interfaces.

22
00:02:31,550 --> 00:02:39,470
Some of them are already configured such as the when one which has that IP address that subnet mass.

23
00:02:39,590 --> 00:02:44,160
We can see the management protocols that are being used such as P engaged.

24
00:02:44,290 --> 00:02:45,690
Yes SSA.

25
00:02:46,250 --> 00:02:50,870
We can see that that interface is a physical interface.

26
00:02:50,870 --> 00:02:54,470
It is part of the 48 switch board.

27
00:02:54,470 --> 00:03:09,040
There are also virtual interfaces such as villains in other command is the get CIs session list and

28
00:03:09,040 --> 00:03:16,500
that will show us sessions that are being held right now on our 48.

29
00:03:16,540 --> 00:03:20,790
We can see the protocol that is being used.

30
00:03:20,890 --> 00:03:26,140
We can see the source the source of the session itself.

31
00:03:26,140 --> 00:03:35,410
We can see the destination and if we were using the Net we would also see the net that is being used

32
00:03:37,230 --> 00:03:46,350
one of the most used commands is the DAG system where we list the different processes that are running

33
00:03:46,410 --> 00:03:48,050
on your forehead.

34
00:03:48,150 --> 00:03:51,750
So we will use the DAG stop that is the command

35
00:03:54,720 --> 00:04:01,460
let's run it and I'll stop it from showing all the processes.

36
00:04:01,460 --> 00:04:03,860
Now there is the process.

37
00:04:03,880 --> 00:04:08,290
Name there is the process I.D..

38
00:04:08,780 --> 00:04:16,100
If we wish to kill the process we can use the process I.D. later on that is the process status.

39
00:04:16,550 --> 00:04:21,400
S is for sleep R is for running and there are more statuses.

40
00:04:21,650 --> 00:04:31,020
There is the utilization of the CPSU and there is the utilization of the memory.

41
00:04:31,130 --> 00:04:41,930
So whenever you need to troubleshoot an issue that is being caused by high memory utilization or high

42
00:04:42,290 --> 00:04:48,410
utilization check out the different processes that are running on your machine.