poe: a refused port is power-deny, and draws 0.0 W #2149
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2149
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1119-1212"
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?
One question: when the PSE detects a powered device and cannot supply it, what does the
Opercolumn say, and what sits in the power cell?Verdict:
power-deny,0.0.Operhas four documented values (on,off,faulty,power-deny);offmeans "No PoE is applied" - the word an empty socket prints. This console printedofffor a refusal, plus a(denied)tag and the device's request in the allocated-power cell.Sources (all in
research/show-power-inline-power-deny.md):power inline- "the PoE port is in a power-deny state ... the Oper column in the show power inline privileged EXEC command output shows power-deny".Operfield table and the sample rowGi3/0/1 auto power-deny 4.0 n/a n/a 15.4.Gi1/13 auto power-deny 0.0 n/a n/a 30.0, Catalyst 3650Gi1/0/9 auto power-deny 0.0 n/a n/a 30.0, Cisco Learning NetworkGi3/0/22 auto power-deny 0.0 n/a n/a 30.0.Changes:
engine/cli.js- refused rows carryOper = power-denyandDraw = 0.0 W; the(denied)tag is dropped because the word now says it, and the denial sentence under the table (... PSE budget exhausted: 12.95 W requested, 12.05 W left) still carries the request.Operwidened to 11 characters, the width the box's own heading holds, so the rest of the row stays in line.test/show-power-inline.test.js- the refused row is pinned cell by cell, with the neighbouring powered / non-PD / shut rows pinned toon/off/offso the new word cannot leak.test/poe-allocation-order.test.js- the lowest port that does not fit now readspower-deny.docs/CLI.md- sample table and the bullet on the denied row.npm test: 373 suites, 12,682 assertions, 0 failed.node scripts/syntax-check.js: 452 files OK.Still open (recorded in the note):
faultyis unreachable (no fault path), thepower inline policeview is not modelled, and theClass/Maxcolumns are a separate layout question.power-deny, and draws 0.0 W`Oper` in `show power inline` has four documented values - on, off, faulty, power-deny - and `off` is defined as "No PoE is applied", the word a socket with nothing on it prints. A port that detected a powered device and could not supply it was printing `off`, so the one row an operator is looking for read exactly like an empty port, with a local `(denied)` tag and the device's 12.95 W request priced in a cell that is meant to hold the power allocated. Cisco's `power inline` reference states the rule in one sentence ("the Oper column ... shows power-deny"), four command references carry the same field table, and budget-exhausted captures from an IE-4000, a Catalyst 3650 and a learning-network thread show the row as `auto power-deny 0.0 n/a n/a 30.0`. The row now reads `auto power-deny 0.0 W PDB`; the requested wattage stays in the denial sentence under the table, which is unchanged. The `Oper` field is eleven characters, the width the box's heading holds, so the columns behind it stay in line. research/show-power-inline-power-deny.md carries the sources and what is still open (`faulty`, the policing view, the Class/Max columns).