Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bgpd: BGP neighbor password change doesn't take effect with a a parti…
…cular config on reboot Description: when vrf add is received, add Vrf-name to the interface database. This is needed while binding the VRF interface to the BGP socket. In this case, the global bgp config containing vrf is received before zebra sends vrf add message to BGP. When we receive the global bgp vrf message first, vrf interface is not present in the interface database of BGP. So, while creating the global bgp socket, interface bind to the vrf interface fails. Also, when setting the password on the bgp socket, first we should apply the password on the socket and then, reset the session or send update to peer. Problem Description/Summary : changing the neighbor password resets the session immediately but it doesn't use the password. It continues to operate without password. Managed to recreate the issue with below reduced config. Setup: Sonic1------Sonic2 Test Steps: 1. Configure eBGP session between Sonic-1 and Sonic2 in default vrf using Peer-group. 2. Create a dummy non-default vrf BGP instance on Sonic1 device. 3. Save and reload Sonic1 device. 4. Once the device is up, try to configure 'password <string>' on Sonic1 BGP neighbor alone. 5. The eBGP session should go down and must not come up until matching password is configured on Sonic2 device. But it comes up. Expected Behavior : The eBGP session should go down and must not come up until matching password is configured on Sonic2 device. Signed-off-by: sudhanshukumar22 <sudhanshu.kumar@broadcom.com>
- Loading branch information