Avinish Pathak1709161001 Posted July 12, 2019 Posted July 12, 2019 we have power down activity at Data center. I have to gracefully shutdown SDX and MPX there. Please help me with the commands on MPX and SDX separately. also suggest, anything special to take care while doing that.
Rhonda Rowland1709152125 Posted July 12, 2019 Posted July 12, 2019 Be sure you save your MPX/vpx netscaler configs first. But the shutdown is nothing special. Some considerations below: For the NetScaler MPX/VPX instances, connect to each management IP (NSIP) and save config first (gui or cli). (if you have admin partitions, you need to verify configurations have been saved per partition as well.) If in HA pairs, plan the order. - Save ns config (on primary NS) - For virtual machines (standalone VPX's) or instances on SDX, you can power off the VMs from the hypervisor console, you don't need to issue a shutdown command from cli (but you can.) - If in an HA pair and both nodes in datacenter, and both are coming down. Power off secondary first, then primary to prevent a failover event. - Make sure you don't have any rules at the the hypervisor level, that would power vms on or keep members of the HA pair enabled in this situation. For MPX systems: - save config first: - To shutdown and require the physical power switch is hit after restoring power: shutdown -p now See here for this and other command: https://support.citrix.com/article/CTX127369 For SDX system: - See this article: https://support.citrix.com/article/CTX219781 - It also tells you how to shutdown a list of vms from the sdx hypervisor cli (aka xenserver); if you aren't doing this per vm separately. - you could also backup the sdx config before continuing with the sdx shutdown: https://docs.citrix.com/en-us/sdx/12-1/configuring-management-service/backup-restore.html
Avinish Pathak1709161001 Posted July 18, 2019 Author Posted July 18, 2019 On 7/13/2019 at 3:18 AM, Rhonda Rowland1709152125 said: Be sure you save your MPX/vpx netscaler configs first. But the shutdown is nothing special. Some considerations below: For the NetScaler MPX/VPX instances, connect to each management IP (NSIP) and save config first (gui or cli). (if you have admin partitions, you need to verify configurations have been saved per partition as well.) If in HA pairs, plan the order. - Save ns config (on primary NS) - For virtual machines (standalone VPX's) or instances on SDX, you can power off the VMs from the hypervisor console, you don't need to issue a shutdown command from cli (but you can.) - If in an HA pair and both nodes in datacenter, and both are coming down. Power off secondary first, then primary to prevent a failover event. - Make sure you don't have any rules at the the hypervisor level, that would power vms on or keep members of the HA pair enabled in this situation. For MPX systems: - save config first: - To shutdown and require the physical power switch is hit after restoring power: shutdown -p now See here for this and other command: https://support.citrix.com/article/CTX127369 For SDX system: - See this article: https://support.citrix.com/article/CTX219781 - It also tells you how to shutdown a list of vms from the sdx hypervisor cli (aka xenserver); if you aren't doing this per vm separately. - you could also backup the sdx config before continuing with the sdx shutdown: https://docs.citrix.com/en-us/sdx/12-1/configuring-management-service/backup-restore.html Thanks Rhonda!!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.