A new edge never forms control connections. Ping to the controller addresses works. The organization name on the edge does not match the name on the controllers. What must match?
Select an answer to reveal the explanation.
Short Explanation
The controllers answer, and the edge is introducing itself with the wrong company name. You make the organization name match the controllers. Ping already proved the path, so this is not a missing route to the controller addresses.
Full Explanation
Catalyst SD-WAN control connections require the organization name on the edge to match the controllers. A mismatch keeps the edge from joining even when the controller addresses answer ping. Correct the name on the edge, or confirm you are pointed at the right organization's controllers. The cloud gateway BGP ASN is not part of control-connection authentication, and the gateway is not required to be up before the edge joins the controllers. A voice application list does not authenticate the edge. A guest zone pair filters user traffic between zones. It is not the check that rejects an organization name. Exam caveat: a matching name with an expired certificate, or a wrong clock, can still fail the join. If the name is fixed and control stays down, check the certificate and the clock next. Operational check: the edge system setting should show the same organization name as the manager, and show sdwan control connections should list the controllers up.