topic Re: DHCP Relay stopped working after gateway upgrade to R80.20 in General Topics

DHCP Relay stopped working after gateway upgrade to R80.20

Noah_T — Tue, 05 May 2020 20:05:21 GMT

Team,

Last weekend we did OS Upgrade on SG 15600 Cluster ( Active/Standby setup ) from R77.30 to R80.20 and after the upgrade dhcp relay stopped working , offer packets were being dropped with error ( offer fw_postvm_chain_handler Reason: 'dhcp_request_code' drop ) . Drops were not seen on CLM Logs , but were seen via Zdebug commandmon cli.

we were using legacy dhcp services ( bootp, dhcp-rep-localmodule etc) and manual NAT rules as per SK98839. The MDS is on R80.10.

After we replaced all the legacy services with New dhcp services (dhcp-request, dhcp-reply ) dhcp relay started working.

As per SK98839 legacy services are still supported so I would like to know the reason why it stopped working as OS was upgraded on the gateways to R80.20.

Thank You.

Re: DHCP Relay stopped working after gateway upgrade to R80.20

JozkoMrkvicka — Wed, 06 May 2020 05:56:27 GMT

check sk98839 and search forfwx_dhcp_relay_nat parameter. Must be 1 after upgrade.

Re: DHCP Relay stopped working after gateway upgrade to R80.20

Noah_T — Wed, 06 May 2020 21:53:28 GMT

@JozkoMrkvicka

Thank You for your reply. fwx_dhcp_relay_nat not being 1 should be the reason. I have another Cluster upgrade this weekend and can confirm.

What is the significance of fwx_dhcp_relay_nat parameter ?

When using Legacy services as per sk98839 manual NAT rules are required but why are they not required when using New DHCP services ?

Re: DHCP Relay stopped working after gateway upgrade to R80.20

PhoneBoy — Thu, 07 May 2020 03:43:18 GMT

Most likely because the newer DHCP services actually handle this through their INSPECT handler, which the legacy services didn't have.