Routing

Expand all | Collapse all

Unable to establish default Rosen6 MDT

  • 1.  Unable to establish default Rosen6 MDT

     
    Posted 15 days ago

    Hi.

     

    I have a Rosen6 topology and am unable to establish the default MDT.

     

    My service provider RP is 4.4.4.4.

     

    My understanding is that every PE must establish a shared tree towards the RP for the configured vpn group address 239.1.1.1. However, there is no PIM state established within the service provider.

     

    Below is the configuration of PE1. Kindly point out what I've done wrong.

     

    [edit]

    jcluser@PE1# show routing-instances | display set

    set routing-instances VPN-A protocols pim mvpn

    set routing-instances VPN-A protocols pim rp static address 5.5.5.5

    set routing-instances VPN-A protocols pim interface all mode sparse

    set routing-instances VPN-A protocols bgp group ebgp type external

    set routing-instances VPN-A protocols bgp group ebgp as-override

    set routing-instances VPN-A protocols bgp group ebgp neighbor 192.168.10.1 peer-as 200

    set routing-instances VPN-A instance-type vrf

    set routing-instances VPN-A provider-tunnel pim-asm group-address 239.1.1.1

    set routing-instances VPN-A interface ge-0/0/3.0

    set routing-instances VPN-A route-distinguisher 1.1.1.1:1

    set routing-instances VPN-A vrf-target target:100:1

     

     

     

    [edit]

    jcluser@PE1# show protocols | display set

    set protocols ospf area 0.0.0.0 interface all interface-type p2p

    set protocols pim rp static address 4.4.4.4

    set protocols pim interface all mode sparse

    set protocols bgp group ibgp type internal

    set protocols bgp group ibgp local-address 1.1.1.1

    set protocols bgp group ibgp family inet-vpn unicast

    set protocols bgp group ibgp neighbor 2.2.2.2

    set protocols bgp group ibgp neighbor 3.3.3.3

    set protocols ldp interface all

    set protocols mpls interface all

     

     

     

    [edit]

    jcluser@PE1# run show pim rps

    Instance: PIM.master

     

    address-family INET

    RP address      Type        Mode   Holdtime Timeout Groups Group prefixes

    4.4.4.4         static      sparse        0    None      0 224.0.0.0/4

     

     

     

    [edit]

    jcluser@PE1# run show pim neighbors

    B = Bidirectional Capable, G = Generation Identifier

    H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,

    P = Hello Option DR Priority, T = Tracking Bit,

    A = Hello Option Join Attribute

     

    Instance: PIM.master

    Interface           IP V Mode        Option       Uptime Neighbor addr

    ge-0/0/1.0           4 2             HPLGTA      00:30:51 10.10.10.2 

     

     

     

    Regards,

    Deepak


    Juniper Business Use Only



  • 2.  RE: Unable to establish default Rosen6 MDT

    Posted 6 days ago
    I am unfamiliar with the 'Rosen6' terminology here, but it seems that this represents a pim-core-tree? Just 'Draft-Rosen' or RFC 6037, if that is the case, then I think you are missing configurations here. Based on the configuration guide, there's more that is required, please follow https://www.juniper.net/documentation/us/en/software/junos/multicast/topics/topic-map/mcast-mvpns-draft-rosen-6.html.

    Also, at ingress PE/LSR, configura tunnel-services so that this router is able to encapsulate PIM packets towards the RP.

    Elvin