ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

dmitris · Tue Jan 16, 2024 3:55 pm

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

/routing ospf instance
add disabled=no name=ospf-instance-v2 router-id=10.0.0.1
/routing ospf area
add comment=backbone_v2 disabled=no instance=ospf-instance-v2 name=area0
/routing bfd configuration
add address-list=bfd-allowed forbid-bfd=no
add disabled=no forbid-bfd=no interfaces=all
/routing bgp connection
add 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=\
    yes
add 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=yes
add 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-template
add area=area0 disabled=no interfaces=loopback0 passive type=ptp
add area=area0 disabled=no interfaces=ether1 type=ptp use-bfd=yes
add area=area0 disabled=no interfaces=ether2 type=ptp use-bfd=yes
add area=area0 disabled=no interfaces=ether3 type=ptp use-bfd=yes

routing/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

/routing ospf instance
add disabled=no name=ospf-instance-v2 router-id=10.0.0.2
/routing ospf area
add comment=backbone_v2 disabled=no instance=ospf-instance-v2 name=area0
/routing bfd configuration
add address-list=bfd-allowed forbid-bfd=no
add disabled=no forbid-bfd=no interfaces=all
/routing bgp connection
add 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=\
    yes
add 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=yes
add 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-template
add area=area0 disabled=no interfaces=loopback0 passive type=ptp
add area=area0 disabled=no interfaces=ether1 type=ptp use-bfd=yes
add area=area0 disabled=no interfaces=ether2 type=ptp use-bfd=yes
add area=area0 disabled=no interfaces=ether3 type=ptp use-bfd=yes

R3-CLIENT

/routing ospf instance
add disabled=no name=ospf-instance-v2 router-id=10.0.0.3
/routing ospf area
add comment=backbone_v2 disabled=no instance=ospf-instance-v2 name=area0
/routing bfd configuration
add forbid-bfd=no interfaces=all
add address-list=bfd-allowed forbid-bfd=no
/routing bgp connection
add 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=yes
add 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-template
add area=area0 disabled=no interfaces=ether1 type=ptp use-bfd=yes
add area=area0 disabled=no interfaces=ether2 type=ptp use-bfd=yes
add area=area0 disabled=no interfaces=loopback0 type=ptp

R3] > 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=yes
Flags: D - DYNAMIC; A - ACTIVE; b - BGP; + - ECMP
Columns: DST-ADDRESS, GATEWAY, DISTANCE
     DST-ADDRESS    GATEWAY   DISTANCE
     
D b  172.21.3.0/24  10.0.0.2       200

D b+ 172.21.4.0/24  10.0.0.4       200
DAb+ 172.21.4.0/24  10.0.0.4       200

BR,
Dmitri

Network5 · Fri Jan 26, 2024 10:12 am

Hi Dmitri,

We also use redundant RR in our network. The RR part in BGP on ROS 7 seems not to be finished jet, but can be used.

Please, try to set the roles on the RR side to ".role=ibgp-rr", this should help in receiving duplicate routes. Use ibgp-rr-client (this should be the same as ibgp role for now) for IPv4 clients and ibgp for IPv6 clients (there was some problems with rr-client role on IPv6). This is working for us. Mikrotik support told us that the cluster should be working, but there is no evidence on clients output (print detail). The two RR are synced with the ibgp role.

You should see a couple of each route in the routing table, one from each RR.

baragoon · Fri Jan 26, 2024 10:53 am

there was some problems with rr-client role on IPv6

Hi, can you be more specific? I'm also using Ros7 with BGP and ipv6 (only) and see that BGP is not working correctly.
At least, with multi interface config my src address is wrong and I set "pref-src" in my input filters, I see that "pref-src" added to the route, but it doesn't actually change the source addr of my packets.

dmitris · Fri Jan 26, 2024 10:00 pm

Hi Network5!

Thank you for your suggestion I appreciate it.

RR1 and RR2 are already configured with local.role=ibgp-rr and on the client side configured "local.role=ibgp".
In my situation, the RR CLIENT is receiving the BGP route which was announced/originated by itself.

Did I understand correctly, that you don't see such a problem in your's installation? Which version of ROS7 you are using?

Br,
Dmitri

Network5 · Sat Jan 27, 2024 10:01 am

@baragoon
I'm not a BGP expert, but with multihop BPG setup you should use loopback addresses to do such work and specify the source address in the BGP connection (one of the main differences in ROS7 compared to ROS6).

@dmitris
I'm using mainly version above 7.11.x. If the router has LDP/MPLS the max version usable is 7.12.x, otherwise 7.13.3 is just working fine. Please find below the typo configuration:

RR1

/routing bgp connection
#RR 211
add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=yes \
    disabled=no input.affinity=alone .filter=ibgp-in-4 listen=yes local.address=10.255.255.211 .role=ibgp-rr multihop=yes name=\
    edge-01v4 nexthop-choice=force-self output.affinity=alone .filter-chain=ibgp-out-4 .keep-sent-attributes=no \
    .no-client-to-client-reflection=no .redistribute="" remote.address=10.255.255.201/32 .as=xxx router-id=10.255.255.211 \
    routing-table=main vrf=main
add address-families=ipv6 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=yes disabled=no \
    input.affinity=alone .filter=ibgp-in-6 listen=yes local.address=2a12:xxxx:ffff::211 .role=ibgp-rr multihop=yes name=edge-01v6 \
    nexthop-choice=force-self output.affinity=alone .filter-chain=ibgp-out-6 .keep-sent-attributes=no .network=ibgp6-output \
    .no-client-to-client-reflection=no .redistribute="" remote.address=2a12:xxxx:ffff::201/128 .as=xxx router-id=10.255.255.211 \
    routing-table=main vrf=main

#RR 212
add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=yes \
    disabled=no input.affinity=alone .filter=ibgp-in-4 listen=yes local.address=10.255.255.212 .role=ibgp-rr multihop=yes name=\
    edge-01v4 nexthop-choice=force-self output.affinity=alone .filter-chain=ibgp-out-4 .keep-sent-attributes=no \
    .no-client-to-client-reflection=no .redistribute=connected,bgp remote.address=10.255.255.201/32 .as=xxx router-id=10.255.255.212 \
    routing-table=main use-bfd=no vrf=main
add address-families=ipv6 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=no disabled=no input.affinity=\
    alone .filter=ibgp-in-6 listen=yes local.address=2a12:xxxx:ffff::212 .role=ibgp-rr multihop=yes name=edge-01v6 nexthop-choice=\
    force-self output.affinity=alone .filter-chain=ibgp-out-6 .keep-sent-attributes=no .network=ibgp6-output \
    .no-client-to-client-reflection=no .redistribute=connected,bgp remote.address=2a12:xxxx:ffff::201/128 .as=xxx router-id=\
    10.255.255.212 routing-table=main use-bfd=no vrf=main
 
#CLIENT 201
add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=xxx cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=no input.affinity=alone \
    .filter=ibgp-in-4 listen=yes local.address=10.255.255.201 .role=ibgp multihop=yes name=Prosek-01v4 nexthop-choice=force-self \
    output.affinity=alone .default-originate=always .filter-chain=ibgp-out-4 .keep-sent-attributes=no .no-client-to-client-reflection=yes \
    .redistribute=connected remote.address=10.255.255.211/32 .as=xxx router-id=yy.yy.yy.yy routing-table=main use-bfd=no vrf=main
add address-families=ipv6 as=xxx cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=no input.affinity=alone .filter=ibgp-in-6 listen=yes \
    local.address=2a12:xxx:ffff::201 .role=ibgp multihop=yes name=Prosek-01v6 nexthop-choice=force-self output.affinity=alone \
    .default-originate=always .filter-chain=ibgp-out-6 .keep-sent-attributes=no .no-client-to-client-reflection=yes .redistribute=connected \
    remote.address=2a12:xxx:ffff::211/128 .as=xxx router-id=yy.yy.yy.yy routing-table=main use-bfd=no vrf=main
add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=xxx cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=no input.affinity=alone \
    .filter=ibgp-in-4 listen=yes local.address=10.255.255.201 .role=ibgp multihop=yes name=Trst-01v4 nexthop-choice=force-self output.affinity=\
    alone .default-originate=always .filter-chain=ibgp-out-4 .keep-sent-attributes=no .no-client-to-client-reflection=yes .redistribute=\
    connected remote.address=10.255.255.212/32 .as=xxx router-id=yy.yy.yy.yy routing-table=main use-bfd=no vrf=main
add address-families=ipv6 as=xxx cisco-vpls-nlri-len-fmt=auto-bits connect=yes disabled=no input.affinity=alone .filter=ibgp-in-6 listen=yes \
    local.address=2a12:xxxx:ffff::201 .role=ibgp multihop=yes name=Trst-01v6 nexthop-choice=force-self output.affinity=alone .default-originate=\
    always .filter-chain=ibgp-out-6 .keep-sent-attributes=no .no-client-to-client-reflection=yes .redistribute=connected remote.address=\
    2a12:xxxx:ffff::212/128 .as=xxx router-id=yy.yy.yy.yy routing-table=main use-bfd=no vrf=main

In RR setup the nexthop-choice is not relevant because is always default.

The resulting route list should look like below, with two same routes from the two RR:

[edge-01.core.] /routing/route> print where dst-address in 10.30.0.0/16  
Flags: A - ACTIVE; b - BGP
Columns: DST-ADDRESS, GATEWAY, AFI, DISTANCE, SCOPE, TARGET-SCOPE, IMMEDIATE-GW
   DST-ADDRESS     GATEWAY         AFI  DISTANCE  SCOPE  TARGET-SCOPE  IMMEDIATE-GW                  
Ab 10.30.1.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02   
 b 10.30.1.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02   
Ab 10.30.2.0/24    10.255.255.251  ip4       200     40            30  10.20.2.2%VLAN1051-BB01-Prosek
 b 10.30.2.0/24    10.255.255.251  ip4       200     40            30  10.20.2.2%VLAN1051-BB01-Prosek
Ab 10.30.3.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02   
 b 10.30.3.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02   
Ab 10.30.4.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02   
 b 10.30.4.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02   
Ab 10.30.5.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02   
 b 10.30.5.0/24    10.255.255.252  ip4       200     40            30  10.20.2.26%VLAN1001-edge-02
 
 [edge-01.core.] /routing/route> print where dst-address in 2a12:xxxx::/32
Flags: A - ACTIVE; s - STATIC, b - BGP; B - BLACKHOLE
Columns: DST-ADDRESS, GATEWAY, AFI, DISTANCE, SCOPE, TARGET-SCOPE, IMMEDIATE-GW
    DST-ADDRESS          GATEWAY               AFI  DISTANCE  SCOPE  TARGET-SCOPE  IMMEDIATE-GW                                                              
Ab  2a12:xxxx:100::/40   2a12:xxxx:ffff::a101  ip6       200     40            30  fe80::a55:31ff:fea5:a5b2%VLAN2001-UpLink-AC  
Ab  2a12:xxxx:300::/40   2a12:xxxx:ffff::a101  ip6       200     40            30  fe80::a55:31ff:fea5:a5b2%VLAN2001-UpLink-AC  
 b  2a12:xxxx:1100::/40  2a12:xxxx:ffff::212   ip6       200     40            30  fe80::1afd:74ff:fef4:471f%VLAN1001-edge-02   
Ab  2a12:xxxx:1100::/40  2a12:xxxx:ffff::211   ip6       200     40            30  fe80::a55:31ff:fe55:ce90%VLAN1051-BB01-Prosek
 b  2a12:xxxx:1200::/40  2a12:xxxx:ffff::212   ip6       200     40            30  fe80::1afd:74ff:fef4:471f%VLAN1001-edge-02   
Ab  2a12:xxxx:1200::/40  2a12:xxxx:ffff::211   ip6       200     40            30  fe80::a55:31ff:fe55:ce90%VLAN1051-BB01-Prosek
 b  2a12:xxxx:1600::/40  2a12:xxxx:ffff::212   ip6       200     40            30  fe80::1afd:74ff:fef4:471f%VLAN1001-edge-02   
Ab  2a12:xxxx:1600::/40  2a12:xxxx:ffff::211   ip6       200     40            30  fe80::a55:31ff:fe55:ce90%VLAN1051-BB01-Prosek

Hope that this is somehow a useful example for you.

dmitris · Sat Jan 27, 2024 6:33 pm

Hello Network5!

Could you check on your RR router's advertised routes, do you see in any entry originator-id or cluster-list attributes?
/routing/bgp/advertisements/print detail

Can you share the BGP peering configuration which is pointing RR211 to R212 and vice-versa?

Thank you!

Br,
Dmitri

Network5 · Sun Jan 28, 2024 9:27 am

Hi,

Find below the RR peering configuration:

#RR211
add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=yes \
    disabled=no input.affinity=alone .filter=ibgp-in-4 listen=yes local.address=10.255.255.211 .role=ibgp multihop=yes name=\
    Trst-01v4 nexthop-choice=force-self output.affinity=alone .filter-chain=ibgp-out-4 .keep-sent-attributes=no \
    .no-client-to-client-reflection=no .redistribute=connected,bgp remote.address=10.255.255.212/32 .as=xxx router-id=\
    10.255.255.211 routing-table=main vrf=main
add address-families=ipv6 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=yes disabled=no \
    input.affinity=alone .filter=ibgp-in-6 listen=yes local.address=2a12:xxxx:ffff::211 .role=ibgp multihop=yes name=Trst-01v6 \
    nexthop-choice=force-self output.affinity=alone .filter-chain=ibgp-out-6 .keep-sent-attributes=no .network=ibgp6-output \
    .no-client-to-client-reflection=no .redistribute=connected,bgp remote.address=2a12:xxxx:ffff::212/128 .as=xxx router-id=\
    10.255.255.211 routing-table=main vrf=main

#RR212
add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=yes \
    disabled=no input.affinity=main .filter=ibgp-in-4 listen=yes local.address=10.255.255.212 .role=ibgp multihop=yes name=Prosek-01v4 \
    nexthop-choice=force-self output.affinity=main .default-originate=if-installed .filter-chain=ibgp-out-4 .keep-sent-attributes=no \
    .no-client-to-client-reflection=no .redistribute=connected,bgp remote.address=10.255.255.211/32 .as=xxx router-id=10.255.255.212 \
    routing-table=main use-bfd=no vrf=main
add address-families=ipv6 as=xxx cisco-vpls-nlri-len-fmt=auto-bits cluster-id=10.255.255.1 connect=yes disabled=no input.affinity=\
    alone .filter=ibgp-in-6 listen=yes local.address=2a12:xxxx:ffff::212 .role=ibgp multihop=yes name=Prosek-01v6 nexthop-choice=\
    force-self output.affinity=alone .filter-chain=ibgp-out-6 .keep-sent-attributes=no .network=ibgp6-output \
    .no-client-to-client-reflection=no .redistribute=connected,bgp remote.address=2a12:xxxx:ffff::211/128 .as=xxx router-id=\
    10.255.255.212 routing-table=main use-bfd=no vrf=main

About the cluster-list and originator-id, I was told time ago from the support that the features are implemented, but not displayed. Cosmetic issue. Supposing that the correct behaviour would be just one route displayed, but I'm not sure about that.

[edge-01.core.] /routing/route> print detail where dst-address in 10.30.0.0/16
Flags: X - disabled, F - filtered, U - unreachable, A - active; 
c - connect, s - static, r - rip, b - bgp, o - ospf, i - is-is, d - dhcp, v - vpn, m - modem, a - ldp-address, l - ldp-mapping, g - slaac, y - bg>
H - hw-offloaded; + - ecmp, B - blackhole 
 Ab   afi=ip4 contribution=active dst-address=10.30.1.0/24 routing-table=main gateway=10.255.255.252 immediate-gw=10.20.2.26%VLAN1001-edge-02 
       distance=200 scope=40 target-scope=30 belongs-to="bgp-IP-10.255.255.211" 
       bgp.peer-cache-id=*2800006 .local-pref=100 .atomic-aggregate=yes .origin=igp 
       debug.fwp-ptr=0x203032A0 

  b   afi=ip4 contribution=candidate dst-address=10.30.1.0/24 routing-table=main gateway=10.255.255.252 immediate-gw=10.20.2.26%VLAN1001-edge-02 
       distance=200 scope=40 target-scope=30 belongs-to="bgp-IP-10.255.255.212" 
       bgp.peer-cache-id=*2800005 .local-pref=100 .atomic-aggregate=yes .origin=igp 
       debug.fwp-ptr=0x203032A0 

 Ab   afi=ip4 contribution=active dst-address=10.30.2.0/24 routing-table=main gateway=10.255.255.251 immediate-gw=10.20.2.2%VLAN1051-BB01-Prosek 
       distance=200 scope=40 target-scope=30 belongs-to="bgp-IP-10.255.255.211" 
       bgp.peer-cache-id=*2800006 .local-pref=100 .atomic-aggregate=yes .origin=igp 
       debug.fwp-ptr=0x20303240 

  b   afi=ip4 contribution=candidate dst-address=10.30.2.0/24 routing-table=main gateway=10.255.255.251 
       immediate-gw=10.20.2.2%VLAN1051-BB01-Prosek distance=200 scope=40 target-scope=30 belongs-to="bgp-IP-10.255.255.212" 
       bgp.peer-cache-id=*2800005 .local-pref=100 .atomic-aggregate=yes .origin=igp 
       debug.fwp-ptr=0x20303240 

 Ab   afi=ip4 contribution=active dst-address=10.30.3.0/24 routing-table=main gateway=10.255.255.252 immediate-gw=10.20.2.26%VLAN1001-edge-02 
       distance=200 scope=40 target-scope=30 belongs-to="bgp-IP-10.255.255.211" 
       bgp.peer-cache-id=*2800006 .local-pref=100 .atomic-aggregate=yes .origin=igp 
       debug.fwp-ptr=0x203032A0 

  b   afi=ip4 contribution=candidate dst-address=10.30.3.0/24 routing-table=main gateway=10.255.255.252 immediate-gw=10.20.2.26%VLAN1001-edge-02 
       distance=200 scope=40 target-scope=30 belongs-to="bgp-IP-10.255.255.212" 
       bgp.peer-cache-id=*2800005 .local-pref=100 .atomic-aggregate=yes .origin=igp 
       debug.fwp-ptr=0x203032A0

dmitris · Tue Feb 06, 2024 1:58 pm

Good news, I received confirmation, that Mikrotik support have managed to reproduce the issue in their lab and will fix it.

d.

Network5 · Wed Feb 14, 2024 10:41 pm

That is a good news!

MWComms · Sun Jul 21, 2024 10:51 am

Have Mikrotik advised whether this has been resolved?

ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Re: ROS 7.12.1 BGP Redundant Route reflection, necessary attributes are missing

Who is online