I'm deploying RED devices with static IPs.
When I first started using these about a year ago I would configure the RED on my ASG, and then bring up the red on a DHCP network to test.
The device would boot, the tunnel would come up once, it would download it's config and then it would reboot and just the System and Router lights would flash, indicating an invalid static IP config, as expected since they are not on site yet. Then I'd ship the RED out to a site and it would work.
About a month or two ago, I noticed that the REDs (v2) started to behave differently. The first time I turned them on, on a dhcp network, they would boot all the way up on DHCP (all 4 lights lit) and stay that way. I would have to manually reboot them and then they would come up with the invalid static IP error indicator, which indicated to me that they got their static IP config. They worked when I sent them to their site.
Now today, after a recent 3.03 ASG upgrade, I am trying to configure a new RED with a static IP and it comes up with all 4 lights every single time I reboot it. I'm not sure if it's getting it's static IP config or not.... How do I tell if it's got the correct config? Is this the expected behavior now? If so, Where was I supposed to look to be aware of this change? I don't see it mentioned in the 3.00 release notes. I can't even find the 3.03 release notes.
This thread was automatically locked due to age.