we found a bug in the ACC daemon that leads to the issue described here
("name not set" and ip "1.1.1.1"). It happens when an ASG connects to the
ACC which doesn't have the Configuration feature. This is always the
case for ASGs that have the ACC configured as second ACC as such devices
doesn't have the Configuration feature by design.
Connecting such a device causes the accd to reach a state after some
hours that makes it unable to process incoming updates from the devices.
I.e. when a new device connects, the accd is unable to process the
information sent by this device such as name and ip address.
Until we release a bugfix, possible workarounds are either to enable the
Configuration feature without using it or to restart the ACC daemon per
cron job every two or three hours: