Network Engineering Stack Exchange is a question and answer site for network engineers. It only takes a minute to sign up.
Sign up to join this community
Let us consider the scenario where two ASN's are announcing the same IP space however one has a summary route.
ASN 123: 200.13.0.0/17
ASN 234: 200.13.115.0/23
Will traffic prefer to go to ASN 234, as it is the most specific route? Also, would anything stop either ASN from using a redistributed static route to handle the traffic after it is inside of their ASN?
The basis of routing is that the more specific match is the primary criteria. So the /23 prefix will be preferred.
eBGP is used to exchange routes between AS. How routing is performed inside an AS is up to the owner of the AS, he can do whatever he wants, even static routing (or even iBGP).
More specific match is always going to be selected, so all the traffic will go to 234. You can't control how other ASNs are going to do their routing. If they decide to announce more specific static via redistribution then all the traffic will use it. However in normal situation ISP is not going to use static routes for subnet which is not part of their address space.
BGP uses TCP as the transport protocol, on port 179. Two BGP routers form a TCP connection between one another. These routers are peer routers. The peer routers exchange messages to open and confirm the connection parameters. BGP routers exchange network reachability information. This information is mainly an indication of the full paths that a route must take in order to reach the destination network. The paths are BGP AS numbers. This information helps in the construction of a graph of ASs that are loop-free. The graph also shows where to apply routing policies in order to enforce some restrictions on the routing behavior. Any two routers that form a TCP connection in order to exchange BGP routing information are "peers" or "neighbors". BGP peers initially exchange the full BGP routing tables. After this exchange, the peers send incremental updates as the routing table changes. BGP keeps a version number of the BGP table. The version number is the same for all the BGP peers. The version number changes whenever BGP updates the table with routing information changes. The send of keepalive packets ensures that the connection between the BGP peers is alive. Notification packets go out in response to errors or special conditions.
you should read this it might help.
http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/26634-bgp-toc.html
