Pakedge P2Es crash when Domotz isntalled

[installersteve]

Hi,

 

We have two Pakedge P2Es in one of our projects. We have found that when Domotz is installed they drop off the network within a couple of hours. Power cycling the P2Es is the only way to get them back on the network, but they drop off again within a couple of hours. We've tested this thoroughly, with Domotz out of the system they happily remain on the network, as soon as we reconnect Domotz to the system they both drop of the network. We've checked through all the cabling and even tried with different network switches in the system.

 

I'm assuming this is an issue with the way the pakedge devices respond to the (possibly frequency of) scanning that the Domotz agent does. The Pakedge units we have are a couple of years old and we haven't had chance to try new firmware on them yet.

 

I wonder if others have been using Domotz with P2Es and, if yes, how old their P2Es are? 

[martyn]

Hello,

 

We have a number of systems running Pakedge P8E units and they drop off the network also after a little while. A reboot cures it!

 

Hope Domotz can sort this out.

[martyn]

Would be great if Domotz would chip in on this topic?

[Silvio]

Apologies. We had simply missed this post!

Our dev team is going to investigate now.

 

 

[martyn]

Thanks - happy to test at our office etc if required.

 

 

[GeorgiTsatsev]

While we are investigating the issue I can suggest that you change the login credentials to something that is not the default ones and you have not entered on the app. This way it will result in a locked device(until you give it the right credentials) and won't poll the device anymore.

That will also disallow you control over the PDU from our config tab but it may fix the problem with the device going down. You can still use the click-to-enter functionality to control the PDU remotely for the time being.

 

[martyn]

I've been doing a lot of testing with this. It seems that when the Control4 Pakedge P2/8/20 driver is installed when a Domotz is running on the network, it knocks the P2/8/20 off the network after a while. I'd imagine this is possible due to user permission or the polling? Anyway hope that gives you more of a clue.

[JoshHarvey]

Did anyone get anywhere with this? We have a few sites with Pakedge installed, when we put in Domotz the Pakedge devices went offline within 12 hours. The only way to get these back online was to reboot them. We have one site with 2 P8's both with control4 drivers...one is offline while the other one is still online? We also have a P8 in our office, by removing the Control4 driver the P8 has stayed online.....any help would be greatly appreciated

[martyn]

We still have the problem on a couple of sites. Doesn't make any sense though as sites with similar setups are absolutely fine. Have tried everything from flashing firmware, different versions, etc..

[JoshHarvey]

Are your Control4 sites all on 2.9? all of ours are on 2.9 i wonder if this is part of the problem as 2.9 has caused us some other issues and inconsistency's. Do you have any sites where you have Domotz and Pakedge PDU's but no Control4 if so how have they behaved?

[martyn]

No it was happening before 2.9. We don't have any sites with Domotz and Pakedge PDU but no Control4.

[Silvio]

We can't replicate the issue at all.

Would you mind to write directly to Domotz support specifying all the exact configurations (models, firmware versions, driver...)?

In particular if you can notice any - even small - difference  between configurations working and those not working, that would help a lot.

Thank you,

Silvio

 

[punter16]

We were sent a Domotz Pro box to monitor a Luxul managed network that was misbehaving. The Domotz box raised the CPU utilization to 99% every 30 seconds. It wasn't completely killing the network but I'm sure it wasn't helping, especially when there were other issues. It is now disconnected.

 

I don't know if this is related but it threw Luxul for a loop.

[Tommaso]

Hi, 

 

we perform a scan every 30 seconds, sending some packets using different protocol of IPS. Anyway, even if you have hundreds of devices, these bunch of packets cannot kill a Luxul switch unless the network configuration keeps the packet in a loop inside the Luxul switch, so that it re-process endless (or after TTL iterations).

 

Can you share your Luxul configuration with our support?

[AgentSonore]

Hi guys,

did any one of you managed to find the reason why Pakedge IP PDUs are dropping from network and most likely crashing ?

 

Thanks a lot

 

Best regards

[GeorgiTsatsev]

Hi,

We still have not found out the exact cause of the Pakedge PDU problem but it is an ongoing investigation.

Currently we have noticed that on some Pakedge PDUs (same firmware, same model etc so we can't really find the distinguishing factor) due to high network traffic the PDU's stop working. It has been reported to us that it has happened with different drivers (for example a Control4 driver for this PDU) that are used to poll the device it can make the PDU unresponsive. 

 

Unfortunately, the PDU we have in the office doesn't go down even though we have at least 6 Domotz agents polling it so we cannot find out why it is happening on some customer's devices.

[ChristianDion]

Hi!

 

We have exactly the same issues with 2 brand new P20 installed on a site with a Domotz box, but we are still at the beginning of our diagnostics, we cannot be sure it's the Domotz yet. We will unplug the Domotz for 2 weeks to see if it happens again.

[Ronklootwijk]

There is a beta version for P2/P8/P20 that handles the data better. Pakedge tech support can probably assist you with that.