Prognosis on Linux

[NE-Prognosis]

Hello Team,

Can any on pelease provide the requirements and installation procedure (setp-by- step) of prognosis on linux platform. I found in support portal which are not clear.

Regards,

Phani

[Khoa_Ngo]

Hello NE Team, 

I agree that the hardware requirements section in regards to LINUX could be much more informational. However, as long as you meet Redhat's minimum specification and the prescribed disk space recommended in the product guide (1 GB) you should not run into any issues. 

[SCOTT_BALDWIN]

Hello Phani,

Installing Prognosis on a Unix/Linux platform is used for monitoring the Unix/Linux server and potentially the Payments application(s) running on the server. This type of installation is used with Prognosis for Payments and Infrastructure monitoring.

In a Prognosis for Payments and Infrastructure environment a Windows server is still needed for the Managing Node and Prognosis Web UI functions. Additional Prognosis Licensing is also needed to enable this type of deployment. The Account Manager will likely need to be contacted for the additional Licensing.

Support for a Linux based Prognosis Managing Node or Web UI is not available at this time.

For information on installing Prognosis on a Unix/Linux server, please see the following Prognosis Online Help links:

• Deployment - Prognosis for Infrastructure
• Prognosis Server on UNIX/Linux

Thank you,

Scott Baldwin

[Venkatesh]

Hello Scott/Team,

Does prognosis support Unified Communications monitoring in LINUX platforms ?

Thanks,

Venkatesh

[ChristopherS]

@Venkatesh  Your question about Unified Communications on Linux should both be A LOT more specific as we have a lot of different Unified Communication platofrms we monitor and be in a completely different thread.

Installing on a supported Redhat Linux or RHEL variant (i.e. CentOS) is extremely straight forward and the installation script prompts you through most of the installation. What you have to do is captured in our documentation to get the files to the system either using our utility or just moving the files manually to a staging directory.. and then to initiate the prompting. The prompting literally gives you step-by-step instructions.. and provide an alternative method of breaking it up into 3 different steps. 

As Scott Baldwin mentioned.. their is no Linux based client or Linux based webui.. but you can (and we have customers that do) use a Linux node as an intermeditate managing node between your monitoring node and your windows managing node for a tiered approach. You just need to remotely manage it from the top level node or connect directly with IRGUI to that node.

This is the high level requirements I give my Payments and Infrastructure customers on pre-reqs for ANY Linux system no matter its role.. then we scale it up from there.

• Linux (i.e. RedHat) / AIX Monitoring Node
  • 4 Gigs of Memory Minimum generally available for Prognosis to utilize.
  • Minimum 2 gigs of space on installation drive
  • Minimum 10 gigs of space on an alternative drive.
  • A separate user and group for Prognosis to run as, certain components of installation and patching require root access. The username must be under 8 characters long.

• Example user PRGN in group PRGN.

• Authentication
  • Linux/AIX Local, LDAP/LDAPS
  • Contact IR Services team if you utilize another authentication tool/method integrated with your system such as something that invokes multi-factor authentication and additional challenges at the Unix level.
• Ports:
  • Port 1960 to intermediate managing node and potentially other monitoring nodes. (bi-directional)
  • Ports to Email Server (25)  and any third party dispatching system (including SNMP traps out 161/162) – (out)
• Must have the following completed before beginning.
  • A separate user created for Prognosis to run as (as noted above)
  • yum install libstdc++.i686 compat-libstdc++-33.i686