| Solution |
Installing configuration for a FortiGate running v7.4 version, which manages FortiAPs, while the FortiGate is still in a v7.2 ADOM, can fail, due to syntax differences of FortiAP profile in v7.4 ADOM and v7.4 FortiGate.
To be more specific, FortiAP profiles use different bands in v7.2 and 7.4, and the failure happens when pushing these profiles, while central management is enabled.
The error can be similar to the following log ('channel X is not supported') (this is an example - actual results will differ based on FortiAP models, bands, countries, etc):
error radio-1 channel- 1:-999 - channel 1 is not supported. dfs=yes,region=,plat=431F,cnty=US,band=802.11ac,bond=20MHz - channel 1 is not supported. dfs=yes,region=,plat=431F,cnty=US,band=802.11ac,bond=20MHz
or
Post vdom failed:
error radio-2 channel- 36:-999 - channel 36 is not supported. dfs=yes,region=,plat=U231F,cnty=DE,band=,bond=40MHz - (in Template 7622-3) channel 36 is not supported. dfs=yes,region=,plat=U231F,cnty=DE,band=,bond=40MHz
To overcome this issue, three workarounds can be used:
- Upgrading ADOM to v7.4 if Centralized Management for FortiAP is enabled in an ADOM.
- Disabling central management for FortiAP, creating new FortiAP profiles/templates to be assigned to the v7.4/v7.2 FortiGate and its FortiAPs." This can be least option in case central AP management is required "
- Using a CLI/Jinja script to override the band configuration and then install , This will be most convenient option until ADOM upgrade is performed to mitigate the syntax mismatch.
For example, a CLI template can be used to override the band configuration. Refer to the below CLI template as an example (It needs to be changed based on configuration and FortiAP profile):
config wireless-controller wtp-profile
edit "FAP431F-default"
config radio-1
set band 802.11b 802.11g 802.11n-2G
end
config radio-2
set band 802.11a 802.11n-5G 802.11ax-5G 802.11ac-5G
end
next
end
- Assign the CLI template to the FortiGates managing FortiAPs.
- On the next install, FortiManager will push this change along with the configuration present in the FortiAP Template.
- The CLI template has precedence over all other configurations in FortiManager.
|
