No Pim Neighbor with MVPNs

Static, RIP, EIGRP, OSPF, BGP, IBGP, IS-IS and any other routing.
Guest

Re:No Pim Neighbor with MVPNs

Post by Guest » Thu Feb 24, 2005 7:15 pm


Hi,I tested it and it's working fine for me:PE1--RR--PE2PE1 running 12.3(16a), non-MDT aware L0= 10.1.2.1RR and PE2 running 12.2(33)SRC2. MDT aware. L0: 100.100.2.1 and 10.1.2.2Debug on PE2:*Sep 28 15:10:07.165: %BGP-5-ADJCHANGE: neighbor 100.100.2.1 Up *Sep 28 15:10:07.169: BGP:from:3 to:3 update format 2:2001:10.1.2.1/32 MDT grp 232.0.0.1 pfxptr->masklen 128*Sep 28 15:10:13.541: BGP(4): ... start import cfg version = 5BGP: bpath->mdt 0xE8000001 232.0.0.1*Sep 28 15:10:14.381: BGP:from:3 to:3 update format 2:2000:10.1.2.2/32 MDT grp 232.0.0.1 pfxptr->masklen 128Debug from RR:00:05:56: BGP(3): 10.1.2.1 send UPDATE (format) 2:2000:10.1.2.2/32, next 10.1.2.2, metric 0, path Local, extended community RT:2:20 MDT:2:232.0.0.1Debugs from PE1:AS2-PE20#*Sep 28 15:15:34.595: BGP: Incoming path from 100.100.2.1*Sep 28 15:15:34.595: BGP: Accepted path from 100.100.2.1*Sep 28 15:15:34.595: BGP: Incoming MDT from 100.100.2.1 : present*Sep 28 15:15:34.595: BGP: Inform multicast system about mdt 232.0.0.1 from router-id 10.1.2.1 with next-hop 10.1.2.1 : present*Sep 28 15:15:34.595: BGP VPNV4: MPLS label changed for prefix 2:2:2001:10.1.2.1/32*Sep 28 15:15:34.595: BGP VPNV4: bestpath from neighbor 100.100.2.1 nexthop 10.1.2.1 new outlabel exp-nullAS2-PE20# AS2-PE20#sh ip pim mdt bgpPeer (Route Distinguisher + IPv4)                                  Next Hop  MDT group 232.0.0.1   2:2:2001:10.1.2.1                                               10.1.2.1AS2-PE20#AS2-PE20#sh ip mroute...(10.1.2.1, 232.0.0.1), 00:14:09/00:02:58, flags: sTIZ  Incoming interface: Ethernet0/0, RPF nbr 192.168.2.5  Outgoing interface list:    MVRF MVPN-IAS-B, Forward/Sparse, 00:14:09/00:02:10(10.1.2.2, 232.0.0.1), 00:31:52/00:03:27, flags: sT  Incoming interface: Loopback0, RPF nbr 0.0.0.0  Outgoing interface list:    Ethernet0/0, Forward/Sparse, 00:09:52/00:03:21(*, 224.0.1.40), 00:32:02/00:02:30, RP 0.0.0.0, flags: DCL  Incoming interface: Null, RPF nbr 0.0.0.0  Outgoing interface list:    Loopback0, Forward/Sparse, 00:32:02/00:02:20    Ethernet0/0, Forward/Sparse, 00:31:57/00:02:30AS2-PE20#sh ip pim vrf MVPN-IAS-B neighbor PIM Neighbor TableNeighbor          Interface                Uptime/Expires    Ver   DRAddress                                                            Prio/Mode10.1.2.1          Tunnel0                  00:17:15/00:01:41 v2    1 / SAS2-PE20#Can you check how the update is propagated from PE2 to PE1 ? Also please share your complete configuration.ThanksLaurent.

Guest

Re:No Pim Neighbor with MVPNs

Post by Guest » Thu Feb 24, 2005 8:13 pm


Hi LaurentMany thanks for this.OK I am using PIM SSM and here is the config attached. each router is linked by a 7600 router that performs IGP connectivity and PIM signalling.  

Guest

Re:No Pim Neighbor with MVPNs

Post by Guest » Thu Feb 24, 2005 9:18 pm


Hi Laurent Forgot to attach debugs from BGP updatesPE1)wsr17-kent-syd-test#clear ip bgp *wsr17-kent-syd-test#*Sep 28 15:02:20.484: %BGP-5-ADJCHANGE: neighbor 203.194.30.62 Down User reset*Sep 28 15:02:27.300: vpn: bgp_vpnv4_bnetinit: 20:1:172.17.20.1/32*Sep 28 15:02:30.176: %BGP-5-ADJCHANGE: neighbor 203.194.30.62 Up *Sep 28 15:02:30.176: BGP: Incoming path from 203.194.30.62*Sep 28 15:02:30.176: vpn: bgp_vpnv4_bnetinit: 20:1:172.17.20.3/32*Sep 28 15:02:30.176: BGP: Accepted path from 203.194.30.62*Sep 28 15:02:30.176: vpn: bgp_vpnv4_alloc_tag route_tag_change for mpls:172.17.20.1/255.255.255.255*Sep 28 15:02:30.176: vpn: tag_vpn_find_route_tags: 20:1:172.17.20.1*Sep 28 15:02:30.176: vpn: intag=1886, outtag=aggregate(mpls), outtag owner=BGP*Sep 28 15:02:40.196: %SEC-6-IPACCESSLOGS: list ssm-range permitted 239.232.0.17 1 packet*Sep 28 15:02:42.612: vpn: tag_vpn_find_route_tags: 20:1:172.17.20.3*Sep 28 15:02:42.612: vpn: intag=vpn-route, outtag=833, outtag owner=BGP*Sep 28 15:03:27.320: vpn: bgp_vpnv4_bnetinit: 2:20:1:203.194.30.63/32*Sep 28 15:03:27.320: vpn: bgp_vpnv4_alloc_tag route_tag_change for mpls:172.17.20.1/255.255.255.255*Sep 28 15:03:27.320: vpn: tag_vpn_find_route_tags: 20:1:172.17.20.1*Sep 28 15:03:27.320: vpn: intag=1886, outtag=aggregate(mpls), outtag owner=BGP*Sep 28 15:03:27.320: vpn: sourced prefix 2:20:1:203.194.30.63/32 not in any VRF, not allocating local label*Sep 28 15:03:27.932: vpn: sourced prefix 2:20:1:203.194.30.63/32 not in any VRF, not allocating local labelRR1)rrv01-kent-syd-test#clear ip bgp vpnv4 unicast 20rrv01-kent-syd-test#5d19h: %BGP_SESSION-5-ADJCHANGE: neighbor 203.194.30.61 VPNv4 Unicast topology base removed from session  User reset5d19h: %BGP_SESSION-5-ADJCHANGE: neighbor 203.194.30.61 IPv4 MDT topology base removed from session  User reset5d19h: %BGP-5-ADJCHANGE: neighbor 203.194.30.61 Down User reset5d19h: %BGP_SESSION-5-ADJCHANGE: neighbor 203.194.30.63 VPNv4 Unicast topology base removed from session  User reset5d19h: %BGP_SESSION-5-ADJCHANGE: neighbor 203.194.30.63 IPv4 MDT topology base removed from session  User reset5d19h: %BGP-5-ADJCHANGE: neighbor 203.194.30.63 Down User reset5d19h: BGP(3): 3 Inform multicast system about mdt [ #0:203.194.30.61, 0.0.0.0] from router-id 0.0.0.0 with next-hop 0.0.0.0 : absent5d19h: BGP(3): 3 Inform multicast system about mdt [ #0:203.194.30.63, 0.0.0.0] from router-id 0.0.0.0 with next-hop 0.0.0.0 : absent5d19h: %BGP-5-ADJCHANGE: neighbor 203.194.30.61 Up 5d19h: BGP(4): Incoming path from 203.194.30.615d19h: BGP(3): 3 Inform multicast system about mdt [ #0:203.194.30.61, 239.232.0.17] from router-id 203.194.30.61 with next-hop 203.194.30.61 : present5d19h: %BGP-5-ADJCHANGE: neighbor 203.194.30.63 Up 5d19h: BGP(4): Incoming path from 203.194.30.635d19h: BGP(4): Incoming path from 203.194.30.635d19h: BGP(3): 3 Inform multicast system about mdt [ #0:203.194.30.63, 239.232.0.17] from router-id 203.194.30.63 with next-hop 203.194.30.63 : presentPE2)*Sep 29 02:46:44.637 EST: vpn: free local label 1048577 for remote prefix mpls:172.17.20.1/32BGP: bpath->mdt 0xEFE80011 239.232.0.17*Sep 29 02:46:44.637 EST: BGP(3): 3 Inform multicast system about mdt [%Rx:203.194.30.63, 239.232.0.17] from router-id 203.194.30.62 with next-hop 203.194.30.63 : present*Sep 29 02:46:44.637 EST: BGP:from:3 to:3 update format 20:1:203.194.30.63/32 MDT grp 239.232.0.17 pfxptr->masklen 128*Sep 29 02:46:44.637 EST: BGP(4): Revise route installing 1 of 1 routes for 172.17.20.1/32 -> 203.194.30.63(mpls) to mpls IP table*Sep 29 02:46:44.637 EST: vpn: get path labels: 20:1:172.17.20.1/255.255.255.255*Sep 29 02:46:44.637 EST: vpn(4): inlabel=nolabel, outlabel=1886, outlabel owner=BGP*Sep 29 02:46:44.637 EST: vpn(4): Announce labels to IPRM mpls:172.17.20.1/32 gw 203.194.30.63 inlabel=nolabel, outlabel=1886

Guest

Re:No Pim Neighbor with MVPNs

Post by Guest » Thu Feb 24, 2005 10:54 pm


I don't see PE1 receiving any MDT updates from the RR.Can you run debug ip bgp vpnv4 unicast updates on both PE1 and RR and then do a clear ip bgp 203.194.30.63 soft out on the RR ?Could you also run SRC2 on the RR so we will have the same set-up.ThanksLaurent.

Guest

Re:No Pim Neighbor with MVPNs

Post by Guest » Fri Feb 25, 2005 12:20 am


OK debugs are here, I am running SRC4, are you sure you want me to downgrade to SRC2?RR1)rrv01-kent-syd-test#clear ip bgp 203.194.30.63rrv01-kent-syd-test#5d23h: %BGP_SESSION-5-ADJCHANGE: neighbor 203.194.30.63 VPNv4 Unicast topology base removed from session  User reset5d23h: %BGP_SESSION-5-ADJCHANGE: neighbor 203.194.30.63 IPv4 MDT topology base removed from session  User reset5d23h: %BGP-5-ADJCHANGE: neighbor 203.194.30.63 Down User reset5d23h: BGP(3): 3 Inform multicast system about mdt [ #0:203.194.30.63, 0.0.0.0] from router-id 0.0.0.0 with next-hop 0.0.0.0 : absent5d23h: %BGP-5-ADJCHANGE: neighbor 203.194.30.63 Up 5d23h: BGP(4): Incoming path from 203.194.30.635d23h: BGP(4): Incoming path from 203.194.30.635d23h: BGP(3): 3 Inform multicast system about mdt [ #0:203.194.30.63, 239.232.0.17] from router-id 203.194.30.63 with next-hop 203.194.30.63 : presentPE1wsr17-kent-syd-test#*Sep 28 19:16:20.923: %BGP-5-ADJCHANGE: neighbor 203.194.30.62 Down Peer closed the sessionwsr17-kent-syd-test#*Sep 28 19:16:34.307: %BGP-5-ADJCHANGE: neighbor 203.194.30.62 Up *Sep 28 19:16:34.307: BGP: Incoming path from 203.194.30.62*Sep 28 19:16:34.307: vpn: bgp_vpnv4_bnetinit: 20:1:172.17.20.3/32*Sep 28 19:16:34.307: BGP: Accepted path from 203.194.30.62*Sep 28 19:16:34.407: vpn: sourced prefix 2:20:1:203.194.30.63/32 not in any VRF, not allocating local label*Sep 28 19:16:48.579: vpn: tag_vpn_find_route_tags: 20:1:172.17.20.3*Sep 28 19:16:48.579: vpn: intag=vpn-route, outtag=868, outtag owner=BGP

Post Reply