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?
A.
Configure the neighbor to 192.168.100.2.
B.
Configure the local-as to 65001.
C.
Configure the peer-as to 65001.
D.
Configure the peering as passive.
Explanation: