fd22635de0
Why I did it In the recent minigraph changes we add separate BGP session configuration for V4 and V6 internal VoQ neighbors. This PR is adding different Peer groups for V4 and V6 neighbors How I did it Add VOQ_CHASSIS_V4_PEER and VOQ_CHASSIS_V6_PEER groups Add extra Unit tests How to verify it Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan <arlakshm@microsoft.com>
29 lines
1.1 KiB
Django/Jinja
29 lines
1.1 KiB
Django/Jinja
!
|
|
! template: bgpd/templates/voq_chassis/peer-group.conf.j2
|
|
!
|
|
neighbor VOQ_CHASSIS_V4_PEER peer-group
|
|
neighbor VOQ_CHASSIS_V6_PEER peer-group
|
|
address-family ipv4
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['type'] == 'ToRRouter' %}
|
|
neighbor VOQ_CHASSIS_V4_PEER allowas-in 1
|
|
{% endif %}
|
|
neighbor VOQ_CHASSIS_V4_PEER activate
|
|
neighbor VOQ_CHASSIS_V4_PEER addpath-tx-all-paths
|
|
neighbor VOQ_CHASSIS_V4_PEER soft-reconfiguration inbound
|
|
neighbor VOQ_CHASSIS_V4_PEER route-map FROM_VOQ_CHASSIS_V4_PEER in
|
|
neighbor VOQ_CHASSIS_V4_PEER route-map TO_VOQ_CHASSIS_V4_PEER out
|
|
exit-address-family
|
|
address-family ipv6
|
|
{% if CONFIG_DB__DEVICE_METADATA['localhost']['type'] == 'ToRRouter' %}
|
|
neighbor VOQ_CHASSIS_V6_PEER allowas-in 1
|
|
{% endif %}
|
|
neighbor VOQ_CHASSIS_V6_PEER activate
|
|
neighbor VOQ_CHASSIS_V6_PEER addpath-tx-all-paths
|
|
neighbor VOQ_CHASSIS_V6_PEER soft-reconfiguration inbound
|
|
neighbor VOQ_CHASSIS_V4_PEER route-map FROM_VOQ_CHASSIS_V6_PEER in
|
|
neighbor VOQ_CHASSIS_V4_PEER route-map TO_VOQ_CHASSIS_V6_PEER out
|
|
exit-address-family
|
|
!
|
|
! end of template: bgpd/templates/voq_chassis/peer-group.conf.j2
|
|
!
|