9500 MPR I&C SG StudentHandout

© Nokia 2017. All Rights Reserved.
© Nokia 2017. All Rights Reserved.

Hello everyone, first toure welcome to France.
I am: Mohamed OUBRAHIME from GPEC Team "global
product expertise center",
and AYMAN RADY , coworker from egypt.
in this week we will try to explain the installation and
commissioning of the 9500 MPR.
The course consists in two parts: a theorical and a practical
part, but the main objective is that you can leave this
room and be able to properly install and turn up the
product .
the last day , we’ll have theorical exam in order to assess
your level and enable us subsequently to improve the
content of our training.
Do not hesitate if you have any questions, we are here to

answer them.
Thank for your attention
1
Agenda Pages
• This page allows for the listing of the sections within a

presentation.
2
Agenda Pages

presentation.
3
4
5
Agenda Pages

presentation.
6
7
8
Agenda Pages

presentation.
9
10
11
Agenda Pages

presentation.
12
13
14
15
16
17
18
19
20
21
22
23
Agenda Pages

presentation.
24
25
26
27
Agenda Pages

presentation.
28
MPT-MC is similar to MPT-HC from architecture standpoint. MPT-MC has limited
capacity vs MPT-HC and is natively Ethernet powered (no Power Extractor is
required).
29 29
MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be
used as spare part of the MPT-HC. The differences are:
–MPT-HC V2 can be natively Ethernet powered through a proprietary
PFoE (or as alternative by using two cables, one cable for the Power
Supply and one optical cable for the Ethernet Traffic (as MPT-HC)
–MPT-HC V2 is XPIC-ready (by the installation of a dedicated module).
The XPIC connector will be used, when this feature will be available.
30
31
32
Agenda Pages

presentation.
33
34
35
36
Agenda Pages

presentation.
37
38
product .

answer them.
1
Agenda Pages

presentation.
2
Agenda Pages

presentation.
3
4
5
Agenda Pages

presentation.
6
Two possible MPT ports can be selected to be the protecting MPT, either
the second port on the same MPT-ACC card, or the corresponding port
on the horizontal neighbor MPT ACC. Leaving the remaining ports to be
used either in separate 1+0 directions or in another 1+1 direction
referred as the W configuration.
7
8
9
Agenda Pages

presentation.
10
11
12
Agenda Pages

presentation.
13
14
15
Agenda Pages

presentation.
16
17
18
Agenda Pages

presentation.
19
20
product .

answer them.
1
Agenda Pages

presentation.
2
Agenda Pages

presentation.
3
4
5
Agenda Pages

presentation.
6
7
8
9
10
Agenda Pages

presentation.
11
12
13
14
Agenda Pages

presentation.
15
16
Agenda Pages

presentation.
17
18
19
Agenda Pages

presentation.
20
21
22
23
Agenda Pages

presentation.
24
25
Agenda Pages

presentation.
26
27
Agenda Pages

presentation.
28
29
30
31
Agenda Pages

presentation.
32
33
34
Agenda Pages

presentation.
35
36
37
38
39
40
Agenda Pages

presentation.
41
42
Agenda Pages

presentation.
43
44
45
46
47
Agenda Pages

presentation.
48
49
50
Agenda Pages

presentation.
51
52
53
Agenda Pages

presentation.
54
55
product .

answer them.
1
Agenda Pages

presentation.
2
3
4
Agenda Pages

presentation.
5
6
7
Agenda Pages

presentation.
8
9
On the MPR equipment view, go to the SW download menu, and choose SW status option.
The resulting view shows the currently installed SW versions on the main and standby flash card
banks.
As we can see with this view, we have currently one bank of this new flash card occupied by the
SW version 3.0.
In order to reach the targeted SW version 3.4, we need to perform an upgrade to 3.4
Close this view and go back to the “SW download” menu and choose the “sever access
configuration” option.
In this view, you can set the parameters used for the FTP connection between the NEtO and the
NE.
Click the “use default” button to load the default parameters. And close the view.
Now go back to the SW download menu, and choose the “init SW download” option.
The resulting view shows the list of SWP added to your PC and ready to be downloaded to the
equipment.
If you cannot find the SWP 3.0 (which is our case here), click the ADD button, and browse for the
DSC file on the MPR 3.0 SWP CD ROM (referenced 3DB18819AAAA) under the path
ECT/SWDW/R95MSS/3_0_0
Open the DSC file to add it to your NEtO CT.
Now we can see in the list that the 3.0 SWP is installed on the CT and ready to be downloaded.
To initiate the download of the 3.0 SWP click the “init download” button.
Wait for the files to be transferred to the flash card, noting that this operation takes about 6
minutes.
When the SWP download is successfully completed, go to the “SW download menu” and check
the “SW status” option again.
Now you can see that your flash card is having on its first bank the SWP 3.0 with the state
“Commit”… which means that this is the currently active SWP.
10
11
12
13
Agenda Pages

presentation.
14
15
Agenda Pages

presentation.
16
17
18
19
20
21
Agenda Pages

presentation.
22
23
24
25
Agenda Pages

presentation.
26
27
28
29
Agenda Pages

presentation.
30
The XPIC function can be applied to MPTs involved in the following radio
configurations:
– 2x(1+0)
– Radio LAG
– 2x(1+1) HSB (each polarisation is protected with HSB)
The HSB configuration is supported:
– with single and double antenna
– with balanced and unbalanced couplers
31
configurations:
– 2x(1+0)
– Radio LAG
32
configurations:
– 2x(1+0)
– Radio LAG
33
The XPIC function can be configured in both cases MPT is connected to
MPT Access unit port or Core unit port that has been provisioned for
connection to MPT.
The XPIC function can be configured in the cases where an MPT is
connected to an EAS unit port, that has been provisioned for
connection to MPT.
The XPIC function can be configured on MPT in protected configurations.
The following configuration sequence is supported:
1 configuration of protection between mate MPTs
2 configuration of XPIC on the protected radio direction.
Regarding 2x(1+1) HSB, this is the equipment configuration to be
supported: use of two MPT Access
peripheral boards with two connected MPTs for each board and with
inter-plugin protection scheme (protected
MPT pair is connected to different plug-ins).
34
Agenda Pages

presentation.
35
36
As you can see in this view, two possible loopbacks can be implemented
on the MPT level.
The core facing loopback, sending your signal back to your station…
And the radio facing loopback, sending the received signal back to the
remote station…
37
38
39
Agenda Pages

presentation.
40
41
Agenda Pages

presentation.
42
The PDH board now is encapsulating the E1 flow received on the first E1
interface into Ethernet packets.
And forwarding the resulting Ethernet flow tagged with the flow ID 100
to the core board through the Giga Ethernet link on the backplane.
The next step to complete this E1 circuit is to teach the core board what
to do with this flow ID 100.
It’s the role of the core board as a layer two switch to forward this flow
to its appropriate destination according to the configured cross
connections.
In our case here, we need this E1 to exit the MSS heading to the radio
direction to be transmitted to the remote site.
43
But as the E1 received from the PDH board is in the Ethernet packet
form, it can also be forwarded an Ethernet port on the core board
keeping its encapsulated form.
Obviously in this case, the device connected to this port should be able
to reconstruct the original E1 stream from the received packets...
44
Now our core board knows where to forward the flow IDs 100 and 200
received from the PDH board…
45
The core board can also be used to switch the traffic between different
radio directions or between a radio direction and an Ethernet port…
As shown in this example, the flow ID 300 received on the slot 4 radio
direction is forwarded to the slot 3 radio direction… while the received
flow ID 400 is directed to the core Ethernet port number 2…
46
connections.
47
connections.
48
connections.
49
connections.
50
connections.
51
connections.
52
connections.
53
connections.
54
connections.
55
connections.
56
connections.
57
connections.
58
connections.
59
Agenda Pages

presentation.
60
For instance, as you can see on the screen, the presented MPR radio link
offers a maximum of 350Mbps throughput at a modem profile of 56MHz
at 256 QAM.
Click
If you deploy a new parallel link using the same MSS8, Radio LAG allows
you to treat both parallel radio channels as one virtual link having a
700 Mbps throughput.
Click
And obviously, further radio links can be added | to increase the
transmission capacity.
Click
So for three radio channels, you would have virtual link of more than 1
Gbps throughput.
During the normal operation of a R-LAG group, the traffic is distributed
according to some fields in the layer two packet header like the
destination MAC address. Or fields in the layer three packet header like
the destination IP address for example.
The algorithm used to distribute the Ethernet packets to the physical
links is called the hashing algorithm.
61
In case of failure | of one of the RLAG radio links, | the virtual channel
capacity is decreased and hence the traffic to be transmitted will be |
defined by the QoS engine according to its priority.
62
63
64
65
66
67
68
69
Agenda Pages

presentation.
70
71
72
73
74
75
76
77
Agenda Pages

presentation.
78
79
80
81
82
83
84
85
86
87
88
89
90
91
Agenda Pages

presentation.
92
Considering the example shown on the screen, containing a well
synchronized equipment (Equipment A), |forwarding traffic to our MPR
that is not yet synchronized…
Any signal received from this synchronized device is |following its clock
signal…
In this case, MPR is going to try to decode this signal following its proper
clock, | that is obviously different than that of the device A …
This clock difference causes mysterious errors during the reception of
the traffic.
|Supposing that we configured MPR to derive its clock from the received
flow…The reception is going to be coherent with the signal clock|, and
no sync Errors are going to be produced…
93
94
95
Two |of these different synchronization sources can be chosen at a time acting as
primary and secondary sources of the MSS…
|For instance, the sync E as a primary source and the STM-1 port as the secondary
source…In that case, |both derived synchronization signals are presented to the
system|, and the primary source is used by default|…
In case a fault occurs to the primary synchronization |signal, the system switches
to the secondary source|…
Once the primary source has recovered, | the system has two different behaviors
according to the configuration…
In case of a not revertive configuration |, the system just remains at the secondary
source, and does not switch back unless the secondary source goes faulty….
|While in case of a revertive configuration, the system would wait for a predefined
|time (Called the wait to restore time), to verify the stability of the recovering
primary source….
Once the wait to restore time expires|, the system switched back to the primary
source…
96
97
Agenda Pages

presentation.
98
Once all the IP addresses and routing protocols are set correctly in your
network, all the deployed MPR can communicate together, and they all
can be managed by the management servers…
In this case, it’s possible to synchronize the time and date of all the
equipments with these management servers…
The protocol used for that is referred to as NTP (Network time
protocol)…
The NTP settings on an MSS, requires the declaration of the IP addresses
of a main and a spare NTP server.
Let’s start by the first node in a transmission axe, referred to as the GNE
(Gateway Network Element)…
On this NE, as it’s the closest NE to the servers…
We can set the main and spare NTP server addresses as depicted in the
figure…
For the NEs behind the GNE, it’s possible to set the main NTP server to
be the GNE rather than being the main NTP server in order to reduce
the charge on the servers…
In this way, the GNE can be considered as a main NTP server for the NEs
behind it…
99
protocol)…
figure…
behind it…
100
protocol)…
figure…
behind it…
101
Agenda Pages

presentation.
102
Welcome again.
In this module, we are going to discuss the ERPS operation and
configurations.
First of all, the ERPS stands for Ethernet ring protection switching. And
that is a very useful feature in case the MPR is involved in a ring
topology.
For instance, in this arrangement we can see three MPR nodes. Each
node is having a west radio port and an east radio port forming an
Ethernet ring topology.
In this Ethernet ring, any packet generated from Node A and terminated
at node C for example… might follow two different paths to reach its
destination, either passing by node B, or following the direct link
between nodes A and C. And in this way, in case of failure of any of the
ring links, traffic continuity wouldn’t be affected.
The only problem we can face here is when the packet destination is not
reachable, and here we are going to have an Ethernet loop.
To overcome this problem, ERPS protocol implements a loop avoidance
mechanism by blocking one of the ring links during the normal
operation. This specific link is called the RPL (Ring protection link).
The RPL should be associated to an RPL owner. This normally should be
one of the NEs terminating the RPL.
103
The RPL owner is the NE controlling the traffic flow on the RPL, So that
in case of failure of one of the operational ring links, the RPL owner
takes the decision to unblock the RPL to allow the traffic to circulate
normally inside the ring.
And when the faulty link is restored, the RPL owner waits for a predefine
period of time (called the wait to restore time) before blocking back
the RPL and restoring the traffic to its original paths.
In order for the protocol to work properly, the RPL owner needs to
communicate with all the ring nodes, and this communicatioin is
carried over a specific VLAN called the R-APS VLAN.
it’s also mandatory to identify each pair of neighbor NEs by a specific ID

called the Maintenance Entity group ID (referred to as the MEG ID )
104
So let’s see an example,
As depicted in this figure, we have four flows circulating in the ring, two
E1 flows (With flow IDs 11 and 12), and two VLAN tagged Ethernet flows
(with VLANs 1000 and 2000).
E1 11 and the Eth flow 1000 are going to be dropped in Node B

While E1 12 and the Ethernet flow 2000 are going to be dropped in node
C.
So let’s see how to configure MPR to implement this ring, assuming that
our RPL owner is the node A
And that the RPL is the link between Node A and Node C.
And let set the R-APS vlan to 100.
With the MEG ID of A and B set to 1, B to C set to 2 and C to A set to 3.
105

C.
106

C.
107

C.
108

C.
109

C.
110

C.
111

C.
112

C.
113
Agenda Pages

presentation.
114
Let’s have a look at the different management interfaces of an MSS8…
In fact there are several ways to get connected to an MSS-8 either using a direct local connection
or a remote connection…
The first management interface is the TMN ETH port |.
This port is found on the core board, and it’s dedicated only for management connections…
The port is normally connected to a local area network | typically containing several other Nes…
It requires the configuration of an IP address | and a subnetwork mask |…
Routing on this port can be performed using the static or dynamic method…
In case of dynamic routing, obviously an OSPF area should be assigned…
This port also supports the DHCP | operation that allows it to assign automatically an IP address
to the connected PC…
The second management port that can be used to connect to the MSS is the TMN P4 port…This
port by default is used for traffic transport… | but it can be switched to the TMN mode, and
that transforms the port into a normal management port similar to the previously presented
TMN port… In case the TMN mode is chosen, this port cannot carry traffic any more…
Once switched to this mode, the port can be connected to a local area network |
And that requires the allocation of an IP address | and a subnetwork mask |
| It also supports static or dynamic routing…
But this port | does not support the DHCP functionality…
The third management method is the TMN in band interface…
Normally the six Ethernet ports of the core board are used for traffic transport… but they can
implement a dedicated VLAN channel to carry the management traffic…
| So this interface can carry the traffic and management in the same time…
| And it should be connected to VLAN aware networks…
|Two TMN in band interfaces can be formed by the six traffic ports on the core board…
Each of these interfaces requires | an IP address and a | subnetwork mask…
Dynamic and static routing are also supported this interface…
While the DHCP functionality is not supported
115
116
The last method to get connected to this MSS is through the radio port
from a remote site…
| The interface used in this case is the PPP-RF interface…
| This interface exists on all the radio ports of the MSS8…
| The other end of this interface is the remote end of the link, so it’s
connected to only one NE
| and this is why it’s considered as a point to point interface | that
requires an IP address but not a subnetwork mask…
Static or dynamic routing can be used on each PPP-RF interface…
117
To summarize, up to five Management interfaces can be used to access
the MSS8…
With an IP address assignment to the TMN ETH, TMN P4 and two TMN in-
band interfaces, along with the local IP address used for point to point
communication…
That makes a maximum of five IP addresses that can be assigned to a
single MSS8…
So now let’s take a look at the configurations of each of these ports…
118
For example, as you can see in this drawing… two normal Ethernet ports
are used to | exchange Ethernet traffic between them…
To establish a management connection between these ports… each of
them should belong to a TMN in band interface…
Both interfaces are going to use a specific VLAN to exchange the

management traffic… referred to as the TMN in band VLAN…
119
In case of a third TMN in band device (Could be an MSS C), another port
can be added to the TMN in band interface of MSS B | to accommodate
the new connection,
In this case, the same VLAN must be used to establish the management
connection between these three MSS…
Notice that you are free to associate any port of the core board to any
interface…
And that obviously more than one port can be assigned to the same
interface…
120
protocol)…
figure…
behind it…
121
protocol)…
figure…
behind it…
122
protocol)…
figure…
behind it…
123
protocol)…
figure…
behind it…
124
Agenda Pages

presentation.
125
Also with the Core protection max. 3 MSS can be interconnected as
shown in this Figure. To implement this configuration the LOS alarm on
the Ethernet ports must be enabled as switching criterion
of the Core protection. To enable this functionality the “Ethernet LOS
Criteria” feature has to be enabled
126
127
Agenda Pages

presentation.
128
129
Agenda Pages

presentation.
130
To manage more directions the “Stacking configuration” can be
realized by installing up to 3 MSS, interconnected
through the Ethernet ports in the Core-E module. In the example of
Figure 10 are shown the interconnected MSS.
For the Stacking configuration it is recommended to enable the Static
Lag Criteria
131
To manage more directions the “Stacking configuration” can be
realized by installing up to 3 MSS, interconnected
through the Ethernet ports in the Core-E module. In the example of
Figure 10 are shown the interconnected MSS.
For the Stacking configuration it is recommended to enable the Static
Lag Criteria
132
133
Agenda Pages

presentation.
134
135
136
Divider Section Break Pages
• Title block set 28/32pt Trebuchet white, flush left with text box
positioned at, Horizontal 1.87” and Vertical 2.87”
• This slide is to be used to create Section Divider slides
• Please copy, paste and modify this slide to reflect your specific needs.
It is not generated from a Master slide template
137
As you can see in this drawing, we have two MPR nodes to be managed by a PC,
with the IP addresses as depicted on the figure…
In order for the PC to manage the remote end of this link (MSS B), it outputs IP
packets | having the destination IP address in THEIR header…
As this PC is connected directly to the MSS A, it forwards the packets to
whatever its destination is…
This MSS8 is referred to as the default gateway of the PC…
Once this IP packet reaches the MSS A, | the later is going to wonder where to
forward it…
And it’s the static route that teaches the MSS A where to forward the packet
according to required destination IP address and mask…
| so the static route to be implemented on this MSS should have the
destination network IP set to 192.168.2.0, with the mask of 255.255.255.0,
and the gateway set to be the radio direction 3.1…
Meaning that to reach the MSS B, you should go through the Radio MPT
connected to the slot three port one…
Once this static route is implemented, | the packet leaves the MSSA heading
to the right destination.
In order for the packet to make its way back from MSSB to the PC, you need to
implement | a similar static route explanting to the MSS B that to go back to
the PC, it should leave | through the radio port in the slot three port one.
Once both static routes are implemented, the bidirectional communication can
be realized…
138
Supposing that we have introduced another MPR site (MSS C)… in order to
establish the management connection to this | new destination, we
have to teach the MSS A, that the MSS C is also accessible via the radio
slot three port one…
And also we need to teach the MSS B that the new destination is
accessible via its radio direction in slot six port one | |…
In the same manner, to establish a bidirectional communication, we
need to implement another static route on the MSS C explaining how to
reach the PC in order for the packet to go back…
139
Supposing that the MSS A receives a packet from the PC containing an
unknown destination, it can use a default static route stating that for
any other destinations not mentioned in the routing table, send the
packet to a default gateway…
In our case it’s the collocated MSS D…
The default gateway is expressed by a static route having the
destination IP address and mask set to all zeros, and gateway address
set to the MSS D address.
140
Supposing that the MSS A receives a packet from the PC containing an
unknown destination, it can use a default static route stating that for
any other destinations not mentioned in the routing table, send the
packet to a default gateway…
In our case it’s the collocated MSS D…
The default gateway is expressed by a static route having the
destination IP address and mask set to all zeros, and gateway address
set to the MSS D address.
141
To resolve this issue, we can use what we call the dynamic routing, allowing the
automatic detection of network topology changes…
The dynamic routing protocol widely used is the open shortest path first (OSPF
protocol)
As an example, consider the MSS A shown in the figure, Initially having an empty
routing table, and using the OSPF protocol
Whenever the MSS B joins this network, given that it also uses the OSPF protocol.
The routing tables of both MSS8s are going to be updated automatically to suit the new
network topology…
The OSPF protocol works in areas, so in order for this topology change detection to
happen, both MSS 8s must belong to the same OSPF area…
The OSPF area is identified by an IP address like identifier referred to as OSPF area
address…
Moreover it is also mandatory in this example to associate this OSPF area to the
interfaces connecting both MSS8s, which is called the PPP-RF interface.
In the same manner, if we introduce the MSS C to the network, create the same OSPF
area address, and associate it to the related PPP-RF interfaces…
Routing tables of all the NEs of the network are going to be updated to suit the new
topology changes…
Let’s now take a look at the configurations of the MSS A…

On this MSS, we will need to create an OSPF area, with the address 0.0.0.1 …
And assign it to the radio PPP interface heading to the MSS B…
142
143
product .

answer them.
1
Agenda Pages

presentation.
2
Agenda Pages

presentation.
3
4
Agenda Pages

presentation.
5
6
Agenda Pages

presentation.
7
8
9
10

9500 MPR I&amp;C SG StudentHandout

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9500 MPR I&amp;C SG StudentHandout

Uploaded by

Copyright:

Available Formats

© Nokia 2017. All Rights Reserved.

© Nokia 2017. All Rights Reserved.

Do not hesitate if you have any questions, we are here to

Thank for your attention

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

Do not hesitate if you have any questions, we are here to

Thank for your attention

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

Do not hesitate if you have any questions, we are here to

Thank for your attention

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

Do not hesitate if you have any questions, we are here to

Thank for your attention

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

• This page allows for the listing of the sections within a

it’s also mandatory to identify each pair of neighbor NEs by a specific ID

E1 11 and the Eth flow 1000 are going to be dropped in Node B

E1 11 and the Eth flow 1000 are going to be dropped in Node B

E1 11 and the Eth flow 1000 are going to be dropped in Node B

9500 MPR I&C SG StudentHandout

9500 MPR I&C SG StudentHandout