: Known Issues in Panorama Plugin for VMware NSX 4.0.4
Focus
Focus

Known Issues in Panorama Plugin for VMware NSX 4.0.4

Table of Contents

Known Issues in Panorama Plugin for VMware NSX 4.0.4

The following list describes known issues in the Panorama plugin for VMware NSX 4.0.4.

PLUG-14186

After to upgrading to NSX plugin 4.0.4, some notifications might not be pushed to Panorama from NSX Manager.
Workaround: Perform a Synchronize Dynamic Objects for the service manager.

PLUG-14068

VM-Series firewalls might remain listed in Panorama's managed device summary after delicensing.
Workaround: Perform a full sync before and after delicensing and deleting the VM-Series firewall.

PLUG-12664

The status of VM-Series firewalls is shown as unknown in NSX Manager although it is successfully undeployed from Panorama and vSphere.

PLUG-7872

An NSX-T Service Definition does not go out-of-sync, as it should, when a steering rule is moved up or down in NSX-T. After performing a config sync, the steering rules move back to their original positions.

PLUG-7560

Fixed in Panorama plugin for VMware NSX 5.0.2.
VM-Series firewalls deployed on NSX-T remain listed on the secondary Panorama after being deleted, deactivated, and removed from the primary Panorama.

PLUG-7030

In the Panorama CLI, there is a specific order of expression arguments that must be followed when defining NSX-T security-centric membership criteria. If you do not follow this order, Panorama returns an error.
Workaround: Use this following order when defining membership criteria through the Panorama CLI.
set plugins vmware_nsx nsx_t membership-criteria SDEF1 dynamic-address-groups DAG1 criteria C1 rule R1 member-type VirtualMachine key Tag operator CONTAINS value ubuntu scope os
Or without scope
set plugins vmware_nsx nsx_t membership-criteria SDEF1 dynamic-address-groups DAG1 criteria C1 rule R1 member-type VirtualMachine key Tag operator CONTAINS value ubuntu