Integrating The MCRNC To The Ran and CN PDF

Integrating the mcRNC to RAN and CN
RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

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
self-development 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.
2 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

Integration
Recovery Groups
VLAN Ethernet Connectivity
SS7 Signalling configuration
OSPF, VRRP/HSRP site solutions
Radio Network Database
Final checks

Integration
Recovery Groups
Final checks

Recovery Groups in mcRNC
• The mcRNC high availability is

implemented by using a Recovery
Group (RG) concept.
• A Recovery Group instance is
associated with certain Functional
Units.
• The service related to the RG is
running in the active Recovery Unit
(RU).

QNUP Recovery Units (user plane) allocation in 2
BCN modules setup

The QNUP Recovery Groups terminate the user plane services of all
mcRNC logical interfaces.
The QNUP Recovery Groups have the following functions and
characteristics:
• It is bound to EIPU nodes
• Holds the termination of IP addresses at the IP layer
• terminates the User Plane connections from any logical interface from
several neighboring nodes
• Has a hot active/standby redundancy scheme for end user connection
resilience

QNIUB Recovery Units (IUB control plane)
allocation in 2 BCN modules setup

The QNIUB Recovery Groups terminate the Iub control plane services at
the IP/SCTP layer.
The QNIUB Recovery Groups have the following functions and
characteristics:
• It is bound to EIPU nodes
• It holds the termination of Control Plane IP addresses at the IP layer
• Terminates connections from several BTSs
• Has a cold active/standby redundancy scheme for end user connection
resilience Cold active/standby redundancy scheme is sufficient for Iub
control plane resilience.
The provided redundancy mechanism is transparent to a BTS.

SCTP multihoming redundancy (Iu and Iur control
plane)

The Iu/Iur control plane traffic termination and the SIGTRAN stack
implementation is located in EIPU nodes. The control plane traffic is
terminated directly at the network interface IP addresses, configured to
these EIPU nodes. The transport network redundancy is provided by
SCTP multihoming, the service level redundancy and load sharing is
handled at the M3UA/SCCP layer.
The SCCP layer contains a hot active/standby redundancy scheme in

order to provide full RANAP/RNSAP resilience. The SCCP layer
redundancy scheme is implemented by the QNIU Recovery Group,
which is automatically maintained by the system. The NIU RG does not
contain the IP addresses and does not require any configuration by the
user.

mcRNC provides three redundancy models:
1. Hot active/standby
- Comprises exactly two recovery units offering identical service
- State and process data is synchronized between active & standby
-Enables uninterrupted service in case of unit failure
2. Cold active/standby
- Comprises exactly two recovery units offering identical service
- Processes in standby unit are not running
-Standby unit needs „warming“ in case of failover
3. . No redundancy
- Allows to configure node-local services
- Processes / recovery units are restarted in case of failure
Examples:
1. Iub user plane termination is configured to hot active/standby
- Keeps end user connections alive also in case of RNC internal failures
2. Iub control plane termination is configured to cold active/standby
- NBAP implementation is tolerant to SCTP layer re-establishment, thus
hot standby not required
- Saves resources

IP interface hierarchy

Link aggregation groups (LAG) provide increased bandwidth and high
reliability by combining several interfaces into one logical link. The
mcRNC Ethernet ports can be aggregated into LAGs to provide more
than 1 Gigabit bandwidth per logical interface. The Link Aggregation
Control Protocol is used to manage LAGs. Up to eight 1GE ports of the
same mcRNC module can be aggregated within a one LAG. A maximum
of eight LAGs can be supported for the mcRNC within the same module.

mcRNC redundant configuration

Basic Routing Configuration

The basic routing configuration provides redundancy via static
routes as shown in this routing example. It is assumed that the
active recovery unit is located in EIPU processing unit zero and
the standby recovery unit is located in EIPU unit one. Note the
single IP address pointing to the recovery group. The network
interface IP addresses are also shown in the example.
In the egress direction there are two high priority routes via site
switch 1.
In the ingress direction there is one high priority route and one low
priority route via site switch 1.
The routes are configured in a similar way via site switch 2.
The internal routing takes place via the 10 Gigabit Ethernet
backbone.

Network Failure Cases: Application Failure

Network Failure Cases: Network Failure

Network Failure Cases: Network Failure, cont.
As a network failure case we assume that a site switch

– say site switch 1 – fails. Again, the loss of signal
recognition causes the stopping of all routing through
the affected network interfaces. All ingress and egress
IP traffic is now routed via site switch 2.

fsclish
• FlexiServer Command Line Interface Shell

• Local Operation and Maintenance interface
• To be executed from CFPU unit
[root@CFPU-0(MCRNC-91) /root]
# fsclish
• Press <tab> key to get help
• Type one command and press <tab> to see the options
• A full command can be also typed at once

Integration
Recovery Groups
Final checks

Map mcRNC units to SFPs and Ports
Map mcRNC units with VLAN interfaces and VLAN tags
Assign IP addresses for mcRNC VLAN interfaces
Create mcRNC static routes towards elements
Add IP-based routes
Create Iub subnetwork
Add NTP and DNS server

Map mcRNC units to SFPs and Ports
add networking ether /EIPU-0 iface ethsfp7 port sfp7
• Maps external interface with the internal logical port to a functional unit
• This command needs to be executed for the EIPU units (interface units)
and for as many ports as needed
• For CFPU units (O&M), the ethernet port eth0 are predefined. No
configuration is needed
• This will connect the functional unit from an internal port to the actual
external interface port where the interface is connected (Iu-CS, Iu-PS, Iur,
Iub)
• Port number varies according to BCN variants: sfp7 to sfp22 for BCN-A,
sfp11 to sfp22 for BCN-B

Map mcRNC units with VLAN interfaces and VLAN
tag (optional)
add networking vlan /EIPU-0 realiface ethsfp7 vid 612
vlaniface iucsup_r1
• Defines a VLAN in the external interface (ethsfp7)

• Tags it with a VLAN Id (612)
• Assigns a name to interface (iucsup_r1)

Assign IP addresses to interfaces
add networking address dedicated /EIPU-0 iface iucsup_r1

ip-address 10.2.36.74/27 (VLAN example)
add networking address dedicated /EIPU-0 iface ethsfp8
ip-address 10.2.36.74/27 (no VLAN)
• In case VLAN is in use, iface should be the vlaniface previously

defined, otherwise use the logical ethsfp port previously defined
• Assigns a dedicated IP address and netmask to the previously defined
VLAN interface or ethernet interface for Operation and Maintenance
access to different Recovery Users in the CFPU unit

Assign logical IP addresses for recovery groups
add networking address dedicated /QNUP-0 iface lo ip-

address 10.2.36.193/32 role iucsup
• The IP address is assigned to the Recovery Group

• This needs to be defined for:
• at least one /QNUP for User Plane in the Iu-CS, Iu-PS and Iur
• at least one /QNIUB
• /SSH for remote connections
• two different /QNOMU for OMS and BTS O&M link

Create mcRNC static routes towards elements
Default route
set routing node CFPU-0 static-route default
nexthop gateway address 10.16.67.17 on
Route to a specific subnet

set routing node CFPU-0 static-route 10.2.34.112/28
• Defines a static routes from the functional unit to the gateway

• Static route can be configured as default or to a specific subnet
• This has to be defined in:
• CFPUs (for O&M)
• EIPUs (for Iu-CS, Iu-PS, Iur and Iub both for Control Plane and User Plane)

Add IP-based routes
add networking ipbr ipbr-id 2 committed-bandwidth 100000

committed-dcn-bandwidth 0 committed-sig-bandwidth 0
ipbr-name IUCSUP route-bandwidth 300000
add networking ipro ipbr-id 2 ip-address 10.16.67.14
iface csup1_r1 owner /QNUP-1
• IP based route needs to be defined for all User Plane interfaces (Iu-CS, Iu-
PS, Iur and Iub) with the following parameters:
• Committed bandwidth
• committed DCN bandwidth
• committed signalling bandwidth
• total route bandwidth
• After this, the IP based route has to be associated to the IP address and
interface and the Recovery Group handling it

Create Iub subnetwork (optional)
add networking iubsnt iubsnt-id 1 net-address

10.16.67.48/28
A local Iub subnetwork can be defined with SCTP parameters to be used for
the Iub control plane subnetwork. If not defined, default values are used.

Configuring O&M connections
• O&M connections must be configured in CFPU-0 and CFPU-1

• eth0 port is used, VLAN is optional
• IP address for RG /SSH must be defined for SSH connection to CFPUs
add networking address dedicated /SSH iface lo ip-
address <ip_address> role ssh
• IP addresses for RG /QNOMU must be defined: northbound IP for OMS
and southbound IP for Node B. Southbound IP is optional and if not
configured the same IP (with role oms) will be used for both interfaces
add networking address dedicated /QNOMU iface lo ip-
address <southbound_ip> role btsom
add networking address dedicated /QNOMU iface lo ip-
address <northbound_ip> role oms user /QNHTTPD
• Static routing or OSPF is required to route to destinations (OMS, Node B,
user PCs) via site routers/switches
• Connect to OMS
set radio-network omsconn omsipadd <oms_ip_address>
rncid <rnc_id>
Configuring DNS and NTP
• Add an NTP server to synchronize the mcRNC time

add networking-service ntp forwarder 10.8.147.40
• Enable DNS
add networking-service dns forwarder 10.8.144.20

Link Aggregation Group (optional)
• Link aggregation group (LAG) provides increased bandwidth and high

reliability
• Up to eight 1GE ports of the same mcRNC module can be aggregated
• The configured LAG can then be assigned VLANs and IP addresses
similar to ordinary SFP or SFP+ ports
add networking ether /EIPU-0 iface ethsfp7_r1 port sfp7

add networking linkaggr /EIPU-0 iface lag1 slave
ethsfp7_r1 slave ethsfp8_r1 slave ethsfp9_r1 slave
ethsfp10_r1
add networking vlan /EIPU-0 realiface lag1 vid 11
vlaniface iuup_r1

Virtual Routing and Forwarding (optional)
• Virtual routing and forwarding (VRF) is used to divide routing tables into
several separate tables
• VRF is required in OSPF configuration to separate dynamic routing part
with internal static routing
• Each VRF instance requires an ID range 1-63. VRF1 to 4 is required for
Iu/Iur control planes. ID=0 is default instance (when VRF is not used,
reserved for management plane if VRF is used.)
• VRF applies to vlan, linkaggr, address, ipro, routing, signaling, iubsnt, etc.
add networking vrf name iuup id 5
add networking instance iuup vlan /EIPU-0 realiface
ethsfp7_r1 vid 11 vlaniface iuup_r1
add networking instance iuup address dedicated /EIPU-0
iface iuup_r1 ipaddress 10.0.1.2/28
set routing instance iuup node EIPU-0 static-route
10.1.1.0/24 nexthop gateway address 10.0.1.1 on
Link State Detector (optional)
• Link state detector is used to notify recovery group about interface state
changes. Once the interface state goes down, the active RU of the RG
instance is moved to the EIPU-pair node.
• Link state detector is required in VRRP/HSRP and L3 OSPF site solution
• Link state detector is applied for 1GE, LAG or 10GE interfaces with QNUP
and QNIUB as owner

add networking link-state-detector /QNUP-0 iface ethsfp7
add networking link-state-detector /QNIUB-0 iface ethsfp7

Ethernet Switch Port Group (optional) 1/2
• Ethernet switch port group contains one or more ports which can be in
different boxes
• All ports the port group share the same VLAN ID
• When a port group is mapped to a node, the node is able to receive traffic
from any port in the port group
• When a port group is mapped to multiple nodes, each node receives traffic
from the same port group
• Port group is used for 10GE port to share the port to two EIPUs (with
different control plane/user plane IP addresses)

Ethernet Switch Port Group (optional) 2/2
Example configuration:
add networking switch port-group name sfp11-
bcn1 port LMP-1-1-1:sfp11
add networking ether /EIPU-0 iface ethsfp11
port sfp11-bcn1 outqset rncdefault
add networking ether /EIPU-2 iface ethsfp11
port sfp11-bcn1 outqset rncdefault
add networking instance iuiurup vlan /EIPU-0
realiface ethsfp11 vid 11 vlaniface
iuiurup_vl11 mapping vlandscptopcp mtu 1560
add networking instance iuiurup vlan /EIPU-2
realiface ethsfp11 vid 11 vlaniface
iuiurup_vl11 mapping vlandscptopcp mtu 1560
add networking instance iuiurup address
dedicated /EIPU-0 iface iuiurup_vl11
ipaddress 10.0.1.2/28
add networking instance iuiurup address
dedicated /EIPU-2 iface iuiurup_vl11
ipaddress 10.0.1.3/28

Example 1: 2 box configuration, Evolved Site
Solution

Example 1: port creation
# port creation

Example 1: IUCS control plane integration

Example 1: vlan, IP and routing for IUCS control
plane
# vlan: iucscp1
add networking vlan /EIPU-0 realiface ethsfp7 vid 10 vlaniface iucscp1_r1
# vlan: iucscp2
# IP: iucscp1
add networking address dedicated /EIPU-0 iface iucscp1_r1 ip-address
10.16.224.2/28 user /SS7SGU
10.16.224.3/28 user /SS7SGU
# IP: iucscp2
10.16.224.18/28 user /SS7SGU
10.16.224.19/28 user /SS7SGU
# iucscp1, iucscp2 routing
set routing instance default node EIPU-0 static-route 10.20.153.48/32 nexthop
gateway address 10.16.224.1 on
Example 1: IUCS user plane integration

Example 1: vlan and IP for IUCS user plane
# vlan: iucsup
add networking vlan /EIPU-0 realiface ethsfp7 vid 60 vlaniface
iucsup_r1
iucsup_r1
iucsup_r2
iucsup_r2
# IP: iucsup
add networking address dedicated /EIPU-0 iface iucsup_r1 ip-address
10.16.224.162/28
10.16.224.163/28
10.16.224.178/28
10.16.224.179/28
# lo: iucsup
add networking address dedicated /QNUP-0 iface lo ip-address
10.16.225.190/32 role iucsup

Example 1: routing and IPBR for IUCS user plane
# iucsup routing
gateway address 10.16.224.161 bfd-detect-mult 3 bfd-rx-interval 150 bfd-tx-
interval 150 bfd-monitoring enabled on
interval 150 bfd-monitoring enabled priority 4 on
gateway address 169.254.0.7 priority 8 on
interval 150 bfd-monitoring enabled on
interval 150 bfd-monitoring enabled priority 4 on
# lo routing iucsup
# ipbr
add networking ipbr ipbr-id 1 committed-bandwidth 100000 committed-dcn-bandwidth 0
committed-sig-bandwidth 0 ipbr-name IUCSUP route-bandwidth 300000
add networking ipro ipbr-id 1 ip-address 10.16.225.190 iface lo owner /QNUP-0

Integration
Recovery Groups
Final checks

SS7 Integration
1. Create an SAP
2. Create local and remote AS
3. Create associations
4. Create own point code and subsystem for the local AS
5. Create destination point code and subsystem for the remote
AS
6. Add concerned point codes
7. Add concerned subsystems
8. Enable the associations

Example 1: IUCS control plane integration

Example 1: IUCS control plane
# service-access-point creation (sap)
add signaling service-access-point id 1 name sap_iucs network-
appearance 1 network-indicator NA0 network-type itu
# m3ua-local-as creation (las)

add signaling ss7 local-as id 1 name las_iucs routing-context 2
routing-key-dpc 1108 service-access-point-name sap_iucs traffic-mode
loadshare
# m3ua-remote-as creation (ras)

add signaling ss7 remote-as id 4 name ras_iucs communication-type ipsp
pending-timer 3 routing-context 2 routing-key-dpc 913 service-
access-point-name sap_iucs traffic-mode loadshare
# sctp-association
add signaling ss7 association id 11 local-as-name las_iucs
communication-type ipsp local-ip-addr 10.16.224.2 local-ip-addr
10.16.224.18 local-client-port 49225 remote-as-name ras_iucs remote-
ip-addr 10.20.153.48 remote-ip-addr 10.20.153.188 remote-port 2905
node /EIPU-0 role client exchange-mode double sctp-profile SS7
add signaling ss7 association id 12 local-as-name las_iucs
communication-type ipsp local-ip-addr 10.16.224.3 local-ip-addr
10.16.224.19 local-client-port 49225 remote-as-name ras_iucs remote-
ip-addr 10.20.153.47 remote-ip-addr 10.20.153.187 remote-port 2905
node /EIPU-1 role client exchange-mode double sctp-profile SS7

# sccp-opc creation (own pointcode)

add signaling sccp own-point-code id 1 type primary local-as-name
las_iucs
# sccp-dpc creation (destination pointcode)

add signaling sccp destination-point-code id 6 remote-as-name ras_iucs
# ssn-for-sccp-opc creation (sccp subsystem for local)

add signaling sccp subsystem id 1 name opc_iucs point-code-name
las_iucs ssn 142
# ssn-for-sccp-dpc creation (sccp subsystem for destination)

add signaling sccp subsystem id 6 name dpc_iucs point-code-name
ras_iucs ssn 142

# concerned-subsystem creation
add signaling sccp concerned-subsystem name css_iucs subsystem-name
opc_iucs affected-subsystem-name dpc_iucs
# conserned-point-code creation
add signaling sccp concerned-point-code name cpc_iucs point-code-name
ras_iucs affected-subsystem-name opc_iucs
# enable associations (admin-state)

set signaling ss7 association admin-state enabled id 11

Exchange-mode configuration
Important parameter in the remote-asp configuration is exchange-mode. This can be either

Single or Double and matches with the Core Network parameter ASP MESSAGES IN IPSP.
This can be seen from the core network element using the command
ZOYI:NAME=>name_of_RNC>:A;
Yes – double mode
No – single mode
This can be changed in the script under section #sctp-association creation by modifying
the exchange-mode parameter
add signaling ss7 association id <MSS/SGSN/IUR_ASSOCIATION_SET_ID>
localas-name las_iucs communication-type ipsp local-ip-addr
<mcRNC_INTERFACE_IP_IUCS> local-client-port 49225 remote-as-name
ras_iucs remote-ip-addr <MSS_IP_ADDRESS> remote-port 2905 node
/EIPU-0 role client exchange-mode <Double/Single>

Integration
Recovery Groups
Final checks

Example 2: 2 box configuration, OSPF Site
Solution with VRF, 10GE and shared EIPU

Example 2: VRF, port group, port creation
# VRF creation
add networking vrf name iuiurup id 5
add networking vrf name iuiurcp id 1
add networking vrf name iub id 11
# Add shared port group to first BCN module
add networking switch port-group name sfp11-bcn1 port LMP-1-1-1:sfp11
# Add shared port group to second BCN module
add networking switch port-group name sfp11-bcn2 port LMP-1-2-1:sfp11
# Assign shared 10GE port to EIPU nodes of first BCN module
add networking ether /EIPU-0 iface ethsfp11 port sfp11-bcn1 outqset
rncdefault
rncdefault
# Assign shared 10GE port to EIPU nodes of second BCN module
rncdefault
rncdefault

Example 2: link state detector, VLAN part 1

# vlan 11&12, iu iur user plane

add networking instance iuiurup vlan /EIPU-0 realiface ethsfp11 vid 11
vlaniface iuiurup_vl11 mapping vlandscptopcp mtu 1560

Example 2: VLAN part 2
# vlan 17&18, iu iur control plane

add networking instance iuiurcp vlan /EIPU-0 realiface ethsfp11 vid 17
vlaniface iuiurcp_vl17 mapping vlandscptopcp
# vlan 21&22, iub control and user plane
add networking instance iub vlan /EIPU-0 realiface ethsfp11 vid 21
vlaniface iub_vl21 mapping vlandscptopcp

Example 2: IP address for VLAN
# VLANs 11 and 12
add networking instance iuiurup address dedicated /EIPU-0 iface iuiurup_vl11 ipaddress
10.0.1.2/28
10.0.1.3/28
10.0.1.18/28
10.0.1.19/28
# VLANs 17 and 18
add networking instance iuiurcp address dedicated /EIPU-0 iface iuiurcp_vl17 ipaddress
10.1.8.2/28
10.1.8.130/28
10.1.8.3/28
10.1.8.131/28
# VLANs 21 and 22
add networking instance iub address dedicated /EIPU-0 iface iub_vl21 ipaddress 10.0.4.2/28

Example 2: Iu/Iur user plane

Example 2: IP address for Iu/Iur user plane 1/2
# Iu-PS user plane IP addresses, VRF iuiurup

add networking instance iuiurup address dedicated /QNUP-0 iface lo ip-
address 10.1.1.1/32 role iupsup
# Iu-CS user plane IP addresses, VRF iuiurup

Example 2: IP address for Iu/Iur user plane 2/2
# Iur user plane IP addresses, VRF iuiurup

address 10.1.1.33/32 role iurup

Example 2: Iub

Example 2: IP address for Iub, IUBSNT
# Iub control and user plane IP addresses, VRF iub

add networking instance iub address dedicated /QNUP-0 iface lo ip-
address 10.1.0.1/32 role iubup
add networking instance iub address dedicated /QNIUB-0 iface lo ip-
address 10.1.0.65/32 role iubcp
add networking iubsnt iubsnt-id 1 net-address 10.1.0.0/24 rto-initial
2000 rto-min 1759 rto-max 3000 association-max-retrans 7 path-max-
retrans 7 heartbeat-interval 2000 sack-period 400 max-frame-size
1452
Example 2: Iu/Iur control plane

Example 2: IP address for Iu/Iur control plane
SCTP interface
Only Iu-PS is shown as example. Adjust IP addresses for Iu-CS and Iur.
# Iu-PS Control plane IP addresses

add networking instance iuiurcp address dedicated /EIPU-0 iface sctp1_1
ip-address 10.1.8.17/28 role iupscp user /SS7SGU

Example 2: Static routing Iu/Iur control plane
# Control plane, routes may serve several destination CN elements

depending on the network planning
set routing instance iuiurcp node EIPU-0 static-route 10.8.0.0/24
Example 2: OSPF router id
# Router id values for iuiurup VRF

set routing instance iuiurup node EIPU-0 router-id 10.0.1.2
# Router id values for iub VRF
set routing instance iub node EIPU-0 router-id 10.0.4.2

Example 2: OSPF area
# iuiurup areas
set routing instance iuiurup node EIPU-0 ospf area 10.0.1.0 on
set routing instance iuiurup node EIPU-0 ospf area 10.0.1.0 stub on
#iub areas
set routing instance iub node EIPU-0 ospf area 10.0.4.0 on
set routing instance iub node EIPU-0 ospf area 10.0.4.0 stub on
Example 2: OSPF loopback interface activation
# iuiurup VRF loopback interface

set routing instance iuiurup node EIPU-0 ospf interface lo area
10.0.1.0 on
10.0.1.0 on
10.0.1.0 on
10.0.1.0 on
# iub VRF loopback interface
set routing instance iub node EIPU-0 ospf interface lo area 10.0.4.0 on

Example 2: OSPF VLAN interface activation
# iuiurup VRF VLAN interfaces

set routing instance iuiurup node EIPU-0 ospf interface iuiurup_vl11
area 10.0.1.0 on
area 10.0.1.0 on
area 10.0.1.0 on
area 10.0.1.0 on
# iub VRF VLAN interfaces
set routing instance iub node EIPU-0 ospf interface iub_vl21 area
10.0.4.0 on
10.0.4.0 on
10.0.4.0 on
10.0.4.0 on

Example 2: OSPF BFD monitoring
# VRF iuiurup
set routing instance iuiurup node EIPU-0 ospf interface iuiurup_vl11 bfd-
detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval
150
150
150
150
# VRF iub
set routing instance iub node EIPU-0 ospf interface iub_vl21 bfd-detect-mult
3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150

Example 2: OSPF parameters 1/2
# VRF iuiurup
priority 0
priority 0
priority 0
priority 0
# VRF iub
set routing instance iub node EIPU-0 ospf interface iub_vl21 priority 0

Example 2: OSPF parameters 2/2
# VRF iuiurup
cost 2
cost 2
cost 2
cost 2
# VRF iub
set routing instance iub node EIPU-0 ospf interface iub_vl21 cost 2

Example 2: user plane
Only Iu-PS is shown as example. Adjust IP addresses for Iu-CS, Iur and Iub.
add networking ipbr ipbr-id 1 route-bandwidth 0 committed-bandwidth 0

committed-dcn-bandwidth 0 committed-sig-bandwidth 0 ipbr-name
iupsipbr-1 scheduler-type none
add networking ipro ipbr-id 1 ip-address 10.1.1.1 iface lo5 owner
/QNUP-0 vrf iuiurup
/QNUP-1 vrf iuiurup
/QNUP-2 vrf iuiurup
/QNUP-3 vrf iuiurup

Example 2: Iu/Iur control plane 1/2
Only Iu-PS is shown as example. Adjust IP addresses for Iu-CS, Iur and Iub.
add signaling sccp sccp-timer-profile name sccpprofile1 network-type

itu t-a 100 t-congestion 5 t-connect 80 t-d 5 t-guard 1380 t-iar 700
t-ias 300 t-interval 50 t-reassembly 10 t-release 10 t-repeat-
release 10 t-reset 10
add signaling service-access-point id 1 name SAPRNC1 network-appearance
1 network-indicator NA0 network-type itu sccp-timer-profile-name
sccpprofile1
add signaling ss7 local-as id 1 name LASRNC1 routing-context 1 routing-
key-dpc 310 service-access-point-name SAPRNC1 traffic-mode loadshare
add signaling ss7 remote-as id 1 name SGSN1 communicationtype ipsp
pending-timer 3 routing-context 2000 routing-keydpc 500 service-
access-point-name SAPRNC1 traffic-mode loadshare

Example 2: Iu/Iur control plane 2/2
add signaling ss7 association id 21 local-as-name LASRNC1
communication-type ipsp local-ip-addr 10.1.8.2 local-ipaddr
10.1.8.145 local-client-port 49225 remote-as-name SGSN1 remoteip-
addr 10.8.0.1 remote-ip-addr 10.8.1.1 remote-port 2905 node /EIPU-0
role client exchange-mode single
add signaling ss7 association id 22 local-as-name LASRNC1
communication-type ipsp local-ip-addr 10.1.8.18 local-ipaddr
10.1.8.130 local-client-port 49225 remote-as-name SGSN1 remoteip-
addr 10.8.0.2 remote-ip-addr 10.8.1.2 remote-port 2905 node /EIPU-1
role client exchange-mode single
add signaling sccp own-point-code id 1 local-as-name LASRNC1
add signaling sccp destination-point-code id 4 remote-asname SGSN1
add signaling sccp subsystem id 1 name SSN310510 point-codename LASRNC1
ssn 142
add signaling sccp subsystem id 2 name SSN500310 point-codename SGSN1
ssn 142
add signaling sccp concerned-subsystem name CSS1 subsystemname
SSN310510 affected-subsystem-name SSN500310
add signaling sccp concerned-point-code name CPC1 pointcode-name SGSN1
affected-subsystem-name SSN310510
Example 3: 2 box configuration, VRRP/HSRP Site
Solution with VRF, LAG and shared EIPU

Example 3: VRF, port creation part 1
add networking vrf name iuiurup1 id 5
add networking vrf name iuiurup1 id 6
add networking vrf name iuiurcp id 1
add networking vrf name iub1 id 11
add networking vrf name iub2 id 12
add networking ether /EIPU-0 iface ethsfp13_r1 port sfp13 outqset
rncdefault
rncdefault
rncdefault
rncdefault
rncdefault
rncdefault
rncdefault
rncdefault
Example 3: port creation part 2

rncdefault
rncdefault
rncdefault
rncdefault
rncdefault
rncdefault
rncdefault
rncdefault

Example 3: LAG, link state detector
add networking linkaggr /EIPU-0 iface lag01 slave ethsfp13_r1 slave

ethsfp14_r1 slave ethsfp15_r1 slave ethsfp16_r1 outqset rncdefault

Example 3: VLAN 1/2
# vlan 11&12, iu iur user plane
add networking instance iuiurup1 vlan /EIPU-0 realiface lag01 vid 11
vlaniface iuiurup_vl11 mapping vlandscptopcp
(similar configuration of vlan 11&12 for EIPU-2 and 3 omitted for brevity)
#vlan 17&18, iu iur control plane

add networking instance iuiurcp vlan /EIPU-0 realiface lag01 vid 17

Example 3: VLAN 2/2
# vlan 21&22, iub control and user plane

add networking instance iub1 vlan /EIPU-0 realiface lag01 vid 21
(configuration of vlan 21&22 for EIPU-2 and 3 omitted)

Example 3: IP address for VLAN
# VLANs 17 and 18
add networking instance iuiurcp address dedicated /EIPU-0 iface
iuiurcp_vl17 ipaddress 10.1.8.2/28
(IP addresses for VLAN 11, 12, 21, 22 are assigned via /QNUP and /QNIUB and are not
configured here)

Example 3: Iu/Iur user plane

Example 3: IP address Iu/Iur for user plane 1/2
Note that /QNUP, /QNIUB IP addresses are assigned for VLAN interface instead of lo
interface in other types of site solution
# Iu-PS user plane IP addresses, VRF iuiurup
add networking instance iuiurup1 address dedicated /QNUP-0 iface
iuiurup_vl11 ip-address 10.0.1.4/27 role iupsup
# Iu-CS user plane IP addresses, VRF iuiurup
iuiurup_vl11 ip-address 10.0.1.14/27 role iucsup

Example 3: IP address Iu/Iur for user plane 2/2
# Iur user plane IP addresses, VRF iuiurup

iuiurup_vl11 ip-address 10.0.1.24/27 role iurup

Example 3: Iub

Example 3: IP address for Iub
# Iub user plane IP addresses, VRF iub

add networking instance iub1 address dedicated /QNUP-0 iface iub_vl21
ip-address 10.0.4.4/27 role iubup
# Iub control plane IP addresses, VRF iub
add networking instance iub1 address dedicated /QNIUB-0 iface iub_vl21
ip-address 10.0.4.20/27 role iubcp
add networking instance iub2 address dedicated /QNIUB -1 iface iub_vl22


Example 3: IP address for Iu/Iur control plane
SCTP interface
#Iu-PS Control plane IP addresses


Example 3: Static routing user plane
Note that VRRP/HSRP group virtual address is used instead of router/switch

physical address. Only Iu/Iur user plane is shown as example. Adjust IP
addresses for Iub user plane and control plane.
set routing instance iuiurup1 node EIPU-0 static-route default nexthop

Example 3: Static routing Iu/Iur control plane


Example 3: user plane
add networking ipbr ipbr-id 1 route-bandwidth 0

committed-bandwidth 0 committed-dcn-bandwidth 0
committed-sig-bandwidth 0 ipbr-name iupsipbr-1
scheduler-type none
add networking ipro ipbr-id 1 ip-address 10.0.1.4 iface
iuiurup_vl11 owner /QNUP-0 vrf iuiurup1

Only M3UA association for Iu-PS is shown as example. Adjust IP addresses

for Iu-CS and Iur. Other parts of control plane configuration are the same as
other types of site solution
add signaling instance iuiurcp ss7 association id 21 local-asname LASRNC1
communication-type ipsp local-ip-addr 10.1.8.2 local-ip-addr 10.1.8.145
local-client-port 49225 remote-as-name SGSN1 remoteip-addr 10.8.0.1
remote-ip-addr 10.8.1.1 remote-port 2905 node /EIPU-0 role client
exchange-mode single
Integration
Recovery Groups
Final checks

RNW Database

Configuring Radio Network Database
Ways to configure Radio Network database

• RNW plan download in mcRNC
• RNW plan download with CM Operation Manager in NetAct
• Modifying RNW with web-based user interface in OMS
• Modifying RNW with CM Editor in NetAct
In NetAct, it is also possible to modify or plan download IP connectivity.

RNW Plan download in mcRNC (zplan.sh)
• A prepared network plan may be downloaded to the mcRNC

• Southbound GOMS IP address needs to be included in this plan so that
mcRNC can recognize what GOMS is connected to
• Plan should be copied to CFPU-0 /mnt/QNOMU/plan using scp
• Plan in XML format with file name RNWPLAND.XML
• Execute command:
zplan /mnt/QNOMU/plan/RNWPLAND.XML
• To see objects that have been written into the Radio Network Database,
execute command:
zdbindex

RNW Plan management with CM Operation
Manager

RNW modification with OMS web-based user
interface

RNW modification with CM Editor
RNW Database Objects - RNC parameters 1/2
Object Description
RNC refers to the logical object of RNC. Exceptionally, there are no create or
delete operations associated with the RNC object. The RNC managed object
contains RNC level parameters i.e. commissioning parameters, System
RNC
Information parameters, Location Services (LCS), Time of Arrival Window
Endpoint (TOAWE) and Time of Arrival Window Startpoint (TOAWS) related
parameters.
RNAC object maintains admission control parameters, Packet Data
Convergence Protocol (PDCP) and power control/balancing/allocation
RNAC
related parameters. This object is not a network topology object. Delete
operation is denied. The number of managed objects is 1.
RNFC object maintains all feature control parameters. This object is not a
RNFC network topology object. Delete operation is denied. The number of managed
objects is 1.
RNHSPA object maintains High Speed Packet Access parameters i.e. High
Speed Packet Access (HSPA), High Speed Uplink Packet Access (HSUPA),
RNHSPA Continuous Packet Connectivity (CPC) and Fractional Dedicated Physical
Channel (F-DPCH) related. This object is not a network topology object.
Delete operation is denied. The number of managed objects is 1.
RNW Database Objects - RNC parameters 2/2
Object Description
RNMOBI object maintains mobility management parameters. i.e.
handover, Compressed mode and mobile device control related. This
RNMOBI
object is not a network topology object. Delete operation is denied.
The number of managed objects is 1.
RNPS object maintains mandatory Packet Scheduler parameters and
Dynamic Link Optimization related parameters. This object is not a
RNPS
network topology object. Delete operation is denied. The number of
managed objects is 1.
RNRLC object maintains Radio Link Control parameters. This object
RNRLC is not a network topology object. Delete operation is denied. The
number of managed objects is 1.
RNTRM object maintains transmission parameters. This object is not
RNTRM a network topology object. Delete operation is denied. The number of
managed objects is 1.
Radio Network Centralized Entity Resource Management object
RNCERM
defines the parameters needed to implement CSCP load balancing.
RNW Database Objects - Interfaces 1/2
Object Description
PREBTS PREBTS object maintains BTS auto connection parameters.
CBCI object maintains the data related to the cell broadcast center
CBCI used in the service area broadcast feature. The maximum number of
CBCI objects is 4.
IUO object maintains data related to the Iu Operator (like plmn-id,
IUO
shared plmn id etc.) The maximum number of IUO objects is 4.
The IUCS managed object contains connection settings towards a
particular MGW. The IUPS managed object contains connection
IUCS, IUPS settings towards a particular SGSN. These objects contain the
configuration for the Iu-CS and Iu-PS interfaces. The maximum
number of IUCS and IUPS core managed objects in the RNC is 32.
The IUCSIP object contains the destination IP address list for the
IUCS item. The maximum number of such objects is 20.
IUCSIP, IUPSIP
The IUPSIP object contains the destination IP address list for the
IUPS item. The maximum number of such objects is 20.
RNW Database Objects - Interfaces 2/2
Object Description
The IUR managed object contains neighboring RNC-related parameters. The
maximum number of IUR managed objects in RNC is 32. If I-BTS sharing
IUR
feature is available, the maximum number of IUR managed objects in RNC is
300.
This object is used in configuring the IP Based Iu-CS and IP Based Iu-PS
IPQM
features. The maximum number of IPQM managed objects in the RNC is 8.
This object is used for configuring RAN1253: Iub Transport QoS feature. The
TQM
maximum number of TQM managed objects in the RNC is 4.
A logical connection configuration object (COCO) is created to reserve local
transmission resources for each WCDMA BTS. A COCO object displays the
transmission resources at the Iub interface, but not the actual radio network
COCO topology. This object is needed only when ATM transport is used for the BTS.
Before creating a COCO, the corresponding ATM interface has to be created.
The maximum number of radio network COCO objects in the RNW database
follows the number of supported BTSs under the RNC.
An IPNB object contains the NBAP link configuration for the WBTS with the IP-
IPNB based Iub interface. The maximum number of radio network IPNB objects in the
RNW database follows the number of the supported BTSs under the RNC.
RNW Database Objects - FMC, HOP
Object Description
A frequency measurement control (FMC) object contains information
concerning the frequency measurement functionality of the RNC. The maximum
number of frequency measurement objects within one category is 100. A logical
FMC object is created so that its parameters can be used in WCDMA cell
FMCS, FMCI, definitions. One FMC can be related to several WCDMA cells. FMC objects
FMCG must be created before they can be used by WCELs.
There are three types of FMC objects:
• FMCS = object for intra-frequency measurement control
• FMCI = object for inter-frequency measurement control
• FMCG = object for inter-system frequency measurement control (optional)
A handover path (HOP) object stores the values used in handover and call drop
decision making. The maximum number of HOP objects within one category is
100. A logical HOP object is created so that its parameters can be used in
adjacent WCDMA cell definitions. One HOP can be related to several adjacency
objects of the same group.
HOPS, HOPI, There are four types of HOP objects:
HOPG, HOPL • HOPS = object for intra-frequency HOP, which contains, for example,
parameters that affect hard handover decision and call drop decision
procedures
• HOPI = object for inter-frequency handover path
• HOPG = object for inter-system handover path (optional)
• HOPL = object for inter-system handover path to LTE network (optional)
RNW Database Objects - WBTS, WCEL
Object Description
A WCDMA BTS (WBTS) is the logical object of the WCDMA base
station. A logical WBTS object is created to manage a BTS-related
telecom and radio resource configuration. A WBTS can host WCDMA
cells. Depending on the transport technology used for the WBTS
WBTS
(ATM or IP), either COCO objects (ATM transport) or IPNB objects
(IP transport) can be related to the WBTS object. It is possible to
create a WBTS without a reference to any COCO objects when the
WBTS is not yet integrated to RNC(IPA-RNC only).
A WCDMA cell (WCEL) is the logical object of the WCDMA cell. A
logical cell object is created to define the configuration of the WCDMA
BTS site.
The following objects have to be created before creating WCELs:
WCEL • a parent WBTS
• IUCS (CS CN node to be used)
• IUPS (PS CN node to be used)
• FMCSs for RT and NRT traffic (also FMCI/FMCG if needed)
• used WRAB
RNW Database Objects - ADJ
Object Description
An adjacency for a WCDMA cell (ADJ) refers to a handover

relationship between two WCDMA cells. Adjacencies are defined for
neighboring cells. Depending on the type of cells for which this
relationship is defined, there are three different types of adjacencies:
• ADJS = object for intra-frequency adjacency
• ADJD = object for additional intra-frequency adjacency
• ADJI = object for inter-frequency adjacency
• ADJG = object for inter-system adjacency (optional)
ADJS, ADJD, • ADJL = object for inter-system adjacency to LTE network
ADJI, ADJG, ADJL
RNW Database Objects - Location Services
Object Description
A WSMLC object contains general purpose parameters used in the positioning
methods. The actual SMLC device does not exist, but the SMLC functionality in
the Interface Control and Signaling Unit (ICSU) is configured using WSMLC
WSMLC
parameters. In the RNW database, there can be only one WSMLC object.
WSLMC objects can only be created if feature RAN2.0041: LCS – Cell
Coverage Based (RTT) with Geographical Coordinates is supported.
WCEL-related parameters needed by location algorithms are defined in a
WLCSE object collection. The WLCSE parameters must be defined for each
cell used in location calculation in the RNC. The parameters must also be
defined for cells controlled by the neighboring RNCs used in location calculation
in the locating RNC.
A WLCSE object in a WLCSE object collection is identified by using the UTRAN

WLCSE cell identifier, which must be unique in the RNC (in the RNW database). In the
RNW database, there can be a total of 8000 WLCSE objects, of which 4800 are
for the RNCs own cells and 3200 for the neighboring RNCs' cells. The amount
of WLCSE objects was increased from 6000 to 8000 due the feature RAN1795:
RNC2600 coverage optimized solution.
WLCSE objects can only be created if feature RAN2.0041: LCS – Cell

Coverage Based (RTT) with Geographical Coordinates is supported.
RNW Database Objects - Misc. Objects 1/2
Object Description
WANE and WSG objects contain parameters used in IMSI-based handover,
WANE, WSG which is an optional feature. WANE and WSG objects can only be created if
feature RAN2.0060: IMSI Based Handover is supported.
RNW CM supports limiting access rights to the network (allowed/restricted)
broadcast to all user equipment (UE) in the system information message on an
access level basis. In a normal situation, the network access is allowed for all
access levels. If network access needs to be limited because of the
aforementioned reasons, the operator can activate the access control algorithm,
which allows and restricts the network access of access levels 0 to 9 users at
predefined intervals.
CMOB A CMOB object contains RNW parameters used in traffic restriction. Traffic
restriction is introduced in the optional feature RAN1128: Dynamic Access
Class Restriction, which means that this object is optional as well. One CMOB
object contains parameters for one restriction area. One WCDMA cell can be
connected up to three restriction areas, which must be of different types (CS-
DSAC, PS-DSAC and RNAR). The maximum number of CMOB objects under
one RNC is 13. If feature RAN801: Radio Network Access Regulation Function
is enabled in the RNC, the RNC creates three 'forced' CMOB objects during the
RNC startup or the RNC object creation.
RNW Database Objects - Misc. Objects 2/2
Object Description
A WRAB object contains connection-based quality control
parameters. The parameters define the service bearer and signaling
WRAB bearer quality targets and the related power control thresholds for
each transport channel configuration. The maximum number of
WRABs in the RNW database is 5.
WCEL Admission Control object servers for storing: cell-specific UL
WAC load control parameters, admission control parameters and several
state transition control parameters.
A virtual BTS. The common configuration for all WCDMA and I-HSPA
VBTS
BTSs is controlled by neighboring network elements.
A virtual cell. The common configuration for all WCDMA and I-HSPA
VCEL
cells is controlled by neighboring network elements.
Preferred Frequency Layer (PFL) object is created in order to define
preferred frequency layers for different UE capability and service
combinations (for example, HSDPA capable UE with NRT service).
PFL The PFL object can be created only when feature RAN2172: Multi-
Band Load Balancing has been installed in the RNC. PFL object is
under RNC object. Maximum number of PFL objects is 50 in the
RNC.
Integration
Recovery Groups
Final checks
Final checks after integration and plan
provisioning (1/2)
• Ping or traceroute to destination IP addresses of the relevant node units. -V
option is required when Virtual Routing and Forwarding is in used.
ping [-V <vrf_id>] –I <source> <destination>
traceroute [-V <vrf_id>] -s <source> <destination>
• Check state of the interfaces by using fsclish commands:
show networking interface iface <iface_name>
show networking vlan iface <iface_name>
show networking address iface <iface_name>
show routing node <node_name> route static
show routing node <node_name> static-route config all
show networking ipbr
show networking ipro
show signaling ss7 association all
show signaling sccp subsystem all
Final checks after integration and plan
provisioning (2/2)
• Show routing for the unit you are logged into
ip r
netstat –r
route
• Show interfaces and ports assigned to the different units
ip a
• To see the IP address of all loopback interfaces on a unit
ip a s lo
• Check if O&M link to OMS and BTS are up
netstat -nat | grep 8002
Module Version control
Version Date Status Contact
v0.1 26.Nov.2010 Draft Guillermo Ferrero-Ferri
V0.2 08.Dec.2010 Review after use Guillermo Ferrero-Ferri
V0.4 30.Jun.2011 Guilermo Ferrero-Ferri
V1.0 29.Sep.2011 Update to existing SW version Marek Janicki

Recovery groups section added
Examples of IP and SS7 integration
added
V2.0 20.Feb.2012 Update for mcRNC2.0 Marek Janicki
V2.1 11.Apr.2012 IP interface hierarchy and network Marek Janicki

failure cases added
V3.0 9 Jan 2014 Update to RU40 Kriang Lerdsuwanakij
114 / RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

Integrating The MCRNC To The Ran and CN PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Integrating The MCRNC To The Ran and CN PDF

Загружено:

Авторское право:

Доступные форматы

Integrating the mcRNC to RAN and CN

RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

Intellectual Property Rights

2 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

VLAN Ethernet Connectivity

SS7 Signalling configuration

OSPF, VRRP/HSRP site solutions

Radio Network Database

3 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

VLAN Ethernet Connectivity

SS7 Signalling configuration

OSPF, VRRP/HSRP site solutions

Radio Network Database

4 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

• The mcRNC high availability is

5 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

6 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

7 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

8 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

9 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

10 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

The SCCP layer contains a hot active/standby redundancy scheme in

11 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

12 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

13 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

14 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

15 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

16 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

17 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

18 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

19 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

As a network failure case we assume that a site switch

20 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

• FlexiServer Command Line Interface Shell

21 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

VLAN Ethernet Connectivity

SS7 Signalling configuration

OSPF, VRRP/HSRP site solutions

Radio Network Database

22 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

Map mcRNC units to SFPs and Ports

Map mcRNC units with VLAN interfaces and VLAN tags

Assign IP addresses for mcRNC VLAN interfaces

Create mcRNC static routes towards elements

Add IP-based routes

Create Iub subnetwork

Add NTP and DNS server

23 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

add networking ether /EIPU-0 iface ethsfp7 port sfp7

24 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

• Defines a VLAN in the external interface (ethsfp7)

25 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

add networking address dedicated /EIPU-0 iface iucsup_r1

• In case VLAN is in use, iface should be the vlaniface previously

26 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

add networking address dedicated /QNUP-0 iface lo ip-

• The IP address is assigned to the Recovery Group

27 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

Route to a specific subnet

• Defines a static routes from the functional unit to the gateway

28 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.

add networking ipbr ipbr-id 2 committed-bandwidth 100000

29 RN33823EN40GLA01 ©2014 Nokia Solutions and Networks. All rights reserved.