-- Exhibit --
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)
-- Exhibit --
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?
Click on the arrows to vote for the correct answer
A. B. C. D.D
Based on the exhibit, the BGP peering is failing due to a "bad peer AS number" error, which indicates that the configured peer AS number (65002) doesn't match the AS number claimed by the remote peer (65003).
To fix this issue, we need to configure the correct peer AS number, which is 65003 in this case. Therefore, option D "Configure the peer-as to 65003" would be the correct answer.
Option A, "Configure the local-as to 65003" is incorrect because the local-as parameter is used for BGP confederations, and it is not relevant to this scenario.
Option B, "Configure the autonomous-system to 65003" is also incorrect because it would change the local AS number, but it wouldn't fix the peer AS number mismatch issue.
Option C, "Configure the EBGP peering as passive" is also incorrect because it would only affect the direction of BGP session initiation, and it wouldn't fix the underlying issue with the AS number mismatch.
In summary, the correct answer is D, "Configure the peer-as to 65003".