[Xorp-users] Question regarding PIM-SM

[Pavlin Radoslavov]

Please add the following statement to your pimsm4 configuration:

        switch-to-spt-threshold {
            /* approx. 1K bytes/s (10Kbps) threshold */
            disable: false
            interval: 100
            bytes: 102400
        }

This will initiate the STP switch if the data bandwidth is above
10Kbps. If you want the switch to happen on the first data packet
for example, then change "bytes" to 0.

Pavlin


Jigar <jjajal at gmail.com> wrote:

> Pavlin,
> Thanks for your very quick reply.
> 
> Here I have attached the configuration file which is used on the RUT.
> Please note that I have not mentioned anything about static route in the
> configuration file but I have used XORP shell (xorpsh) for configuring it.
> 
> Following are the commands which I have fired on xorpsh to configure xorp:
> 
> # set protocols pimsm4 static-rps rp 12.22.33.44 group-prefix 224.0.0.0/4
> # set protocols static route 12.22.33.44/32 next-hop 10.100.3.220
> # set protocols static route 11.22.33.44/32 next-hop 10.100.3.221
> 
> Source address of UDP packet is 11.22.33.44.
> 
> Please refer to following details related to setup diagram which is sent
> in previous mail:
> 
> IP address of TR2 : 10.100.3.220/24
> IP address of TR1 : 10.100.3.221/24
> IP address of eth1 on RUT : 10.100.3.107/24
> IP address of eth0 on RUT : 192.168.14.212/24
> 
> Network 0: 192.168.14.0/24
> Network 2: 10.100.3.0/24
> 
> Thanks,
> Jigar
> 
> Pavlin Radoslavov wrote:
> > Please send your XORP configuration (on the RUT).
> >
> > Pavlin
> >
> > P.S. Yes, XORP supports the SPT switch.
> >
> >
> > Jigar <jjajal at gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> I want to test the following scenario given in RFC-4601 (PIM-SM) in
> >> section 3.3 ( Phase Three: Shortest Path Tree ):
> >> ##############################################################
> >> To obtain lower latencies or more efficient bandwidth utilization,
> >> a router on the receiver's LAN, typically the DR, may *optionally* initiate
> >> a transfer from the shared tree to a source specific shortest path tree (SPT).
> >> To do this, it issues an (S,G) Join towards S.
> >> ##############################################################
> >>
> >> I have tested this scenario with XORP and I found that XORP does not initiate
> >> this step.
> >>
> >> To test this particular initiation, I have following setup:
> >> Please find the setup which is attached.
> >>
> >> Test Setup details:
> >> - XORP PIM-SM is enabled on the RUT. The RP is statically configured
> >> for 224.0.6.130.
> >> - The RUT is the DR for network 0.
> >> - RUT has a static route to the RP through TR2.
> >> - The RUT has a static route to the source through TR1.
> >>
> >> Steps followed:
> >> 1. On networks 2, TR1 and TR2 transmit Hello messages.
> >> 2. On network 0, transmit IGMP reports for 224.0.6.130.
> >> 3. On network 1, the RP will transmit the data packets.
> >> 4. The multicast destination address of the data is 224.0.6.130.
> >> 5. TR2 will forward the data packets on to network 2.
> >>
> >> Expectations:
> >> - As expected, RUT forwards multicast data packets from network 2 to network 0.
> >> - As mentioned in statements in RFC, RUT may issue an (S,G) Join towards
> >> source.
> >> But I did not find any (S,G) Join on network 2.
> >>
> >> I want to know whether XORP supports the feature of creating Shortest Path Tree
> >> or not. If XORP initiates this step then please tell me where I am going wrong.
> >>
> >> Regards,
> >> Jigar Jajal
> >> _______________________________________________
> >> Xorp-users mailing list
> >> Xorp-users at xorp.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> >
> 
> /*$XORP*/
> 
> 
> interfaces {
>     restore-original-config-on-shutdown: false
>     interface eth0 {
> 	description: "data interface"
> 	disable: false
> 	default-system-config
>     }
>     interface eth1 {
> 	description: "data interface"
> 	disable: false
> 	default-system-config
>     }
> }
> 
> fea {
>     unicast-forwarding4 {
> 	disable: false
> 	forwarding-entries {
> 	    retain-on-startup: false
> 	    retain-on-shutdown:	false
> 	}
>     }
> }
> 
> plumbing {
>     mfea4 {
> 	disable: false
> 	interface eth0 {
> 	    vif eth0 {
> 		disable: false
> 	    }
> 	}
> 	interface eth1 {
> 	    vif eth1 {
> 		disable: false
> 	    }
> 	}
> 	interface register_vif {
> 	    vif register_vif {
> 		/* Note: this vif should be always enabled */
> 		disable: false
> 	    }
> 	}
> 	traceoptions {
> 	    flag all {
> 		disable: false
> 	    }
> 	}
>     }
> 
> }
> 
> protocols {
>  igmp {
>         disable: false
>         interface eth0 {
>             vif eth0 {
>                 disable: false
>                  version: 3
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                 disable: false
>                  version: 3
> 	    }
> 	}
>         traceoptions {
>             flag all {
>                 disable: false
>             }
>         }
>     }
> }
> 
> /*
> protocols {
> 	static {
> 		route 11.22.33.44/23 {
> 		next-hop: 10.100.3.220
> 		metric: 1
> 		}
> 	}
> }
> */
> protocols {
>  pimsm4 {
> 	disable: false
> 	interface eth0 {
> 	    vif eth0 {
> 		disable: false
> 	    }
> 	}
> 	interface eth1 {
> 	    vif eth1 {
> 		disable: false
> 	    }
> 	}
> 	interface register_vif {
> 	    vif register_vif {
> 		/* Note: this vif should be always enabled */
> 		disable: false
> 	    }
> 	}
> 	traceoptions {
> 	    flag all {
> 		disable: false
> 	    }
> 	}
>     }
> }
> 
> /*
>  * Note: fib2mrib is needed for multicast only if the unicast protocols
>  * don't populate the MRIB with multicast-specific routes.
>  */
> protocols {
>     fib2mrib {
> 	disable: false
>     }
> }
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users