Role
|
From the
drop-down list box, choose the ILS role for this cluster from the following
options:
-
Stand Alone Cluster—Stand alone clusters cannot join
an ILS network. This is the default option.
-
Hub
Cluster—Hub clusters act as hubs within the ILS network. Hub
clusters may connect to multiple hub and spoke clusters. Hub clusters exchange
ILS updates with other hub clusters and then communicate that information to
their spoke clusters.
If the
cluster that you are configuring is a hub cluster, and you want to connect this
hub cluster to a remote hub cluster, you can enter a registration server for
the remote hub cluster in the ILS Cluster Registration popup window that
appears after you click
Save.
If you want to connect
this hub cluster to another hub cluster, click the
Register to another hub button and enter the IP
address or fully qualified domain name of the publisher node for the hub
cluster to which you want to connect. This button does not appear if the local
cluster is enabled as a stand alone cluster or as a spoke cluster.
-
Spoke Cluster—Spoke clusters register to a single
hub cluster. Spoke clusters rely on the hub in order to communicate with remote
clusters. If you choose a spoke cluster, you must enter a registration server
in the text box that appears after you click the
Save button
|
Exchange
Global Dial Plan Replication Data with Remote Clusters
|
Check this
check box to enable Global Dial Plan Replication for this cluster. When Global
Dial Plan Replication is enabled, the local cluster advertises its catalog of
local and learned directory URIs, alternate numbers, alternate number patterns,
PSTN failover numbers, and route strings, to remote clusters in the ILS
network. In addition, the local cluster also receives the same types of
replication data from the remote clusters in the ILS network.
Note
|
You must
check this check box if you want to implement intercluster URI dialing.
|
Note
|
Even if
Global Dial Plan Replication is enabled, you can include or exclude an
individual directory URI or alternate number from being replicated. If
theAdvertise
Globally via ILS check box in Directory Number Configuration window
is not checked for an individual directory URI or alternate number, Cisco
Unified Communications Manager does not include that directory URI or alternate
number with the Global Dial Plan Replication data.
|
|
Advertised
Route String
|
In the text box, enter a route string. Route strings can be up to 64 alphanumeric characters and can include dots(.) and dashes(-).
If Global
Dial Plan Replication is enabled, ILS associates this route string to all the
global dial plan replication data that was configured in this cluster and
advertises the route string and global dial plan data to the rest of the ILS
network. Global dial plan data includes all the directory URIs, alternate
numbers, and alternate number patterns that were configured in this cluster.
When a
user in a remote cluster dials a number that matches a directory URI, alternate
number, or alternate number pattern from this cluster,
Cisco Unified Communications Manager matches the
called number to this route string, looks for a SIP route pattern that matches
the route string, and routes the call to the outbound trunk specified by the
SIP route pattern.
|
Synchronize Clusters Every
|
Enter the
delay, in minutes, between when the local cluster checks with remote clusters
for ILS updates. The default value is 10 minutes.
|
ILS Authentication
|
Use TLS
Certificates
|
Click this
radio button to configure ILS to use TLS to encrypt communications between
remote clusters. If you check this radio button, and you are using certificates
that are not signed by a trusted certificate authority, you must exchange
Tomcat certificates between the clusters in your network.
|
Use
Password
|
Click this radio button to
configure ILS to use password based authentication for communications between
remote clusters. If you check this radio button, you must enter a password. You
must configure all clusters in your network with the same password.
|
Confirm
Password
|
If you
checked Use Password, confirm your password here.
|
Registration Server
|
The
Registration Server text box appears in the ILS Cluster Registration popup
window that displays after you change the Role to Spoke Cluster or Hub Cluster
and click
Save.
To enter a registration
server, enter the IP address or fully qualified domain name of the publisher
node in the hub cluster to which you want to connect. You must enter a
registration server in the following circumstances:
-
If you
are configuring a spoke cluster, you must enter a registration server for the
hub cluster to which you want to connect.
-
If you
are configuring a hub cluster, you only have to enter a registration server if
you want to connect this hub cluster to another hub cluster in the ILS network.
Otherwise, you can leave the field blank.
If ILS is
running on both the local and remote clusters, ILS uses the registration server
to form a relationship with the remote cluster. Once ILS forms a connection,
the registration server is no longer used.
|
Activate the Intercluster
Lookup Service on the publisher in this cluster
|
This check box appears in
the ILS Cluster Registration popup window that displays after you change the
Role to Spoke Cluster or Hub Cluster and click
Save. Check this check box if you want to activate
ILS on the publisher node in the cluster.
|
ILS Clusters and Imported
Directory URI Catalogs
|
ILS
Clusters and Imported Directory URI Catalogs
|
This section
displays a snapshot of the current ILS network, including all hub clusters,
spoke clusters, and imported directory URI catalogs. Spoke clusters are
displayed under their associated hub cluster. The cluster that you are
currently logged into is identified as the local cluster
For large
networks, you can use the
Find button to filter the display to just those
clusters that meet specific search criteria.
The table
contains the following columns:
-
Cluster
ID/Name—This column displays the cluster ID for the remote cluster. If the
other cluster is from a non-ILS system that was manually imported into Cisco
Unified CM, the field displays the imported catalog name and the Role column
lists the catalog as a Directory URI Imported Catalog.
-
Last Contact Time—This column
displays the last time the local cluster had direct contact with this cluster.
If more than two replication intervals pass without an update from the other
cluster, a warning icon appears, alerting you that there may be a connection
issue.
Note
|
Spoke clusters only make direct contact with their local hub
cluster. Spoke clusters never contact remote hub clusters, or other spokes.
|
-
Role—This column displays whether the remote cluster is a hub
cluster, spoke cluster, or an imported directory URI catalog. The cluster that
you are currently logged into is identified as the local cluster.
-
Advertised Route String—This column displays the route string
for the remote cluster or imported directory URI catalog.
-
Last
USN Data Received—This column displays the last time the local cluster received
an updated USN data from this cluster or imported catalog.
-
USN
Data Synchronization Status—This column displays the USN replication status of
the cluster or imported directory URI catalog.
-
Action—Click
Disconnect if you want to remove this cluster from
the ILS network.
Note
|
If you
disconnect a hub cluster from the network,
Cisco Unified Communications Manager also disconnects
that hub cluster’s spoke clusters.
|
|