Unable to determine a local IP address for any OnPlus Network Agent on your current network.

Answered Question
Sep 19th, 2012

Hi,

I am trying to activate a new Onplus appliance and I get the error noted above. I have factory reset the device to no avail. I can see that the device has got an IP address via DHCP and can ping it. I cannot get to it via a web browser locally either.

The device turns up in the Portal and also shows that it has discovered 2 routers. See attached screenshots

Can some help?

Thanks

Shailen

I have this problem too.
0 votes
Correct Answer by afullfor about 2 years 7 months ago

Hi Shailen,

I took a look at the logs on failsafe.imageboot.com for attempts from 64:00:F1:21:18:BC and found just a few. Looks like all but one came from me or our support folks.  The other came from an IP allocated from NZ Telecom.  Hopefully that is you!  I was able to trigger a successful transfer, the others transferred zero bytes.  I suspect these were test attempts from browsers and were interrupted.

Based on this, the ON100 is not reaching the internet for some reason.  It appears none of the several thousand attempts from the device reached the server.  This also explains why you are not seeing the activation entry, which depends on the ON100 posting its status to our activation service.

So, we have to figure out why the device is not able to reach the internet.  It could be that it is not getting a gateway or DNS sevrers from DHCP or there is some filtering on the outbound path, or possibly bad hardware.

As you have the IP address, can you get a computer set up the same way (via the same DHCP server, switch, etc) and see if you can access the URL above?  It should return you a 45,086,817 byte file.

Andy

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (2 ratings)
Michael Holloway Thu, 09/20/2012 - 06:17

Hi Shailen,

The two routers listed in your screenshot were learned via Scanner (the green button on that page) and not via the the On100. It sounds as though the ON100 is having a problem with it's software load, and may require a full factory reset (press reset button for 15 seconds, then wait 20 minutes as it downloads software). You might try accessing the debug screen by surfing to the device on port 81 (i.e. http://192.168.0.4:81) to see if the device is even partially booting.  If not, this could be a bad unit which might require RMA. If the factory reset fails on that network, you might want to try the procedure on a separate network, perhaps a simple one with no VLANs.

-mike

SHAWN EFTINK Thu, 09/20/2012 - 06:26

Shailen,

I'm not sure if this applies or not, but I was running into a similiar issue with some deployments.  The issue turned out to be that all the access ports on the switch were configured to include another VLAN.  In our case it was a voice VLAN as it was assumed a Cisco phone was going to be plugged into it and a workstation plugged into the phone.  This was causing the ON100 to pull DHCP from both the data VLAN and the Voice VLAN and even though I could ping it, I could never get to the web page.  Once I removed the Voice VLAN from that interface and did a "shutdown/no shutdown" on the interface to cause the ON100 to request DHCP again, everything started working like it was supposed to.  You can get access to all the VLANs after the fact by switching the interface to "switchport mode trunk" after you get everything activated.  To keep it clean from the beginning and minimze issues, the interface needs to be in "switchport mode access" and only have access to the default data VLAN. Just another thought to consider.

Michael Holloway Thu, 09/20/2012 - 08:15

Great pro-tip Shawn, thanks for sharing it.

shailen-tpnl Thu, 09/20/2012 - 18:06

Hi Mike,

Tried Shawn's tip but no go the device is getting an IP address from the Data VLAN not the phone VLAN. Other device on the Data VLAN can get to the internet.

I then looked at the debug log as you pointed out and found the log full with the messages Atempt# below.

Thoughts..

begining of log

  • 2012-09-19:05:02:40 ON100_6400F12118BC
  • 2012-09-19:05:02:48 INFO: Starting HTTPD - Status info now available
  • 2012-09-19:05:02:48 NOTE: ubiattach was successful to ubi0
  • 2012-09-19:05:02:48 NOTE: mknod was successful for /dev/ubi0
  • 2012-09-19:05:02:48 INFO: Starting mount of internal flash .... ubi0 onto /mnt/INTFLASH
  • 2012-09-19:05:02:49 flash_mount_done
  • 2012-09-19:05:02:49 INFO: .... successfully completed mount
  • 2012-09-19:05:02:49 dhcp-done
  • 2012-09-19:05:02:49 INFO: Attempting to mount /dev/sda1 flash device
  • 2012-09-19:05:02:49 EXTERNAL_FLASH_NO_MAGIC
  • 2012-09-19:05:02:49 NO_OVERIDE_DETECTED
  • 2012-09-19:05:02:49 MISSING_CRAMFS_FAILSAFE_TIME
  • 2012-09-19:05:02:49 ERRR: No CRAMFS file, we have run out of options .... failsafe time
  • 2012-09-19:05:02:49 dhcp-done
  • 2012-09-19:05:02:49 INFO: Beginning fail safe recovery
  • 2012-09-19:05:02:49 INFO: Cleaning up left-over rogue processes ... should already have stopped
  • 2012-09-19:05:02:52 INFO: Beginning reformat of internal flash ....
  • 2012-09-19:05:02:52 NOTE: Detached the UBI volume from mtd6
  • 2012-09-19:05:03:28 NOTE: UBI Format completed
  • 2012-09-19:05:03:28 NOTE: ubiattach was successful to ubi0
  • 2012-09-19:05:03:28 NOTE: mknod was successful for /dev/ubi0
  • 2012-09-19:05:03:28 NOTE: ubimkvol was successful for /dev/ubi0
  • 2012-09-19:05:03:29 INFO: .... Format Completed

SNIP and went to end of log

Correct Answer
afullfor Fri, 09/21/2012 - 07:59

Hi Shailen,

I took a look at the logs on failsafe.imageboot.com for attempts from 64:00:F1:21:18:BC and found just a few. Looks like all but one came from me or our support folks.  The other came from an IP allocated from NZ Telecom.  Hopefully that is you!  I was able to trigger a successful transfer, the others transferred zero bytes.  I suspect these were test attempts from browsers and were interrupted.

Based on this, the ON100 is not reaching the internet for some reason.  It appears none of the several thousand attempts from the device reached the server.  This also explains why you are not seeing the activation entry, which depends on the ON100 posting its status to our activation service.

So, we have to figure out why the device is not able to reach the internet.  It could be that it is not getting a gateway or DNS sevrers from DHCP or there is some filtering on the outbound path, or possibly bad hardware.

As you have the IP address, can you get a computer set up the same way (via the same DHCP server, switch, etc) and see if you can access the URL above?  It should return you a 45,086,817 byte file.

Andy

SHAWN EFTINK Fri, 09/21/2012 - 08:08

Shailen,

I'm sure this may go without saying, but also ensure the ports that need to be open for outbound communication from the ON100 to the internet are not being blocked.  Michael Holloway laid them out nicely in this post.

https://supportforums.cisco.com/message/3579381#3579381

Michael Holloway Fri, 09/21/2012 - 08:39

Not much I can add to what Andy and Shawn suggested here, thanks guys. I also suspect that this issue might be due to an overly-aggressive content firewall, or less likely a faulty allocation of DNS or gateway IP from the DHCP server.

-mike

shailen-tpnl Mon, 09/24/2012 - 22:39

Hi Andy,

Yep you were correct the device was not getting out to the internet. Those NZ Telecom connections was me testing the url.

Basically the device was getting an IP from the LAN DHCP server with static assignment however the IT admin put an incorrect default gateway/router in when he did the static assignment.

The device is now doing it's firmware update :-)

Thanks for your assistance, much appreciated.

Regards

Shailen

afullfor Tue, 09/25/2012 - 06:55

Great to hear it is working!

a.

Actions

Login or Register to take actions

This Discussion

Posted September 19, 2012 at 7:29 PM
Stats:
Replies:9 Overall Rating:
Views:540 Votes:0
Shares:0
Tags: install, on100
+

Related Content