05-28-2018 01:21 PM - edited 03-17-2019 12:54 PM
Hi,
We've configured ILS and GPDR for SIP URIs between two clusters, HQ and Br1, each configured as a Hub. We are using a password for ILS authentication. We are using CA signed certificates and have also exchanged the Tomcat certificates and each cluster has the root CA certificate.
The SIP Route Patterns for the route strings are configured in both directions.
Both clusters show the USN Data Synchronization Status is "up to date" for both clusters and if I make a change then the LAST USN Data received value updates. On one cluster I can see all the learned SIP URIs and can route to them but on the other I can see none. If I look at the ILS trace I can see that the missing URIs are being received but otherwise I can't understand the trace.
I've attached the ILS trace from the cluster receiving the updates but not putting them into the learned URI list.
Any help would be appreciated.
05-29-2018 12:09 PM
FWIW: I looked at your traces, too, and see where the data is received but do not see where the URIs are not being posted to the database. It makes me wonder if there is another trace that would show the incoming data committed.
Does the command utils ils findroutestring show the learned patterns?
05-31-2018 05:37 AM
Thanks Maren,
I'm running 12.0.
There doesn't seem to be a command "utils ils findroutestring". I looked for a show command but couldn't find one.
The only command is "utils ils showpeerinfo", which shows the peer info correctly.
I guess I'll have to call TAC.
Thanks!
05-31-2018 06:28 AM
Oops. Sorry. It looks like they got rid of that one in v10 and I didn't notice.
If TAC shows you how to find the information about committing learned information to the database, please post that answer here. I would LOVE to know how to do that.
Good luck!
Maren
05-31-2018 07:41 AM
Hi there
Thats right. From 10.x later we just got only "utils ils showpeerinfo" command available. But you have couple of options
Hope this Helps
Cheers
Rath!
***Please rate helpful posts***
07-17-2018 03:47 AM
08-27-2018 06:31 AM
Hey,
I just got back to this and found that it's working now.
I'm not sure what we might have done that fixed it. We did clean up the SIP URI assignments but I'm not sure if it was working before we did that or fixed itself afterwards. We also applied a COP file and rebooted.
Thank you for your interest.
08-27-2018 08:19 AM
08-27-2018 10:02 AM
Hi
Good thought. My understanding is that the hubs end up being fully meshed.
Here's some text from:
Activate ILS on the Hub Cluster
You must configure each cluster in your ILS network as either a hub cluster or a spoke cluster. Each ILS network must have at least one hub cluster. You can connect a hub cluster to other hub clusters, or you can configure a hub cluster as the only hub cluster in the network. In addition, you can connect a hub cluster to multiple spoke clusters, or you can configure the hub cluster with no spoke clusters. Perform the following procedure to activate the ILS on the hub cluster in the ILS network.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide