Junos OS

last person joined: yesterday 

Ask questions and share experiences about Junos OS.
  • 1.  Multicast packet not getting out in logical systems basic topology

    Posted 04-06-2015 10:35

    Hi,

     

    I am using the following logical systems topology

     

    R1------------R2-------------R3

     

    R1 = designated_source router

    R3 = desinated_destinstion router

     

    When a ping packet is generated for R1 for the IGMP group, it says no route to host.

     

    Configs are as below for the logical systems:

     

    R1:

     

    set logical-systems R1 interfaces ge-0/0/0 unit 1 vlan-id 101
    set logical-systems R1 interfaces ge-0/0/0 unit 1 family inet address 10.0.0.1/24
    set logical-systems R1 interfaces lo0 unit 1 family inet address 1.1.1.1/32
    set logical-systems R1 protocols ospf area 0.0.0.0 interface all
    set logical-systems R1 protocols ospf area 0.0.0.0 interface fxp0.0 disable
    set logical-systems R1 protocols pim rp static address 2.2.2.2
    set logical-systems R1 protocols pim interface all mode sparse
    set logical-systems R1 protocols pim interface all version 2
    set logical-systems R1 protocols pim interface fxp0.0 disable
    set logical-systems R1 routing-options router-id 1.1.1.1

     

     

    R2:

     

    set logical-systems R2 interfaces ge-0/0/0 unit 2 vlan-id 102
    set logical-systems R2 interfaces ge-0/0/0 unit 2 family inet address 20.0.0.1/24
    set logical-systems R2 interfaces ge-0/0/1 unit 1 vlan-id 101
    set logical-systems R2 interfaces ge-0/0/1 unit 1 filter input PACKET_CAPTURE
    set logical-systems R2 interfaces ge-0/0/1 unit 1 family inet address 10.0.0.2/24
    set logical-systems R2 interfaces gr-0/0/10 unit 0 tunnel source 20.0.0.1
    set logical-systems R2 interfaces gr-0/0/10 unit 0 tunnel destination 20.0.0.2
    set logical-systems R2 interfaces gr-0/0/10 unit 0 family inet address 21.21.21.1/24
    set logical-systems R2 interfaces lo0 unit 2 family inet address 2.2.2.2/32
    set logical-systems R2 protocols ospf area 0.0.0.0 interface all
    set logical-systems R2 protocols ospf area 0.0.0.0 interface fxp0.0 disable
    set logical-systems R2 protocols pim rp local address 2.2.2.2
    set logical-systems R2 protocols pim interface all mode sparse
    set logical-systems R2 protocols pim interface all version 2
    set logical-systems R2 protocols pim interface fxp0.0 disable
    set logical-systems R2 routing-options static route 30.0.0.0/24 next-hop 21.21.21.2
    set logical-systems R2 routing-options router-id 2.2.2.2

     

    R3:

     

    set logical-systems R3 interfaces ge-0/0/0 unit 3 vlan-id 103
    set logical-systems R3 interfaces ge-0/0/0 unit 3 family inet address 30.0.0.1/24
    set logical-systems R3 interfaces ge-0/0/1 unit 2 vlan-id 102
    set logical-systems R3 interfaces ge-0/0/1 unit 2 filter input PACKET_CAPTURE
    set logical-systems R3 interfaces ge-0/0/1 unit 2 family inet address 20.0.0.2/24
    set logical-systems R3 interfaces gr-0/0/10 unit 1 tunnel source 20.0.0.2
    set logical-systems R3 interfaces gr-0/0/10 unit 1 tunnel destination 20.0.0.1
    set logical-systems R3 interfaces gr-0/0/10 unit 1 family inet address 21.21.21.2/24
    set logical-systems R3 interfaces lo0 unit 3 family inet address 3.3.3.3/32
    set logical-systems R3 protocols igmp interface ge-0/0/0.3 static group 225.1.1.1
    set logical-systems R3 protocols ospf area 0.0.0.0 interface all
    set logical-systems R3 protocols ospf area 0.0.0.0 interface fxp0.0 disable
    set logical-systems R3 protocols pim rp static address 2.2.2.2
    set logical-systems R3 protocols pim interface all mode sparse
    set logical-systems R3 protocols pim interface all version 2
    set logical-systems R3 protocols pim interface fxp0.0 disable
    set logical-systems R3 routing-options static route 1.1.1.1/32 next-hop 21.21.21.1
    set logical-systems R3 routing-options static route 10.0.0.0/24 next-hop 21.21.21.1
    set logical-systems R3 routing-options router-id 3.3.3.3

     

     

    The output at R1 after ping:

     

    root@vmx1_re# run ping 225.1.1.1 ttl 255 source 1.1.1.1 logical-system R1
    PING 225.1.1.1 (225.1.1.1): 56 data bytes
    ping: sendto: No route to host
    ping: sendto: No route to host
    ping: sendto: No route to host

     

     

     

    run show multicast route logical-system R1
    Instance: master Family: INET

    Group: 225.1.1.1
        Source: 1.1.1.1/32
        Upstream interface: local
        Downstream interface list:
            ge-0/0/0.1 pe-0/0/10.229377

    Instance: master Family: INET6

     

     

     

     



  • 2.  RE: Multicast packet not getting out in logical systems basic topology
    Best Answer

    Posted 04-06-2015 12:52

    Hello,

    Please try 

     

    root@vmx1_re# run ping 225.1.1.1 ttl 255 source 1.1.1.1 logical-system R1 bypass-routing interface ge-0/0/0.1 

     

    HTH

    Thanks

    Alex



  • 3.  RE: Multicast packet not getting out in logical systems basic topology

    Posted 04-06-2015 21:18

    Hi Alex,

     

    Many thanks for the help.

     

    Can you please tell me what is the purpose of the command "bypass-routing interface ge-x/x/x". Why is it required for the ping to go successfully?

     

    Thanks

    Sumit



  • 4.  RE: Multicast packet not getting out in logical systems basic topology

     
    Posted 04-06-2015 21:44

    the bypass -routing command is used to bypass the routing table and use the interface to send out the icmp request directly.

     

     



  • 5.  RE: Multicast packet not getting out in logical systems basic topology

    Posted 04-06-2015 21:48

    Hi Marc,

     

    Does this mean even if the router does not have a route for a particular prefix, one can inject a ping packet out of the interface for that particular prefix?

     

    Thanks

    Sumit



  • 6.  RE: Multicast packet not getting out in logical systems basic topology

     
    Posted 04-06-2015 22:33

    @sumit.trehan wrote:

    Hi Marc,

     

    Does this mean even if the router does not have a route for a particular prefix, one can inject a ping packet out of the interface for that particular prefix?

     

    Thanks

    Sumit


    Bypass the normal routing tables and send ping requests directly to a system on an attached network. If the system is not on a directly attached network, an error is returned. Use this option to ping a local system through an interface that has no route through it