Loosing connectivity after setting PORT1 IP on Forti VM

[satish_verma1999]

Hi

I am new to fortigate applications. I need to use VM as FW for one of my customer.

I am trying the same using evaluation version. but facing a issue. Pls help me to resolve the same.

My setup:

1. Fortigate VM with 8 interfaces hosted on openstack.

Issue:

1. After running following commands on port1 (which is mgmt port to access VM, 10.109.190.134 )

config system interface edit "port1"

set mode static set ip 10.109.190.134 255.255.255.0 set allowaccess ping https ssh snmp fgfm

set secondary-IP disable

The connectivity to VM goes. Unable to understand the issue. Pls help.

Rgds

Satish

[lobstercreed]

I believe the evaluation version does not allow HTTPS for admin access, so that may be your issue.  If you try to make the change in the GUI I think it warns you/doesn't let you, but it's been a long time since I've played with it.

EDIT:  See here for more info about trial limitations.

https://docs.fortinet.com/vm/vmware-nsx-t/fortigate/6.0/about-fortigate-for-vmware-nsx-t/6.0.4/99217...

[Yurisk]

As @lobstercreed said you cannot use HTTPS to manage the firewall that works on default 15 days evaluation license, you have to use HTTP or SSH:

config sys int

edit port1

set allowaccess http ssh ping snmp fgfm

set mode static set ip 10.109.190.134 255.255.255.0

next

[satish_verma1999]

Just noticed that the VM gets unreachable after executing the highlighed line "set secondary-IP disable" under "port1".

edit "port1" set mode static set ip 10.109.190.134 255.255.255.0 set allowaccess ping https ssh snmp fgfm set description "OM Network1" set alias "OM_Network_Cluster" set lldp-transmission vdom set secondary-IP disable

Just after this command VM becomes unreachable. Why it is causing issue?

Also this is not evaluation version but using the VM with 1cpu and 1GB RAM for testing purpose before production.

Pls advise.

Satish

[Yurisk]

Then why do you put this command if it gets unreachable after this ?? :)