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
Dual stack means the VLAN has IPv4 and IPv6 on purpose, each with a prefix you were given. NAT64 lets an IPv6-only client reach an IPv4 destination through a translator you run. 6to4 and a casual tunnel are old mechanisms. Do not choose 6to4 for a new site.
The synthesizer and the converters draft an address form. They do not turn up a tunnel to a network you do not administer. A tunnel that encapsulates someone else's traffic is out of scope.
Write which side is IPv6-only, which side is IPv4, and who operates the translator. One path. Documentation prefixes stay in the example.
If the site can be dual stacked with real prefixes, that is the simpler plan. Say so.
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.
- Name the applications that still need IPv4.
- Choose dual stack or NAT64.
- Reject 6to4 for a new design.
- Write who operates the translator.
- Keep the lab prefix assigned.
- Do not open a tunnel to a network you do not run.
Mistakes that outlive the command
IPv6 Transition Mechanisms (Dual Stack, NAT64, 6to4) goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Enabling 6to4 because a converter existed.
- A tunnel toward a network you do not administer.
- NAT64 with no one named as the operator.
- Documentation prefixes in production.
Decisions to write down
One decision for IPv6 Transition Mechanisms (Dual Stack, NAT64, 6to4): The mechanism is one choice. 6to4 is not the new design. The operator is named. Prefixes are assigned. And no foreign tunnel was opened.
Checks before you call it done
Confirm this before you call the change done: The choice is written. 6to4 is absent. The translator owner is named. Prefixes are not documentation. And no tunnel was opened. If one of those fails, stop.
Before you leave the device
IPv6 Transition Mechanisms (Dual Stack, NAT64, 6to4) 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.