Most items of configuration are applied via the primary peer to all peers in a cluster. However, the following items (marked
with a
on the web interface) must be specified separately on each cluster peer.
Configuration data that applies to all peers should only be modified on the primary peer. Otherwise, at best the changes will
be overwritten from the primary or at worst the cluster replication will fail.
Service setup wizard
Configuration settings made through the service setup wizard (including Select Type, Select Series, service selection, licensing
for those services, and basic network settings) must be configured on each peer in a cluster.
Cluster configuration (System > Clustering)
The list of Peer N addresses (including the peer's own address) that make up the cluster must be specified on each peer and must be identical for all
peers.
The Cluster name, Configuration primary, and Cluster IP version must also be specified on each peer and must be identical for all peers.
If you need to enable cluster address mapping, we recommend forming the cluster on IP addresses first. Then you only need
to add the mappings on one peer.
Ethernet speed (System > Network interfaces > Ethernet)
The Ethernet speed is specific to each peer. Each peer may have slightly different requirements for the connection to their Ethernet switch.
IP configuration (System > Network interfaces > IP)
LAN configuration is specific to each peer.
-
Each peer must have a unique IP address, whether that is an IPv4 address, an IPv6 address, or both.
-
IP gateway configuration is peer-specific. Each peer can use a different gateway.
![](https://www.cisco.com/content/dam/en/us/td/i/templates/note.gif)
Note
|
The IP protocol is applied to all peers, because each peer must support the same protocols.
|
IP static routes (System > Network interfaces > Static routes)
Any static routes you add are peer-specific and you may create different routes on different peers if required. If you want
all peers in the cluster to be able to use the same static route, you must create the route on each peer.
System name (System > Administration)
The System name must be different for each peer in the cluster.
DNS servers and DNS host name (System > DNS)
DNS servers are specific to each peer. Each peer can use a different set of DNS servers.
The System host name and Domain name are specific to each peer.
NTP servers and time zone (System > Time)
The NTP servers are specific to each peer. Each peer may use one or more different NTP servers.
The Time zone is specific to each peer. Each peer may have a different local time.
SNMP (System > SNMP)
SNMP settings are specific to each peer. They can be different for each peer.
Logging (Maintenance > Logging)
The Event Log and Configuration Log on each peer only report activity for that particular Expressway. The Log level and the list of Remote syslog servers are specific to each peer. We recommend that you set up a remote syslog server to which the logs of all peers can be sent.
This allows you to have a global view of activity across all peers in the cluster.
Security certificates (Maintenance > Security)
The trusted CA certificate, server certificate and certificate revocation lists (CRLs) used by the Expressway must be uploaded
individually per peer.
Administration access (System > Administration)
The following system administration access settings are specific to each peer:
-
Serial port / console
-
SSH service
-
Web interface (over HTTPS)
-
Redirect HTTP requests to HTTPS
-
Automated protection service
Option keys (Maintenance > Option keys)
This section only applies to systems that use PAK-based licensing (option keys do not apply if your system uses Smart Licensing).
Option keys can control licensing or specific features. They are gradually being phased out for Expressway and their use is
diminishing.
Option keys that control licenses are pooled for use by the whole cluster.
Option keys that control features (such as advanced account security or Microsoft Interoperability) are specific to the peer where they are applied. Each peer
must have an identical set of feature option keys installed, which means that if you use option keys for features you must
purchase a key for each peer in the cluster.
License option keys can be applied to one or more peers in the cluster, and the sum of the installed licenses is available
across the cluster. This license pooling behavior includes the following option keys:
![](https://www.cisco.com/content/dam/en/us/td/i/templates/note.gif)
Note
|
In some cases a peer will raise an alarm that it has no key to enable licenses the peer needs, even though there are licenses
available in the cluster. You can acknowledge and ignore this category of alarm, unless the only peer that has the required
licenses is out of service.
|
Active Directory Service (Configuration > Authentication > Devices > Active Directory Service)
When configuring the connection to an Active Directory Service for device authentication, the NetBIOS machine name (override), and domain administrator Username and Password are specific to each peer.
Conference Factory template (Applications > Conference Factory)
The template used by the Conference Factory application to route calls to a conferencing server must be unique for each peer
in the cluster.