Evo Controller 8200 IP Configuration KO PDF
Evo Controller 8200 IP Configuration KO PDF
Evo Controller 8200 IP Configuration KO PDF
IP configuration
Ivan Guo
Agenda
1. Overview
2. IP transmission boards
3. IP Configuration
4. Learn by instance
References.
Overview
HW architecture
TN Infra Structure
IP/Ethernet ATM
IP/Ethernet
Traffic Main Subrack 1..1
(e.g. Mub/Mut)
Synch. Ref.
CMXB SCXB
OSS-RC Mur
Ext. Mgmt Sys
EPB ET
Mur -48V/DC
Thin Client/
Console
Extension Subrack 0..2
Iu
CN CMXB SCXB
Iur
EPB ET
RNC
Iub -48V/DC
RBS
RNC
HW architecture
TN Infra Structure
IP/Ethernet
IP/Ethernet
Traffic Main Subrack 1..1
(e.g. Mub/Mut)
Synch. Ref.
CMXB SCXB
OSS-RC Mur
Ext. Mgmt Sys -48V/DC
EPB
Mur
Thin Client/
Console
Extension Subrack 0..2
Iu
CMXB SCXB
CN
Iur -48V/DC
EPB
RNC
Iub
RBS
RNC
Evo Processor Board
Evo Processor Board (EPB1)
General processing
2 X 10 Gbps Ethernet ports in the back plane
2 X RS232 ports in one connector on the front panel
(RS232)
2 X 1 Gbps Ethernet ports in one connector on the front
panel (DBG) 25 (GE)
22 (RS232)
EPB1
Evo Processor Board
The EPB implements IP and Ethernet layer functions, such as: 10
Gigabit Ethernet termination, VLAN termination and IP layer
termination, Performance Management (PM), and Fault Management
(FM).
The two 10 Gigabit Ethernet links (interfaces) at the back are accessed
from the Ethernet switch board through the backplane
Local Access to the node is only supported through the Gigabit
Ethernet interface on the front.
Evo Processor Board
Ethernet interface redundancy (1+1) is handled by the embedded
Ethernet forwarder. The embedded Ethernet forwarder does not
require any configuration.
Each GigabitEthernet MO is configured to use the 10 Gigabit Ethernet
Interface 1 or the 10 Gigabit Ethernet Interface 2 by using the
primaryLink attribute.
IP termination on EPB
3810/3820
EVO
EPB
UDP UDP UDP UDP
Ext. host PDR Int. host DC Ext. host
Iu-ps Iub
(IP) (IP)
IP termination on EPB
Advantage & disadvantage
Increase call setup capacity and throughput
Large increase in external IP addresses
3 types of Software Allocations (SWAs) for EPB:
EPB_C1 RNC Central Processor 1 placed only in Main Subrack
in slots 3 and 25.
EPB_C2 RNC Central Processor 2 placed only in Main Subrack
in slots 4 and 26.
EPB_BLADE_A Module Controller (MC) functionality resides on
the primary processor and Device functionality on the primary
and secondary processor.
IP termination on EPB
RNC Software deployment
C1 (1+1) C2 (1+1)
- 2 x SCTP Front End - 2 x SCTP Front End
- O&M - Central device handling
- RFN server (moved from TUB) - UE register
Blade (2 68)
Primary processor Secondary processor
CPP PDR device + CPP
IP (bare metal) IP (bare metal)
CC device DC device
RNC Module + RNSAP DC device
RNC Module + RANAP DC device
RNC Module + PCAP DC device
DC device DC device
DC device DC device
IP transmission boards
Cabinet
EvoC 8200/RNC
EPB
ES-2 ES2
EPB
ES-1
MS
APP2
APP1
MS
32 (SC)
20 (GE 1)
Connector to regional processor in AXE, not used 17 (E 4)
in RNC (RP-B) 15 (E 3)
10 (E 1)
GE2, GE3)
SCXB3
4 X 10 Gbps Ethernet ports on the front panel (E1,
E2, E3, E4)
Common Main Switch Board
35 (GE 2)
- GE4)
27 (E 8)
E8) 22 (E 6)
17 (E 4)
panel (E1 E4) 15 (E 3)
12 (E 2)
10 (E 1)
CMXB3
Evo Controller Provides 10G and 1G
Ethernet to all Slot Positions
White fronts and new LEDs
APP Pos
Board connector
CMXB3
CMXB3
Type Connect Pos
or
Other end
SCXB3
EPB1
EPB1
SCXB3
One end
Unit Connector Pos Unit Pos
SCXB3 SC 02-32 APP 02-74
SCXB3 SC 80-32 APP 03-74
EPB1 GE 08-25 APP 02-68
EPB1 GE 74-25 APP 03-68
SCXB3 SCXB3 SCXB3
ESL & CISL
CMXB
CMXB
EPB
SCXB
SCXB
40G
40G
40G
CMXB
CMXB
SCXB
EPB
SCXB
40G 40G
40G
CMXB
CMXB
EPB
SCXB
SCXB
4x10G 4x10G
APP APP
4x10G 4x10G
IP Transport in Evo
IP Host User Plane Termination
The EPB1 board is equipped with two processors with 8 cores each. Each processor
will that uses external or internal communication needs an IP host in order to
communicate. Each processor supports up to 16 external and 1 internal IP host
terminations.
RNC user plane software (DC, CC and PDR) will be located on both processors
which results in that IP interfaces will be needed on both processors.
The external IP hosts will be configured in a similar way as the IpAccessHostEt using
the MOM. However the internal IP host will not be shown in the MOM and will not be
possible to configure.
IP Transport in Evo
IP Host Control Plane Termination
The control plane (SCTP) can be terminated in two different ways; via ipAccessSctp
or directly to the ipAccessHostEt. The main benefit of using the IpAccessSctp MO is
that the CP and UP can share the same ipAccessHostEt (IP address). The SCTP
functionality supports multi-homing; see MO structure for Iub CP below.
The proposed default configuration is to configure the Iub CP without any multi-
homing and share IP address with the Iub UP.
IP Addressing
External and internal IP hosts
The IP termination on the EPB consists of a number of external and
internal IP hosts.
Up to 16 external hosts and up to 64 internal hosts are supported
for each processor.
Each external host is connected to a separate IpInterface MO
and all the internal hosts are connected to the same IpInterface.
The internal IP hosts require no configuration and are not visible
in the MO structure.
It is important to make sure that the VLAN ID is not colliding with
any planned external VLANs.
IP Addressing
The PIU processor contains MCs, where the IUB CP is terminated. It
also contains a CC device (terminating IUB common channels) and
DC device (terminating the IUB and IUR UP for dedicated channels).
The Piudevice processor contains PDR device (terminating the IU-
PS UP) and DC device (terminating the IUB and IUR UP for
dedicated channels).
A typical configuration:
different VLANs/subnets used for all different interfaces.
3 IP hosts per blade on PIU, for IUB UP/CP, IU-CS UP, IUR-UP
4 IP hosts per blade on Piudevice, for IUB UP, IU-CS UP, IUR-UP, plus
IU-PS UP.
For the central boards(C1, C2), one IP host is needed per board for
termination of SCTP for IU-CS, IUPS and IUR CP and for IU-PC.
In addition, IP hosts are needed on C1 for Mur and IU-BC.
IP Addressing
E E E E E E
Iub:
2*68 (EPB blade)+2 (C1 EPB) =138 IP hosts Up to 24 EPB blades
One /24 network with 256 addresses
IuCS/Iur UP: E E E E E E
2*68 (EPB balde) =136 IP hosts
One /24 network with 256 addresses Up to 24 EPB blades
IuPS UP:
68 (EPB blade) IP hosts C1 C2 E E E E C1 C2
H Iub UP/CP - two IpAccessHostEt per EPB blade + 2 for NTP Server on C1 device processor
H IuCS/Iur UP - two IpAccessHostEt per EPB blade
H IuPS UP - one IP host per EPB blade, only on secondary (PIU Device)
processor
H Iu/Iur CP one (multi homed) IP host on each c1 and c2 EPB (two VLANs, CP-A and CP-B)
Vlan Configuration
The configuration of node Ethernet infrastructure (VLAN, CoS, RSTP etc)
remains unchanged compared to baseline (3820).
E1 E2 E3
E E E E E E
Up to 24 EPB blades
IuCS/Iur B
IuPS
CP-A
Iub
C1 C2 E E E E C1 C2
H Iub UP/CP - two IpAccessHostEt per EPB blade + 2 for NTP Server on C1 device processor
H IuPS UP - one IP host per EPB blade, only on secondary (PIU Device) processor
H Iu/Iur CP one (multi homed) IP host on each c1 and c2 EPB (two VLANs, CP-A and CP-B)
Node Internal VLAN
A node internal VLAN needs to be defined on all backplane and ISL ports (not
external ports). This is performed by creating a internal VLAN and setting the
IpAccessHostEt ExhangeTerminalIp
ipAddress
CnOperator ipInterfaceMoRef GigaBitEthernet
IuLink IpInterface
userPlaneTransportOption IpAccessHostPool
IpAccessHostEt defaultRouter0
userPlaneIpResourceRef ipAccessHostRef
ipAddress networkPrefixLength
Ranap ipInterfaceMoRef mtu, vlanRef
cnDomainInd=CS
IpInterface
defaultRouter0
IuLink networkPrefixLength
userPlaneTransportOption mtu, vlanRef
userPlaneIpResourceRef
IpAccessHostPool IpAccessHostEt
Ranap ipAddress IpInterface
cnDomainInd=PS ipAccessHostRef
ipInterfaceMoRef defaultRouter0
networkPrefixLength
mtu, vlanRef
IP Configuration on EPB Blade
IuPS (1..) IuCS (1..) Iur (1..n) Iub (1..n)
Sctp
Sctp Sctp
IpAccessSctp
IpAccessSctp IpAccessSctp
Rpu
Rpu Rpu
Slot
Slot Slot
IpAccessHostEt IpAccessHostEt IpAccessHostEt PlugInUnit
PlugInUnit PlugInUnit
IpInterface
IpAccessHostEt IpInterface IpAccessHostEt IpInterface IpAccessHostEt
IpInterface
IpInterface IpInterface
PiuDevice
PiuDevice PiuDevice IpAccessHostEt
IpAccessHostEt IpAccessHostEt
IpInterface
IpInterface IpInterface
IpAccessHostEt
IpAccessHostEt IpAccessHostEt IpInterface
IpInterface IpInterface
IpAccessHostEt IpInterface
IpAccessHostEt IpInterface IpAccessHostEt IpInterface
C1 (Slot 3)
C2 (Slot 4) C1 (Slot 25) C2 (Slot 26)
SS7/SCTP Configuration Four single
SCTP Front Ends
Four FE defined
One on each EPB with C1 and C2 role (Slots 3,4,25 and 26 in MS)
RncFunction
CnOperator SccpSp
IuLink mtp3bSpId
Ranap SccpScrc Mtp3bSpItu
localSccpApRef SccpApLocal
remoteSccpApRef ssN Mtp3bAp
serviceIndicator
SccpApRemote routeSetId
ssN
mtp3bApId
Mtp3bSrs
destPointCode
Mtp3bSr Mtp3bSr Mtp3bSr Mtp3bSr
linkSetM3UId linkSetM3UId linkSetM3UId linkSetM3UId
priority priority priority priority
RncFunction
CnOperator SccpSp
IuLink mtp3bSpId
Ranap SccpScrc
Mtp3bSpItu
localSccpApRef SccpApLocal
remoteSccpApRef ssN Mtp3bAp Mtp3bAp
serviceIndicator serviceIndicator
SccpApRemote routeSetId routeSetId
ssN
mtp3bApId
IuLink
Mtp3bSrs Mtp3bSrs
Ranap destPointCode destPointCode
localSccpApRef
remoteSccpApRef SccpApRemote Mtp3bSr Mtp3bSr Mtp3bSr Mtp3bSr Mtp3bSr Mtp3bSr Mtp3bSr Mtp3bSr
ssN
mtp3bApId
RncFunction
SccpSp
IurLink mtp3bSpId
Rnsap SccpScrc
Mtp3bSpItu
localSccpApRef SccpApLocal
remoteSccpApRef ssN Mtp3bAp Mtp3bAp
serviceIndicator serviceIndicator
SccpApRemote routeSetId routeSetId
ssN
mtp3bApId
IurLink
Mtp3bSrs Mtp3bSrs
Rnsap destPointCode destPointCode
localSccpApRef
remoteSccpApRef SccpApRemote Mtp3bSr Mtp3bSr Mtp3bSr Mtp3bSr
ssN linkSetM3UId linkSetM3UId linkSetM3UId linkSetM3UId
mtp3bApId priority priority priority priority
Slot=MS3 Slot=MS25
PlugInUnit PlugInUnit
ExchangeTerminalIp ExchangeTerminalIp
GigaBitEthernet GigaBitEthernet
PiuDevice PiuDevice
IpAccessHostEt
IpAccessHostEt
ipAddress ExhangeTerminalIp ExhangeTerminalIp
ipInterfaceMoRef ipAddress
ntpServerMode=ENABLED ipInterfaceMoRef
GigaBitEthernet GigaBitEthernet
ntpServerMode=ENABLED
IpInterface IpInterface
defaultRouter0 defaultRouter0
networkPrefixLength networkPrefixLength
mtu, vlanRef mtu, vlanRef
For configuration of Iub control plane and user plane the following data must
be known:
ipAddress: The IP address for the host of the Iub control plane and user
plane. Two for each EPB are needed.
routerIpAddress: The IP address to the default router. One mandatory
address can be configured. If no router is going to be used in the network a
fictitious address must be used, because this attribute is used to determine
the subnet mask.
networkPrefixLength: Used to specify which part of the routerIpAddress is
the subnet address.
IUB User Plane
When the Iub control plane is configured using
IpAccessHostEt on EPB, the additional
IpInterface and IpAccessHostEt are required for
the Iub user plane.
The typical situation is to have one
IpAccessHostPool for Iub user plane. One
IpAccessHostEt is defined on primary processor
for Iub Control Plane and Iub User Plane, and
one IpAccessHostEt on secondary processor
used only for Iub User Plane.
Iub User and Control Plane
1. Create one IpInterface MO for primary processor (PIU) and one for
secondary processor (PiuDevice).
2. Create two IpAccessHostEt for each EPB
SET ipInterfaceMoRef as the interface on the EPB created.
3. Create one IpAccessHostPool for Iub, including all IpAccessHostEt
defined on EPB_BLADE_A in both processors created.
4. Create IpAccessSctp MO for each EPB
Set ipAccessHostEtRef1 to IpAccessHostEt defined on Primary processor.
5. Create one Sctp MO for each EPB
Set ipAccessSctpRef to IpAccessSctp defined above.
6. Add In the IubLink MO created above add a reference to the
IpAccessHostPool MO, by setting the userPlaneIpResourceRef attribute.
Set the IP addresses for the Iub control plane and the attributes:
userPlaneTransportOption and controlPlaneTransportOption to IPv4.
Iu/Iur Control Plane
Horizontal Distribution (HD) stack is divided into two parts, Front End (FE) and Back
End (BE).
The FE handles the communication with the CN and containsthe SCTP-stack.
The BE contains the SCC server. One SCTP (FE) executes on each C1 and C2 EPB
(four EPBs in total).
On each EPB used as Front End (FE) the following MOs are needed.
References
1. Initial IP Configuration, 57/1543-AXD 105 03/1 Uen A
2. Hardware Configurations for Evo Controller 8200 for RNC, 2/155 18-COA
109 400 Uen
3. NDS IP Termination on EPB1 in Evo, 50/102 68-FCP 101 8201 Uen
4. IP EPB SW, IP Termination, 20/159 41-FCP 105 1096 Uen