Someone will have to correct me if I am wrong but CBWFQ is not supported on Virtual interfaces like Dialers, - basically it tries to apply hardware queueing on a virtual interface. You can use nested policy-maps though. Here is an example of what I had to do for a connection that the provider had given me where 6 megs where for internet and 14 megs were for MPLS connection and in order to apply QoS to a sub-interface I used nested policy map but it will be the same concept for Dialers I believe.
I have tried entering it on to atm0/0/0, atm0/0/0.38 and on to the PVC. I get the same GTS: Not supported on this interface on 0/0/0 & 0/0/0.38, I tried it on the PVC 0/38, it goes in but does not appear in the config. I have read up on the subject and you can apply it to virtual interfaces just as long as the CBFWQ is nested and I am sure this config is.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...