Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
38 Cards in this Set
- Front
- Back
syntax of ebgp-multihop command
|
neighbor {ip-address | peer-group-name} ebgp-multihop [ttl]
|
|
common reason to use ebgp-multihop
|
allow routes to EBGP loopback address, which is considered more than 1 hop
|
|
why to use next-hop-self command
|
if a route points towards an address that is not being redistributed by any IGP
the source address will be replaced by the address of the border router which is directly connected to the other AS but is not advertising the network of the link between them via the IGP |
|
T/F: BGP "network" command specifies an interface and then advertises the network with the same subnet mask that is used on the ip address of that interface
|
FALSE. it does not specify interfaces, just networks to advertise
|
|
syntax of BGP "network" command
|
network network-number [mask network-mask] [route-map map-tag]
|
|
what is the default status of the bgp auto-summary setting
|
no auto-summary (as of IOS 12.2(8)T)
|
|
what is the BGP synchronization rule
|
the BGP router should not use, or advertise to an external neighbor, a route that is learned from IBGP unless that route is local or the router learns it from the IGP
|
|
T/F: by default, BGP synchronization is disabled
|
TRUE (as of IOS 12.2(8)T)
|
|
what happens if BGP synchronization is disabled
|
routers are able to use and advertise routes that have been learned by IBGP and not an IGP
|
|
when is it safe to disable BGP synchronization and what is the advantage
|
if all routers in the transit path are running full mesh IBGP
advantage - router can carry fewer routes in the IGP and allows BGP to converge more quickly |
|
T/F: BGP synchronization is used when all external routes are to be imported into the IGP. this is difficult now because of the size of the internet routing table and is usually not used
|
TRUE
|
|
BGP states
|
idle, connect, open sent, open confirm, established
|
|
meaning of BGP states
|
idle - searching the routing table to find a route to the neighbor
connect - found a route to the neighbor and has completed the TCP handshake open sent - message sent open confirm - received agreement on the parameters for the session established - peering is established; routing begins |
|
why would a BGP router be stuck in idle state
|
it is not able to find the specified IP address in its routing table
|
|
why would a router be stuck in active or cycling between idle and active
|
it has sent the open packet but does not get a response. this may be because the peer router does not have a way to send the response
|
|
how to create a peer group
|
neighbor peer-group-name peer-group
|
|
benefit of peer group
|
can apply policies to multiple neighbors without doing it over again for each one
|
|
command for BGP authentication
|
neighbor {ip-address | peer-group-name} password string
|
|
ways to trigger a BGP update
|
hard reset
soft reset route refresh |
|
reset all BGP information
|
clear ip bgp *
|
|
reset BGP information for a single peer
|
clear ip bgp [neighbor-address]
|
|
clear ip bgp soft in
|
soft reconfiguration of both inbound and outbound updates
|
|
what are the common categories of BGP path attributes
|
Well-known mandatory
Well-known discretionary Optional transitive Optional nontransitive |
|
only _________ attributes can be marked as partial
|
optional transitive
|
|
optional attributes are either _______ or _______
|
transitive
non-transitive |
|
three well-known mandatory attributes
|
autonomous system path
next hop origin |
|
two well-known discretionary attributes
|
local preference
atomic aggregate |
|
what is one optional transitive attribute
|
aggregator
|
|
what is one optional nontransitive attribute
|
multi-exit discriminator (MED)
|
|
what kind of attribute is weight
|
it is a locally configured attribute and not propagated to other routers
|
|
what information and what form does the AS path attribute have
|
list of autonomous system numbers that a route has traversed to reach a destination, with the number of the autonomous system that originated the route at the end of the list
|
|
what information does the next-hop attribute contain
|
IP address of the border router that should be used as the next hop to the destination
|
|
when an EBGP route is put into IBGP, what next-hop address is used
|
the same as is used by EBGP, the IP of the border router of the other AS
|
|
three values of the origin attribute
|
IGP, EGP (no longer supported), incomplete (usually when a route is redistributed into BGP)
|
|
local path attribute contains what information
|
preferred path out of the AS
|
|
MED value advertises what
|
to tell EBGP neighbors how to exit their AS to reach networks owned by this AS
|
|
routes with {higher | lower} weight are preferred when multiple routes exist to the same destination
|
higher
|
|
command to change the default local preference value
|
bgp default local-preference value
|