IP Address reset?

Keith,

Please forgive the tardiness of my reply, I got caught up in a few issues yesterday in the office. Also, please forgive the length of this post, its going to be a bit long.

After talking with a few of the developers around here, there is an issue in our code with switching between different IP addresses that will cause problems with fixture communication in the CMA. Efforts are being made as we speak to clean this code up and hopefull eliminate these problems.

I was able to recreate your issue here in the office today pretty much exactly as you described it. In order to do this, I booted the DL2 with no network connection at all (meaning no Cat5 cable plugged into it). When it booted, the IP address was assigned at 127.0.0.1. This is normal, as this is the default IP address for a computer when no network is connected (essentially its "home"). I then plugged the DL2 into a network that contained no router (meaning it should auto-ip itself to a 169.254.x.x address). After a brief time I saw the fixture in my CMA, but then started to witness the jumping back and forth between IP addresses that you described. Communication with the fixture in CMA didn't work, I couldn't load content or look at the configuration, etc.

I then powered down the fixture, and booted it again, this time with the network connected. After booting, it had a 169.254.x.x IP address, and everything worked as it should in the CMA.

I think the issue here is the state of your network when the DL2s are booted. The DL2s need a good connection right when they boot. They can't be booted first, then plugged into a network (or have the network switch plugged in after they are booted). I would first of all check to make sure you have good link lights on your switch for each one of your fixtures. Also, make sure that the switch is powered on and completely up and running before booting your DL2s. If you are still having issues, trying to swap your switch out for another would be a good troubleshooting measure.

You mentioned that connecting with your laptop directly, then doing a reboot on the computer would make everything work correctly. This is because the network connection was there when the DL2 booted. Making sure the network is in good shape before booting the computers should solve this issue. Also, our next round of software should make the DL2 far less sensitive to the problem.

Please let me know what you find and I'll do my best to help.

Keith,

Please forgive the tardiness of my reply, I got caught up in a few issues yesterday in the office. Also, please forgive the length of this post, its going to be a bit long.

After talking with a few of the developers around here, there is an issue in our code with switching between different IP addresses that will cause problems with fixture communication in the CMA. Efforts are being made as we speak to clean this code up and hopefull eliminate these problems.

I was able to recreate your issue here in the office today pretty much exactly as you described it. In order to do this, I booted the DL2 with no network connection at all (meaning no Cat5 cable plugged into it). When it booted, the IP address was assigned at 127.0.0.1. This is normal, as this is the default IP address for a computer when no network is connected (essentially its "home"). I then plugged the DL2 into a network that contained no router (meaning it should auto-ip itself to a 169.254.x.x address). After a brief time I saw the fixture in my CMA, but then started to witness the jumping back and forth between IP addresses that you described. Communication with the fixture in CMA didn't work, I couldn't load content or look at the configuration, etc.

I then powered down the fixture, and booted it again, this time with the network connected. After booting, it had a 169.254.x.x IP address, and everything worked as it should in the CMA.

I think the issue here is the state of your network when the DL2s are booted. The DL2s need a good connection right when they boot. They can't be booted first, then plugged into a network (or have the network switch plugged in after they are booted). I would first of all check to make sure you have good link lights on your switch for each one of your fixtures. Also, make sure that the switch is powered on and completely up and running before booting your DL2s. If you are still having issues, trying to swap your switch out for another would be a good troubleshooting measure.

You mentioned that connecting with your laptop directly, then doing a reboot on the computer would make everything work correctly. This is because the network connection was there when the DL2 booted. Making sure the network is in good shape before booting the computers should solve this issue. Also, our next round of software should make the DL2 far less sensitive to the problem.

Please let me know what you find and I'll do my best to help.