update-groups bgp

[luis.pico.herrero]

Buenas tardes,

Estoy tratando de hacer unas pruebas en un CRS con la versión IOS XR 4.3.2 y tengo una duda.

Se supone que cuando dos BGP neighbors tienen la misma routing policy de salida, dichos neighbors se asignan automáticamente al mismo update-group.

Sin embargo, en mi caso, no ocurre esto. Cada uno de los BGP neighbors están siendo asignados a un update group diferente. ¿Por que puede ser esto?

Muchas gracias de antemano.

Saludos,

Luis

[xthuijs]

hey luis,

love to help out, but my spanish is a bit rusty. to get the best responses best to write it in english please. or french, or dutch or german, that in case you would like a response from me :)

xander

[luis.pico.herrero]

Hi Alex,

Thanks for helping.

The problem is the following. I expected that bgp neighbors with the same outbound routing policy will be assigned automatically to the same update-group. However, that is not the case in the tests I am performing...

I have the following scenario:  

The Cisco has two eBGP sessions to two different routers with exactly the same outbound  and inbound routing policy.

¿Do you know what could be the problem? ¿Is there a way to force both neighbors to be in the same update group?

Thanks again for your help!

Kind regards,

Luis

[xthuijs]

ah thanks for the xlate luis :)

more things need to align for the neighbors to be in the same update group.

you can check the update group definition with this command below.

If you see 2 groups with different/separate attributes, then you can see what one needs to change in order to get them in the same group.

xander

RP/0/RSP0/CPU0:A9K-BNG#show bgp update-group
Tue Feb 17 16:44:10.627 EST

Update group for IPv4 Unicast, index 0.1:
  Attributes:
    Neighbor sessions are IPv4
    Outbound policy: pass-all
    Internal
    Common admin
    First neighbor AS: 64524
    Send communities
    Send extended communities
    4-byte AS capable
    Non-labeled address-family capable
    Send AIGP
    Minimum advertisement interval: 0 secs
  Update group desynchronized: 0
  Sub-groups merged: 0
  Number of refresh subgroups: 0
  Messages formatted: 1322264, replicated: 1322264
  All neighbors are assigned to sub-group(s)
    Neighbors in sub-group: 0.4, Filter-Groups num:1
     Neighbors in filter-group: 0.4(RT num: 0)
      172.28.98.2               

Update group for IPv4 Unicast, index 0.2:

[luis.pico.herrero]

Ok! I will check the differences tomorrow and let you know!

Could affect the "First neighbor AS"?

Thanks!

Luis