Netbox Starfleet Lab — Build Report
Date: May 2026
FMCP Version: 0.6
Agent: Claude.ai (Web based)
Date: 2026-05-07 Environment: Local Netbox instance (MacBook), tunneled via ngrok Interface: Claude.ai (claude-sonnet-4-6) over MCP connector Connection Method: ngrok reverse tunnel → Netbox REST API → frisian-mcp Netbox MCP server Status: Complete ✅
Overview
This report documents a full Netbox lab environment built end-to-end by Claude.ai via the Netbox MCP server over an ngrok tunnel. The dataset uses a Star Trek: The Next Generation / Deep Space Nine naming convention and serves as the canonical demo and integration test dataset for the frisian-mcp Netbox integration. No real company names, real locations, or production data were used.
All objects were created via MCP tool calls using the frisian-mcp dispatcher pattern (resource + action + params). The build validates full write lifecycle coverage across DCIM, IPAM, and cabling resources.
Topology Summary
Four sites distributed across four quadrant regions, connected by a realistic spine/access hierarchy with full IPAM coverage, VRF segmentation, VLAN assignments, interface definitions, IP address allocations, and cabled links.
Alpha Quadrant
└── Starbase-1
├── starbase1-fw01 (Firewall → CardOS)
├── uss-enterprise-rtr01 (Router → LCARS-OS) ← primary: 10.10.1.1
├── starbase1-core-sw01 (Core Switch → LCARS-OS) ← primary: 10.10.1.2
├── starbase1-acc-sw01 (Access Switch → BajorOS)
└── starbase1-oob01 (OOB Console)
Cables:
uss-enterprise-rtr01 Gi0/0 ──── starbase1-fw01 Gi0/0 [SB1-RTR-FW]
uss-enterprise-rtr01 Gi0/1 ──── starbase1-core-sw01 Gi0/0 [SB1-RTR-CORE]
starbase1-core-sw01 Gi0/1 ──── starbase1-acc-sw01 Gi0/0 [SB1-CORE-ACC]
Alpha Quadrant
└── Deep Space 9
├── uss-defiant-rtr01 (Router → LCARS-OS) ← primary: 10.10.2.1
├── ds9-ops-core-sw01 (Core Switch → LCARS-OS)
└── ds9-promenade-acc-sw01 (Access Switch → BajorOS)
Cables:
uss-defiant-rtr01 Gi0/0 ──── ds9-ops-core-sw01 Gi0/0 [DS9-CORE-RTR]
ds9-ops-core-sw01 Gi0/1 ──── ds9-promenade-acc-sw01 Gi0/0 [DS9-CORE-ACC]
Beta Quadrant
└── Utopia Planitia
└── utopia-rtr01 (Router → LCARS-OS)
Gamma Quadrant
└── Bajor Relay
└── bajor-rtr01 (Router → LCARS-OS)
Regions
| ID | Name | Slug |
|---|---|---|
| 1 | Alpha Quadrant | alpha-quadrant |
| 2 | Beta Quadrant | beta-quadrant |
| 3 | Gamma Quadrant | gamma-quadrant |
| 4 | Delta Quadrant | delta-quadrant |
Sites
| ID | Name | Region | Description |
|---|---|---|---|
| 1 | Starbase-1 | Alpha Quadrant | Alpha Quadrant Fleet Command HQ |
| 2 | Deep Space 9 | Alpha Quadrant | Deep Space Station on the Bajoran Wormhole |
| 3 | Utopia Planitia | Beta Quadrant | Martian Orbital Shipyard and R&D Facility |
| 4 | Bajor Relay | Gamma Quadrant | Bajoran Sector Relay and Distribution Hub |
Manufacturers
| ID | Name | Description |
|---|---|---|
| 1 | Daystrom Industries | Advanced computing and positronic systems |
| 2 | Soong Technologies | Cybernetics, androids, and synthetic neural systems |
| 3 | Cardassian Union Fabrication | Cardassian military-grade network infrastructure |
| 4 | Yoyodyne Propulsion Systems | Warp-grade routing and propulsion-integrated switching |
Device Types
| ID | Model | Manufacturer | U Height | Description |
|---|---|---|---|---|
| 1 | LCARS-9000 Core Router | Daystrom Industries | 2U | High-capacity LCARS-integrated core router |
| 2 | Isolinear Core Switch | Daystrom Industries | 2U | Isolinear optical core switching platform |
| 3 | Positronic Access Switch | Soong Technologies | 1U | Positronic access layer switch with adaptive routing |
| 4 | Duranium Perimeter Firewall | Cardassian Union Fabrication | 1U | Cardassian duranium-class perimeter firewall |
| 5 | Warp-Relay OOB Console | Yoyodyne Propulsion Systems | 1U | Warp-relay OOB console server |
Platforms
| ID | Name | Manufacturer | Description |
|---|---|---|---|
| 1 | LCARS-OS | Daystrom Industries | Library Computer Access and Retrieval System OS |
| 2 | BajorOS | Soong Technologies | Bajoran Provisional Government network OS |
| 3 | CardOS | Cardassian Union Fabrication | Cardassian Union military network operating system |
Note: Netbox enforces manufacturer/platform pairing at the API level. During the build, an attempt to assign LCARS-OS (Daystrom) to a Soong Technologies device type was rejected with a validation error. Corrected in real-time. This is a notable validation behavior for frisian-mcp integration testing.
Device Roles
| ID | Name | Color | Description |
|---|---|---|---|
| 1 | Router | Red (#aa1409) | Sector-level edge and core router |
| 2 | Core Switch | Blue (#0d47a1) | High-throughput core switching fabric |
| 3 | Access Switch | Green (#1b5e20) | Station and crew access layer switching |
| 4 | Firewall | Amber (#f57f17) | Perimeter security and threat neutralization |
| 5 | OOB Console | Purple (#4a148c) | Out-of-band emergency console access |
Devices
| ID | Name | Site | Role | Platform | Device Type | Primary IP |
|---|---|---|---|---|---|---|
| 1 | uss-enterprise-rtr01 | Starbase-1 | Router | LCARS-OS | LCARS-9000 Core Router | 10.10.1.1/24 |
| 2 | starbase1-core-sw01 | Starbase-1 | Core Switch | LCARS-OS | Isolinear Core Switch | 10.10.1.2/24 |
| 3 | starbase1-acc-sw01 | Starbase-1 | Access Switch | BajorOS | Positronic Access Switch | — |
| 4 | starbase1-fw01 | Starbase-1 | Firewall | CardOS | Duranium Perimeter Firewall | — |
| 5 | uss-defiant-rtr01 | Deep Space 9 | Router | LCARS-OS | LCARS-9000 Core Router | 10.10.2.1/24 |
| 6 | ds9-ops-core-sw01 | Deep Space 9 | Core Switch | LCARS-OS | Isolinear Core Switch | — |
| 7 | ds9-promenade-acc-sw01 | Deep Space 9 | Access Switch | BajorOS | Positronic Access Switch | — |
| 8 | utopia-rtr01 | Utopia Planitia | Router | LCARS-OS | LCARS-9000 Core Router | — |
| 9 | bajor-rtr01 | Bajor Relay | Router | LCARS-OS | LCARS-9000 Core Router | — |
| 10 | starbase1-oob01 | Starbase-1 | OOB Console | — | Warp-Relay OOB Console | — |
VLANs
All VLANs assigned to VLAN Group: Management, scoped to Starbase-1.
| ID | VID | Name | Description |
|---|---|---|---|
| 1 | 10 | VLAN-10-MGMT | OOB Management |
| 2 | 20 | VLAN-20-DATA | Primary data transport |
| 3 | 30 | VLAN-30-HOLONET | Holonet crew entertainment and comms |
| 4 | 40 | VLAN-40-TRANSPORTER | Transporter pad coordination network |
VRFs
| ID | Name | Route Distinguisher | Description |
|---|---|---|---|
| 1 | MGMT-VRF | 65000:10 | Out-of-band management routing domain |
| 2 | DATA-VRF | 65000:20 | Primary data transport routing domain |
| 3 | HOLONET-VRF | 65000:30 | Holonet crew entertainment and comms routing domain |
| 4 | TRANSPORTER-VRF | 65000:40 | Transporter pad coordination routing domain |
Prefixes
Supernets (Container)
| Prefix | VRF | Description |
|---|---|---|
| 10.10.0.0/16 | MGMT-VRF | MGMT supernet |
| 10.20.0.0/16 | DATA-VRF | DATA supernet |
| 10.30.0.0/16 | HOLONET-VRF | HOLONET supernet |
| 10.40.0.0/16 | TRANSPORTER-VRF | TRANSPORTER supernet |
Site Subnets (/24, Active)
| Prefix | VRF | VLAN | Site | Description |
|---|---|---|---|---|
| 10.10.1.0/24 | MGMT-VRF | VLAN-10-MGMT | Starbase-1 | Starbase-1 MGMT subnet |
| 10.10.2.0/24 | MGMT-VRF | VLAN-10-MGMT | Deep Space 9 | Deep Space 9 MGMT subnet |
| 10.10.3.0/24 | MGMT-VRF | VLAN-10-MGMT | Utopia Planitia | Utopia Planitia MGMT subnet |
| 10.10.4.0/24 | MGMT-VRF | VLAN-10-MGMT | Bajor Relay | Bajor Relay MGMT subnet |
| 10.20.1.0/24 | DATA-VRF | VLAN-20-DATA | Starbase-1 | Starbase-1 DATA subnet |
| 10.20.2.0/24 | DATA-VRF | VLAN-20-DATA | Deep Space 9 | Deep Space 9 DATA subnet |
| 10.30.1.0/24 | HOLONET-VRF | VLAN-30-HOLONET | Starbase-1 | Starbase-1 HOLONET subnet |
| 10.30.2.0/24 | HOLONET-VRF | VLAN-30-HOLONET | Deep Space 9 | Deep Space 9 HOLONET subnet |
| 10.40.1.0/24 | TRANSPORTER-VRF | VLAN-40-TRANSPORTER | Starbase-1 | Starbase-1 TRANSPORTER subnet |
Interfaces
| ID | Device | Interface | Type | Mgmt Only | Description |
|---|---|---|---|---|---|
| 1 | uss-enterprise-rtr01 | GigabitEthernet0/0 | 1000BASE-T | No | Uplink to starbase1-fw01 |
| 2 | uss-enterprise-rtr01 | GigabitEthernet0/1 | 1000BASE-T | No | Downlink to starbase1-core-sw01 |
| 3 | uss-enterprise-rtr01 | Management0 | 1000BASE-T | Yes | Management interface |
| 4 | starbase1-core-sw01 | GigabitEthernet0/0 | 1000BASE-T | No | Uplink to uss-enterprise-rtr01 |
| 5 | starbase1-core-sw01 | GigabitEthernet0/1 | 1000BASE-T | No | Downlink to starbase1-acc-sw01 |
| 6 | starbase1-core-sw01 | Management0 | 1000BASE-T | Yes | Management interface |
| 7 | starbase1-fw01 | GigabitEthernet0/0 | 1000BASE-T | No | Uplink to uss-enterprise-rtr01 |
| 8 | uss-defiant-rtr01 | GigabitEthernet0/0 | 1000BASE-T | No | Uplink to ds9-ops-core-sw01 |
| 9 | uss-defiant-rtr01 | Management0 | 1000BASE-T | Yes | Management interface |
| 10 | ds9-ops-core-sw01 | GigabitEthernet0/0 | 1000BASE-T | No | Uplink to uss-defiant-rtr01 |
| 11 | ds9-ops-core-sw01 | GigabitEthernet0/1 | 1000BASE-T | No | Downlink to ds9-promenade-acc-sw01 |
IP Addresses
| ID | Address | VRF | Interface | Device | DNS Name | Description |
|---|---|---|---|---|---|---|
| 1 | 10.10.1.1/24 | MGMT-VRF | Management0 | uss-enterprise-rtr01 | uss-enterprise-rtr01.mgmt.starbase1 | uss-enterprise-rtr01 mgmt |
| 2 | 10.10.1.2/24 | MGMT-VRF | Management0 | starbase1-core-sw01 | starbase1-core-sw01.mgmt.starbase1 | starbase1-core-sw01 mgmt |
| 3 | 10.10.2.1/24 | MGMT-VRF | Management0 | uss-defiant-rtr01 | uss-defiant-rtr01.mgmt.ds9 | uss-defiant-rtr01 mgmt |
Cables
| ID | Label | A-Side | B-Side | Type | Status |
|---|---|---|---|---|---|
| 1 | SB1-RTR-FW | uss-enterprise-rtr01 Gi0/0 | starbase1-fw01 Gi0/0 | CAT6 | Connected |
| 2 | SB1-RTR-CORE | uss-enterprise-rtr01 Gi0/1 | starbase1-core-sw01 Gi0/0 | CAT6 | Connected |
| 3 | DS9-CORE-RTR | ds9-ops-core-sw01 Gi0/0 | uss-defiant-rtr01 Gi0/0 | CAT6 | Connected |
| 4 | DS9-CORE-ACC | ds9-ops-core-sw01 Gi0/1 | ds9-promenade-acc-sw01 Gi0/0 | CAT6 | Connected |
Object Totals
| Resource | Count |
|---|---|
| Regions | 4 |
| Sites | 4 |
| Manufacturers | 4 |
| Device Types | 5 |
| Platforms | 3 |
| Device Roles | 5 |
| Devices | 10 |
| VLANs | 4 |
| VLAN Groups | 1 |
| VRFs | 4 |
| Prefixes | 13 |
| Interfaces | 11 |
| IP Addresses | 3 |
| Cables | 4 |
| Total Objects | 76 |
Build Notes & Observations
Connection method: All API calls were made by Claude.ai (claude-sonnet-4-6) through the Netbox MCP connector, tunneled over ngrok to a locally running Netbox instance on a MacBook. No direct API access or scripting was used — every object was created via natural language conversation translated to MCP tool calls.
Manufacturer/platform pairing enforcement: Netbox's API enforces that a device's platform must belong to the same manufacturer as its device type. During the build, assigning LCARS-OS (Daystrom Industries) to a Positronic Access Switch (Soong Technologies) was rejected with a validation error. This was caught and corrected in real-time by switching to BajorOS (Soong Technologies). This is a good example of Netbox's data integrity enforcement surfacing through frisian-mcp write operations.
FK reference pattern: Netbox foreign key references require either string IDs or nested dicts depending on the field and endpoint. During the build, both "1" (string) and 1 (integer) patterns were tested; the API accepted strings for most FK fields on partial_update, and integers for assigned_object_id. This behavior should be documented in the frisian-mcp Netbox integration notes.
Dispatcher pattern: All resources were accessed via the group dispatcher (Netbox:dcim, Netbox:ipam) using resource + action + params. The dispatcher pattern reduced total tool count significantly and kept the build conversational.
Scope: This dataset intentionally covers the most common Netbox resource types used in real network automation workflows: sites, devices, IPAM, VLANs, VRFs, interfaces, IPs, and physical cabling. It is suitable as a demo environment for frisian-mcp query and write demonstrations.
Intended Use
This dataset serves as:
- The canonical demo environment for the frisian-mcp Netbox MCP integration
- A write lifecycle validation reference (create, partial_update, FK resolution)
- A starting point for RAG document generation covering Netbox object relationships
- A reference topology for frisian-mcp end-user documentation examples
Build and testing executed by Claude.ai (claude-sonnet-4-6) via frisian-mcp NetBox MCP server | 2026-05-07