Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
StevenT
New Contributor III

Dedicated mgmt out of band for standalone fortigate

Hi,

 

Anyone had done this setup before.

Fortigate firmware 7.2.5

Standalone unit using dedicated mgmt port for these services: syslog, ntp, tacas, ssh, snmp, onboard fgt to fmg.

 

We followed those references below but the one using the vrf and creating additional vdom is not approved by end user. But during the changes of the config(repeated the process for 2 time) for oob setup, these few is working, SSH, SNMP, FortiGate-FortiManager but others is not working(TACACS, syslog, NTP).

 

The NTP is reachable after we assign the IP but 5 seconds later, it become unreachable.

We could ping the NTP server IP. 

 

references we had follow:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-dedicated-mgmt-feature-Out-of-ba... 

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Out-of-band-management-on-standalone-unit-... 

2 REPLIES 2
dbhavsar
Staff
Staff

Hello @StevenT 

 

- So far mgmt interface is not used for any routing purposes, but still you can try disabling ha-direct in the ha settings using CLI.

https://docs.fortinet.com/document/fortigate/6.4.1/administration-guide/375961/routing-data-over-the...

DNB
StevenT
New Contributor III

Hi @dbhavsar 

 

There is no ha configured for this standalone setup.

 

Even though we solved the tacacs+ issue using dedicated management (dmgmt-vdom, which is automatically created when enabling dedicated management) but the syslog and ntp still remain in the root vdom and could not be configure in this dmgmt-vdom.

Anyone in the community had encounter this method?

 

Steven

Labels
Top Kudoed Authors