Creating the Azure Custom Storage Account and Virtual Appliance
Before you create your ClearPass virtual appliance (VA) , you must create a custom storage account within the Azure portal. The ClearPass VA will not function correctly using a default storage account.
1. | Log in to the Azure portal. If you do not have an account, you will be prompted to create one before you can log in. |
2. | From the Azure portal home page, select | .
3. | in the | search field, enter . The list of services will filter as you begin to type.
4. | Select | .
5. | Select | . The window appears. Configure the storage account settings as defined in the table below, and then click .
Field |
Description |
---|---|
Subscription |
Select the Azure subscription you will use to manage this storage account. ClearPass is available in the Microsoft Azure marketplace as a virtual appliance with the Bring Your Own License (BYOL) licensing model only. ClearPass is not supported on the Microsoft Azure Cloud Solution Provider (CSP) program or any other mode. |
Resource group |
Select an existing resource group to assign the storage account to that group, or click to create a new resource group. |
Storage account name |
Give a unique name to the storage account. |
Location |
Set the location for the storage account. |
Performance |
Select . |
Account Kind |
Retain the default setting. |
Replication |
Retain the default setting. |
Blob access tier |
Retain the default setting. |
Create the ClearPass Virtual Appliance
The following procedure describes the steps to launch the ClearPass VA in Azure.
1. | Log in to the Azure marketplace (https://azuremarketplace.microsoft.com/en-us) and search for to locate the ClearPass Policy Manager virtual appliance offer. |
2. | Select the image. |
3. | Click | . The page appears in the Azure portal with the tab selected.
|
When creating your virtual appliance, use the ClearPass does not support pre-set configurations. option only. Do not use the option for creating a VA, as |
Basics
On the Table 2.
tab, configure the virtual appliance settings as described inWhen you are done configuring the
settings, click .Disks
On the Table 3.
tab, configure the virtual appliance disk settings as described in
Field |
Description |
---|---|
|
|
OS disk type |
Select an OS disk type. The option is supported. |
Encryption type |
Selected the default option . |
|
|
Create and Attach a New Disk |
This setting is optional, as you do not need to create and attach a new disk at this time. You may choose to attach a disk when you are ready to move your VA from a test environment into production. |
When you are done configuring disk settings, click
.Networking
On the Table 4. Note that these settings allow you to define only one interface. Once the VA is created, you must log in to the Azure portal and create a second interface for the VA.
tab, configure the virtual appliance network interface as described inWhen you are done configuring network interface settings, click
.Management
On the Table 5.
tab, configure the virtual appliance management settings as describedField | Description |
---|---|
|
|
Boot diagnostics |
Select . |
Diagnostics storage account |
Select the customer storage account you created in Creating the Azure Custom Storage Account and Virtual Appliance. The ClearPass VA does not support the default managed storage account, so you must create a custom storage account. |
|
|
System assigned managed identity |
Select . |
Azure Active Directory |
The default ClearPass VA does not support Azure Active Directory. setting cannot be changed as the |
Auto Shutdown
|
|
Enable auto-shutdown |
Select .ClearPass VA will not operate correctly with this setting enabled. Enabling this setting will cause regular ClearPass outages. : A |
When you are done configuring management settings, click
.Advanced
On the Table 6.
tab, configure the advanced virtual appliance settings as described in
Field |
Description |
---|---|
|
|
Extensions |
Do not select any extensions. The available extensions in this menu are Azure extensions, not ClearPass extensions. The ClearPass VA does not support any Azure extensions. |
|
|
Custom data |
This field is optional. Custom data is supported if required by your deployment, but it is not required by the ClearPass VA. |
|
|
Host group |
Do not select a host group. |
Proximity placement group |
Do not select a proximity placement group. |
VM generation |
Select ClearPass VA. . This is the only option supported by the |
When you are done configuring advanced VA settings, click
.Tags
Tags are not required by the ClearPass VA. However, you can use the tab to configure tags for your individual deployment, if desired.
Click
to complete your VA configuration.Review + Create
This tab displays the settings you configured in the previous tabs, the product details and pricing for the selected VA size, and Azure terms and conditions. You may be prompted to enter a contact name, email address and phone number for your VA.
1. | When you have verified your settings, click | . The window appears.
2. | Click | .
|
The Azure VA configuration process requires that you generate these keys, but these keys will not be used by your ClearPass VA, and cannot be used to log in to ClearPass. |
3. | After you generate the SSH key pair, the | dialog appears and indicates the status of each VA resource. When each resource has been successfully created, the message appears.
4. | Click | to open your VA in the Azure portal.
Adding an Additional Interface to the ClearPass Virtual Appliance
1. | Once your ClearPass VA is created, navigate to the Azure portal (https://portal.azure.com) and select your ClearPass VA if it is not already selected. |
2. | Click the | menu link, and select the icon to stop the VA.
3. | Click the | menu link and select . The menu opens.
4. | Define your network interface using the settings described in Table 7. |
Field | Description |
---|---|
|
|
Subscription |
Select the Azure portal subscription that will manage this VA interface. |
Resource group |
Select the resource group for the VA interface. |
|
|
Name |
Enter a unique name for this VA interface. |
Region |
Choose the region in which you want to deploy the ClearPass VA. |
Virtual Network |
Select the virtual network for the interface. |
Subnet |
Select the subnet for your VA interface. |
Private IP address assignment |
Select . |
Network security group |
Select the security group for your VA interface. |
Next, you must add an inbound port rule for TCP and UDP ports to the new interface. For a list of ports commonly used by many ClearPass deployments, see Table 8. For additional information on ports for ClearPass, refer to the Firewall Ports Recommended and Required to be Open topic in the ClearPass Policy Manager 6.11 User Guide.
1. | From the Azure portal, select the ClearPass VA. |
2. | Select the new VA interface. |
3. | Click the | menu link.
4. | Select | Rule.
5. | In the | field, select , then add ports as a comma-separated list in the field.
6. | Select the | option in the field then add UDP ports as a comma-separated list in the field.
7. | Select the | menu link and click the icon to restart the VA.
Port |
Description |
---|---|
|
|
TCP Port 80 |
HTTP (Between cluster members) |
UDP Port 123 |
NTP (subscriber to publisher) |
TCP Port 443 |
HTTPS (Bi-directional) |
TCP Port 4231 |
NetWatch (Post-authentication module and the cluster member with Insight enabled) |
TCP Port 5432 |
PostgreSQL for DB replication (subscriber to publisher) |
|
|
TCP Port 80 |
HTTP (Endpoint --> Policy Manager) |
TCP Port 443 |
HTTPS (Endpoint --> Policy Manager) |
TCP/UDP Port 49 |
TACACS+ (NAD <--> Policy Manager) |
UDP 3799 |
RFC 3576/5176 (CoA) (NAD <--> Policy Manager) |
TCP 25 or 465 |
SMTP Mail |
TCP 22 and 443 |
SSH and HTTPS and multicast between two servers in a high availability configuration |
|
|
TCP/UDP Port 53 |
DNS from a client to domain controller and between domain controllers |
UDP Port 88 |
Kerberos authentication |
TCP/UDP Port 135 |
Operations between domain controllers and between a client and a domain controller |
UDP Port 389 |
LDAP to handle normal queries from client computers to the domain controllers |
TCP/UDP Port 464 |
Kerberos password changes |
TCP Port 3268 and 3269 |
Global catalog from a client to a domain controller. |
|
|
TCP Port 6658 |
OnGuard client to communicate with Policy Manager |
|
|
UDP Port 1812, 1645 |
RADIUS authentication |
UDP Port 1813, 1646 |
RADIUS accounting |
TCP/UDP Port 53 |
DNS |
TCP/UDP Port 389 |
LDAP |
TCP/UDP Port 636 |
LDAP protocol over TLS/SSL |
TCP/UDP Port 3269 |
Microsoft Global Catalog with LDAP/SSLTCP |
TCP port 2083 |
RadSec |
UDP Port 5432 |
ClearPass clustering |