Table of Contents
Advertisement
Hardware Manual
changed at initialization if required. See
change.
No use of virtual LANs, custom subnets, or other routing parameters are used that could
conflict with the customer network.
Matching of the interfaces to the external destinations is implemented using a default route.
Network Configuration
DSM and Sync Network addresses are configured to default values at EPAP or ELAP initialization
and should not need to be changed. If they need to be changed for any reason, refer to sections
"Network Connection" and "Configuration Menu" in the ELAP Administration Manual or EPAP
Administration Manual included in your current Documentation Suite.
The provisioning network addresses are configured using the ELAP or EPAP user interface
configuration menu; refer to "Configuration Menu" in the ELAP Administration Manual or EPAP
Administration Manual.
Firewall and Router Filtering Considerations
If a firewall is installed in the provisioning network between the MPS systems or between the
MPS system(s) and the provisioning system, it must be configured to allow selected traffic to
pass.
Firewall protocol filtering for the various interfaces is defined in
for MPS
on page 151 from the perspective of each MPS.
Table 16: Interface Functions Required for MPS
Interface
IP Port
To
20
Provisioning
Network
Netra:
10/BaseT
(hme0)
Tekserver:
Gigabit (eth0)
21
910-2969-001 Revision K, June 2009
Network Configuration
In
Use
bound
1
1
ftp-data
- The
yes
customer may
need to
transfer
provisioning
data for bulk
loading into
PDB
1
1
ftp
- Tekelec
yes
Customer
Service may
need to ftp
ELAP or EPAP Network Integration
on page 151 to implement a
Table 16: Interface Functions Required
Out
MPS
Application
bound
yes
EPAP and
ELAP
yes
EPAP and
ELAP
151
Advertisement
Table of Contents
