DCN

The MINI-LINK network consists of two networks, the

traffic network and the DCN. The traffic network handles
the data transmission between, for example, radio base
stations in the mobile access network.
The DCN connects the management system to the MINI-
LINK cluster and is also used for transport of
management data between NEs. In this document the
external DCN is referred to as the connection between
the management system and NEs.
The management traffic in a MINI-LINK TN cluster is
sent over an IP based DCN. Each MINI-LINK TN is
assigned an individual IP address and contains an
embedded IP router. The embedded router supports
both static and dynamic routing, that is, Open Shortest
Path First (OSPF), to establish IP connectivity between
the NEs on different sites. On sites with multiple NEs,
the DCN Site LAN switch connects the IP DCN locally on
the site.
A MINI-LINK E cluster is using the proprietary GNM
protocol for management transport. GNM messages are
broadcasted in a GNM cluster.
The IP and GNM based management communication is
propagated in overhead channels and traffic channels
(for example E1, VC-12, and separate LAN) internally in a
MINI-LINK cluster, that is, it has no impact on traffic
capacity. However, additional DCN connections might be
required to propagate an external DCN network, that is,
a non-MINI-LINK network.
Network Example
The microwave network in Figure 2 consists of MINI-LINK
E, MINI-LINK TN, and MINI-LINK HC terminals and cross-
connect units.
The sites in Figure 2 are common examples of nodes in
a microwave network.
The requirements, from a DCN perspective, are
described in this document.
For information and technical details refer to the
technical documentation
respectively.
Site A
This site consists of MINI-LINK E terminals.
Site B
This site consists of MINI-LINK HC terminals .
Site C
This site consists of MINI-LINK TN and MINI-LINK HC
terminals.
Site D
This site consists of MINI-LINK E and MINI-LINK TN
terminals.
IP Routing
Introduction
Since MINI-LINK TN DCN is based on IP, IP routers are
required in the network to enable management data
handling. MINI-LINK NEs have built-in IP routers.
Transport of information across a network from a source
to a destination is called routing. Each router holds a
routing table with available routers, which determines
the transmission path between different routers. The
router provides two routing alternatives, static routing
and routing using the OSPF protocol. With static routing
the routing table is entered and updated manually. The
OSPF protocol enables the routers to automatically
exchange information about the routing paths. The OSPF
protocol uses information from the routing table and the
cost, that is, the port bandwidth, to determine the best
route for the transmission.
Subnet
Network Elements (NEs) connected to a common site LAN
should be
considered as a subnet, from an IP point of view. All
equipment connected to the same site LAN must be
configured with IP addresses and a subnet mask
belonging to that subnet.
Static Routing
When static routing is used the operator manually
establish the fixed routing scheme before routing is
started. Each terminal must be updated with information
about all other available terminals. Static routing is
recommended in small networks. In larger and more
complex networks, dynamic routing with OSPF is
recommended.
OSPF Protocol
The OSPF protocol automatically calculates the best route
to a destination, based on the total cost of using the
interfaces required to reach the destination. Descriptions
of the local links for a router are sent to all other
connected routers. When the network is expanded with
new nodes, information about the new routers (link-
state update) is sent to the present routers by means of
flooding. Each router that receives a link-state update
stores a copy in its
link-state database and then propagates the update to
other routers.
To put boundaries on the flooding in the network, it is
divided into smaller sections – areas. Flooding and
calculations of paths are limited to changes. within an
area. A router with all directly connected routers
belonging to the same area is an Internal Router (IR).
OSPF has restrictions when multiple areas are involved. If
more than one area is configured, one of these areas has
to be the backbone area, also called Area 0. The routers
belonging to the area 0 are Backbone Routers (BR). When
designing networks it is good practice to start with area
0 and then expand into other areas afterward. The
backbone area is the center of all other areas, thus
all other areas must be connected to it. It is important to
avoid discontinuance in the communication between
included routers in the backbone area and therefore it is
recommended to apply a meshed topology.
A router connected to more than one area, whereas
one area is the backbone area, is an Area Border
Router (ABR). This router holds information of all
connected areas.
Routers that act gateway between OSPF and other
routing protocol, such as BGP, RIP, static, and so on,
are Autonomous System Boundary Routers (ASBR). An
isolated OSPF domain is accordingly an autonomous
system.
Routers that share a common segment can become
neighbors. Before routers become neighbors they must
communicate through the Hello protocol, which also
works as a form of keep-alive control. Hello packets are
periodically sent out from each interface to its neighbors.
Designated Router (DR)
In order to minimize the amount of information on a
segment between two or more routers (IP subnet or PPP
link), the OSPF protocol selects one of the routers to
become the Designated Router (DR). The DR becomes a
central point for exchange of information on that
segment.OSPF uses priority settings in the Hello
protocol to select the Designated Router (DR). The
router with the highest priority on a segment will
become the DR for that segment. A router with priority
value zero will not become DR. In the case of two
routers in a segment having the same priority, the
router with the highest ID (IP address) will become DR.
MINI-LINK E DCN
Introduction
MINI-LINK E uses a proprietary broadcast protocol, the
GNM protocol, for communication between NEs. The
MINI-LINK E system also carries IP traffic in 2×64 kbps
channels, using an SAU IP, which has an embedded
router. Operational Considerations
MINI-LINK E terminals should not be grouped into
clusters of more than 200 NEs, when connected to the
management system from a single access point. The
access from each cluster to the IP network is made
through a terminal server port on SAU IP or a separate
terminal server. Only one of the NEs (called the front
end terminal) in each cluster should have this
connection. The clusters should not be connected to
each other. Several clusters can be connected to same
terminal server, if enough ports are available.
When a cluster is growing and approaching 200 NEs, a
split has to be done. This can be done in several ways.
One example is to choose a site consisting of at least
two AMMs and remove the NCC or EAC connection
between them. The AMMs should then be separately
connected to Service On Element Manager (SoEM), thus
forming two separate clusters. Connection to ServiceOn
Element Manager Clusters of MINI-LINK E NEs can be
connected to the external IP DCN through the SAU IP or
a terminal server.
It is also possible to connect a cluster directly to the
COM ports on the PC running the SoEM. The SAU IP and
the terminal server provide V.24 ports for connection to
one MMU in each cluster and an Ethernet interface to the
management system. The MINI LINK E terminal
connected to SoEM through the O&M port is the front-
end terminal. The maximum bandwidth required from a
front-end terminal is 1200 bps.
Connections Using SAU IP
SAU IP has an embedded terminal server for mapping the
GNM data into IP packets. The O&M port on any of the
MMUs in an AMM is connected to the terminal server port
on the SAU IP through an O&M connection, see Figure 4).
Note: Only one O&M connection to an SAU IP is allowed
in each MINI-LINK E cluster. If more than one connection
is set up, a DCN loop leading to overload in the DCN is
established.
The IP packets with GNM data is routed to the Ethernet
interface for further transportation to the SoEM. Thus,
this terminal becomes the front-end terminal to the
management system.
The SoEM connects to the IP address of the SAU IP.
Connection Using a Terminal Server
Any terminal server that fulfills the requirements below
can be used. The some Application connects to an IP
address and a port number on the terminal server. The
V.24 port on the terminal server is connected directly to
the O&M port on a MINI-LINK E MMU with a cable with a
maximum length of 15 meters.
Terminal Server Requirements
The terminal server must support the following:
• One or more RS-232 asynchronous serial interfaces
• Raw TCP connections
• Time-out on inactive connections
Configure the serial interfaces of the terminal server to
the following:
• 1200 bps
• 8 data bits
• 1 stop bit
• No parity
• No flow control
Configure the following settings (or equivalent) if they are
available in the terminal server:
• Time-out on inactive connections after 1 minute.
• Send a carriage return as a CR followed by a NULL.
• Refuse to negotiate full duplex.
• Allow all protocols to connect.
• Allow all protocols to establish outgoing connections.
• Allow both incoming and outgoing traffic.
• Disable char string for termination of the connection on
the serial interface.
Connection Using the COM Port on a PC
One or more MINI-LINK E clusters can be connected
directly to available COM
ports on the SoEM PC.
Node Communication Channel (NCC)
The Node Communication Channel (NCC) is used for
distribution of management data (GNM protocol) between
units in up to four MINI LINK E Access Module Magazines
(AMMs). NCC connection between units in one AMM is
done through the backplane, but for connection between
two or more AMMs a connector on the MMU front is used.
Alternatively, the EAC connector on SAU Basic, Exp 1 or
Exp 2, or Ethernet connector on SAU IP can be used for
interconnection of AMMs on same site.
The maximum amount of AMMs when NCC is used is as
follows:
Up to four AMM 1U-3 or AMM 2U-3 can be
interconnected through NCC, provided that the software
conditions below are fulfilled. Equipment with lower
release number can only be interconnect in pairs of two,
using NCC Two AMM 4U can be interconnected through
NCC Interconnection of up to four AMM 1U-3 and AMM
2U 3 requires a SW release equal or higher than listed in
Table 1.
Maximum cable lengths for NCC are 15 m between
different MINI-LINK E AMMs.
Ethernet
The SAU IP is equipped with an Ethernet interfaces for
interconnection of
AMMs on site, also in combination with NCC.
External Alarm Channel (EAC)
Data between AMMs (in case of more than two AMMs per
site) and to other MINI LINK E equipment within a site can
be distributed through EAC. SAU
Basic, Exp 1 and Exp 2 is equipped with two EAC
connectors respectively. There are a few limitations
concerning the use of EAC cabling:
Maximum 32 MINI-LINK E terminals per site can be
interconnected using EAC cabling.
Maximum total length of the EAC cable is 1200 m.
If these limitations prohibit implementation of the site
as required, an RAC or Ethernet connection can be
used.
Remote Alarm Channel (RAC)
RAC is used for connection of two AMMs located on
different sites. SAU Exp 1 and Exp 2 are each equipped
with two RAC connectors with different interfaces
(V.24/V.28, 9600 bps or ITU-T G.703, 64 kbps).
Hop Communication Channel (HCC)
Transmission of data between two terminals, over a
hop, is sent in separate channel, HCC (8kbps). Thus, it
is not affecting the traffic capacity.
AUX Ports
SAU IPEX provides two AUX ports (serial interfaces). The
AUX2 port is a 9 pin female D-SUB. AUX1 is a 26 pin
male high density D-SUB (that can also be used as User
IO ports). For accessing AUX1, a special Y-cable is
required.
The AUX ports support data rates from 1.2 up to 64
kbps depending on the physical mode (V.11, V.28, or
G.703).
AUX ports can be used in the following scenarios:
• Tunneling MINI-LINK IP DCN traffic over a network of
3rd party equipment (for example microwave
equipment)• Tunneling 3rd party management traffic
(for example for microwave equipment) over a MINI-
LINK IP DCN network.
• Propagating management to/from the MINI-LINK E
cluster when MINI-LINK TN is collocated with MINI-
LINK E.
IP Support
The SAU IP is designed to facilitate the integration of
MINI-LINK TN in an existing network consisting of
MINI-LINK E. The SAU IP adds, among other things, the
ability for MINI LINK E to route IP packets that, for
example, contains management data from MINI-LINK
TN. However, the internal communication between MINI
LINK E NEs is still based on the proprietary GNM
protocol as well as the communication channels
described in
The SAU IP enables routing of the IP packets to different
interfaces, which are the 64 kbps, Ethernet, V.24 and I/O
ports.
The built in router handles all 64 kbps service channels
from the MMUs (two from each MMU) in one AMM. IP
packets carried on the 64 kbps channels cannot only be
routed between all MMUs in the AMM but also to the
Ethernet interface on the SAU IP. The Ethernet interface
can further be connected to a site LAN for access of a
management system over an IP based communication
network.
The SAU IP also provides terminal server functionality
that can be used for mapping of the GNM protocol into
IP Packets. The O&M port on the MMU is then
connected with an external cable to the V.24 port on
the SAU IP. The MMU connected through the O&M port
to the SAU IP becomes the front-end terminal. Observe
that only one front-end terminal is allowed per MINI-
LINK E cluster, hence avoiding DCN loops.
IP Services
The following standard external IP services are
supported:
• Network Time Protocol (NTP) for synchronization of
internal clocks. For example, time stamping of alarm
events.
• File Transfer Protocol (FTP) can be used for transferring
of software
upgrades and also for backup or restoration of terminal
configuration.
• Domain Name System (DNS) enables the use of host
names of all
terminals.
• Dynamic Host Configuration Protocol (DHCP), used
to allocate IP
addresses in the DCN. The terminal has a DHCP relay
agent, serving other equipment connected to the site
LAN.
SAU IP Router
The SAU IP has a built in IP router for handling of traffic
on the different interfaces.
Unnumbered Interfaces
The IP router in the SAU IP uses unnumbered interfaces.
The Ethernet interface is assigned one IP address, which
is then inherited by the other interfaces.
Ethernet Interfaces
The SAU IP has a built in two-port Ethernet hub
(10/100BASE-T) for connection to other IP equipment or
site LAN. This interface is also used for local
management through MINI-LINK Craft, which provides a
graphical user interface using a standard web browser. IP
Routing Functionality
The SAU IP router supports static routing and Open
Shortest Path First (OSPF) routing protocol. The DCN
router will only work as an Internal Router (IR),
supporting only OSPF routing between terminals
belonging to the same OSPF area.
Static Routing
Each route is typed as destination, subnet mask and
gateway.
Dynamic Routing (OSPF)
SAU IP supports Dynamic Routing (OSPF).
MINI-LINK TN DCN
Introduction
MINI-LINK TN provides an IP based DCN for transport of
operation and maintenance data. Each MINI-LINK TN has
a router for handling of IP traffic. The router is
configured in MINI-LINK Craft and Command Line
Interface (CLI). CLI can use either Telnet or, if Security
Software Package is installed. SSH. MINI-LINK Craft
communicates with an embedded web server in the
terminal that displays performance, fault and
configuration data in a standard web browser on a
PC/laptop.
MINI-LINK TN can also be supervised remotely from
Service On Element Manager (SoEM), as well as any
Network Management System (NMS) using SNMP
protocol. It shall in both cases be connected to the
management system
through an IP based external DCN.
Connection to Service On Element Manager
MINI-LINK TN is connected to the management system
through the Ethernet Interface, an unstructured or
structured E1, or two asynchronous E0 interfaces.
Ethernet
The NPU plug-in units in MINI-LINK TN provide Ethernet
ports (10BASE-T,10/100BASE-T, or 1000BASE-T) for
management trafic.
Remote supervision of a network consisting of MINI-
LINK TN is realized with a connection to the Ethernet
interface on one of the NEs. The Ethernet interface on
each MINI-LINK must be assigned an IP address, subnet
mask and default gateway.
Structured/Unstructured E1
MINI-LINK TN can use up to two of its connected E1s for
transport of IP DCN. It can be a fixed E1 connected to an
NPU or LTU, an E1 transported in an STM-1
frame or an E1 transported over a radio link. PPP over E1
can either be used as a single IP DCN connection, that is,
a PPP/E1 terminated in a router at the operator’s OMC
site or to build IP DCN chains.
Note: NPU 8×2 only supports the use of DCN over
unstructured E1.
The following options are available:
• Dedicated E1 for DCN
A structured or unstructured E1 can be dedicated for
DCN.
For the structured E1, n×64 kbps time slots can be
configured for DCN transport. The remaining time slots
are unused, that is, they cannot be used to transport
traffic. For the unstructured E1, the entire 2 Mbps is
used for DCN transport.
A router is required for terminating the E1, before
connection to the
management system, when using an external
transmission link.
• E1 with traffic pass-through
MINI-LINK TN supports an embedded multiplexing
feature on the NPU enabling insertion of IP DCN in spare
time slots (n×E0 over traffic). In a structured E1 used for
traffic, n×64 kbps time slots can be used for DCN
transport. The time slots used for traffic is cross-
connected in normal manner through the NE. This PPP
channel has to be established manually.
E0
The SMU2 plug-in units provide two asynchronous co-
directional E0 (64 kbps) interfaces for transport of
management traffic. The E0 interface can be connected
to transmission equipment with octet sync.
DCN Channels
The channels are used for transport of operation and
maintenance data over the hop and with peripheral
systems.
Point-to-point Protocol Links
For connection to MINI-LINK TN on other sites, point-
to-point links using Point-to-point Protocol (PPP) can
be established to the IP router at the other end.
These links are automatically setup in various overhead
channels,
provided that the other end is MINI LINK TN.
Over a radio hop where both sides are MINI-LINK TN, a
PPP link is
automatically setup over n×64 kbps in the radio frame
overhead, where n=1–12. The modem units utilize the
same channel (HCC) over a hop as MINI-LINK E for their
internal communication.
Management data over a MINI-LINK TN microwave hop
is sent over two channels with the total capacity n×64
kbps, where n=1–12, as well as over the HCC channel (8
kbps).
The 64 kbps channels are also used for connection of
two MINI-LINK TN NEs over a MINI-LINK E hop. Both
SAU IP and SAU Exp 1 provide the MINILINK E AMMs
with the required interfaces for connection to MINI-LINK
TN.
Management data for MINI-LINK E is, however, still
transported through HCC over the hop. When using
SAU IP, the connection is established through the
Ethernet ports on the SAU IP and the NPU plug-in unit
on MINI-LINK TN, see Figure 25.An SMU2 plug-in unit
for MINI-LINK TN is required when a connection
(2×E0) is made to the SAU Exp 1 (MINI-LINK E).
DCN Connection to MINI-LINK E
MINI-LINK TN has a built-in terminal server functionality
that provides DCN connection to MINI LINK E.
For MINI-LINK E terminals on the other end of the hop,
the management data is sent in HCC
For MINI-LINK E on the same site as MINI-LINK TN, the
connection is done through the O&M ports (V.24) on the
MMU and the SMU2 or SAU3.
The NPU board has a built in IP router for handling of
traffic on the different interfaces, see Figure 30.
The IP router in MINI-LINK TN can be configured for the
use of both
unnumbered as well as numbered interfaces.
Unnumbered is default. Only the Ethernet interface has to
be assigned an IP address, which is inherited by the PPP
interfaces.
When numbered interfaces are chosen, each router
interface is configured with unique IP addresses,
belonging to separate networks. When the router is acting
as Area Border Router (ABR), numbered interfaces are
mandatory.
IP Routing Functionality
The MINI-LINK TN router supports static routing and Open
Shortest Path First (OSPF) routing protocol.
The router supports ABR functionality from release 2.0 of
MINI-LINK TN. In earlier releases, the DCN router will only
work as an Internal Router (IR),supporting only OSPF
routing between terminals belonging to the same OSPF
area.
Static Routing
Each route is typed as destination, subnet mask and
gateway.
Dynamic Routing (OSPF)
SAU3 supports Dynamic Routing (OSPF