Hi,   We are facing an issue with our agents being placed in Reserve mode and unable to receive calls.  This is affecting multiple CSQ's.   When an agent receives a call their status is either never moving from reserved OR reverting back to reserved after a couple of minutes. While talking on an ACD call, a second call is routed to the agent (While in reserved status) and will not be rolled over to another available agent. I have found some information that the CTI Port CSS should be the same as the agents CSS? Can anyone assist with this, it would be greatly appreciated.    Thanks, ... View more

Hi,   We are having issues with our backup's using SFTP.  The SFTP server is running on Linux Centos OS 6, we are receiving a SSH connect error. I have appended the failed logs and steps taken when running a backup below.  Can anyone assist with this issue, it would be greatly appreciated. I'm not sure the issue is related to the Linux server being used?    Logged into the GUI, verified the backup configuration  - Attempted manual backup, backup failed at 75%  - Logged into the CLI, checked backup history, no recents backups  - Verified repository setup  - Reconfigured the SFTP repository  - Reconfigured the host keys for SFTP (RCA)  - Rerun the backup process, backup failed with the below errors  acs01/admin# backup Test repository acs01  % backup in progress: Starting Backup...10% completed  % Creating backup with timestamped filename: Test-190626-1057.tar.gpg  Please enter backup encryption password [8-32 chars]:  Please enter the password again:  % backup in progress: Backing up ADEOS configuration...55% completed  Calculating disk size for /opt/backup/backup-Test-1561564640  Total size of backup files are 64 M.  Max Size defined for backup files are 105277 M.  % backup in progress: Moving Backup file to the repository...75% completed  % Error: RSA host key for remote server has been changed  % Please add the host key using the crypto host_key exec command  % SSH connect error  acs01/admin#  ... View more

Hi,   We have an end user that has Cisco Attendant Console Standard ver. 12 that is no longer able to sign-on. We upgraded the OS from Windows 7 64 to Windows 10 64. I believe the issue is with the TSP driver on the client machine, can anyone provide a link to the documentation that explains how to install/re-install the TSP driver on the client computer? Your assistance would be greatly appreciated.   Thanks, ... View more

Hi, We had a issue on Sunday 4/28 for our CCX engine service being in "Partial Service" status.  We had to reboot the UCCX cluster to resolve the issue. We have notice after the reboot when running reports for the current week the data is blank, when running reports prior to the reboot information does produce.  We have verified no issues with database replication and restarted the CUIC service to no avail.  Can anyone advise what other steps can be taken to troubleshoot this issue? Any assistance would be greatly appreciated.   Thanks,   ... View more

Hi, We have a issue with on UCS system at one of our location licensing not synchronizing.  I have been unable to find any documentation on licensing and troubleshooting for this model.  Can anyone assistance with locating the licensing documentation. Any assistance would be greatly appreciated.   Thanks, ... View more

Hi,   We want to add some new AP's to our environment and want to you ports on a specific switch stack member (5).  I reviewed some documentation and found to connect to the specific member I can use the "Session x" command. But the documentation inform only the show and debug commands are available. We need to provide POE to port 1-7 on the stack member, can anyone confirm how to accomplish this?  My thoughts are below for connecting to the stack member and configuring the ports to receive power.   Test# session 5 Test-5# config t config t interface range gi1/0/1-7 power inline auto end   ... View more

Hi,   We have a 3850 switch that is reporting the below Vlan flapping error on multiple trunk interfaces. When researching this error I found a bug for this model with the exact symptoms but for port-channels. The bug CSCut87285  inform this is seen on 3850 stacks running 03.06.00E or later. The switch is running IOS cat3k_caa-universalk9.SPA.03.07.04.E.152-3.E4.bin which falls within the IOS range for this issue according to the bug documentation. My questions is since the bug inform of port channels does this apply to trunk ports as well? Since everything else matches per the documentation I believe this apply. Any confirmation would be greatly appreciated.   System  version 15.2 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption service compress-config ! hostname 3850-CORE1 ! boot-start-marker boot system switch all flash:cat3k_caa-universalk9.SPA.03.07.04.E.152-3.E4.bin     Logs *Jan 29 16:03:52.201: %SW_MATM-4-MACFLAP_NOTIF: Host 7081.eb5d.a0ac in vlan 130 is flapping between port Gi2/0/10 and port Te1/0/6 *Jan 29 16:03:52.300: %SW_MATM-4-MACFLAP_NOTIF: Host 7081.eb5d.a0ac in vlan 130 is flapping between port Gi2/0/10 and port Te1/0/6 (KAH-3850-CORE1-1) *Jan 29 16:04:37.261: %SW_MATM-4-MACFLAP_NOTIF: Host 544e.9001.6945 in vlan 120 is flapping between port Gi3/0/8 and port Gi3/0/7 *Jan 29 16:04:37.284: %SW_MATM-4-MACFLAP_NOTIF: Host 544e.9001.6945 in vlan 120 is flapping between port Gi3/0/8 and port Gi3/0/7 (KAH-3850-CORE1-1) *Jan 29 16:05:14.077: %SW_MATM-4-MACFLAP_NOTIF: Host a0d7.9558.fc3d in vlan 130 is flapping between port Gi2/0/25 and port Gi3/0/24 *Jan 29 16:05:14.164: %SW_MATM-4-MACFLAP_NOTIF: Host a0d7.9558.fc3d in vlan 130 is flapping between port Gi2/0/25 and port Gi3/0/24 (KAH-3850-CORE1-1) *Jan 29 16:06:37.475: %SW_MATM-4-MACFLAP_NOTIF: Host 0878.0816.4924 in vlan 120 is flapping between port Te1/0/5 and port Te1/0/7 *Jan 29 16:07:54.790: %SW_MATM-4-MACFLAP_NOTIF: Host c01a.da84.633b in vlan 130 is flapping between port Gi2/0/9 and port Gi3/0/11 *Jan 29 16:07:54.885: %SW_MATM-4-MACFLAP_NOTIF: Host c01a.da84.633b in vlan 130 is flapping between port Gi2/0/9 and port Gi3/0/11 (KAH-3850-CORE1-1) *Jan 29 16:08:31.415: %SW_MATM-4-MACFLAP_NOTIF: Host e8b2.ac7c.6efe in vlan 130 is flapping between port Gi3/0/18 and port Gi2/0/30 *Jan 29 16:08:31.523: %SW_MATM-4-MACFLAP_NOTIF: Host e8b2.ac7c.6efe in vlan 130 is flapping between port Gi3/0/18 and port Gi2/0/30 (KAH-3850-CORE1-1) *Jan 29 16:08:44.935: %SW_MATM-4-MACFLAP_NOTIF: Host f86f.c1d1.c033 in vlan 130 is flapping between port Gi3/0/6 and port Gi2/0/16 *Jan 29 16:08:45.034: %SW_MATM-4-MACFLAP_NOTIF: Host f86f.c1d1.c033 in vlan 130 is flapping between port Gi3/0/6 and port Gi2/0/16 (KAH-3850-CORE1-1) *Jan 29 16:09:59.866: %SW_MATM-4-MACFLAP_NOTIF: Host 1098.c395.db2b in vlan 130 is flapping between port Gi2/0/30 and port Gi3/0/18 *Jan 29 16:09:59.965: %SW_MATM-4-MACFLAP_NOTIF: Host 1098.c395.db2b in vlan 130 is flapping between port Gi2/0/30 and port Gi3/0/18 (KAH-3850-CORE1-1) *Jan 29 16:11:06.036: %SW_MATM-4-MACFLAP_NOTIF: Host 3408.bc11.4d5b in vlan 130 is flapping between port Gi3/0/22 and port Te1/0/10 *Jan 29 16:11:06.155: %SW_MATM-4-MACFLAP_NOTIF: Host 3408.bc11.4d5b in vlan 130 is flapping between port Gi3/0/22 and port Te1/0/10 (KAH-3850-CORE1-1) *Jan 29 16:11:22.304: %SW_MATM-4-MACFLAP_NOTIF: Host e8b2.ac7c.6efe in vlan 130 is flapping between port Gi2/0/13 and port Gi3/0/20 *Jan 29 16:11:22.395: %SW_MATM-4-MACFLAP_NOTIF: Host e8b2.ac7c.6efe in vlan 130 is flapping between port Gi2/0/13 and port Gi3/0/20 (KAH-3850-CORE1-1) *Jan 29 16:12:17.996: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8b.a01c.fccd in vlan 130 is flapping between port Gi3/0/20 and port Gi3/0/24 *Jan 29 16:12:18.103: %SW_MATM-4-MACFLAP_NOTIF: Host 9c8b.a01c.fccd in vlan 130 is flapping between port Gi3/0/20 and port Gi3/0/24 (KAH-3850-CORE1-1) *Jan 29 16:12:48.595: %SW_MATM-4-MACFLAP_NOTIF: Host b4f7.a1e4.0c74 in vlan 130 is flapping between port Gi3/0/24 and port Gi2/0/25 *Jan 29 16:12:48.688: %SW_MATM-4-MACFLAP_NOTIF: Host b4f7.a1e4.0c74 in vlan 130 is flapping between port Gi3/0/24 and port Gi2/0/25 (KAH-3850-CORE1-1) *Jan 29 16:13:47.866: %SW_MATM-4-MACFLAP_NOTIF: Host a45e.603b.9678 in vlan 130 is flapping between port Te1/0/5 and port Te1/0/7 *Jan 29 16:13:47.966: %SW_MATM-4-MACFLAP_NOTIF: Host a45e.603b.9678 in vlan 130 is flapping between port Te1/0/5 and port Te1/0/7 (KAH-3850-CORE1-1) *Jan 29 16:14:37.365: %SW_MATM-4-MACFLAP_NOTIF: Host c01a.da84.633b in vlan 130 is flapping between port Te1/0/10 and port Gi3/0/17 *Jan 29 16:14:37.463: %SW_MATM-4-MACFLAP_NOTIF: Host c01a.da84.633b in vlan 130 is flapping between port Te1/0/10 and port Gi3/0/17 (KAH-3850-CORE1-1) *Jan 29 16:14:53.017: %SW_MATM-4-MACFLAP_NOTIF: Host f86f.c1c1.7aac in vlan 130 is flapping between port Gi3/0/20 and port Gi3/0/17 *Jan 29 16:14:53.113: %SW_MATM-4-MACFLAP_NOTIF: Host f86f.c1c1.7aac in vlan 130 is flapping between port Gi3/0/20 and port Gi3/0/17 (KAH-3850-CORE1-1) *Jan 29 16:17:28.551: %SW_MATM-4-MACFLAP_NOTIF: Host 4491.605b.ed09 in vlan 130 is flapping between port Gi2/0/13 and port Gi2/0/16 *Jan 29 16:17:28.644: %SW_MATM-4-MACFLAP_NOTIF: Host 4491.605b.ed09 in vlan 130 is flapping between port Gi2/0/13 and port Gi2/0/16 (KAH-3850-CORE1-1) *Jan 29 16:17:41.015: %SW_MATM-4-MACFLAP_NOTIF: Host 003d.e8f7.6672 in vlan 130 is flapping between port Gi3/0/20 and port Gi2/0/13 *Jan 29 16:17:41.107: %SW_MATM-4-MACFLAP_NOTIF: Host 003d.e8f7.6672 in vlan 130 is flapping between port Gi3/0/20 and port Gi2/0/13 (KAH-3850-CORE1-1) *Jan 29 16:19:36.855: %SW_MATM-4-MACFLAP_NOTIF: Host 08f4.ab95.3416 in vlan 120 is flapping between port Gi2/0/13 and port Te1/0/24 *Jan 29 16:19:36.944: %SW_MATM-4-MACFLAP_NOTIF: Host 08f4.ab95.3416 in vlan 120 is flapping between port Gi2/0/13 and port Te1/0/24 (KAH-3850-CORE1-1) *Jan 29 16:20:54.395: %SW_MATM-4-MACFLAP_NOTIF: Host 24e3.1461.b657 in vlan 130 is flapping between port Te1/0/24 and port Gi2/0/13 *Jan 29 16:20:54.487: %SW_MATM-4-MACFLAP_NOTIF: Host 24e3.1461.b657 in vlan 130 is flapping between port Te1/0/24 and port Gi2/0/13 (KAH-3850-CORE1-1) *Jan 29 16:22:43.198: %SW_MATM-4-MACFLAP_NOTIF: Host 9cf4.8e0d.05a0 in vlan 130 is flapping between port Gi3/0/5 and port Gi3/0/16 *Jan 29 16:22:43.299: %SW_MATM-4-MACFLAP_NOTIF: Host 9cf4.8e0d.05a0 in vlan 130 is flapping between port Gi3/0/5 and port Gi3/0/16 (KAH-3850-CORE1-1) *Jan 29 16:23:01.918: %SW_MATM-4-MACFLAP_NOTIF: Host f862.14d7.ed1c in vlan 130 is flapping between port Te1/0/4 and port Te1/0/5 *Jan 29 16:23:42.526: %SW_MATM-4-MACFLAP_NOTIF: Host f86f.c1c1.7aac in vlan 130 is flapping between port Gi3/0/24 and port Gi3/0/20 *Jan 29 16:23:42.620: %SW_MATM-4-MACFLAP_NOTIF: Host f86f.c1c1.7aac in vlan 130 is flapping between port Gi3/0/24 and port Gi3/0/20 (KAH-3850-CORE1-1) *Jan 29 16:25:09.662: %SW_MATM-4-MACFLAP_NOTIF: Host 1098.c395.db2b in vlan 130 is flapping between port Gi2/0/14 and port Gi3/0/18 ... View more

  I have been task with configuring STP for one of our customers and looking for some direction on how to configure the environment. The topology consist of Cisco 4506 devices on the end and Meraki MS425-32 and MS120-24 in the middle. I will be implementing MSTP and from the information I found doing my research,   Meraki   doesn't support MST but is compatible and will see the traffic as one instance. From the information I have found to make the   Meraki  devices the root? Once the traffic passes through the   Meraki   devices the 4506 will re-elect a root bridge for the instance. So, if someone can inform on how to approach the configuration it will be greatly appreciated. My thoughts are below. Also, are there firmware concerns?   <cisco enterprise switch> -- <meraki switch> -- <cisco enterprise switch>   1. Configure the Cisco 4506 for MST only one instance for vlans 2. Configure the Mekari devices for RSTP 3. Make the Mekari devices the root\secondary for the vlans (several) 4. Set spanning-tree priority on one of the Cisco 4506 to elect preferred root bridge for MST instance 5. Include native or vlan 1 in the instance as the Mekari devices uses for processing ? ... View more

Hi, We have a 4500 core switch with multiple trunk interfaces, each trunk interface is terminated to a different switch. Each trunk has the same vlan associations. Looking at some documentation from my understanding to load balance the traffic one end of the trunk should be the root bridge for the even vlans and the secondary root for the odd vlans for that region and instance. My questions is since there are multiple trunks with different devices on each end and the core switch has all the trunk ports, how can this be configured?  - Make the core switch the root bridge for the even vlans and all the other devices on the opposite end of the trunk the secondary root bridge for the even vlans, created a separate instance for each trunk and set the other end of the trunks as root for the odd vlans?  This doesn't seem correct can someone inform on how to configure this?   Thanks ... View more

Hi,   I am currently troubleshooting a high cpu utilization issue on a 4506 switch. From the information I have gathered I believe it might be related to ARP/Spanning tree but not sure. If someone could review the information below and inform what might be the issue, I would greatly appreciated it.  Thanks   Show processes cpu  57 145208054 245284872 591 4.79% 4.92% 4.99% 0 Cat4k Mgmt HiPri 58 30682270394037420626 759 45.03% 32.76% 32.24% 0 Cat4k Mgmt LoPri 116 168042297 179628065 935 3.11% 3.39% 3.40% 0 Spanning Tree Show platfrom Health K2CpuMan Review 30.00 63.34 30 101 100 500 76 90 70 49827:17 Show platform cpu packet statistics L3 Fwd Low 18602603250 6406 7176 6037 6906 Show platform cpu packet buffered Index 0: 71 days 0:39:52:479920 - RxVlan: 1007, RxPort: Gi6/46 Priority: Normal, Tag: No Tag, Event: L3 Forward, Flags: 0x440, Size: 64 Eth: Src 00:50:56:90:3B:78 Dst 68:EF:BD:6E:C5:3F Type/Len 0x0800 Ip: ver:IpVersion4 len:20 tos:0 totLen:41 id:737 fragOffset:0 ttl:120 proto:tcp src: 96.60.119.222 dst: 192.168.33.2 firstFragment lastFragment   Index 224: 71 days 0:26:23:36082 - RxVlan: 1007, RxPort: Gi6/46 Priority: Normal, Tag: No Tag, Event: L3 Forward, Flags: 0x440, Size: 64 Eth: Src 00:50:56:90:3B:78 Dst 68:EF:BD:6E:C5:3F Type/Len 0x0800 Ip: ver:IpVersion4 len:20 tos:0 totLen:40 id:207 fragOffset:0 ttl:120 proto:tcp src: 96.60.119.222 dst: 192.168.33.2 firstFragment lastFragment   Index 221: 71 days 0:26:22:967267 - RxVlan: 1007, RxPort: Gi6/46 Priority: Normal, Tag: No Tag, Event: L3 Forward, Flags: 0x440, Size: 64 Eth: Src 00:50:56:90:3B:78 Dst 68:EF:BD:6E:C5:3F Type/Len 0x0800 Ip: ver:IpVersion4 len:20 tos:0 totLen:41 id:206 fragOffset:0 ttl:120 proto:tcp src: 96.60.119.222 dst: 192.168.33.2 firstFragment lastFragment Index 5: 71 days 0:39:52:547648 - RxVlan: 1007, RxPort: Gi6/46 Priority: Normal, Tag: No Tag, Event: L3 Forward, Flags: 0x440, Size: 64 Eth: Src 00:50:56:90:3B:78 Dst 68:EF:BD:6E:C5:3F Type/Len 0x0800 Ip: ver:IpVersion4 len:20 tos:0 totLen:40 id:738 fragOffset:0 ttl:120 proto:tcp src: 96.60.119.222 dst: 192.168.33.2 firstFragment lastFragment Index 155: 71 days 0:39:52:737669 - RxVlan: 1007, RxPort: Gi6/46 Priority: Normal, Tag: No Tag, Event: L3 Forward, Flags: 0x440, Size: 64 Eth: Src 00:50:56:90:3B:78 Dst 68:EF:BD:6E:C5:3F Type/Len 0x0800 Ip: ver:IpVersion4 len:20 tos:0 totLen:40 id:740 fragOffset:0 ttl:120 proto:tcp src: X.X.X.X dst: X.X.X.X firstFragment lastFragment Index 163: 71 days 0:39:52:852784 - RxVlan: 1007, RxPort: Gi6/46 Priority: Normal, Tag: No Tag, Event: Input Acl, Flags: 0x40, Size: 68 Eth: Src 00:12:80:5A:62:89 Dst 01:00:0C:CC:CC:CD Type/Len 0x0032 Index 166: 71 days 0:39:52:853558 - RxVlan: 1007, RxPort: Gi6/46 Priority: Normal, Tag: No Tag, Event: L3 Forward, Flags: 0x440, Size: 64 Eth: Src 00:50:56:90:3B:78 Dst 68:EF:BD:6E:C5:3F Type/Len 0x0800 Ip: ver:IpVersion4 len:20 tos:0 totLen:41 id:741 fragOffset:0 ttl:120 proto:tcp src: 96.60.119.222 dst: 192.168.33.2 firstFragment lastFragment     Show platform cpu packet statistics Packets Transmitted from CPU per Output Interface Interface Total 5 sec avg 1 min avg 5 min avg 1 hour avg ---------------------- --------------- --------- --------- --------- ---------- Gi2/1 715 37 5 0 0 Gi2/2 696 35 4 0 0 Gi2/4 713 36 4 0 0 Gi3/1 692 35 3 0 0 Gi3/3 691 35 3 0 0 Gi3/4 334 16 1 0 0 Gi5/1 14 0 0 0 0 Gi5/3 692 35 3 0 0 Gi6/2 7 0 0 0 0 Gi6/5 658 33 3 0 0 Gi6/6 1 0 0 0 0 Gi6/8 1 0 0 0 0 Gi6/9 13 0 0 0 0 Gi6/10 120 5 0 0 0 Gi6/11 692 35 3 0 0 Gi6/22 124 5 0 0 0 Gi6/27 120 5 0 0 0 Gi6/28 120 6 0 0 0 Gi6/29 120 5 0 0 0 Gi6/30 120 5 0 0 0 Gi6/31 120 5 0 0 0 Gi6/32 692 35 3 0 0 Gi6/35 6 0 0 0 0 Gi6/36 120 5 0 0 0 Gi6/37 6 0 0 0 0 Gi6/41 146 7 0 0 0 Gi6/43 7 0 0 0 0 Gi6/45 691 35 3 0 0 Gi6/46 50 3 0 0 0 Gi6/47 6 0 0 0 0 Packets Received at CPU per Input Interface Interface Total 5 sec avg 1 min avg 5 min avg 1 hour avg ---------------------- --------------- --------- --------- --------- ---------- Gi2/1 128 5 0 0 0 Gi2/2 413 18 2 0 0 Gi2/4 5 0 0 0 0 Gi3/3 4 0 0 0 0 Gi3/4 466 24 3 0 0 Gi5/1 13 0 0 0 0 Gi5/3 16 0 0 0 0 Gi6/5 25 1 0 0 0 Gi6/6 51 2 0 0 0 Gi6/7 7 0 0 0 0 Gi6/8 76 3 0 0 0 Gi6/10 10 0 0 0 0 Gi6/11 3 0 0 0 0 Gi6/22 104 4 0 0 0 Gi6/28 22 0 0 0 0 Gi6/33 8 0 0 0 0 Gi6/41 19 0 0 0 0 Gi6/43 14 0 0 0 0 Gi6/45 9 0 0 0 0 ... View more