Fortinet Document Library

Version:


Table of Contents

FortiGate-VM on OpenStack

Use Case: Automatically Updating Dynamic Addresses Using Fabric Connector

Resources

Upgrade Path Tool
6.0.0
Download PDF
Copy Link

Completing the FortiGate-VM network configuration

From each FortiGate-VM instance CLI, enter the following commands to change the FortiGate-VM interfaces from DHCP to static, add IP addresses, and add a static route. The IP addresses assigned to the interfaces must be on the subnets of the networks that the interfaces are connected to.

The example shows the fgt-vm-1 configuration. The fgt-vm-2 configuration would be the same except for the interface IP addresses.

config system interface

edit "port1"

set mode static

set ip 172.31.0.3 255.255.255.0

set allowaccess ping https ssh http

next

edit "port2"

set mode static

set ip 172.32.0.9 255.255.255.0

set allowaccess ping https ssh http

next

edit "port3"

set mode static

set ip 172.33.0.4 255.255.255.0

set allowaccess ping https ssh http

end

 

config router static

edit 1

set gateway 172.31.0.1

set device "port1"

end

Resources

Completing the FortiGate-VM network configuration

From each FortiGate-VM instance CLI, enter the following commands to change the FortiGate-VM interfaces from DHCP to static, add IP addresses, and add a static route. The IP addresses assigned to the interfaces must be on the subnets of the networks that the interfaces are connected to.

The example shows the fgt-vm-1 configuration. The fgt-vm-2 configuration would be the same except for the interface IP addresses.

config system interface

edit "port1"

set mode static

set ip 172.31.0.3 255.255.255.0

set allowaccess ping https ssh http

next

edit "port2"

set mode static

set ip 172.32.0.9 255.255.255.0

set allowaccess ping https ssh http

next

edit "port3"

set mode static

set ip 172.33.0.4 255.255.255.0

set allowaccess ping https ssh http

end

 

config router static

edit 1

set gateway 172.31.0.1

set device "port1"

end