What is the default keepalive time for BGP?
The default keepalive time for BGP is60 seconds1.The keepalive time is the interval at which BGP sends keepalive messages to maintain the connection with its peer1.If the keepalive message is not received within the hold time, the connection is considered lost1.By default, the hold time is three times the keepalive time, which is180 seconds1.
You are an operator for a network running 1S-IS. Two routers are failing to form an adjacency. What are two reasons for this problem? (Choose two.)
The two reasons for the failure to form an adjacency in a network running IS-IS could be:
B) There is no configured ISO address on any IS-IS interface.IS-IS requires each router interface to have an ISO address configured.Without this address, the routers cannot form an adjacency1.
D) The family iso configuration is missing from the adjacency interface.The 'family iso' configuration is essential for IS-IS to function correctly.If this configuration is missing from the adjacency interface, it could prevent the formation of an adjacency1.
These explanations are based on the Enterprise Routing and Switching Specialist (JNCIS-ENT) documents and learning resources available at Juniper Networks23.
Exhibit.

You want to verify prefix information being sent from 10.36.1.4.
Which two statements are correct about the output shown in the exhibit? (Choose two.)
The output shown in the exhibit is the result of the command ''show ip bgp neighbor 10.36.1.4 received-routes'', which displays all received routes (both accepted and rejected) from the specified neighbor.
Option A is correct, because the routes displayed have traversed one or more autonomous systems. This can be seen from the AS_PATH attribute, which shows the sequence of AS numbers that the route has passed through. For example, the route 10.0.0.0/8 has an AS_PATH of 65001 65002, which means that it has traversed AS 65001 and AS 65002 before reaching the local router.
Option B is correct, because the output shows routes that were received prior to the application of any BGP import policies. This can be seen from the fact that some routes have a status code of ''r'', which means that they are rejected by an import policy. The ''received-routes'' keyword shows the routes coming from a given neighbor before the inbound policy has been applied. To see the routes after the inbound policy has been applied, the ''routes'' keyword should be used instead.
Option C is incorrect, because the output does not show routes that are active and rejected by an import policy. The status code of ''r'' means that the route is rejected by an import policy, but it does not mean that it is active. The status code of ''>'' means that the route is active and selected as the best path. None of the routes in the output have both ''>'' and ''r'' status codes.
Option D is incorrect, because the routes displayed are not being learned from an IBGP peer. An IBGP peer is a BGP neighbor that belongs to the same AS as the local router. The output shows that the neighbor 10.36.1.4 has a remote AS of 65001, which is different from the local AS of 65002. Therefore, the neighbor is an EBGP peer, not an IBGP peer.
What is the default keepalive time for BGP?
The default keepalive time for BGP is60 seconds1.The keepalive time is the interval at which BGP sends keepalive messages to maintain the connection with its peer1.If the keepalive message is not received within the hold time, the connection is considered lost1.By default, the hold time is three times the keepalive time, which is180 seconds1.
Exhibit

You have configured a GRE tunnel. To reduce the risk of dropping traffic, you have configured a keepalive OAM probe to monitor the state of the tunnel; however, traffic drops are still occurring.
Referring to the exhibit, what is the problem?
A keepalive OAM probe is a mechanism that can be used to monitor the state of a GRE tunnel and detect any failures in the tunnel path. A keepalive OAM probe consists of sending periodic packets from one end of the tunnel to the other and expecting a reply.If no reply is received within a specified time, the tunnel is considered down and the line protocol of the tunnel interface is changed to down1.
To configure a keepalive OAM probe for a GRE tunnel, you need to specify two parameters: the keepalive-time and the hold-time. The keepalive-time is the interval between each keepalive packet sent by the local router.The hold-time is the maximum time that the local router waits for a reply from the remote router before declaring the tunnel down2.
According to the Juniper Networks documentation, the hold-time value must be two times the keepalive-time value for a GRE tunnel2. This is because the hold-time value must account for both the round-trip time of the keepalive packet and the processing time of the remote router. If the hold-time value is too small, it may cause false positives and unnecessary tunnel flaps.
In the exhibit, the configuration shows that the keepalive-time is set to 10 seconds and the hold-time is set to 15 seconds for the gr-1/1/10.1 interface. This means that the local router will send a keepalive packet every 10 seconds and will wait for 15 seconds for a reply from the remote router. However, this hold-time value is not two times the keepalive-time value, which violates the recommended configuration. This may cause traffic drops if the remote router takes longer than 15 seconds to reply.
Therefore, option D is correct, because the hold-time value must be two times the keepalive-time value for a GRE tunnel.Option A is incorrect, because BFD is not required for GRE tunnels; BFD is another protocol that can be used to monitor tunnels, but it is not compatible with GRE keepalives3.Option B is incorrect, because the ''event link-adjacency-loss'' option is not related to GRE tunnels; it is an option that can be used to trigger an action when a link goes down4.Option C is incorrect, because LLDP does not need to be removed from the gr-1/1/10.1 interface; LLDP is a protocol that can be used to discover neighboring devices and their capabilities, but it does not interfere with GRE tunnels5.
1:Configuring Keepalive Time and Hold time for a GRE Tunnel Interface2: keepalive | Junos OS | Juniper Networks3: Configuring Bidirectional Forwarding Detection4: event link-adjacency-loss | Junos OS | Juniper Networks5: Understanding Link Layer Discovery Protocol
William White
11 days agoEric Wright
24 days agoBrenda Rodriguez
1 month agoGeorge Miller
27 days agoRebecca Johnson
26 days agoEmma Williams
22 days agoGeorge Allen
17 days agoAnthony Hill
1 month agoDannie
2 months agoVashti
2 months agoLucy
2 months agoClemencia
3 months agoSharee
3 months agoVashti
3 months agoDarnell
3 months agoJerry
4 months agoVirgilio
4 months agoSkye
4 months agoPaul
5 months agoNoah
5 months agoNelida
5 months agoGlory
5 months agoCelia
6 months agoWendell
6 months agoHortencia
6 months agoHeidy
6 months agoSonia
7 months agoMargo
7 months agoAlayna
7 months agoAaron
7 months agoKenny
8 months agoAlex
8 months agoRosina
8 months agoTina
8 months agoNathalie
9 months agoHelaine
9 months agoJeanice
11 months agoHyman
12 months agoCarin
1 year agoLinn
1 year agoLeota
1 year agoKristofer
1 year agoIrma
1 year agoDorothy
1 year agoCarma
1 year agoJudy
1 year agoQueen
2 years agoCeleste
2 years agoNadine
2 years agoAnnice
2 years agoIesha
2 years agoRory
2 years agoLezlie
2 years agoRoxane
2 years agoLayla
2 years agoColette
2 years agoMaurine
2 years agoQueenie
2 years agoCrista
2 years agoKeneth
2 years agoHerminia
2 years agoGlory
2 years agoTerrilyn
2 years agoLazaro
2 years agoFernanda
2 years agoPamella
2 years agoBlondell
2 years agoHelaine
2 years agoKattie
2 years agoBrynn
2 years ago