Loader

Open Ports for Communication

This section describes the open ports for communication between Panorama PON EMS and Optical Network Terminals (OLTs).

 Ports and Protocols

The following table lists the ports that must be open for successful communications between the Panorama PON EMS server(s), the Panorama PON EMS Client, the Panorama PON EMS remote Clients, the Tellabs 1000 VGW OLTs, and the Tellabs 1100 Series OLTs.

The following table is the firewall setup for traffic into or out of a Panorama PON server:

Table 1 - RMI Port List

Host Incoming/ Listening Port Outgoing/ Destination Port Outgoing/ Source Port Protocol Purpose
Ports for traffic into or out of Panorama PON server
PanoramaPON server 7099     RMI/TCP For PanoramaPON remote client to connect to server directory
PanoramaPON server 7101     RMI/TCP For PanoramaPON remote client to connect to Panorama server for initial login
PanoramaPON server   1632   CORBA/TCP For PanoramaPON server to connect to OLT via TLS 1.2
PanoramaPON server 1632     CORBA/TCP For OLT to connect to PanoramaPON server via TLS 1.2
PanoramaPON server 3001     HTTPS/TCP For OLT/ONT to connect to secured TConfig server
PanoramaPON server 3010     HTTPS/TCP For ONT729GP to connect to PanoramaPON server to retrieve certificates, ignore if ONT729GP AS-SIP is not in use
PanoramaPON server 8081     HTTPS/TCP For web browser to connect to Panorama HTTP/web server
PanoramaPON server 8090     HTTPS/TCP For OLT to connect to PanoramaPON HTTP server for secured software download
PanoramaPON server   587   SMTP/TCP For forwarding OLAN alarms to SMTP server via emails, ignore if alarm forwarding is not in use
PanoramaPON server 8055     TCP For EMS/OLT user Yubikey authentication
PanoramaPON server if RMI firewall ports enabled     1840-1849 RMI/TCP For PanoramaPON server connect to client for notifications, default port numbers
PanoramaPON server if RMI firewall ports enabled   2075-2079   RMI/TCP For PanoramaPON server connects to client for notifications, default port numbers
PanoramaPON server if RMI firewall ports enabled 1835-1839     RMI/TCP For PanoramaPON client connect to server for normal GUI operations, default port numbers
Ports for traffic into or out of Panorama PON client
PanoramaPON client   7099     For Panorama client to connect to server directory
PanoramaPON client   7101     For Panorama client to connect to Panorama server for initial login
PanoramaPON client if RMI firewall ports enabled     2080-2090 RMI/TCP For PanoramaPON client connect to server for normal GUI operations, default port numbers
PanoramaPON client if RMI firewall ports enabled   1835-1839   RMI/TCP For PanoramaPON client connect to server for normal GUI operations, default port numbers
PanoramaPON client if RMI firewall ports enabled 2075-2079     RMI/TCP For the PanoramaPON server to connect to client for notifications, default port numbers
Ports for traffic into or out of OLT
OLAN system (OLT) 22     SSH/TCP For command line interface connection to OLT
OLAN system (OLT) 1632     CORBA/TCP For PanoramaPON server to open a secured TLS 1.2 connection with OLT

 Table 1 - RMI Port List (Cont)

Host Incoming/ Listening Port Outgoing/ Destination Port Outgoing/ Source Port Protocol Purpose
Ports for traffic into or out of OLT (Cont)
OLAN system (OLT)   1632   CORBA/TCP For OLT to send notifications to PanoramaPON server via TLS 1.2
OLAN system (OLT)   8090   HTTPS/TCP For OLT to download software in a secured connection
OLAN system (OLT)   3001   HTTPS/TCP For OLT to retrieve TConfig data in a secured connection
OLAN system (OLT)   3010   HTTPS/TCP For ONT 729GP AS-SIP to retrieve certificates
OLAN system (OLT)   1812   TCP/UDP For OLT to connect to RADIUS server for authentication, ignored if RADIUS server is not in use
OLAN system (OLT)   3799   UDP For OLT to connect to RADIUS server for change of authorization, ignored if RADIUS server is not in use
OLAN system (OLT)   8055   TCP For EMS/OLT user Yubikey authentication

 The following table describes the ports that can be used to setup a firewall for traffic into or out of VGW.

Table 2 - VGW External Systems Ports 

Host Incoming Port Outgoing Port Protocol

Purpose  

Tellabs 1000 VGW system 23   Telnet/TCP For command-line Telnet interface to VGW
 
Tellabs 1000 VGW system 3023
 
  Telnet/TCP For text-based craft menus 
Tellabs 1000 VGW system 3082
 
  TL1/TCP For PanoramaPON server to open non-connection with VGW
Tellabs 1000 VGW system 5111   TCP For system discovery by PanoramaPON server
Tellabs 1000 VGW system 5112   TCP For broadcasting messages by AUP software
Tellabs 1000 VGW system 55113   TCP For auto-upgrade of VGW software
Tellabs 1000 VGW system 55114     TCP  For secondary console port

Previous  |  

Send feedback on this topic to Tellabs.
FEEDBACK: Are you happy with this material?

On this page