Vendor dan OS masing-masing

Each switch vendor runs its own network operating system (NOS) with its own CLI and its own way of showing a transceiver. Knowing which NOS you face helps you read optics information and match a module to the platform.

Common vendors and NOS

Why the NOS matters for optics

• The commands to view a transceiver differ per NOS — see Verifying optics on a switch.
• The acceptance policy for third-party optics differs too — see Vendor lock & coding.
• The identity a switch expects (vendor name, part number) is vendor-specific, and that is exactly what CodingBox can read and code.

In CodingBox

The app can present a module's details formatted like several of these platforms' own output — see Transceiver summaries.

Further reading

• Network operating systems: a field guide — 17 NOS with CLI style, transceiver commands and documented third-party policy; open networking.
• OEM part numbers — naming grammars of Cisco, Juniper, Arista, Huawei, H3C, HPE, Dell, Nvidia, Brocade, MikroTik and others; grades and suffixes; matching rules.