最新的Juniper JN0-694免費考試真題

問題1

-- Exhibit --
Jun 12 02:56:06 R1 rpd[60735]: RPD_OSPF_NBRDOWN: OSPF neighbor 10.50.10.25 (realm ospf-v2 fe-0/0/4.0 area 0.0.0.0) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode)
Jun 12 02:59:36 R1 rpd[60735]: RPD_OSPF_NBRUP: OSPF neighbor 10.50.10.25 (realm ospf-v2 fe-0/0/4.0 area 0.0.0.0) state changed from Init to ExStart due to 2WayRcvd (event reason: neighbor detected this router)
Jun 12 02:59:36 R1 rpd[60735]: RPD_OSPF_NBRUP: OSPF neighbor 10.50.10.25 (realm ospf-v2 fe-0/0/4.0 area 0.0.0.0) state changed from Exchange to Full due to ExchangeDone (event reason: DBD exchange of slave completed)
-- Exhibit -
Click the Exhibit button.
You notice that there is a problem with the OSPF adjacency between two routers, R1 and R2. The relevant system logs from R1 are shown in the exhibit.
What would cause this behavior?

A. R1's interface went down and came back up.

B. R2 was dropping R1's OSPF hello packets.

C. R1 was dropping R2's OSPF hello packets.

D. There is an OSPF hello timer mismatch between the two routers.

正確答案: B

問題2

-- Exhibit -user@router# run show log ospf-test ... Jun 10 22:35:38.598494 OSPF sent Hello 10.100.0.1 -> 224.0.0.5 (ge-1/0/3.1000 IFL 77
area 0.0.0.0) Jun 10 22:35:38.598520 Version 2, length 44, ID 10.100.1.2, area 0.0.0.0 Jun 10 22:35:38.598543 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128 Jun 10 22:35:38.598564 dead_ivl 32, DR 10.100.0.1, BDR 0.0.0.0 Jun 10 22:35:41.522956 OSPF periodic xmit from 10.200.26.1 to 224.0.0.5 (IFL
2684276196 area 0.0.0.1)
Jun 10 22:35:42.798220 OSPF rcvd Hello 10.100.0.2 -> 224.0.0.5 (ge-1/0/3.1000 IFL 77
area 0.0.0.0)
Jun 10 22:35:42.798311 Version 2, length 48, ID 10.100.1.1, area 0.0.0.0
Jun 10 22:35:42.798334 checksum 0x0, authtype 0
Jun 10 22:35:42.798356 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
Jun 10 22:35:42.798377 dead_ivl 40, DR 10.100.0.2, BDR 10.100.0.1
Jun 10 22:35:45.189034 OSPF rcvd Hello 10.100.0.2 -> 224.0.0.5 (ge-1/0/3.1000 IFL 77 area 0.0.0.0) Jun 10 22:35:45.189097 Version 2, length 44, ID 10.100.1.1, area 0.0.0.0 Jun 10 22:35:45.189118 checksum 0x0, authtype 0 Jun 10 22:35:45.189140 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128 Jun 10 22:35:45.189162 dead_ivl 40, DR 10.100.0.2, BDR 0.0.0.0
Jun 10 22:35:45.196969 OSPF DR is 10.100.1.2, BDR is 0.0.0.0 Jun 10 22:35:45.197050 OSPF sent Hello 10.200.26.1 -> 224.0.0.5 (ge-1/0/0.0 IFL 69 area 0.0.0.1)
Jun 10 22:35:45.197076 Version 2, length 44, ID 10.100.1.2, area 0.0.0.1 Jun 10 22:35:45.197098 mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128 Jun 10 22:35:45.197119 dead_ivl 40, DR 10.200.26.1, BDR 0.0.0.0 Jun 10 22:35:46.746900 OSPF periodic xmit from 10.100.0.1 to 224.0.0.5 (IFL 2684276196
area 0.0.0.0) -- Exhibit -
Click the Exhibit button.
Referring to the exhibit, what is preventing the OSPF neighborship with two directly connected routers using interface ge-1/0/3 from reaching the full state?

A. hello interval mismatch

B. subnet mismatch

C. dead interval mismatch

D. authentication type mismatch

正確答案: C

問題3

-- 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 incorrect IP address.

D. The peer has an NLRI mismatch.

正確答案: D

問題4

-- 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/9

B. ge-0/0/12

C. ge-0/0/10

D. ge-0/0/6

正確答案: B

問題5

You recently deployed two Anycast RPs. Multicast clients in the network are reporting that
they are receiving traffic from some, but not all, multicast sources.
What are two solutions for this problem? (Choose two.)

A. Configure rp-set for the Anycast RPs.

B. Configure MSDP between the Anycast RPs.

C. Configure the network to always use the RPT and not switch over to the SPT.

D. Configure multicast BGP between the Anycast RPs.

正確答案: A,B

問題6

-- Exhibit - -- Exhibit -

Click the Exhibit button.
Your network has two connections to your ISP. You have been asked to load-balance traffic across both links that connect to your ISP. You have enabled multipath for this peer, but you are still not getting the expected load balancing.
Given the information shown in the exhibit, what else must you do?

A. Configure and apply a load-balancing policy.

B. Create a policy to manually change the next hops.

C. Enable the keep all parameter.

D. Change the multipath parameter to multihop.

正確答案: A

最新的Juniper Enterprise Routing and Switching Support, Professional (JNCSP-ENT) - JN0-694免費考試真題

聯系我們

站內鏈接

最新更新