10. Choose The Right Path BGP routing table entry for 68.156.159.0/24 Paths: (13 available, best #9, table Default-IP-Routing-Table) Advertised to non peer-group peers: 195.28.164.125 3333 6320 2828 29766 193.0.0.56 from 193.0.0.56 (193.0.0.56) Origin IGP, localpref 100, valid, external Community: 6320:21000 6320:21310 Last update: Sat Sep 12 00:54:11 2009 34225 1299 2828 29766 193.138.164.1 from 193.138.164.1 (193.138.164.1) Origin IGP, localpref 100, valid, external Community: 34225:1000 34225:1001 Last update: Fri Sep 11 12:51:30 2009 1930 20965 3549 2828 29766 193.136.5.1 from 193.136.5.1 (193.136.5.1) Origin IGP, localpref 100, valid, external Last update: Fri Sep 11 10:28:59 2009 42109 41965 41877 12389 8342 2828 29766 91.103.24.1 from 91.103.24.1 (91.103.24.1) Origin EGP, localpref 100, valid, external Last update: Fri Sep 11 09:55:24 2009
11.
12.
13. Well Known Mandatory Must be understood by all BGP speakers, and must be included in all update messages.
14. Well Known Discretionary Must be understood by all BGP speakers, and can be carried in updates, but are not required.
15. Optional Transitive May be understood by some BGP speakers, but not all. They need to be included in updates and advertised to all peers whether they understand them or not.
16. Optional Non-Transitive May be understood by some BGP speakers, but not all. If these attributes are not understood, they are dropped and not advertised to peers.
17.
18.
19.
20.
21.
22.
23.
24. Route Reflectors What if your AS looked like this? In iBGP, all speakers must have a neighbor relationship with each other to prevent routing loops. In a 10 router AS, you would have to configure 9 neighbors per router for a total of 45 neighbor relationships based on (n–(n–1))/2.
25. Route Reflectors With route reflectors, your AS could look like this. A lot fewer iBGP neighbor relationships would be required. RR – Route Reflector RRC – Route Reflector Client NCP – Non-Client Peer