| These steps describe the process of replacing 201E with 101G (Steps apply to other models mentioned above as well). - Both have single modems with, 5 RJ45 eth ports (4 LAN + 1 WAN).Â
- The 101G has a Telit modem.
- The 201E is a Sierra modem (both have 2 sim slots).
- Both the modems are 4G LTE capable models.
- FortiExtender is deployed on FortiGate. There are two modes available:
- wan-extension mode
- lan-extension mode
 Preparation: - Ensure the new FortiExtender firmware is compatible with the version of FOS on the FortiGate.
- Back up the FortiGate configuration.
- Gain console access to the replacement FortiExtender, as is highly recommended.
- Ensure that modem firmware is up to date (preferably on the latest that is available on the support portal).
 There is no way to perform a software 'swap' of the new extender with the old one. The new extender has to be deployed on the FortiGate and has to be reconfigured similar to the old one. But the models are almost similar in functionality and formfactor so the deployment should be straightforward.  Follow the steps below, as per the current deployment:  FortiExtender deployed in wan-extension mode. - If there was any static configuration made in the 201E mode, mimic the same on the 101G model. This can be done by accessing the FortiExtender through a console cable (baud rate 115200) or through its default IP address 192.169.200.99 (using ssh or through https://192.168.200.99).
- Cable the FortiExtender 101G in the exact same way as the existing FortiExtender device. The FortiExtender should discover the FortiGate and should appear on the FortiGate GUI for authorization.
- If the WAN interface on the FortiGate is being used to discover the FortiExtender, remove the cable to the old extender and connect it to the new one. If LAN interface is being used on the FortiGate to discover the FortiExtender, then select or choose a new unused port on the FortiGate for discovery.
- On the FortiGate create a new FortiExtender wan-extension interface which will be used for mapping the new FortiGate’s LTE interface.
- While authorizing the FortiExtender, select the wan-extension deployment mode and assign the new wan-extension interface that was created earlier and save it.
- The FortiExtender should come online on FortiGate (give it a couple of minutes).
- If the old wan-extension interface was an SD-WAN member, include the new FortiExtender wan-extension interface as a member as well.
 Use the following CLI commands to affect the replacement for wan-extension mode:  Replacement steps (managed mode – WAN extension). - Record existing configuration.
 On the FortiGate CLI:  show extender-controller extender
show system interface  Note: - Extender name.
- Serial number.
- Assigned WAN interface.
- SIM/APN settings (if configured via FortiGate).
 - Disconnect Old FortiExtender.
- Physically unplug the old device.
- Remove it from FortiGate:
 config extender-controller extender
  delete <old-extender-name>
end  - Connect the New FortiExtender.
- Power it on.
- Connect to FortiGate.
- Wait 2 - 3 minutes for discovery.
 Check discovery:  diagnose extender-controller extender list  - Authorize the New FortiExtender.
 If it appears as 'unauthorized', run the following configuration:  config extender-controller extender
  edit <new-serial-number>
    set authorized enable
    set mode wan-extension
  next
end  Or authorize it via the GUI:  WiFi & Switch Controller → FortiExtender → Authorize  - Reassign WAN Interface (if needed)
 Check interface binding:  show system interface | grep extender  If required:  config system interface
  edit <wan-interface-name>
    set device-identification enable
    set role wan
  next
end  FortiExtender deployed in Lan-extension mode. For a FortiExtender deployed in lan-extension mode, first ensure that the static config that is currently on the 201E is mimicked on the 101E. Items that are normally configured directly on the FortiExtender include the APN value for LTE connectivity and the FortiGate IP address that the FortiExtender has to reach out to for discovery. Most of the FortiExtenders deployed in lan-extension mode are remotely deployed and discover the FortiGate over LTE or thru the WAN interface, due to which the LTE link has to be up and the remote FortiGate IP address has to be statically configured.  Steps for replacing the 201E with 101G: - Replicate any static configuration on the new device (101G) similar to what is present on the older device (201E).
 config lte plan   edit <carrier>     set apn <apnvalue>  <----- This info is available from the old extender. end  To configure the FortiGate IP address where the FortiExtender has to be discovered, follow the instructions in Multiple static access controller addresses or FQDN. - Insert the sim card (from the older 201E model) into the new FortiExtender and check that the LTE comes up.
- On the FortiGate, the FortiExtender should appear for authorization.
- While authorizing the device, select the 'lan-extension' mode for deployment, similar to what is needed for deploying any FortiExtender in lan-extension mode.
- All the config (IPsec VPN tunnel config, VXLan overlay config etc) is generated on the FortiGate and pushed to the FortiExtender.
- Verify on the FortiGate and FortiExtender that the IPsec tunnel between them is up.
- Create firewall policies on the FortiGate similar to what is present for the existing 201E extender.
 FortiExtender deployed on the FortiEdge Cloud:  Preparation: - Upgrade the 101G device to the latest firmware.
- Ensure that modem firmware is up to date (preferably on the latest that is available on the support portal)
- Register the device under the support portal (support.fortinet.com).
- Login to the FortiEdge Cloud portal and do asset sync for the device to appear under inventory.
- Deploy the 101G device on the FortiEdge Cloud portal in the same network/location as the earlier 201E device. The 101G device has to be deployed as a new device on cloud. New config (profiles, LTE plans, etc) has to be created on the FortiEdge Cloud portal as appropriate for the 101G model. Ensure that the new config mimics the existing config on the 201E that is currently deployed.
Steps: - Configure the APN value on the extender and insert the SIM(login to the device through console access or through its default address 192.168.200.99). Steps provided earlier.
- Verify that the LTE interface comes up and connectivity to internet is present from the device (Try to ping 8.8.8.8 from the CLI of the FortiExtender to verify internet connectivity).
- The extender device should now reach out (on its own) to the FortiEdge Cloud portal and come online.
- The device once it comes online on the cloud should have the config synced/pushed from the cloud to the device.
- If the config is not in sync, try force syncing the config (by selecting 'sync' on the FortiEdge Cloud portal).
 Replacing with 211E with 202F-AM or 211G: The same steps mentioned for 201E applies to this as well. The only difference is that these have different modems and would need the right modem firmware downloaded from the support portal for upgrade before deployed. Just note that 202F-AM has dual modems with potential for holding 2 active LTE connections if needbe. Deployment steps and methods are similar to deploying 101G.  Other related reference links: | 
