Yup, make sure you have the latest and greatest for teaming and only use it for Fault Tolerant settings, not load balancing. And they can be a problem setting up.... once they are set, they should be fine though
Alright, I've used it in the past, and had no problems, however with my most recent setup I'm having connectivity issues. From the switch when I try to traceroute to the servers I get the following output.
1 * * * Request timed out.
2 1 ms 1 ms 1 ms 192.168.18.20
But when I try to traceroute to the Unity I don't get that first time out, The teaming software is a bit different on that box. I'm also getting errors on the boxes that Cisco cannot figure out, so it probably has something to do with connectivity.
I've disabled the teaming and I still have the issues, any ideas?
Oh this is for Unity? yeah, be extra careful. Unity 4.0(5) cd's had issues withe NIC driver.... You will need to a firmware upgrade and driver udpate to the NIC card. Try just using one NIC card and see if you are still have issues.
Break the team
Assign it one static IP
check Unity connection.
The team gettings flakey also if you are using Failover. If the fault redudency if flakey... Failover will randomly kick in and go to the secondary server...
No, actually the Unity is the only box working; the callmanager servers are having the issue. I broke the team on the CCM servers, and it had no effect. Could there be a NIC teaming issue with the CallManager?
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...