Simplified installation of vSCOUT on Windows: Difference between revisions
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
Please read the article on [[vSCOUT_vSTREAM_Embedded_and_vSTREAM_Agent_resource_usage|vSCOUT resource usage]]. | Please read the article on [[vSCOUT_vSTREAM_Embedded_and_vSTREAM_Agent_resource_usage|vSCOUT resource usage]]. | ||
This article assumes familiarity with Windows server operations systems. | |||
| | ||
Line 27: | Line 29: | ||
| | ||
=== Supported Hardware === | === Supported Hardware === | ||
Line 37: | Line 38: | ||
=== Prepare === | === Prepare === | ||
> Create a first file <code> | > Open a command prompt (CMD) as Administrator. | ||
<pre> | |||
> Create a first file <code>.nsprobei</code>d containing the hostname of the target host. This name will eventually be used to identify the vSCOUT: | |||
<pre>C:\> notepad %temp%\.nsprobeid</pre> | |||
Content of the file: | Content of the file: | ||
<pre>HOSTNAME</pre> | <pre>HOSTNAME</pre> | ||
Save and exit | Save and exit. | ||
> Create a second file named <code> | > Create a second file named <code>nsagent_config.cfg</code>. Replace <A.B.C.D> with the IP address of the nGenius Server. Replace <MON> and <MAN> with the device name of the network interface on the target host. In most cases the interface to monitor will be the same interface used to communicate with nGenius (<MON>=<MAN>): | ||
<pre> | <pre>C:> notepad %temp%\nsagent_config.cfg</pre> | ||
Content of the file: | Content of the file: | ||
Line 64: | Line 67: | ||
Note: these files will be copied by the installer to their final destination in the installation folder. The file nsagent_config.cfg can be modified after installation to change vSCOUT settings as many times as you want. You must restart vSCOUT for the changes to take effect. | Note: these files will be copied by the installer to their final destination in the installation folder. The file nsagent_config.cfg can be modified after installation to change vSCOUT settings as many times as you want. You must restart vSCOUT for the changes to take effect. | ||
*<code>%temp%\.nsprobeid</code> will be copied to <code><install directory>\rtm\config\.nsprobeid</code> | |||
*<code>%temp%\nsagent_config.cfg</code> will be copied to <code><install directory>\rtm\config\nsagent_config.cfg</code> | |||
| |
Revision as of 10:55, 21 June 2020
Introduction
vSCOUT verion 6.1.1 build 336 is the final version of product that supports "lite" mode. In lite mode the agent is not analyzing traffic. It can only be used as packet forwarder to any InfiniStream NG.
The procedure below is a siplified installation procedures tested by our engineers and in accordance with our best practises. Supported OS and Harware as specified by NETSCOUT.
Please read the article on vSCOUT resource usage.
This article assumes familiarity with Windows server operations systems.
Solution
Supported Operating Systems
- Windows Server 2008 R2 SP1
- Windows Server 2012 R2 (minimum of R2 required regardless of SP level)
- Windows Server 2016
Supported Hardware
- vSCOUT is only supported on hosts based on 64-bit Intel x86 processors
Prepare
> Open a command prompt (CMD) as Administrator.
> Create a first file .nsprobei
d containing the hostname of the target host. This name will eventually be used to identify the vSCOUT:
C:\> notepad %temp%\.nsprobeid
Content of the file:
HOSTNAME
Save and exit.
> Create a second file named nsagent_config.cfg
. Replace <A.B.C.D> with the IP address of the nGenius Server. Replace <MON> and <MAN> with the device name of the network interface on the target host. In most cases the interface to monitor will be the same interface used to communicate with nGenius (<MON>=<MAN>):
C:> notepad %temp%\nsagent_config.cfg
Content of the file:
export NSCONFIG_SERVER=<A.B.C.D> export NSCOMM_PORT=395 export NSCONSOLE_PORT=7501 export HTTP_PORT=7080 export HTTPS_PORT=7443 export NUM_CPUS=2 export MEM_SIZE=2048 export MON_INF=<MON> export MGMT_INF=<MAN> export VSCOUT_MODE=lite
Save and exit (wq).
Note: these files will be copied by the installer to their final destination in the installation folder. The file nsagent_config.cfg can be modified after installation to change vSCOUT settings as many times as you want. You must restart vSCOUT for the changes to take effect.
%temp%\.nsprobeid
will be copied to<install directory>\rtm\config\.nsprobeid
%temp%\nsagent_config.cfg
will be copied to<install directory>\rtm\config\nsagent_config.cfg
Download
Use wget or curl to download the required installation file to the /tmp directory on the host. There are two versions of this file: RPM to be used with Redhat, CentOS and Amazon Linux and BIN to be used with Ubuntu, Fedore and SUSE Linux. Keep in mind that only x86_64 architecture is supported.
Installing vSCOUT using the RPM file
# md5sum is-6xxx-xxx-vSCOUT.x86_64.rpm # yum -y is-6xxx-xxx-vSCOUT.x86_64.rpm --prefix=<target directory>
The --prefix argument is optional and allows you to specify a location for the vSCOUT installation. The default location is /opt/NetScout/. If you want for example install vSCOUT in /usr/lib/NetScout/, you must specify /usr/lib/ as target directory.
Installing vSCOUT using the BIN file
# md5sum is-6xxx-xxx-vSCOUT.bin # chmod +x is-6xxx-xxx-vSCOUT.bin # ./is-6xxx-xxx-vSCOUT.bin --prefix=<target directory>
Removing vSCOUT from Linux
vSCOUT, vSTREAM Embedded and vSTREAM Agent are completely different products with different capabilities and different licenses. Before moving to vSTREAM Embedded or vSTREAM Agent, vSCOUT must be removed entirely.
To remove vSCOUT, please read the article.