Hostname

Displays the hostname of the node.

Node Type

Displays the node type.

It can be one of the following:

• Cisco ISE (PAN, PSN, Mnt) nodes

Personas

(Only appears if the node type is Cisco ISE) Lists the personas that a Cisco ISE node has assumed.

For example, Administration, Policy Service, Monitoring, or pxGrid.

Role

Indicates the role (primary, secondary, or standalone) that the Administration and Monitoring personas have assumed, if these personas are enabled on this node. The role can be any one or more of the following:

• PRI(A): Refers to the primary PAN

• SEC(A): Refers to the secondary PAN

• PRI(M): Refers to the primary MnT

• SEC(M): Refers to the secondary MnT

Services

(Only appears if the Policy Service persona is enabled) Lists the services that run on this Cisco ISE node. Services can include any one of the following:

• Identity Mapping

• Session

• Profiling

• All

Node Status

Indicates the status of each Cisco ISE node in a deployment for data replication.

• Green (Connected): Indicates that a Cisco ISE node, which is already registered in the deployment is in sync with the primary PAN.

• Red (Disconnected): Indicates that a Cisco ISE node is not reachable, is down or data replication is not happening.

• Orange (In Progress): Indicates that a Cisco ISE node is newly registered with the primary PAN, you have performed a manual sync operation, or the Cisco ISE node is not in sync (out of sync) with the primary PAN.

For more information, click the quick view icon for each Cisco ISE node in the Node Status column.

Check this check box if you want a Cisco ISE node to assume the Administration persona. You can enable the Administration persona only on nodes that are licensed to provide the administrative services.

Role: Displays the role that the Administration persona has assumed in the deployment. The persona could take any one of the following values: Standalone, Primary, or Secondary.

Make Primary: Click this button to make this node your primary Cisco ISE node. You can have only one primary Cisco ISE node in a deployment. The other options on this page will become active only after you make this node primary. You can have only two Administration nodes in a deployment. If the node has a Standalone role, Make Primary button appears next to it. If the node has a Secondary role, Promote to Primary button appears next to it. If the node has a Primary role and there are no other nodes registered with it, Make Standalone button appears next to it. You can click this button to make your primary node a standalone node.

Check this check box if you want a Cisco ISE node to assume the Monitoring persona and function as your log collector. There must be at least one Monitoring node in a distributed deployment. At the time of configuring your primary PAN, you must enable the Monitoring persona. After you register a secondary Monitoring node in your deployment, you can edit the primary PAN and disable the Monitoring persona, if required.

To configure a Cisco ISE node on a VMware platform as your log collector, use the following guidelines to determine the minimum amount of disk space that you need: 180 KB per endpoint in your network, per day 2.5 MB per Cisco ISE node in your network, per day.

You can calculate the maximum disk space that you need based on how many months of data you want to have in your Monitoring node. If there is only one Monitoring node in your deployment, it assumes the standalone role. If you have two Monitoring nodes in your deployment, Cisco ISE displays the name of the other Monitoring node for you to configure the primary-secondary roles. To configure these roles, choose one of the following:

• Primary: For the current node to be the primary Monitoring node.

• Secondary: For the current node to be the secondary Monitoring node.

• None: If you do not want the Monitoring nodes to assume the primary-secondary roles.

If you configure one of your Monitoring nodes as primary or secondary, the other Monitoring node automatically becomes the secondary or primary node, respectively. Both the primary and secondary Monitoring nodes receive Administration and Policy Service logs. If you change the role for one Monitoring node to None, the role of the other Monitoring node also becomes None, thereby cancelling the high availability pair after you designate a node as a Monitoring node. You will find this node listed as a syslog target in the Remote Logging Targets window: Administration > System > Logging > Remote Logging Targets.

• Enable Session Services: Check this check box to enable network access, posture, guest, and client provisioning services. Choose the group to which this Policy Service node belongs from the Include Node in Node Group drop-down list. Note that Certificate Authority (CA) and Enrollment over Secure Transport (EST) services can only run on a Policy Service node that has session services enabled on it.

  For Include Node in Node Group, choose None if you do not want this Policy Service node to be part of any group.

  All the nodes within the same node group should be configured on the network access device (NAD) as RADIUS clients and authorized for CoA, because any one of them can issue a CoA request for the sessions that are established through any node in the node group. If you are not using a load balancer, the nodes in a node group should be the same as, or a subset of the RADIUS servers and clients configured on the NAD. These nodes would also be configured as RADIUS servers.

  While a single NAD can be configured with many Cisco ISE nodes as RADIUS servers and dynamic-authorization clients, it is not necessary for all the nodes to be in the same node group.

  The members of a node group should be connected to each other using high-speed LAN connection such as Gigabit Ethernet. The node group members need not be L2 adjacent, but L2 adjacency is highly recommended to ensure sufficient bandwidth and reachability. See the Create Policy Service Node Group section in See Create a Policy Service Node Group for more details.

• Enable Profiling Service: Check this check box to enable the Profiling service. If you enable the Profiling service, you must click the Profiling Configuration tab and enter the details as required. When you enable or disable any of the services that run on the Policy Service node or make any changes to this node, you will be restarting the application server processes on which these services run. You must expect a delay while these services restart. You can determine when the application server has restarted on a node by using the show application status ise command from the CLI.

• Enable Threat Centric NAC Service: Check this check box to enable the Threat Centric Network Access Control (TC-NAC) feature. This feature allows you to create authorization policies based on the threat and vulnerability attributes received from the threat and vulnerability adapters. Threat severity levels and vulnerability assessment results can be used to dynamically control the access level of an endpoint or a user.

• Enable SXP Service: Check this check box to enable SXP service on the node. You must also specify the interface to be used for SXP service.

  If you have configured NIC bonding or teaming, the bonded interfaces are also listed along with the physical interfaces in the Use Interface drop-down list.

• Enable Device Admin Service: Check this check box to create TACACS policy sets, policy results, and so on to control and audit the configuration of network devices.

• Enable Passive Identity Service: Check this check box to enable the Identity Mapping feature. This feature enables you to monitor users that are authenticated by a omain Controller (DC) and not by Cisco ISE. In networks where Cisco ISE does not actively authenticate users for network access, you can use the Identity Mapping feature to collect user authentication information from the Active Directory (AD) Domain Controller.

NetFlow

Check this check box to enable NetFlow per Cisco ISE node that has assumed the Policy Service persona to receive Netflow packets sent from the routers. Enter the required values for the following options:

• Interface: Choose the interface on the Cisco ISE node.

• Port: Enter the NetFlow listener port number on which NetFlow exports are received from the routers. The default port is 9996.

DHCP

Check this check box to enable DHCP per Cisco ISE node that has assumed the Policy Service persona to listen for DHCP packets from IP helper. Enter the required values for the following options:

• Interface: Choose the interface on the Cisco ISE node.

• Port: Enter the DHCP server UDP port number. The default port is 67.

DHCP SPAN

Check this check box to enable DHCP SPAN per Cisco ISE node that has assumed the Policy Service persona to collect DHCP packets.

• Interface: Choose the interface on the Cisco ISE node.

HTTP

Check this check box to enable HTTP per Cisco ISE node that has assumed the Policy Service persona to receive and parse HTTP packets.

• Interface: Choose the interface on the Cisco ISE node.

RADIUS

Check this check box to enable RADIUS per Cisco ISE node that has assumed the Policy Service persona to collect RADIUS session attributes as well as Cisco Device Protocol (CDP) and Link Layer Discovery Protocol (LLDP) attributes from the IOS Sensor enabled devices.

Network Scan (NMAP)

Check this check box to enable the NMAP probe.

DNS

Check this check box to enable DNS per Cisco ISE node that has assumed the Policy Service persona to perform a DNS lookup for the FQDN. Enter the Timeout period in seconds.

SNMP Query

Check this check box to enable SNMP Query per Cisco ISE node that has assumed the Policy Service persona to poll network devices at specified intervals. Enter values for the following fields: Retries, Timeout, Event Timeout, and an optional Description.

SNMP Trap

• Link Trap Query: Check this check box to receive and interpret linkup and linkdown notifications received through the SNMP Trap.

• MAC Trap Query: Check this check box to receive and interpret MAC notifications received through the SNMP Trap.

• Interface: Choose an interface on the Cisco ISE node.

• Port: Enter the UDP port of the host to use. The default port is 162.

Active Directory

Check this check box to scan the defined Active Directory servers for information about Windows users.

• Days before rescan: Choose the days after which you want the scan to happen again.

pxGrid

Check this check box to allow Cisco ISE to collect (profile) endpoint attributes over pxGrid.

Select Node

(Required) The node for which you want to generate the system certificate.

Common Name (CN)

(Required if you do not specify a SAN) By default, the common name is the Fully Qualified Domain Name of the ISE node for which you are generating the self-signed certificate.

Organizational Unit (OU)

Organizational Unit name. For example, Engineering.

Organization (O)

Organization name. For example, Cisco.

City (L)

(Do not abbreviate) City name. For example, San Jose.

State (ST)

(Do not abbreviate) State name. For example, California.

Country (C)

Country name. You must enter the two-letter ISO country code. For example, US.

Subject Alternative Name (SAN)

An IP address, DNS name, or Uniform Resource Identifier (URI) that is associated with the certificate.

Key Type

Specify the algorithm to be used for creating the public key: RSA or ECDSA.

Key Length

• 512

• 1024

• 2048

• 4096

• 256

• 384

Choose 2048 if you plan to get a public CA-signed certificate or deploy Cisco ISE as a FIPS-compliant policy management system.

Digest to Sign With

Choose one of the following hashing algorithm: SHA-1 or SHA-256.

Certificate Policies

Enter the certificate policy OID or list of OIDs that the certificate should conform to. Use comma or space to separate the OIDs.

Expiration TTL

Specify the number of days after which the certificate will expire.

Friendly Name

Enter a friendly name for the certificate. If you do not specify a name, Cisco ISE automatically creates a name in the format <common name> # <issuer> # <nnnnn> where <nnnnn> is a unique five-digit number.

Allow Wildcard Certificates

Check this check box if you want to generate a self-signed wildcard certificate. A wildcard certificate uses a wildcard notation (an asterisk and period before the domain name) and allows the certificate to be shared across multiple hosts in an organization.

Usage

Choose the service for which this system certificate should be used:

• Admin: Server certificate used to secure communication with the Admin portal and between ISE nodes in a deployment.

• EAP Authentication: Server certificate used for authentications that use the EAP protocol for SSL/TLS tunneling.

• RADIUS DTLS: Server certificate used for RADIUS DTLS authentication.

• pxGrid: Client and server certificate to secure communication between the pxGrid client and server.

• SAML: Server certificate used to secure communication with the SAML Identity Provider (IdP). A certificate designated for SAML use cannot be used for any other service such as Admin, EAP authentication, and so on.

• Portal: Server certificate used to secure communication with all Cisco ISE web portals.

Certificate(s) will be used for

Choose the service for which you are going to use the certificate:

Cisco ISE Identity Certificates

• Multi-Use: Used for multiple services (Admin, EAP-TLS Authentication, pxGrid, and Portal). Multi-use certificates use both client and server key usages. The certificate template on the signing CA is often called a Computer or Machine certificate template. This template has the following properties:

  • Key Usage: Digital Signature (Signing)

  • Extended Key Usage: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1) and TLS Web Client Authentication (1.3.6.1.5.5.7.3.2)

• Admin: Used for server authentication (to secure communication with the Admin portal and between ISE nodes in a deployment). The certificate template on the signing CA is often called a Web Server certificate template. This template has the following properties:

  • Key Usage: Digital Signature (Signing)

  • Extended Key Usage: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1)

• EAP Authentication: Used for server authentication. The certificate template on the signing CA is often called a Computer or Machine certificate template. This template has the following properties:

  • Key Usage: Digital Signature (Signing)

  • Extended Key Usage: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1)

  Note	Digital signature key usage is required for EAP-TLS client certificates.

• RADIUS DTLS: Used for RADIUS DTLS server authentication. This template has the following properties:

  • Key Usage: Digital Signature (Signing)

  • Extended Key Usage: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1)

• Portal: Used for server authentication (to secure communication with all ISE web portals). The certificate template on the signing CA is often called a Computer or Machine certificate template. This template has the following properties:

  • Key Usage: Digital Signature (Signing)

  • Extended Key Usage: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1)

• pxGrid: Used for both client and server authentication (to secure communication between the pxGrid client and server). The certificate template on the signing CA is often called a Computer or Machine certificate template. This template has the following properties:

  • Key Usage: Digital Signature (Signing)

  • Extended Key Usage: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1) and TLS Web Client Authentication (1.3.6.1.5.5.7.3.2)

• SAML: Server certificate used to secure communication with the SAML Identity Provider (IdP). A certificate designated for SAML use cannot be used for any other service such as Admin, EAP authentication, and so on.

  • Key Usage: Digital Signature (Signing)

  • Extended Key Usage: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1)

source=local ; type=fatal ; message="unsupported certificate"

Cisco ISE Certificate Authority Certificates

• ISE Root CA: (Applicable only for the internal CA service ) Used for regenerating the entire internal CA certificate chain including the root CA on the Primary PAN and subordinate CAs on the PSNs.

• ISE Intermediate CA: (Applicable only for the internal CA service when ISE acts as an intermediate CA of an external PKI) Used to generate an intermediate CA certificate on the Primary PAN and subordinate CA certificates on the PSNs. The certificate template on the signing CA is often called a Subordinate Certificate Authority. This template has the following properties:

  • Basic Constraints: Critical, Is a Certificate Authority

  • Key Usage: Certificate Signing, Digital Signature

  • Extended Key Usage: OCSP Signing (1.3.6.1.5.5.7.3.9)

• Renew ISE OCSP Responder Certificates: (Applicable only for the internal CA service) Used to renew the ISE OCSP responder certificate for the entire deployment (and is not a certificate signing request). For security reasons, we recommend that you renew the ISE OCSP responder certificates every six months.

Allow Wildcard Certificates

Check this check box to use a wildcard character (*) in the CN and/or the DNS name in the SAN field of the certificate. If you check this check box, all the nodes in the deployment are selected automatically. You must use the asterisk (*) wildcard character in the left-most label position. If you use wildcard certificates, we recommend that you partition your domain space for greater security. For example, instead of *.example.com, you can partition it as *.amer.example.com. If you do not partition your domain, it might lead to security issues.

Generate CSRs for these Nodes

Check the check boxes next to the nodes for which you want to generate the certificate. To generate a CSR for select nodes in the deployment, you must uncheck the Allow Wildcard Certificates option.

Common Name (CN)

By default, the common name is the FQDN of the ISE node for which you are generating the CSR. $FQDN$ denotes the FQDN of the ISE node. When you generate CSRs for multiple nodes in the deployment, the Common Name field in the CSRs is replaced with the FQDN of the respective ISE nodes.

Organizational Unit (OU)

Organizational Unit name. For example, Engineering.

Organization (O)

Organization name. For example, Cisco.

City (L)

(Do not abbreviate) City name. For example, San Jose.

State (ST)

(Do not abbreviate) State name. For example, California.

Country (C)

Country name. You must enter the two-letter ISO country code. For example, US.

Subject Alternative Name (SAN)

An IP address, DNS name, Uniform Resource Identifier (URI), or Directory Name that is associated with the certificate.

• DNS Name: If you choose the DNS name, enter the fully qualified domain name of the ISE node. If you have enabled the Allow Wildcard Certificates option, specify the wildcard notation (an asterisk and a period before the domain name). For example, *.amer.example.com.

• IP Address: IP address of the ISE node to be associated with the certificate.

• Uniform Resource Identifier: A URI that you want to associate with the certificate.

• Directory Name: A string representation of distinguished name(s) (DNs) defined per RFC 2253. Use a comma (,) to separate the DNs. For “dnQualifier” RDN, escape the comma and use backslash-comma “\,” as separator. For example, CN=AAA,dnQualifier=O=Example\,DC=COM,C=IL

Key Type

Specify the algorithm to be used for creating the public key: RSA or ECDSA.

Key Length

Specify the bit size for the public key.

The following options are available for RSA:

• 512

• 1024

• 2048

• 4096

The following options are available for ECDSA:

• 256

• 384

Choose 2048 or greater if you plan to get a public CA-signed certificate.

Digest to Sign With

Choose one of the following hashing algorithm: SHA-1 or SHA-256.

Certificate Policies

Enter the certificate policy OID or list of OIDs that the certificate should conform to. Use comma or space to separate the OIDs.

Node Name

Name of the Policy Service node (PSN) that issued the certificate.

Certificates Issued

Number of endpoint certificates issued by the PSN node.

Certificates Revoked

Number of revoked endpoint certificates (certificates that were issued by the PSN node).

Certificates Requests

Number of certificate-based authentication requests processed by the PSN node.

Certificates Failed

Number of failed authentication requests processed by the PSN node.

Certificate Check Settings

Check ongoing sessions against automatically retrieved CRL

Check this check box if you want Cisco ISE to check ongoing sessions against CRLs that are automatically downloaded.

CRL/OCSP Periodic Certificate Checks

First check at

Specify the time of the day when the CRL or OCSP check should begin each day. Enter a value between 00:00 and 23:59 hours.

Check every

Specify the time interval in hours that Cisco ISE waits before checking the CRL or OCSP server again.

Select Node

(Required) Choose the Cisco ISE node on which you want to import the system certificate.

Certificate File

(Required) Click Browse to select the certificate file from your local system.

Private Key File

(Required) Click Browse to select the private key file.

Password

(Required) Enter the password to decrypt the private key file.

Friendly Name

Enter a friendly name for the certificate. If you do not specify a name, Cisco ISE automatically creates a name in the format <common name> # <issuer> # <nnnnn> where <nnnnn> is a unique five-digit number.

Allow Wildcard Certificates

Check this check box if you want to import a wildcard certificate. A wildcard certificate uses a wildcard notation (an asterisk and period before the domain name) and allows the certificate to be shared across multiple hosts in an organization.

If you check this check box, Cisco ISE imports this certificate to all the other nodes in the deployment.

Validate Certificate Extensions

Check this check box if you want Cisco ISE to validate the certificate extensions. If you check this check box and the certificate that you are importing contains a basic constraints extension with the CA flag set to true, ensure that the key usage extension is present, and that the keyEncipherment bit or the keyAgreement bit, or both, are also set.

Usage

Choose the service for which this system certificate should be used:

• Admin: Server certificate used to secure communication with the Admin portal and between ISE nodes in a deployment

  Note	Changing the certificate of the admin role certificate on a Primary PAN restarts services on all other nodes.

• EAP Authentication: Server certificate used for authentications that use the EAP protocol for SSL/TLS tunneling

• RADIUS DTLS: Server certificate used for RADIUS DTLS authentication

• pxGrid: Client and server certificate to secure communication between the pxGrid client and server

• ISE Messaging Service: Used by Syslog Over Cisco ISE Messaging feature, which enables MnT WAN survivability for built-in UDP syslog collection targets (LogCollector and LogCollector2).

• SAML: Server certificate used to secure communication with the SAML Identity Provider (IdP). A certificate designated for SAML use cannot be used for any other service such as Admin, EAP authentication, and so on.

• Portal: Server certificate used to secure communication with all Cisco ISE web portals

Friendly Name

Displays the name of the certificate.

Status

Enabled or Disabled. If Disabled, ISE will not use the certificate for establishing trust.

Trusted for

Displays the service for which the certificate is used.

Issued To

Common Name (CN) of the certificate subject.

Issued By

Common Name (CN) of the certificate issuer.

Valid From

The “Not Before” certificate attribute.

Expiration Date

The “Not After” certificate attribute.

Expiration Status

Provides information about the status of the certificate expiration. There are five icons and categories of informational message that appear in this column:

• Green: Expiring in more than 90 days

• Blue: Expiring in 90 days or less

• Yellow: Expiring in 60 days or less

• Orange: Expiring in 30 days or less

• Red: Expired

Certificate Issuer

Friendly Name

Enter a friendly name for the certificate.

Status

Choose Enabled or Disabled. If Disabled, ISE will not use the certificate for establishing trust.

Description

Enter an optional description.

Usage

Trust for authentication within ISE

Check the check box if you want this certificate to verify server certificates (from other ISE nodes or LDAP servers).

Trust for client authentication and Syslog

(Applicable only if you check the Trust for authentication within ISE check box) Check the check box if you want this certificate to be used to:

• Authenticate endpoints that connect to ISE using the EAP protocol

• Trust a Syslog server

Trust for authentication of Cisco Services

Check this check box if you want this certificate to be used to trust external Cisco services such as the feed service.

Certificate Status Validation

ISE supports two ways of checking the revocation status of a client or server certificate that is issued by a particular CA. The first is to validate the certificate using the Online Certificate Status Protocol (OCSP), which makes a request to an OCSP service maintained by the CA. The second is to validate the certificate against a Certificate Revocation List (CRL) which is downloaded from the CA into ISE. Both of these methods can be enabled, in which case OCSP is used first, and only if a status determination cannot be made then the CRL is used.

Validate Against OCSP Service

Check the check box to validate the certificate against OCSP services. You must first create an OCSP Service to be able to check this box.

Reject the request if OCSP returns UNKNOWN status

Check the check box to reject the request if certificate status is not determined by OCSP. If you check this check box, an unknown status value returned by the OCSP service will cause ISE to reject the client or server certificate currently being evaluated.

Reject the request if OCSP Responder is unreachable

Check the check box for ISE to reject the request if the OCSP Responder is not reachable.

Download CRL

Check the check box for the Cisco ISE to download a CRL.

CRL Distribution URL

Enter the URL to download the CRL from a CA. This field will be automatically populated if it is specified in the certificate authority certificate. The URL must begin with “http”, “https”, or “ldap.”

Retrieve CRL

The CRL can be downloaded automatically or periodically. Configure the time interval between downloads.

If download failed, wait

Configure the time interval to wait before Cisco ISE tries to download the CRL again.

Bypass CRL Verification if CRL is not Received

Check this check box, for the client requests to be accepted before the CRL is received. If you uncheck this check box, all client requests that use certificates signed by the selected CA will be rejected until Cisco ISE receives the CRL file.

Ignore that CRL is not yet valid or expired

Check this check box if you want Cisco ISE to ignore the start date and expiration date and continue to use the not yet active or expired CRL and permit or reject the EAP-TLS authentications based on the contents of the CRL.

Uncheck this check box if you want Cisco ISE to check the CRL file for the start date in the Effective Date field and the expiration date in the Next Update field. If the CRL is not yet active or has expired, all authentications that use certificates signed by this CA are rejected.

Certificate File

Click Browse to choose the certificate file from the computer that is running the browser.

Friendly Name

Enter a friendly name for the certificate. If you do not specify a name, Cisco ISE automatically creates a name in the format <common name># <issuer># <nnnnn>, where <nnnnn> is a unique five-digit number.

Trust for authentication within ISE

Check the check box if you want this certificate to be used to verify server certificates (from other ISE nodes or LDAP servers).

Trust for client authentication and Syslog

(Applicable only if you check the Trust for authentication within ISE check box) Check the check box if you want this certificate to be used to:

• Authenticate endpoints that connect to ISE using the EAP protocol

• Trust a Syslog server

Trust for authentication of Cisco Services

Check this check box if you want this certificate to be used to trust external Cisco services such as the feed service.

Validate Certificate Extensions

(Only if you check both the Trust for client authentication and Enable Validation of Certificate Extensions options) Ensure that the “keyUsage” extension is present and the “keyCertSign” bit is set, and that the basic constraints extension is present with the CA flag set to true.

Description

Enter an optional description.

Name

Name of the OCSP Client Profile.

Description

Enter an optional description.

Configure OCSP Responder

Enable Secondary Server

Check this check box to enable a secondary OCSP server for high availability.

Always Access Primary Server First

Use this option to check the primary server before trying to move to the secondary server. Even if the primary was checked earlier and found to be unresponsive, Cisco ISE will try to send a request to the primary server before moving to the secondary server.

Fallback to Primary Server After Interval n Minutes

Use this option when you want Cisco ISE to move to the secondary server and then fall back to the primary server again. In this case, all other requests are skipped, and the secondary server is used for the amount of time that is configured in the text box. The allowed time range is 1 to 999 minutes.

Primary and Secondary Servers

URL

Enter the URL of the primary and/or secondary OCSP server.

Enable Nonce Extension Support

You can configure a nonce to be sent as part of the OCSP request. The Nonce includes a pseudo-random number in the OCSP request. It is verified that the number that is received in the response is the same as the number that is included in the request. This option ensures that old communications cannot be reused in replay attacks.

Validate Response Signature

The OCSP responder signs the response with one of the following certificates:

• The CA certificate

• A certificate different from the CA certificate

  In order for Cisco ISE to validate the response signature, the OCSP responder needs to send the response along with the certificate, otherwise the response verification fails, and the status of the certificate cannot be relied on. According to the RFC, OCSP can sign the response using different certificates. This is true as long as OCSP sends the certificate that signed the response for Cisco ISE to validate it. If OCSP signs the response with a different certificate that is not configured in Cisco ISE, the response verification will fail.

Use OCSP URLs specified in Authority Information Access (AIA)

Click the radio button to use the OCSP URLs specified in the Authority Information Access extension.

Response Cache

Cache Entry Time To Live n Minutes

• To reduce network traffic and load from the OCSP servers on an already-known certificate

• To increase the performance of Cisco ISE by caching already-known certificate statuses

By default, the cache is set to 2 minutes for the internal CA OCSP client profile. If an endpoint authenticates a second time within 2 minutes of the first authentication, the OCSP cache is used and the OCSP responder is not queried. If the endpoint certificate has been revoked within the cache period, the previous OCSP status of Good will be used and the authentication succeeds. Setting the cache to 0 minutes prevents any responses from being cached. This option improves security, but decreases authentication performance.

Clear Cache

Click Clear Cache to clear entries of all the certificate authorities that are connected to the OCSP service.

In a deployment, Clear Cache interacts with all the nodes and performs the operation. This mechanism updates every node in the deployment.

Disable Certificate Authority

Click this button to disable the internal CA service.

Host Name

Host name of the Cisco ISE node that is running the CA service.

Personas

Cisco ISE node personas that are enabled on the node running the CA service. For example, Administration, Policy Service, etc.

Role(s)

The role(s) assumed by the Cisco ISE node running the CA service. For example, Standalone or Primary or Secondary.

CA, EST & OCSP Responder Status

Enabled or disabled

OCSP Responder URL

URL for Cisco ISE node to access the OCSP server.

SCEP URL

URL for the Cisco ISE node to access the SCEP server.

Name

(Required) Enter a name for the certificate template. For example, Internal_CA_Template.

Description

(Optional) Enter a description.

Common Name (CN)

(Display only) Common name is autopopulated with the username.

Organizational Unit (OU)

Organizational Unit name. For example, Engineering.

Organization (O)

Organization name. For example, Cisco.

City (L)

(Do not abbreviate) City name. For example, San Jose.

State (ST)

(Do not abbreviate) State name. For example, California.

Country (C)

Country name. You must enter the two-letter ISO country code. For example, US.

Subject Alternative Name (SAN)

(Display only) MAC address of the endpoint.

Key Type

RSA or ECC

Key Size

(Applicable only if you choose RSA) Specify a key size of 1024 or higher.

Curve Type

(Applicable only if you choose ECC) Specify a curve type (the default is P-384).

SCEP RA Profile

Choose the ISE Internal CA or an external SCEP RA profile that you have created.

Valid Period

Enter the number of days after which the certificate expires.

Extended Key Usage

Client Authentication

Check this check box if you want to use this certificate for client authentication.

Server Authentication

Check this check box if you want to use this certificate for server authentication.

Name

Enter a name for the new syslog target.

Target Type

Select the target type from the drop-down list. The default value is UDP Syslog.

Description

Enter a brief description of the new target.

IP Address

Enter the IP address or hostname of the destination machine that will store the logs. Cisco ISE supports IPv4 and IPv6 formats for logging.

Port

Enter the port number of the destination machine.

Facility Code

Choose the syslog facility code that must be used for logging from the drop-down list. Valid options are Local0 through Local7.

Maximum Length

Enter the maximum length of the remote log target messages. Valid values are from 200 through 1024 bytes.

Buffer Message When Server Down

This check box is displayed when you choose TCP Syslog or Secure Syslog from the Target Type drop-down list. Check this check box to allow Cisco ISE to buffer the syslog messages when a TCP syslog target or secure syslog target is unavailable. Cisco ISE retries sending the messages to the target when the connection to the target resumes. After the connection resumes, messages are sent sequentially, starting with the oldest and proceeding to the newest. Buffered messages are always sent before new messages. If the buffer is full, old messages are discarded.

Buffer Size (MB)

Set the buffer size for each target. By default, it is set to 100 MB. Changing the buffer size clears the buffer and all existing buffered messages for the specific target are lost.

Reconnect Timeout (Sec)

Enter the time (in seconds) to configure how long the TCP and secure syslogs are stored before being discarded, when the server is down.

Select CA Certificate

This drop-down list is displayed when you choose Secure Syslog from the Target Type drop-down list. Choose a client certificate from the drop-down list.

Ignore Server Certificate Validation

This check box is displayed when you choose Secure Syslog from the Target Type drop-down list. Check this check box for Cisco ISE to ignore server certificate authentication and accept any syslog server.

Name

Displays the name of the logging category.

Log Severity Level

For some logging categories, this value is set by default and you cannot edit it. For some logging categories, you can choose one of the following severity levels from a drop-down list:

• FATAL: Emergency level. This level means that you cannot use Cisco ISE and you must immediately take the necessary actions.

• ERROR: This level indicates a critical error condition.

• WARN: This level indicates a normal but significant condition. This is the default level set for many logging categories.

• INFO: This level indicates an informational message.

• DEBUG: This level indicates a diagnostic bug message.

Local Logging

Check this check box to enable logging events for the category on the local node.

Targets

This area allows you to choose the targets for a logging category by transferring the targets between the Available and the Selected areas using the left and right arrow icons. The Available area contains the existing logging targets, both local (predefined) and external (user-defined). The Selected area, which is initially empty, then displays the targets that have been chosen for the category.

Repository

Enter the name of the repository. Alphanumeric characters are allowed and the maximum length is 80 characters.

Protocol

Choose one of the available protocols that you want to use.

Server Name

(Required for TFTP, HTTP, HTTPS, FTP, SFTP, and NFS) Enter the hostname or IP address (IPv4 or IPv6) of the server where you want to create the repository.

Path

Enter the path to your repository. The path must be valid and must exist at the time you create the repository.

This value can start with two forward slashes (//) or a single forward slash (/) denoting the root directory of the server. However, for the FTP protocol, a single forward slash (/) denotes the FTP of the local device home directory and not the root directory.

Enable PKI authentication

(Optional; applicable only for SFTP repository) Check this check box if you want to enable RSA Public Key Authentication in SFTP repository.

User Name

(Required for FTP, SFTP) Enter the username that has write permission to the specified server. Only alphanumeric characters are allowed.

Password

(Required for FTP, SFTP) Enter the password that will be used to access the specified server. Passwords can consist of the following characters: 0 to 9, a to z, A to Z, -, ., |, @, #,$, %, ^, &, *, (, ), +, and =.

Type

Choose one of the following:

• Configuration Data Backup: Includes both application-specific and Cisco ADE operating system configuration data

• Operational Data Backup: Includes monitoring and troubleshooting data

Backup Name

Enter the name of your backup file.

Repository Name

Repository where your backup file should be saved. You cannot enter a repository name here. You can only choose an available repository from the drop-down list. Ensure that you create the repository before you run a backup.

Encryption Key

This key is used to encrypt and decrypt the backup file.

Type

Choose one of the following:

• Configuration Data Backup: Includes both application-specific and Cisco ADE operating system configuration data

• Operational Data Backup: Includes monitoring and troubleshooting data

Name

Enter a name for your backup file. You can enter a descriptive name of your choice. Cisco ISE appends the timestamp to the backup filename and stores it in the repository. You will have unique backup filenames even if you configure a series of backups. On the Scheduled Backup list window, the backup filename will be prepended with “backup_occur” to indicate that the file is an occurrence kron job.

Description

Enter a description for the backup.

Repository Name

Select the repository where your backup file should be saved. You cannot enter a repository name here. You can only choose an available repository from the drop-down list. Ensure that you create the repository before you run a backup.

Encryption Key

Enter a key to encrypt and decrypt the backup file.

Schedule Options

Choose the frequency of your scheduled backup and fill in the other options accordingly.

Minimum Length

Specifies the minimum length of the password (in characters). The default is six characters.

Password must not contain

Admin name or its characters in reverse order: Check this check box to restrict the use of the administrator username or its characters in reverse order.

"cisco" or its characters in reverse order: Check this check box to restrict the use of the word “cisco” or its characters in the reverse order.

This word or its characters in reverse order: Check this check box to restrict the use of any word that you define or its characters in the reverse order.

Repeated characters four or more times consecutively: Check this check box to restrict the use of repeated characters four or more times consecutively.

Dictionary words, their characters in reverse order or their letters replaced with other characters: Check this check box to restrict the use of dictionary words, their characters in reverse order or their letters replaced with other characters.

Substitution of "$" for "s", "@" for "a", "0" for "o", "1" for "l", "!" for "i", "3" for "e" is not permitted. For example, Pa$$w0rd

• Default Dictionary: Choose this option to use the default Linux dictionary in Cisco ISE. The default dictionary contains approximately 480,000 English words.

  By default, this option is selected.

• Custom Dictionary: Choose this option to use your customized dictionary. Click Browse to select the custom dictionary file. The text file must be of newline-delimited words, .dic extension, and size less than 20 MB.

Password must contain at least one character of each of the selected types

Specifies that the administrator password must contain at least one character of the type that you choose from the following choices:

• Lowercase alphabetic characters

• Uppercase alphabetic characters

• Numeric characters

• Non-alphanumeric characters

Password History

Specifies the number of previous passwords from which the new password must be different to prevent the repeated use of the same password.

Also, specifies the number of characters that must be different from the previous password.

Enter the number of days before which you cannot reuse a password.

Password Lifetime

Specifies the following options to force users to change passwords after a specified time period:

• Time (in days) before the administrator account is disabled if the password is not changed. (The allowable range is 0 to 2,147,483,647 days.)

• Reminder (in days) before the administrator account is disabled.

Display Network Device Sensitive Data

Require Admin Password

Check this check box if you want the admin user to enter the login password to view network device sensitive data such as shared secrets and passwords.

Password cached for

The password that is entered by the admin user is cached for this time period. The admin user will not be prompted to enter the password again during this period to view the network device sensitive data. The valid range is from 1 to 60 minutes.

Session Timeout

Session Idle Timeout

Enter the time in minutes that you want Cisco ISE to wait before it logs out the administrator if there is no activity. The default value is 60 minutes. The valid range is from 6 to 100 minutes.

Session Info

Invalidate

Check the check box next to the session ID that you want to terminate and click Invalidate.

Configuration Name

Enter the name of PRA configuration.

Configuration Description

Enter a description for PRA configuration.

Use Reassessment Enforcement?

Check the check box to apply the PRA configurations for the user identity groups.

Enforcement Type

Choose the action to be enforced:

• Continue: The user continues to have the privileged access without any user intervention to remediate the client irrespective of the posture requirement.

• Logoff: If the client is not compliant, the user is forced to logoff from the network. When the client logs in again, the compliance status is unknown.

• Remediate: If the client is not compliant, the agent waits for a specified time for the remediation to happen. Once the client has remediated, the agent sends the PRA report to the policy service node. If the remediation is ignored on the client, then the agent sends a logoff request to the policy service node to force the client to logoff from the network.

  If the posture requirement is set to mandatory, then the RADIUS session will be cleared as a result of the PRA failure action and a new RADIUS session has to start for the client to be postured again.

  If the posture requirement is set to optional, then the agent on the client allows the user to click the continue option from the agent. The user can continue to stay in the current network without any restriction.

Interval

Enter a time interval in minutes to initiate PRA on the clients after the first successful login.

The default value is 240 minutes. Minimum value is 60 minutes and maximum is 1440 minutes.

Grace time

Enter a time interval in minutes to allow the client to complete remediation. The grace time cannot be zero, and should be greater than the PRA interval. It can range between the default minimum interval (5 minutes) and the minimum PRA interval.

The minimum value is 5 minutes and the maximum value is 60 minutes.

Select User Identity Groups

Choose a unique group or a unique combination of groups for your PRA configuration.

PRA configurations

Displays existing PRA configurations and user identity groups associated to PRA configurations.

Configuration Name

Enter the name of the AUP configuration that you want to create.

Configuration Description

Enter the description of the AUP configuration that you want to create.

Show AUP to Agent users (for Windows only)

When selected, the link to network usage terms and conditions for your network is displayed to users upon successful authentication and posture assessment.

Use URL for AUP message

When selected, you must enter the URL to the AUP message in the AUP URL field.

Use file for AUP message

When selected, you must browse to the location and upload a file in a zipped format. The file must contain the index.html at the top level.

The .zip file can include other files and subdirectories in addition to the index.html file. These files can reference each other using HTML tags.

AUP URL

Enter the URL to the AUP, which users must access upon successful authentication and posture assessment.

AUP File

Browse to the file and upload it to the Cisco ISE server. It should be a zipped file and should contain the index.html file at the top level.

Select User Identity Groups

Choose a unique user identity group or a unique combination of user identity groups for your AUP configuration.

Note the following while creating an AUP configuration:

• Posture AUP is not applicable for a guest flow

• No two configurations have any user identity group in common

• If you want to create a AUP configuration with a user identity group “Any”, then delete all other AUP configurations first

• If you create a AUP configuration with a user identity group “Any”, then you cannot create other AUP configurations with a unique user identity group or user identity groups. To create an AUP configuration with a user identity group other than Any, either delete an existing AUP configuration with a user identity group “Any” first, or update an existing AUP configuration with a user identity group “Any” with a unique user identity group or user identity groups.

Acceptable use policy configurations—Configurations list

Lists existing AUP configurations and end user identity groups associated with AUP configurations.

Authority Identity Info Description

Enter a user-friendly string that describes the Cisco ISE node that sends credentials to a client. The client can discover this string in the Protected Access Credentials (PAC) information for type, length, and value (TLV). The default value is Identity Services Engine.

Master Key Generation Period

Specifies the primary key generation period in seconds, minutes, hours, days, or weeks. The value must be a positive integer in the range 1 to 2147040000 seconds. The default is 604800 seconds, which is equivalent to one week.

Revoke all master keys and PACs

Click Revoke to revoke all primary keys and PACs.

Enable PAC-less Session Resume

Check this check box if you want to use EAP-FAST without the PAC files.

PAC-less Session Timeout

Specifies the time in seconds after which the PAC-less session resume times out. The default is 7200 seconds.

Tunnel PAC

Click this radio button to generate a tunnel PAC.

Machine PAC

Click this radio button to generate a machine PAC.

Trustsec PAC

Click this radio button to generate a Trustsec PAC.

Identity

(For the Tunnel and Machine PAC identity field) Specifies the username or machine name that is presented as the “inner username” by the EAP-FAST protocol. If the identity string does not match that username, authentication fails.

This is the hostname as defined on the Adaptive Security Appliance (ASA). The identity string must match the ASA hostname otherwise, ASA cannot import the PAC file that is generated.

If you are generating a Trustsec PAC, the Identity field specifies the Device ID of a Trustsec network device and is provided with an initiator ID by the EAP-FAST protocol. If the Identity string entered here does not match that Device ID, authentication fails.

PAC Time to Live

(For the Tunnel and Machine PAC) Enter a value in seconds that specifies the expiration time for the PAC. The default is 604800 seconds, which is equivalent to one week. This value must be a positive integer between 1 and 157680000 seconds. For the Trustsec PAC, enter a value in days, weeks, months, or years. By default, the value is one year. The minimum value is one day and the maximum is 10 years.

Encryption Key

Enter an encryption key. The length of the key must be between 8 and 256 characters. The key can contain uppercase or lowercase letters, or numbers, or a combination of alphanumeric characters.

Expiration Data

(For Trustsec PAC only) The expiration date is calculated based on the PAC Time to Live.

Enable EAP-TTLS Session Resume

If you check this check box, Cisco ISE will cache the TLS session that is created during phase one of EAP-TTLS authentication, provided the user successfully authenticates in phase two of EAP-TTLS. If a user needs to reconnect and the original EAP-TTLS session has not timed out, Cisco ISE uses the cached TLS session, resulting in faster EAP-TTLS performance and a reduced AAA server load.

EAP-TTLS Session Timeout

Specifies the time in seconds after which the EAP-TTLS session times out. The default value is 7200 seconds.

Suppress Repeated Failed Clients

Suppress Repeated Failed Clients

Check this check box to suppress the clients for which the authentications fail repeatedly for the same reason. These clients are suppressed from the audit logs and the requests from these clients are rejected for the specified time period if Reject RADIUS Requests from Clients with Repeated Failures option is enabled.

Detect Two Failures Within

Enter the time interval in minutes. If a client fails authentication twice for the same reason within this time period, it will be suppressed from the audit logs, and the requests from this client will be rejected if Reject RADIUS Requests from Clients with Repeated Failures option is enabled.

Report Failures Once Every

Enter the time interval in minutes for the failed authentications to be reported. For example, if this value is set as 15 minutes, clients that repeatedly fail authentication will be reported in the audit logs only once every 15 minutes, thereby preventing over-reporting.

Reject RADIUS Requests from Clients with Repeated Failures

Check this check box to automatically reject the RADIUS requests from the clients for which the authentications fail repeatedly. You can enable this option to avoid unnecessary processing by Cisco ISE and to protect against potential denial of service attacks.

Failures Prior to Automatic Rejection

Continue Rejecting Requests for

Enter the time interval (in minutes) for which the requests from clients with repeated failures are to be rejected.

Ignore Repeated Accounting Updates Within

Repeated accounting updates that occur within this period will be ignored.

Suppress Repeated Successful Authentications

Check this check box to prevent repeated reporting of successful authentication requests in last 24 hours that have no change in identity context, network device, and authorization.

Authentications Details

Highlight Steps Longer Than

Enter the time interval in milliseconds. If execution of a single step exceeds the specified threshold, it will be marked with a clock icon in the authentication details page.

Detect High Rate of RADIUS Requests

Detect Steady High Rate of Radius Requests

Check this check box to raise an alarm for high RADIUS request load when the limit specified in the Duration of RADIUS requests and Total number of RADIUS requests fields is exceeded.

Duration of RADIUS Requests

Enter the period of time (in seconds) that will be used to calculate the RADIUS rate. The default is 60 seconds. The valid range is from 20 to 86400 seconds.

Total Number of RADIUS Requests

Enter the request limit that will be used to calculate the RADIUS rate. The default is 72000 requests. The valid range is from 24000 to 103680000 requests.

RADIUS UDP Ports

Authentication Ports

Specify the ports to be used for RADIUS UDP authentication flows. You can specify a maximum of 4 port numbers (separated by a comma). By default, port 1812 and port 1645 are used. The valid range is from 1024 to 65535.

Accounting Ports

Specify the ports to be used for RADIUS UDP accounting flows. You can specify a maximum of 4 port numbers (separated by a comma). By default, port 1813 and port 1646 are used. The valid range is from 1024 to 65535.

RADIUS DTLS

Authentication and Accounting Port

Specify the port to be used for RADIUS DTLS authentication and accounting flows. By default, port 2083 is used. The valid range is from 1024 to 65535.

Idle Timeout

Enter the time (in seconds) that you want Cisco ISE to wait before it closes the TLS session if no packets are received from the network device. Default value is 120 seconds. The valid range is from 60 to 600 seconds.

Enable RADIUS/DTLS Client Identity Verification

Check this check box if you want Cisco ISE to verify the identity of the RADIUS/DTLS clients during the DTLS handshake. Cisco ISE fails the handshake if the client identity is not valid. Identity check is skipped for the default network device, if configured. Identity check is performed in the following sequence:

1. If the client certificate contains the subject alternative name (SAN) attribute:

   • If SAN contains the DNS name, the DNS name specified in the certificate is compared with the DNS name that is configured for the network device in Cisco ISE.

   • If SAN contains the IP address (and does not contain the DNS name), the IP address specified in the certificate is compared with all the device IP addresses configured in Cisco ISE.

2. If the certificate does not contain SAN, subject CN is compared with the DNS name that is configured for the network device in Cisco ISE. Cisco ISE fails the handshake in the case of mismatch.

Allow Multiple SGACLs

Check this check box if you want to allow multiple SGACLs in a cell. If this option is not selected, Cisco ISE will allow only one SGACL per cell.

By default, this option is disabled upon fresh install.

After upgrade, Cisco ISE will scan the Egress cells and if it identifies at least one cell with multiple SGACLs assigned to it, it allows the admin to add multiple SGACLs in a cell. Otherwise, it allows only one SGACL per cell.

Allow Monitoring

Check this check box to enable monitoring for all cells in the matrix. If monitoring is disabled, Monitor All icon is greyed out and the Monitor option is disabled in the Edit Cell dialog.

By default, monitoring is disabled upon fresh install.

Show SGT Numbers

Use this option to display or hide the SGT values (both decimal and hexadecimal) in the matrix cells.

By default, the SGT values are displayed in the cells.

Appearance Settings

The following options are available:

• Custom settings: The default theme (colors with no patterns) is displayed initially. You can set your own colors and patterns.

• Default settings: Predefined list of colors with no patterns (not editable).

• Accessibility settings: Predefined list of colors with patterns (not editable).

Color/Pattern

To make the matrix more readable, you can apply coloring and patterns to the matrix cells based on the cell contents.

The following display types are available:

• Permit IP/Permit IP Log: Configured inside the cell

• Deny IP/Deny IP Log: Configured inside the cell

• SGACLs: For SGACLs configured inside the cell

• Permit IP/Permit IP Log (Inherited): Taken from the default policy (for non-configured cells)

• Deny IP/Deny IP Log (Inherited): Taken from the default policy (for non-configured cells)

• SGACLs (Inherited): Taken from the default policy (for non-configured cells)

SMS Gateway Provider Domain

Enter the provider domain, which is used as the host portion and the guest account's mobile number as the user portion of the email address to send the message to the provider's SMS/MMS gateway.

Provider account address

(Optional)

Enter the account address, which is used as the FROM address (typically the account address) for the email and overrides the Default Email Address global setting in Guest Access > Settings.

SMTP API destination address

(Optional)

Enter the SMTP API Destination Address, if you are using an SMTP SMS API that requires a specific account recipient address, such as Clickatell SMTP API.

This is used as the TO address for the email and the guest account's mobile number is substituted into the message's body template.

SMTP API body template

(Optional)

Enter the SMTP API Body Template, if you are using an SMTP SMS API that requires a specific email body template for sending the SMS, such as Clicketell SMTP API.

The supported dynamic substitutions are $mobilenumber$, $timestamp$ (of format $YYYYMMDDHHHMISSmimi$), and $message$. You can use $timestamp$$mobilenumber$ for SMS gateways that require a unique idenitifier in the URL.

URL

Enter the URL for the API.

This field is not URL encoded. The guest account's mobile number is substituted into the URL. The supported dynamic substitutions are $mobilenumber$ and $message$.

If you are using HTTPS with the HTTP API, include HTTPS in the URL string and upload your provider's trusted certificates into Cisco ISE. Choose Administration > System > Certificates > Trusted Certificates.

Data (Url encoded portion)

Enter the Data (Url encoded portion) for the GET or POST request.

This field is URL encoded. If using the default GET method, the data is appended to the URL specified above.

Use HTTP POST method for data portion

If using the POST method, check this option.

The data specified above is used as the content of the POST request.

HTTP POST data content type

If using the POST method, specify the content type such as "plain/text" or "application/xml".

HTTPS Username

HTTPS Password

HTTPS Host name

HTTPS Port number

Enter this information.

Scope Name

Enter a name by which you can easily remember the purpose of this scope.

Status

Select Enabled or Disabled. The scope can only be used for an ISE node when enabled.

ISE Node

Apply an ISE node to act as the DHCP/DNS server. From the dropdown list, select the ISE node with which to use this scope. The Auth VLAN is defined per ISE node or network interface and no two interfaces or two nodes can share the same VLAN.

Network Interface

The network interfaces available for the ISE node that you selected appear in this dropdown list dynamically based on the ISE node that you selected. Select the interface from which the DHCP/DNS server listens. Multiple VLANs may be connected to one network interface card by configuring a VLAN IP-helper on the NAD.

Domain Name

Enter the domain name for the DHCP server to be used in this scope.

DHCP Address range

Based on your network definitions, select the range of DHCP addresses available to be used for this scope.

Subnet mask

Network ID

Automatically determined by Cisco ISE based on the DHCP attributes you enter.

Exclusion address range

Based on your network definitions, select the range of DHCP addresses that should not be used for this scope.

Default gateway

Enter the IP address of the default gateway.

DHCP lease time

Define the the DHCP lease time.

DHCP options

(Optional) DHCP options are added configuration parameters that a DCHP server send to DHCP clients. DHCP options provide support for devices such as cameras, access points, or phones that require the information indicated in the option value to access the network, or as a method to bootstrap the device before final authorization. When the DHCP server receives the DHCP Request message from the client, the server (typically) responds by sending a DHCP ACK packet to the client. At this time, the server then forwards any configured options within the DHCP ACK packet.

For more details, see the DHCP Options section below this table.

External DNS servers

If you would like users to be allowed access to external domains outside of the Auth VLAN before receiving authentication to access the entire corporate network, enter the IP addresses of the DNS servers to resolve the external DNS names.

External Domains

If you would like users to be allowed to access a specific site before receiving authentication to access the entire corporate network, enter the domain names of those sites in these fields.

Enter the names of all the child domains that users may need access to, apart from the parent domain.