GigaVUE‑OS and GigaVUE-OS Module Licenses

You must consider some of the following points:

  • GigaVUE-OS and GigaVUE-OS Module licenses support both Term and Perpetual licensing.
  • You can activate the GigaVUE-OS and GigaVUE-OS Module licenses from the Gigamon Licensing portal or from the GigaVUE-FM GUI. Refer to Manage GigaSMART, GigaVUE-OS, and GigaVUE-OS Module Licenses
    • When assigning GigaVUE-OS licenses, only the relevant chassis (based on the model) is available for assignment (GigaVUE-HC1, GigaVUE-HC3, GigaVUE-HC1-Plus) based on the specific SKU.
    • When assigning GigaVUE-OS module licenses, only the relevant cards (based on the card type) is available for assignment (PRT-, BPS-, TAP-, SMT-) based on the specific SKU of the card.
  • Activation of licenses from GUI is applicable only for the following devices:
    • GigaVUE-HC1
    • GigaVUE‑HC1-Plus
    • GigaVUE-HC3
  • Devices must be running software version 6.2.00. GigaVUE-FM does not allow you to activate licenses for devices running earlier software versions.
  • You cannot transfer the GigaVUE-OS and GigaVUE-OS Modules licenses across chassis and cards.
  • On the GigaVUE-OS and GigaVUE-OS Module licenses that are activated from the GigaVUE-FM GUI, an F-icon is displayed.

Refer to the GigaVUE HC Series Data Sheet for the license SKUs.

Supported Hardware Devices

The following table shows the licenses applicable for the GigaVUE HC series and TA series devices and expiry of the license.

License Type

 Supported Platforms Installation of License

Uninstallation/Expiry of License

Term License Behavior

GigaVUE‑OS License

 
● GigaVUE‑HC1/GigaVUE‑HC1-Plus
● GigaVUE-HC3
● Chassis will be operationally up and active.
● All the modules except the CC cards will be in shutdown state.
● You cannot bring the cards up through CLI or GigaVUE-FM until the licenses are renewed.

Refer to Term License Behavior after expiry for details.

 

 
● GigaVUE-TA25
● GigaVUE-TA25E
● GigaVUE-TA200
● GigaVUE-TA200E
● GigaVUE-TA400
● Default ports will be up and active.
● Non-default ports (Pseudo slot) will require appropriate port license.
● All ports in the device will go to inactive state.
● Port level configurations (such as, admin enable, port type change) are not allowed until licenses are renewed.
GigaVUE-TA400E
● Default ports will be up and active until 100Gb speed. To upgrade to 400Gb speed, you require an upgrade license.
● All ports in the device will go to inactive state.

GigaVUE‑OS Module License
● GigaVUE‑HC1/GigaVUE‑HC1-Plus
● GigaVUE-HC3
● Ports will be up and active.
● Ports will be in inactive state.
● Port level configurations (such as, admin enable, port type change) are not allowed until licenses are renewed.

Note: The GigaVUE-HC1-X12G4 card does not require a separate module license. The GigaVUE‑OS license is used to bring up / down the card.

Appropriate banner notifications will be displayed on expiry of licenses.
The Gigamon G-TAP/Dell platforms do not support GigaVUE‑OS and GigaVUE‑OS Module License. The GigaVUE TA Series devices do not support GigaVUE‑OS Module license.

The following table provides additional details on the dependency between the chassis and the modules types for software version 5.12.00 and above (for the GigaVUE HC Series devices):

 

Chassis License Type

 Module License Type

Dependency
Chassis with Hardware only license (-HW) Module with Hardware only license (-HW card)

GigaVUE‑OS license and GigaVUE‑OS Module license are required for the chassis and the modules to be operationally up and active.

 
Chassis with integrated license Module with integrated license

Base license required for chassis and module to be operationally up.

 

Chassis with Hardware only license

Module with integrated license

GigaVUE‑OS license is required for the modules to be operationally up.

No license requirement for the ports.

Chassis with integrated license

Module with Hardware only license

GigaVUE‑OS Module license is required for the ports to be in active state.

No license requirement for the chassis.

If the GigaVUE‑OS Module license expires on the BPS card, physical bypass is enabled on all protected inline-networks in the card, allowing traffic to be physically bypassed when licenses are expired.

Rules and Notes

  • For OOB clusters, it is recommended to install license for all the nodes from the leader.
  • For Inband clusters, GigaVUE‑OS and GigaVUE‑OS module licenses (as applicable) must be installed in the individual nodes before the cluster is formed.
  • On expiry of the GigaVUE‑OS or GigaVUE‑OS Module licenses:
    • Inband cluster will break.
    • Logical inline traffic flows will get affected.
    • config switch-to will fail.
    • Switching to FIPS/Crypto Mode will fail

Note:  Renew the licenses for the above functionality/commands to work.

Troubleshooting Scenarios

Use the following table to troubleshoot issues that you might encounter on expiry of the GigaVUE‑OS and GigaVUE‑OS Module licenses.

Problem

Solution

On expiry of the GigaVUE‑OS Module license, installing the new term license or perpetual license will not move the ports to active state.
● Uninstall the new license and re-install it.
● Execute the write memory command after installing the license.

 

GigaVUE TA Series devices:
On expiry of the GigaVUE‑OS license, installing the new term license or perpetual license will not bring up the cards.
● Uninstall the new license and re-install it.
● Execute the write memory command after installing the license.

GigaVUE HC Series devices: 
On expiry of the GigaVUE‑OS license, installing the new term license or perpetual license will not bring up the cards.
● Execute the no card slot <slot number> down command for all the cards.
● If the problem persists, uninstall the new license and re-install it.
● Execute the write memory command after installing the license.

During new cluster formation or adding a node to a cluster, the leader does not detect member nodes license that have been installed before the cluster formation.
● Install the member nodes license once again from the leader after the cluster is formed.
● If the problem persists, uninstall the new license and re-install it.
● Execute the write memory command.