| Description |
This article describes how to resolve router ID conflicts that occur when configuring the Secure Private Access (SPA) service on FortiSASE, where the BGP Router ID for POPs is automatically generated within the range of the 'BGP Router ID Subnet.' The ID starts from the first available address x.x.x.1 in the subnet.
In the example, the 'BGP Router ID Subnet.' is 192.168.21.0/24
If the FortiGate Hub is configured with 192.168.21.1 as the Router ID, the POP will display an invalid Router ID in the Hub's BGP debug logs. This results in the POP's BGP status remaining in an 'Idle' state.
|
| Scope | FortiSASE. |
| Solution |
To avoid Router ID conflicts, it is recommended to configure the BGP Router ID on the Hub using the last available address in the 'BGP Router ID Subnet', such as x.x.x.254. This practice ensures that the Router ID does not overlap with those automatically generated for POPs.
Related articles: |
