Refer to the Exhibit.
— Exhibit –user@router> show configuration | no-more
…
interfaces {
ge-0/0/0 {
unit 0 {
family inet {
address 10.210.12.131/27;
}
}
}
ge-0/0/1 {
unit 0 {
family inet {
filter {
input fbf;
}
address 10.210.14.1/24;
}
}
}
}
firewall {
filter fbf {
term 1 {
then {
routing-instance fbf;
}
}
}
}
routing-instances {
fbf {
instance-type forwarding;
routing-options {
static {
route 0.0.0.0/0 next-hop 10.210.12.129;
}
}
}
}
user@router> show route
inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both
10.210.12.128/27 *[Direct/0] 3d 23:21:02
> via ge-0/0/0.0
10.210.12.131/32 *[Local/0] 3d 23:21:17
Local via ge-0/0/0.0
10.210.14.0/24 *[Direct/0] 00:00:07
> via ge-0/0/1.0
10.210.14.1/32 *[Local/0] 00:00:07
Local via ge-0/0/1.0
— Exhibit –What is causing the behavior shown in the exhibit?
A.
The software is ignoring the fbf routing instance because it uses a reserved name.
B.
The software is ignoring the default route in the fbf routing instance because there is no default
route in the main routing instance.
C.
The software is not able to find an interface on the router configured with the 10.210.12.129
address.
D.
The software is not able to resolve the next hop of the default route in the fbf routing instance.
Explanation: