Professional Documents
Culture Documents
Product Overview: MINI-LINK 6600 R1
Product Overview: MINI-LINK 6600 R1
MINI-LINK 6600 R1
Description
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.
Contents
1 Introduction 1
2 System Overview 2
2.1 Indoor Part 2
2.2 Outdoor Part 7
1 Introduction
MINI-LINK 6600 consists of small flexible nodes for high capacity, with
advanced Ethernet functionality and designed for an efficient migration path for
customers going to an all-IP network.
MINI-LINK 6600 offers both compact nodes and nodes using plug-in units, which
make it easy to customize configurations and make future upgrades. The full
range of MINI-LINK outdoor units can easily be combined in many different
ways: traditional frequencies (6–42 GHz), V-band 60 GHz, E-band 70/80 GHz,
single and dual carrier, Coax and Ethernet interface.
Different packet migration strategies are supported by MINI-LINK 6600. For cost
efficient migration MINI-LINK 6600 are hop compatible with MINI-LINK TN R6
equipped with MMU4 A. Upgrading a site to MINI-LINK 6600, the radio unit,
antenna and outdoor cabling can be reused.
2 System Overview
Basic Node The Basic Node holds the system platform providing traffic
and system control.
Specific plug-in units provide Ethernet and PDH traffic
interfaces for connection to other network equipment, for
example radio base stations.
It also includes indoor mechanical housing, power
distribution, and cooling.
Radio Terminals A Radio Terminal provides microwave transmission and
consists of an outdoor radio connected to an indoor modem
carrier, that is, a split mount solution.
MINI-LINK 6600 provides dual carrier modem, and can be
connected to two outdoor radios to create two separate
Radio Terminals.
For more information, see Radio Link .
Network Element
Radio Terminals
Basic Node
External
Equipment
16917
Switch 14.5 Gbps 14.5 Gbps 14.5 Gbps 36.5 Gbps 44 Gbps 38 Gbps 88 Gbps(1) 46.5 Gbps 46.5 Gbps
capacity (PNM (NPU (NPU
1001) 1002) 1002)
45.5 Gbps 45.5 Gbps
(NPU (NPU
1003) 1003)
Combo – – – PNM 1001 PNM 1002 – – – –
Solution or PNM
(PFU, 1002
NPU,
MMU)
Node – – – – – NPU 1002 NPU 1002 NPU 1002 NPU 1002
Processor or (2) or or
Unit (NPU) NPU 1003 NPU 1003 NPU 1003
Single – – – MMU MMU MMU MMU MMU MMU
Carrier 1001 1001 1001 1001 1001 1001
Modem
Unit
(MMU)
Dual – –(3) – MMU MMU MMU MMU MMU MMU
Carrier (3) 1002 1002 1002 1002 1002 1002
Modem
Unit
(MMU)
Line – – – LTU 1001 LTU 1001 LTU 1001 LTU 1001 LTU 1001 LTU 1001
Terminatio
n Unit
(LTU) for
E1/DS1
Line – – – LTU 1002 LTU 1002 LTU 1002 LTU 1002 LTU 1002 LTU 1002
Terminatio
n Unit
(LTU) for
E1 and
STM-1
Ethernet – – – ETU 1001 ETU 1001 ETU 1001 ETU 1001 ETU 1001 ETU 1001
Terminatio
n Unit
(ETU)
Ethernet – – – ETU 1002 ETU 1002 ETU 1002 ETU 1002 ETU 1002 ETU 1002
Terminatio
n Unit
(ETU)
The interconnection between the outdoor part (radios and antennas) and the
indoor part is one coaxial cable per carrier interface. This cable carries full duplex
traffic, DC supply voltage, and management data.
There are three variants, MINI-LINK 6651/1 (Figure 2), MINI-LINK 6651/2
(Figure 3), and MINI-LINK 6651/3 (Figure 4).
MINI-LINK 6651/1 and MINI-LINK 6651/2 have a replaceable Fan Unit that
provides cooling for the indoor part.
Modem Unit (MMU) The MMU constitutes the indoor part of a Radio
Terminal. It determines the traffic capacity and
modulation scheme.
Power Filter Unit (PFU) The PFU filters the external power and distributes
the internal power to the plug-in units through the
backplane.
Fan Unit (FAU) The FAU provides cooling for the indoor part.
Line Termination Unit (LTU) The LTU provides E1 interfaces.
Ethernet Termination Unit The ETU provides Ethernet interfaces.
(ETU)
17417
MMU 1002
MMU 1002
1201
PFU
1002
NPU
FAU 1201
MMU 1002
1001
LTU
17934
18088
The radio and the antenna are easily installed on a wide range of support
structures. The radio is fitted directly to the antenna as standard, integrated
installation. The radio and the antenna can also be fitted separately and
connected by a flexible waveguide. In all cases, the antenna is easily aligned and
the radio can be disconnected and replaced without affecting the antenna
alignment.
The MINI-LINK 6363, MINI-LINK 6363/2, and RAU2 X radios and the antennas
are described in more detail in Radio Units and Antennas.
17460
GHz
15
ENT
ALARM
POWER
ALIGNM
RADIO
15 GHz
CABLE
GHz
15
RADIO
CABL ALARM
E
POWER
ALIGN
MENT
Installation
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.
Contents
1 Overview 1
2 Safety Information 4
3 Outdoor Installation 5
3.1 Outdoor Radio Options 5
3.2 Antenna Installation Options 5
5 Indoor Installation 7
6 Indoor Cabling 8
7 Radio Configuration 9
8 Antenna Alignment 10
11 Functional Test 13
12 Handover to OMC 14
1 Overview
If the installation must be performed in one single flow, first perform the outdoor
HW installation and outdoor radio cabling, and then continue with the indoor HW
installation followed by indoor cabling, and so on.
After the functional test has been performed, and the installation and
configuration have been verified, the site can be handed over to the Operation
and Management Center (OMC).
2 Safety Information
3 Outdoor Installation
— MINI-LINK 6363
— RAU2 X
— Installing RAU2 X
— Separate Installation
There are a number of different antenna types and sizes, as well as antenna
accessories. The antennas and their accessories are described in the Installation
folder under Antennas and Antenna Accessories.
RAU2 X requires antennas of type ANT2 (fixed or modular) or IPS2 for integrated
installation. MINI-LINK 6363 requires modular antennas with ANT3 interface or
IPS3 for integrated installation.
5 Indoor Installation
— Indoor cabinets
• RBS 6201
— Outdoor cabinets
6 Indoor Cabling
7 Radio Configuration
Configure the Radio Link, either with CLI or MINI-LINK Node GUI. If CLI is used,
it is possible to prepare a script and transfer to the NE using CLI Tool.
The packet interface on the MMU provided by the Radio Link Terminal (RLT) is
called Wide Area Network (WAN).
Note: If Automatic Transmit Power Control (ATPC) shall be used, first make
the antenna alignment with ATPC set to Off. After the antenna
alignment, set ATPC to On.
Note: The Telecom Standard is set to ETSI by default. For ANSI, the Telecom
Standard must be set, using CLI or MINI-LINK Node GUI before
continuing with the initial radio link configuration.
8 Antenna Alignment
Before antenna alignment can be performed, configure the radio link with
regards to frequency and output power.
— Aligning an Antenna
Note: There are additional ways to initially configure, for example, DCN,
Network Sync, and Radio Link. See the Operation and Maintenance
folder.
After the initial setup, additional configuration can be performed, for example,
Quality of Service, IGMP & MLD Snooping, Link Aggregation Groups, and
synchronization, either with CLI Tool or MINI-LINK Node GUI. If CLI Tool is used,
it is possible to prepare a script and transfer to the NE using CLI Tool.
11 Functional Test
— Verifying an Installation
12 Handover to OMC
When the installation and configurations have been verified, it is time to hand
over to the Operation and Maintenance Center (OMC).
Operating Instructions
© Ericsson AB 2018, 2019. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.
Trademark List
Contents
1 Overview 1
3 NE Operation Modes 4
3.1 Normal Mode 4
3.2 PNM Installation Mode 4
4 Accessing an NE Locally 5
4.1 Accessing an NE Locally Using a CLI Session 5
4.2 Accessing an NE Locally Using the CLI Tool: Local
Authentication 15
4.3 Accessing an NE Locally Using the CLI Tool: Centralized
Authentication 15
4.4 Accessing an NE Locally Using MINI-LINK Node GUI: Local
Authentication 16
4.5 Accessing an NE Locally Using MINI-LINK Node GUI:
Centralized Authentication 17
4.6 Accessing the Far End Node 18
5 Accessing an NE Remotely 20
5.1 Accessing an NE Through Ethernet Connection 20
5.2 Accessing an NE from a Remote Device 20
5.3 Accessing the Far End Remotely 20
6 Configuring IP Addressing 21
6.1 Configuring IP Addressing in Windows 7: Static IP Addressing 21
6.2 Configuring IP Addressing in Windows 7: Dynamic IP
Addressing 21
6.3 Configuring IP Addressing in Windows 8: Static IP Addressing 22
6.4 Configuring IP Addressing in Windows 8: Dynamic IP
Addressing 23
6.5 Configuring IP Addressing in Windows 10: Static IP
Addressing 23
6.6 Configuring IP Addressing in Windows 10: Dynamic IP
Addressing 24
1 Overview
This instruction describes how to access an NE through a PC, using either CLI
commands or MINI-LINK Node GUI.
2.1 Prerequisites
Make sure the following access information is available:
— Default user names and passwords for the NE and the FTP server, see
Managing User Authorization and Authentication.
— When executing a set of CLI commands, for example, a prepared CLI script
and a PC with MINI-LINK CLI Tool installed. If MINI-LINK CLI Tool is not
installed, follow the instructions in Installing or Uninstalling CLI Tool.
Otherwise, start a CLI session using Telnet or SSH, for example, Putty.
— For how to prepare and run a CLI script, see CLI User Guide and CLI Tool
User Guide.
— How to navigate in MINI-LINK Node GUI, see MINI-LINK Node GUI User
Guide.
3 NE Operation Modes
O&M
Figure 1 Example of the LEDs and the Maintenance Button on the PNM
During PNM power up (Fault (red), Operational (green), and Maintenance (blue)
LEDs on the PNM are ON), immediately press the maintenance button. The
Maintenance (blue) LED starts flashing after about two minutes, indicating that
the NE is in PNM installation mode.
The PNM installation mode is left when the PNM restarts because one of the
following reasons:
4 Accessing an NE Locally
This section describes how to access the NE locally using a USB connection.
Before starting a CLI session or a MINI-LINK Node GUI session, make sure that
the following is available:
Note: — The following instruction assumes that CLI over Telnet is used. If
CLI over SSH is used, the procedure to start a CLI session depends
on which SSH client is used. For SSH, the default port is 22 and the
user name view_user is required. After the CLI session is started,
working with CLI over SSH does not differ from working with CLI
over Telnet.
MINI-LINK Node GUI is not required when working with CLI, but it is often useful
and also needed for some tasks such as enabling CLI.
Administrator for the required access level. For more information, see Managing
User Authorization and Authentication.
The CLI must have status enabled in order to be used. This is configured in MINI-
LINK Node GUI and it requires admin role access to the NE.
Steps
1. Start MINI-LINK Node GUI and log on to the NE with admin role privilege.
4. Under CLI settings, check if the CLI is currently enabled. If it is not, select CLI
Interface.
Steps
Steps
2. Enter telnet <A.B.C.D> (<PORT>), that is, the IP address and the port
number for the NE, and press Enter.
3. Enter the view_user password for the NE (same as used for the MINI-LINK
Node GUI).
The CLI session always starts in Exec mode, indicated by > at the end of the
command prompt.
6. The user is connected to the NE as the selected user type and can configure
the system. The displayed prompt is #.
Note: Only one CLI session at a time is granted access to the NE. To
prevent blocking of the CLI, an automatic logout is performed if no
keystrokes are detected for a period of 15 minutes.
Steps
6. Text messages, for example welcome message, are displayed for the user if
the external RADIUS or TACACS+ server is configured properly.
Note: Only one CLI session at a time is granted access to the NE. To
prevent blocking of the CLI, an automatic logout is performed if no
keystrokes are detected for a period of 15 minutes.
After admin_user enabled SSH in MINI-LINK Node GUI, perform the following
steps:
Steps
2. On Session page, under Host Name (or IP Address) add the IP address or the
host name of the node. Under Connection Type select SSH.
3. On SSH page, under Preferred SSH protocol version select 2 only for SSHv2.
— login as, if <ip address is set. In this case the user has to type cli
after the displayed prompt.
5. Enter the view_user password for the NE (same as used for the MINI-LINK
Node GUI).
The CLI session always starts in Exec mode, indicated by > at the end of the
command prompt.
8. The user is connected to the NE as the selected user type and can configure
the system. The displayed prompt is #.
Note: Only one CLI session at a time is granted access to the NE. To
prevent blocking of the CLI, an automatic logout is performed if no
keystrokes are detected for a period of 15 minutes.
4.1.9.2 Login with SSH by User ID and Password through Command Line Based CLI
After admin_user enabled SSH in MINI-LINK Node GUI, perform the following
steps:
Steps
2. For SSH login, enter ssh cli@<ip address , that is, the IP address for the
NE to use SSHv2, then press Enter.
3. Enter the view_user password for the NE (same as used for the MINI-LINK
Node GUI).
The CLI session always starts in Exec mode, indicated by > at the end of the
command prompt.
6. The user is connected to the NE as the selected user type and can configure
the system. The displayed prompt is #.
Note: Only one CLI session at a time is granted access to the NE. To
prevent blocking of the CLI, an automatic logout is performed if no
keystrokes are detected for a period of 15 minutes.
After admin_user enabled SSH in MINI-LINK Node GUI, perform the following
steps:
Steps
2. On Session page, under Host Name (or IP Address) add the IP address or the
host name of the node. Under Connection Type select SSH.
3. On SSH page, under Preferred SSH protocol version select 2 only for SSHv2.
— login as, if <ip address> is set. In this case the user has to type cli
after the displayed prompt.
8. Text messages, for example welcome message, are displayed for the user if
the external RADIUS or TACACS+ server is configured properly.
Note: Only one CLI session at a time is granted access to the NE. To
prevent blocking of the CLI, an automatic logout is performed if no
keystrokes are detected for a period of 15 minutes.
4.1.10.2 Login with SSH by User ID and Password through Command Line Based CLI
After admin_user enabled SSH in MINI-LINK Node GUI, perform the following
steps:
Steps
2. For SSH login, enter ssh cli@<ip address>, that is, the IP address for the
NE to use SSHv2, then press Enter.
6. Text messages, for example welcome message, are displayed for the user if
the external RADIUS or TACACS+ server is configured properly.
Note: Only one CLI session at a time is granted access to the NE. To
prevent blocking of the CLI, an automatic logout is performed if no
keystrokes are detected for a period of 15 minutes.
Steps
Access an NE as follows:
— User (enable)
— Password
4. Click Connect.
Steps
Access an NE as follows:
— User (enable)
— Password
4. Click Connect.
Access an NE as follows:
1. Connect the USB cable between the PC and the USB connector (O&M) on the
PNM.
Access an NE as follows:
1. Connect the USB cable between the PC and the USB connector (O&M) on the
PNM.
— The four user roles with different privileges are defined on the external
RADIUS or TACACS+ server: system admin, network admin, operator,
and guest.
This can be done even if there is no configured DCN connection towards the far
end. DHCP must be enabled on the computer.
Access the far end node using the appropriate IP address in the web browser,
Telnet client, or SSH client running on the connected computer:
Table 1
Radio Link Terminal (R/S/P) IP Address
Far end on radio link terminal 1/1/1 169.254.101.1
Far end on radio link terminal 1/1/2 169.254.101.2
Far end on radio link terminal 1/2/1 169.254.102.1
Far end on radio link terminal 1/2/2 169.254.102.2
Far end on radio link terminal 1/3/1 169.254.103.1
Far end on radio link terminal 1/3/2 169.254.103.2
Far end on radio link terminal 1/4/1 169.254.104.1
Far end on radio link terminal 1/4/2 169.254.104.2
Far end on radio link terminal 1/5/1 169.254.105.1
Far end on radio link terminal 1/5/2 169.254.105.2
Far end on radio link terminal 1/6/1 169.254.106.1
Far end on radio link terminal 1/6/2 169.254.106.2
Far end on radio link terminal 1/7/1 169.254.107.1
Far end on radio link terminal 1/7/2 169.254.107.2
Far end on radio link terminal 1/8/1 169.254.108.1
Far end on radio link terminal 1/8/2 169.254.108.2
Far end on radio link terminal 1/11/1 169.254.111.1
Far end on radio link terminal 1/11/2 169.254.111.2
5 Accessing an NE Remotely
Note: When using the default static NE IPv6 address, it is possible to locally
access the NE but not any other NE in the IPv6 Data Communication
Network (DCN) as the IPv6 address is not configured for global access.
telnet ferlt-<R>-<S>-<P>
Note: The default user name in local authentication mode is cli. To start an
SSH session in centralized authentication mode, use your personal user
ID.
6 Configuring IP Addressing
Steps
3. In the Network and Internet folder, click Network and Sharing Center.
4. In the Network and Sharing Center folder, in the left column click Change
Adapter Settings.
7. Select Use the following IP address in the Internet Protocol Version dialog
box.
9. Click OK.
Steps
3. In the Network and Internet folder, click Network and Sharing Center.
4. In the Network and Sharing Center folder, in the left column click Change
Adapter Settings.
8. Click OK.
Steps
1. Right click the Network symbol in the taskbar in the bottom-right corner of
the Desktop.
3. In the Network and Sharing Center folder, click Change Adapter Settings in
the left navigation bar.
4. In the Network Connections folder, right click Local Area Connection, and
then click Properties in the shortcut menu.
6. Click Properties.
9. Click OK.
Steps
1. Right click the Network symbol in the taskbar in the bottom-right corner of
the Desktop.
3. In the Network and Sharing Center folder, click Change Adapter Settings in
the left navigation bar.
4. In the Network Connections folder, right click Local Area Connection, and
then click Properties in the shortcut menu.
6. Click Properties.
8. Click OK.
Steps
1. Right click the Network symbol in the taskbar in the bottom-right corner of
the Desktop.
3. In the Network and Sharing Center folder, click Change Adapter Settings in
the left navigation bar.
4. In the Network Connections folder, right click Local Area Connection, and
then click Properties in the shortcut menu.
6. Click Properties.
9. Click OK.
Steps
1. Right click the Network symbol in the taskbar in the bottom-right corner of
the Desktop.
3. In the Network and Sharing Center folder, click Change Adapter Settings in
the left navigation bar.
4. In the Network Connections folder, right click Local Area Connection, and
then click Properties in the shortcut menu.
6. Click Properties.
8. Click OK.
Steps
4. In the Local Area Network (LAN) settings dialog box, clear the Use a proxy
server check box and click OK.
User Guide
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.
Contents
1 Overview 1
1.1 SNMP Traps or Syslog for Sending Alarms and Events 1
1.2 Alarm Types 1
1.3 Event Types 2
1.4 Alarm and Event Severities 2
1.5 Disabling Alarm Notifications 3
1.6 Notification when the NE Configuration is Changed 3
1.7 Monitoring of Alarms and Events 4
1 Overview
All software and hardware in operation is monitored by the control system. The
control system locates and maps faults down to the correct replaceable hardware
unit. Faults that cannot be mapped to one replaceable unit result in a fault
indication of all suspect units (this may be the whole NE).
The control system generally tries to repair software faults by performing warm
restarts on a given plug-in unit or on the whole NE.
Hardware errors are indicated with a red LED found on each plug-in unit and
radio. See LED Descriptions for more information.
StateChange — An event informing that there has been a change of state in the
network element.
— NE, preventing alarms from leaving the NE. This sends an event notification
to MINI-LINK Node GUI informing that no notifications will be sent. If the
alarm notifications are enabled later on, a new notification is sent informing
about the change. New alarms on NE level are always added to the Alarm
List.
— Plug-in unit, also suppressing notifications from all the interfaces on the unit.
Disabling alarm notifications on a plug-in unit means that for all its existing
alarms a clear alarm is sent removing the alarms from the Alarm List.
Note: If an alarm notification is disabled, the Alarm and Status page will
report No Alarm for this alarm.
— AlarmID: For an alarm this uniquely identifies an entry in the Notification list.
It increases every time a new alarm occurs. Due to cleared alarms the index
will not be continuous. When the maximum is reached, the value of this
object rolls over to 1. The value 0 is used for events. Note, the same ID will be
used for a new alarm entry and when the same alarm is cleared. For an
event, simply "Event" is stated as ID.
— Source: Indicating from where the alarm or event was generated, like
hardware and interface.
— SpecificProblem: Text string detailing the probable cause. Also, the name of
the alarm or event.
The Notification List is cleared after a restart (cold or warm) of the PNM or the
NE.
For more details about the Notification List, see MINI-LINK Node GUI User Guide
and MINI-LINK Node GUI Descriptions.
The relation between the operational status and alarm severity is listed in Table
3.
Each position in the enclosure has a state, indicating whether a unit is inserted in
that position, and if there are any problems associated with that plug-in unit in
that position.
Figure 4 The Network Element Page with NE Alarms and Status in MINI-LINK
Node GUI
Valid Unit There are no problems with a unit of this type in this
position.
Inaccessible Unit
The unit has been removed from this position and the
position is reserved for units of the same type.
— Replacing a PNM
— Replacing an MMU
— Replacing an RMM
Wrong Unit The unit in this position cannot use the configuration that
is saved for this position.
Clicking the icon opens the Slot Status Table page, see
MINI-LINK Node GUI Descriptions.
Insufficient Resources
The NE does not have the resources to handle this unit.
Unsupported Unit
The plug-in unit is of a type that is not recognized by the
NE.
For example, this can happen if you insert a unit that was
released after the release of the software baseline
running on the NE. Make sure you are using the latest
system software.
Steps
1. The following example script enables SNMP traps for sending notifications:
Example
2. The following example script disables SNMP traps for sending notifications:
Note: Disabling the SNMP traps prevents alarms from leaving the NE.
Example
Steps
1. The following example script configures the timer for the NE Configuration
Changed Event. The valid timer value range is 30–86400 seconds. The
default value is 900 seconds:
Example
3. Under SNMP Manager (Trap Receiver), select Send Alarms and Events to
enable SNMP traps.
Alternatively, clear the Send of Alarms and Events checkbox to disable SNMP
traps.
Note: Disabling the SNMP traps prevents alarms from leaving the NE.
5. Specify the IP address in SNMP Manager and the port in Port. The default
port number is 162. The port number can be set to any integer value
between 2 and 65535.
6. Click Save.
Steps
Steps
Set the timer for sending the NE configuration changed event as follows:
The Notification List presents the current alarm and status information, and
alarm notification records. The Notification List is a dynamic view. The dynamic
lists are updated every time a new notification is received, unless the notification
is suppressed by any selection.
Steps
To access an Alarms and Status page, right click the entity for which you want to
view the alarms and status and click Alarms and Status.
Steps