Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Cluster-Wide Parameters
This section describes the following features:
|
|
In ClearPass 6.11.0 and later, the maximum single cluster size is 32 servers. This includes the publisher, standby publisher, subscribers, dedicated insight server, and standby insight servers. |
General Parameters
Configure the parameters that apply to the nodes in a cluster by configuring Policy Manager . To configure Cluster-Wide Parameters:
1. Navigate to the > > page.
2. Select the link. The page opens to the page:
Figure 1 Cluster-Wide Parameters > General Page
3. Configure > parameters as described in the following table, then click .
Setting the Cluster Communication Mode
Cluster configuration operations (the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. commands available under the cluster command section) support IPv4 or IPv6 communication depending on the cluster wide parameter called the Cluster Communication Mode.
If set to IPv6, cluster replication, database connections and internal API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. calls specific to the cluster operations listed above will use an IPv6 address, or otherwise use IPv4.
The default Cluster Communication Mode depends on the IP address configured on the node at the time of an upgrade or install. If the node has only an IPv6 address, the default Cluster Communication Mode will be IPv6.
If both IPv4 and IPv6 addresses are configured, or if only an IPv4 address is configured, the default Cluster Communication Mode will be IPv4.
Keep in mind, the following modules are not supported for cluster communication using IPv6:
Insight database communication
Admin UI User Interface. features (Access Tracker, API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. calls etc.)
License usage computation on Publisher
Async-netd Monitor (tracks the sync status of other modules)
Set the Cluster Communication Mode from either the ClearPass UI User Interface. or command line interface (CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions.). To set the Cluster Communication Mode from the UI User Interface., go to Setting Cluster Wide Parameters.
To review the cluster specific commands supported by ClearPass, go to ClearPass Cluster Commands. For information on using the ClearPass command line to set the Cluster Communication mode, go to Cluster Communication Mode.
The Cluster Communication Mode performs 3 pre-checks to ensure cluster operations do not fail if the mode is changed. These pre-checks include:
1. Configuration checks - Ensure the IP address of a given format is configured on the interface.
2. Certificate checks for database - The database certs must have the correct IP address configured in the SAN field. Make sure the SAN field is updated to use the correct IP address format in the pattern DNS Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element.:<ip address>. Multiple IP addresses must be separated by a comma (,) delimiter. For example, DNS Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element.:<ipv6 address>, DNS Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element.:<ipv4 address>.
3. Certificate checks for HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. certs - The HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. certs must have the correct IP address configured in the SAN field. Make sure the SAN field is updated to use the correct IP address format in the pattern IP Address:<ip address>. Multiple IP addresses must be separated by a comma (,) delimiter. For example, DNS Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element.:<ipv6 address>, DNS Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element.:<ipv4 address>.
Cleanup Intervals Parameters
The following figure displays the > dialog:
Figure 2 Cluster-Wide Parameters > Cleanup Intervals Dialog
Specify the > parameters as described in the following table:
|
Parameter |
Action/Description |
|
Cleanup interval for Session log details in the database |
Specify the duration in number of days to keep the following data in the Policy Manager database: Session logs (found on the > > page) Event logs (found on the > page) Machine authentication cache The default value is . |
|
Cleanup interval for information stored on the disk |
Specify the duration in number of days to keep log files that are written to the disk. The default value is . |
|
Cleanup interval for CSRs and private keys |
By default, ClearPass automatically performs a cleanup for Certificate Signing Requests (CSRs) older than 15 days. use this parameter to extend the cleanup interval for old CSRs and associated private keys from 15 days to up to 90 days. Network administrators should extend the cleanup interval for CRS and private keys in cases where the CA Certificate Authority or Certification Authority. Entity in a public key infrastructure system that issues certificates to clients. A certificate signing request received by the CA is converted into a certificate when the CA adds a signature generated with a private key. See digital certificate. takes more than 15 days to create a certificate, as the CSR Certificate Signing Request. In PKI systems, a CSR is a message sent from an applicant to a CA to apply for a digital identity certificate. generated on the system would become invalid with the default 15 day setting, and would be removed automatically from the system. |
|
Old Audit Records cleanup interval |
Specify the cleanup interval in number of days that Policy Manager uses to determine when to start deleting old audit records from the page. The default value is. |
|
Known endpoints cleanup interval |
Specify the duration in number of days that Policy Manager uses to determine when to start deleting known or disabled entries from the Endpoint repository. Known entries are deleted based on the when the endpoint was last seen. For example, if this value is , then known Endpoints that have not been seen within the last 7 days are deleted. The default value is s. This indicates that no cleanup interval is specified. |
|
Unknown endpoints cleanup interval |
Specify the duration in number of days that Policy Manager uses to determine when to start deleting unknown entries from the Endpoint repository. Unknown entries are deleted based on the when the endpoint was last seen. For example, if this value is , then unknown Endpoints that have not been seen within the last 7 days are deleted. The default value is . This indicates that no cleanup interval is specified. |
|
Expired guest accounts cleanup interval |
The cleanup interval for expired guest accounts indicates the number of days after expiry that the cleanup occurs. A value of specifies no expired guest accounts cleanup interval. The default value is. |
|
Profiled Unknown endpoints cleanup interval |
Specify the cleanup interval in number of days that Policy Manager uses to determine when to start deleting profiled unknown entries from the Endpoint repository. Profiled unknown entries are deleted based either the time the unknown Endpoint was last seen or the time it was last profiled, whichever is most recent. The default value is ,indicating that no cleanup interval is specified. |
|
Profiled Known endpoints cleanup option |
Specify whether to enable the option to clean up profiled known endpoints. The default value is . Profiled known entries are deleted based either the time the known Endpoint was last seen or the time it was last profiled, whichever is most recent. |
|
Static IP endpoints cleanup option |
Specify whether to enable the option to clean up static IP endpoints. The default option is . |
|
Close Idle RadSec Tunnel from NAD Network Access Device. NAD is a device that automatically connects the user to the preferred network, for example, an AP or an Ethernet switch. after |
Use this setting to configure a timeout value between 15 and 2880 minutes to close an idle RadSec tunnel once the set value is exceeded. The default setting is 15 minutes. If no server status or RADIUS Remote Authentication Dial-In User Service. An Industry-standard network access protocol for remote authentication. It allows authentication, authorization, and accounting of remote users who want to access network resources. message is received from the RadSec client by the time the configured interval is reached, then the RadSec tunnel is disconnected. |
Notifications Parameters
The following figure displays the > dialog:
Figure 3 Cluster-Wide Parameters > Notifications Dialog
Specify the parameters as described in the following table:
|
Parameter |
Action/Description |
|
System Alert Level |
Specify the alert notifications that are generated for system events logged at this level or higher. : Alerts that provide Information, Warnings, and Error messages are generated. : Alerts that provide Warnings and Error messages are generated. : Alerts that provide Error messages only are generated. The default value is . |
|
Alert Notification Timeout |
Specify the timeout in hours that determines how often alert messages are generated and distributed. If you select , alert generation is disabled. The default value is . |
|
Alert Notification - eMail Address |
Enter a comma-separated list of email addresses to which alert messages are sent. |
|
Alert Notification - SMS Short Message Service. SMS refers to short text messages (up to 140 characters) sent and received through mobile phones. Address |
Enter a comma-separated list of phone numbers to which alert messages are sent. |
Standby Publisher Parameters
The standby publisher is the publisher in the cluster that is configured to come up in the event that the publisher is not reachable. The following figure displays the > dialog:
|
|
During a failover, the standby publisher does not have to wait for all the servers in the cluster to fully resynchronize, and instead is available with complete publisher functionality within moments of the triggering failover event. |
Figure 4 Cluster-Wide Parameters > Standby Publisher Dialog
Specify the following >parameters:
|
Parameter |
Action/Description |
|
Enable Publisher Failover |
To authorize a node in a cluster on the system to act as a publisher if the primary publisher fails, select . The default value is . To avoid false failover triggers, the value should be set to before starting a cluster update. |
|
Designated Standby Publisher |
Select the server in the cluster to act as the standby publisher. The default value is . If the standby publisher is on a different subnet Subnet is the logical division of an IP network. than the publisher, then ensure that a reliable connection between the two subnets Subnet is the logical division of an IP network. is available to avoid unwanted network segmentation and potential data loss from a false failover. |
|
Failover Wait Time |
Specify the time (in minutes) that the standby publisher must wait before it assumes the role of publisher after the primary publisher becomes unreachable. The default failover wait time is . This parameter prevents the standby publisher from taking over when the publisher is temporarily unavailable during a restart. Failover wait times vary based on the size of the data needing to synchronize, as well as the number of subscribers that need to be checked. |
|
|
If a cluster is configured with a standby publisher, add the HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. server certificate of the standby publisher to the Trust list and ensure sure all the servers in the cluster have this certificate in the Trust list. Similarly, before you promote a subscriber to publisher, add the HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. server certificate of the subscriber to the Trust list and ensure sure all the servers in the cluster have this certificate in the Trust list. This step is not required if the HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. server certificates for all the nodes in the cluster are signed by a certificate authority (CA Certificate Authority or Certification Authority. Entity in a public key infrastructure system that issues certificates to clients. A certificate signing request received by the CA is converted into a certificate when the CA adds a signature generated with a private key. See digital certificate.). |
|
|
When a database backup is made with a subscriber configured as the standby publisher, and the backup is restored without using the -s flag, then after the backup is restored the cluster list command could fail with an error message displaying Caught unexpected error while retrieving the Cluster Node List. If this occurs, navigate to the Standby Publisher tab and remove the server from the Designated Standby Publisher field. You can designate it as the standby again once the restoration is complete. If the subscriber is configured as the standby in the backup file, pass the -s flag during the restoration to restore the cluster configuration. |
Common Criteria Mode Parameter
The tab in the page allows you to enable or disable and choose the mode devices within the cluster will communicate. Common Criteria is an international standard for security certification. Use Common Criteria Mode for deployments that require strict compliance to Common Criteria requirements.
Common Criteria Mode has the following restrictions and requirements:
When a user enables Common Criteria mode they must enter the existing cluster password, which is validated against existing Common Criteria password rules. If the existing cluster password meets the requirements, no action is needed for the password and Common Criteria mode can be enabled. If the existing password does not meet the requirements, the user is prompted to change the password. If the new cluster password provided is not strong enough, the requirements display so it can be corrected. The Change Cluster Password screen also includes this validation step when the cluster is in Common Criteria mode. The cluster password requirements for Common Criteria mode include:
At least one uppercase letter
At least one lowercase letter
At least one number
At least one special character { } & ! @ # $ % ^ ? _ = . , + < > - *
A minimum length of 15 characters
The password cannot include a dictionary word
The password cannot contain more than four consecutive repeating characters
Common Criteria Mode cannot be enabled if there are less than three NTP Network Time Protocol. NTP is a protocol for synchronizing the clocks of computers over a network. servers configured (for information on configuring multiple NTP Network Time Protocol. NTP is a protocol for synchronizing the clocks of computers over a network. servers, see the option in Table 1, Changing Date and Time Parameters).
Common Criteria Mode requires that all the Policy Manager servers in the cluster must have FIPS Federal Information Processing Standards. FIPS refers to a set of standards that describe document processing, encryption algorithms, and other information technology standards for use within non-military government agencies, and by government contractors and vendors who work with these agencies. mode enabled (see FIPS Page ).
Server certificates must be updated before you enable Common Criteria Mode (see Certificate Store).
Only Certificate Authority (CA Certificate Authority or Certification Authority. Entity in a public key infrastructure system that issues certificates to clients. A certificate signing request received by the CA is converted into a certificate when the CA adds a signature generated with a private key. See digital certificate.)-issued certificates can be used for Policy Manager server certificates.
No self-signed certificates are allowed as trusted certificates.
All X.509 X.509 is a standard for a public key infrastructure for managing digital certificates and public-key encryption. It is an essential part of the Transport Layer Security protocol used to secure web and email communication. v3 trusted Certificate Authority (CA Certificate Authority or Certification Authority. Entity in a public key infrastructure system that issues certificates to clients. A certificate signing request received by the CA is converted into a certificate when the CA adds a signature generated with a private key. See digital certificate.) certificates must satisfy the basic constraints.
X.509 X.509 is a standard for a public key infrastructure for managing digital certificates and public-key encryption. It is an essential part of the Transport Layer Security protocol used to secure web and email communication. is an important standard for a public key The part of a public-private key pair that is made public. The public key encrypts a message and the message is decrypted with the private key of the recipient. infrastructure to manage digital certificates A digital certificate is an electronic document that uses a digital signature to bind a public key with an identity—information such as the name of a person or an organization, address, and so forth. and public-key encryption. X.509 X.509 is a standard for a public key infrastructure for managing digital certificates and public-key encryption. It is an essential part of the Transport Layer Security protocol used to secure web and email communication. is a key part of the Transport Layer Security protocol used to secure web and email communication.
All HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. communication to external services using X.509 X.509 is a standard for a public key infrastructure for managing digital certificates and public-key encryption. It is an essential part of the Transport Layer Security protocol used to secure web and email communication. v3 certificates must pass the basic constraint checks.
Cipher suites that use RSA Rivest, Shamir, Adleman. RSA is a cryptosystem for public-key encryption, and is widely used for securing sensitive data, particularly when being sent over an insecure network such as the Internet., DSA, or DH keys shorter than 2048 bits or ECC Elliptical Curve Cryptography or Error correcting Code memory. Elliptical Curve Cryptography is a public-key encryption technique that is based on elliptic curve theory used for creating faster, smaller, and more efficient cryptographic keys. Error Correcting Code memory is a type of computer data storage that can detect and correct the most common kinds of internal data corruption. ECC memory is used in most computers where data corruption cannot be tolerated under any circumstances, such as for scientific or financial computing. keys shorter than 224 bits are not supported in Common Criteria Mode.
If a cluster is using CA Certificate Authority or Certification Authority. Entity in a public key infrastructure system that issues certificates to clients. A certificate signing request received by the CA is converted into a certificate when the CA adds a signature generated with a private key. See digital certificate.-signed certificates, the replication service remains in a stopped state until after a cluster communication mode change is completed. This is expected behavior, introduced as a safety measure to keep the cluster secure while the operation completes. Reboot the individual cluster nodes after changing the cluster communication mode using ca-signed certificates.
Figure 5 Cluster-Wide Parameters Page > Common Criteria Mode Parameter
Specify the parameter as described in the following table:
|
Parameter |
Action/Description |
|
Cluster Communication Mode (Supports only the cluster configuration operations) |
Click the drop-down list and select either or as the mode of communication for all cluster operations. If the value of this parameter is set to ipv6, all database and API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. calls will use IPv6 addresses for cluster communication. If the value is set to ipv4, it will use IPv4 for database and API Application Programming Interface. Refers to a set of functions, procedures, protocols, and tools that enable users to build application software. calls instead. The default value of the cluster communication mode will depend on the IP address configured on the appliance during installation or upgrade. If the appliance has only an IPv6 address, the default cluster communication mode will be IPv6. If the appliance has both IPv4 and IPv6 addresses configured, or if only an IPv4 address is configured, then the default cluster communication mode will be IPv4. Whenever the cluster communication mode is changed, it performs the following validations: Configuration checks to verify an IP address in the correct format is configured for the interface. Certificate checks to verify the database certificates have the correct IP address in the SAN field. Certificate checks to verify the HTTPS Hypertext Transfer Protocol Secure. HTTPS is a variant of the HTTP that adds a layer of security on the data in transit through a secure socket layer or transport layer security protocol connection. certificates have the correct IP address in the SAN field Before changing the cluster communication mode, carefully review the displayed warning message stating that resetting the cluster communication mode can cause the cluster to go out of sync by resetting the IP address format of the cluster communication interface. Resetting the certificates on each cluster node along with rebooting ensures the cluster is in sync. |
|
Common Criteria Mode |
The is for specific deployments that require strict compliance to Common Criteria requirements. To enable or disable , select or . The default is . When you set , the following message appears: Setting this value to TRUE enables strict validation of Certificates and changes to modules in order to comply with Common Criteria requirements. When Policy Manager is in Common Criteria (CC) mode, TLS 1.2 is enforced with RadSec, and TLS 1.0 and TLS 1.1 are no longer supported. When Common Criteria Mode is enabled, the text is shown in the release version footer of the WebUI. |
Database Parameters
The following figure displays the > dialog:
Figure 6 Cluster-Wide Parameters > Database Dialog
Configure the > parameters as described in the following table:
|
Parameter |
Action/Description |
|
Auto backup configuration options |
Select any of the following auto-backup configuration options: : Select this to not perform periodic backups. Select before upgrading Policy Manager to avoid the interference between Auto backup and migration process. : Performs a periodic backup of the configuration database that includes licensing information that would be required to restore a server to its original state. This is the default auto backup configuration option. In a cluster deployment, the backup file on the publisher also contains license information for all subscribers. : Performs a backup of the configuration database, certificates and licenses, and also the session log database. : Extensions are included in the backup, in addition to configuration data. : Extensions are included in the backup, in addition to configuration data, session log, and Insight data. Keep in mind, if extensions are excluded from a backup file, and that backup file is restored on a system that already has extensions, that system's existing extensions remain and are not overwritten. It is recommended you set this option to Off or Config before starting an upgrade. This ensures the Auto Backup process does not interfere with migration post upgrade. If required, you can change this setting back to Config|SessionInfo 24 hours after upgrade completion. Evaluation and Subscription A business model where a customer pays a certain amount as subscription price to obtain access to a product or service. licenses which have expired will not be included in the backup. |
|
Database user "appexternal" password |
Enter the password for the username for this connection to the database. |
|
Replication Batch Interval |
Configure the time interval (in seconds) at which the subscribers synchronize with the publisher. The default value is . The allowed range is 1 to 60 seconds. |
|
Store Password Hash for MSCHAP authentication |
To store passwords for admin and local users to Hash and NTLM hash formats (which enables RADIUS Remote Authentication Dial-In User Service. An Industry-standard network access protocol for remote authentication. It allows authentication, authorization, and accounting of remote users who want to access network resources. MSCHAP authentications against admin or local repositories), set this to . If you set this to , RADIUS Remote Authentication Dial-In User Service. An Industry-standard network access protocol for remote authentication. It allows authentication, authorization, and accounting of remote users who want to access network resources. MSCHAP authentications are not possible because the NTLM hash passwords are removed for all the users. When you set this value to , reset all the passwords to reenable RADIUS Remote Authentication Dial-In User Service. An Industry-standard network access protocol for remote authentication. It allows authentication, authorization, and accounting of remote users who want to access network resources. MSCHAP authentication against the user repositories. |
|
Store Local User Passwords using reversible encryption |
To enable cleartext password comparison against local users, set this to . If you set this to , cleartext password comparison against local users is not possible because the reversible passwords for local users are removed. After setting this value to , you must reset all the local user passwords to reenable cleartext password comparison against local users. |
|
|
The time it takes for subscribers to synchronize with the publisher in the event of downtime will depend on the duration of the subscriber's downtime and on when the replication recovery is next run on the subscriber after it is back online. It might take as much as 24 hours for the subscriber to synchronize with the publisher. |
Profiler Parameters
The following figure displays the > dialog:
Figure 7 Cluster-Wide Parameters > Profiler Dialog
|
|
Starting with Policy Manager 6.10.2, the Policy Manager server no longer needs to have Device Insight integration disabled in order to run other types of scans that use the Policy Manager Profiler so users can seamlessly run any type of Profiler scan even while Device Insight's device discovery is active. In Policy Manager 6.10.0 and 6.10.1, when is enabled, the > tab is hidden because Device Insight functionality replaces the Policy Manager functions available through the tab (for more information, see Device Insight Integration Page). |
Configure the > parameters as described in the following table:
TACACS+ Parameters
The following figure displays the > dialog:
Figure 8 Cluster-Wide Parameters > TACACS+ Dialog
Configure the > parameters as described in the following table, then click .