What is causing this problem?
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?
what is causing this OSPF adjacency problem?
Click the Exhibit button.
You are troubleshooting an OSPF adjacency problem between R1 and R2. Referring to the exhibit,
what is causing this OSPF adjacency problem?
What would cause this behavior?
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?
what is causing the adjacency to fail?
— 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 —
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?
what is causing the problem?
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?
What is causing the IPv4 BGP peering to stay in an active state?
— 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 —
What is causing the IPv4 BGP peering to stay in an active state?
What is causing the problem?
— Exhibit —
user@router> show route protocol bgp detail
inet.0: 20 destinations, 20 routes (19 active, 0 holddown, 1 hidden)
10.222.1.3/32 (1 entry, 1 announced)
*BGP Preference: 170/-101
Next hop type: Indirect
Address: 0x15ec944
Next-hop reference count: 3
Source: 1.1.1.1
Next hop type: Router, Next hop index: 536
Next hop: 1.1.1.1 via ge-0/0/1.0, selected
Protocol next hop: 1.1.1.1
Indirect next hop: 14081d0 262142
State:
Local AS: 65222 Peer AS: 65221
Age: 2:12 MetriC. 1 Metric2: 0
Task: BGP_65221.1.1.1.1+56417
Announcement bits (2): 0-KRT 4-Resolve tree 1
AS path: 65221 I
Communities: no-advertise
Accepted
Localpref: 100
Router ID. 10.222.1.1
— Exhibit —
You are troubleshooting a problem where an EBGP route is not being advertised to your local IBGP
peers. You have received a 10.222.1.3/32 route from an EBGP peer as shown in the Above, but the
route is not being advertised. What is causing the problem?
What is causing this problem?
— Exhibit —
user@R1> show bgp neighbor 172.10.3.201
Peer: 172.10.3.201+54714 AS 64512 Local: 172.10.3.202+179 AS 64513
Type: External State: Established Flags:
Last State: OpenConfirm Last Event: RecvKeepAlive
Last Error: None
Export: [ export ]
Options:
Local Address: 172.10.3.202 Holdtime: 90 Preference: 170 Local AS: 64513
Local System AS: 0
Number of flaps: 0
Peer ID. 10.247.194.254 Local ID. 10.247.24.6 Active Holdtime: 90
Keepalive Interval: 30 Peer index: 0
BFD. disabled, down
Local Interface: ge-0/0/0.500
NLRI for restart configured on peer: inet-unicast
NLRI advertised by peer: inet-unicast
NLRI for this session: inet-unicast
Peer supports Refresh capability (2)
Restart time configured on the peer: 120
Stale routes from peer are kept for: 300
Restart time requested by this peer: 120
NLRI that peer supports restart for: inet-unicast
NLRI that restart is negotiated for: inet-unicast
NLRI of received end-of-rib markers: inet-unicast
NLRI of all end-of-rib markers sent: inet-unicast
Peer supports 4 byte AS extension (peer-as 64512)
Peer does not support Addpath
Table inet.0 Bit: 30000
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: in sync
Active prefixes: 7
Received prefixes: 7
Accepted prefixes: 7
Suppressed due to damping: 0
Advertised prefixes: 30
Last traffic (seconds): Received 5 Sent 18 Checked 8
Input messages: Total 40 Updates 3 Refreshes 0 Octets 877
Output messages: Total 55 Updates 13 Refreshes 0 Octets 1764
Output Queue[2]: 0
— Exhibit —
A customer reports that BGP graceful restart is not working on R1. After a Routing Engine failover,
R1 did not set the restart state bit in its Open message. The customer provides the BGP neighbor
output shown in the Above. What is causing this problem?
Which action will resolve the problem?
Click the Exhibit button.
You are asked to assist with a problem with a new EBGP peering between Site 1 and Site 2. Referring
to the exhibit, Site 1 is not receiving the 100.100.0.0/16 routes from Site 2. Which action will resolve
the problem?
What should you do on R1 to resolve this problem?
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?