E
Edge Switch
Figure 70: Solution 2 — Remote site iBGP
Solution 2 — Remote site iBGP
A
Internet Gateway Router
B
Remote Site Core Routing Switch
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.
Troubleshooting BGP
Debug log messages
1.
Logs per-peer BGP State Transitions.
2.
Logs per-peer arrivals of a new BGP update.
410
Aruba 3810 / 5400R Multicast and Routing Guide for ArubaOS-
Switch 16.08