[Device]: FS NC8200-4TD (4-slot modular DC chassis) #760

Closed
opened 2026-11-08 06:20:07 +00:00 by jaylouisw · 1 comment
Owner

Vendor

FS

Exact model name

FS NC8200-4TD (4-slot modular DC chassis)

Category

Switch (L3)

Ports and interfaces

  • 4-slot modular chassis (unloaded)
  • Line cards: NC8200-24BC, NC8200-8C

PoE budget (watts)

None unless stated in the port list above

Datasheet or product page URL

https://www.fs.com/uk/c/data-center-switches-3404

What do you want to model with it?

Modular data center switch chassis.

Capabilities

l2-forward, l3-forward, cli

Before submitting

  • I searched the catalog and existing issues, and this model is not there yet.
  • The port list above comes from a datasheet, not from memory or another wiki.
### Vendor FS ### Exact model name FS NC8200-4TD (4-slot modular DC chassis) ### Category Switch (L3) ### Ports and interfaces - 4-slot modular chassis (unloaded) - Line cards: NC8200-24BC, NC8200-8C ### PoE budget (watts) None unless stated in the port list above ### Datasheet or product page URL https://www.fs.com/uk/c/data-center-switches-3404 ### What do you want to model with it? Modular data center switch chassis. ### Capabilities l2-forward, l3-forward, cli ### Before submitting - [x] I searched the catalog and existing issues, and this model is not there yet. - [x] The port list above comes from a datasheet, not from memory or another wiki.
Author
Owner

Closing status: blocked on a stated configuration.

These are 4-slot modular chassis: FS publishes the slot count and the module set (16x 10G SFP+, 8x 25G, 8x GE PoE, etc.), and a module is a bay rather than a port - the components clause in docs/DEVICE_REGISTRY.md says a line card is a fact about a host device, not a node in a topology.

Two ways this gets modelled honestly: (a) you name the module set for the SKU you want - "NC8200-4TD with two 16x10G modules" - or (b) the catalogue gains a chassis concept, where a frame declares slots and a lab populates them. (b) is a feature, not a spec.

Compare #766-#769, the FS controllers, which closed once the comparison table gave their fixed port rows, and #458 (Peplink SDX), which closed because its ordering row named the base chassis's ports exactly.

Closing status: **blocked on a stated configuration.** These are 4-slot modular chassis: FS publishes the slot count and the module set (16x 10G SFP+, 8x 25G, 8x GE PoE, etc.), and a module is a bay rather than a port - the components clause in `docs/DEVICE_REGISTRY.md` says a line card is a fact about a host device, not a node in a topology. Two ways this gets modelled honestly: (a) you name the module set for the SKU you want - "NC8200-4TD with two 16x10G modules" - or (b) the catalogue gains a chassis concept, where a frame declares slots and a lab populates them. (b) is a feature, not a spec. Compare #766-#769, the FS *controllers*, which closed once the comparison table gave their fixed port rows, and #458 (Peplink SDX), which closed because its ordering row named the base chassis's ports exactly.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#760
No description provided.