Routing
Highlighted
Routing

Multicast Testing

[ Edited ]
‎02-13-2017 04:52 PM

Hello again,

Thanks in advance for your help with this basic lab issue.

I am having a lot of trouble doing simple testing for Multicast in a Juniper lab.   My lab works fine with Cisco CE's, but the Juniper CE's don't respond to pings.

 

I am always able to test my CISCO devices with this command on a loopback:

      ip igmp join-group x.x.x.x

 

With this simple CISCO command, I can even ping the group locally, and with an RP, I can ping all receivers.  NO problem with Cisco as my CE devices.   But...

 

 

...I cannot get it to work in JUNIPER.  The documentation says to use this command:

      set protocol igmp interface X/Y static group x.x.x.x

 

 

Creating the IGMP join (static-group):

set protocols igmp interface fe-0/0/4.0 static group 228.9.9.9

 

 

SomeLabGuy@PE-1>   show igmp group detail 228.9.9.9
Interface: fe-0/0/4.0, Groups: 6
    Group: 228.9.9.9
        Group mode: Exclude
        Source: 0.0.0.0
        Source timeout: 0
        Last reported by: Local
        Group timeout:       0 Type: Static
        Output interface: fe-0/0/4.0

 

 

 

 

SomeLabGuy@PE-1>   show pim rps instance ACME-1 detail
Instance: PIM.ACME-1
 Address family INET
 RP: 111.111.111.111
Learned from 222.222.222.222 via: auto-rp
Mode: Sparse
Time Active: 07:27:59
Holdtime: 150 with 102 remaining
Group Ranges:
        224.0.0.0/4, 102s remaining
Active groups using RP:
        228.9.9.9

 

 

INTERFACE

set interfaces fe-0/0/4 unit 0 description "facing ACME-1"
set interfaces fe-0/0/4 unit 0 family inet address 10.1.1.1/24

 

 

NOW TESTING with PING

SomeLabGuy@PE-1>   ping routing-instance ACME-1 10.1.1.1
PING 10.1.1.1 (10.1.1.1): 56 data bytes
64 bytes from 10.1.1.1: icmp_seq=0 ttl=64 time=0.313 ms
64 bytes from 10.1.1.1: icmp_seq=1 ttl=64 time=0.325 ms

 

OKAY......here goes.

SomeLabGuy@PE-1>   ping routing-instance ACME-1 228.9.9.9 source 10.1.1.1
PING 228.9.9.9 (228.9.9.9): 56 data bytes

--- 228.9.9.9 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

 

 

OKAY....let's try with bypass-routing


SomeLabGuy@PE-1> ...e ACME-1 228.9.9.9 source 10.1.1.1 bypass-routing
PING 228.9.9.9 (228.9.9.9): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host

 

 

 

2 REPLIES 2
Highlighted
Routing

Re: Multicast Testing

‎02-13-2017 06:43 PM

Hi,

 

You can probably try using protocol sap instead of igmp for doing ping test. Here are the details:

 

http://www.juniper.net/documentation//en_US/junos/topics/reference/configuration-statement/sap-edit-...

http://www.juniper.net/techpubs/en_US/junos/topics/task/verification/routing-protocol-multicast-secu...

 

To Initiate Traffic: 'ping 239.2.2.2 bypass-routing interface ge-x/y/z.t ttl 10 count 10000 source 1.1.1.1 interval 1 size 1000

 

Hope this helps.

 

Thanks


--------------------------------------------------------------------------------------------------------
If this post was helpful, please mark this post as an "Accepted Solution".
Kudos are always appreciated!
--------------------------------------------------------------------------------------------------------

Hope this helps

--------------------------------------------------------------------------------------------------------
If this post was helpful, please mark this post as an "Accepted Solution".
Kudos are always appreciated!
--------------------------------------------------------------------------------------------------------
Highlighted
Routing

Re: Multicast Testing

[ Edited ]
‎02-14-2017 10:53 AM

Hi SaraThirao,

Thanks again for helping with these Juniper configs.   It seems to be true that Juniper makes everything difficult.  Why is it such a pain to test multicast.  Cisco makes it easy.    Very frustrated with this.

 

I was happy to see your post.  It showed me that I was on the right track with SAP. Unfortunately it still does not work.

I should be able to ping a local multicast address, right?

 


ping 228.9.9.9  routing-instance ACME-1 bypass-routing interface fe-0/0/4.0 ttl 10 count 10000 source 11.11.11.11 interval 1 size 1000

 

 

SomeLabGuy@PE-1> ...ount 10000 source 11.11.11.11 interval 1 size 1000
PING 228.9.9.9 (228.9.9.9): 1000 data bytes
^C
--- 228.9.9.9 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss

 





set protocols sap listen 228.9.9.9

SomeLabGuy@PE-1#     run show sap listen
Group Address   Port
224.2.127.254   9875
228.9.9.9       9875



set protocols igmp interface lo0.1 static group 228.9.9.9
set protocols igmp interface fe-0/0/4.0 static group 228.9.9.9

SomeLabGuy@PE-1#      run show igmp group terse
Interface: fe-0/0/4.0, Groups: 6
  Group: 224.0.0.2
  Group: 224.0.0.5
  Group: 224.0.0.6
  Group: 224.0.0.13
  Group: 224.0.0.22
  Group: 228.9.9.9
Interface: local, Groups: 6
  Group: 224.0.0.2
  Group: 224.0.0.5
  Group: 224.0.0.6
  Group: 224.0.0.13
  Group: 224.2.127.254
  Group: 228.9.9.9
 
 
SomeLabGuy@PE-1# run show igmp group 228.9.9.9
Interface: fe-0/0/4.0, Groups: 6
    Group: 228.9.9.9
        Source: 0.0.0.0
        Last reported by: Local
        Timeout:       0 Type: Static
Interface: local, Groups: 6
    Group: 228.9.9.9
        Source: 0.0.0.0
        Last reported by: Local
        Timeout:       0 Type: Dynamic

        
SomeLabGuy@PE-1#   run show igmp interface
Interface: fe-0/0/4.0
    Querier: 10.1.1.1
    State:         Up Timeout:    None Version:  2 Groups:      6
    Immediate leave: Off
    Promiscuous mode: Off
    Passive: Off
    
    
    

set interfaces fe-0/0/4 unit 0 family inet address 10.1.1.1/24
set interfaces lo0 unit 1 family inet address 11.11.11.11/32
                
SomeLabGuy@PE-1# show routing-instances ACME-1 | match interface | display set
set routing-instances ACME-1 interface fe-0/0/4.0
set routing-instances ACME-1 interface lo0.1
set routing-instances ACME-1 protocols ospf area 0.0.0.2 interface fe-0/0/4.0 priority 255
set routing-instances ACME-1 protocols ospf area 0.0.0.2 interface lo0.1
set routing-instances ACME-1 protocols pim interface all mode sparse-dense
set routing-instances ACME-1 protocols pim interface fe-0/0/4.0 priority 777
        
    
SomeLabGuy@PE-1#   run show pim interfaces instance ACME-1
Instance: PIM.ACME-1
<SNIP>
Name               Stat Mode IP V State        NbrCnt JoinCnt(sg/*g) DR address
fe-0/0/4.0         Up   SD    4 2 DR,NotCap         1 1/1            10.1.1.1
lo0.1              Up   SD    4 2 DR,NotCap         0 0/0            11.11.11.11
lsi.0              Up   SD    4 2 P2P,NotCap        0 0/0
ppe0.32769         Up   S     4 2 P2P,NotCap        0 0/0
lsi.0              Up   SD    6 2 P2P,NotCap        0 0/0

 

 

 

SomeLabGuy@PE-1#   run show pim rps instance ACME-1 detail
Instance: PIM.ACME-1
Address family INET
RP: 111.111.111.111
Learned from 222.222.222.222 via: auto-rp
Mode: Sparse
Time Active: 1d 01:37:38
Holdtime: 150 with 97 remaining
Group Ranges:
        224.0.0.0/4, 97s remaining
Active groups using RP:
        228.9.9.9

 

 

SomeLabGuy@PE-1# run show route table ACME-1.inet.0 111.111.111.111
ACME-1.inet.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
111.111.111.111/32 *[OSPF/10] 1d 01:41:00, metric 1
                    > to 10.1.1.100 via fe-0/0/4.0

 

 

Feedback