You are troubleshooting a problem where an OSPF adjacency between two neighboring routers will not
form.
What are two reasons for this problem? (Choose two.)
A. One or both of the connected interfaces are missing the family inet statement.
B. One or both of the connected interfaces are missing the family iso statement.
C. The connected interfaces are not on the same subnet.
D. Another IGP is running on one or both of the routers, overriding OSPF.
Two neighboring routers are able to form an OSPF adjacency, but are not able to establish an IBGP neighborship.
What are two reasons for the IBGP neighborship problem? (Choose two.)
A. One of the devices has a misconfigured BGP peer address.
B. One or both of the connected interfaces are missing the family iso statement.
C. OSPF has a lower route preference than BGP.
D. A firewall filter on one of the interfaces is blocking TCP traffic.
Your Layer 2 network uses VLAN IDs 100 through 400 and you are required to load-balance these VLANs between two different root bridges. You are currently using the default RSTP settings and notice that all VLANs are using the same root bridge.
How do you ensure the VLANs are load-balanced between two root bridges?
A. Configure MSTP with two MSTI regions and split the VLAN range between them.
B. Configure VSTP with two VLAN groups and split the VLAN range between them.
C. Configure two RSTP instances and split the VLAN range between them.
D. Configure STP and RSTP and split the VLAN range between them.
-- Exhibit
-- Exhibit -Click the Exhibit button.
Referring to the exhibit, you are configuring an OSPF network. All OSPF adjacencies come up and stay stable. But neither R1 nor R2 has the prefix 200.200.200.200/32 in its routing table.
What is causing this problem?
A. R2 does not have the export policy for prefix 200.200.200.200/32.
B. R1 does not have routes to network 172.10.1.0/24.
C. R2 is BDR on both network 172.10.1.0/24 and 172.20.1.0/24.
D. The router ID of R1 is the same as the router ID of R3.
-- Exhibit -user@router# run show log bgp-test ... Jun 10 23:50:43.056697 BGP SEND 192.168.133.1+179 -> 192.168.133.0+64925 Jun 10 23:50:43.056739 BGP SEND message type 3 (Notification) length 23 Jun 10 23:50:43.056760 BGP SEND Notification code 2 (Open Message Error) subcode 7 (unsupported capability) Jun 10 23:50:43.056781 BGP SEND Data (2 bytes): 00 04 Jun 10 23:50:52.215104 advertising receiving-speaker only capabilty to neighbor ::192.168.133.0 (External AS 300) Jun 10 23:50:52.215173 bgp_senD. sending 59 bytes to ::192.168.133.0 (External AS 300) Jun 10 23:50:52.215200 Jun 10 23:50:52.215200 BGP SEND ::192.168.133.1+179 -> ::192.168.133.0+57107 Jun 10 23:50:52.215233 BGP SEND message type 1 (Open) length 59 Jun 10 23:50:52.215256 BGP SEND version 4 as 23456 holdtime 90 id 10.200.1.1 parmlen 30 Jun 10 23:50:52.215276 BGP SEND MP capability AFI=2, SAFI=1 Jun 10 23:50:52.215294 BGP SEND Refresh capability, code=128 Jun 10 23:50:52.215312 BGP SEND Refresh capability, code=2 Jun 10 23:50:52.215332 BGP SEND Restart capability, code=64, time=120, flags= Jun 10 23:50:52.215353 BGP SEND 4 Byte AS-Path capability (65), as_num 2123456789 Jun 10 23:50:52.216018 Jun 10 23:50:52.216018 BGP RECV ::192.168.133.0+57107 -> ::192.168.133.1+179 Jun 10 23:50:52.216058 BGP RECV message type 3 (Notification) length 21 Jun 10 23:50:52.216079 BGP RECV Notification code 2 (Open Message Error) subcode 2 (bad peer AS number) Jun 10 23:51:15.058112 advertising receiving-speaker only capabilty to neighbor 192.168.133.0 (External AS 300) Jun 10 23:51:15.058192 bgp_senD. sending 59 bytes to 192.168.133.0 (External AS 300) Jun 10 23:51:15.058217 Jun 10 23:51:15.058217 BGP SEND 192.168.133.1+50083 -> 192.168.133.0+179 Jun 10 23:51:15.058250 BGP SEND message type 1 (Open) length 59 Jun 10 23:51:15.058273 BGP SEND version 4 as 65001 holdtime 90 id 10.200.1.1 parmlen 30 Jun 10 23:51:15.058294 BGP SEND MP capability AFI=1, SAFI=128 Jun 10 23:51:15.058312 BGP SEND Refresh capability, code=128 Jun 10 23:51:15.058331 BGP SEND Refresh capability, code=2 Jun 10 23:51:15.058386 BGP SEND Restart capability, code=64, time=120, flags= Jun 10 23:51:15.058416 BGP SEND 4 Byte AS-Path capability (65), as_num 65001 Jun 10 23:51:15.058651 bgp_pp_recv:3140: NOTIFICATION sent to 192.168.133.0 (External AS 300): code 6 (Cease) subcode 7 (Connection collision resolution), Reason: dropping
192.168.133.0 (External AS 300), connection collision prefers 192.168.133.0+53170 (proto) Jun 10 23:51:15.058680 bgp_senD. sending 21 bytes to 192.168.133.0 (External AS 300) Jun 10 23:51:15.058702 Jun 10 23:51:15.058702 BGP SEND 192.168.133.1+50083 -> 192.168.133.0+179 Jun 10 23:51:15.058735 BGP SEND message type 3 (Notification) length 21 Jun 10 23:51:15.058755 BGP SEND Notification code 6 (Cease) subcode 7 (Connection collision resolution) Jun 10 23:51:15.059557 advertising receiving-speaker only capabilty to neighbor 192.168.133.0 (External AS 300) Jun 10 23:51:15.059594 bgp_senD. sending 59 bytes to 192.168.133.0 (External AS 300) Jun 10 23:51:15.059617 Jun 10 23:51:15.059617 BGP SEND 192.168.133.1+179 -> 192.168.133.0+53170 Jun 10 23:51:15.059649 BGP SEND message type 1 (Open) length 59 Jun 10 23:51:15.059671 BGP SEND version 4 as 65001 holdtime 90 id 10.200.1.1 parmlen 30 Jun 10 23:51:15.059691 BGP SEND MP capability AFI=1, SAFI=128 Jun 10 23:51:15.059709 BGP SEND Refresh capability, code=128 Jun 10 23:51:15.059727 BGP SEND Refresh capability, code=2 Jun 10 23:51:15.059747 BGP SEND Restart capability, code=64, time=120, flags= Jun 10 23:51:15.059768 BGP SEND 4 Byte AS-Path capability (65), as_num 65001 Jun 10 23:51:15.060383 bgp_process_caps: mismatch NLRI with 192.168.133.0 (External AS 300): peer: (1) us: (4) Jun 10 23:51:15.060445 bgp_process_caps:2578: NOTIFICATION sent to 192.168.133.0 (External AS 300): code 2 (Open Message Error) subcode 7 (unsupported capability) value 4 Jun 10 23:51:15.060470 bgp_senD. sending 23 bytes to 192.168.133.0 (External AS 300) Jun 10 23:51:15.060492 Jun 10 23:51:15.060492 BGP SEND 192.168.133.1+179 -> 192.168.133.0+53170 Jun 10 23:51:15.060556 BGP SEND message type 3 (Notification) length 23 Jun 10 23:51:15.060578 BGP SEND Notification code 2 (Open Message Error) subcode 7 (unsupported capability) Jun 10 23:51:15.060600 BGP SEND Data (2 bytes): 00 04 -- Exhibit -
Click the Exhibit button.
Referring to the exhibit, what is causing the IPv4 BGP peering to stay in an active state?
A. The peer AS is incorrect.
B. The peer does not support 4-byte AS values.
C. The peer has an NLRI mismatch.
D. The peer has an incorrect IP address.
-- Exhibit -[edit routing-instances]
user@router# show vr1 routing-options
instance-import [ vr1 vr2 ];
[edit routing-instances]
user@router# show vr2 routing-options
instance-import [ vr1 vr2 ];
[edit routing-instances]
user@router# top show policy-options policy-statement vr1 term 1 {
from instance vr1;
then accept;
}
term 2 {
then reject;
}
[edit routing-instances]
user@router# top show policy-options policy-statement vr2 term 1 {
from instance vr2;
then accept;
}
term 2 {
then reject;
}
-- Exhibit -
Click the Exhibit button.
A network engineer wants to leak routes between routing instances vr1 and vr2. No routes from vr2 are
showing up in vr1.
Which change should the engineer make to accomplish this task?
A. [edit routing-instances]user@router# delete vr1 routing-options instance-import[edit routing- instances] user@router# set vr1 routing-options instance-import (vr1 || vr2)
B. [edit routing-instances]user@router# delete vr1 routing-options instance-import[edit routing- instances] user@router# set vr1 routing-options instance-import (vr1 andand vr2)
C. [edit routing-instances]user@router# set vr1 routing-options auto-export
D. [edit routing-instances]user@router# set vr1 routing-options interface-routes rib-group vr2
-- Exhibit -policy-options {
policy-statement accept-static {
from protocol static;
then accept;
}
}
-- Exhibit -
Click the Exhibit button.
The policy shown in the exhibit is deployed on a router and used as the only BGP export policy. The router
is sending only one BGP route to its peers. However, when you run the CLI command test policy accept-
static 0.0.0.0/0, the policy matches thousands of routes.
Which statement explains this discrepancy?
A. All policies have an implicit then accept final term.
B. The default policy for BGP is to reject all routes.
C. The default policy for the test policy command is to accept all routes.
D. The test policy command always shows all routes, regardless of whether they match the policy, when you use the 0.0.0.0/0 argument.
-- Exhibit -user@switch# show vlans
ws {
vlan-id 23;
interface {
ge-0/0/12.0;
ge-0/0/6.0;
}
dot1q-tunneling;
no-mac-learning;
}
-- Exhibit -
Click the Exhibit button.
Referring to the exhibit, an administrator notices that all traffic is flooded out of all the ports in VLAN ws.
What would cause this problem?
A. no-mac-learning is enabled on the interface.
B. Spanning tree is disabled.
C. dot1q-tunneling is enabled on the VLAN.
D. Unicast destinations are flooded out of all ports.
The exhibit shows part of the configuration for a router. You receive a complaint that the router is not correctly reclassifying all traffic to the best-effort forwarding class when the amount of IPv4 traffic exceeds 10 Mbps.
You have isolated the problem to traffic with the IP precedence bits set to the binary value 101. Which configuration is causing this behavior?
A. the filter firewall filter's term 1
B. the filter firewall filter's term 2
C. the ip_classifier_1 classifier
D. the policer1 policer
You add a multicast source to a network. The source's DR sends register messages to the RP However, multicast clients are not able to receive traffic from the source. What are two causes of this problem? (Choose two.)
A. A reject policy is configured on the designated router.
B. The RP did not receive a PIM join message for the group specified.
C. A reject policy is configured on the RP.
D. The designated router must send a null register message to the RP.