Table C-5. Interface Functions Required For Mps - Tekelec 1100 Hardware Manual

ELAP or EPAP Network Integration
Table C-5. Interface Functions Required for MPS
Interface IP Port Use
To 20
Provisioning
Network
Netra:
21
10/BaseT
(hme0)
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
910-2969-001 Revision H, February 2007
Preliminary
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)
MPS
In Out
Applicatio
bound bound
n
1
yes yes EPAP and
ELAP
1
yes yes EPAP and
ELAP
2
yes yes EPAP and
ELAP
Yes Yes EPAP and
ELAP
Yes Yes EPAP and
ELAP
Yes No EPAP and
ELAP
Yes No EPAP and
ELAP
Yes Yes EPAP and
ELAP
Yes No EPAP only
Yes Yes EPAP only
Yes Yes EPAP only
Yes Yes EPAP only
Yes Yes ELAP only
Yes Yes ELAP only
Yes Yes ELAP only
C-9