On a hub and spoke environment, when checking the Event log of the Hub on the Orchestrator, "New client device seen" events might be seen referencing an Invalid IP address
Hub and spoke topology
Edges on version prior to 5.2.4.0 or 6.1.0.0
This was caused by known software issue #134125 that relates to not initializing properly a DHCP info structure, which affected the processing of the client requested IP address field. This caused triggering unnecessary Orchestrator events with content similar to the below (redacting MAC address, hostname, OS info for the purpose of this article, they will show properly on the Orchestrator Event log if the issue is seen):
{"last_request_time":0,"client_mac":"XX:XX:XX:XX:XX:XX","client_ipv4addr":"0.0.86.59","hostname":"XXXX","os_type":XX,"os_class":1,"os_class_name":"XXXXX","os_version":"XX","device_type":"Desktop/Laptop","os_description":"XX","dhcp_param_list":"1,3,6,15,31,33,43,44,46,47,119,121,249,252","segment_id":0}
Upgrade the Hub device to a version later than 5.2.4.0 or 6.1.0.0, which contain the fix for #134125