-
Low-touch onboarding of NetScaler instances using Console Advisory Connect
-
-
Minimum and maximum capacity for Flexed and Pooled licensing
-
Scenarios for Flexed or Pooled license expiry and connectivity issues behavior
-
Configure NetScaler Console only as the Flexed or Pooled license server
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!
Scenarios for Flexed or Pooled license expiry and connectivity issues behavior
This document presents different scenarios of license expiry and connectivity issues behavior in NetScaler MPX, NetScaler SDX, and NetScaler VPX/NetScaler BLX/NetScaler CPX.
Components of Flexed licenses
- Software instance (VPX/BLX/CPX, SDX, MPX, VPX FIPS)
- Bandwidth capacity
Scenario: MPX form factor
You are using Flexed or Pooled licensing and the licenses are due to expire soon. The following scenarios explain the behavior when a new license is uploaded on NetScaler Console before and after the term expires, or when a license file is not present.
Before the term expires
If the new license is uploaded before the term expires and the old license is still valid, two different pools of capacity (old and new) are available.
- If NetScaler is up and running, it switches to the new Flexed or Pooled license seamlessly after the old license expires.
- Restart is not required.
- NetScaler does not require a manual capacity reconfiguration.
After the term expires
The MPX instances with expired license have the following behavior:
-
Warm reboot to become unlicensed
-
Traffic processing stops immediately
-
Configurations are lost
Before or after term expiry if license edition of old and new are different
If the license edition of old and new are different, then irrespective of before or after the term expires, you must perform the following:
-
Bandwidth must be manually reconfigured. In NetScaler GUI:
- Navigate to System > Licenses > Manage Licenses.
- Click Release Allocation to release the allocation.
- Click Change Allocation to reallocate the bandwidth and change the bandwidth to premium.
-
Restart NetScaler.
Scenario: SDX form factor
You are using Flexed or Pooled licensing and the licenses are due to expire soon. The following scenarios explain the behavior when a new license is uploaded on NetScaler Console before and after the term expires, or when a license file is not present.
Before the term expires
If the new license is uploaded before the term expires and the old license is still valid, two different pools of capacity (old and new) are available.
- If NetScaler is up and running, it switches to the new Flexed or Pooled license seamlessly after the old license expires.
- Restart is not required.
- NetScaler does not require a manual capacity reconfiguration.
After the term expires
The SDX instances with expired license have the following behavior:
-
License server configuration from SDX is removed
-
VPX license bandwidth is reduced to 1 Mbps
If license edition of old and new are different
Before the term expires
-
Ensure that both old and new license files exist on Console.
-
Bandwidth must be manually reconfigured. In the NetScaler SDX GUI:
- Navigate to System > Licenses > Manage Licenses.
- Click Release Allocation to release the allocation.
- Click Change Allocation to reallocate the bandwidth and change the bandwidth to premium.
-
Change all the edition of VPX to premium to reboot the VPX instances.
-
Click Change Allocation and retain only premium bandwidth. Delete all other bandwidth allocations.
After the term expires
- Delete the VPX instances on SDX.
- Click Change allocation to reallocate the bandwidth for SDX on Console.
- Reprovision the VPX with premium edition on SDX.
Scenario: VPX/BLX/CPX form factor
You are using Flexed or Pooled licensing and the licenses are due to expire soon. The following scenarios explain the behavior when a new license is uploaded on NetScaler Console before and after the term expires, or when a license file is not present.
Before the term expires
If the new license is uploaded before the term expires, and the old license is still valid, two different pools of capacity (old and new) are available.
- If NetScaler is up and running, it switches to the new Flexed or Pooled license seamlessly after the old license expires.
- Restart is not required.
- NetScaler does not require a manual capacity reconfiguration.
After the term expires
The VPX/BLX/CPX instances with expired license have the following behavior:
-
Capacity is reduced to 20 Mbps (for VPX and BLX)
-
Capacity is reduced to 100 Mbps (for CPX)
-
License edition remains the same
-
Instance is not rebooted
-
No configuration loss or change
Before or after term expiry if license edition of old and new are different
If the license edition of old and new are different, then irrespective of before or after the term expires, you must perform the following:
-
Bandwidth must be manually reconfigured. In NetScaler VPX/BLX/CPX GUI:
- Navigate to System > Licenses > Manage Licenses.
- Click Release Allocation to release the allocation.
- Click Change Allocation to reallocate the bandwidth and change the bandwidth to premium.
-
Restart VPX/BLX/CPX instance.
Summary
The following table summarizes the behavior of all NetScaler form factors if a new license is not applied on NetScaler Console:
| Form factor | After the license expires | After NetScaler restarts |
|---|---|---|
| VPX/BLX | Keeps running until restart | VPX/BLX becomes unlicensed |
| CPX | Keeps running until restart | CPX becomes CPX Express |
| MPX | Keeps running until restart | MPX becomes unlicensed |
| SDX | Keeps running until restart | Throughput of all VPX is reduced to 1 Mbps (rendering them unusable) |
Scenarios for connectivity issues behavior
If connectivity breaks between NetScaler and agent, or agent and NetScaler Console service, the behavior is as follows:
-
NetScaler goes into grace for 30 days.
-
During this grace period, licensing functionality continues to work until the thirtieth day.
-
On the thirty-first day,
-
NetScaler VPX/NetScaler CPX/NetScaler BLX and NetScaler MPX undergo a forced reboot and become unlicensed.
-
The throughput on all the VPX on NetScaler SDX is decreased to 1 Mbps.
-
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.