MPR IP Addressing

5/24/2018 MPR IP Addressing

1/13

9500 MPR 1.x IP Addressing


2/132 | 9500 MPR 1.x IP Addressing |27/02/2009 All Rights Reserved Alcatel-Lucent 2009

MPR IP Addressing 1

The MPR NE is identified by its Local IP Address.

All point-to-point interfaces (TMN RF in 1.x) are unnumbered and borrow the

IP address from the Local IP Address.

The MPR has two Ethernet interfaces which can be used to access locally theNE. Each interface has its own IP address which must belong to different

subnet than the other.

Local IP Address

10.0.1.1Local Etherneton User Port 4IP Address 2

Local Ethernet

IP Address 1192.168.2.0/24

.1

.2192.168.1.0/24

.1

.2



MPR IP Addressing 2

The CT access the NE using the Local IP Address, the SNMP Trap are sent by

NE using the Local IP Address as source IP address.

It is possible to configure the IP address of one of the two Local Ethernet

interfaces with the same value used for Local IP Address.

Local IP Address10.0.1.1Local Ethernet

on User Port 4IP Address 2

Local EthernetIP Address 1

192.168.2.0/24

.1

.2

.1

.2

10.0.1.0/24

NE 10.0.1.1

NE 10.0.1.1



MPR IP Addressing 3

In the following scenario the station B, in order to reach the Local IP

Address, must be configured with a Default Gateway or static route having

the IP Address 2 as gateway.


IP Address 2User Port 4


192.168.2.0/24

.1

.2

.1

.2

10.0.1.0/24

NE 10.0.1.1

NE 10.0.1.1

A

B

Default Gateway 192.168.2.1

10.0.1.0/24 Gateway 192.168.2.1



MPR IP Addressing 4

When Local Ethernet IP addresses are different from Local IP Address all of

them must belong to different subnets.

In the following scenario, station A and B, in order to reach the Local IP

Address, must be configured with a Default Gateway or static route havingthe Local Ethernet IP Address as gateway.


IP Address 2User Port 4


192.168.2.0/24

.1

.2

.1

.2

192.168.1.0/24

NE 10.0.1.1

NE 10.0.1.1

A

B


10.0.1.0/24 Gateway 192.168.1.1


10.0.1.0/24 Gateway 192.168.2.1



MPR IP Addressing 5

In the following scenario, the CT, in order to reach the local and remote NEs

by their Local IP Address, must be configured with a Default Gateway or

static route having the Local Ethernet IP Address as gateway.

At the same time the CT must be reachable by the remote NE using a staticroute or enabling OSPF on local and remote NE.

Local IP Address10.0.1.1

Local EthernetIP Address 1 .1

.2

192.168.1.0/24NE 10.0.1.1

NE 10.0.1.2


10.0.1.0/24 Gateway 192.168.1.1




MPR IP Addressing 6

In order to allow more than one CT to access the network, the IP addresses

configured on each Local Ethernet interface inside the network must belong

to different subnets.



.2

192.168.1.0/24

NE 10.0.1.1

NE 10.0.1.2


10.0.1.0/24 Gateway 192.168.1.1

Local IP Address

10.0.1.2

.2 NE 10.0.1.1

NE 10.0.1.2


10.0.1.0/24 Gateway 192.168.2.1

.1

192.168.2.0/24


8/13

8 | 9500 MPR 1.x IP Addressing |27/02/2009 All Rights Reserved Alcatel-Lucent 2009

MPR IP Addressing 7

The following scenario doesnt work and its not allowed. Following IP

routing rules the 10.0.1.2 address must be directly reachable by the CT.



.3

10.0.1.0/24NE 10.0.1.1NE 10.0.1.2

Local IP Address

10.0.1.2


9/13


MPR IP Addressing 8

In order to reach the remote NE, its Local IP Address must belong to a

different subnet. A Default Gateway or static route having the Local

Ethernet IP Address as gateway must be configured to make the remote NE

reachable by CT.



.3

10.0.1.0/24NE 10.0.1.1

NE 172.16.1.1

Local IP Address

172.16.1.1


172.16.1.0/24 Gateway 10.0.1.1


10/13


MPR IP Addressing 9

The OSPF routing protocol can be activated on each point-to-point interface

and on each Local Ethernet interface.

The MPR NE can act as ABR (Area Border Router) managing a maximum of 4

areas (Backbone + 3 areas). It is possible to assign different OSPF areas toeach point-to-point interface.

An OSPF area can be configured as Stub Area. Configuring a Stub Area

reduces the topological database size and reduces the memory requirements

for NE inside that area for NEs that are not ABR.

The OSPF Area Identifier can take a form similar to an IP address A.B.C.D

The Area 0 or Backbone has Area ID 0.0.0.0

The Area ID hasnt any correlation with the IP address of the interface that

belongs to that area.


11/13


MPR IP Addressing 10

Enabling OSPF, static routing information configured on one NE are

automatically redistributed as OSPF external routes inside the OSPF areas

active on this NE.

Static routing are not redistributed inside the OSPF areas configured as StubArea.

If OSPF is enabled on NEs, static routes, if needed, have to be added only on

the NE reached by Ethernet (called Gateway NE).

In case of CT not directly connected to Gateway NE, the Ethernet interface

of this NE must be reachable in order to make the software download

working.


12/13


MPR IP Addressing 11

An example of OSPF Area configuration.


Local EthernetIP Address 1OSPF Area 0

.1

.2

192.168.1.0/24

NE 10.0.1.1NE 10.0.1.2NE 10.0.1.3




PtP TMN RFOSPF Area 1


OSPF Area 1 OSPF Area 2




13/13


www.alcatel-lucent.com

MPR IP Addressing

Documents

Transcript of MPR IP Addressing