[Infrastructure Monitor] Configure Static RPC/WMI TCP ports for Infrastructure Monitor

[Infrastructure Monitor] Configure Static RPC/WMI TCP ports for Infrastructure Monitor

  
Forge Component
(18)
Published on 8 Aug (13 days ago) by Duarte Santos
18 votes
Published on 8 Aug (13 days ago) by Duarte Santos

Introduction

Inframon gathers performance information via RPC/WMI. 

By default the reply from the servers back to Inframon occurs on random high tcp ports (>1024) which would require an almost open network path.

This document helps setting up the reply tcp ports to a smaller range.

Requirements

  • Administrator access to the OutSystems servers

  • At the end of the configuration a server reboot is required

Setup

The setup consists of:

  1. Select a tcp port range

    1. For this document we will use 5900 - 6000

  2. Registry entries

Select Port Range

A communication tcp port range must be agreed with the network team / administrator.

It is not advisable to have a shot tcp range, since RPC is used for many other things in the Windows.

After the tcp port range is agreed, the network team configures the firewalls for the following communication:

Lifetime Server > TCP Port 135 > OutSystems Servers

Outsystems Servers < TCP Port 5900 - 6000 < Lifetime Server

Below is a screenshot of a communication report via the command line “netstat -a”

Registry Entries

Based on this Microsoft KB.

  1. Open regedit on the Outsystems Server

  2. Go to the following registry location HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc

  3. Add the Internet key under the location above

  4. Inside the Internet key create the following values:

    1. Ports: REG_MULTI_SZ: 5900-6000

    2. PortsInternetAvailable: REG_SZ: Y

    3. UseInternetPorts: REG_SZ: Y