GigaVUE‑OS License and GigaVUE‑OS Module License

Starting in software version 5.12, Gigamon hardware devices can be manufactured with or without a software license:

License Type	Supported Platforms
Fully licensed devices (integrated devices)	Provisioned with both hardware and software licenses. Software license is a perpetual license.
Hardware-only licensed devices (suffixed with "-HW" in the hardware type)	Provisioned with only the hardware license. Need additional software licenses for the device to be fully operational.

The following software licenses must be installed in the hardware-only licensed devices for the chassis and the modules to be active and operational:

• GigaVUE‑OS License.
• GigaVUE‑OS Module License.

Note:  GigaVUE-OS and GigaVUE-OS Module licenses support both Term and Perpetual licensing.

Supported Hardware Devices

The following table shows the licenses applicable for the GigaVUE H series and TA series devices.

License Type	Supported Platforms	Installation of License	Uninstallation/Expiry of License	Grace Period Behavior
GigaVUE‑OS License	● GigaVUE-HC1 ● GigaVUE-HC2/HC2P ● 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.	Existing traffic flow will be unaffected. No traffic-based configurations (map configurations) are allowed.
	● GigaVUE-TA25 ● GigaVUE-TA100 ● GigaVUE-TA200 ● GigaVUE-TA10 ● GigaVUE-TA40	● 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‑OS Module License	● GigaVUE-HC1 ● GigaVUE-HC2/HC2P ● 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.	Existing traffic flow will be unaffected. Traffic-based configurations (map configurations) specific to the module are not allowed.

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 H Series devices):

Chassis License Type	Module License Type	Dependency
Chassis with Hardware only license	Module with Hardware only license	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	No license requirement 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.

Install GigaVUE‑OS and GigaVUE‑OS Module license

Use the license command to install the GigaVUE‑OS and GigaVUE‑OS Module license:

For example: To install the GigaVUE‑OS license:

(config) # license install box 1 key LK2-GVOS-****-****-****-****-****-****-****-****-****-****-****
                                            -****-*

Note:  Execute the Write Memory command after installing the license.

To verify that the GigaVUE‑OS license is installed:

show license

---------

Box 2

---------

Slot    Feature    Parameters  Start Date  Expiration Date

----------------------------------------------------------

1     GVOS-module  -                       Never

Chassis-Feature  Parameters  Start Date  Expiration Date

--------------------------------------------------------

GVOS             -           2021/02/22  Never

To verify that the cards and ports are operationally up:

show card

Box ID: 2

Slot  Config    Oper Status         HW Type       Product Code  Serial Num  HW Rev  PowerReq  PowerPriority

-----------------------------------------------------------------------------------------------------------

cc1   yes     up               HC3-Main-Board     132-00DR      1DR0-1100   1.0-00  N/A       N/A

1     yes     up               PRT-HC3-X24-HW     132-00DY      1DY0-1000   1.0-0   60        1

2     yes     up               PRT-HC3-C08Q08     132-00DW      1DW0-2001   1.0-0   160       2

3     yes     up (unlicensed)  SMT-HC3-C05-HW     132-00DX      1DX0-1005   1.0-0   200       3

4     yes     up (unlicensed)  PRT-HC3-C08Q08-HW  132-00DW      1DW0-2002   1.0-0   160       4

The above show card output indicates the following:

• GigaVUE‑OS license is installed for the chassis: cc1 is displayed as licensed.
• GigaVUE‑OS Module license is installed for Module 1: Module 1 is displayed as licensed.
• Module 2 (PRT-HC3-C08Q08) is displayed as licensed, since it has the integrated license.
• The rest of the modules are displayed as unlicensed (highlighted in gray).

Note:  To assign GigaVUE‑OS and GigaVUE‑OS Module licenses from GUI Refer to Activate Licenses

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.