SInce my RED_10 device updated to the latest firmware (which was delivered with the 8.970 up2date), the RED device seems not to correctly update its configuration any more from the RED provisioning servers. Especially the "hub hostname" is not fetched any more (I din´ßt test other parameters).
Environment:
- RED-10 device was bound to a UTM9 beta
- after having upgraded the UTM to 8.970, the RED device updated its firmware, too [correct]
- afterwards I wanted to change to hub hostname/hub ip adreess of the device (it should connect to a different UTM now). so I changed this in the UTM "RED Management". After applying the changes, the red logfile told me: uploaded changes to registry server.
- I checked with the red-db fronted that the changed IP addres was correctly set in the red registry server
- the RED-devic still tried to connect to the "old" hub (which was shut down, so the red device was NOT getting any subccessfull connection!)
- however, after 10 minutes, it still did not connect to the NEW UTM hub
- I checked with tcpdump the communication of the red device to the rest of the world any saaw that it still tries to connect to the old huib hostname. after this is unsuccessfull, it seems to conenct to the registry service, and exchenages a bunch ofpackets on port 3400 with the registry. then it reboots. but after the reboot it still connects to the OLD ip adress
- I checked on red-db that there is NO configuration fetch any more. ALthough tcpdump shows me that the red device is talking to the registry, there seems to go something wrong and the change is not really downloaded to the RED device
- I cross-checked with the ssh debugging console access on the RED device itself and saw that in /astaro/cfg/hub_hostname still the old ip adress is contained.
SO it seems either the communication between RED and registry server is broken or the updated configuratiuon is not wirtten correctly to /astaro/cfg/hub_hostname
Elmar
Environment:
- RED-10 device was bound to a UTM9 beta
- after having upgraded the UTM to 8.970, the RED device updated its firmware, too [correct]
- afterwards I wanted to change to hub hostname/hub ip adreess of the device (it should connect to a different UTM now). so I changed this in the UTM "RED Management". After applying the changes, the red logfile told me: uploaded changes to registry server.
- I checked with the red-db fronted that the changed IP addres was correctly set in the red registry server
- the RED-devic still tried to connect to the "old" hub (which was shut down, so the red device was NOT getting any subccessfull connection!)
- however, after 10 minutes, it still did not connect to the NEW UTM hub
- I checked with tcpdump the communication of the red device to the rest of the world any saaw that it still tries to connect to the old huib hostname. after this is unsuccessfull, it seems to conenct to the registry service, and exchenages a bunch ofpackets on port 3400 with the registry. then it reboots. but after the reboot it still connects to the OLD ip adress
- I checked on red-db that there is NO configuration fetch any more. ALthough tcpdump shows me that the red device is talking to the registry, there seems to go something wrong and the change is not really downloaded to the RED device
- I cross-checked with the ssh debugging console access on the RED device itself and saw that in /astaro/cfg/hub_hostname still the old ip adress is contained.
SO it seems either the communication between RED and registry server is broken or the updated configuratiuon is not wirtten correctly to /astaro/cfg/hub_hostname
Elmar