mx-ip addressing routing (alcatel evolution mx platform)

All Rights Reserved © Alcatel-Lucent 2006, 2007

A9130 BSC/MFS Evolution

IP addressing and routing

February 2007 – Ed04

All Rights Reserved © Alcatel-Lucent 2006, 20072 | A9130 IP addressing and Routing – Ed04 | February 2007

Agenda

1. O&M Link Options

2. External IP addresses

3. Handling address conflicts

4. Routing protocols


1 O&M link Options


MX-MFS and MX-BSC O&M link options

X25

IP

AterE1

E1

MSC MX-MFSTC MX-BSC

IP

MX-BSC

IP

MX-MFS

IP

IP

IP

IP

IP/Ethernet O&M link:MX-BSC directly connectedto IP LAN

IP/Ethernet O&M link:MX-MFS directly connectedto IP LAN

O&M over Ater (extraction at TC or MSC side):Ethernet/IP link from colocalized MFS to BSC,BSC manages O&M IP connection using ML-PPP over Ater

Rou

ter 1

CBC

AGPS server

OMC-R

IP

NEM

IP O&M NETWORK


Connecting a MX-BSC via IP/Ethernet

The two SSW boards of the MX-BSC are connected to the IP O&M network, providing redundancy of the O&M link

Alarm Box may be connected to the SSW#1 of the MX-BSC or directly to the IP O&M network.

Router 1 and router 2 may be the same equipment

MX-BSC

IP O&M NETWOR

K

OM

CP

1

OM

CP

2

SSW 2

Alarm Box

SSW 1 Rou

ter 1

Rou

ter 2


Connecting a MX-MFS via IP/Ethernet

IP O&M NETWOR

K

MX-MFS

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Rou

ter 1

Rou

ter 2

The two SSW boards of the MX-MFS are connected to the IP O&M network, providing redundancy of the O&M Link



Connecting multiple MX-BSC and MX-MFS via IP/Ethernet

IP O&M NETWOR

K

Rou

ter 1

Rou

ter 2

MX-MFS

MX-BSC

MX-BSC

…

Multiple MX-BSC and MX-MFS may be connected to the same router(s)



Connecting a MX-BSC and a MX-MFS via Ater

MX-MFS is optional. If it is present the two SSW boards of the MX-MFS are connected to the SSW boards of the MX-BSC.

O&M link over Ater uses a flexible bandwidth from 128 Kbps up to 1 Mbps

ML-PPP protocol is used between MX-BSC and the router

O&M link extraction is possible at TC or at MSC

MX-BSC

IP O&M NETWOR

K

MX-MFS

OM

CP

1

OM

CP

2

Alarm Box

OM

CP

1

OM

CP

2

SSW 2

SSW 1

TP

SSW 2

SSW 1

TC MSC

Rou

ter


2 External IP addresses


MX-BSC external IP addresses (1/3)

External subnet A (via IP/Ethernet):

Fixed size /29

The subnet A is visible everywhere in the IP O&M network

Subnet A

Equipment IP Address in subnet A

MX-BSC OMCP#1 A.1

MX-BSC OMCP#2 A.2

MX-BSC active OMCP A.3

External Alarm Box A.6

MX-BSC

IP O&M NETWOR

K

OM

CP

1

OM

CP

2

SSW 2

Alarm Box

SSW 1 Rou

ter 1

Rou

ter 2


TC MSC


External subnet A (via Ater):

Fixed size /29

For MX-MFS only active OMCP is reachable

The subnet A is visible everywhere in the IP O&M network

In case of connection via Ater RIP is not used

Subnet A

Equipment IP Address in subnet A

MX-BSC OMCP#1 A.1

MX-BSC OMCP#2 A.2

MX-BSC active OMCP A.3

Co localized MX-MFS active OMCP A.4

External Alarm Box A.6

MX-BSC

IP O&M NETWOR

K

MX-MFS

OM

CP

1

OM

CP

2

SSW 2

Alarm Box

SSW 1

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Rou

ter



MX-BSC

IP O&M NETWOR

K

OM

CP

1

OM

CP

2

SSW 2

Alarm Box

SSW 1 Rou

ter 1

Rou

ter 2

Subnet B

Subnet C

Equipment IP Address in subnet B

IP Address in subnet C

MxBSC OMCP#1 B.1 C.1

MxBSC OMCP#2 B.2 C.2

MxBSC active OMCP

Co localized MxMFS active OMCP

B.4 C.4

Router 1 B.6

Router 2 C.6

Local subnets B and C (only in case of direct connection):

Fixed size /29

Local subnets are used to announce the entry point of the system

External alarm box is internally routed by MX-BSC active OMCP

Local subnet are visible only by the router in entrance of the IP network


MX-MFS external IP addresses (1/3)

External IP address:

Only one external IP address to access the active OMCP: A.x

MX-MFS external IP address always points to the active OMCP (pilot)

IP O&M NETWOR

K

MX-MFS

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Rou

ter 1

Rou

ter 2

With RIP V2:



IP O&M NETWOR

K

MX-MFS

Rou

ter 1

Rou

ter 2

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Subnet B

Subnet C

B.y

C.yC.x

B.x

With RIP V2:

Local subnets B and C:

One IP address to access the active OMCP in each subnet: B.x and C.x

One IP address to reach the router in each subnet: B.y and C.y

Local subnets are visible only by the router in entrance of the IP network



IP O&M NETWOR

K

MX-MFS

Rou

ter

OM

CP

1

OM

CP

2

SSW 2

SSW 1

A.y

Without RIP V2:

A.x

A.t A.z

A.rA.f

External IP addresses:

One floating IP address to access the active OMCP: A.f

Two physical IP addresses per OMCP: A.x, A.z, A.y, A.t

One IP address to reach the router A.r


How to choose IP addresses for a MX-MFS

IP addresses for a MX-MFS can be chosen freely, limited only by the following rules:

MX-MFS external addresses must not belong to the following networks:

172.16/16, 172.17/16, 172.18/16, 172.19/16, 172.32/16

OMC-Rs or other equipments with which the MX-MFS interacts must not belong to the following networks:

172.16/16, 172.17/16, 172.18/16, 172.19/16, 172.32/16

Customer is free to use these networks, provided these networks or machines on this network do not interact with MX-MFS


How to choose IP addresses for a MX-BSC

IP addresses for a MX-BSC can be chosen freely, limited only by the following rules:

MX-BSC external addresses must not belong to the following networks:

172.16/16, 172.17/16, 172.18/16

OMC-Rs or other equipments with which the MX-BSC interacts must not belong to the following networks:

172.16/16, 172.17/16, 172.18/16 Customer is free to use these networks, provided these networks or

machines on this network do not interact with MX-BSC

In the case of an O&M link on ML-PPP (O&M link over Ater), MX-BSC external addresses must not belong to the network:

1.1.1.0/29


3 Handling address conflicts


When do we have an address conflict?On OMC-R side

When the OMC-R network uses reserved addresses

Solution: Use NAT on the router

IP O&M NETWORK

MX-MFS or MX-BSC

172.16/16

OMC-R

Rou

ter

IP O&M NETWORK

MX-MFS or MX-BSC

172.16/16

OMC-R

Rou

ter

Enable NAT on the MX

router


When do we have an address conflict?On element network side

When legacy element network uses reserved addresses

Solution: Create new subnet for MX equipments

new subnet for MX equipments

IP O&M NETWORKOMC-R

Legacy MFS

Legacy MFS

172.16/16

MX-MFS

IP O&M NETWORKOMC-R

Legacy MFS

Legacy MFS

172.16/16

MX-MFS

MX-MFS


When do we have an address conflict?Somewhere in the customer intranet

What if the customer uses a reserved network somewhere not related to MX in his IP infrastructure?

No problem!

Only restrictions are on giving reserved addresses as MX external addresses or as addresses that MX communicates with!

OMC-R

IP O&M NETWORK

MX-MFS or MX-BSC

Rou

ter

Customer intranet172.16/16


Using NAT to solve IP address conflictsWhat is NAT?

NAT stands for Network Address Translation.

NAT consists in translating IP addresses on-the-fly, from « internal » addresses to « external » ones based on translation rules.

Can translate source addresses, destination addresses, or both

operates in both directions (inout), (outin)

NAT is very widespread and available in most routers

NAT function

Internal addresses External addresses

172.17.3.30

172.17.3.3010.0.0.30

10.0.0.30

Configuration rules:Translate

External: 172.17.3.30 tointernal: 10.0.0.30

inside outside


Using NAT to solve IP address conflictsAn MX-MFS example (1/2)

The problem

OMC-R uses a MX reserved address, for example: 172.17.3.3

MX-MFS external address A.x is 10.2.2.1 (no problem here)

OMC-R has no problems sending packets to the MFS, since 10.2.2.1 is a valid address routed to the MX-MFS

But the MX-MFS cannot reply, because 172.17.3.3 is used internally by MFS, and MFS does not know where to send the reply.

The main problem is on source addresses of packets coming from OMC-R, which the MX-MFS cannot use as a destination for replies.

O&M IPNETWORK

MX-MFS

172.17.3.3

OMC-R

Rou

ter

10.2.2.1


Using NAT to solve IP address conflictsAn MX-MFS example (2/2)

The solution: enable NAT on the router

Choose a translated (NATed) address for the OMC-R: 139.54.96.5

Enable NAT on the router and configure NAT rules

Translate outside source address (src) 172.17.3.3 to 139.54.96.5 Translate inside destination address (dst) 139.54.96.5 to 172.17.3.3

O&M IPNETWORK

172.17.3.3

OMC-R

Rou

ter

MX-MFS 10.2.2.1

Src: 172.17.3.3Dst: 10.2.2.1

Src: 139.54.96.5Dst: 10.2.2.1

Src: 10.2.2.1Dst: 172.17.3.3

Src: 10.2.2.1Dst: 139.54.96.5

insideoutside

request

reply


4 Routing protocols


Are there requirements for customer networks?

No. MX imposes no requirements on routing protocols within customer networks! Customer is free to architect his network any way he likes.

… but MX-MFS and MX-BSC use RIP protocol for managing first link redundancy, only between the equipment and the first router.

There is no RIP on customer network

Smallest possible constraint on first router for redundancy management

RIP for link redundancy

MX-BSC or MX-MFS

CustomerO&M IP network

OM

CP

1

OM

CP

2

SSW 2

SSW 1 Rou

ter 1

Rou

ter 2

Any customer routing architecture


Why RIP v2 on the first link? (1/2)

RIP is used by MX to tell the router to change the route when link fails

… or by the router to tell MX when a router fails

MX-MFS orMX-BSC

O&M IP

network

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Subnet B

Subnet C

B.y

C.yC.x

B.x

Rou

ter 1

Rou

ter 2

O&M path

A.x

O&M IP

network

MX-MFS orMX-BSC

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Subnet B

Subnet C

B.y

C.yC.x

B.x

Rou

ter 1

Rou

ter 2

O&M path

A.x

Link C has failed. Go through B

instead

Path through C has failed

Go through B instead


Why RIP v2 on the first link? (2/2)

RIP thus allows to re-route O&M traffic to the appropriate first link

when a MX link fails

when a MX edge router fails (or router interface in the single router case)

when a router along the path fails requiring a MX link change

O&M IP networ

k

MX-MFS orMX-BSC

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Subnet B

Subnet C

B.y

C.yC.x

B.x

Rou

ter 1

Rou

ter 2

O&M pathA.x


Why RIP and not OSPF or some other method?

Ease-of-use: RIP represents the smallest possible constraint on the MX edge router

RIP is found in all routers on the market

Simplest protocol to configure: almost no configuration (default values are used)

Simplest redundancy solution

And remember: RIP is for the first link only. Within his network, the Customer uses whatever solution he wants.

« translating » between routing protocols is also what routers are for!RIP for link redundancy

MX-BSC or MX-MFS

CustomerO&M IP network

OM

CP

1

OM

CP

2

SSW 2

SSW 1

Rou

ter 1

Rou

ter 2

Any customer routing architecture


Example: MX-MFS router configuration in an OSPF network

Router configuration consists in:

Telling the router to run RIP on MX-MFS interfaces,

Telling the router to run OSPF on backbone interface,

Telling the router to redistribute RIP info from MX-MFS to OSPF backbone,

Telling the router to redistribute OSPF info to the MX-MFS.

This is done via few router configuration commands

O&M IPnetwork

MX-MFS

Rou

ter R

_21

1

OMC-R

192.168.201/24

192.168.202/24

A.x=192.168.203.4

10.121.4/24

10.125.1/24

RIP for link redundancy OSPF customer backbone


www.alcatel-lucent.com

mx-ip addressing routing (alcatel evolution mx platform)

Documents