I've inherited a CRS server that had NIC teaming enabled. Cisco TAC (and the installation guide) both maintain and teamed NICs are not supported, especially in cases of desktop-side recording.
So, the NIC team has been disolved, the first NIC has the CRS IP address and the second NIC has been disabled. Everything works fine except that Client for Microsoft Networks can not be installed on the NICs anymore, so backups can not be done. My impression is that the NIC will have to be uninstalled and reinstalled to get this working again, but I am concerened with the ramifications to CRS. What are the gotchas in this situation?
A better approach would be to configure a second network interface card (NIC) on the VoIP Monitor server, and place that NIC in a dedicated VLAN (Layer 2 configuration only). If you have not already installed CRS, then run the CRS installation file and specify the address of the second NIC in the VoIP Monitor address configuration. If CRS is already installed, you will need to reinstall CRS to specify the second NIC as the VoIP Monitor address (this is configurable during the CRS re-installation). This workaround has been successfully tested, and resolves the spanning tree issues. An explanation and network diagram
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...