cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1691
Views
10
Helpful
6
Replies

Does ASR9000 support NG-MVPN Profile 10 ??

Jacobo Schneider
Beginner
Beginner

Hi,

I'm wondering if Profile 10 (p2mp-te with static mapping in VRF) is supported in ASR9000 XR

 

I configured according to this link

http://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/multiprotocol-label-switching-vpns-mpls-vpns/118983-configure-mpls-00.html#anc28

However it seems that something is broken

Also I notice that in the configuration guide for XR 5.3.x says that only the first 9 profiles are supported, can anyone clarify.

Thanks

Jacobo

6 Replies 6

Giuseppe Larosa
Hall of Fame Master Hall of Fame Master
Hall of Fame Master

Hello Jacobo,

Cisco implementation of NG MVPN uses mLDP not RSVP-TE based p2mp LSPs. So the answer to your question is that your configuration is not supported.

I have heard news of mLDP with NG MVPN on Vodafone Italy from a linkedin peer.

Also there was an aske the expert session two years ago where the host clearly stated that Cisco implementation supports only mLDP not RSVP TE p2mp.

This is the opposite of what does Juniper that supports RSVP TE p2mp LSPs on M and MX series.

Hope to help

Giuseppe

Hi Giuseppe, thanks for your answer,

I managed to get the configuration to work just yesterday, actually by mistake I didn't enable PIM on the loopback which was the root cause of the problem.

Now, aside from my lab is now working, it seems to me that it should be supported, I mean, the commands are there to support p2mp-te signaled by rsvp-te as the core tree, there is also a configuration guide for XR for it and also I found a couple of Cisco Live presentations that stats that this profile is supported in XR... hopefully somebody from the Cisco Business Unit will read this post and clarify if it is officially supported.

Best Regards,

Jacobo

Hello Jacobo,

I agree that in two years support for p2mp RSVP TE LSPs with NG MVPN can have been added.

I have to apologize for my previous answer.

If this is supported it opens scenarios of interoperability between Cisco and Juniper devices in the NG MVPN feature.

Hope to help

Giuseppe

ps. I have rated 5 your answer because it is something I have been waiting for years

Hi Jacobo - I am sorry, this post is almost 2 years back. But I am trying to make it on VIRL as of today, but I can't manage to do actual ping test over SSM group from a certain source from CE side. 

 

But just to check, if you can share your PE head end and tail end config here. I tried already this config template from cisco config guide created by @Luc De Ghein  but not sure what I miss.

 

Config guide from Cisco: https://www.cisco.com/c/en/us/support/docs/multiprotocol-label-switching-mpls/multiprotocol-label-switching-vpns-mpls-vpns/118983-configure-mpls-00.html#anc28

 

Here is my Config Below:

 

Head End:
+------------------------------------------------------------------------+
router igmp
vrf ONE
 interface tunnel-mte1
   static-group 232.1.1.1 192.168.1.1 ==> Actual C-(S,G)
  !
 !
!

multicast-routing
 address-family ipv4
  interface Loopback0
   enable
 !
!
 vrf ONE
  address-family ipv4
   mdt source Loopback0
   rate-per-route
   interface all enable
   accounting per-prefix
   bgp auto-discovery p2mp-te
   !
   mdt static p2mp-te tunnel-mte1
  !
 !
!
router pim
 vrf ONE
  address-family ipv4
   mdt c-multicast-routing pim
  !
  interface tunnel-mte1
   enable
   !
  interface GigabitEthernet0/0/0/2 ==> Interface facing CE
   enable
  !
  !
 !
!

interface tunnel-mte1
 ipv4 unnumbered Loopback0
 destination 1.1.1.1 ===>Tail End PE1
   path-option 1 dynamic
 !
 destination 2.2.2.2 ===>Tail End PE2
  path-option 1 dynamic
 !
 destination 3.3.3.3 ===>Tail End PE3
  path-option 1 dynamic
 !
!

 

Tail End:
+------------------------------------------------------------------------+
router pim
 vrf ONE 
  address-family ipv4
    mdt c-multicast-routing pim
  !
  interface GigabitEthernet0/0/0/2 ==> Interface facing CE
   enable
  !
 !
!
!

multicast-routing
 address-family ipv4
  interface Loopback0
   enable
 !
!
  vrf ONE
  address-family ipv4
    mdt source Loopback0
  core-tree-protocol rsvp-te
  rate-per-route
  interface all enable
  accounting per-prefix
    bgp auto-discovery p2mp-te
 !
!
!
!

 

mVPN solutions using P2MP TE as core tree protocol do not work and are not supported on virtual XR routers (XRv and XRv9k) currently.

 

 

Regards,

 

Luc

Thank you so much, Luc.  Got some feedback also that Profile 10 dataplane don't work in XRv.

 

Can you also confirm the Ingress Replication as Core Tree dataplane will not work in XRv/XRv9k?   Since base on my lab test, it fails to send traffic from Sender to Reciever too and also RP distribution fail using BSR. :(

 

Below is just a note, maybe you have time to check it and have some comment. Thank you very much in advance.

 

Note: Now I understand, earlier I was confused about Core tree for Profile 20/22 & 24/26 since it is also P2MP-TE but the core tree is just P2MP( as indicated in one of the cisco live mVPN profile chart. Base on my test over VIRL, Profile 20/22 okay for both C-mcast traffic ASM/SSM but Profile 24/26 only work for C-mcast traffic SSM, I manage to test it successfully. Below is my test logs from Sender, Ingress and Egress PE and also one Core P router using profile 20.

 

Ping Test From Source:

 

RP/0/0/CPU0:SENDER#ping 239.9.9.9 re 70
Tue Nov 28 06:47:10.134 UTC
Type escape sequence to abort.
Sending 70, 100-byte ICMP Echos to 239.9.9.9, timeout is 2 seconds:

Reply to request 0 from 192.168.1.1, 9 ms ==> Reciever at PE1 VRF ONE
Reply to request 0 from 192.168.103.1, 9 ms
Reply to request 0 from 192.168.1.1, 9 ms
Reply to request 0 from 192.168.103.1, 9 ms
Reply to request 0 from 192.168.2.1, 9 ms
Reply to request 0 from 192.168.2.1, 9 ms
Reply to request 1 from 192.168.103.1, 19 ms
Reply to request 1 from 192.168.1.1, 19 ms
Reply to request 1 from 192.168.103.1, 19 ms
Reply to request 1 from 192.168.1.1, 19 ms
Reply to request 1 from 192.168.2.1, 19 ms
Reply to request 1 from 192.168.2.1, 19 ms
RP/0/0/CPU0:SENDER#

 

Overlay PIM neighbor for C-mcast at Ingress PE:

 

RP/0/0/CPU0:PE5#sh pim vrf ONE neighbor
Tue Nov 28 07:01:14.525 UTC

PIM neighbors in VRF ONE
Flag: B - Bidir capable, P - Proxy capable, DR - Designated Router,
E - ECMP Redirect capable
* indicates the neighbor created for this router

Neighbor Address Interface Uptime Expires DR pri Flags

192.168.104.1 GigabitEthernet0/0/0/3 5d19h 00:01:22 1 B
192.168.104.2* GigabitEthernet0/0/0/3 5d19h 00:01:38 1 (DR) B E
11.11.11.11 TmdtONE 00:24:36 00:01:19 1 ===> PE1(One of Egress-Reciever Connected)
12.12.12.12 TmdtONE 00:24:35 00:01:30 1
14.14.14.14 TmdtONE 00:24:40 00:01:25 1
15.15.15.15* TmdtONE 00:24:42 00:01:17 1 (DR)
RP/0/0/CPU0:PE5#
RP/0/0/CPU0:PE5#sh mfib vrf ONE route
Tue Nov 28 07:01:14.435 UTC
<output filtered>
(192.168.4.1,239.9.9.9), Flags:
Up: 00:22:24
Last Used: 00:02:42
SW Forwarding Counts: 153/0/0
SW Replication Counts: 153/0/0
SW Failure Counts: 0/0/0/0/0
TmdtEXAM Flags: F NS TMI, Up:00:22:24
GigabitEthernet0/0/0/3 Flags: A, Up:00:22:24
RP/0/0/CPU0:PE5#

 

Overlay PIM neighbor for C-mcast at Egress PE:

 

RP/0/0/CPU0:PE1#sh pim vrf ONE neighbor
Tue Nov 28 07:00:27.766 UTC

PIM neighbors in VRF ONE
Flag: B - Bidir capable, P - Proxy capable, DR - Designated Router,
E - ECMP Redirect capable
* indicates the neighbor created for this router

Neighbor Address Interface Uptime Expires DR pri Flags

192.168.101.1 GigabitEthernet0/0/0/3 5d19h 00:01:39 1 B
192.168.101.2* GigabitEthernet0/0/0/3 5d19h 00:01:36 1 (DR) B E
11.11.11.11* TmdtONE 00:24:27 00:01:35 1
12.12.12.12 TmdtONE 00:24:09 00:01:16 1
14.14.14.14 TmdtONE 00:23:59 00:01:42 1 ==> PE5(Ingress PE-Source Connected)
15.15.15.15 TmdtONE 00:23:52 00:01:33 1 (DR)
RP/0/0/CPU0:PE1#


Reciever Join the C-(*,G) with MFIB stats:

 

RP/0/0/CPU0:RECIEVER1#sh run router igmp
router igmp
interface Loopback0
join-group 239.9.9.9
!
!
RP/0/0/CPU0:RECIEVER1#
RP/0/0/CPU0:RECIEVER1#sh mfib route
<output filtered>
(192.168.4.1,239.9.9.9), Flags:
Up: 00:08:00
Last Used: 00:05:40
SW Forwarding Counts: 137/135/13500
SW Replication Counts: 137/0/0
SW Failure Counts: 0/0/0/0/0
Loopback0 Flags: IC NS EG, Up:00:08:00
GigabitEthernet0/0/0/0 Flags: A NS, Up:00:08:00
RP/0/0/CPU0:RECIEVER1#

 


TE Information at Head End:

 

RP/0/0/CPU0:PE5#sh mpls traffic-eng tunnel
Tue Nov 28 07:01:14.795 UTC


Name: tunnel-mte1000 (auto-tunnel for MVPN (pim))
Signalled-Name: auto_PE5_mt1000
Status:
Admin: up Oper: up (Up for 00:24:42)

Config Parameters:
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Interface Bandwidth: 0 kbps
Metric Type: TE (global)
Fast Reroute: Not Enabled, Protection Desired: None
Record Route: Not Enabled
Reoptimization after affinity failure: Enabled

Destination summary: (3 up, 0 down, 0 disabled) Affinity: 0x0/0xffff
Auto-bw: disabled
Destination: 11.11.11.11
State: Up for 00:24:42
Path options:
path-option 10 dynamic [active]
Destination: 12.12.12.12
State: Up for 00:24:42
Path options:
path-option 10 dynamic [active]
Destination: 14.14.14.14
State: Up for 00:24:42
Path options:
path-option 10 dynamic [active]

Current LSP:
lsp-id: 10002 p2mp-id: 1000 tun-id: 1000 src: 15.15.15.15 extid: 15.15.15.15
LSP up for: 00:24:42 (since Tue Nov 28 06:36:32 UTC 2017)
Reroute Pending: No
Inuse Bandwidth: 0 kbps (CT0)
Number of S2Ls: 3 connected, 0 signaling proceeding, 0 down

S2L Sub LSP: Destination 11.11.11.11 Signaling Status: connected
S2L up for: 00:24:42 (since Tue Nov 28 06:36:32 UTC 2017)
Sub Group ID: 1 Sub Group Originator ID: 15.15.15.15
Path option path-option 10 dynamic (path weight 20)
Path info (IS-IS 1 level-2)
10.13.15.13
10.11.13.11
11.11.11.11

S2L Sub LSP: Destination 12.12.12.12 Signaling Status: connected
S2L up for: 00:24:42 (since Tue Nov 28 06:36:32 UTC 2017)
Sub Group ID: 2 Sub Group Originator ID: 15.15.15.15
Path option path-option 10 dynamic (path weight 20)
Path info (IS-IS 1 level-2)
10.13.15.13
10.12.13.12
12.12.12.12

S2L Sub LSP: Destination 14.14.14.14 Signaling Status: connected
S2L up for: 00:24:42 (since Tue Nov 28 06:36:32 UTC 2017)
Sub Group ID: 3 Sub Group Originator ID: 15.15.15.15
Path option path-option 10 dynamic (path weight 20)
Path info (IS-IS 1 level-2)
10.13.15.13
10.13.14.14
14.14.14.14

Reoptimized LSP (Install Timer Remaining 0 Seconds):
None
Cleaned LSP (Cleanup Timer Remaining 0 Seconds):
None

LSP Tunnel 11.11.11.11 1000 [10002] is signalled, Signaling State: up
Tunnel Name: auto_PE1_mt1000 Tunnel Role: Tail
InLabel: GigabitEthernet0/0/0/2, 24009
Signalling Info:
Src 11.11.11.11 Dst 15.15.15.15, Tun ID 1000, Tun Inst 10002, Ext ID 11.11.11.11
Router-IDs: upstream 13.13.13.13
local 15.15.15.15
Bandwidth: 0 kbps (CT0) Priority: 7 7 DSTE-class: 0
Soft Preemption: None
SRLGs: not collected
Path Info:
Incoming Address: 10.13.15.15
Incoming:
Explicit Route:
Strict, 10.13.15.15
Strict, 15.15.15.15

Record Route: Disabled
Tspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
Session Attributes: Local Prot: Not Set, Node Prot: Not Set, BW Prot: Not Set
Soft Preemption Desired: Not Set
Resv Info: None
Record Route: Disabled
Fspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
<Output filtered>
RP/0/0/CPU0:PE5#

 

TE Information at Head End:

 

RP/0/0/CPU0:PE1#sh mpls traffic-eng tunnel
<Output filtered>
LSP Tunnel 15.15.15.15 1000 [10002] is signalled, Signaling State: up
Tunnel Name: auto_PE5_mt1000 Tunnel Role: Tail
InLabel: GigabitEthernet0/0/0/2, 24009
Signalling Info:
Src 15.15.15.15 Dst 11.11.11.11, Tun ID 1000, Tun Inst 10002, Ext ID 15.15.15.15
Router-IDs: upstream 13.13.13.13
local 11.11.11.11
Bandwidth: 0 kbps (CT0) Priority: 7 7 DSTE-class: 0
Soft Preemption: None
SRLGs: not collected
Path Info:
Incoming Address: 10.11.13.11
Incoming:
Explicit Route:
Strict, 10.11.13.11
Strict, 11.11.11.11

Record Route: Disabled
Tspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
Session Attributes: Local Prot: Not Set, Node Prot: Not Set, BW Prot: Not Set
Soft Preemption Desired: Not Set
Resv Info: None
Record Route: Disabled
Fspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
Displayed 1 (of 1) heads, 0 (of 0) midpoints, 3 (of 3) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
RP/0/0/CPU0:PE1#


Core P MPLS FIB:

 

RP/0/0/CPU0:P#sh mpls forwarding
Tue Nov 28 06:55:28.207 UTC
Local Outgoing Prefix Outgoing Next Hop Bytes
Label Label or ID Interface Switched
------ ----------- ------------------ ------------ --------------- ------------
<output filtered>
24004 24006 P2MP TE: 1000 Gi0/0/0/0 10.11.13.11 0
24007 P2MP TE: 1000 Gi0/0/0/3 10.13.14.14 0
24007 P2MP TE: 1000 Gi0/0/0/2 10.13.15.15 0
24005 24007 P2MP TE: 1000 Gi0/0/0/1 10.12.13.12 0
24008 P2MP TE: 1000 Gi0/0/0/3 10.13.14.14 0
24009 P2MP TE: 1000 Gi0/0/0/2 10.13.15.15 0
24006 24008 P2MP TE: 1000 Gi0/0/0/0 10.11.13.11 0
24008 P2MP TE: 1000 Gi0/0/0/1 10.12.13.12 0
24008 P2MP TE: 1000 Gi0/0/0/2 10.13.15.15 0
24007 24009 P2MP TE: 1000 Gi0/0/0/0 10.11.13.11 0 ===> From Sender at PE5 to All other tail/Recievers
24009 P2MP TE: 1000 Gi0/0/0/1 10.12.13.12 0
24009 P2MP TE: 1000 Gi0/0/0/3 10.13.14.14 0
RP/0/0/CPU0:P#

 

 

 

 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: