Known Limitations
Note the following caveats for this
release of Extreme Visibility Manager.
- LAG created when port channel deployment fails
- Any changes to Visibility Manager configuration are
reverted when a port channel deployment fails. However, even when deployment
fails, a link aggregation group (LAG) is created on the device. The LAG is
immediately deleted, but you will see the creation and deletion of a LAG in logs
for the device.
- 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
9920, 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.
- This instruction is documented in the
Extreme Visibility Manager Administration and
User Guide, 6.1.0
but not in the Visibility Manager online help.
- Firmware upgrade requires an absolute path to image locations
- In the Absolute Path field, enter the complete file path
to the location of the firmware image. The following are sample file paths for
the various supported devices.
- 9920 (absolute
path to the binary file): /root/TierraOS-<version>-NPB.bin
- SLX (absolute directory path where supported image files are located):
/root/slxos18s.1.03/slxos18s.1.03a
- MLX (path to the manifest file): XMR-MLX/MLX_npb_06200_mnf.txt
- This instruction is documented in the
Extreme Visibility Manager Administration and
User Guide, 6.1.0
but not in the Visibility Manager online help.
- 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.
- This instruction is documented in the
Extreme Visibility Manager Administration and
User Guide, 6.1.0
but not in the Visibility Manager online help.
- 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
- This release supports the creation and
management of only one region.
