Prognosis IPTM and IPTMR 9 6 1 Pre-Requisites v1.0 - 2011 - 09 - 27 - Cisco

Pre-Requisites Checklist for
Cisco
Prognosis IP Telephony Manager 9.6.1
with Prognosis Path Insight
Prognosis IP Telephony Management Reporter 9.6.1
Date published
Friday, November 18, 2011
Version
1.0
Integrated Research Consulting Services
Integrated Research – The people behind PROGNOSIS www.prognosis.com
Americas Europe/UK Germany Asia Pacific/M.East/Africa

t: +1 (303) 390 8700 t: +44 (0) 1344 894 200 t: +49 (69) 710 455 255 t: +61 (2) 9966 1066
f: +1 (303) 390 8777 f: +44 (0) 1344 890 851 f: +49 (69) 710 455 450 f: +61 (2) 9966 1042
e: info.usa@prognosis.com e: info.europe@prognosis.com e: info.germany@prognosis.com e: info.ap@prognosis.com
Table of contents
1 Revision History ......................................................................................................................................................................... 3

2 Introduction............................................................................................................................................................................... 4
3 Scope ......................................................................................................................................................................................... 5
4 Prognosis IPTM Platform Pre-Requisites ................................................................................................................................... 6
4.1 Cisco Unified Communications Manager 5.x, 6.x, 7.x & 8.x .....................................................................................................................6
5 Prognosis Network Diagnostics Pre-Requisites ....................................................................................................................... 11
6 Prognosis Deployment Architecture Example ......................................................................................................................... 13
7 Bandwidth Requirement ......................................................................................................................................................... 14
8 Prognosis IPTMR Pre-Requisites: ............................................................................................................................................. 15
8.1 Supported Platforms .............................................................................................................................................................................15
9 PROGNOSIS Server/ GUI Specifications ................................................................................................................................... 17
9.1 Management and 3rd Party Nodes .......................................................................................................................................................17
9.2 Monitoring Nodes .................................................................................................................................................................................18
9.3 IPTMR Reporter Server ..........................................................................................................................................................................19
9.4 Prognosis IPTM GUI ...............................................................................................................................................................................21
9.5 Prognosis IPTMR GUI.............................................................................................................................................................................22
10 Summary ............................................................................................................................................................................. 23
Integrated Research – The people behind PROGNOSIS www.prognosis.com
Americas Europe/UK Germany Asia Pacific/M.East/Africa

t: +1 (303) 390 8700 t: +44 (0) 1344 894 200 t: +49 (69) 710 455 255 t: +61 (2) 9966 1066
f: +1 (303) 390 8777 f: +44 (0) 1344 890 851 f: +49 (69) 710 455 450 f: +61 (2) 9966 1042
e: info.usa@prognosis.com e: info.europe@prognosis.com e: info.germany@prognosis.com e: info.ap@prognosis.com
Integrated Research Pre-Requisites Checklist
1 Revision History
Document control: \\ir-file-srv\ir-work\Consulting\IPTM\Prerequisites
Prior to Prognosis 9.6.1:
Version Date Author Comments
1.0 Thomas Pilz Initial draft per vendor
Draft 21.10.2011
Page 3 of 23
2 Introduction
Prior to a Prognosis solutions consultant being dispatched to site to carry out an installation of the
Prognosis IP Telephony Manager and Prognosis IP Telephony Management Reporter product range, it is
imperative that a set of pre-requisites are met and confirmed to be in place before the installation date.
This will assist in the smooth implementation of Prognosis and avoid potential delays to the project,
maximising the duration of the consultant’s allocated time. In light of this, a set of pre-requisites detailed
in this document should be met.
Included as part of this document is a specification recommendation for the managing/monitoring

servers, reporter server and GUI so that the correct hardware can be supplied for the installation.
Page 4 of 23
3 Scope
It is the scope of this document to detail the pre-requisites for Prognosis across the Cisco platform as
follows:
 CCM 3.x & CUCM 4.x – Based on the windows platform

 CUCM 5.x, 6.x, 7.x & 8.x – Based on the Cisco Linux appliance platform
It will also detail the minimum specification for servers/GUI for these platforms.
It is not within scope to detail how Prognosis works within each platforms technology.
Page 5 of 23
4 Prognosis IPTM Platform Pre-Requisites

This area is broken down into 3 sections, one for each platform. Please note, the section for legacy Cisco
CCM3.x and CUCM4.x is put in Appendix A.
Each section is split into 2 sub sections. The first sub section requires information to be provided that will
help build a picture of the environment into which Prognosis will be deployed. This will also provide the
relevant information to create the correct licenses and estimate the amount of days required to carry
out the implementation. The second sub section lists the requirements that must be implemented and
understood to ensure the installation is successful.
NOTE: If any of the following pre-requisites are not met, it will lead to a delay in the implementation,
which will ultimately increase the amount of days required of a Prognosis consultant and customer
representative for implementation.
4.1 Cisco Unified Communications Manager 5.x, 6.x, 7.x & 8.x
4.1.1 Overview
CUCM 5.x, 6.x, 7.x and 8.x are Linux based appliances. As a consequence, a Prognosis agent cannot be
installed directly onto the appliance which leads to a different information gathering mechanism to CCM
3.x & CUCM 4.x. Prognosis is installed only onto the Monitoring node, unity and other servers in the
environment. Prognosis will poll the publishers and subscribers and communicate with Unity/Other
servers via the installed agents. This results in a different set of pre-requisites to CCM 3.x & CUCM 4.x.
Provide the following information by entering the details in the column provided:
# Question Response
1 Version of Cisco Unified Communication Manager
2 Number and type of phones
 Hard
 Soft
 Analogue
3 Number and type/version of gateways:
 MGCP
 H323
4 Number of:
Publishers
Subscribers
Unity Connection Servers
Cisco Express routers
Other servers i.e. Exchange, MOH, TFTP etc.
Cisco CTS Telepresence Units
Please detail other servers:
Page 6 of 23
5 Please detail the cluster servers and its location i.e. are
they on site where we are visiting?
6 Will installation be carried out onsite where servers are
located or remotely?
7 Will Prognosis be installed onto a standalone server or
onto VMware?
8 Is it a live or lab environment?
9 What is important for each customer in IPT i.e. QoS, call
reporting, capacity planning etc.?
10 Full list of servers that IPTM is to be installed onto, to
include hostnames and IP addresses and locations
11 Do you have an application that takes the CDRs from
CUCM?
12 Administrator user name and password for IPTM to access
cluster data
13 What is the call volume for each call manager?
14 What is the average call duration?
15 How long do you require to keep the historical data?
16 Will historical data be stored on the monitoring server or
over a SAN
17 Do you have Unity Connection?
18 Do you have Cisco Unity Express (CUE)?
19 Do you have SRST routers?
20 Do you have CUCME?
4.1.2 Pre-requisites
Confirm that the following pre-requisites have been met by typing “complete” and date it was
completed into the completed column:
# Pre-Requisite Completed & Date

1 Is there a change management process to be followed
prior to a site visit and the installation of Prognosis?
If so, it must be in place and completed before a
Prognosis consultant visits the site.
2 Setup the following parameters within CUCM (Cisco
Unified Communications Manager) Administration
Console.
• Activate Call Manager Service
• Set the SNMP Community String
• Set CDR Disk Space
• Set the Performance Rate
• Enable CDRs for Voice Quality Data
• Enable Valid Namespaces
Page 7 of 23
a. Set the Billing Application Server (Prognosis user

name: PrognosisCDR, password: Prognosis_CDR)
b. Set the CDR Cluster Name
These two items to be carried out after IPTM is
installed.
Please refer to Installation Guide document for the

configuration details.
3 If CUCM administrator user name and password cannot
be used by Prognosis to access cluster data through AXL
web service, please create a new application user for
Prognosis in CUCM.

configuration detail.
4 Please provide application user name and password for

Prognosis to access cluster data through AXL web service.
5 Setup the following parameters within CUC (Cisco Unity
Connection) Administration Console.
• Run Network Services
• Set the SNMP Community String
• Set the Performance Rate

configuration detail.
6 IP connectivity is required from Prognosis monitoring
server as follows
• To Reporting server (IPTMR) over TCP 5999
• To Publisher and Subscriber over TCP 443
• To Publisher and Subscriber over TCP 8443
• To Publisher over UDP 161
• To IP phones over TCP 80
• To H.323/SIP gateways over UDP 161
• To Unity/other servers over TCP 1960
• From publisher to Prognosis Monitoring server over TCP
22
• For email alert via SMTP over TCP 25
• For web interface over TCP 80 or 8080
7 Firewalls opened and ACL’s configured to allow the
connectivity as detailed in the point above.
8 Ensure any gateways within the IPT network to be
monitored by Prognosis have been setup to allow for
SNMP polling.
SNMP traffic is enabled between CUCM, gateways and
IPTM monitoring server.
Page 8 of 23
Please note that if H323 gateway has a permission group

configured, Prognosis monitoring server IP address has to
be included in the permission group to enable the
gateway to respond to SNMP polling from Prognosis
monitoring server.
9 If the CUCM uses SNMP V1/V2c, the same community
string needs to exist on all nodes in the cluster, if not, it
needs to be added on each node. (and the community
string name MUST match the SNMP Entry Name in the
IPTM PASSWORD Configuration).
If the CUCM uses SNMP V3, the same user must exist on
all nodes in the cluster. If it does not, it needs to be added
to each node.
The user needs to have same authentication protocol and
encryption protocol (and the user name, authentication
protocol, authentication password, encryption protocol
and
encryption password must match the SNMP Entry Names
in the IPTM PASSWORD Configuration and the profile in
the Cluster Static Configuration).
Please refer to Installation Guide document page177 for

configuration details.
10 CDR enabled flag is set to true, Call Diagnostics enabled
value is set to “Enable Only When CDR Enabled Flag is
True” and calls with zero duration set to true throughout
cluster.
11 Please provide SNMP community string for the cluster.
 SNMPv1/v2c community string:

or
 SNMPv3 Username:
 SNMPv3 Authentication protocol: MD5/SHA
 SNMPv3 Password for Authentication:
 SNMPv3 Encryption Required: Yes/No
SNMPv3 password for encryption:
12 Availability of personnel who have full admin rights on the
IPT environment for the duration of the implementation
13 Network Diagram showing CUCM environment
14 Internet access for Prognosis engineers to create a VPN
connection to company network.
15 Physical full access or remote access to Prognosis server is
available to the Prognosis consultant.
If physical (console) access is supplied, a single keyboard,
mouse, and monitor must be provided.
If remote access is supplied, at least 2 (two) computers
Page 9 of 23
with remote desktop connectivity to Prognosis server are

required.
16 Please provide the hostname, IP address, connection
mode (Telnet/SSH) and login ID/password of CUCME, CUE,
SRST, Unity Connection (if applicable)
Tips to check the credentials, services and configurations:
1. Putty to Publisher and Subscriber to verify the login ID and password provided
2. Check the web service connectivity to Publisher and Subscriber by using e.g.
https://10.39.38.11:443/perfmonservice/services/PerfmonPort to verify the login ID and
password provided
3. Check the community string from Cisco Unified Call Manager Administration > Cisco Unified
Call Manager Serviceability > SNMP Community String Configuration
Page 10 of 23
5 Prognosis Network Diagnostics Pre-Requisites

Overview
Prognosis Network Diagnostics is a VoIP Ecosystem Management tool for Cisco. It supports the following
Cisco platforms:
Product Versions/Models
Cisco Unified Communications
Manager 5, 6 and 7
Cisco Unified CallManager 4

Cisco CallManager 3.3
Provide the following information by entering the details in the column provided:
# Question Response
1 Version of Cisco platform
Pre-requisites:
completed into the completed column

1 Does your Prognosis IP Telephony Manager license
include Network Diagnostics add-in? Is the license
available?
2 Java Applet setting:
Is the 'Use JRE for <applet> (requires restart)' option

enabled in the Internet Options dialog of your Web
browser?
To check the setting:
 Step1: On the IP Telephony Manager GUI

machine, open the Windows Control Panel;
 Step2: Click on Internet Options;
 Step3: On the Internet Properties dialog box
select the Advanced Tab and then scroll down to
the Java (Sun) section;
 Step4: Check that the 'Use JRE for <applet>
Page 11 of 23
(requires restart)' option is enabled (box

checked). If it is not, check the adjacent box;
Step5: When finished select the OK button and then
restart the machine.
3 Do you have available Community Strings for the nodes in
your network? What are the Community strings for SNMP
request?
These credentials are used by Network Diagnostics to

make SNMP requests which are needed to classify and
monitor nodes in the network, and need to be setup and
stored in the IP Telephony Manager PASSWORDS
Configuration
Tips:
1. In order to use Network Diagnostics, you will need to ensure that when adding a PBX/Cluster,
customer and site fields have been entered and not left blank.
2. The PASSWORDS configuration setup for SNMP community strings is in addition to any that may
have been previously done for Cisco monitoring.
3. As of IPTM patch 6, there is a bug in which Avaya customers will have to enter their community
strings into the PASSWORDS Configuration without the customer and site fields.
Snmpv2c:<customer_name>:<site_name>:<password_number>
should be entered as:
Snmpv2c:::<password_number>
4. The recommended resolution for Prognosis GUI is increased for Network Diagnostics from
1024x768 to 1260x1024 due to the map displays in Network Diagnostics.
Page 12 of 23
6 Prognosis Deployment Architecture Example
Figure 1. Generic Prognosis Deployment Example
Note:
This is a generic deployment, it does not take redundant Prognosis servers into consideration.
Page 13 of 23
7 Bandwidth Requirement
To minimize IP Telephony Manager bandwidth usage on the WAN it is recommended to position an IP
Telephony Manager Monitoring Server close to (i.e. in the same LAN) the device group being monitored.
The following table contains indicative bandwidth requirements for Prognosis “Monitoring Traffic”
Phone Count User Erlang Value Indicative Bandwidth Mb/s

2000 0.17 2.0
5000 0.17 3.5
30000 0.17 12.0
There is one factor that impacts on scalability of the Monitoring Server in a CUCM 5+ environment - the
BHCA (Busy Hour Call Attempts) across all CUCM 5+ clusters.
To calculate the minimum bandwidth required and recommended bandwidth in monitoring Cisco
environment, please answer the following questions:
No Question Answer
1 How many MGCP BRI devices?
2 How many MGCP FXO devices?
3 How many MGCP FXS devices? (Includes VG224 MGCP FXS devices)
4 How many MGCP PRI devices?
5 How many MGCP T1 CAS devices?
6 How many SIP devices (trunks+gateways)?
7 How many H.323 gateways?
8 How many H.323 devices, excluding gateways? (Includes phones, trunks & ATA ports)
9 How many Locations configured?
10 How many phones (Cisco IP phones + VG ports + ATAs)?
11 How many extensions/DNs?
12 How many phones are sharing extensions?
13 How many Route Patterns?
14 Are you planning to open the IPTM Server Central display?
15 How many servers are in each Call Manager Group?
16 Are you planning on collecting HP Hardware MIB information?
17 What performance profile will you use? (see below Profile table)
18 Total number of Subscribers in this cluster?
19 What is the mean call duration (in seconds) for this cluster?
20 What is the Subscriber/User Erlang figure for this cluster?
Performance Profiles for monitoring CUCM 5+ clusters - used to determine the collection periods used by the data
collectors:
Profile High Medium Low Minimal
Polling Interval
30 60 120 300
(Sec)
Page 14 of 23
8 Prognosis IPTMR Pre-Requisites:
8.1 Supported Platforms

Supported Platforms
Management Reporter provides reporting functionality for the following IP telephony systems:
• Cisco Unified CallManager 4

• Cisco Unified Communications Manager 5, 6, 7 and 8
completed into the completed column

1 Is a server ready and available with the recommended
system requirements?
2 Is the server configured with all prerequisite software
requirements?
 Microsoft Word 2003/2007 or Microsoft Office

2003/2007
 Microsoft .Net Framework v2.0
 Microsoft Windows Installer 3.1
 Microsoft SQL Server 2000/2005, SQL Server 2005
Express
 SMTP Server
3 Microsoft SQL Database:
 TCP/IP protocols need to be enabled prior to the

installation of Prognosis IP Telephony
Management Reporter in order for it to use the
SQL database.
The SQL Server Browser is needed and must be enabled

and running.
4 The database should be able to accept SQL authenticated
logins ('mixed' authentication mode).
5 If using a remote database, an SQL authenticated user
login should be created with specific rights. See
Management Reporter Installation Guide page 29 for
details.
Page 15 of 23
6 Any anti-virus program on the reporter server machine

should allow outgoing emails on port 25 if email
distribution of reports and/or error alerting via email is
required.
7 IP connectivity is required from Prognosis Management
Reporter server as follows:
• To Prognosis managing server or monitoring server
over TCP 1960
Any firewalls should allow internal TCP traffic on the

nominated Reporting Server and Logger ports.
Additionally, two TCP ports must be used for

communication between the Reporting Server and
remote Reporting GUIs. These ports can be chosen on a
per remote GUI basis.
8 The SMTP mail server must be configured to allow
outgoing emails from the server machine if email
distribution of reports and/or error alerting via email is
required.
9 It is recommended that a dedicated machine be set up to
run Management Reporter.
Page 16 of 23
9 PROGNOSIS Server/ GUI Specifications

In order for Prognosis to operate satisfactorily the monitoring, managing and reporting servers should be
built to the minimum specification. The following sections provide the minimum hardware and VMWare
specifications for both Prognosis IP Telephony Manager 9.6.1 and Prognosis IP Telephony Management
Reporter 9.6.1.
9.1 Management and 3rd Party Nodes
9.1.1 Minimum IPTM Server Specifications - Hardware

Component Version/ Size
Processor (CPU): 2.4 GHz Intel Pentium® Dual-Core Processor
System Memory (RAM): 8Gb
Hard Drive Space (NTFS): 250Gb
Microsoft Windows® 7 32/64-bit*
Microsoft Windows 2008 R2
Microsoft Windows Server® 2008 - 32/64-bit*
Microsoft Windows XP 32 (SP2)/64-bit*
Operating System:
Microsoft Windows Server 2003 (SP1) - 32 bit only
Microsoft Windows 2000 (SP4)
*PROGNOSIS will run as 32 bit application on 64 bit versions of Windows;
however, if you choose to install on 64 bit Windows please do not install
PROGNOSIS under the standard "C:\Program Files (x86)" directory.
Network 1GB network adaptor
9.1.2 Minimum IPTM Server Specifications - VMWare

Processor (CPU): 6.2Ghz across 2 vCPUs
Operating System: Microsoft Windows Server 2003 (SP1) - 32 bit only
Network 1GB virtual network adaptor
Page 17 of 23
9.2 Monitoring Nodes

Processor (CPU): 2.4 GHz Intel Pentium® Dual-Core Processor
Operating System:
Microsoft Windows Server 2003 (SP1) - 32 bit only
Network 2x 1GB network adaptor

Processor (CPU): 12.4GHz across at least 4 vCPUs
The Reporting Server component is to collect data from the Cisco environment via the monitoring
servers and publish capacity planning, troubleshooting, SLA and analytical style reports. The reports are
generated and stored on the reporter server.
Page 18 of 23
9.2.3 Pre-Requisites
1 Is a server ready and available with the recommended
system requirements?
2 Ensure the SNMP service is installed and running on the
Management node?
3 IP connectivity is required from Prognosis managing
server as follows:
• To all Prognosis monitoring nodes and monitored
servers running Prognosis locally over TCP 1960
Access to TCP port 1960 on any Prognosis managing node

is required from all workstations running the Prognosis
GUI to allow GUI connections.
9.3 IPTMR Reporter Server

Processor (CPU): Intel Pentium® Dual-Core 2.4 GHz Processor
Required Applications: Microsoft Word 2003/2007 or Microsoft Office
2003/2007+
Microsoft .Net Framework v2.0++
Microsoft Windows Installer 3.1++
Prognosis IP Telephony Manager 9.6.1+++
Microsoft SQL Server 2000/2005, SQL Server 2005
Express
SMTP Server*
Page 19 of 23

Processor (CPU): 12.4GHz across at least 4 vCPUs
Required Applications: Microsoft Word 2003/2007 or Microsoft Office
2003/2007+
Microsoft .Net Framework v2.0++
Prognosis IP Telephony Manager 9.6.1+++
Microsoft SQL Server 2000/2005, SQL Server 2005
Express
SMTP Server*
+
Ensure that no other versions or Word or Office are installed.
++
The installation will detect if this software is not present and will install it from the CD after prompting for permission. If
necessary, Windows Installer 3.1 will also be installed from the CD, however this will require a system reboot.
+++
See the previous section on Managing Server pre-requisites for more detail.
*
Access to an SMTP Mail Server (e.g. MS Exchange) is required if email distribution of reports and/or error alerting via
email is required. The SMTP server does not need to be on the same machine.
Page 20 of 23
9.4 Prognosis IPTM GUI

The GUI is the interface that operators use to view monitored data, action alerts and configure
Prognosis. The GUI may be installed on the Prognosis Management Node or by itself on a separate
machine. A copy of the GUI must be installed somewhere in the monitoring environment in order to
view data. If installed on a separate server to the Prognosis Managing Node, there is no requirement that
this server be dedicated to the Prognosis GUI. The minimum specification for a server that is hosting a
Prognosis GUI is as follows:

Processor (CPU): Intel Pentium® IV
Hard Drive Space (NTFS): 800Mb
Microsoft .Net V2.0
Required Applications
++
If necessary, Windows Installer 3.1 will be installed from the CD. However, this will
require a machine reboot.
Page 21 of 23
9.5 Prognosis IPTMR GUI

The Prognosis IP Telephony Management Reporter GUI is the user interface through which reports can
be configured, scheduled and generated. The GUI will be installed automatically with the Reporting
Server. However, it is also possible to install the GUI separately, i.e. without the reporting server, onto
other machines if required. These other machines do not need to be stand-alone. Multiple client GUIs
may interact with the same Management Reporter Server. The minimum specification for a client
machine to host the GUI is as follows:

Processor (CPU): Intel Pentium® 500Mhz
Hard Drive Space (NTFS): 50Mb
Microsoft .Net V2.0
Required Applications
++
If necessary, Windows Installer 3.1 will be installed from the CD. However, this will
require a machine reboot.
Page 22 of 23
10 Summary
The applicable section for your IP Telephony environment should be checked and all relevant
information requested sent back to the Prognosis engineer/account manager at least 1 week before the
agreed installation date. This will confirm everything is in place and ready.
Page 23 of 23

Prognosis IPTM and IPTMR 9 6 1 Pre-Requisites v1.0 - 2011 - 09 - 27 - Cisco

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Prognosis IPTM and IPTMR 9 6 1 Pre-Requisites v1.0 - 2011 - 09 - 27 - Cisco

Încărcat de

Drepturi de autor:

Formate disponibile

Pre-Requisites Checklist for

Prognosis IP Telephony Management Reporter 9.6.1

Integrated Research Consulting Services

Integrated Research – The people behind PROGNOSIS www.prognosis.com

Americas Europe/UK Germany Asia Pacific/M.East/Africa

1 Revision History ......................................................................................................................................................................... 3

Integrated Research – The people behind PROGNOSIS www.prognosis.com

Americas Europe/UK Germany Asia Pacific/M.East/Africa

Included as part of this document is a specification recommendation for the managing/monitoring

 CCM 3.x & CUCM 4.x – Based on the windows platform

4 Prognosis IPTM Platform Pre-Requisites

# Pre-Requisite Completed & Date

a. Set the Billing Application Server (Prognosis user

Please refer to Installation Guide document for the

Please refer to Installation Guide document for the

4 Please provide application user name and password for

Please refer to Installation Guide document for the

Please note that if H323 gateway has a permission group

Please refer to Installation Guide document page177 for

 SNMPv1/v2c community string:

with remote desktop connectivity to Prognosis server are

Tips to check the credentials, services and configurations:

5 Prognosis Network Diagnostics Pre-Requisites

Cisco Unified CallManager 4

# Pre-Requisite Completed & Date

Is the 'Use JRE for <applet> (requires restart)' option

To check the setting:

 Step1: On the IP Telephony Manager GUI

(requires restart)' option is enabled (box

These credentials are used by Network Diagnostics to

should be entered as:

6 Prognosis Deployment Architecture Example

Figure 1. Generic Prognosis Deployment Example

Phone Count User Erlang Value Indicative Bandwidth Mb/s

8 Prognosis IPTMR Pre-Requisites:

8.1 Supported Platforms

• Cisco Unified CallManager 4

# Pre-Requisite Completed & Date

 Microsoft Word 2003/2007 or Microsoft Office

 TCP/IP protocols need to be enabled prior to the

The SQL Server Browser is needed and must be enabled

6 Any anti-virus program on the reporter server machine

Any firewalls should allow internal TCP traffic on the

Additionally, two TCP ports must be used for

9 PROGNOSIS Server/ GUI Specifications

9.1 Management and 3rd Party Nodes

9.1.1 Minimum IPTM Server Specifications - Hardware

9.1.2 Minimum IPTM Server Specifications - VMWare

9.2 Monitoring Nodes

9.2.1 Minimum IPTM Server Specifications - Hardware

9.2.2 Minimum IPTM Server Specifications - VMWare

Access to TCP port 1960 on any Prognosis managing node

9.3 IPTMR Reporter Server

9.3.1 Minimum IPTM Server Specifications - Hardware

9.3.2 Minimum IPTM Server Specifications - VMWare

9.4 Prognosis IPTM GUI

Component Version/ Size

9.5 Prognosis IPTMR GUI

Component Version/ Size

S-ar putea să vă placă și