You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope this is the proper place to ask this question. My company is interested in getting the nProbe for troubleshooting purposes. We already have a flow collector. We just need to install the nProbe on various servers to export the flow data. The problem is that it is not permanent and we only put it on the server that needs the flow data to be collected. Once completed, we will remove it and turn the service off.
Can we revoke the license from server 1 and then apply it to server 2? From the shop.ntop.org page, it looks like the license is generated for the specific System ID.
In addition, is there a page to compare different license types (pro vs enterprise, S vs M, ...etc)? We don't need any advanced features. We only need it to export the Netflow data.
Thanks!
The text was updated successfully, but these errors were encountered:
The new license manager will work in your situation. As long as the machine with nprobe on it can talk to the machine with LM then it work. For basic data collection the pro version is what you want.
Hi team,
I hope this is the proper place to ask this question. My company is interested in getting the nProbe for troubleshooting purposes. We already have a flow collector. We just need to install the nProbe on various servers to export the flow data. The problem is that it is not permanent and we only put it on the server that needs the flow data to be collected. Once completed, we will remove it and turn the service off.
Can we revoke the license from server 1 and then apply it to server 2? From the shop.ntop.org page, it looks like the license is generated for the specific System ID.
In addition, is there a page to compare different license types (pro vs enterprise, S vs M, ...etc)? We don't need any advanced features. We only need it to export the Netflow data.
Thanks!
The text was updated successfully, but these errors were encountered: