PrepAway - Latest Free Exam Questions & Answers

Category: JN0-360 (v.4)

Exam JN0-360: Juniper Networks Certified Internet Specialist (JNCIS-SP) (updated July 13, 2015)

what should be changed under the BGP configuration to resolve this issue?

Leave a comment

user@R1> show route protocol bgp
inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both
200.200.0.0/24 *[BGP/170] 00:00:47, localpref 100
AS path: 65001 I
> to 192.168.100.1 via ge-1/1/5.435
200.200.1.0/24 *[BGP/170] 00:00:47, localpref 100
AS path: 65001 I
> to 192.168.100.1 via ge-1/1/5.435
200.200.2.0/24 *[BGP/170] 00:00:47, localpref 100
AS path: 65001 I
> to 192.168.100.1 via ge-1/1/5.435
200.200.3.0/24 *[BGP/170] 00:00:47, localpref 100

AS path: 65001 I
> to 192.168.100.1 via ge-1/1/5.435
user@R2> show route 200.200/16
inet.0: 36 destinations, 36 routes (36 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, – = Last Active, * = Both
200.200.0.0/24 *[Static/5] 00:09:12
Reject
200.200.1.0/24 *[Static/5] 00:09:12
Reject
200.200.2.0/24 *[Static/5] 00:09:12
Reject
200.200.3.0/24 *[Static/5] 00:09:12
Reject
200.200.4.0/24 *[Static/5] 00:09:12
Reject
user@R2> show configuration protocols bgp
export export-200;
group c5 {
neighbor 192.168.100.2 {
export export-200.200;
peer-as 65002;
}
}

user@R2> show configuration policy-options policy-statement export-200.200
term 1 {
from {
route-filter 200.200.0.0/22 longer;
}
then accept;
}
user@R2> show configuration policy-options policy-statement export-200
term 1 {
from {
route-filter 200.200.0.0/21 longer;
}
then accept;
}

Click the Exhibit button.
R2 is exporting static routes to R1 using BGP. R1 is not receiving one of the five static routes that
is configured on R2.
Referring to the exhibit, what should be changed under the BGP configuration to resolve this
issue?

what should be changed to the BGP configuration to bring up the peering?

Leave a comment

user@router> show configuration interfaces ge-1/0/0
unit 0 {
family inet {
address 192.168.100.1/30;
}
}
user@router> show configuration routing-options
autonomous-system 65001;
user@router> show configuration protocols bgp
group 65002 {
traceoptions {
file bgp-trace;
flag open detail;
}
neighbor 192.168.100.3 {
peer-as 65002;
}
}
user@router> show log bgp-trace
Feb 5 20:31:01 R4 clear-log[5510]: logfile cleared
Feb 5 20:32:22.658155 bgp_connect_completE. error connecting to 192.168.100.3 (External AS
65002): Socket is not connected
user@router> run monitor traffic interface ge-1/0/0 extensive

Address resolution is ON. Use to avoid any reverse lookup delay.
Address resolution timeout is 4s.
Listening on ge-1/0/0, capture size 1514 bytes
20:45:44.212833 Out
Juniper PCAP Flags [Ext], PCAP Extension(s) total length 22
Device Media Type Extension TLV #3, length 1, valuE. Ethernet (1)
Logical Interface Encapsulation Extension TLV #6, length 1, valuE. Ethernet (14)
Device Interface Index Extension TLV #1, length 2, valuE. 35328
Logical Interface Index Extension TLV #4, length 4, valuE. 70
Logical Unit Number Extension TLV #5, length 4, valuE. 32767
—–original packet—–
80:71:1f:c7:f8:60 > 84:18:88:8e:3b:3f, ethertype 802.1Q (0x8100), length 82: vlan 435, p 6,
ethertype IPv4, (tos 0xc0, ttl 255, id 19548, offset 0, flags [DF], proto: TCP (6), length: 64)
192.168.100.1.bgp > 192.168.100.2.49373: S 1088527795:1088527795(0) ack 214564428 win
16384
20:45:44.213226 In
Juniper PCAP Flags [Ext, no-L2, In], PCAP Extension(s) total length 22
Device Media Type Extension TLV #3, length 1, valuE. Ethernet (1)
Logical Interface Encapsulation Extension TLV #6, length 1, valuE. Ethernet (14)
Device Interface Index Extension TLV #1, length 2, valuE. 35328
Logical Interface Index Extension TLV #4, length 4, valuE. 70
Logical Unit Number Extension TLV #5, length 4, valuE. 32767
—–original packet—–
PFE proto 2 (ipv4): (tos 0xc0, ttl 1, id 2367, offset 0, flags [none], proto: TCP (6), length: 52)
192.168.100.2.49373 > 192.168.100.1.bgp: . 1:1(0) ack 1 win 17376

Click the Exhibit button.

You are asked to configure an EBGP peering to AS 65002. The EBGP peering is stuck in a
Connect state.
Referring to the exhibit, what should be changed to the BGP configuration to bring up the peering?

what would be changed to bring up the peering?

Leave a comment

user@router> show configuration routing-options
autonomous-system 65001;
user@router> show configuration protocols bgp
group 65002 {
traceoptions {
file bgp-trace;
flag open detail;
}
neighbor 192.168.100.2 {
peer-as 65002;
}
}
user@router> show log bgp-trace
Feb 5 20:07:08 trace_on: Tracing to “/var/log/bgp-trace” started

Feb 5 20:08:23.477912 bgp_senD. sending 63 bytes to 192.168.100.2 (External AS 65002)
Feb 5 20:08:23.478040
Feb 5 20:08:23.478040 BGP SEND 192.168.100.1+62776 -> 192.168.100.2+179
Feb 5 20:08:23.478077 BGP SEND message type 1 (Open) length 63
Feb 5 20:08:23.478100 BGP SEND version 4 as 65001 holdtime 90 id 10.200.1.4 parmlen 34
Feb 5 20:08:23.478119 BGP SEND MP capability AFI=1, SAFI=1
Feb 5 20:08:23.478138 BGP SEND Refresh capability, code=128
Feb 5 20:08:23.478155 BGP SEND Refresh capability, code=2
Feb 5 20:08:23.478176 BGP SEND Restart capability, code=64, time=120, flags=
Feb 5 20:08:23.478196 BGP SEND Restart capability AFI=1, SAF=1, Flags=ForwardingSaved
Feb 5 20:08:23.478217 BGP SEND 4 Byte AS-Path capability (65), as_num 65001
Feb 5 20:08:23.478820
Feb 5 20:08:23.478820 BGP RECV 192.168.100.2+179 -> 192.168.100.1+62776
Feb 5 20:08:23.478859 BGP RECV message type 1 (Open) length 59
Feb 5 20:08:23.478880 BGP RECV version 4 as 65003 holdtime 90 id 192.168.1.1 parmlen 30
Feb 5 20:08:23.478899 BGP RECV MP capability AFI=1, SAFI=1
Feb 5 20:08:23.478918 BGP RECV Refresh capability, code=128
Feb 5 20:08:23.478935 BGP RECV Refresh capability, code=2
Feb 5 20:08:23.478955 BGP RECV Restart capability, code=64, time=120, flags=
Feb 5 20:08:23.478974 BGP RECV 4 Byte AS-Path capability (65), as_num 65003
Feb 5 20:08:23.479057 bgp_process_open: : NOTIFICATION sent to 192.168.100.2 (External AS
65002): code 2 (Open Message Error) subcode 2 (bad peer AS number), Reason: peer
192.168.100.2 (External AS 65002) claims 65003, 65002 configured
Feb 5 20:08:23.479083 bgp_senD. sending 21 bytes to 192.168.100.2 (External AS 65002)
Feb 5 20:08:23.479104
Feb 5 20:08:23.479104 BGP SEND 192.168.100.1+62776 -> 192.168.100.2+179
Feb 5 20:08:23.479136 BGP SEND message type 3 (Notification) length 21
Feb 5 20:08:23.479156 BGP SEND Notification code 2 (Open Message Error) subcode 2 (bad

peer AS number)

Click the Exhibit button.
You have been asked to configure an EBGP peering to AS 65002. The EBGP peering is stuck in
an Active state.
Referring to the exhibit, what would be changed to bring up the peering?

what is missing in the configuration to make the Layer 3 VPN functional?

Leave a comment

[edit]
user@router# show protocols bgp
group ibgp {
type internal;
local-address 3.3.3.3;
family inet;
neighbor 2.2.2.2;

}
[edit]
user@router# show routing-instances
VRF {
instance-type vrf;
interface xe-0/0/1.0;
route-distinguisher 3.3.3.3:100;
vrf-target target:100:100;
vrf-table-label;
}
[edit]
user@router# show protocols mpls
interface all;
[edit]
user@router# show protocols rsvp
interface all;

Click the Exhibit button.
Referring to the exhibit, what is missing in the configuration to make the Layer 3 VPN functional?
(Choose two.)

which configuration element is missing to bring up the Layer 2 circuit?

Leave a comment

user@router# show interfaces
xe-0/0/0 {
unit 0 {
family inet {
address 192.168.12.1/24;
}
family mpls;
}
}
xe-0/0/1 {
encapsulation ethernet-ccc;
unit 0 {
family ccc;
}
}
lo0 {
unit 0 {
family inet {
address 1.1.1.1/32;
} }
}
[edit]

user@router# show protocols
mpls {
interface all;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface all;
}
}
ldp {
interface all;
}
l2circuit {
neighbor 2.2.2.2 {
interface xe-0/0/1.0 {
} }
}

Click the Exhibit button.
In the exhibit, which configuration element is missing to bring up the Layer 2 circuit?


Page 11 of 26« First...910111213...20...Last »