Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Why set origin attribute in bgp only take effect after reset bgp session?

hi!Dear all

It is said that "clear ip bgp neighbour-address soft out" will make routing policy take effect WITHOUT reset the bgp session;but when I do a lab to set the origin attribute in bgp route this command doesn't works.I must use "clear ip bgp neighbour-address" to reset bgp session to make it works.Is it?And are there other attritbutes in bgp be modified will take effect only after the bgp session reset?

below is my configration:

...

router bgp 100

no synchronization

bgp log-neighbor-changes

aggregate-address 192.168.192.0 255.255.248.0 attribute-map setorigin suppress-map filter

redistribute eigrp 100

neighbor 192.168.1.253 remote-as 200

neighbor 192.168.1.253 send-community

neighbor 192.168.1.253 route-map COMMUNITY out

no auto-summary

!

access-list 101 permit ip host 192.168.192.0 host 255.255.248.0

!

!

route-map setorigin permit 10

match ip address 101

set origin incomplete

...

In this lab I must reset the bgp session between this router and it's peer to let the route-map "setorigin" take effect.

Thanks a lot for your help!

2 ACCEPTED SOLUTIONS

Accepted Solutions
Cisco Employee

Re: Why set origin attribute in bgp only take effect after reset

The "clear ip bgp soft out" will usually do the trick for policies that are applie outbound on the neighbor. In your case the route-map is configured on the attribute-map on the aggregate statement. Try adding the "set origin incomplete" to the existing outbound route-map COMMUNITY. The "clear ip bgp soft out" should then work.

Hope this helps,

Harold Ritter
Sr. Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
Cisco Employee

Re: Why set origin attribute in bgp only take effect after reset

BTW: if you want the new policy to take effect in your current configuration without resetting the session, you could just remove and re-apply the aggregate statement. This will do the job too.

Hope this helps

Harold Ritter
Sr. Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
5 REPLIES
Cisco Employee

Re: Why set origin attribute in bgp only take effect after reset

The "clear ip bgp soft out" will usually do the trick for policies that are applie outbound on the neighbor. In your case the route-map is configured on the attribute-map on the aggregate statement. Try adding the "set origin incomplete" to the existing outbound route-map COMMUNITY. The "clear ip bgp soft out" should then work.

Hope this helps,

Harold Ritter
Sr. Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
Cisco Employee

Re: Why set origin attribute in bgp only take effect after reset

BTW: if you want the new policy to take effect in your current configuration without resetting the session, you could just remove and re-apply the aggregate statement. This will do the job too.

Hope this helps

Harold Ritter
Sr. Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
New Member

Re: Why set origin attribute in bgp only take effect after reset

hi!hritter

Thanks for your help!

Silver

Re: Why set origin attribute in bgp only take effect after reset

I could be wrong but something doesn't look right with access-list 101 as it is shown in the configuration...

Please rate all helpful posts.

Regards,

Brad

Purple

Re: Why set origin attribute in bgp only take effect after reset

Hi Brad,

When using an extended access-list with BGP, the 'source' portion of it matches the 'prefix' of the route and the 'destination' portion of it matches the mask of the prefix....

So in this case, ACL 101 matches 192.168.192.0/255.255.248.0 only..

Paresh

362
Views
0
Helpful
5
Replies
CreatePlease to create content