— Exhibit —
SITE1:
routing-options {
autonomous-system 65001;
}
protocols {
bgp {
group 65002 {
neighbor 10.200.12.1 {
peer-as 65002;
} } }
}
SITE2:
routing-options {
autonomous-system 65002;
}
protocols {
bgp {
group 65001 {
neighbor 10.200.12.2 {
peer-as 65003;
} } }
}
— Exhibit —
Referring to the exhibit, SITE1 is configuring an EBGP peering with SITE2. SITE2 configured the
incorrect peer AS during a maintenance window and now is unable to change the configuration
until the next maintenance window.
Which configuration would you use on SITE1 to establish the EBGP peering?
A.
protocols {
bgp {
group 65002 {
passive;
neighbor 10.200.12.2 {
peer-as 65002;
}}}}
B.
protocols {
bgp {
group 65002 {
accept-remote-nexthop;
neighbor 10.200.12.2 {
peer-as 65002;
}}}}
C.
protocols {
bgp {
group 65002 {
local-as 65003;
neighbor 10.200.12.2 {
peer-as 65002;
}}}}
D.
protocols {
bgp {
group 65002 {
as-override;
neighbor 10.200.12.2 {
peer-as 65002;
}}}}