Simplified installation of vSCOUT on Windows: Difference between revisions

From wiki.comcert.com
Jump to navigation Jump to search
VisualWikitext
No edit summary
No edit summary
Line 2: Line 2:
== Introduction ==
== 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.
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 to forward packets encapsulated in GRE or UDP to a InfiniStreamNG.  vSCOUT consumes signifiantly less CPU time when in lite mode than when in standard mode.


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.
The procedure below requires the use of a MSI installer transformed by COMCERT and is only available to COMCERT customers with an active support contract.  This installer overcomes a few installation limitations and problems with the NETSCOUT provided installer.


Please read the article on [[vSCOUT_vSTREAM_Embedded_and_vSTREAM_Agent_resource_usage|vSCOUT resource usage]] before you start.
Please read the article on [[vSCOUT_vSTREAM_Embedded_and_vSTREAM_Agent_resource_usage|vSCOUT resource usage]] before you start.


This article assumes familiarity with Windows server operations systems.
This article assumes familiarity with Windows Server OS.


 
 
Line 19: Line 19:
*Windows Server 2012 R2 (minimum of R2 required regardless of SP level)  
*Windows Server 2012 R2 (minimum of R2 required regardless of SP level)  
*Windows Server 2016  
*Windows Server 2016  
*Windows Server 2019 (not officially supported by NETSCOUT)


 
 
Line 24: Line 25:
=== Supported Hardware ===
=== Supported Hardware ===


*vSCOUT is only supported on hosts based on 64-bit Intel x86 processors  
*vSCOUT is supported on virtual and physical hosts based on 64-bit Intel x86 processors  


 
 
Line 32: Line 33:
==== Serial number ====
==== Serial number ====


Open a command prompt (CMD) as Administrator.
The installer will automatically use the hostname (%COMPUTERNAME%) to identify itself in Device Configuration.
 
Create a file <code>.nsprobeid</code>&nbsp;containing the hostname of the target host.&nbsp; Pay special attention to the leading dot and abscence of any extension in&nbsp;the name of the file. This text inside the file will be&nbsp;used to identify the&nbsp;vSCOUT in NGS Device Configuration:
<pre>C:\> notepad&nbsp;%temp%\.nsprobeid</pre>
 
Content of the file:
<pre>HOSTNAME</pre>
 
Save and exit.
 


&nbsp;


==== Installation parameters ====
==== Installation parameters ====


Before we start, make a list of these installation depending&nbsp;parameters:
Before you&nbsp;start, obtain and make a list of these parameters:
 
&nbsp;


{| border="1" cellpadding="1" cellspacing="1" style="width: 800px;"
{| border="1" cellpadding="1" cellspacing="1" style="width: 800px;"
Line 78: Line 69:
|}
|}


(*) If the path includes spaces, be sure to enclose it in quotation marks.&nbsp; Make sure to respect Microsoft's path naming conventions"
(*) If the path includes spaces, be sure to enclose it in quotation marks.&nbsp; You also must respect Microsoft's path naming conventions.
 
(<sup>#</sup>) After setting these&nbsp;options and starting the agent, the MON_INF and MGMT_INF options in the nsagent_config.cfg file will be set automatically with the correct interface&nbsp;number and the NSCONFIG_MONITOR_IP and NSCONFIG_MGMT_IP options will no&nbsp;longer appear in the file.&nbsp; If the target host has only one network interface, both MON_INF and MGMT_INF will be set to 1.
 
=== &nbsp; ===
 
=== Installing vSCOUT using the EXE file&nbsp; ===
 
Download, save and checksum the EXE installation file to a directory on the host (suggested <code>C:\Temp</code>).&nbsp;
 
Run the folllowing command while substituting the correct values from Table 1:&nbsp;
<pre>C:\Temp>is-6110-336-vSCOUT-x64.exe /s /v/qn /v"INSTALLDIR=E:\Programs\NETSCOUT\vSCOUT NSHTTP_PORT=7080 NSHTTPS_PORT=7443 NSCONFIG_SERVER_IP=A.B.C.D NSCOMM_PORT=395 NSCONSOLE_PORT=7501 NSCONFIG_MONITOR_IP=E.F.G.H NSCONFIG_MGMT_IP=I.J.K.L NUM_CPUS=2 MEM_SIZE=2048 FWD_SRC_IP=M.N.O.P VSCOUT_MODE=lite" </pre>
 
After installation, the parameters listed in Table 1&nbsp;are stored in the <code><INSTALLDIR>\rtm\config\nsagent_config.cfg</code> file. You can edit this file and restart vSCOUT services to apply your changes.


The log file for vSCOUT installation using the EXE file is stored at the path&nbsp;<code>%TEMP%\vSCOUT.log</code>.&nbsp;&nbsp;
(<sup>#</sup>) After setting these&nbsp;options and starting the agent, the MON_INF and MGMT_INF options in the nsagent_config.cfg file will be set automatically with the correct interface&nbsp;number and the NSCONFIG_MONITOR_IP and NSCONFIG_MGMT_IP options may&nbsp;no&nbsp;longer be present in the configuration file.&nbsp; Consider this a machanism to automatically the interface number from the Windows registry.


&nbsp;
&nbsp;
Line 106: Line 84:
<pre>msiexec /i is-6110-336-vSCOUT-x64.msi /qn INSTALLDIR=E:\Programs\NETSCOUT\vSCOUT NSHTTP_PORT=7080 NSHTTPS_PORT=7443 NSCONFIG_SERVER_IP=A.B.C.D NSCOMM_PORT=395 NSCONSOLE_PORT=7501 NSCONFIG_MONITOR_IP=E.F.G.H NSCONFIG_MGMT_IP=I.J.K.L NUM_CPUS=2 MEM_SIZE=2048 FWD_SRC_IP=M.N.O.P VSCOUT_MODE=lite</pre>
<pre>msiexec /i is-6110-336-vSCOUT-x64.msi /qn INSTALLDIR=E:\Programs\NETSCOUT\vSCOUT NSHTTP_PORT=7080 NSHTTPS_PORT=7443 NSCONFIG_SERVER_IP=A.B.C.D NSCOMM_PORT=395 NSCONSOLE_PORT=7501 NSCONFIG_MONITOR_IP=E.F.G.H NSCONFIG_MGMT_IP=I.J.K.L NUM_CPUS=2 MEM_SIZE=2048 FWD_SRC_IP=M.N.O.P VSCOUT_MODE=lite</pre>


After installation, the parameters listed in Table 1 are stored in the <code><INSTALLDIR>\rtm\config\nsagent_config.cfg</code> file.&nbsp; You can edit this file and restart vSCOUT services to apply your changes.
After installation, the parameters listed in Table 1 are stored in the <code><INSTALLDIR>\rtm\config\nsagent_config.cfg</code> file.&nbsp; You can edit this file and restart vSCOUT services to apply changes.


The log file for vSCOUT installation using the MSI&nbsp;file is stored at the path&nbsp;<code>%TEMP%\MSI???.log</code>.&nbsp;&nbsp;
The log file for vSCOUT installation using the MSI&nbsp;file is stored at the path&nbsp;<code>%TEMP%\MSI???.log</code>.&nbsp;&nbsp;
Line 114: Line 92:
=== Removing vSCOUT from Windows ===
=== Removing vSCOUT from Windows ===


vSCOUT, vSTREAM Embedded and vSTREAM Agent are completely different products with different capabilities and different licenses.&nbsp; Before moving to vSTREAM Embedded or vSTREAM Agent, vSCOUT must be removed entirely.
vSCOUT, vSTREAM Embedded and vSTREAM Agent are completely different products with different capabilities and different license requirements.&nbsp; Before moving to vSTREAM Embedded or vSTREAM Agent, vSCOUT must be removed entirely.


To [[Removing_vSCOUT_vSTREAM_Embedded_and_vSTREAM_Agent|remove vSCOUT from Windows]], please read the article.
To [[Removing_vSCOUT_vSTREAM_Embedded_and_vSTREAM_Agent|remove vSCOUT from Windows]], please read the article.

Revision as of 07:51, 20 July 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 to forward packets encapsulated in GRE or UDP to a InfiniStreamNG.  vSCOUT consumes signifiantly less CPU time when in lite mode than when in standard mode.

The procedure below requires the use of a MSI installer transformed by COMCERT and is only available to COMCERT customers with an active support contract.  This installer overcomes a few installation limitations and problems with the NETSCOUT provided installer.

Please read the article on vSCOUT resource usage before you start.

This article assumes familiarity with Windows Server OS.

 

Solution

Supported Operating Systems

  • Windows Server 2008 R2 SP1
  • Windows Server 2012 R2 (minimum of R2 required regardless of SP level)
  • Windows Server 2016
  • Windows Server 2019 (not officially supported by NETSCOUT)

 

Supported Hardware

  • vSCOUT is supported on virtual and physical hosts based on 64-bit Intel x86 processors

 

Before you begin

Serial number

The installer will automatically use the hostname (%COMPUTERNAME%) to identify itself in Device Configuration.

 

Installation parameters

Before you start, obtain and make a list of these parameters:

Table 1
Parameter Description Initial Value
INSTALLDIR* Specifies the path for vSCOUT installation E:\Programs\NETSCOUT\VSCOUT
NSCONFIG_SERVER_IP nGeniusONE Server Address A.B.C.D
NSCONFIG_MONITOR_IP# Specifies the network interfaces to be monitored by vSCOUT by IP address or subnet E.F.G.H
NSCONFIG_MGMT_IP# Specifies the network interface to be used for
communications with the managing nGeniusONE server either by IP address or subnet 		I.J.K.L
FWD_SRC_IP Specifies the IP address of the interface from which vSCOUT forwards traffic (tunnel) M.N.O.P

(*) If the path includes spaces, be sure to enclose it in quotation marks.  You also must respect Microsoft's path naming conventions.

(#) After setting these options and starting the agent, the MON_INF and MGMT_INF options in the nsagent_config.cfg file will be set automatically with the correct interface number and the NSCONFIG_MONITOR_IP and NSCONFIG_MGMT_IP options may no longer be present in the configuration file.  Consider this a machanism to automatically the interface number from the Windows registry.

 

Installing vSCOUT using the MSI file 

Download, save and checksum the MSI installation file to a directory on the host (suggested C:\Temp). 

Before you can install vSCOUT using the MSI installer, you must download and install the Microsoft Visual C++ Redistributable 2015 (64-bit). 

Run the folllowing command while substituting the correct values from Table 1:  

msiexec /i is-6110-336-vSCOUT-x64.msi /qn INSTALLDIR=E:\Programs\NETSCOUT\vSCOUT NSHTTP_PORT=7080 NSHTTPS_PORT=7443 NSCONFIG_SERVER_IP=A.B.C.D NSCOMM_PORT=395 NSCONSOLE_PORT=7501 NSCONFIG_MONITOR_IP=E.F.G.H NSCONFIG_MGMT_IP=I.J.K.L NUM_CPUS=2 MEM_SIZE=2048 FWD_SRC_IP=M.N.O.P VSCOUT_MODE=lite

After installation, the parameters listed in Table 1 are stored in the <INSTALLDIR>\rtm\config\nsagent_config.cfg file.  You can edit this file and restart vSCOUT services to apply changes.

The log file for vSCOUT installation using the MSI file is stored at the path %TEMP%\MSI???.log.  

 

Removing vSCOUT from Windows

vSCOUT, vSTREAM Embedded and vSTREAM Agent are completely different products with different capabilities and different license requirements.  Before moving to vSTREAM Embedded or vSTREAM Agent, vSCOUT must be removed entirely.

To remove vSCOUT from Windows, please read the article.

Retrieved from "https://wiki.comcert.com/index.php?title=Simplified_installation_of_vSCOUT_on_Windows&oldid=6238"