BGP in Cisco ACI Explained: L3Outs, MP-BGP and Route Reflectors

Short answer: Cisco ACI uses BGP in two distinct ways: external BGP sessions on border leaf switches exchange routes with routers through an L3Out, while internal MP-BGP and spine route reflectors distribute eligible external routes to tenant leaves. This is not simply a conventional BGP fabric where every leaf peers with every other leaf; policy and tenant scope determine which routes are imported and advertised.[1][2]

X Follow @ipexptobe

BGP EVPN Explained: VXLAN Routes, Route Types and Troubleshooting

Short answer: BGP EVPN is a control-plane protocol that advertises Ethernet and IP reachability between VXLAN tunnel endpoints. It lets a fabric distribute endpoint, subnet and multihoming information without relying on data-plane flooding for every learning event. EVPN carries reachability; VXLAN encapsulates the user traffic.

X Follow @ipexptobe

BGP Filtering Explained: Prefix Lists, AS-Path Filters and Maximum-Prefix

Short answer: BGP filtering is a set of explicit import and export policies that limits which routes a neighbor can send you and which routes you advertise. Use prefix filters for exact route authorization, AS-path filters for path-pattern checks, and maximum-prefix limits as a safety guard—not as a substitute for either filter.[1][2]

X Follow @ipexptobe

How to Control Inbound BGP Traffic: AS_PATH Prepending, MED and Provider Communities

Short answer: You can influence which of your links a remote AS uses to send traffic toward you, but you cannot dictate its routing policy. AS_PATH prepending, MED, provider communities and selective prefix advertisement are signals; the neighboring network makes the final decision.[1][4]

X Follow @ipexptobe

BGP Best-Path Selection Explained: How Routers Choose a Route

Short answer: BGP best-path selection is the router’s policy-driven comparison of eligible routes to the same prefix. There is no single universal vendor order: attributes, tie-breakers, and multipath behavior vary by implementation.

X Follow @ipexptobe

BGP Route Reflection Explained: ORIGINATOR_ID, CLUSTER_LIST and Loop Prevention

Short answer: BGP route reflectors let an iBGP speaker advertise routes learned from one iBGP peer to other iBGP peers, avoiding a full mesh. ORIGINATOR_ID and CLUSTER_LIST prevent reflected routes from looping back through their origin or a reflector cluster.[1]

X Follow @ipexptobe

BGP Route Distinguisher (RD) vs Route Target (RT): What They Do and How to Troubleshoot

Short answer: A BGP Route Distinguisher (RD) makes otherwise identical VPN routes unique; a Route Target (RT) is the extended-community policy tag that controls which VRFs import or export those routes. RD answers “which route is this?”; RT answers “where should it go?” [1][2]

X Follow @ipexptobe

BGP AS_PATH Explained: Loop Prevention, Path Selection and Traffic Engineering

Short answer: AS_PATH is the ordered record of autonomous systems a BGP route has traversed. It helps detect routing loops and contributes to path selection. Prepending can influence how some remote networks choose an inbound path, but it is not a guarantee.

X Follow @ipexptobe

Weekly BGP Table Watch: IPv4, IPv6 and ASN Changes — 2026-10-26

The global BGP table keeps moving every day. This weekly BGP Table Watch snapshot tracks IPv4 prefixes, IPv6 prefixes, visible ASNs and the largest routing-table changes reported during the last week.

The goal is not to alarm on every change. BGP is noisy by design. The goal is to build a simple operational habit: watch the size of the routing table, notice large origin-AS changes, and keep an eye on where new ASNs and route withdrawals appear.

X Follow @ipexptobe

BGP LOCAL_PREF Explained: Outbound Traffic Engineering and Configuration

Short answer: BGP LOCAL_PREF tells routers inside one autonomous system which exit path to prefer for outbound traffic. A higher value wins among otherwise eligible paths, and the value is distributed to internal BGP peers—not to ordinary external peers.^[1]

X Follow @ipexptobe

BGP NEXT_HOP Explained: Next-Hop Reachability, next-hop-self and Troubleshooting

Short answer: BGP NEXT_HOP is the IP address a router recursively resolves to determine the forwarding path for a destination. A route can be present in BGP yet unusable if that address is unreachable. In iBGP, next-hop-self is commonly used to make the advertising router the reachable next hop.

X Follow @ipexptobe

BGP Extended Communities Explained: Route Targets, EVPN and Policy Signaling

Short answer: BGP Extended Communities are structured route tags carried with BGP paths. They extend standard communities with typed values, enabling policy signals such as VPN route targets and EVPN-specific information. They do not themselves forward packets or force a remote network to accept a route.

X Follow @ipexptobe

Spine-Leaf and Clos Topology Explained for Network Engineers

A useful data center interview question is: What is a spine-leaf topology, and why use it instead of a traditional switching hierarchy? Start with the wiring and a packet path, not a list of protocols.

Short answer: spine-leaf is a two-tier fabric in which every leaf connects to every spine; endpoints connect at the leaves, while spines provide transit between them.^[2]

X Follow @ipexptobe

BGP Large Communities Explained: 4-Byte ASN Policy Tags and Routing Examples

Short answer: A BGP Large Community is a transitive route tag written as Global-Administrator:Local-Data-1:Local-Data-2. Its three 32-bit fields provide a practical namespace for policy signaling, including four-byte ASNs; the tag itself does not change forwarding unless a router or provider policy acts on it.^[4]

X Follow @ipexptobe

BGP Communities Explained: Policy Tags, no-export and Blackhole Routing

Short answer: A BGP community is a 32-bit tag attached to a route so routers and networks can apply policy consistently. Communities do not change forwarding by themselves: a route policy must match the tag and take an action such as setting local preference, controlling advertisement, or requesting a provider service.[1][2]

X Follow @ipexptobe

BGP ORIGIN Attribute Explained: IGP, EGP, Incomplete and Best-Path Selection

Short answer: BGP ORIGIN is a well-known mandatory attribute that records how a route entered BGP: IGP (i), EGP (e, historical), or INCOMPLETE (?). It is a late tie-breaker in many best-path implementations—not a measure of route quality or a traffic-engineering knob by itself.^[1]

X Follow @ipexptobe

BGP NEXT_HOP Explained: Route Reachability, next-hop-self and Troubleshooting

Short answer: BGP NEXT_HOP identifies the address a router must resolve to forward traffic. A route may appear in BGP but be unusable if its next hop is unreachable; iBGP often uses next-hop-self. ^[1]

NEXT_HOP provides a forwarding target; it does not select the complete end-to-end path.

X Follow @ipexptobe

Weekly BGP Table Watch: IPv4, IPv6 and ASN Changes — 2026-10-19

The global BGP table keeps moving every day. This weekly BGP Table Watch snapshot tracks IPv4 prefixes, IPv6 prefixes, visible ASNs and the largest routing-table changes reported during the last week.

The goal is not to alarm on every change. BGP is noisy by design. The goal is to build a simple operational habit: watch the size of the routing table, notice large origin-AS changes, and keep an eye on where new ASNs and route withdrawals appear.

X Follow @ipexptobe