Technical Tip: How to centrally configure multiple FortiExtender devices controlled by FortiGate with the appropriate dataplan for the specific SIM inserted
| Description | This article describes how to create a central configuration in FortiManager that will ultimately associate the appropriate dataplan entry for the specific SIM card inserted in a FortiExtender device managed via the Extension Controller in the FortiGate controller.
The FortiExtender device integrated as FortiGate WAN extension will have a single SIM card inserted, and this SIM card will be from the carrier with better coverage for the specific location where FortiGate and FortiExtender devices are deployed. |
| Scope | FortiExtender v7.6 (managed through FortiGate), FortiGate running FortiOS v7.4.9, and FortiManager v7.4.8. |
| Solution | In deployment scenarios where multiple FortiExtender devices are deployed in different geographical locations and hence have different signal strengths available for different mobile carriers, there is a requirement to provide a configuration that can adapt to the mobile carrier associated with the SIM card inserted in the FortiExtender device.
In this kind of scenario, usually the FortiExtender devices are integrated as FortiGate WAN extension, and when dealing with massive deployments, both the controller FortiGate and the FortiExtender devices are ultimately managed centrally from FortiManager.
For reasons of specificity, a FortiExtender-511F (4G/5G) is considered in this article. This model supports a single modem with dual SIM, and the supported SIM card is in Micro SIM (3FF) only.
FortiExtender is already pre-defined with regular carriers, and hence it already contains the corresponding MCC and MNC codes for those pre-defined carriers. However, if the SIM carrier MCC and MNC are not part of the pre-defined list, then LTE may not work on FortiExtender.
The second article in the 'Related documents' section in this article mentions how to use the 'config carrier' and 'config lte simmap' FortiExtender CLI commands for declaring a carrier that is not pre-defined in the FortiExtender.
Having the carrier correctly defined is a requirement for the different dataplans that will be created to be operational.
In this scenario, where the configuration is managed centrally from FortiManager, declaring the specific carriers locally on each FortiExtender is not an option, and hence an alternative approach should be used instead.
The 'execute extender lte-carrier add' and 'execute extender lte-simmap add' CLI commands available in the FortiOS CLI for the FortiGate controller fit that purpose.
execute extender lte-carrier add <FEX-serial-number> <carrier-1>
These commands can be included in a FortiManager CLI script, allowing for the push of this configuration to all FortiExtender devices through the FortiGate controller devices for each of those FortiExtender devices.
Once this configuration is deployed to all FortiExtender devices, then it is possible to reference those carriers in the 'config extension-controller dataplan' configuration section:
config extension-controller dataplan
config extension-controller extender-profile
config extension-controller extender
With this central configuration, all FortiExtender devices will select the configuration based on the carrier corresponding to the SIM card inserted, where the SIM card will be for the mobile carrier with better coverage in that specific location.
Related articles: |
