If the family was disabled or partially enabled, Nessus. When Nessus receives new plugins via a plugin update, Nessus enables the new plugins automatically if the family they are associated with is enabled. When you create and save a scan or policy, it records all the plugins that you select initially.
Why? Any suggestions on how to get the darn plugin to use the primary ZVM IP address (and the one that is explicitly configured via the diagnostic tool?). The plugin details include a, ,, , and. I went so far as to repeat the above steps with the secondary network interface disabled but the vCenter plugin insists on trying to use that IP address. From the vCenter the secondary network interface on the ZVM (happens to be our NFS network interface) is used by vCenter when trying to open the ZVM page. I disabled the plugin from vCenter, removed it from the /mob extension-manager interface and re-ran the diagnostic utility in order to re-install the plugin. Far Managers interface encourages keyboard operation - all actions are easily accessible with keyboard shortcuts, you can quickly record macros for any repeatable action, there are no screen redraws if it is not necessary and that makes everything faster. The ZVM diagnostics tool was re-run and now the plugin is trying to open in vCenter using a secondary IP address on the ZVM server which was not in any way specified during the diagnostics tool re-configure process. I briefly had it working from within the vCenter web-client. Yesterday I had changed the self-signed cert on our ZVM installation to an internal-CA signed cert.
0 kommentar(er)
