Known Limitations in XVM

LAG created when port channel deployment fails

Any changes to the Visibility Manager configuration are reverted when a port channel deployment fails. However, a link aggregation group (LAG) is created on the device. The LAG is immediately deleted, but you can see the creation and deletion of a LAG in the device logs.

Egress group configuration cannot be updated during migration

During the migration of MLX configuration to an Extreme 9920 device, you cannot change the configuration of an egress group. After migration is complete, you can change the configuration on the Extreme 9920 device, including the mapping of multiple egress to an egress group.

MLX UDA profile must be associated with an ingress group if the policy contains a UDA match

(MLX only) When you create an ingress group and associate it with an ingress policy, you must also associate the group with a UDA profile if the ingress policy contains a UDA match. For more information, see Extreme Visibility Manager Administration and User Guide, 6.1.0.

Firmware upgrade requires an absolute path to image locations

A device can be managed by only one instance of VM

Before adding a device, ensure that it is not managed by any other instance of Visibility Manager. For more information, see Extreme Visibility Manager Administration and User Guide, 6.1.0.

Listener policy byte count is incorrect when truncation is enabled

On the Extreme 9920 device, the byte count for truncated packets is the actual byte count seen by the egress ACL before truncation.

LACP LAG is not supported for Extreme 9920 devices

Although the option to select LACP LAG appears in the Create Port Channel page, the option is grayed out. Only static LAG is supported.

Only one region is supported

The Visibility Manager supports creation and management of only one region.