Hi Team,
I was trying to edit an existing BGP route-map via FortiManager but cannot save the configuration. I am getting this notification while doing so.
Error: rule/1/set-priority : out of range - prop[set-priority]: value 0 out of range (1,65535).
But I don't see any attribute or priority to set in the route-map configuration dialogue box. Please do let me know what am i missing here.
Warm Regards
Solved! Go to Solution.
Hi @midlajkp888 ,
FortiManager rejects your route-map edit because the hidden field set-priority inside rule 1 is still set to 0, which is outside the current FortiOS valid range 1-65535. The CLI reference confirms that 0 is invalid, so any legacy route-map rule containing set-priority 0 triggers the “value 0 out of range (1,65535)” error you saw in FortiManager.
https://docs.fortinet.com/document/fortigate/7.2.0/cli-reference/556620/config-router-route-map
Clear the value ( unset set-priority ) or assign any number ≥ 1 on the FortiGate CLI, then re-sync; the route-map will save normally in FortiManager.
BR.
If my answer provided a solution for you, please mark the reply as solved it so that others can get it easily while searching for similar scenarios.
CCIE #68781
Hi @midlajkp888 ,
FortiManager rejects your route-map edit because the hidden field set-priority inside rule 1 is still set to 0, which is outside the current FortiOS valid range 1-65535. The CLI reference confirms that 0 is invalid, so any legacy route-map rule containing set-priority 0 triggers the “value 0 out of range (1,65535)” error you saw in FortiManager.
https://docs.fortinet.com/document/fortigate/7.2.0/cli-reference/556620/config-router-route-map
Clear the value ( unset set-priority ) or assign any number ≥ 1 on the FortiGate CLI, then re-sync; the route-map will save normally in FortiManager.
BR.
If my answer provided a solution for you, please mark the reply as solved it so that others can get it easily while searching for similar scenarios.
CCIE #68781
Hi @atakannatak , Thank you very much for the reply. Yes, it was working when tried via CLI.
This is a know issue fixed in 7.4.7:
bug id 1152564, 1047850
https://docs.fortinet.com/document/fortimanager/7.4.7/release-notes/972111/resolved-issues
Indeed. found it that later. Thank for the reply.
Yes, it follows the same logic of @atakannatak's explanation.
User | Count |
---|---|
2534 | |
1351 | |
795 | |
641 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.