From: ccie2be (ccie2be@nyc.rr.com)
Date: Fri Mar 25 2005 - 11:09:56 GMT-3
Hi guys,
I'm looking to find out what are considered "Best Practices" in the sequence
of configuring sparse-mode mcast particularly when using auto-rp
In the past, what I've done is this:
1 Enable mcast on all rtr's and configure all specified interfaces with ip
pim sparse-dense-mode.
2 Configured the rp
3 Configure the MA
4 Configure one or more interfaces to join one or more mcast groups.
5 Configure any restrictions
5 Test by pinging mcast group from all mcast routers
6 Troubleshoot
My experience with this process has been spotty. Sometimes, depending on
the topology everything has gone smoothly but occasionally, when things
don't work, troubleshooting problems has been very difficult and time
consuming.
In considering the process, I can see that it would be much better to save
step 5 until later on. But, I wonder if there's a better way.
Now, I think maybe I would be better off if I used a different process such
as this:
1 Identify which routers will be the rp and MA
2 Configure ONLY those routers and interfaces allowed by the scenario and
IN THE PATH between the rp and MA.
3 Configure the rp and MA
4 Configure an interface to Join a mcast group.
5 TEST
6 IF test doesn't succeed, look for rfp failure.
7 After finding rfp failure, configure static mroute.
8 Test
9 Configure any constraints, one at a time and test
9 Add additional mcast rtrs one at a time.
10 After each additional mcast rtr is adding, test again.
What does the GS community think of this?
TIA, Tim
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:51 GMT-3