Dear all, I have a statically configured probe, FW version 4270. If the internet connection goes down/flaps the probe seems to get confused and stops communicating (is shown as Down) even when the connection is back up and stable, but can actually be pinged etc from inside and outside my network fine. I have a second probe that is on DHCP (FW 4280) on a different network, this one seems not to have the same issue, don't know which is the important differentiator. Wondering if anyone has similar issues and a solution other than switch it off and on again. Thanks to All, Kyriacos
On 1/27/12 13:33 , Kyriacos Sakkas wrote:
I have a statically configured probe, FW version 4270. If the internet connection goes down/flaps the probe seems to get confused and stops communicating (is shown as Down) even when the connection is back up and stable, but can actually be pinged etc from inside and outside my network fine.
I have a second probe that is on DHCP (FW 4280) on a different network, this one seems not to have the same issue, don't know which is the important differentiator.
Wondering if anyone has similar issues and a solution other than switch it off and on again.
Firmware version 4270 has an issue where if the connection to the controller goes down, it may not come back until the probe reboots. This fixed in 4280. It looks like your probe is now upgrading to 4280. Philip Homburg ps. it helps if you list probe ids when talking about specific probes. It saves me the time to figure out who you are and what probes you own.
On 1/27/12 13:33 , Kyriacos Sakkas wrote:
I have a statically configured probe, FW version 4270. If the internet connection goes down/flaps the probe seems to get confused and stops communicating (is shown as Down) even when the connection is back up and stable, but can actually be pinged etc from inside and outside my network fine.
I have a second probe that is on DHCP (FW 4280) on a different network, this one seems not to have the same issue, don't know which is the important differentiator.
Wondering if anyone has similar issues and a solution other than switch it off and on again.
Firmware version 4270 has an issue where if the connection to the controller goes down, it may not come back until the probe reboots. This fixed in 4280. It looks like your probe is now upgrading to 4280.
Philip Homburg
ps. it helps if you list probe ids when talking about specific probes. It saves me the time to figure out who you are and what probes you own. Thanks for the info. Will include probe ids in the future, was unsure of
On 27/01/2012 14:53, Philip Homburg wrote: the protocol. No been on the mailing list long. Kyriacos Sakkas
participants (2)
-
Kyriacos Sakkas -
Philip Homburg