WEBVTT

1
00:00.000 --> 00:03.040
In this video, I'd like to do a couple just quick tests regarding the network

2
00:03.040 --> 00:04.320
topology and also

3
00:04.320 --> 00:09.180
walk you through access to the 40 Analyzer. Now, the 40 Analyzer itself can be

4
00:09.180 --> 00:10.080
deployed as an

5
00:10.080 --> 00:14.520
appliance or it can be deployed as a virtual machine. There's platforms as far

6
00:14.520 --> 00:15.200
as virtual

7
00:15.200 --> 00:20.450
machines are concerned for Microsoft and for VMware and others. And in my

8
00:20.450 --> 00:21.440
environment, in my lab

9
00:21.440 --> 00:26.470
environment, I've deployed this on an ESXi host. That's a host running VMware's

10
00:26.470 --> 00:28.160
virtualization software.

11
00:28.160 --> 00:31.660
And for its management interface, I put it on my management network, which is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.160 --> 00:31.660
And for its management interface, I put it on my management network, which is

12
00:31.660 --> 00:35.040
192.168.1.0 with

13
00:35.040 --> 00:39.850
the slash 24. And it's IP address I gave it is .81. However, the challenge is

14
00:39.850 --> 00:40.800
that when you get a

15
00:40.800 --> 00:45.300
brand new 40 Analyzer, it's very likely not going to have the IP address that

16
00:45.300 --> 00:46.400
you want it to have.

17
00:46.400 --> 00:50.380
Also, that 40 Analyzer is probably not going to have the correct default

18
00:50.380 --> 00:51.680
gateway information.

19
00:51.680 --> 00:55.950
It may have the default DNS servers to use, which would be fine. But to get it

20
00:55.950 --> 00:56.720
up and running

21
00:56.720 --> 01:00.790
and connected up to the cloud to Fortinet so it can get licensed and validated,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:56.720 --> 01:00.790
and connected up to the cloud to Fortinet so it can get licensed and validated,

22
01:00.790 --> 01:01.360
it's going to need to

23
01:01.360 --> 01:05.920
have a workable IP address with a gateway in the case of a private RFC 19

24
01:05.920 --> 01:07.120
address like this.

25
01:07.120 --> 01:11.230
It's going to need to have NAT as well, network address translation. And also,

26
01:11.230 --> 01:11.600
as I mentioned,

27
01:11.600 --> 01:16.060
it needs DNS. It can do name resolution to connect to home to connect up to the

28
01:16.060 --> 01:17.040
Fortinet servers.

29
01:17.040 --> 01:21.010
So what I would like to do is I would like to go ahead and show you this 40

30
01:21.010 --> 01:22.160
Analyzer that I have

31
01:22.160 --> 01:26.230
where it's currently being deployed in VMware. And then I'd like to also walk

32
01:26.230 --> 01:26.960
you through

33
01:26.960 --> 01:31.520
how we can see from the command line interface what the IP address is and also
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:26.960 --> 01:31.520
how we can see from the command line interface what the IP address is and also

34
01:31.520 --> 01:32.560
what the gateway is

35
01:32.560 --> 01:36.220
and the DNS information is. And that way, we can change it should we need to

36
01:36.220 --> 01:36.960
and we will,

37
01:36.960 --> 01:41.040
especially the default gateway so that we can have this 40 Analyzer connect out

38
01:41.040 --> 01:41.840
to the public

39
01:41.840 --> 01:45.980
Internet. So I'm going to use a terminal emulator called secure CRT. And I have

40
01:45.980 --> 01:47.360
an entry right here

41
01:47.360 --> 01:53.680
that's going to use SSH to connect to 192.168.1.81, which is the 40 Analyzer I

42
01:53.680 --> 01:54.640
have set up in my lab

43
01:54.640 --> 01:58.420
environment. I also through scripting told it to submit the username and

44
01:58.420 --> 02:00.320
password, which is admin
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:58.420 --> 02:00.320
password, which is admin

45
02:00.320 --> 02:04.370
with the password I'm using on this device. So the first thing I did is I

46
02:04.370 --> 02:06.240
configured port one

47
02:06.240 --> 02:09.930
as part of the interfaces and gave it the IP address I needed in my environment

48
02:09.930 --> 02:10.800
. So to do that,

49
02:10.800 --> 02:14.930
I did a config system interface. I then typed in edit port one. That's the

50
02:14.930 --> 02:16.240
first logical network

51
02:16.240 --> 02:19.910
interface on this virtual machine, the 40 Analyzer. And then here I'm just

52
02:19.910 --> 02:21.280
going to show you the

53
02:21.280 --> 02:25.710
current configuration that I have, which is for port one, the IP address is set

54
02:25.710 --> 02:26.560
to this address

55
02:26.560 --> 02:31.910
ending in dot 81 on my management network. I've also set allow access for ping,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:26.560 --> 02:31.910
ending in dot 81 on my management network. I've also set allow access for ping,

56
02:31.910 --> 02:33.840
HTTPS SSH and HTTP.

57
02:33.840 --> 02:37.200
But you know what, I really don't need HTTP. So let me go ahead and take that

58
02:37.200 --> 02:38.080
off. I'll do an

59
02:38.080 --> 02:42.010
edit port one. Oh, I'm already in port one. So I'm going to go ahead and do a

60
02:42.010 --> 02:43.280
set allow access for

61
02:43.280 --> 02:48.240
ping HTTPS and SSH only. So I'll copy and paste that press enter. And then we

62
02:48.240 --> 02:48.880
'll do a show just

63
02:48.880 --> 02:52.750
to make sure that took because I don't need HTTP. I'm going to use just HTTPS

64
02:52.750 --> 02:53.920
for the GUI. So the

65
02:53.920 --> 02:58.670
default IP address on most fortunate devices is going to be 192, once state 1.

66
02:58.670 --> 03:00.000
99. And so in my
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:58.670 --> 03:00.000
99. And so in my

67
03:00.000 --> 03:03.500
topology, I wanted to be 81. And that's why I said it here. So let me go ahead

68
03:03.500 --> 03:04.560
and clear the screen.

69
03:04.560 --> 03:07.380
The next thing I chose to do, which I didn't have to because the defaults were

70
03:07.380 --> 03:08.640
going to be fine is

71
03:08.640 --> 03:14.510
I specified DNS using 8888. And that's Google. And the secondary is from Cloud

72
03:14.510 --> 03:15.840
flare. But you could

73
03:15.840 --> 03:20.180
just take the defaults and that would work. And then finally, I also set up my

74
03:20.180 --> 03:21.360
routing. So in my

75
03:21.360 --> 03:24.260
environment, my default gateway for my management network going out to the

76
03:24.260 --> 03:25.920
public internet is 192

77
03:25.920 --> 03:31.620
once state 1.1. So I set up the routing to tell it specifically the correct
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:25.920 --> 03:31.620
once state 1.1. So I set up the routing to tell it specifically the correct

78
03:31.620 --> 03:33.200
default gateway to use.

79
03:33.200 --> 03:36.610
Because if you don't have a default route, the 40 analyzer can't get off the

80
03:36.610 --> 03:37.360
local network and

81
03:37.360 --> 03:41.600
won't be able to reach out to the cloud for getting the license validated. Also

82
03:41.600 --> 03:42.400
, my experience has

83
03:42.400 --> 03:45.810
been with the 40 analyzer. If you haven't deployed a 40 analyzer yet and you

84
03:45.810 --> 03:47.120
want to download it,

85
03:47.120 --> 03:51.360
there's an option for a trial license. I think it's good for some period of

86
03:51.360 --> 03:52.240
days where you can work

87
03:52.240 --> 03:55.220
with it and play with it just to get comfortable with it as well. That would

88
03:55.220 --> 03:56.320
require setting up

89
03:56.320 --> 04:00.140
an account up at Fortinet and then downloading the software and then deploying
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
03:56.320 --> 04:00.140
an account up at Fortinet and then downloading the software and then deploying

90
04:00.140 --> 04:01.040
it and then choosing

91
04:01.040 --> 04:04.980
the option for using a trial license. So for my 40 analyzer, if I use the

92
04:04.980 --> 04:06.800
command GetSystemStatus,

93
04:06.800 --> 04:10.720
I added some licenses to it so I could demonstrate the things I needed to. And

94
04:10.720 --> 04:11.600
currently I'm using

95
04:11.600 --> 04:17.100
version 474, which is a mature version. There was also an option of using a

96
04:17.100 --> 04:18.320
feature version,

97
04:18.320 --> 04:22.080
but sometimes those have bugs. It's also specifying here the maximum number of

98
04:22.080 --> 04:22.960
administrative domains

99
04:22.960 --> 04:27.200
we can set up as five and it also shows here that the current license is valid.

100
04:27.200 --> 04:28.320
So if we confirm the

101
04:28.320 --> 04:33.360
IP address once again, it's 192.168.1.81. Let's go ahead and open up a browser
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
04:28.320 --> 04:33.360
IP address once again, it's 192.168.1.81. Let's go ahead and open up a browser

102
04:33.360 --> 04:34.000
for my management

103
04:34.000 --> 04:37.880
computer and connect to it via GUI. So that's what I've done right here. I'm in

104
04:37.880 --> 04:38.480
fullscreen mode,

105
04:38.480 --> 04:44.910
so I connected to https colon slash 192.168.1.81. And I'm going to specify the

106
04:44.910 --> 04:45.840
using a password I

107
04:45.840 --> 04:50.570
have for this device, which is admin and then my lab password and click on

108
04:50.570 --> 04:51.760
login. I also took

109
04:51.760 --> 04:55.920
a moment to chose this cute cat background for it and that's optional as well.

110
04:55.920 --> 04:56.320
You don't have to

111
04:56.320 --> 04:59.560
you can take the default. It works just as well. So I'll click on login and

112
04:59.560 --> 05:00.560
here we are directly
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
04:59.560 --> 05:00.560
here we are directly

113
05:00.560 --> 05:06.160
connected to the 40 analyzer interface. So just to confirm the two options for

114
05:06.160 --> 05:07.040
connecting initially

115
05:07.040 --> 05:11.680
to the 40 analyzer would be through the CLI, which may be through a console

116
05:11.680 --> 05:12.960
cable. If you're going to

117
05:12.960 --> 05:17.600
a physical device or through VMware or Hyper-V, it could be a console provided

118
05:17.600 --> 05:18.880
by that virtualized

119
05:18.880 --> 05:21.780
environment. And then once you have the IP address all set up the way you need

120
05:21.780 --> 05:22.640
to and the default

121
05:22.640 --> 05:26.540
gateway setup, we could then go ahead and connect to be a browser to connect to

122
05:26.540 --> 05:27.680
the device. Also,

123
05:27.680 --> 05:30.730
from the GUI here we could verify our settings. So if we get on the system
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
05:27.680 --> 05:30.730
from the GUI here we could verify our settings. So if we get on the system

124
05:30.730 --> 05:31.840
settings and go down

125
05:31.840 --> 05:35.510
to network, this would confirm for us our IP address on port one that I'm

126
05:35.510 --> 05:37.200
currently using and also our

127
05:37.200 --> 05:40.760
DNS information is shown right here as well. If we scroll down here's our

128
05:40.760 --> 05:42.000
default route as well.

129
05:42.000 --> 05:45.830
But once again to get the initial connectivity to the internet and to connect

130
05:45.830 --> 05:46.720
to this device,

131
05:46.720 --> 05:50.720
we'd want to go to the command line interface and specify the IP address as

132
05:50.720 --> 05:51.600
well as the default

133
05:51.600 --> 05:55.760
gateway so that device can be registered.