Configuring Bgp - HP 7102dl - ProCurve Secure Router Configuration Manual

N o t e
6. Redistribute routes discovered by the EGP into OSPF. Also, redistribute
connected routes because not all interfaces are running OSPF:
ProCurve(config-rip)# redistribute rip
ProCurve(config-rip)# redistribute connected
7. You could alternatively generate a default route for external traffic:
ProCurve(config-ospf)# default-information-originate always
Or you could configure a route summary for the external traffic:
ProCurve(config-ospf)# summary-address 10.200.0.0 255.255.0.0

Configuring BGP

BGP is an external protocol: it allows different autonomous systems to
exchange routes. BGP is the protocol most ISPs use, and it was designed to
allow diverse, sometimes competitive organizations to communicate:
BGP can filter both the routes it receives and those that it sends according
to bit length, thereby minimizing the number of routes exchanged.
BGP uses policies to determine best routes rather than per-hop counts,
like RIP does, or link states, like OSPF does. Autonomous systems can set
their own policy.
BGP routers communicate only with manually configured neighbors.
You can configure different policies for route exchange with different
neighbors.
BGP runs in External BGP (eBGP), which is the protocol used to communicate
between two autonomous systems, and Internal BGP (iBGP), which is the
protocol that the AS uses to synchronize its own routing tables.
Do not confuse eBGP with EGP, a nearly obsolete protocol once used on the
Internet. Also, do no confuse iBGP with an IGP such as OSPF. ISPs use iBGP
to distribute BGP routes between routers within an AS. However, ISPs usually
still need to run an IGP to generate routes for traffic within the AS.
On the ProCurve Secure Router, eBGP is intended to allow a private network
to send and receive routes from remote sites through the Internet. The private
network itself will run an IGP such as RIP or OSPF.
IP Routing—Configuring RIP, OSPF, BGP, and PBR
Configuring BGP
15-67