Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
709
Views
1
Helpful
3
Replies

configuring mpls vpn multicast

Go to solution
bob brennan
Level 1
Level 1

‎01-04-2016 08:59 AM - edited ‎03-08-2019 03:17 AM

I am trying to configure multicast of our test mpls vpn network and I cannot get it to work. below is the configuration for each pe, p, and rr routers. i have omitted the interface with the ip pim statements because i have verified that multicast works in this environment. I am not sure what I am missing but it will not work. any help would be greatly appreciated. I verified that multicast does run when not using the vrf's. the error message I get is below from PE1 trying to ping PE2 interface.

Jan  4 09:55:24: IP(0): s=172.18.2.1 (Loopback1) d=239.1.1.1 (FastEthernet0/0) id=17760, ttl=255, prot=47, len=82(82), mforward
Jan  4 09:55:35: IP(0): s=172.18.2.1 (Loopback1) d=239.1.1.1 (FastEthernet0/0) id=17761, ttl=255, prot=47, len=52(52), mforward
Jan  4 09:55:43: IP(0): s=172.18.2.1 (Loopback1) d=239.1.1.1 (FastEthernet0/0) id=17762, ttl=255, prot=47, len=124(124), mforward
Jan  4 09:55:43: IP(1): s=172.18.60.60 (Loopback60) d=239.12.12.12 id=91, ttl=254, prot=1, len=100(100), RPF lookup failed for source or RP
Jan  4 09:55:43: IP(1): s=172.18.2.1 (Tunnel0) d=239.12.12.12 id=91, ttl=254, prot=1, len=100(100), RPF lookup failed for source or RP
test-network-dist2811-1#   

PE1

ip vrf mvpn1
 rd 10:1
 route-target export 10:1
 route-target import 10:1
 mdt default 239.1.1.1

ip multicast-routing
ip multicast-routing vrf mvpn1

interface Loopback1
 ip address 172.18.2.1 255.255.255.255
 ip pim sparse-mode

interface Loopback60
 ip vrf forwarding mvpn1
 ip address 172.18.60.60 255.255.255.255
 ip pim sparse-mode

router bgp 65000
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 172.18.22.1 remote-as 65000
 neighbor 172.18.22.1 update-source Loopback1
 !
 address-family ipv4 mdt
  neighbor 172.18.22.1 activate
  neighbor 172.18.22.1 send-community extended
 exit-address-family
 !
 address-family vpnv4
  neighbor 172.18.22.1 activate
  neighbor 172.18.22.1 send-community extended
 exit-address-family
 !
 address-family ipv4 vrf mvpn3
  redistribute connected
  no synchronization
 exit-address-family
 !
 address-family ipv4 vrf mvpn2
  redistribute connected
  no synchronization
 exit-address-family
 !
 address-family ipv4 vrf mvpn1
  redistribute connected
  no synchronization
 exit-address-family

ip pim rp-address 172.18.100.1
ip pim vrf mvpn1 rp-address 172.18.100.1

PE2

ip vrf mvpn1
 rd 10:1
 route-target export 10:1
 route-target import 10:1
 mdt default 239.1.1.1

ip multicast-routing
ip multicast-routing vrf mvpn1

interface Loopback1
 ip address 172.18.1.1 255.255.255.255
 ip pim sparse-mode
!
interface Loopback50
 ip vrf forwarding mvpn1
 ip address 172.18.50.50 255.255.255.255
 ip pim sparse-mode
 ip igmp join-group 239.12.12.12

router bgp 65000
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 172.18.22.1 remote-as 65000
 neighbor 172.18.22.1 update-source Loopback1
 !
 address-family ipv4 mdt
  neighbor 172.18.22.1 activate
  neighbor 172.18.22.1 send-community extended
 exit-address-family
 !
 address-family vpnv4
  neighbor 172.18.22.1 activate
  neighbor 172.18.22.1 send-community extended
 exit-address-family
 !
 address-family ipv4 vrf mvpn4
  redistribute connected
  no synchronization
 exit-address-family
 !
 address-family ipv4 vrf mvpn1
  redistribute connected
  no synchronization
 exit-address-family

ip pim rp-address 172.18.100.1
ip pim vrf mvpn1 rp-address 172.18.100.1

P router

ip multicast-routing

interface Loopback100
 ip address 172.18.100.1 255.255.255.255
 ip pim sparse-mode

ip pim rp-address 172.18.100.1

RR router

ip multicast-routing

 interface Loopback1
 ip address 172.18.22.1 255.255.255.255
 ip pim sparse-mode
!

router bgp 65000
 no bgp default ipv4-unicast
 bgp cluster-id 192.168.100.1
 bgp log-neighbor-changes
 neighbor rr-client peer-group
 neighbor rr-client remote-as 65000
 neighbor rr-client update-source Loopback1
 neighbor 172.18.1.1 peer-group rr-client
 neighbor 172.18.2.1 peer-group rr-client
 neighbor 172.18.3.1 peer-group rr-client
 neighbor 172.18.19.1 peer-group rr-client
 !
 address-family ipv4 mdt
  neighbor rr-client send-community extended
  neighbor rr-client route-reflector-client
  neighbor 172.18.1.1 activate
  neighbor 172.18.2.1 activate
  neighbor 172.18.3.1 activate
  neighbor 172.18.19.1 activate
 exit-address-family
 !
 address-family vpnv4
  neighbor rr-client send-community extended
  neighbor rr-client route-reflector-client
  neighbor 172.18.1.1 activate
  neighbor 172.18.2.1 activate
  neighbor 172.18.3.1 activate
  neighbor 172.18.19.1 activate
 exit-address-family

ip pim rp-address 172.18.100.1

sh ip mroute from each device

P router

IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.1.1.1), 5d00h/00:02:45, RP 172.18.100.1, flags: S
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet8/36, Forward/Sparse, 5d00h/00:02:45
    GigabitEthernet8/45, Forward/Sparse, 5d00h/00:02:42

(172.18.2.1, 239.1.1.1), 5d00h/00:03:29, flags: T
  Incoming interface: GigabitEthernet8/36, RPF nbr 172.17.253.213, RPF-MFD
  Outgoing interface list:
    GigabitEthernet8/45, Forward/Sparse, 5d00h/00:02:42, H

(172.18.1.1, 239.1.1.1), 5d00h/00:03:29, flags: T
  Incoming interface: GigabitEthernet8/45, RPF nbr 172.17.253.221, RPF-MFD
  Outgoing interface list:
    GigabitEthernet8/36, Forward/Sparse, 5d00h/00:02:45, H

(*, 225.2.2.2), 3d22h/00:02:58, RP 172.18.100.1, flags: SJC
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet8/45, Forward/Sparse, 3d22h/00:02:58

(*, 224.0.1.40), 5d00h/00:02:53, RP 172.18.100.1, flags: SJCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet8/44, Forward/Sparse, 4d01h/00:02:10
    GigabitEthernet8/45, Forward/Sparse, 5d00h/00:02:53
    GigabitEthernet8/36, Forward/Sparse, 5d00h/00:02:10

RR router

IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group,
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.0.1.40), 5d00h/00:02:34, RP 172.18.100.1, flags: SJPL
  Incoming interface: FastEthernet0/1, RPF nbr 172.17.253.226
  Outgoing interface list: Null

PE1

test-network-dist2811-1# sh ip mroute vrf mvpn1
Load for five secs: 2%/0%; one minute: 2%; five minutes: 2%
Time source is NTP, 10:02:44.861 arizona Mon Jan 4 2016

IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group,
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.0.1.40), 5d00h/00:02:48, RP 172.18.100.1, flags: SJCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Tunnel0, Forward/Sparse, 4d01h/00:02:48

PE2

test-network-dist2811-2#sh ip mroute vrf mvpn1
Load for five secs: 2%/0%; one minute: 2%; five minutes: 2%
Time source is NTP, 10:03:27.886 arizona Mon Jan 4 2016

IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group,
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.12.12.12), 01:16:20/00:02:06, RP 172.18.100.1, flags: SJCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback50, Forward/Sparse, 00:14:22/00:02:06

(*, 224.0.1.40), 4d01h/00:02:05, RP 172.18.100.1, flags: SJPL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Peter Paluch
Cisco Employee
Cisco Employee

‎01-04-2016 04:08 PM

Hi Bob,

When looking at your configuration, the RP address 172.18.100.1 that is being defined for the VRF mvpn1 does not seem to be correct. This IP address has to exist and be reachable within that particular VRF, and it is entirely independent of the 172.18.100.1 that exists in the global routing table. Incidentally, this IP address is your P router, the one that has no clue about VRFs and customers and their MVPNs, and conversely, this IP address does not seem to exist anywhere in the VPN as there is no interface assigned to VRF mvpn1 in your configs that would be carrying this IP address. Surely, PEs and CEs that - within the VPN created by VRF mvpn1 - have no visibility into your core network cannot use the P router as the RP.

You will need to designate one of the routers that has a visibility into this VPN to be an RP for this VPN. This precludes using any of the P routers for this purpose. The RP for this VPN must be either one of the PEs, or any of the CE/C routers. Of course, all routers within this VPN must know about it.

The easiest thing to do is to create a new loopback on some of the PEs, put it into VRF mvpn1, configure it with 172.18.100.1 and have this loopback advertised

  • In IGP to other routers in the site connected to this PE
  • In BGP to all other PEs

Best regards,
Peter

View solution in original post

3 Replies 3

Go to solution
Peter Paluch
Cisco Employee
Cisco Employee

‎01-04-2016 04:08 PM

Hi Bob,

When looking at your configuration, the RP address 172.18.100.1 that is being defined for the VRF mvpn1 does not seem to be correct. This IP address has to exist and be reachable within that particular VRF, and it is entirely independent of the 172.18.100.1 that exists in the global routing table. Incidentally, this IP address is your P router, the one that has no clue about VRFs and customers and their MVPNs, and conversely, this IP address does not seem to exist anywhere in the VPN as there is no interface assigned to VRF mvpn1 in your configs that would be carrying this IP address. Surely, PEs and CEs that - within the VPN created by VRF mvpn1 - have no visibility into your core network cannot use the P router as the RP.

You will need to designate one of the routers that has a visibility into this VPN to be an RP for this VPN. This precludes using any of the P routers for this purpose. The RP for this VPN must be either one of the PEs, or any of the CE/C routers. Of course, all routers within this VPN must know about it.

The easiest thing to do is to create a new loopback on some of the PEs, put it into VRF mvpn1, configure it with 172.18.100.1 and have this loopback advertised

  • In IGP to other routers in the site connected to this PE
  • In BGP to all other PEs

Best regards,
Peter

Go to solution
bob brennan
Level 1
Level 1
In response to Peter Paluch

‎01-05-2016 06:26 AM

hi peter,

you are correct, i missed that. i setup a loopback in vrf mvpn1 and set it as the rp and made sure the other devices in the vrf could see it and the multicast is now working. thanks again for all your help, its greatly appreciated.

0 Helpful

Go to solution
rpalmeida
Level 1
Level 1
In response to Peter Paluch

‎11-03-2024 01:59 AM

Hi,

With that info, you solve some issues i had.

Very gratefull.

Best regards.

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card