[j-nsp] data mdt is not created

Mihai Gabriel mihaigabriel at gmail.com
Mon Aug 19 05:26:51 EDT 2013


Hello,

 I use a simple topology to setup a Rosen 7 multicast vpn  like this:

S1 -> R1 (PE) -> R3(P)  -> R5(PE)->Rec

The multicast traffic always stay on the default MDT even though the data
MDT is configured.
Am I doing something wrong?

r1# top show protocols bgp
group mvpn {
    type internal;
    local-address 172.27.255.1;
    family inet-vpn {
        unicast;
    }
    family inet-mdt {
        signaling;
    }
    neighbor 172.27.255.5;
}

r1# top show routing-instances mvpn
instance-type vrf;
interface ge-1/1/5.360;
interface lo0.10;
route-distinguisher 1:1;
provider-tunnel {
    pim-ssm {
        group-address 232.2.2.2;
    }
    mdt {
        threshold {
            group 224.2.2.2/32 {
                source 0.0.0.0/0 {
                    rate 10;
                }
            }
        }
        group-range 225.2.2.0/24;
    }
}
vrf-target target:1:1;
vrf-table-label;
protocols {
    pim {
        vpn-tunnel-source 172.27.255.1;
        mvpn {
            autodiscovery {
                inet-mdt;
            }
        }
        rp {
            local {
                address 172.27.255.1;
            }
        }
        interface all;
    }
    mvpn {
        autodiscovery-only {
            intra-as {
                inclusive;
            }
        }
    }
}


r1# run show multicast route extensive instance mvpn
Instance: mvpn Family: INET

Group: 224.2.2.2
    Source: 172.27.0.30/32
    Upstream interface: ge-1/1/5.360
    Downstream interface list:
        mt-1/1/10.100696064
    Session description: Multimedia Conference Calls
    Statistics: 122 kBps, 80 pps, 1434 packets
    Next-hop ID: 1048588
    Upstream protocol: PIM
    Route state: Active
    Forwarding state: Forwarding
    Cache lifetime/timeout: 360 seconds
    Wrong incoming interface notifications: 0
    Uptime: 00:00:18

r1# run show pim mdt instance mvpn
Instance: PIM.mvpn
Tunnel direction: Outgoing
Tunnel mode: PIM-SSM
Default group address: 232.2.2.2
Default source address: 172.27.255.1
Default tunnel interface: mt-1/1/10.100696064
Default tunnel source: 172.27.255.1

Instance: PIM.mvpn
Tunnel direction: Incoming
Tunnel mode: PIM-SSM
Default group address: 232.2.2.2
Default source address: 172.27.255.5
Default tunnel interface: mt-1/1/10.101744640
Default tunnel source: 172.27.255.1

r3# run show multicast route extensive
Instance: master Family: INET

Group: 232.2.2.2
    Source: 172.27.255.1/32
    Upstream interface: ge-1/1/7.31
    Downstream interface list:
        ge-1/1/7.35
    Session description: Source specific multicast
    Statistics: 128 kBps, 82 pps, 6199 packets
    Next-hop ID: 1048580
    Upstream protocol: PIM
    Route state: Active
    Forwarding state: Forwarding
    Cache lifetime/timeout: forever
    Wrong incoming interface notifications: 0
    Uptime: 00:01:25

Group: 232.2.2.2
    Source: 172.27.255.5/32
    Upstream interface: ge-1/1/7.35
    Downstream interface list:
        ge-1/1/7.31
    Session description: Source specific multicast
    Statistics: 0 kBps, 0 pps, 11 packets
    Next-hop ID: 1048585
    Upstream protocol: PIM
    Route state: Active
    Forwarding state: Forwarding
    Cache lifetime/timeout: forever
    Wrong incoming interface notifications: 0
    Uptime: 00:01:24


More information about the juniper-nsp mailing list