GigaVUE ReleaseNotes v51004

GigaVUE-OS, GigaVUE-FM, GigaVUE-VM, and
GigaVUE® Cloud Suite Release Notes v5.10.04

Updated: June 2, 2021
Document Version: 4.0 ( Change Notes )
Table of Contents
What’s New ........................................................................................................................... 2
Fixed Issues ............................................................................................................................ 9
Known Issues ........................................................................................................................ 20
Documentation Errata ....................................................................................................... 30
Deprecation Announcements .......................................................................................... 34
System Requirements ......................................................................................................... 34
Support and Compatibility ................................................................................................ 36
Installation, Migration, and Upgrade ............................................................................... 38
Documentation .................................................................................................................. 41
Additional Information ....................................................................................................... 43
Change Notes..................................................................................................................... 44
These Release Notes describe the new features and enhancements, resolved issues, and known
issues for all GigaVUE® software version 5.10.xx, including:
Product Summary
GigaVUE® H Series and With a web-based interface and a powerful command-line interface
TA Series Visibility (CLI), the Visibility Platform can replicate, filter, optimize and selectively
Fabric™ Nodes forward network traffic to monitoring, management, and security
tools. GigaVUE-OS can be used in conjunction with GigaVUE-FM to
provide extended visibility fabric management and reporting capabilities.
G-TAP A Series 2 Securely manageable active network taps that mirror network
traffic and utilizing the “Always-On” architecture.
GigaVUE® Fabric With a web-based interface, GigaVUE-FM provides high-level visibility,

Manager (GigaVUE- reporting, and management of both the physical and virtual traffic visibility
FM) nodes that form the Gigamon Visibility and Analytics Fabric™.
GigaVUE® Cloud Suite The GigaVUE Cloud Suite provides consistent visibility into data in motion
in cloud-based environments such as AWS*, Azure, Kubernetes,
Nutanix, OpenStack*, VMware*
The GigaVUE Cloud Suite extends GigaVUE traffic distribution principles
to containerized and virtualized environments, allowing users to filter,
monitor, optimize and forward traffic in private and public clouds
environments to monitoring and analysis tools.
*Is a GigaVUE V Series 2 solution.
To learn more about GigaVUE-OS, GigaVUE® Fabric Manager (GigaVUE-FM), GigaVUE® Virtual
Manager (GigaVUE-VM), GigaVUE® Cloud Suite, and other products, visit www.gigamon.com.
GigaVUE-OS, GigaVUE-FM, GigaVUE-VM, and GigaVUE® Cloud Suite Release Notes v5.10.04
What’s New
This section describes the new features and improvements introduced in v5.10.xx releases.
DOCUMENTATION NOTE: For the complete online documentation for this release, visit the GigaVUE 5.10 Online
Documentation. No login required. View What's New in the online documentation to access quick links to
topics for each of the new features. To download PDFs, check out the new Documentation Library site and
select PDF Downloads > GigaVUE 5.10 Guides.
In this section:
• New Features and Improvements in 5.10.04
• New Features and Improvements in 5.10.01.01
New Features and Improvements in 5.10.04

GigaVUE-OS 5.10.04 offers usability improvements and resolved issues. There are no new features
introduced in this release.
NOTE : Refer to Resolved 5.10.04.

GigaVUE-OS 5.10.03 offers usability improvements, resolved issues, and the following new
capabilities.
NOTE : Refer to Resolved 5.10.03 for bug fixes.
New in 5.10.02
Area Feature
Application Metadata Application Metadata Intelligence is enabled to multi-collect

Intelligence protocols with more than one metadata attribute of the same type.
This can be collected and exported in CEF format. The multi-collect
feature now supports additional protocols such as DNS, GTP, GTPV2,
DHCP, HTTP, HTTPS, SSL, HTTP_PROXY, HTTP2, KERBEROS5, and DHCP6.
(Reference: HD-59377)

GigaVUE-OS 5.10.02 offers usability improvements and resolved issues. There are no new features
introduced in this release.
NOTE : Refer to Resolved 5.10.02.
6/2/2021 What’s New 2

New Features and Improvements in 5.10.01.01

This section describes the new features and improvements introduced in GigaVUE Cloud
Suite v5.10.01.01 releases pertaining to V Series and VMware. These features were initially available
as a controlled release and are now Generally Available (GA) in GigaVUE-FM software v5.10.01.01.
New in 5.10.01.01
Feature Documentation
Network visibility with V Series nodes on VMware ESXi and NSX-T GigaVUE Cloud Suites:
The next generation of V Series fabric nodes provide improved Configure Visibility with V Series nodes
on ESXi
efficiency and accessibility on VMware environments. With the
Configure Visibility with V Series nodes
V Series solution, users can create Monitoring Sessions instead of on NSX-T
configuring vMaps and can use Automatic Target Selection Ref: GigaVUE Cloud Suite for VMware
instead of manual vNIC selection in VMware ESXi and NSX-T. Configuration Guide (Download
• V Series on VMware ESXi - The V Series fabric nodes support PDF)
traffic visibility on both the vSphere standard and distributed
switches. GigaVUE-FM creates, updates, and deletes the V
Series fabric nodes in the ESXi hosts based on the configuration
information provided by the user. You can deploy only one V
Series node on a single ESXi host. GigaVUE-FM can
communicate directly with the V series fabric nodes.
• V Series on VMware NSX-T - The V Series fabric nodes support
traffic visibility on the NSX-T NVDS switch. GigaVUE-FM creates,
manages, and deletes the V Series fabric nodes in the NSX-T
hosts based on the configuration information provided by the
user. GigaVUE-FM can communicate directly with the V Series
fabric nodes.
Gigamon Containerized Broker GCB GigaVUE Cloud Suites:

Gigamon Containerized Broker (GCB) provides the network broker Gigamon Containerized Broker
Ref: Gigamon Containerized Broker
features in a containerized form for customers who are running
Configuration Guide (Download
their workloads in containers. GCB can perform traffic acquisition, PDF)
aggregation, basic filtering, replication, and tunneling with
encryption support.
6/2/2021 What’s New 3


GigaVUE software v5.10.01 is the GA release of 5.10.xx. This release offers usability improvements,
resolved issues, and the following new capabilities. Prior to this release, GigaVUE-OS v5.10.00 was
released to embed on new hardware, exclusively. For more about 5.10.00, see New Features in
5.10.00.
New in 5.10.01
Area Feature Documentation
Threat SMT-HC1-S Hardware:

Detection GigaVUE-HC1 supports a Generation 3 GigaSMART card SMT-HC1-S (Gen 3 GigaSMART
Card)
(SMT-HC1-S), which gives 80Gb throughput and can be
Ref: GigaVUE-HC1 Hardware
used to provide the ThreatINSIGHT solution for security Installation Guide
detection.
Gigamon ThreatINSIGHT Sensor Fabric Management:

Gigamon ThreatINSIGHT is a SaaS-based network Gigamon ThreatInsight Sensor
Supported GigaSMART
security monitoring platform built with the ability to
Operations
detect, respond, and investigate network-based Ref: GigaVUE-FM User’s Guide
threats. You can now deploy Gigamon ThreatINSIGHT
Sensor on the GigaVUE-HC1 SMT-HC1-S module using
GigaVUE-FM. It provides single, integrated security
solution for threat detection.
Intent-Based Intent-Based Orchestration Enhancements: Fabric Management:

Orchestration • Multi-cluster Topology Support: create policies in Orchestrated Configurations
Ref: GigaVUE-FM User’s Guide
which the source ports, the destination ports and the
engine ports are configured across clusters.
• Hybrid Port Support: use hybrid ports in a policy as
both source ports and destination ports.
• Tagging and RBAC Support: with RBAC, the
accessibility of the users to the policies is restricted
based on the tags.
• Drop Rules: with Drop Rules, packets can be either
dropped or passed based on the usage with other
pass rules or Everything Else.
Mobility GigaSMART TCP Enhancements Fabric Management:

In 5G traffic, the GigaSMART TCP load balancing is GigaSMART SIP/RTP Correlation
5G Correlation
performed based on the following correlations:
• SIP/RTP Correlation - All the SIP/RTP traffic with port or
load balancing port group is forwarded based on
the session table. The correlation engine load
balancing keeps track of both the SIP session and
the associated multiple RTP channels.
• 5G Correlation - If the node role is CPN, the load
balancing of the packets depends upon the
parameters configured for TCP.
6/2/2021 What’s New 4

New in 5.10.01
GigaSMART 5QI Correlation Fabric Management:

In 5G traffic, 5QI values present in the control traffic and GigaSMART 5QI
its associated QoS Flow Identifiers (QFI) value are
correlated and the data traffic is sent to the tools.
Enhanced Application Session Filtering (ASF) Fabric Management:

Enhanced Application Session Filtering allows to filter a GigaSMART Application Session
Filtering (ASF) and Buffer ASF
specific application field from the incoming traffic.
GigaSMART NetFlow Generation
Enhanced Application Session Filtering supports the Ref: GigaVUE-FM User’s Guide
following session capabilities:
• Application SSL – Supports SNI field in a hello packet.
• HTTP – Supports HOST and User-agent field in a
request packet.
NetFlow Cache-less Export using TCP
NetFlow monitor enables you to set the cache timeout
to zero and makes the NetFlow to operate in a cache-
less mode. Each packet received by the NetFlow is
treated as a complete flow and the metadata
extracted from the packet are immediately exported
without caching the flow. In cacheless mode, the
metadata are directly sent to the export buffer as they
are not copied to the cache, thereby providing more
record space.
GigaSMART Stand-Alone User Plane Node Traffic Fabric Management:

Monitoring Stand-Alone User Processing
Node Traffic Monitoring
In Stand-Alone User Processing Node (UPN) traffic
monitoring, the UPN processes the subscriber
information that is extracted from the Packet
Forwarding Control Protocol (PFCP) packets and
correlates with the GTP-u traffic without the CPN.
GigaSMART 5G Network Slice Correlation Fabric Management:

Network Slicing is a feature of 5G networks whereby 5G Network Slice Correlation
slices of network resources are dedicated to a specific
application. Gigamon enables customers to have
differentiated levels of visibility for each network slice.
GigaSMART RAN Correlation Fabric Management:

This feature enables the support for RAN based 5G RAN Correlation
correlation for both 4G CUPS and 5G CUPS solutions. The
monitoring of core traffic is based upon the RAN source.
It exposes RAN data fields from control plane. RAN data
fields are available for filtering and whitelisting.
Fabric Maps Fabric Port Group Fabric Management:

Extends GigaSMART load balancing functionality to Fabric Port Group
fabric maps using circuit ids and circuit tunnels, thus
allowing load balancing between tool ports that reside
on different clusters.
6/2/2021 What’s New 5

New in 5.10.01
Flexible Inline Resilient Inline Arrangement with Single VLAN Tag Fabric Management:
Arrangement Deploy resilient inline arrangement with a single VLAN Configure Resilient Inline
Arrangement
tag in which, a packet received from an inline network
is guided to the inline tool using a single VLAN tag,
which is configurable when creating a flexible inline
map.
GigaVUE-OS Microburst Enhancements Fabric Management: Microburst

The Microburst performance in GigaVUE-OS devices Ref: GigaVUE-FM User’s Guide
have been improved such that devices have some
amount of buffer to queue these packets.
High and Low Utilization for GigaSMART Engine Ports Fabric Management:
GigaSMART engine ports now use high and low Set Port Utilization Threshold
CLI Reference:
utilization threshold percentage. The utilization alarms
port, snmp-server
will be forwarded to SNMP management stations Ref: GigaVUE-FM User’s Guide,
configured as notification destinations. GigaVUE-OS CLI Reference
Guide
Port Filter Statistics Enhancements Fabric Management: Port Filters

View the port filter counters based on the filter rules CLI Reference: port
Ref: GigaVUE-FM User’s Guide,
configured for the port.
GigaVUE-OS CLI Reference
Guide
New Active Visibility Conditions and Actions for Inline Fabric Management:
Tool Groups Configure Active Visibility
CLI Reference: policy
You can now configure Active Visibility policies using
conditions and actions that are newly added for inline GigaVUE-OS CLI Reference
tool group and flexible inline maps. Guide
Enhancements to 5G CUPS Configuration using Ansible Fabric Management:

The Gigamon Ansible Module exposes playbooks that Configuration of 5G CUPS using
Ansible.
allows the configuration and maintenance of the CUPS
solution, and the GigaVUE-FM GUI allows you to
visualize, monitor and troubleshoot the CUPS solution.
GigaVUE-FM Information Architecture and GUI Reorganization Fabric Management:

Core Improved and modernized user experience. Ease of Modern View and Classic View
accessibility of the physical and virtual nodes and the
solutions.
Alarms for Inline Networks and GigaSMART Operations Administration:

Alarms to track the changes in the health status of the Alarms for Inline Networks
View Events based on RBAC
inline network configurations and the GigaSMART
Tags
Operations. Archive or Purge Event Records
• RBAC Enhancements for Events, and Audit Logs Archive or Purge Audit Log
Records
• Filter Audit Logs and Events based on RBAC tags Ref: GigaVUE Administration
• Archive, Purge Audit Logs and Events based on Guide
RBAC tags
GigaVUE-FM Scale Enhancements Fabric Management:
6/2/2021 What’s New 6

New in 5.10.01
Provides a reliable and stable environment for Health Status
managing large number of physical devices without Flows
any impact to the performance. Includes the following Administration:
SNMP Traps
changes:
Backup/Restore
• Health computation of devices and ports in an Ref: GigaVUE-FM User’s Guide,
optimized way GigaVUE Administration Guide
• Enhancement to Flows with option to enable
through GUI
• Determining Traffic health state using SNMP traps
• Backup/Restore changes
Security Protocol Signature Enhancements Fabric Management:

Upgrade the protocol signature by upgrading the Create an Application
Intelligence Session
image file on the card, and by uploading the
GigaSMART card image to GigaVUE-FM from the
Internal Server or External Server.
GigaSMART RFS Configuration to Manage Encrypted Keys Fabric Management:

Security Use Remote File System (RFS), a component in HSM to NCipher HSM for SSL Decryption
for Out-of- Band Tools
store and manage encrypted keys.
CLI Reference: apps hsm-group
GigaVUE-OS CLI Reference
Guide
Split DNS Profile Configuration for GigaSMART Engine Port CLI Reference:
Configure separate DNS servers for internal and external apps split-dns
gigasmart
networks to ensure better security and privacy
Ref: GigaVUE-OS CLI Reference
management. Guide
Volume Volume based licensing for V Series on VMware GigaVUE Cloud Suites:
Licensing Volume-Based License (VBL) is introduced to support GCB License Information
Ref: Gigamon Containerized
V Series for VMware virtual device environments. In this
Broker Configuration Guide
model, instead of being assigned to a specific physical
chassis or GigaSMART card, your license is based on the
volume of data usage across many virtual devices
gathered per available statistics collected in GigaVUE-
FM. With VBL you can also monitor and analyze your
data usage daily, within specific service periods, or
spanning multiple service periods.
6/2/2021 What’s New 7


GigaVUE-OS 5.10.00 offers usability improvements, resolved issues, and the following new
capabilities. See Resolved 5.10.01 for a list of resolved issues.
What’s New in GigaVUE-OS

GigaVUE-OS on DELL S4112F-ON
The GigaVUE-OS is now installable on the commercial off-the-shelf (COTS) DELL S4112F-ON power
switch. This integration allows the DELL S4112F-ON, with 12 1Gb/10Gb SFP+ and three 40Gb/100Gb
QSFP28 ports, to run GigaVUE-OS with its core intelligence visibility node features and functionalities
– all in a 1RU half rack-width form factor. Adding the Advanced Feature License enables clustering,
tunneling, and header stripping. (Reference: HD-57727)
Documentation: Refer to the GigaVUE-OS on DELL S4112F-ON Installation Guide.
What’s New in Hardware

GigaVUE-TA25
The GigaVUE-TA25 is the latest member of the GigaVUE-TA Series. It has 48 ports of 1/10/25Gb and
8 40/100Gb in a 1RU form factor. The Advanced Feature License enables clustering, tunneling, and
header stripping. (Reference: HD-56397)
Documentation: Refer to the GigaVUE-TA Series Hardware Installation Guide
G-TAP A Series 2
The G-TAP A Series 2 comprises active network taps that mirror 100% of network traffic, implement
the “Always-On” architecture, and have increased density (8 TAPs in 1RU) and improved security
(SSH and SNMPv3). This release introduces the following additional products in this series:
• G-TAP-ASF21: The G-TAP A-SF2 SFP+ network TAPs run the same GigaVUE-OS as the GigaVUE TA
Series and HC Series devices, and can be managed via CLI over SSH or by GigaVUE-FM. Unlike
G-TAP A-TX2, the G-TAP A-SF21 supports SFP/SFP+ ports.
• G-TAP-ATX21-C: The G-TAP A-TX2 copper network TAPs run the same GigaVUE-OS as the
GigaVUE TA Series and HC Series devices, and the G-TAP-ATX21 model can be managed via
CLI over SSH or by GigaVUE-FM. The G-TAP-ATX21-C model looks and works just like G-TAP-
ATX21 except the Ethernet management port is disabled and can only be managed via the
console port.
(Reference: HD-58040)
Documentation: Refer to the G-TAP A Series 2 Hardware Installation Guide.
6/2/2021 What’s New 8

Fixed Issues
This section lists the issues that are resolved in each release in this branch.
Resolved 5.10.04
The following table describes the issues that were resolved in 5.10.04 sorted by Product Area and
Reference ID.
Resolved in 5.10.04
Product Area Reference Issue Description
Infrastructure- HD- 64239, The chassis migration procedure failed to successfully add a second
Mgmtd HD-64822 replacement device to the cluster, which shifted all remaining nodes
except the master device to limited mode.
Hardware HD-64977 The GigaVUE-TA25 Intel Firmware Security vulnerabilities have been
fixed.
Note: The fix requires a BIOS update. GigaVUE-FM devices would be
updated automatically. For other devices use the command ‘coreboot
install’ to update your BIOS. Power cycle the device once the update is
completed.
Infrastructure HD-64911 While a cluster/device is configured with huge number of maps, where
majority of maps have a greater number of source ports associated
with them, joining a node to the cluster, or reloading the cluster/device
can trigger the safe mode.
Hardware HD-64978 In rare scenarios the port LEDs of GigaVUE-TA25 were not functional due
to LEDs microcontroller timing issue.
Infrastructure HD-62268 Upgrade path to EL7 supported 5.13.00
Resolved 5.10.03
The following table describes the issues that were resolved in 5.10.03, sorted by Product Area and
Reference ID.
Resolved in 5.10.03
API HD-61258, Packet drop counter is not getting populated in device UI.
HD-62553
Application HD-60635, When the DNS traffic exceeds 40 KPPS, the AMI engine would not be
Intelligence HD-62560 able to export the metadata records for all DNS traffic. The "out of
buffer" counter under the VPort stats would increment indicating the
number of packets for which the metadata records are not exported.
Workaround: configure the match ipv4 rule instead of the no rule match
pass all.
Driver HD-62542 When reloading HC2 image, due to mux deselection miss, the sfp
eeproms are read incorrectly and eventually the SFP's would be
displayed as invalid. This was resolved by adding mux deselection logic.
6/2/2021 Fixed Issues 9

Resolved in 5.10.03
Flexible Inline HD-60374 Creating a map with an inline tool group that has any inline-tool with a
Bypass “down” operational state will cause the port to flap to other inline-tool
ports.
GigaVUE-OS HD-60314, When a cluster master is configured with a cluster VIP address, logs will
HD-62832 be seen in message files related to IP update in rediscd.
HD-60490, After performing reload/card enable actions, the Filter Resources API
HD-62830 query does not report correct usage and limit values.
HD-61087 Login Tracking Days, Last Login and Login Attempt options are not
HD-61140 displayed.
HD-60817, When configuring a certificate and key to the management port on

HD-62558 the GigaVUE appliance, the Private Key in its entirety is viewable later
by issuing the command 'show cli history'.
HD-62807 When the device has been running for a very long time, there is a
possibility that misleading error logs pointing to high CPU utilization may
be seen in the device logs. There will be no functional impact on the
performance of the device.
HD-62305, Cluster with multiple GigaVUE-TA100s on v5.10.02 OS experienced

HD-62540 longer than expected restore time.
GigaVUE-OS - HD-62549 Redis cluster related errors might be observed in larger cluster nodes.
Cluster
Inline Bypass - HD-61582 Traffic is not forwarded to the next inline-tool when a port is made down
Classic in the presence of OOB maps from the inline-serial ports.
Inline Bypass - HD-61687, When inline-netlag is configured with Flexible filter-template, LACP
Flexible HD-62547 protocol is flapping on the switch side.
HD-62858, Traffic outage occurs when the Inline-tool that is part of Inline-tool-
HD-62582 group is removed from the group and deleted. The Inline-tool-group is
associated with flexible Inline maps.
Inline SSL HD-62720 In H-VUE the Inline SSL profile is not configurable.
Traffic HD-62859, Combination of IPv4 and ESP protocol(0x32) based rules cannot be
HD-62500 combined in a specific map.
Resolved 5.10.02
Reference ID.

Resolved in 5.10.02
Alarm FM-35407 Incorrect health state is observed for flow maps even when the port is
Management showing healthy.
Application HD-61053 When Application Intelligence is configured to export the records of

Metadata DNS attributes, the count of exported metadata records is sometimes
Intelligence lower than the actual packets received.
Device FM-35401 The upgrade through GigaVUE-FM failed due to the failure of version
Upgrade verification during the upgrade.
Gen 3 HD-60748 Gen 3 GigaSMART card (SMT-HC1-S) card only supports frame size up
GigaSMART to 2036 bytes.
card (SMT-HC1-S)
HD-61119 The GigaSMART Gen 3 card on HC1 (SMT-HC1-S) does not support
fragmentation and reassembly for tunnel encapsulation and
decapsulation.
GigaSMART HD-61198 After the upgrade, no traffic is being sent to the tools when
Load Balancing GigaSMART load balancing is enabled.
GigaVUE- FM FM-34678 Failed to copy the migration backup file into the
Install/ ‘/config/gigamon/migration/bak directory' of the target GigaVUE-FM
Upgrade/ during Hyper-V Migration.
Migration
FM-34761 In the case where DHCPv4 is disabled, DHCPv6 is enabled and there
are no IPv6 DNS servers configured pre-migration, there is a chance
that the DNS servers already configured in the target system may be
removed post migration. In such case, configure the DNS servers in the
migrated system once again post migration.
GigaVUE TA HD-61457 During boot up of GigaVUE-TA10 and GigaVUE-TA40, GigaVUE- OS

Series Driver may hang resulting in boot failure. The only way to recover the device
from this condition is to perform a power cycle.
GigaVUE TA HD-61374 After upgrade to 5.10.01 from 5.7.05, map rules used filter-resources has
Series Upgrade been exhausted for some or all pseudo slots in GigaVUE-TA100 and
GigaVUE-TA200.
GigaVUE-FM – FM-34797 Port ID will be displayed in Fabric statistics Page alias column instead of
GUI port alias.
Packets RX/TX values will be delayed by 10 to 15 seconds on initial
page load and when user refresh the page.
GigaVUE-FM FM-35230 On the GigaVUE-FM dashboard, an incorrect number of devices is

Dashboard displayed on the "Status Summary: Node" widget.
GigaVUE-HC1 HD-60376 In GigaVUE-OS CLI on a GigaVUE-HC1 device, "no serial enable"

command behavior does not persist over reboot.
GigaVUE-OS HD-60639 Process level logs shall not be available if the overall logging level is set
to none.
GigaVUE-OS - HD-61825 GigaVUE-OS CLI access and inband cluster convergence take longer
Cluster than expected during cluster upgrade/reload.
HD-61098 Redis cluster related errors might be observed in larger cluster nodes.

Resolved in 5.10.02
GigaVUE-OS IP HD-61544 IP validation is modified to allow both IPs of /31 subnet, in IP interface
Interface configuration.
GigaVUE-VM VM-13874 After a GigaVUE-VM instance is rebooted/reloaded, the default

NSX-T gateway is retained. The commands ‘show ip route’ and ‘show ip
default-gateway’ show the gateway configured.
Hardware HD-61142 In GigaVUE-TA100, the fanout ports stop sending traffic to the tool ports
even though the interface is in UP state. The port utilization would
remain zero.
Inline Bypass - HD-61583 Failover Tool-bypass in inline-tool member of inline-serial tool group,
Classic does not work when inline-tool status down.
Inline Bypass - HD-61699 When the inline-netlag is configured with flexible filter-template in use,
Flexible LACP on the peer devices will go down and keep flapping.
Threat FM-34787 Activating INSIGHT Sensor on a GigaSMART Gen3 engine that is being
Detection – used in other GigaSMART Group results in activation failure.
Insight Sensor If you create a GigaSMART Group of type ‘gs_apps’ with one of the
GigaSMART Gen3 engines and then add a Sensor in GigaVUE-FM by
selecting the same GigaSMART engine, the INSIGHT Sensor activation
will fail, and the Activation window will not finish.
Topology FM-35135 If the tools attached to the cluster are discovered via cdp/lldp it will
return “Internal Server Error” while loading topology page.
Traffic HD-58246 If both from and to ports of a map are connected to the same switch
and the switch sends RSTP BPDU's at a higher rate, then after node
reload, the switch would detect the loop as there is a transient traffic
leak to the tool.
HD-61309 Stack links (HC3-TA200/TA100-TA100) may go down unidirectionally

(one side down) and traffic will not be forwarded on these links due to
faulty optics or cables.
V Series VM-13655 Multiple Monitoring sessions can be tested till 500Mbps only.
Resolved 5.10.01.01
The following table describes the issues that were resolved in 5.10.01.01, sorted by Product Area
and Reference ID.
Resolved in 5.10.01.01
GigaVUE Cloud VM-12514 Static IP configuration is not supported on V Series nodes.

Suite for
VMware
GigaVUE-FM FM-34986 The "Auto Export" option has been removed from the GigaVUE-FM GUI.
Administration Exporting stats data to the external server is not supported.

Resolved in 5.10.01.01
GigaVUE-OS - HD-61468 Redis cluster related errors might be observed in larger cluster nodes.
Cluster
Resolved 5.10.01
Reference ID.
Resolved in 5.10.01
Active Visibility HD-59139 The triggered time of the Active Visibility policy shown in GigaVUE-FM
incorrectly appears as with double the time zone offset applied.
Alarm FM-32602 In the GigaVUE-FM Alarms page, when hovering over an alarm
Management “Source ID” column details of the Cluster ID associated with the
alarm does not match the original Cluster ID associated with the
alarm.
FM-32605 In the GigaVUE-FM Alarms page, when the user opens the
“Correlation Detail” pop up window, details of the alarms are
displayed as three dots "..." instead of displaying the entire character
length.
FM-32622 In the GigaVUE-FM Alarms page, the "VIEW NEW ALARMS " message
blocks table content.
API HD-56153 The GigaSMART engine port status is displayed as “down” from
GigaVUE-FM even though it is "up" when viewed from the GigaVUE-
OS CLI.
Application HD-56965 App Intelligence is not able to convert IpInterface and IpAddress
Metadata directly from ipv4 to ipv6, and vice-versa. This also applies to
Intelligence Application Monitoring and Application Metadata.
Device FM-31488 When G-TAP A-TX21 is registered with GigaVUE-FM, the ports are
Configuration FM-31455 enabled with auto-negotiation. Depending on the line condition and
remote configuration, GigaVUE-FM might display the last displayed
link speed for thirty minutes without affecting the function of the link.
FM-33849 When a CBL-205 (10G-DAC) SFP cable is inserted in a GTAP-ASF21

monitor port, the link status or signal detect status is not applicable. In
this case, the device RestAPI response "operstate" and
"isSignaldetect" property value is 'none' and the same will be
reflected in GigaVUE-FM on the port page.
The health state of this port will not be re-computed, and the
previous health state of the port will continue to be shown in the
GigaVUE-FM GUI. The same port will be counted as an unhealthy
port in the Port Status Widget on the GigaVUE-FM Dashboard.
FM-34156 The port edit configuration is not getting applied from the chassis
page.

Resolved in 5.10.01
Device FM-33716 Map topology fails to display the maps if there are two or more maps
Monitoring configured with the same circuit port as a source.
Device Upgrade FM-21565 If Image extraction shows a failure status in GigaVUE-FM, check if
images are properly fetched, extracted, and installed on every
individual node.
FM-31097 After upgrading the Device via the GigaVUE-OS CLI to 5.10.00, the
subsequent rediscovery will display an authentication failure error for
the device.
Driver HD-58216 The SNMP trap was not sent due to fan fault or stuck state in
GigaVUE-TA200.
HD-59667 When LRM optics are used on GTAP-ASF, a link cannot be

HD-59705 established, or traffic will have too many errors. GTAP-ASF hardware is
not compatible with LRM optics
Flexible Inline FM-31559 For a flexible inline map, if a single tag is enabled, at least one VLAN
mapping must be provided.
FM-33121 Flexible inline canvas links to an OOB-copy tool are disconnected

from the inline tool and inline map in post-deployment.
FM-33487 When the browser zoom ratio is not at 100%, the OOB-copy and inline
tool appears disconnected from the inline map.
FM-33495 Unable to add the tool side VLAN tags with the IN-network bundle.
FM-33598 Updating the RIA solution returns a duplicate VLAN error.
FM-33634 When solutions share the same map alias in GigaVUE-FM, a single tag
VLAN config is being displayed.
HD-57786 In some cases, making multiple edits to a flexible inline map can
cause VLAN IDs to be reallocated, which can cause the inline tool to
drop packet traffic.
HD-58272 After reloading a node, the Bypass Link Aggregation Control Protocol
(LACP) packets may be forwarded to an incorrect inline-network
port in a Link Aggregation Group (LAG).
HD-58965 LACP packets are being hashed when the inline netlag has inline
network pairs from different cards. This issue is specific to GigaVUE-
HC3.
HD-59128 In an inline netlag, the LACP stops working after editing or creating
rules in the flexible inline map that requires a change in the filter
template.
FM-31283 If you use domain-policy rules in the Flex Inline SSL Canvas in 5.8 and
then upgrade to 5.9, the wildcard policy rule will not automatically
convert “domain.com” to “*.domain.com” on the canvas.

Resolved in 5.10.01
GigaSMART HD-58242 On performing the following steps, SAFE mode was expected.
• When you have an IP interface with tool ports and associates the
same port as tunnel port in the map.
• Then you remove the node from the cluster and do a factory
reset all.
• Connecting the node back.
HD-58829 Traffic loss is observed on a BPS module on a card flap (down /up)
with inline Network LAG.
GigaSMART - 5G HD-57985 Reordering of second-level flow sampling maps or whitelisting maps

CUPS created on a GigaVUE-OS device fails.
The polling of NetFlow exporter statistics fails because the GigaVUE
HC Series devices are temporarily unavailable to communicate with
GigaVUE-FM.
GigaSMART - GTP HD-60262 The REST API to add or delete GTP whitelist entries through GigaVUE-
FM in GigaVUE-HC3 fails to reflect in 2nd level whitelist maps.
GigaSMART - HD-53991 The port translation will be supported on HTTP proxy connections.
Inline SSL Note: Port translation will remain not applicable to StartTLS
connections.
HD-58390 Intermittent network connectivity is experienced on the inbound

Web server due to the soft reset of the GigaSMART engine.
GigaSMART - HD-55521 The ‘show ssl server-cert stats’ command did not display the stats of
Passive SSL remote nodes in the cluster.
GigaSMART GUI HD-59501 Unable to edit gsgroup from GUI in GigaVUE-HC1 and it throws an '
/api/v1/gtaProfiles was not found on this server' error.
GigaVUE Cloud VM-11456 Custom tags are not appearing on the EC2 instance for V Series
Suite for AWS nodes.
GigaVUE Cloud VM-13468 When the individual tunnel statistics to display are selected, the
Suite for VMware outgoing Mbps (bytes) are not displayed. The incoming packets/sec
and outgoing packets/sec are displayed though.
GigaVUE Cloud VM-13389 In the Monitoring Session statistics of VMware ESXi, the incoming
Suite for VMware Mbps (bytes) is not displayed. The incoming packets/sec, outgoing
– ESXi packets/sec, and outgoing Mbps are displayed though.
GigaVUE Cloud VM-13402 The V Series node has a limitation of up to three service chains if
Suite for VMware deployed to NSX-T.
– NSX-T
VM-13481 In legacy GVM solution for NSX-T, the user must "select all" to remove
the NSX-T connections from GigaVUE-FM, and so GigaVUE-FM can
clean up the NSX-T service deployments/templates. This applies only
to the GVM solution, not for the V Series solution.
GigaVUE-FM FM-32816 On GigaVUE-FM 5.9, seeing an old port info after updating the alias
of ports and maps.

Resolved in 5.10.01
GigaVUE-FM – FM-18690 After removing nodes from a cluster, the standalone and master
Clusters HD-60015 devices will retain the stale configuration of the removed node.
GigaVUE-FM – FM-12007 When configuring LDAP or SSL, if the Certification Check is set to ON,
Single Sign-On & user authentication fails during certificate verification.
AAA Service
FM-27868 Case sensitivity is not handled in LDAP user mapping for
GroupBaseDn.
FM-31456 Escaping special character in GroupBaseDn with '\' single backslash

won’t work. GroupBaseDn is used as an LDAP search filter. But
currently, the special characters in GroupBaseDn are not escaped as
per LDAP filter syntax.
GigaVUE-FM FM-33477 In GigaVUE-FM 5.7xx, the browser will throw an error while logging in
Administration to GigaVUE-FM if the HTTPS port (ssl port) is changed to a non-
default.
FM-33696 The “Node failed to join cluster" email notification was unsuccessful
due to duplicate entries in the list of subscription notifications.
FM-33843 Since GigaVUE-FM 5.8 was released, the installation of GigaVUE-FM is

different than it was in previous releases. One of the differences is the
fact that while installing, the GigaVUE-FM instance is rebooted twice
instead of once. This behavior is entirely normal. The consequence of
this behavior is that a login prompt was appearing between these
two reboots, even though it was not appropriate or useful to log into
the GigaVUE-FM instance at this time.
FM-34099 Unable to generate Sysdump through GigaVUE-FM or GigaVUE-OS-

CLI.
FM-34120 GigaVUE-FM showing startup time in GMT which is not matching the
time which is showing on the overview screen
GigaVUE-FM GUI FM-31510 The following GTAPA Series 2 specific battery related SNMP traps
cannot be configured from the ‘System’ page in GigaVUE-FM
(GigaVUE-FM > System > SNMP Traps):
1.Battery BET Complete
2.Battery Charge Level
3.Battery Presence
FM-32219 Data points do not display hover details when scaled to "Day" in the
Port graph.
FM-33258 In GigaVUE-FM, when navigating into a device and redirecting to

the Fabric Statistics page inside the Ports menu, the 'Select All'
checkbox is not displayed.
FM-33261 The column header and + icon is overlapping in the GigaVUE-FM grid
tables.
FM-33307 Adding multiple filters creates a long filter list that overlaps the
buttons in the GigaVUE-FM ports page.

Resolved in 5.10.01
FM-33448 The “Most Utilized” widget in the dashboard shows no data after a
refresh.
FM-33695 The Authentication field label was misspelled.
GigaVUE-FM FM-31113 During Migration, the interface names are swapped between eth0
Install / Upgrade/ and eth2.
Migration
FM-31451 To migrate an IP address, the physical links on which the static IP
address is assigned were not available.
FM-33127 When a link on the interface is down, the Static IP and routes will not
be migrated.
GigaVUE-FM FM-34096 High memory utilization was observed in TRFPOL03 South GigaVUE-FM
Scale due to which REST API timeouts and staggered performance was
experienced while running APIs.
GigaVUE-OS HD-57769 While doing config operations from GigaVUE-FM, if the master node
is reloaded via the CLI, other non-master nodes in the same cluster
would enter safe mode. This is not supported.
HD-58548 If a new map is created by sharing the same “from” port with an
existing shared collector map, the map creation will fail.
HD-58953 New CLI command to redirect the web log output.
HD-59933 When load-balance port group stats are polled via API/GigaVUE-FM,
the GigaVUE-OS times out.
HD-60167 Sometimes, a frequent switch of the master role is observed between

the standby and master node after a reload.
HD-60712 Battery optimization configuration on the monitor port is not added

to the back-up text file.
HD-60718 The battery test will not get started upon config-binary apply.
GigaVUE-OS - HD-58219 When G-TAP A-TX21 is added to GigaVUE-FM with IPV6 or DNS node
Audit/Logging name, the system log did not show in Giga VUE-GigaVUE-FM for the
GTAP-A-TX21 physical node.
GigaVUE-OS – CLI HD-57934 Inline map creation with inline network group is allowed even when
the destination ports are already associated with another inline OOB
map.
HD-59471 The command "ssh client global known-host <host entry>" does not
allow ECDSA host keys.
GigaVUE-OS - HD-57477 Executing write memory local command with cluster enabled will
Cluster throw a warning and prompt for confirmation.
GigaVUE-OS - HD-57917 While using inline-SSL on a GigaVUE-HC1 chassis, the chassis will
General sometimes not be able to fetch the flow-ops report to show the
history of the SSL sessions, as the fetch command will timeout.

Resolved in 5.10.01
GigaVUE-OS - HD-60915 Advanced feature license validation is missing while configuring

License features like cluster, tunnels, and fabric maps on the DELL S4112F-ON
switch.
GigaVUE-OS GUI HD-58462 The following CVEs are addressed:

• CVE-2020-12251
• CVE-2020-12252
GigaVUE-VM VM-13125 DSA host keys for the SSH server are not supported from 5.10.01 on
GigaVUE-VM.
Hardware HD-59534 Auto MDIX setting is enabled when copper ports have auto
negotiation disabled in X12G4 and Copper BPS line cards.
Hardware – SFP HD-54692 After swapping from 100G QSFP28 to 40G QSFP+ optics on the 100G
Swap port with an FEC "CL91" configuration, when the FEC configuration is
changed from "CL91" to "OFF" for the 40G port, the port will remain
down.
Health Monitoring FM-33262 If using GigaVUE-FM to manage a device with GigaVUE-OS v5.7.05
software, the power and fan modules that are absent in the chassis
will appear as powered off, the respective alarm for powered off will
be raised, and the overall chassis health will be incorrect with respect
to absent power and fan modules. This requires an upgrade to
device version 5.10.01 and GigaVUE-FM version 5.10.01.
Intent Based FM-31124 If you modify the rules in an orchestrated policy that is already
Orchestration deployed, and if the rules currently consume over half of the
remaining filter resources on any given source which are in use by
those rules, then the deployed policy update may fail with
inadequate filter resources error.
FM-31592 ClusterIds should not contain the letter 'P'.
FM-32582 Cannot delete or modify fabric maps generated by IBO.
FM-33513 For VLAN and inner VLAN, the ranges wider than 1000 are restricted.
FM-34295 IBO policies created in earlier versions will not be retained after the
FM-33702 GigaVUE-FM upgrade.
FM-33867
Security FM-26986 The remote Advanced Message Queuing Protocol (AMQP) service
supports one or more authentication mechanisms that allow
credentials to be sent in the clear.
FM-31080 The following CVEs are addressed:

• CVE-2019-2389
• CVE-2019-2390
FM-33004 GigaVUE-FM runs on the CentOS kernel version 3.10.0-1062.12.1.el7 in

5.9.01; but if you run the scanner after upgrading to GigaVUE-FM
5.9.01, it sometimes falsely reports the older kernel version.

Resolved in 5.10.01
You can check the GigaVUE-FM version information using "about_fm
get fm_full_version" from GigaVUE-FM CLI.
Site and Tags FM-32606 While tagging a resource, when you enter a tag value instead of
selecting an existing value, a stale tag value gets added to the
selected list of Tag values.
Statistics FM-34111 Port Utilization on GigaVUE-FM 5.9.01 (Avg Util Tx/Rx) displayed 0/0 on
network ports.
FM-34200 Port statistics graph view showed inconsistency after upgrading a

migrated GigaVUE-FM 5.9.00 to version 5.9.01. With the latest
optimizations with 5.10.01, GigaVUE-FM will provide enough samples
(based on the availability of the data) for the rate queries
irrespective of hour/day/week/month time ranges.
Traffic HD-55944 When fabric map source ports are edited with new ports, shared
collector traffic is dropped at ingress circuit GigaStream ports in cross
cluster.
HD-56849 IPv6 traffic matches v4 (IpSrc/IpDst ) based rules and vice-versa.
HD-57757 In GigaVUE HC series devices, the configuration of flexible Inline

maps with inline network LAG as source fails with Rx engine error
code 14002.
HD-61907 The issue was due to continuous PSU status flapping because of the
spurious PSU register bit in Zippy PSU.
It is fixed by determining the PSU presence based on the I2C read
error and powerok bit by CPLD "RT_EXP_REG2" register bits. (Formerly
listed by the Ref ID: HD-57635)
Traffic GUI HD-59704 IP interface cannot be configured via GigaVUE-OS if the MTU value is
changed/edited.

Known Issues
The following table describes the customer-reported and priority known issues in this release.
Note: For V Series on VMware Known Issues, please contact Gigamon Technical Support.
Key: * = Added in this release. ** = Added in post-release update to the Release Notes.
Known Issues
Alarm FM-29547 For non-admin users, permission to view an alarm for a given resource
Management is based on the user’s permission at the time of alarm generation. Any
change in resource access permission after the generation of an
alarm will not get reflected.
FM-33247 When a port that is part of a map or GigaStream or PortGroup gets

admin disabled (from UI or using API), it takes a long time to reflect in
the status (after the next health computation happens) and raise an
Alarm condition.
FM-35136 Alarms not getting cleared until manual refresh/rediscovery.
FM-35367 The GigaVUE-FM Alarm Management page does not allow multi-
select of pages, CSV download of full pages beyond 500 entries and
displays the wrong number of selected items.
API FM-32020 The global search with port alias does not display the map information
but only shows the port information.
FM-35238 Port ID is not being displayed in Fabric statistics page. Packet RX/TX
values are delayed by 10 to 15 seconds on initial page loading and
when page is refreshed.
Workaround: Refresh the page to get the port alias in fabric stats
page. To refresh the fabric stats page, wait for 10 to 15 seconds for
packets RX/TX values.
FM-35313 In dashboard widgets, API does not provide any values if the direction
field is sent as (*) for Circuit Port (Utilization), Inline Tool, Inline Network.
FM-35366 FM 5.10.01 Swagger missing Cluster ID field for Flow Ops report
summary under gsgroup API.
HD-61734 GigaVUE-FM Rest API, when used to create map rules with large ruleID
(valid int32) crashes the device.
Application FM-24987 When editing the exporter template in Application Metadata

Intelligence Intelligence, if you change any of the non-editable fields (Format,
Record Type, NetFlow Version), the solution will move to the "Failed"
state because there is no dynamic edit support for these fields on the
device side.
Workaround: Reconfigure the original template to modify these fields
instead of editing the template in the exporter.
HD-61040, As part of the Insight Solution, do not delete a VPort of an existing

FM-35820 online solution. Deleting a VPort may result in unexpected
consequences.
6/2/2021 Known Issues 20

Known Issues
HD-61742 Application Filtering Intelligence (AFI) does not filter passive FTP-DATA
traffic.
FM-34802 After creating the Application Metadata Intelligence solution, any

changes made to the Standard Collect fields found under "Advanced
Settings" are not saved.
Workaround: There is no workaround. It is best to avoid modifying the
Standard Collect fields found under "Advanced Settings" after the
solution has been created. We recommend planning your solution
and defining the Standard Collect fields needed during initial
deployment.
Backup & FM-30374 In GigaVUE-FM the backup status is not displaying the status correctly
Restore for devices that failed in a successful backup creation.
Clusters HD-56971 After the GigaSMART Card is replaced in a cluster environment and
the licenses are updated, trying to create a tunnel interface triggers
the non-master nodes to enter SAFE Mode.
(Correlates to HD-60957)
Device FM-36187 GTAP-ATX21 Ports not showing up on GigaVUE-FM.

Configuration
HD-27019 In GigaVUE-OS H-VUE, changing the chassis mode on GigaVUE-HC2
with Control Card version 2 is not supported.
Workaround: Use the chassis box-id <box ID> mode <normal | 100G>
command in the CLI to configure the mode. Once the mode is
configured in CLI, H-VUE will display it.
HD-31932 On some GigaVUE platforms, the MTU size is fixed at 9600 while on
other GigaVUE platforms the MTU size is fixed at 9400.
Workaround: Set the MTU to 9400 on all platforms.
Device Inventory FM-35195 When adding a Node to GigaVUE-FM with a site tag, the site tag does
not stick.
Driver HD-56979 SMT-HC0-Q02X08 card in GigaVUE-HC2 chassis moves into "removed"

state after chassis reboot/reload. Power cycling the chassis would
help recover from this condition.
HD-59028 When 10G link between GTAP-ASF21 and GigaVUE-TA10 are up and
running without an ifnerror, if GTAP-ASF21 is reloaded or a link is
manually flapped from the G-TAP side, then GigaVUE-TA10 will re-
establishes the link with an Ifnerror observed in GigaVUE-TA10.
Workaround: GigaVUE-TA10 side disable and enable the links recovers
ifnerror to normal.
HD-59143 When 10G SR TAA link between GTAP-ASF21 and HC2P are up and
running without ifnerror. If GTAP-ASF21 is reloaded or Link is manually
flapped from GTAP side, then HC2P re-establishes the link with Ifnerror
observed in HC2P.
Workaround: HC2P side disable and enable the links recovers ifnerror
to normal.

Known Issues
HD-60165 In G-TAP, when sfp+ sr and dac cable are mixedly interoped with
GigaVUE-TA10, sfp oir on networks ports of TA10 brings down ports of
GigaVUE-TA10 connected to tool ports of GTAP.
Workaround:
1. Admin disable/enable the corresponding port group(na,nb,ta,tb)
ports in GigaVUE-TA10 side will bring up the link.
2. SFP OIR on the down port (in GigaVUE-TA10 side) brings up the link.
Fabric Maps FM-35196 In GigaVUE-FM, the hover tooltip text on Fabric Source Ports results
remains visible even after moving away.
FM-35426 In GigaVUE-FM modern view, the Fabric Map link was moved under
Traffic which loses the auto-generated maps that are associated to
the selected asset.
FM-35427 Port Details quick view for Fabric Maps components shows minimum
details and has issues in scrolling.
Workaround: Click on ‘More Details’ link to get the complete details.
Flexible Inline FM-34526 Undo support for any accidental delete operation is currently not
available.
FM-35374 Flexible Inline solution deployment takes more time with 400+ rules in
each map.
FM-35375 The GigaVUE-FM UI takes more time to render 400+ map rules in Flex
Inline pages while Map creation or Edit is performed.
FM-35813 The number of maps that can share per source ports is 512.
HD-61815 "Configuration switch-to" to a new config from existing flexible filter

template (FFT) config with LACP bypass enabled would impact the
traffic flow.
Workaround: Enable physical bypass and reload the device after
config switch-to.
HD-61839 Filter template switch to default with scaled map config with inline-
netlag as source, disrupts traffic flow.
Workaround: Enable the physical bypass and reload the box after
switching the filter template.
HD-62580, Not able to configure the Inline SSL profile in H-VUE.

HD-62768, Workaround: Use CLI for the SSL configuration.
HD-62721
Gen 3 HD-61030 During map or tunnel encapsulation reconfigurations, some packets

GigaSMART card are dropped in the GigaSMART card (SMT-HC1-S). However, these
(SMT-HC1-S) packet drops are not counted in the RX drop counters for the
gsgroup.
HD-61123 Under rare conditions, the communication link between the controller
and the GigaSMART card (SMT-HC1-S) breaks down. In that case, any

Known Issues
subsequent attempt to fetch statistics and change the configuration
stops working.
Workaround: Reload the GigaSMART card.
GigaSMART HD-60516 GigaVUE-FM does not automatically map gen1 and gen2 cards to
their corresponding images.
Workaround: If you have gen1 and gen2 cards on a chassis, you must
manually map the images to the corresponding GS card.
HD-61058 When there are multiple maps with GSOPs sourcing from the same
network ports and you reconfigure one or more of the maps (X) to a
GSOP map that is already in use (Y), packets from X maps will briefly
leak to Y during configuration.
HD-61764** 5G/4G: The GigaSMART Engine may crash resulting in stability issues
when 5G or LTE CPN is enabled.
HD-62762 The DSCP value configured in the L2GRE encapsulation GSOP is not
effective.
GigaSMART - HD-61666 While ISSL traffic decryption is performed by the GigaSMART Engine,
Inline SSL there is a possibility of hitting the buffer overflow issue which may lead
to GigaSMART crash or reset.
The symptom noticed would be the VPort going down and the inline
network status may be displayed as abnormal.
HD-61381 ISSL will not decrypt the connections with multiple http connect
messages.
GigaSMART - HD-58141 When two NetFlow exporters are configured with one of the exporters
NetFlow containing exporter filter (IP SRC and IP DST), then the NetFlow records
may not be exported.
GigaSMART – FM-34226 Health Status of UPN remains as FAILED even after successful re-
Subscriber deployment of the failed configuration.
Intelligence
GigaSMART- HD-59442 On GigaVUE-HC3 5.7.03 with SMT-HC3-C05 card and base GigaSMART
Tunnel licenses, the L2GRE tunnel encapsulation GSOP is checking the base
‘tunneling’ license and not the expected Advanced Tunneling /
‘erspan’ license.
GigaVUE Cloud VM-10965 Monitoring session status never get changed to failure state when v
Suite for series node is down.
AnyCloud Workaround: In AnyCloud solution, user has total control of the fabric
nodes. User can power on the nodes to continue the monitoring
solutions already deployed.
GigaVUE Cloud VM-7990 GigaVUE V Series node upgrade fails for some of the instances, even
Suite for AWS though the GigaVUE V Series controller works fine.
Workaround: Before upgrading the GigaVUE V Series controllers and
nodes, the required number of free addresses must be available in
the subnets. Otherwise, the upgrade will fail.

Known Issues
VM-5800 The MTU field in the GigaVUE V Series node launch spec is a dummy
field and needs to be greyed out, because irrespective of the value
entered by the user, only 9001 is used by the GigaVUE V Series node
interfaces.
GigaVUE Cloud VM-13742 In GigaVUE-FM for Azure, the monitoring session is not displaying
Suite for Azure statistics.
GigaVUE Cloud VM-13702 NSX-V: All GigaVUE Virtual Managers are going to read status after
Suite for VMware upgrading to 5.10.01 (NSX-V, version 6.3.4).
VM-13654 GigaVUE-VM is not supported as a log source when both the

management and tunnel interfaces are on the same subnet. This issue
does not occur if the interfaces belong to 2 different networks.
Workaround: Avoid configurations with management and data
(tunnel) interfaces on the same subnet.
VM-13275 On VMware NSX-T 3.0, minimum application drops are observed

during over-night runs of 1Gbps traffic. This was observed when the
monitoring topology includes 80 or more apps.
VM-13269 Minimal rep drop observed during over-night run of 1Gbps traffic. This
was observed when the monitoring topology includes 80 or more
apps.
VM-12961 NSX-T: In GigaVUE-VM, OVFs are not certificate signed.
Workaround: for successful GVM deployment:

(1) Login to each NSX-T manager via SSH shell using the root
credentials.
(2) Open file :/config/vmware/auth/ovf_validation.properties
(3) Set the value for THIRD_PARTY_OVFS_VALIDATION_FLAG as 2 to
disable certificate validation.
(4) Click Save and exit the file.
VM-12264 Occasionally, not all GVMs power on after the host comes out of
maintenance mode.
Workaround: Manually start the GVMs that do not start automatically.
VM-11005 Added support for NSX-T liveness support in GigaVUE-VM. This helps to
configure the failure policy in NSX-T. Once done user can configure
either 'Allow' or "Block' traffic when service GigaVUE-VM is down.
VM-10097 When a vCenter connection is in "Virtual Center in unreachable"

state, user will not be able to delete it. If user attempts to delete the
connection, GigaVUE-FM will display "Failed to connect" error
message.
Workaround: Restore the connectivity between GigaVUE-FM and the
vCenter.
VM-8274 In GigaSECURE Cloud for Azure, any change in the proxy server (such
as, password) requires editing both proxy server information and the
connection information in GigaVUE-FM.

Known Issues
Workaround: Update both the proxy server information and the
connection information in GigaVUE-FM.
VM-7909 If the GigaVUE V Series node specification has a Minimum of 0, then

the V Series node(s) will be deployed at the same time the Monitoring
Session is deployed. Depending on the platform and the V Series
Node instance size/type, this can take some time for the node(s) to
launch and initialize. The monitoring session will be updated after the
GigaVUE V Series node(s) are deployed.
Workaround: There is no "workaround". The monitoring session will take
some time to deploy.
VM-4814 For NSX, the vMap traffic status is displayed as ‘Inconsistent’ when the
VMs are powered on and end-to-end traffic is flowing.
GigaVUE-FM FM-14055 For clustering, when the virtual IP address (VIP) is changed from CLI, it
does not reflect in GigaVUE-FM through configuration sync, and all
the nodes in the cluster go into an unreachable state.
Workaround:
GigaVUE-FM does not provide an option to edit the VIP, hence,
delete the cluster and add it back into GigaVUE-FM with a new VIP.
FM-31944 After configuring the remote server, the first two audit logs or the set of
audit logs without any sleep time should not be captured in syslog.
FM-33086 GigaVUE-FM RBAC stats are not restricted based on tags.
FM-33865 To change the default port used by the GigaVUE-FM web services,
you must edit ‘/etc/httpd/conf.d/ssl.conf’ manually and restart
Apache.
NOTE : Changes made in this manner will not be carried over after an
update is applied to the installed version of GigaVUE-FM.
Workaround: Re-apply the change to ssl.conf file after updating the
GigaVUE-FM version.
FM-8937 After fresh deployment or upgrade, first-time access to GigaVUE-FM

might take longer (3 to 4 minutes) than expected.
GigaVUE-FM - FM-11830 Using LDAP over SSL with certificate verification will not work in AMIs
Administration (Amazon Machine Images).
Workaround: Use SSL without certifications.
FM-17289 When modifying a scheduled task, if you enter an invalid date, the
existing scheduled task will get deleted.
Workaround: Create a new task and delete the previously created
defect
FM-34997 “Auto Export” option present in Statistics option under storage

management.
GigaVUE-FM – FM-20156 Spine-to-Spine interconnect is not supported by the GigaVUE-FM

Clusters interface.

Known Issues
Workaround: Use the GigaVUE-FM API to create, update and delete
(core spine) cluster.
FM-21813 In a map with leaf-spine topology, if one GigaStream goes down,

then the traffic health state of the map is marked ‘Red’ instead of
‘Yellow’ (even though there is a path through another spine to reach
the destination).
GigaVUE-FM – FM-17363 The notification window does not appear when editing a cluster by
Device/ Cluster adding a stack link.
Management
GigaVUE-FM – FM-17407 In GigaVUE-FM, when right-clicking in the Flex Inline workflow view, the
GUI interface displays browser-specific options. This issue is observed only
in the Edge browser.
Workaround: Use a different supported browser.
FM-20394 In GigaVUE-FM, printing list results that are multiple pages using the
browser print option is not supported on all list pages. This issue was
discovered on the Events page and the Physical Node page.
FM-33055 When attempting to create a new Role, clicking on the 'Read' or

'Write' radio buttons results in the page count changing from 2 to 18
(or 16 in some cases). The drop-down menu also shows the
corresponding pages though going to any page > 2 results in just the
2nd page (which is the actual max number of pages).
This happens only on the page where the radio button is clicked.
Moving to the next page or previous page resets the count to the
right number of pages.
Workaround:
This seems to happen only when user chooses a "R/W" radio button.
Subsequent clicking of a Read-only radio button brings back the right
page count. Note that this is only a display issue and does not affect
functionality.
FM-35627 Sorting issues on the Inventory Physical Nodes page.
FM-36488 The sorting of the 'Last Sync Time' column in the Physical Nodes page
is not functional.
HD-61023 In GigaVUE-OS the code version and hostname are exposed at the
login page.
GigaVUE-FM – FM-30912 The Single Sign-On feature is not supported in GigaVUE-FM High
Single Sign-On & Availability and External IDP cannot be configured with Giga VUE-
AAA Service GigaVUE-FM High Availability Cluster.
Workaround: Sign-in each time that you Switch between GigaVUE-FM
Clusters
FM-28536 Auto logout from GigaVUE-FM, and then relogging into GigaVUE-FM
from the same tab does not redirect the user to dashboard.
Workaround: Refresh the browser and login into GigaVUE-FM.

Known Issues
FM-28712 If you are using the IPv6 address for GigaVUE-FM, the CMS service
needs to be restarted. This only occurs in fresh installations; not
upgrades.
Workaround: Restart CMS Service.
Command: "sudo systemctl restart [email protected].
FM-34186 User group mapping will not work if the distinguished name has '\'
character.
GigaVUE-FM GUI FM-35061 The GigaVUE-FM dashboard widgets doesn't work with TAGs in 5.10.01.
GigaVUE-OS HD-60527 ALL PORT LED will glow as green when the link is UP irrespective of the
speed at which they operate.
HD-58332 In Gen3 GigaSMART-HC1 card, third-party vendor’s temperature is not

shown in the ‘show environment’ output.
HD-47497 In GigaVUE-OS CLI, after editing a GigaStream port group attached

to a map in a map group, the CLI takes longer than expected time to
process the request and appear stuck. This issue occurs in a scaled
environment.
Workaround: Wait for the CLI to complete the process, which may
take up to 15-20 minutes.
FM-33287 jQuery 1.2 reported multiple cross-site scripting vulnerability.
GigaVUE-OS – HD-33681 In an out-of-band cluster, a GigaVUE-HC2 with Control Card version 2

Cluster lost its chassis ID when its state changed from standby to master.
Workaround:
1. Issue the cluster enable command on the GigaVUE- HC2 with
Control Card version 2 and wait for the state of this node to
change to master.
2. Issue the cluster enable command on the second node in the
cluster, a GigaVUE-HC2 with a lower cluster preference.
3. Activate all the cards on the standby node from the master node.
GigaVUE-OS – IP HD-60684 IP validation is modified to allow both IPs of /31 subnet, in IP interface
Interface configuration.
GigaVUE-OS – HD-60716, Constant high CPU alerts are produced every few minutes from the
iSSL Decryption HD-62543 GSengines performing ISSL decryption.
GigaVUE-OS – HD-61631 When "show diag detail" is gathered from GigaVUE-FM for a GigaVUE-
Port Stats HC3 device running v5.7.03/5.7.04.03, the "show port stats" output is
missing. When gathered from CLI, the "port stats" output is available.
Health FM-21928 When computing the health state of map, GigaStreams with traffic
Monitoring health state ‘Red’ are prioritized compared to those with traffic health
state ‘Yellow’.
FM-33983 When Power/Fan module is removed or inserted and powered on,

inconsistently health state will be shown incorrectly in GigaVUE-FM. If
SNMP traps for power module change and fan change events are

Known Issues
enabled, then this will get corrected in next config cycle of GigaVUE-
FM.
Workaround: Do a forced rediscovery or wait up to 5 minutes for the
next config sync cycle of GigaVUE-FM to end.
High Availability FM-35451 In rare cases, when multiple GigaVUE-FM instances go down and are
not brought back up at exactly the same time, FMs device
communication can be momentarily impacted due to simultaneous
failovers.
GigaVUE-OS HD-61000 If the signaling port is present in a specific line card and if this card
status is toggled by executing "Card slot down" and then "card slot
down" then the GRIP signaling port may stay down.
HD-61143 Maps deployed by IBO stops forwarding traffic when an expired APF
license is present in the device.
HD-62459 On some occasions, UGWD process may restart when port stats are
being queried continuously for long time or if the node is managed by
GigaVUE-FM.
HD-62860 While performing a "config switch to" when the current db has a
history of meta map (especially in leaf in spine cluster environment)
edits can lead to system crash.
HD-59357 503 error from Trustwave relay using SMTP over TLS causes connection
to be closed without sending message.
GigaVUE-OS - HD-61826 Gaining access to CLI and inband cluster convergence, if GigaVUE-
Cluster TA100 is part of the cluster, it is taking long time during the cluster
upgrade/reload on an inband cluster.
Inline Bypass - HD-60938 OOB maps with ports across cross-box in a cluster is not supported.
Classic
Inline Bypass – HD-60634 When configuring a classic inline by-rule map followed by a flex inline
Sustaining collector (inline-networks used in each map is different) at a non-
master node in a cluster, would impact the traffic on by rule map.
Workaround: Create the flex inline collector is first and then create the
classic inline by-rule map.
Insight Sensor FM-32196 When you do GigaVUE-FM backup and delete the Insight tool from
GigaVUE-FM and restore the GigaVUE-FM config from the backup,
the sensor data is lost. The auto generated VPort and GS group are
not restored. Also, the Sensor status shows as “disabled”. If the user
enables the sensor, the sensor comes back in the “Awaiting code”
state instead of “Online”.
Workaround: After GigaVUE-FM restore, go to Tools > Insight Sensor
and enable the sensor. Get a new provision code from Insight portal/
support and re-provision by selecting Provision from the “Action”
menu.
FM-34624 After activating an Insight Sensor, generated gsgroup and VPort are
seen on device CLI but not on GigaVUE-FM GUI.

Known Issues
Workaround: Login as admin in GigaVUE-FM UI to see the generated
Virtual Port and GigaSMART group. Create Fabric Map with
generated VPort as destination in the first level map.
Intent Based FM-33987 The hybrid port used as a source outside IBO won’t be available in IBO
Orchestration both on source and destination.
Workaround: Delete the Legacy map and use the port in IBO.
FM-34356 Editing policy GigaSMART Operation (GSOP) and Tools together is not
FM-34731 supported.
Workaround: This should be a two-step process where: (1) edit the
GSOP deploy and then (2) edit the Tool.
Mobility – CUPS FM-34773 The status of CPN/UPN will be shown as ‘UNSUCCESSFUL’ when the
ports participating in the CUPS solution are marked as excluded under
Alarm Management.
Workaround: Do not exclude the ports that participate in the CUPS
Solution.
FM-34817 Monitor User has ‘write’ privilege on the CUPS solution.
RBAC FM-34452 Audit Log of Role does not contain name of the Role. Also, there is no
audit log generated for any operations performed on Group.
RBAC HD-61614 Remote group mapping is not working with LDAP/LDAPS.
Site and Tags FM-32604 Duplicate TAG values are displayed on Node/Cluster resource in
Physical Nodes page of GigaVUE-FM.
Software FM-31272 When a bulk addition of G-TAP devices is attempted, GigaVUE-FM

Licensing may enforce node licensing and display the license column as 'NO'
in the following two scenarios:
1. G-TAP device is unreachable, and GigaVUE-FM considers it a
device that requires a license when the node limit has
reached.
2. A device other than G-TAP( H series) that requires a license, is
being added in bulk with G-TAP, and the number of license
nodes in GigaVUE-FM has been exhausted.
Workaround: Ensure that G-TAP is always reachable while adding it to
GigaVUE-FM. If G-TAPs are added in bulk with other devices, ensure
that node license for other devices are not exhausted.
Statistics FM-34047 Since RBAC filtering at the resource level should be implemented for
/queryIndices API, you will be able to see devices that are not owned
by you but will not be able to perform any RBAC operation.
Traffic HD-40239 For GigaVUE-HC2 with Control Card version 2, under certain traffic
configurations involving network, tool, and GigaStream on the same
PRT-HC0-X24 module, traffic on the GigaStream may be affected
after a hot-swap of the module.
Workaround: Reload the GigaVUE-HC2 after swapping the PRT-HC0-
X24 module.

Known Issues
HD-59750 UDA does not match tunnel decapsulation traffic.
HD-61094 Enabling Autoneg on 10G ports with 1G optics would make the port
go down.
HD-61161 Stack link in Gigastream going down on one side is not resulting in the
port down on the peer end resulting in missing traffic.
HD-61398 Card flap on BPS module results with Traffic Loss.

Workaround: Toggling physical bypass stops the traffic loss.
HD-61708 Observing error while importing scaled map rules (300 +)

configurations from FM map canvas page for inline netlag maps.
HD-63276** When performing multiple map rule operations (such as adding and
deleting a map rule) comprising of multiple rule types (such as IPV4,
IPV6, MAC) in a single edit operation, this may result in traffic outage.
Workaround: Perform two separate edit operations; one for deletion
of the map rules and the other for adding the map rules.
Traffic – Inline HD-63017** The LFP (link fault passthrough) does not work properly when changing
Network the traffic path on an inline network. This results in inconsistent status of
inline network port pairs.
Traffic – Network HD-60159 When a network port is shared between an L2GRE encapsulation
Ports map and a shared collector map, if the traffic does not match the
qualifier, then the traffic exiting the collector port will have an
additional 4-byte VLAN.
Documentation Errata
The following table lists known corrections to the documentation.
Product Area Reference Information that should be noted in the documentation
Application HD-47495 When creating a by-rule map with IP Filters through GigaVUE-OS CLI,
Intelligence an invalid Netmask is accepted without error.
FM-34626 Config Sync issues is seen in the below three hardware platforms:
1. GigaVUE-TA25
2. GTAP A Series 2
3. DELL S4112F-ON
Workaround: The 5.10.00 version was a limited release; it is
recommendation to upgrade to GigaVUE-FM 5.10.01 release version.
Device FM-17651 When using GigaVUE-OS H-VUE and GigaVUE-FM, options like
Configuration FM-21371 "InlineToolDown", "InlineToolReady" are not available in the Active
Visibility section of the GUI.
Workaround: These options are available from the GigaVUE-OS CLI.
6/2/2021 Documentation Errata 30

FM-31640 Once the device is added to GigaVUE-FM, if the syslog is configured

either through GigaVUE-OS CLI or H-VUE, it doesn't reflect in
GigaVUE-FM. GigaVUE-FM do not pull the syslog configurations as
part of the configuration process.
Recommendation: Add the syslog servers through GigaVUE-FM.
HD-48732 The “configuration switch-to” operation may take longer than

expected for a large-scale configuration. In certain configurations,
the restore operation has been reported to fail because the
management process was unable to complete.
Documentation FM-32811 The minimum Disk storage required to install GigaVUE-FM is 84 GB.
However, in the GigaVUE-FM Installation, Migration and Upgrade
Guide, it is mentioned as 40 GB. Refer FM-32743 for details.
FM-33305 The GigaVUE-FM 5.7.02.12 image is only to be used for migration to

GigaVUE-FM 5.9.xx. It is not intended for managing production
nodes. Upgrades from earlier GigaVUE-FM releases to the migration
image must immediately be followed by an upgrade to 5.9.xx within
the same maintenance window to avoid any performance
challenges.
Driver HD-23356 Force link-up is not supported on the 100Gb CFP2 ports on the PRT-
HD0-C02X08 line card on GigaVUE HD Series nodes.
Flexible Inline HD-57995 UDA rule using uda-base as inner-l3 or inner-l4 does not match the
Bypass ERSPAN, LISP, L2GRE Inner Headers due to platform limitations.
Workaround: However, the inner headers of ERSPAN, LISP, L2GRE can
be matched using outer-l3 and outer-l4 uda-base by appropriately
adjusting the offsets.
HD-58316 The traffic issue is observed while adding the rules which has different
TCAM width requirement. This is expected as the new rule triggers
removal of all the TCAM entries and changes the TCAM width and
reconfigures all the rules. This results in Traffic Drops.
Workaround: Use the Appropriate filter temple before adding the
Rules. To modify the filter template, enable Bypass then to modify the
template.
GigaSMART HD-34496 Port “ifIndex” re-indexing of the SNMP ifTable on GigaVUE nodes
occurs when upgrading from 4.6.xx or earlier releases to 4.7.xx or later
releases. This might potentially impact monitoring for customers using
third-party management applications. As our SNMP implementation
is compliant to RFC-2863, it is recommended the management
applications account for agent side re-indexing by monitoring HOST-
RESOURCE-MIBs, for example, “sysUpTime”, and have the server-side
ifIndex in sync for monitoring the correct ports on GigaVUE nodes.
HD-47726 Inline Networks: When an Inline Network port is configured as traffic-

path bypass and there is a rule-based map from Inline Network port
to a destination, the map’s counters are incremented for traffic that
matches the rule. However, the traffic is being safely bypassed to
other side of the Network and these counters can be ignored. It is

also recommended to use a collector to avoid packet drops on
unmatched traffic.
HD-52621 In a cluster environment, when there is a NetFlow configuration, the

backup-and-restore functionality does not work as expected. The
restore operation does not push the configuration to the GigaSMART
engine of non-master nodes.
Recommendation: Copy and paste the configuration backup file
instead of running the “config text apply” operation.
HD-59108 PFCP packets received on a node will be sent to all the 4G/5G maps
configured on the device.
HD-59202 A maximum of 128 unique combinations (entries) of maps and

GigaSMART operations are allowed per GigaSMART engine. The
GigaSMART engine calculates one entry for every map associated
with a GigaSMART operation (GSOP). For example:
• If two maps are configured with a single GSOP, then two entries
will be created.
If one map is associated with two GSOPs, then two entries will be
created.
HD-61032 In Gen 3 GigaSMART card (SMT-HC1-S) after creating a map with

tunnel-encap gsop traffic drop may be seen momentarily even
though the ARP is resolved for the IP interface before configuring the
map.
GigaVUE Cloud VM-12623 In NSX-T based deployments, the service instance logical switch
Suite for VMware created by the NSX-T manager will not be deleted as part of the
service instance undeployment process. It has to be manually
deleted by the user through NSX-T GUI.
VM-13274 In the Monitoring Session statistics of VMware ESXi, the incoming data
may be disproportionate to the outgoing data and may be a lot
more than expected.
GigaVUE V Series VM-12860 VXLAN Decap: "pktDropVxLanDstPortMismatch" stats do not

increment for the destination port other than 8472, 48879, and 4789
ports.
VM-13916 To deploy a 5.10.xx V Series node, connect GigaVUE-FM to the

vCenter through "vseries-user" with the following privileges:
<add list of privileges>.
GigaVUE-FM – FM-25819 After adding the Prime License, the alarm generation will not start
Alarm until after GigaVUE-FM is restarted.
Management Workaround: Restart GigaVUE-FM after adding the Prime License
GigaVUE-FM – FM-32904 It is not possible to uses two different lb gsop operations for same
GUI port-group. So, it is an expected limitation with respective
GigaSMART.

GigaVUE-FM – FM-27001 Software Licensing updates need to be updated under "Licensing" in

Licensing FM-24065 the GigaVUE-FM User's Guide and GigaVUE Administration Guide.
GigaVUE-FM – FM-29286 The different types of GigaVUE-FM license can influence the Historical
Licensing Trend Analysis duration.
GigaVUE-FM – FM-31347 Rules involving filters of VLAN, InnerVLAN, ProtocolByte, PortSrc,

Orchestration PortDst, Ethertype, Tosval, TTL, IP6FL, and tcpctl may not correctly
calculate rule overlap. As a result, two rules using the same source
port and using the same filter from this list may have one rule
subsume traffic from the other.
GigaVUE-OS HD-59713 The DELL S4112F-ON switch will go into ONIE# prompt when the
temperature exceeds the permissible limits.
Workaround: Upgrade CPLD provided by DELL
HD-60557 PCAP feature would not capture the packets if the traffic is burst.
GigaVUE-OS – HD-53354 Changes to Secure Cryptography mode using the CLI now require a
Administration HD-52253 confirmation from the user. There is also a new ‘security’ option for
the ‘show system’ command. These need to be updated in the
HD-55211 GigaVUE Administration Guide.
Hardware HD-52659 Stack ports do not support SFP-531 (10GBASE-T module).
HD-52680 If a GigaVUE node is unable to read the product code of the Power
Supply Unit (PSU) module, then all the PSU parameters will be
displayed as N/A except the following parameters:
• Product Code
• Serial Number
• Hardware revision
• Status
In addition to the above parameters, for GigaVUE-HC3, the value for
the "capacity" parameter will also be displayed as N/A.
Minimal output voltage (such as 0.63 V) and minimal output current
(such as 0.2 A) is expected when the PSU module is in the "off" state.
This behavior is due to a voltage leak. In the GigaVUE-HC3 node, the
input under "voltage fault" is set only when there is a real under-
voltage condition.
In some modules, the temperature fault is latched, which means that
if an over-temperature condition occurs, the temperature fault is set.
When the PSU temperature drops and remains within a safe range,
the PSU module will shut down and will restore power automatically,
but the temperature fault will remain set. The only time the fault
setting is cleared is when the PSU is power cycled. This behavior
occurs in the following modules:
• GigaVUE-TA10
• GigaVUE-TA40
• GigaVUE-TA100
• GigaVUE-TA100CXP

• GigaVUE-TA200
• GigaVUE-HC1
Inline Bypass HD-29231 Enabling auto-negotiation is allowed on inline bypass ports after the
port speed has been hardcoded.
Intent Based FM-33995 Do not use fanout port as a source port in the policy.
Orchestration
Traffic – Network HD-58022 The PCAP feature on egress ports with filter rules does not capture
Ports double-tagged packets.
Deprecation Announcements
• The existing traffic threshold configuration settings have been removed and traffic health state
based on GigaSMART Engine Port utilization will not be visible.
• GigaVUE-TA1 is no longer supported as of GigaVUE-OS 5.9.00.
• Do not use the configuration delete-all command; it is not recommended and will be removed
in a future release. (ref: HD-18654)
System Requirements
GigaVUE-FM Memory and CPU Requirements
Memory and CPU requirements for GigaVUE-FM are as follows:
Reference Memory CPU Devices GVMs2 QA

Qualification
Default VM Configuration 16 GB 2vCPU 10-25 100 GVMs Qualified
GigaVUE-FM Hardware Appliance 64 GB1 12vCPU 300 100 GVMs Qualified
GigaVUE-FM Hardware Appliance 2.0 128 GB 32vCPU 300 100 GVMs Qualified
1 The default memory for GigaVUE-FM Hardware Appliance is 16 GB. You can choose to add the memory based on your
requirements. The memory given in this table is required to manage the number of devices and GVMs specified.
2 GVM: GigaVUE-VM
NOTE: The disk size (/config) after a fresh installation of GigaVUE-FM is 40GB. When you upgrade from
previous versions, you must ensure that the disk space remains at 40GB. Otherwise, you must increase
the disk space to 40GB. Refer to the “Increasing Disk Size on a New or Existing GigaVUE-FM Installation”
section in the GigaVUE-FM Installation and Upgrade Guide for instructions on how to increase the disk
size.
6/2/2021 Deprecation Announcements 34

GigaVUE-VM System Requirements

Minimum Hardware Requirements for GigaVUE-VM
Component Requirements
Hypervisor VMware ESXi (v5.5 and later)

CPU One 64-bit x86 CPUs with virtualization assist (Intel-VT or AMD-V) enabled
RAM 8GB
Disk Space 2GB shared or locally attached storage
Network At least one 1Gbps NIC
Minimum Virtual Computing Requirements
Component Requirements
Memory 2GB
Virtual CPU (vCPU) 2 vCPUs
Virtual Storage for Guest 2GB using virtual IDE
Virtual Network Interfaces 10 Network Adapters (3 in NSX)
Network Adapter 1: GigaVUE-VM Management Port
Network Adapter 2: GigaVUE-VM Tunneling Port
Network Adapter 3 – 10: GigaVUE-VM Network Ports
Supported Hypervisors
Tested Platforms
GigaVUE-VM Supported
Hypervisors vCenter Server ESXi GigaVUE-FM
vSphere ESXi v5.5 v5.5 v5.5 v5.7.02, v5.8.01, v5.9.00, v5.10.00

v6.0 v6.0.0a v6.0.0a v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.5 v6.5 v6.5 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.7 V6.7U2, v6.7U3 V6.7U2, v6.7U3 v5.7.01, v5.8.00, v5.8.01, v5.9.00,
v5.10.00
vSphere NSX T V2.5 v6.5U2, v6.7U2 v6.5U2, v6.7U2 v5.8, v5.9.00, v5.10.00
vSphere NSX V v6.2.4 v6.0 v6.0 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.2.5 v6.0 v6.0 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.3.1 v6.5 v6.5 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.3.2 v6.5 v6.5 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.3.3 v6.5 v6.5 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.3.6 v6.5 v6.5 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.4.3 v6.5U2, v6.7U2 v6.5U2, v6.7U2 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.4.4 v6.7U2 v6.7U2 v5.7.01, v5.8.00, v5.9.00, v5.10.00
v6.4.6 v6.7U3 v6.7U3 v5.8.01, v5.9.00, v5.10.00
6/2/2021 System Requirements 35

Supported Operating Systems for G-vTAP Agents

Supported Operating Systems for G-vTAP Agent v1.4-1, v1.5-1, v1.6-1, v1.7-1
Table 1 OS Support for G-vTAP Agent
Operating System Supported Version(s)
Ubuntu/Debian Versions 14 through 18

CentOS/RHEL/Fedora Versions 7 and above
(For older versions such as 5, 6, supported G-vTAP agent is v1.2)
Amazon Linux Versions 1 and 2
(For version 2, package iproute-tc must be installed first)
OpenSuse or SLES Versions 11 and 12
Windows Server Versions 2008 through 2019
G-vTAP agent version must be v1.2-1 for older releases where the kernel modules and packages
required are not officially supported.
Support and Compatibility

GigaVUE-FM and GigaVUE-OS Compatibility
GigaVUE-FM 5.10.xx supports GigaVUE-OS 5.10.xx as well as earlier versions.
Supported Browsers
Supported Browsers for GigaVUE-FM
GigaVUE-FM supports the following browsers:
Browser Minimum Version
Mozilla Firefox™ 77.01

Microsoft Edge 83.0.478.54
Apple® Safari® Version 13.05
Google® Chrome® Version 83.0.4103.106
*Internet Explorer 11 (IE11) is deprecated for security reasons and is no longer supported. IE users are
strongly encouraged to switch to Edge. (Ref. FM-25767, HD-55024, HD-55103)
Supported Browsers for GigaVUE-OS H-VUE (Classic mode) and GigaVUE-FM

GigaVUE-OS H-VUE and GigaVUE-FM support the following browsers in Classic Mode:
OS Browser Minimum Browser Version
Windows® Mozilla Firefox™ Version 77.01

Microsoft Edge Version 83.0.478.54
Apple® Safari® Version 13.05
Internet Explorer® No longer supported* (formerly, Version 11)
6/2/2021 Support and Compatibility 36

OS Browser Minimum Browser Version

Mac OSX Mozilla Firefox™ Version 77.01
Mac OSX Apple® Safari® Version 13.05
Linux
Mozilla Firefox™ Version 77.01
*Internet Explorer 11 (IE11) is deprecated for security reasons and is no longer supported. IE users are
Supported Browsers for GigaVUE-OS H-VUE Secure Cryptography Mode

GigaVUE-OS H-VUE supports the following browsers when secure cryptography mode is enabled.
OS Browser Validated Browser Version in Secure Cryptography

Mode*
Windows® Mozilla Firefox™ Version 77.01

Internet Explorer® No longer supported** (formerly, Version 11.0.120)
Mac Mozilla Firefox 77.01
*Only the stated versions have been validated. Higher versions may also be supported but are subject
to change if the vendor modifies the ciphers supported by their browser.
**Internet Explorer 11 (IE11) is deprecated for security reasons and is no longer supported. IE users are
When secure cryptography mode is enabled, only the following ciphers are supported:
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Be aware that not all browsers support these ciphers. Refer to Error! Reference source not found. for
the list of validated and recommended browser versions to use for GigaVUE-OS H-VUE when secure
cryptography mode is enabled.
6/2/2021 Support and Compatibility 37

Installation, Migration, and Upgrade

Complete installation, migration, and upgrade instructions can be found in the respective product
documentation. This section provides additional advice that is important to know before installing
or that is specific to this release. Installation and upgrade guidance in product documentation:
Product Refer to… How To…
GigaVUE-OS GigaVUE-OS Upgrade Guide install the bootloader and upgrade all GigaVUE®
H Series and TA Series Visibility Fabric™ Nodes
and Certified Traffic Aggregation White Boxes as
standalone nodes or clusters
GigaVUE-FM GigaVUE-FM Installation and install GigaVUE-FM on VMware ESXi, MS Hyper-V,
Migration Guide and KVM; migrate GigaVUE-FM data
GigaVUE-VM GigaVUE Cloud Suite for VMware install, deploy, and operate the GigaVUE® Virtual
Configuration Guide Machine (GigaVUE-VM)
GigaVUE GigaVUE Cloud Suite for… configure GigaVUE Cloud components and set
Cloud Suites • AnyCloud Configuration Guide up traffic monitoring sessions for the respective
• AWS Configuration Guide Cloud platform
• Azure Configuration Guide
• Kubernetes Configuration Guide
• Nutanix Configuration Guide
• OpenStack Configuration Guide
DOCUMENTATION NOTE
When upgrading to a new release, first download the Software and Release Notes from the Software
and Release Notes page on My Gigamon (login required).
Use the Documentation Library to download guides and access online documentation; no login
required. However, for Release Notes, you must log in to My Gigamon and go to the Software and
Release Notes page. For additional details about online documentation offerings, refer to
Documentation in this document.
GigaVUE-OS Upgrade
To upgrade GigaVUE-OS, the recommended procedure is to back-up your settings on each node
and perform the pre-upgrade checks (default admin password, the maximum number of images,
U-Boot version, and Coreboot version) before installing the image. The upgrade path from previous
versions of the GigaVUE-OS varies depending on the current OS version and node type. It is
recommended that you plan your upgrade before performing any upgrade steps.
NOTE: While upgrading from any version lower than v5.5.xx, an association of more than one VPort
to the same GigaSMART group needs to be removed for any existing GTP GigaSMART operation.
IMPORTANT : The size of the GigaVUE-OS image for GigaVUE-HC1 increased in 5.10.01 and
upgrading directly from a pre-5.9 release to 5.10.01 or above is not supported. The following upgrade
path is recommended: 5.9.00.04 or 5.9.01 → 5.10.04.
Documentation: Refer to the GigaVUE-OS Upgrade Guide for the complete upgrade procedures, also
available via the Online Documentation: 5.10.xx Upgrade Documentation and Supported Upgrade
Paths for GigaVUE-OS 5.10.xx.
6/2/2021 Installation, Migration, and Upgrade 38

GigaVUE-FM Deployments
IMPORTANT NOTE ABOUT GIGAVUE-FM DEPLOYMENTS
GigaVUE-FM deployments using releases before 5.8 cannot be directly upgraded. To preserve all
the configurations and data from the installations running prior releases of GigaVUE-FM,
complete the special migration procedure, you must perform migration steps, first.
• Fresh Installs: If deploying GigaVUE-FM for the first time in the environment OR if configuration
and data migration from the prior release is not desired, refer to the GigaVUE-FM Installation
for a fresh installation.
NOTE : If you are deploying a GigaVUE-FM Hardware Appliance 2.0, for initial configuration
of iDRAC9, refer to Dell PowerEdge - How to configure the iDRAC9 and the LifeCycle Controller
Network IP.
• Migrating from a release prior to 5.8: If you are running a version prior to 5.8, you must first
upgrade to GigaVUE-FM 5.7.02.21, a special release that provides the tools to manage and
perform the migration. You can then proceed with the migration. Refer to GigaVUE-FM
Migration in this guide.
NOTE : If you do not perform the migration, you will be required to add existing devices to
GigaVUE-FM.
GigaVUE-FM Migration
NOTE : Because the GigaVUE release v5.10.03 is for GigaVUE-OS only; not GigaVUE-FM, there is no
update to the migration instructions in this release.
You cannot directly upgrade a GigaVUE-FM instance from a release prior to 5.8 to release 5.10.04
or above. As described under GigaVUE-FM Deployments, instead of upgrading to 5.10.04, you
must migrate your existing configurations and data such as audit logs, events, syslogs, and statistics
from your current GigaVUE-FM version (prior to 5.8.xx ) to GigaVUE-FM 5.10.04.
Upgrading from 5.8.xx to 5.10.04:
• If you already migrated to 5.8.xx, you can upgrade directly to 5.10.04. Refer to GigaVUE-FM
Upgrade in this document.
Migrating to 5.10.04 from a release prior to 5.8.xx:
• If you are running a version prior to 5.8.xx, you must first upgrade to GigaVUE-FM 5.7.02.21, a
special release that provides the tools to manage and perform the migration. You can then
proceed with the migration to GigaVUE-FM 5.10.04.
• Perform the GigaVUE-FM upgrade to 5.7.02.21 and the migration to 5.10.04 in the same
maintenance/migration window.
Documentation: Refer to the GigaVUE-FM Installation and Migration Guide v5.10.01 for the procedures
or search for “GigaVUE-FM Migration” in the 5.10 Online Documentation. Refer to the “Supported
Migration and Upgrade Paths” section in the GigaVUE-FM Migration instructions for a clear description
of the paths to upgrade from any supported release.
NOTE: The GigaVUE-FM 5.7.02.21 migration image is only to be used for migration to GigaVUE-FM
5.10.02. It is not intended for managing production nodes. Upgrades from earlier GigaVUE-FM
releases to the migration image must immediately be followed by an upgrade to 5.10.02 within the
same maintenance window to avoid any performance challenges.

GigaVUE-FM Installation
GigaVUE-FM can be installed on ESX, MS HyperV, or KVM.
Documentation: Refer to the GigaVUE-FM Installation and Migration Guide for the procedures or search
for “GigaVUE-FM Installation and Migration” in the 5.10 Online Documentation.
Credentials for Admin Account for New Deployments

During new installations of GigaVUE-FM, you will be forced to create a new password that meets
the password criteria. The default password, ‘admin123A!’, can no longer be used after the first
login.
GigaVUE-FM Upgrade
NOTE: You cannot directly upgrade your GigaVUE-FM instance to release 5.10.02 from a release
prior to 5.8. Refer to GigaVUE-FM Migration Instructions in this document for details.
General GigaVUE-FM Upgrade Guidance

To upgrade GigaVUE-FM, the recommended procedure is to back up your current configuration
and perform the pre-upgrade checks (memory requirements, the maximum number of images)
before installing the image. You can upgrade via the GigaVUE-FM UI or CLI. It is recommended
that you plan your upgrade before performing any upgrade steps.
IMPORTANT: Always upgrade your GigaVUE-FM instance before upgrading the GigaVUE-OS nodes.
You can upgrade the attached nodes from the device or GigaVUE-FM. The latter is
recommended. Refer to “Upgrade Software on a GigaVUE Node or a Cluster from GigaVUE-FM” in
the GigaVUE-FM User’s Guide.
Documentation: Refer to the GigaVUE-FM Installation and Migration Guide for the GigaVUE-FM upgrade
procedures.
GigaVUE-FM Upgrade Rules and Notes

When upgrading from any version of GigaVUE-FM lower than 5.4.00, be aware of the minimum
memory requirements in the new release. Earlier releases specified 4GB of memory for the OVA
template; whereas versions after 5.4.00 require 8GB and versions after 5.7.00 require 16GB. If the
existing virtual or physical hardware running GigaVUE-FM is configured with less memory than
required, then increase the amount of memory available to the GigaVUE-FM machine. Refer to
GigaVUE-FM Memory and CPU Requirements in this document for details.
While upgrading from any version lower than 5.5.00, an association of more than one VPort to the
same GigaSMART group needs to be removed for any existing GTP GigaSMART operation.
Line Card or Module Removal Procedure (Hot Removal)

Line cards or modules are hot-swappable – they can be installed or removed from the chassis with
the power on. To remove a card safely with the power on, you must follow the procedures defined
in the Hardware Installation Guide. Hot removal without following the steps defined in the
respective document can cause system instability and require a reboot.

Documentation
Online Documentation – No Login Required
All online product documentation is available without a login. Online product documentation
provides the content from all of the product guides for the release in a single, searchable, online
format. Online documentation also includes PDF Downloads, a video library, links to the online
Troubleshooting Guide and Gigamon Validated Designs.
• For complete online documentation for this release, visit GigaVUE 5.10 Documentation. No login
required.
• View What's New in the online documentation to access quick links to topics for each of the new
features.
• To download PDFs or find additional resources, check out the new Documentation Library site.
Bookmark this link for future reference.
IMPORTANT : The online documentation does not include Release Notes. When upgrading to a
new release, first download the Software and Release Notes from the Software and Release
Notes page (login required) on the Gigamon Community, then click the Documentation Library
option to access the PDFs, online documentation, and additional resources.
How to Get the Latest Documentation—No Login Required

o Always view the Online Documentation for the latest updates.
o Visit the Documentation Library to download the latest PDFs and find additional resources.
o You can also find all published documentation from a simple search on the Gigamon
Community, even without a login. Click the Documentation tab on the Search Results
page to filter by release, doc type, or topic area.
o In the online documentation:
 Use the Search box to search across the whole doc set.
 Use the left navigation to peruse content from the full doc set in online format.
 Click the PDF Download button to visit the Documentation Downloads site.
 Check out the new Gigamon Validated Designs and Troubleshooting Guide as
well!
How to Get the Older Documentation—Login Required

• To find documentation for releases prior to 5.7:
Registered Customers can log in to the Gigamon Community. From the menu, select More >
Software & Docs to download software and documentation. In the search section, select
the Product and Release using the filters, enter "pdf" in the search box, and then click Go.
How to Get the Latest Release Notes—Login Required

• To find the Release Notes for any release:
Registered Customers can log in to the Gigamon Community. From the menu, select More >
Software & Docs to download software and documentation. In the search section, select
the Product and Release using the filters, enter "note" in the search box, and then click Go.
6/2/2021 Documentation 41
Available Documentation
Visit the Documentation Library to download the latest PDFs and find additional resources.
Hardware
• G-TAP A 2 Series Hardware Installation Guide
• GigaVUE-HC3 Hardware Installation Guide
• GigaVUE TA Series Hardware Installation Guide
Software Installation, Upgrade, and Migration

• GigaVUE-FM Installation, Migration, and Upgrade Guide
• GigaVUE-OS Upgrade Guide
• Gigamon Subscriber Metadata Aggregator Function (SMAF) Installation Guide
Administration
• GigaVUE Administration Guide (includes administration guidance for both GigaVUE-OS and
GigaVUE-FM)
Fabric Management
• GigaVUE Fabric Managment Guide
Cloud Configuration and Monitoring

• GigaVUE Cloud Suite for AnyCloud Configuration Guide
• GigaVUE Cloud Suite for AWS Configuration Guide
• GigaVUE Cloud Suite for AWS Secret Regions Configuration Guide
• GigaVUE Cloud Suite for Azure Configuration Guide
• GigaVUE Cloud Suite for OpenStack Configuration Guide
• GigaVUE Cloud Suite for Kubernetes Container Configuration Guide
• GigaVUE Cloud Suite for Nutanix Configuration Guide
• GigaVUE Cloud Suite for VMware Configuration Guide
Reference
• GigaVUE-OS CLI Reference Guide
• GigaVUE-OS Cabling Quick Reference Guide
• GigaVUE-OS Compatibility and Interoperability Matrix
• Gigamon Protocol Bundle Index (available in GigaVUE-FM and offline upon request)
• GigaVUE-OS, GigaVUE-FM, GigaVUE-VM, and GigaVUE® Cloud Suite Release Notes (this
document)
• GigaVUE-FM API Reference Guide (available within the Fabric Management reference
materials in the online documentation)
6/2/2021 Documentation 42
Additional Information
Contacting Gigamon Support
Refer to http://www.gigamon.com/support-and-services/contact-support for Technical Support hours
and contact information. You can also email Technical Support at [email protected]. Refer
also to the Gigamon Community at https://gigamoncp.force.com/gigamoncp/.
Copyright
Copyright © 2020-Gigamon Inc. All Rights Reserved. No part of this publication may be
reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language
in any form or by any means without Gigamon’s written permission.
Trademark Attributions
Gigamon and the Gigamon logo are trademarks of Gigamon in the United States and/or other
countries. Gigamon trademarks can be found at www.gigamon.com/legal-trademarks. All other
trademarks are the trademarks of their respective owners.
The Gigamon Community

The Gigamon Community is a technical site where Gigamon users, partners, security, and network
professionals and Gigamon employees come together to share knowledge and expertise, ask
questions, build their network, and learn about best practices for Gigamon products.
Visit the Gigamon Community site to:
• Find knowledge base articles and documentation
• Ask and answer questions and learn best practices from other members.
• Join special interest groups to have focused collaboration around a technology, use-case,
vertical market, or beta release
• Take online learning lessons and tutorials to broaden your knowledge of Gigamon products.
• Submit and vote on feature enhancements and share product feedback. (Customers only)
• Open support tickets (Customers only)
• Download the latest product updates and documentation (Customers only)
The Gigamon Community is a great way to get answers fast, learn from experts and collaborate
directly with other members around your areas of interest.
Register today at community.gigamon.com
Questions? Contact our Community team at [email protected]
6/2/2021 Additional Information 43

Change Notes
Date Revision Change
6/3/2021 4.0 Updated the following sections for MR version 5.10.04:

• Resolved in 5.10.04 (HD- 64239, HD-64822, HD-64977, HD-64911, HD-64978)
3/15/2021 3.3 Added HD-63017 and HD-61764 to the Known Issues list. Updated the
Documentation section.
3/5/2021 3.2 Added HD-63276 to the Known Issues list.
2/17/2021 3.1 Fixed title

• Resolved in 5.10.03 (HD-60314, HD-60374, HD-60490, HD-60635, HD-60817,
HD-61087, HD-61140, HD-61258, HD-61582, HD-61582, HD-61687, HD-62305,
HD-62500, HD-62540, HD-62542, HD-62547, HD-62549, HD-62553, HD-62558,
HD-62560, HD-62582, HD-62720, HD-62807, HD-62830, HD-62832, HD-62858,
HD-62859)
• Resolved in 5.10.02 (HD-60639)
• New Known Issues added (FM-34997, FM-35627, FM-35813, FM-36187, FM-
36488, HD-40239, HD-60716, HD-60938, HD-61631, HD-61666, HD-61708,
HD-62459, HD-62543, HD-62580, HD-62721, HD-62762, HD-62768, HD-
62860)
12/01/2020 2.1 Fixed broken links to online documentation topics.

• Resolved in 5.10.02 (FM-35407, HD-61053, FM-35401, HD-60748, HD-61119,
HD-61198, FM-34678, FM-34761, HD-61457, HD-61374, FM-34797, FM-35230,
HD-60376, HD-61825, HD-61098, HD-61544, VM-13874, HD-61142, HD-
61583, HD-61699, FM-34787, FM-35135, HD-61309, HD-58246, VM-13655)
• New Known Issues added (VM-13269, VM-10965, HD-61839, HD-61826,
HD-61815, HD-61398, HD-60516, HD-60490, HD-58141, FM-35451, FM-35427,
FM-35426, FM-35375, FM-35374, FM-35367, FM-35366, FM-35196, FM-35195,
FM-35136, FM-35061, FM-34226, FM-33287, FM-30374, FM-28536, FM-32020,
FM-32604, FM-33247, FM-34186, FM-34452, FM-35238, FM-35313, HD-27019,
HD-31932, HD-33681, HD-47497, HD-56979, HD-56971, HD-59357, HD-59435,
HD-59442, HD-60635, HD-60817, HD-61000, HD-61023, HD-61094, HD-61258,
HD-61381, HD-61582, HD-61614, HD-61687, HD-61734, HD-61742, VM-
10097, VM-12264, VM-12961, VM-13654, VM-13702, VM-13742)
• Additional Known Issues were removed as minor or non-customer issues.
9/23/2020 1.2 GigaVUE Cloud Suite for VMware and GigaVUE-VM were added to the GA
release when they were previously part of a controlled release. Merged
updates from standalone Release Notes for the controlled release into this
document, and updated these sections:
• What’s New
• Fixed Issues (VM-12514, FM-34986, VM-13402, VM-13389, VM-13468)
• Known Issues (VM-13275, VM-13269, VM-13513, VM-13655, VM-13397, VM-
12676, VM-12623, VM-12430, VM-13481, VM-13521, VM-13522)
6/2/2021 Change Notes 44

Date Revision Change
09/04/2020 1.1 Added these issues to Resolved in 5.10.01: FM-34267, HD-60015 (FM-18690),
FM-30339, FM-31455, FM-31488, FM-33004, HD-54692, HD-58829, HD-60015.
Updated the list of products in the intro and added some documentation
notes throughout.
08/28/2020 1.0 The original release of this document with version 5.10.01 GA.
6/2/2021 Change Notes 45

GigaVUE ReleaseNotes v51004

Uploaded by

Copyright:

Available Formats

GigaVUE ReleaseNotes v51004

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GigaVUE ReleaseNotes v51004

Uploaded by

Copyright:

Available Formats

GigaVUE-OS, GigaVUE-FM, GigaVUE-VM, and

GigaVUE® Cloud Suite Release Notes v5.10.04

GigaVUE® Fabric With a web-based interface, GigaVUE-FM provides high-level visibility,

New Features and Improvements in 5.10.04

New Features and Improvements in 5.10.03

Application Metadata Application Metadata Intelligence is enabled to multi-collect

New Features and Improvements in 5.10.02

6/2/2021 What’s New 2

New Features and Improvements in 5.10.01.01

Gigamon Containerized Broker GCB GigaVUE Cloud Suites:

6/2/2021 What’s New 3

New Features and Improvements in 5.10.01

Threat SMT-HC1-S Hardware:

Gigamon ThreatINSIGHT Sensor Fabric Management:

Intent-Based Intent-Based Orchestration Enhancements: Fabric Management:

Mobility GigaSMART TCP Enhancements Fabric Management:

6/2/2021 What’s New 4

GigaSMART 5QI Correlation Fabric Management:

Enhanced Application Session Filtering (ASF) Fabric Management:

GigaSMART Stand-Alone User Plane Node Traffic Fabric Management:

GigaSMART 5G Network Slice Correlation Fabric Management:

GigaSMART RAN Correlation Fabric Management:

Fabric Maps Fabric Port Group Fabric Management:

6/2/2021 What’s New 5

GigaVUE-OS Microburst Enhancements Fabric Management: Microburst

Port Filter Statistics Enhancements Fabric Management: Port Filters

Enhancements to 5G CUPS Configuration using Ansible Fabric Management:

GigaVUE-FM Information Architecture and GUI Reorganization Fabric Management:

Alarms for Inline Networks and GigaSMART Operations Administration:

GigaVUE-FM Scale Enhancements Fabric Management:

6/2/2021 What’s New 6

Security Protocol Signature Enhancements Fabric Management:

GigaSMART RFS Configuration to Manage Encrypted Keys Fabric Management:

6/2/2021 What’s New 7

New Features and Improvements in 5.10.00

What’s New in GigaVUE-OS

What’s New in Hardware

6/2/2021 What’s New 8

Infrastructure HD-62268 Upgrade path to EL7 supported 5.13.00

6/2/2021 Fixed Issues 9

HD-60817, When configuring a certificate and key to the management port on

HD-62305, Cluster with multiple GigaVUE-TA100s on v5.10.02 OS experienced

6/2/2021 Fixed Issues 10

Application HD-61053 When Application Intelligence is configured to export the records of

GigaVUE TA HD-61457 During boot up of GigaVUE-TA10 and GigaVUE-TA40, GigaVUE- OS

GigaVUE-FM FM-35230 On the GigaVUE-FM dashboard, an incorrect number of devices is

GigaVUE-HC1 HD-60376 In GigaVUE-OS CLI on a GigaVUE-HC1 device, "no serial enable"

6/2/2021 Fixed Issues 11

GigaVUE-VM VM-13874 After a GigaVUE-VM instance is rebooted/reloaded, the default

HD-61309 Stack links (HC3-TA200/TA100-TA100) may go down unidirectionally

GigaVUE Cloud VM-12514 Static IP configuration is not supported on V Series nodes.

6/2/2021 Fixed Issues 12

FM-33849 When a CBL-205 (10G-DAC) SFP cable is inserted in a GTAP-ASF21

6/2/2021 Fixed Issues 13

HD-59667 When LRM optics are used on GTAP-ASF, a link cannot be

FM-33121 Flexible inline canvas links to an OOB-copy tool are disconnected

FM-33598 Updating the RIA solution returns a duplicate VLAN error.

6/2/2021 Fixed Issues 14

GigaSMART - 5G HD-57985 Reordering of second-level flow sampling maps or whitelisting maps