pim JoinDesired warning

Solaris · October 2, 2010, 3:37pm

I need help about these warning :

19:28:47 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.88.1 and group 239.255.255.250: not found
19:28:48 pim,info Added new address to interface Server: 192.168.88.1/30
19:28:48 pim,info PIM interface started: Server
19:28:48 pim,info IGMP interface started: Server
19:29:01 pim,info PIM interface stopped: Server
19:29:01 pim,info IGMP interface stopped: Server
19:29:01 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.88.1 and group 239.255.255.250: not found
19:36:46 dhcp,info dhcp-server deassigned 192.168.88.2 from 00:24:1D:8E:84:E4
20:36:35 pim,info Added new address to interface Server: 192.168.88.1/30
20:36:35 pim,info PIM interface started: Server
20:36:35 pim,info IGMP interface started: Server
20:38:33 pim,info PIM interface stopped: Server
20:38:33 pim,info IGMP interface stopped: Server
20:38:33 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.88.1 and group 239.255.255.250: not found
20:41:51 pim,info Added new address to interface Server: 192.168.88.1/30
20:41:51 pim,info PIM interface started: Server
20:41:51 pim,info IGMP interface started: Server
20:48:10 pim,info PIM interface stopped: Client
20:48:10 pim,info IGMP interface stopped: Client
20:48:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.66.1 and group 239.255.255.250: not found
20:48:10 pim,warning JoinDesired(S,G) = false: upstream neighbor for source 192.168.66.2 and group 239.255.255.250: not found
20:52:12 pim,info Added new address to interface Client: 192.168.66.1/30
20:52:12 pim,info PIM interface started: Client
20:52:12 pim,info IGMP interface started: Client

my pim interfaces :

[admin@local] /routing pim interface> pr
Flags: X - disabled, I - inactive, D - dynamic, R - designated-router, v1 - IGMPv1, v2 - IGMPv2, v3 - IGMPv3 
 #      INTERFACE                                               PROTOCOLS                                             
 0  Rv2 Server                                             pim                                                   
                                                                igmp                                                  
 1  Rv2 Client                                             pim                                                   
                                                                igmp                                                  
 2 DR   register                                                pim

pim rp :

[admin@local] /routing pim rp> pr
Flags: D - dynamic, X - disabled 
 #    ADDRESS         TYPE      PRIORITY  
 0    192.168.66.1    static    192

pim mrib :

[admin@local] /routing pim mrib> pr
Flags: X - disabled, I - inactive, D - dynamic 
 #   DESTINATION        GATEWAY         METRIC INTERFACE                                                              
 0 D 0.0.0.0/0          192.168.1.1     1       Wan                                                                    
 1 D 192.168.1.0/24     0.0.0.0         0      Wan                                                                    
 2 D 192.168.55.0/29    0.0.0.0         0      House                                                                  
 3 D 192.168.66.0/30    0.0.0.0         0      Client                                                            
 4 D 192.168.77.0/30    0.0.0.0         0      Squid                                                                  
 5 D 192.168.88.0/30    0.0.0.0         0      Server                                                            
 6 D 192.168.99.0/28    0.0.0.0         0      Hotspot

pim mfc :

[admin@local] /routing pim mfc> pr
GROUP           SOURCE          RP             
239.255.255.250 192.168.66.2    192.168.66.1   
239.255.255.250 192.168.88.1    192.168.66.1

pim join :

[admin@local] /routing pim join> pr
Flags: RP - (*,*,RP), WC - (*,G), SG - (S,G), SG_rpt - (S,G,rpt) 
       GROUP           SOURCE          RP             
    WC 224.0.0.0       192.168.66.1    192.168.66.1   
    SG 239.255.255.250 0.0.0.0         192.168.66.1   
SG_rpt 239.255.255.250 192.168.66.2    192.168.66.1   
SG_rpt 239.255.255.250 192.168.88.1    192.168.66.1

pim igmp-group :

[admin@local] /routing pim igmp-group> pr
Flags: v1 - IGMPv1, v2 - IGMPv2, v3 - IGMPv3, I - include, E - exclude, F - forward, D - don't forward 
    INTERFACE                                                     GROUP           SOURCE          TIMEOUT             
v2E Server                                                   224.0.0.2       0.0.0.0         3m14s               
v2E Server                                                   224.0.0.13      0.0.0.0         3m15s               
v2E Server                                                   224.0.0.22      0.0.0.0         3m8s                
v2E Server                                                   239.255.255.250 0.0.0.0         3m10s               
v2E Client                                                   224.0.0.2       0.0.0.0         3m9s                
v2E Client                                                   224.0.0.13      0.0.0.0         3m10s               
v2E Client                                                   224.0.0.22      0.0.0.0         3m9s                
v2E Client                                                   239.255.255.250 0.0.0.0         3m3s

I just need to ‘join’ client and server interface together both upstream and downstream to each other, specifically udp, all works fine but as you can see above, it throws the warning , please help to eliminate the warning .

Solaris · October 5, 2010, 9:58pm

anyone can help?

janisk · October 20, 2010, 1:34pm

can you see router in neighbors? also, what version you are using?

have you tried to reboot router when applied the settings?, have you tried to reboot other routers in the multicast cloud?

Solaris · October 20, 2010, 7:37pm

yes both of the device can see the router, hmm, it’s only 1 router used, in simple word i wanted to interconnected 2 devices from 2 different subnet which is these 2 :

3 D 192.168.66.0/30    0.0.0.0         0      Client   
5 D 192.168.88.0/30    0.0.0.0         0      Server

The purpose of ip routing pim can be applied for my case right? or i get the concept wrong?. My topology

    Mikrotik RB 1100
       |          |
       |          |
       |          |
   Client     Server

janisk · October 22, 2010, 9:22am

hmm.. you have to set only 2 interfaces and rp for this to work in either direction even if you have nat in between.

Solaris · October 24, 2010, 5:17pm

yes i have set the interface only 2, server and client but somehow mikrotik added another available online interface into /routing pim mrib

Flags: X - disabled, I - inactive, D - dynamic 
 #   DESTINATION        GATEWAY         METRIC INTERFACE                       
 0 D 0.0.0.0/0          192.168.1.1     1      Wan                             
 1 D 192.168.1.0/24     0.0.0.0         0      Wan                             
 2 D 192.168.55.0/29    0.0.0.0         0      House                           
 3 D 192.168.66.0/30    0.0.0.0         0      Client                     
 4 D 192.168.77.0/30    0.0.0.0         0      Squid                           
 5 D 192.168.88.0/30    0.0.0.0         0      Server

Both client and server has internet access, could be one of the reason mikrotik adding more mrib? , how to stop mikrotik automatically adding these?

janisk · October 25, 2010, 12:03pm

they are taken from routing table, it is not possible to change that.