Routing

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



  • 1.  Verification for PIM Registers Processed by RP

    Posted 02-19-2013 05:39

    I was testing a scenario where there is functioning multicast network. The RP information has been disseminated correctly and all the multicast routers have this information. I verified that there were no RPF issues. Essentially, everything works as desired.

     

    Now in this network, I introduce a multicast source. The FRR connected to the source sends a unicast PIM register message to the RP (verified via traceoptions). The RP responds with the register-stop (verified via traceoptions).

     

    My scenario tested is as follows :-

     

    If there is source but no receivers, I expect to see an S,G state on the RP and the FRR. I do see this on the FRR (show pim join) but all the commands I tried do not show this S,G state on the RP. I know the register has been received and processed as I see that in the traceoptions. Furthermore, as soon as I add a receiver to the network, both *,G and S,G states immediately become visible in the "show pim join" at the RP and the traffic flows without a hitch.

     

    The question then is this :-

     

    Without any receivers on the network, how can one verify that the source has registered with the RP properly without having to rely on traceoptions?

     

    Please let me know if the scenario needs further elaboration.

     

    Thanks,

     

    Nic


    #Multicast
    #pimregister
    #pim-sm


  • 2.  RE: Verification for PIM Registers Processed by RP

    Posted 02-19-2013 05:45
    I guess you tried "show multicast route", could you confirm? Ato


  • 3.  RE: Verification for PIM Registers Processed by RP

    Posted 02-19-2013 05:54
    Feb 19 07:34:01.630920 PIM gre.0 RECV 192.168.36.1 -> 192.168.24.1 V2 Register Flags: 0x00000000 Border: 0 Null: 0 Source 1.1.1.1 Group 228.1.1.2 sum 0xdeff len 92 
    Feb 19 07:34:01.631181 PIM SENT 192.168.24.1 -> 192.168.36.1 V2 RegisterStop Source 0.0.0.0 Group 228.1.1.2 sum 0xf6db len 18 
    
    
    nbhasin@Sangiovese> show multicast route 
    Instance: master Family: INET
    
    Group: 224.0.1.39
        Source: 192.168.24.1/32 
        Upstream interface: local
        Downstream interface list: 
            local gre.1 gre.0
    
    Group: 224.0.1.40
        Source: 192.168.20.1/32 
        Upstream interface: gre.1
        Downstream interface list: 
            local gre.0
    
    Instance: master Family: INET6
    
    nbhasin@Sangiovese> 

    I tried out that command just now (was only using PIM commands up until now except for RPFs) but unfortunately no luck.

     

    The output above is from the RP. The log message shows  that the register/register-stop were processed for 228.1.1.2. But nothing in the "show multicast route" or any other PIM commands.

     

    On a side note, what is the major difference between "show multicast route" and "show pim join"?

     

    Thanks,

     

    Nic



  • 4.  RE: Verification for PIM Registers Processed by RP

    Posted 02-19-2013 05:56
    Can you post the (edit protocols pim) config of the FHR and the RP?


  • 5.  RE: Verification for PIM Registers Processed by RP

    Posted 02-19-2013 06:06

    FHR ----------------GRE.0 (10.222.4.0/24)------------------RP

     

    FHR output

    nbhasin@Shiraz# show protocols pim 
    traceoptions {
        file PIM;
        flag register detail;
    }
    dense-groups {
        224.0.1.40/32;
    }
    rp {
        auto-rp discovery;
    }
    interface gre.0 {
        mode sparse-dense;
    }
    interface gre.1 {
        mode sparse-dense;
    }
    interface gre.2 {
        mode sparse-dense;
    }
    
    [edit]
    
    nbhasin@Shiraz# run show pim rps 
    
    Instance: PIM.master
    Address family INET
    RP address      Type        Mode   Holdtime Timeout Groups Group prefixes
    192.168.24.1    auto-rp     sparse      150     137      0 224.0.0.0/4
    
    Address family INET6
    

     RP

    nbhasin@Sangiovese# show protocols pim 
    traceoptions {
        file AUTORP;
        flag register;
    }
    dense-groups {
        224.0.1.40/32;
        224.0.1.39/32;
    }
    rp {
        local {
            address 192.168.24.1;
        }
        auto-rp announce;
    }
    interface gre.0 {
        mode sparse-dense;
    }
    interface gre.1 {
        mode sparse-dense;
    }
    interface lo0.0 {
        mode sparse-dense;
    }
                                            
    [edit]
    nbhasin@Sangiovese# run show pim rps 
    Instance: PIM.master
    Address family INET
    RP address      Type        Mode   Holdtime Timeout Groups Group prefixes
    192.168.24.1    auto-rp     sparse      150     136      2 224.0.0.0/4
    192.168.24.1    static      sparse      150    None      2 224.0.0.0/4
    
    Address family INET6

     The show pim join outputs :-

     

    FHR

    nbhasin@Shiraz# run show pim join 
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 224.0.1.40
        Source: 192.168.20.1
        Flags: dense
        Upstream interface: gre.0
    
    Group: 228.1.1.2
        Source: 1.1.1.1
        Flags: sparse,spt
        Upstream interface: gre.2                 
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    [edit]
    nbhasin@Shiraz# run show pim join     

     RP

    nbhasin@Sangiovese# run show pim join 
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 224.0.1.39
        Source: 192.168.24.1
        Flags: dense
        Upstream interface: Local
    
    Group: 224.0.1.40
        Source: 192.168.20.1
        Flags: dense
        Upstream interface: gre.1
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    

     I really appreciate you taking a look at this.

     

    Thanks,

     

    Nic

     



  • 6.  RE: Verification for PIM Registers Processed by RP
    Best Answer

     
    Posted 02-19-2013 06:10

    show pim rps extensive  

    on FHR and RP 

     

     

    Krasi



  • 7.  RE: Verification for PIM Registers Processed by RP

    Posted 02-19-2013 06:15

    Nailed it!

     

     

    show pim rps extensive on the RP:

    nbhasin@Sangiovese# run show pim rps extensive    
    Instance: PIM.master
    Address family INET
    
    RP: 192.168.24.1
    Learned from 192.168.20.1 via: auto-rp
    Mode: Sparse
    Time Active: 1d 16:35:12
    Holdtime: 150 with 100 remaining
    Device Index: 26
    Subunit: 32769
    Interface: pimd.32769
    Group Ranges:
            224.0.0.0/4, 100s remaining
    Register State for RP:
    Group           Source          FirstHop        RP Address      State    Timeout
    228.1.1.2       1.1.1.1         192.168.36.1    192.168.24.1    Receive      176
    
    RP: 192.168.24.1
    Learned via: static configuration
    Mode: Sparse
    Time Active: 1d 17:08:16
    Holdtime: 150
    Device Index: 26
    Subunit: 32769                          
    Interface: pimd.32769
    Static RP Override: Off
    Group Ranges:
            224.0.0.0/4
    
    Address family INET6

     

    Exactly what I was looking for.

     

    Thanks and kudos,

     

    Nic