FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
nithincs
Staff & Editor
Staff & Editor
Article Id 378753
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.


Change the neighbor-group name to a specific word or name without space.

 

Example:

BGP is configured with neighbor-group name as '192.168.1.0':

 

config router bgp
    set as 65412
        config neighbor-group
            edit "192.168.1.0" <-----
                set remote-as 65412
            next
        end


config neighbor-range
    edit 1
    set prefix 192.168.1.0 255.255.255.0 <----- Prefix should match incoming BGP communication from 192.168.1.1 to 192.168.1.255.
    set neighbor-group "192.168.1.0"
    next
end
end

 

config system interface
    edit "port1"
        set vdom "root"
        set ip 192.168.1.254 255.255.255.0 <-----
        set allowaccess ping https ssh HTTP
        set type physical
        set snmp-index 1
    next
end

 

InternalFGT1 # get router info routing-table connected
Routing table for VRF=0
C 192.168.1.0/24 is directly connected, port1 <<<<<<<<<
C 192.168.128.0/24 is directly connected, port3

 

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)
BGP: [NETWORK] Accept Thread: 192.168.1.1 - No such Peer configured
BGP: [RIB] Scanning BGP Network Routes for VRF 0...
BGP: [RIB] Scanning BGP RIB for VRF 0...
BGP: [NETWORK] Accept Thread: Incoming conn from host 192.168.1.1 (FD=27 VRF=0)
BGP: [NETWORK] Accept Thread: 192.168.1.1 - No such Peer configured
BGP: [RIB] Scanning BGP Network Routes for VRF 0...

 

InternalFGT1 # get router info bgp summary

VRF 0 BGP router identifier 192.168.128.254, local AS number 65412
BGP table version is 1
0 BGP AS-PATH entries
0 BGP community entries

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

 

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

 

Contributors