Provisioning issue in TMS 13.1 and VCS X7

[Mattias Widman]

Hi,

anybody out there that have seen this issue?

A client of mine have recently upgraded from TMS 13 > TMS 13.1 and VCS X6 > X7. They had provisioning / Replication running succesfully pre-upgrade and they followed the right procedure (or so they say ) to perform the upgrade (diable replication etc).

After upgrade when they try to enable replication again it fails leaving a failure message stating that there is a difference in versions of the Argon Server. It states that TMS is running v3.4 and VCS running v3.2.

I´m currently looking into it but I thought sending out a question here might provide a quicker answer

//Mattias

[Jens Didriksen]

Don't know if this is what they're getting, but the TMS release notes says:

"Cisco TMS13.1 and 13.1.1 include version 3.4 of the Cisco TMS Agent which is not currently available on the Cisco VCS. This will result in a Trouble Ticket being displayed in Cisco TMS for those VCS systems stating „TMS Agent Software Version Differs from Cluster Master‟. This ticket is accurate, but the condition is acceptable as 3.4 is backwards compatible with version 3.3. This ticket can be safely ignored until a Cisco VCS release is available to update the TMS Agent version running on the Cisco VCS."

[Mattias Widman]

Hi,

found it soon after posting . I will have to ask the client to let me take a closer look but it seems that provisining should work anyway then.

Thanx

[Andrew Vasel]

I would agree that it still should be working. My test environment is TMS 13.1.1 and VCS X7, and provisioning is working for me.

[daleritc]

Agree with everyone here, this should work. TMS Agent application v3.2, 3.3 and 3.4 are all compatible with one another. And btw, these are 'internal' version numbering for the TMS Agent application. TMS 13.1 introduced v3.4 while VCS X7.0 (and soon X7.0.1) has v3.3 installed.

And for everyone's info, between 12.6.x and up to TMS 13.02, the TMS Agent application was v3.2 and this was the same vesion between VCS X5.2 up to X6.1. And before anyone asks, then why are they different now? This is simply because of the different fixes and QA matrixes between the two development teams. However, and as discussed, all these TMS Agent versions are compatible with one another

With that said, and what seems peculiar to me is that they report TMS reports running TMS Agent 3.4 and the VCS reporting TMS Agent 3.2, which means to me that they didn't upgrade the VCS to X7.0 yet since you'd expect the VCS to report TMS Agent 3.3.