From: Edwards, Andrew M (andrew.m.edwards@boeing.com)
Date: Mon Sep 12 2005 - 20:53:25 GMT-3
Dave,
You have multiple options for this... Aside from the 12.3GD release
command. I believe they are as follows:
1. If you use sparse-dense on an interface:
Weather using AutoRP or BSR, place one single static RP-address entry in
your config. Append and ACL to this entry which denies the 224.0.1.39
and 224.0.1.40 AutoRP addresses and permits anything else. This way, if
autoRP or BSR RP fails, the final static RP kicks in. The reason you
deny AutoRP is so they are always running in dense mode. 8)
2. If you use sparse-mode on an interface:
Use ip pim autorp listener for AutoRP, and again, one single static RP
entry with the appropriate ACL as mentioned above.
HTH,
andy
-----Original Message-----
From: Schulz, Dave [mailto:DSchulz@dpsciences.com]
Sent: Monday, September 12, 2005 11:11 AM
To: ccielab@groupstudy.com
Subject: Multicast - No ip pim dm-fallback vs. Sink RP
If there is a requirement that requires you to use Auto-RP, which means
using sparse-dense mode. And, another requirement to insure that you
never go into dense mode.....is it more correct to:
1. Use the command - "no ip pim dm-fallback"
Or,
2. Use the "sink RP" configuration that cisco details in the
following white-paper.....
http://cisco.com/en/US/tech/tk828/technologies_white_paper09186a00800d6b
63.shtml
Thoughts?
Dave Schulz
Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com >
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:14 GMT-3