multicast first ping puzzel!!
Don’t mean to hijack your thread, but I thought of this email when I got this ping result. I got it while doing testing msdp:
Cat3560-4#ping 225.0.0.25 re 1000
Type escape sequence to abort. Sending 1000, 100-byte ICMP Echos to 225.0.0.25, timeout is 2 seconds: …………………………………………………………. Reply to request 66 from 100.100.100.100, 17 ms… …………………………………………………………….. ……………… Reply to request 157 from 100.100.100.100, 17 ms………………
5 bucks if you can guess the next number! ![]()
On Mon, Sep 29, 2008 at 4:16 PM, one atatime wrote:
> My guess would be that you are successful for the first few pings then the > Mcast group switches to the SPT across the NBMA network. There is not a > direct PIM relationship between the spoke routers so they cannot build a > complete tree to each other. Try the following. > > Make the PIM router originating the request toward the RP the pim DR for > the > segment originating the IGMP (using the ip pim dr-priority interface > command). Then issue the “ip pim stp threhold infinity” command so that > when the tree is built to the RP it will never switch to the SPT (there is > no benefit in it doing so in this topology anyway). > > See if that sorts it out. > > Good luck > > Pick > > > Blogs and organic groups at http://www.ccie.net > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
























