Wavence TMN

Networking Guide
3DB 19353 AFAA TQZZA
March-2018

1 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 1. TMN Interfaces
2. TMN Related Services
3. TMN IP Addresses
4. The TMN Network
5. DCN Interconnections examples
6. Basic Wavence Address Provisioning
7. Interconnecting Multiple Wavence Shelves
8. Craft and Management Communication Requirements
9. Planning and Addressing a Network
10. Configuring the Wavence

2 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 A. Basics of IP Addressing
B. Communication in Networks
C. Wavence DHCP Overview
D. Wavence OSPF Overview
E. Comparison to TMN Networking in the MDR-8000
F. MPR-e and MPR-1c differences
G. Default and Reserved addresses
H. NAT router

3 © 2018 Nokia
3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 1. TMN Interfaces

4 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking - Physical Interfaces
Dir #35
Dir #34
Dir #N
TMN In-Band #1
VLAN Interface

TMN In-Band #2
VLAN Interface
Port #4 TMN TMN Ethernet

Wavence supports a variety of interfaces for TMN traffic:

1. For transport across RF links, there are in-band PPPoE channels, one per Direction
2. The TMN Ethernet port, enabled by default. This interface is intended for local Craft access.
3. User Ethernet Port #4 can be configured for TMN. When provisioned for TMN this interface is intended for TMN connecting to
external networks for TMN backhaul.
4. Optionally one or two TMN In-band interfaces. These interfaces can be associated with one or more User Ethernet ports with a
user specified VLAN Id. These interfaces are also intended for connecting with external networks. Using these interfaces
requires VLAN aware external equipment.
5. Starting with R8.0 TMN in-band is supported on EASv2 card through configuration file. Refer to “Wavence Configuration File
Management User Manual”.

5 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Interface to the TMN Router
Dir #35
Dir #34
Dir #N
TMN In-Band #1 VLAN
Interface
TMN
In-Band #1
TMN In-Band #2 VLAN

}
VLAN Subnet
Interface Port #4 TMN TMN Ethernet
Dir #34

TMN Dir #35

In-Band #2
VLAN Subnet
RF PPPoE links

…
Dir #N

Port #4
TMN Subnet TMN Ethernet
Subnet

•Each TMN interface to the Wavence connects with an internal router.

•With the exception of the RF PPPoE links, all interfaces to the Router are Broadcast Ethernet interfaces. When these interfaces are provisioned, the
subnets must all be unique.
•TMN traffic passing between any two TMN Network Interfaces is routed at Layer 3.
•ALL TMN Interface subnets must be unique and cannot overlap. The router does not support Bridging.
•TMN In-Band VLANs may be associated with one or more User Ethernet ports on the Core. All traffic in common TMN VLANs will be switched between
the member ports.

6 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 2. TMN Related Services

7 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Addressing Support
Wavence supports TMN Networking in either IPv4 or IPv6 mode.
 Only one mode may be active at a time. Simultaneous support of both IPv4 and IPv6 (Dual Stack) for TMN
Networking is not available.
Most of this presentation is written using IPv4 examples but the examples apply equally to IPv6.
 IPv6 specific behaviors are noted where applicable.

8 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Services - OSPF
Wavence provides two services related to TMN networking.
The first service is OSPF for dynamic routing of TMN network traffic
1. For IPv4 TMN Networks the Wavence supports OSPFv2
2. For IPv6 TMN Networks the Wavence supports OSPFv3
3. Wavence provides a very basic OSPF implementation
4. User configurable parameters are limited to:
✓ Enabling or disabling OSPF on each individual TMN interface.
✓ Assigning an OSPF Area ID to each interface (default Area is 0)
✓ Enabling or disabling the Stub Flag (indicates whether the interface is a member of an OSPF
Stub Area)
5. A single Wavence can function as an Area Border Router (ABR) for up to four OSPF Areas, one of
which must be Area 0. A Wavence may not be a member of more than one OSPF Area unless one
active interface is a member of Area 0.
6. Wavence is able to interoperate with external OSPF capable devices such as an 7705 SAR.
Refer to the OSPF Appendix at the back of this presentation for additional information about
interoperating with external equipment.

9 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Services – Craft computer address
assignment
In IPv4 mode a trivial DHCP server available only on the TMN Ethernet port.
1. This limited server is intended to support dynamic address configuration of directly connected Craft
computers.
2. Enabled by default, the DHCP server can be disabled. This is the only user configurable option.
3. The DHCP server uses an address pool determined by the TMN Local Ethernet IP address and subnet.
4. The maximum number of Addresses managed by the DHCP Server is 10. Clients are served the same
Netmask assigned to the TMN Local Ethernet interface and a Default Gateway of the TMN Local
Ethernet Port IP address.
5. The Lease Time is fixed to 10 minutes.

Refer to the DHCP Appendix for specifics on how the Wavence reserves address for leases.
In IPv6 mode DHCP is not supported. Instead the Wavence supports the RFC4861 Neighbor Discovery
Protocol (NDP) and sends link-local announcements allowing Stateless Address Auto-configuration of
external devices.

10 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 3. TMN IP Addresses

11 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addresses
Wavence can be configured with up to five addresses.
Local Address:10.0.36.9

1. The first and primary address is the NE Local Address:

a) This is the Address of the Wavence itself. This is equivalent to the System
Address for other types of equipment.
b) The Local Address is the address the Craft and SNMP Managers must use when
monitoring or provisioning the NE.
c) All Wavence SNMP Traps or Notifications are sent from this address
d) All RF PPPoE connections terminating in this shelf (one per Direction) use this
address as their PPP Endpoint Identifier.
e) The NE Local Address is reachable by using one of the TMN Interface addresses
as a gateway (see the next slide).

12 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addresses
Port #4 TMN TMN Ethernet
Address: 192.168.10.0 Address: 172.22.64.86
Netmask: 255.255.255.192 Netmask: 255.255.255.248

2. The TMN Ethernet interface address

a) The default interface intended for local Craft access, it is enabled by default.
➢ Caution: Disabling this interface may prevent any direct Craft access to the Wavence. Unless
another means of connectivity is available such as Port #4 TMN, TMN In-Band, or an RF-PPP link
recovery will require scratching the Wavence Database to return the system to defaults.
➢ Caution: Connecting this interface to external networks is possible but not recommended. The
default DHCP server may interfere with other external DHCP servers and high volumes of
Broadcast or other traffic in the subnet can disrupt Core operations and may trigger unexpected
Core restarts.
3. Optional Port #4 TMN Ethernet interface address
a) This interface is disabled by default. When enabled Core User Ethernet port #4 is reconfigured as a
dedicated TMN interface.
b) Intended for use when connecting to external networks keeping the TMN Ethernet interface available for
direct Local Craft access.

13 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addresses: In-
Band interfaces
TMN In-Band #2
VLAN Id: 3720 TMN In-Band #1
User Ports: 1,3 VLAN Id: 2152
Address: 10.139.22.6 User Port: 2
Netmask: 255.255.255.248 Address: 172.22.65.132
Netmask: 255.255.255.224

4. Optional TMN In-Band #1 Ethernet interface address

Optional TMN In-Band #2 Ethernet interface address
a) These interfaces are disabled by default.
b) When a TMN In-Band interface is enabled a unique VLAN Id is specified for the
interface and one or more User Ethernet ports are assigned as members of the VLAN.
Traffic in the In-Band VLAN will be switched between all member ports.
c) These interfaces are intended for connection to external networks

Refer to the “Wavence Configuration File Management User Manual” for further configurations.

14 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addresses: In-Band interfaces

The primary differences between the In-Band interfaces and the other TMN
interfaces are:
1) In-Band TMN Traffic is always VLAN tagged with the user specified VLAN
Access to the TMN In-Band traffic requires interfacing with a VLAN
aware external device, one that can be configured to use the same VLAN
2) Port flexibility. The user can provision one or more User Ethernet ports
that will be used with the In-Band interface
a) When multiple User Ethernet ports are associated with a TMN In-
Band interface the associated TMN VLAN will be switched between
the member ports.

15 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addresses: In-Band interfaces
(Continued)
3) User ports used for TMN In-Band:
a) May not be port segregated.
b) May be associated with PDH cross-connections.
c) When in 802.1Q mode the ports are always a member of the Wavence internal
VLAN 1 and may also be a member of additional User defined VLANs.
d) When in 802.1ad mode the ports are always a member of the Wavence internal S-
VLAN 1 and may also be a member of additional User defined VLANs.
e) When in 802.1D mode the ports are connected directly to the Wavence L2 switch
fabric
➢ The user should be aware of these behaviors when transporting TMN Traffic in a VLAN
through the same physical interface used for external backhaul or when
interconnecting User Ethernet traffic between stacked Wavence shelves.

16 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addresses – Tips and Limitations
1. Tip: When assigning addresses to TMN Interfaces, the Local Address may
be set to match the address of one external TMN Interface but no more
than one.

2. The Local Address must match the address of an external TMN interface if
it is in the same subnet.

3. The Wavence Local Address must be reachable from the external network.
The Local Address must be reachable from SNMP Management servers,
FTP/SFTP servers hosting upgrade software for download, and external
NTP servers. If the NE Local Address cannot be reached then some types
of SNMP Management functions will fail, provisioning operations will fail,
Remote Software downloads will fail and the Wavence NTP client will fail. A
TMN Interface address is not a substitute for the Wavence Local Address.

17 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 4. The TMN Network

18 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
The Basic TMN Network – RF PPP Links
Local Address:10.3.27.5 Local Address:172.22.37.49

RF PPP Link

•When enabled, the RF PPP link comes up as soon as the Radio channel is operational.
•It doesn’t matter what Local IP Address is assigned at either end, as long as it is unique
and the IP version is the same (IPv4 or IPv6). When the Radio link is up, the routers can
exchange packets with each other.
•TMN packets exchanged between the routers travel over the RF link in a high priority
queue.

19 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - The Basic TMN Network –
RF PPP Links Local Address:10.3.27.5 Local Address:172.22.37.49 Local Address:192.168.10.16

Site C
Site A Site B

RF PPP Link RF PPP Link

•If we move beyond a single hop, when the RF links are up:
•The NE at Site A can communicate with Site B
•The NE at Site B can communicate with Site C
•but A cannot communicate with C until routing is configured.
•For routing to function, the NE addresses must all be unique. If there are any duplicate
addresses, or if all addresses are the same (factory default), routing will fail!
•Routing can be configured dynamically or statically.
•The recommended configuration is to enable OSPF within the Wavence network for dynamic
routing.

20 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - The Basic TMN Network
Local Address:192.168.25.66 Local Address:172.22.37.49
TMN Ethernet Port: 10.0.2.1

Craft Computer RF PPP Link

Craft Address:10.0.2.2
Default Gateway: 10.0.2.1

TMN Ethernet
Network

•Before external devices can gain access to this network, at least one external TMN interface must be provisioned.
•If we connect a properly addressed Craft computer to one of the TMN Ethernet Interfaces we should be able to communicate
with all the Wavences in the network, provided the Craft computer is configured to use the TMN Ethernet interface as the
Gateway to the Wavence network and OSPF is enabled or suitable static routes have been provisioned in the Wavences
•To communicate with either NE specify the Local Address of each Wavence when connecting with the Craft: 192.168.25.66
and 172.22.37.49 in this example.
❖By default the Wavence DHCP service is enabled. If the network interface of the Craft computer is set to “Obtain an IP
address automatically”, the Craft computer will be configured correctly when connecting to the TMN Ethernet Port. No user
action will be required.
❖When configured for IPv6 the Wavence provides link-local announcements using the Neighbor Discovery Protocol (NDP). This
allows Craft computers to configure themselves through stateless auto-configuration.

21 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - A Simple Linear Network

TMN
Port #4 In-Band
TMN Subnet RF PPP Link RF PPP Link Subnet
X Y
TMN TMN
Ethernet Ethernet TMN
Subnet Subnet Ethernet
A Subnet
B
C

• To provide local access to the Wavence and to connect external equipment to the TMN network, we
use TMN interfaces at each site. Each interface functions as gateway to the TMN Network.
• From a TMN perspective, we have a network of Routers interconnected with PPP links.
• Each TMN Interface subnet must be unique in the network. Subnets used at one interface cannot be
reused at another interface or site within the same Radio network. Subnets on different interfaces
must not overlap.
• All TMN traffic is routed. Bridging between Ethernet subnets is not supported.

22 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Supported TMN Layer 3
Network Topologies R R

R R R R R
R R

R R R R R R Ring
R R R R
R R
R R
R R R R
R
R
Linear and Tree
Mesh

• The TMN Network operates entirely at Layer 3. This network can be configured in Linear, Tree, Ring,
or Mesh topologies.
• With Ring and Mesh networks, OSPF can dynamically update the routing to take advantage of
alternate routes for TMN traffic in the event of a link failure.
• OSPF will manage routes to prevent Layer 3 loops in the TMN Network only.
Notice: The Ring and Mesh topologies depicted are ONLY applicable for TMN Networking at Layer 3.
All Wavence user data transport is performed at Layer 2. It is mandatory that the data transport
network be configured to prevent any Layer 2 Ethernet loops through the appropriate provisioning
of 802.1Q or 802.1ad VLANs, Ethernet Ring Protection, Port Segregation, or other physical means.

23 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Supported TMN Network Topologies R R R
R
R X R R R R R
Linear
R

Management Traffic R R R
Path After a failure
R Wavence TMN Router SNMP
Manager
R External Router
External
Network

• Wavence TMN Networks can have multiple external gateways that allow alternate management paths in the
event of an outage.
• To make the best use of multiple gateways, OSPF must be enabled throughout TMN Network.
• To maximize the availability of alternate TMN network paths, OSPF should be used to manage the links
between and any external routers and a suitable dynamic routing protocol should be used in the External
Network.

24 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 5. DCN Interconnections examples

25 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence (MSS 8/4/1/O) Capability IP parameters
Wavence

512 Kb/s Radio 512Kb/s Radio

Management Protocol:
SNMPv2c/V3 for supervision
FTP/sFTP for download/backup/restore
Telnet/SSH for WT-CLI Wavence-MSS1c
NTP for time synchronization
10/100 Base T
Physical DCN Ports:
10/100 Base T
1x Ethernet RJ45 10/100 BaseT for local access
with DHCP (Out of Band) 10/100 Base T

1x Ethernet RJ45 10/100/1000 BaseT, SW

configurable (Out of Band)
• MSS 8/4/1/O all have routing capability. From a
Up to 4 x Ethernet RJ45 10/100/1000 BaseT
connections (In Band) DCN/IP point of view it is a router.
Up to 2 x Ethernet SFP connections (In Band)
• Each port can use OSPF or static routing ; for each
Nx Radio links 512 Kb/s
MSS 8/4/1/O up to 3 different OSPF Areas can be
IP addressing provisioned in addition to the backbone.
1x IP address for all the radio channels (/32) that is
the same as the LocalIP address of the NE. • In case of OSPF each address must belong to an
1x IP address and associated net-mask for each OSPF area.
TMN Eth port in use
• The area can be Secondary or Totally Stub.

26 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Wavence (MSS-O/1/4/8) IPv6/OSPFv3 Capabilities
Overview
512 Kb/s Radio
512Kb/s Radio

IPv6 parameters and suggested dimensioning Wavence

Overview

• In line with IPv4 DCN. Some constraints detailed here 10/100 Base T

• IPv6 DCN cannot be managed by 1350/1353 NM 10/100 Base T

10/100 Base T
• No support for dual stack IPv4/IPv6 (only one active stack is managed) Physical DCN Ports
• 1x Ethernet RJ45 10/100 BaseT for local access
• IPv6 is supported only by MSS-O/1/4/8
without support of DHCPv6 (Out of Band) – IPv6
• DHCPv6 is not supported. Instead, IPv6 Stateless Auto-configuration is Stateless Auto-Configuration is supported (always
supported on TMN Local ETH interface enabled)
Management Protocols • 1x Ethernet RJ45 10/100/1000 BaseT SW
configurable (Out of Band) – IPv6 Stateless Auto-
• SNMPv2 and SNMPv3 for supervision Configuration is supported (always enabled for
• FTP and SFTP for download/backup/restore TMN interface)
• Telnet and SSH for Ethernet Features Shell • 4 MAX x Ethernet RJ45 10/100/1000 BaseT ports
• Remark – SNMPv3, SSH and SFTP protocols are not supported by 1350 / (In Band)
1353 NM
• 2 MAX x Ethernet SFP ports (In Band) Remark – a
• HTTPS for Debugging (special page on Web Server) maximum of 2 TMN in-band interfaces can be
• NTP for time synchronization configured for each node
• nx Radio 512 Kb/s
27 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence (MSS-O/1/4/8) IPv6/OSPFv3
Capabilities Overview 512 Kb/s Radio
512Kb/s Radio

IPv6 parameters and suggested dimensioning Wavence

IPv6 addressing
• 1x IPv6 address for all the radio channels (/128) that
10/100 Base T
is the Local IP address of the NE.
10/100 Base T
• 1x IPv6 address and relevant prefix for each used
10/100 Base T
Eth port
• Remark - refer to IANA spec for valid IPv6
addresses
IPv6 routing
• MSS-O/1/4/8 all have routing capability. From DCN/IP point of view it is a router.
• Each port can use OSPFv3 or static routing; for each MSS-O/1/4/8 up to 3 additional OSPF
Areas can be provisioned, plus the backbone.
• Recommended deployment is with maximum 2 OSPFv3 areas per node (including
backbone)
• Remark – OSPFv3 Router ID must be manually provisioned to a unique value for each
node (see System Settings) – this is mandatory
• OSPFv3 areas can be either Totally Stub or “not Stub”.
• Recommended dimensioning is to limit the maximum number of direct neighbors connected
to an Wavence Ethernet interface to 8
28 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence (MSS 1c) Capability IP parameters
Wavence

Management Protocol: 512 Kb/s Radio 512Kb/s Radio

SNMPv2c for supervision
FTP/sFTP for
download/backup/restore/provisioning
NTP for time synchronization Wavence-MSS1c

Physical DCN Ports: 10/100 Base T

10/100 Base T

2x Ethernet RJ45 10/100 BaseT port (Out

10/100 Base T
of Band) 10/100 Base T
10/100 /1000Base T 10/100 /1000 Base T
1x Ethernet RJ45 10/100/1000 BaseT
port (In Band) selectable
1 x Radio 512 Kb/s
IP addressing:
1x IP address and associated netmask for
each Eth DCN ports
1x IP address for the radio channel that is • MSS 1C has routing capability. From a
the same as the Local IP address of the NE. DCN/IP point of view it is a router.
• Each port can use static routing ; OSPF
routing available since the R3.2 release.

29 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence (MPR-e) Capability
IP parameters Wavence

512 Kb/s Radio

Management Protocol: 512Kb/s Radio

SNMPv2c for supervision

MPR-e
FTP/sFTP for download/backup/restore
NTP for time synchronization
10/100 Base T

10/100 Base T
Physical DCN Ports: 10/100 Base T
1x Ethernet Elec./Opt. 1000 (In Band)
1 x Radio 512 Kb/s

IP addressing
▪ MPR-e has routing capability. From a DCN/IP
1x IP address and relevant net-mask for point of view it is a router.
the Eth DCN port
▪ Each port can use static routing ; OSPF routing
1x IP address for the radio channel available since the R3.2 release.
that is the same as the Local IP address of
the NE.

30 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence - DCN Interconnection using
Out of Band 512Kb/s Radio 512Kb/s Radio

(OoB) Wavence
MPR-e

10/100 BT
10/100 Base T

512Kb/s Radio

Wavence

Wavence-MSS1c

10/100 BT
512Kb/s Radio

Wavence

10/100 Base T

• Multiple Wavence nodes can be chained without need for external

switch
31 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence - DCN Interconnection using In Band
(InB) 512Kb/s Radio 512Kb/s Radio

MPR-e
Wavence

10/100 BT
10/100 Base T
On these links the Supervision
is tagged and sent over the
512Kb/s Radio same links as traffic saving:
- Ethernet ports
- IP addresses
Wavence

Wavence-MSS1c

10/100 BT
512Kb/s Radio

Wavence

10/100 Base T

• Multiple Wavence nodes can be chained without need for external

switch
32 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence
DCN Interconnection using In Band (InB) w/ OEM (MPT-GS, MPT-GM, MPT-SUB6)

VID=XXX VID=XXX VID=XXX VID=XXX

IP=x.y.w.z /29 IP=x.y.w.z+1 /29 IP=x.y.w.z+2 /29 IP=x.y.w.z+3 /29
OSPF enabled DG=x.y.w.z DG=x.y.w.z OSPF enabled OEM
MPT-SUB6 PtP
MPT-GS
MPT-GM
OEM OEM
Wavence Wavence

VID=XXX VID=XXX
IP=x.y.w.z+2 /28 IP=x.y.w.z+4 /28
DG=x.y.w.z OSPF enabled
VID=XXX VID=XXX
IP=x.y.w.z /28 IP=x.y.w.z+1 /28
OSPF enabled DG=x.y.w.z

Wavence
OEM OEM
VID=XXX VID=XXX MPT-SUB6 PtMP
IP=x.y.w.z+3 /28 IP=x.y.w.z+5 /28
OEM DG=x.y.w.z OSPF enabled
Wavence

Wavence
OEM
• The OEMs use a LAN bridged addressing; they require a Default Gateway provided by
Wavence sharing the management channel.
33 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 6. Basic Wavence Address Provisioning

34 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addressing
How many addresses does an Wavence need?
A better question might be:
How much address space does an Wavence require?
To answer these questions, we need to know how the interfaces are used in
various configurations.
TMN In-Band #1
VLAN Id: 2152
User Port: 2
Address:
172.22.65.132
Netmask: Local Address:10.0.36.9
255.255.255.224 TMN In-Band #2
VLAN Id: 3720
User Port: 1,5
Address: 10.139.22.6
Netmask: 255.255.255.248

Port #4 TMN TMN Ethernet

Address: 192.168.10.0 Address: 172.16.1.86
Netmask: 255.255.255.192 Netmask: 255.255.255.248

35 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing
Examples -Adding an Wavence terminal to an existing Network
Existing Network
Other Network
*External Local Address:192.168.64.10
DHCP Server

192.168.64.1

192.168.64.0/29 TMN Ethernet

Address: 192.168.64.10
Netmask: 255.255.255.240 (/29)
Default External Gateway:192.168.64.1

•In the simplest case if an Wavence is connected to a small existing external network defined by an
external Router only requires one IP Address.
•In this configuration, the TMN Ethernet interface is assigned an address and netmask from the
existing subnet, and the Local Address can be set to match. only will use only one IP Address.
•Craft computers connect to Wavence using the external network.
•For external networks larger than a /29 the TMN Port #4 or one of the TMN In-Band interfaces should
be used reserving the TMN Ethernet Port for local direct Craft access.
*If the router or other external device is providing DHCP service in the subnet the internal DHCP server for the TMN Ethernet Port
must be disabled before connecting Wavence to the external network in order to prevent conflicts!

36 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing
Examples – Basic Addressing
When Wavence is installed at a location where no pre-existing external network is available, it must at a minimum, provide a network that can be
used for local Craft connections.
All TMN user interfaces to Wavence are Ethernet Broadcast interfaces. The smallest network that can be provisioned is a /30. This size network
supports two useable addresses one for the TMN Ethernet port and one for a Craft computer. If the TMN Ethernet interface is used for this
function the Wavence internal DHCP server should be enabled (the default) to configure the network interface on the Craft computer when it
connects.
In this example the Local Address is set differently from the TMN Ethernet address. Wavence and associated equipment use the space of 5 IP
addresses: 4 IP addresses for the TMN Ethernet (/30) network supporting a Craft computer and one for the (different) Local Address.
Local Address: 172.22.46.51

TMN Ethernet Network

10.3.27.4 Network
10.3.27.5 Wavence TMN Ethernet Port
10.3.27.6 Craft
10.3.27.7 Broadcast
Netmask: 255.255.255.252

Remember: To provision or manage this NE, the Craft or SNMP Manager must specify the 172.22.46.51 Local Address
regardless of whether the physical connection is local or remote.

37 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing
Examples – Basic Addressing
Port #4 TMN Ethernet Network
192.168.137.24 Network Number
192.168.137.25 Wavence Port #4 Local Address: 192.168.137.25
192.168.137.26 Ext Eqpt 1 TMN Ethernet Network
192.168.137.27 Ext Eqpt 2 10.3.27.4 Network Number
192.168.137.28 spare 10.3.27.5 Wavence TMN Ethernet
192.168.137.29 spare 10.3.27.6 Craft
192.168.137.30 Router Local
10.3.27.7 Broadcast
192.168.137.31 Broadcast Backhaul Net Netmask: 255.255.255.252
Netmask: 255.255.255.248 Net

1 2

For larger networks where TMN traffic will be backhauled through an external network use either Port #4 in TMN mode
or one of the TMN In-Band interfaces.

In this example we have an external router for TMN backhaul a few local external devices and use Port #4 in TMN mode. As shown the
smallest subnet that can provide sufficient addresses is a /29. The figure above shows how the addresses could be assigned.
By setting the Local Address and Port #4 address to be the same Wavence will appear to be part of the same subnet as the external
equipment from a management perspective.
This configuration requires the space of eight addresses in the Port#4 TMN network, plus the space of four addresses for the TMN
Ethernet network for a total space of 12 addresses. Note: The spare addresses left over cannot be deployed at another site. They
remains part of this subnet but are available for future site expansion. If the router were the only external device and addresses for
future expansion with external equipment were not needed the router could connect directly to TMN Port #4 and a /30 network could be
used.
Be aware that all TMN traffic is transported through the Wavence network at high priority. Normal Wavence TMN traffic is relatively low
bandwidth. A high volume of Ethernet traffic to and from external equipment via the Wavence TMN Network may impact revenue bearing
traffic. This should be considered during the network design phase.

38 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing
TMN In-Band Interface Example Local Address:
Manager
Wavence Data traffic and TMN In- 172.22.65.132
SNMP Network Band VLAN backhaul through a
Manager single interface.
Untagged
Wavence TMN traffic
Ethernet Data
TMN In-Band #1 TMN Ethernet Network
Core Data VLAN Id: 2152 10.3.27.4 Network Number
Network User Port: 5 (SFP) 10.3.27.5 Wavence TMN Ethernet
Address: 172.22.65.132 10.3.27.6 Craft
802.1Q tagged Netmask: 255.255.255.224 10.3.27.7 Broadcast
TMN traffic Netmask: 255.255.255.252
VLAN Id: 2152

•This example shows TMN In-Band #1 configured to use Optical SFP Port #5
•Wavence data traffic also flows through this same interface. The TMN In-Band VLAN Id must be unique in the data flow so
the TMN traffic can be identified and controlled by the external equipment.
•Intermediate routers forward the combined TMN In-Band VLAN and Wavence data traffic to appropriate destinations. TMN
In-Band traffic can be steered to the appropriate destination using the VLAN Id. In this example the final external router
strips the TMN VLAN Id tags from the TMN packets on egress and sends them to the Manager network. Conversely, TMN
Traffic coming from the Manager and destined for the TMN Network must be tagged at ingress with the TMN VLAN Id before
heading to Wavence.

39 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 7. Interconnecting Multiple Wavence
Shelves

40 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing Shelf
Interconnect using TMN Port #4 Interfaces Wavence #1 Dir #35

Connecting TMN between two Wavence shelves

Wavence #1
IP Addr Equipment Comment Local
10.3.27.64 Network Netmask: 255.255.255.252 Craft
10.3.27.65 Wavence #1 Port Also Wavence #1 Local
#4 Address Wavence #2
10.3.27.66 Wavence #2 Port Also Wavence #2 Local Local
#4 Address Craft
10.3.27.67 Broadcast

Wavence #2 Dir #38

▪ Port #4 TMN ports are addressed in the same /30 subnet and connected together.
▪ TMN Traffic flowing through the site via Wavence #1 Dir #35 and Wavence #2 Dir #38 will be routed through
the TMN Port #4 interfaces.
▪ Any Wavence Data traffic must be cabled separately between shelves. This interconnect method offers
maximum flexibility with respect to how data traffic is interconnected between the two shelves.
▪ Each TMN Ethernet interface is configured with it’s own unique /30 subnet and the DHCP server in each
Wavence is enabled (details not shown). This configuration permits independent local Craft access to each
Wavence as well as the entire TMN Network.
▪ The site consumes the space of 12 addresses, four for the Port #4 /30 and eight more for the two /30 Craft
networks.

41 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing
Stacked Shelves with External Equipment and Switch Wavence #1 Dir #35

Connecting multiple Wavence shelves at a site using the Port #4 TMN interfaces

Port #4 TMN Network (/29) Wavence #1

10.3.27.64 Network Local
10.3.27.65 Wavence #1 Craft
10.3.27.66 Wavence #2 External
10.3.27.67 Wavence #3 Switch Wavence #2
10.3.27.68 External Eqpt #1 Local
10.3.27.69 External Epqt #2 Ext #1 Craft
10.3.27.70 Spare
10.3.27.71 Broadcast Ext #2 Wavence #3
Netmask: 255.255.255.248
Local
Craft
Wavence #3 Dir #38

▪All Port #4 TMN ports are addressed in the same /29 subnet and connected together with an external switch. External
site equipment may be connected to the TMN Network using via the switch.
▪TMN Traffic flowing through the site via Wavence #1 Dir #35 and Wavence #3 Dir #38 will pass through the external
switch. Wavence Data traffic must be cabled separately between shelves.

▪Local management is through the TMN Ethernet interfaces (details not shown).
▪The site consumes 20 addresses, eight for the /29 Port #4 network and twelve for the three /30 Craft networks.

42 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addressing – Stacked Shelves with TMN In-Band Wavence #1 Dir #35
Connecting multiple Wavence shelves at a site using TMN In-Band interfaces

Wavence #1
TMN In-Band Network Local
10.3.27.64 Network
10.3.27.65 Wavence #1, VLAN Id 4079, optical Port #6
Craft
10.3.27.66 Wavence #2, VLAN Id 4079, optical Ports #5 and #6
10.3.27.67 Wavence #3, VLAN Id 4079, optical Port #5 Wavence #2
10.3.27.68 Spare Local
10.3.27.69 Spare Craft
10.3.27.70 Spare
10.3.27.71 Broadcast
Netmask: 255.255.255.248 Wavence #3
Similar to the previous slide but by using the In-Band Interfaces Local
switch functionality is moved into Wavence #2. Shelf-to-shelf Data Craft
traffic is able to share the same cables.
Wavence #3 Dir #38
▪ All TMN In-Band ports are addressed in the same /29 subnet and use the same VLAN 4079. Putting all In-Band ports in the same subnet
avoids an extra routing hop between Wavence #1 and Wavence #3. In larger sites using a single subnet for interconnection will improve
address efficiency.
▪ Wavence #2 shelf has two User ports associated with In-Band VLAN 4079 and provides the switch functionality to connect Wavence#1 with
Wavence #3. TMN Traffic flowing through the site via Wavence #1 Dir #35 and Wavence #3 Dir #38 will pass through the In-Band VLAN 4079
optical switched ports in Wavence #2
▪ Shelf-to-shelf Wavence Data traffic can be transported across the same Layer 2 physical connections using separate VLANs. See the notes
on In-Band Interfaces in Section 3.
▪ Optical ports are shown in this example. A mix of Electrical and Optical or all Electrical are possible. Since Data traffic also uses these
connections using 1000Mb/s speed is recommended for Electrical ports.
▪ Local management is through the TMN Ethernet interfaces (details not shown).
▪ The site consumes the space of 20 addresses, eight for the /29 and twelve for the three /30 Craft networks.

43 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing
Another Shelf Interconnect using TMN In-Band Interfaces Wavence #1 Dir #35
Another variation connecting multiple Wavence shelves at a site using TMN
In-Band interfaces, external equipment, and no external switch
Ext #1
IP Addr Equipment Comment
10.3.27.64 Network Netmask: 255.255.255.252 Wavence #1
10.3.27.65 Wavence #1 Port Also Wavence #1 Local Addr Local
#4 Craft
Ext #2
10.3.27.66 Ext #1 External Equipment
10.3.27.67 Broadcast Wavence #2
Local
10.3.27.68 Network Netmask: 255.255.255.252
Craft
10.3.27.69 Wavence #1 In- Eth Port #3, Vlan ID: 1001
Band #1
10.3.27.70 Wavence #2 In- Eth Port #3, Vlan ID: 1001
band #1
Wavence #2 Dir #38
10.3.27.71 Broadcast
10.3.27.72 Network Netmask: 255.255.255.252
10.3.27.73 Wavence #2 Port Also Wavence #2 Local Addr
#4
10.3.27.74 Ext #2 External Equipment
10.3.27.75 Broadcast

▪ This example uses a total of five /30 subnets. This configuration is expensive in terms of the amount of address
space required (Space of 20 addresses for 6 devices) but requires no external switch while supporting one external
TMN device per Wavence shelf.
▪ The two TMN Ethernet ports are dedicated for Craft use with DHCP enabled. Craft addressing is not shown, but
would be the same as in other examples.
▪ The path for TMN Traffic flowing through the site via Dir #35 and Dir #38 is via the TMN In-Band interconnection.
▪ Shelf-to-shelf Wavence Data traffic will also flow across the same Layer2 physical connections. See the notes on In-
Band interfaces in Section 3.
44 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 8. Craft and Management
Communication Requirements

45 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking Management

We know up to five addresses can be assigned to each Wavence,

Which address must be used for Craft access?
Which address must be used for SNMP Management?

TMN In-Band Interface #1

? Address: 10.78.101.0
Local Address:172.22.46.83?

TMN In-Band Interface #2

? Address: 172.22.65.0

Port #4 TMN TMN Ethernet ?

Address: 192.168.10.0 Address: 10.0.36.9
?

46 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking Management
The Local Address is used to provision and manage Wavence.
Regardless of how either the TMN Ethernet, Port #4 TMN, or TMN In-Band Interfaces are
configured, the Local Address is the one to specify in NEtO when using the Craft, or at an
SNMP Manager.
NEtO Example

TMN In-Band #1 Local Address:172.22.46.83

Address: z.z.z.z

TMN In-Band #2
Address: w.w.w.w
TMN Ethernet
Address: yyy.yyy.yyy.yyy
Port #4 TMN
Address: xxx.xxx.xxx.xxx

Connecting to the wrong address is one of the primary reasons

for provisioning problems with Wavence !

47 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking Management
When a Craft computer is directly connected to the TMN Ethernet subnet, NEtO will find
Wavence Local Addresses through a Layer 2 Discovery Protocol. Double-clicking on a
Discovered NE entry will copy the address to the correct location for connection.
NEtO Example
Local Address:172.22.46.36

L2 Discovery Protocol

48 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking Management –Using the
Local Address
Why Must the Local Address be used for provisioning?
1. The Wavence SNMP Agent responds at all the Wavence IP
Addresses, but SNMP Traps and Notifications only originate from
the Local Address.
• When the Craft performs complex multi-step SNMP operations
such as cross-connections, it expects SNMP Notifications
verifying completion of the intermediate steps. The Craft will
be listening for these Notifications to come from the address
entered in NEtO. It will ignore Notifications that come from
other (unknown) addresses. If the Craft does not receive the
proper responses provisioning fails.

49 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking Management –Using the
Local Address (Continued)
Why Must the Local Address be used for provisioning (continued)?
2. SNMP Managers need to know which IP Addresses will be sending Traps so that
Alarms can be associated with the proper NE.
• The NFM-P and 5620 SAM are aware of Wavence operation. When an
Wavence TMN Interface is Discovered the appropriate SNMP MIB objects are
inspected to determine the Local Address of that NE. When Traps or
Notifications arrive, they can be correlated with the proper NE.
• Third party Managers using auto-discovery in an Wavence network will likely
find a mix of various TMN Ethernet interfaces and Local Addresses unless the
discovery can be restricted to just the range of addresses used for Local
Addresses. The usual symptoms of simply auto-discovering in an Wavence
network are multiple copies of each NE: one for each active TMN interface IP
address, or by Traps that arrive from ‘unknown’ NEs where the source
address can be correlated with an Wavence Local Address somewhere in the
network.

50 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking Network Communication

Local Address 1 Local Address 2 Local Address 3 TMN

In-Band
Port #4 RF PPP Link RF PPP Link Subnet
TMN Subnet
X Y
TMN
Ethernet TMN TMN
Subnet Ethernet Ethernet

VLAN
A Subnet Subnet
Local B C
Non-VLAN Local
Craft Local Aware
Craft Craft
equipment
External
Network SNMP SNMP External
Network
Manager Manager
• Communication requirements with external networks
• SNMP packets from the Local Address of each NE must have a route to the managers. This is usually provided
by either a Static Default Route at the Wavence Network borders, or learned via OSPF from external Neighboring
routers.
• External routers must be either manually configured to use an Wavence as the gateway to the network of Local
Addresses or they must learn the gateways to the Wavence network by exchanging routes with an Wavence
through OSPF.
• TMN In-Band interfaces must connect to VLAN aware equipment.

51 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 9. Planning and Addressing a
Network

52 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking - TMN Network
Planning R2 SNMP
Manager
Fiber or other

Site
Network

External
Network
E 1 2

A B D
R1
1
Site 1 2 3
Network

Ext Existing C
DHCP external
Server equipment

➢Consider the above network. For TMN purposes, it is a combination of Linear and Ring topologies.
➢External equipment [ ] ]to be managed is located at sites B, D, and E.
123
➢How could this network be addressed?

53 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning
➢Definitions for the Example:
➢The type of addresses needed will depend on whether we use IPv4 or IPv6 and the
type of connectivity required with external networks.
➢If the management network is private we can use address space intended for
private networks.
➢For IPv4 addresses for private networks are defined in RFC1918:
➢10.0.0.0 /8
➢172.16.0.0 /12
➢192.168.0.0 /24

➢For IPv6 they are defined in RFC4193

➢IPv6 addresses are typically assigned from the fd00:: /8 sub-range
(L-bit set to 1). A suitable Locally Assigned Global ID will be required.
Refer to the RFC for more information.
➢For this example we will use IPv4 with Private Addressing

54 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning
➢Definitions for the Example (continued):
➢Site A is an existing site where other equipment is already installed. An
Wavence will be added to the site. The existing subnet is 192.168.19.0/27.
Router R1 is at 192.168.19.1. The address available for Wavence is
192.168.19.23.
➢Site B is a junction. There are three external devices to be managed via the
TMN Network.
➢Site C is a repeater with no external equipment.
➢Site D is a repeater with one external device.
➢Site E is a repeater with two external devices. A new router (R2) connected
via an external link will be added to provide an alternate pathway for TMN
Traffic. The Wavence DHCP server will be used to provide DHCP services for
direct craft connections at this site.
➢Site F is a repeater with no external equipment.

55 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning
➢Definitions for the Example (continued)
➢OSPF will be enabled within the network
➢The recommended configuration is to enable OSPF within the
Wavence network whenever possible.
•Correctly configuring Static routing internally within the
Wavence network can be very complex for anything other than
trivial linear networks and is not recommended.
➢The Wavence network will be an Autonomous OSPF network. It will use Static
routing at the borders
➢The use of OSPF or Static routing between the Wavence network
border and external networks is a network design choice. When OSPF
monitors the status of a link carrying TMN Traffic and the link fails it
may be possible for OSPF to reroute the TMN traffic to use an alternate
gateway provided one is available.

56 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning
➢Definitions for the Example (continued)
➢At site A where an external network is available, Wavence will be a member of the external network, using the Port
#4 TMN interface. Wavence will be configured to use router R1 as the Default Gateway for reaching all other
external networks.
➢At site E, a new local network will be defined using router R2. This network will provide an alternate external route
for TMN traffic. The Wavence at site E will be come a member of this network and will use Router R2 as the Default
Gateway to reach the external networks
➢The Wavence Local Address will be set to match the TMN Ethernet Port address at all sites.
➢DHCP will be used for Craft computers connected to the local TMN Ethernet port.
➢Using the Wavence internal DHCP server whenever possible is recommended. The internal DHCP server will
correctly configure external Craft computers to communicate with the local Wavence and the greater TMN
Network. This eliminates the need for users to know how to manually configure a laptop at each site.

57 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking - TMN Network
Planning – New Addresses Requirements
Site TMN Ethernet Network Port #4 TMN Network Interface Comments
Interface

Site A 4 address subnet (/30) 0 new addresses (Wavence Port #4 TMN interface will be connected with the local site
assigned a spare address from network. The separate TMN Ethernet port will remain active
the existing external network) with DHCP direct Local Craft access.

Site B 4 address subnet (/30) 8 address subnet (/29) Connect external equipment to the Port #4 TMN interface.

Site C 4 address subnet (/30) (disabled) No external equipment. Local direct craft connections only.

Site D 8 address subnet (/29) (disabled) A very small local network. One external device connected to
the TMN Eth port. There is no addressing advantage in
splitting the subnet between TMN Eth and Port #4 TMN
Site E 16 address subnet (/28) (disabled) Extra addresses reserved to allow adding equipment as the
network expands.
Site F 4 address subnet (/30) (disabled) No external equipment. Direct craft connections only.
Total 40 addresses 8 addresses

➢The TMN Ethernet port with DHCP enabled will be active at all sites.
➢The Port #4 TMN interface is only enabled at two sites: A and B
➢The Addressing for the Port #4 interface at Site A is not shown here. This interface is connected
to and uses a spare address from the existing external site network. This was stated in the
Definitions near the beginning of this example.
➢At sites where external equipment is present it is connected to the Wavence using an external switch.
58 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Wavence TMN Networking
TMN Network Planning
➢With the network plan shown in the previous table, this network requires the space
of at least 48 addresses.
➢Of the 48:
➢6 addresses are assigned as Wavence Local Address/TMN Ethernet
addresses
➢1 address is assigned as a TMN Port #4 address
➢7 addresses are assigned to external equipment (including router R2)
➢14 addresses are reserved for use by the internal Wavence DHCP servers
➢6 Spare addresses
➢Netmasks require subnets to start and end on specific boundaries. For example a
subnet of 8 addresses must start at an address that is evenly divisible by 8.
➢Before we request address space from our Network Administrator, we first need to
verify what size address block will hold all our subnets. This is shown on the next
slide.

59 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Wavence TMN Networking - TMN Network
Planning Wavence A TMN Eth Subnet
Netmask: 255.255.255.252
Wavence C TMN Eth Subnet
Netmask: 255.255.255.252
xxx.xxx.xxx.0 Network (/30) xxx.xxx.xxx.16 Network (/30)
xxx.xxx.xxx.1 A TMN Eth Port xxx.xxx.xxx.17 C TMN Eth Port
xxx.xxx.xxx.2 DHCP Assigned xxx.xxx.xxx.18 DHCP Assigned Wavence E TMN Eth Subnet
xxx.xxx.xxx.3 Broadcast xxx.xxx.xxx.19 Broadcast Netmask: 255.255.255.240
Wavence B TMN Eth Subnet Wavence F TMN Eth Subnet xxx.xxx.xxx.32 Network (/28)
Netmask: 255.255.255.252 Netmask: 255.255.255.252 xxx.xxx.xxx.33 DHCP Assigned
xxx.xxx.xxx.4 Network (/30) xxx.xxx.xxx.20 Network (/30) xxx.xxx.xxx.34 DHCP Assigned
xxx.xxx.xxx.5 B TMN Eth Port xxx.xxx.xxx.21 F TMN Eth Port xxx.xxx.xxx.35 DHCP Assigned
xxx.xxx.xxx.6 DHCP Assigned xxx.xxx.xxx.22 DHCP Assigned xxx.xxx.xxx.36 DHCP Assigned
xxx.xxx.xxx.7 Broadcast xxx.xxx.xxx.23 Broadcast xxx.xxx.xxx.37 DHCP Assigned
Wavence B Port #4 TMN Subnet Wavence D TMN Eth Subnet xxx.xxx.xxx.38 DHCP Assigned
Netmask: 255.255.255.248 Netmask: 255.255.255.248 xxx.xxx.xxx.39 DHCP Assigned
xxx.xxx.xxx.8 Network (/29) xxx.xxx.xxx.24 Network (/29) xxx.xxx.xxx.40 E TMN Eth Port
xxx.xxx.xxx.9 B Port #4 xxx.xxx.xxx.25 DHCP Assigned xxx.xxx.xxx.41 E Ext Eqpt 1
xxx.xxx.xxx.10 B Ext Eqpt 1 xxx.xxx.xxx.26 DHCP Assigned xxx.xxx.xxx.42 E Ext Eqpt 2
xxx.xxx.xxx.11 B Ext Eqpt 2 xxx.xxx.xxx.27 DHCP Assigned xxx.xxx.xxx.43 Spare
xxx.xxx.xxx.12 B Ext Eqpt 3 xxx.xxx.xxx.28 D TMN Eth Port xxx.xxx.xxx.44 Spare
xxx.xxx.xxx.13 Spare xxx.xxx.xxx.29 D Ext Eqpt 1 xxx.xxx.xxx.45 Spare
xxx.xxx.xxx.14 Spare xxx.xxx.xxx.30 Spare xxx.xxx.xxx.46 Router R2
xxx.xxx.xxx.15 Broadcast xxx.xxx.xxx.31 Broadcast xxx.xxx.xxx.47 Broadcast
This shows how the required subnets could map into an arbitrary block of 48 contiguous addresses. Other arrangements
are possible. Notice the addresses for Wavence F are between the addresses of Wavence C and Wavence D. With OSPF
enabled there will be no routing complications resulting from this choice. Also notice TMN Eth Port addresses for D and E
are in the middle of the subnet. This is to limit addresses reserved by DHCP. Refer to Appendix C for more information.
60 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Wavence TMN Networking
TMN Network Planning
➢The previous slide shows how this network design will fit within the total space of 48
addresses. This is the minimum sized block number of addresses we must request to
deploy this network.
➢Depending on the availability of IP address space:
➢we could be assigned a single /26 block with 64 addresses.
➢If the availability of new address space is limited, we might be assigned exactly 48
addresses broken down as:
➢a /27 block (32 addresses) plus
➢a /28 (16 addresses)
➢If assigned separately like this, the address blocks might not be
contiguous. With OSPF enabled no special configuration for routing is
required.
➢For this example, we’ll assume we’ve been assigned 172.28.137.64 /26
➢The block contains 64 contiguous addresses ranging from 172.28.137.64 to
172.28.137.127
➢We’ll further divide this block of addresses into our own subnets following the
plan.

61 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking -TMN Network Planning Wavence C TMN Ethernet Subnet
Wavence A TMN Ethernet Subnet Wavence E TMN Ethernet Subnet
Netmask: 255.255.255.252 Netmask: 255.255.255.240
Netmask: 255.255.255.252
172.28.137.80 Network (/30) 172.28.137.96 Network (/28)
172.28.137.64 Network (/30)
172.28.137.81 C TMN Eth Port (L) 172.28.137.97 DHCP Assigned
172.28.137.65 A TMN Eth Port (L)
172.28.137.82 DHCP Assigned 172.28.137.98 DHCP Assigned
172.28.137.66 DHCP Assigned 172.28.137.99 DHCP Assigned
172.28.137.83 Broadcast
172.28.137.67 Broadcast 172.28.137.100 DHCP Assigned
Wavence F TMN Ethernet Subnet
Wavence B TMN Ethernet Subnet 172.28.137.101 DHCP Assigned
Netmask: 255.255.255.252
Netmask: 255.255.255.252 172.28.137.102 DHCP Assigned
172.28.137.84 Network (/30)
172.28.137.68 Network (/30) 172.28.137.85 F TMN Eth Port (L) 172.28.137.103 DHCP Assigned
172.28.137.69 B TMN Eth Port (L) 172.28.137.86 DHCP Assigned 172.28.137.104 E TMN Eth Port (L)
172.28.137.70 DHCP Assigned 172.28.137.87 Broadcast 172.28.137.105 E Ext Eqpt 1
172.28.137.71 Broadcast Wavence D TMN Ethernet Subnet 172.28.137.106 E Ext Eqpt 2
Wavence B Port #4 TMN Subnet Netmask: 255.255.255.248 172.28.137.107 Spare
Netmask: 255.255.255.248 172.28.137.108 Spare
172.28.137.88 Network (/29)
172.28.137.72 Network (/29) 172.28.137.109 Spare
172.28.137.89 DHCP Assigned
172.28.137.73 B Port #4 172.28.137.110 Router R2
172.28.137.90 DHCP Assigned 172.28.137.111 Broadcast
172.28.137.74 B Ext Eqpt 1
172.28.137.75 B Ext Eqpt 2 172.28.137.91 DHCP Assigned Wavence A TMN Port #4 Subnet
Address
172.28.137.76 B Ext Eqpt 3 172.28.137.92 D TMN Eth Port (L) assignments from
172.28.137.77 Spare 172.28.137.93 D Ext Eqpt 1 Netmask: 255.255.255.224 the existing
192.168.19.1 Router R1 external network
172.28.137.78 Spare 172.28.137.94 Spare at Site A.
172.28.137.79 Broadcast 172.28.137.95 Broadcast 192.168.19.23 Port #4

Merging our assigned addresses into the tables shows how to address our equipment.
Wavence Local addresses will be set to match the TMN Ethernet Port as specified in the Plan and
are labeled (L) for easy identification.
62 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 172.28.137.112 Unused
172.28.137.113 Unused
172.28.137.114 Unused
172.28.137.115 Unused
172.28.137.116 Unused
172.28.137.117 Unused
172.28.137.118 Unused
172.28.137.119 Unused
172.28.137.120 Unused
172.28.137.121 Unused
172.28.137.122 Unused
172.28.137.123 Unused
172.28.137.124 Unused
172.28.137.125 Unused
172.28.137.126 Unused
172.28.137.127 Unused

Sixteen addresses out of the 64 allocated addresses remain unused.

These will be reserved for future expansion of the network.

63 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Wavence TMN Networking
TMN Network Planning
Per the plan:
A. The Wavence at Site A will be configured as an ASBR with a static route to
pointing to R1 as it’s default gateway.
➢ This is required so that TMN traffic destined to leave the Wavence TMN
Network will have a way out
B. Conversely, External router R1 must be configured to use Wavence A as a
gateway to access the network 172.28.137.64 /26
C. The Wavence at site E will be configured as an ASBR with a static route to use R2
as it’s default gateway
➢ This defines an alternate gateway for traffic leaving the Wavence TMN
network.
D. External router R2 must also be configured to use Wavence E as a gateway for
network 172.28.137.64 /26
➢ This route provides an alternate way into the Wavence TMN Network.
Routing in the external DCN between R1 and R2 is beyond the scope of this
presentation

64 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking - TMN Network
Planning – Growing the network R
SNMP Fiber or other
Site 2
Manager
Network

G H
External
Network
E 1 2 3 4 5
1
F J

D
A B 1
R
1
1
Site 1 2 3 K
Network

Ext C 1
DHCP
Server

➢ What if the network grows and we need to expand by adding Sites G, H, J, and K?
➢ What if Site F, where we originally had no plans for expansion suddenly needs a new external device?
➢ What if the old expansion plans change, and the additional external equipment planned for site E will now be deployed at site H, leaving site E with
an excess of unused addresses?
➢ We can use some of the sixteen addresses left over from the original /26, but we don’t have enough addresses for all new the equipment. We’ll
have to request additional address space.

65 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning – Growing the network
Here’s the new plan:
Site TMN Ethernet Network Port #4 TMN Network Comments

Site E Original 16 address 8 address subnet (/29) Extra address space no longer needed. So we split the 16
subnet now a 4 address (local reallocation) address subnet, allocating 8 addresses to Port #4 TMN
subnet (/30) and 4 addresses to TMN Ethernet. The four recovered
addresses are moved to site F.
Site F (Keep existing subnet) 4 address subnet (/30) Add subnet to Port #4 TMN interface for new equipment,
(reallocated addresses using the address space recovered from Site E.
from Site E)

Site G 4 address subnet (/30) (disabled) No external equipment. Direct craft connections only.

Site H 4 address subnet (/30) 8 address subnet (/29) External eqpt connected to Port #4 TMN interface.

Site J 8 address subnet (/29) (disabled)

Site K 8 address subnet (/29) (disabled)
Total 24 new addresses 8 new addresses

➢Expansion of the network will require the space of 32 addresses, 16 of which were left over from our original
allocation, and 16 new addresses.
➢We request a new block of 16 addresses from our Network Administrator:
➢Our new address block assigned is: 172.30.10.0 /28
66 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning
Wavence A TMN Ethernet Subnet Wavence C TMN Ethernet Subnet
Netmask: 255.255.255.252 Netmask: 255.255.255.252
With the new expanded network 172.28.137.64 Network (/30) 172.28.137.80 Network (/30)
plan, original subnets at site A, B,C, 172.28.137.65 A TMN Eth Port (L) 172.28.137.81 C TMN Eth Port (L)
D, and the TMN Ethernet subnet at 172.28.137.66 DHCP Assigned 172.28.137.82 DHCP Assigned
172.28.137.67 Broadcast
site F remain unchanged. The 172.28.137.83 Broadcast

addresses are repeated here: Wavence B TMN Ethernet Subnet Wavence D TMN Ethernet Subnet
Netmask: 255.255.255.252 Netmask: 255.255.255.248
172.28.137.68 Network (/30) 172.28.137.88 Network (/29)
172.28.137.69 B TMN Eth Port (L) 172.28.137.89 DHCP Assigned
172.28.137.90 DHCP Assigned
172.28.137.70 DHCP Assigned
172.28.137.91 DHCP Assigned
172.28.137.71 Broadcast
172.28.137.92 D TMN Eth Port (L)
Wavence B Port #4 TMN Subnet
Netmask: 255.255.255.248 172.28.137.93 D Ext Eqpt 1

172.28.137.72 Network (/29) 172.28.137.94 Spare

172.28.137.73 B Port #4 172.28.137.95 Broadcast

172.28.137.74 B Ext Eqpt 1 Wavence F TMN Ethernet Subnet

172.28.137.75 B Ext Eqpt 2 Netmask: 255.255.255.252
172.28.137.76 B Ext Eqpt 3 172.28.137.84 Network (/30)
172.28.137.77 Spare 172.28.137.85 F TMN Eth Port (L)
172.28.137.78 Spare 172.28.137.86 DHCP Assigned
172.28.137.79 Broadcast 172.28.137.87 Broadcast

67 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking NEW

TMN Network Planning

Wavence E TMN Ethernet Subnet
Netmask: 255.255.255.248
172.28.137.96 Network (/30)
Wavence E TMN Ethernet Subnet 172.28.137.97 Wavence E TMN Eth
OLD Netmask: 255.255.255.240 (L)
172.28.137.96 Network (/28) 172.28.137.98 DHCP Assigned
172.28.137.97 DHCP Assigned 172.28.137.99 Broadcast
172.28.137.98 DHCP Assigned Wavence F Port #4 TMN Subnet
172.28.137.99 DHCP Assigned Netmask: 255.255.255.252
172.28.137.100 DHCP Assigned 172.28.137.100 Network (/30)
172.28.137.101 DHCP Assigned 172.28.137.101 Wavence F Port #4
172.28.137.102 DHCP Assigned 172.28.137.102 F Ext Eqpt 1
172.28.137.103 DHCP Assigned 172.28.137.103 Broadcast
172.28.137.104 E TMN Eth Port Wavence E Port #4 TMN Subnet
(L)
Netmask: 255.255.255.248
172.28.137.105 E Ext Eqpt 1 172.28.137.104 Network (/29)
172.28.137.106 E Ext Eqpt 2 172.28.137.105 E Ext Eqpt 1
172.28.137.107 Spare 172.28.137.106 E Ext Eqpt 2
172.28.137.108 Spare 172.28.137.107 Spare
172.28.137.109 Spare 172.28.137.108 Spare
172.28.137.110 Router R2 172.28.137.109 Wavence E Port #4
172.28.137.111 Broadcast 172.28.137.110 Router R2
172.28.137.111 Broadcast
This is how the old subnet E can be split to recover some unused address space. Half the address space with the external
equipment moves to the Site E Port #4 TMN subnet with a new netmask. Four addresses from the original subnet remain
assigned to the Wavence E TMN Eth subnet with a new netmask. The remaining four addresses are relocated to Site F as
a new Port #4 subnet. New or changed addressing parameters are highlighted.
68 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning
Growing the Network
Wavence G TMN Ethernet Subnet
Netmask: 255.255.252
172.28.137.112 Network (/30)
172.28.137.113 Wavence G TMN Eth
(L)
172.28.137.114 DHCP Assigned
172.28.137.115 Broadcast
Wavence H TMN Ethernet Subnet
The unused 16 addresses from the Netmask: 255.255.255.252
original /26 allocation are split into 172.28.137.116 Network (/30)
subnets and assigned at sites G and H. 172.28.137.117 Wavence H TMN Eth
(L)
172.28.137.118 DHCP Assigned
172.28.137.119 Broadcast
Wavence H Port #4 TMN Subnet
Netmask: 255.255.255.248
172.28.137.120 Network (/29)
172.28.137.121 Wavence H Port #4
172.28.137.122 H Ext Eqpt 1
172.28.137.123 H Ext Eqpt 2
172.28.137.124 H Ext Eqpt 3
172.28.137.125 Spare
172.28.137.126 Spare
172.28.137.127 Broadcast
69 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
TMN Network Planning – Growing the Network
Wavence J TMN Ethernet Subnet Wavence K TMN Ethernet Subnet
Netmask: 255.255.255.248 Netmask: 255.255.255.248
172.30.10.0 Network (/29) 172.30.10.8 Network (/29)
172.30.10.1 DHCP Assigned 172.30.10.9 DHCP Assigned
172.30.10.2 DHCP Assigned 172.30.10.10 DHCP Assigned
172.30.10.3 DHCP Assigned 172.30.10.11 DHCP Assigned
172.30.10.4 Wavence J TMN Eth 172.30.10.12 Wavence K TMN
(L) Eth (L)
172.30.10.5 J Ext Eqpt 1 172.30.10.13 K Ext Eqpt 1
172.30.10.6 Spare 172.30.10.14 Spare
172.30.10.7 Broadcast 172.30.10.15 Broadcast
•This slide shows address assignments using the new block of 16 addresses
•OSPF will automatically handle route changes within the Wavence TMN Network.
•External routers R1 and R2 will need additional static routes using Wavence A and
Wavence E respectively as gateways to reach the new 172.30.10.0/28 addresses.
•With OSPF managing routes within the Wavence network and DHCP configuring the Craft
computers the additional static routes added to the external routers are the only routing
change required.

70 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 10. Configuring Wavence

71 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Wavence Networking - Wavence Addressing –
Setting the Local Address

The Local Address is set in the Local Configuration dialog box.

a) Access the Local Configuration from the Menu by selecting:
Configuration->Network Configuration->Local Configuration
b) Enter the Local Address and click Apply
• The Local Address has an implied /32 netmask (255.255.255.255).
• Note that the WebEML Craft restricts the choices for the Local Address as if a /24 netmask was in effect.
This means Local Addresses ending in .0 or .255 cannot be assigned. This is a known limitation.
• The Wavence will reboot after this address is changed.
• After the reboot, you will need to reconnect using the new Local Address

72 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing – Preparing Port #4 for TMN mode
2

3
5
Before Port #4 can be configured for TMN any User port settings must
be disabled and returned to defaults.
1. In the Craft Equipment View, double-click on the Core Main
module. This opens the Core Main View 7
2. In the View, select the Ethernet Physical Interface tab. 6
3. Highlight the Ethernet Port#4 interface. A
4. Verify Port #4 status shows Disabled. The port status shown
here must be Disabled before TMN mode can be used.
5. To disable the port, select the Settings tab at the bottom of the
panel.
6. A: Uncheck Auto Negotiation Status, and B:Click Apply at the
bottom.
6
7. Uncheck the Enabled box in the Port Status area and click Apply. B

73 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addressing – Configuring the TMN Port #4 and In-Band Interfaces

2
1

The TMN In-Band interfaces:

1. In the Craft Equipment View, double-click on the Core 4
Main module. This opens the Core Main View
2. In the Views window select the TMN Interface tab.
Current interface settings are shown in the table.
3. Select an interface in the equipment tree or table to
configure.
4. To change the parameters, select the Settings tab in
the bottom panel and enter your settings. The
Settings panels for all TMN interfaces are similar. In-
Band Settings (shown) have a few unique items: the
VLAN ID, DSCP, PCP, and the Associated Ethernet
Ports (circled). Selection of multiple Ethernet ports is 5
allowed. All selected ports will become members of
the specified VLAN.
5. Click on Apply.

74 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addressing – Configuring MPT RF PPPoE Links
2

3
1

For RF PPPoE interfaces:

4
1. In the Craft Equipment View double-click on the
associated EAS Board. This opens the EAS Main
View.
2. In the Views panel select the desired Radio Port 6
3. Select the Additional Settings Tab
4. In the PPP RF area Enable the interface and
configure the routing as needed. No IP Address
is required, the Local Address will be used.
5. Click on Apply
6. After both ends of the radio hop have been 5
configured and the RF PPP link comes up the
detected far end Wavence Local Address will
show in the Remote Address box.

75 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addressing – Configuring Static Routes

2
Static Route Configuration:
1. Access the panel to configure static routing from the from the Main 3
Menu by selecting Configuration->Network Configuration ->IP
Configuration ->IP Static Routing Configuration
2. To add a new static route select the type of route. Use Network for a
route to a range of addresses, use Host for a route to a single device.
3. Enter the destination network number and mask or else the destination
4a 4b
host IP Address as appropriate.
4. Configure the Interface Choice
a) If the gateway is an IP address, chose Gateway IP Address and
enter the address. 5
b) If the gateway is a radio direction choose the Point to Point
Interface and select the appropriate interface from the
dropdown. See the detail
Gateways must always be on a directly attached network.
5. Click Create.

Point to Point interfaces are

selected from a dropdown

76 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking
Wavence Addressing – Defining Wavence OSPF Areas

1 4

OSPF Areas are configured in the OSPF Area Configuration panel:

1. Access the OPSF Area Configuration from the from the
Main Menu by selecting Configuration->Network 2
Configuration ->IP Configuration ->OPSF Area
Configuration
2. To add a new OSPF Area, check the ‘New’ checkbox, and fill
in the OSPF Area parameters. OSPF Area Addresses in the
Wavence are entered as dotted quads like an IP Address. If
this is a Stub Area set the Stub Flag to True
3. Click on Create. 3
4. Id values at the top left (0..3) will be used when associating
a particular OSPF area with an interface: TMN Ethernet,
TMN Port #4, TMN In-Band, or Radio. See the next slide

77 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence Networking - Wavence Addressing –
Selecting an OSPF Area for a TMN Interface
1. When provisioning a TMN
Interface, the OSPF Area is
assigned using the associated Id
from the OSPF Area Configuration
window.
2. In the Craft, select the
appropriate Id value from the
drop down lists.

OSPF Area Drop Down OSPF Area Drop Down

for TMN Ports for TMN PPP RF Links

78 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 A. Basics of IP Addressing

79 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – Addressing Standards
There are two types of IP addressing schemes:
•IPv4 - Internet Protocol version 4
•Most widely used addressing type

•IPv6 - Internet Protocol version 6

•Replacement for IPv4
Authority : IANA - Internet Assigned Number Authority
http://www.iana.org

Wavence TMN Management interfaces can be configured for either IPv4

(default) or IPv6. Simultaneous support for both IPv4 and IPv6 (dual stack) is
not supported.

80 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – IPv4 Addresses
IPv4 ADDRESS

IPv4 addresses are a 32 bit binary number:

1010 1100 0001 0110 1000 1010 1100 1111

The most common representation uses dotted decimal notation such as:
172.22.138.207

Each of the four decimal numbers represents an octet, or 8 bits, of the 32 bit
address. Each of the four numbers can range from 0 to 255. IPv4 provides an
addressing capability of 232 or about 4.3 billion addresses.

81 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – IPv4 Address parameters
The 32 bit IP addresses are divided into a Network prefix and a Host number. This
particular example shows a 22 bits allocated for the network prefix and 10 bits for the host
number:
172.22.138.207 -> 1010 1100 0001 0110 1000 1010 1100 1111
network prefix host number

There are two numbers reserved in each network, the first number and the last number.
When the Host number portion of an IP address is all zeros it is called the Network Number.
This is the first number in a Network:
1010 1100 0001 0110 1000 1000 0000 0000 -> 172.22.136.0
network prefix host number

When the Host number portion of an IP address is all ones it is called the Broadcast
Address. This is the last number in a Network:
1010 1100 0001 0110 1000 1011 1111 1111 -> 172.22.139.255
network prefix host number

82 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 The division between the network prefix and host number in an IP Address is specified using a Netmask. Like IP
Addresses, Netmasks are 32 bit numbers and the usual representation is four dotted decimal numbers. Netmasks
define the size or the number of hosts within a network.

Netmasks consists of:

▪a contiguous string of ones starting from the left end for the Network prefix portion
▪a contiguous string of zeros starting from the end of the Network prefix all the way to the right end for the Host
number portion
▪No intervening bits
Table 1
Using the example address from before with a 22 bit network prefix, the corresponding Acceptable mask values
netmask is shown:
172.22.138.207 -> 1010 1100 . 0001 0110 . 1000 1010 . 1100 1111 HEX BIN DEC
network prefix host number 00 0000 0000 0
255.255.252.0 -> 1111 1111 . 1111 1111 . 1111 1100 . 0000 0000 80 1000 0000 128
C0 1100 0000 192
E0 1110 0000 224
F0 1111 0000 240
F8 1111 1000 248
Wavence supports recommendations in RFC1812 section 2.2.5.2: Net Mask FC 1111 1100 252
Requirements for Classless Inter Domain Routing (CIDR) which allows the boundary FE 1111 1110 254
between the network and host portions to be defined in 1 bit increments. The table to FF 1111 1111 255
the right shows the allowed netmask values for any octet.

83 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking - IPv4 Addressing
Basics – Derivation of related network
parameters
Netmask are utilized for ease in computation of related Network parameters.
A logical “AND” of the Netmask and Address gives the Network Number.
A logical “OR” of the Address with the inverse of the Netmask gives the Broadcast
Address.
For example:
If my address were 10.100.49.30 and my netmask was 255.255.254.0 then I am a member of network
10.100.48.0, and my broadcast address is 10.100.49.255
10.100.49.30 -> 0000 1010 . 0110 0100 . 0011 0001 . 0001 1110 IP Address
255.255.254.0 -> 1111 1111 . 1111 1111 . 1111 1110 . 0000 0000 Netmask
---------------------------------------------
Logical AND 0000 1010 . 0110 0100 . 0011 0000 . 0000 0000 -> 10.100.48.0 Network

10.100.49.30 -> 0000 1010 . 0110 0100 . 0011 0001 . 0001 1110 IP Address
255.255.254.0 -> 0000 0000 . 0000 0000 . 0000 0001 . 1111 1111 Inverted Netmask
---------------------------------------------
Logical OR 0000 1010 . 0110 0100 . 0011 0001 . 1111 1111 -> 10.100.49.255 Broadcast

84 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IPv4 Addressing Basics – Describing Networks
(1/2)
There are two ways to describe networks:
1. Long method:
Requires 3 numbers, only two of which are needed to determine the
third.
• Network Address (all 0’s host)
• Broadcast Address (all 1’s host)
• Netmask (leading 1’s, trailing 0’s)

2. A shorthand method also called CIDR (from RFC 4632):

• In the form of the Network Number followed by a slash ‘/’ and the
Netmask length in decimal
• Trailing zeros in the Network Number are often dropped.

85 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IPv4 Addressing Basics – Describing Networks (2/2)
Long
Binary
CIDR Shorthand method
Loop back Network 0111 1111.0000 0000.0000 0000.0000 0000
1111 1111.0000 0000.0000 0000.0000 0000
127/8 NET 127.0.0.0
0111 1111.1111 1111.1111 1111.1111 1111
MASK 255.0.0.0
BCAST 127.255.255.255

One of the Reserved networks for private 1100 0000.1010 1000.0000 0000.0000 0000
address space 1111 1111.1111 1111.0000 0000.0000 0000
192.168/16 NET 192.168.0.0 1100 0000.1010 1000.1111 1111.1111 1111
MASK 255.255.0.0
BCAST 192.168.255.255
1000 1111.1101 0001.0110 0100.0000 0000
1111 1111.1111 1111.1111 1100.0000 0000
Sample Network Info 1000 1111.1101 0001.0110 0111.1111 1111
143.209.100/22 NET 143.209.100.0
MASK 255.255.252.0
BCAST 143.209.103.255

86 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – IPv4 Possible Network Sizes

Two hosts are reserved in any Ethernet Broadcast network for the Network Number, and the Broadcast address: the all 0’s
host and the all 1’s host respectively. This means the number of useable hosts is always two less than the total number of
addresses in the network.
The smallest Broadcast Ethernet network supported by Wavence is highlighted*.
Table 2
Network bits host bits useable hosts Decimal mask
31* 1 0 255.255.255.254
30 2 2 255.255.255.252
29 3 6 255.255.255.248
28 4 14 255.255.255.240
27 5 30 255.255.255.224
26 6 62 255.255.255.192
25 7 126 255.255.255.128
24 8 254 255.255.255.0
23 9 510 255.255.254.0
22 10 1022 255.255.252.0
21 11 2046 255.255.248.0
20 12 4094 255.255.240.0
19 13 8190 255.255.224.0
18 14 16382 255.255.192.0
17 15 32766 255.255.128.0
16 16 65534 255.255.0.0
… … … …
•Although RFC 3021 allows using /31 for point to point links Wavence does not support this extension.

87 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – Subnet Calculators

Calculating network parameters can be difficult for those not familiar with the
process.
The are various online Network subnet calculators available that make
derivation of all the related numbers relatively easy.
Here are examples of such tools:
http://www.subnet-calculator.com
http://www.calculator.net/ip-subnet-calculator.html
http://www.subnetmask.info

88 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – IPv6 Addresses
IPv6 addresses are a 128 bits long. The most common representation uses eight groups of
four hexadecimal words separated by colons (:)
2001:0db8:5160:c058:0000:8fd1:0513:fa0b

Each of the colon separated hexadecimal numbers represents one 16 bit word of the 128 bit
address. Each of the eight words can range from 0000 to ffff (decimal: 0 to 65535).
Addresses are case-insensitive but using only lower case hex digits is recommended.

The binary representation of the above address is shown below:

0010 0000 0000 0001 0000 1101 1011 1000 0101 0001 0110 0000 1100 0000 0101 1000 0000 0000 0000 0000 1000 1111 1101 0001 0000 0101 0001 0011 1111 1010 0000 1011
2 0 0 1 : 0 d b 8 : 5 1 6 0 : c 0 5 8 : 0 0 0 0 : 8 f d 1 : 0 5 1 : 3 f a 0 b

The 128 bits provide for an address space of 2128 or about 3.4x1038 addresses. Most of the
potential address space is unused by design. The longer addresses simplify the allocation of
addresses, enable efficient route aggregation, and enable the implementation of special
features like Stateless Auto Configuration.

89 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – IPv6 Address
Simplification Techniques
Due to the long length of IPv6 addresses there are methods to simplify written or displayed addresses. There
are two basic rules:
1) Leading zeros may be removed from any hexadecimal word.
2) Consecutive words of zero may be replaced with a double colon (::). The double colon may only be used
once in an address otherwise it becomes impossible to figure out how many zeros have been removed.
This would make the address ambiguous. RFC 5952 recommends that a double colon not be used to
eliminate a single zero.
Consider the following IPv6 addresses:
2001:0db8:0000:000b:0000:0000:0000:001a
0000:0000:0000:0000:0000:0000:0000:0001 (IPv6 loopback address)
After applying rule 1)
2001:0db8:0000:000b:0000:0000:0000:001a becomes 2001:db8:0:b:0:0:0:1a
0000:0000:0000:0000:0000:0000:0000:0001 becomes 0:0:0:0:0:0:0:1
After applying rule 2)
2001:db8:0:b:0:0:0:1a becomes 2001:db8:0:b::1
0:0:0:0:0:0:0:1 becomes ::1

90 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – Networks
As with IPv4 the 128 bit IPv6 addresses are divided into a Network prefix and a Host number using a
Netmask.

IPv6 Netmasks use the CIDR (Classless Inter-Domain Routing) style shorthand notation of a slash (/)
followed by a decimal number specifying the number of bits used for the network prefix.

For example the network written as:

2001:db8:5160:c058::/64

indicates 64 bits allocated for the network prefix and defines a network with addresses in the range:

2001:db8:5160:c058:0000:0000:0000:0000
2001:db8:5160:c058:ffff:ffff:ffff:ffff

An address and netmask for a specific interface in the above network can be written as:
2001:db8:5160:c058::1/64

91 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – Literal IPv6 addresses
When using IPv6 addresses with resource identifiers such as URLs the colon (:) conflicts
with the established syntax of using a colon to designate a port number at the end of the
host address. The workaround for this problem is to enclosed IPv6 addresses in square
brackets [ ]

Web Browsers are probably the most often used application requiring square brackets with
IPv6 addresses.

Example:
http://[fec0:0:0:1::1]/

If the URL requires a port number it goes outside the square brackets:
http://[2001:db8:5160:c058:0:8fd1:513:fa0b]:80/

Square brackets are needed around an IPv6 address when connecting to the Wavence with
a web browser.

92 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – IPv6 alternative forms
The hexadecimal representation for IPv6 addresses is the most frequently
used.

Some hybrid dual-stack IPv6/IPv4 implementations support IPv4-mapped

IPv6 addresses. This is a transition technology to aid the migration to IPv6.

These addresses are typically written with a 96-bit prefix in standard IPv6
notation and the remaining 32 bits using a dotted decimal format:

::ffff:172.22.100.10

The Wavence does not support dual-stack or IPv4-mapped IPv6 addressing.

93 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics – IPv6 Multicast

IPv6 does not implement broadcast addressing.

The traditional role of a Broadcast address is replaced by Multicast addressing to the All
Nodes multicast group.
In general it is not necessary to communicate with all nodes in a network so most IPv6
protocols that need to talk with multiple nodes use a dedicated multicast group to avoid
disturbing all the devices in the network.
Multicast addresses generally take the form: ff0x::y
Common multicast addresses are:
ff02::1 – All Nodes address
ff02::2 – All Routers address
ff02::5 – OSPFIGP
ff02::6 – OSPFIGP Designated Routers

94 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
IP Addressing Basics - Wavence Addressing
•For IPv4
•Private networks often use Addresses from those defined in RFC1918:
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
•Globally unique addresses could be used if they are available.
•It is possible to choose a globally unique address for the Local Address and use
RFC1918 addresses for the TMN interfaces

•For IPv6
•Globally unique addresses can be used.
•For private networks one suggestion would be to follow the recommendations
in RFC4193 and choosing addresses from the fd00::/8 block (L bit set to 1) and
selecting a suitable Locally Assigned Global ID.
•It is possible to choose a globally unique address for the Local Address and use
private addressing for the TMN interfaces.
95 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 B. Communication in Networks

96 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Communication
within a Network Computer 2

Network
Computer 1

A simple local network using Ethernet to allow Computer 1 and

Computer 2 to communicate with each other.
The network could be implemented with fiber, twisted-pair (such as
CAT-5) or some other technology.
The connection between the two computers could be direct using a
single crossover cable, or via a switch or hub.

97 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Communication
within a Network Computer 2
00:F8:62:CF:8A:B3

Network
Computer 1
00:C0:F8:34:19:C0

So how do two devices communicate using Ethernet?

A physical address is used to distinguish the two devices. This address is
often referred to as the MAC address, but is sometimes referred to as the
hardware address or the Ethernet address. The MAC address is a 48 bit
address assigned by the manufacturer of the network interface before it is
shipped, it is intended to be unique, and is used to help identify a machine
on a network.

98 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Communication
within a Network Computer 2
10.0.0.2
Network
Computer 1
10.0.0.1

MAC addressing is OK for direct Ethernet communication, but…

• the end user usually has no control over the address
• it is impractical outside a local network.
To make things easier for users, another communication layer is
added:
•IP Addressing

99 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Communication
within a Network
Computer 2
I’m at 10.0.0.2
Who has 00:C0:DF:48:F3:47
10.0.0.2? Network
Computer 1
10.0.0.1
Even with IP Addressing, any time one device needs to talk with
another using Ethernet, it still needs to know the MAC address for
that device.
MAC addresses are resolved by queries on the local network asking
the device you are trying to communicate with to send back its MAC
address.
The Address Resolution Protocol (ARP) is used with IPv4
For IPv6 this is part of the Neighbor Discovery (ND) protocol.

100 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Network Concepts – TCP
So how do the addressing methods fit together?
Stack
Sender Receiver
SNMP Manager Application Virtual Application
Layer SNMP Agent
Layer 5 Layer Connection

TCP, UDP Packets Transport Transport

Layer Layer
Layer 4
IP Datagram Network Network IP Addresses used
Layer Layer
Layer 3 at this layer
Ethernet Frames Data Link Data Link MAC Addresses
Layer Layer
Layer 2 used at this layer

Copper, Fiber, etc Physical Physical Physical

Network Connection Network
Layer 1

•MAC addresses are used at Layer 2

•IP Addresses are used at Layer 3

101 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts – Connecting
Networks Computer 2 Computer 4

Network A Network B

Computer 1 Computer 3

In this situation we have two isolated networks. Computer 1 can communicate with
Computer 2, and Computer 3 can communicate with Computer 4.
But what if Computer 1 needs to send a message to Computer 4?
We need a way to interface the two Networks.

102 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Router and Bridge
Comparison Sender
Application
Layer
Virtual
Connection
Receiver
Application
Layer

Transport Transport
Bridges connect Layer Layer

at Layer 2 Layer 3 Network

Bridge Network
Layer Layer
Data Link
Layer 2 Data Link Data Link Data Link
Layer Layer Layer Layer

There are two common ways Layer 1 Physical

Network
Physical Physical Physical Physical Physical
Network Connection Network
Connection Network
to connect networks
together
Sender Virtual
Receiver
Application Application
Connection
Layer Layer

Transport Router Transport

Routers connect Layer Layer
Network Network
at Layer 3 Layer 3 Network Layer Layer Network
Layer Layer
Data Link Data Link
Layer 2 Data Link Data Link
Layer Layer Layer Layer

Physical
Layer 1 Physical Physical Physical Physical Physical
Network Connection Network Network Connection Network

103 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts – Connecting Networks
Computer 2 Computer 4
10.0.0.2 10.0.0.4

Network A Switch Network B

Computer 1 Computer 3
10.0.0.1 10.0.0.3

The common Ethernet Switch is a form of bridge. The interfaces on a bridge have no IP
address. Bridges are convenient when all network devices share the same IP address
space (the same subnet). Packets received at one port are essentially repeated on the
other port(s). Most bridging devices are somewhat more intelligent about which packets
they forward and where, but that’s beyond the scope of this presentation.
Wavence TMN Network is not bridged between TMN Ports or across RF Links!

104 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts – Connecting Networks
Computer 2 Computer 4
IP 172.22.64.2 IP 192.168.10.4
Gateway 172.22.64.38 Gateway 192.168.10.137

Gateway Interface
192.168.10.137
Network A
Network B
Gateway Interface
172.22.64.38

Computer 1 Computer 3
IP 172.22.64.1 IP 192.168.10.4
Gateway 172.22.64.38 Gateway 192.168.10.137

Routers are another way to connect two networks together. Routers are used when the
two networks use different IP address space.
Unlike bridges, interfaces on a router need an address within the networks they are
attached to. The interface IP address of a router is a ‘gateway’ to other networks. Most
network devices are configured to use a nearby router as a Default Gateway.

105 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Routers
External 192.168.0.0/18 Address Range
192.168.0.0/16
Network Router
65534 addresses
192.168.0.0/20
4094 addresses
192.168.16.0/20
4094 addresses

Router
External Router B
192.168.0.0/18
Network A 16346 addresses From A
192.168.32.0/20
4094 addresses

192.168.192.0/18 192.168.128.0/18 192.168.48.0/20

16346 addresses 16346 addresses 4096 addresses

▪ A Router with multiple interfaces can also be used to divide address space into smaller networks. This process of
division can be repeated to get the desired network size, optimizing use of the available address space. Each division is
called a sub-network.
▪ In the above example, the original 192.168.64.0/16 network at the top left is divided into four subnets as the length of
the netmask is increased from 16 to 18 bits. Three of the new subnets are directly attached to Router A. One /18
subnet has been further divided into four /20 subnets using Router B as shown with the detail.
▪ Router A doesn’t need to know that Router B has divided the 192.168.64.0/18 network into subnets, it only needs to
know that the 192.168.64.0/18 aggregate address space is accessible via Router B.

106 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Route Configuration
In the Previous slide, Router A needs to know that addresses in the 192.168.64.0/18 network can be
reached by using Router B as a gateway.
There are two methods considered:
1. Static Routing where all routes are manually provisioned.
2. Dynamic Routing where routers exchange route information using a Dynamic Routing Protocol. A
Dynamic routing message exchange is depicted below: I’m Router B.
I know how to reach 192.168.0.0/20
addresses in the range: 4094 addresses
192.168.64.0/18
192.168.16.0/20
Use my gateway at:
Router 172.16.0.2
4094 addresses
Router
A B
External
Networks 192.168.32.0/20
4094 addresses

I’m Router A.
Use me for your
Default Route 192.168.48.0/20
My gateway is at: 172.16.0.1 4096 addresses

❖ There are several different dynamic routing protocols. The protocol used by Wavence is called OSPF (Open Shortest
Path First). Refer to the OSPF Appendix for more information.

107 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 C. Wavence DHCP Overview

108 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - DHCP
There are two address assignment methods:
1. Static assignment
2. Dynamic assignment

With Static Assignment, addresses are configured manually:

IP Address:
172.22.88.175
Netmask:
255.255.224.0
Default Gateway:
172.22.64.1

109 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Address Assignment
for IPv4 With Dynamic Addressing equipment on a network is configured using the Dynamic Host
Configuration Protocol (DHCP) as documented in RFC2131. Wavence provides a simple
DCHP server on the TMN Ethernet port for configuring Craft computers. This DHCP server
is enabled by Default.
Hello! I’d like to I offer to configure DHCP
configure my your network Server
network interface. interface.

Network

With DCHP, when clients connect to a network, they send a broadcast asking if there is a server that can
provide networking configuration.
If a DHCP Server is available, the client can then request its network configuration parameters.
When a DHCP Server provides an IP Address to a client it is called a Lease. The typical parameters
provided usually include: IP Address, Netmask, Default Gateway, and Lease Timeout.

110 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Address Assignment
for IPv4
•The DHCP Server is responsible for keeping track of which IP Addresses are currently
Leased and not hand out duplicates.
•When a client is finished with an IP address, it is supposed to inform the Server the address
is no longer needed. The Server will then mark the address as available for reuse.
•Leases have an associated timeout specified by the server. The Lease timeout is part of
the configuration parameter message. This timeout is the maximum time the client is
allowed to use the IP Address. Timeouts are specified in seconds and usually range from
minutes to days.
•If a client disconnects without informing the server or otherwise fails to renew the Lease
then when the timeout arrives the Server will mark the address as available for reuse.
•If a client needs an IP Address for an extended period, it must negotiate with the DHCP
server to renew the Lease prior to timeout. If the Lease expires, the client must request a
new Lease and may be assigned a different IP Address.

111 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Address Assignment
for IPv4
•DHCP is based on the Bootstrap Protocol RFC951 (BOOTP)
➢DHCP can be relayed between networks by a BOOTP Relay Agent. These
are sometimes called DHCP Relay Agents.
➢A BOOTP Relay allows DHCP clients and servers to be in different
Networks.
➢Some routers incorporate BOOTP Relay Agents.

Wavence TMN Network router does NOT Relay DHCP or BOOTP messages!

112 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts - Address Assignment
for IPv4
• Multiple DHCP Servers on a Network:
1) This is possible provided either:
• The multiple DHCP Servers share a common Lease database so they do not serve
duplicate addresses
or
• The Servers are configured to offer Leases from non-overlapping address
ranges.
2) When a client broadcasts a request looking for a DHCP server and multiple servers
respond, the client chooses the server it will use for configuration. Frequently this is
the first server to respond, but this behavior is not required.

113 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Basic Networking Concepts – DHCP in Wavence
▪ Wavence DHCP service is only available with IPv4.
▪ When configured for IPv6 the Wavence provides link-local announcements using the
Neighbor Discovery Protocol (NDP). This allows Craft computers to configure
themselves through stateless autoconfiguration.
▪ Wavence DHCP server Leases addresses based on a very specific set of rules. These
rules, defined on the following pages, are unique to Wavence and are not user
configurable.
▪ Wavence DHCP server defaults to Enabled and must be disabled before connecting the
TMN Ethernet interface to an external network controlled by another DHCP server
otherwise conflicts will occur including possible loss of connectivity in the external
network.

114 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Wavence Addressing – DHCP: Wavence DHCP Leased Address Assignment Behavior

For simplicity, the built-in DHCP server in Wavence operates using a fixed set of rules. This fixed behavior
puts restrictions on the way addresses in the TMN Ethernet Port subnet can be used whenever the
DHCP server is enabled.
1. The DHCP Server uses an address pool based on the TMN Ethernet IP address and subnet.
2. Up to 10 addresses are reserved for Leases in the following manner:
a) If the TMN Ethernet Port address is the first address in the subnet, reserve addresses
immediately above the Port to the end of the subnet or a maximum of 10 addresses, whichever
comes first.
b) If the TMN Ethernet Port address is NOT the first address of the subnet but there are 10 IP
addresses above it before the end of the subnet reserve those 10 addresses for the DHCP pool.
c) If the TMN Ethernet Port address is NOT the first address in the subnet, and there are fewer than
10 addresses above it before the end of the subnet then reserve addresses immediately prior to
the port up to a maximum of 10 addresses or the start of the subnet whichever comes first.
If the Wavence DHCP Server is enabled, the addresses reserved for DHCP Leases should not be statically
assigned to other equipment.
The manner in which DHCP addresses are reserved and assigned by the Wavence is shown with examples on
the following slides.

115 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Wavence TMN Networking
Wavence Addressing – DHCP: Wavence
Table 1
DHCP Address Assignment
Table 2
Behavior
IP Addr Equipment IP Addr Equipment
192.168.1.15 Broadcast 192.168.1.15 Broadcast
192.168.1.14 192.168.1.14
192.168.1.13 DHCP Assigned 10 192.168.1.13
192.168.1.12 DHCP Assigned 9 192.168.1.12 TMN Ethernet Port
192.168.1.11 DHCP Assigned 8
192.168.1.11 DHCP Assigned 10
192.168.1.10 DHCP Assigned 7
192.168.1.10 DHCP Assigned 9
192.168.1.9 DHCP Assigned 6
192.168.1.9 DHCP Assigned 8
192.168.1.8 DHCP Assigned 5
192.168.1.8 DHCP Assigned 7
192.168.1.7 DHCP Assigned 4
192.168.1.7 DHCP Assigned 6
192.168.1.6 DHCP Assigned 3
192.168.1.6 DHCP Assigned 5
192.168.1.5 DHCP Assigned 2
192.168.1.5 DHCP Assigned 4
192.168.1.4 DHCP Assigned 1
192.168.1.4 DHCP Assigned 3
192.168.1.3 TMN Ethernet Port 192.168.1.3 DHCP Assigned 2
192.168.1.2 192.168.1.2 DHCP Assigned 1
192.168.1.1 192.168.1.1
192.168.1.0 Network (/28) 192.168.1.0 Network (/28)

In Table 1, there are 10 addresses available above the TMN Ethernet Port address and they are
reserved for the DHCP address pool (Rule 2b). Addresses not used by the TMN Ethernet Port or
reserved for DHCP Leases can be statically assigned to other equipment.
In Table 2, there are fewer than 10 addresses available above the TMN Ethernet Port, but there are 10
available below it and they are reserved for the DHCP address pool (Rule 2c). Addresses not used by
the TMN Ethernet Port or reserved for DHCP Leases can be statically assigned to other equipment.

116 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Wavence Addressing – DHCP: Wavence DHCP Address Assignment Behavior
Table 3 Table 4 Table 5
IP Addr Equipment IP Addr Equipment IP Addr Equipment
192.168.1.7 Broadcast 192.168.1.7 Broadcast 192.168.1.7 Broadcast
192.168.1.6 DHCP Assigned 5 192.168.1.6 192.168.1.6
192.168.1.5 DHCP Assigned 4
192.168.1.5 TMN Ethernet Port 192.168.1.5
192.168.1.4 DHCP Assigned 3
192.168.1.4
192.168.1.3 DHCP Assigned 2 192.168.1.4 DHCP Assigned 4
192.168.1.3
192.168.1.2 DHCP Assigned 1 192.168.1.3 DHCP Assigned 3
192.168.1.2 DHCP Assigned 2 192.168.1.2 TMN Ethernet Port
192.168.1.1 TMN Ethernet Port
192.168.1.1 DHCP Assigned 1 192.168.1.1 DHCP Assigned 1
192.168.1.0 Network (/29) 192.168.1.0 Network (/29) 192.168.1.0 Network (/29)

In Table 3, the TMN Ethernet Port address is the first address in the subnet so addresses
above the port will be reserved. Since there are fewer than 10 addresses to the end of the
subnet all addresses are reserved for the DHCP address pool (Rule 2a). This leaves NO
addresses available for static assignment to other equipment.
In Tables 4 and 5, the TMN Ethernet Port address is not the first address in the subnet and
there are fewer than 10 addresses available above the port so addresses below the port
will be reserved. With fewer than 10 addresses available below the port all are reserved
for the DHCP address pool (Rule 2c). Addresses not used by the TMN Ethernet Port or
reserved for DHCP Leases may be statically assigned to other equipment.

117 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 D. Wavence OSPF Overview

118 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF Overview
▪ Open Shortest Path First (OSPF) is the dynamic routing protocol used with
Wavence.
▪ In IPv4 mode the Wavence uses OSPFv2 as defined in RFC 2328.
▪ In IPv6 mode the Wavence uses OSPFv3 as defined in RFC 5340.
▪ OSPF is a link-state protocol. We can think of a link as an interface to a router,
and the associated link state as a description of that interface and it’s relation to
other routers. The link state includes such info as:
• IP Address of the interface
• Netmask
• The type of network
• The routers connected to that interface
▪ The collection of these link-states for several interfaces would form a link-state
database

119 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF Overview

▪ Routers running OSPF advertise their link state to neighboring routers at

initialization and again whenever any link state information changes. The
advertisement represents the collection of all link states on that router.
▪ Routers exchange link states by means of flooding. Whenever a router receives a
link state update, it stores a copy in it’s local database and propagates the update
to other routers.
▪ After the database is updated, the router will calculate the Shortest Path tree to
all destinations. The destinations, the cost, and the next hop to reach those
destinations form the IP routing table.
▪ To control the flooding of link state updates, OSPF uses Areas. All routers within
an Area have the same link state database.

120 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF Overview Area Border Router
(ABR) Autonomous System
Boundary Router (ASBR)

Internal
Routers
Static

External
Router

▪ Routers that have all of their interfaces in the same area are called Internal Routers.
▪ Routers that belong to one or more areas and connect to the backbone must keep a
link state database for all attached areas plus the Backbone Area. These routers are
called Area Border Routers (ABR)
▪ A router that act as a gateway between OSPF and another routing protocol (including
Static routes) is called an Autonomous System Boundary Router (ASBR).

121 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF Overview Inter-Area
Route Area 2

Intra-Area
Routes

Area 1 Backbone
Area 0 Area 3

External
External
Static
Static
Routes
Routes

OSPF has special restrictions when multiple Areas are involved:

• If more than one area is configured, ONE of these areas must be Area 0. This area is defined as the
Backbone. When designing networks, it’s good practice to start with Area 0 and expand into other
areas later on.
• The backbone has to be at the center of all other areas. All other areas must be physically attached
to the backbone. OSPF expects all non-zero areas to inject routes into the backbone and the
backbone will redistribute this information to the other areas.

122 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking - Network Services -
OSPF External
Static
Stub Area 2

Routes
ASBR
ABR

Area 1 Backbone
Area 0 Area 3

ASBR
External
Static
Routes
Stub Areas:
• OSPF allows certain areas to be defined as Stub Areas. Routes to external networks, including those
learned through other protocols are not allowed to be flooded into these areas. Routing from Stub areas
to the outside world is based on a default route to the nearest ABR. Configuring an area as a Stub
reduces the size of the routing database within the area.
• An area could be qualified as a Stub if there is a single exit point from the area or if routing to
destinations outside the area do not need to take an optimal path. In the example above, Area 2 is
shown as a Stub, Area 3 could be a candidate for a Stub.
• Stub areas can have more than one ABR but must not contain any ASBR.
• All routers within a Stub area must have the Stub Flag set.

123 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF
Wavence OSPF Features
▪ Each Wavence supports up to 3 non-zero user defined OSPF Areas, for a total of 4 Areas.

▪ Area 0 is always defined in each Wavence and cannot be deleted. Area 0 does not have to be associated with any interface unless the Wavence is
acting as an ABR.

• The Wavence becomes an Area Border Router (ABR) when at least one TMN interface is associated with Area 0 and one or more other TMN
interfaces are associated with non-zero Areas. If the Wavence has connections to multiple OSPF Areas at least one active TMN interface must be
assigned to Area 0.

• Wavence will act as an Autonomous System Border Router (ASBR) when:

1) OSPF is selected as the Routing Protocol for a TMN Interface

2) At least one Static Route is configured to reach a Gateway through that TMN Interface

3) There is no OSPF Adjacency with the Gateway router

▪ Stub Area support

▪ Set the Stub Flag to True on each Wavence in the area. The Wavence can only be configured for Stub True or False. There is no support for
Not So Stubby Areas (NSSA)

▪ The Wavence has no options to suppress Type 3 Summary LSAs (Totally Stubby) or configuring route summarization. To limit the size of the
route table in a Stub area use a more configurable external router for the ABR and restrict the routes advertised into the Wavence OSPF
Areas or configure the interface of the external ABR for Totally Stubby operation.

▪ There is no support for provisioning Virtual Links

▪ Authentication is not supported.

124 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF
Wavence OSPF Features cont.
▪ RouterID (RID)
▪ With OSPFv2 the Local Address is automatically used as the RID.
▪ With OSPFv3 the RID must be explicitly set and must be unique within the
autonomous system.
▪ Router Priority fixed to 1.
▪ Router Priority affects the Designated Router (DR) Election process.
▪ If you want external routers to have a greater chance of becoming the DR
configure them to have a Router Priority greater than 1.
▪ Note that if the DR goes down or becomes unreachable an Wavence might
become the DR. If it is possible for an Wavence to become the DR the maximum
number of direct neighbors supported in the same Broadcast network is eight.

125 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF
Wavence OSPF Deployment Hints
▪ The recommended limit for the number of entries in the Wavence routing table, including both
Static and Dynamic entries, is around 200.
▪ Route tables with more than 250 entries are not supported. This provides sufficient margin for
OSPF convergence and proper operation. When the maximums are reached or exceeded random
routes will be silently dropped with a consequent impact on remote management. Dropped routes
raise no faults or alarms.
• To estimate the size of the OSPF routing table in an Area sum together:
• 1 entry for each active RF-PPP link
• 1 entry for each active TMN In-Band interface in each Wavence (up to two)
• 1 entry for each active TMN Port #4 interface in each Wavence
• 1 entry for each active Local TMN Ethernet Interface in each Wavence
• 1 entry for the NE Local Address (only if it does not match an interface address)
• 1 entry for each static route provisioned in the Wavence network.
• 1 entry for each route distributed into the Area from the ABR
• See the example on the next page

126 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services – OSPF
Wavence OSPF Deployment Hints cont.

• Example: A typical repeater supporting:

• two Radio Directions
• an active TMN Port #4 interface with a matching Local Address
• an active TMN Ethernet port
• will contribute up to 4 route entries to the OSPF routing tables.
• A general Rule of Thumb is to put no more than about 50 Wavences in an autonomous OSPF system
• This is based on a target route table size of about 200 entries and an average of about 4
active interfaces per Wavence: (200 / 4 = 50 )
• If a Wavence OSPF area is attached to an external OSPF system it may be necessary to provision the
external router to act as the ABR and restrict Type 3 Summary LSAs flooded into the Wavence area
or else use route summarization to keep the size of the route table within recommended limits. One
way to achieve this would be to configure the external router interface to the Area for Total Stub
(stub, no-summaries).

127 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Other Wavence OSPF Fixed Parameters
It may be necessary to configure several OSPF parameters on external routers to
match the values in Wavence before an adjacency can be formed.
Wavence OSPF parameters are:
➢ Hello Interval: 10 seconds
➢ Router Dead Interval: 40 seconds
➢ MTU: 1500 bytes
➢ Retransmit Interval: 5 seconds
➢ Interface Transit Delay: 1 second
➢ Router Priority: Fixed to 1 (lowest priority)
➢ Note: In an IPv6 environment, the maximum size LSA supported by Wavence
is 1280 bytes. LSAs larger than this will be discarded.

128 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Other Wavence OSPF Deployment Hints cont.
• Wavence will not form Full adjacency with a neighboring OSPF router if:
• The Area IDs do not match
• There is a mismatch in Hello Interval, Dead Time, or MTU size
• The neighboring router is configured to require authentication.
• or other incompatible settings.
• Deleting an unused OSPF area can lead to loss of remote connectivity.
• Caution: Once OSPF Adjacency has been established changing the OSPF Area Id associated
with an Wavence TMN interface will cause a loss of Adjacency through that interface.
Changing the Area Id of the opposite end of the link to match will restore Adjacency but if
one of the routers is an ABR an NE Restart may be required at both ends of the link before
routes will be exchanged correctly. This may lead to loss of remote connectivity and
require a site visit to restart the Wavence and correct any other provisioning issues.
• An NE Restart can be performed using the ‘Supervision ->Restart NE’ function in the Craft.

129 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services - Wavence OSPF Deployment
Hints • Attaching a Wavence OSPF Area to an external OSPF network.
• When the Wavence forms an adjacency with a more fully featured external
router (such as an Nokia 7705 SAR, 7750, or other) at an OSPF Area border
the best results will be obtained when the external router is configured as
the ABR.
ABR
Preferred Area 1 Area 0
Configuration Wavence
7705/7750
or other
router

ABR
OK Area 1 Area 0
Wavence
7705/7750
or other
router

130 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services - Wavence OSPF Deployment
Hints
Other Wavence OSPF Deployment Hints
• Autonomous Wavence OSPF systems with more than one ASBR may exhibit
external reachability issues in the event of a link failure.
• Workarounds:
1) Use more fully featured external routers for the ASBRs.
2) Integrate the Wavence OSPF system with an external OSPF system.
a) Configure the Wavence OSPF area as a Stub to help limit the
number of routes advertised into the area.
b) In some cases it may be necessary to use an external ABR and
configure the interface to the Wavence Area for Totally Stubby
operation (stub with no summaries).

131 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Network Services - Wavence OSPF Deployment
Hints • Connecting an Wavence Autonomous OSPF network to external networks.
• Autonomous networks will normally require a static route in the ASBR.
• If a more fully featured external router is available (such as a Nokia 7705 or
7750 or other) using the external router as the ASBR will improve the
performance.
• If there will be multiple ASBRs in the network the external router solution is
preferred.
ASBR
External
OK Area 0 Network
Wavence

ASBR
External
Better Area 0 Network
Wavence
7705/7750
or other
router

132 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 E. Comparison to TMN Networking
in the MDR-8000

133 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 1) The MDR8000 TMN offers only one external Ethernet interface (feeding a 4 port switch).
2) The MDR8000 uses the same Local Address and TMN Ethernet address concept as Wavence where the Local Address is used for PPP
endpoint identifiers, the Local Address can be set the same as the TMN Ethernet address, and Traps originate from the Local Address.
3) MDR8000 TMN Craft port is a serial interface. The LLMAN utility is used to obtain a PPP connection through this interface in contrast to
the Ethernet craft interface of Wavence.
4) The MDR8000 TMN PPP interfaces are:
a) PPP Front Access interface
b) Repeater PPP interface.
c) RF PPP interface
These serial interfaces are functionally equivalent to the PPP RF links in a Wavence network and serve the same purpose: providing a point
to point connection to another NE. It's mainly a hardware interface difference not a networking difference.
4) The MDR8000 TMN supports RIPv1, RIPv2 and OSPFv2 as dynamic routing protocols whereas Wavence supports OSPFv2 and OSPFv3
5) The MDR8000 TMN offers no built-in mini-DCHP server. Use of the LLMAN utility and the serial Craft port allow direct NE connections
with minimal user configuration.
6) MDR8000 TMN transport operates at 64kb/s in a dedicated out-of-band overhead channel. Wavence TMN transport uses an in-band
dedicated VLAN at a high priority supporting much higher transfer rates across the RF link.
7) The MDR8000 TMN supports a hard limit of 250 entries in the routing table but the practical number of MDR8000 NEs is limited primarily
by the slow transport channel and the number of hops (delay) to the farthest NE. The recommended maximum number of MDR8000 NEs
in an contiguous TMN Network is around 30.
Otherwise, from a TMN Networking and Addressing standpoint, the two systems are very similar.

134 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 F. MPR-e and MPR-1c differences

135 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Primary differences in IPv6 TMN vs IPv4 TMN

The major differences when running IPv6 are:

1) No DHCP support for the TMN Ethernet port when in IPv6 mode. Instead the Wavence
uses the IPv6 Stateless Address Auto Configuration (SLAAC). As a side benefit, all TMN
ports support SLAAC.
2) In IPv4 mode, alarming of the TMN Ethernet port was automatically suppressed
whenever DHCP was enabled. When using IPv6 it is necessary to manually provision
suppression of the alarm if the port will not normally be connected. Alarm
suppression is configured by changing the Alarm Profile on the TMN Ethernet port
provisioning screen to: No Alarms.
3) IPv6 uses OSPFv3. With IPv4 and OSPFv2 the OSPF Router ID was automatically set to
match the Wavence Local Address. With IPv6 this is no longer possible. The OSPFv3
Router IDs are still 32 bits long, but IPv6 addresses are 128 bits. When using OSPFv3
the Router ID must be manually set to a unique value in the overall OSPF system.
4) No dual stack operation. Wavence TMN management will be either all IPv4 or all
IPv6. There are no settings associated with User traffic. Both IPv4 and IPv6 can be
carried simultaneously.

136 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
MPRe and MPR-1c
The MPR-e, MSS-1c, and MSS-O are compact components of the
Wavence family of equipment. These units offer a subset of the full
Wavence TMN features.

The following pages highlight the TMN differences and provide

suggestions on TMN network deployment.

137 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking- MPR-e and MPR-1c
Supported Interfaces TMN In-Band
VLAN Interface NMS1
RF PPPoE

TMN In-Band RF PPPoE

VLAN Interface
CT Connector NMS2
TMN RF PPPoE
In-Band

MSS-1c
TMN
VLAN Subnet
In-Band
VLAN Subnet

Dedicated Only accessible TMN RF-PPPoE

Craft with special NMS1
Subnet Maintenance Subnet
cable

MPR-e TMN
NMS2
Subnet
CT
Connector
• The MPR-e and MSS-1c support fewer interfaces. Subnet
• The MPR-e supports one TMN In-Band VLAN interface and an RF-PPPoE link
• The MSS-1c supports:
• One TMN In-Band VLAN Interface
• Two TMN NMS interfaces for connecting to external networks
• One dedicated CT Connector for Local Craft connections
• An RF PPPoE link

138 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
MSS-O Supported Interfaces TMN Local
Management
Ethernet port
In-Band VLAN #1
RF PPPoE
In-Band VLAN #2

MSS-O TMN
In-Band #1
VLAN Subnet

RF-PPPoE

TMN
In-Band#2
VLAN Subnet
TMN
Ethernet
Subnet
• The MSS-O supports:
• Two TMN In-Band VLAN Interfaces
• One dedicated TMN Management Ethernet port for Local Craft connections
• RF PPPoE links

139 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Differences between Wavence MSS and the
MPR-e
MPR-e:
1. Starting with R03.02.00 the MPR-e supports OSPF.
a) Older releases only supported static routing.
2. The MPR-e has a dedicated Craft interface that can only be accessed using a special
service cable. This interface may be used at initial NE turn-up and is not designed to
be connected with an external network, only to a Craft computer. This dedicated
interface is configured as a DHCP server with a fixed address and subnet. The DHCP
server, NE address, and netmask are not user configurable.
a) Fixed address: 192.168.10.1
b) Fixed netmask: 255.255.255.0
3. When the radio is in service, all TMN network access is via the TMN In-Band VLAN
Interface. The VLAN Id is user configurable, but the interface is always associated
with the MPR-e Traffic interface. Accessing the TMN In-Band interface requires that
the external equipment be VLAN aware.

140 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Differences between Wavence MSS and the
MPR-1c
MPR-1c:
1. Starting with R03.02.00 the MPR-1c supports OSPF.
a) Older releases only support static routing.
2. The CT Connector port is a dedicated Craft interface. It is not designed to be
connected with an external network, only to a Craft computer. The NE is configured
on this interface as a DHCP server with a fixed address and subnet. The DHCP
server, NE address and netmask are not configurable.
a) Fixed address: 192.168.30.1
b) Fixed netmask: 255.255.255.252
3. NMS1 and NMS2 ports are dedicated TMN ports. They are functionally equivalent to
Wavence Port #4 in TMN Mode. If both NMS1 and NMS2 are enabled, they must be in
different subnets.
4. One TMN In-Band interface is supported. It may be associated with the User
Ethernet ports on the MSS-1c. The VLAN Id is user configurable. Accessing the TMN
In-Band interface requires that the external equipment be VLAN aware.
141 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Differences between Wavence MSS and the
MSS-O
MSS-O:
1. The MSS-O does not support TMN Port #4. Otherwise its networking
capabilities are identical to the MSS

142 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 G. Default and Reserved addresses

143 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 MSS-1/4/8 Shelf and MSS-O
• IPv4
• 10.0.1.2 NE Local Address
• 10.0.1.2/24 TMN Ethernet port
• 10.0.2.2/24 Port #4 in TMN Mode (MSS-1/4/8 only)
• 10.0.3.2/24 TMN In-Band #1
• 10.0.4.2/24 TMN In-Band #2

• IPv6
• FEC0:0:0:1::1/128 Local Address
• FEC0:0:0:1::1/64 TMN Ethernet port
• FEC0:0:0:2::1/64 Port #4 in TMN Mode (MSS-1/4/8 only)
• FEC0:0:0:3::1/64 TMN In-Band #1
• FEC0:0:0:4::1/64 TMN In-Band #2

144 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
Wavence TMN Networking
Default Wavence NE Addressing (Continued)

MPR-e Standalone
• 10.0.1.2 NE Local Address
• 192.168.100.1/24 TMN In-Band in VLAN 4080
• 192.168.10.1/24 Service (Maintenance) cable interface (Fixed, not configurable)

MPR-1c Shelf
• 10.0.1.2 Network Element (Local Address)
• 192.168.30.1/30 CT Port (Fixed, not configurable)
• 10.0.1.2/24 NMS Management port 1
• 10.0.2.2/24 NMS Management port 2

145 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 The following address ranges are used internally by Wavence. Addresses from the following ranges
should not be assigned as a Local Address or used for an interface address.
MSS:
• 127.0.0.0/8 Loopback
• 100.1.0.0/24 Internal Core Main to Core Spare communications
• 100.1.0.1 Core Main
• 100.1.0.2 Core Spare
• 100.2.0.0/24 Internal MSS to MPT communications
• 100.2.0.1 Core
• 100.2.0.x one for each MPT, depending on slot/port
MPR-e
• 192.168.10.1/24 Dedicated service cable interface and subnet (Fixed, not user configurable
MPR-1c
• 192.168.30.1/30 Dedicated CT Connector Port Address and subnet (Fixed, not user
configurable)

146 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 TMN Interfaces do not support jumbo frames.
The MTUs:
• TMN PPP RF links
• 1492 Byte Layer 2 MTU
• TMN Broadcast Ethernet interfaces
• 1500 Byte Layer 3 MTU
• 1518 Byte Layer 2 MTU
• 1522 Byte Layer 2 MTU for TMN In-Band with 802.1q VLAN tag.

147 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 H. NAT router

148 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
NAT Router
What is the NAT router
The Network Address Translation allows a single device, such as a router, to act as
agent between the Internet (or "public network") and a local (or "private") network. This
means that only a single unique IP address is required to represent an entire group of
computers to anything outside their network. The shortage of IPv4 addresses is the
main reason to use NAT.

NAT Router
Outgoing Outgoing
Private Public
Network Incoming Incoming Network

Local Internet
Area
Network

149 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
NAT Router
NAT Operational Characteristics:
NAT devices are application unaware and the translations are limited to
IP/TCP/UDP/ICMP headers and ICMP error messages only.

This means NAT devices are transparent to applications in many cases.

NAT devices do not change the payload of the packets as payloads tend to be
application specific. Applications and protocols that are not supported transparently
may require the use of Application Level Gateways (ALGs).

Those that want to deploy NAT based solutions need to determine their application
requirements first and assess the need for NAT extensions (i.e., ALGs) necessary to
provide application transparency for their environment.

150 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
NAT Router
What are the NAT router limitations
As described in RFC 2663 – IP Network Address Translator (NAT) Terminology and
Considerations, there are several areas where NAT devices often cause difficulties:
1) When an application payload includes an IP address,
2) FTP applications
3) When end-to-end security is needed (ex. IPSec transport mode or the TCP MD5
Signature Option)

SNMP is one such application where IP Addresses are contained within the payload. NAT
routers do not translate IP Addresses within SNMP payloads.

It is possible to have an SNMP specific ALG residing on a NAT router to perform SNMP
MIB translations that are proprietary to the private network. These will likely be custom
ALGs and NAT device dependent.

The following slides describe how NAT impacts the Wavence.

The scenarios are for a remote manager that wants to access the Wavence through a
NAT router. We do not recommend using NAT devices because of the consequences
described.
151 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
NAT Router
How Wavence equipment is impacted
-Wavence Manager IP Address and Access Control Security
Wavence uses Access Control Security based on the IP Address of the manager.
Access Control restricts access from any manager that is not registered.

Wavence WebEML Craft applications are manager applications. During the “Start Supervision” sequence a manager
registers its IP Address with the Wavence. The IP address to be registered is sent within an SNMP message. During
subsequent management communication the Wavence checks the source IP address of packets against the list of IP
Addresses for registered managers. If there is a match, communication is allowed. If there is no match, access is denied.

Consider the scenario where a Manager is on the Private side of a NAT router and the Wavence is on the Public side. During
the Start Supervision sequence the manager will register its Private address with the Wavence but the Source IP Address of
the packets will be the NAT Public address. In subsequent communication when the Wavence compares the source address
of packets to the list of registered IP Addresses it will not find a match and access will be denied.

This means there is no way to access or manage the Wavence through NAT.

152 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 NAT Router:
How Wavence equipment is impacted
-FTP application
Wavence uses FTP by default for:
• Software Download
• Backup and Restore
FTP through a NAT router requires use of an ALG. NAT implementations often provide an ALG supporting FTP for the case where
the FTP Client is located on the Private side of the NAT and the FTP Server is located on the Public side.
During Software Download, the Wavence acts as an FTP Client. If the FTP Server hosting the Wavence software for download is
behind a NAT router a suitable AGL will be needed.
During Backup and Restore the FTP role of the Wavence depends on the model. MSS-1/4/8 and MSS-O act as FTP Servers. The
MPR-e acts as an FTP Client. If the FTP transfer for the Backup and Restore passes through a NAT router, a suitable AGL will be
required.
Due to the varying FTP Client/Server roles the use of NAT with the Wavence is not recommended.

153 © 2018 Nokia 3DB 19353 AFAA TQZZA - Wavence TMN Networking Guide
 Copyright and confidentiality

The contents of this document are proprietary commercialize the feedback in any Nokia are protected by copyright according to the
and confidential property of Nokia. This product, technology, service, specification or applicable laws.
document is provided subject to confidentiality other documentation.
obligations of the applicable agreement(s). Nokia is a registered trademark of Nokia
Nokia operates a policy of ongoing development. Corporation. Other product and company names
This document is intended for use of Nokia’s Nokia reserves the right to make changes and mentioned herein may be trademarks or trade
customers and collaborators only for the improvements to any of the products and/or names of their respective owners.
purpose for which this document is submitted by services described in this document or withdraw
Nokia. No part of this document may be this document at any time without prior notice.
reproduced or made available to the public or to
any third party in any form or means without the The contents of this document are provided "as
prior written permission of Nokia. This document is". Except as required by applicable law, no
is to be used by properly trained professional warranties of any kind, either express or implied,
personnel. Any use of the contents in this including, but not limited to, the implied
document is limited strictly to the use(s) warranties of merchantability and fitness for a
specifically created in the applicable particular purpose, are made in relation to the
agreement(s) under which the document is accuracy, reliability or contents of this
submitted. The user of this document may document. NOKIA SHALL NOT BE RESPONSIBLE
voluntarily provide suggestions, comments or IN ANY EVENT FOR ERRORS IN THIS DOCUMENT
other feedback to Nokia in respect of the or for
contents of this document ("Feedback"). Such any loss of data or income or any special,
Feedback may be used in Nokia products and incidental, consequential, indirect or direct
related specifications or other documentation. damages howsoever caused, that might arise
Accordingly, if the user of this document gives from the use of this document or any contents
Nokia Feedback on the contents of this of this document.
document, Nokia may freely use, disclose,
reproduce, license, distribute and otherwise This document and the product(s) it describes

155 © 2018 Nokia