
Obtain a License Key for SecurityCenter
When using a PVS with SecurityCenter, a license key may be purchased as an upgrade to an existing SecurityCenter
installation. A license key is needed for each PVS installation attached to a SecurityCenter.
Host-Based – A separate license is needed for each host where a PVS is deployed.
Network-Based – This licensing method is based on the network that the PVS will monitor. Choose from either
Class C (up to 255 contiguous hosts) or Class B (up to 65,535 contiguous hosts) options based on the size of the
monitored network.
As many PVS hosts as required can be deployed per licensed subnet and some or the entire targeted network
can be monitored at any point. If an IP range greater than the license range is specified in the PVS configuration,
it will be truncated to the licensed range. If a narrower range than the licensed range is specified, the narrower
range will be used. For example, an organization with a license of 10.32.0.0/16 may deploy a PVS with that
license with a network range of 10.32.66.0/24. Specifying a monitored range of 10.32.0.0/8 would not increase the
IP base from the licensed base of 10.32.0.0/16.
Evaluation License Key or Activation Code
To obtain an evaluation Activation Code for PVS, contact sales@tenable.com. Evaluation Activation Codes are handled
the same way by the PVS as a full Activation Code, except that an evaluation Activation Code will only allow monitoring
for 30 days. During an evaluation of the PVS, all of the features are available.
Upgrading
This section describes the steps to upgrade an existing PVS installation on Linux and Windows platforms. During the
upgrade process on both platforms, items that are commented out in the configuration file are not migrated. Review the
configuration file for any information that may need to be preserved.
Upgrading PVS on Linux
Before upgrading, the PVS services must be stopped. Failure to do so may result in errors. Custom SSL
certificates must be backed up before an upgrade. It is assumed that all commands are run with root privileges.
If you have used a PVS RPM to install PVS previously, an upgrade retains configuration settings.
Transfer the PVS RPM package to the system it is being installed on. Confirm the integrity of the installation package by
comparing the download md5 checksum with the one listed in the product release notes.
Before upgrading you will first need to stop the PVS service:
# service pvs stop
Copy the file /opt/pvs/var/pvs/tenable.key to the machine that will be used to configure the PVS after the
upgrade is complete.
Install the PVS software with the following command. Note that the specific filename will vary, depending on your version:
# rpm -Uvh pvs-4.x.x-es6.x86_64.rpm
Preparing... ########################################### [100%]
1:pvs ########################################### [100%]
[*] PVS installation completed.
#
Once the upgrade is complete, start the PVS service with the following command:
Comentarios a estos manuales