Multicast VPN with C-Anycast on PE supported?

Answered Question
Apr 12th, 2010
Are C-Anycast RPs  supported in a mVPN solution?

We are a  service-provider. We use cisco PEs (MPLS and native PIM-SM/SSM in the core ->  draft rosen)
The PEs (c7609,  SUp720, 12.0 SRD) must play the role of the C-RP (two different PEs for each  mVPN). We want to have
C-RP redundancy  with C-Anycast and MSDP running between those c-RPs.

I couldn't find a statement that C-Anycast with mVPN on PEs is supported or not.

thanks for the help
I have this problem too.
0 votes
Correct Answer by Laurent Aubert about 6 years 7 months ago

Hi Harald,

I tested it quickly and it's working. My PE's are running SRC3 and SRE:

AS1-PE2-6509#sh run | beg ip msdp

ip msdp vrf MVPN peer 172.16.3.254

ip msdp vrf MVPN cache-sa-state

ip msdp vrf MVPN originator-id FastEthernet3/2.700

ip pim vrf MVPN rp-address 1.1.1.1 override

AS1-PE2-6509#sh ip msdp vrf MVPN sa-cache

MSDP Source-Active Cache - 1 entries

(40.1.1.1, 224.1.1.1), RP 172.16.3.254, BGP/AS 1, 00:03:03/00:05:15, Peer 172.16.3.254

AS1-PE3#sh ip mroute vrf MVPN

...

(40.1.1.1, 224.1.1.1), 00:01:56/00:03:23, flags: TA

Incoming interface: Tunnel0, RPF nbr 10.1.1.4

Outgoing interface list:

Ethernet1/0.10, Forward/Sparse, 00:01:56/00:03:20

AS1-PE3#r | in ip msdp

ip msdp vrf MVPN peer 172.16.2.254

ip msdp vrf MVPN cache-sa-state

ip msdp vrf MVPN originator-id Ethernet1/0.10

ip pim vrf MVPN rp-address 1.1.1.1 override

HTH

Laurent.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
HARALD ZECH Fri, 04/16/2010 - 00:46

Yes, MSDP is VPN-aware and I tested it. It

didn't work. No information was exchanged although

connectivity was ok.

However, the problem is most likely more related to

the way MSDP is treated in a draft-rosen based core.

Correct Answer
Laurent Aubert Fri, 04/16/2010 - 06:31

Hi Harald,

I tested it quickly and it's working. My PE's are running SRC3 and SRE:

AS1-PE2-6509#sh run | beg ip msdp

ip msdp vrf MVPN peer 172.16.3.254

ip msdp vrf MVPN cache-sa-state

ip msdp vrf MVPN originator-id FastEthernet3/2.700

ip pim vrf MVPN rp-address 1.1.1.1 override

AS1-PE2-6509#sh ip msdp vrf MVPN sa-cache

MSDP Source-Active Cache - 1 entries

(40.1.1.1, 224.1.1.1), RP 172.16.3.254, BGP/AS 1, 00:03:03/00:05:15, Peer 172.16.3.254

AS1-PE3#sh ip mroute vrf MVPN

...

(40.1.1.1, 224.1.1.1), 00:01:56/00:03:23, flags: TA

Incoming interface: Tunnel0, RPF nbr 10.1.1.4

Outgoing interface list:

Ethernet1/0.10, Forward/Sparse, 00:01:56/00:03:20

AS1-PE3#r | in ip msdp

ip msdp vrf MVPN peer 172.16.2.254

ip msdp vrf MVPN cache-sa-state

ip msdp vrf MVPN originator-id Ethernet1/0.10

ip pim vrf MVPN rp-address 1.1.1.1 override

HTH

Laurent.

HARALD ZECH Wed, 04/21/2010 - 08:14

Hi Laurent

I found the problem. Our control-plane policing (COPP) was blocking MSDP

(and causing other Multicast issues). Your reply confirmed that MSDP is really working and so

I could focus to other possible causes.

Thanks for your help !

Harald

Actions

This Discussion