Custom internal communication: Difference between revisions
No edit summary |
No edit summary |
||
(6 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
== Introduction == | == Introduction == | ||
This procedure describes how to configure an alternative communication path between the nGeniusONE server and the | This procedure describes how to configure an alternative communication path between the nGeniusONE server and the InfiniStream. This procedure can also be used for vStream. | ||
| | ||
Line 20: | Line 20: | ||
Step 2: | Step 2: | ||
Drill a hole into the local firewall that is running on the InfiniStream. There are many different ways to accomplish this task. The below suggestion is a 'quick and dirty' one but it works | Drill a hole into the local firewall that is running on the InfiniStream. There are many different ways to accomplish this task. The below suggestion is a 'quick and dirty' one but it works well. Insert the following line in the iptables configuration file, just before the REJECT rule. Port TCP/7443 is the custom port that we are using | ||
<pre># vi /etc/sysconfig/iptables</pre> | <pre># vi /etc/sysconfig/iptables</pre> | ||
Line 39: | Line 39: | ||
#Launch module "Device Configuration" | #Launch module "Device Configuration" | ||
#Select the corresponding InfiniStream | |||
#Change Communication Protocol to 'HTTPS' | #Change Communication Protocol to 'HTTPS' | ||
#Change HTTP/HTTPS Port to '7443' | #Change HTTP/HTTPS Port to '7443' | ||
| |||
Step 5: | Step 5: | ||
Log into the nGeniusONE server using ssh and alter the serverprivate.properties and append the following line: | |||
| | ||
device.<InfiniStream_IP_address>.procman.port=7443 | |||
This approach gives the flexibility to use different TCP ports amongst the various InfiniStreams that are part of the distributed environment. | |||
| | ||
In case the use of this particular custom port is required for every InfiniStream please use the following line: | |||
BaseEngineManager.ssl.port=7443 | |||
<pre># cd /opt/NetScout/rtm/bin | |||
# vi serverprivate.properties</pre> | |||
| | ||
Step 6: | |||
Reboot both the InfiniStream and nGO server and relearn the InfiniStream using the module Device Confiugaration. | |||
| |
Latest revision as of 11:26, 29 October 2019
Introduction
This procedure describes how to configure an alternative communication path between the nGeniusONE server and the InfiniStream. This procedure can also be used for vStream.
Procedure
Step 1:
Log into the nGeniusONE server and stop all nGenius processes
# cd /opt/NetScout/rtm/bin # ./stop
Log into the InfiniStream and stop all nGenius processes
# isbin # ./stopall
Step 2:
Drill a hole into the local firewall that is running on the InfiniStream. There are many different ways to accomplish this task. The below suggestion is a 'quick and dirty' one but it works well. Insert the following line in the iptables configuration file, just before the REJECT rule. Port TCP/7443 is the custom port that we are using
# vi /etc/sysconfig/iptables
-A INPUT -p tcp -m state --state NEW -m tcp --dport 7443 -j ACCEPT
# service iptables restart
Step 3:
Log into the InfiniStream and alter the 'NSPROCPORT_SECURED' directive.
# isbin # vi procmanager.env
NSPROCPORT_SECURED=7443
Step 4:
Log into nGeniusONE server using the web browser.
- Launch module "Device Configuration"
- Select the corresponding InfiniStream
- Change Communication Protocol to 'HTTPS'
- Change HTTP/HTTPS Port to '7443'
Step 5:
Log into the nGeniusONE server using ssh and alter the serverprivate.properties and append the following line:
device.<InfiniStream_IP_address>.procman.port=7443
This approach gives the flexibility to use different TCP ports amongst the various InfiniStreams that are part of the distributed environment.
In case the use of this particular custom port is required for every InfiniStream please use the following line:
BaseEngineManager.ssl.port=7443
# cd /opt/NetScout/rtm/bin # vi serverprivate.properties
Step 6:
Reboot both the InfiniStream and nGO server and relearn the InfiniStream using the module Device Confiugaration.