Installation

For a step by process on how the installation works please take a look at our Quick Start Guide.

Here is some additional configuration information:

 

Port Requirements

The Longitude Management Console requires network access for the protocols used for data collection. For example, Network Device collections require UDP access to SNMP (default port = 161), and Unix collections require access to SSH (default port = 22). WMI data collection from Windows computers requires RPC, which assigns a random, high numbered port to the WMI connection – as a result, firewalls often block RPC connections by default.

Any applications which require a connection to a specified port will include the port number as part of the configuration information – see Application help for details on specific applications.

In addition to the ports needed for data collection, Longitude uses the following ports:

Port Use
7220 Statistics Server Component Port; if a Remote Agent is behind a firewall, this port will need to be opened to the Longitude Management Console.
7221 Consolidator Component on Longitude Management Console. External access not required.
7222 Engine Component on Longitude Management Console. External access not required.
7223 SSL communication from Management Console to Remote Agent statistics collection service.
7228 Longitude Web UI HTTP port.
7229 Upgrade Manager Component Port; if a Remote Agent is behind a firewall, this port will need to be opened to the Longitude Management Console
7238 Longitude Web UI HTTPS port.

 

Permissions

Longitude collects data without the need to install a Longitude agent on the monitored computers or network devices, but Longitude will require permission to connect to the devices it is monitoring. Please make sure you have the following information available before trying to monitor devices with Longitude:

Device Type Method Permissions Needed
Windows WMI Windows account with local Administrator
privileges on target device*
Unix/Linux SSH Unix user account with SSH connection privileges
Network Devices SNMP SNMP V1 Community string with read privileges

* Longitude is designed to operate in a Windows domain for the purpose of WMI data collection. If Longitude is installed in a workgroup, it will be able to collect WMI data only for the Longitude Management Console server itself. To collect WMI data for additional machines, see the Troubleshooting article “Longitude installed on a Workgroup computer”.

Some applications require further configuration – please refer to Application Help for further details.

 

License Types

Longitude has the following types of license units:

  • Base:
    One unit required per monitored device. Allows monitoring for Windows, WindowsEventLog, Unix, or NetworkDevice.
  • Layered Application:
    Allows use on a monitored device of predefined Longitude software
    application monitors, e.g. Exchange2010, SQL2012, IIS.
  • VMware CPU Sockets and Hyper-V CPU Sockets:
    The Longitude Virtualization application is licensed by the number of CPU sockets in either the VMware or Hyper-V environment. VMware socket licenses cannot be applied to the Hyper-V application, and Hyper-V socket licenses cannot be applied to the VMware application. Please contact Heroix Support (support@heroix.com) to convert between VMware and Hyper-V socket licenses.
  • Transaction:
    Transactions are connectivity tests for basic protocols, e.g. Ping, SSH, SMTP.