P. 1
Gdnw Jncis-fwv Study Guide

Gdnw Jncis-fwv Study Guide

|Views: 4,560|Likes:
Published by Gavrilo
Hi,
Attached is a Juniper JNCIS-FWV Study Guide for exam JN0-532 in PDF document format. It is similar to the Jason Ha document some of you may remember from the past. However, my version follows the syllabus for the current exam.
If you find it useful, I would be really grateful if you can donate a little something to the below appeal Fund.
The Tsunami appeal information is here: http://www.rescue.org/japan-crisis
Finally can I ask for errata etc. to be sent to my GMX account which is garnet.newton-wade@gmx.com (I can withstand a bit of spam on that address  )
Thanks
Garnet Newton-Wade

Hi,
Attached is a Juniper JNCIS-FWV Study Guide for exam JN0-532 in PDF document format. It is similar to the Jason Ha document some of you may remember from the past. However, my version follows the syllabus for the current exam.
If you find it useful, I would be really grateful if you can donate a little something to the below appeal Fund.
The Tsunami appeal information is here: http://www.rescue.org/japan-crisis
Finally can I ask for errata etc. to be sent to my GMX account which is garnet.newton-wade@gmx.com (I can withstand a bit of spam on that address  )
Thanks
Garnet Newton-Wade

More info:

Published by: Gavrilo on Mar 21, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

12/11/2013

pdf

text

original

Border Gateway Protocol (BGP) is a protocol that allows additional routing variables to help add
customisability to routing decisions. BGP is a Path Vector routing protocol because of its
reliance on paths to determine routes. The current version of BGP in is BGP version 4 and is the
de facto exterior routing protocol BGP uses techniques include using autonomous systems to
represent entire networks incremental update and classless inter-domain routing (CIDR). BGP
peers use TCP port 179 to communicate routing updates between themselves.

Autonomous Systems

An autonomous system (AS) is a network under administrative control by a single organisation.
A series of autonomous systems used for routing decisions describes a path so the AS number
must be unique and be assigned to an organisation participating in BGP though there are private
AS numbers which can be used for internal purposes. IANA distributes AS numbers to
organisations which need their own AS

BGP Peers

Routers participating in BGP must be connected to at least one other BGP router which is known
as a BGP peer. The BGP peer’s communicate over TCP port 179 and updates are sent
incrementally to their peers as new route data becomes available. Peers must be configured to
talk to their neighbour or else the BGP session won’t be established.

BGP Attributes

Attributes commonly used by the Juniper firewalls:

AS Path - Defines the AS numbers the route has traversed and determines the best path and
avoids routing loops. Route decisions can be enforced based upon the ASs the route has
traversed. The attribute is passed to other routers that the route is announced to with the AS
number of each AS appended to the path as it passes through the respective AS (mandatory)

Next-Hop - Next-hop IP address that the router will take to reach the destination (mandatory)

Origin - How the route was learned e.g. from an internal gateway protocol (IGP) such as OSPF
an exterior gateway protocol EGP or incomplete (mandatory)

Local Preference - The preferred exit point for an AS for routes that travel through it (optional)

Atomic Aggregate - lets the BGP neighbor know the route was summarised and the original
path was lost (optional)

Aggregator – the BGP peer specifies the router ID and AS number used for the aggregation
(optional)

Page | 108

Community - used to group routes together based on their attributes (optional)

Multiple Exit Discriminator - Advertised to BGP peers to indicating the preferred value when
multiple paths exist into the AS (optional)

Cluster List - Defined for iBGP and used to determine the route reflector the route has gone

through.
BGP communicates on TCP port 179 and within that communication channel BGP uses several
different control messages to perform BGP tasks.

Open Message - first message exchanged between two BGP peers after the TCP session

on port 179 has been initiated and formally establishes the BGP connection between the
peers.

Update Message - BGP announcement to withdraw routes done with information
contained in the update message.
Notification Message - exchanged when an error is detected by BGP and contains the
reason for the message, then closes the BGP session
Keep-Alive Message - exchanged between BGP peers to keep TCP sessions established
and let each know the other peer is still active

IBGP

IBGP is used when BGP AS Path information must be maintained within an AS to other BGP
peers and must be fully meshed or have equivalent behaviour with route reflectors or
confederations which is important to help maintain a loop-free topology.

Route Reflection

IBGP can employ route reflectors to reduce the complexity of a BGP internal network. The
complexity of fully meshed networks grows with every peer added to the domain so Route

reflectors help to subdivide an iBGP domain into a more manageable topology. Route reflectors
work similarly to designated routers in OSPF. All iBGP routers within a route reflector group
send the routes to the route reflector which then distribute them to other directly connected
route reflector peers. Route reflector properties:

Route Reflector - Specifies whether the BGP instance should act as a route reflector or

not

Cluster ID - Specifies what the cluster ID should be for this route reflector instance

Confederations

Confederations allow you to make sub-ASs which are ASs that are further segmented so you
don’t have to mesh an entire iBGP network and can mesh within sub-ASs. Those can then be
meshed together with the other ASs and can greatly reduce the number of links to be
maintained and reduce complexity. Confederations properties:

Confederation - specifies whether confederations are enabled or disabled.
ID - the AS number of the confederation.
Peer Member Area ID - the AS number of the sub-AS which is part of the confederation

Page | 109

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->