Tag :: DMF

When configuring the MAC address of a switch, CLI commands and REST endpoints will accept a MAC address formatted as three groups of four hexadecimal digits separated by periods (e.g. 1122.3344.5566) in addition to the already accepted form of six hexadecimal digit pairs separated by colons (e.g. 11:22:33:44:55:66). 

The DANZ Monitoring Fabric (DMF) Aggregate Arista GRE TAP action receives GRE-encapsulated packet samples from EOS switches, and generates an IPFIX report containing the flow 5-tuple, metadata, and timestamps from switches that the packet passed through.  Use the IPFIX report to determine the flows in a data fabric, monitor server session initialization delays, estimate the bandwidth of flows, and learn the path of packets through the fabric.

The DANZ Monitoring Fabric (DMF) Aggregate sFlow takes sFlow packet samples and generates an IPFIX report containing the flow 5-tuple, metadata, and timestamps from switches that the packet passed through.

A DMF interface used by a DMF policy as both a filter and a delivery interface is known as a filter-and-delivery interface. Filter-and-delivery interfaces now support configuring sFlow in the DMF Controller.

This feature supports configuring more than one L3 delivery interface over the same subnet using the same gateway.

The Switch detail page in the DMF GUI has a new Inventory tab displaying information about optics, cables, and transceivers.

This document describes the updates to the DANZ Monitoring Fabric (DMF) 8.7 release verified scale and performance numbers.

The hardware support update details newly supported hardware and other changes in the DANZ Monitoring Fabric (DMF) release 8.7.0.

This document describes the updates to the DANZ Monitoring Fabric (DMF) 8.8 release verified scale and performance numbers. Verified scale values for “DCA-DM-RN760” and “DCA-DM-RN760L” Recorder Nodes.

The hardware support update details newly supported hardware and other changes in the DANZ Monitoring Fabric (DMF) release 8.8.0.

Before version DMF-8.4, the fabric-wide settings (Features section in the screenshot below) were available on the home page (after logging in). In DMF-8.4, a newly designed Dashboard replaces the old home page. The Features section is now the new DMF Features page.

As of DMF version 8.7.0, all DMF appliances will operate on the AlmaLinux 9.4 operating system, replacing the previous Ubuntu 20.04 LTS. This migration of the underlying operating system will not impact any currently supported features.

This feature provides a method to rename a DMF object. DMF 8.7 Controllers support the Policy rename feature.

The DANZ Monitoring Fabric (DMF) allows the integration and monitoring of virtual machines in a VMware NSX fabric deployed in a vSphere environment. The DMF Controller communicates with NSX to retrieve its managed inventory and configures port mirroring sessions for selected virtual machines managed by the NSX fabric.

The DANZ Monitoring Fabric (DMF) allows the integration and monitoring of virtual machines in a VMware NSX fabric deployed in a vSphere environment. The DMF Controller communicates with NSX to retrieve its managed inventory and configures port mirroring sessions for selected virtual machines managed by the NSX fabric.

This feature prevents policy churn by automatically placing switch interfaces with frequent flapping into an error-disabled state, effectively performing an automatic administrative shutdown. The feature also allows for automatically recovering these interfaces after a specified time. This feature reduces the risk of lost packets caused by continuous recomputation of DANZ Monitoring Fabric (DMF) policies due to flapping interfaces.

If any two policies use the same filter interface and the same priority, then an additional dynamic policy will be created to ensure the delivery of packets matching both of the original policies. There is a limit on how many overlap policies can be created and it is configurable with a range between 0 to 10 with a default value of 4. Currently, we exclude policies configured as inactive in the overlap policy limit calculation. With this new feature, we exclude policies that have an expired duration from the overlap policies limit calculation.

DMF 8.5 introduced a newly designed Create Policy configuration workflow, replacing the former workflow page.

Using the show switch <switch name/all> interface details or show switch <switch name/all> interface <interface name> details commands in the CLI will now include a Description column, which provides the configured description (if any) for the corresponding interface. This is a CLI-only change.

This document addresses LAG hashing improvements across different platforms. In DANZ Monitoring Fabric (DMF) 8.7, the Controller applies the default hash configuration if no hash fields are configured or the configuration contains an error. If the Controller detects any hash error, DMF reports it as a fabric error.

DMF 8.7.0 supports Media Access Control Security (MACsec) as an Early Field Trial (EFT) feature. MACsec is a global configuration option for the entire fabric, with the option to enable it on intracore traffic only. MACsec only encrypts traffic between core switches, ignoring all other ancillary traffic (e.g., tap to filter, delivery to tool). MACsec is a licensed feature. Verify a MACsec license is installed on all switches participating in MACsec before using this feature.

This document describes managing certificates and private keys in DMF.

In DMF 8.7.0,  the redesigned integration configuration now masks the password field and improves the configuration management. Use the Edit icon to Add, Modify, or Delete the Integration configuration.

DMF 8.7.0 introduces an updated dashboard for viewing sFlow drops. The DMF analytics Node (AN) displays reasons for dropped packets as a Mirror on Drop (MOD) drop Flow sFlow collector by analyzing overall drops and drops by flow.

The new Switches page provides a modernized overview of all switches configured in DMF. A header and tabulated layout allow observation of different aspects of installed switches and provisioning new switches while on the same dashboard.

DMF version 8.8.0 introduces a redesigned workflow for Interface Groups in the DMF UI. An interface group is a collection of one or more filter or delivery interfaces, making it more convenient to create a policy. Users won't need to specify each individual interface to which the policy will apply.

DMF 8.7.0 introduces a redesigned Recorder Node configuration workflow, monitoring page, and query workflow. 

In previous versions, the DMF Controller had a hidden CLI command to change the log level from INFO to WARN for a particular port down log in the DMF Controller. This hidden command has been removed in DMF 8.7.0. The following is an example of the hidden command:

This feature keeps the configured hostname for a managed appliance and the actual hostname on the managed appliance aligned. Before this change, the configured hostname for a managed appliance on the controller and the actual hostname on the managed appliance could be different.

The new 96TB Recorder Node SKU (DCA-DM-RN760), primarily designed as a lower-cost model, meets lower data retention and recording performance requirements and is supported starting from DMF 8.7.0.

The Recorder Node (RN) supports being managed by CloudVision (CV) on-prem starting DMF 8.7.0. This feature extends support to CVaaS starting DMF 8.8.0. Recorder Node was not supported with CVaaS before 8.8.0 because of an RN requirement to store the query results file in CV while archiving the query results. However, this was not permitted on CVaaS as these files might contain data that cannot be stored in a cloud service. This feature supports CVaaS by allowing the RN to store query result files.

This document provides a comprehensive overview of the redesigned Alerts page, detailing its features and how to use them to monitor and manage Fabric health effectively. The new design improves clarity, usability, and the efficiency of alert management.

This document describes the workflow for renaming a Group Name in DMF. Navigate to Security → Groups and select Groups.

With the DANZ Monitoring Fabric (DMF) 8.7 release, a DMF Controller will allow multiple managed services to share a delivery interface with an IP address, commonly called an L3 delivery interface. These interfaces redirect the packets processed by managed services to the required tool nodes for further analysis. Sharing an L3 delivery interface is useful when applying different actions to a packet that otherwise cannot be chained together in one managed service when sending it to the same destination.

With the DANZ Monitoring Fabric (DMF) 8.7 release, a DMF Controller will allow sharing of managed services utilizing L3 delivery interfaces (e.g., NetFlow, IPFIX, app ID, etc.) across multiple policies. In prior releases, DMF did not support managed service sharing because the L3 delivery interface was an optional setting in a policy configuration. However, sharing is now supported because the managed service configuration must now specify the L3 delivery interface.

This feature supports enabling and configuring SSH host key algorithms. Along with existing SSH crypto configurations, this enables Secure Shell Daemon (sshd) configurations managed by DMF not to use SHA-1-based algorithms. DMF imposes the default SSHd configuration in the absence of configured SSH host key algorithms and MACs, which will not include SHA-1 algorithms by default.

The feature exposes metrics and health status of storage devices on controllers and all managed nodes, but not switches. Metrics and health status are updated every minute and exposed through the Telemetry collector

This feature adds support for the following IPFIX keys TCP Source Port, TCP Destination Port, UDP Source Port, UDP Destination Port

DMF 8.7.0 provides support for Management Redundancy on an Extensible Operating System (EOS) Fixed System Chassis. It provides a method to enable redundant active/active connectivity on the management IP address for a Danz Monitoring Fabric (DMF) switch in a fixed system chassis using an out-of-band management port and a front-panel port on the switch.

This document describes a new feature of Arista Analytics that can process sFlow^® records containing IP packets encapsulated in additional protocol headers.

Use this feature to configure Access Control Lists (ACLs) on a managed device that do not directly reflect the ACLs configured on the controller. Specifically, a user can override the user-configured ACLs on the controller (generally inherited by the managed devices) so that ACLs allowing specific types of traffic from the controller-only are pushed to managed devices.

Often, there is a need to accept IPFIX/NFv9 and NFv5 traffic arriving at ports other than the standard 4739 and 2055 ports, respectively. To address this need, DMF allows the following non-standard ports to forward traffic to their standard ports on the physical IP of the Analytics Node (AN) and the cluster's Virtual IP (VIP).

The system reinstall feature allows users to reinstall EOS on an Arista switch. A system reinstall is accomplished by removing the local startup-config/zerotouch-config on the switch so the DMF controller no longer manages it. Rebooting the switch restarts the Arista native ZTP process and requests a fresh image from the controller.

On platforms with multiple FAPs (e.g., chassis), hashing parameters (hash seed, polynomial, etc.) must be synced across all the FAPs when symmetric hashing is enabled to ensure hashing behavior is consistent for any given ingress port. The fix applies to all DMF Sand platforms running EOS.

DMF 8.7.0 introduces an updated dashboard for analyzing TCP Flows from Dapper. The DMF Analytics Node (AN) displays TCP Window, Network Loss, Zero Window, RTT vs Sender Reaction Time for flows or select Flow from TCP Health Flows.

The following describes LAG hashing for L2GRE and VXLAN transit traffic on Arista 7050X4 platforms: For L2GRE transit traffic, LAG hashing uses only the encapsulated (inner) packet header fields. There is no option to use underlay (outer) packet header fields. When the encapsulated packet is IP, the system uses the IP parameters configured with hash ipv4 or hash ipv6 for hashing.

UDF is an important DMF feature that matches customized fields in packet payloads for network traffic filtering on the Arista 7050X4 Series. Only supports IPv4 traffic UDF filtering, Maximum UDFs per rule: 6 UDFs.

DMF 8.7.0 introduces an updated dashboard for viewing tunnel traffic. The widgets display traffic distribution by tunnel type using sFlow traffic categorized by a combination of Ethernet Type, Protocol, and L4 ports. Recognized tunnels include:

The Arista Service Node (SN) provides specialized packet processing within the DANZ Monitoring Fabric (DMF), which is not easily accomplished within the CPU on a switch.  The SN provides a packet processing pipeline tied to a physical interface, reading packets and writing results from the same interface.

This document describes the usage of wildcard tunnels for VMware vCenter monitoring. The current implementation of VMware vCenter creates one tunnel interface from every ESXi host to DMF.