[cisco-voip] Setting Cluster to Mixed Mode

[Eric Pedersen]

That's a little disturbing.  AFAIK, the password is on the token, not on the ctl plugin.  I will make sure to be *very* careful with anything I do with the tokens.  It would be very bad to have to delete the ctl files on all the phones.

On a related note, can you go from mixed mode to non-secure mode without having to delete the ctl files on the phones?

From: Wes Sisk [mailto:wsisk at cisco.com]
Sent: February 10, 2009 12:47
To: Ryan Ratliff
Cc: Eric Pedersen; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Setting Cluster to Mixed Mode

I think I tried this before and had intermittent success. I want to say there is a password recorded on the tokens.  I ended up with 2 passwords  for 2 clusters using the same token, and then it stopped working. Fortunately I had a backup token for each cluster and was able to use it.  I did not investigate thoroughly to figure out where i zigged when I should have zagged.  It's flagged 'do not repeat' in my notebook.

/Wes

On Tuesday, February 10, 2009 1:37:29 PM, Ryan Ratliff <rratliff at cisco.com><mailto:rratliff at cisco.com> wrote:

I don't see why you can't use the same tokens on more than 1 cluster, but that won't natively allow you to move them between clusters.
To do this you need to make sure you add both cluster's TFTP servers as authorized servers when running the CTL plugin (for both clusters).  That way no matter what CTL file the phones have they can use the TFTP server from the other cluster.


-Ryan

On Feb 10, 2009, at 1:02 PM, Eric Pedersen wrote:


Can I use the same USB tokens on 2 CM clusters (I don't see why I shouldn't be able to).  Then, will I be able to move phones between the 2 cluster?

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: February 10, 2009 07:45
To: Bill Greenwood (US)
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Setting Cluster to Mixed Mode

Yes the USB token needs to be used on the PC where you are running the CTL client, and only when asked for.   There is no way around this.

Also keep in mind that you need (at least) two tokens, and you are in serious trouble if you lose them both.  I'd strongly advise having more and keeping them in separate, safe places.

-Ryan

On Feb 10, 2009, at 9:30 AM, Bill Greenwood (US) wrote:

I am trying to set the security mode to mixed mode on a 6.1 cluster.  The CTLclient is failing to find the security token.  The token is installed in the USB port on the CallManager.  Should the token be installed in the local (where the CTLclient is running) or on the CallManager?  I remember that the token should be installed in the local system, but I am doing this remote and the customer has the token in the CallManager (which is at a unmanned facility).  Is there a way to get the CTLclient to recognize the token in the CallManager or must it be moved.

Thanks,

Bill


________________________________


Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip








________________________________






_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

https://puck.nether.net/mailman/listinfo/cisco-voip



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090210/3910ec16/attachment.html>