User Tools

Site Tools


network_stuff:cisco:bgp_notes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
network_stuff:cisco:bgp_notes [2017/02/13 22:09] jotasandokunetwork_stuff:cisco:bgp_notes [2023/11/02 14:38] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +**OUTPUT OF BGP TABLE** (triplet and parenthesis meaning):\\
 **show ip bgp <prefix>**\\ **show ip bgp <prefix>**\\
 x.x.x.x from y.y.y.y (RID) \\ x.x.x.x from y.y.y.y (RID) \\
Line 4: Line 5:
   * y.y.y.y IP address of the router's interface who sent the update.   * y.y.y.y IP address of the router's interface who sent the update.
   * RID: router-id of the spoke sending the update   * RID: router-id of the spoke sending the update
 +Listing all routes and filtering on AS-PATH:
 +  show ip bgp regexp ^$ # test this w/ internal networks
  
 +----
 +**ASN PREPENDING**
 +  ip as-path access-list 1 permit ^$    # this indicates my own local routes
 +  route-map BGP100_SANTANDER_TO_BGP200_FR01_DMZR01_GRE permit 10
 +   match ip address prefix-list BGP100_SANTANDER_GRE_TO_ALL_SITES
 +   set as-path prepend 65103 65103 65103 65103 65103 # 
 +
 +
 +----
 +**PATH HUNTING**
 +  * Undesired phenomeda. Happens because BGP is, by definition, unaware of the topology
 +  * During convergence, BGP will ''hunt'' for another path andn happily advertises these paths to peers even though the path is through the peer itself. [[https://lostintransit.se/2023/10/09/path-hunting-in-bgp/|External Link]]
network_stuff/cisco/bgp_notes.1487023750.txt.gz · Last modified: (external edit)