-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Support for increasing NetScaler VPX disk space
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Support for increasing NetScaler VPX disk space
NetScaler VPX supports a default disk space of 20 GB. If you encounter disk size constraints for various reasons, the following options are available to increase VPX disk space:
- Manually increase the primary disk size
- Dynamically increase the primary disk size
- Add a secondary disk
Note:
The ability to increase NetScaler VPX disk space is available for both VPX on-premises and VPX cloud deployments.
Manually increase the primary disk size on NetScaler VPX
Follow these steps to manually increase the VPX primary disk size using a Hypervisor or Cloud platform:
- Shut down the VM.
- Extend the default disk size from 20 GB to a higher value, such as 30 GB or 40 GB. For Azure, extend the default disk size from 32 GB to 64 GB.
- Power on the VM and enter the boot prompt.
- Log into single user mode using the
boot -s
command. - Verify the disk space. You can check the newly allocated disk space using
gpart show
command. - Note the partition name. In the following example, the VM partition is da0.
-
Resize the disk partition using the
gpart resize
command.Example: Let’s resize the da0 MBR partition to include 10 GB free space by running the following command.
gpart resize -i 1 da0
-
Merge the free space to the last partition.
Example:
gpart resize -i 5 da0s1
-
Extend the filesystem to include newly allocated free space using the “growfs” command.
Example:
growfs /dev/da0s1e
- Reboot the VM and verify the increased disk space using the “df -h” command on shell prompt.
Dynamically increase the primary disk size on NetScaler VPX
Starting from NetScaler release 14.1 build 21.x, administrators can dynamically increase the primary disk size on NetScaler VPX from 20 GB up to 1 TB at a time. For each subsequent increase, you can again extend up to 1 TB. Ensure you shut down the VM each time you increase the primary disk size. This allows the system to properly recognize the new disk size, update the partition table, and maintain system stability. To increase the disk space, extend the primary disk size by at least 1 GB in the respective cloud or hypervisor UI.
Note:
You can only increase the size of the disks. Once the new size is allocated, you cannot decrease it later. Therefore, increase the disk size only if it is essential.
Add a secondary disk
Starting from NetScaler release 13.1 build 21.x, you can increase disk space on the NetScaler VPX instance by adding a secondary disk. When you attach the secondary disk, the /var/crash
directory is automatically mounted on this disk. The secondary disk is used for storing core files and logs. Existing directories for core files and log files continue to function as before.
Note:
Take an external backup before downgrading the NetScaler appliance to avoid loss of data.
For information on how to attach a new hard disk drive (HDD) to a NetScaler VPX instance on a cloud, see the following:
-
Note:
To attach a secondary disk on VPX instances deployed on Azure, ensure that the Azure VM sizes have a local temporary disk. For more information, see Azure VM sizes with no local temporary disk.
- AWS documentation
- GCP documentation
Warning:
After you add a new HDD to VPX, some of the scripts that work on files, which are moved to the new HDD might fail under the following conditions:
If you use the “link” shell command to create hard links to the files, which were moved to a new HDD.
Replace all such commands with “ln -s” to use a symbolic link. Also, modify the failing scripts accordingly.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.