[c-nsp] Multi Area OSPF

Heath Jones hj1980 at gmail.com
Wed Sep 15 10:57:26 EDT 2010


Nick,

As soon as you redistribute from another protocol (connected, static
included) into OSPF, that router then acts as an ASBR. According to both
routers, that area will contain an ASBR and can therefore not be a stub.


Cheers




On 15 September 2010 11:32, Nick Ryce <Nick.Ryce at lumison.net> wrote:

> Hi Guys,
>
> Im having some issues with setting up multi area ospf between a j 2320 and
> a cisco 1812.  I have a funny feeling the issues will be user related.
>
>
> The j2320 is acting as an abr with backbone area 0.0.0.0 and stub area
> 0.0.0.1 and advertises a default route into the stub area.
>
> The 1812 is set as a stub with no other routing protocols being used.  When
> I use the redistribute static or redistribute connected commands it advises
> these cant be used as the router is an asbr.  The router is only running 1
> ospf process for the stub area so I am not sure why this is occurring.
>
> I add the network x.x.x.x y.y.y.y area 0.0.0.1 command and can start seeing
> a default route being sent by the juniper which is great but the juniper
> cannot see anything being sent from the router.  I can get around this by
> setting the network in the ospf process to 0.0.0.0 255.255.255.255 but is
> this the correct way to do this as it would mean that any interface on the
> router will be sending out ospf requests which I do not want to occur as I
> want to be specific.
>
> Any ideas?
>
> Nick
>
> ________________________________
> --
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the sender. Any
> offers or quotation of service are subject to formal specification.
> Errors and omissions excepted. Please note that any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of Lumison.
> Finally, the recipient should check this email and any attachments for the
> presence of viruses. Lumison accept no liability for any
> damage caused by any virus transmitted by this email.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>


More information about the cisco-nsp mailing list