[pim] Secondary ip address in transit network
"iamredheart22 ." <myselfindranil@gmail.com> Wed, 18 February 2015 12:10 UTC
Return-Path: <myselfindranil@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D60F91A8547 for <pim@ietfa.amsl.com>; Wed, 18 Feb 2015 04:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uZ9UFLHBZ-G for <pim@ietfa.amsl.com>; Wed, 18 Feb 2015 04:10:32 -0800 (PST)
Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26C961A037C for <pim@ietf.org>; Wed, 18 Feb 2015 04:10:32 -0800 (PST)
Received: by iecrp18 with SMTP id rp18so679560iec.9 for <pim@ietf.org>; Wed, 18 Feb 2015 04:10:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LninLOqu3rI9xPs4xdiwqj+HjHtw6dMaBgHJIPpPrko=; b=K/E4VyxDdq+ARvZHnqc/3hDvBwfud+KK+IoMlF1xLDtEwOYBLJjFmdCMIwhzlnHBud EvEAE43daqYU9h6SHixwHPIYbWCXLtI1UY8cUJultBIWLDdcCODS2oJZPbB/yyNg9cRV G4wAUj3FUAldgpooPUhKFE9ho4XQtl9XHSIPc5+CocAmVJsFl4ulJCSoThtf5ssKWxrR Uhh8acN0lZLy5BBcCbRiKwB82bUsjywYVkzO0icA5C1jZAf+Kig7NBXY4EN/+435q8GT 7fgOWBDcknLF1S77bljMebJAMM07dbb6pET1lJUyarK+y+XdAQiL5BJKnOfsDu5bYREJ ORuw==
MIME-Version: 1.0
X-Received: by 10.42.88.9 with SMTP id a9mr40114163icm.34.1424261431630; Wed, 18 Feb 2015 04:10:31 -0800 (PST)
Received: by 10.36.104.15 with HTTP; Wed, 18 Feb 2015 04:10:31 -0800 (PST)
Date: Wed, 18 Feb 2015 17:40:31 +0530
Message-ID: <CAAaur94TtmoSmko2Soc+zPWVeyQKzPJdRYMBLdJNTC=n0SeD2Q@mail.gmail.com>
From: "iamredheart22 ." <myselfindranil@gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: multipart/alternative; boundary="90e6ba61486eb321e3050f5bb4ef"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/_7hpLf4cirr00Cvka65mtH31iCQ>
Subject: [pim] Secondary ip address in transit network
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 12:10:35 -0000
Hello, I have some doubt about PIM on secondary ip address in transit network. Please refer the topology shown below. Source(10.10.10.1)-----------------sw1---------------------------sw2------------Rcv RFC 4601 mentions the following points. "*4.3.4 <https://tools.ietf.org/html/rfc4601#section-4.3.4>Maintaining Secondary Address List* * Communication of a router's interface secondary addresses to its PIM neighbors is necessary to provide the neighbors with a mechanism for mapping next_hop information obtained through their MRIB to a primary address that can be used as a destination for Join/Prune messages."* * Then RFC also talks about the macros mentioned below..* * neighbor RPF'(*,G) { if ( I_Am_Assert_Loser(*, G, RPF_interface(RP(G))) ) { return AssertWinner(*, G, RPF_interface(RP(G)) ) } else { return NBR( RPF_interface(RP(G)), MRIB.next_hop( RP(G) ) ) } } "The function MRIB.next_hop( S ) returns an address of the next-hop PIM neighbor toward the host S, as indicated by the current MRIB. If S is directly adjacent, then MRIB.next_hop( S ) returns NULL. At the RP for G, MRIB.next_hop( RP(G)) returns NULL." "The function NBR( I, A ) uses information gathered through PIM Hello messages to map the IP address A of a directly connected PIM neighbor router on interface I to the primary IP address of the same router (Section 4.3.4 <https://tools.ietf.org/html/rfc4601#section-4.3.4>). The primary IP address of a neighbor is the address that it uses as the source of its PIM Hello messages*." What I understand from this is that MRIB.next_hop(S) can return a secondary ip address as a nexthop which then will pass through NBR macro which returns the primary address associated with this secondary address. This primary address is then used as the final nexthop neighbor. My question is that in a transit network by what configuration I can achieve a scenario so that nexhop(10.10.10.1) on sw2 returns a nexthop address which is configured as a secondary address on sw1? Can someone please help? Thanks, Indranil
- [pim] Secondary ip address in transit network iamredheart22 .
- Re: [pim] Secondary ip address in transit network iamredheart22 .
- Re: [pim] Secondary ip address in transit network Stig Venaas