Specifications

Chapter 3 Configuration Installation and Operation Manual
3-14 Configuring Pseudowire Services MPW-1 MP-4100 Ver. 2.0
3.4 Configuring Pseudowire Services
The pseudowire services enable converting TDM payload to packets and
transferring these packets through router interfaces defined in the
Megaplex-4100.
The pseudowire services supported by MPW-1 modules are configured by
providing two main groups of parameters:
• Routing parameters for the Megaplex-4100 router function
• Pseudowire processing parameters
Defining a router interface creates automatically an Ethernet E-line flow, a type
of Ethernet logical connection that interconnects two compatible network
interfaces (called
bridge ports on supervision terminal screens). Refer to Section
3.6 for a description of Ethernet flows supporting pseudowires.
Configuring the Router Function to Support Pseudowire Services
With respect to MPW-1 modules, the Megaplex-4100 router function is used to
route pseudowire packets to their destination (peer). It also provides ARP
services.
Each MPW-1 supports up to 6 different router interfaces (additional interfaces
can be configured on any bridge port in the Megaplex-4100 – see description of
Ethernet services in the
Megaplex-4100 Installation and Operation Manual ). The
IP address of the appropriate interface is automatically inserted as the
pseudowire source IP address (the destination IP address is that of the
pseudowire peer, as explained in the
Configuring the Pseudowire Peers section).
For Megaplex-4100 equipped with CL.1 or CL.1/155 modules, you can define
router interfaces only on the Ethernet ports of the same MPW-1 module (only CL
modules with GbE interfaces, that is, CL.1/155 or CL.1/155GbE, enable
transferring Ethernet traffic between different I/O modules).
To control the paths used to reach the pseudowire destinations, the MPW-1
router supports the definition of up to 100 static routes, in addition to a default
gateway. To ensure that only valid forwarding information is used, the user can
configure the ARP aging time.
To help you design the routing information,
Figure 3-1 summarizes the process
used to select the router interface for each pseudowire peer. The priority of the
various router interfaces, as determined by the routing process, is as follows:
1. If the peer IP address is in the subnet of a router interface, that interface will
always be used.
2. If the peer IP address is not within a router interface subnet, then the router
checks if the specified peer next hop address is within the subnet of a router
interface.
3. If neither of the previous conditions are fulfilled, the router checks if the
specified peer next hop address is specified in a static route that is within the
subnet of a router interface.
Note