From: Rich Collins (nilsi2002@gmail.com)
Date: Mon Oct 01 2007 - 15:31:30 ART
Bob,
Thanks for that great summary. My approach is to try to study and practice
the technologies but at the same time try to learn the 'terminology' of the
task requirements. It is aggravating to actually know the method or
technology but then to take the wrong approach because you missed the clue
in the task requirement statement.
Rgds
Rich
On 10/1/07, Bob Sinclair <bob@bobsinclair.net> wrote:
>
> Rich Collins wrote:
> > I'm curious about BSR. What should you see in the question to point you
> in
> > that direction versus DM, autorp or static RP?
> >
> Rich,
>
> The more you know about these methods, the easier it is to interpret the
> task requirements. The primary attribute of both Auto-RP and BSR is
> dynamic advertising and fail-over. One of the primary differentiators
> would be Cisco protocol (Auto-RP) versus IETF standard (BSR, PIMv2).
> Beyond that, there are many distinctions. For example:
>
> Auto-RP works with the multicast boundary to enable announcement filters
> for individual groups, BSR does not.
>
> Auto-RP RPs and MAs use IP multicast trees to communicate, BSR uses a
> combination of subnet-local multicasts and unicast.
>
> BSR gives us priorities to control candidate RPs and BSRs, Auto-RP does
> not.
>
> Auto-RP gives us the scope parameter, BSR does not. This is one of the
> reasons Beau Williamson is still so hot on Auto-RP.
>
> As with all topics, the more you know about the protocol and the IOS
> options, the easier it is to interpret the task requirements.
>
> HTH,
>
>
> --
>
>
> Bob Sinclair CCIE 10427 CCSI 30427
> www.netmasterclass.net
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:11 ART