Thank you sharing your experience - I'd like to get some more detail, and feed it back in to our development team.
What was the "original" version of SecureSphere, and what was the "upgrade" version?
Was this an MX or Gateaway?
If a Gateway, was this a physical Gateway or VM Gateway?
If a physical Gateway, was this copper / 1G, or Fiber/10G NICs?
Were the NICs in question the management NIC, bridge NICs or all NICs?
Thank you,
Erik
------------------------------
Erik Hersker
Sr. Technical Account Manager
------------------------------
Original Message:
Sent: 10-25-2019 11:09
From: cezmi çal
Subject: MTU size config survives but not enforced after upgrade/patch installation
According to this article https://imperva.my.salesforce.com/kA0D0000000PM7g?popup=true, if you change MTU size of interfaces, this config will survive after upgrade/patch installation.
This is true but config is not enforced after device first boot of post upgrade/patch installation and you need to reboot the appliance or run "service network restart" command manually.
I think, this enforcement can be included to upgrade/patch process and not to be required to run manually.
#AllImperva
------------------------------
cezmi çal
technical expert
Barikat Cyber Security
------------------------------