You are configuring an IBGP peer between R1 and R2. The BGP neighbor cannot be established.
Referring to the exhibit, which configuration change will resolve this problem?
A. Configure local-as on R1 and R2.
B. Configure router-id on R1 and R2.
C. Configure family inet-unicast on R1 and R2.
D. Configure local-address on R1 and R2.
正解:C
質問 2:
-- Exhibit - -- Exhibit -
Click the Exhibit button.
On R1, the interface fe-0/0/1 is assigned to the default routing instance and fe-0/0/2 is assigned to a virtual router instance named VR-1.
Referring to the exhibit, the static route 200.200.200.200/32 is missing from the routing table of the default routing instance.
What should you do on R1 to resolve this problem?
A. Create a RIB group to import the direct route 70.1.1.0/24 to both the default instance and the VR-1 instance.
B. Configure an import policy to import the route 200.200.200.200/32 to the VR-1 instance.
C. Change the instance type on VR-1 to forwarding.
D. Configure a static ARP entry for address 70.1.1.1.
正解:A
質問 3:
-- Exhibit -user@R1> show ospf neighbor Address Interface State ID Pri Dead
10.222.0.2 ge-0/0/1.0 Init 10.222.1.2 128 32
user@R1> show ospf interface detail Interface State Area DR ID BDR ID Nbrs ge-0/0/1.0 DR 0.0.0.0 10.222.1.1 0.0.0.0 1 Type: LAN, Address: 10.222.0.1, Mask: 255.255.255.252, MTU: 1500, Cost: 1 DR addr: 10.222.0.1, Priority: 128 Adj count: 0 Hello: 10, DeaD. 40, ReXmit: 5, Not Stub Auth type: MD5, Active key ID. 10, Start time: 1970 Jan 1 00:00:00 UTC Protection type: None Topology default (ID 0) -> Cost: 1 lo0.0 DR 0.0.0.0 10.222.1.1 0.0.0.0 0 Type: LAN, Address: 10.222.1.1, Mask: 255.255.255.255, MTU: 65535, Cost: 0 DR addr: 10.222.1.1, Priority: 128 Adj count: 0 Hello: 10, DeaD. 40, ReXmit: 5, Not Stub Auth type: None Protection type: None Topology default (ID 0) -> Cost: 0
user@R2> show ospf neighbor
user@R2> show ospf interface detail Interface State Area DR ID BDR ID Nbrs ge-0/0/1.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 0 Type: P2P, Address: 10.222.0.2, Mask: 255.255.255.252, MTU: 1500, Cost: 1 Adj count: 0 Hello: 10, DeaD. 40, ReXmit: 5, Not Stub Auth type: MD5, Active key ID. 10, Start time: 1970 Jan 1 00:00:00 UTC Protection type: None Topology default (ID 0) -> Cost: 1 lo0.0 DR 0.0.0.0 10.222.1.2 0.0.0.0 0 Type: LAN, Address: 10.222.1.2, Mask: 255.255.255.255, MTU: 65535, Cost: 0 DR addr: 10.222.1.2, Priority: 128 Adj count: 0 Hello: 10, DeaD. 40, ReXmit: 5, Not Stub Auth type: None Protection type: None Topology default (ID 0) -> Cost: 0 -- Exhibit -
Click the Exhibit button.
You are trying to establish an OSPF adjacency between R1 and R2, but the adjacency does not establish.
Referring to the exhibit, what is causing the adjacency to fail?
A. The IP subnet mask is mismatched between R1 and R2.
B. The MD5 key ID values are mismatched between R1 and R2.
C. The interface type is mismatched between R1 and R2.
D. R1 has both family inet and family iso configured on the link toward R2.
正解:C
質問 4:
-- Exhibit - -- Exhibit -
Click the Exhibit button.
You are asked to configure a multihop EBGP peering to a loopback address of your ISP. The peering does not establish, and the ISP has verified that the settings are correct on their side.
Referring to the exhibit, what is causing the problem?
A. The peer-as parameter is misconfigured.
B. The static route is misconfigured.
C. The neighbor parameter is misconfigured.
D. The local-address parameter is misconfigured.
正解:B
質問 5:
-- 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 does not support 4-byte AS values.
B. The peer has an incorrect IP address.
C. The peer has an NLRI mismatch.
D. The peer AS is incorrect.
正解:C
Ootake -
合格率は高いです。順調にJN0-694試験をパスしました。こころから感謝します。