I have a requirement to deploy Cisco 8811 IP Phones on our current Communications Manager 10.0.1 which it at present does not support.  According to the compatibility matrix there is "No Devpack Available" for this version.  There is a devpack available for version 10.5.1 however this system is running under HCS version 10.0.1 which prevents me from upgrading to 10.5.1. http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/compat/devpack_comp_mtx.html Does anyone know if it is possible to apply the 10.5.1 devpack to 10.0.1 Communications Manager?  If not, is there any other way to deploy an 8811 on version 10.0.1?   ... View more

I am reading up on the PIMG's for an upcoming installation.  On page 2-4 of the Integration guide it states the following two points which seem to contradict each other. Does it send all calls to the Sub then Pub (As we would normally configure for CUCM) or does it balance the voice messaging traffic between the Connection servers? Which one is it? ... View more

I have two separate Communications Manager clusters running 9.1.1.20000-5.  It was brought to my attention that a user was not showing up with the correct extension.  When I performed a manual synchronization I could see an error displayed on the screen showing that it failed to connect to LDAP server x.x.x.x. I have three LDAP servers defined for both and in one cluster the LDAP server that couldn't be reached was the first one in the list.  In the second cluster it was the last one in the list.  As soon as I removed the LDAP server that the CUCM couldn't communicate with and performed a manual synchronization the update occurred. Is anyone aware of a bug related to this?  LDAP synchronization shouldn't fail if only one of the servers defined isn't reachable. I checked the bug toolkit but don't see any open bugs related to this and I am currently running the latest version of code that I am aware of. ... View more

As per the command line reference you can enter a configuration statement under call-manager-fallback that looks like this: Router(config-cm-fallback)#max-dn 3 dual-line 1 octo-line When you do this the router outputs the following: *Nov  8 21:59:34.323: %LINK-3-UPDOWN: Interface ephone_dsp DN 1.1, changed state to up *Nov  8 21:59:34.327: %LINK-3-UPDOWN: Interface ephone_dsp DN 1.2, changed state to up *Nov  8 21:59:34.335: %LINK-3-UPDOWN: Interface ephone_dsp DN 2.1, changed state to up *Nov  8 21:59:34.339: %LINK-3-UPDOWN: Interface ephone_dsp DN 2.2, changed state to up *Nov  8 21:59:34.347: %LINK-3-UPDOWN: Interface ephone_dsp DN 3.1, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 3.2, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.1, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.2, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.3, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.4, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.5, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.6, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.7, changed state to up *Nov  8 21:59:34.351: %LINK-3-UPDOWN: Interface ephone_dsp DN 4.8, changed st My question is this.  It would appear that the configuration statement above configures 3 dual-line directory numbers and 1 octo-line directory number.  How would one determine which phone will get the octo-line vs what phone will get the dual-line configuration?  If you cannot determine or configure which phone gets the octo-line configuration what is the purpose of having the ability to configure both? I have a situation where I want to configure dual-line on all the phones except the main line reception phone.  In SRST I'd like this phone to have an octo-line appearance to support the additional calls the main line receives.  I require SRST  because of the amount of phones (720 - the max supported). Is there a way to assign the octo-line to the main line reception phone?  If not what is the purpose of this command? Thanks, Marc ... View more

All. I just recently performed an upgrade test in a lab.  In this scenario I needed to change the IP addresses and host names of the Communications Manager.  I performed a back and restore and then upgraded that restore in a virtual machine.  I only restored the first node and then proceeded to change the ip addresses in the servers section of the GUI admin (servers are defined by IP) and then changed the IP of the first node in the CLI along with the hostname change after that.  When that was done I simply installed the four other subscribers in parallel with the new hostnames and IP addressess. Everything in Cisco Unified Reporting for the report Unified CM Database status shows green and all looks good.  The only thing that looks odd is a section of the report called Unified CM Services which still has some entries for the old host name and some lines that say bogusip in them. I'm wondering why I still have the references to the old publisher hostname and why I have the entries for bogusip.  They only appear to be on the publisher file.  All the subscribers look clean.  I am wondering if there is a way to clean this up and or if its something i need to be concerned about. I have changed the hostnames and IP's for this post.  Here is a brief description of them: Old IP               Old Hostname          New IP     New Hostname 10.26.1.1                                        10.1.1.2     siteacucms1 10.29.202.1                                    10.2.1.2     sitebcucms4   10.30.1.1                                        10.2.1.1     sitebcucms2 10.28.1.1                                        10.1.1.3     siteacucms3 10.31.1.1     oldsiteapub                    10.1.1.1    siteacucmp1 Server    services File 10.1.1.1    ### IDS BEGIN - DO NOT REMOVE siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 bogusip_10_1_1_2_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_1_1_2 bogusip_10_1_1_3_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_1_1_3 bogusip_10_2_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_2_1_1 bogusip_10_2_1_2_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_2_1_2 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 bogusip_10_1_1_2_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_1_1_2 bogusip_10_1_1_3_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_1_1_3 bogusip_10_2_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_2_1_1 bogusip_10_2_1_2_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_2_1_2 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 oldsiteapub_ccm8_6_2_21900_5    1500/tcp    # IDS on OLDSITEAPUB bogusip_10_1_1_2_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_1_1_2 bogusip_10_1_1_3_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_1_1_3 bogusip_10_2_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_2_1_1 bogusip_10_2_1_2_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_2_1_2 oldsiteapub_ccm8_6_2_21900_5    1500/tcp    # IDS on OLDSITEAPUB bogusip_10_26_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_26_1_1 bogusip_10_29_202_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_29_202_1 bogusip_10_30_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_30_1_1 bogusip_10_28_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_28_1_1 oldsiteapub_ccm8_6_2_21900_5    1500/tcp    # IDS on OLDSITEAPUB bogusip_10_26_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_26_1_1 bogusip_10_29_202_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_29_202_1 bogusip_10_30_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_30_1_1 bogusip_10_28_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_28_1_1 oldsiteapub_ccm8_6_2_21900_5    1500/tcp    # IDS on OLDSITEAPUB bogusip_10_26_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_26_1_1 bogusip_10_29_202_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_29_202_1 bogusip_10_30_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_30_1_1 bogusip_10_28_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_28_1_1 oldsiteapub_ccm8_6_2_21900_5    1500/tcp    # IDS on OLDSITEAPUB bogusip_10_26_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_26_1_1 bogusip_10_29_202_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_29_202_1 bogusip_10_30_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_30_1_1 bogusip_10_28_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_28_1_1 oldsiteapub_ccm8_6_2_21900_5    1500/tcp    # IDS on OLDSITEAPUB bogusip_10_26_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_26_1_1 bogusip_10_29_202_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_29_202_1 bogusip_10_30_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_30_1_1 bogusip_10_28_1_1_ccm8_6_2_21900_5    1500/tcp    # IDS on BogusIP_10_28_1_1 oldsiteapub_ccm8_6_2_21900_5        1500/tcp        # CCM IDS Server ### IDS END - DO NOT REMOVE 10.1.1.2    ### IDS BEGIN - DO NOT REMOVE siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucms1_ccm8_6_2_21900_5        1500/tcp        # CCM IDS Server ### IDS END - DO NOT REMOVE 10.1.1.3    ### IDS BEGIN - DO NOT REMOVE siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucms3_ccm8_6_2_21900_5        1500/tcp        # CCM IDS Server ### IDS END - DO NOT REMOVE 10.2.1.1    ### IDS BEGIN - DO NOT REMOVE siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 sitebcucms2_ccm8_6_2_21900_5        1500/tcp        # CCM IDS Server ### IDS END - DO NOT REMOVE 10.2.1.2    ### IDS BEGIN - DO NOT REMOVE siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 siteacucmp1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMP1 siteacucms1_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS1 siteacucms3_ccm8_6_2_21900_5    1500/tcp    # IDS on siteaCUCMS3 sitebcucms2_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS2 sitebcucms4_ccm8_6_2_21900_5    1500/tcp    # IDS on sitebCUCMS4 sitebcucms4_ccm8_6_2_21900_5        1500/tcp        # CCM IDS Server ### IDS END - DO NOT REMOVE Marc ... View more

Is there anyway to do this? The only way I can find so far is by a query as per below but I require the ability to specify specific DN's in a CSV file. In CUCM under Bulk Administration --> Phones --> Add/Update Lines --> Update Lines You can then search by: Directory Number Route Partition Line Description CSS (Phone) CSS (Line) Device Pool Device Description Line Position Unassigned DN Call Pickup Group ... View more

Page 10/78 of the Installing Cisco Unified Contact Center Express  Release 8.5(1) has a note stating... Note:  DNS configuration is mandatory for Unified CCX installation. Both Forward and Reverse records are required. The release notes for 8.5.1 in open caveats state: CSCtk05428 - Need to document DNS config as mandatory for UCCX installation The bug id referenced above has no details  when entered into the public bug toolkit.  I’ve also heard of an installation where  8.5.1 is running and DNS was not used and there have been no reports of any issues not having DNS installed I am trying to find out if it is actually mandatory for what particular reason?  What components rely on DNS and wont work if it is not used?  The SRND for CUCM 8.x states not to rely on DNS and thus change all hostnames to IP addresses which is what we have been doing for years now.  Is this not the case for UCCX? ... View more

I am looking to implement QoS on a Cat6509E running 12.2(33)SXH8a IOS.  The object of this implementation is to prioritize one specific data class while all others can be treated as default traffic.  QoS is currently disabled and thus all traffic is being handled as CoS 0. As Switch based QoS uses hardware queues I am trying to understand the best way to implement this solution as if I were working with two queues.  A priority queue and an "everything else" queue. After reading the documenation online I have come up with a couple of options.  I am hoping someone out there has done this before and can comment on what makes sense and what doesn't and even provide recommendations. The line card the ports are connected to is a WS-X6748-GE-TX. With QoS globally disabled I see the following when I issue the show queueing interface command     WRR bandwidth ratios:  100[queue 1]   0[queue 2]   0[queue 3]     queue-limit ratios:    100[queue 1]   0[queue 2]   0[queue 3] queue tail-drop-thresholds     --------------------------     1     100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8]     2     100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8]     3     100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] queue thresh cos-map     ---------------------------------------     1     1      0     1     2      1     1     3     1     4     1     5     1     6     1     7     1     8     2     1      2     2     2      3 4     2     3     2     4     2     5     2     6     2     7     2     8     3     1      6 7     3     2     3     3     3     4     3     5     3     6     3     7     3     8     4     1      5 When I enabled QoS the following changes were observed: WRR bandwidth ratios:  100[queue 1] 150[queue 2] 200[queue 3] queue-limit ratios:     50[queue 1]  20[queue 2]  15[queue 3]     queue tail-drop-thresholds     --------------------------     1     70[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8]     2     70[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8]     3     100[1] 100[2] 100[3] 100[4] 100[5] 100[6] 100[7] 100[8] So what I can see is that the WRR bandwidth ratios changed so that Q1 now does not get 100% of the bandwidth and actually gets the lowest amount of bandwith of the 3 WRR queues.  The queue limit ratios for the buffers were also changed alloting some of the buffers to the other two WRR queues. What I am considering doing is to:     - Utilize the PQ and WRR Q1 and to disable the other two WRR queues     - Assign all CoS values to Q1 except for CoS 5 which would be assigned to the PQ Implementing the following commands on the ports     - wrr-queue bandwidth 100 0 0     - wrr-queue queue-limit 85 0 15     - wrr-queue cos-map 1 1 0 1 2 3 4 6 7 I now see the following:     WRR bandwidth ratios:  100[queue 1]   0[queue 2]   0[queue 3]     queue-limit ratios:     85[queue 1]   0[queue 2]  15[queue 3] queue thresh cos-map     ---------------------------------------     1     1      0 1 2 3 4 6 7     1     2     1     3     1     4     1     5     1     6     1     7     1     8     2     1     2     2     2     3     2     4     2     5     2     6     2     7     2     8     3     1     3     2     3     3     3     4     3     5     3     6     3     7     3     8     4     1      5 I may actually map the other CoS values to Q1T2 instead of Q1T1 so that the drop thresholds are 100% instead of 70%. Does this make sense?  Will this give me the two queues I am looking for?  The original CoS to Queue mapping table breaks up the differenet CoS values into the different queues placing CoS 6 and CoS 7 into Q3T1.  If I lump them all into Q1T1 or Q1T2 could I be causing any issues?  Am I correct in recalling that specific core protocols might be tagged CoS 6 or CoS 7?  I am thinking it shouldnt matter as when QoS was disabled it was all being treated the same anyways (right?). Antother thing I noticed was that when changing the CoS to Q mapping it affected a group of 12 ports.  I really only need to do egress queuing on the WAN links however the qos command affects another 11 ports around it.  Should I be concerned about this?  Would it make sense to set the CoS to Q mapping the same for all ports on the switch? The final question I have is if I just enabled QoS globally and left the other settings as default could this have an adverse affect on the data traffic compared to when QoS was not enabled.  This would be in regards to buffers and bandwidth not being 100% assigned to a single queue.  If the only traffic in the network was either CoS 5 or CoS 0.  Could Q1 utilize the buffers and bandwidth assigned to those other two WRR queues that have no trafffic? If so.  What would be the better solution?  Customizing it to have two queues or just having all 4 and only utilizing 2 of them? Thanks ... View more