[j-nsp] NG-MVPN flow prob

Ahsan Khan ahsan.khan.sn at gmail.com
Tue Feb 14 00:35:47 EST 2012


Hello Stacy/Humair,

Yes i've configure SSM ranges on both PEs.

Output for "show mvpn c-multicast extensive" :

admin at PE1> show mvpn c-multicast instance-name test extensive
MVPN instance:

Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel

Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)          RM -- remote VPN route
Instance: test
  C-mcast IPv4 (S:G)            Ptnl                           St
  192.168.1.2/32:239.1.1.2/32   RSVP-TE P2MP:3.3.3.3, 11078,3.3.3.3
RM


Configs are attached.


BR/Ahsan


On Tue, Feb 14, 2012 at 1:01 AM, Humair Ali <humair.s.ali at gmail.com> wrote:

> Not sure about J-series, only dealt with MX for MVPN,
>
> on PE1 (J-series), what state do you see in  "show mvpn c-multicast
> extensive"  ?
>
> can you post your output here ?
>
> Thanks
>
>
> On 13 February 2012 14:40, Stacy W. Smith <stacy at acm.org> wrote:
>
>> I think we will need to see the configs.
>>
>> Have you configured non-default PIM SSM ranges? If not, which router(s)
>> are acting as the RP(s)?
>>
>> --Stacy
>>
>>
>> On Feb 13, 2012, at 4:54 AM, Ahsan Khan wrote:
>>
>> > Hi,
>> >
>> > I am working on NG-MVPN, my topology is as under:
>> >
>> >
>> >
>> > – CE1 – PE1 – P – PE2 – CE2 –
>> >
>> >                  |_______|
>> >
>> >                       |
>> >
>> >         Routing instance “test”
>> >
>> >
>> >
>> > CE1: Cisco 3845                           (Source IP: 192.168.1.2)
>> >
>> > PE1: J6350 (JUNOS 8.5R3.4)         Lo0: 3.3.3.3
>> >
>> > P: M7i (JUNOS 8.5R3.4)                Lo0: 1.1.1.1
>> >
>> > PE2: M7i (JUNOS 8.5R3.4)            Lo0: 2.2.2.2
>> >
>> > CE2: Cisco 2800                           (Source IP: 192.168.2.2)
>> >
>> >
>> >
>> > I am using p2mp rsvp based tunnel (default template). Everything is
>> working
>> > fine when a source attached with CE2 (connected with Juniper M7i) starts
>> > sending multicast traffic, receiver at CE1 (Connected with J6350) end
>> > receives it perfectly.
>> >
>> > Problem occurs when CE1 (Connected with J6350) source starts sending
>> > multicast traffic but CE2 (Connected with M7i) receiver doesnot receive
>> it
>> >
>> > Type 1 and 7 routes are present in route table test.mvpn but traffic is
>> > unable to flow from PE1-PE2.
>> >
>> >
>> >
>> > Anyone else faces this issue before or am I missing something here?
>> (“Show
>> > route table test.mvpn” is attached )
>> >
>> > I can share configurations if it helps. Any assist will be appreciated.
>> >
>> >
>> >
>> > BR/Ahsan
>> > <route table test
>> mvpn.txt>_______________________________________________
>> > juniper-nsp mailing list juniper-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
>
> --
> Humair
>
>
-------------- next part --------------
admin at PE1> show configuration routing-instances test 
instance-type vrf;
interface ge-0/0/1.0;
route-distinguisher 9541:100;
provider-tunnel {
    rsvp-te {
        label-switched-path-template {
            default-template;
        }
    }
}
vrf-target target:9541:100;
vrf-table-label;
routing-options {
    multicast {
        ssm-groups [ 239.1.1.1/32 239.1.1.2/32 ];
    }
}
protocols {
    bgp {
        group test {
            description "***Connection with CE1***";
            authentication-key "$9$LKzN-wGDkmPQUD9pORle4aJZHm"; ## SECRET-DATA
            peer-as 65100;
            local-as 9541;
            neighbor 10.1.1.1;
        }
    }
    pim {
        interface all {
            mode sparse-dense;
        }
    }
    mvpn;
}

admin at PE1> 


admin at PE1> show configuration protocols bgp 
group internal {
    local-address 3.3.3.3;
    family inet {
        unicast;
    }
    family inet-vpn {
        unicast;
    }
    family inet-mvpn {
        signaling;
    }
    authentication-key "$9$.5T30BESyKOBxdwgUDCtpuRS"; ## SECRET-DATA
    peer-as 9541;
    local-as 9541;
    neighbor 1.1.1.1;
    neighbor 2.2.2.2 {
        multihop {
            ttl 2;
        }
    }
    neighbor 4.4.4.4 {
        multihop {
            ttl 2;
        }           
    }
}

-------------- next part --------------
admin at PE2> show configuration routing-instances test 
instance-type vrf;
interface fe-1/3/0.0;
route-distinguisher 9541:100;
inactive: provider-tunnel {
    rsvp-te {
        label-switched-path-template {
            default-template;
        }
    }
}
vrf-target target:9541:100;
vrf-table-label;
routing-options {
    multicast {
        ssm-groups [ 239.1.1.1/32 239.1.1.2/32 ];
    }
}
protocols {
    bgp {
        group test {
            description "***Connection with CE2***";
            authentication-key "$9$ntNiCA0ylMLX-rl2aGif5RhcSvL"; ## SECRET-DATA
            peer-as 65300;
            local-as 9541;
            neighbor 10.1.4.2;
        }
    }
    pim {
        interface all {
            mode sparse-dense;
        }
    }
    mvpn;
}


admin at PE2> show route table test.inet.1 

test.inet.1: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

239.1.1.2,192.168.1.2/32*[MVPN/70] 00:05:24
                      Multicast (IPv4)

admin at PE2> 


More information about the juniper-nsp mailing list