user@host> show log ibgp-trace … Jun 12 10:21:08
10:21:08.367627:CID-0:RT:192.168.2.1/49170->192.168.1.1/179;6> matched filter
ibgp-traffic: Jun 12 10:21:08 10:21:08.367747:CID-0:RT:packet [64] ipid = 11792,
@423f741c Jun 12 10:21:08 10:21:08.367747:CID-0:RT:—- flow_process_pkt: (thd 2):
flow_ctxt type 15, common flag 0x0, mbuf 0x423f7200, rtbl_idx = 0 Jun 12 10:21:08
10:21:08.367747:CID-0:RT: flow process pak fast ifl 71 in_ifp ge-0/0/3.0 Jun 12 10:21:08
10:21:08.367747:CID-0:RT: ge-0/0/3.0:192.168.2.1/49170->192.168.1.1/179, tcp, flag 2 syn
Jun 12 10:21:08 10:21:08.367747:CID-0:RT: find flow: table 0x4f161150, hash
15898(0xffff), sa 192.168.2.1, da 192.168.1.1, sp 49170, dp 179, proto 6, tok 7 Jun 12
10:21:08 10:21:08.367747:CID-0:RT: no session found, start first path. in_tunnel – 0,
from_cp_flag – 0 Jun 12 10:21:08 10:21:08.367747:CID-0:RT: flow_first_create_session Jun
12 10:21:08 10:21:08.367747:CID-0:RT:Doing DESTINATION addr route-lookup Jun 12
10:21:08 10:21:08.367747:CID-0:RT: routed (x_dst_ip 192.168.1.1) from trust (ge-0/0/3.0 in
0) to lo0.0, Next-hop: 92.168.1.1 Jun 12 10:21:08
10:21:08.367747:CID-0:RT:flow_first_policy_search: policy search from zone trust-> zone
loopback-zone (0x0,0xc01200b3,0xb3) Jun 12 10:21:08 10:21:08.367747:CID-0:RT: policy
has timeout 900 Jun 12 10:21:08 10:21:08.367747:CID-0:RT: app 0, timeout 1800s, curr
ageout 20s Jun 12 10:21:08 10:21:08.367747:CID-0:RT: permitted by policy allow-bgp(8)
Jun 12 10:21:08 10:21:08.368250:CID-0:RT: flow_first_install_session======>
0x5394a110 Jun 12 10:21:08 10:21:08.368250:CID-0:RT:flow_first_service_lookup():
natp(0x5394a110): app_id, 0(0). Jun 12 10:21:08 10:21:08.368250:CID-0:RT: service
lookup identified service 0. Jun 12 10:21:08 10:21:08.368250:CID-0:RT:
flow_first_final_check: in 0/3.0>, out Jun 12 10:21:08 10:21:08.368250:CID-0:RT: existing
vector list 2-49c75930. Jun 12 10:21:08 10:21:08.368250:CID-0:RT: Session (id:137)
created for first pak 2 Jun 12 10:21:08 10:21:08.368250:CID-0:RT: post addr xlation:
192.168.2.1->192.168.1.1. Jun 12 10:21:08 10:21:08.368250:CID-0:RT:check self-traffic on
lo0.0, in_tunnel 0x0 Jun 12 10:21:08 10:21:08.368250:CID-0:RT:retcode: 0xa01 Jun 12
10:21:08 10:21:08.368250:CID-0:RT:pak_for_self : proto 6, dst port 179, action 0x0 Jun 12
10:21:08 10:21:08.368250:CID-0:RT: flow_first_create_session Jun 12 10:21:08
10:21:08.368250:CID-0:RT: flow_first_in_dst_nat: in , out A> dst_adr 192.168.1.1, sp
49170, dp 179 Jun 12 10:21:08 10:21:08.368752:CID-0:RT: chose interface lo0.0 as
incoming nat if. Jun 12 10:21:08 10:21:08.368752:CID-0:RT: packet droppeD. for self but
not interested Jun 12 10:21:08 10:21:08.368752:CID-0:RT: packet dropped, packet
droppeD. for self but not interested. Jun 12 10:21:08 10:21:08.368752:CID-0:RT: flow find
session returns error. Jun 12 10:21:08 10:21:08.368752:CID-0:RT: —– flow_process_pkt rc
0x7 (fp rc -1) You are asked to troubleshoot a new IBGP peering problem on your SRX
Series device. The IBGP peering is not establishing. Referring to the outputs in the exhibit,
what is causing the problem?
A.
NAT is translating the destination IP addresses.
B.
The loopback interface does not have the correct IP address assigned to it.
C.
The host inbound traffic configuration does not include the BGP parameter.
D.
The traffic is not being accepted by the security policy.