Required Ports for Prime Collaboration

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (Ports Used by Prime Collaboration Assurance Server, Devices, and Applications)
m (Ports Used by Prime Collaboration Assurance Server, Devices, and Applications)
Line 4: Line 4:
The following tables lists the required ports for the Cisco Prime Collaboration Assurance (PCA) to communicate with the devices and applications.<br>  
The following tables lists the required ports for the Cisco Prime Collaboration Assurance (PCA) to communicate with the devices and applications.<br>  
 +
 +
Note: SNMP v3 AuthPriv is not supported. <br>
{| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable"
{| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable"
Line 127: Line 129:
|-
|-
| rowspan="2" | Network Devices  
| rowspan="2" | Network Devices  
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 22:TCP<br>
 +
| To log into Medianet initiator CLI during troubleshooting process (SSH).<br>
 +
|-
| PCA<br>  
| PCA<br>  
| Network Devices<br>  
| Network Devices<br>  
| 23:TCP<br>  
| 23:TCP<br>  
-
| To initiate connection to Medianet devices during troubleshooting process (Telnet).<br>
+
| To log into Medianet initiator CLI during troubleshooting process (Telnet).<br>
|-
|-
| PCA<br>  
| PCA<br>  
| Network Devices<br>  
| Network Devices<br>  
| 80:TCP<br>  
| 80:TCP<br>  
-
| To initiate connection Medianet devices during troubleshooting process (HTTP). <br>
+
| To access Medianet initiator via WSMA during troubleshooting (HTTP). <br>
 +
|-
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 161:UDP<br>
 +
| To poll device and Medianet information (SNMP). <br>
 +
|-
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 443:TCP<br>
 +
| To access Medianet initiator via WSMA during troubleshooting (HTTPS).<br>
|-
|-
| rowspan="9" | Cisco Unified CM (CUCM)
| rowspan="9" | Cisco Unified CM (CUCM)

Revision as of 02:26, 17 March 2013

The following tables lists the required ports for the Cisco Prime Collaboration Assurance and Cisco Prime Collaboration Provisioning servers to communicate with the devices.

Contents

Ports Used by Prime Collaboration Assurance Server, Devices, and Applications

The following tables lists the required ports for the Cisco Prime Collaboration Assurance (PCA) to communicate with the devices and applications.

Note: SNMP v3 AuthPriv is not supported.

Devices/Applications
From (Sender)
To (Listener)
Destination Port
Purpose
Cisco 1040 Sensor PCA
1040 Sensor
2000
To communicate with Cisco 1040 server using SCCP.
CTS-Manager (CTSMAN) PCA
CTSMAN
80:TCP
To import sessions and to poll health status (HTTP).
PCA
CTSMAN
161:UDP
To poll health status (SNMP).
PCA
CTSMAN
443:TCP
To import sessions and to poll health status (HTTPS).
Cisco MCU PCA
MCU
80:TCP
To poll call details and health status (HTTP).
PCA
MCU
161:UDP
To poll health status (SNMP).
PCA
MCU
443:TCP
To poll call details and health status (HTTPS)
Cisco TelePresence Multipoint Switch (CTMS) PCA
CTMS
80:TCP
To poll health status (HTTP).
PCA
CTMS
161:UDP
To poll health status (SNMP).
PCA
CTMS
443:TCP
To poll health status (HTTPS).
Cisco TelePresence Server (TPS) PCA TPS
80:TCP
To poll health status (HTTP).
PCA
TPS
161:UDP
To poll health status (SNMP).
PCA TPS
443:TCP
To poll health status (HTTPS).
Cisco TMS PCA
TMS
80:TCP
To import sessions and health status (HTTP).
PCA
TMS
161:UDP
To poll health status (SNMP).
PCA
TMS
443:TCP
To import sessions and health status (HTTPS).
Cisco VCS PCA
VCS
80.TCP
To poll call details and health status (HTTP).
PCA
VCS
161:UDP
To poll health status (SNMP).
PCA
VCS
443:TCP
To poll call details and health status (HTTPS).
IP Phones
PCA
IP Phones
80:TCP
To obtain XML data (serial numbers and load ID) during discovery (HTTP).
PCA
IP Phones
443:TCP
To obtain XML data (serial numbers and load ID) during discovery (HTTPS).
Network Devices PCA
Network Devices
22:TCP
To log into Medianet initiator CLI during troubleshooting process (SSH).
PCA
Network Devices
23:TCP
To log into Medianet initiator CLI during troubleshooting process (Telnet).
PCA
Network Devices
80:TCP
To access Medianet initiator via WSMA during troubleshooting (HTTP).
PCA
Network Devices
161:UDP
To poll device and Medianet information (SNMP).
PCA
Network Devices
443:TCP
To access Medianet initiator via WSMA during troubleshooting (HTTPS).
Cisco Unified CM (CUCM) PCA
CUCM
22:TCP
To obtain data from CUCM using SFTP service (SFTP).
PCA
CUCM
80:TCP
To obtain call details from CUCM (HTTP).
PCA
CUCM
161:UDP
To poll health status (SNMP).
PCA
CUCM
443:TCP
To polls status and RTMT information (HTTPS).
PCA
CUCM
2748:TCP
CTI application server.
PCA
CUCM
2749:TCP
TLS connection between CTI applications (JTAPI/TSP) and CTI manager.
PCA
CUCM
2789:TCP
JTAPI application server.
PCA
CUCM
8080:TCP
To determine whether the CUCM web service is running (HTTP).
PCA
CUCM
8443:TCP
To polls CUCM status (HTTPS).
TP/Video Endpoints PCA
TP Endpoints
22:TCP
To initiate connection to endpoints during troubleshooting process (SSH).
PCA
TP Endpoints
80:TCP
To poll device info and status and call quality stats (HTTP).
PCA
TP Endpoints
161:UDP
To poll device info and status and call quality stats (SNMP).
PCA
TP Endpoints
443:TCP
To poll device info and status and call quality stats (HTTPS).
DHCP/DNS/SMTP Servers PCA
DHCP Server
67,68:TCP
DHCP service.
PCA
DNS Server
53:TCP
DNS service.
PCA
SMTP Server
25:TCP
SMTP service.
Assurance Server (PCA) Cisco 1040
PCA
5666
To receive syslog messages from Cisco 1040 sensors.
Cisco VCS
PCA
8886:TCP
To receive feedback/notification from Cisco VCS (HTTPS).
Cisco VCS
PCA
8889:TCP
To receive feedback/notification from Cisco VCS (HTTP).
Network Devices
PCA
162:UDP
To receive SNMP traps.
Network Devices
PCA
514:UDP
To receive syslogs
Network Devices
PCA
9000:UDP
To receive traps (CSListener) if port 162 is occupied.


Internal Ports used by Prime Collaboration Assurance Server

The following ports are used by the Prime Collaboration Assurance server to communicate either with the client machine or for the internal use.

From (Sender)
To (Listener)
Destination Port
Purpose
Assurance server
-
1018:TCP
Poller RMI port.
Assurance server
-
1019:TCP
Fault RMI port.
Assurance server
-
1024-4999
Ephemeral ports.
Assurance server
-
5665-5680
Inter processes communication between user interface and backend processes. These ports must be free.
Assurance server
-
9002
DynamID authentication
Assurance server
-
9009
Default port number used by the IP telephony server for receiving traps from the device fault server.
Assurance server
-
9822:TCP
Used for internal communication within the Prime Collaboration Assurance server
Assurance server
-
40000-41000
Used by Common Transport Mechanism for internal application messaging.
Assurance server
-
42344
Used by Synthetic Testing web service.
Assurance server
-
42350-42353
Used by messaging software.
Assurance server
-
43445
Used by Alert History database engine.
Assurance server
-
43446
Used by inventory service database engine.
Assurance server
-
43447
Used by event processing database engine.
Assurance server
-
43449
Used by IP Phone Information Facility database engine.
Assurance server
-
43459
QOVRdatabase.
Client browser
Assurance server
22:TCP
To connect to the Prime Collaboration server from the client machine.
Client browser
Assurance server
80:TCP
To connect to the Prime Collaboration server from the client machine over HTTP.
Client browser
Assurance server
443:UDP
To connect to the Prime Collaboration server from the client machine over HTTPS.


Ports Used by Prime Collaboration Provisioning Server, Devices, and Applications

The following tables lists the required ports for the Cisco Prime Collaboration Provisioning server to communicate with the devices and applications.

From (Sender)
To (Listener)
Destination Port
Purpose
Provisioning server
Cisco Unified Presence
8443:TCP
To communicate over HTTPS.
Provisioning server
Cisco Unity Connection
8443:TCP
To communicate over HTTPS.
Provisioning server
Cisco Unity Express
22:TCP
To communicate using SSH service.
Provisioning server
Cisco Unity Express
23:TCP
To communicate using Telnet service.
Provisioning server
Cisco Unity
1433
JDBC
Provisioning server
Unified CM
80:TCP
HTTP/Apache Web Server
Provisioning server
Unified CM
8443:TCP
To communicate over HTTPS.
Provisioning server
Unified CM Express
22:TCP
To communicate using SSH service.
Provisioning server
Unified CM Express
23:TCP
To communicate using Telnet service.


Internal Ports used by Prime Collaboration Provisioning Server

The following ports are used by the Prime Collaboration Provisioning servers to communicate either with the client machine or for the internal use.

From (Sender)
To (Listener)
Destination Port
Purpose
Client browser
Provisioning server 80:TCP
To communicate with the client machine over HTTP.
Client browser
Provisioning server
46443:TCP
To communicate with the client machine over HTTPS.
Provisioning server
Database
5432 (JDBC)
Used by the Postgres database. If you are performing a distributed installation (where the application and database are on separate server), this port must be open for inbound communication on the Provisioning Manager database server. For the Prime Collaboration Provisioning single server installation, this port is not used and should not be open for external access.
Provisioning server
-
46001
CUPM NICE Engine (RMI)
Provisioning server
-
46008
Jboss Application Server (HTTP)
Provisioning server
-
46009
Jboss Application Server (AJP)
Provisioning server
-
46083
Jboss Application Server (web services)
Provisioning server
-
46098
Jboss Application Server (RMI)
Provisioning server
-
46099
Jboss Application Server (JNP service)
Provisioning server
-
46444
Jboss Application Server (JRMP)
Provisioning server
-
46445
Jboss Application Server (Transaction Manager)
Provisioning server
-
46446
Jboss Application Server  (Remote server)
Provisioning server
-
46457
Jboss Application Server (Bisocket Transport)



Rating: 5.0/5 (2 votes cast)

Personal tools