Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

BGP and OSPF in BayRS 13.10

8 views
Skip to first unread message

Callis Goodrich

unread,
Jul 2, 1999, 3:00:00 AM7/2/99
to

We are having some configuration problems with a Bay ASN router
configuration.
Specifically, we cannot get BGP-sourced routes injected into the OSPF
database. I have read and searched the ver. 12.20 documentation CDrom
on the OSPF and BGP chapters and configured the router accordingly,
but with no success.

A BGP accept policy was added which alllows the BGP routes to show up
in the
routing table, and the OSPF Global parameter is set for Boundary AS
router=TRUE. This particular ASN router (OS ver. 13.10) has 1
ethernet
interface running OSPF, 1 ethernet interface running BGP-4, and 1
serial ISDN
link running OSPF. The routing table shows the routes coming from BGP
and also
from OSPF, but the "bcc> show ospf lsdb" does not show any of the
BGP-sourced
routes in the OSPF database.

Do you have any suggestions on configuration items to check? Thanks
for your help and suggestions,
--
Mr. Callis G. Goodrich (mailto:good...@spawar.navy.mil)
Ph:619-553-3610; FAX: -6902; (DSN 553-)
Code D44206, US Navy SPAWAR Systems Center, San Diego

--
Mr. Callis G. Goodrich (mailto:good...@spawar.navy.mil)
Ph:619-553-3610; FAX: -6902; (DSN 553-)
Code D44206, US Navy SPAWAR Systems Center, San Diego

Callis Goodrich

unread,
Jul 2, 1999, 3:00:00 AM7/2/99
to

Callis Goodrich

unread,
Jul 2, 1999, 3:00:00 AM7/2/99
to

Callis Goodrich

unread,
Jul 2, 1999, 3:00:00 AM7/2/99
to

Patrick Wolfe

unread,
Jul 4, 1999, 3:00:00 AM7/4/99
to Callis Goodrich
Callis Goodrich wrote:
> Specifically, we cannot get BGP-sourced routes injected into the OSPF
> database. I have read and searched the ver. 12.20 documentation CDrom

You just need to add an OSPF accept policy with the "route source" and
"ext route source" fields set to BGP.

I cannot find this is any Bay manual either, but I think it's covered
in the Advanced IP class.

RFC1403 defines the standard for OSPF/BGP interaction (see
http://www.faqs.org/rfcs/rfc1403.html). Section 2.2 states that
the vendor SHOULD allow the administrator to control which BGP routes
are accepted by OSPF. Bay has chosen to implement this feature.

--

Patrick Wolfe (pwo...@mc.net)
Sr Engineer, Ameritech Cellular, Wide Area Network Transport

George Matey

unread,
Jul 5, 1999, 3:00:00 AM7/5/99
to
Patrick Wolfe wrote:
>
> Callis Goodrich wrote:
> > Specifically, we cannot get BGP-sourced routes injected into the OSPF
> > database. I have read and searched the ver. 12.20 documentation CDrom
>
> You just need to add an OSPF accept policy with the "route source" and
> "ext route source" fields set to BGP.

Once intra-as-routing is disabled, you use OSPF _announce_ policies to
regulate what is announced to the OSPF LSDB.

>
> I cannot find this is any Bay manual either, but I think it's covered
> in the Advanced IP class.
>
> RFC1403 defines the standard for OSPF/BGP interaction (see
> http://www.faqs.org/rfcs/rfc1403.html). Section 2.2 states that
> the vendor SHOULD allow the administrator to control which BGP routes
> are accepted by OSPF. Bay has chosen to implement this feature.

The updated RFC is 1745 which covers OSPF/BGP-4 interaction.
Not much has changed, but its good to reference the updated RFC.

--
George

0 new messages