add the output of 'debug ccsip messages'   regards ... View more

Do you have testes "mtu 1400" without ip in front of mtu?   Sounds like the bug  CSCuz58508.   Symptom: Configuring MTU size for interfaces results in a message to console: % Interface GigabitEthernet1 does not support user settable MTU. Conditions: CSR1000v running Denali-16.3.1 and attempting to configure interface MTU size for interfaces that rely on polled mode drivers. Determining if an interface uses a polled mode driver is done by using the following show command: show platform software vnic-if interface-mapping If the driver name ends with '_pmd' it is a polled mode driver.   There are no workaround. You can try to update the IOS.   If you cannot fix the issue, my suggestion is open a case to TAC.   Regards. ... View more

If the access point is a wireless bridge you don't have problem.   Wireless bridge means that the wireless clients will be on the same layer 2 segment of the ASA so they will have the same IP addresses of the ASA network. If the access point will be NAT, you could have problems. In this case you can check if the access point support 'ip dhcp helper address' features in order to forward dhcp requests to the ASA shcp server.   In my opinion is better have a single DHCP server to avoid problem with duplicate IP, ecc.   Regards. ... View more

Hi   Q.        What Cisco IOS Software feature sets are supported in Cisco Catalyst 2960-X Series Switches? A.       The Cisco Catalyst 2960-X Series come with a common universal image and supports LAN Lite, LAN Base, and IP Lite feature sets, as shown in Table 1. Table 1.         Feature sets supported in the 2960-X Series Platform IP Lite (Layer 3) LAN Base (Layer 2) LAN Lite (Basic Layer 2) 2960-XR Yes No No 2960-X No Yes Yes   Q.        What features does IP Lite bring to the 2960-XR switch models? A.       IP Lite introduced enterprise access Layer 3 features to the 2960-XR switch models. IP Lite is subset of IP Base features. Some of the IP Lite features are: ●    Routing Information Protocol (RIP) v1 ●    Routing Information Protocol (RIP) v2 ●    Open Shortest Path First (OSPF) v2 stub ●    Open Shortest Path First (OSPF) v3 stub ●    Enhanced Interior Gateway Routing Protocol (EIGRP) stub ●    Equal-cost routing ●    Hot Standby Router Protocol (HSRP) ●    Protocol Independent Multicast PIM (Sparse Mode, Dense Mode, Sparse Dense Mode, Source Specific Multicast) stub ●    Virtual Router Redundancy Protocol (VRRP) for IPv4 ●    Private VLAN ●    IPv6 First Hop Security source guard ●    Per-VLAN and per-port policers   Q.        Do I need a software license for the Cisco Catalyst 2960-X Series Switches? A.       No. Cisco Catalyst 2960-X Series Switches use the Universal image, but no license is required. The feature set is bound to the hardware model type and cannot be changed.   For convenience, a single software image is used for all Cisco Catalyst 2960-X and 2960-XR switches, regardless of whether they are IP Lite, LAN Base, or LAN Lite models.   Q.        Can a Cisco Catalyst 2960-X Series Switch feature set license be upgraded? A.       No. The feature set is bound to the hardware model. To get the features and capabilities of IP Lite, you must purchase an IP Lite (2960-XR) switch.     So, 2960 cannot support IP Lite functions, you must use a 2960X with IP Lite image. Regards. ... View more

Hi, the bug toolkit shows that the only know affected version is  8.2(1.15) but "other software versions might be affected as well". No releases are planned to fix this bug and no workaroundd are suggested. The statuts of the bug is terminated so no other action will be done.   My suggestion is contact the TAC. In this way cisco will investigate about your case and, is it's needed, they can re-open the case.   Regards. ... View more

Hi, in the bug toolkit there isn't any indication about fixed released but there is a description about condition and a suggested workaround.   Anyhow TAC can be more helpful. Regards.   Conditions: When a device is configured with a File Policy with the HTTP protocol included. Workaround: new workaround: Disable the file policy Use the uninstaller script to rollback to the previously installed patch release. In case both the FMC and the managed device have been upgraded, the managed device has to be rolled back using the CLI. The uninstaller script will be in the location '/var/sf/updates'. In case only the FMC has been upgraded, the uninstaller for FMC is available on the user interface under "System > Updates". ... View more

Hi, can you check the log of the switch (show logging)? Can you check if the port go in blocking due to spanning tree (show spanning tree summary)?   Regards. ... View more

Hi, in the bugtoolkit I cannot find informations about version 9.6. These are the notes related to this bug:   Symptom: ASA Firewalls and Firepower Threat Defense devices may traceback and reload when the state of the unit in a Failover pair or multi-unit cluster changes. For example, when moving from ACTIVE to STANDBY or STANDBY to ACTIVE, or as it joins/leaves a cluster. The problem also occurs during software upgrade. Conditions: To encounter the problem, the following conditions must be met: 1) Syslogging to an off-box syslog host must be configured, using the UDP logging protocol 2) FTD devices must be running Firepower 6.2.3.5 ASA devices must be running versions: 9.9.2.16 through 9.9.2.22 9.8.3.9 through 9.8.3.10 Versions outside of these ranges are not affected by the problem. 3) A unit must leave and then join the high availability (cluster or failover) and this might happen during a software upgrade The problem occurs in cluster and failover high availability setups, and can be triggered during a high-availability upgrade. For example, during the process of upgrading from 6.2.3.5 to a later version such as 6.2.3.6, after one unit successfully upgrades to 6.2.3.6, another unit still running 6.2.3.5 might encounter the problem as it is upgrading and attempting to re-join the cluster. Workaround: The problem can be mitigated by disabling UDP syslogging prior to upgrading the software version. If the device is crashing in a bootloop: ASA-remove the "logging host" command from startup config. FTD- contact Cisco TAC to apply the workaround If you would like to use logging host, Configure TCP logging instead of UDP logging (and consider the 'logging permit-hostdown' command) If the FTD device is stable following a crash (not continuously crashing) the upgrade will not be running due to the system restart, however could be resumed via CLI using the following command: #sudo install_update.pl --detach --resume /var/sf/updates/ example (for a 2100 series device): #sudo install_update.pl --detach --resume /var/sf/updates/Cisco_FTD_SSP_FP2K_Patch-6.2.3.6-37.sh.REL.tar If there are any issues with the upgrade resume command, or if the device is not stable to run the update, contact TAC.     Known Affected Releases: (4) 101.5(1.55) 101.5(1.62) 9.8(3.9) 9.9(2.21)   Known Fixed Releases: (11) 201.3(11.2) 201.3(1.52) 201.1(15.61) 101.5(1.70) 99.3(0.33) 9.10(0.82) 9.9(2.245) 9.9(2.23) 9.8(3.11) 9.8(2.40) 6.2(3.6) ... View more

Hi, the ATA192.cfg file is the common general file. You can use it to load in the ATA the general common configuration. The macaddress.cfg file will be used to load the specific configuration of a single ATA. E.g. SIP username and password.   Regards. ... View more

And here the ATA 19x provisioning guide.   Regards. ... View more

Ok, try to set the profile rule in the xml file. This is an example:   <Profile_Rule>tftp://192.168.1.1/00bf7718f1ba.cfg</Profile_Rule>   If I correctly remember, you can force the ATA to load the xml profile stored in your TFTP server using this url:   http://ATA192_IP/admin/resync?tftp://192.168.1.1/00bf7718f1ba.cfg   The ATA will load the xml file and then reboot itself.   You can find others info in the attached file. The file is related to linksys device but the provisioning process is similar.   Regards.   ... View more

Hi, you can find an xml file example at this link: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cata/19x/3PCC/english/provguide/at1x_b_ata191-ata192-mpp-prov/at1x_b_ata191-ata192-mpp-prov_appendix_0111.html You can copy the xml and paste it in a text editor. You can save the file as ata192.cfg or mac-address.cfg.   The options related to SIP registration are these:   <!-- Proxy and Registration --> <Proxy_1_ ua="na">192.168.0.24</Proxy_1_> <Outbound_Proxy_1_ ua="na"/> <Use_Outbound_Proxy_1_ ua="na">No</Use_Outbound_Proxy_1_> <Use_OB_Proxy_In_Dialog_1_ ua="na">Yes</Use_OB_Proxy_In_Dialog_1_> <Registrar_Server_1_ ua="na"/> <Register_1_ ua="na">Yes</Register_1_> <Make_Call_Without_Reg_1_ ua="na">No</Make_Call_Without_Reg_1_> <Register_Expires_1_ ua="na">3600</Register_Expires_1_> <Ans_Call_Without_Reg_1_ ua="na">No</Ans_Call_Without_Reg_1_> <Use_DNS_SRV_1_ ua="na">No</Use_DNS_SRV_1_> <DNS_SRV_Auto_Prefix_1_ ua="na">No</DNS_SRV_Auto_Prefix_1_> <Proxy_Fallback_Intvl_1_ ua="na">3600</Proxy_Fallback_Intvl_1_> <Proxy_Redundancy_Method_1_ ua="na">Normal</Proxy_Redundancy_Method_1_> <Mailbox_Subscribe_URL_1_ ua="na"/> <Mailbox_Subscribe_Expires_1_ ua="na">2147483647</Mailbox_Subscribe_Expires_1_> <Auto_Register_When_Failover_1_ ua="na">No</Auto_Register_When_Failover_1_> <!-- Subscriber Information --> <Display_Name_1_ ua="na">1060</Display_Name_1_> <User_ID_1_ ua="na">1060</User_ID_1_> <Password_1_ ua="na"/> <Use_Auth_ID_1_ ua="na">No</Use_Auth_ID_1_> <Auth_ID_1_ ua="na"/> <Resident_Online_Number_1_ ua="na"/> <SIP_URI_1_ ua="na"/> In this example the username and phone number is 1060.   You must chage the value according to your needs.   You can also study the full manual available at this link: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cata/19x/3PCC/english/provguide/at1x_b_ata191-ata192-mpp-prov.pdf   Regards. ... View more