Re: [OSPF] Fw: Tye - 5 and Type -3 LSA issues

Acee Lindem <acee@redback.com> Fri, 30 May 2008 12:08 UTC

Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 766303A67DD; Fri, 30 May 2008 05:08:10 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D5893A67DD for <ospf@core3.amsl.com>; Fri, 30 May 2008 05:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level:
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wOcBUvUruM94 for <ospf@core3.amsl.com>; Fri, 30 May 2008 05:08:07 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id CAA053A67A5 for <ospf@ietf.org>; Fri, 30 May 2008 05:08:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id B1A28B7BD25; Fri, 30 May 2008 05:08:07 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06736-09; Fri, 30 May 2008 05:08:07 -0700 (PDT)
Received: from [*2???n?IPv6???1] (login005.redback.com [155.53.12.64]) by prattle.redback.com (Postfix) with ESMTP id 2C0C4B7BD21; Fri, 30 May 2008 05:08:07 -0700 (PDT)
In-Reply-To: <152196.89284.qm@web46314.mail.sp1.yahoo.com>
References: <152196.89284.qm@web46314.mail.sp1.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <89118FE2-973B-4D40-98A9-50F1B9255CFB@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Fri, 30 May 2008 08:08:06 -0400
To: Jennifer Christy <jenniferchristy56@yahoo.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
Cc: ospf@ietf.org
Subject: Re: [OSPF] Fw: Tye - 5 and Type -3 LSA issues
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0284148064=="
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Jennifer,
This is the wrong list for this question. I suggest you use the Zebra  
List:

    http://www.zebra.org/mailing.html

www.zebra.org contains other useful resources as well.

Having said that, you've definitely found an issue. The zebra daemon  
should not delete the route it just installed.

Good Luck,
Acee

On May 30, 2008, at 2:28 AM, Jennifer Christy wrote:

> Hi ,
>
> We are using zebra-0.93b in all the routers , installed it in three  
> linux boxes.
>
> As per the topology ( PPT attached ) , we have three routers A ,  
> B , C in our setup.
> Steps to reproduce the issue :
> 1. Router A is sending a Type 5 LSA route 172.25.25.0/24 ( External  
> Route ) via 11.11.11.11 to Router C.
> 2. Router B is sending a Type 3 LSA route 172.25.25.0/24 via  
> 12.12.12.12 to Router C.
>
> Let me explain the issue.
>
> Case 1 :
>
> 1. Enable OSPF in Router C on interface ( 12.12.12.10 )
> 2. Then Type - 3 LSA Route 172.25.25.0/24 via 12.12.12.12 from  
> Router B will be added to Router C.
> 3. Now Router C will have the route 172.25.25.0/24 via 12.12.12.12.  
> ( Added by Type -3 LSA )
> 4. Enable OSPF in Router C opn interface ( 11.11.11.10 )
> 5. Then Type - 5 LSA Route 172.25.25.0/24 from Router A is not  
> added to Router C , because while comparing the Type - 5 and Type -  
> 3 , its adding the best route as Type - 3 Route.
> 6. So the Router will have the Type - 3 route in routing table
>
> Case 2 :
>
> 1. Enable OSPF in Router C on interface ( 11.11.11.10 ).
> 2. Then Type - 5 LSA Route 172.25.25.0/24 via 11.11.11.11 from  
> Router A will be added to Router C.
> 3. Now Router C will have the route 172.25.25.0/24 via 11.11.11.11  
> ( Added by Type -5 LSA )
> 4. Enable OSPF in Router C on interface ( 12.12.12.10 )
> 5. Now Type - 3 ( 172.25.25.0/24 via 12.12.12.12 ) is the best  
> route when compared to Type -5 route
> ( 172.25.25.0/24 via 11.11.11.11 ) , so zebra is sending a message  
> to delete the Type -5 route.
> 6. And its sending a message to add the Type -3 route.So Type - 3  
> route is added into the Router C.
> 7. Here the issue starts , again zebra is sending a message to  
> delete the existing the Type - 3 route from the Router C.
> 8. So the Type - 3 route is deleted from the routing table , now  
> there is no routes for 172.25.25.0/24 in the routing table.
>
> This is the real issue , not happening when u enable type -3 first.
>
> We dont know this is an usual behaviour or its really an issue
> Please let us know the this is an already existing issue or if any  
> patch is there for this issue that would be fine.
>
> We want to know the root cause analysis of this issue .
> Its a long mail but hope you understand it.
> Please reply as soon as possible.
>
> Note :
> The issue is reproducible in latest version also ( zebra-0.95a )
> If you need any help in reproducing / understanding the issue ,  
> please let us know.
>
> Thanks in Advance ,
> Jenny
>
>
>
>
> <issue.ppt>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf