Thanks a lot Peter and Jeff for this great video. The concept of using BGP communities to prevent BGP path hunting is really interesting, but I am not 100% sure how this works. Let's say the FSW1 switch has 2 paths for an IP address behind the RSW1 - 1 primary (with the "rack_prefix" community) and 1 backup (with "completed_backup_path" community). How is the path hunting prevented if a prefix behind the RSW1 became unreachable? In my understanding, RSW1 would send BGP withdraw to FSW1 and FSW2. Both routers will start to converge, let's say FSW1 converges first, he can see the backup path via RSW2 and start to use this path and in the meantime it will send explicit withdraw to RSW2. RSW2 will now send the traffic via FSW2 (if FSW2 is not fully converged and didn't send withdraw to RSW2). Once all RSWx / FSWx are not fully converged, traffic is dropped. Probably I am missing something, could someone please explain? Thanks a lot !
Thanks a lot Peter and Jeff for this great video. The concept of using BGP communities to prevent BGP path hunting is really interesting, but I am not 100% sure how this works. Let's say the FSW1 switch has 2 paths for an IP address behind the RSW1 - 1 primary (with the "rack_prefix" community) and 1 backup (with "completed_backup_path" community). How is the path hunting prevented if a prefix behind the RSW1 became unreachable? In my understanding, RSW1 would send BGP withdraw to FSW1 and FSW2. Both routers will start to converge, let's say FSW1 converges first, he can see the backup path via RSW2 and start to use this path and in the meantime it will send explicit withdraw to RSW2. RSW2 will now send the traffic via FSW2 (if FSW2 is not fully converged and didn't send withdraw to RSW2). Once all RSWx / FSWx are not fully converged, traffic is dropped. Probably I am missing something, could someone please explain? Thanks a lot !