Vous êtes sur la page 1sur 16

BSC LAN Redundancy

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Nokia Solutions and Networks Academy

Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Solutions and Networks training documentation,
product documentation and slide presentation material, all of which are forthwith known as Nokia Solutions
and Networks training material, are the exclusive property of Nokia Solutions and Networks. Nokia Solutions
and Networks owns the rights to copying, modification, translation, adaptation or derivatives including any
improvements or developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend,
modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and Networks training
material. Individuals can use the Nokia Solutions and Networks training material for their own personal selfdevelopment only, those same individuals cannot subsequently pass on that same Intellectual Property to
others without the prior written agreement of Nokia Solutions and Networks. The Nokia Solutions and
Networks training material cannot be used outside of an agreed Nokia Solutions and Networks training
session for development of groups without the prior written agreement of Nokia Solutions and Networks.

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Module Objectives

After completing this learning element, the participant will be able to:
Explain 2N/N+1 redundancy models for functional units
Describe Interface and link redundancy
Describe SCTP multihoming
Explain redundancy of integrated L2 switches (SWUs)

Refer to RG30 Documentation:


Plan and dimension / BSC Site IP Connectivity Guidelines (DN03502792)
Plan and dimension / BSC Site IP Configuration Examples (DN70609908)

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Redundancy Models for Functional Units


For internal use
RN28225EN30GLA0

Nokia Solutions and Networks 2014

2N/N+1 Redundancy Models for Functional Units

OMU no redundancy
MCMU 2N redundant
BCSU N+1 redundant
PCU units follow the BCSU redundancy scheme
ETPE and ETPT 2N redundant
ETPA load sharing redundancy
Logical IP addressing is used to hide the MCMU, BCSU and ETP switchovers. During a switchover, the
logical IP addresses are moved to the unit that takes over as the new working unit. The serving IP address
remains the same for the remote peer-end application.
Note:
Only the IP address remains after a unit switchover. All existing IP connections are lost, since the TCP/IP
stack and local IP applications of BSC are not warned and are therefore unable to move established
connections from the failing unit to the new working unit in time.
6

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Interface and Link Redundancy


For internal use
RN28225EN30GLA0

Nokia Solutions and Networks 2014

Interface and Link Redundancy

UNIT-n (WO-EX)

Logical &
carrier sense
active

carrier sense
back-up

172.16.2.2

(172.16.2.2)

CPU and PCUs units have two functionally independent LAN interfaces.
CPU EL0 and EL1
PCU ifeth0 and ifeth1
ETP IL0 and IL1 (internal BSC interfaces)
ETP EL0 (external interface)
- (EL0 comprises two SFP units offering carrier sense redundancy).
8

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Interface and Link Redundancy, cont.

The link between the unit and the SWU can fail because of a failure of the active interface, LAN cable, or
SWU. If the physical link fails, a carrier sense IP address is quickly moved to the standby interface and a
gratuitous ARP is broadcast in order to advertise the MAC address of the new active interface.
The hosts and routers in the same L2 network learn the new MAC address for the IP address from the
gratuitous ARP message. Hosts and routers can thus send traffic without interruption, using the MAC
address of the new active interface. Status changes at the physical link are detected by device interrupt. A
redundant IP address switchover is therefore a nearly transparent action for IP user applications and has no
effect on established IP connections.
The PCU plug-in unit variants PCU, PCU-S, and PCU-T cannot generate hardware interrupts from link
status changes. Instead, they detect physical link status changes by polling the status at 200-ms intervals by
means of the Ethernet driver.

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Interface and Link Redundancy, cont.

Interface redundancy is achieved by configuring the same logical IP address for two separate network
interfaces of the unit. From the operators point of view, the IP address appears to float between two
interfaces, but in practice the IP address is assigned to only one interface at a time. The user may optionally
prioritise the interfaces so that a unit always favours the same physical network interface when both
interfaces are functionally stable.
Multiple Ethernet and VLAN interfaces may exist. Each IP address may have at most one redundant
interface with the same type (either Ethernet or VLAN; no mixes). Redundant interface switchovers can also
be triggered manually with the MML command QRW. For more information, see TCP/IP Stack Data
Handling.

10

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Bond Interfaces

BOND-type interface redundancy means that, unlike on a carrier sense interface, both interfaces are active
and may send and receive simultaneously. In case of failure, all traffic is handled by the remaining active
interface. An example of this is the bonding of the IL0/IL1 interfaces that are used for internal signalling on
the ETP/ETP-A PIUs.

UNIT-n (WO-EX)

active
(172.16.2.2)

0
BOND 0

11

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

SCTP Multihoming
For internal use
RN28225EN30GLA0

Nokia Solutions and Networks 2014

SCTP Multihoming

A host is called multi-homed if it can be addressed by multiple IP addresses


When both peers have multiple IP addresses and traffic is routed via physically different paths then SCTP can survive any
single point network problem.
SCTP can use the two Ethernet interfaces of a MCMU and BCSU in such a way that one is working as a primary and the
other one as a secondary path .
If the primary path fails, the SCTP can re-send unacknowledged messages via the secondary path, ensuring that no
messages are lost if one of the paths is broken.
SCTP also has a built-in heartbeat mechanism for idle paths.
If M3UA destination is not reachable via BCSU multihoming interface within association set (load sharing) other BCSU is
used for backup.

13

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Redundancy of Integrated L2/L3 Switches


(SWUs)
For internal use
RN28225EN30GLA0

Nokia Solutions and Networks 2014

Redundancy of Integrated L2/L3 Switches


(SWUs)
The SWUs are divided into SWU pairs. Both SWUs in a pair are in operation. If a malfunction occurs in a
SWU, the other SWU in the pair will take over and provide connectivity towards the site router or multilayer
switch. The SWUs are managed by the active MCMU.

15

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Other Redundancy Principles

Redundancy of SWU Site equipment links


- The physical layer supervision of the LAN interfaces of the interface plug-in unit can only detect
failures in the link between the unit and the SWU. Therefore the unit cannot make an interface
switchover if the link between the SWU and the site router or multilayer switch fails. To provide for this
kind of situation, the SWUs are connected to each other in a loop.
- The Spanning Tree Protocol (STP) is needed to break the loop. With the Rapid Spanning Tree
Protocol (RSTP), the system recovers from this type of failure in less than a second.
Redundancy in multilayer site switch and in site router
- hardware redundancy features is recommended with replicated power supplies and cooling and fast
recovery times due to trunk links
- Virtual Router Redundancy Protocol (VRRP) or Hot Standby Router Protocol (HSRP)
Redundancy towards backbone
- Dynamic routing protocol is used between the site routers and the backbone. Open Shortest Path First
(OSPF) is the recommended dynamic routing protocol. If one of the links fails, the routers find out the
working link through OSPF.
16

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014

Redundancy Summary

Redundant IP backbone may


provide different IP path for sent
and received IP packet.
MSTP manages ports in the
switches and opens the best path
between assigned IFETH and
L2/L3 switch.
Switchover from root to alternate
port should take < 200 ms
Virtual Gateway address
HSRP switchover takes 1-5
seconds by tuned timers (L2
recovery takes 100200ms)
Site Switch, ESB and Backbone
redundancies (HW)
Interface redundance and
Logical interface

17

For internal use


RN28225EN30GLA0

Nokia Solutions and Networks 2014