Hi,I am trying to connect my Fortiweb Manager to a new Fortiweb
installed at a client.The two devices see each other, the local user
created on the customer's fwb dedicated to hookup is ok; but on
"onborading" I get this error:Failed to connect to FW...
On my lab,I licensed the EMS server with a trial license through my
forticloud account, see image below: I noticed that there are only 3
licenses to test the clients.From direct experience does anyone know if
it is possible to get trials for the ztna...
Hi,On Vmware ESXi platform is present a FAZ with version 7.2.4 Premise,
on the vcenter where I am operating the cpu and ram resources are
available I have performed similar operations on other Fortinet vm's
(Fortigate, ect) Under edit settings -> cpu...
Hello everyone,There is some study material on the training institute
portal or here on the Fortinet support page regarding the configuration
and functionality of a Fortigate used as an IDS/IPS probe.I would like
to learn more about this and the admi...
Hi @ssudhakar ,For the 4 points you mentioned I confirm that everything
is ok, I have other devices hooked to my Fortiwebmanager or verified
also local user with which I hook the two devices and it is ok.I would
not like it to fail me because momenta...
Hi @ozkanaltas,I understood the reason why i don't see the ztna trial
license on the ems server.Momentarily we have not yet set up the fabric
connector between EMS server and Fortigate.I guess that is why I do not
see the trial licenses on the ztna c...
Hi,I am just writing to let you know that after hardware upgrade of the
vm hosting FAZ we were able to assign 16 cpu to the machine.As a
precautionary measure, a snapshot of the vm and backup of the FAZ config
had been done.This activity in our case ...
Hi,I inform you that we have found the cause of what was reported.This
limitation is due to the hardware version of the vm hosting the
FAZ.Updates will follow, in the meantime thank you for your supportBest
Regards
