Re: Clarification on Cisco OSPF network types

Sina Mirtorabi <sina@CISCO.COM> Wed, 25 June 2003 01:38 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02097 for <ospf-archive@LISTS.IETF.ORG>; Tue, 24 Jun 2003 21:38:55 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <19.00A2F69E@cherry.ease.lsoft.com>; Tue, 24 Jun 2003 21:16:09 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 46522281 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 24 Jun 2003 21:16:06 -0400
Received: from 171.68.227.75 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 24 Jun 2003 21:16:05 -0400
Received: from smirtoraw2k03 (sjc-vpn3-459.cisco.com [10.21.65.203]) by fire.cisco.com (8.11.7+Sun/8.8.8) with ESMTP id h5P1FxT09017 for <OSPF@PEACH.EASE.LSOFT.COM>; Tue, 24 Jun 2003 18:15:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
Message-ID: <000301c33ab7$59294950$f2ce7243@amer.cisco.com>
Date: Tue, 24 Jun 2003 18:15:59 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Sina Mirtorabi <sina@CISCO.COM>
Subject: Re: Clarification on Cisco OSPF network types
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <sef96c60.089@aapt-gwia2.aapt.com.au>
Precedence: list
Content-Transfer-Encoding: 7bit

Paresh,

->Hi all,
->
->Appreciate if someone could clarify how the various Cisco
->OSPF modes for NBMA networks work.
->
->The command "ip ospf network {broadcast | non-broadcast |
->{point-to-multipoint [non-broadcast] | point-to-point}}"
->allows you to set an OSPF network mode.
->
->I would like to know:
->1.  How OSPF packets are transmitted on each of these modes -
->unicast, multicast etc ?


network \packet type |type 1 | type 2| type 3| type 4| type 5
---------------------|-------|-------|-------|-------|------
p2p                  |  M    |   M   |   M   |   M   |  M
---------------------|-------|-------|-------|-------|------
p2mp non-broadcast   |  U    |   U   |   U   |   U   |  U
---------------------|-------|-------|-------|-------|------
p2mp broadcast       |  M    |   U   |   U   |   U   |  U
---------------------|-------|-------|-------|-------|------
NBMA                 |  U    |   U   |   U   |   U   |  U
---------------------|-------|-------|-------|-------|------
Broadcast            |  M    |   U   |   U   |M /MD *|  M/MD *


U  : unicast ( neighbor IP address )
M  : Multicast AllSPFRouters (224.0.0.5)
MD : Multicast AllDRouters ( 224.0.0.4 )

* For broadcast network, if Interface FSM is DR /BDR type 4 & 5 are sent
to M ( 224.0.0.5) otherwise it is sent to MD ( 224.0.0.4 )


->2.  How are neighbors discovered ?

When the packet ( actually Hello ) is sent to unicast IP address a
manual configuration is required (except for VL which is found
dynamically once there is an intra-area path to the other end-point )

If Hello is sent to Multicast AllSPFRouters address and the link layer
has the broadcast capability ( or packet can be replicated to sent to
different VC ) then the neighbor discovery is dynamic

Sina

->
->All responses appreciated.
->
->Regards,
->Paresh.
->