BGP intro
- BGP used TCP port 179
- 3 way handshake between ngrs
- Public AS : 1 - 64495
- Private AS: 65512 - 65534

eBGP requirements:
1) ASN should be correct
2) peer must be reachable by IGP. Default route won't work
3) BGP router ID can't be same
4) MD5 authentication must pass. password is set under TCP option field
5) TCP connection
6) TTL = 1

eBGP
update source and ebgp multihop:
- when we say our nbr as 1.1.1.2, router is going to check routing table for destination and outgoing interface for source IP .

iBGP:
1) TTL = 255
- if iBGP is not full mesh.. router which is not running iBGP can blackhole the traffic as that router doesn't know how to reach destination

BGP state machine

all bgp msg are carried in IP/TCP header.

stage 1: establish BGP nbrship

1) Idle: admin down or couldn't find the route in routing table for BGP peer.
2) connect state: BGP process has detected an TCP connection request and BGP process is waiting for TCP to complete
3) Active: BGP process has initiated a outbound TCP connection request and is waiting for the 3-way handshake to complete

some issues:
peer doesn't have BGP configured or firewall blocking 179.
4) openSent: TCP is done. sent open to nbr. waiting nbgr to send open. send details like BGP remote as, BGP capabilities.
- BGP capabilities:
1) route refresh
2) support VPNv4
3) or support ipv4 and ipv6
4)Outbound Route Filtering Capability
see full list here:
http://www.iana.org/assignments/capability-codes/capability-codes.xhtml

5) openconfirm: open msg send and received. keepalive has been exchanged
6) established: BGP has established

7) now lets start exchanging update
8) now lets check for best routes

BGP messages type:
all msgs are send over TCP/IP
1. open: type 1.
2. update: type 2
3. keepalive: type 4
4. notification : type 3 - tier down nbgrship due to xyz reason

BGP AS path
1) AS sequence
2) AS SET : 4 5 {1 2 3} - during summarization

Inject route into BGP
1) Network command:
- check for routing table
- check for non BGP routes in routing table
- convert route into BGP table
- advertise to neighbor

#network subnet mask sub-mask
if no mask: classful network mask

2) redistribute command:
- no need to give seed metric
-

3)

IBGP route update rules:
1) only advertise the best route in any BGP update.
2) do not advertise iBGP learned routes iBGP peers - so we need full mesh bgp ngbrship. prevent iBGP loops
3) rule of synchronization:
-do not consider an iBGP-learned route as "best" unless the exact prefix was learned via an IGP and is currently in the routing table
- synchronization is off by default
- synchronizaton was designed in case of we have a router/routers between 2 iBGP peers which is not running iBGP.
3) iBGP gives next hop of eBGP neighbor unless next-hop-self command is used
4) next hop should reachable else route will not be added in routing table. IGP routing table should have next hop and should be reachable

RIB failure reasons:
-RIB failure: unable to put route in routing table
reasons:
1) route has been learned from other routing table with lower AD
2) memory failure .. in case of full routing table learned.
3) we configured size of routing table
4) running vrf and configured routing table limit

R1#show ip bgp 100.100.100.0
BGP routing table entry for 100.100.100.0/28, version 56
Paths: (1 available, no best path)
Flag: 0x820
Not advertised to any peer
300
1.1.1.33 (inaccessible) from 1.1.1.2 (1.1.1.2)
Origin incomplete, metric 0, localpref 100, valid, internal

5)

BGP Peer groups
-all neighbor in peer group needs to share same outbound policy
- all neighbor in a peer group can have different inbound policy
- updates are generated once for a peer goup

router bgp 300
neighbor peer-group
neighbor remote-as 300
neighbor reoutemap <> out

neighbor 2.2.2.2 peer-group
neighbor 2.2.2.2 filter-list <> in

BGP Filtering
- can be done at any router
- after filtering is applied, BGP ngbrship must be reset or cleared for the filter to take affect
- BGP filtering is done per neighbor
1) Filter list
router bgp 123
neighbor x.x.xx filter-list 2 in/out
!
ip as-path access-list 2
filter list uses as-path access-list

- used to filter AS path

2) route-map
3) prefix-list
4) distribute-list
-

BGP redistribution(study again)
Add "bgp redistribute-internal" to your bgp process. By default, iBGP doesn't redistribute into an IGP. The reason for this is simply the amount of routes that a bgp router can receive could overload an igp very easily, so you would definitely want to filter routes out when doing this.

BGP best path algorithm

“We Love Oranges AS Oranges Mean Pure Refreshment”

W Weight (Highest) L LOCAL_PREF (Highest) O Originate (local -0.0.0.0) AS AS_PATH (shortest) O ORIGIN Code (IGP > EGP > Incomplete) M MED (lowest) P Paths (External > Internal, eBGP>iBGP) R RID (lowest)

Mandatory path attributes:
next-hop
AS-path
origin code

optional path attributes:
1) transitive optional path attribute
AS-path prepend

2)non transitive optional path attribute:
local preference

steps:
1) Next hop: it should be reachable

2) weight: bigger is better
- cisco proprietary
- locally significant to a router
- influence outbound traffic and applied inbound
- default is 0 for learned routes and 32768 for locally injected routes
- BGP only sends best path to its neighbor

a) Per prefix influence
R4#show ip bgp
BGP table version is 10, local router ID is 1.1.1.4
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*>i100.100.100.0/28 1.3.4.3 0 100 0 300 ?
* 1.3.4.1 0 100 300 ?

R4(config)#ip prefix-list INE permit 100.100.100.0/28
R4(config)#route-map INE permit 10
R4(config-route-map)#match ip address prefix-list INE
R4(config-route-map)#set weight 100
R4(config-router)#neighbor 1.3.4.1 route-map INE in
R4#show ip bgp
BGP table version is 4, local router ID is 1.1.1.4
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*> 100.100.100.0/28 1.3.4.1 100 100 300 ?
* i 1.3.4.3 0 100 0 300 ?

b) per neighbor

3) local preference: bigger is better
- default is 100
- advertised to all iBGP peer
- not advertised to eBGP peer
- influence routes in a BGP AS
- applied inbound to an external nbr

4) locally originated routes: next hop 0.0.0.0

5) AS-Path length
-

6) origin: i>e>?
- i : by IGP routing protocol and by using Network command
- e : by EGP routing protocol
- ? : by redistribute command

igp > egp > ?

7) MED :smaller is better
- same like AS path prepend. influence inbound traffic.
- non-transitive
- travels to only 1 AS. propagate to one neighboring AS
- default 0
- in route-map "set metric"
- MED is only compared when prefix is received from same AS but multiple source. if prefix is received from multiple AS - MED is not compared. we can change it using command:
"bgp always compare med"
-

8) Nbgr: eBGP >iBGP
9) IGP metric to next hop : smaller is preferred

- Weight, local preference and AS path can be used to change outbound traffic
- As path and MED can be used for inbound traffic

10) router id:

BGP maximum path
-

BGP community:
- Standard community is 4 byte number
- AA:NN ( usually AA is BGP AS number and NN is locally significant value. eg 11179:143)
-
Well known BGP community:
- No export: dont advertise to BGP peers
- No advertise: do not advertise to any peer
- Local as: do not advertise to confederation eBGP peers

mBGP
- address family supporting ipv4 nd ipv6
- BGP will have ipv4 and ipv6 details
-

Route-reflectors
- iBGP learned routes are not send to iBGP peers - this is to avoid loops
- RR can reflect received iBGP updates to other iiBGP peer - if i am RR. to one more hop
-
Terminology:
-RR- a router will can Reflect IBGP routes to other iBGP peers
-client: RR client. RR will send iBGP updates to clients. we need to configure which neighbors will be RR clients in RR BGP config.
-cluster - one or more RR and clients is a single cluster
-not client - any neighbor in RR which is not configured as client

Loop Avoidance in RR:
- We can have loop RR1-->RR2-->RR3. RR3-->RR1. this can cause loop
- RRs will add below attributes in the routes while advetising to clients:

1) Originator-ID: created by RR. carried the RID of the originator of the route in the local AS.
route can be originated by 2 ways:
a) learned from eBGP peer
b) redistribute command

2) Cluster_ID list:
- RR will add cluster-ID. cluste_ID is same router-ID by default.
- only RRs will add cluster-ID
- if RR sees its own cluster-ID in a cluster list - its a loop and it will drop it.
- change BGP cluster_ID:
#bgp cluster-id x.x.x.x

- non client learned prefix wont be advertised to non-client peers
- RR can't change attributes like local preference, next hop, weight etc. its just a reflector.

	Erstellt von inga pinga vor mehr als 8 Jahre

Notiz am BGP, erstellt von inga pinga am 26/03/2016.