This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
AOS-S and AOS-CX do not share a command language. The converter drafts one VLAN, one interface, or one ACL. You read it. An AOS-S habit pasted by hand beside the draft is how a hybrid file appears.
Keep the AOS-S backup. One object. A permit any in the draft is deleted. Secrets are redacted and rotated if they were in the export.
The push, if it ever happens, is a lab CX switch in a later window. This page stops at the draft.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Choose one AOS-S object you may convert.
- Read the CX draft.
- Remove hybrid leftovers.
- Delete a wide permit.
- Keep the AOS-S backup.
- Do not push.
Mistakes that outlive the command
Aruba AOS-S to Aruba AOS-CX Migration Guide goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The two operating systems mixed in one file.
- The backup discarded.
- A wide permit kept.
- A secret retained.
- A production push.
Decisions to write down
One decision for Aruba AOS-S to Aruba AOS-CX Migration Guide: One object was converted. The languages were not mixed. The backup exists. Nothing was pushed. And secrets are gone.
Checks before you call it done
Confirm this before you call the change done: The object is named. The draft is CX only. The backup location is written. No secret remains. And no switch was changed. If one of those fails, stop.
Before you leave the device
Aruba AOS-S to Aruba AOS-CX Migration Guide ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.