BGP IPV4 soo community

Hi Guys ,
how can i configure bgp soo community in IPV4 network enviorment ? i have BGP IPv4 running in my network . no vrf's no vpnv4 bgp.. Simple IPv4 BGP with some IBGP and EBGP peers.i wanna advertise a network with soo community . how could i do this. any ideas please. and how can i verify that soo community is being advertised ..
here is what i tried.
address-family ipv4
neighbor x.x.x.x activate
neighbor x.x.x.x send-community both
neighbor x.x.x.x next-hop-self
neighbor x.x.x.x activate
neighbor x.x.x.x send-community both
neighbor x.x.x.x route-map med out
no auto-summary
network 10.1.75.0 mask 255.255.255.0 route-map extendcom
exit-address-family
route-map extendcom permit 30
set extcommunity soo 1001:1001
regards
amit

hello Amit,
see the answers in WAN ... forum
Best Regards
Giuseppe

Similar Messages

Bgp ipv4 mvpn prefix details ?

Hello,
Does anyone knows how to see more detailed information for bgp ipv4 mvpn prefix in IOS-XR. When I type "show bgp ipv4 mvpn summary" I see the prefixes received:
RP/0/RSP0/CPU0:XR#show bgp ipv4 mvpn
Thu Oct 31 14:55:33.649 BGT
BGP router identifier 192.168.0.1, local AS number 65001
BGP generic scan interval 60 secs
Non-stop routing is enabled
BGP table state: Active
Table ID: 0x0   RD version: 1269813008
BGP main routing table version 37
BGP NSR Initial initsync version 3 (Reached)
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 10:10
*>i[1][192.168.0.4]/40
                      192.168.0.4                   100      0 i
.....snipped
Processed 8 prefixes, 8 paths
RP/0/RSP0/CPU0:XR#
But it is not clear how to see more details regarding the prefix itself (communities, PMSI attributes etc). The interactive help only says this:
RP/0/RSP0/CPU0:XR#show bgp ipv4 mvpn ?
WORD                   ipv4 mvpn network
....snipped
I could not find any information in the docummentation.
Any help will be greatly appriciated!
Hristo

Found it!
Just copy the prefix without the RD value:
show bgp ipv4 mvpn [1][192.168.0.4]/40
Hristo

Bgp no-peer community

Could an expert help me understand bgp NO-PEER community as mentioned in
http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_6-2/bgp_communities.html?

Kashish
It is basically a way to restrict who you advertise routes to. There is an RFC for it, it is quite a short document so it won't take too long to read and it explains it more clearly than i could -
https://tools.ietf.org/html/rfc3765
Jon

InterAS MPLS Option C (BGP IPv4 + Labels) IOS XR with eBGP multihop session

Hello,
Right now we have InterAS MPLS Option C configured between 2 autonomous systems.
Now we need to add more bandwith and would like to add another interface between the two routers establishing a multihop session using loopbacks to load share traffic.
I know that IOS-XR does not automatically learn directly connected host routes so for the XR router to assign labels you'll need to configure a static host route to ensure MPLS forwarding to the neighboring AS.
This works with directly connected neighbors but when I try to enable the multihop session, the XR does not assign labels even configuring the staic host route.
Does anybody has a configuration like that working?
Thanks!!
Jose.

Hello Jose
There are basically two options in Option C L3VPN setup. I will discuss the first option for Multihop.
Following are the key points that distinguish the InterAS Option C from previous options.
1) External Multihop BGP address families are invoked between two different autonomous systems; however, these eBGP sessions are invoked between the route reflectors in each AS and not on the ASBR. The route reflector in each AS thus passes labeled ipv4 unicast VPN routes to the other AS. Note:- The route reflector in this case will have PE clients in the vpnv4 address family within that Autonomous System.
2) ASBRs facilitate the creation of InterAS LSP by providing labeled /32s for PE and Route Reflector loopback.
3) This option enhances scalability because ASBRs do not handle VPNv4 routes in fact this option gets rid of the extra L3VPN LFIB that is created as a result of option B . The LFIB size is minimal as we control the redistribution to the only 2 needed loopback addresses (remote ASBR and remote RR)
Sample config of the RR:
router bgp 102
address-family ipv4 unicast
address-family vpnv4 unicast
neighbor-group ibgp
remote-as 102
update-source Loopback0
address-family ipv4 unicast
   route-reflector-client
address-family vpnv4 unicast
   route-reflector-client
neighbor 192.168.253.3
remote-as 101
ebgp-multihop 255
description eBGP-RR-PEER-AS101
update-source Loopback0
address-family vpnv4 unicast
   route-policy allow-all in
   route-policy allow-all out
   next-hop-unchanged
neighbor 192.168.254.1
use neighbor-group ibgp
neighbor 192.168.254.3
use neighbor-group ibgp
neighbor 192.168.254.4
use neighbor-group ibgp
On the PE router, the config will look something like this:
router bgp 102
address-family ipv4 unicast
redistribute ospf 1 metric 3333 route-policy interAS-optionc-out
allocate-label route-policy interAS-optionc-out
neighbor 65.10.20.1
remote-as 101
address-family ipv4 labeled-unicast
   route-policy interAS-optionc-in in
   route-policy interAS-optionc-out out
neighbor 192.168.254.2
remote-as 102
update-source Loopback0
address-family ipv4 unicast
router static
address-family ipv4 unicast
65.10.20.1/32 TenGigE0/0/0/1
192.0.2.0/24 Null0 tag 10
route-policy interAS-optionc-in
if destination in remote-RR-PE then
    pass
else
    drop
endif
end-policy
route-policy interAS-optionc-out
if destination in local-RR-PE then
    pass
else
    drop
endif
end-policy
prefix-set local-RR-PE
192.168.254.2/32,
192.168.253.6/32,
192.168.253.5/32
end-set
prefix-set remote-RR-PE
192.168.253.2/32,
192.168.253.3/32,
192.168.253.3/32
end-set
Just for your clarification, 192.168.253.0/24 is the Remote AS networks and 192.168.254.0/24 is the local AS networks.
Hope this clarifies your doubts.
Cheers ... !!!
Vinit

BGP routing updates via VRF's fails on PE

HQ connects to 2 different remote sites via MPLS.
HQ connects to PE1 via MPLS vrf SITE1
HQ also connects to PE1 via MPLS vrf SITE2
WAN1 connects to PE2 via F0/0 vrf SITE1
WAN2 connects to PE2 via F0/1 vrf SITE2
HQ sees all prefixes from both remote sites!!
HQ and WAN1 can successfully ping/trace each other.
HQ and WAN2 can successfully ping/trace each other.
WAN1 only sees HQ prefixes
WAN2 only sees HQ prefixes
PE1 vrf SITE1 routing table sees HQ and WAN1 prefixes only
PE1 vrf SITE2 routing table sees HQ and WAN2 prefixes only
I can see from HQ that HQ is sending the same prefixes to both eBGP PE1 peers.
(I.E. sh bgp ipv4 uni nei x.x.x.x adv)
TOPOLOGY:
           /---MPLS--PE2------WAN1
HQ----PE1--
           \---MPLS--PE2------WAN2
HQ   AS 10
WAN1 AS 20
WAN2 AS 30
MPLS AS 65535
On PE1 and PE2
Under vrf SITE1, I added route-target import from vrf SITE2 and
Under vrf SITE2, I added route-target import from vrf SITE1 and this did not work at all.
HQ must remain in 2 different vrf's while the remotes are in different vrf's as well.
PROBLEM:
I need to be able to communicate between WAN1 to WAN2 via HQ.
Anyone know what might fix my problem????, Or can explain what is happening that causes this failure?
THANKS and BEST REGARDS
Frank

Hi Frank
Looking at your mentioned design above it seems all fine and should work..Just one question did you import the cross-vrf RTs after the normal setup was up and working ' coz in that case I think we would need to soft clear the BGP Process on PE1 to cross import the vrf routes from PE2..But on PE2 it should have worked fine..
May be as asked by Olivier you can share the configs once to look at it.
Coming to your second question of
PROBLEM:
I need to be able to communicate between WAN1 to WAN2 via HQ.
This is a case of MPLS Hub and Spoke VPN Services using eBGP as PE-CE..
Here we need to use 3 VRF with separe export RT for the Hub (HQ-VRF) and Spoke 1(Site 1-VRF) /Spoke 2(Site 2-VRF)
Hub will import the RT of Spoke 1 and Spoke 2 . SPoke 1/ Spoke 2 will import only HQ RT..
On PE1 create a default null route under VRF Hub and under BGP addess-family ipv4 vrf HQ-VRF send a default route using below network statement
network 0.0.0.0
This will help to achieve the desired traffic flow of WAN1 communicating to WAN2 via HQ..
Hope this provides some insight to your query.
Regards
Varma

Bgp path selection issue

hi,
i have the following cli show command output,
R2#show bgp ipv4 unicast
BGP table version is 11, local router ID is 192.168.220.252
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
* i192.168.30.0     192.168.110.70           0    100      0 63000 i
*>                  192.168.220.70           0             0 63000 63000 i
* i192.168.40.0     192.168.110.70           0    100      0 63000 63000 i
*>                  192.168.220.70           0             0 63000 i
R2#
why isn't the route through the shortest AS path not selected as the best route for 192.168.30.0. ?
thanks,
uddika

R2#
R2#
R2#show ip bgp 192.168.30.0
BGP routing table entry for 192.168.30.0/24, version 7
Paths: (2 available, best #2, table Default-IP-Routing-Table)
Advertised to update-groups:
     2
63000
    192.168.110.70 (inaccessible) from 192.168.111.251 (192.168.111.251)
      Origin IGP, metric 0, localpref 100, valid, internal
63000 63000, (received & used)
    192.168.220.70 from 192.168.220.70 (192.168.220.70)
      Origin IGP, metric 0, localpref 100, valid, external, best
R2#
R2#
thanks, i noticed that R2 does not have the route for the next hop, 192.168.110.70.

Prefix-list; clear bgp peer-group Test soft in; no file prompt quiet

Hello everyone,
I have a few simple questions. Hope someone will help me Thank you in advance.
1) We are using prefix-set into route-maps, but how I can use a prefix-list?
2) In classic IOS we have the command: clear bgp peer-group Test soft in
I don't see it in IOS-XR (Cisco IOS XR Software, Version 4.0.1):
RP/0/RSP0/CPU0:STH02#clear bgp ipv4 unicast ?
*                  Clear all peers and all routes from the BGP table
A.B.C.D or X:X::X BGP neighbor address to clear
as                 Clear peers in a specific AS
dampening          Clear route flap dampening information
external           Clear all external peers
flap-statistics    Clear flap statistics
nexthop            Clear nexthop
self-originated    Clear redistributed, network and aggregate routes originated here
shutdown           Clear all peers which were shut down due to low memory
3) In classic IOS we have the command: no file prompt quiet
I don't see it in IOS-XR. What is the command for IOS-XR?
I need it for the operation like this:
copy ftp://**:***@216.*.*.*/CUST_AS-TEST-in.prefixlist compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist
Wed Apr 18 12:02:00.936 UTC
Destination filename [/compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist]? !!!!   I don't need this question
Copy : Destination exists, overwrite ?[confirm]                                                   !!!!   I don't need this question
Accessing ftp://*:*@216.*.*.*/CUST_AS-TEST-in.prefixlist
C
584 bytes copied in      0 sec
Have a nice day,
Dimitry

Thank you Alexander for your reply. It is the good RPL description and I've got the idea of REFRESH capable peer.
BUT, I still don't find the answer on my 3-d question:
In classic IOS we have the command: no file prompt quiet
I don't see it in IOS-XR. What is the command for IOS-XR?
I need it for the operation like this:
copy ftp://**:***@216.*.*.*/CUST_AS-TEST-in.prefixlist compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist
Wed Apr 18 12:02:00.936 UTC
Destination filename [/compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist]? !!!!   I don't need this question
Copy : Destination exists, overwrite ?[confirm]                                                   !!!!   I don't need this question
Accessing ftp://*:*@216.*.*.*/CUST_AS-TEST-in.prefixlist
C
584 bytes copied in      0 sec
How can I suppress confirmations like this?
Destination filename [/compactflash:/PrefixFilters/CUST_AS-TEST-in.prefixlist]?
Copy : Destination exists, overwrite ?[confirm]
Dimitry

BGP allowas-in and split horizon problem.

Hi,
I need some help. I can't understand why R2 advertises back the same networks to the neighbor from that received.
My topology is:
R1 is in AS1, R2 is in AS2 and R3 is in AS3, I've eBGP R1-R2, and eBGP R2-R3.
R1 and R3 has configured allowas-in to permit routes with their own AS.
The problem is with eBGP Updates. The router R1 advertise 1.1.1.1/32 to R2, and R2 sent back to R1 the same route 1.1.1.1/32.
I think that should not happen according the BGP split horizon rules. R2 should not advertise those networks who learned from R1, unless R2 has a route with better metric.
The same behavior happens between R2 and R3.
Thanks in advance.
All the router had the same IOS: c7200-is-mz.123-14.T1.bin
R1 Configuration
R1#sh run | sec router
router bgp 1
no synchronization
bgp log-neighbor-changes
network 1.1.1.1 mask 255.255.255.255
neighbor 172.28.1.1 remote-as 2
neighbor 172.28.1.1 allowas-in 10
neighbor 172.28.1.1 soft-reconfiguration inbound
no auto-summary
R1#
R2 Configuration
router bgp 2
no synchronization
bgp log-neighbor-changes
neighbor 172.28.1.2 remote-as 1
neighbor 172.28.1.2 soft-reconfiguration inbound
neighbor 172.28.2.2 remote-as 3
neighbor 172.28.2.2 soft-reconfiguration inbound
no auto-summary
R2#
R3 Configuration
router eigrp 200
redistribute connected
redistribute bgp 3 metric 100000 10 255 100 1500
network 192.168.3.0 0.0.0.3
no auto-summary
router bgp 3
no synchronization
bgp log-neighbor-changes
redistribute connected
redistribute eigrp 200
neighbor 172.28.2.1 remote-as 2
neighbor 172.28.2.1 allowas-in 10
neighbor 172.28.2.1 soft-reconfiguration inbound
no auto-summary
R3#
R1 BGP Table, Advertised Route, Received Routes
R1#sh ip bgp
BGP table version is 6, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
* 1.1.1.1/32       172.28.1.1                             0 2 1 i
*>                  0.0.0.0                  0         32768 i
*> 3.3.3.3/32       172.28.1.1                             0 2 3 ?
*> 4.4.4.4/32       172.28.1.1                             0 2 3 ?
*> 172.28.2.0/30    172.28.1.1                             0 2 3 ?
*> 192.168.3.0/30   172.28.1.1                             0 2 3 ?
R1#
R1#sh ip bgp neighbors 172.28.1.1 advertised-routes
BGP table version is 6, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 1.1.1.1/32       0.0.0.0                  0         32768 i
Total number of prefixes 1
R1#
R1#sh ip bgp neighbors 172.28.1.1 received-routes
BGP table version is 6, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
* 1.1.1.1/32       172.28.1.1                             0 2 1 i
*> 3.3.3.3/32       172.28.1.1                             0 2 3 ?
*> 4.4.4.4/32       172.28.1.1                             0 2 3 ?
*> 172.28.2.0/30    172.28.1.1                             0 2 3 ?
*> 192.168.3.0/30   172.28.1.1                             0 2 3 ?
Total number of prefixes 5
R1#
R2 BGP Table, Advertised Route, Received Routes
R2#sh ip bgp
BGP table version is 7, local router ID is 172.28.2.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 1.1.1.1/32       172.28.1.2               0             0 1 i
*> 3.3.3.3/32       172.28.2.2               0             0 3 ?
*> 4.4.4.4/32       172.28.2.2          156160             0 3 ?
r> 172.28.2.0/30    172.28.2.2               0             0 3 ?
*> 192.168.3.0/30   172.28.2.2               0             0 3 ?
R2#
R2#
R2 Received routes from R1
R2#sh ip bgp neighbors 172.28.1.2 received-routes
BGP table version is 7, local router ID is 172.28.2.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 1.1.1.1/32       172.28.1.2               0             0 1 i
Total number of prefixes 1
R2#
R2 Advertised routes to R1
R2#sh ip bgp neighbors 172.28.1.2 advertised-routes
BGP table version is 7, local router ID is 172.28.2.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 1.1.1.1/32       172.28.1.2               0             0 1 i
*> 3.3.3.3/32       172.28.2.2               0             0 3 ?
*> 4.4.4.4/32       172.28.2.2          156160             0 3 ?
r> 172.28.2.0/30    172.28.2.2               0             0 3 ?
*> 192.168.3.0/30   172.28.2.2               0             0 3 ?
Total number of prefixes 5
R2#
R2 Received routes from R3
R2#sh ip bgp neighbors 172.28.2.2 received-routes
BGP table version is 7, local router ID is 172.28.2.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 3.3.3.3/32       172.28.2.2               0             0 3 ?
*> 4.4.4.4/32       172.28.2.2          156160             0 3 ?
r> 172.28.2.0/30    172.28.2.2               0             0 3 ?
*> 192.168.3.0/30   172.28.2.2               0             0 3 ?
Total number of prefixes 4
R2#
R2 Advertised routes to R3
R2#sh ip bgp neighbors 172.28.2.2 advertised-routes
BGP table version is 7, local router ID is 172.28.2.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 1.1.1.1/32       172.28.1.2               0             0 1 i
*> 3.3.3.3/32       172.28.2.2               0             0 3 ?
*> 4.4.4.4/32       172.28.2.2          156160             0 3 ?
r> 172.28.2.0/30    172.28.2.2               0             0 3 ?
*> 192.168.3.0/30   172.28.2.2               0             0 3 ?
Total number of prefixes 5
R2#
R3 BGP Table, Advertised Route, Received Routes
R3#sh ip bg
BGP table version is 7, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 1.1.1.1/32       172.28.2.1                             0 2 1 i
* 3.3.3.3/32       172.28.2.1                             0 2 3 ?
*>                  0.0.0.0                  0         32768 ?
* 4.4.4.4/32       172.28.2.1                             0 2 3 ?
*>                  192.168.3.2         156160         32768 ?
* 172.28.2.0/30    172.28.2.1                             0 2 3 ?
*>                  0.0.0.0                  0         32768 ?
* 192.168.3.0/30   172.28.2.1                             0 2 3 ?
*>                  0.0.0.0                  0         32768 ?
R3#
R3#sh ip bgp neighbors 172.28.2.1 advertised-routes
BGP table version is 7, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 3.3.3.3/32       0.0.0.0                  0         32768 ?
*> 4.4.4.4/32       192.168.3.2         156160         32768 ?
*> 172.28.2.0/30    0.0.0.0                  0         32768 ?
*> 192.168.3.0/30   0.0.0.0                  0         32768 ?
Total number of prefixes 4
R3#
R3#sh ip bgp neighbors 172.28.2.1 received-routes
BGP table version is 7, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 1.1.1.1/32       172.28.2.1                             0 2 1 i
* 3.3.3.3/32       172.28.2.1                             0 2 3 ?
* 4.4.4.4/32       172.28.2.1                             0 2 3 ?
* 172.28.2.0/30    172.28.2.1                             0 2 3 ?
* 192.168.3.0/30   172.28.2.1                             0 2 3 ?
Total number of prefixes 5
R3#

I agree with the previous posters. What you could do is look at show bgp ipv4 unicast 1.1.1.1 on R2. You will find that the prefix is associated with an update group. An update group is an optimisation within the router BGP process to reduce the processing overhead for generating updates to peers. If two peers have exactly the same outbound routing policy they would be in the same update group. If you looked at the update group show bgp ipv4 unicast update-group <number> you would probabably find that it would contain the peers 172.28.1.2 and 172.28.2.2.
This would mean that the 1.1.1.1 would be replicated to R1 and R3. Without remoteas-in configured R1 would reject the prefix due the AS path containing AS1 - you can see this if you look at the output from show bgp ipv4 unicast neighbor 172.28.1.1 towards the bottom you will see the quantity of prefixes that have been rejected and why - use debug ip bgp updates if you want to see this in real time.
When remoteas-in is configured the prefix from R2 is accepted into the BGP table - however this is irrelevant as it will never become the best-path due to the weight 32768 for the local origination. If R1 peered with R4 via eBGP for example only this best path would advertised and hence nothing is broken.
HTH

Redistributing BGP into ISIS

I have issue Reditributing BGP into ISIS network. I have Router R1 running ISIS Level-2 with a neighborn router R2 ISIS L1-L2. Router R1 has a peering BGP with another router, so I want to redistribute network that receives from peering BGP and anounce to its neighbour ISIS.
Here are go setting, all seems to be ok, but withen I check into R2 network 172.16.40.0 it gets "% Subnet not in table"
R1 ISIS
R1#sh isis neighbors
R2 L2   Gi9/3       172.30.100.98   UP    24       R1.09
router isis
net 49.0001.0000.0000.0024.00
is-type level-2-only
redistribute connected
redistribute bgp 11562 route-map Metricas level-1-2
route-map Metricas permit 10
match ip address 20
access-list 20 permit 172.16.40.0 0.0.0.255
R1#show ip bgp neighbors 172.16.40.38 received-routes
   Network          Next Hop            Metric LocPrf Weight Path
* i172.16.40.0/24 172.16.40.38             0    100      0 i
Command "redistribute bgp 11562 route-map Metricas level-1-2" I tried with "redistribute bgp 11562 route-map Metricas level-2" too, but didnt work. Please, help me

The prefix you're trying to redistribute into IS-IS is coming from an iBGP peering. By default, the BGP process will not redistribute iBGP into an IGP because this scenario can frequently create routing loops. If you really want to do this and you're sure your routing setup is stable, you can override this behaviour by adding the "bgp redistribute-internal" configuration command under your "router bgp" process.
Make sure you issue a "clear bgp ipv4 unicast *" to clear the BGP table once you've made the configuration change.

BGP Smoothing Interval Exceeded

I got this error meassge on one of customer routers where the BGP failed:
SYSLOG Smoothing Interval Exceeded Alarm:xxxxxxxxxx BGP-5-ADJCHANGE down 666 seconds which exceeds smoothing interval of 660 seconds for neighbor x.x.x.x.
the BGP config:
router bgp 65002
bgp log-neighbor-changes
network x.x.x.x mask x.x.x.x
timers bgp 15 45
neighbor x.x.x.x remote-as xxxxx
neighbor x.x.x.x description PE - load sharing
neighbor x.x.x.x soft-reconfiguration inbound
neighbor x.x.x.x route-map setmedprimary out
neighbor x.x.x.x filter-list 1 in
We found that the link was down between the CE and PE router, but I don't understeand why the BGP adjecency didn't fail on dead timer set to 45s.

Found it!
Just copy the prefix without the RD value:
show bgp ipv4 mvpn [1][192.168.0.4]/40
Hristo

"sh ip bgp ipv6" or "sh bgp ipv6"

Hi All,
im trying to clarify some confusion with where this is going in terms of show commands for bgp
when i first played with ipv6 bgp in 12.3 years back, the only way to view bgp v6 items was via "sh bgp ipv6", and this as far as i recall was meant to be the way forward for v4 too, and 'sh ip bgp' was to be removed in future ios releases.
Now im looking at SRE5 in the lab, and a 'sh bgp ipv6' gives me not output saying its deprecated, and 'show ip bgp ipv4' shows me all v4 and v6 bgp neighbour sessions.
if anyone can anyone shed some light on this it would be great since its a tad confusing, even more when you add vpnv4 to the mix.
thanks
Mark

Mark,
Let me try to answer your question like this.
As far as I know. Both commands are still valid (check int recent 15.2.1T release).
R2#show bgp ipv6 unicastBGP table version is 2, local router ID is 192.168.23.2Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-FilterOrigin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path*> 2001:DB8:2::/64 :: 0 32768 iR2#show ip bgp ipv6 unicastBGP table version is 2, local router ID is 192.168.23.2Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-FilterOrigin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path*> 2001:DB8:2::/64 :: 0 32768 i
What is deprecated is the command without "unicast" added.
R2#show ip bgp ipv6% Incomplete command.R2#show bgp ipv6BGP table version is 3, local router ID is 192.168.23.2Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-FilterOrigin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path*> 2001:DB8:2::/64 :: 0 32768 i% NOTE: This command is deprecated. Please use 'show bgp ipv6 unicast'
I'm not aware of anything specific to SRE that would cause it to be different.
Can you make share same outputs from your devices?
M.

Recursion Against IPv4+Labels prefix learned via iBGP

Hi,
Due to a number of reasons we have a rather unique requirement to use IPv4+labels as a means to install a BGP next-hop against which other labelled BGP routes can be resolved. Though this sounds fairly complex I was hoping to acheive this as follows, (basic example):
R1 (loop0 = a, loop1 = b) <---- -----> R2 (loop0 = y, loop1 = z)
There is an IGP session between R1 and R2, whereby loop0 and the inter-link are inserted into the IGP, a BGP IPv4 + labels session is established between loop0's (a and y), over this session R1 advertises b --> R2, and R2 advertises z --> R1. Using route-maps, further labelled prefixes advertised between R1 and R2 have the BGP next-hop modified to b and z respectively.
Everything looks as I would expect, labels advertised / received as I would expect, (RIB entires etc), however, CEF shows recursion issues. I have tried various IOS images but same (or similar) behaviour.
Should this work.. All CCO references to IPv4+labels (unless related to IPv6 prefix / path distribution) explicitly state eBGP IPv4+labels, but our requirement is for IPv4+labels in conjuction with iBGP.
(If I try a similar schema using LDP - this works fine, but unfortunately LDP is not an option in the production network).
Also note, the link between devices is Ethernet,
I can appreciate why this may not work, but conversely I see no reason (except implementation) why this will not work.
Can someone please confirm whether this should work, and if so which version of IOS for the C7200.
Thanks. Simon

Hi Simon,
BGP IPv4 + Labels relies on a MPLS aware core (BGP free core usually) so you need a label associated to your loopback 0. You used static mapping but LDP will do the job as well.
HTH
Laurent.

BGP AS Migration

Hi all.
I've just run into the following problem when configuring Dual Autonomous System Support for BGP.
We handle 2 AS numbers that we intend to merge.
R1 has the following config:
router bgp 10
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 192.168.0.2 remote-as 10
address-family ipv4
neighbor 192.168.0.2 activate
no auto-summary
no synchronization
exit-address-family
R2 is located in a different AS (As20) and we try to pretend it is in AS10 ( from R1 perspective). R2 config is as follows:
router bgp 20
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 192.168.0.1 remote-as 10
neighbor 192.168.0.1 local-as 10 no-prepend replace-as
address-family ipv4
neighbor 192.168.0.1 activate
no auto-summary
no synchronization
exit-address-
It seems that BGP session is properly established with this config. However as soon as we add a network command to originate a given prefix the bgp session goes down. We see the following when running a debug ip bgp:
*Mar 1 00:08:30.643: %BGP-3-NOTIFICATION: received from neighbor 192.168.0.1 3/3 (update missing required attributes) 0 bytes
*Mar 1 00:08:30.643: BGP: 192.168.0.1 went from Established to Closing *Mar 1 00:08:30.643: %BGP-3-NOTIFICATION: received from neighbor 192.168.0.1 3/3 (update missing required attributes) 0 bytes
*Mar 1 00:08:30.643: BGP: 192.168.0.1 went from Established to Closing
Then the BGP session is established again but it goes down inmediately.....
I haven't a clue about where the problem might be. Any suggestion?
Thanks
Flo.

Hi Riccardo
Thanks for your comments.
I've just run the ip bgp events/updates debug and this is what I can see in both sides:
R1 ( the router that receives the update)
*Mar 1 00:06:38.803: BGP: 192.168.0.2 Update missing attributes, flags 0x7
*Mar 1 00:06:38.807: BGP: 192.168.0.2 reset due to BGP Notification sent
*Mar 1 00:06:38.807: %BGP-5-ADJCHANGE: neighbor 192.168.0.2 Down BGP Notification sent
*Mar 1 00:06:38.807: %BGP-3-NOTIFICATION: sent to neighbor 192.168.0.2 3/3 (update missing required attributes) 0 bytes
R1# FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0035 0200 0000 1940 0101 0040 0204 0201 000A 4003 04C0 A800 0280 0404 0000 0000 2002 0202 02
*Mar 1 00:06:38.927: BGP: service reset requests
*Mar 1 00:06:38.927: BGP: service reset requests
R2(config)#router bgp 20
R2(config-router)#net
R2(config-router)#network 2.2.2.2 mask
R2(config-router)#network 2.2.2.2 mask 255.255.255.255
R2(config-router)#
*Mar 1 00:06:38.179: BGP(0): route 2.2.2.2/32 up
*Mar 1 00:06:38.179: BGP(0): nettable_walker 2.2.2.2/32 route sourced locally
*Mar 1 00:06:38.183: BGP(0): 192.168.0.1 send UPDATE (format) 2.2.2.2/32, next 192.168.0.2, metric 0, path Local
*Mar 1 00:06:38.251: %BGP-3-NOTIFICATION: received from neighbor 192.168.0.1 3/3 (update missing required attributes) 0 bytes
*Mar 1 00:06:38.255: BGP: 192.168.0.1 reset due to BGP Notification received
*Mar 1 00:06:38.255: %BGP-5-ADJCHANGE: neighbor 192.168.0.1 Down BGP Notification received
R2(config-router)#
*Mar 1 00:06:38.255: BGP: service reset requests
*Mar 1 00:06:38.259: BGP: service reset requests
*Mar 1 00:06:38.259: BGP: service reset requests
*Mar 1 00:06:38.259: BGP: service reset requests
R2(config-router)#
*Mar 1 00:06:39.675: BGP: Regular scanner event timer
*Mar 1 00:06:39.675: BGP: Performing BGP general scanning
*Mar 1 00:06:39.675: BGP(0): scanning IPv4 Unicast routing tables
*Mar 1 00:06:39.675: BGP(IPv4 Unicast): Performing BGP Nexthop scanning for general scan
*Mar 1 00:06:39.675: BGP(0): Future scanner version: 5, current scanner version: 4
*Mar 1 00:06:39.679: BGP(2): scanning VPNv4 Unicast routing tables
*Mar 1 00:06:39.679: BGP(VPNv4 Unicast): Performing BGP Nexthop scanning for general scan
*Mar 1 00:06:39.679: BGP(2): Future scanner version: 5, current scanner version: 4
*Mar 1 00:06:39.679: BGP(4): scanning IPv4 Multicast routing tables
*Mar 1 00:06:38.803: BGP: 192.168.0.2 Update missing attributes, flags 0x7
*Mar 1 00:06:38.807: BGP: 192.168.0.2 reset due to BGP Notification sent
*Mar 1 00:06:38.807: %BGP-5-ADJCHANGE: neighbor 192.168.0.2 Down BGP Notification sent
*Mar 1 00:06:38.807: %BGP-3-NOTIFICATION: sent to neighbor 192.168.0.2 3/3 (update missing required attributes) 0 bytes
R1# FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0035 0200 0000 1940 0101 0040 0204 0201 000A 4003 04C0 A800 0280 0404 0000 0000 2002 0202 02
*Mar 1 00:06:38.927: BGP: service reset requests
*Mar 1 00:06:38.927: BGP: service reset requests
R2 (router that is configured with the "local-as no-prepend replace-as"). As soon as I configured the network 2.2.2.2 mask 255.255.255.255 command to announce a loopback interface to the peer, everything is triggered. These are the debug messages:
R2(config)#router bgp 20
R2(config-router)#net
R2(config-router)#network 2.2.2.2 mask
R2(config-router)#network 2.2.2.2 mask 255.255.255.255
R2(config-router)#
*Mar 1 00:06:38.179: BGP(0): route 2.2.2.2/32 up
*Mar 1 00:06:38.179: BGP(0): nettable_walker 2.2.2.2/32 route sourced locally
*Mar 1 00:06:38.183: BGP(0): 192.168.0.1 send UPDATE (format) 2.2.2.2/32, next 192.168.0.2, metric 0, path Local
*Mar 1 00:06:38.251: %BGP-3-NOTIFICATION: received from neighbor 192.168.0.1 3/3 (update missing required attributes) 0 bytes
*Mar 1 00:06:38.255: BGP: 192.168.0.1 reset due to BGP Notification received
*Mar 1 00:06:38.255: %BGP-5-ADJCHANGE: neighbor 192.168.0.1 Down BGP Notification received
R2(config-router)#
*Mar 1 00:06:38.255: BGP: service reset requests
*Mar 1 00:06:38.259: BGP: service reset requests
*Mar 1 00:06:38.259: BGP: service reset requests
*Mar 1 00:06:38.259: BGP: service reset requests
R2(config-router)#
*Mar 1 00:06:39.675: BGP: Regular scanner event timer
*Mar 1 00:06:39.675: BGP: Performing BGP general scanning
*Mar 1 00:06:39.675: BGP(0): scanning IPv4 Unicast routing tables
*Mar 1 00:06:39.675: BGP(IPv4 Unicast): Performing BGP Nexthop scanning for general scan
*Mar 1 00:06:39.675: BGP(0): Future scanner version: 5, current scanner version: 4
*Mar 1 00:06:39.679: BGP(2): scanning VPNv4 Unicast routing tables
*Mar 1 00:06:39.679: BGP(VPNv4 Unicast): Performing BGP Nexthop scanning for general scan
*Mar 1 00:06:39.679: BGP(2): Future scanner version: 5, current scanner version: 4
*Mar 1 00:06:39.679: BGP(4): scanning IPv4 Multicast routing tables
Regarding the IOS, I'm currently using Version 12.4(25d),
Cheers!
Flo.

BGP Next-hop conflict with MPLS Label.

Hi, Experts
Equipment: Cisco ASR9922, IOS-XR 4.3.2
Issue: I have problem that my RR do the next-hop-self by using route-policy for client routers, the next-hop is changed as intended but the MPLS label doesn’t changed to reflect the new next-hop.
What I would like to achieve: I would like RR to set next-hop-self only for selected prefixes(172.168.0.0/24, 0.0.0.0/0) but maintain original next-hop for the rest, I do this by using route-policy.
Detail:
I have routers running MPLS infrastructure with ASR9922 as an RR. RN router is in neighbor-group RN and CPE-xx routers are in neighbor-group AN.
•-       Every routers are in same BGP AS64549.
•-       RN sends prefixes 0.0.0.0/0 and 172.168.0.0/24 to RR.
•-       CPE-25 sends prefix 192.168.25.1/32 to RR.
Neighbor-group AN has the route-policy AN-OUT2 to set next-hop of prefix 172.168.0.0/24 and 0.0.0.0/0 to RR#loopback1 before send out update to CPE routers. Below is BGP and RPL configuration at RR.
router bgp 64549
nsr
bgp graceful-restart
ibgp policy out enforce-modifications
address-family vpnv4 unicast
additional-paths receive
additional-paths send
additional-paths selection route-policy ADD-PATH-iBGP
retain route-target all
neighbor-group AN
remote-as 64549
cluster-id 172.16.1.11
update-source Loopback1
address-family vpnv4 unicast
   route-reflector-client
   route-policy AN-OUT2 out
   soft-reconfiguration inbound
route-policy AN-OUT2
if destination in DEFAULT or destination in RNC then
    set next-hop 192.168.10.11
else
    pass
endif
end-policy
This is what RR advertises to CPE-24
RP/0/RP0/CPU0:RR#show bgp vpnv4 unicast neighbors 192.168.10.24 advertised-routes
Fri Dec 20 15:23:14.931 BKK
Network            Next Hop        From            AS Path
Route Distinguisher: 64549:3339
0.0.0.0/0          192.168.10.11   172.16.1.1      ?
                                   172.16.1.2      ?
172.168.0.0/24     192.168.10.11   172.16.1.1      ?
                                   172.16.1.2      ?
192.168.0.1/32     192.168.10.11   192.168.10.24   i
192.168.0.26/32    192.168.10.26   192.168.10.26   i
192.168.25.1/32    192.168.10.25   192.168.10.25   i
192.168.211.8/30   192.168.10.22   192.168.10.22   i
The IP part works as intended but MPLS Label doesn’t work as intended. Please take a look at RN who is originates 172.168.0.0/24, label 16025 is locally assigned.
RP/0/RP0/CPU0:RN1#show bgp vpnv4 unicast labels
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop        Rcvd Label      Local Label
Route Distinguisher: 64549:3339 (default for vrf VLAN3339)
*> 0.0.0.0/0          0.0.0.0         nolabel         16025
* i                   172.16.1.11     16068           16025
* i                   172.16.1.13     16033           16025
*> 172.168.0.0/24     0.0.0.0         nolabel         16025
* i                   172.16.1.11     16059           16025
* i                   172.16.1.13     16024           16025
172.168.0.0/24 at RR, label 16059 is locally assigned, label 16025 is receive from RN router. It should send 172.168.0.0/24 with label 16059 to CPE-24 to reflect next-hop changed.
RP/0/RSP0/CPU0:RR#show bgp vpnv4 unicast labels
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop        Rcvd Label      Local Label
Route Distinguisher: 64549:3339
*>i0.0.0.0/0          172.16.1.1      16025           16068
* i                   172.16.1.2      16007           16068
*>i172.168.0.0/24     172.16.1.1      16025           16059
* i                   172.16.1.2      16007           16059
*>i192.168.0.1/32     192.168.10.24   131070          16060
*>i192.168.25.1/32    192.168.10.25   131070          16062
*>i192.168.211.8/30   192.168.10.22   131070          16065
What I found at CPE-24 which is Alcatel router is that, RR send prefix 172.168.0.0/24, nh 192.168.10.11 with label 16025 which is incorrect.
A:CPE-24# show router bgp routes vpn-ipv4 172.168.0.0/24
===============================================================================
BGP Router ID:192.168.10.24    AS:64549       Local AS:64549
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best, b - backup
===============================================================================
BGP VPN-IPv4 Routes
===============================================================================
Flag Network                                            LocalPref   MED
      Nexthop                                            Path-Id     VPNLabel
      As-Path
u*>? 64549:3339:172.168.0.0/24                          100         0
      192.168.10.11                                      None        16025
      No As-Path
Routes : 1
===============================================================================
On RR If I just remove the policy and do the next-hop-self under vpv4 address family, CPE-24 will get corrent nh with correct label(16059) but that won’t achieve our requirement to change nh only on selected prefixes. Is this software problem? Or is there any solution to work around?
Regard,
Marit

Hello Marit,
I am able to recreate this in the lab, and unfortunately this scenario is not supported. BGP does not advertise allocated label if we set nexhop using route policy. The only way is by next-hop-self configured on RR, and yes it eventually will applies to all prefixes advertised to neighbor-group AN. Currently i do not have workaround available.
Below is the capture of what i have tested in the lab:
The topology:
CRS-4-02 ---------- CRS-8-01 ------------ ASR-9006-1
CRS-8-01 is Route-reflector of CRS-4-02 and ASR-9006-1.
CRS-4-02 advertise some prefixes.
This issue occurs when RR have route-policy toward ASR-9006-1, where it assign incorrect label. But it assign correct label if CRS-8-01 use next-hop-self.
Below is the test done in the lab if RR use next-hop-self:
RP/0/RP0/CPU0:CRS-4-02#show run router bgp
Tue Jan 7 08:16:18.945 UTC
router bgp 1
bgp router-id 172.16.4.1
ibgp policy out enforce-modifications
address-family ipv4 unicast
address-family vpnv4 unicast
neighbor 172.16.8.3
remote-as 1
update-source Loopback0
address-family ipv4 unicast
address-family vpnv4 unicast
   route-policy PASS in
   route-policy PASS out
vrf RTAMAELA
rd 100:1
address-family ipv4 unicast
   redistribute connected
RP/0/RP0/CPU0:CRS-4-02#show bgp vpnv4 unicast advertised summary
Tue Jan 7 08:16:29.001 UTC
Network            Next Hop        From             Advertised to
Route Distinguisher: 100:1
78.22.11.2/32      172.16.4.1      Local            172.16.8.3
78.22.11.3/32      172.16.4.1      Local            172.16.8.3
93.22.15.61/32     172.16.4.1      Local            172.16.8.3
RP/0/RP0/CPU0:CRS-4-02#
RP/0/RP0/CPU0:CRS-4-02#show bgp vpnv4 unicast labels
Tue Jan 7 08:16:53.655 UTC
BGP router identifier 172.16.4.1, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0
BGP main routing table version 57
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop        Rcvd Label      Local Label
Route Distinguisher: 100:1 (default for vrf RTAMAELA)
*>i22.51.32.77/32     172.16.8.3      16056           nolabel
*> 78.22.11.2/32      0.0.0.0         nolabel         16003
*> 78.22.11.3/32      0.0.0.0         nolabel         16003
*> 93.22.15.61/32     0.0.0.0         nolabel         16003
Processed 4 prefixes, 4 paths
RP/0/RP0/CPU0:CRS-4-02#
RP/0/RP1/CPU0:CRS-8-01#show run router bgp
Wed Jan 8 11:07:05.436 UTC
router bgp 1
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
allocate-label all
address-family vpnv4 unicast
retain route-target all
neighbor-group AN
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
   route-reflector-client
   next-hop-self                              <-- use next-hop-self toward ASR-9006-1
   soft-reconfiguration inbound
neighbor-group RN
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
   route-reflector-client
   next-hop-self
   soft-reconfiguration inbound
neighbor 10.10.10.10
remote-as 1
address-family ipv4 unicast
neighbor 72.15.48.5
use neighbor-group AN
neighbor 172.16.4.1
use neighbor-group RN
RP/0/RP1/CPU0:CRS-8-01#show bgp vpnv4 unicast labels
Wed Jan 8 11:07:09.091 UTC
BGP router identifier 172.16.8.3, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0   RD version: 344169
BGP main routing table version 92
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop        Rcvd Label      Local Label
Route Distinguisher: 100:1
*>i22.51.32.77/32     72.15.48.5      16000           16056
*>i78.22.11.2/32      172.16.4.1      16003           16053
*>i78.22.11.3/32      172.16.4.1      16003           16054
*>i93.22.15.61/32     172.16.4.1     16003           16055
Processed 4 prefixes, 4 paths
RP/0/RP1/CPU0:CRS-8-01#
RP/0/RSP1/CPU0:ASR-9006-01#show run router bgp
Wed Jan 8 17:02:02.796 UTC
router bgp 1
bgp router-id 72.15.48.5
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
address-family vpnv4 unicast
retain route-target all
neighbor-group RR
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
   route-reflector-client
   soft-reconfiguration inbound
neighbor 172.16.8.3
use neighbor-group RR
neighbor 192.169.1.2
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
   route-policy PASS in
   route-policy PASS out
vrf RTAMAELA
rd 100:1
address-family ipv4 unicast
   redistribute connected
RP/0/RSP1/CPU0:ASR-9006-01#show bgp vpnv4 unicast labels
Wed Jan 8 17:02:04.381 UTC
BGP router identifier 72.15.48.5, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0   RD version: 253825
BGP main routing table version 126
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop        Rcvd Label      Local Label
Route Distinguisher: 100:1 (default for vrf RTAMAELA)
*> 22.51.32.77/32     0.0.0.0         nolabel         16000
*>i78.22.11.2/32      172.16.8.3      16053           nolabel          <== 172.16.8.3 is the loopback address of CRS-8-01
*>i78.22.11.3/32      172.16.8.3      16054           nolabel
*>i93.22.15.61/32     172.16.8.3      16055           nolabel
Processed 4 prefixes, 4 paths
RP/0/RSP1/CPU0:ASR-9006-01#
From output above we can see that ASR-9006-01 received correct label for each prefix.
Below is the output with route-policy configured and ASR-9006-01 receive incorrect label:
RP/0/RP1/CPU0:CRS-8-01#show run router bgp
Wed Jan 8 11:04:46.310 UTC
router bgp 1
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
allocate-label all
address-family vpnv4 unicast
retain route-target all
neighbor-group AN
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
   route-reflector-client
   route-policy RTAMAELA out
   soft-reconfiguration inbound
neighbor-group RN
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
   route-reflector-client
   next-hop-self
   soft-reconfiguration inbound
neighbor 72.15.48.5
use neighbor-group AN
neighbor 172.16.4.1
use neighbor-group RN
RP/0/RP1/CPU0:CRS-8-01#show run route-policy RTAMAELA
Wed Jan 8 11:16:06.847 UTC
route-policy RTAMAELA
if destination in RNC then
    set next-hop 172.16.8.3
else
    pass
endif
end-policy
RP/0/RP1/CPU0:CRS-8-01#show run prefix-set RNC
Wed Jan 8 11:16:12.099 UTC
prefix-set RNC
78.22.11.3/32
end-set
RP/0/RP1/CPU0:CRS-8-01#show bgp vpnv4 unicast labels
Wed Jan 8 11:04:33.512 UTC
BGP router identifier 172.16.8.3, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0   RD version: 344013
BGP main routing table version 92
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop        Rcvd Label      Local Label
Route Distinguisher: 100:1
*>i22.51.32.77/32     72.15.48.5      16000           16056
*>i78.22.11.2/32      172.16.4.1      16003           16053
*>i78.22.11.3/32      172.16.4.1      16003           16054
*>i93.22.15.61/32     172.16.4.1      16003           16055
Processed 4 prefixes, 4 paths
RP/0/RP1/CPU0:CRS-8-01#
RP/0/RSP1/CPU0:ASR-9006-01#show run router bgp
Wed Jan 8 16:59:41.601 UTC
router bgp 1
bgp router-id 72.15.48.5
bgp graceful-restart
ibgp policy out enforce-modifications
address-family ipv4 unicast
address-family vpnv4 unicast
retain route-target all
neighbor-group RR
remote-as 1
update-source Loopback0
graceful-restart
address-family vpnv4 unicast
   route-reflector-client
   soft-reconfiguration inbound
neighbor 172.16.8.3
use neighbor-group RR
neighbor 192.169.1.2
remote-as 1
update-source Loopback0
address-family vpnv4 unicast
   route-policy PASS in
   route-policy PASS out
vrf RTAMAELA
rd 100:1
address-family ipv4 unicast
   redistribute connected
RP/0/RSP1/CPU0:ASR-9006-01#show bgp ipv4 unicast labels
Wed Jan 8 16:59:52.173 UTC
RP/0/RSP1/CPU0:ASR-9006-01#show bgp vpnv4 unicast labels
Wed Jan 8 17:00:00.457 UTC
BGP router identifier 72.15.48.5, local AS number 1
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0x0   RD version: 253701
BGP main routing table version 123
BGP scan interval 60 secs
Status codes: s suppressed, d damped, h history, * valid, > best
              i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network            Next Hop        Rcvd Label      Local Label
Route Distinguisher: 100:1 (default for vrf RTAMAELA)
*> 22.51.32.77/32     0.0.0.0         nolabel         16000
*>i78.22.11.2/32      172.16.4.1      16003           nolabel
*>i78.22.11.3/32      172.16.8.3      16003           nolabel   <-- It receive label 16003, which is wrong. it should receive label 16054.
*>i93.22.15.61/32     172.16.4.1      16003           nolabel
Processed 4 prefixes, 4 paths
RP/0/RSP1/CPU0:ASR-9006-01#
Rivalino

BGP Troublshooting

I have configured network contaion 3 routers R1----R2-----R3, router 2 & 3 connected together via EBGP direct connect & router 1 & 2 connect together via IBGP , I have Advertise the follwoing networks 10.10.10.0, 20.20.20.0, 30.30.30.0, from router 3 to router 2 , the problem is i have the previous subnets in my router 1 but i cannot ping to it also when i have turn on debug ip BGP events i have the follwoing massage :
Mar 5 15:34:30.063: BGP: Regular scanner event timer
*Mar 5 15:34:30.063: BGP: Import timer expired. Walking from 1 to 1
*Mar 5 15:34:45.063: BGP: Regular scanner event timer
*Mar 5 15:34:45.063: BGP: Performing BGP general scanning
*Mar 5 15:34:45.063: BGP(0): scanning IPv4 Unicast routing tables
*Mar 5 15:34:45.063: BGP(IPv4 Unicast): Performing BGP Nexthop scanning for general scan
*Mar 5 15:34:45.067: BGP(0): Future scanner version: 70, current scanner version: 69
*Mar 5 15:34:45.067: BGP(1): scanning IPv6 Unicast routing tables
*Mar 5 15:34:45.071: BGP(IPv6 Unicast): Performing BGP Nexthop scanning for general scan
*Mar 5 15:34:45.071: BGP(1): Future scanner version: 71, current scanner version: 70
*Mar 5 15:34:45.071: BGP(2): scanning VPNv4 Unicast routing tables
*Mar 5 15:34:45.071: BGP(VPNv4 Unicast): Performing BGP Nexthop scanning for general scan
*Mar 5 15:34:45.071: BGP(2): Future scanner version: 71, current scanner version: 70
*Mar 5 15:34:45.071: BGP(4): scanning IPv4 Multicast routing tables
*Mar 5 15:34:45.075: BGP(IPv4 Multicast): Performing BGP Nexthop scanning for general scan
*Mar 5 15:34:45.075: BGP(4): Future scanner version: 71, current scanner version: 70
*Mar 5 15:34:45.075: BGP(5): scanning IPv6 Multicast routing tables
*Mar 5 15:34:45.075: BGP(IPv6 Multicast): Performing BGP Nexthop scanning for general scan
*Mar 5 15:34:45.075: BGP(5): Future scanner version: 71, current scanner version: 70
Best Regards

Hi Ven :
( Router 3)
MAIN-SOURSE#show ip bgp
BGP table version is 4, local router ID is 40.40.40.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 20.20.20.0/32    0.0.0.0                  0         32768 i
*> 30.30.30.0/32    0.0.0.0                  0         32768 i
*> 40.40.40.0/32    0.0.0.0                  0         32768 i
MAIN-SOURSE#
router bgp 400
no synchronization
bgp log-neighbor-changes
network 20.20.20.0 mask 255.255.255.255
network 30.30.30.0 mask 255.255.255.255
network 40.40.40.0 mask 255.255.255.255
neighbor 217.173.48.206 remote-as 500
no auto-summary
ip forward-protocol nd
ip route 20.20.20.0 255.255.255.255 Null0
ip route 30.30.30.0 255.255.255.255 Null0
ip route 30.30.30.1 255.255.255.255 Null0
ip route 40.40.40.0 255.255.255.255 Null0
ip route 40.40.40.1 255.255.255.255 Null0
MAIN-SOURSE#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater
Device ID        Local Intrfce     Holdtme    Capability Platform Port ID
ISP-Main         Gig 0/0            159          R        7206VXR   Gig 0/0
MAIN-SOURSE#
( Router 2)
ISP-Main#show ip bgp
BGP table version is 4, local router ID is 217.173.48.206
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*> 20.20.20.0/32    217.173.48.205           0             0 400 i
*> 30.30.30.0/32    217.173.48.205           0             0 400 i
*> 40.40.40.0/32    217.173.48.205           0             0 400 i
router bgp 500
no synchronization
bgp log-neighbor-changes
neighbor 172.21.1.2 remote-as 500
neighbor 172.21.1.2 next-hop-self
neighbor 217.173.48.205 remote-as 400
no auto-summary
ISP-Main#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater
Device ID        Local Intrfce     Holdtme    Capability Platform Port ID
Router           Gig 1/0            126          R        7206VXR   Gig 0/0
MAIN-SOURSE      Gig 0/0            126          R        7206VXR   Gig 0/0
( Router 1)
Router#show ip bgp
BGP table version is 4, local router ID is 172.21.1.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
*>i20.20.20.0/32    172.21.1.1               0    100      0 400 i
*>i30.30.30.0/32    172.21.1.1               0    100      0 400 i
*>i40.40.40.0/32    172.21.1.1               0    100      0 400 i
Router#
router bgp 500
no synchronization
bgp log-neighbor-changes
neighbor 172.21.1.1 remote-as 500
no auto-summary
ip forward-protocol nd
no ip http server
no ip http secure-server
Router#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater
Device ID        Local Intrfce     Holdtme    Capability Platform Port ID
ISP-Main         Gig 0/0            171          R        7206VXR   Gig 1/0
Router#

BGP IPV4 soo community

Similar Messages

Maybe you are looking for