What's New
What's New contains a list of features and functionalities introduced in recent releases.
New Features in 6.14.00
GigaVUE 6.14.00 Software offers usability improvements and the new capabilities described below.
|
Product Area |
Feature Summary |
||||||
|---|---|---|---|---|---|---|---|
| Cloud Suite
|
5G-Ericsson vTAP Packet Processing (5G-EVP) 5G-Ericsson vTAP Packet Processing (5G-EVP) now reorders Ericsson vTAP packets using embedded timestamps before sending them to monitoring probes, preserving original packet sequence and reducing analysis gaps caused by out-of-order delivery. It supports PCC, CCx, and SCP traffic, uses NTP synchronization for accurate timing, and provides configurable ordering parameters. Supported on VMware ESXi, OpenStack, and Third-Party Orchestration. Refer to: 5G-Service Based Interface Application |
||||||
|
Configurable AWS EC2 Instance Type Support for VPC Traffic Mirroring GigaVUE-FM now enables you to control AWS EC2 instance type eligibility for VPC Traffic Mirroring using an GigaVUE-FM owned registry, along with UI and REST API support. This allows you to adopt new AWS instance types more quickly, without waiting for AWS SDK updates while maintaining strong RBAC enforcement and audit visibility within GigaVUE‑FM.
Refer to: Enable Traffic Mirroring for New AWS EC2 Instance Types |
|||||||
|
Enhanced AMX Troubleshooting and Deployment Workflows in GigaVUE‑FM GigaVUE‑FM improves the AMX experience with faster, UI‑driven troubleshooting and simplified deployment workflows. You can download 3PO cloud configuration files, capture AMX ingestor TCP dumps, and retrieve the latest exporter records with clear status indicators—without requiring V‑Series console access. It also lets you verify traffic ingestion and confirm that records are sent to the configured tools. GigaVUE‑FM also introduces proactive operational events such as resource utilization events, JSON web token expiry warnings, and address resolution failure notifications that help prevent issues. These enhancements reduce deployment errors, streamline exporter options, and improve scalability for high‑traffic environments. Refer to: |
|||||||
|
Ericsson 5G DTLS Support Ericsson 5G DTLS Support adds DTLS as an ingress option for 5G-EVP, alongside the existing UDP-GRE tunnel. When enabled, traffic is decrypted using the configured certificate and private key before EVP processing. DTLS can be enabled in GigaVUE-FM, and the required SSL key pair can be uploaded under Inventory > Security > SSL Key. Supported on VMware ESXi, OpenStack, and Third-Party Orchestration. Refer to: 5G-Service Based Interface Application |
|||||||
|
Fully Qualified Domain Name (FQDN) GigaVUE Cloud Suite supports the use of a fully qualified domain name (FQDN) in addition to an IPv4 or IPv6 address for the remote destination of supported egress tunnels. This support is available for VXLAN and L2GRE egress tunnels. By using an FQDN, you can keep the same tunnel configuration even when the destination IP address changes, because the system resolves the FQDN to the current IP address during operation. Refer to: |
|||||||
|
Nokia HEP3 Support for SBI Traffic from Nokia CMM GigaVUE Cloud Suite now supports processing of SBI and non-SBI traffic from Nokia Cloud Mobility Manager (CMM) vTAPs using the HEP3 (Homer Encapsulation Protocol Version 3) format. The 5G Cloud applica tion decodes and synthesizes HEP3-encapsulated traffic and delivers it to connected tools via VXLAN or L2GRE tunnels. mTLS is supported for secure ingress connections. This feature is supported on VMware ESXi, OpenStack, and Third-Party Orchestration platforms. Refer to: 5G Cloud Nokia HEP3 CMM Solution |
|||||||
|
Oracle Cloud Infrastructure (OCI) Support GigaVUE Cloud Suite now supports deployment in Oracle Cloud Infrastructure (OCI), enabling organizations to deploy and manage cloud visibility solutions in OCI environments. This enhancement extends platform support and provides consistent traffic visibility across multi-cloud deployments. |
|||||||
|
Terraform-based Deployment for GigaVUE Cloud Suite GigaVUE Cloud Suite now supports Terraform-based deployment using the Gigamon Terraform provider. You can automate the deployment and management of monitoring domains, connections, and monitoring sessions in GigaVUE-FM across GigaVUE-FM Orchestration (VMware ESXi) and Third-Party Orchestration environments. Refer to : Terraform Guide |
|||||||
|
Traffic Acquisition Enhancements for Nutanix pc.7.5 with FNS-NG 7.5.0 Environments Gigamon Cloud Suite now supports Nutanix Prism Central pc.7.5 environments that use Flow Network Security – Next Generation (FNS‑NG) 7.5.0 and the newer single-stack architecture. This update restores underlay east-west visibility by letting you steer traffic to Gigamon V Series nodes using Prism Central security policies (customer-orchestrated service insertion) or use Generic 3PO with UCT‑V mirroring. It also prevents unsupported GigaVUE-FM orchestrated underlay deployments on FNS single-stack clusters and guides you to supported options. Refer to Acquire Traffic using Customer Orchestrated Source. |
|||||||
|
GigaVUE-FM Core
|
Customer Telemetry GigaVUE-FM provides a unified Telemetry Insight dashboard and built-in EOS/EOL notifications, which enable you to quickly view health, usage, licensing risk (due to End of Sale, End of Life), and recommended actions across your physical and cloud deployments without switching between multiple pages. It also provides enhanced feature-adoption metrics that help you validate how key capabilities are used in your environment. Refer to Telemetry Insights Dashboard. |
||||||
| Enhanced Port and Map Alias Search
GigaVUE‑FM now provides comprehensive search capabilities for port and map aliases. You can search using a port alias (including partial matches) and instantly see the port along with directly related resources such as maps, GigaStreams, inline components, port groups, and interfaces in a single result set. This streamlines troubleshooting and impact analysis by eliminating the need for a separate search using the port ID. Refer to : How to Search in GigaVUE‑FM. |
|||||||
| Flexible Element Positioning in the Map's Diagram view GigaVUE‑FM now lets you reposition elements such as devices, ports, and maps in the Topology View (Free Layout), so you can organize these elements in a layout that matches how you troubleshoot traffic flows. This reduces clutter from fixed-lane layouts and makes complex topologies easier to read. Refer to Map Views. |
|||||||
| Manage Rulesets across Traffic Policies You can now copy and paste Source rules or Application rules between traffic policies to quickly reuse proven rule sets, reduce manual work, and avoid rebuilding large policies from scratch. This workflow also detects exact duplicate rules, so you can paste only the non-duplicates and keep your policies clean. Refer to Manage Rulesets across Traffic Policies. |
|||||||
|
Gigamon Insights |
Simplified Deployment and AI Experience with a Unified Prompt Library Gigamon Insights 6.14 modernizes deployment and configuration and improves the AI experience. You can now configure your LLM provider, MCP data tool, and outbound proxy in guided Fabric Manager workflows with built-in validation and dynamic updates, and you get a unified Prompt Library with search, favorites, and history to make it easy to find and reuse prompts. The release also improves accuracy for AMI/AMX-based questions by automatically injecting Gigamon-curated reference documents into the AI context—without requiring complex retrieval infrastructure. Refer to Gigamon Insights Post Deployment Configurations in GigaVUE‑FM. |
||||||
|
GigaSMART |
Artificial Intelligence (AI) Traffic Insights Artificial Intelligence (AI) Traffic Intelligence Application Intelligence supports monitoring usage of new AI apps (5) including MCP protocol accessed via web browser or desktop/mobile app for Governance, Risk and Compliance (GRC). In addition, it includes expanded coverage for Web API based classification (check for WebAPI in the Classification Workflows in the Protobook). You can access the Protobook from the GigaVUE-FM in the following ways:
|
||||||
|
Identity Enrichment using Zscaler Private Access GigaVUE Enriched Metadata (GEM) now provides identity-based enrichment through integration with Zscaler Private Access (ZPA). By correlating Application Metadata Intelligence (AMI) flow records with User Activity Logs from the ZPA Log Streaming Service (LSS), it delivers per-flow visibility into who accessed which application, when, and from where, along with the associated network policy context. This eliminates the need for separate correlation of network telemetry and supports continuous monitoring and faster troubleshooting of Zero Trust policy enforcement. Refer to: |
|||||||
|
Reload GigaSMART engine ports in a GigaSMART group Refer to: |
|||||||
|
Recurring TLS Server Name Export in Application Metadata Intelligence Application Metadata Intelligence (AMI) now supports exporting Server Name for the lifetime of TLS flows. By default, Server Name is exported at the beginning of a TLS flow. You can turn on this feature by enabling Server Name option under Recurring Attributes in AMI Settings. This feature is supported on GigaVUE HC Series Gen3 GigaSMART module through the Traffic Policy workflow and on GigaVUE V Series only
|
|||||||
|
GigaVUE‑FM Ansible Automation GigaVUE‑FM Ansible enables automation of GigaVUE‑FM operations using reusable playbooks, helping you streamline configuration, manage deployments consistently, and reduce manual effort. By leveraging Ansible, you can integrate GigaVUE‑FM into existing automation workflows and improve operational efficiency across your environment. For instructions on setting up and using Ansible with GigaVUE‑FM, refer to the GigaVUE-FM Ansible Users Guide. |
|||||||
|
GigaVUE‑OS |
Upgrade Prerequisite for Unified GigaVUE-TA Image The software image for GigaVUE‑TA25, GigaVUE‑TA25E, GigaVUE‑TA200, GigaVUE‑TA200E, GigaVUE‑TA400, and GigaVUE-TA400E will be provided as a single unified GigaVUE-TA image. GigaVUE-TA devices (GigaVUE‑TA25, GigaVUE‑TA25E, GigaVUE‑TA200, GigaVUE‑TA200E, GigaVUE‑TA400, GigaVUE-TA400E) running software versions earlier than 6.12.01 must first be upgraded to 6.12.01 or 6.13.01 before upgrading to the unified GigaVUE-TA image version 6.14.00. Upgrade attempts from versions lower than 6.12.01 directly to 6.14.00 will fail.Refer to Supported Upgrade Path—Standalone Nodes. |
||||||
|
Configuring TLS and Cryptographic Settings on the Management Interface You can configure the TLS versions, cipher suites, and curves used on the management interface. This feature helps align with internal security policies and reduces audit or scan findings by allowing you to disable unapproved cryptographic options while maintaining secure, approved settings across management protocols such as HTTPS, CURL, ACME, and secure LDAP. It also supports standardizing cryptography across your environment for greater consistency and compliance. Refer to: |
|||||||
| Hardware |
Support for Optics Dual-Rate Active Optical Cables (AOC) CBL-505A and CBL-510A supporting 40Gb/100Gb speeds.
|
||||||
|
New DC Power Cable For GigaVUE‑TA25E The DC power cable, PCD-00061, complies with the AS/NZS 5000 and AS/NZS 3015 standards applicable in the Australia and New Zealand region. This specification supports the GigaVUE‑TA25E DC-powered platform. Refer to Transceivers. |



