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.  Testing multicast on small setup

    Posted 09-20-2014 16:56

    Hi all,

     

        I am trying to test a small multicast setup and it's not working. The setup conists of four routers. Router3 is acting as the source of the multicast traffic and Router4 is acting as the client joining the multicast group. The multicast group is 224.140.140.1. Below is the network diagram and the configs for the four routers. I am sending pings from router to group 224.140.140.1 and on Router4 I have joined the group using interface fe-0/0/0.

     

    Router1:

     

    root@Router1> show configuration protocols 
    ospf {
        area 0.0.0.0 {
            interface fe-0/0/7.0;
            interface fe-0/0/0.0;
            interface fe-0/0/6.0;
        }
    }
    pim {
        rp {
            local {
                address 160.6.6.6;
            }
        }
        interface fe-0/0/0.0;
        interface fe-0/0/6.0;
        interface fe-0/0/7.0;

    root@Router1> show ospf neighbor
    Address Interface State ID Pri Dead
    166.1.12.2 fe-0/0/0.0 Full 160.6.6.6 128 39
    166.1.21.2 fe-0/0/6.0 Full 160.6.6.6 128 39
    166.1.13.3 fe-0/0/7.0 Full 160.3.3.3 128 31

    root@Router1>


    root@Router1> show pim interfaces
    Instance: PIM.master

    Stat = Status, V = Version, NbrCnt = Neighbor Count,
    S = Sparse, D = Dense, B = Bidirectional,
    DR = Designated Router, P2P = Point-to-point link,
    Active = Bidirectional is active, NotCap = Not Bidirectional Capable

    Name Stat Mode IP V State NbrCnt JoinCnt(sg/*g) DR address
    fe-0/0/0.0 Up S 4 2 NotDR,NotCap 1 0/0 166.1.12.2
    fe-0/0/6.0 Up S 4 2 NotDR,NotCap 1 0/0 166.1.21.2
    fe-0/0/7.0 Up S 4 2 NotDR,NotCap 1 0/0 166.1.13.3
    ppd0.32770 Up S 4 2 P2P,NotCap 0 0/0

    root@Router1> show pim neighbors
    B = Bidirectional Capable, G = Generation Identifier
    H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
    P = Hello Option DR Priority, T = Tracking Bit

    Instance: PIM.master
    Interface IP V Mode Option Uptime Neighbor addr
    fe-0/0/0.0 4 2 HPLGT 03:30:36 166.1.12.2
    fe-0/0/6.0 4 2 HPLGT 03:30:36 166.1.21.2
    fe-0/0/7.0 4 2 HPLGT 01:01:56 166.1.13.3

    root@Router1>


    root@Router1> show route protocol ospf

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

    160.3.3.3/32 *[OSPF/10] 00:54:57, metric 1
    > to 166.1.13.3 via fe-0/0/7.0
    160.6.6.0/24 *[OSPF/10] 00:34:41, metric 1
    to 166.1.12.2 via fe-0/0/0.0
    > to 166.1.21.2 via fe-0/0/6.0
    160.6.6.6/32 *[OSPF/10] 00:34:41, metric 1
    to 166.1.12.2 via fe-0/0/0.0
    > to 166.1.21.2 via fe-0/0/6.0
    166.1.24.0/24 *[OSPF/10] 00:38:22, metric 2
    > to 166.1.12.2 via fe-0/0/0.0
    to 166.1.21.2 via fe-0/0/6.0
    224.0.0.5/32 *[OSPF/10] 00:56:04, metric 1
    MultiRecv

     

    Router2:

     

    root@Router2> show configuration protocols 
    ospf {
        export ADV_NETWORK;
        area 0.0.0.0 {
            interface fe-0/0/0.0;
            interface fe-0/0/6.0;
            interface 160.2.2.2;
            interface fe-0/0/7.0;
            interface lo0.0 {
                passive;
            }
        }
    }
    pim {
        rp {
            local {
                address 160.6.6.6;
            }
        }
        interface fe-0/0/0.0;
        interface fe-0/0/6.0;
        interface fe-0/0/7.0;
        interface lo0.0 {
            version 2;
        }                                   
    }
    lldp {
        interface all;
    }
    stp;
    
    root@Router2> show ospf neighbor 
    Address          Interface              State     ID               Pri  Dead
    166.1.12.1       fe-0/0/0.0             Full      160.1.1.1        128    36
    166.1.21.1       fe-0/0/6.0             Full      160.1.1.1        128    36
    166.1.24.4       fe-0/0/7.0             Full      166.1.24.4       128    37
    
    root@Router2> show pim interfaces 
    
    show pim neighbors
    
    Instance: PIM.master
    s
    Stat = Status, V = Version, NbrCnt = Neighbor Count,
    S = Sparse, D = Dense, B = Bidirectional,
    DR = Designated Router, P2P = Point-to-point link,
    Active = Bidirectional is active, NotCap = Not Bidirectional Capable
    
    Name               Stat Mode IP V State        NbrCnt JoinCnt(sg/*g) DR address
    fe-0/0/0.0         Up   S     4 2 DR,NotCap         1 0/0            166.1.12.2
    how fe-0/0/6.0         Up   S     4 2 DR,NotCap         1 0/0            166.1.21.2
    rofe-0/0/7.0         Up   S     4 2 DR,NotCap         0 0/0            166.1.24.2
    utlo0.0              Up   S     4 2 DR,NotCap         0 0/0            160.6.6.6
    eppd0.32769         Up   S     4 2 P2P,NotCap        0 0/0
     
    protocol ospfroot@Router2> 
    
    root@Router2> show pim neighbors 
    B = Bidirectional Capable, G = Generation Identifier
    H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
    P = Hello Option DR Priority, T = Tracking Bit
    
    Instance: PIM.master
    Interface           IP V Mode        Option       Uptime Neighbor addr
    fe-0/0/0.0           4 2             HPLGT      03:36:59 166.1.12.1     
    fe-0/0/6.0           4 2             HPLGT      03:36:59 166.1.21.1     
    
    root@Router2> 
    
    root@Router2> show route protocol ospf 
    
    inet.0: 17 destinations, 17 routes (17 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both
    
    160.3.3.3/32       *[OSPF/10] 01:00:34, metric 2
                          to 166.1.12.1 via fe-0/0/0.0
                        > to 166.1.21.1 via fe-0/0/6.0
    166.1.13.0/24      *[OSPF/10] 01:00:34, metric 2
                        > to 166.1.12.1 via fe-0/0/0.0
                          to 166.1.21.1 via fe-0/0/6.0
    224.0.0.5/32       *[OSPF/10] 01:00:49, metric 1
                          MultiRecv
    
    inet.1: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
    
    inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
    
    inet6.1: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
    
    root@Router2> 

     

    Router3:

     

    root@Router3> show configuration protocols 
    ospf {
        area 0.0.0.0 {
            interface fe-0/0/0.0;
        }
    }
    pim {
        interface fe-0/0/0.0;
    }
    
    root@Router3> show ospf neighbor 
      Address         Interface             State      ID              Pri  Dead
    166.1.13.1       fe-0/0/0.0             Full      160.1.1.1        128   39  
    
    root@Router3> show pim interfaces 
    Instance: PIM.master
    
    Name                   Stat Mode       IP V State Count DR address
    fe-0/0/0.0             Up   Sparse      4 2 DR        1 166.1.13.3
    
    
    show pim neighbors
    
    show route protocol ospfroot@Router3> 
    
    root@Router3> show pim neighbors 
    Instance: PIM.master
    
    Interface           IP V Mode        Option      Uptime Neighbor addr
    fe-0/0/0.0           4 2             HPLG      01:09:46 166.1.13.1     
    
    root@Router3> 
    
    root@Router3> show route protocol ospf 
    
    inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both
    
    160.6.6.0/24       *[OSPF/10] 00:42:07, metric 2
                        > to 166.1.13.1 via fe-0/0/0.0
    160.6.6.6/32       *[OSPF/10] 00:42:07, metric 2
                        > to 166.1.13.1 via fe-0/0/0.0
    166.1.12.0/24      *[OSPF/10] 01:02:07, metric 2
                        > to 166.1.13.1 via fe-0/0/0.0
    166.1.21.0/24      *[OSPF/10] 01:02:02, metric 2
                        > to 166.1.13.1 via fe-0/0/0.0
    166.1.24.0/24      *[OSPF/10] 00:45:48, metric 3
                        > to 166.1.13.1 via fe-0/0/0.0
    224.0.0.5/32       *[OSPF/10] 01:03:14, metric 1
                          MultiRecv
    
    __juniper_private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
    
    inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
    
    root@Router3> 

     

    Router4:

     

    [edit]
    root@Router4# exit 
    Exiting configuration mode
    
    root@Router4> show configuration protocols 
    igmp {
        interface fe-0/0/0.0 {
            static {
                group 224.140.140.1;
            }
        }
    }
    ospf {
        area 0.0.0.0 {
            interface fe-0/0/0.0;
        }
    }
    
    root@Router4> show ospf neighbor 
      Address         Interface             State      ID              Pri  Dead
    166.1.24.2       fe-0/0/0.0             Full      160.6.6.6        128   33  
    
    root@Router4> show pim interfaces 
    PIM instance is not running
    
    
    show pim neighbors
    
    show route protocol ospfroot@Router4> 
    
    root@Router4> show pim neighbors 
    PIM instance is not running
    
    root@Router4> 
    
    root@Router4> show route protocol ospf 
    
    inet.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both
    
    160.3.3.3/32       *[OSPF/10] 00:46:57, metric 3
                        > to 166.1.24.2 via fe-0/0/0.0
    160.6.6.0/24       *[OSPF/10] 00:43:15, metric 1
                        > to 166.1.24.2 via fe-0/0/0.0
    160.6.6.6/32       *[OSPF/10] 00:43:15, metric 1
                        > to 166.1.24.2 via fe-0/0/0.0
    166.1.12.0/24      *[OSPF/10] 00:46:57, metric 2
                        > to 166.1.24.2 via fe-0/0/0.0
    166.1.13.0/24      *[OSPF/10] 00:46:57, metric 3
                        > to 166.1.24.2 via fe-0/0/0.0
    166.1.21.0/24      *[OSPF/10] 00:46:57, metric 2
                        > to 166.1.24.2 via fe-0/0/0.0
    224.0.0.5/32       *[OSPF/10] 01:02:25, metric 1
                          MultiRecv
    
    __juniper_private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
    
    root@Router4>


    [edit]
    root@Router4# show protocols igmp
    interface all;
    interface fe-0/0/0.0 {
    static {
    group 224.140.140.1;
    }
    }

    [edit]
    root@Router4#

     

     

    Screen Shot 2014-09-20 at 7.42.59 PM.png

     

     


    #routing
    #Multicast
    #PIM


  • 2.  RE: Testing multicast on small setup

    Posted 09-21-2014 01:00
    Check page 22-24 of:

    http://www.juniper.net/us/en/training/jnbooks/day-one/networking-technologies-series/a-packet-walkthrough/

    It's a MVPN example but you'll see some tricks that apply to IPv4 multicast too.

    The First-Hop Router and the Last-Hop Router must be the DR at the host-facing segments.


  • 3.  RE: Testing multicast on small setup
    Best Answer

    Posted 09-21-2014 06:31

    Hi,

     

    There are a few things to check.

     

     

    Router3 is the source, it doesn't need to run PIM. Same for Router4 which is the receiver.

    Thus let's call them respectively Host3 and Host4 just to avoid confusions.

     

     

     

    You should start by confirming that all your PIM routers know the correct RP.  From your configs it appears to me the RP is Router2 with IP 160.6.6.6 and it is learned statically. In that case on Router1 the configuration should include the following lines:

     

    pim {
        rp {
            static {
                address 160.6.6.6;
            }
        }
    }

    You can then confirm running show pim rps

     

     

    Then as I said earlier you don't need to run PIM on the source Host3. Disable it, this will ensure that Router1 is the DR for the subnet Router1-Host3.

     

     

     

    Also the IGMP static group membership should not be configured on the receiver Host4 but on the DR for that subnet (in your scenario it would be Router2).

     

     

    --
    If this post solves your problem, please mark this post as "Accepted Solution".
    Kudos are appreciated

     



  • 4.  RE: Testing multicast on small setup

    Posted 09-22-2014 17:49

    Pantunes,

     

        Thank you. Your suggestions worked for me.