ISY Error Log questions

[TrojanHorse]

I've been experiencing what I can only best describe as some slow and flaky behavior from my ISY (e.g. Elk to ISY integration taking longer than usual, programs slow to trigger, Mobilinc taking longer to load status, especially for the Elk Alarm for example).  Not always slow, just sometimes, with no obvious (to me) reason why.  Running 5.0.16B.  

So, I opened my error log and I'm seeing a bunch of errors including:

System    -100    [DHCP] state=RENEW

System    -100    [DHCP] state=REBIND

Literally every 5 seconds there's an entry.  

Yesterday I was getting a bunch of the "REBIND" errors every 5 seconds until I got an entry in the error log - "System    -100    [DHCP] state=DISCOVER " at which point they stopped until today around 4:15pm when I started getting the "RENEW" error every 5 seconds.  

Any suggestions?  I have the ISY hardwired and set to DHCP with a reserved address on my router.

 

[Mecheng70]

Have you tried rebooting your cable modem, router and/or ISY?  See what that does.  

[TrojanHorse]

Have you tried rebooting your cable modem, router and/or ISY?  See what that does.  

Yes, all of the above. I actually use an Elk relay to power cycle my router and modem (separate devices). This is unusual I know but I had a connectivity issue (ISP related) before when I was out of town so I’ve been doing that for a couple years now and only started noticing the odd behavior recently. I suspected this could be an issue but the power cycles happen in the middle of the night and the errors are starting and stopping at other times. Tried rebooting the ISY as well which helped for maybe a day but then I continue to get these errors. The rest of the network seems to work as well as it always has.


Sent from my iPhone using Tapatalk

[TrojanHorse]

In case anyone else is using a Netgear router and getting these errors, I wanted to follow up on this. 

I downgraded the firmware and the DHCP reservation has been working now without errors for 48 hours.  Downgraded from 1.0.9.88 to 1.0.9.64 on the Netgear R7000. 

Edit: and my ISY now seems to be its snappy happy self again and the lag is gone.

[larryllix]

On 2/18/2020 at 10:10 PM, TrojanHorse said:

I've been experiencing what I can only best describe as some slow and flaky behavior from my ISY (e.g. Elk to ISY integration taking longer than usual, programs slow to trigger, Mobilinc taking longer to load status, especially for the Elk Alarm for example).  Not always slow, just sometimes, with no obvious (to me) reason why.  Running 5.0.16B.  

So, I opened my error log and I'm seeing a bunch of errors including:

System    -100    [DHCP] state=RENEW

System    -100    [DHCP] state=REBIND

Literally every 5 seconds there's an entry.  

Yesterday I was getting a bunch of the "REBIND" errors every 5 seconds until I got an entry in the error log - "System    -100    [DHCP] state=DISCOVER " at which point they stopped until today around 4:15pm when I started getting the "RENEW" error every 5 seconds.  

Any suggestions?  I have the ISY hardwired and set to DHCP with a reserved address on my router.

 

Have a look at this. It would seem if ISY cannot get an IP address from your router it can be crippled by being over busy. It may be your router somewhat too,  but ISY may not operate without a DHCP server, depending on setup. I have now manually locked my ISY to the IP address it would get anyway from my router.

 

[TrojanHorse]

Thanks for that info.

I don’t have a deep grasp of these issues but I should note that despite these errors and ISY slowness it still worked, just slower. I could ping the ISY at the reserved address. I guess the ISY and my router weren’t playing well together and the Netgear firmware downgrade fixed the problem for now. I guess I could set the ISY to be static at the same IP address but I wanted to avoid that.

I’m left wondering which piece of hardware is responsible for not playing nice. The Netgear firmware was released in July 2019. I didn’t notice any DHCP problems with other devices. I tend to update things when they’re available but didn’t keep close track of what I upgraded when. And the issue was intermittent as my daily router reboot would fix the problem for a while.

I was able to observe that the DHCP errors would begin at 12 hour intervals from the last ISY restart. The router reboot would fix them until then. So if the last time I restarted the ISY was say 11am (days or weeks ago, didn’t matter. I rarely reboot the ISY) and if I rebooted the router at 5am, there were no errors from 5am to 11am on a daily basis.




Sent from my iPhone using Tapatalk