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
Single-mode fiber and multimode fiber are different glass. You do not mix them on one link and hope the optic figures it out. The selector drafts a type from distance and speed you type.
The optic has to match the fiber. A transceiver page owns the module. This page owns the glass choice for one run.
Write the distance. A short run can be multimode. A long run is usually single-mode. Existing plant may decide for you. Write what is already in the tray.
Do not disconnect a production pair to see the colour of the cladding.
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.
- Write the distance.
- Write what is already installed.
- Choose single-mode or multimode.
- Match the optic family in a sentence.
- Leave production pairs connected.
- Stop at one link.
Mistakes that outlive the command
Single-Mode vs Multimode Fiber goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Mixed fiber on one link.
- An optic that does not match.
- A production pair unplugged to look.
- Distance guessed.
Decisions to write down
One decision for Single-Mode vs Multimode Fiber: Distance is written. Existing plant is written. The type matches both. The optic family matches. And no production pair was opened.
Checks before you call it done
Confirm this before you call the change done: The link is named. The type is written. The optic constraint is a sentence. Distance is a number. And nothing was unplugged. If one of those fails, stop.
One link. Match the glass and the optic.
Do not open a production pair to look.Before you leave the device
Single-Mode vs Multimode Fiber 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.