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

Known Issues in Panorama Plugin for VMware NSX 4.0.2

Table of Contents

Known Issues in Panorama Plugin for VMware NSX 4.0.2

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

PLUG-10766

When downgrading from Panorama plugin for VMware NSX 4.0.0 or 4.0.1 to 3.2.3 on an operation-centric deployment running Panorama 10.1.x, new dynamic address group changes are not seen on Panorama.
Workaround
: Downgrade to Panorama plugin for VMware NSX 3.2.4.

PLUG-10652

When upgrading to or downgrading from Panorama plugin for VMware NSX 3.2.4 or 4.0.1, dynamic objects are not automatically synchronized.
Workaround
: After upgrading or downgrading, select
Panorama
VMware
NSX-T
Service Managers
and click
Synchronize Dynamic Objects
.

PLUG-8532

The Panorama user interface might time out when generating a large amount of steering rules.
Workaround
: You can optimize the generation of steering rules by defining the steering rules in Panorama as post security rules.

PLUG-8503

If you delete steering rules from NSX-T manager, the service definition goes out of sync because the rules are still present on Panorama. If you delete the steering rules from Panorama and then recreate them, the service definition remains out of sync.
Workaround
: Perform a commit to Panorama after deleting the steering rules but before recreating them. Perform another commit after recreating the steering rules.

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

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

Recommended For You