[Device]: Garland AggregatorTAP Copper: 10/100/1000M TAP (P1GCCAS) #664
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#664
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
Garland Technology
Exact model name
P1GCCAS
Category
Other / not sure
Ports and interfaces
PoE budget (watts)
None
Datasheet or product page URL
https://www.4gon.co.uk/garland-aggregatortap-copper-101001000m-tap-p1gccas-p-10342.html
What do you want to model with it?
A network appliance (controller/tap/transport) on the network.
Capabilities
see product page
Before submitting
Closing as a component, not a device. The page says it outright: "TAP Module fits into the RMP-1U". The P1GCCAS is a module for a 1U rack chassis, sold without a chassis; on its own it has no enclosure and no ports until it is seated.
Closed as a component, not a device.
docs/DEVICE_REGISTRY.md(What the catalogue cannot represent) now names this class explicitly, commit34df8fa: a part that must be installed inside something else to exist has no enclosure of its own and no ports until it is seated, so the host device is the catalogue entry and the component is a fact about it (which modem, which line card, which TAP module) - not a node a lab can cable.This is deliberately narrower than "we could not find a datasheet". #527 (Netonix) stays open for that reason: it is a real switch that merely lacks a published PoE budget. A gap in the source is not a gap in the simulator.
The chassis (RMP-1U) plus a specified set of modules would be a legitimate device request, and the copper TAP shape it produces is already represented by the standalone parts -
P1GCCBand the newP1GCUA_miniare in the catalogue.