interfaces {
ge-0/0/0 {
vlan-tagging;

unit 100 {
vlan-id 100;
family inet {
address 192.168.100.97/30;
}
family iso;
}
unit 200 {
vlan-id 200;
family inet {
address 192.168.100.94/30;
}
family iso;
} }
fxp0 {
description “MGMT INTERFACE – DO NOT DELETE”;
unit 0 {
family inet {
address 10.210.10.11/27;
} } }
lo0 {
unit 0 {
family inet {
address 192.168.100.1/32;

}
family iso {
address 49.1111.1921.6801.0001.00;
} } }
}
protocols {
isis {
interface ge-0/0/0.100;
interface ge-0/0/0.200;
}
}

Click the Exhibit button.
An operator is unable to establish any IS-IS adjacencies on a router in the network.
Based on the configuration shown in the exhibit, what is the problem?

user@r1> show interfaces terse ge-1/0/0
Interface Admin Link Proto Local Remote
ge-1/0/0 up up
ge-1/0/0.0 up up inet6 fe80::226:88ff:fe02:7481/64
fec0:0:0:2003::1/64

Click the Exhibit button.
You run the command show interfaces terse ge-1/0/0 and see the output shown in the exhibit.
Why are two addresses being shown for this interface?

[edit]
user@Router-X# show policy-options policy-statement nhs
term 1 {
from {
protocol bgp;

neighbor 10.0.21.2;
}
then next-hop self;
}

Click the Exhibit button.
Router-X has an external peering session to 10.0.21.2 and several internal peers.
How can the policy referenced in the exhibit be used to make sure routes are usable?

protocols {
isis {
interface lo0.0;
interface ge-0/0/0.100;
}
}

Click the Exhibit button.

Referring to the exhibit, what will be the IS-IS levels enabled on the interface ge-0/0/0.100?