Security

I am migrating ClearPass in Azure from 6.10 to 6.11, and I want to keep the same IP Address. I am testing the procedure in a lab stup.

As per documentation, IP address is managed by Azure, so I modified the IP address for mgmt NIC to static and set it to the required IP address (I modified also the IP address for old ClearPass to avoid conflict).

When I start ClearPass after modifying IP address, all service stop and never starts. Any idea if this is common behavior? What is the solution for this?

What is the best approach to upgrade Azure deployment from 6.10 to 6.11 while keeping the same IP address?

If I'm remembering correctly, setting a static IP address within ClearPass, when operating as a VM in Azure, doesn't work as expected and shouldn't be used.

I am migrating ClearPass in Azure from 6.10 to 6.11, and I want to keep the same IP Address. I am testing the procedure in a lab stup.

As per documentation, IP address is managed by Azure, so I modified the IP address for mgmt NIC to static and set it to the required IP address (I modified also the IP address for old ClearPass to avoid conflict).

When I start ClearPass after modifying IP address, all service stop and never starts. Any idea if this is common behavior? What is the solution for this?

What is the best approach to upgrade Azure deployment from 6.10 to 6.11 while keeping the same IP address?

I am setting the static IP address in Azure, not ClearPass. ClearPass server gets its IP address from Azure VNET and Subnet settings

If I'm remembering correctly, setting a static IP address within ClearPass, when operating as a VM in Azure, doesn't work as expected and shouldn't be used.

I am migrating ClearPass in Azure from 6.10 to 6.11, and I want to keep the same IP Address. I am testing the procedure in a lab stup.

As per documentation, IP address is managed by Azure, so I modified the IP address for mgmt NIC to static and set it to the required IP address (I modified also the IP address for old ClearPass to avoid conflict).

When I start ClearPass after modifying IP address, all service stop and never starts. Any idea if this is common behavior? What is the solution for this?

What is the best approach to upgrade Azure deployment from 6.10 to 6.11 while keeping the same IP address?

Good to hear, wasn't entirely clear from your post and some users have made that mistake.

You can open a case with TAC but I'm seeing indications that changing the IP address of a ClearPass VM in Azure just doesn't work.  I've not played with Azure enough to know for certain, but when you're "setting the static IP address in Azure", does that mean setting a specific IP address on the vNIC?  Or are you just creating a DHCP reservation for the VM?

I am setting the static IP address in Azure, not ClearPass. ClearPass server gets its IP address from Azure VNET and Subnet settings

If I'm remembering correctly, setting a static IP address within ClearPass, when operating as a VM in Azure, doesn't work as expected and shouldn't be used.

I am migrating ClearPass in Azure from 6.10 to 6.11, and I want to keep the same IP Address. I am testing the procedure in a lab stup.

As per documentation, IP address is managed by Azure, so I modified the IP address for mgmt NIC to static and set it to the required IP address (I modified also the IP address for old ClearPass to avoid conflict).

When I start ClearPass after modifying IP address, all service stop and never starts. Any idea if this is common behavior? What is the solution for this?

What is the best approach to upgrade Azure deployment from 6.10 to 6.11 while keeping the same IP address?

I set it statically by following the process below. It seems to be working, but when I modify the static IP address in Azure all serveries stop. I tried reloading the VM with no improvement. 

I am wondering if there is any trick or procedure to modify  ClearPass IP address in Azure.

I'll open a ticket with TAC. Thanks 

Create a VM with a static private IP address - Azure portal

Good to hear, wasn't entirely clear from your post and some users have made that mistake.

You can open a case with TAC but I'm seeing indications that changing the IP address of a ClearPass VM in Azure just doesn't work.  I've not played with Azure enough to know for certain, but when you're "setting the static IP address in Azure", does that mean setting a specific IP address on the vNIC?  Or are you just creating a DHCP reservation for the VM?

I am setting the static IP address in Azure, not ClearPass. ClearPass server gets its IP address from Azure VNET and Subnet settings

If I'm remembering correctly, setting a static IP address within ClearPass, when operating as a VM in Azure, doesn't work as expected and shouldn't be used.

I am migrating ClearPass in Azure from 6.10 to 6.11, and I want to keep the same IP Address. I am testing the procedure in a lab stup.

As per documentation, IP address is managed by Azure, so I modified the IP address for mgmt NIC to static and set it to the required IP address (I modified also the IP address for old ClearPass to avoid conflict).

When I start ClearPass after modifying IP address, all service stop and never starts. Any idea if this is common behavior? What is the solution for this?

What is the best approach to upgrade Azure deployment from 6.10 to 6.11 while keeping the same IP address?