Directly on the fortigate firewall I would just right click a rule and
select 'clear counters' but I can't figure out how to do it in
fortimanager. This is the only document I could find on it and it
doesn't mention clearing the hit counter.
https://...
I'm playing with another VDOM setup. This time the Root vdom will hold
the primary traffic while a sub vdom will only have an inbound IPSec VPN
connection for remote clients to connect too via forticlient. I've got
the root vdom setup and it's passin...
I know that you can have like VDOM-A and VDOM-B that both have the same
IP space, such as 10.10.0.0/16 when Root is just passing traffic to
physical interfaces. However, can you have Root have the same IP space
as VDOM-A if all traffic runs through r...
Background on environment.Root vdom contains all the physical interfaces
for traffic to the internet and vmware stack. All traffic coming into or
flowing out of the VDOMs has to route through Root. Vdom-A and Vdom-B
share IP schemes, so everything ha...
Quick background on the environment.Root vdom contains all the physical
connections to the VMWare stack and the internet. VDOM A - All internet
bound traffic (inbound or outbound) runs through an intervdom link.
Everything works as expected.I underst...
Fair enough. I don't share policies across my devices but I understand
what you are saying. Will resetting it directly in the FTG cause an "out
of sync" with FortiManager?
According to support "If you don't upgrade within the 7 days access to
the current logs could be restricted and new logs might not be recorded
in the Cloud. Once the upgrade is completed access to the Logs and new
logs will be recorded". So what that...
We got this as well and I'm not very happy about it. I think we only use
FortiCloud "free" for the logging and don't have a "subscription" but
I'm not really sure. My biggest problem is, I can't guarantee that I can
upgrade my firewalls within 7 days...
Just FYI - from the VDOM-A context (which I call 'Bubble') So you can
see it does not matter what context you run the debug in. I see the
traffic in both.