Fortinet white logo
Fortinet white logo

Special notes

Special notes

  • For FortiExtender 511F devices, the Telstra modem must connect to an LTE/5G network following the first attach request.

  • For FortiExtender 511F devices, the Telstra modem requires that a PDN be set for each and every LTE data plan.

  • Not all receivers can receive SMS notifications. Be sure to adjust the receiver sequence to ensure that the first receiver always gets SMS notifications.
  • Upon reboot, FortiExtender will try to discover the FortiGate or FortiEdge Cloud that manages it, depending on your existing configuration. Because of this, there might be a short delay before the device reconnects to the FortiGate or FortiEdge Cloud.
  • In order for FortiExtender to forward syslog messages to a remote syslog server, the syslog server and the FortiExtender LAN port must be part of the same subnet.
  • FortiExtender and FortiGate share the same LTE IP in WAN-extension mode. To distinguish local services from FortiGate services, you must configure FortiExtender to use different ports. Otherwise, all traffic to these default services will be sent to FortiExtender locally instead of the FortiGate.

  • For FortiGate-managed FBS and FEX-G/R models, each physical port has an Ethernet interface in the kernel. There is no physical LAN-switch interface. Since FortiExtender does not support VLAN over a softswitch interface, it can't use the LAN as the discovery interface for VLAN WAN-extension mode.

    To resolve this, you can do one of the following:

    • Separate one port (port1, port2, or port3) from the LAN switch.
    • Use the default port4 as the discovery interface.

Special notes

Special notes

  • For FortiExtender 511F devices, the Telstra modem must connect to an LTE/5G network following the first attach request.

  • For FortiExtender 511F devices, the Telstra modem requires that a PDN be set for each and every LTE data plan.

  • Not all receivers can receive SMS notifications. Be sure to adjust the receiver sequence to ensure that the first receiver always gets SMS notifications.
  • Upon reboot, FortiExtender will try to discover the FortiGate or FortiEdge Cloud that manages it, depending on your existing configuration. Because of this, there might be a short delay before the device reconnects to the FortiGate or FortiEdge Cloud.
  • In order for FortiExtender to forward syslog messages to a remote syslog server, the syslog server and the FortiExtender LAN port must be part of the same subnet.
  • FortiExtender and FortiGate share the same LTE IP in WAN-extension mode. To distinguish local services from FortiGate services, you must configure FortiExtender to use different ports. Otherwise, all traffic to these default services will be sent to FortiExtender locally instead of the FortiGate.

  • For FortiGate-managed FBS and FEX-G/R models, each physical port has an Ethernet interface in the kernel. There is no physical LAN-switch interface. Since FortiExtender does not support VLAN over a softswitch interface, it can't use the LAN as the discovery interface for VLAN WAN-extension mode.

    To resolve this, you can do one of the following:

    • Separate one port (port1, port2, or port3) from the LAN switch.
    • Use the default port4 as the discovery interface.