{"id":464,"date":"2013-10-24T10:46:11","date_gmt":"2013-10-24T08:46:11","guid":{"rendered":"http:\/\/www.netnea.com\/cms\/?p=464"},"modified":"2023-11-14T18:54:39","modified_gmt":"2023-11-14T17:54:39","slug":"qos-on-cisco-asr","status":"publish","type":"post","link":"https:\/\/www.netnea.com\/cms\/2013\/10\/24\/qos-on-cisco-asr\/","title":{"rendered":"QoS on Cisco ASR"},"content":{"rendered":"<p>In CISCO-CLASS-BASED-QOS-MIB.my, Cisco says:<\/p>\n<blockquote><p>Service policy is a policymap that is being attached to a logical interface. Because a policymap can also be a part of the hierarchical structure (inside a classmap), only a policymap that is directly attached to a logical interface is considered a service policy. Each service policy is uniquely identified by an index called cbQosPolicyIndex. This number is <strong>usually identical<\/strong> to its cbQosObjectsIndex as a policymap.<\/p><\/blockquote>\n<p>Sadly, Cisco doesn&#8217;t explain when it&#8217;s identical or not, and when not, how to find the matching cbQosConfigIndex. And here we are, I do have a few bad players, namely the Cisco ASR 1001. All other Cisco routers I analysed have identical values for \u00a0cbQosPolicyIndex and\u00a0cbQosObjectsIndex, but those beasts don&#8217;t. The most expensive Cisco routers are somewhat different then the basic crop. But anyway, I probably shall not complain, the MIB says &#8220;usually&#8221;, so it seems they protected themselves in a very inelegant but efficient way.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-465  alignleft\" style=\"margin: 8px;\" alt=\"Cisco ASR 1001\" src=\"http:\/\/www.netnea.com\/cms\/wp-content\/uploads\/2013\/10\/asr1001.png\" width=\"400\" height=\"116\" \/><br \/>\nI&#8217;m not really sure what is the best way to solve this problem, maybe some fuzzy-matching of top-level policy-maps, e.g. those having no parents in the object tree ? Will see.<\/p>\n<p>Update, <a title=\"QoS parsing on Cisco routers\" href=\"http:\/\/www.netnea.com\/cms\/2013\/11\/19\/qos-parsing-on-cisco-routers\/\">problem fixed<\/a> through a parser rewrite.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In CISCO-CLASS-BASED-QOS-MIB.my, Cisco says: Service policy is a policymap that is being attached to a logical interface. Because a policymap can also be a part of the hierarchical structure (inside a classmap), only a policymap that is directly attached to a logical interface is considered a service policy. Each service policy is uniquely identified by [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[22,21],"class_list":{"0":"post-464","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-nms","7":"tag-cisco","8":"tag-qos","9":"czr-hentry"},"_links":{"self":[{"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/posts\/464","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/comments?post=464"}],"version-history":[{"count":4,"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/posts\/464\/revisions"}],"predecessor-version":[{"id":490,"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/posts\/464\/revisions\/490"}],"wp:attachment":[{"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/media?parent=464"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/categories?post=464"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.netnea.com\/cms\/wp-json\/wp\/v2\/tags?post=464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}