100% Pass Guarantee with Juniper JN0-694 Dumps!

You observe that a router is using an unusually high amount of CPU cycles. You determine that continuous SPF calculations in OSPF are being performed.

What are two reasons for this problem? (Choose two.)

A. The wrong authentication keys between the OSPF neighbors are used.

B. The interface MTU is mismatched between the OSPF neighbors.

C. There are duplicate router IDs within the OSPF area.

D. An OSPF adjacency is flapping.

-- 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 -(MSTI 2 regional root: 16386.2c:6b:f5:3e:f8:01)

{master:0}

user@switch> show spanning-tree interface

Spanning tree interface parameters for instance 0

Interface Port ID Designated Designated Port State Role port ID bridge ID Cost

ge-0/0/6.0 128:519 128:519 16384.80711fbc 20000 BLK ALT ge-0/0/9.0 128:522 128:522

53248.2c6bf591a441 20000 FWD DESG ge-0/0/10.0 128:523 128:523 8192.80711fbe8110 20000 FWD

ROOT ge-0/0/12.0 128:525 128:525 49152.2c6bf53ef801 20000 BLK ALT

[...]

-- Exhibit -

Click the Exhibit button.

While troubleshooting an MSTP operation in your network, you see the output shown in the exhibit on one

of your switches. You know that the MSTI 2 regional root bridge ID is 16386.2c:6b:f5:3e:f8:01.

Which port is attached to the root bridge of MSTI 2?

A. ge-0/0/6

B. ge-0/0/9

C. ge-0/0/10

D. ge-0/0/12