One issue I have run into many times with the VCS 7.x upgrades is that the web interface is not refreshing correctly. I will perform an upgrade, it will all look good and then at the last minute it will fail.
It seems to fail when sending out the restart or reboot command from either the Web interface or the Telnet(ssh) interface.
It is usually corrected by physically powering down the system and powering up the system (hard reboot).
This has fixed what you describe in about 10 upgrades I have performed.
Does your VCS have "Device Provisioning" option Key? And are you runing Provisioning? E.g MOVI etc..
Also did you disable Provisioning before performing the upgrade of the VCS as per the guide?
My thoughts are..
The "Legacy TMS Agent mode" warning is because you are still running TMS agent in legacy mode instead of using TMSPE (the new way of provisioning). Don't have to worry too much about this as you can still run the Legacy TMS Agent mode on x7.1
As for the "Application failed" it is as it says that the "The OpenDS service has stopped unexpectedly and has been restarted". I suspect ist because u manually hard rebooted the VCS. Not that you had too much of a choice there. : )
Am not too sure about "B2BUA misconfiguration". But from the message it just seems to be wanting the cluster name.
Am not too sure about "Directory service database failure" but it just seems to want another restart. I would probably try that.
As for the SIP trunk with MS Lync.. is it using TCP ot TLS? If it is using TLS try changing it to TCP and see if it works. You will need to change it on Lync end as well. If it works with TCP then it could be due to (assuming nothing has changed in the network) the fact that VCS 7.1 uses a newer version of openssl 1.01d. I had a similar issue where the upon upgrading to x7.1 the SIP truink (to VCS Expressway) failed for TLS. But in our case there was some work being done on the FW.
it seems to me you are using TLS and for some reason the cluster name has been removed from the VCS configuration.
so configure the cluster name again and restart the B2BUA service.
this is the reason that your calls to MS Lync is stopped working.
for directory service you might want to restart the provisioning service on the VCS but then it might require to purge the opends data and for that reason i recommend you to open a TAC case.
Application failed & The OpenDS service has stopped unexpectedly and has been restarted is very much related to directory service. this will be removed once the ddirectory service issue get fixed.
for TMS legacy mode warning its just a warning which says you are still reunning the old legacy mode..there is new architecture for provisioning which is provisioning extension and it doesn't use the legacy opends any more.
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...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4