NetBox FMS -- Fiber Management System
Under active development -- alpha. netbox-fms is pre-1.0 and changing fast. Models, migrations, REST endpoints, and configuration keys may break between releases without deprecation cycles. Pin an exact version in production, expect to read the CHANGELOG before every upgrade, and back up your database before running migrations. Issue reports and PRs are very welcome.
A NetBox plugin for fiber cable management, splice planning, and circuit provisioning.
Define fiber cable construction as reusable blueprints, auto-instantiate components on cable creation, plan splices with diff computation and draw.io export, and provision end-to-end fiber circuits with DAG-based pathfinding -- all within NetBox's native UI and API.
Features
- Cable type blueprints with auto-instantiation -- Define fiber cable construction once as a FiberCableType, then create instances that automatically populate buffer tubes, ribbons, strands, and cable elements following NetBox's Device/DeviceType pattern.
- Four construction cases -- Loose tube, ribbon-in-tube, central-core ribbon, and tight buffer cable designs with full template-driven instantiation.
- EIA/TIA-598, ABNT NBR 14771, and DIN IEC 60304 color schemes -- Each FiberCableType selects the strand color standard applied when instances are created; tube and ribbon template color pickers follow the selected standard.
- Per-wavelength loss budgeting -- Attach manufacturer max-attenuation specs (dB/km) to each FiberCableType at any wavelength.
FiberCircuitPath.calculated_loss_dbcomputes per-wavelength losses across the full cable path from spec values and each cable'sglass_length. - Splice planning -- Map strand-to-strand connections in splice closures, compute diffs against live state, and export diagrams to draw.io for field crews.
- Fiber circuit provisioning -- End-to-end provisioning with DAG-based pathfinding and multi-hop tracing.
- Provider span awareness -- The trace engine crosses core Circuits cabled inline (leased dark fiber through a provider meet-me room) as opaque hops; each fiber circuit tracks the provider circuits it rides, with provider/circuit impact filters and deletion protection.
- Device fiber overview -- Per-device fiber connection view, splice closure management with tray and group organization.
- Slack loop tracking -- Record slack loop locations and storage methods at splice closures, with insert-into-closure workflows.
- Port label templates -- FMS-provisioned FrontPorts and RearPorts carry human-readable labels (cable, tube, ribbon, strand color, absolute fiber number) rendered from sandboxed Jinja2 templates, customizable plugin-wide through
PLUGINS_CONFIGand refreshed automatically when the cable is relabeled. - Port name templates -- Optional
front_port_name_template/rear_port_name_templatesettings render write-once port names with the same token set; a rendered set that would not fit the dcim column or would not be unique on the device falls back to the pk-based grammar with a warning, so a cable end is never half-named. - Full REST API and GraphQL -- All models exposed via NetBox's standard API framework.
Compatibility
| Plugin version | NetBox version | Python |
|---|---|---|
| 0.3.x | 4.5-4.7 | 3.12-3.14 |
Installation
pip install netbox-fms
In your NetBox configuration.py:
PLUGINS = [
"netbox_fms",
]
Run migrations and restart NetBox:
cd /opt/netbox/netbox
python manage.py migrate
sudo systemctl restart netbox netbox-rq
Configuration
netbox-fms has no required PLUGINS_CONFIG entries. See Configuration for optional settings.
Documentation
Full documentation: jsenecal.github.io/netbox-fms
Related plugins
netbox-fms is part of a three-plugin set that models the full optical transport stack:
- netbox-pathways -- physical cable plant documentation with PostGIS. Models conduits, aerial spans, structures (poles, manholes, cabinets), and the geographic routes NetBox cables traverse. FMS describes what is inside a fiber cable and how strands are spliced; Pathways describes where the cable physically runs.
- netbox-wdm -- WDM (Wavelength Division Multiplexing) device management. Models ITU channel plans, ROADM mappings, and wavelength services that ride on top of the fiber circuits FMS provisions.
Contributing
PRs welcome. Use conventional-commits PR titles (feat:, fix:, chore:, docs:, ...) -- release-drafter assembles release notes from them. Run make setup after cloning to install dev dependencies and the pre-commit hooks (including the AI-attribution-rejecting commit-msg hook).
For questions and discussion, join the #netbox channel on the NetDev Community Slack.
License
Release files for netbox-fms 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| netbox_fms-0.5.0.tar.gz | 371.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| netbox_fms-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 704.1 kB
Release files / netbox_fms-0.5.0.tar.gz
| Download URL | netbox_fms-0.5.0.tar.gz |
|---|---|
| Size | 371.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34dea798cc947e18338d86c258fd827ca9b2d54e3cfe2e66a7df1e17d216e0e2
|
|
BLAKE2b-256 checksum How to use checksums |
d5e4bb780b74168505d9746511798101b84123015cccf309b45e66cf5c5a0203
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / netbox_fms-0.5.0-py3-none-any.whl
| Download URL | netbox_fms-0.5.0-py3-none-any.whl |
|---|---|
| Size | 332.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
744e85bd47d461590afe0e1fad240e3df480dff931bd85c5cac987a71629cecb
|
|
BLAKE2b-256 checksum How to use checksums |
456c66e1ee2ef7ac2f99c033564eb0c74b09f7937a3367e413be0e190592c61e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log