Creating a uniquely named user account marked as home cluster on each cluster would appear to be the simplest. This assumes you have ILS setup between all clusters and you don’t have a large number of clusters that would chew through licensing.
> On Apr 28, 2021, at 11:03, Nick Barnett <nick@barnett.email> wrote: > > > Thanks, let me try and clarify a bit. > > > > We have a support team that needs to log their Jabber device into multiple > clusters. Using the "home cluster" setting is too cumbersome and requires > CUCM access. Our testers do not have CUCM access, but they can modify their > own local config files. > > > > Ultimately, I'm looking for a bootstrap hack, or some other way, to MANUALLY > and / or STATICALLY define which cluster the Jabber client registers with. > > > > This is purely for our support group with CUCM access and our testing team > without CUCM access. No real end users need to use this feature... but > security is taking away our CIPC and I need to have another way for them to > jump between prod clusters... > > > > Additionally, I personally have to jump between prod and non-prod, so i want > this fix for me as well. > > > > Ideally, there is something local that a tech can do to their jabber config > file, bootstrap, or registry that will make their jabber register to a > specific cluster instead of using UPN discovery. Granted, some of the > installation switches seem to fundamentally change how jabber is installed > (imagine that!)... so another requirement would be NOT HAVING TO uninstall > and reinstall with different switches. (If in the end, the support team MUST > be configured to never use UPN, that's fine, i just want to know the best > way). > > > > Does that make it any clearer? I'm just looking for an easy way to hop > between clusters without discovery to replace CIPC. > > > > Thanks! > > >> On Wed, Apr 28, 2021, at 9:26 AM, Lelio Fulgenzi wrote: >> I may not understand exactly what you’re trying to do, but, I think that >> will come out during discussion. >> >> >> >> I have a production cluster and a development cluster. >> >> >> >> To switch between the clusters (and to switch users) I have had to do two >> things: >> >> >> >> Create a new service discovery domain with the appropriate servers listed >> (including development expressway cluster) >> Ensure I use the UDS disabled switch when installing Jabber (this allows for >> different userIDs to be used) >> >> >> I know there are a few parameters out there that allow you to push the >> domain out, but I’m not 100% sure how that works to be honest. Especially >> because it sounded like they were meant to be done at install time. And >> still required a domain to be set. >> >> >> >> Let the games begin! >> >> >> >> >> >> >> >> >> >> From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Nick >> Barnett >> Sent: Wednesday, April 28, 2021 10:16 AM >> To: cisco-voip <cisco-voip@puck.nether.net> >> Subject: [cisco-voip] moving jabber client between clusters for support? >> >> >> CAUTION: This email originated from outside of the University of Guelph. Do >> not click links or open attachments unless you recognize the sender and know >> the content is safe. If in doubt, forward suspicious emails to >> ith...@uoguelph.ca >> >> >> >> Up until now, I've just been using CIPC as it does everything I needed it to >> do... for the most part. Starting this year, I have to jump through way too >> many hoops to keep using CIPC as it is EOL and our security team doesn't >> like that. >> >> >> >> I'm trying to figure out how to configure my Jabber client to register to a >> specific non-prod cluster, but I'm not having much luck. >> >> >> >> Our prod has 2 clusters with ILS. the internal SRV record for discovery >> contains all nodes for both clusters. This works just fine in production and >> relies on the HOME CLUSTER checkbox for the user to be logged into the >> correct cluster. >> >> >> >> My problem comes because I work on non-prod systems as well as prod. The >> only way I've been able to figure out how to get my jabber to jump to >> non-prod system is to create a NEW srv record that only contains the nodes >> of the cluster I want to work with and then change the entry in the >> bootstrap file. >> >> >> >> Is there some way to override discovery and hard code a TFTP or subscriber >> so that Jabber goes to the intended cluster? Or, maybe there's a way to do >> this without a custom SRV record for each non-prod cluster using registry >> like we could in Cucilync? Some other trick? I'm hopeful there is some >> combination of bootstrap settings that I need to figure out, but all of >> those fields can be a nightmare to get correct without unintentionally >> breaking something else. >> >> >> >> Thanks, >> >> Nick >> >> >> > > > Thanks, > Nick > > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
