Verify the GRE/UDP tunnel between vSCOUT and vSTREAM: Difference between revisions
(Created page with " == Introduction == vSCOUT does not produce session detail records nor does it store packets . However, you can still gain access to session details and packet-level data by...") |
No edit summary |
||
| Line 10: | Line 10: | ||
== Solution == | == Solution == | ||
On NGeniusONE Server module Device Settings, write down the IP address of the interface that terminates the tunnel. | |||
| |||
=== On vSTREAM === | |||
Login to vSTREAM CLI (ssh) as root | Login to vSTREAM CLI (ssh) as root | ||
Type <pre>ip addr </pre>and note the interface that has the IP address from step 1</pre> | |||
Type ip addr and write down the name of the interface that has the IP address from step 1</pre> | |||
<pre>ip addr </pre> | |||
and note the interface that has the IP address from step 1</pre> | |||
| | ||
| | ||
Revision as of 09:36, 28 February 2018
Introduction
vSCOUT does not produce session detail records nor does it store packets . However, you can still gain access to session details and packet-level data by configuring traffic forwarding from vSCOUT to vSTREAM or InfiniStream interface managed by the same nGeniusONE server. Forwarded packets can be stripped out of the tunnel and made availabe for packet-level analysis on the receiving interface.
This procedure allows you to verify the existance of the tunnel i.e. packets being transported between vSCOUT and vSTREAM
Solution
On NGeniusONE Server module Device Settings, write down the IP address of the interface that terminates the tunnel.
On vSTREAM
Login to vSTREAM CLI (ssh) as root
Type ip addr and write down the name of the interface that has the IP address from step 1
ip addr
and note the interface that has the IP address from step 1