BGP solution use cases https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-K...

Border Gateway Protocol (BGP) > BGP solution use cases next

BGP solution use cases

Solution 1 — Campus iBGP
Two use cases are presented. The first illustrates the extension of BGP into an enterprise routing
environment. The second case shows BGP connectivity in a remote site environments.

Solution 1 — Campus iBGP

Devices

A WAN Gateway Router

B Enterprise Core Router

C Enterprise Core Router (Campus Edge)

1 of 4 17/09/2021, 2:03 PM
BGP solution use cases https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-K...

D Campus Core Routing Switch

E Campus Distribution Routing Switch

F Edge Switch

In the figure above, multiple campus domains are segmented by using BGP in the enterprise core.
Traditionally, HP solutions have been used with devices E and F, facing the client or server network
edges. With the introduction of BGP functionality, it becomes possible to position solutions at locations B,
C, and D.

With proper filtering, a routing switch with 20,000 routes can be used in an iBGP deployment. A device at
location C represents the boundary between interior gateway protocol (IGP) domains, and the BGP core.
Functionality used on this device includes redistribution with route maps and the establishment of BGP
communities. Devices at location B require AS path filtering. All locations within the BGP AS require the
remaining “Foundation” features (Route Reflection, Refresh, Multihop, etc..)

Additional Autonomous Systems may be configured within a network, resembling the enterprise core
module as shown in the diagram. With larger enterprise customers, it is likely that an AS that is directly
adjacent to IGP campus modules will be the location for HP foundation BGP solutions. See Multiple
internal AS deployment with Campus iBGP solution.

Multiple internal AS deployment with Campus iBGP solution

The core routing switch (device C) can establish eBGP peering with the Enterprise Core. It is possible to
utilize the foundation Campus iBGP feature to satisfy some of these solutions.

2 of 4 17/09/2021, 2:03 PM
BGP solution use cases https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-K...

A Enterprise Core Router

B Enterprise Core Router (Campus Edge)

C Campus Core Routing Switch

D Campus Distribution Routing Switch (or Collapsed Core)

E Edge Switch

Solution 2 — Remote site iBGP

Solution 2 — Remote site iBGP

A Internet Gateway Router

B Remote Site Core Routing Switch

3 of 4 17/09/2021, 2:03 PM
BGP solution use cases https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-K...

C Remote Site Distribution Routing Switch

D Remote Site Edge Switches

You have the alternative of using static routes or BGP to connect to your service provider. For multi-
homing or policy control, you can choose to deploy BGP. This may be used for internet connectivity.
Foundation iBGP solutions do not carry full internet routing tables, so the diagram above requires that 1)
only default routes are taken from the internet and 2) multiple VRF instances do not exist at a single
physical remote site.

The deployment of device A may require additional traffic shaping and scalability features. If you prefer
extending BGP routing to devices B or C, you can use BGP functionality on a routing switch. In this
deployment model, the routing switch would be used for route redistribution and the marking of
communities.

prev up next

BGP show routines home Troubleshooting BGP

Copyright © 2015 Hewlett-Packard Development Company, L.P.

4 of 4 17/09/2021, 2:03 PM