[Device]: TP-Link TL-SG1005P #1512
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1512
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
TP-Link
Exact model name
TL-SG1005P
Category
Switch (L2)
Datasheet / source
https://www.tp-link.com/uk/business-networking/unmanaged-switch/tl-sg1005p/v1/
Ports (from the vendor's own hardware table)
Why it matters
This is the switch feeding two PoE cameras in a real install, and the catalogue's nearest
entry is
tl-sg105, which is the non-PoE 5-port model. Modelling this box as a tl-sg105produces a switch that cannot power the devices plugged into it, so a lab of that install
refuses a cable the hardware accepts.
Notes for whoever implements it
poeOutbelongs on eth1-eth4 only (30 W is wrong here: the spec says 802.3af, 15.4 W per port)poeBudget: 56cli/http-servercapabilityShipped as
devices/tp-link/tl-sg1005p.jsoninf3fe1b48(PR #1645, "TP-Link TL-SG10xxP: four unmanaged PoE desktop switches").One nuance worth recording rather than fixing: the spec documents the current revision (datasheet 6.0) — 802.3af/at, up to 30 W per port, 65 W budget — while this request quoted the UK v1 product page, which is 802.3af only, 15.4 W per port and 56 W total. Both are correct for their revision; the file is right to follow the current one, and its note about the budget (not the port count) being the limit matches the "four 30 W devices cannot all be powered" behaviour.
Closing: the request is satisfied.