netravnen/NetworkLabNotes
1
0
Fork 0
mirror of https://gitlab.com/netravnen/NetworkLabNotes.git synced 2024-11-26 19:27:57 +00:00
Code Releases Activity

Update section: BGP

Browse source
This commit is contained in:
netravnen 2017-08-19 20:01:18 +02:00
parent 092cb255ab
commit cf6ae6cc1c
1 changed files with 68 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

59
chapter/layer3.tex
View file

@ -17,27 +17,69 @@
The protocol of the internet used since 1994.\cite{wiki:Border_Gateway_Protocol}
Currently based upon \rfc{4271} with updates following in \rfc{6286} \rfc{6608}, \rfc{6793}, \rfc{7606}, \rfc{7607}, \rfc{7705}.
\begin{itemize}
\item \itemhead{Properties}
\subsection{Properties}
\begin{itemize}
\item Uses tcp/179 as \gls{dst} port
\item Sends keep-alive message every 1 minute
\item Keep-alive message is 19 byte
\item Keep-alive message is 19 byte long
\end{itemize}
\item \itemhead{Route exchange}
Be ware if sessions are terminated immediately upon trying to establish connection. Try debugging following points.
\begin{itemize}
\item \itemhead{Route-maps mechanism}
\item tcp/179 is not open,
\item random port 1023> is not open,
\item incorrect peer-ip,
\item incorrect peer-as.
\end{itemize}
\subsection{Route exchange}
Exchanging routes between routers is a reliant and tolerant manner is \glspl{bgp} 1-advantage over \gls{ospf}/\gls{isis}/\gls{rip}/\gls{eigrp}.
The sheer tuning and control mechanisms \gls{bgp} can offer is simply astounding. Route-maps is the key and access-lists just one option.
\subsubsection[Route-maps]{Route-maps mechanism}
Route-maps is used to target a select set of routes and either modify/add/remove attributes attached to the select route-set.
\begin{itemize}
\item Routes can be aggregated between \glspl{as}.
\item Properties can be changed on the fly by mathing
\item Properties can be changed on the fly by matching
\begin{enumerate}[label={\alph*)}]
\item \Gls{bgp} communities,
\item \Gls{ip} prefix,
\item \Gls{bgp} as-path,
\end{enumerate}
\end{itemize}
\end{itemize}
\item \itemhead{States}
An simple example of using route-maps is
\begin{cisco}
ip prefix-list 1 permit 172.16.0.0/16
ip prefix-list 2 permit 192.168.1.0/24
!
route-map RED permit 10
match ip address prefix-list 1
set ip next hop 10.1.1.1
continue 20 ! Continues to apply rules normally only
! applied to prefix-list 2. To apply to
! prefix-list 1, too.
! Any attributes set in '20' will
! override any set during '10'.
route-map RED permit 20
match ip address prefix-list 2
set ip next hop 10.2.2.2 ! Last rule overrides previous rules from
! previous '10' rule-set.
\end{cisco}
When rules from a rule-set is chained together as shown above. The last rule will override all previous set values regarding the attribute being applied. In this case \texttt{next-hop} from 'permit 10' is overridden in 'permit 20'.
\subsection[States]{BGP States}
The states is the way \gls{bgp} handles peer/neighbor connection establishing. The \underline{playbook} so to speak.
\begin{enumerate}
\item Idle: \gls{bgp} while initializing refuses all incoming connections. Will initiate \gls{tcp} connection to peer.
\item Connect: Waits for \gls{tcp} connection. If \gls{tcp} is established goes to state OpenSent. If \gls{tcp} is \textit{un}successful ConnectRetry timer is started and then goes to Active state.
@ -46,7 +88,6 @@ Currently based upon \rfc{4271} with updates following in \rfc{6286} \rfc{6608},
\item OpenConfirm: Nodes exchange keepalive \glspl{msg} and goes to Established state if successful.
\item Established: Nodes can now exchange KeepAlive, Updates, and Notification \glspl{msg}.
\end{enumerate}
\end{itemize}
\subsection[iBGP]{Internal Border Gateway Protocol}