{"id":24619,"date":"2026-11-17T17:53:41","date_gmt":"2026-11-17T09:53:41","guid":{"rendered":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html"},"modified":"2026-11-17T17:53:41","modified_gmt":"2026-11-17T09:53:41","slug":"how-to-check-qos-on-cisco-switch","status":"publish","type":"post","link":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html","title":{"rendered":"How to Check QoS on Cisco Switch"},"content":{"rendered":"<p>Verifying Quality of Service (QoS) on a Cisco switch requires more than just inspecting the running configuration. Because modern Catalyst switches handle packet classification, policing, and queuing directly within hardware ASICs, a policy that looks valid in the configuration file may not actually match traffic or prevent buffer exhaustion during microbursts. Properly auditing QoS means verifying global and port-level trust boundaries, confirming that traffic matches your intended class-maps, and inspecting hardware egress queues for silent tail drops.<\/p>\n<p>Before entering verification commands into the CLI, however, you must first identify which QoS architecture your Catalyst switch uses.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_17 counter-hierarchy counter-decimal ez-toc-light-blue\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" style=\"display: none;\"><i class=\"ez-toc-glyphicon ez-toc-icon-toggle\"><\/i><\/a><\/span><\/div>\n<nav><ul class=\"ez-toc-list ez-toc-list-level-1\"><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#Legacy_MLS_QoS_vs_Modern_Cisco_IOS-XE_MQC_Commands\" title=\"Legacy MLS QoS vs. Modern Cisco IOS-XE MQC Commands\">Legacy MLS QoS vs. Modern Cisco IOS-XE MQC Commands<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#CLI_Command_Template_for_Verifying_Cisco_Switch_QoS_Status\" title=\"CLI Command Template for Verifying Cisco Switch QoS Status\">CLI Command Template for Verifying Cisco Switch QoS Status<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#How_to_Read_and_Interpret_show_policy-map_interface_Output\" title=\"How to Read and Interpret show policy-map interface Output\">How to Read and Interpret show policy-map interface Output<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#How_to_Check_and_Troubleshoot_QoS_Queue_Drops_at_the_Hardware_Level\" title=\"How to Check and Troubleshoot QoS Queue Drops at the Hardware Level\">How to Check and Troubleshoot QoS Queue Drops at the Hardware Level<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#Step_1_Check_High-Level_Interface_Output_Drops\" title=\"Step 1: Check High-Level Interface Output Drops\">Step 1: Check High-Level Interface Output Drops<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#Step_2_Inspect_Hardware_ASIC_Queue_Statistics_IOS-XE_Catalyst_9000\" title=\"Step 2: Inspect Hardware ASIC Queue Statistics (IOS-XE \/ Catalyst 9000)\">Step 2: Inspect Hardware ASIC Queue Statistics (IOS-XE \/ Catalyst 9000)<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#Step_3_Check_Hardware_Queue_Drops_on_Legacy_MLS_QoS_Switches\" title=\"Step 3: Check Hardware Queue Drops on Legacy MLS QoS Switches\">Step 3: Check Hardware Queue Drops on Legacy MLS QoS Switches<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#Step_4_Baseline_Counters_and_Tune_Queue_Buffers\" title=\"Step 4: Baseline Counters and Tune Queue Buffers\">Step 4: Baseline Counters and Tune Queue Buffers<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#Best_Network_Monitoring_Tools_to_Track_Cisco_Switch_QoS_Metrics\" title=\"Best Network Monitoring Tools to Track Cisco Switch QoS Metrics\">Best Network Monitoring Tools to Track Cisco Switch QoS Metrics<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\/#Official_Cisco_Catalyst_QoS_Documentation_and_Command_References\" title=\"Official Cisco Catalyst QoS Documentation and Command References\">Official Cisco Catalyst QoS Documentation and Command References<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Legacy_MLS_QoS_vs_Modern_Cisco_IOS-XE_MQC_Commands\"><\/span>Legacy MLS QoS vs. Modern Cisco IOS-XE MQC Commands<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A common point of confusion when checking QoS on newer switches like the Cisco Catalyst 9200, 9300, 9400, or 9500 series is running <code>show mls qos<\/code> and receiving an <code>% Invalid input detected<\/code> error. <\/p>\n<p>Older Cisco IOS switches (such as the Catalyst 2960, 3560, and 3750 series) relied on Multi-Layer Switching (MLS) QoS. Under MLS QoS, prioritization was disabled by default, and enabling it globally without configuring port trust caused the switch to rewrite all incoming CoS and DSCP markings to zero. Modern Cisco IOS-XE switches (Catalyst 3650\/3850 and the Catalyst 9000 family) replace MLS QoS with the Modular QoS CLI (MQC) framework and the Forwarding Engine Driver (FED). On IOS-XE platforms, QoS is permanently enabled in hardware by default, and switch ports implicitly trust incoming DSCP and CoS markings unless a service policy explicitly remarks them.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Verification Task \/ Criterion<\/th>\n<th style=\"text-align: left;\">Legacy Cisco IOS (MLS QoS)<\/th>\n<th style=\"text-align: left;\">Modern Cisco IOS-XE (MQC &amp; FED)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Target Switch Platforms<\/strong><\/td>\n<td style=\"text-align: left;\">Catalyst 2960, 2960-X\/S, 3560, 3750, 3750-X<\/td>\n<td style=\"text-align: left;\">Catalyst 3650, 3850, 9200, 9300, 9400, 9500<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Default Global QoS State<\/strong><\/td>\n<td style=\"text-align: left;\">Disabled (<code>mls qos<\/code> required to activate)<\/td>\n<td style=\"text-align: left;\">Always enabled in hardware by default<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Default Interface Trust State<\/strong><\/td>\n<td style=\"text-align: left;\">Untrusted (rewrites CoS\/DSCP to <code>0<\/code> when MLS is active)<\/td>\n<td style=\"text-align: left;\">Implicitly trusts incoming CoS and DSCP values<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Check Global QoS Status<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show mls qos<\/code><\/td>\n<td style=\"text-align: left;\">Active by default; check policies via <code>show policy-map<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Check Interface Trust State<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show mls qos interface &lt;id&gt; trust<\/code><\/td>\n<td style=\"text-align: left;\">Check attached policy via <code>show run interface &lt;id&gt;<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Verify Active Service Policies<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show policy-map interface &lt;id&gt;<\/code><\/td>\n<td style=\"text-align: left;\"><code>show policy-map interface &lt;id&gt;<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Inspect Marking &amp; Queue Maps<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show mls qos maps dscp-output-q<\/code><\/td>\n<td style=\"text-align: left;\"><code>show table-map<\/code> and <code>show platform hardware fed switch active qos queue config interface &lt;id&gt;<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Check Hardware Queue Drops<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show mls qos interface &lt;id&gt; statistics<\/code><\/td>\n<td style=\"text-align: left;\"><code>show platform hardware fed switch active qos queue stats interface &lt;id&gt;<\/code><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>View DSCP\/CoS Traffic Counters<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show mls qos interface &lt;id&gt; statistics<\/code><\/td>\n<td style=\"text-align: left;\"><code>show platform hardware fed switch active qos dscp-cos counters interface &lt;id&gt;<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Key Takeaway:<\/strong> Always match your verification syntax to your switch&#8217;s operating system\u2014use <code>show policy-map<\/code> and <code>show platform hardware fed<\/code> commands on IOS-XE Catalyst 9000 switches, and reserve <code>show mls qos<\/code> for legacy IOS platforms.<\/p>\n<p>Once you know which architecture your switch runs, you can execute the exact CLI verification commands to inspect your configuration and port states.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"CLI_Command_Template_for_Verifying_Cisco_Switch_QoS_Status\"><\/span>CLI Command Template for Verifying Cisco Switch QoS Status<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use the following CLI commands to verify global QoS definitions, active interface service policies, AutoQoS profiles, and port trust configurations. Replace <code>&lt;interface-id&gt;<\/code> with your target switch port (for example, <code>GigabitEthernet1\/0\/1<\/code> or <code>TenGigabitEthernet1\/1\/1<\/code>).<\/p>\n<pre><code class=\"language-ios\">! ==========================================================\n! 1. VERIFY GLOBAL QOS DEFINITIONS (MQC - IOS &amp; IOS-XE)\n! ==========================================================\n! List all configured traffic classification rules (DSCP, CoS, ACLs)\nshow class-map\n\n! Display all defined QoS policies, bandwidth allocations, and policers\nshow policy-map\n\n! Verify marking translation tables (e.g., CoS-to-DSCP or policed-dscp maps)\nshow table-map\n\n! ==========================================================\n! 2. CHECK INTERFACE SERVICE POLICIES &amp; PORT CONFIGURATION\n! ==========================================================\n! Check which service-policy or trust commands are applied to a port\nshow running-config interface &lt;interface-id&gt;\n\n! View active ingress and egress policy statistics on a specific port\nshow policy-map interface &lt;interface-id&gt;\n\n! Filter policy verification to only ingress (marking\/policing) or egress (queuing)\nshow policy-map interface &lt;interface-id&gt; input\nshow policy-map interface &lt;interface-id&gt; output\n\n! ==========================================================\n! 3. VERIFY AUTOQOS STATUS (VOIP, VIDEO, &amp; TRUST PROFILES)\n! ==========================================================\n! Display all interfaces where AutoQoS is currently enabled\nshow auto qos\n\n! Check the specific AutoQoS profile (e.g., trust, voip cisco-phone) on one port\nshow auto qos interface &lt;interface-id&gt;\n\n! ==========================================================\n! 4. CHECK LEGACY MLS QOS STATUS &amp; TRUST (CATALYST 2960\/3750)\n! ==========================================================\n! Confirm whether MLS QoS is globally enabled on legacy IOS switches\nshow mls qos\n\n! Verify port trust state (trust dscp, trust cos, untrusted) and default CoS\nshow mls qos interface &lt;interface-id&gt; trust\n\n! Check legacy Shaped\/Weighted Round Robin (SRR\/WRR) queue settings\nshow mls qos interface &lt;interface-id&gt; queueing\n<\/code><\/pre>\n<p><strong>Key Takeaway:<\/strong> Confirming that a <code>policy-map<\/code> exists globally is not enough; always verify that <code>service-policy input<\/code> or <code>service-policy output<\/code> is actively bound to the target <code>&lt;interface-id&gt;<\/code>.<\/p>\n<p>Running these commands generates detailed real-time telemetry, making it essential to understand how to parse the statistical output of an active service policy.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_to_Read_and_Interpret_show_policy-map_interface_Output\"><\/span>How to Read and Interpret <code>show policy-map interface<\/code> Output<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The <code>show policy-map interface &lt;interface-id&gt;<\/code> command is the primary tool for verifying how a Cisco switch classifies, remarks, polices, and queues live traffic. Consider the following output from an egress policy on a Catalyst switch:<\/p>\n<pre><code class=\"language-text\">Switch# show policy-map interface GigabitEthernet1\/0\/1 output\n GigabitEthernet1\/0\/1\n\n  Service-policy output: PMAP-CAMPUS-EGRESS\n\n    Class-map: CMAP-VOICE-PRIORITY (match-any)\n      148290 packets, 29658000 bytes\n      5 minute offered rate 64000 bps, drop rate 0000 bps\n      Match: ip dscp ef (46)\n      Priority: 10% (100000 kbps), burst bytes 2500000,\n      Priority Level: 1\n      Queueing\n      queue limit 1200 packets\n      (queue depth\/total drops\/no-buffer drops) 0\/0\/0\n      (pkts output\/bytes output) 148290\/29658000\n\n    Class-map: CMAP-MULTIMEDIA (match-any)\n      52100 packets, 62520000 bytes\n      5 minute offered rate 412000 bps, drop rate 0000 bps\n      Match: ip dscp af41 (34) af42 (36)\n      Queueing\n      bandwidth remaining ratio 40\n      queue-limit 2400 packets\n      (queue depth\/total drops\/no-buffer drops) 0\/142\/0\n      (pkts output\/bytes output) 51958\/62349600\n\n    Class-map: class-default (match-any)\n      9841220 packets, 11809464000 bytes\n      5 minute offered rate 84500000 bps, drop rate 12000 bps\n      Match: any\n      Queueing\n      bandwidth remaining ratio 25\n<\/code><\/pre>\n<p>Follow this step-by-step sequence to interpret the metrics accurately:<\/p>\n<ol>\n<li><strong>Verify Policy Direction and Evaluation Order:<\/strong> Check the <code>Service-policy input:<\/code> or <code>Service-policy output:<\/code> header first. Cisco switches evaluate packets against <code>Class-map<\/code> blocks sequentially from top to bottom. Note whether the class uses <code>match-any<\/code> (logical OR) or <code>match-all<\/code> (logical AND). Any traffic that fails to match user-defined classes falls into <code>class-default<\/code> at the bottom.<\/li>\n<li><strong>Validate Classification via Packet and Byte Counters:<\/strong> Inspect the <code>&lt;X&gt; packets, &lt;Y&gt; bytes<\/code> line and the <code>5 minute offered rate<\/code> directly beneath each class-map name. If you have active VoIP calls on the link but <code>CMAP-VOICE-PRIORITY<\/code> shows <code>0 packets<\/code> while <code>class-default<\/code> increments rapidly, upstream devices or ingress policies are failing to mark traffic as DSCP <code>ef (46)<\/code> (or the ingress port is rewriting markings to <code>0<\/code>).<\/li>\n<li><strong>Evaluate Priority Servicing vs. Bandwidth Ratios:<\/strong> Look for <code>Priority: &lt;X&gt;% (&lt;Y&gt; kbps)<\/code> and <code>Priority Level: 1<\/code> (or <code>2<\/code>). On Cisco switches, strict priority queues are serviced immediately ahead of standard queues to minimize latency and jitter, but they are also internally policed to their configured percentage during congestion so they cannot starve lower-priority traffic. Non-priority classes use <code>bandwidth remaining ratio<\/code> to divide the leftover link capacity proportionally.<\/li>\n<li><strong>Compare Offered Packets Against Output and Drop Counters:<\/strong> Compare the top-level matched packets (<code>52100 packets<\/code> in <code>CMAP-MULTIMEDIA<\/code>) against <code>(pkts output\/bytes output)<\/code> (<code>51958<\/code> packets) and <code>(queue depth\/total drops\/no-buffer drops)<\/code> (<code>0\/142\/0<\/code>). Any discrepancy between matched packets and output packets is reflected in <code>total drops<\/code> or policer <code>exceeded<\/code>\/<code>violated<\/code> counters (on ingress policies), pinpointing exactly which application class is experiencing congestion.<\/li>\n<\/ol>\n<p><strong>Key Takeaway:<\/strong> Non-zero match counters prove your classification rules work, while the difference between matched packets and <code>(pkts output)<\/code> reveals whether a specific traffic class is being throttled or dropped.<\/p>\n<p>While software-polled policy-map counters provide a solid overview of class performance, diagnosing transient microbursts or buffer starvation requires inspecting the switch&#8217;s hardware ASIC queues directly.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_to_Check_and_Troubleshoot_QoS_Queue_Drops_at_the_Hardware_Level\"><\/span>How to Check and Troubleshoot QoS Queue Drops at the Hardware Level<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When users report voice choppiness, video pixelation, or TCP retransmissions\u2014especially on ports stepping down from 10 Gbps uplinks to 1 Gbps access links\u2014hardware egress buffers may be overflowing even when average link utilization appears low. Follow these steps to isolate and troubleshoot hardware queue drops:<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Check_High-Level_Interface_Output_Drops\"><\/span>Step 1: Check High-Level Interface Output Drops<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Start by checking whether the physical interface reports aggregate outbound drops:<\/p>\n<pre><code class=\"language-ios\">Switch# show interfaces GigabitEthernet1\/0\/1 | include output drops|Queueing\n  Input queue: 0\/2000\/0\/0 (size\/max\/drops\/flushes); Total output drops: 48291\n  Queueing strategy: Class-based queueing\n<\/code><\/pre>\n<p>If <code>Total output drops<\/code> is incrementing, one or more hardware egress queues on that port are exhausting their allocated buffer thresholds.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Inspect_Hardware_ASIC_Queue_Statistics_IOS-XE_Catalyst_9000\"><\/span>Step 2: Inspect Hardware ASIC Queue Statistics (IOS-XE \/ Catalyst 9000)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>On Catalyst 3650\/3850 and Catalyst 9000 switches, query the Forwarding Engine Driver (FED) to see exact enqueue and drop counts per hardware queue (<code>Queue 0<\/code> through <code>Queue 7<\/code>) and per drop threshold (<code>TH0<\/code>, <code>TH1<\/code>, <code>TH2<\/code>):<\/p>\n<pre><code class=\"language-ios\">Switch# show platform hardware fed switch active qos queue stats interface GigabitEthernet1\/0\/1\n----------------------------------------------------------------------------------------------\nAsic:0 Core:0 DATA Port:0 GPN:1 LinkSpeed:0x1\nInterface: GigabitEthernet1\/0\/1 (0x1)\n----------------------------------------------------------------------------------------------\nQueue   Enqueue-TH0         Enqueue-TH1         Enqueue-TH2         \n----------------------------------------------------------------------------------------------\n0       0                   0                   4589210             \n1       148290              0                   0                   \n2       0                   51958               0                   \n----------------------------------------------------------------------------------------------\nQueue   Drop-TH0            Drop-TH1            Drop-TH2            SBufDrop            QebDrop\n----------------------------------------------------------------------------------------------\n0       0                   0                   48149               48149               0\n1       0                   0                   0                   0                   0\n2       0                   142                 0                   142                 0\n<\/code><\/pre>\n<p>Interpret the hardware FED fields as follows:<br \/>\n* <strong>Enqueue-TH0 \/ TH1 \/ TH2:<\/strong> Packets successfully admitted into the hardware queue under Threshold 0, Threshold 1, or Threshold 2 (higher thresholds typically accommodate higher-priority DSCP markings within the same queue).<br \/>\n* <strong>Drop-TH0 \/ TH1 \/ TH2:<\/strong> Weighted Tail Drop (WTD) counters showing packets discarded because that specific threshold exceeded its limit.<br \/>\n* <strong>SBufDrop (Shared Buffer Drops):<\/strong> Packets dropped because the queue consumed its dedicated buffer reservation and the ASIC&#8217;s shared memory pool was also full\u2014a classic signature of microburst congestion.<br \/>\n* <strong>QebDrop (Queue Entry Buffer Drops):<\/strong> Packet descriptor exhaustion at the ASIC level, usually seen during extreme small-packet floods.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Check_Hardware_Queue_Drops_on_Legacy_MLS_QoS_Switches\"><\/span>Step 3: Check Hardware Queue Drops on Legacy MLS QoS Switches<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If you are troubleshooting a legacy Catalyst 2960 or 3750 switch (as differentiated in the platform table earlier), run <code>show mls qos interface &lt;interface-id&gt; statistics<\/code> and inspect the bottom <code>output queues dropped<\/code> block:<\/p>\n<pre><code class=\"language-text\">  output queues enqueued:\n   queue:    threshold1   threshold2   threshold3\n  -----------------------------------------------\n   queue 0:           0         1420        89210\n   queue 1:      541200            0            0\n\n  output queues dropped:\n   queue:    threshold1   threshold2   threshold3\n  -----------------------------------------------\n   queue 0:           0           84         3102\n   queue 1:           0            0            0\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Baseline_Counters_and_Tune_Queue_Buffers\"><\/span>Step 4: Baseline Counters and Tune Queue Buffers<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Because hardware counters accumulate since the last reboot, clear the statistics to verify whether drops are actively occurring right now:<\/p>\n<pre><code class=\"language-ios\">! On Cisco IOS-XE switches\nSwitch# clear platform hardware fed switch active qos statistics interface GigabitEthernet1\/0\/1\n\n! Standard interface counter reset\nSwitch# clear counters GigabitEthernet1\/0\/1\n<\/code><\/pre>\n<p>If non-priority queues (<code>Queue 0<\/code> or <code>class-default<\/code>) show recurring <code>SBufDrop<\/code> increments during normal business hours while average link bandwidth remains well below 100%, increase the soft buffer allocation inside your egress <code>policy-map<\/code> using the <code>queue-buffers ratio<\/code> command on IOS-XE (or <code>mls qos queue-set output &lt;id&gt; buffers<\/code> on legacy IOS).<\/p>\n<p><strong>Key Takeaway:<\/strong> Always inspect hardware-level FED queue counters (<code>Drop-THx<\/code> and <code>SBufDrop<\/code>) to distinguish harmless bulk-traffic tail drops in <code>Queue 0<\/code> from critical real-time packet loss in priority queues.<\/p>\n<p>Because CLI counters only reflect cumulative totals since the last reset, tracking intermittent congestion over days or weeks requires polling these QoS metrics into a centralized monitoring platform.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Best_Network_Monitoring_Tools_to_Track_Cisco_Switch_QoS_Metrics\"><\/span>Best Network Monitoring Tools to Track Cisco Switch QoS Metrics<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Relying solely on CLI commands makes it difficult to correlate temporary voice or application degradation with overnight backup spikes or daytime microbursts. Network monitoring tools solve this by polling Cisco&#8217;s <code>CISCO-CLASS-BASED-QOS-MIB<\/code> (CBQoS MIB) via SNMP or subscribing to IOS-XE Model-Driven Telemetry streams.<\/p>\n<ul>\n<li><strong>1. Cisco Catalyst Center (formerly Cisco DNA Center):<\/strong> Cisco&#8217;s native management and assurance appliance for Catalyst 9000 environments. It uses streaming telemetry and SNMP to visualize per-queue bandwidth utilization, end-to-end DSCP marking preservation, and hardware queue drops across the fabric without manual MIB configuration.<\/li>\n<li><strong>2. SolarWinds Network Traffic Analyzer (NTA) &amp; NPM:<\/strong> Combines NetFlow\/IPFIX flow analysis with SNMP CBQoS polling. SolarWinds charts pre-policy versus post-policy byte rates, highlights policer drops per class-map, and lets engineers correlate DSCP class spikes with specific top-talker IP addresses.<\/li>\n<li><strong>3. ManageEngine OpManager (with NetFlow Analyzer Add-on):<\/strong> Offers built-in Cisco CBQoS monitoring templates that break down traffic consumption by class-map, queuing policy, and match statement. It supports automated threshold alerts whenever egress queue drop rates exceed defined percentages.<\/li>\n<li><strong>4. Paessler PRTG Network Monitor:<\/strong> Provides a dedicated <strong>SNMP Cisco CBQoS Sensor<\/strong> that tracks individual class-map throughput, pre-policy\/post-policy bytes, buffer drops, and policer violations with granular per-channel alerting.<\/li>\n<li><strong>5. Telegraf + Prometheus + Grafana (Open-Source Telemetry Stack):<\/strong> Ideal for modern Cisco IOS-XE switches supporting Model-Driven Telemetry (gNMI\/NETCONF). By streaming YANG operational models (such as <code>Cisco-IOS-XE-interfaces-oper<\/code> and policy-map statistics) at 5- to 10-second intervals, this stack detects sub-minute microburst drops that standard 5-minute SNMP pollers miss.<\/li>\n<\/ul>\n<p><strong>Key Takeaway:<\/strong> Use SNMP CBQoS polling for historical trend reporting across mixed switch fleets, or deploy streaming telemetry via Catalyst Center or Telegraf\/Grafana to catch sub-minute microburst drops on Catalyst 9000 switches.<\/p>\n<p>When configuring telemetry collectors or auditing platform-specific hardware queue limits, always cross-reference Cisco&#8217;s authoritative platform documentation.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Official_Cisco_Catalyst_QoS_Documentation_and_Command_References\"><\/span>Official Cisco Catalyst QoS Documentation and Command References<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Hardware queue architectures, buffer ratios, and supported MQC keywords vary by ASIC generation (such as UADP 2.0, UADP 3.0, and Cisco Silicon One) and IOS-XE release train. Reference the following official Cisco documentation manuals and MIB specifications for platform-exact verification definitions:<\/p>\n<ul>\n<li><strong>Quality of Service Configuration Guide, Cisco IOS XE (Catalyst 9200 \/ 9300 \/ 9400 \/ 9500 Switches):<\/strong> The primary platform specification grouped by IOS-XE release (16.x and 17.x). Defines default 8-queue (<code>2P6Q3T<\/code>) hardware mappings, MQC restrictions, AutoQoS macro expansions, and FED verification commands.<\/li>\n<li><strong>Cisco IOS Quality of Service Solutions Command Reference:<\/strong> The alphabetical syntax dictionary detailing every command argument and output field for <code>show policy-map interface<\/code>, <code>show class-map<\/code>, <code>show table-map<\/code>, and <code>show auto qos<\/code>.<\/li>\n<li><strong>Catalyst 3750-X and 3560-X \/ Catalyst 2960-X Switch Software Configuration Guide (Configuring QoS):<\/strong> The authoritative engineering manual for legacy MLS QoS platforms, specifying Shaped Round Robin (SRR) weight calculations, queue-set buffer allocations, and <code>show mls qos<\/code> diagnostic syntax.<\/li>\n<li><strong>Enterprise QoS Solution Reference Network Design (SRND) &amp; Cisco Validated Designs (CVD):<\/strong> Official architecture guides detailing RFC 4594 DSCP marking standards, campus trust boundary placement, and recommended queue buffer ratios for voice, video, and transactional data.<\/li>\n<li><strong>Cisco SNMP Object Navigator \u2014 <code>CISCO-CLASS-BASED-QOS-MIB<\/code> (OID <code>1.3.6.1.4.1.9.9.166<\/code>):<\/strong> The formal MIB specification mapping CLI <code>show policy-map interface<\/code> counters to SNMP tables, including <code>cbQosCMStatsTable<\/code> (class-map traffic counters), <code>cbQosQueueingStatsTable<\/code> (queue depths and drops), and <code>cbQosPoliceStatsTable<\/code> (conformed, exceeded, and violated policer statistics).<\/li>\n<\/ul>\n<p><strong>Key Takeaway:<\/strong> Consult the platform-specific <em>Quality of Service Configuration Guide<\/em> matching your exact switch model and IOS-XE version whenever verifying ASIC queue-to-threshold mappings or hardware buffer limits.<\/p>\n<p>Checking QoS on a Cisco switch follows a clear hierarchy: confirm your switch platform&#8217;s QoS architecture (IOS-XE MQC versus legacy MLS QoS), verify that service policies are bound to the right interfaces, confirm live traffic classification in <code>show policy-map interface<\/code>, and inspect hardware ASIC counters for threshold or shared buffer drops. Combining these targeted CLI checks with continuous CBQoS or streaming telemetry monitoring ensures your critical voice, video, and business traffic remains protected even during peak network congestion.<\/p>\n<div class='sfsi_Sicons' style='width: 100%; display: inline-block; vertical-align: middle; text-align:left'><div style='margin:0px 8px 0px 0px; line-height: 24px'><span>Please follow and like us:<\/span><\/div><div class='sfsi_socialwpr'><div class='sf_fb_share sf_icon' style='text-align:left;vertical-align: middle;'><a href='https:\/\/www.facebook.com\/sharer\/sharer.php?u=https%3A%2F%2Fcciedump.spoto.net%2Fblog%2Fhow-to-check-qos-on-cisco-switch_24619.html' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Facebook Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/fbshare_bck.png'  \/><\/a><\/div><div class='sf_twiter sf_icon' style='display: inline-block;vertical-align: middle;width: auto;margin-left: 7px;'>\r\n\t\t\t\t\t\t<a target='_blank' href='https:\/\/twitter.com\/intent\/tweet?text=How+to+Check+QoS+on+Cisco+Switch+https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html'style='display:inline-block' >\r\n\t\t\t\t\t\t\t<img data-pin-nopin= true width='auto' class='sfsi_wicon' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/en_US_Tweet.svg' alt='Tweet' title='Tweet' >\r\n\t\t\t\t\t\t<\/a>\r\n\t\t\t\t\t<\/div><div class='sf_pinit sf_icon' style='text-align:left;vertical-align: middle;float:left;line-height: 33px;width:auto;margin: 0 -2px;'><a href='#'  onclick='sfsi_pinterest_modal_images(event,\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\",\"How to Check QoS on Cisco Switch\")' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Pin Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/share_icons\/Pinterest_Save\/en_US_save.svg'  \/><\/a><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Verifying Quality of Service (QoS) on a Cisco switch requires more than just inspecting the running configuration. Because modern Catalyst switches handle packet classification, policing, and queuing directly within hardware ASICs, a policy that looks valid in the configuration file may not actually match traffic or prevent buffer exhaustion during microbursts. Properly auditing QoS means&#8230; &raquo; <a class=\"read-more-link\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\">read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,608],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v18.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to Check QoS on Cisco Switch - SPOTO Official Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Check QoS on Cisco Switch - SPOTO Official Blog\" \/>\n<meta property=\"og:description\" content=\"Verifying Quality of Service (QoS) on a Cisco switch requires more than just inspecting the running configuration. Because modern Catalyst switches handle packet classification, policing, and queuing directly within hardware ASICs, a policy that looks valid in the configuration file may not actually match traffic or prevent buffer exhaustion during microbursts. Properly auditing QoS means... &raquo; read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\" \/>\n<meta property=\"og:site_name\" content=\"SPOTO Official Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T09:53:41+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"SPOTO \u7f16\u8f91\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\",\"name\":\"SPOTO Club\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"caption\":\"SPOTO Club\"},\"logo\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\"},\"description\":\"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205\",\"sameAs\":[\"https:\/\/cciedump.spoto.net\/\"]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/\",\"name\":\"SPOTO Official Blog\",\"description\":\"Focus on Online IT Training for 20+ Years\",\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#webpage\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\",\"name\":\"How to Check QoS on Cisco Switch - SPOTO Official Blog\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\"},\"datePublished\":\"2026-11-17T09:53:41+00:00\",\"dateModified\":\"2026-11-17T09:53:41+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/cciedump.spoto.net\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Check QoS on Cisco Switch\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#webpage\"},\"author\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\"},\"headline\":\"How to Check QoS on Cisco Switch\",\"datePublished\":\"2026-11-17T09:53:41+00:00\",\"dateModified\":\"2026-11-17T09:53:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#webpage\"},\"wordCount\":1712,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"articleSection\":[\"CCNA Certification\",\"Cisco Certification\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\",\"name\":\"SPOTO \u7f16\u8f91\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"caption\":\"SPOTO \u7f16\u8f91\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Check QoS on Cisco Switch - SPOTO Official Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html","og_locale":"en_US","og_type":"article","og_title":"How to Check QoS on Cisco Switch - SPOTO Official Blog","og_description":"Verifying Quality of Service (QoS) on a Cisco switch requires more than just inspecting the running configuration. Because modern Catalyst switches handle packet classification, policing, and queuing directly within hardware ASICs, a policy that looks valid in the configuration file may not actually match traffic or prevent buffer exhaustion during microbursts. Properly auditing QoS means... &raquo; read more","og_url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html","og_site_name":"SPOTO Official Blog","article_published_time":"2026-11-17T09:53:41+00:00","twitter_card":"summary_large_image","twitter_misc":{"Written by":"SPOTO \u7f16\u8f91","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Person","Organization"],"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638","name":"SPOTO Club","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","caption":"SPOTO Club"},"logo":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo"},"description":"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205","sameAs":["https:\/\/cciedump.spoto.net\/"]},{"@type":"WebSite","@id":"https:\/\/cciedump.spoto.net\/blog\/#website","url":"https:\/\/cciedump.spoto.net\/blog\/","name":"SPOTO Official Blog","description":"Focus on Online IT Training for 20+ Years","publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#webpage","url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html","name":"How to Check QoS on Cisco Switch - SPOTO Official Blog","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#website"},"datePublished":"2026-11-17T09:53:41+00:00","dateModified":"2026-11-17T09:53:41+00:00","breadcrumb":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cciedump.spoto.net\/blog"},{"@type":"ListItem","position":2,"name":"How to Check QoS on Cisco Switch"}]},{"@type":"Article","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#article","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#webpage"},"author":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1"},"headline":"How to Check QoS on Cisco Switch","datePublished":"2026-11-17T09:53:41+00:00","dateModified":"2026-11-17T09:53:41+00:00","mainEntityOfPage":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#webpage"},"wordCount":1712,"commentCount":0,"publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"articleSection":["CCNA Certification","Cisco Certification"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-qos-on-cisco-switch_24619.html#respond"]}]},{"@type":"Person","@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1","name":"SPOTO \u7f16\u8f91","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","caption":"SPOTO \u7f16\u8f91"}}]}},"_links":{"self":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24619"}],"collection":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/comments?post=24619"}],"version-history":[{"count":0,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24619\/revisions"}],"wp:attachment":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/media?parent=24619"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/categories?post=24619"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/tags?post=24619"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}