A9130 BSC/MFS Evolution IP addressing and routing

February 2007 Ed04

All Rights Reserved Alcatel-Lucent 2006, 2007

Agenda

1. O&M Link Options

2. External IP addresses
3. Handling address conflicts 4. Routing protocols

2 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

O&M link Options

3 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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

NEM

IP

IP

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

MX-MFS IP

IP

OMC-R IP O&M NETWORK

IP

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

MX-BSC

AGPS server
X25

IP E1 IP
Router 1

Ater E1

IP

MSC

TC

MX-BSC

MX-MFS

CBC

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

4 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

Connecting a MX-BSC via IP/Ethernet

SSW 1 Alarm Box

OMCP 2 OMCP 1

Router 1 Router 2

IP O&M NETWORK

SSW 2

MX-BSC

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
5 | A9130 IP addressing and Routing Ed04 | February 2007 All Rights Reserved Alcatel-Lucent 2006, 2007

Connecting a MX-MFS via IP/Ethernet

SSW 1
OMCP 2 OMCP 1

Router 1 Router 2

IP O&M NETWORK

SSW 2

MX-MFS

The two SSW boards of the MX-MFS are connected to the IP O&M network, providing redundancy of the O&M Link Router 1 and router 2 may be the same equipment

6 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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

Router 1

MX-BSC

MX-MFS

IP O&M NETWORK
Router 2

MX-BSC

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

Router 1 and router 2 may be the same equipment

7 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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

SSW 1 Alarm Box

OMCP 2 OMCP 1

SSW 1

IP O&M NETWORK

OMCP 2

OMCP 1

Router

TP

SSW 2

SSW 2

MX-MFS

MX-BSC

TC

MSC

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
8 | A9130 IP addressing and Routing Ed04 | February 2007 All Rights Reserved Alcatel-Lucent 2006, 2007

External IP addresses

9 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

MX-BSC external IP addresses (1/3)

Subnet A

SSW 1 Alarm Box

OMCP 2 OMCP 1

Router 1 Router 2

IP O&M NETWORK

SSW 2

MX-BSC

External subnet A (via IP/Ethernet):

Equipment MX-BSC OMCP#1 MX-BSC OMCP#2 MX-BSC active OMCP External Alarm Box

IP Address in subnet A A.1 A.2 A.3 A.6

Fixed size /29

The subnet A is visible everywhere in the IP O&M network
10 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

MX-BSC external IP addresses (2/3)

Subnet A
SSW 1 Alarm Box
OMCP 2 OMCP 1

SSW 1
Router OMCP 2 OMCP 1

IP O&M NETWORK

SSW 2

SSW 2

MX-MFS External subnet A (via Ater): Fixed size /29

MX-BSC

TC

MSC
Equipment IP Address in subnet A A.1 A.2 A.3 A.4 A.6

MX-BSC OMCP#1 MX-BSC OMCP#2 MX-BSC active OMCP Co localized MX-MFS active OMCP External Alarm Box

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
11 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

MX-BSC external IP addresses (3/3)

Equipment

SSW 1 Alarm Box

IP Address in subnet B B.1 B.2

IP Address in subnet C C.1 C.2 C.4

MxBSC OMCP#1

Router 1

Subnet B Subnet C

IP O&M NETWORK

MxBSC OMCP#2 MxBSC active OMCP Co localized active OMCP Router 1 Router 2 MxMFS

SSW 2

MX-BSC

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

12 | A9130 IP addressing and Routing Ed04 | February 2007

OMCP 2

OMCP 1

B.4 B.6

Router 2

C.6

All Rights Reserved Alcatel-Lucent 2006, 2007

MX-MFS external IP addresses (1/3)

With RIP V2:

SSW 1
OMCP 2 OMCP 1 Router 1 Router 2

IP O&M NETWORK

SSW 2

MX-MFS

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)

13 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

MX-MFS external IP addresses (2/3) With RIP V2:

SSW 1
OMCP 2 OMCP 1

Router 1

B.x

B.y

Subnet B
C.x

IP O&M NETWORK

Subnet C

Router 2

C.y

SSW 2

MX-MFS

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

14 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

MX-MFS external IP addresses (3/3) Without RIP V2:

SSW 1

A.y
OMCP 2 OMCP 1

A.x
A.f A.r A.z
SSW 2

IP O&M NETWORK

Router

A.t

MX-MFS

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

15 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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

16 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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

17 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

Handling address conflicts

18 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

When do we have an address conflict?

On OMC-R side

When the OMC-R network uses reserved addresses

OMC-R

IP O&M NETWORK

Router

172.16/16

MX-MFS or MX-BSC

Solution: Use NAT on the router

Enable NAT on the MX router

OMC-R

IP O&M NETWORK 172.16/16

Router

MX-MFS or MX-BSC

19 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

When do we have an address conflict?

On element network side

When legacy element network uses reserved addresses

172.16/16 IP O&M NETWORK
Legacy MFS

OMC-R

MX-MFS
Legacy MFS

Solution: Create new subnet for MX equipments

172.16/16
Legacy MFS OMC-R

IP O&M NETWORK
Legacy MFS

MX-MFS

new subnet for MX equipments

MX-MFS

20 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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?

IP O&M NETWORK

Router

MX-MFS or MX-BSC
Customer intranet 172.16/16

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

21 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

Using NAT to solve IP address conflicts

What 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
Configuration rules: Translate External: 172.17.3.30 to internal: 10.0.0.30

inside

10.0.0.30 NAT function

172.17.3.30

outside

10.0.0.30 Internal addresses

172.17.3.30 External addresses

22 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

Using NAT to solve IP address conflicts

An 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.
10.2.2.1 172.17.3.3 O&M IP NETWORK
OMC-R

Router

MX-MFS

23 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

Using NAT to solve IP address conflicts

An 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

outside
request

inside
Src: 172.17.3.3 Dst: 10.2.2.1 Src: 139.54.96.5 Dst: 10.2.2.1

O&M IP NETWORK
OMC-R reply

Router

172.17.3.3

Src: 10.2.2.1 Dst: 172.17.3.3

Src: 10.2.2.1 Dst: 139.54.96.5

MX-MFS 10.2.2.1

24 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

Routing protocols

25 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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.
RIP for link redundancy Any customer routing architecture

SSW 1
OMCP 2 OMCP 1

Router 1 Router 2

SSW 2

Customer O&M IP network

MX-BSC or MX-MFS

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

26 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

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
Link C has failed. Go through B instead

O&M path O&M IP networ k

Router 1

SSW 1

B.x
OMCP 1

MX-MFS or MX-BSC

Subnet B
Subnet C

B.y

SSW 2

or by the router to tell MX when a router fails

MX-MFS or MX-BSC

27 | A9130 IP addressing and Routing Ed04 | February 2007

OMCP 2

Router 2

C.x

C.y

A. x

Path through C has failed Go through B instead

O&M path

Router 1

SSW 1
OMCP 2 OMCP 1

B.x

Subnet B

B.y

SSW 2

C.x

Subnet C

C.y

O&M IP networ k

Router 2

A. x

All Rights Reserved Alcatel-Lucent 2006, 2007

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
A.x
SSW 1
Router 1

O&M path

B.x
OMCP 1

MX-MFS or MX-BSC

Subnet B Subnet C

B.y

O&M IP network

SSW 2

28 | A9130 IP addressing and Routing Ed04 | February 2007

OMCP 2

Router 2

C.x

C.y

All Rights Reserved Alcatel-Lucent 2006, 2007

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
SSW 1
OMCP 2 OMCP 1 Router 1 Router 2

Any customer routing architecture

SSW 2

Customer O&M IP network

MX-BSC or MX-MFS
29 | A9130 IP addressing and Routing Ed04 | February 2007 All Rights Reserved Alcatel-Lucent 2006, 2007

Example: MX-MFS router configuration in an OSPF network

RIP for link redundancy OSPF customer backbone
10.121.4/24 192.168.201/24 Router R_211 A.x= 192.168.203.4 192.168.202/24 10.125.1/24

O&M IP network OMC-R

MX-MFS

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

30 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007

www.alcatel-lucent.com

31 | A9130 IP addressing and Routing Ed04 | February 2007

All Rights Reserved Alcatel-Lucent 2006, 2007