to as a mated MPS system. Within one MPS system (i.e., the MPS system for one EAGLE 5 ISS), the
two MPS servers are considered mated MPS servers and are referred to as MPS A (the upper server)
and MPS B (the lower server).
The application bundle that runs G-Flex, G-Port, INP, EIR, A-Port, AINPQ, and IGM is referred to as
the EPAP. The EPAP consists of software applications needed to provision the databases, including
the Provisioning database. That is the database referred to as the PDB. In terms of G-Flex, G-Port, INP,
EIR, A-Port, AINPQ, and IS41 GSM Migration provisioning, the MPS upper and lower servers are
called simply EPAP A and EPAP B or MPS A and MPS B.
EPAP A and EPAP B are slightly different in their configuration. EPAP A runs the PDBA software
and thus holds a copy of the PDB. This is the EPAP that is accessed using the PDBI. EPAP A also holds
a copy of the RTDB for downloading to the Service Module cards. EPAP B contains a redundant copy
of the RTDB, but contains none of the PDBA software. This architecture is duplicated on the mated
MPS system on the mated EAGLE 5 ISS. Typically the redundant EAGLE 5 ISSs are called EAGLE 5
ISS A and EAGLE 5 ISS B.
The EPAPs are connected to the Service Module cards via a 10/100 BASE-T Ethernet for the
downloading of the RTDB; these Ethernet connections are called the main and backup DSM networks.
Network Connections
Connections and IP addressing for the customer (or provisioning) network, the main and DSM
networks, the RTDB, and the Dialup PPP network are described in greater detail in the EPAP
Administration Manual.
23
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual