Open jhlasnik opened 1 year ago
After further testing it seems trying to apply any specific bgp neighbor config it will cause the service to crash.
root@clab-cx-sw1:mgmt:~# nv set vrf default router bgp neighbor 101.1.1.1 remote-as 1001
root@clab-cx-sw1:mgmt:~# nv config diff
- set:
vrf:
default:
router:
bgp:
neighbor:
101.1.1.1:
remote-as: 1001
type: numbered
root@clab-cx-sw1:mgmt:~# nv config apply
reloadingError: Could not connect to nvued.
To start nvued, use
sudo systemctl start nvued
To check the status of nvued, use
sudo systemctl status nvued
To configure nvued to start when the device boots, use
sudo systemctl enable nvued
I can't reproduce this. Started with a clean 5.3 image and did this:
nv set vrf default router bgp neighbor 101.1.1.1 remote-as 1001
nv config apply -y
It complained about missing ASN and router-id, so I did:
nv set router bgp autonomous-system 65100
nv set router bgp router-id 1.1.1.1
nv config apply -y
And the config got applied successfully.
Do you have any prior configuration in FRR or do you mount/overwrite some of the FRR files (in /etc/frr dir)? I suspect there's something preventing your frr from running (check systemctl status frr
).
I've been testing the 5.3 image and seem to be running into a commit issue on certain config under router.
journalctl -u nvued -f &
I broke up the commits on other sections and it eventually took but I can't seem to get this to apply