In this video, I'd like to do a couple just quick tests regarding the network
topology and also
walk you through access to the 40 Analyzer. Now, the 40 Analyzer itself can be
deployed as an
appliance or it can be deployed as a virtual machine. There's platforms as far
as virtual
machines are concerned for Microsoft and for VMware and others. And in my
environment, in my lab
environment, I've deployed this on an ESXi host. That's a host running VMware's
virtualization software.
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
And for its management interface, I put it on my management network, which is
192.168.1.0 with
the slash 24. And it's IP address I gave it is .81. However, the challenge is
that when you get a
brand new 40 Analyzer, it's very likely not going to have the IP address that
you want it to have.
Also, that 40 Analyzer is probably not going to have the correct default
gateway information.
It may have the default DNS servers to use, which would be fine. But to get it
up and running
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
and connected up to the cloud to Fortinet so it can get licensed and validated,
it's going to need to
have a workable IP address with a gateway in the case of a private RFC 19
address like this.
It's going to need to have NAT as well, network address translation. And also,
as I mentioned,
it needs DNS. It can do name resolution to connect to home to connect up to the
Fortinet servers.
So what I would like to do is I would like to go ahead and show you this 40
Analyzer that I have
where it's currently being deployed in VMware. And then I'd like to also walk
you through
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
how we can see from the command line interface what the IP address is and also
what the gateway is
and the DNS information is. And that way, we can change it should we need to
and we will,
especially the default gateway so that we can have this 40 Analyzer connect out
to the public
Internet. So I'm going to use a terminal emulator called secure CRT. And I have
an entry right here
that's going to use SSH to connect to 192.168.1.81, which is the 40 Analyzer I
have set up in my lab
environment. I also through scripting told it to submit the username and
password, which is admin WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
password, which is admin
with the password I'm using on this device. So the first thing I did is I
configured port one
as part of the interfaces and gave it the IP address I needed in my environment
. So to do that,
I did a config system interface. I then typed in edit port one. That's the
first logical network
interface on this virtual machine, the 40 Analyzer. And then here I'm just
going to show you the
current configuration that I have, which is for port one, the IP address is set
to this address
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
ending in dot 81 on my management network. I've also set allow access for ping,
HTTPS SSH and HTTP.
But you know what, I really don't need HTTP. So let me go ahead and take that
off. I'll do an
edit port one. Oh, I'm already in port one. So I'm going to go ahead and do a
set allow access for
ping HTTPS and SSH only. So I'll copy and paste that press enter. And then we
'll do a show just
to make sure that took because I don't need HTTP. I'm going to use just HTTPS
for the GUI. So the
default IP address on most fortunate devices is going to be 192, once state 1.
99. And so in my WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
99. And so in my
topology, I wanted to be 81. And that's why I said it here. So let me go ahead
and clear the screen.
The next thing I chose to do, which I didn't have to because the defaults were
going to be fine is
I specified DNS using 8888. And that's Google. And the secondary is from Cloud
flare. But you could
just take the defaults and that would work. And then finally, I also set up my
routing. So in my
environment, my default gateway for my management network going out to the
public internet is 192
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
once state 1.1. So I set up the routing to tell it specifically the correct
default gateway to use.
Because if you don't have a default route, the 40 analyzer can't get off the
local network and
won't be able to reach out to the cloud for getting the license validated. Also
, my experience has
been with the 40 analyzer. If you haven't deployed a 40 analyzer yet and you
want to download it,
there's an option for a trial license. I think it's good for some period of
days where you can work
with it and play with it just to get comfortable with it as well. That would
require setting up
an account up at Fortinet and then downloading the software and then deploying WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
an account up at Fortinet and then downloading the software and then deploying
it and then choosing
the option for using a trial license. So for my 40 analyzer, if I use the
command GetSystemStatus,
I added some licenses to it so I could demonstrate the things I needed to. And
currently I'm using
version 474, which is a mature version. There was also an option of using a
feature version,
but sometimes those have bugs. It's also specifying here the maximum number of
administrative domains
we can set up as five and it also shows here that the current license is valid.
So if we confirm the
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
IP address once again, it's 192.168.1.81. Let's go ahead and open up a browser
for my management
computer and connect to it via GUI. So that's what I've done right here. I'm in
fullscreen mode,
so I connected to https colon slash 192.168.1.81. And I'm going to specify the
using a password I
have for this device, which is admin and then my lab password and click on
login. I also took
a moment to chose this cute cat background for it and that's optional as well.
You don't have to
you can take the default. It works just as well. So I'll click on login and
here we are directly WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
here we are directly
connected to the 40 analyzer interface. So just to confirm the two options for
connecting initially
to the 40 analyzer would be through the CLI, which may be through a console
cable. If you're going to
a physical device or through VMware or Hyper-V, it could be a console provided
by that virtualized
environment. And then once you have the IP address all set up the way you need
to and the default
gateway setup, we could then go ahead and connect to be a browser to connect to
the device. Also,
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
from the GUI here we could verify our settings. So if we get on the system
settings and go down
to network, this would confirm for us our IP address on port one that I'm
currently using and also our
DNS information is shown right here as well. If we scroll down here's our
default route as well.
But once again to get the initial connectivity to the internet and to connect
to this device,
we'd want to go to the command line interface and specify the IP address as
well as the default
gateway so that device can be registered.