This section describes ways to install the Panorama plugin for VMware
NSX.
| Where Can I Use
This? | What Do I Need? |
|---|
Download and install the Panorama plugin for VMware NSX. See the
Compatibility Matrix before installing or
upgrading your plugin.
The security-centric deployment workflow requires the Panorama plugin for VMware
NSX 4.0.0. Additionally, you must upgrade to plugin 4.0.0 from Panorama plugin
for VMware NSX 3.2.x.
If you have a Panorama HA configuration, repeat this installation process on each
Panorama peer. When installing the plugin on Panorama HA peers, install the plugin
on the passive peer before the active peer. After installing the plugin on the
passive peer, it will transition to a nonfunctional state. Installing the plugin on
the active peer returns the passive peer to a functional state.
If you have a standalone Panorama or two Panorama appliances installed in an HA pair
with multiple plugins installed, the plugins might not receive updated IP-tag
information if one or more of the plugins is not configured. This occurs because
Panorama won’t forward IP-tag information to unconfigured plugins. Additionally,
this issue can occur if one or more of the Panorama plugins is not in the Registered
or Success state (positive state differs on each plugin). Ensure that your plugins
are in the positive state before continuing or executing the commands described
below.
If you encounter this issue, there are two workarounds:
Uninstall the unconfigured plugin or plugins. It is recommended that you
don’t install a plugin that you don’t plan to configure right away
You can use the following commands to work around this issue. Execute the
following command for each unconfigured plugin on each Panorama instance to
prevent Panorama from waiting to send updates. If you don’t, your firewalls
may lose some IP-tag information.
request plugins dau
plugin-name <plugin-name> unblock-device-push yesYou can
cancel this command by executing:
request plugins dau
plugin-name <plugin-name> unblock-device-push no
The commands described are not persistent across reboots and must be used again for
any subsequent reboots. For Panorama in HA pair, the commands must be executed on
each Panorama.
