C1M1 unusual IP address error

[Jeff Caulk]

I’ve had my M1Gold with a C1M1 running flawlessly for about 6 months.

I was using a DHCP reservation in my router to provide a static IP address of 192.168.0.101.  Everything worked correctly.  I had IP connectivity through Elk RP and Elk link, the monitoring company had good cell and IP comms.

This past weekend I had to reboot my network switch and router.  When it came back online I started getting the ETHERNET TROUBLE alert on my key pads.

I rebooted the entire Elk system, within minutes the trouble alert would return.

The C1M1 was reporting b 4, and E 7.  Prior to the E 7 error, it would display b 4, then begin displaying the IP address “a 192.168.0.10…” before it finished showing the IP address the led displayed the circular segment behavior, then the E 7 displayed.

The router saw the C1M1 MAC address and asigned the x.x.x.101 IP address.  Elk RP could see the C1M1 using the find function, and reported the IP address as x.x.x.101. But Elk RP could not connect to the M1.  So it appeared the IP side of the C1M1 was working but there was a problem with the serial connection to the M1.  I cehcked all the cables and connections, not had been disturbed during the switch and router reboot, but I checked to ensure they were all connected.

Doing some searching here for the E 7 error, I power cycled just the C1M1.  That did not fix the issue.

I went into the installation menu and performed the module registration, the E 7 and ETHERNET ERROR cleared temporarily, but I could still not get into the M1 through Elk RP.  The error returned after a few minutes.

Finally, I removed the DHCP IP reservation in the router and rebooted the M1.  The system powered up, obtained an IP Address of 192.168.0.53, was located by Elk RP and I was able to log in to the M1.  I let the system run an hour and the error did not return.

I added a new DHCP reservation of 192.168.0.100 and rebooted the system.  Again, the system powered up, received the x.x.x.100 IP address, was discoverable and I was able to,log in through Elk RP.

I modified the DHCP reservation back to 192.168.0.101 and rebooted the system, and the error immediately returned.

I modified the reservation back to x.x.x.100, rebooted the system, it worked normally and has been running 20 hours with no errors.

 

The original IP address reservation of x.x.x.101 was working for months, but after the network reboot seems to have induced an error in the system that was not cleared by power cycling/rebooting.

Changing the address reservation to something other than x.x.x.101 seems to have cleared the error.

 

 

 

 

[Brad Weeks]

Could another device on your network have been assigned x.x.x.101?

[Jeff Caulk]

There was/is not another device listed in the router client table with that address.
The DHCP pool is 21-99 – all the addresses 100-255 are static reservations and no other device has the 101 address.

The 101 address was the originally assigned address the device has been using for 6 months.    101 is outside the DHCP pool so no device could be assigned that address by the DHCP server.

[Author]

Posts