nerdexam
Check_Point

156-115.77 · Question #8

While troubleshooting a DHCP relay issue, you run a fw ctl zdebug drop and see the following output: ;[cpu_1];[fw_0];fw_log_drop: Packet proto=17 10.216.14.108:67 > 172.31.2.1:67 dropped by…

The correct answer is D. A link collision due to more than one NAT symbolic link being created for connections returning. See the full explanation below for the reasoning.

Question

While troubleshooting a DHCP relay issue, you run a fw ctl zdebug drop and see the following output:

;[cpu_1];[fw_0];fw_log_drop: Packet proto=17 10.216.14.108:67 > 172.31.2.1:67 dropped by fw_handle_first_packet Reason:

fwconn_init_links (INBOUND) failed; Where 10.216.14.108 is the IP address of the DHCP server and 172.31.2.1 is the VIP of the Cluster. What is the most likely cause of this drop?

Options

  • AAn inbound collision due to a connections table check on pre-existing connections.
  • BAn outbound collision due to a Rule Base check, and dropped by incorrectly configuring DHCP in
  • CA link collision due to more than one NAT symbolic link being created for outgoing connections to
  • DA link collision due to more than one NAT symbolic link being created for connections returning

How the community answered

(61 responses)
  • A
    7% (4)
  • B
    5% (3)
  • C
    13% (8)
  • D
    75% (46)

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 156-115.77 Practice