Application Delivery Management

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.

Types of Flexed licenses

  • Software instance (VPX/BLX/CPX, SDX, MPX, VPX FIPS)
  • Bandwidth capacity

Scenario: MPX form factor

You are using Flexed/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/Pooled license seamlessly after the old license expires.
  • Restart is not required.
  • NetScaler does not require a manual capacity reconfiguration.

After the term expires

NetScaler instance stops its normal operations after the license expiry, including configuration loss and complete shutdown of traffic processing.

Scenario: SDX form factor

You are using Flexed/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/Pooled license seamlessly after the old license expires.
  • Restart is not required.
  • NetScaler does not require a manual capacity reconfiguration.

After the term expires

NetScaler instance stops its normal operations after the license expiry, including configuration loss and complete shutdown of traffic processing.

Scenario: VPX/BLX/CPX form factor

You are using Flexed/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/Pooled license seamlessly after the old license expires.
  • Restart is not required.
  • NetScaler does not require a manual capacity reconfiguration.

After the term expires

NetScaler instance stops its normal operations after the license expiry, including configuration loss and complete shutdown of traffic processing.

Scenarios for connectivity issues behavior

If connectivity breaks between NetScaler and NetScaler Console on-prem server, 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.

Scenarios for Flexed or Pooled license expiry and connectivity issues behavior
OSZAR »