WAVENCE18 Installation & Comm - RN88294 - C - 1800 - V1.0 - SG - Ed1 - CE

© Nokia 2018. All Rights Reserved.

Welcome to Wavence 18
Installation & Commissioning
1. Installation & Commissioning

1. Installation & Commissioning
2. Lab Exam

Welcome to Wavence 18
Installation & Commissioning
Upon completion of this course, you should be able to describe:
PC Connection to the NE
WebCT Start
WebCT Application
NE Initial Configuration
UBT Radio parameter configuration
Housekeeping Configuration
Ethernet Traffic configuration
Radio Power Measurements
Radio Measurements (Radio Dashboard)
Synchronization distribution
IP address configuration
NTP configuration
TMN configuration
Your feedback is appreciated!

Please feel free to Email your comments to:
training.feedback@nokia.com
Please include the following training reference in your email:

RN88294-C-1800_V1.0-SG Edition 1
Thank you!

Copyright © 2018 Nokia. All Rights Reserved.
RN88294-C-1800_V1.0-SG-Ed1 Module 1.1 Edition 1
1· 1·1
Document History
Edition Date Author Remarks
1 2018-03-16 NokiaEDU First version

1· 1·2
1· 1·3
This page is left blank intentionally

1· 1·4
Page
1 PC Connection to the NE 7
1.1 PC Connection to NE 8
1.1.1 PC Characteristics 9
2 WebCT Start 12
2.1 WebCT Start Procedure 13
3 WebCT Application 15
3.1 WebCT (Administration & Networking domain shown) 16
4 NE Initial Configuration 17
4.1 NE Initial Configuration Overview 18
4.2 Card Configuration Overview 19
5 UBT Radio parameter configuration 20
5.1 EAC/EASv2 Card port Provisioning with UBT 21
5.1.1 UBT Power Source Procedure 22
5.1.2 UBT Radio Parameters Configuration Procedure 23
5.1.2.1 Capacity license 25
5.1.2.2 Modem Profile Settings (FCM) 26
5.1.2.3 Modem Profile Settings (ACM) 27
5.1.2.4 Frequency Settings 28
5.1.2.5 Tx Power Settings (RTPC) 29
5.1.2.6 Tx Power Settings (ATPC) 30
5.1.2.7 Additional Settings 31
5.2 L1 Radio LAG Configuration Procedure 32
6 Housekeeping Configuration 36
6.1 Housekeeping Configuration Procedure 37
7 Ethernet Traffic configuration 40
7.1 CorEvo Provisioning (Ethernet user ports) - Overview 41
7.1.1 CorEvo Card Ethernet User Interfaces 42
7.1.2 CorEvo Ethernet Ports 43
7.2 EASv2 Card Ethernet User Interfaces 50
7.2.1 EASv2 Ethernet Ports 51
7.3 EAC Ethernet Ports 53
7.4 Ethernet Switch Configuration - Overview 56
7.4.1 Virtual Bridge Configuration 57
7.4.1.1 Create a C-VLAN 58
7.4.2 Provider Bridge configuration overview 60
7.4.2.1 Create a S-VLAN 69
7.4.2.2 Provision Provider Bridge port: NNI 71
7.4.2.3 Provision Provider Bridge port: UNI Port-based 72
7.4.2.4 Provision Provider Bridge port: UNI VLAN-based 73
7.5 Quality Of Services (QoS) 75
7.6 CorEvo/EASv2 QoS 77
7.7 UBT QoS 78
7.8 CorEvo scheduler 79
7.8.1 Scheduler Configuration 80
7.8.2 Queue Scheduling configuration 81
7.8.3 Queue Size configuration 83
7.8.4 QoS Classification configuration 85
7.8.4.1 QoS Classification Criteria - 802.1p 86
7.8.4.2 QoS Classification Criteria - DiffServ 89
8 Radio Power Measurements 90
8.1 Procedure to perform radio analog measurements 91
9 Radio Measurements (Radio Dashboard) 94
9.1 Procedure to perform radio measurements 95
10 Synchronization distribution 100
10.1 Synchronization distribution 101

1· 1·5
Page
10.2 Input sources (MASTER NE) 102

10.3 Input sources (SLAVE NE) 103
10.4 Synch IN/OUT SFP 104
10.5 Synchronization Source Protection 105
10.6 Synchronization configuration 106
11 IP address configuration 109
11.1 Local IP address 110
11.2 IP Static Routing 111
11.2.1 IP Static Routing: Next Hop 112
11.2.2 IP Static Routing: Point to Point 113
11.3 OSPF Area 114
11.4 System Settings Procedure 115
11.5 SNMP Setting procedure 117
12 NTP configuration 118
12.1 NTP Configuration Procedure 119
13 TMN configuration 120
13.1 Management interfaces 121
13.2 TMN ETH (Management port) 122
13.3 TMN Port 4 123
13.4 TMN In-Band 124
13.5 PPP-RF 127
13.6 Management Interfaces summary 128
13.7 TMN In-Band configuration 129
13.8 TMN Ethernet configuration (Management port of CorEvo) 131
13.9 TMN Port 4 configuration 132
13.10 PPP-RF configuration 133
14 Resources 134
14.1 Static Routing 135
14.2 Default Gateway 137
14.3 OSPF (Open Shortest Path First) 138
14.4 Scratch of the MIB of the CorEvo Compact Flash 140
14.4.1 Hardware scratch 141
14.4.2 Software scratch 143
14.5 Scratch the MIB of the MSS-1 Compact Flash 145
14.5.1 MIB scratch by using a standard Web Browser 146
14.5.2 MIB scratch by using the WebCT 147

1· 1·6
1· 1·7
1· 1·8
1· 1·9
1 · 1 · 10
1 · 1 · 11
1 · 1 · 12
Note: Default User Name: initial
Default Password: adminadmin

1 · 1 · 13
1 · 1 · 14
1 · 1 · 15
The Banner bar shows the available domains:
Administration & Networking
Monitoring & Maintenance
Equipment
Interfaces
Services
Statistics
The icons showing a summary of Active alarms, Abnormal Conditions (AC), Local Access (LAC), and NE
information are displayed at the upper right of every webpage.
The Navigation frame at the left of the webpage changes based on the domain selected.

1 · 1 · 16
1 · 1 · 17
1 · 1 · 18
1 · 1 · 19
1 · 1 · 20
1 · 1 · 21
1 · 1 · 22
To configure the Radio parameters 5 setting menus are available:
Capacity license
Modem Profile Settings
Frequency Settings
Power Settings
Additional Settings

1 · 1 · 23
To configure the Radio parameters 5 setting menus are available:
Capacity license
Modem Profile Settings
Frequency Settings
Power Settings
Additional Settings

1 · 1 · 24
1 · 1 · 25
1 · 1 · 26
1 · 1 · 27
1 · 1 · 28
1 · 1 · 29
1 · 1 · 30
1 · 1 · 31
1 · 1 · 32
1 · 1 · 33
1 · 1 · 34
1 · 1 · 35
1 · 1 · 36
1 · 1 · 37
1 · 1 · 38
1 · 1 · 39
1 · 1 · 40
1 · 1 · 41
Notes:
• The physical electrical ports are RJ45.
• Port 4 can be also configured for TMN.

1 · 1 · 42
Notes:
• Auto negotiation Status – Default is disabled. If enabled, up to five speeds and capabilities and flow control
are supported. If disabled, only one speed is supported.
• Flow Control – When enabled, the auto negotiation function stops receiving traffic. If the radio input buffer
reaches overflow, a pause message is sent to the link partner that is transmitting data. Ethernet ports cannot be
configured to transmit pause messages. If a pause message is received on an Ethernet port, it is discarded.
Default is disabled.
• Advertised Capability – For Electrical ports with auto negotiation enabled, select all capabilities that apply (10
or 100 Mb/s half/full duplex, 1000 Mb/s full duplex). When auto negotiation is disabled, only one speed and
capability is allowed (no 1000 Mb/s).

1 · 1 · 43
LLDP = Link Layer Discovery Protocol
The Automatic Link Discovery allows Wavence equipment to discover and store information about its neighbors.
This information is then used by network managers such as NFM-P to automatically learn the network topology.

1 · 1 · 44
1 · 1 · 45
1 · 1 · 46
Notes:
• Auto negotiation Status – Default is disabled. If enabled, up to five speeds and capabilities and flow control
are supported. If disabled, only one speed is supported.
• Flow Control – When enabled, the auto negotiation function stops receiving traffic. If the radio input buffer
reaches overflow, a pause message is sent to the link partner that is transmitting data. Ethernet ports cannot be
configured to transmit pause messages. If a pause message is received on an Ethernet port, it is discarded.
Default is disabled.
• Advertised Capability – All capabilities that apply (10 or 100 Mb/s half/full duplex, 1000 Mb/s full duplex).
When auto negotiation is disabled, only one speed and capability is allowed (no 1000 Mb/s).

1 · 1 · 47
LLDP = Link Layer Discovery Protocol
The Automatic Link Discovery allows Wavence equipment to discover and store information about its neighbors.
This information is then used by network managers such as NFM-P to automatically learn the network topology.

1 · 1 · 48
1 · 1 · 49
Notes:
• The physical electrical ports are RJ45 providing four PFoE-capable 10/100/1000 10BaseT Ethernet
interfaces.
• Optical ports are GigE Ethernet SFP
• The optional optical SFP plug-in, which has to be installed in ports 5 through 8 contains a Class 1
laser source.

1 · 1 · 50
For the electrical ports refer to the configuration done for the CorEvo.

1 · 1 · 51
1 · 1 · 52
1 · 1 · 53
For the electrical Ethernet ports refer to the configuration done for the electrical ports of the CorEvo.

1 · 1 · 54
1 · 1 · 55
1 · 1 · 56
1 · 1 · 57
1 · 1 · 58
Notes:
The functions and fields are the same in the Create S-C-VLAN screen
1. VLAN ID field: Enter the C-VLAN ID (the configurable values must be in the range 2 - 4080)
• The C-VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be
used.
2. VLAN Name field: Enter the C-VLAN Name: a text string of up to 32 characters.
• There is no check on unambiguity name.
3. VLAN Ports field: Select the port members of this C-VLAN by putting a check mark on the relevant check
box. All the user Ethernet ports and all the Radio directions can be considered.
4. Untagged Ports field: Select, among the ports belonging to this C-VLAN (members), the untagged ports (in
egress the C-VLAN will be removed from the frames). Only the user Ethernet ports, enabled and disabled,
are manageable. The C-VLAN cannot be removed from the radio ports (with the exception of the C-VLAN 1).
• The VLAN-ID values allowed are in the range 2 - 4080. By default, for the C-VLAN IDs defined, all the ports are
members and the Untag flag is set to “False”, which means all the frames are transmitted with Tag.
• Tagged frames - If one tagged packet with C-VLAN-ID X is received on a port which is not member of the C-
VLAN-ID X, the packet is dropped.

1 · 1 · 59
Notes:
• An S-VLAN Component is a VLAN-aware bridge able to recognize, insert, and remove S-VLAN tags.

1 · 1 · 60
1 · 1 · 61
Notes:
• C-VLAN - Customer VLAN. Port priority represents the priority assigned to untagged frames ingressing the port.

1 · 1 · 62
All the C-VLAN entering an Ethernet port are transported with a S-VLAN.
The priority is assigned at S-VLAN level.

1 · 1 · 63
All the C-VLAN entering an Ethernet port are transported with a S-VLAN.
The used priority is the priority associated to each C-VLAN, as shown in the example.

1 · 1 · 64
The S-VLAN is created by selecting the C-VLAN to be transported with the S-VLAN.
The priority can be configured at S-VLAN level or can be inherited by the C-VLAN.
In the figure C-VLAN 100 and 101 are transported with S-VLAN 500.
C-VLAN 102 is transported with S-VLAN 501.
As priority is used the priority written in the C-VLAN.

1 · 1 · 65
S-VLAN 501 (created in Wavence 1) transits from Wavence 2 to Wavence 3 (through port 1 of slot 1).
This port in both MPR must be configured as NNI with TPID 9100.

1 · 1 · 66
S-VLAN 501 (created in Wavence 1) transits from Wavence 2 to a port of an old switch.
In this case the MPR port must be configured as NNI with TPID 8100.

1 · 1 · 67
S-VLAN 501 (created in Wavence 1) transits from Wavence 2 to a port of a CISCO switch.
In this case the MPR port must be configured as NNI with TPID 88a8.

1 · 1 · 68
1 · 1 · 69
Notes:
The functions and fields are the same in the Create S-C-VLAN screen
1. VLAN ID field: Enter the S-VLAN ID (the configurable values must be in the range 2 - 4080)
• The S-VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be
used.
2. VLAN Name field: Enter the S-VLAN Name: a text string of up to 32 characters.
• There is no check on unambiguity name.
3. VLAN Ports field: Select the port members of this S-VLAN by putting a check mark on the relevant check
box. All the user Ethernet ports and all the Radio directions can be considered.
4. Untagged Ports field: Select, among the ports belonging to this S-VLAN (members), the untagged ports (in
egress the S-VLAN will be removed from the frames). Only the user Ethernet ports, enabled and disabled,
are manageable. The S-VLAN cannot be removed from the radio ports (with the exception of the S-VLAN 1).
• The VLAN-ID values allowed are in the range 2 - 4080. By default, for the S-VLAN IDs defined, all the ports are
members and the Untag flag is set to “False”, which means all the frames are transmitted with Tag.
• Tagged frames - If one tagged packet with S-VLAN-ID X is received on a port which is not member of the S-
VLAN-ID X, the packet is dropped.

1 · 1 · 70
1 · 1 · 71
1 · 1 · 72
1 · 1 · 73
1 · 1 · 74
The QoS function inside Wavence is the result of a distributed implementation in the CorEvo switch, in the EASv2
switch and in UBT.
The QoS function must be properly configured in order to get the wanted operation on the Ethernet flows to
transmit towards the Radio link.
The QoS in the CorEvo selects the Ethernet frames to be sent to the output of the CorEvo: the output has a
10 Giga capacity.
The QoS in the EASv2 selects the Ethernet frames to be sent to the output of the EASv2: the output has a
2.5 Giga capacity.
The QoS in the UBT selects the Ethernet frames to be sent to the radio channel. The input capacity can be 1
Giga, 2.5 Giga or 10 Giga (depending on the type of UBT), but the radio capacity is lower and depends on the
modulation scheme and the radio bandwidth.

1 · 1 · 75
The Ethernet frames are assigned to one egress queue according to the selected classification (802.1p or
DiffServ). There is a default classification, but it can be changed by the WebCT.
The egress queues are 5 in CorEvo and EASv2 and 8 in UBT.

1 · 1 · 76
The figure shows an overview of the QoS implementation inside the CorEvo/EASv2.
The Quality of Service feature provides 5 internal queues per port:
Queue 5 is the highest priority queue and
Queue 1 is the lowest priority queue
Typically the high-priority traffic experiences less delay than the low-priority one in the switch under congested
conditions.
According to the QoS classification method configured in the switch, the packets for each egress port will be
assigned to each queue. Queues 8 to 1 are shared by all Ethernet frames according to the classification
configured by the WebCT.

1 · 1 · 77
The figure shows an overview of the QoS implementation inside the UBT.
The Quality of Service feature provides 8 internal queues per port:
Queue 8 is the highest priority queue and
Queue 1 is the lowest priority queue
Typically the high-priority traffic experiences less delay than the low-priority one in the switch under congested
conditions.
According to the QoS classification method configured in the switch, the packets for each egress port will be
assigned to each queue. Queues 8 to 1 are shared by all Ethernet frames according to the classification
configured by the WebCT.

1 · 1 · 78
Two types of Scheduler are available:
Strict Priority
Deficit Weighted Round Robin
The default scheduler is DWRR with the default weights shown in the table.
The default DWRR scheduler can be changed to SP scheduler.
The weight of the DWRR scheduler can also be changed.

1 · 1 · 79
Notes:
The QoS Configuration menu has 3 submenus:
• QoS Classification
• Queue Size
• Scheduler

1 · 1 · 80
Notes:
• Warning changes can be traffic affecting.
• Mode – contains a drop-down menu that contains the following queue scheduling algorithm selections:
• SP – Strict Priority
• DWRR – Deficit Weighted Round Robin
• Weight field – priority weight (1-16)

1 · 1 · 81
1 · 1 · 82
1 · 1 · 83
Notes:
• Each queue can have an assigned buffer size (in bytes) for each radio direction.
For example radio direction #63 has a buffer size of 3118838 bytes with a maximum delay of 659,421msec.

1 · 1 · 84
• The QoS Classification Criterion drop-down menu contains the following choices:
• Deactivated - All Ethernet traffic has the same priority (FIFO) and are assigned the lowest priority queue
(default mode)
• IEEE 802.1p
• DiffServ

1 · 1 · 85
Notes:
• Priority value is carried by Priority Code Point (PCP) field.
• PCP values are mapped to one of five internal forwarding classes for CorEvo/EASv2 and one of eight internal
forwarding classes for UBT.

1 · 1 · 86
1 · 1 · 87
1 · 1 · 88
Notes:
• Each packet is classified based on Differentiated Service Code Point (DSCP) field in the IPv4 or IPv6 packet
header to determine packet priority.
• DSCP values are mapped to one of the internal Forwarding Classes.
• When incoming packets are not IPv4 or IPv6, the packets are assigned to Q1.

1 · 1 · 89
1 · 1 · 90
The Radio Power Measurements menu gives the level of the Tx and Rx power.

1 · 1 · 91
1 · 1 · 92
1 · 1 · 93
1 · 1 · 94
The Radio dashboard menu gives the radio equipment measurements and the PM G.826.

1 · 1 · 95
1 · 1 · 96
1 · 1 · 97
1 · 1 · 98
1 · 1 · 99
1 · 1 · 100
1 · 1 · 101
The Clock Reference Unit (CRU) inside the CorEvo can be synchronized by:
one of the Ethernet streams entering the MSS
one synchronization signal (Sync IN) entering the dedicated SFP (Sync In/Out) installed on port 7 or 8 of the
CorEvo.
The Clock Selector, according to the configuration done with the WebCT, selects the Primary Source and the
Secondary Source.
The selected input source controls the CRU.
The clock at the output of the CRU is distributed to all the units of MSS.
By WebCT it is possible to make available this used clock to a connector on the SFP installed in port 7 or 8 the
CorEvo to synchronize other NEs.

1 · 1 · 102
The Clock Reference Unit (CRU) inside the CorEvo can be synchronized by:
one of the clock extracted from a radio link
one of the Ethernet streams entering the MSS
one synchronization signal (Sync IN) entering the dedicated SFP installed on port 7 or 8 of the CorEvo.
The Clock Selector, according to the configuration done with the WebCT, selects the Primary Source and the
Secondary Source.
The selected input source controls the CRU.
The clock at the output of the CRU is distributed to all the units of MSS.
By WebCT it is possible to make available this used clock to a connector on the SFP installed in port 7 or 8 the
CorEvo to synchronize other NEs.

1 · 1 · 103
1 · 1 · 104
Two of these different synchronization sources can be chosen at a time acting as primary and secondary sources
of the MSS.
For instance, the SyncE as a primary source and the SyncIn 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 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.

1 · 1 · 105
1 · 1 · 106
1 · 1 · 107
1 · 1 · 108
1 · 1 · 109
Note: After the Local IP Address change, the NE restarts.

1 · 1 · 110
1 · 1 · 111
1 · 1 · 112
1 · 1 · 113
1 · 1 · 114
1 · 1 · 115
Note:
DHCP - configures automatically IP address, IP mask and default gateway of the PC Ethernet interface used
to reach the NE.

1 · 1 · 116
Note:
SNMP Mode - This field indicates which protocol is allowed for SNMP managers accessing the NE: SNMPv2
or SNMPv3. Default is SNMPv2.

1 · 1 · 117
1 · 1 · 118
Notes:
This menu is used to enable the NTP (Network Time Protocol)
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The following
information can appear:
"Main server reachable"
"Spare server reachable"
"None servers reachable"
"Both servers reachable"

1 · 1 · 119
1 · 1 · 120
There are several ways to get connected to an MSS either using a direct local connection or a remote connection:
TMN Eth
TMN Port 4
TMN In-band
TMN PPP-RF
The next pages explain all the available ways.

1 · 1 · 121
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.

1 · 1 · 122
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.

1 · 1 · 123
The third management method is the TMN in band interface…
Normally the 8 Ethernet ports of the CorEvo 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.

1 · 1 · 124
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.

1 · 1 · 125
In case of a third TMN in band device (Could be the 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.

1 · 1 · 126
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 MSS.
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.

1 · 1 · 127
To summarize, up to five Management interfaces can be used to access the MSS.
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 MSS.

1 · 1 · 128
1 · 1 · 129
1 · 1 · 130
1 · 1 · 131
1 · 1 · 132
1 · 1 · 133
1 · 1 · 134
As you can see in this drawing, we have two Wavence 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 MSS A heading to the right destination.
In order for the packet to make its way back from MSS B 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.

1 · 1 · 135
Supposing that we have introduced another Wavence 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.

1 · 1 · 136
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 co-located 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.

1 · 1 · 137
1 · 1 · 138
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 MSSs 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 MSSs 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
MSSs, 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.

1 · 1 · 139
1 · 1 · 140
1 · 1 · 141
1 · 1 · 142
1 · 1 · 143
1 · 1 · 144
1 · 1 · 145
1 · 1 · 146
1 · 1 · 147
1 · 1 · 148
1 · 1 · 149
1 · 1 · 150
1· 2·1
Document History
Edition Date Author Remarks
1 2018-03-16 NokiaEDU First version

1· 2·2
1· 2·3

1· 2·4
Page
1 Lab Exam 7
1.1 Lab description 8
1.2 Instrument characteristics 10
1.3 Abilities to demonstrate 11

1· 2·5

1· 2·6
In this chapter you will learn:
• the licenses available with Wavence

1· 2·7
1· 2·8
1· 2·9
1 · 2 · 10
1 · 2 · 11
1 · 2 · 12
1 · 2 · 13
1 · 2 · 14
1 · 2 · 15
1 · 2 · 16
© Nokia

WAVENCE18 Installation & Comm - RN88294 - C - 1800 - V1.0 - SG - Ed1 - CE

Загружено:

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

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

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

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

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

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

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

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

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

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

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

WAVENCE18 Installation & Comm - RN88294 - C - 1800 - V1.0 - SG - Ed1 - CE

Загружено:

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

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

© Nokia 2018. All Rights Reserved.

© Nokia 2018. All Rights Reserved.

1. Installation & Commissioning

© Nokia 2018. All Rights Reserved.

Upon completion of this course, you should be able to describe:

Your feedback is appreciated!

Please include the following training reference in your email:

© Nokia 2018. All Rights Reserved.

Edition Date Author Remarks

1 2018-03-16 NokiaEDU First version

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

10.2 Input sources (MASTER NE) 102

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

• Port 4 can be also configured for TMN.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

• Optical ports are GigE Ethernet SFP

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

• Weight field – priority weight (1-16)

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

• Priority value is carried by Priority Code Point (PCP) field.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.

Copyright © 2018 Nokia. All Rights Reserved.