[Device]: FS NC8200-4TD (4-slot modular DC chassis) #760
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#760
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Vendor
FS
Exact model name
FS NC8200-4TD (4-slot modular DC chassis)
Category
Switch (L3)
Ports and interfaces
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
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.mdsays 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.