BGP - definition of Internal BGP (iBGP)
Internal BGP or iBGP is implemented between BGP routers that are in the same autonomous system. There is no specialized command to implement an iBGP peering. An iBGP peering is characterized by the fact that the AS argument in the neighbor
command is the same as the AS of the router
command. Note the following BGP configuration:
router bgp 2 bgp log-neighbor-changes neighbor 3.3.3.3 remote-as 2
This BGP router is in AS 2, and it is peering with a neighbor with a remote AS which is also 2. Thus, this is an iBGP peering. For more information about establishing a full mesh of iBGP peerings, take a look at BGP - iBGP full-mesh peering.
This is in contrast to eBGP peering. For a general overview of the difference between the two, take a look at BGP internal vs external.
Links
https://networklessons.com/bgp/internal-bgp-border-gateway-protocol-explained
Links to this page:
- BGP - BGP Algorithm within confederations
- BGP - Handling Multiple Communities on a Single Route
- BGP - Loop Prevention
- BGP - RRs vs confederations
- BGP - Synchronization Rule
- BGP - TCP Peering Session Process
- BGP - bgp redistribute-internal command
- BGP - definition of External BGP (eBGP)
- BGP - eBGP peerings
- BGP - next-hop-self vs update source
- BGP - oldest path attribute
- BGP - redistributing iBGP routes into an IGP
- BGP Cluster ID
- BGP Default local preference and its appearance in the BGP table
- BGP Maximum Prefix Feature
- BGP Originator ID
- BGP Route Reflector
- BGP dmzlink-bw feature
- BGP internal vs external
- BGP which address is used as the next hop
- BGP
- DMVPN - Phase 2 BGP peerings
- DMVPN - What is the best routing protocol to use
- MPLS - Disabling IPv4 address family in BGP for VPNv4
- MPLS 6PE uses two labels in the data plane
- MPLS Troubleshooting
- Network Design Achieving Redundancy with PE Devices
- Routing what if the administrative distance is the same