vlan: a voice VLAN belongs to an access port, and a trunk only stores it #1877
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!1877
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rev/1117-1730"
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?
The rule
switchport voice vlan <id>is the one command that puts a phone's tagged VLAN and a PC's untagged VLAN on the same port. This console had the rule backwards in both directions:validatePortConfigrefused a voice VLAN on an access port - "voice traffic is tagged";classifyEgress/classifyIngresscarried it on a trunk whether or not the allowed list named it;switchportSentencecalled an access port's voice VLAN "stored, not in use".So the one configuration a Cisco phone actually uses was reported as doing nothing, and the one place Cisco says the feature does not work was the place it worked.
The evidence
Every current Cisco switching guide states the same prerequisite:
and the 9600 port-security chapter adds that on a trunk the configuration is allowed yet does nothing:
Full write-up, including what is inferred rather than quoted (the dual row in
show vlan brief):research/voice-vlan-port-mode.md.The change
classifyEgress- an access port sends the voice VLAN tagged (markedvoice) beside the untagged access VLAN and still drops every other VLAN. A trunk is decided by its allowed list alone.classifyIngress- an access port accepts the one tagged VLAN it is configured for; every other tag is stilltagged-frame-on-access. The trunk lost its voice exemption.validatePortConfig- the warning moved to the trunk case: "voiceVlan 20 has no effect on a trunk port: a voice VLAN applies to access ports".switchportSentenceand itsweb/app.jsmirror -access VLAN 10 · voice 20 (tagged); a trunk prints· voice 20 (no effect on a trunk).framesCompatible/mismatchReason- two access ports in the same data VLAN but with different voice VLANs no longer look interchangeable to a LAG member check.no vlan <id>- the reference guard still refuses, but names(voice)on an access port and(voice, no effect)on a trunk, and no longer claims the port went inactive in a VLAN that was never its data VLAN.show vlanneeded no change: it asksclassifyEgress, so a voice port is now listed under both VLANs - the transcript indocs/CLI.mdshows the two rows.Verification
node scripts/syntax-check.js- 392 files, all OK.npm test- 320 suites, 11157 assertions, 0 failed.Suite deltas:
voice-vlan37 -> 39 assertions (command receipts, classifier in both directions, dualshow vlanrows),vlan60 -> 62,switchport-agreement12 -> 13 (the sentence is now checked against a live voice claim, and against the inert one on a trunk),vlan-delete-leaves-port-inactive21 -> 27.`switchport voice vlan <id>` had its rule backwards in both directions. `validatePortConfig` refused a voice VLAN on an access port ("voice traffic is tagged"), `classifyEgress` carried it on a trunk whether or not the allowed list named it, and an access port with a voice VLAN was reported as "stored, not in use" - so the one configuration a Cisco IP phone actually uses was the one this console said did nothing. Every current Cisco switching guide states the prerequisite the same way: voice VLAN configuration "is only supported on device access ports; ... not supported on trunk ports", and the note beside it says a trunk "can carry any number of voice VLANs, similar to regular VLANs". The 9600 port-security chapter adds that the configuration is allowed on a trunk and still has no effect (research/voice-vlan-port-mode.md). - `classifyEgress`: an access port sends the voice VLAN tagged and marks it as voice, sends its access VLAN untagged and still drops everything else. A trunk is told what to carry by its allowed list alone. - `classifyIngress`: an access port accepts the one tagged VLAN it is configured for and still refuses every other tag with `tagged-frame-on-access`; the trunk lost its voice exemption. - `validatePortConfig`: the warning moved to the trunk case, where the parameter really is inert. - `switchportSentence` (and its panel mirror): `access VLAN 10 · voice 20 (tagged)` against `... · voice 20 (no effect on a trunk)`. - `framesCompatible`/`mismatchReason`: two access ports with different voice VLANs no longer look interchangeable to a LAG member check. - `no vlan <id>` still refuses a VLAN a voice port references, but names an access port's reference `(voice)`, a trunk's `(voice, no effect)`, and no longer calls the port inactive in it. - `show vlan` needed no change of its own: it asks `classifyEgress`, so a voice port is now listed under both its access VLAN and its voice VLAN. Closes nothing; #1368 and #1701 are the earlier halves of the same field. Tests: npm test - 320 suites, 11157 assertions, 0 failed.e2fda7572c9898d3a99a