Chapter 16: Dynamic Routing Protocols
STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide
© 2016 ARRIS Enterprises LLC. All Rights Reserved. 460
Some MSOs use BGP as the protocol of choice for advertising C4/c CMTS CAM-side IP prefixes. In such an application iBGP
is used throughout their regional networks with a full mesh of interconnected peering routers.
The C4/c CMTS in this environment is required to run iBGP peering sessions with various routers in a particular Regional
Area Network (RAN). iBGP peers typically communicate using loopback interfaces.
Loopback interfaces are not assigned to any particular interface; therefore, a particular BGP session is not interrupted by
an interface failure. Interface IP addresses may also be changed without impacting BGP sessions.
Typically, iBGP networks require the following:
BGP Autonomous System: A routing domain in which all routers are associated with the same AS. iBGP peering
sessions occur within an AS.
BGP Route Reflector: A route reflector supports the readvertisement of routes between iBGP peers.
BGP Route Reflector Client: Depends on a route reflector to advertise its routes to the entire BGP AS
Since iBGP full mesh topologies scale at a rate of N(N-1)/2, two methods have been developed to reduce the number of
BGP peering sessions:
AS confederations
Route reflectors