BGP doens't starts at router reboot

Bugs
1

Hi team,

we have some Vyos routers with BGP setup. Version 1.3.3 and 1.3.6.
Routers was working find for many months without issues. But today I made a reboot and at restart, BGP doesn’t works.

*show ip bgp summary *
% No BGP neighbors found

show bgp
No BGP prefixes displayed, 0 exist

All BGP setup is at configure

set protocols bgp 65001 address-family ipv4-unicast maximum-paths ebgp ‘6’
set protocols bgp 65001 address-family ipv4-unicast maximum-paths ibgp ‘6’
set protocols bgp 65001 address-family ipv4-unicast network 10.68.255.0/24
set protocols bgp 65001 address-family ipv4-unicast network 172.30.255.0/24
set protocols bgp 65001 address-family ipv4-unicast redistribute connected
set protocols bgp 65001 address-family ipv4-unicast redistribute static
set protocols bgp 65001 neighbor 10.68.255.8 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.12 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.16 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.20 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.24 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.28 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.32 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.36 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.40 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.44 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.52 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.64 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.116 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.120 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.124 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.128 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.132 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.136 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.140 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.144 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.164 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.196 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.198 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.200 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 10.68.255.204 peer-group ‘DMVPN’
set protocols bgp 65001 neighbor 172.30.255.1 address-family ipv4-unicast prefix-list export ‘AS65000_OUT’
set protocols bgp 65001 neighbor 172.30.255.1 address-family ipv4-unicast prefix-list import ‘AS65000_IN’
set protocols bgp 65001 neighbor 172.30.255.1 address-family ipv4-unicast soft-reconfiguration inbound
set protocols bgp 65001 neighbor 172.30.255.1 bfd
set protocols bgp 65001 neighbor 172.30.255.1 description ‘router.tbcn.central01’
set protocols bgp 65001 neighbor 172.30.255.1 remote-as ‘65000’
set protocols bgp 65001 neighbor 172.30.255.2 address-family ipv4-unicast prefix-list export ‘AS65000_OUT’
set protocols bgp 65001 neighbor 172.30.255.2 address-family ipv4-unicast prefix-list import ‘AS65000_IN’
set protocols bgp 65001 neighbor 172.30.255.2 address-family ipv4-unicast soft-reconfiguration inbound
set protocols bgp 65001 neighbor 172.30.255.2 bfd
set protocols bgp 65001 neighbor 172.30.255.2 description ‘router.tbcn.central02’
set protocols bgp 65001 neighbor 172.30.255.2 remote-as ‘65000’
set protocols bgp 65001 neighbor 172.30.255.251 address-family ipv4-unicast prefix-list export ‘AS65001_HUB’
set protocols bgp 65001 neighbor 172.30.255.251 address-family ipv4-unicast prefix-list import ‘AS65001_HUB’
set protocols bgp 65001 neighbor 172.30.255.251 bfd
set protocols bgp 65001 neighbor 172.30.255.251 description ‘dmvpn.tbcn.centralhub01’
set protocols bgp 65001 neighbor 172.30.255.251 remote-as ‘internal’
set protocols bgp 65001 parameters bestpath as-path multipath-relax
set protocols bgp 65001 parameters default no-ipv4-unicast
set protocols bgp 65001 parameters graceful-restart
set protocols bgp 65001 parameters graceful-shutdown
set protocols bgp 65001 parameters log-neighbor-changes
set protocols bgp 65001 parameters network-import-check
set protocols bgp 65001 parameters router-id ‘10.68.255.253’
set protocols bgp 65001 peer-group DMVPN address-family ipv4-unicast prefix-list export ‘AS65001_OUT’
set protocols bgp 65001 peer-group DMVPN address-family ipv4-unicast prefix-list import ‘AS65001_IN’
set protocols bgp 65001 peer-group DMVPN address-family ipv4-unicast route-reflector-client
set protocols bgp 65001 peer-group DMVPN address-family ipv4-unicast soft-reconfiguration inbound
set protocols bgp 65001 peer-group DMVPN bfd
set protocols bgp 65001 peer-group DMVPN description ‘xxxxxxxxx’
set protocols bgp 65001 peer-group DMVPN remote-as ‘external’
set protocols bgp 65001 timers holdtime ‘30’
set protocols bgp 65001 timers keepalive ‘10’

but not at vtysh -c “show run”

Building configuration…

Current configuration:
!
frr version 7.5.1-20231128-03-g06f8c4ce0
frr defaults traditional
hostname xxxxxxxxxxxxxxxxxxxxxxxx
log syslog
log facility local7
service integrated-vtysh-config
!
ip route 0.0.0.0/0 91.126.32.17 10
!
router bgp 65001

  • bgp router-id 10.68.255.253*
  • bgp log-neighbor-changes*
  • no bgp ebgp-requires-policy*
  • no bgp default ipv4-unicast*
  • bgp graceful-shutdown*
  • bgp bestpath as-path multipath-relax*
  • neighbor DMVPN peer-group*
    *** neighbor DMVPN remote-as external***
  • !*
  • address-family ipv4 unicast*
  • neighbor DMVPN activate*
  • neighbor DMVPN prefix-list AS65001_IN in*
  • neighbor DMVPN prefix-list AS65001_OUT out*
  • exit-address-family*
    !
    ip prefix-list AS65001_OUT seq 10 permit 10.68.0.0/17 le 24
    ip prefix-list AS65001_OUT seq 20 permit 10.68.128.0/18 le 24
    ip prefix-list AS65001_OUT seq 30 permit 10.69.0.0/16 le 24
    ip prefix-list AS65001_OUT seq 40 permit 10.70.0.0/16 le 24
    ip prefix-list AS65001_OUT seq 50 permit 10.71.0.0/16 le 24
    ip prefix-list AS65001_OUT seq 60 permit 192.168.0.0/16 le 24
    ip prefix-list AS65001_OUT seq 70 permit 172.18.0.0/16 le 24
    ip prefix-list AS65001_OUT seq 80 permit 172.19.0.0/16 le 24
    ip prefix-list AS65001_OUT seq 90 permit 172.20.0.0/16 le 24
    ip prefix-list AS65001_OUT seq 100 permit 172.30.255.0/24 le 24
    ip prefix-list AS65001_OUT seq 1000 deny 0.0.0.0/0 le 32
    ip prefix-list AS65001_IN seq 10 permit 192.168.0.0/20 le 24
    ip prefix-list AS65001_IN seq 20 permit 172.18.0.0/16 le 24
    ip prefix-list AS65001_IN seq 30 permit 172.19.0.0/16 le 24
    ip prefix-list AS65001_IN seq 40 permit 172.20.0.0/16 le 24
    ip prefix-list AS65001_IN seq 50 permit 10.69.0.0/16 le 24
    ip prefix-list AS65001_IN seq 60 permit 10.70.0.0/16 le 24
    ip prefix-list AS65001_IN seq 1000 deny 0.0.0.0/0 le 32
    ip prefix-list AS65000_OUT seq 10 permit 10.68.0.0/17 le 24
    ip prefix-list AS65000_OUT seq 20 permit 10.68.128.0/18 le 24
    ip prefix-list AS65000_OUT seq 30 permit 10.69.0.0/16 le 24
    ip prefix-list AS65000_OUT seq 40 permit 10.70.0.0/16 le 24
    ip prefix-list AS65000_OUT seq 50 permit 10.71.0.0/16 le 24
    ip prefix-list AS65000_OUT seq 1000 deny 0.0.0.0/0 le 32
    ip prefix-list AS65000_IN seq 10 permit 192.168.0.0/20 le 24
    ip prefix-list AS65000_IN seq 20 permit 172.18.0.0/16 le 24
    ip prefix-list AS65000_IN seq 30 permit 172.19.0.0/16 le 24
    ip prefix-list AS65000_IN seq 40 permit 172.20.0.0/16 le 24
    ip prefix-list AS65000_IN seq 1000 deny 0.0.0.0/0 le 32
    ip prefix-list AS65001_HUB seq 10 permit 10.68.0.0/17 le 24
    ip prefix-list AS65001_HUB seq 20 permit 10.68.128.0/18 le 24
    ip prefix-list AS65001_HUB seq 30 permit 10.69.0.0/16 le 24
    ip prefix-list AS65001_HUB seq 40 permit 10.70.0.0/16 le 24
    ip prefix-list AS65001_HUB seq 50 permit 10.71.0.0/16 le 24
    ip prefix-list AS65001_HUB seq 70 permit 172.30.255.0/24 le 24
    ip prefix-list AS65001_HUB seq 1000 deny 0.0.0.0/0 le 32
    !
    line vty
    !
    bfd
  • peer 10.68.255.8 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.12 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.16 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.20 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.24 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.28 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.32 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.36 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.40 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.44 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.52 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.64 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.116 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.120 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.124 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.128 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.132 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.136 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.140 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.144 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.164 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.196 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.198 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.200 multihop local-address 10.68.255.253*
  • !*
  • peer 10.68.255.204 multihop local-address 10.68.255.253*
  • !*
  • peer 172.30.255.1 multihop local-address 172.30.255.250*
  • !*
  • peer 172.30.255.2 multihop local-address 172.30.255.250*
  • !*
  • peer 172.30.255.251 multihop local-address 172.30.255.250*
    !

This is the log “frr”

Apr 22 19:10:23 watchfrr[1090]: watchfrr 7.5.1-20231128-03-g06f8c4ce0 starting: vty@0
Apr 22 19:10:23 watchfrr[1090]: zebra state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: bgpd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: ripd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: ripngd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: ospfd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: ospf6d state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: isisd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: ldpd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: staticd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: bfdd state → down : initial connection attempt failed
Apr 22 19:10:23 watchfrr[1090]: Forked background command [pid 1091]: /usr/lib/frr/watchfrr.sh restart all
Apr 22 19:10:24 watchfrr.sh[1122]: Cannot stop isisd: pid file not found
Apr 22 19:10:24 watchfrr.sh[1110]: Cannot stop ospfd: pid file not found
Apr 22 19:10:24 watchfrr.sh[1118]: Cannot stop ripd: pid file not found
Apr 22 19:10:24 watchfrr.sh[1124]: Cannot stop ospf6d: pid file not found
Apr 22 19:10:24 watchfrr.sh[1121]: Cannot stop bgpd: pid file not found
Apr 22 19:10:24 watchfrr.sh[1114]: Cannot stop ripngd: pid file not found
Apr 22 19:10:24 watchfrr.sh[1116]: Cannot stop zebra: pid file not found
Apr 22 19:10:24 watchfrr.sh[1105]: Cannot stop staticd: pid file not found
Apr 22 19:10:24 watchfrr.sh[1101]: Cannot stop bfdd: pid file not found
Apr 22 19:10:24 watchfrr.sh[1112]: Cannot stop ldpd: pid file not found
Apr 22 19:10:28 watchfrr[1090]: ripngd state → up : connect succeeded
Apr 22 19:10:28 watchfrr[1090]: bgpd state → up : connect succeeded
Apr 22 19:10:28 watchfrr[1090]: zebra state → up : connect succeeded
Apr 22 19:10:28 watchfrr[1090]: ripd state → up : connect succeeded
Apr 22 19:10:28 watchfrr[1090]: Forked background command [pid 1200]: /usr/lib/frr/watchfrr.sh restart staticd
Apr 22 19:10:29 watchfrr.sh[1205]: Cannot stop staticd: pid file not found
Apr 22 19:10:29 watchfrr[1090]: Forked background command [pid 1207]: /usr/lib/frr/watchfrr.sh restart ospf6d
Apr 22 19:10:29 watchfrr[1090]: Forked background command [pid 1208]: /usr/lib/frr/watchfrr.sh restart isisd
Apr 22 19:10:29 watchfrr.sh[1216]: Cannot stop ospf6d: pid file not found
Apr 22 19:10:29 watchfrr.sh[1218]: Cannot stop isisd: pid file not found
Apr 22 19:10:29 watchfrr[1090]: Forked background command [pid 1224]: /usr/lib/frr/watchfrr.sh restart ldpd
Apr 22 19:10:29 watchfrr[1090]: Forked background command [pid 1226]: /usr/lib/frr/watchfrr.sh restart bfdd
Apr 22 19:10:29 watchfrr.sh[1235]: Cannot stop bfdd: pid file not found
Apr 22 19:10:29 watchfrr.sh[1240]: Cannot stop ldpd: pid file not found
Apr 22 19:10:29 watchfrr.sh[1259]: Failed to start ospf6d!
Apr 22 19:10:29 watchfrr.sh[1268]: Failed to start isisd!
Apr 22 19:10:29 watchfrr[1090]: isisd state → up : connect succeeded
Apr 22 19:10:29 watchfrr.sh[1274]: Failed to start bfdd!
Apr 22 19:10:29 watchfrr[1090]: staticd state → up : connect succeeded
Apr 22 19:10:29 watchfrr[1090]: ospf6d state → up : connect succeeded
Apr 22 19:10:30 watchfrr[1090]: ldpd state → up : connect succeeded
Apr 22 19:10:30 watchfrr[1090]: Daemon: zebra: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: Daemon: bgpd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: Daemon: ripd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: Daemon: ripngd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: ospfd state → up : connect succeeded
Apr 22 19:10:30 vyos-router[924]: Started watchfrr.
Apr 22 19:10:30 watchfrr[1090]: Daemon: ospf6d: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: Daemon: isisd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: Daemon: ldpd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: Daemon: staticd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:10:30 watchfrr[1090]: bfdd state → up : connect succeeded
Apr 22 19:10:30 watchfrr[1090]: all daemons up, doing startup-complete notify
Apr 22 19:10:49 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 20 seconds, sending signal 15
Apr 22 19:11:09 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 40 seconds, sending signal 9
Apr 22 19:11:29 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 60 seconds, sending signal 9
Apr 22 19:11:49 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 80 seconds, sending signal 9
Apr 22 19:12:09 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 100 seconds, sending signal 9
Apr 22 19:12:29 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 120 seconds, sending signal 9
Apr 22 19:12:49 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 140 seconds, sending signal 9
Apr 22 19:13:09 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 160 seconds, sending signal 9
Apr 22 19:13:37 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 188 seconds, sending signal 9
Apr 22 19:13:57 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 208 seconds, sending signal 9
Apr 22 19:14:17 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 228 seconds, sending signal 9
Apr 22 19:14:37 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 248 seconds, sending signal 9
Apr 22 19:14:57 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 268 seconds, sending signal 9
Apr 22 19:15:17 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 288 seconds, sending signal 9
Apr 22 19:15:37 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 308 seconds, sending signal 9
Apr 22 19:15:57 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 328 seconds, sending signal 9
Apr 22 19:16:17 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 348 seconds, sending signal 9
Apr 22 19:16:37 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 368 seconds, sending signal 9
Apr 22 19:16:57 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 388 seconds, sending signal 9
Apr 22 19:17:17 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 408 seconds, sending signal 9
Apr 22 19:17:37 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 428 seconds, sending signal 9
Apr 22 19:17:57 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 448 seconds, sending signal 9
Apr 22 19:18:17 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 468 seconds, sending signal 9
Apr 22 19:18:37 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 488 seconds, sending signal 9
Apr 22 19:18:57 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 508 seconds, sending signal 9
Apr 22 19:19:17 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 528 seconds, sending signal 9
Apr 22 19:19:37 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 548 seconds, sending signal 9
Apr 22 19:19:57 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 568 seconds, sending signal 9
Apr 22 19:20:17 watchfrr[1090]: Warning: restart bfdd child process 1226 still running after 588 seconds, sending signal 9

This is log | bgp

Apr 22 19:10:23 watchfrr[1090]: bgpd state → down : initial connection attempt failed
Apr 22 19:10:24 watchfrr.sh[1121]: Cannot stop bgpd: pid file not found
Apr 22 19:10:28 watchfrr[1090]: bgpd state → up : connect succeeded
Apr 22 19:10:30 watchfrr[1090]: Daemon: bgpd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 19:11:42 vyatta-cfg-quagga[2869]: /usr/bin/vtysh -c configure terminal -c router bgp 65001 -c address-family ipv4 unicast -c neighbor DMVPN route-reflector-client failed: 256

I tried to delete this line
set protocols bgp 65001 peer-group DMVPN address-family ipv4-unicast route-reflector-client

with this error at commit

[ protocols bgp 65001 ]
% Invalid command. Not an internal neighbor
Error configuring routing subsystem. See log for more detailed information

and this message in logs

[email protected]:~$ journalctl -b | grep -i bgp
Apr 22 18:32:49 dmvpn.tbcn.centralhub02 watchfrr[1104]: bgpd state → down : initial connection attempt failed
Apr 22 18:32:49 dmvpn.tbcn.centralhub02 watchfrr.sh[1135]: Cannot stop bgpd: pid file not found
Apr 22 18:32:54 dmvpn.tbcn.centralhub02 watchfrr[1104]: bgpd state → up : connect succeeded
Apr 22 18:32:55 dmvpn.tbcn.centralhub02 watchfrr[1104]: Daemon: bgpd: is in Up state but expected it to be in DAEMON_DOWN state
Apr 22 18:34:05 dmvpn.tbcn.centralhub02 vyatta-cfg-quagga[2845]: /usr/bin/vtysh -c configure terminal -c router bgp 65001 -c address-family ipv4 unicast -c neighbor DMVPN route-reflector-client failed: 256
Apr 22 18:40:32 dmvpn.tbcn.centralhub02 vyatta-cfg-quagga[5296]: /usr/bin/vtysh -c configure terminal -c router bgp 65001 -c address-family ipv4 unicast -c no neighbor DMVPN route-reflector-client failed: 256

I tried removing all bgp config, with this error message

*[email protected]# delete protocols bgp *
[edit]
[email protected]# commit
[ protocols bgp 65001 ]
% Specify remote-as or peer-group commands first
Error configuring routing subsystem. See log for more detailed information

but bgp config was erased from setup.

I tried to setup bgp again, block by block… general config and commit not-grouping peers and commit, general peer-group and commit, all peer-group neighbours and commit…WHITHOUT ERRORS!!!

bgp works fine again…but

save and reboot, and it doesn’t works again with same behaviour

please, can anybody help’s me?

regards