Tekelec T1000 Hardware Manual page 185

Table C-5. Interface Functions Required for MPS
Interface IP Port
To Provisioning 20
Network
Netra: 10/BaseT
(hme0)
21
Tekserver: Gigabit
(eth0)
22
23
123
80
8001
8473
5871-
5873
5874
5019
9696
1030
7483
9691
1. FTP data is normally received from the customer's Provisioning System.
This assumes the firewall automatically opens the high numbered return
port (the default behavior of firewalls like Firewall-1). If using a basic
packet filtering router, contact the Customer Care Center.
2. The two-way TCP communication channel endpoints are the port number
22 and the Server spawned random port value.
3. These ports are configurable via the configuration menus of the ELAP and
EPAP software. See "Configuration Menu" in the ELAP Administration
Manual or EPAP Administration Manual for more information.
910-0095-001 Revision J, November 2007
Preliminary
Use
1
ftp-data - The customer may need to
transfer provisioning data for bulk
loading into PDB
1
ftp - Tekelec Customer Service may
need to ftp software to MPS in recovery
situations
TCP (ssh) - ssh connections use TCP
telnet - needed by customer or Tekelec
customer service
NTP - needed for time-sync
Apache - needed for ExAP Web-based
GUI
3
SuEXEC - needed by ExAP Web-based
GUI
3
GUI server - needed by ExAP Web-based
GUI
Provisioning data to the EPAP
3
Provisioning data to the EPAP
Versant Fault Tolerant Server - EPAP
database mgmt system
PDBA - PDB application messages the
provisioning data
3
LSMS Bulk Download and High Speed
Audit
3
LSMS Provisioning Data
Watcher Port (diagnostics)
Firewall and Router Filtering Considerations
In
bound
1
yes
1
yes
2
yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Out MPS
bound Application
yes EPAP and
ELAP
yes EPAP and
ELAP
yes EPAP and
ELAP
Yes EPAP and
ELAP
Yes EPAP and
ELAP
No EPAP and
ELAP
No EPAP and
ELAP
Yes EPAP and
ELAP
No EPAP only
Yes EPAP only
Yes EPAP only
Yes EPAP only
Yes ELAP only
Yes ELAP only
Yes ELAP only
C-9