topic Re: vISE Azure Deployment Issue in Network Access Control

vISE Azure Deployment Issue

DCoutinho93 — Fri, 09 Jun 2023 12:07:13 GMT

Hello,

We have deployed ISE node in Azure. However, out of the box ISE application is stuck in initializing.

No DNS, NTP or domain is correct for our environment, as it comes with defaults. Every time I try to change domain-name, ISE will restart its services and ISE is broken (access to Azure serial console stops working and I have to redeploy it.)

Is there a way to stop ISE from restarting services when I change NTP, DNS or other configuration?
I tried stopping (application ise stop) but then the services start after I change config.

Best Regards,
Diogo

Re: vISE Azure Deployment Issue

Nancy Saini — Fri, 09 Jun 2023 13:28:15 GMT

It is expected for services to restart on ISE when you change the domain name, as it would change the FQDN of the server and all system certificates are required to be replaced with new FQDN. Hence, a service restart is needed and cannot be skipped.

For NTP, there should not be any service restart on the server.

Re: vISE Azure Deployment Issue

thomas — Tue, 20 Jun 2023 21:47:38 GMT

You should provision the ISE node with NTP and DNS settings when you provision the node using the User data field.

Deploy Cisco Identity Services Engine Natively on Cloud Platforms > Cisco ISE on Azure Cloud Services:

Step 11

In the Management tab, retain the default values for the mandatory fields and click Next: Advanced.

Step 12

In the User data area, check the Enable user data check box.

In the User data field, enter the following information:

hostname=<hostname of Cisco ISE>
primarynameserver=<IPv4 address>
dnsdomain=<example.com>
ntpserver=<IPv4 address or FQDN of the NTP server>
timezone=<timezone>
password=<password>
ersapi=<yes/no>
openapi=<yes/no>
pxGrid=<yes/no>
pxgrid_cloud=<yes/no>