— 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?
A.
Configure both routers’ ae0 LACP configuration to periodic fast.
B.
Change the LACP system-priority of R1 to 300.
C.
Configure R1’s LACP configuration as active.
D.
Configure R2’s LACP configuration as passive.