New s VS Legacy DHCP Services

[Malik1]

Hi Experts

We ran a pre upgrade verification where we were presented with a warning  "Legacy DHCP Relay Services - Change in behavior in R80 and higher"

Description:
Legacy DHCP Relay services were found in the security rule base. Action is required in order for DHCP Relay to function properly post-upgrade.
Two possible options to solve the problem:
1). Remove legacy DHCP Relay services and add new DHCP Relay services. See sk104114 for instructions. This is the recommended action if managing only R77.20 gateways and above.
2). Keep legacy DHCP Relay services and make changes to the Gateways and the Security Management Servers. See sk98839 for instructions. Do this if managing any gateways which are older than R77.20.
Legacy DHCP Relay service(s):
bootpc, bootps, dhcp-relay, dhcp-rep-localmodule, dhcp-req-localmodule

So we opted for option 1 and migrated to new DHCP services (in test env). Now post upgrade from R77.30 to R80.30  we are being presented with a warning mentioned below

Policy installed on gateways of versions earlier than R77.20 run dhcp-request_ service with limited DHCP functionality. See sk98839 for more details.

(and similar for dhcp_reply)

We have 14 clusters and all are on R77.30 .We have a plan to migrate these to R80.30 but that will take time around 6 months (something political) 

So I need to understand the below.

1. What are the DHCP functionality limitations if we use new DHCP services where the mgmt servers is on r80.30 and gateway on R77.30 as i cant find it in the mentioned sk98839 . The SK describes the process to enable legacy services

2.Are there issues if we use the legacy DHCP services with mgmt server on r80.30 and gateways on r77.30. 

3.Can we neglect the warning presented in the PUV report.

Regards,

Sijeel Malik  

[MartinTzvetanov]

Legacy DHCP services stops SecureXL acceleration, the new dhcp services - don't