05-30-2016 12:53 AM
Hi! I'm having a problem with my mVPN Configuration. Also the Multicast doesn't seem to work intervlan. Hoping someone can help me with this one. Thanks!
RP/0/RSP0/CPU0:ASR9010-1#show mpls traffic-eng tunnels auto-tunnel p2mp
Mon May 30 15:17:21.104 PHT
Name: tunnel-mte2000 (auto-tunnel for MVPN (pim))
Signalled-Name: auto_ASR9010-1_mt2000
Status:
Admin: up Oper: down
Reason: No destination is configured
Config Parameters:
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Interface Bandwidth: 0 kbps
Metric Type: TE (default)
Fast Reroute: Not Enabled, Protection Desired: None
Record Route: Not Enabled
Reoptimization after affinity failure: Enabled
Destination summary: (0 up, 0 down, 0 disabled) Affinity: 0x0/0xffff
Auto-bw: disabled
Current LSP:
None
Reoptimized LSP (Install Timer Remaining 0 Seconds):
None
Cleaned LSP (Cleanup Timer Remaining 0 Seconds):
None
Displayed 1 (of 16) heads, 0 (of 50) midpoints, 0 (of 14) tails
Displayed 0 up, 1 down, 0 recovering, 0 recovered heads
Below is the configuration:
ipv4 access-list SSM
10 permit ipv4 232.0.0.0/8 any
20 permit ipv4 239.0.0.0/8 any
30 permit ipv4 235.0.0.0/8 any
!
!
vrf MulticastIPTV
vpn id 65001:1111
address-family ipv4 unicast
import route-target
65001:1111
!
export route-target
65001:1111
!
router bgp 65001
! other configs are omitted
address-family ipv4 mvpn
neighbor-group ibgp-session-RR
! other configs are omitted
address-family ipv4 mvpn
neighbor-group ibgp-session-RR-client
remote-as 65001
! other configs are omitted
address-family ipv4 mvpn
route-reflector-client
next-hop-self
vrf MulticastIPTV
rd auto
address-family ipv4 unicast
redistribute connected
redistribute static
!
address-family ipv4 mvpn
!
interface Bundle-Ether3.802
description ***IPTV_MAY2016TEST SOURCE***
vrf MulticastIPTV
ipv4 address 10.20.1.2 255.255.255.0
load-interval 30
encapsulation dot1q 802
!
interface Bundle-Ether3.803
description ***IPTV_MAY2016TEST DESTINATION ***
vrf MulticastIPTV
ipv4 address 192.168.2.1 255.255.255.0
load-interval 30
encapsulation dot1q 803
interface Loopback300
vrf MulticastIPTV
ipv4 address 100.100.102.1 255.255.255.255
route-policy rpf-for-one
set core-tree p2mp-te-partitioned
end-policy
mpls traffic-eng
! interfaces for MPLS are configured but omitted on this page
auto-tunnel p2mp
tunnel-id min 2000 max 2999
!
ipv4 unnumbered mpls traffic-eng Loopback0
multicast-routing
address-family ipv4
mdt source Loopback0
interface all enable
!
vrf MulticastIPTV
address-family ipv4
mdt source Loopback300
ssm range SSM
rate-per-route
interface all enable
accounting per-prefix
bgp auto-discovery p2mp-te
!
mdt partitioned p2mp-te
mdt data p2mp-te 100
!
router pim
address-family ipv4
interface Loopback0
enable
!
!
vrf MulticastIPTV
address-family ipv4
rpf topology route-policy rpf-for-one
mdt c-multicast-routing bgp
!
interface Loopback300
enable
!
interface Bundle-Ether3.802
enable
!
interface Bundle-Ether3.803
enable
Config to other MPLS Routers is similar to the above mentioned configuration
06-12-2016 02:34 PM
Was this working before or is this the first time you have configured it. Also, could you please let me know what is the software version you are running?
I will look into this issue.
Regards
Vinit
06-29-2016 12:24 AM
Hi Vinit,
We're using 5.2.2.
It's now working when I've changed the SSM access-list from 235.x.x.x/8 to 235.1.x.x/24. But the tunnel goes up only with this 1 particular IP 235.1.0.6, when other 235.1.0.X IP is requesting a join, no tunnel is being formed.
What config could possibly correct this?
Since the Source has 1 unicast with multiple multicast IP.
RP/0/RSP0/CPU0:ASR9010-1#sh mpls traffic-eng tunnels p2mp tabular
Wed Jun 29 14:50:00.483 PHT
Tunnel LSP Destination Source FRR LSP Path
Name ID Address Address State State Role Prot
----------------- ----- --------------- --------------- ------ ------ ---- -----
^tunnel-mte2000 0 Unknown 0.0.0.0 down Inact Head
^tunnel-mte2044 10002 172.31.128.103 172.31.128.1 up Inact Head
RP/0/RSP0/CPU0:MESJN-ASR9010-1#sh pim vrf IPTV_Bronze topology
Wed Jun 29 14:51:00.749 PHT
IP PIM Multicast Topology Table
Entry state: (*/S,G)[RPT/SPT] Protocol Uptime Info
Entry flags: KAT - Keep Alive Timer, AA - Assume Alive, PA - Probe Alive
RA - Really Alive, IA - Inherit Alive, LH - Last Hop
DSS - Don't Signal Sources, RR - Register Received
SR - Sending Registers, SNR - Sending Null Registers
E - MSDP External, EX - Extranet
MFA - Mofrr Active, MFP - Mofrr Primary, MFB - Mofrr Backup
DCC - Don't Check Connected, ME - MDT Encap, MD - MDT Decap
MT - Crossed Data MDT threshold, MA - Data MDT Assigned
SAJ - BGP Source Active Joined, SAR - BGP Source Active Received,
SAS - BGP Source Active Sent, IM - Inband mLDP, X - VxLAN
Interface state: Name, Uptime, Fwd, Info
Interface flags: LI - Local Interest, LD - Local Dissinterest,
II - Internal Interest, ID - Internal Dissinterest,
LH - Last Hop, AS - Assert, AB - Admin Boundary, EX - Extranet,
BGP - BGP C-Multicast Join, BP - BGP Source Active Prune,
MVS - MVPN Safi Learned, MV6S - MVPN IPv6 Safi Learned
(*,224.0.1.40) DM Up: 5d00h RP: 0.0.0.0
JP: Null(never) RPF: Null,0.0.0.0 Flags: LH DSS
Bundle-Ether3.802 5d00h off LI II LH
(10.20.1.253,235.1.0.6)SPT SSM Up: 04:03:32
JP: Join(never) RPF: Bundle-Ether3.802,10.20.1.253* Flags: MT MA
TmdtIPTV/Bronze 04:03:32 fwd BGP
Thanks!
06-30-2016 08:05 PM
Hi Viniit,
Yes, some multicast IP like 235.1.0.8 has been up before. But the source is the on the other end And this router was the receiver then.
Is there a way to tear down the auto-tunnel that was created?
Thanks!
Regards,
mazzy
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide