Refer to the Exhibit.

You recently added an EBGP neighbor to R1 and you are receiving a single BGP route for their
internal network. You notice that on R2 the route learned from C1 is being marked as hidden
because the next hop is unusable.
Referring to the exhibit, what should you do to resolve the problem?

— Exhibit –user@router> show system switchover
Graceful switchover: On
Configuration databasE. Ready
Kernel databasE. Version incompatible
Peer statE. Steady State
— Exhibit –You have enabled graceful Routing Engine switchover (GRES). During verification, you switched
mastership and all interfaces went down.
Referring to the output shown in the exhibit, why did the interfaces go down?

— Exhibit –[edit]
user@router# show interfaces
ge-1/1/2 {
gigether-options {
802.3ad ae0;
}
}
ge-1/1/3 {
gigether-options {
802.3ad ae0;
}
}
ae0 {
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 100;
}
}
}

— Exhibit –You are asked to configure a LAG. You configure and commit the configuration as shown in the
exhibit. When verifying your ae0 interface, you encounter the following error:
[edit]
user@router# run show interfaces ae0
error: device ae0 not found
Which command would you use to resolve this problem?

— Exhibit –[edit]
user@R1# run show interfaces ge-1/1/2 terse
Interface Admin Link Proto Local Remote
ge-1/1/2 up up
ge-1/1/2.0 up up aenet –> ae0.0
[edit]
user@R1# run show interfaces ge-1/1/3 terse
Interface Admin Link Proto Local Remote
ge-1/1/3 up up
ge-1/1/3.0 up up aenet –> ae0.0

[edit]
user@R1# run show interfaces ae0 terse
Interface Admin Link Proto Local Remote
ae0 up down
ae0.0 up down bridge
[edit]
user@R1# show interfaces ae0
aggregated-ether-options {
lacp {
periodic slow;
system-priority 200;
}
}
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 100;
}
}
**************************************************************************
[edit]
user@R2# run show interfaces ge-1/1/2 terse
Interface Admin Link Proto Local Remote
ge-1/1/2 up up
ge-1/1/2.0 up up aenet –> ae0.0

[edit]
user@R2# run show interfaces ge-1/1/3 terse
Interface Admin Link Proto Local Remote
ge-1/1/3 up up
ge-1/1/3.0 up up aenet –> ae0.0
[edit]
user@R2# run show interfaces ae0 terse
Interface Admin Link Proto Local Remote
ae0 up down
ae0.0 up down bridge
[edit]
user@R2# show interfaces ae0
aggregated-ether-options {
lacp {
periodic fast;
system-priority 100;
}
}
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 100;
}
}
— Exhibit —

You have configured a LAG and are now enabling LACP on the ae0 interface. You have
configured and committed the configuration as shown in the exhibit. However, the exhibit also
shows that the ae0 interface is now in the up/down state.
What must you do to resolve this problem?