Quantcast
Channel: MikroTik
Viewing all articles
Browse latest Browse all 23620

Forwarding Protocols • ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

$
0
0
Hello,

I have noticed that in Redundant RR scenario, when RR1 received prefix from RR-client1 and reflecting received prefix to the RR2 which is in the same cluster, originator-id and cluster-list attributes are not added to the reflected prefix. Is it known problem in Mikrotik or I'm missing something ?
As result rr-client receiving it's advertised prefix back over BGP.

RR1
Code:
/routing ospf instanceadd disabled=no name=ospf-instance-v2 router-id=10.0.0.1/routing ospf areaadd comment=backbone_v2 disabled=no instance=ospf-instance-v2 name=area0/routing bfd configurationadd address-list=bfd-allowed forbid-bfd=noadd disabled=no forbid-bfd=no interfaces=all/routing bgp connectionadd as=65000 cluster-id=1.1.1.1 connect=yes listen=yes local.address=10.0.0.1 .role=\    ibgp name=to-r2-rr remote.address=10.0.0.2 .as=65000 router-id=10.0.0.1 use-bfd=\    yesadd as=65000 connect=yes listen=yes local.address=10.0.0.1 .role=ibgp-rr name=\    to-r3-rr-client remote.address=10.0.0.3 .as=65000 router-id=10.0.0.1 use-bfd=yesadd as=65000 connect=yes listen=yes local.address=10.0.0.1 .role=ibgp-rr name=\    to-r4-rr-client remote.address=10.0.0.4 .as=65000 router-id=10.0.0.1 use-bfd=yes/routing ospf interface-templateadd area=area0 disabled=no interfaces=loopback0 passive type=ptpadd area=area0 disabled=no interfaces=ether1 type=ptp use-bfd=yesadd area=area0 disabled=no interfaces=ether2 type=ptp use-bfd=yesadd area=area0 disabled=no interfaces=ether3 type=ptp use-bfd=yesrouting/bgp/advertisements/print detail  0 peer=to-r4-rr-client-1 dst=172.21.3.0/24 afi=ip local-pref=100 nexthop=10.0.0.3    origin=0 atomic-aggregate=yes  0 peer=to-r3-rr-client-1 dst=172.21.4.0/24 afi=ip local-pref=100 nexthop=10.0.0.4    origin=0 atomic-aggregate=yes  0 peer=to-r2-rr-1 dst=172.21.4.0/24 afi=ip local-pref=100 nexthop=10.0.0.4 origin=0    atomic-aggregate=yes  0 peer=to-r2-rr-1 dst=172.21.3.0/24 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0    atomic-aggregate=yes 


RR2
Code:
/routing ospf instanceadd disabled=no name=ospf-instance-v2 router-id=10.0.0.2/routing ospf areaadd comment=backbone_v2 disabled=no instance=ospf-instance-v2 name=area0/routing bfd configurationadd address-list=bfd-allowed forbid-bfd=noadd disabled=no forbid-bfd=no interfaces=all/routing bgp connectionadd as=65000 cluster-id=1.1.1.1 connect=yes listen=yes local.address=10.0.0.2 .role=\    ibgp name=to-r1-rr remote.address=10.0.0.1 .as=65000 router-id=10.0.0.2 use-bfd=\    yesadd as=65000 connect=yes listen=yes local.address=10.0.0.2 .role=ibgp-rr name=\    to-r3-rr-client remote.address=10.0.0.3 .as=65000 router-id=10.0.0.2 use-bfd=yesadd as=65000 connect=yes listen=yes local.address=10.0.0.2 .role=ibgp-rr name=\    to-r4-rr-client remote.address=10.0.0.4 .as=65000 router-id=10.0.0.2 use-bfd=yes/routing ospf interface-templateadd area=area0 disabled=no interfaces=loopback0 passive type=ptpadd area=area0 disabled=no interfaces=ether1 type=ptp use-bfd=yesadd area=area0 disabled=no interfaces=ether2 type=ptp use-bfd=yesadd area=area0 disabled=no interfaces=ether3 type=ptp use-bfd=yes
R3-CLIENT
Code:
/routing ospf instanceadd disabled=no name=ospf-instance-v2 router-id=10.0.0.3/routing ospf areaadd comment=backbone_v2 disabled=no instance=ospf-instance-v2 name=area0/routing bfd configurationadd forbid-bfd=no interfaces=alladd address-list=bfd-allowed forbid-bfd=no/routing bgp connectionadd as=65000 connect=yes listen=yes local.address=10.0.0.3 .role=ibgp name=to-r1-rr \    output.redistribute=connected remote.address=10.0.0.1 .as=65000 router-id=\    10.0.0.3 use-bfd=yesadd as=65000 connect=yes listen=yes local.address=10.0.0.3 .role=ibgp name=to-r2-rr \    output.redistribute=connected remote.address=10.0.0.2 .as=65000 router-id=\    10.0.0.3 use-bfd=yes/routing ospf interface-templateadd area=area0 disabled=no interfaces=ether1 type=ptp use-bfd=yesadd area=area0 disabled=no interfaces=ether2 type=ptp use-bfd=yesadd area=area0 disabled=no interfaces=loopback0 type=ptpR3] > routing/bgp/advertisements/print detail  0 peer=to-r2-rr-1 dst=192.168.1.0/30 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0  0 peer=to-r2-rr-1 dst=192.168.3.0/30 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0  0 peer=to-r2-rr-1 dst=172.21.3.0/24 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0  0 peer=to-r2-rr-1 dst=10.0.0.3 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0  0 peer=to-r1-rr-1 dst=192.168.1.0/30 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0  0 peer=to-r1-rr-1 dst=192.168.3.0/30 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0  0 peer=to-r1-rr-1 dst=172.21.3.0/24 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0  0 peer=to-r1-rr-1 dst=10.0.0.3 afi=ip local-pref=100 nexthop=10.0.0.3 origin=0   R3] > ip route/print where bgp=yesFlags: D - DYNAMIC; A - ACTIVE; b - BGP; + - ECMPColumns: DST-ADDRESS, GATEWAY, DISTANCE     DST-ADDRESS    GATEWAY   DISTANCE     D b  172.21.3.0/24  10.0.0.2       200D b+ 172.21.4.0/24  10.0.0.4       200DAb+ 172.21.4.0/24  10.0.0.4       200
BR,
Dmitri

Statistics: Posted by dmitris — Tue Jan 16, 2024 3:55 pm



Viewing all articles
Browse latest Browse all 23620

Trending Articles