I haven't tried this process but you should be able to at least use the tokens again to put the cluster into non-secure mode and then run the new mixed-mode commands to use the new method.
If you have tokens, I recommend using them since it's easier to recover since you don't need to worry about backing up the certificates. On Thu, Mar 12, 2015 at 11:58 AM, Justin Steinberg <[email protected]> wrote: > on this subject, is it possible to take a mixed mode v8 or v9 (signed by > USB tokens) and upgrade to v10 and then use the new CLI command to update > the CTL and move away from the need for the tokens? > > Is there anything to do other than run the CLI command to update the CTL ? > Do I then no longer need the tokens? > > On Thu, Mar 12, 2015 at 11:22 AM, Jason Burns <[email protected]> > wrote: > >> You can use the same USB tokens for the two systems. >> >> I would recommend this because it makes it a bit easier to move phones >> around between the two systems. >> >> If both systems are under the same domain of control, and same level of >> trust, there is no problem using the tokens again. >> >> If one system has phones that should NEVER register to the other system >> for security reasons - then I would recommend using separate tokens. >> >> -- >> Jason Burns >> >> On Thu, Mar 12, 2015 at 11:09 AM, Reto Gassmann <[email protected]> wrote: >> >>> hello Group >>> >>> We run a cucm 9.1(2) and have the Phones authenticated. To do that we >>> used the two USB Tokens and the CTL Client. >>> >>> Now we set up a new Testserver and want to do some tests with certificat >>> renwal and upgrades to 10.5. can I use the same two USB Tokens I used for >>> the production system or do I have to order two new USB Tokens for the >>> Testserver? >>> >>> Thanks for helping out >>> Regards Reto >>> >>> _______________________________________________ >>> cisco-voip mailing list >>> [email protected] >>> https://puck.nether.net/mailman/listinfo/cisco-voip >>> >>> >> >> _______________________________________________ >> cisco-voip mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-voip >> >> > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
