This message was deleted.

I would use configuration jobs to re-use existing ns.conf and replace the IP address in it. https://docs.citrix.com/en-us/citrix-application-delivery-management-software/curren[…]unning-saved-configuration-from-one-netscaler-to-another.html

I was talking about migration the ADM itself to a new IP

Ho, sorry... 😞

You can run networkconfig from the CLI to change the IP on the ADM itself

ok. will ADM dann push the changed IP setting to all managed ADC nodes?

No, that is for setting a new IP on the ADM, you could send a job to the ADCs beforehand

mmmpf... a bit trickey. perhaps I will test this before proceeding in my prod environment😅

Sounds like a good idea. And please let us know how it went.

if you have isolated mgmt interfaces and are using PBRs for access, bear in mind to create and apply new PBRs for the new ADM IP 👀

Got it. Thanks for the hint.

i moved from the on prem ADM to the cloud ADM Agent which had a new IP and was a new appliance. Basically i had to re submit the firewall requests for logstream/ipfix/snmp/syslog/22/80/443 between ADM agent and ADC's then i basically removed the old appflow polices/collectors from the ADC instances and then added and discovered the VPX instances and re enabled HDX insights on the adc instances and then removed the ADC instances from the on prem ADM and decommissioned the old on prem adm. I only really use ADM for HDX insights and a few configurations jobs and firmware updates and i use the ssl dashboard and got alerting configured so my ADM config is pretty basic

We decided to install new server Nodes. Removed VPX from old Adm. added to new one. Metrics collector will stay on old ip. But can be updated with re-enabling on new adm. Thanks god we didn’t used stylebooks so far on this ADM. 🙈🙈🙈