This case case was open due a Memory paging alert on the Exinda most probably caused by a Process called Avahi which is the process in charge of the feature for "www.findmyexinda.com". This feature is used by customers to locate the Exindas IP when it has been recently installed and the management port grabbed an IP from the DHCP.
In other words: When you put a Exinda online in the network it needs an IP to grant access to the WebUI. By going to "www.findmyexinda.com", the site will display any Exinda maagament IP detected for further access.
CauseIn such cases, you will be able to see similar logs:
Oct 30 15:19:18 Exinda4010 avahi-daemon: Received packet from invalid interface.
Oct 30 15:20:07 Exinda4010 avahi-daemon: Received packet from invalid interface.
Oct 30 15:20:18 Exinda4010 avahi-daemon: Received packet from invalid interface.
Oct 31 00:26:57 Exinda4010 avahi-daemon: Invalid response packet from host 10.41.221.121.
Oct 31 00:26:57 Exinda4010 avahi-daemon: Invalid response packet from host 10.41.221.124.
Oct 31 00:26:57 Exinda4010 avahi-daemon: Invalid response packet from host 10.41.221.122.
This is due to a software error with the avahi daemon itself and how handles multicast DNS.
As mentioned before the avahi process is merely used for installations on customer that do not know the IP they assigned to the management port.
The best way to get rid of these errors will be terminating the process, and as the process automatically restarts every time the System boots, we also need to add a command to disable the auto-launch sequence when the system reboots.
ResolutionPlease open a support case for assistance with this matter.
Internal NotesPlease type the following commands in CLI:
2. conf t
3. pm process avahi terminate
4. no pm process avahi launch auto
Given that the avahi is a process and needs a "pm" command to terminate or restart, the restricted License key for this device needs to be added before executing these commands.