Remote Ethernet Device (RED…
How to reset a RED with an…
Release Notes & News
This group requires membership for participation - click to join
8 Jun 2011 12:26 PM
Have a cool product idea or improvement?
We'd love to hear about it! Click
to go to the product suggestion community
How to reset a RED with an invalid static IP?
I've got a RED that I need to redeploy but it has an invalid static IP. Is there a way to 'reset' it without jumping through hoops? The manual implies that it will fall back to DHCP but this doesn't seem to be the case. It just keeps rebooting and flashing the System and Internet lights.
The only thing I can think of is to fake the invalid network with another NAT router. I would like to avoid this if possible.... I'll need to do this quite often as I will have 30 REDS deployed with static IPs.
9 Jun 2011 7:26 AM
Nevermind. The device DOES fallback to DHCP and will get a new config. You just have to modify the config.
21 Sep 2011 12:41 PM
I have also this Problem - there´s a easy way to shoot down a Static - IP RED - just made the failure setting Device and Interface config to Mask /32 - this was uploaded to the RED and since then there is no way to get a new config to the red
Have anybody an idea how to reset the RED?
Thank you very much.
21 Sep 2011 2:02 PM
In reply to
Ask and Ye shall receive -- I had to do this to a unit (which later turned out to just be defective)...
There is one way to completely blow the configuration from the RED and force it to go out the provisioning server to pull a new config, as just using the unlock code may not work since the RED always goes back to the its previously connected ASG and if it finds that, it will be happy and not go out to find a new config.
The way I have it setup here is I just created a new interface on a spare NIC on our Astaro. Then create 2 PF rules:
1.) NETWORK -- ANY -- RED.ASTARO.COM -- AlLOW
2.) NETWORK -- ANY -- ANY -- DROP
You could do it by the IP the RED gets as well but we just do so many here I found it easier to just create a new network for our warehouse.
Then just plug the REDs WAN port into that interface and let it sit, watch the PF log and watch it drop a few times then it will be back to its factory state and will go out to the provisioning server next time.
22 Sep 2011 4:06 AM
If a RED can't connect to neither ASG or provisioning service with its static config, it will do a one-shot DHCP fallback. But due to the connection checks timing out this can take 3-4 minutes, so you have to be patient.