You are deploying a new AOS-10 mobility gateway cluster. Because of customer requirements, the gateways must use static IP addresses and may communicate on port 443 only with URLs matching `*.central.arubanetworks.com`. How can these gateways be successfully onboarded into HPE Aruba Networking Central?
Static Activate relies on Aruba Activate for initial provisioning, and Aruba Activate uses HTTPS endpoints such as `device.arubanetworks.com`, which do not match the permitted `*.central.arubanetworks.com` domain. Full Setup supports static addressing and configuration of the ACP FQDN, so the gateway can establish its Central connection using the allowed Central domain.