Public AS nubers 1 to 64511

Private AS numbers 64512 o 65535

Igp operates with in an AS but bgp beween Ass.
Between

Isps
Isp and enterprise

Bgp gives reliability, scalability and control but not speed.

It is a Path-vector; in terms of which ASs they pass through.
BGP attributes allow granularity in path selection.
When update about a network leaves an AS, t
eBGP & iBGP are neighbour relationship types.
IBGP:
Within an AS
Used when more than one internet edge.
As-path is not prepend.
But local preference attribute is sent to ibgp but not to an ebgp
Route learn from an ibgp will not advertise back to another ibgp by default.
Next hop will not change.
iBGP peers dont need to directly connect.
Admin distance is 200
eBGP:
between Ass
along with routes as-path attribute is also updated between ebgp peers.
By default ttl is set to 1, that means it assumes directly connected but not in the case of ibgp
is 255.
Neighbour relationship:
Igp reachability must be established beteween peers.
Then only tcp session will be formed at port 179.
Syn packet goint to the port of 179. Reply come from same port, going to high port number.
Both peers attempt tcp connection same time highest router id contining peer will start
initiation.
Debugging neighbour forming relationships.

R1(config)#access-list 100 permit tcp any host 155.1.0.2

R1(config)#access-list 100 permit tcp host 155.1.0.2 any
R1(config)#do debug ip packet detail 100

Extended acl:
Access-list
[ name/num ]
[ permit/deny/remark ]
[ tcp/udp/protocol/protocol no]
[ any/source/host/ipadd/object group ]
[ destination host/ipadd/object group/any ]

There are two ways to configure when peering EBGP:

Case 1 R1 and R2 are peering with a physical interface.
Case 2 R1 and R2 are indirectly connected or they are peering with each other's loopback
interfaces.

ebgp-multihop 5 means that neighbor 131.108.10.2 can be only five hops away from R1, and the Time To
Live (TTL) field in the IP header is set to 5.
update-source Loopback0 means that all BGP updates are sourced from the Loopback 0 address of R1. R2
uses 131.108.10.1 as the next-hop address for all routes learned through R1.

The BGP Nighbour States

> Idle - Indicates the router is currently not attempting any connection establishments.
> Connect - Indicates the router is waiting for the TCP connection to be completed. If successful an OPEN message
is sent.
> Active - Indicates the router didn't receive agreement on parameters of establishment and is trying to initiate
TCP.
> OpenSent - After the TCP session is setup, the router waits for an OPEN message to confirm all parameters.
- If no errors a BGP keepalive message is sent.
> OpenConfirm - Indicates the router is waiting for a keepalive or notification message.
- If a keepalive is received the state changes to Established, else changes to Idle
> Established - Indicates peering to a neighbor is established; routing begins.

BGP Conditional Advertisement

This feature can be used in a network that is multihomed to two ISPs. In this lab, it enables the
100.100.100.0/30 prefix inside of AS3 to be advertised only to AS2, under the condition that AS2 has connection
to its transit provider (R4). If not, we will advertise this prefix to the backup service provider (R1). The idea is
that it will force external traffic that is destined to this prefix to go via the primary ISP. Only if the path via primary
ISP fails, then external users will start using the backup ISP to reach it. Lets take a look at an example.

BGP conditional route injection

Provides a method to originate a prefix into the BGP routing table without the corresponding match in the IGP
table.
- Only prefixes that are equal to or more specific than the original prefix may be injected.
- This is used to improve the accuracy of route aggregation, by conditionally injecting or replacing less specific
prefixes with more specific prefixes.

eBGP loop prevention

> A router will not accept a prefix if the locally-configured ASN is listed in the received as-path
list.
> This default behavior can be changed with the "neighbor allowas-in" command.

iBGP loop prevention:

>Split-horizon rule: in ibgp, route reflector, confederation and full mesh also.

Bgp backdoor:
> When a router learns a prefix via two paths, one via eBGP and the other via IGP, the eBGP route based on the
AD(20) will be chosen as the best.
> This might not always be the required best route.
> The AD of that one route could be changed or the BGP backdoor feature could be used, which makes the IGP
route the preferred route.

Next hop processing:

When a packet is passed between iBGP peers, NO next-hop processing is done,
- For iBGP, the protocol states that the next hop that eBGP advertises should be carried into iBGP.
- next-hop-self neighbor command to force the router to advertise itself, rather than the external peer,
as the next hoP.
- When a packet is passed between eBGP peers, the next-hop field is modified to the IP address of the
sending eBGP router's interface.
-For eBGP, the next hop is always the IP address of the neighbor that the neighbor command specifies.
- If the receiving BGP router is in the same subnet as the current next-hop address, the next-hop field
remains unchanged to optimize packet forwarding (typically seen on
multi-access networks).
- Be careful with next-hop processing on NBMA networks. The next-hop must be reachable. Rather use a subinterface interface on a different subnet or alternatively change
the next-hop processing.
- Next-hop processing could be changed in one of two ways:
> As mentioned above with the "neighbor next-hop-self" command.
> Or with a route-map by setting the "ip next-hop".

BGP Synchronization Rule:

> If an autonomous system is a transit autonomous system and synchronization is enabled, BGP will not advertise
a route until that router has learned that external route via its IGP.
Community Attribute
> The community attribute is an optional transitive attribute.
> BGP communities are a means of tagging routes to ensure consistent filtering or route selection policy in
incoming/outgoing routing updates, or with redistribution.
> By default, communities are stripped in outgoing BGP updates. Sending them must be manually enabled.
> Routers that do not support communities will pass them along unchanged.

Routes can be originated into BGP in the following ways:

>
>
>
>
>

Using the "network" statement.

By doing redistribution from another protocol.
By originating a default route.
By using the "aggregate-address" command.
By using BGP conditional route injection.

Route dampening:
Designed to reduce router processing load caused by unstable routes.
- Each time an eBGP route flaps, it gets 1000 penalty points (this cannot be configured or changed).
- iBGP routes are not dampened.
- Benefits of using Peer-Groups
> Reduce the amount of system resources (CPU and memory) necessary in the update generation.
> Mostly used to simplify large repeating BGP configurations.

The main purpose of route reflectors and confederations is not to prevent loops but to avoid the need to
have all iBGP routers fully meshed (fully peered in BGP).
The route reflector design is usually preferred to confederations. It is a relatively lightweight solution that
scales nicely. Confederations are usable only for huge autonomous systems where you can afford to split
them into several sub-ASes. Note that each sub-AS in a confederation needs to have its internal iBGP
peers either fully meshed, or use route reflection internally, returning back to the route reflector concept. As
you can see, the confederations are not much of an advantage for small ASes having a few BGP routers.

BGP neighbor TS:

1. check the configuration both sidesl
a. AS number, timers, neighbor ip address, multiphop command, update source
loop back.
2. Ping the Peer ip address(show ip route)
3. Check the tcp port 179 is opend or not
4. If neighbor is flapping check mtu on both sides.