Table of Contents
Advertisement
Network Assumptions
The MPS network route and gateway implementation conforms to the following:
• Four individual networks are required. Three of these networks are internal to
the MPS system and should not need to be changed.
• MPS is configured to listen for Routing Information Protocol (RIP) broadcasts
but does not send out any routing updates.
• Individual interfaces are configured with default IP addresses at the time of
EPAP or ELAP initialization. IP addresses are assigned as part of the
manufacturing procedure and can be changed at initialization if required. See
"Network Configuration" on page C-8 to implement a 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 Table C-5 from
the perspective of each MPS
.
C-8
ELAP or EPAP Network Integration
Preliminary
910-2969-001 Revision H, February 2007
Advertisement
Table of Contents
