| Description | This article describes the reason and solution for the message 'No such Peer configured' when using neighbor-group in BGP. |
| Scope | FortiGate. |
| Solution |
neighbor-group configured with the IP address or name with space is not recognized, and hence, the 'No such Peer configured' message shows up in BGP debug.
Example: BGP is configured with neighbor-group name as '192.168.1.0':
config router bgp
config system interface
InternalFGT1 # get router info routing-table connected
BGP peering with 192.168.1.1 will fail, and a debug message is shown below:
InternalFGT1 # BGP: [NETWORK] Accept Thread: Incoming conn from host 192.168.1.1 (FD=27 VRF=0)
InternalFGT1 # get router info bgp summary VRF 0 BGP router identifier 192.168.128.254, local AS number 65412 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
Changing the neighbor-group name from the IP address to word will resolve the issue.
config router bgp
set as 65412
config neighbor-group
edit "one"
set remote-as 65412
next
end
config neighbor-range
edit 1
set prefix 192.168.1.0 255.255.255.0
set neighbor-group "one"
next
end
VRF 0 BGP router identifier 192.168.128.254, local AS number 65412
BGP table version is 1
1 BGP AS-PATH entries
0 BGP community entries
Next peer check timer due in 39 seconds
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.1.0 4 65412 0 0 0 0 0 never Active
192.168.1.1 4 65412 10 7 0 0 0 00:04:42 11
|
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.