FW: Auto-RP : Multiple C-RPs for the same group

From: hadek.el-ayachi@nsn.com
Date: Tue Oct 30 2007 - 12:44:46 ART


RP is selected based on the following criteria, respectively:
      1- Longest match
      2- low Priority
      3- high hash
      4- high Ip address
In case of AutoRP, this is equivalent to the 4th condition, provided
that there are many condidates for the same prefix (exact match)

________________________________

From: ext Toh Soon, Lim [mailto:tohsoon28@gmail.com]
Sent: mardi 30 octobre 2007 15:21
To: El Ayachi Hadek (NSN - MA/Rabat)
Cc: ccielab@groupstudy.com
Subject: Re: Auto-RP : Multiple C-RPs for the same group

Hi,

Kindly correct me if I'm wrong.

A Mapping Agent selects the RP for a given multicast group address
range(s) based on the candidate RPs' IP address. The highest candidate
RP IP address is selected.

In other words, the tie-breaker is purely based on C-RP's IP address.

Thank you.

B.Rgds,
Lim TS

On 10/30/07, hadek.el-ayachi@nsn.com <hadek.el-ayachi@nsn.com> wrote:

        The task is to make R5 RP for all but 239/8, so you should use
selective
        acl denying 239/8.
        Otherwise, the RP is selected based on longest match (before
prefering
        low priority, high hash or high IP address)
        All that I know!
        -----Original Message-----
        From: nobody@groupstudy.com [mailto:nobody@groupstudy.com ] On
Behalf Of
        ext Toh Soon, Lim
        Sent: mardi 30 octobre 2007 13:51
        To: ccielab@groupstudy.com
        Subject: Auto-RP : Multiple C-RPs for the same group

        Hi Group,

        I have the following Auto-RP scenario:

        R7
        --
        1. C-RP for 239.0.0.0/8
        2. RP address 200.0.0.7

        R5
        --
        1. Mapping agent
        2. C-RP for all groups except 239.0.0.0/8 3. RP address
200.0.0.5

        I guess one way of configuring this is, we define an ACL on R5
that
        matches groups 224 until 238 (summarizing whatever we can) and
let R5
        announce this group-list.

        Another way I'm thinking of is, since R7's IP address is higher
than
        R5's, I will configure R5 to announce, by default, all groups.
When R5
        and R7 contend for group 239.0.0.0/8, R7 will win. R5 will be RP
for the
        rest of the groups. In the end, this solution meets the task
requirement
        and does not violate any rules but is it acceptable?

        Please share if you have other methods.

        Thank you.

        B.Rgds,
        Lim TS



This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:19 ART