Routing
Highlighted
Routing

Multicast - first hop router not encapsulating packets

‎07-02-2015 01:58 PM

I have been try to do some maulticast labs and test the. The pim v2 neighbours are as expected and a static IGMP configuration has been made on the last hop router. The RP (SRX210) is aware of the join request.

 

lab@RTR_B> show pim join extensive    
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

Group: 239.255.255.2
    Source: *
    RP: 172.30.15.2
    Flags: sparse,rptree,wildcard
    Upstream interface: Local                 
    Upstream neighbor: Local
    Upstream state: Local RP
    Uptime: 00:32:00
    Downstream neighbors:
        Interface: fe-0/0/3.0             
            172.30.0.14 State: Join Flags: SRW Timeout: 209
            Uptime: 00:32:00 Time since last Join: 00:00:00

 

I have used a SRX240 as the mcst source and started a ping:

 

lab@RTR_D> ping 239.255.255.2 bypass-routing interface ge-0/0/1.40   

 

However the first hop router (SRX210) does nothing.

 

lab@RTR_A> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

 

And the source is still unknown by the RP and downstream routers.

 

Any ideas?

JNCIE-ENT #552, JNCSP-ENT, JNCIP-SEC, JNCIP-SP, JNCIP-DC, JNCDS-DC, JNCDS-SEC, JNCDS-SP, CCNP, CCDA
2 REPLIES 2
Highlighted
Routing

Re: Multicast - first hop router not encapsulating packets

‎07-02-2015 10:26 PM

Could you please post your (relevent) configuration and topology?

_
Regards
Malik
JNCIEx4, CCIE, HCIE, VCIX-DCV, VCIX-NV, CISSP, PMP

[If it helped to solve your problem, please mark it "Accept as solution"; Kudos are always Appreciated]
Highlighted
Routing

Re: Multicast - first hop router not encapsulating packets

‎07-03-2015 04:54 PM

I now seem to have this working:

 

lab@RTR_A> show pim join     
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

Group: 239.255.255.2
    Source: 192.168.40.100
    Flags: sparse,spt
    Upstream interface: fe-0/0/4.40           

Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

 

I was using inet.2 but had failed to apply the appropriate rib-group to the interface-routes.

 

Thanks for the interest.

 

 

 

JNCIE-ENT #552, JNCSP-ENT, JNCIP-SEC, JNCIP-SP, JNCIP-DC, JNCDS-DC, JNCDS-SEC, JNCDS-SP, CCNP, CCDA
Feedback