BGP error with config load

[selvaraj rajan]

Hi

I am a newbie to SONiC..incase if I should not ask this question here pls  let me know the correct email group!  

I am running SONiC.201911 in which I could not save configured BGP neighbors. Since "config save" doesn't work, I edited config_db.json manually and ran "config load" which shows me following error logs..that is "Not all dependencies are met" !! 

BGP_NEIGHBOR DB remains consequently "config save" could not see any BGP neighbors to save. Would have been nice if some of those dependencies were listed along that error message.  Am I missing some configuration?

Appreciate any help to debug/troubleshoot this! 

Aug 13 01:02:29.592187 frank DEBUG bgp#bgpcfgd: Received message : '('10.10.30.10', 'SET', (('rrclient', '0'), ('name', 'ARISTA01T1'), ('local_addr', '10.10.30.2'), ('nhopself', '0'), ('holdtime', '10'), ('asn', '64600'), ('keepalive', '3')))'
Aug 13 01:02:29.592187 frank DEBUG bgp#bgpcfgd: Not all dependencies are met for the Manager: <class 'bgpcfgd.managers_bgp.BGPPeerMgrBase'>

-----------------config_db.json-----

"DEVICE_METADATA": {
        "localhost": {
           ----------,

           ----------,
            "bgp_asn": "64100"
        }

  "VLAN_INTERFACE": {
        "Vlan31|10.10.31.2/24": {},
        "Vlan31": {}
    },

"BGP_NEIGHBOR": {
        "10.10.31.10": {
            "local_addr": "10.10.31.2",
            "asn": "64600",
            "name": "TESTNEIGH31"
        },
        "10.10.30.10": {
            "local_addr": "10.10.30.2",
            "asn": "64600",
            "name": "TESTNEIGH"
        }

}

admin@frank:~$ show ip interfaces
Interface    Master    IPv4 address/mask    Admin/Oper    BGP Neighbor    Neighbor IP
-----------  --------  -------------------  ------------  --------------  -------------
Eth29            10.10.29.2/24        up/up         N/A             N/A
Eth30            10.10.30.2/24        up/up         TESTNEIGH       10.10.30.11
Vlan31                 10.10.31.2/24        up/up         TESTNEIGH31     10.10.31.10
docker0                240.127.1.1/24       up/down       N/A             N/A
eth0                   172.30.129.249/16    up/up         N/A             N/A
lo                     127.0.0.1/8          up/up         N/A             N/A
admin@frank:~$

Thanks,

Selva

[Christian Svensson]

Hi Selva,

I have worked mostly with the 202012 release, so this might be different on your version - but I would start investigating how the FRR or Quagga configuration looks like.

Do you know if your 201911 uses Quagga or FRR?

Forgive me if you already know this, but you can use 'vtysh' and 'show run' to verify that SONiC has successfully imported your configuration to the BGP routing daemon.

If that configuration looks wrong, I would investigate the template configuration generated by SONiC.

For FRR I would do something like this:

# Regenerate the BGP config from the templates

$ systemctl restart bgp

# Fetch the generated templated configuration

$ docker exec -ti bgp cat /etc/frr/bgpd.conf

If the templated configuration looks wrong, you know that your CONFIG_DB contents are not correct.

It seems to me that SONiC has changed the BGP configuration format over the years quite a bit so I wouldn't be surprised if you are running into issues related to that.