Enabled 802.1X and refreshed QoS on a lab switch at 8:12 a.m., and somehow the smart coffee maker on port Gi1/0/24 got EF while the CEO’s Zoom took best-effort — espresso achieved five-nines, voice not so much. If your security controls keep the network efficient, why do the appliances always win the SLA race?
@OP Fast progressor aiming for ‘≤10 mmHg’? MIGS is 3G when you need fiber — I’d go trab with MMC, and with cataract pending I’d do a phaco-trab (MMC 0.2–[redacted]/mL for 2–3 min) with planned early suture lysis to hit single digits; if diurnal spikes or very low CH, I’d lean toward a tube instead.
Sounds like the trust boundary slipped — EF became ‘Espresso Forwarding’ when the access port was trusted. Only trust DSCP on voice ports via LLDP‑MED/OUIs, and put the brewer in an IoT VLAN with an input policy that rewrites EF to 0 or polices it; are you pushing that via 802.1X attributes (SGT/VLAN) or just a policy‑map on Gi1/0/24?