[Device]: FS NC8400-4TH (4-slot modular DC chassis) #757

Closed
opened 2026-11-08 06:20:04 +00:00 by jaylouisw · 2 comments
Owner

Vendor

FS

Exact model name

FS NC8400-4TH (4-slot modular DC chassis)

Category

Switch (L3)

Ports and interfaces

  • 4-slot modular chassis (unloaded)
  • Line cards: NC8400-32C, NC8400-16CD

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 high-density 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 NC8400-4TH (4-slot modular DC chassis) ### Category Switch (L3) ### Ports and interfaces - 4-slot modular chassis (unloaded) - Line cards: NC8400-32C, NC8400-16CD ### 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 high-density 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.
Author
Owner

Resolved by naming the fill, which is what the block above asked for: FS's NC8400 data sheet leads with 4x NC8400-32C ("can be loaded with line card NC8400-32C and supports a maximum of 128x 40G/100G"), so devices/fs/nc8400-4th.json lands as NC8400-4TH (4x NC8400-32C) — 128x HundredGigabitEthernet<slot>/<port> QSFP28 at 100G/40G, one console, 12.8 Tbps per direction of the stated 25.6 Tbps duplex, no PoE. Per-direction figure for the same reason NC8200-4TD uses it.

Two things this does not give you, stated now rather than discovered later:

  • The 400G fill is a different box. 4x NC8400-16CD is 64x 40/100G + 16x 400G QSFP-DD (data sheet Table 2). If the spine you want is 400G, say so and that fill gets its own spec.
  • Breakout is not modelled. The port note allows 4x10G/4x25G on a QSFP28 cage, but ports 1-4 are one group where only one supports breakout and three go dark, and Table 2 reports no breakout density for the 32C at all. The spec is 40G/100G per cage.

Sources: data sheet https://resource.fs.com/mall/resource/nc8400-series-switches-data-sheet.pdf (Tables 1-4), interface naming from the NC8400 CLI reference guide, and the older data sheet https://img-en.fs.com/file/datasheet/nc8400-series-switch-datasheet.pdf, which agrees on every figure (its "19.05 Bpps" is the current sheet's "19050 Mpps").

PR #1719 — body starts with Fixes #757, so merging closes this.

Resolved by naming the fill, which is what the block above asked for: FS's NC8400 data sheet leads with 4x **NC8400-32C** ("can be loaded with line card NC8400-32C and supports a maximum of 128x 40G/100G"), so `devices/fs/nc8400-4th.json` lands as **NC8400-4TH (4x NC8400-32C)** — 128x `HundredGigabitEthernet<slot>/<port>` QSFP28 at 100G/40G, one console, 12.8 Tbps per direction of the stated 25.6 Tbps duplex, no PoE. Per-direction figure for the same reason `NC8200-4TD` uses it. Two things this does **not** give you, stated now rather than discovered later: - **The 400G fill is a different box.** 4x NC8400-16CD is 64x 40/100G + 16x 400G QSFP-DD (data sheet Table 2). If the spine you want is 400G, say so and that fill gets its own spec. - **Breakout is not modelled.** The port note allows 4x10G/4x25G on a QSFP28 cage, but ports 1-4 are one group where only one supports breakout and three go dark, and Table 2 reports no breakout density for the 32C at all. The spec is 40G/100G per cage. Sources: data sheet https://resource.fs.com/mall/resource/nc8400-series-switches-data-sheet.pdf (Tables 1-4), interface naming from the NC8400 CLI reference guide, and the older data sheet https://img-en.fs.com/file/datasheet/nc8400-series-switch-datasheet.pdf, which agrees on every figure (its "19.05 Bpps" is the current sheet's "19050 Mpps"). PR #1719 — body starts with `Fixes #757`, so merging closes this.
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#757
No description provided.