Operating Instruction     1543-CSH 109 32/1-V2 Uen A    

MINI-LINK TN ANSI

© Ericsson AB 2007 - All Rights Reserved.

Disclaimer

No part of this document may be reproduced in any form without the written permission of the copyright owner.

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.1 Target Group
1.2 Revision Information
1.3 Related Documents
1.4 Conventions
1.5 Copyright for Third Party Software Products
1.6 Technical Support

2

System Overview
2.1 Indoor Part with AMM
2.2 Outdoor Part
2.3 Management

3

Getting Started
3.1 System Requirements
3.2 Installing Software
3.3 Starting the LCT
3.4 Uninstalling Software

4

Using the EEM
4.1 User Interface Overview
4.2 Navigation Tree
4.3 Menus
4.4 Status Bar
4.5 Confirm Button
4.6 Using the Help
4.7 Naming Principles
4.8 EEM Troubleshooting

5

Initial Setup
5.1 Radio Terminal Configuration
5.2 Automatic Configuration of NE Parameters
5.3 Manual Configuration of NE Parameters

6

Configuration Management
6.1 Typical Workflow
6.2 Administrative Status
6.3 Licensing Optional Features
6.4 Unit and Interface Configuration
6.5 Radio Terminal Configuration
6.6 Working with APS Protection
6.7 Working with 1+1 DS1 SNCP Protection
6.8 Configuring the Ethernet Bridge
6.9 Working with Traffic Routing of DS Interfaces
6.10 Working with DS1 Overview
6.11 DCN Configuration
6.12 Uploading a Configuration File to an FTP Server
6.13 Software Upgrade
6.14 Introduction to CLI
6.15 Generating Configuration Reports

7

Fault Management
7.1 Operational Status
7.2 Alarms and Events
7.3 Viewing the DCN Status
7.4 Loops
7.5 Error Log Handling

8

Performance Management
8.1 Specifying the PM Start Time
8.2 Viewing Performance Data
8.3 Running a BERT on an DS1 Interface

9

Security Management
9.1 User Names
9.2 Changing Passwords
9.3 Replacing Lost Passwords

10

Hardware Maintenance
10.1 Adding and Removing Plug-in Units
10.2 Replacing an LTU 16x DS1 , LTU 16/1, LTU 12x DS1 , LTU 155 ANSI , ETU2, SMU2 ANSI (co-siting)
10.3 Replacing an MMU2 or SMU2 ANSI (protection)
10.4 Replacing an MMU2 B A /C A
10.5 Replacing a PFU
10.6 Replacing an NPU1 ANSI
10.7 Replacing an NPU1 B A
10.8 Replacing an NPU2 A
10.9 Replacing a Radio Unit
10.10 Changing the Traffic Capacity of a Radio Terminal with MMU2
10.11 Changing the Traffic Capacity of a Radio Terminal with MMU2 B A /C A
10.12 Changing an 1+0 Radio Terminal to a 1+1 Radio Terminal with MMU2
10.13 Changing an 1+0 Radio Terminal to a 1+1 Radio Terminal with MMU2 B A /C A
10.14 Changing the Traffic Capacity of an SMU2 ANSI (co-siting)

11

User Interface Reference
11.1 Radio Terminal Configuration
11.2 Radio Terminal Configuration for MMU2 B A /C
11.3 Automatic Configuration
11.4 Manual Configuration
11.5 Software Upgrade - Installation Wizard
11.6 Finish Installation
11.7 Installation Finished
11.8 Change Password
11.9 Emergency Fallback
11.10 Perform Emergency Fallback
11.11 Factory Setting
11.12 Delete Configuration File
11.13 Configuration File Deleted
11.14 Restore NPU Configuration
11.15 Basic NE Configuration
11.16 LAN/Servers Configuration
11.17 PPP Configuration
11.18 Static Routing Configuration
11.19 Modify Static Route
11.20 OSPF Area Configuration
11.21 Modify OSPF Area
11.22 PFU1 Configuration
11.23 PFU2 Configuration
11.24 PFU3 Configuration
11.25 FAU Configuration
11.26 NPU1 B A Configuration
11.27 NPU1 ANSI Configuration
11.28 NPU2 A Configuration
11.29 Ethernet Bridge Configuration
11.30 Bridge Configuration (ETU2)
11.31 ETU2 Configuration
11.32 LTU 12x DS1 Configuration
11.33 LTU 16x DS1 or LTU 16/1 Configuration
11.34 LTU 155 ANSI Configuration
11.35 MMU2 Configuration
11.36 SMU2 ANSI Configuration
11.37 MMU2 B A /C A Configuration
11.38 RAU IF Configuration
11.39 RAU Configuration
11.40 RF Configuration
11.41 Reset Configuration
11.42 Restore Configuration
11.43 SWITCH Configuration
11.44 SWITCH Protection
11.45 Line/Section Configuration
11.46 APS Configuration
11.47 STS-1 Configuration
11.48 VT1.5 Configuration
11.49 All VT1.5 Configuration
11.50 MUX23 Configuration
11.51 MUX12 Configuration
11.52 DS1 Configuration
11.53 All ANSI Configuration
11.54 DS1 Overview
11.55 User Input Configuration
11.56 User Output Configuration
11.57 Traffic Routing Select Interfaces
11.58 Traffic Routing Matrix View
11.59 Traffic Routing List View
11.60 Traffic Routing - Current Traffic Routings
11.61 Create Traffic Routing
11.62 Create Multiple Traffic Routings
11.63 Modify Traffic Routing
11.64 1+1 DS1 SNCP Select Interfaces
11.65 1+1 DS1 SNCP Matrix View
11.66 1+1 DS1 SNCP List View
11.67 Create 1+1 DS1 SNCP
11.68 Create Multiple 1+1 DS1 SNCP
11.69 Modify 1+1 DS1 SNCP
11.70 Create APS Protection
11.71 Creating Protection
11.72 Modify APS Protection
11.73 Deleting Protection
11.74 Inventory
11.75 Edit Asset ID
11.76 Report
11.77 View Report
11.78 Upgrade of Baseline
11.79 Upgrade of Modules
11.80 Settings
11.81 Start Upgrade
11.82 View Units
11.83 Preferences
11.84 Upgrade Progress - Baseline
11.85 Upgrade Progress - Modules
11.86 Scheduled Activation
11.87 Activation in Progress
11.88 Confirm New Software Configuration
11.89 Load Configuration
11.90 Load Configuration Progress
11.91 Load Configuration Preview
11.92 Restart
11.93 Help Setup
11.94 Licenses
11.95 Create License Request
11.96 License File Overview
11.97 License File Inventory
11.98 License File Content
11.99 Clear Reservation
11.100 NE Alarms and Status
11.101 Ethernet Bridge Alarms and Status
11.102 Bridge Alarm and Status (ETU2)
11.103 LAN Status
11.104 USB Status
11.105 PPP Status
11.106 PPP and ML-PPP Counters
11.107 TCP Status
11.108 UDP Status
11.109 ARP Status
11.110 IP/ICMP Status
11.111 Static Routing Status
11.112 OSPF General Status
11.113 OSPF Area Status
11.114 OSPF Interface Status
11.115 OSPF Neighbor Status
11.116 OSPF Host Status
11.117 PFU Alarms and Status
11.118 FAU Alarms and Status
11.119 NPU1 B A Alarms and Status
11.120 NPU1 ANSI Alarms and Status
11.121 NPU2 A Alarms and Status
11.122 ETU2 Alarms and Status
11.123 LTU 16x DS1 and LTU 16/1 Alarms and Status
11.124 LTU 12x DS1 Alarms and Status
11.125 LTU 155 ANSI Alarms and Status
11.126 Radio Terminal Alarms and Status for MMU2 B A /C A
11.127 MMU2 Alarms and Status
11.128 RAU Alarms and Status for MMU2
11.129 RF Alarms and Status for MMU2 and ATU MMU2
11.130 RAU IF Alarms and Status for MMU2
11.131 SWITCH Alarms and Status for MMU2
11.132 SMU2 ANSI Alarms and Status
11.133 Unsupported Unit Alarms and Status
11.134 DS1 Alarms and Status
11.135 MUX12 Alarms and Status
11.136 MUX23 Alarms and Status
11.137 Line/Section Alarms and Status
11.138 MSP APS Alarms and Status
11.139 STS-1 Alarms and Status
11.140 VT1.5 Alarms and Status
11.141 User Input Alarms and Status
11.142 User Output Alarms and Status
11.143 Alarm List
11.144 Event Log
11.145 Load Error Log
11.146 Activities
11.147 NE Loops
11.148 Loops
11.149 Line/Section Performance
11.150 MS/RS Line/Section Performance 15 Minute Intervals
11.151 APS Performance
11.152 APS Performance 15 minute Intervals
11.153 STS-1 Performance
11.154 STS-1 Performance 15 minute Intervals
11.155 VT1.5 Performance
11.156 VT1.5 Performance 15 minute Intervals
11.157 DS1 Performance
11.158 DS1 Performance 15 Minute Intervals
11.159 Radio Link Performance
11.160 RF Power
11.161 Bit Error Ratio Test (BERT)
11.162 Security
11.163 Select Option

Glossary


1   Introduction

A MINI-LINK TN Network Element (NE) has an embedded Web server hosting an Embedded Element Manager (EEM) application. Local management is performed using a Local Craft Terminal (LCT), that is a locally connected PC, accessing the EEM from a Web browser. The EEM can also be accessed remotely over the DCN or launched from MINI-LINK Manager.

This operating instruction mainly describes how to use an LCT to set up, configure and maintain MINI-LINK TN equipment. However, the information is valid for other ways of accessing the EEM, unless otherwise stated.

MINI-LINK Service Manager (MSM) is conveniently launched from the EEM for management of Radio Terminals with MMU2.

Figure 1   Local management using the LCT


1.1   Target Group

This operating instruction is written for field technicians and supervisors who work with installation, configuration and maintenance of MINI-LINK TN equipment on site.

It is assumed that the user:

1.2   Revision Information

This release of this operating instruction applies to MINI-LINK TN 3.1 ANSI.

The information is updated due to the following:

1.3   Related Documents

Table 1 contains documents related to installation and operation of MINI-LINK TN equipment. References are made in Italics using the document name only.

Table 1    Related documents

MSM 6.6 User Guide

AE/LZT 712 0193

MSM 6.6 Installation Guide

AE/LZT 712 0069

MINI-LINK TN ANSI Indoor Installation Manual

AE/LZT 712 0215

MINI-LINK TN, MINI-LINK HC, MINI-LINK E

Outdoor Installation Manual

AE/LZT 712 0015

MINI-LINK TN, MINI-LINK HC, MINI-LINK E ANSI Product Catalog

AE/LZT 712 0195

MINI-LINK TN ANSI Technical Description

AE/LZT 712 0213

MINI-LINK DCN Guideline

1/15443-FGB 101 004/1

1.4   Conventions

This section states the typographic and safety conventions used in this operating instruction.

1.4.1   Typographic Conventions

The following typographic conventions are used:

1.4.2   Safety Conventions

At some places the user must be careful to do as described to avoid disturbing ongoing traffic, initiate ESD or cause a loss of data. To highlight such sensitive parts the following safety conventions are used.

Caution


Caution!  
Caution means that disturbances may occur if the warning is neglected. This type of disturbance may cause damage to tangible property or cause traffic interruptions when doing software work.

Notes

Note:  
Notes are used to call to the attention of the reader key points that might otherwise be overlooked.

Electrostatic Discharge

Figure 2   ESD symbol

The Electrostatic Discharge (ESD) symbol indicates when external ESD protection must be used to avoid possible damage to the equipment.

1.5   Copyright for Third Party Software Products


1.6   Technical Support

If you have a technical question or have encountered a problem working with MINI-LINK TN equipment, please contact your local Ericsson representative. When contacting your local Ericsson representative, please provide the following information for the fastest possible service:

2   System Overview

MINI-LINK TN provides a platform for flexible, scalable and cost-effective wireless transmission. The system offers integrated traffic routing, PDH and SONET multiplexing, Ethernet transport as well as protection mechanisms on link and network level. The software configurable traffic routing minimizes the use of cables, improves network quality and facilitates control from a remote location.

The modular system enables new interface units to be added while in operation. This hot insertion of new plug-in units and automatic software upgrade ensure that traffic is operational during replacement and functional upgrade.

Configurations range from small end sites with one single Radio Terminal to large hub sites where all the traffic from a number of southbound links is aggregated into one link, microwave or optical, in the northbound direction.

A Network Element (NE) comprises two parts:

Figure 3   Indoor and outdoor parts

2.1   Indoor Part with AMM

The summary below introduces the standard types of indoor units, available in different versions further described in this section.

Access Module Magazine (AMM)   Houses the plug-in units and provides backplane interconnection of traffic, power and control signals.
Node Processor Unit (NPU)   Handles the system's control functions. It also provides traffic and management interfaces.
Line Termination Unit (LTU)   A plug-in unit that provides PDH or SONET traffic interfaces.
Ethernet Interface Unit (ETU2)   A plug-in unit that provides Ethernet interfaces.
Modem Unit (MMU)   The indoor part of a Radio Terminal. This plug-in unit determines the traffic capacity of the Radio Terminal.
ATM Aggregation Unit (AAU)   A plug-in unit that provides aggregation of ethernet traffic.
Switch Multiplexer Unit (SMU)   Provides protection for the Radio Terminals. Alternatively it can be configured to interface MINI-LINK E equipment on the same site.
Power Filter Unit (PFU)   Filters the external power and distributes the internal power to the plug-in units via the backplane.
Fan Unit (FAU)   Provides cooling for the indoor part.

The interconnection between the outdoor part (Radio Units and antennas) and the indoor part is one coaxial cable per MMU carrying full duplex traffic, DC supply voltage, as well as operation and maintenance data.

2.1.1   AMM

The AMM houses the plug-in units and provides backplane interconnection of traffic, power and control signals. One plug-in unit occupies one slot in the AMM. The AMM fits into standard 19" or metric racks and cabinets. It is available in three sizes described below.

2.1.1.1   AMM 2p

The AMM 2p is suitable for end site and repeater site applications. It has two half-height slots equipped with one NPU2 A and the optional LTU 12xDS1. Two full-height slots can be equipped with MMU, LTU or ETU. The FAU4 is used depending on the configuration.

Figure 4   AMM 2p

2.1.1.2   AMM 6p

The AMM 6p is suitable for medium-sized hub sites. It has six full-height slots and two half-height slots and it houses one NPU1 BA or NPU1 ANSI, one PFU2 and one FAU2. The remaining slots are equipped with MMU, LTU, ETU and SMUs.

Figure 5   AMM 6p


2.1.1.3   AMM 6p B

The AMM 6p B is the successor of AMM 6p, providing power redundancy. It has six full-height slots and two half-height slots and it houses one NPU1 BA or NPU1 ANSI, one or two PFU3 (in one half-height slot) and one FAU2. The remaining slots are equipped with MMU, LTU, ETU and SMU.

Figure 6   AMM 6p B

2.1.1.4   AMM 20p

The AMM 20p is suitable for large-sized hub sites, for example at the intersection between the optical network and the microwave network. It has 20 full-height slots and two half-height slots and it houses one NPU1 BA or NPU1 ANSI, and one or two PFU1. The remaining slots are equipped with MMU, LTU, ETU and SMU.

A cable shelf is fitted directly underneath the AMM to enable neat handling of cables connected to the fronts of the plug-in units. An FAU1 is fitted on top of the AMM unless forced air-cooling is provided. An air guide plate is fitted right above the FAU1.

Figure 7   AMM 20p

2.1.2   NPU

The NPU holds the system's control functions. One NPU is always required in the AMM. The NPU also provides DS1, DCN and management interfaces.

2.1.2.1   NPU2 A

The unit fits in an AMM 2p. The external power supply is connected directly to the NPU2 A. It provides 4xDS1 for traffic connection, USB interface for LCT connection and a 10/100BASE-T Ethernet interface. The Ethernet interface can be configured to detect the type of cable used and is intended for the optional features Ethernet Site LAN or Ethernet Traffic.

Note:  
NPU2 A contains a Removable Memory Module (RMM). The RMM is intended for future use and should not be removed from the unit.

2.1.2.2   NPU1 ANSI

The unit fits in an AMM 6p (B) and AMM 20p. It provides 8xDS1 for traffic connection, 10BASE-T Ethernet interface for LCT connection, three User Input and three User Output ports.

2.1.2.3   NPU1 BA

NPU1 BA is the successor of NPU1 ANSI. It provides 8xDS1 for traffic connection, USB interface for LCT connection, three User Input, three User Output ports and a 10/100BASE-T Ethernet interface. The Ethernet interface can be configured to detect the type of cable used and is intended for the optional feature Ethernet Site LAN.

Note:  
NPU1 BA contains a Removable Memory Module (RMM). The RMM is intended for future use and should not be removed from the unit.

2.1.3   LTU

The LTUs are used to connect traffic from external PDH or DS1 equipment.

2.1.3.1   LTU 12xDS1

The unit fits in an AMM 2p. For sites where the four DS1 interfaces on the NPU2 A are insufficient, the LTU 12xDS1 provides 12 additional DS1 interfaces.

2.1.3.2   LTU 16xDS1 and LTU 16/1

These units fits in an AMM 2p, AMM 6p (B) or AMM 20p. For sites where the DS1 interfaces on the NPU are insufficient, the LTU 16xDS1 and LTU 16/1 provides 16 additional DS1 interfaces.

2.1.3.3   LTU 155 ANSI

The unit fits in an AMM 6p (B) and AMM 20p. It provides one optical or one electrical OC-3/STS-3 interface.

2.1.4   ETU2

The ETU2 fits in an AMM 2p, AMM 6p (B) and AMM 20p. It provides five 10/100BASE-T Ethernet interfaces and one 10/100/1000BASE-T Ethernet interface.

2.1.5   MMU

The MMU is the indoor part of a Radio Terminal determining the traffic capacity (4 to 34 Mbit/s).

MMU2

The MMU2 is a traffic agile plug-in unit for C-QPSK modulation used for traffic capacity 4 to 16xDS1 .

A protected (1+1) Radio Terminal requires two MMU2 units and one SMU2 ANSI.

The local management is done using MSM, which is launched from the LCT.

MMU2 BA

The MMU2 BA is a traffic agile plug-in unit for C-QPSK modulation used for traffic capacity 4 to 16xDS1.

A protected (1+1) Radio Terminal requires two MMU2 BA units.

The local management is done using the LCT.

MMU2 CA

The MMU2 CA is a traffic agile plug-in unit used for the following modulation schemes and traffic capacities:

The use of the different capacities and modulation scheme depends on frequency band. For more information, see the MINI-LINK TN, MINI-LINK HC, MINI-LINK E ANSI Product Catalog.

A protected (1+1) Radio Terminal requires two MMU2 CA units.

The local management is done using the LCT.

2.1.6   SMU2 ANSI

The SMU2 ANSI provides either 1+1 radio protection (with MMU2 only) or co-siting features for MINI-LINK E equipment, depending on how the unit is configured. It has one O&M connector.

2.1.7   PFU

The PFU is connected to the external power supply, which is filtered and distributed to the plug-in units via the backplane.

2.1.7.1   PFU1

The unit fits in AMM 20p. Two PFU1 units connected to separate power supply sources provide power redundancy.

2.1.7.2   PFU2

The unit fits in AMM 6p.

2.1.7.3   PFU3

The unit fits in AMM 6p B. Two PFU3 units connected to separate power supply sources provide power redundancy.

2.1.8   FAU

The FAU provides cooling for the AMM and plug-in units.

2.1.8.1   FAU1

The unit is fitted directly above the AMM 20p.

2.1.8.2   FAU2

The unit is fitted in the AMM 6p (B).

2.1.8.3   FAU4

The unit is fitted in the AMM 2p.


2.2   Outdoor Part

The outdoor part is supplied for various frequency bands. It consists of an antenna, a Radio Unit (RAU) and associated installation hardware. For protected (1+1) systems, two RAUs and one or two antennas are used. When using one antenna, the two RAUs are connected to the antenna using a power splitter. The RAU and the antenna are easily installed on a wide range of support structures. The RAU is fitted directly to the antenna as standard, integrated installation. The RAU and the antenna can also be fitted separately and connected by a flexible waveguide. In all cases, the antenna is easily aligned and the RAU can be disconnected and replaced without affecting the antenna alignment.

Figure 8   RAUs and antennas in different installation alternatives

The antennas range from 0.2 m (9") up to 3.7 m (12ft) in diameter Antennas up to 1.8 m in diameter can be fitted integrated with the RAU and all antennas can be installed separately, if required.


2.3   Management

Below follows a summary of the tools used to manage a MINI-LINK TN network.

EEM

The element management function is implemented as an Embedded Element Manager (EEM) application, accessed using a standard web browser. For local management a Local Craft Terminal (LCT) is used, that is the EEM is accessed locally by connecting a PC to the NPU with a crossed Ethernet cable (NPU1 ANSI) or a USB cable (NPU2 A/NPU1 BA). The EEM can also be accessed over the site LAN or remotely over the DCN.

Local management of Radio Terminals based on MMU2 or is mainly done with MSM, which is launched from the EEM. Terminals based on MMU2 BA, MMU2 CA are handled by the EEM itself.

CLI

A Command Line Interface (CLI) is provided for advanced IP router configuration and troubleshooting. It is similar to Cisco's industry standard router configuration and is accessed from a Command Prompt window using telnet.

MINI-LINK Manager

Remote management is typically done using MINI-LINK Manager, the network management tool for all MINI-LINK products. The EEM is launched from MINI-LINK Manager for access of a single NE.

Each NE provides an SNMP agent enabling easy integration with any other SNMP based management system.

3   Getting Started

This section covers the following:

3.1   System Requirements

Make sure that your PC fulfils the following requirements:


3.2   Installing Software

The following LCT related software can be installed on the PC:

3.2.1   Installing and Configuring BulletProof FTP Server

BulletProof FTP server (2.15 or later) is used for uploading and downloading load modules and configuration files. A user account for MINI-LINK TN on the FTP server and a correct directory structure must be created.

3.2.1.1   Installing BulletProof FTP Server

To install BulletProof FTP Server with default settings:

  1. Start the BulletProof FTP Server installation program from the MINI-LINK Service Software CD (LZY 214 2358/1).
  2. In the Licence Agreement dialog box, click Next to accept the licence agreement.
  3. In the Installation Options dialog box, click Next to accept the installation type Standard.
  4. In the Installation directory dialog box, click Next to accept the default location of the FTP server files.
  5. In the Completed dialog box, click Close to exit the installation program.

3.2.1.2   Directory Structure of the FTP Server

When using the FTP server certain directories must be present as follows:

-- tn_ftp_home
   |-- tn_backup_configuration
   |-- tn_error_log
   |-- tn_licenses
   |-- tn_system_release
       |-- ml_tn_software

Note:  
A correct directory structure is a prerequisite for software upgrade and load of files.

The root directory (tn_ftp_home) and the directories directly below (tn_backup_configuration, tn_error_log and tn_system_release) are created by the FTP Server installation program on the MINI-LINK Service Software CD.

tn_backup_configuration is used to store configuration files uploaded from an NE as backup and configuration files to be downloaded to an NE. A configuration file is named <hostname>.cfg where <hostname> is typically the name or IP address of an NE.

tn_error_log is used to store error log files loaded from the NE, for example <hostname>_active.elog.

Note:  
Since tn_backup_configuration and tn_error_log are likely to hold files belonging to several NEs it is important to use file names that can be easily identified. To avoid overwriting existing files the extension .old should be added, for example <hostname>.cfg.old, before loading a new file to the FTP server.

tn_licenses is used for LKFs containing licenses to be installed on an NE.

tn_system_release is used for load modules and the directories below are created when installing a load module, see Section 3.2.5.

MINI-LINK TN 2.1 ANSIintroduces a new software upgrade concept which puts new requirements on the directory structure. In MINI-LINK TN 1.1 all load modules are contained in one Software System Release (SSR) file. The content is described in an System Release Description File (SRDF).

In MINI-LINK TN 2.1 ANSI, each load module resides in a separate directory. The load modules included in a Software Baseline (SBL) is described in a Software Baseline Description File (SBDF).

To facilitate software upgrade and NPU repair in a network with both "post-2.1" and "pre-2.1" products, the software must be stored in both the old (1.1) and new (2.1 and later) file structure.

Example 1and Example 2show lists of available files under tn_system_release.

Example 1   Old (1.1) directory structure

.\tn_system_release\CXP9010021_1_R3A\
						srdf.tn                        (SRDF 2.0)
						CXP901584_1_R3A                (NPU1 ANSI)
						CXP9010618_1_R1A               (NPU1 BA)
						CXP9010617_1_R3A               (NPU2 A)
						CXCR102004_1_R3A               (LTU 155)

Example 2   New (2.1 and later) directory structure

.\tn_system_release\ml_tn_software\
						CXP9010021_1\CXP9010021_1_R3A  (SBDF 2.1 and later)
						CXP901584_1\CXP901584_1_R3A    (NPU1 ANSI)
						CXP9010618_1\CXP9010618_1_R1A  (NPU1 BA)
						CXP9010617_1\CXP9010617_1_R3A  (NPU2 A)
						CXCR102004_1\CXCR102004_1_R3A  (LTU 155)

3.2.1.3   Configuring BulletProof FTP Server

To configure the FTP Server:

Creating a User
  1. On the Start menu, point to ProgramsBulletProof FTP Server and then click BPFTP Server.
  2. On the Setup menu, click User Accounts.
  3. The Setup User Accounts dialog box appears.

Figure 9   The Setup User Accounts window

  1. Right-click in the User Accounts list and then click Add on the shortcut menu.
  2. In the Enter Account Name dialog box, type anonymous and click OK. This is the default user name.
  3. In the Setup User Accounts dialog box, type anonymous in the Password box. This is the default password.
Specifying the FTP Server Root Directory
  1. Right-click in the Directories list and then click Add on the shortcut menu.
  2. In the Select Directory dialog box, browse to the <drive:>\tn_ftp_home directory and click Select. The NE uses this directory and its sub-directories for uploading and downloading configuration files and load modules.
  3. In the Directories list, select the <drive:>\tn_ftp_home directory.
  4. Under Files, select the Read, Write and Append check boxes.
  5. Under Directories, select the Make, List and +Subdirs check boxes.
  6. Click OK. The FTP server is now configured to be used by the NE.
Configuring the FTP Server to be Activated on Startup
  1. On the Setup menu, point to Main and then click General.
  2. In the FTP Server Setup dialog box, select the Activate Ftp server on startup check box and then click OK.
Starting the FTP Server
  1. On the Server menu, click Go On-line to start the FTP server.

3.2.2   Installing MINI-LINK Service Manager (MSM)

MSM (6.5 or later) is required to manage Radio Terminals with MMU2. Install MSM according to the MSM Installation Guide.


3.2.3   Installing USB Driver

A USB driver must be installed on the PC to be able to connect to the NPU2 A/NPU1 BA. The MINI-LINK Service Software CD (LZY 214 2358/1) provides an installation program for Belcarra Windows USBLAN Software, hereafter referred to as USBLAN.

To install USBLAN:

Note:  
Make sure the USB cable is disconnected from the PC.

  1. Locate and click the link on the CD that starts the installation program.
  2. In the Ericsson Installer ... License Agreement" dialog box, click I Agree to accept the license agreement.
  3. In the Ericsson Installer ... Installation Folder dialog box, click Install to accept the default location (C:\Program Files\Ericsson\USBLAN\).
  4. The first time the USB cable is connected between the PC and the NPU, the Found New Hardware dialog box will appear. Complete the procedure on the screen in order to start USBLAN automatically each time the cable is connected.

More information on installation of USBLAN is found in the readme.txt file available on the CD. After installation, the file will be located in C:\Program Files\Ericsson\USBLAN\.

3.2.4   Installing Software Baselines

This section describes how to install a new Software Baseline on the LCT PC for software upgrade. The file containing the baseline is named <product number>_<R-state>.tar.Z and must be unpacked according to the instruction below.

To install a Software Baseline on the PC:

  1. Extract the contents of the file to the <drive:>\tn_ftp_home directory.
    Note:  
    Make sure the internal directory structure is preserved as described in Section 3.2.1.2. For example when using WinZip, the Use folder names check box must be selected in the Extract dialog box.


3.2.5   Installing Load Modules

This section describes how to install load modules (that are not included in a Software Baseline) on the LCT PC for software upgrade. The load module file is named <product number>_<R-state>.zip and must be unpacked according to the instruction below.

To install a load module on the PC:

  1. Create a new folder in <drive:>\tn_ftp_home\tn_system_release\ml_tn_software.
  2. Rename the new folder to the <product number> of the load module file.

    For example, if the load module file is named CXC113404_R5B.zip, the name of the folder should be CXC113404

  3. Extract the contents of the load module file to the new folder.
  4. Remove the .upg extension from the name of the extracted files.

    For example, if an extracted file is named CXC113404_R5B.upg, you should rename it to CXC113404_R5B

3.3   Starting the LCT

This section describes how to connect the PC to the equipment and access the EEM. It also contains supplementary information regarding PC and browser settings.

3.3.1   Starting the LCT for NPU2 A/NPU1 BA

This section describes how to start the LCT when working with an NPU2 A or NPU1 BA.

Locally, the NE is accessed using a USB connection and a default IP address (10.0.0.1). The PC (and the FTP server on the PC) obtains a dynamic IP address (10.0.0.2) from a DHCP server in the NE. This means that the PC should be configured to use dynamic IP addressing.

Remotely, the NE is accessed using the IP address to be used during normal operation. It is typically found in the site documentation or on the information plate of the NE. The PC uses a static or dynamic IP address, depending on whether a DHCP server is used or not, and must be configured accordingly. It is recommended to use a DHCP server if available.

The NE has two modes of operation as described below.

3.3.1.1   Normal Mode

This mode is used for normal operation, allowing complete configuration possibilities. The BR (yellow) LED is OFF when the NE is in Normal mode.

Figure 10   LEDs and BR button on the NPU1 BA. For a full description of the LEDs, see the MINI-LINK TN ANSI Indoor Installation Manual.

3.3.1.2   NPU Installation Mode

This mode is used for replacement of the NPU. The LCT will give the possibility to download a new configuration file in order to restore the configuration.

Default user names and passwords are used for the NE and the FTP server, see Section 9.1 and Section 3.2.1.3.

The NPU Installation mode is entered by inserting the NPU in an active NE (only NPU1 BA) and immediately pressing the BR button during NPU power up (Fault (red), Power (green) and BR (yellow) LEDs on the NPU are ON). The BR (yellow) LED will start flashing, indicating that the NE is in NPU Installation mode. The NPU Installation mode is normally left as a result of the completed replacement procedure. However, the mode can always be left by pressing the BR button.

The procedures of replacing the NPU is described in Section 10.7 and Section 10.8.

3.3.1.3   Starting the LCT

To start the LCT:

  1. Do one of the following:
  2. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
  3. A non-configured NE lacks a configuration a file and an installation wizard will be provided for the initial setup, see Figure 11. The initial setup is described in Section 5.

    A configured NE will display a page like the one in Figure 12. From here you can perform all operations, for example configuration, see Section 6.

    Should the NE be in NPU Installation mode, the LCT will give the possibility to download a new configuration file in order to restore the configuration, see Figure 13. The procedures of replacing the NPU is described in Section 10.7 and Section 10.8.

Figure 11   The Radio Terminal Configuration page

Figure 12   The Alarms and Status page for an AMM 2p

Figure 13   The Restore NPU Configuration page

3.3.2   Starting the LCT for NPU1 ANSI

This section describes how to start the LCT when working with an NPU1 ANSI. The NE is accessed using an Ethernet connection.

3.3.2.1   Operation Modes

The NE can operate in different modes providing different functions when working with the LCT. Below follows a short description of the different modes.

Node Installation Mode

This mode is used for initial setup of an NE, allowing a limited set of parameters to be set. It is also used for some specific maintenance procedures. The NE is accessed using a default IP address (10.0.0.1) and the PC (and the FTP server on the PC) obtains a dynamic IP address (10.0.0.2) from a DHCP server in the NE. This means that the PC should be configured to use dynamic IP addressing. However, using the static IP address 10.0.0.2 on the PC will also work.

Default user name and password are used for the NE and the FTP server, see Section 9.1 and Section 3.2.1.3.

The Node Installation mode is entered by pressing the BR button on the NPU1 ANSI during NE power up, that is when the Fault (red), Power (green) and BR (yellow) LEDs on the NPU1 ANSI are ON. The BR (yellow) LED will then start flashing, indicating that the NE is in Node Installation mode.

Figure 14   Entering Node Installation mode

When the initial setup is completed, the NE leaves Node Installation mode and goes into Normal mode. However, the Node Installation mode can always be left by pressing the BR button. An automatic save of the running configuration is always performed, when leaving the Node Installation mode.

The initial setup is described in Section 5.

NPU Installation Mode

This mode is used for replacement of the NPU. The LCT will give the possibility to download a new configuration file in order to restore the configuration.

The NE is accessed using a default IP address (10.0.0.1) and the PC (and the FTP server on the PC) obtains a dynamic IP address (10.0.0.2) from a DHCP server in the NE. This means that the PC should be configured to use dynamic IP addressing. However, using the static IP address 10.0.0.2 on the PC will also work.

Default user names and passwords are used for the NE and the FTP server, see Section 9.1 and Section 3.2.1.3.

The NPU Installation mode is entered by inserting the NPU in an active NE and immediately pressing the BR button during NPU power up (Fault (red), Power (green) and BR (yellow) LEDs on the NPU are ON). The BR (yellow) LED will start flashing, indicating that the NE is in NPU Installation mode. The mode is also entered if the NPU1 ANSI lacks a startup configuration file.

The NPU Installation mode is normally left as a result of the completed replacement procedure. However, the mode can always be left by pressing the BR button.

The procedure of replacing the NPU1 ANSI 2 is described in Section 10.6.

Normal Mode

This mode is used for normal operation, allowing complete configuration possibilities. The NE is accessed using the IP address to be used during normal operation. It is typically found in the site documentation or on the information plate of the NE. The PC uses a static or dynamic IP address, depending on whether a DHCP server is used or not, and must be configured accordingly. It is recommended to use a DHCP server if available.

The BR (yellow) LED is OFF when the NE is in Normal mode.

Figure 15   LEDs and BR button on the NPU1 ANSI. For a full description of the LEDs, see the MINI-LINK TN ANSI Indoor Installation Manual.

To start the LCT while the NE is in:

3.3.2.2   Starting the LCT in Node/NPU Installation Mode

  1. Connect the Ethernet cable (twisted pair) between your PC and the 10/100BASE-T connector on theNPU1 ANSI.
  2. Configure the PC to use a dynamic IP address obtained from the DHCP server in the NE. For more information on IP addressing, see Section 3.3.3.
    Note:  
    It is also possible to configure the PC to use the static IP address 10.0.0.2.

  3. Start a Web browser and make sure your browser is configured not to use a proxy server. For more information, see Section 3.3.4.
  4. In your Web browser, enter the URL http://10.0.0.1/.
  5. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.

    Figure 16 shows an example of what will be displayed in your browser when in Node Installation mode. The initial setup is described in Section 5.

    Should the NE be in NPU Installation mode, the LCT will give the possibility to download a new configuration file in order to restore the configuration, see Figure 17. The procedure of replacing the NPU 8x2 is described in Section 10.6.

Figure 16   The Radio Terminal Configuration page

Figure 17   The Restore NPU Configuration page

3.3.2.3   Starting the LCT in Normal Mode

  1. Connect the Ethernet (twisted pair) cable between your PC and the 10/100BASE-T connector on the NPU1 ANSI.
  2. Make sure the PC is properly configured regarding the use of DHCP server. The configuration defines whether dynamic or static IP addressing should be used. It is recommended to use a DHCP server if available. For more information on IP addressing, see Section 3.3.3.
  3. Start a Web browser and make sure your browser is configured not to use a proxy server. For more information, see Section 3.3.4.
  4. Find out the IP address of the NE, typically from the site documentation or on the information plate of the NE and enter the URL http://<IP address>.
  5. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.

    Figure 18 shows an example of what will be displayed in your browser: From here you can perform all operations, for example configuration, see Section 6.

Figure 18   The NE Alarms and Status page for an AMM 20p

3.3.3   Configuring IP Addressing

Your PC can be configured to obtain a dynamic IP address from a DHCP server. Without the use of a DHCP server, only a static IP address can be used. Follow the instructions in the section that apply to your operating system.

3.3.3.1   Configuring IP Addressing in Windows 2000

To configure for static IP addressing:

  1. On the Start menu, click Control Panel.
  2. In Control Panel, double-click Network and Dial-up Connections.
  3. In the Network and Dial-up Connections folder, right-click the connection to be used and click Properties on the shortcut menu.
  4. In the Connection Properties dialog box, select Internet Protocol (TCP/IP) and click Properties.
  5. In the Internet (TCP/IP) Properties dialog box, select Use the following IP address.
  6. Type IP Address and Subnet Mask.
  7. Click OK.

To configure for dynamic IP addressing:

  1. On the Start menu, click Control Panel.
  2. In Control Panel, double-click Network and Dial-up Connections.
  3. In the Network and Dial-up Connections folder, right-click the connection to be used and click Properties on the shortcut menu.
  4. In the Connection Properties dialog box, select Internet Protocol (TCP/IP) and click Properties.
  5. In the Internet (TCP/IP) Properties dialog box, select Obtain an IP address automatically.
  6. Click OK.

3.3.3.2   Configuring IP Addressing in Windows XP

To configure for static IP addressing:

  1. On the Start menu, click Control Panel.
  2. In Control Panel, double-click Network Connections.
  3. In the Network Connections folder, right-click the connection to be used and click Properties on the shortcut menu.
  4. In the Connection Properties dialog box, select Use the following IP address.
  5. Type IP Address and Subnet Mask.
  6. Click OK.

To configure for dynamic IP addressing:

  1. On the Start menu, click Control Panel.
  2. In Control Panel, double-click Network Connections.
  3. In the Network Connections folder, right-click the connection to be used and click Properties on the shortcut menu.
  4. In the Connection Properties dialog box, select Obtain an IP address automatically.
  5. Click OK.

3.3.4   Configuring Internet Explorer Not to Use a Proxy Server

This section describes how to configure your browser not to use a proxy server.

To configure Internet Explorer:

  1. On the Tools menu, click Internet Options.
  2. In the Internet Options dialog box, click the Connections tab.
  3. Click LAN Settings.
  4. In the Local Area Network (LAN) settings dialog box, clear the Use a proxy server check box and click OK.

3.4   Uninstalling Software

The following should be uninstalled if you want to remove all LCT related software from the PC:

3.4.1   Uninstalling BulletProof FTP Server

To uninstall the FTP server:

  1. On the Start menu, point to ProgramsBulletProof FTP Server and then click Uninstall.
  2. Follow the instructions on the screen.

3.4.2   Uninstalling MINI-LINK Service Manager (MSM)

Uninstall MSM according to the MSM Installation Guide.

3.4.3   Uninstalling USB Driver

To uninstall the USB driver:

  1. Connect the USB cable between your PC and the USB connector on the NPU.
  2. Remove the USB hardware device using the Control Panel. This is described in detail in the file C:\Program Files\Ericsson\USBLAN\readme.txt.
  3. Uninstall USBLAN, by double-clicking the file C:\Program Files\Ericsson\USBLAN\uninstall.exe.
  4. Do a manual file search for erblan* and delete the files found.

3.4.4   Uninstalling Load Modules

To uninstall load modules.

  1. Start Windows Explorer and locate the <drive:>\tn_ftp_home\tn_system_release\ml_tn_software folder.
  2. Select a folder containing load modules or a specific load module, right-click and then click Delete.

4   Using the EEM

This section describes the basics of how to work with the EEM.

4.1   User Interface Overview

Figure 19 shows the different parts of the EEM user interface. The main frame displays information on different pages, further described in Section 11. The other parts are described in the following sections.

Figure 19   EEM user interface

A

Navigation Tree

D

Help

B

Status Bar

E

Confirm button

C

Menu

F

Page


4.2   Navigation Tree

The Navigation Tree is used to locate entities of different types, that is the NE, plug-in units, interfaces and ports. It is only available in Normal mode.

Figure 20   The Navigation Tree

Each entity is displayed with an icon and name. Entities that contain sub-entities, for example a plug-in unit that contains interfaces, are displayed with a plus-sign in front of its icon. When the plus-sign or the icon is clicked the entity is expanded and the sub-entities are displayed.

The NE is located at the top of the tree and the plug-in units are located below. A plug-in unit can contain interfaces and/or ports in different structures depending on the unit type and the current configuration of the unit. An interface can contain higher layer interfaces. In this case the interface icon has a plus-sign that displays the higher layer interfaces when selected.

4.3   Menus

The functionality of the EEM is represented by pages reached by clicking menu commands. The menus change dynamically depending on what type of entity (plug-in units, interfaces etc.) you have selected in the Navigation Tree. Different menus are provided depending on the NE's mode of operation. A dimmed menu indicates a non-available function for the selected entity.

4.3.1   Menus in the Installation Wizard

An installation wizard for the initial setup is provided in the following cases:

The menu commands are described below.

Figure 21   Menus in the installation wizard

4.3.2   Menus in NPU Installation Mode

The menu commands in NPU Installation mode are described below.

Figure 22   Menus in NPU Installation mode

4.3.3   Menus in Normal Mode

The menu commands in Normal mode are described below. The available commands on a menu depend on the selected entity.

Figure 23   Menus in Normal mode

4.4   Status Bar

The Status Bar gives a summary of all alarms and is found at the bottom of all pages. It also displays additional information as described in Table 2. The Status Bar is automatically updated every tenth second.

Note:  
If the Status Bar is not displayed properly, the page must me refreshed.

Figure 24   The Status Bar

Table 2    Status Bar information

Item

Description

Red field

Displays the number of alarms with severity Critical. Clicking the field opens the Alarm List page displaying all alarms with this severity, see Section 11.143.

Orange field

Displays the number of alarms with severity Major. Clicking the field opens the Alarm List page displaying all alarms with this severity, see Section 11.143.

Yellow field

Displays the number of alarms with severity Minor. Clicking the field opens the Alarm List page displaying all alarms with this severity, see Section 11.143.

Blue field

Displays the number of alarms with severity Warning. Clicking the field opens the Alarm List page displaying all alarms with this severity, see Section 11.143.

Activities

Opens the Activities page, where you can view the status of loops, BERTs and software upgrade in the NE, see Section 11.146.

Date and time

The date and time of the last notification. The background color depends on the severity of the last notification.

Confirm

Indicates the time left before the NE reverts to the last saved configuration. Clicking the field will allow you to confirm the configuration of some specific DCN related parameters. A pop-up dialog is displayed when there are 3, 2 and 1 minutes left.

Only available if you are logged on as control_user.

For more information, see Section 4.5.

User name

Displays the user name currently logged on.

Clock

The date and time kept by the NE timer.

4.5   Confirm Button

Configuration of parameters that could lead to loss of a DCN channel, for example change of IP address, need to be confirmed. The confirmation is made automatically if an NE generated ping command to the EEM PC is successful. Otherwise, the confirmation must be done manually. This is done using the Confirm button , displayed in the upper right-hand corner on a page. The button is only displayed in Normal mode.

The Status Bar indicates the remaining time and warnings will be issued when time is running out.


Caution!  
If you do not confirm your configurations within 15 minutes, the NE will make a warm restart, restoring the saved configurations, and your unconfirmed changes will be lost.
Note:  
The contact with the Web server in the NE will be lost during the restart.


4.6   Using the Help

The Help provides on-screen information about the user interface as well as working instructions. Information on a specific page is accessed by clicking Help on a menu.

Figure 25   Help window

The Help file can be located on a PC or on a Web server. It is available on the MINI-LINK Service Software CD (LZY 214 2358/1) or on the internal Ericsson web. The help file is named 19089-EN_LZN7120177.<version>.zip or similar and should be unpacked preserving the internal directory structure.

To install the Help on the local drive:

  1. Extract the file to C:\.
    Note:  
    Make sure the internal directory structure is preserved. When using WinZip, the Use folder names check box must be selected in the Extract dialog box.

  2. The help file will be unpacked with the following path: C:\MINI-LINK\Documentation\TN_help\ANSI_<revision>\help.html

When installing the Help file on a web server, C: is replaced by <URL>.

To be able to access the Help, the location of the file must be pointed out. The location is saved as a cookie in your browser, one for each NE, but it is sometimes necessary to do a new setup, for example if a new version is available.

To set up the Help:

  1. On the Tools menu, click Help Setup.
  2. On the Help Setup page, do one of the following:
  3. Click Apply.
    Note:  
    If the Help cannot be accessed, make sure that cookies are enabled in your browser and that you have typed the correct path or URL.

    Note:  
    A security feature in Internet Explorer 6 SP1 sometimes denies the browser to access the Help file on your PC. Should this occur do the following in your browser: Click Tools->Internet Options->Security and add http://<IP address of the NE> as a "Trusted Site".

4.7   Naming Principles

This section describes the principles used to denote the NE, plug-in units, ports and interfaces.

4.7.1   Naming of the NE

The NE name is specified in the Name box on the System Configuration page, see Section 11.15. The name is used for example to denote the root in the Navigation Tree.

4.7.2   Naming of Physical Entities

Physical entities in the AMM are named as: Name + Magazine/Position/Port.

For example an NPU1 ANSI in position 11 in an AMM 20p gives the following names:

An RAU is denoted in accordance with the MMU it is connected to. For example, RAU 1/6.1 is connected to MMU2 BA 1/6.

An RMM is denoted in accordance with the NPU where it is inserted. For example, RMM 1/11.1 is inserted in NPU1 BA 1/11.


4.7.3   Naming of Interfaces

Interfaces are named as: Name + Magazine/Position/Port + Hierarchy Number, where:

The following principles also apply:


4.8   EEM Troubleshooting

This section contains descriptions of potential EEM related problems that could occur and instructions how to solve them.

4.8.1   Graphical Layout Problems in the Browser

After a software upgrade, there is a possibility that the browser experiences some graphical layout problems, for example wrong background color for the menu, wrong tree icons or plug-in unit pictures. This behavior is caused by the caching mechanism of the browser, often Internet Explorer 5.5 and 6. To solve this problem you have to clear the cache file of the browser.

To clear the cache file in Internet Explorer:

  1. On the Tools menu, click Internet Options.
  2. In the Internet Options dialog box, click Delete Files.
  3. In the Delete Files dialog box, select the Delete all offline content check box and click OK.

4.8.2   Pages Do Not Fit in Browser

If the pages in the EEM does not fit within the browser viewing space, you can put the browser into full screen view. This view minimizes the toolbars, hides the Windows Taskbar, and maximizes the browser viewing space.

To put the browser into full screen view:

  1. On the View menu, click Full Screen. You can also press F11 on the keyboard.
  2. To go back to the normal view, press F11 on the keyboard.

You can use the F11 key to toggle back and forth between normal and full screen view.

4.8.3   MSM Launch Failure

MSM 6.5 or later must be installed on the PC in order to completely manage a Radio Terminal with MMU2. During the installation an association is created making it possible to launch MSM from the EEM.

Should the launch of MSM fail displaying an error message similar to Error opening file C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\LOCAL SETTINGS\TEMPORARY INTERNET FILES\CONTENT.IE5\O5QNCPYN\TEST[1].mxm, you have to delete the temporary Internet files on your PC.

Should the launch of MSM otherwise fail, reinstall MSM according to the instructions in MSM Installation Guide.

5   Initial Setup

This section describes the initial setup performed during the installation of a new NE. The initial setup is done following an installation wizard presented in the following cases:

The initial setup includes two major steps:

When the initial setup is completed the configuration is continued in Normal mode, see Section 6.


5.1   Radio Terminal Configuration

The Radio Terminal configuration in the installation wizard is a part of the hardware installation procedure in order to establish communication over a hop. As a minimum, the Radio Terminals used for DCN communication must be configured at this stage. The DCN is a requirement for remote configuration of the NE after the installation. For more information on DCN configuration, see Section 6.11.

The Radio Terminal configuration is started indoors with a station radio cable connecting the MMU and the RAU. For further instructions, see MINI-LINK TN ANSI Indoor Installation Manual.

The procedure for configuration of the Radio Terminal depends on the MMU type:

5.1.1   Configuring a Radio Terminal with MMU2

Note:  
For NPU2 A/NPU1 BA NE, you can exit the wizard at any time by clicking Exit Wizard on the Configuration menu.

To configure a Radio Terminal with MMU2:

  1. On the Radio Terminal Configuration page, click Next until Initial setting of MMU2 ... appears as a link for the unit you want to configure, and then click the link. For a protected (1+1) terminal any of the two MMU2s can be selected.
  2. On the MMU2 Configuration page, under Protection Mode, select one of the following:

    Click Apply. The page is reloaded and displays information about administrative status and notifications for the unit.

    Note:  
    The 1+1 configuration is only possible if the units are placed in adjacent AMM positions according to specifications in MINI-LINK TN ANSI Indoor Installation Manual.

  3. For each unit, select In Service and clear the Enable check box.
  4. Click Apply.
  5. Click Perform AM Setup and Hop Setup.
  6. In MSM, perform an AM and Hop Setup. Follow the instructions in MSM User Guide or MSM online Help. Exit MSM when finished.
  7. On the MMU2 4-16xDS1 Configuration page , select the Enable check box for all units in the Radio Terminal and click Apply.
  8. Repeat the procedure if more terminals should be configured.

This procedure is followed by outdoor equipment installation, indoor and outdoor radio cabling, and antenna alignment. Follow the instructions in MINI-LINK TN ANSI Indoor Installation Manual and MINI-LINK TN, MINI-LINK HC, MINI-LINK E Outdoor Installation Manual.

The initial setup is finished by the configuration of NE parameters, that is security, DCN and system parameters. This can be done in two ways:


5.1.2   Configuring a Radio Terminal with MMU2 BA/CA

Note:  
To configure a protected (1+1) terminal, you must first configure two temporary unprotected (1+0) Radio Terminals, one for each MMU that will be part of the final protected terminal.

You can then go Back in the wizard and create a protected terminal by changing the protection mode of the MMU in the lower position to 1+1. Optionally, you can exit the wizard and then create the protected terminal as described in Section 6.5.2.

To be able to configure a protected terminal, the following conditions apply:


Note:  
For NPU2 A/NPU1 BA, you can exit the wizard at any time by clicking Exit Wizard on the Configuration menu.

To configure a Radio Terminal with MMU2 BA/CA:

  1. On the Radio Terminal Configuration page, click Next until Initial setting of MMU2 BA/CA [...] appears as a link for the unit you want to configure, and then click the link.
  2. Click Perform MMU2 BA/CA [...] to open the MMU2 BA/CA Configuration page.
  3. Under ID, type the identity of this Radio Terminal in the Near End box.
  4. If this terminal should send notifications, select the Notifications check box.
  5. If an alarm should be generated when the received traffic originates from the wrong far-end, type the expected far-end identity in the Far End box, and select the Radio ID Check check box.
  6. Under Traffic Capacity - Modulation, select the wanted traffic capacity.
  7. Under Protection Mode, select the wanted protection mode.
    Note:  
    If you are creating a temporary unprotected terminal, select 1+0.

  8. Click Apply to set the protection mode.
  9. Under BER Alarm Threshold, select the threshold for generating BER alarms.
  10. Under Modulation, select the wanted modulation method.
  11. Under MMU2 BA/CA <ID>, select all check boxes.
  12. Click Apply, then click Next.
  13. Click Perform RAU [...] to open the RAU Configuration page.
  14. Under Near End Radio Terminal <ID>, select all check boxes.
  15. Under RAU <ID>, type the transmit frequency in the Tx Frequency box.
  16. Select the Transmitter On check box.
  17. In the Tx Attenuator box, type the value of the fixed attenuator (if used).
  18. In the Output Power Mode list, select how the output power is to be controlled.
    Note:  
    The ATPC option is only available when all units in the radio link support ATPC. Click Show ATPC Capabilities to see which units support ATPC.

  19. Do one of the following:
  20. In the RF Input Alarm Threshold box, type the threshold for generating RF Input Threshold alarms.
  21. Click Apply, then click Next.
  22. If you have configured a protected terminal, click Perform Protection Configuration to open the SWITCH Protection page.
  23. Configure the protection as described in Section 11.44.
  24. Click Apply, then click Next.
  25. Click Next.
  26. Repeat this procedure if more terminals should be configured.
    Note:  
    When you have configured the two temporary unprotected terminals, you can go Back in the wizard and create a protected terminal by changing the protection mode of the MMU in the lower position to 1+1.

This procedure is followed by outdoor equipment installation, indoor and outdoor radio cabling, and antenna alignment. Follow the instructions in MINI-LINK TN ANSI Indoor Installation Manual, and MINI-LINK TN, MINI-LINK HC, MINI-LINK E Outdoor Installation Manual.

The initial setup is finished by the configuration of NE parameters, that is security, DCN and system parameters. This can be done in two ways:

5.2   Automatic Configuration of NE Parameters

This section describes the configuration of NE parameters, using a configuration file. This always includes configuration of security, DCN and system parameters. The configuration file could also include the configuration of plug-in units and interfaces.

The configuration files are located in the <drive:>\tn_ftp_home\tn_backup_configuration folder on the FTP server. A configuration file is named <hostname>.cfg where <hostname> is typically the name or IP address of an NE. The file extension .cfg.old is used when a configuration file is uploaded using a file name that already exists.

Note:  
For NPU2 A/NPU1 BA, you can exit the wizard at any time by clicking Exit Wizard on the Configuration menu.

To configure the NE parameters automatically:

  1. On the Configuration menu, click Automatic Configuration.
  2. On the Automatic Configuration page, click Download Configuration File.
  3. On the Load Configuration page, type the File Name and then click Apply.
  4. Wait until the configuration has been downloaded, then click Apply when you have verified that this is the configuration you want.

    If the configuration file requires new software to be loaded, this will be done automatically. This requires that the software is present in the <drive:>\tn_ftp_home\tn_system_release\ml_tn_software folder.

    A progress bar displays the progress of the software upgrade. When the download and software upgrade is finished, the NE will make a warm restart. After the restart you can continue with the configuration of the plug-in units and their interfaces, see Section 6.

  5. For an NPU1 ANSI the following also applies:

    After the restart it will run in Normal mode. The IP address of the NE is changed during the automatic configuration. To start the LCT in Normal mode you have to enter the URL http://<IP address> where IP address is typically found in the site documentation or on the information plate of the NE. See also Section 3.3.2.3.

5.3   Manual Configuration of NE Parameters

This section describes the configuration of the NE parameters, without using a configuration file. This includes configuration of security, DCN and system parameters.

Note:  
Make sure the Radio Terminals which will carry DCN are up and that the antennas are aligned before starting this procedure, see Section 5.1.

Note:  
The procedure below may contain steps not applicable to your configuration.

Note:  
For NPU2 A/NPU1 BA, you can exit the wizard at any time by clicking Exit Wizard on the Configuration menu.

To configure the NE parameters manually:

  1. On the Configuration menu, click Manual Configuration.

Performing a Local Software Upgrade

  1. On the Manual Configuration page, click Perform Software Upgrade. If a software upgrade is not required click Next and continue to Step 8.
  2. On the Software Upgrade - Installation Wizard page, under Desired Baseline, enter the Product Number and Release of the new baseline.
  3. Click Start Upgrade. The Upgrade Progress - Baseline page monitors the download of the new software. The page is refreshed every fifth second. When all load modules have been correctly received, the baseline gets status Upgrade Finished and the Activate button appears.
  4. Click Activate. When the activation is done, the Confirm New System Configuration page is displayed.
    Note:  
    You can check if the restart is finished by refreshing the page in your browser. While the Web server is down you will get an error message.

  5. Click Confirm. The new baseline is now the active software in the NE.
    Note:  
    If you do not confirm the new software configuration within 15 minutes of the restart, a new restart will occur and the NE will revert to the previous software configuration.

  6. Click Next.

    Setting Passwords

    1. On the Manual Configuration page, click Configure Basic Security.
    2. On the Security page, under Set control_user and Set view_user, type Password and Confirm Password and then click Apply.
    3. Click Next.

    Configuring Basic NE Parameters

    1. On the Manual Configuration page, click Configure Basic NE.
    2. On the Basic NE Configuration page, under Basic NE Data, type the NE Name.
    3. Specify NE Location and NE Contact information, such as the telephone number of the person responsible.
    4. Type the NE IP Address, Subnet Mask and Default Gateway of the NE.
    5. Under FAU Settings, select In Service for the units to be used.
      Note:  
      This step is not applicable for ATU (B).

    6. Under General Settings, in the Date/Time boxes, type the current date (yyyy-mm-dd) and time (hh:mm:ss).
    7. Type Alarm Filter Time or use the default value of 2.5 seconds.
    8. In the PM Start Time box, type the time of day that 24 hour performance interval starts or use the default value 00:00. This time can be set in the range 00:00 - 23:45 in steps of 15 minutes.
    9. In the Automatic Backup list, select where automatic backups of the configuration should be sent.
    10. Click Apply.
    11. Click Next.

      Configuring DCN Parameters

      1. On the Manual Configuration page, click Configure DCN.
      2. On the LAN/Servers Configuration page do one of the following:
      3. Specify Administrative Status of the LAN interface.
      4. Select the Enable Notifications check box if notifications should be sent for the LAN interface.
      5. Select the Speed of the LAN interface and MDI-MDIX.
      6. Under SNMP Manager (Trap Receiver), select the Enable Notifications check box if SNMP traps should be sent to SNMP Managers.
      7. In the SNMP Manager box, type the IP address of each SNMP Manager to be used. An SNMP Manager is for example MINI-LINK Manager.
      8. In the Port box, for each SNMP Manager, type the port number that the SNMP Manager uses for SNMP communication.
      9. Select SNMP Version for each SNMP Manager.
      10. Under Network Services, type the Domain name
      11. Type the IP address of each DNS Server to be used.
      12. Type the IP address or host name of the NTP Server.
      13. Type the DHCP Address or host name of the DHCP server the NE is a relay for.
      14. Under FTP, specify the IP address of the Remote FTP Server, User Name and Password.
      15. Repeat the previous step for the Local FTP Server.
      16. Click Apply.
      17. On the LAN/Servers Configuration page, click PPP.
      18. On the PPP Configuration page, for each interface, specify the Administrative Status and Notifications.
      19. For each numbered interface, type the IP Address. The box should be left empty for an un-numbered interface.

        Caution!  
        It is recommended to set all interfaces destined to the same NE as either numbered or un-numbered. Mixing both types may cause DCN instability.
      20. Click Apply.

      Creating Static Routes

      1. On the PPP Configuration page, click Static Routing.
      2. On the Static Routing Configuration page, type Destination, Route Mask and Gateway.
      3. Click Create. The static route is displayed under Current Static Routes.
      4. Repeat the two previous steps for each static route to be created. To modify or delete a static routes, see Section 6.11.4.

      Creating OSPF Areas

      1. On the Static Routing Configuration page, click OSPF Areas.
      2. On the OSPF Areas Configuration page, type Net Address, Subnet Mask, Area ID and select Area Type.
      3. Click Create. The OSPF area is displayed under Current OSPF Areas.
      4. Repeat the two previous steps for each OSPF area to be created. To modify or delete OSPF areas, see Section 6.11.6.

      Configuring DCN Over Traffic

      1. Do one of the following:
      2. On the DCN Over Traffic page, select the DCN service mode: DCN over dedicated DS1 or DCN over channelized DS1 with traffic passthrough.
      3. Click Apply.
      4. Under Interface Settings, in the Unit for DS1 list, select the unit which holds the DS1 you want to use for DCN.
        Note:  
        There are two Interface Settings groups on the configuration page. It does not matter which of these groups you use.

      5. In the DS1 list, select the DS1 to be used for DCN and click Select.
      6. Select the Error AIS check box if AIS should be sent in case of connection failure.
        Note:  
        This step is only applicable when DCN over channelized DS1 with traffic passthrough is selected.

      7. In the Clock Source list, select the clock to be used as transmit clock.
      8. In the Framing list, select the framing mode and click Select. Go to Step 60 if you selected Unframed.
      9. Use the Idle Pattern check boxes to specify the bit pattern for unused timeslots.
      10. Use the Timeslots check boxes to specify which timeslots to use for DCN. Timeslots that are already used for other purposes are not selectable.
      11. Repeat from Step 53 if you want to use a second DS1 for DCN.
      12. Click Apply.
      13. Click Next.
      14. Go to Step 68.

      Configuring DS1 for DCN (NPU1 ANSI NE only)

      1. On the OSPF Areas Configuration page, click Next.
      2. On the Manual Configuration page, click Configure DS1 DCN.
      3. On the DS1 DCN Configuration page, select the DS1 interface to be used for DCN and then click Apply.
        Note:  
        All interfaces are not available at this stage. When the initial setup is completed, the DS1 DCN Configuration page can be used to select an DS1 for DCN, see Section 11.52.

      4. Click Next.

        Finishing the Installation

        1. On the Manual Configuration page, click Finish Installation.
        2. On the Finish Installation page, click OK. This will exit the installation wizard and you can continue with the configuration of the plug-in units and their interfaces, see Section 6.
        3. For NPU1 ANSI the following also applies:

          The NE will make a warm restart. After the restart it will run in Normal mode. The IP address of the NE is changed during the manual configuration. To start the LCT in Normal mode you have to enter the URL http://<IP address> where IP address is the one set in Step 14. See also Section 3.3.2.3.

        6   Configuration Management

        This section contains information and instructions related to configuration tasks performed after the initial setup has been completed. It includes the configuration of plug-in units, Radio Terminals, interfaces, traffic routing, protection and DCN.

        The following is covered:

        6.1   Typical Workflow

        When the initial setup is completed, the following steps represent a typical workflow:

        1. Configure plug-in units and their interfaces, see Section 6.4.
        2. Finalize the configuration of the Radio Terminals, see Section 6.5.
        3. Create APS protection, see Section 6.6.1.
        4. Create 1+1 DS1 SNCP protection, see Section 6.7.1.
        5. Configure the Ethernet Bridge (NPU2 A), see Section 6.8.
        6. Create traffic routing of DS1 interfaces, see Section 6.9.1.
        7. Upload a configuration file as backup to an FTP server, see Section 6.12.

        6.2   Administrative Status

        The desired status of a plug-in unit or interface is set as Administrative Status on the applicable Configuration page.

        The signification of the administrative status of a plug-in unit is described in Table 3.

        Table 3    Administrative status of a plug-in unit

        Administrative status

        Description

        In Service

        Sets the unit in operating mode.

        Out of Service

        Sets the unit in non-operating mode. All notifications from the unit and its interfaces are disabled. No active alarms are displayed.

        The signification of the administrative status of an interface is described in Table 4.

        Table 4    Administrative status of an interface

        Administrative status

        Description

        Up

        Sets the interface in operating mode.

        Down

        Sends an AIS instead of traffic on the interface (in both directions). Notifications from this interface and higher layer interfaces are suppressed.

        When a new unconfigured plug-in unit is inserted the administrative status of the unit is In Service and its interfaces are Up by default. The notifications from the unit and its interfaces will be enabled. However, to prevent too many alarms from not traffic routed DS1s, notifications are default disabled on these interfaces.


        6.3   Licensing Optional Features

        Depending on which plug-in units are installed, all NEs have a baseline of features that are available without licenses. If the installed NPU has an RMM, the set of available features can be expanded by installing licenses that unlock additional functionality in the NE. Depending on how the equipment was ordered, licenses can also be pre-installed at delivery.

        The process for migrating from MINI-LINK TN R2 to MINI-LINK TN R3 is described in the document Migration into License Management, 3/221 02-CSH 109 32/1 Uen

        6.3.1   Using Optional Features

        All optional features are indicated by a icon in the user interface. This icon only means that this feature is licensed; it is not an indication on whether a license for this feature is available or not.

        When you try to use an optional feature, you may or may not get a warning or error message. This depends on whether license warnings and errors are set to be suppressed on this NE. See Section 6.3.10 for instructions on how to suppress warnings and errors.

        License warnings are issued whenever you are using an optional feature without a license; however, the feature can still be used. Licence errors means that the feature is locked (disabled) due to missing licenses. In MINI-LINK TN R3, optional features are never locked. Future releases of MINI-LINK TN may lock features if licenses are missing.

        If you have upgraded the NE to MINI-LINK TN R3, you should create a license request file and provide it to your local Ericsson representative. See Section 6.3.4 for instructions on how to create such files.

        6.3.2   License Key File (LKF)

        Licenses are distributed in the form of LKFs which can be stored in those NEs where additional functionality is required.

        An LKF is an XML file that may contain one or more licenses for one or more optional features. When installed, the LKFs are stored on the Removable Memory Module (RMM), which is located on the NE NPU. Licenses for a particular feature may be provided by one or more LKFs.

        The LKF is identified by issuer, fingerprint, and sequence number:

        As several LKFs from different issuers can be stored on a single RMM, the effective set of licenses is the sum of all licenses from all LKFs.

        6.3.3   Removable Memory Module (RMM)

        The RMM is the physical media where the License key Files (LKFs) are stored. Several LKFs, from different issuers, may be stored on the RMM. Every RMM has a unique fingerprint that is used to confirm that the licenses in an LKF may be used on the NE where the RMM is installed (the fingerprint is the same as the Chip S-Nr printed on the RMM). The RMM is installed on the NPU in the NE.

        Note:  
        You cannot install an RMM on an NPU1 ANSI. This means that there will be no locking of optional features.

        Figure 26 shows where the RMM is installed on the different units.

        Figure 26   Location of the RMM

        The RMM also stores the current configuration of the NE, and the name implies, the RMM is removable. This means that, if the NPU needs to be replaced, you can remove the RMM from the old NPU and install it on the new NPU. All licensed functionality will then automatically work with the new NPU and you can use the configuration stored on the RMM.

        6.3.4   Requesting Licenses

        Licenses that where bought in previous releases of MINI-LINK TN are not bound to individual NEs. Instead, they are registered on a per-customer basis. To be able to use these licenses in MINI-LINK TN R3, they need to be transformed into licenses that can be installed on each NE. This transformation of licenses require that you provide Ericsson with detailed information about the licenses you need for each individual NE.

        To simplify this process, you can create a license request file for the network or for single NE, after upgrading to MINI-LINK TN R3. This is an XML file that contains all information that is needed to do the transformation of licenses. This file should be provided to your local Ericsson representative who forwards it to the Ericsson central license register, where it is used to generate one or more LKFs containing licenses for the NEs.

        Note:  
        The following procedure describes how to create a license request file for a single NE. However, if you are migrating an entire network, you are recommended to do this as a batch job from ServiceOn Microwave, or from a version of MINI-LINK Manager that supports this.

        The process for migrating from MINI-LINK TN R2 to MINI-LINK TN R3 is described in the document Migration into License Management, 3/221 02-CSH 109 32/1 Uen

        To create a licence request file:

        1. In the Navigation Tree, click the NE.
        2. On the Tools menu, click Licenses, and then click Licences.
        3. Click Create License Request.
        4. In the Quantity column, specify how many licenses you need for each feature.

          The default value in the Quantity column is the difference between the value in the Installed column and the value in the Used column. This value cannot be negative.

        5. Click Save License Request to save the license request to a file.

        6.3.5   Installing Licenses

        To change the set of licenses, you need to download and store one or more LKFs on the RMM:

        1. In the Navigation Tree, click the NE.
        2. On the Tools menu, click Licenses, and then click Install Licences.
        3. Under FTP, do one of the following:

          The LKF must be located in the tn_ftp_home\tn_licenses folder on the FTP server.

        4. In the File Name box, type the file name of the LKF or click Browse to search for the file.
        5. Click Apply.
          Note:  
          If the fingerprint in the LKF does not match the RMM fingerprint, you will get a warning.

        6.3.6   Viewing Available Optional Features

        Based on the AMM type and software baseline, the system keeps a list of all optional features that can be used. The system also keeps track of how many licenses are installed for each feature and how many of those licenses that are used.

        To see a list of all available optional features, license availability, and license usage:

        1. In the Navigation Tree, click the NE.
        2. On the Tools menu, click Licenses, and then click Licences.

          A list of available optional features is shown.

          The Installed column contains a summary of all installed licenses from all LKFs on the RMM. The Used column shows how many licenses that are needed for the current configuration, that is, how many optional features that are used.

          If the value in the Used column is greater than the corresponding value in the Installed column, the NE is using optional features without licenses.

          If the value in the Used column is less than the corresponding value in the Installed column, the NE has licenses for unused features.

          The Status column shows the status of the licenses for this feature:

          Clicking a feature opens a list of installed licenses for that feature, see Section 6.3.8.

        6.3.7   Viewing a List of Stored LKFs

        An RMM may store several LKFs, provided they have different issuers.

        To see a list of all stored license files:

        1. In the Navigation Tree, click the NE.
        2. On the Tools menu, click Licenses, and then click Licence File Overview.

          A list of all stored LKFs is shown.

          Clicking an LKF opens a page where the XML source of the LKF is shown, see Section 6.3.9.

        6.3.8   Viewing a List of Optional Features with Installed Licenses

        An LKF may contain licenses for more than one feature, and licenses for one feature may be contained in several LKFs. The system keeps track of which licenses are installed from which LKF.

        To view a list of features with installed licenses:

        1. In the Navigation Tree, click the NE.
        2. On the Tools menu, click Licenses, and then click Licence File Inventory.

          A list of features with installed licenses is shown.

          If several LKFs contains licenses for the same feature, the list will contain one entry for each LKF. For example, if two LKFs both contains a license for a specific feature, that feature will appear twice in the list.

          Clicking a feature opens a page where the XML source of the LKF is shown, see Section 6.3.9.

        6.3.9   Viewing LKF Details

        The LKF is an XML file containing licenses from an issuer. To see the details of that file, you can view the XML source.

        To view the license file details:

        1. In the Navigation Tree, click the NE.
        2. On the Tools menu, click Licenses, and then click Licence File Overview.
        3. Click an LKF in the list to see its XML source.

        6.3.10   Suppressing License Warnings and Errors

        If you suppress warnings and errors, you can still see the status of the license usage on the Licenses page, see Section 6.3.6.

        To suppress license warnings and errors:

        1. In the Navigation Tree, click the NE.
        2. On the Configuration menu, click Basic NE.
        3. Under General Settings, select if license warnings and errors should be suppressed (hidden).
        4. Click Apply.

        6.4   Unit and Interface Configuration

        Note:  
        This section describes how to configure units and interfaces not included in a Radio Terminal. The configuration of Radio Terminals is described in Section 6.5.

        To configure a unit or interface:

        1. In the Navigation Tree, navigate to and select the entity to configure.
        2. On the Configuration menu, click Configuration.
        3. Configure the entity.

          Click Help for information on the configuration options. See also Table 5 to find the applicable configuration page description.

        4. Click Apply on the configuration page to apply the changes.
        Table 5    References to Configuration Pages

        Unit and related entities

        See

        PFU1

        Section 11.22

        PFU2

        Section 11.23

        PFU3

        Section 11.24

        FAU

        Section 11.15

        Section 11.25

        NPU1 BA

        NPU1 ANSI

        NPU2 A

        • LAN Interface (NPU2 A/NPU1 BA)

        • Single DS1 Interface

        • All DS1 Interfaces

        • User Input (NPU1 ANSI/NPU1 BA)

        • User Output (NPU1 ANSI/NPU1 BA)

        Section 11.26

        Section 11.27

        Section 11.28

        LTU 12xDS1

        LTU 16xDS1

        LTU 16/1

        • Single DS1 Interface

        • All DS1 Interfaces

        Section 11.32

        Section 11.33

        LTU 155 ANSI

        • Line/Section Interface

        • APS Interface(1)

        • STS-1 Interface

        • Single VT1.5 Interface

        • All VT1.5 Interfaces

        • Single DS1 Interface

        • All DS1 Interfaces

        Section 11.34

        ETU2

        Bridge Interface

        Section 11.31

        Section 11.30

        SMU2 ANSI (co-siting)

        • Single DS1 Interface

        • All DS1 Interfaces

        Section 11.36

        MMU2 BA/CA

        • RAU unit

        • RF Interface

        • RAU Interface

        • SWITCH Interface (MMU2 B/C only)

        • MUX23

        • MUX12

        • Single DS1 Interaface

        • All DS1 Interfaces

        Section 11.37

        (1)  Configured after both units and their interfaces are configured. See also Section 6.6.1 on how to create APS protection.

        6.5   Radio Terminal Configuration

        This section describes how to configure a radio terminal. It could be a completion of a configuration made during the initial setup or a completely new installation. The procedure is started indoors with a station radio cable connecting the MMU and the RAU. For further instructions, see MINI-LINK TN ANSI Indoor Installation Manual.

        The following procedures are covered:

        6.5.1   Configuring an Unprotected (1+0) Radio Terminal with MMU2 BA/C

        To configure an unprotected (1+0) Radio Terminal when the indoor part comprises one MMU2 BA/CA:

        1. In the Navigation Tree, click an MMU2 BA, MMU2 CA.
        2. Click the Configuration menu to open the MMU2 BA/CA Configuration page.
        Note:  
        Click the Show Far End link to see the corresponding configuration for the far-end terminal. The far-end is only available when at least one of its RAUs has operative status In Service.

        See Section 11.37 for information on which settings are available from the near-end EEM. If you want to make changes that are not available from the near-end EEM, you need to access the EEM for the far-end. See Section 6.5.5 for information on how to do this.


        1. Under ID, type the identity of the Radio Terminal in the Near End box.
        2. If the terminal should send notifications, select the Notifications check box.
        3. If an alarm should be generated when the received traffic originates from the wrong far-end, type the expected far-end identity in the Far End box, and select the Radio ID Check check box.
        4. Under Traffic Capacity - Modulation, select the wanted traffic capacity, modulation and frame format. Only possible combinations are listed.
        5. Under Protection Mode, select 1+0.
        6. Select BER Alarm Threshold.
        7. Under MMU2 BA/CA <ID>, select all check boxes.
        8. Click Apply for the terminals you have changed.
        9. Under MMU2 BA/CA <ID>, click the RAU <ID> link to open the RAU Configuration page.
        Note:  
        Click the Show Far End link to see the corresponding configuration for the far-end terminal. See Section 11.39 for information on which settings are available from the near-end EEM.

        1. Under Near End Radio Terminal <ID>, select all check boxes.
        2. Under RAU <ID>, type the transmit frequency in the Tx Frequency box.
        3. Select the Transmitter On check box.
        4. In the Tx Attenuator box, type the value of the fixed attenuator (if used).
        5. In the Output Power Mode list, select how the output power is to be controlled.

          If you select ATPC, then ATPC will be enabled on both the near- and far-end.

          Note:  
          The ATPC option is only available when all units in the radio link support ATPC. Click Show ATPC Capabilities to see which units support ATPC.

        6. Do one of the following:
        7. In the RF Input Alarm Threshold box, type the threshold for generating RF Input Threshold alarms.
        8. Click Apply for the terminals you have changed.
        9. Carry out the outdoor equipment installation, indoor and outdoor radio cabling, and antenna alignment. Follow the instructions in MINI-LINK TN ANSI Indoor Installation Manual and MINI-LINK TN, MINI-LINK E, MINI-LINK HC Outdoor Installation Manual.
        10. Configure the applicable interfaces:

        6.5.2   Configuring a Protected (1+1) Radio Terminal with MMU2 BA/CA

        Note:  
        The 1+1 configuration is only possible if the units are placed in adjacent AMM positions according to specifications in MINI-LINK TN ANSI Indoor Installation Manual.

        To configure a protected (1+1) terminal when the indoor part comprises two MMU2 BA or MMU2 CA units:

        1. Configure two temporary unprotected (1+0) Radio Terminals, one for each MMU that will be part of the final protected terminal, as described in Section 6.5.1.
          Note:  
          Do not turn on the transmitters when creating the temporary terminals.

          Note:  
          To be able to configure a protected terminal, the following conditions apply:
          • Both of the temporary terminals must be configured to use the same traffic capacity, modulation method, frame format and identity.
          • For 1+1 Hot configurations, both RAUs must have the same frequency.
          • For 1+1 Work configurations, both RAUs must have different frequencies.

        2. In the Navigation Tree, click the MMU in the lower position.
        3. Click the Configuration menu to open the MMU2 BA/CA Configuration page.
        Note:  
        Click the Show Far End link to see the corresponding configuration for the far-end terminal. The far-end is only available when at least one of its RAUs has operative status In Service.

        See Section 11.37 for information on which settings are available from the near-end EEM. If you want to make changes that are not available from the near-end EEM, you need to access the EEM for the far-end. See Section 6.5.5 for information on how to do this.


        1. Under Protection Mode, select 1+1 Hot or 1+1 Work.
        2. Click Apply to set the protection mode.
        3. Click the Protection Switch Configuration link to open the SWITCH Protection page.
        Note:  
        Click the Show Far End link to see the corresponding configuration for the far-end terminal. See Section 11.44 for information on which settings are available from the near-end EEM.

        1. Configure the protection as described in Section 11.44, then go back to the MMU2 BA/CA Configuration page.
        2. In the Fade Notification Timer box, type how many seconds that faults caused by fading must last before alarm notifications are sent. The default value is 200 seconds.
        Note:  
        Step 9 to Step 11 is repeated for both RAUs.

        1. Under MMU2 BA/CA <ID>, click the RAU <ID> link to open the RAU Configuration page.
        Note:  
        Click the Show Far End link to see the corresponding configuration for the far-end terminal. See Section 11.39 for information on which settings are available from the near-end EEM.

        1. Select the Transmitter On check box, then click Apply.
        2. Under Near End radio Terminal <ID>, click the MMU2 BA/CA <ID> link to return to the MMU2 BA/CA Configuration page. Repeat from Step 9 to Step 11 for the other RAU.
        3. Under MMU2 BA/CA <ID>, , select all check boxes, then click Apply.
        4. Configure the applicable interfaces:

        6.5.3   Configuring an Unprotected (1+0) Radio Terminal with MMU2

        To configure an unprotected (1+0) Radio Terminal when the indoor part comprises one MMU2:

        1. In the Navigation Tree, click an MMU2.
        2. Click the Configuration menu.
        3. On the MMU2 Configuration page, select In Service, clear the Enable check box and select Prepare for 1+0 configuration.
        4. Click Apply.
        5. Click Perform AM Setup and Hop Setup.
        6. In MSM, perform an AM and Hop Setup. Follow the instructions in MSM User Guide or MSM online Help. Exit MSM when finished.
        7. Carry out the outdoor equipment installation, indoor and outdoor radio cabling, and antenna alignment. Follow the instructions in MINI-LINK TN ANSI Indoor Installation Manual and MINI-LINK TN, MINI-LINK HC, MINI-LINK E Outdoor Installation Manual.
        8. Configure the applicable interfaces:
        9. On the MMU2 Configuration page, select the Enable check box and click Apply.

        6.5.4   Configuring a Protected (1+1) Radio Terminal with MMU2

        Note:  
        The 1+1 configuration is only possible if the units are placed in adjacent AMM positions according to specifications in MINI-LINK TN ANSI Indoor Installation Manual.

        To configure a protected (1+1) Radio Terminal when the indoor part comprises two MMU2 units and one SMU2:

        1. In the Navigation Tree, click one of the MMU2s.
        2. Click the Configuration menu.
        3. On the MMU2 Configuration page, select Prepare for 1+1 configuration and click Apply.
        4. For all three units, select In Service, clear the Enable check box and click Apply.
        5. Click Perform AM Setup and Hop Setup.
        6. In MSM, perform an AM and Hop Setup. Follow the instructions in MSM User Guide or MSM online Help. Exit MSM when finished.
        7. Carry out the outdoor equipment installation, indoor and outdoor radio cabling, and antenna alignment. Follow the instructions in MINI-LINK TN ANSI Indoor Installation Manual and MINI-LINK TN, MINI-LINK HC, MINI-LINK E Outdoor Installation Manual.
        8. Configure the applicable interfaces:
        9. On the MMU2 Configuration page, select the Enable check box for all three units and click Apply.

        6.5.5   Navigating to Far-End Radio Terminals

        For radio links where the near-end terminal is based on MMU2 or ATU MMU2, you are able to launch MSM and view the far-end (you need MSM 6.5 or later). The near-end terminal is shown in the left pane and the far-end terminal is shown in the right pane. From here you are able to view the alarms in the far-end radio-terminal, change configuration parameters, set loops, and so on. Section 6.5.3 and Section 6.5.4 describes how to launch MSM for unprotected and protected radio terminals.

        Similarly, if the near-end is based on MMU2 B/C, you can view alarms and change the configuration of the far-end by clicking the Show Far End link in the Alarms and Status, MMU2 BA/CA Configuration, RAU Configuration, and SWITCH Protection pages.

        However, if you want to see or change settings that are not available (read-only or not shown), you must open a second browser and access the far-end EEM. How to do this depends on the type of MMU in the near-end terminal:

        6.5.5.1   Navigating to Far-End when Near-End is Based on MMU2 BA/CA

        To navigate to the far-end terminal:

        1. In the Navigation Tree, click an MMU2 BA/CA in the near-end terminal.
        2. On the Fault menu, click Alarm and Status.
        3. Click Show Far End.
        4. If the far-end is based on MMU2 BA/CA make a note of the slot positions of the MMUs in the far-end.
        5. Click Launch Far End EEM.
        6. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
        7. If the far-end is based on MMU2 BA/CA, skip to Step 11.
        8. In the far-end browser, click the NE in the Navigation Tree.
        9. On the Fault menu, first click DCN, and then click PPP.
        10. Under Remote IP Address, find the IP address of the near-end NE. You will find the positions of the MMUs in the far-end terminal under PPP Name.
          Note:  
          If the far-end is a protected terminal based on MMU2, the position of the SMU2 is listed under PPP Name.

        11. In the Navigation Tree, find the MMUs in the far-end radio terminal.
        12. Depending on the unit types in the far-end terminal, do one of the following:

        6.5.5.2   Navigating to Far-End when Near-End is Based on MMU2

        Note:  
        Only MMU2 is described since the procedure for ATU MMU2 is similar.

        To navigate to the far-end terminal:

        1. In the Navigation Tree, click the NE.
        2. On the Fault menu, first click DCN, and then click PPP.
        3. Under PPP Name, find the positions of the MMUs in the near-end terminal. You will find the IP address of the far-end NE under Remote IP Address. The naming principles of unit positions are described in Section 4.7.
          Note:  
          If the near-end is a protected terminal based on MMU2, the position of the SMU2 is listed under PPP Name.

        4. Open a second (far-end) browser.
        5. Enter the far-end IP address in the Address field and then press Enter.
        6. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
        7. In the far-end browser, click the NE in the Navigation Tree.
        8. On the Fault menu, first click DCN, and then click PPP.
        9. Under Remote IP Address, find the IP address of the near-end NE. You will find the positions of the MMUs in the far-end terminal under PPP Name.
          Note:  
          If the far-end is a protected terminal based on MMU2, the position of the SMU2 ANSI is listed under PPP Name.

        10. In the Navigation Tree, find the MMUs in the far-end radio terminal.
        11. Depending on the unit types in the far-end terminal, do one of the following:

        6.6   Working with APS Protection

        This section describes how to create, modify and delete APS protection.

        6.6.1   Creating APS Protection

        This procedure describes how to create APS protection including two adjacent LTU 155 ANSIs. Each unit's OC-3/STS-3 port will have the status MSP 1+1 VC-12.

        Note:  
        The two LTU 155 ANSIs must be placed in adjacent AMM positions according to specifications in MINI-LINK TN ANSI Indoor Installation Manual..

        Note:  
        Creating APS protection will remove the existing traffic routings on the LTU 155 ANSI.

        To create MSP protection:

        1. Make sure that both units and their interfaces are configured, see Section 6.4.
        2. In the Navigation Tree, click one of the two LTU 155 ANSIs.
        3. Click the Configuration menu.
        4. On the LTU 155 ANSI Configuration page, under Port Configuration, click APS Protection.
        5. On the Create APS Protection page, click OK.
        6. The selected LTU 155 ANSI along with its adjacent unit will be configured to operate together as a protected pair, in an APS protection. During the process it is indicated how many units (0,1 or 2) that have been configured so far. The page is refreshed every fifth second to give up-to-date information about the progress.
        7. When the APS protection has been created the Modify APS Protection page is displayed.

        To verify or change the configuration of the APS protection do the following:

        1. In the Navigation Tree, click the APS interface found below one of the LTU 155 ANSIs.
        2. On the Configuration menu, click Configuration. The APS Configuration page is displayed, where the configuration can be changed.

        6.6.2   Modifying APS Protection

        This procedure describes how to change active line and switch mode for an existing APS protection, including two adjacent LTU 155 ANSI units.

        To modify APS protection:

        1. In the Navigation Tree, click one of the two LTU 155 ANSIs.
        2. Click the Configuration menu.
        3. On the LTU 155 ANSI Configuration page, under Port Configuration, click APS Protection.
        4. On the Modify MSP Protection page, change Active Line and/or Switch Mode.
        5. Click Apply.

        6.6.3   Deleting MSP Protection

        This procedure describes how to delete an existing MSP protection, including two adjacent LTU 155s. Deleting MSP protection will set the status of each unit's STM-1port to Not Configured, that is the port does not provide traffic until it is configured using the LTU 155 Configuration page, see Section 11.34.

        To delete MSP protection:

        1. In the Navigation Tree, click one of the two LTU 155s.
        2. Click the Configuration menu.
        3. On the LTU 155 Configuration page, under Port Configuration, click MSP Protection.
        4. On the Modify APS Protection page, change the status for both units to Not Configured.
        5. Click OK.
        6. The selected LTU 155 ANSI along with its adjacent unit will be set to operate alone. During the process, the Deleting APS Protection page indicates how many units (0,1 or 2) that have been configured so far. The page is refreshed every fifth second to give up-to-date information about the progress.
          Note:  
          If you leave the Deleting Protection page during the process and then enter it later, you have to re-specify the status of the second unit's OC-3/STS-3 port.

        7. When the MSP protection has been deleted the LTU 155 ANSI Configuration page is displayed.

        6.7   Working with 1+1 DS1 SNCP Protection

        This section describes how to create, modify and delete 1+1 DS1 SNCP protection using the EEM.

        Note:  
        If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

        6.7.1   Creating 1+1 DS1 SNCP Protection

        Protection of DS1 interfaces can be created in two ways:

        6.7.1.1   Creating 1+1 DS1 SNCP Protection Using the Matrix View

        1. In the Navigation Tree, click the NE.
        2. On the Configuration menu, click 1+1 DS1 SNCP.
        3. On the 1+1 DS1 SNCP Select Interfaces page, under Interface Type, select DS1 and then click Select.
          Note:  
          This version of EEM supports only selection of DS1.

        4. Under Select units for interface views, select the two units, one from each list, that contain the interfaces to be protected.
        5. Click Matrix View.
        6. On the 1+1 DS1 SNCP Matrix View page, click the blank button in the intersection point between the two interfaces to be protected. This creates a protection with default settings indicated by a P button in the intersection point.

          You can use an interface interval link to locate interfaces currently not present on an axis. The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

          Note:  
          If there is no blank button in the intersection point, the two interfaces cannot be used. To find out why, click the interface names to display the DS1 Overview page. The possible reasons can be summarized as follows:
          • One or both of the interfaces are already part of a 1+1 DS1 SNCP protection.
          • Both interfaces are already routed.
          • The interface is used for DCN.

          To modify the protection, route the protected interface or modify a traffic routing of the protected interface (optional):

          1. Click the P button .
          2. On the Modify 1+1 DS1 SNCP page, do one of the following:

          6.7.1.2   Creating 1+1 DS1 SNCP Protection Using the List View

          1. In the Navigation Tree, click the NE.
          2. On the Configuration menu, click 1+1 DS1 SNCP.
          3. On the 1+1 DS1 SNCP Select Interfaces page, under Interface Type, select DS1 and then click Select.
            Note:  
            This version of EEM supports only selection of DS1.

          4. Under Select units for interface views, select the units, one unit or All Units from each list, that contain the interfaces to be protected.
          5. Click List View.
          6. On the 1+1 DS1 SNCP List View page, select one or multiple interface pairs to be protected. When selecting multiple items, the topmost selected interfaces in the two lists will form an interface pair and so on. Use CTRL or SHIFT to select multiple items.
            Note:  
            The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

          7. Click Create and do one of the following:
          8. The 1+1 DS1 SNCP List View page is displayed. Click Show Current Protections to display the Current Protections list.

            To modify a protection, route the protected interface or modify a traffic routing of the protected interface (optional):

            1. Locate the protection and click Modify.
            2. On the Modify 1+1 DS1 SNCP page, do one of the following:

            6.7.2   Modifying or Deleting 1+1 DS1 SNCP Protection

            Existing protection of DS1 interfaces can be modified, that is change the protection parameters or route the protected interface, or deleted in two ways:

            6.7.2.1   Modifying or Deleting 1+1 DS1 SNCP Protection Using the Matrix View

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click 1+1 DS1 SNCP.
            3. On the 1+1 DS1 SNCP Select Interfaces page, under Interface Type, select DS1 and then click Select.
              Note:  
              This version of EEM supports only selection of DS1.

            4. Under Select units for interface views, select the two units, one from each list, that contain the interfaces in the protection.
            5. Click Matrix View.
            6. On the 1+1 DS1 SNCP Matrix View page, click the P button in the intersection point between the two interfaces in the protection.
              Note:  
              You can use an interface interval link to locate interfaces currently not present on an axis.

              Note:  
              The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            1. On the Modify 1+1 DS1 SNCP page do one of the following:

            6.7.2.2   Modifying or Deleting 1+1 DS1 SNCP Protection Using the List View

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click 1+1 DS1 SNCP.
            3. On the 1+1 DS1 SNCP Select Interfaces page, under Interface Type, select DS1 and then click Select.
              Note:  
              This version of EEM supports only selection of DS1.

            4. Under Select units for interface views, select the two units, one unit or All Units from each list, that contain the interfaces in the protection.
            5. Click List View.
            6. On the 1+1 DS1 SNCP List View page, click Show Current Protections to display the Current Protections list.

            1. Under Current Protections, do one of the following:
              Note:  
              The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            6.8   Configuring the Ethernet Bridge

            The procedure for setting up the Ethernet Bridge is different depending on which unit that is used for the bridge. Follow the following procedures for the unit you want to set up:

            If an ETU2 is inserted into an AMM 2p, you can configure the Ethernet Bridge on both units.

            6.8.1   Configuring the Ethernet Bridge in ETU2

            This section describes how to configure the Ethernet Bridge, implemented in the ETU2. A maximum of 16 DS1s can be used for transmission of Ethernet traffic.

            1. In the Navigation Tree, expand the ETU2 and then click a Bridge interface.
            2. On the Configuration menu, click Configuration.
            3. On the Bridge Configuration page, under Units, select the unit that contain the DS1s to be bridged and click Select.
            4. Under Interfaces, select the DS1s that should be bridged and click Add. Use CTRL or SHIFT to select multiple items.
            5. If the DS1s to be bridged belong to more than one unit, repeat the two previous steps.
            6. If DS1s should be removed do the following:

              Under IM Group Interfaces, select the DS1s to be removed and click Remove.

            7. Under IM Group, set the configuration options for the IM Group interface. See Section 11.30 for information on the options.
            8. Under Bridge, set the options for the Bridge interface. See Section 11.30 for information about the options.
            9. Click Apply.

            6.8.2   Configuring the Ethernet Bridge in NPU2 A

            This section describes how to configure the Ethernet Bridge, implemented in the NPU2 A. A maximum of 16 DS1s can be used for transmission of Ethernet traffic.

            To configure the Ethernet Bridge:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click Ethernet Bridge.
            3. On the Ethernet Bridge Configuration page, under Units, select the unit that contain the DS1s to be bridged and click Select.
            4. Under Interfaces, select the DS1s that should be bridged and click Add. Use CTRL or SHIFT to select multiple items.
            5. If the DS1s to be bridged belongs to more than one unit, repeat the two previous steps.
            6. If DS1s should be removed do the following:

              Under Bridged Interfaces, select the DS1s to be removed and click Remove.

            7. Select the Enable check box if alarm notifications should be sent for the bridge's HDLC encapsulation interface.
            8. Under Bridge, set the options for the Bridge interface. See Section 11.29 for information about the options.
            9. Click Apply.

            6.9   Working with Traffic Routing of DS Interfaces

            This section describes how to create, modify and delete traffic routing of DS1 interfaces.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            6.9.1   Creating Traffic Routing of DS1 Interfaces

            Traffic routing of DS1 interfaces can be done in two ways:

            6.9.1.1   Creating Traffic Routing of DS1 Interfaces Using the Matrix View

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click Traffic Routing.
            3. On the Traffic Routing Select Interfaces page, under Interface Type, select DS1 and then click Select.
            4. Under Select units for interface views, select the two units, one from each list, that contain the interfaces to be routed.
            5. Click Matrix View.
            6. On the Traffic Routing Matrix View page, click the blank button in the intersection point between the two interfaces to be routed. This creates a nameless traffic routing indicated by an X button in the intersection point.
              Note:  
              You can use an interface interval link to locate interfaces currently not present on an axis.

              Note:  
              If there is no blank button in the intersection point the two interfaces cannot be used. To find out why, click the interface names to display the DS1 Overview page. The possible reasons can be summarized as follows:
              • One or both of the interfaces are already routed or part of a 1+1 DS1 SNCP protection where the protected interface is already routed.
              • The two interfaces are part of the same 1+1 DS1 SNCP protection.

              Note:  
              The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            To name the traffic routing (optional):

            1. Click the X button to modify the traffic routing.
            2. On the Modify Traffic Routing page, type the Name and then click OK. The Traffic Routing Matrix View page will be opened.

            6.9.1.2   Creating Traffic Routing of DS1 Interfaces Using the List View

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click Traffic Routing.
            3. On the Traffic Routing Select Interfaces page, under Interface Type, select DS1 and then click Select.
            4. Under Select units for interface views, select the two units, one unit or All Units from each list, that contain the interfaces to be routed.
            5. Click List View.
            6. On the Traffic Routing List View page, select one or multiple interface pairs to be routed. When selecting multiple items, the topmost selected interfaces in the two lists will form one interface pair and so on. Use CTRL or SHIFT to select multiple items.
              Note:  
              The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            7. Click Create and do one of the following:
            8. The Traffic Routing List View page is displayed. Click Show Current Routings to display the Current Traffic Routings list.

            6.9.2   Modifying or Deleting Traffic Routing of DS1 Interfaces

            Existing traffic routing of DS1 interfaces can be modified or deleted in two ways:

            6.9.2.1   Modifying or Deleting Traffic Routing of DS1 Interfaces Using the Matrix View

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click Traffic Routing.
            3. On the Traffic Routing Select Interfaces page, under Interface Type, select DS1 and then click Select.
            4. Under Select units for interface views, select the two units, one from each list, that contain the interfaces in the traffic routing.
            5. Click Matrix View.
            6. On the Traffic Routing Matrix View page, click the X button in the intersection point between the two interfaces in the traffic routing.
              Note:  
              You can use an interface interval link to locate interfaces currently not present on an axis.

              Note:  
              The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            7. On the Modify Traffic Routing page, do one of the following:
            8. The Traffic Routing Matrix View page is displayed reflecting your changes.

            6.9.2.2   Modifying or Deleting Traffic Routing of DS1 Interfaces Using the List View

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click Traffic Routing.
            3. On the Traffic Routing Select Interfaces page, under Interface Type, select DS1 and then click Select.
            4. Under Select units for interface views, select the two units, one unit or All Units from each list, that contain the interfaces in that are routed.
            5. Click List View.
            6. On the Traffic Routing List View page, click Show Current Routings to display the Current Traffic Routings list.
            7. Under Current Traffic Routings do one of the following:
              Note:  
              The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            8. The Traffic Routing List View page is displayed reflecting your changes.

            6.10   Working with DS1 Overview

            The DS1 Overview page is opened in a separate window and provides a convenient way to view and change the configuration of an DS1 interface, as well as handle its 1+1 DS1 SNCP protection and traffic routing. Furthermore, it is possible to handle the DS1 as part of the Ethernet Bridge, implemented in the NPU2 A.

            This section covers the following procedures:

            6.10.1   Configuring an DS1, Creating 1+1 DS1 SNCP Protection and Traffic Routing

            This procedure describes how to use the main features of the DS1 Overview page, excluding the Ethernet Bridge handling. The different parts of the procedure can also be used standalone, when applicable.

            Opening the DS1 Overview page and Configuring an DS1

            1. In the Navigation Tree, click an DS1 that is neither protected nor routed.
            2. On the Configuration menu, click Configuration.
            3. On the DS1 Configuration page, view the parameters at hand. If required, make changes and click Apply.
            4. Click DS1 Overview to open the DS1 Overview page in a separate window. The upper part of the page displays the configuration of the DS1 for which the page is opened. The lower part is a graphical view used to display and change protection and traffic routing related to this DS1.
              Note:  
              The upper part of the page will have links to the DS1 Configuration page for all DS1s related to the one for which the page is opened. Use these links to change the configuration, if required.

            Creating a 1+1 DS1 SNCP Protection

            1. On the DS1 Overview page, click Create 1+1 DS1 SNCP. The 1+1 DS1 SNCP List View page is opened in the main EEM browser window. The DS1 for which the DS1 Overview page is opened is preselected in the Interface 1 list. The Interface 2 list contains all available DS1s that can be used to create a protection.
            2. On the 1+1 DS1 SNCP List View page, under Interface 2, select an DS1 and click Create.
            3. On the Create 1+1 DS1 SNCP page, define Hold-Off Time and Switch Mode. Click Apply.
            4. On the DS1 Overview page, click Reload. The page is now updated with an SNCP symbol for the new protection. The configuration of the two unprotected and the protected DS1 s are also displayed in the upper part of the page.

            Creating Traffic Routing

            1. On the DS1 Overviewpage, click Create Traffic Routing.
            2. The Traffic Routing List View page is opened in the main EEM browser window. The protected DS1 is preselected in the Interface 1 list. The Interface 2 list contains all available DS1 s that can be used to create a traffic routing.
            3. On the Traffic Routing List View page, under Interface 2, select an DS1 and click Create.
            4. On the Create Traffic Routing page, specify a Name of the traffic routing and click Apply.
            5. On the DS1 Overviewpage, click Reload. The page is now updated with a Traffic Routing symbol. The configuration of the DS1 selected under Interface 2 is also displayed in the upper part of the page.

            Creating a 1+1 DS1 SNCP Protection

            1. If the DS1 selected under Interface 2 in Step 11 in Section 6.10.1 should be protected as well, repeat Step 5 in Section 6.10.1 to Step 8 in Section 6.10.1 above. This protection will be displayed with an SNCP symbol to the right. The configuration of the DS1s in this protection is also displayed in the upper part of the page.

            6.10.2   Adding an DS1 to the Ethernet Bridge

            The DS1 Overview page displays if an DS1 is used for the Ethernet Bridge, implemented in ETU2, NPU2. If not, the DS1 can be added. See also how to configure the Ethernet Bridge in Section 6.8.

            To add an DS1 to the Ethernet Bridge:

            1. In the Navigation Tree, click an DS1 that is not used for the Ethernet Bridge.
            2. On the Configuration menu, click Configuration.
            3. On the DS1 Configuration page, view the parameters at hand. If required, make changes and click Apply.
            4. Click DS1 Overview to open the DS1 Overview page in a separate window.
            5. On the DS1 Overview page, click Add DS1 to Ethernet Bridge.
            6. The Ethernet Bridge Configuration page is opened in the main EEM browser window. The selected DS1 and the unit containing it are preselected.
            7. On the Ethernet Bridge Configuration page, click Add. The DS1 is added to the Bridged Interfaces list.
            8. On the DS1 Overview page, click Reload. The Ethernet Bridge symbol is now displayed.

            6.10.3   Adding a G.804 to the Ethernet Bridge

            1. In the Navigation Tree, click an DS1 that is not used for the Ethernet Bridge.
            2. On the Configuration menu, click Configuration.
            3. On the DS1 Configuration page, view the parameters at hand. If required, make changes and click Apply.
            4. Click DS1 Overview to open the DS1 Overview page in a separate window.
            5. On the DS1 Overview page, click Add DS1 to Ethernet Bridge.
            6. The Ethernet Bridge Configuration page is opened in the main EEM browser window. The selected DS1 and the unit containing it are preselected.
            7. On the Ethernet Bridge Configuration page, click Add. The DS1 is added to the Bridged Interfaces list.
            8. On the DS1 Overview page, click Reload. The Ethernet Bridge symbol is now displayed.

            6.11   DCN Configuration

            This section covers general information and procedures related to the Data Communication Network (DCN), providing IP based transport of operation and maintenance data between management systems and MINI-LINK TN equipment.

            The DCN parameters are normally set during the initial setup but can also be changed later following procedures in this section.

            6.11.1   Overview

            Each NE holds an internal IP router using numbered and un-numbered interfaces. PPP interfaces configured for an Area Border Router (ABR) use numbered interfaces. All other interfaces are un-numbered, that is inheriting the IP address of the router.

            Basic DCN parameters, such as IP address and default gateway, are set during the initial setup, see Section 5.3. These parameters can always be changed from the LAN/Servers Configuration page, see Section 11.16.

            The preferred IP routing strategy for MINI-LINK TN is the Open Shortest Path First (OSPF) protocol, which makes use of automatically updated routing tables in order to determine the most efficient transmission of data. The OSPF areas can be created during the initial setup or at a later occasion, see Section 6.11.5. The Command Line Interface (CLI) is used for advanced OSPF configuration and troubleshooting, see Section 6.14.3.

            MINI-LINK TN supports static routing from the EEM. Static routing can be configured during the initial setup or at a later occasion, see Section 6.11.3. The CLI also provides configuration of static routing, see Section 6.14.4.

            The available DCN channels are briefly described below.

            DS1   One DS1 interface per NPU1 ANSI NE and up to two DS1 interfaces per NPU1 BA/NPU2 A NE can be used for transport of DCN traffic. The interfaces can be selected during the initial setup, see Section 5.3. It is also possible to select the interface from the DS1 Configuration page, see Section 11.52.
            Radio Terminal   An unprotected (1+0) protected or protected (1+1) Radio Terminal provides two 64 kbit/s PPP interfaces by default.
            OC-3/STS-3   The OC-3/STS-3 interface (stand-alone or APS) on the LTU 155 ANSI provides PPP interfaces in the RSOH and MSOH bytes of the SONET frame. The default bandwidth is DCCR=192 kbit/s and DCCM=192 kbit/s. The bandwidth can be changed, see Section 6.11.2.1.
            LAN   The LAN interface on the NPU can be used to connect to an external DCN. The NPU 8x2 provides 10 Mbit/s. For NPU2/NPU1 B it is possible to configure the interface to 10 or 100 Mbit/s on the LAN/Servers Configuration page, see Section 11.16.

            For ATU (B), the LAN interface is used to connect to an external DCN. It is possible to configure this 10 Mbit/s interface on the LAN/Servers Configuration page, see Section 11.16.

            DIG SC   The SMU2 ANSI in co-siting mode provides 2x64 kbit/s channels for DCN connection, typically to co-sited MINI-LINK E equipment, see Section 6.11.2.2.

            For more specific information on DCN for MINI-LINK, see MINI-LINK DCN Guideline.

            6.11.2   Configuring the PPP Interfaces

            This section describes how to configure the PPP interfaces. They can specifically be used to change the default bandwidth of the OC-3/STS-3 PPP interfaces and to set the number of DIG SC (2x64 kbit/s) for SMU2 ANSI in co-siting mode.

            To configure the PPP interfaces:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click PPP.
            3. On the PPP Configuration page, for each interface, specify the Administrative Status and Notifications.
            4. For a numbered interface, type the IP Address. The box should be left empty for an un-numbered interface.

              Caution!  
              It is recommended to set all interfaces destined to the same NE as either numbered or un-numbered. Mixing both types may cause DCN instability.
            5. Click Apply.

            6.11.2.1   Changing the Bandwidth of the OC-3/STS-3 PPP Interfaces

            The OC-3/STS-3 interface (stand-alone or APS) on the LTU 155 provides PPP interfaces in the RSOH and MSOH bytes of the SONET frame. Table 7 and Table 9 show the possible and default bandwidth of the interfaces.

            For increased bandwidth it is recommended to change the administrative status of the interfaces in accordance with the tables.

            Table 6    Bandwidth of the STM-1 RSOH PPP interfaces

            Bandwidth [kbit/s]

            DCCR (D1-3) status

            0

            Down

            192

            Up (Default)


            Table 7    Bandwidth of the OC-3/STS-3 RSOH PPP interfaces

            Bandwidth [kbit/s]

            DCCR (D1-3) status

            0

            Down

            192

            Up (Default)


            Table 8    Bandwidth of the STM-1 MSOH PPP interfaces

            Bandwidth [kbit/s]

            DCCM (D4-6) status

            DCCM (D7-9) status

            DCCM (D10-12) status

            0

            Down

            Down

            Down

            192

            Up (Default)

            Down

            Down

            384

            Up

            Up

            Down

            576

            Up

            Up

            Up


            Table 9    Bandwidth of the OC-3/STS-3 MSOH PPP interfaces

            Bandwidth [kbit/s]

            DCCM (D4-6) status

            DCCM (D7-9) status

            DCCM (D10-12) status

            0

            Down

            Down

            Down

            192

            Up (Default)

            Down

            Down

            384

            Up

            Up

            Down

            576

            Up

            Up

            Up

            6.11.2.2   Setting the Number of DIG SC (2x64 kbit/s) for SMU2 in Co-siting Mode

            The SMU2 ANSI in co-siting mode provides 2x64 kbit/s channels for DCN connection, typically to co-sited MINI-LINK E equipment. If a channel should be used, the administrative status of the interface must be set to Up.

            6.11.3   Creating Static Routes

            Static routing means that a fixed routing scheme is used where the address of the router that a message will be sent to, has to be entered manually. A maximum of 100 static routes is possible.

            To create a static route:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click Static Routing.
            3. On the Static Routing Configuration page, type Destination, Route Mask and Gateway.
            4. Click Create. The static route is displayed under Current Static Routes.

            See also Section 6.14.4 on how to use the CLI to create static routes.

            6.11.4   Modifying or Deleting Static Routes

            To modify or delete an existing static route:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click Static Routing.
            3. On the Static Routing Configuration page, under Current Static Routes, do one of the following:
            4. The Static Routing Configuration page is displayed reflecting your changes.

            6.11.5   Creating OSPF Areas

            The Open Shortest Path First (OSPF) protocol makes use of automatically updated routing tables in order to determine the most efficient transmission of data. OSPF networks are divided in sections, so called OSPF areas. The EEM can be used to create OSPF areas as described below. If there is only one ABR within an area, it is recommended to define the area as a stub area in order to improve the performance of the routing.

            To create an OSPF area:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click OSPF Areas.
            3. On the OSPF Areas Configuration page, type Net Address, Subnet Mask, Area ID and select Area Type.
            4. Click Create. The OSPF area is displayed under Current OSPF Areas.

            6.11.6   Modifying or Deleting OSPF Areas

            To modify or delete an existing OSPF area:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click OSPF Areas.
            3. On the OSPF Areas Configuration page, under Current OSPF Areas, do one of the following:
            4. The OSPF Areas Configuration page is displayed reflecting your changes.

            6.11.7   Configuring DCN Over Traffic

            Two unframed or framed (channelized) DS1s can be used for transport of DCN data. It can be a fixed DS1 connected to an NPU1 BA, NPU2 A or LTU, an DS1 transported in an OC-3/STS-3 frame or an DS1 transported over a radio link.

            The DCN data can be transported over a dedicated DS1 or use spare timeslots in an DS1 used for traffic. Depending on framing, a complete 2 Mbit/s or up to 31 timeslots can be used for DCN for the selected DS1s.

            6.11.7.1   Using a Dedicated DS1 for DCN

            To use a dedicated DS1 for DCN:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click DCN Over Traffic.
            3. On the DCN Over Traffic page, select DCN over dedicated DS1.
            4. Under Interface Settings, in the Unit for DS1 list, select the unit that holds the DS1 you want to use for DCN, then click Apply.
              Note:  
              There are two Interface Settings groups on the configuration page. It does not matter which of these groups you use.

            5. In the DS1 list, select the DS1 to be used for DCN and click Select.
            6. In the Clock Source list, select the clock to be used as transmit clock.
            7. In the Framing list, select the framing mode and click Select. Go to Step 10 if you selected Unframed.
            8. Use the Idle Pattern check boxes to specify the bit pattern for unused timeslots.
            9. Use the Timeslots check boxes to specify which timeslots to use for DCN. Timeslots that are already used for other purposes are not selectable.
            10. Repeat from Step 4 if you want to use a second DS1 for DCN.
            11. Click Apply.

            6.11.7.2   Using Spare Timeslots in an DS1 Used for Traffic

            To use spare timeslots in an DS1 used for traffic:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click DCN Over Traffic.
            3. On the DCN Over Traffic page, select DCN over channelized DS1 with traffic pass-through..
            4. Under Interface Settings, in the Unit for DS1 list, select the unit that holds the DS1 you want to use for DCN, then click Apply.
              Note:  
              There are two Interface Settings groups on the configuration page. It does not matter which of these groups you use.

            5. In the DS1 list, select the DS1 to be used for DCN and click Select.
            6. Select the Error AIS check box if AIS should be sent in case of connection failure.
            7. In the Timing list, select the timing mode.
            8. In the Framing list, select the framing mode and click Select.
            9. Use the Idle Pattern check boxes to specify the bit pattern for unused timeslots.
            10. Use the Timeslots check boxes to specify which timeslots to use for DCN. Timeslots that are already used for other purposes are not selectable.
            11. Repeat from Step 4 if you want to use a second DS1 for DCN.
            12. Click Apply.

            6.11.8   Modifying or Deleting DCN Over Traffic

            To modify or delete :

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click DCN and then click DCN Over Traffic.
            3. On the DCN Over Traffic page, do one of the following:

            6.12   Uploading a Configuration File to an FTP Server

            This procedure describes how to upload a configuration file to an FTP Server for backup purposes.

            Note:  
            It is recommended to carry out this procedure when the installation and configuration of a new NE is completed.

            To upload a configuration file:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click Load Configuration.
            3. On the Load Configuration page, under Configuration File, select Upload to FTP server.
            4. Specify File Name. The configuration will be stored in the <drive:>\tn_ftp_home\tn_backup_configuration folder.
            5. Under FTP, do one of the following:
            6. Click Apply.

            6.13   Software Upgrade

            Whenever the system configuration is changed, for example by adding or replacing plug-in units, it could be necessary to upgrade the system software. The process can be performed locally with the PC connected directly to the NE or from remote location using a DCN connection.

            Note:  
            Software Upgrade cannot be performed when the NE is in fault mode.

            Note:  
            Warnings will be issued when you perform both upgrade and downgrade.

            Note:  
            When you are downgrading beware that you can loose support on some units.

            The following tasks are covered:

            6.13.1   Performing an Upgrade of Baseline

            This procedure describes how to perform a software upgrade, where all load modules comply with a baseline defined in a Software Baseline Description File (SBDF).

            Note:  
            The SBDF and the load modules must be stored in specific folders under: <drive:>\tn_ftp_home\tn_system_release\
            ml_tn_software
            , see Section 3.2.1.2. See also Section 3.2.4 for instructions on how to install a Software Baseline on the LCT PC.

            Note:  
            MMU2 (and their connected RAUs) and SMU2 ANSI(protection) are upgraded using MSM, Local Upgrade or MINI-LINK Manager.

            Note:  
            Load modules that are not included in the baseline must be upgraded separately as described in Section 6.13.2. For example, the load modules for RAUs are not included in the baselines defined by Ericsson.

            To perform an upgrade of baseline:

            1. In the Navigation Tree, click the NE.
            2. On the Tools menu, click Software Upgrade.
            3. On the Upgrade of Baseline page, under Desired Baseline, specify the Product Number and Release state of the new baseline.
            4. Click Apply and then click Next.
            5. On the Settings page, under FTP server, do one of the following:
            1. Under Activation, do one of the following:
            2. Under Confirmation, do one of the following:
            3. Verify the Preferences used for the software upgrade. The following is recommended:

              If Automatic Upgrade or Automatic Downgrade are cleared, the preferences can be changed after the SBDF has been loaded. This will then initiate an automatic software upgrade/downgrade.

            4. On the Settings page, click Next.
            5. On the Start Upgrade page, verify the requested actions and click Start Upgrade.

              The Upgrade Progress - Baseline page monitors the download of the new software configuration. The page is refreshed every fifth second. When all load modules have been correctly received, the status Upgrade Finished is displayed for the software baseline.

              If the upgrade fails, you can either click Cancel to cancel the upgrade and try again at a later time, or click Start Upgrade to retry the failed upgrade.

            1. Depending on the selected activation method the following apply:

            6.13.2   Performing an Upgrade of Modules

            This procedure describes how to perform a software upgrade of specific load modules.

            Note:  
            The load modules must be stored in specific folders under: <drive:>\tn_ftp_home\tn_system_release\
            ml_tn_software
            , see Section 3.2.1.2. See also Section 3.2.5 for instructions on how to install load modules on the LCT PC.

            Note:  
            MMU2 (and their connected RAUs) and SMU2 ANSI(protection) are upgraded using MSM, Local Upgrade or MINI-LINK Manager.

            Note:  
            Performing an upgrade of modules will disable version control.

            To perform an upgrade of modules:

            1. In the Navigation Tree, click the NE.
            2. On the Tools menu, click Software Upgrade.
            3. On the Upgrade of Baseline page, click Upgrade of Modules.
            4. On the Upgrade of Modules page, enter the New Release and select the Upgrade check box for each module to be included in the upgrade.
            5. Click Apply and then click Next.
            6. On the Settings page, under FTP server, do one of the following:
            7. Under Activation, select Immediate.
            8. Under Confirmation, do one of the following:
              Note:  
              Selecting Manual requires an action whenever the confirmation takes place.

            9. On the Settings page, click Next.
            10. On the Start Upgrade page, verify the requested actions and click Start Upgrade.

              The Upgrade Progress - Modules page monitors the download of the new software configuration. The page is refreshed every fifth second. When all load modules have been correctly received, the status Upgrade Finished is displayed for the all modules and the Activate button appears.

              If the upgrade fails, you can either click Cancel to cancel the upgrade and try again at a later time, or click Start Upgrade to retry the failed upgrade.

            11. Click Activate. The Activation page is displayed.
            12. If manual confirmation was selected, click Confirm on the Upgrade Progress - Modules page. The new software configuration is now the active software in the NE.
              Note:  
              If you do not confirm within 15 minutes the NE will revert to the old software configuration. Clicking Fallback will give the same result.

            13. When the software upgrade is finished, you can use the View Units page to verify the load module version in each unit, see Section 11.82.

              Should a failure occur, the Event Log page provides information about the software upgrade, see Section 11.144.


            6.13.3   Performing Emergency Fallback for NPU2 A/NPU1 BA

            This procedure describes how to revert to a previous software release for an NPU2 A/NPU1 BA.


            Caution!  
            Use this function restrictively and only in the unlikely event that you have performed a software upgrade to a software version, from which you cannot perform a full software upgrade back to a correct version.

            To perform an emergency fallback:

            1. Connect the USB cable to the USB connector on the NPU.
            2. Start a Web browser and enter the URL http://10.0.0.1/.
            3. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
            4. On the Configuration menu, click Installation Wizard.
            5. On the Tools menu, click Emergency Fallback.
            6. On the Emergency Fallback page, click Perform Emergency Fallback.
            7. On the Perform Emergency Fallback page, click OK.
            8. Click OK, in the confirmation dialog box.
            9. On the Emergency Fallback page, click Finish Installation.
            10. On the Finish Installation page, click OK.
            11. The NE will make a warm restart. After the restart the NE is in NPU Installation mode where a configuration file can be downloaded that will cause an upgrade to a consistent system.

            6.13.4   Performing an Emergency Fallback for NPU1 ANSI

            This procedure describes how to revert to a previous software release for an NPU1 ANSI.


            Caution!  
            Use this function restrictively and only in the unlikely event that you have performed a software upgrade to a software version, from which you cannot perform a full software upgrade back to a correct version.
            Note:  
            The NE is accessed in Node Installation mode. Configure the PC to use a dynamic IP address obtained from the DHCP server in the NE or alternatively use the static IP address 10.0.0.2. For more information on IP addressing, see Section 3.3.3.

            To perform an emergency fallback:

            1. Switch off and switch on the power supply.

            Figure 27   Entering Node Installation mode

            1. While the Fault (red), Power (green) and BR (yellow) LEDs on the NPU1 ANSI are ON (NE power up), press the BR button gently and release it. The BR (yellow) LED will start flashing, indicating that the NE is in Node Installation mode.
            2. Connect the Ethernet cable (twisted pair) to the 10/100BASE-T port.
            3. Start a Web browser and enter the URL http://10.0.0.1/.
            4. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
            5. On the Tools menu, click Emergency Fallback.
            6. On the Emergency Fallback page, click Perform Emergency Fallback.
            7. On the Perform Emergency Fallback page, click OK.
            8. Click OK, in the confirmation dialog box.
            9. On the Emergency Fallback page, click Finish Installation.
            10. On the Finish Installation page, click Apply.
            11. The Installation Finished page is displayed and the NE will make a warm restart.

            6.14   Introduction to CLI

            This section gives an introduction to the Command Line Interface (CLI), a text based configuration tool similar to industry standards used for router configuration. It is intended for specific configuration and troubleshooting of IP routing parameters and accessed from a Command Prompt window using telnet.

            The following is covered:

            6.14.1   Overview

            This section describes how to use the CLI and the modes of operation.

            Figure 28   CLI in a Command Prompt window

            6.14.1.1   Confirmation of Configuration

            Configuration of parameters that could lead to loss of a DCN channel, for example change of IP address, need to be confirmed. The confirmation is made automatically if an EEM user is logged on as control_user and an NE generated ping command to the EEM PC is successful. Otherwise, confirmation of these parameters must be done manually.

            Confirmation from the CLI is done using the write command, see Table 12. It is also possible to use the Confirm button. The Status Bar indicates the remaining time and warnings will be issued when time is running out. It is also possible to use the show confirm timer command to display the remaining time, see Table 12.


            Caution!  
            If you do not confirm your configurations within 15 minutes, the NE will make a warm restart, restoring the saved configurations, and your unconfirmed changes will be lost.

            6.14.1.2   Help Facility

            The CLI contains a text based help facility accessed by typing in the full or partial command string then typing "?". The CLI displays the command keywords or parameters plus a short description. Typing only "?" displays all commands that can be entered.

            For example, at the CLI command prompt, type "ping?" (the CLI does not display the question mark). The CLI displays the following keyword list with short descriptions for each keyword:

            <HOST> Hostname to ping

            <A.B:C:D> IP Address to ping

            The CLI can complete the spelling of command or parameter keywords, using the TAB key. The following example shows how this function can be used.

            1. Type the beginning of a command. The CLI displays the complete command (if not ambiguous).

              TN-10-0-1-1>sh. Press the TAB key.

              TN-10-0-1-1>show

            2. The CLI shows if the command or parameter partial spelling is ambiguous and displays the choices that match the abbreviation.

              TN-10-0-1-1>show i. Press the TAB key.

              interface

              ip

            3. Type a character that excludes one of the choices.

              TN-10-0-1-1>show in. Press the TAB key.

              TN-10-0-1-1>show interface

            4. Type "?" to display the parameters for the specific command.

              [IFNAME] Interface name

              TN-10-0-1-1>show interface

            6.14.1.3   Command Modes

            The CLI commands are sorted into classes: Exec commands and Configuration commands. Configuration commands are further categorized into the following modes: Global Configuration, Interface Configuration and Router Configuration. Figure 29 illustrates the command modes.

            Figure 29   Command modes

            Below follows a description of the command modes. The IP address 10.0.1.1 is used as an example.

            6.14.1.3.1   Exec Mode
            Access method   Start a telnet session.

            C:\>telnet 10.0.1.1

            Password:<view_user password>

            Prompt   TN-10-0-1-1>
            Exit method   exit, quit, logout terminates the session.
            Description   Change terminal settings and perform basic tests. Display non-configurable information.
            6.14.1.3.2   Privileged Exec Mode
            Access method   Enter enable in Exec mode.

            Password:<control_user password>

            Prompt   TN-10-0-1-1#
            Exit method   disable exits to Exec mode. exit, quit or logout terminates the session.
            Description   Verify information and save configurations.
            6.14.1.3.3   Global Configuration Mode
            Access method   Enter configure in Privileged Exec mode.
            Prompt   TN-10-0-1-1(config)#
            Exit method   exit, end or CTRL+Z exits to Privileged Exec mode.
            Description   A gateway to other modes. Configuration of general IP parameters.
            6.14.1.3.4   Interface Configuration Mode
            Access method   Enter one of the following commands in Global Configuration mode:

            interface ethernet

            interface ospf <if>

            interface serial<if>

            Prompts   TN-10-0-1-1-(interface-ethernet)#

            TN-10-0-1-1-ospf(config-if)#

            TN-10-0-1-1-(interface-serial)#

            Exit method   exit or quit exits to Global Configuration mode.

            end or CTRL+Z exits to Privileged Exec mode.

            Description   Configuration of Ethernet, PPP interfaces and OSPF parameters related to specific interfaces.
            6.14.1.3.5   Router Configuration Mode
            Access method   Enter router ospf in Global Configuration mode.
            Prompt   TN-10-0-1-1-ospf(config-router)#
            Exit method   exit or quit exits to Global Configuration mode.

            end or CTRL+Z exits to Privileged Exec mode.

            Description   Configuration of the OSPF routing protocol.

            6.14.1.4   Command Editing Keys and Functions

            Table 10 describes the editing features of the CLI.

            Note:  
            The telnet client must be configured for VT100 emulation for the arrow keys to work.

            Table 10    Command editing keys and functions

            Keys

            Description

            TAB

            Completes a partial command name entry. When you enter a unique set of characters and press the TAB key, the system completes the command name. If you enter a set of characters that could indicate more than one command, the system beeps to indicate an error and provides a list of commands that begin with that string.

            ?

            Entering a stand-alone question mark (?) provides a list of all available commands. Entering a question mark (?) immediately after a partial command (no space), provides a list of commands that begin with that string.

            BACKSPACE

            Erases the character to the left of the cursor.

            ENTER

            Performs the function of processing a command. At the ">" prompt on a terminal screen, pressing the ENTER key scrolls down one line.

            LEFT ARROW

            Moves the cursor one character to the left. When you enter a command that extends beyond a single line, you can press the LEFT ARROW key repeatedly to scroll back toward the system prompt and verify the beginning of the command entry.

            RIGHT ARROW

            Moves the cursor one character to the right.

            UP ARROW or CTRL+P

            Recalls commands in the history buffer, beginning with the most recent command. Repeat the key sequence to recall successively older commands.

            DOWN ARROW or CTRL+N

            Returns to more recent commands in the history buffer after recalling commands with UP ARROW or CTRL+P. Repeat the key sequence to recall successively more recent commands.

            CTRL+A

            Moves the cursor to the beginning of the line.

            CTRL+B

            Moves the cursor back one character.

            CTRL+C

            Starts on a new command line.

            CTRL+D

            Deletes the character at the cursor.

            CTRL+E

            Moves the cursor to the end of the command line.

            CTRL+F

            Moves the cursor forward one character.

            CTRL+H

            Deletes the character in front of the cursor.

            CTRL+K

            Deletes all characters from the cursor to the end of the command line.

            CTRL+L

            Redisplays the system prompt and command line.

            CTRL+U

            Deletes all characters from the command line.

            CTRL+W

            Deletes the word to the left of the cursor.

            CTRL+Z

            Exits to Privileged Exec mode.

            6.14.2   Summary of Important Commands

            This section gives a summary of the most important commands in the different modes. Use the help utility to get all available options for each command.

            Table 11    Commands in Exec mode

            Command

            Parameter

            Description

            debug

            ospf

            Enables debugging of OSPF information. The following additional parameters are supported:

            route - OSPF route information

            packet - OSPF route information

            nfsm - Neighbor state machine

            lsa - Link state advertisement

            ifsm - Interface state machine

            event - OSPF event information

            enable

            -

            Enters Privileged Exec mode, see Table 12. Protected by a control_user password.

            exit

            -

            Terminates the current telnet session.

            logout

            -

            Terminates the current telnet session.

            ping

            -

            Used for testing a bi-directional IP connection.

            quit

            -

            Terminates the current telnet session.

            show

            -

            Displays information as described below.

            interface

            Displays the configuration and status of the interfaces (PPP and Ethernet)

            networks

            Lists all DCN networks with interface type, NE identification, interface name, bandwidth and status.

            history

            Displays CLI command history per command mode. The list is cleared after each telnet session. Use the UP ARROW/DOWN ARROW keys in order to access the command history buffer. Note: the telnet client must be configured for VT100 emulation for the arrow keys to work.

            ip

            The following additional parameters are supported:

            route - IP routing table

            protocols - Protocol process parameters and statistics

            ospf - OSPF information.

            forwarding - IP forwarding status

            traffic - IP statistics

            confirm timer

            Displays the remaining time until a configuration confirm must be done.

            telnet

            -

            To establish a telnet session onto a host.

            traceroute

            -

            Used to test IP connections with other NEs, listing routers visited on the way.


            Table 12    Commands in Privileged Exec mode

            Command

            Parameter

            Description

            configure

            -

            Enters global configuration mode, see Table 13.

            debug

            ospf

            Enables debugging of OSPF information. The following additional parameters are supported:

            route - OSPF route information

            packet - OSPF route information

            nfsm - Neighbor state machine

            lsa - Link state advertisement

            ifsm - Interface state machine

            event - OSPF event information

            disable

            -

            Returns to Exec mode, see Table 11.

            enable

            -

            No effect since already in Privileged Exec mode.

            exit

            -

            Terminates the current telnet session.

            logout

            -

            Terminates the current telnet session.

            no

            -

            Negates a configuration

            ping

            -

            Used for testing a bi-directional IP connection.

            quit

            -

            Terminates the current telnet session.

            show

            -

            Displays information as described below.

            interface

            Displays the configuration and status of the interfaces (PPP and Ethernet).

            networks

            Lists all DCN networks with interface type, NE identification, interface name, bandwidth and status.

            history

            Displays CLI command history per command mode. The list is cleared after each telnet session. Use the UP ARROW/DOWN ARROW keys in order to access the command history buffer. Note: the telnet client must be configured for VT100 emulation for the arrow keys to work.

            show

            ip

            The following additional parameters are supported:

            route - IP routing table

            protocols - Protocol process parameters and statistics

            ospf - OSPF information.

            forwarding - IP forwarding status

            traffic - IP statistics

            confirm timer

            Displays the remaining time until a configuration confirm must be done.

            telnet

            -

            To establish a telnet session onto another NE or get access to a local host shell.

            terminal

            ospf

            Enables OSPF debug printouts to the telnet console.

            no

            Negates a command or set its default.

            traceroute

            -

            Used to test IP connections with other NEs, listing routers visited on the way.

            write

            -

            Sends operator confirm for configuration of parameters that could cause loss of a DCN channel.

            Caution! If you do not save your configurations within 15 minutes, the NE will make a warm restart, restoring the saved configurations, and your unconfirmed changes will be lost. For more information, see Section 6.14.1.1.


            Table 13    Commands in Global Configuration mode

            Command

            Parameter

            Description

            debug

            ospf

            Enables debugging of OSPF information. The following additional parameters are supported:

            route - OSPF route information

            packet - OSPF route information

            nfsm - Neighbor state machine

            lsa - Link state advertisement

            ifsm - Interface state machine

            event - OSPF event information

            end

            -

            Exits to Privileged Exec mode.

            exit

            -

            Exits to Privileged Exec mode.

            ip

            -

            IP configuration as described below.

            route

            Sets up static IP routes, including the default gateway route.

            forwarding

            Turns on IP forwarding (default).

            name-server

            Configures one, two or three Domain Name Servers (DNS).

            This is normally done from the EEM.

            domainname

            Configures the name of the domain the NE belongs to. This is used for name resolution.

            This is normally done from the EEM.

            dhcp relayaddress

            Configures the IP address of the DHCP server the NE is a relay for.

            This is normally done from the EEM.

            no

            -

            Negates a configuration as described below.

            router

            Disables a routing protocol.

            interface

            Selects an interface to delete.

            ip

            Removes IP configuration.

            ntp

            server

            Defines the address of the NTP server.

            This is normally done from the EEM.

            router

            ospf

            Used to configure OSPF, see Table 15.

            For a summary of the most common OSPF related commands, see Section 6.14.3.2.


            Table 14    Commands in Interface Configuration mode

            Command in Global Configuration mode

            Command

            Description

            interface ethernet

            ip address

            Configures the IP address of the ethernet interface.

            This is normally done from the EEM.

            interface ospf <if>

            -

            Configures OSPF parameters for the selected interface as described below.

            For a summary of the most common commands, see Section 6.14.3.2 .

            description

            Interface specific description.

            end

            Exits to Privileged Exec mode, see Table 12.

            exit

            Exits to Global Configuration mode, see Table 13.

            ip

            Configuration of IP parameters.

            list

            Prints the command list.

            no

            Negates a command or sets its default value.

            ospf

            OSPF interface commands.

            quit

            Exits to Global Configuration mode, see Table 13.

            write

            Displays the OSPF running-config file.

            interface serial <if>

            -

            Specifies a particular serial interface as described below.

            trapenable

            Enables traps for the interface.

            shutdown

            Sets the administrative status to Down.

            exit

            Exits to Global Configuration mode, see Table 13.


            Table 15    Commands in Router Configuration mode

            Command

            Description

            area

            Sets OSPF area parameters.

            auto-cost

            Calculates OSPF interface cost according to bandwidth.

            compatible

            OSPF compatibility list.

            default-information

            Controls distribution of default information.

            default-metric

            Sets metric of redistributed routes.

            distance

            Defines an administrative distance.

            distribute-list

            Filters networks in routing updates.

            end

            Exits to Privileged Exec mode, see Table 12.

            exit

            Exits to Global Configuration mode, see Table 13.

            help

            Description of the interactive help system.

            list

            Prints the command list.

            neighbor

            Specifies neighbor router.

            network

            Enables routing on an IP network.

            no

            Negate a command or set its defaults

            opaque-lsa-capable

            Enables Opaque-LSA capability

            ospf

            OSPF specific commands.

            overflow

            Controls overflow.

            passive-interface

            Suppresses routing updates on an interface.

            quit

            Exits to Global Configuration mode, see Table 13.

            redistribute

            Redistributes information from another routing protocol.

            refresh

            Adjusts refresh parameters.

            router-id

            Sets the router ID for the OSPF process.

            summary-address

            Creates aggregate addresses.

            timers

            Adjusts routing timers.

            write

            Displays the OSPF running-config file.

            6.14.3   OSPF Configuration and Troubleshooting

            This section introduces how to use the CLI for OSPF configuration and troubleshooting.

            6.14.3.1   Defining an OSPF Area as a Stub Area

            If there is only one Area Border Router (ABR) within an area, it is recommended to define the area as a stub area, in all routers within the area, in order to reduce the size of the routing table. Using stub areas improves the performance of the OSPF routing by reducing the size of the link state database and the memory requirements of routers inside the areas.

            Creating a stub area can also be done from the EEM, see Section 6.11.5.

            The following example shows how to define an area (area ID=1.1.1.1) as a stub area.

            1. Log in in Exec mode.

              C:\>telnet 10.0.1.1

              Password:*****

            2. Enter Privileged Exec mode.

              TN-10-0-1-1>enable

              Password:******

            3. Enter Global Configuration mode.

              TN-10-0-1-1#configure

            4. Enter Router Configuration mode for OSPF.

              TN-10-0-1-1(config)#router ospf

            5. Define the area as a stub area.

              TN-10-0-1-1-ospf(config-router)#area 1.1.1.1 stub

              Note:  
              For an ABR it is possible to add the no-summary parameter in order to stop the ABR from sending summary link advertisements into the stub area. This will reduce the routing table even more.

            6. Exit Router Configuration mode.

              TN-10-0-1-1-ospf(config-router)#exit

            7. Exit Global Configuration mode.

              TN-10-0-1-1(config)#exit

            8. Save the configuration.

              TN-10-0-1-1#write

            6.14.3.2   OSPF Configuration Commands

            This section introduces the most common commands for OSPF configuration. Use the help utility to get all available parameter options for each command.

            Table 16    OSPF configuration commands

            Command

            Mode

            Description

            interface ospf <if>

            Example:

            interface ospf ppp0

            Global Configuration

            Enters Interface Configuration mode.

            router ospf

            Global Configuration

            Enters Router Configuration mode for OSPF.

            area stub

            Example:

            area 1.1.1.1 stub

            Router Configuration

            Defines an area as a stub area. All routers (including the ) in a stub area must be configured accordingly. See also Section 6.14.3.1.

            network

            Example:

            network 10.0.0.0/8 area 1.1.1.1

            Router Configuration

            Enables OSPF routing with a specified area ID on interfaces with IP addresses that match the specified network address.

            redistribute

            Example:

            redistribute connected

            Router Configuration

            To redistribute routes from other routing protocols, static routes and kernel routes into an OSPF routing table

            router-id

            Example:

            router-id 2.3.4.5

            Router Configuration

            To specify a router ID for the OSPF process.

            cost

            Example:

            ip ospf cost 10

            Interface Configuration

            Sets the interface cost.

            dead-interval

            Example:

            ip ospf dead-interval 60

            Interface Configuration

            Sets the dead-interval (default 40).

            hello-interval

            Example:

            ip ospf hello-interval 20

            Interface Configuration

            Sets the hello-interval (default 10).

            priority

            Example:

            ip ospf priority 3

            Interface Configuration

            Sets the router priority to determine the Designated Router (DR) for the network (default 1)

            6.14.3.3   OSPF Show Commands

            Table 17 lists the most common commands showing OSPF configuration. Use the help utility to get all available parameter options for each command.

            All commands are entered in Privileged Exec mode.

            Table 17    OSPF show commands

            Command

            Description

            show ip ospf database

            Displays a database summary for OSPF information.

            show ip ospf database network

            Displays information about the network LSAs.

            show ip ospf database router

            Displays information about the router LSAs.

            show ip ospf database summary

            Displays information about the summary LSAs.

            show ip ospf interface

            Displays interface information for OSPF.

            show ip ospf neighbor

            Displays information on OSPF neighbors.

            show ip ospf route

            Displays the OSPF routing table.

            show ip route

            Displays the complete routing table including OSPF (O) entries.

            6.14.4   Configuring Static Routing

            Using static routing means that a fixed routing scheme is entered manually from the CLI. Static routing can also be done from the EEM, see Section 6.11.3. A maximum of 100 static routes is possible.

            The following command is used from the CLI:

            ip route <destination> <gateway>

            The example below sets up a static route from an NE (IP address= 10.0.1.1) to IP address 10.0.3.0, subnet mask 24, through the gateway 10.0.2.1.

            1. Log in in Exec mode.

              C:\>telnet 10.0.1.1

              Password:******

            2. Enter Privileged Exec mode.

              TN-10-0-1-1>enable

              Password:******

            3. Enter Global Configuration mode.

              TN-10-0-1-1#configure

            4. Set up the static route.

              TN-10-0-1-1(config)#ip route 10.0.3.0/24 10.0.2.1

            5. Exit Global Configuration mode.

              TN-10-0-1-1(config)#exit

            6. Save the configuration.

              TN-10-0-1-1#write

            Although a default route is not required in OSPF networks it is recommended to configure a default gateway since it reduces the risk of loosing DCN contact with the NE. The example below defines a default gateway with IP address 10.0.2.1.

            1. Log in in Exec mode.

              C:\>telnet 10.0.1.1

              Password:******

            2. Enter Privileged Exec mode.

              TN-10-0-1-1>enable

              Password:******

            3. Enter Global Configuration mode.

              TN-10-0-1-1#configure

            4. Define the default gateway.

              TN-10-0-1-1(config)#ip route 0.0.0.0/0 10.0.2.1

            5. Exit Global Configuration mode.

              TN-10-0-1-1(config)#exit

            6. Save the configuration.

              TN-10-0-1-1#write

            6.15   Generating Configuration Reports

            Reports on the NEs hardware and software inventory, and the configuration settings can be generated, viewed, and saved.

            To generate a report:

            1. In the Navigation Tree, click the NE (the root).
            2. On the Tools menu, click Report to open the Report page.
            3. Select the items to include on the report. You can click Clear All and Select All to toggle all check boxes on and off.
            4. Click View Report to see the report in the LCT, or click Save Report to save the report as an HTML file on your computer. See Section 11.77 for information on what the report contains.

            7   Fault Management

            This section contains information and instructions for typical fault, status and test handling tasks.

            The following areas are covered:

            7.1   Operational Status

            This section describes the principles of the operational status of equipment and interfaces when working with the EEM.

            7.1.1   Operational Status of Equipment

            The operational status is a high-level status indication of a plug-unit or the NE. It is displayed as Status on an Alarms and Status page, see for example Section 11.124. An equipment failure initiates an update of the operational status. A more detailed equipment status is indicated by alarms, for example high temperature, see Section 7.2.5.

            The signification of the operational status of a unit is listed in Table 18.


            Table 18    Operational status of equipment

            Operational status

            NE

            Unit

            In Service

            The NE is operating properly.

            The unit is operating properly.

            Reduced Service

            The traffic functionality in the backplane is available but the management functionality or a redundant function is reduced or unavailable. A further reduction will have impact on traffic.

            The traffic functionality is available but the management functionality is reduced or unavailable.

            Out of Service

            The NE is not operating.

            The unit is not operating, that is a traffic disturbing failure has occurred. A plug-in unit is in a cold reset state where all traffic, control and management logics are reset.

            The relation between the operational status and alarm severity is listed in Table 19.

            Table 19    Relation between operational status and alarm severity

            Operational status

            Alarm severity

            In Service

            Clear/Warning

            Reduced Service

            Minor/Major

            Out of Service

            Critical

            7.1.2   Operational Status of Interfaces

            The possible operational status of an interface is listed in Table 20.

            Table 20    Operational status of an interface

            Operational status

            Description

            Up

            Payload is passing on the interface and one or several of the active lower layers have operational status Up.

            Down

            A defect is detected on the interface or administrative status is set to Down.

            Unknown

            The unit is in cold reset, warm reset or repair state.

            Testing

            The interface is in test mode, for example a loop is active or a BERT is running.

            Lower Layer Down

            The interface is Down due to lower layer interfaces. Payload is passing on the interface but not all active lower layers have operational status Up.

            7.2   Alarms and Events

            7.2.1   Alarm Notifications

            The sending of alarm notifications can be disabled on the following levels:

            Enabling of alarm notifications on any level means that new alarms are added to the Alarm List.

            Alarm notifications on all levels are enabled by default. However, to prevent too many alarms from not traffic routed DS1s, notifications are default disabled on these interfaces.

            7.2.2   Viewing Alarms

            The alarms and status information of the NE, a plug-in unit or an interface is displayed on a specific Alarms and Status page, see for example Section 11.100.

            To access an Alarms and Status page:

            1. In the Navigation Tree, click the entity for which you want to view the alarms and status.
            2. On the Fault menu, click Alarms and Status.

            The alarms and status for DCN and Ethernet Bridge are accessed on the Fault menu by selecting the NE in the Navigation Tree.

            The alarms and status of Radio Terminals with MMU2 BA/CA are displayed on the Radio Terminal Alarms and Status page, see Section 11.126.

            An Alarm List page displaying all active alarms is available on NE, unit and interface level, see Section 11.143. The Alarm List is cleared after a restart (cold or warm) of the NPU or NE.


            To display the Alarm List:

            1. In the Navigation Tree, click the entity for which you want to display the Alarm List.
            2. On the Fault menu, click Alarm List.

            7.2.3   Viewing Logged Alarms and Events

            The NE keeps a log of the 400 latest alarms and events, which can be accessed from the Event Log page, see Section 11.144. The Event Log is cleared after a restart of the NPU or NE.

            To display the Event Log:

            1. In the Navigation Tree, click the NE.
            2. On the Fault menu, click Event Log.

            7.2.4   Severity

            Table 21 explains the signification of the alarm and event severities.

            Table 21    Explanations of alarm and event severities

            Color

            Severity

            Description

            Green

            Cleared

            Indicates the clearing of one or more previously reported alarms.

            Bluish-green

            Indeterminate

            Indicates that the severity level cannot be determined. This severity is not used on NE level.

            Blue

            Warning

            Indicates the detection of a potential or impending service affecting fault, before any significant effects are known. An action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming more serious service affecting. Can also be used for events.

            Yellow

            Minor

            Indicates the existence of a non-service affecting fault condition and that a corrective action should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity can be reported, for example when the detected alarm condition is not currently degrading the capacity of the managed object. This severity is used for example in case of high temperature on a unit.

            Orange

            Major

            Indicates that a service affecting condition has developed and an urgent corrective action is required. Such a severity can be reported, for example when there is a severe degradation in the capability of a unit or interface and its full capability must be restored, like in case of SES or high temperature on a unit.

            Red

            Critical

            Indicates that a service affecting condition has occurred and an immediate corrective action is required. Such a severity can be reported, for example when a unit or interface is totally Out of Service and its capability must be restored, like in case of a LOS.


            7.2.5   Lists of Alarms and Events

            This section gives a summary of:

            Table 22    List of alarms

            Entity

            Specific Problem

            Description

            Severity

            NE

            Power Failure

            A malfunction in the redundant PFU.

            Major

            Low Input Voltage

            The input voltage is low. If it drops further, one or more plug-in units may stop working.

            Major

            Node Installation

            The NE is in Node Installation mode. Enter the URL http://10.0.0.1/ to reach the installation wizard.

            Minor

            NPU Installation

            The NE is in NPU Installation mode. Enter the URL http://10.0.0.1/ to reach the installation wizard.

            Major

            Traffic System Failure

            A malfunction related to traffic. At least one bus in the backplane fails.

            Major: One bus fails.

            Critical: Two or three TDM busses fail.

            Control System Failure

            A malfunction related to management. The NPU or the control bus fails. Load the Error Log. A software upgrade is probably required.

            Major

            Node Fault Mode

            The self-repair mechanism has failed and the NE is in a fault mode(1). A replacement of the NPU is probably required.

            Critical

            OSPF LSA Database Overload

            The OSPF routing database is full due to too many routers in the network.

            Minor

            FAL <number> license missing

            A license for an optional feature with the specified product number is missing.

            Major: An optional feature is used without a license

            Critical: An optional feature is locked due to a missing license

            Not able to find RMM

            The RMM is missing or it has failed.

            Major: The first 30 days

            Critical: After 30 days

            Plug-in Unit

            Unit Removed

            The unit is removed.

            Critical

             

            High Temperature

            The unit has reached an abnormal temperature.

            Minor

            Excessive Temperature

            The unit has reached an excessive temperature.

            Critical

            Wrong Software

            A wrong load module release is running on the unit.

            Critical

            Plug-in Unit

            Hardware Error

            A malfunction related to hardware.

            Minor: Control system failure.

            Critical: Traffic or power system failure.

            Wrong NPU software

            The unit needs a later NPU software release

            Critical

            Unsupported Unit Type

            Unit type not supported by SW.

            Critical

            Wrong Position

            The unit is in the wrong position in the AMM.

            Critical

            Insufficient Resources

            The NE does not have the resources to handle this plug-in unit.

            Critical

            Missing License

            When this plug-in unit was inserted, the total number of plug-in units in the AMM became more than 10, but no license for the optional feature AMM 20p Slot Extension was available. Only applicable for AMM 20p.

            Critical

            Reserved Position

            The plug-in unit in this position is of a different type than what the position is reserved for.

            Critical

            FAU

            Hardware Error

            A malfunction related to hardware.

            Critical

            MMU2 BA/CA(2)

            RCC Unavailable

            Communication is lost on the Radio Communication Channel, between the MMU and the RAU.

            Major

            ICC Unavailable

            Communication is lost on the Internal Communication Channel, between two MMUs

            Major

            HCC Unavailable

            Communication is lost on the Hop Communication Channel, between the near-end MMU and the far-end MMU.

            Major

            ATPC Capability (Far-end)

            The terminal on the far end is configured for ATPC but at least one of the indoor units does not support ATPC.

            Major

            RAU IF (on MMU2 BA/CA)

            Dmod Clock

            The internal data rate of the MMU does not correspond to the received data rate. This fault will cause bit slip in the composite bit stream.

            Critical: Active transmitter.

            Major: Standby transmitter.

            LOS

            Input traffic failure in the transmitting direction.

            Critical: Active transmitter.

            Major: Standby transmitter.

            Rx IF Input

            Failure on the receiver IF signal from the RAU to the MMU.

            Major

            Tx IF Input

            Failure on the received IF signal from the MMU to the RAU.

            Critical: Active transmitter.

            Major: Standby transmitter.

            Radio Frame

            The receiver failed to synchronize the frame of the received composite bit stream due to signal failure.

            Critical: Active transmitter.

            Major: Standby transmitter.

            RAU IF (on MMU2 BA/CA)

            BER

            The Bit Error Rate for the received signal has exceeded the BER alarm threshold.

            Critical: Active transmitter.

            Major: Standby transmitter.

            Radio ID

            The received traffic comes from a terminal with an ID not matching the far-end ID.

            Critical: Active transmitter.

            Major: Standby transmitter.

            Mod Index

            The modulation index of the MMU, controlled by the far end MMU, is out of the allowed range. Only valid for C-QPSK modulation.

            Major

            AIS Received

            AIS detected on the received traffic signal. Only available for a far-end terminal with MMU2 or a far-end MINI-LINK E terminal.

            Critical: Active transmitter.

            Major: Standby transmitter.

            Unknown

            The status of the interface is unknown, for example due to loss of communication.

            Major

            Rx Loop(3)

            Indicates that an Rx Loop is set.

            Warning

            IF Loop (3)

            Indicates that an IF Loop is set.

            Warning

            SWITCH (MMU2 BA/CA)

            Unable To Protect

            The protection failed.

            Major: A Tx or a common Tx/Rx alarm on one path. Also for an Rx alarm on one path and the duration is longer than 200 s.

            Critical:f alarms on both paths.

            Hitless Phase

            Failure of synchronizing the received traffic in the two MMUs with a duration longer than 200 s.

            Major

            Tx Switch Over

            A TDM Tx switch or an active RAU transmitter switch. Only 1+1 Hot Standby.

            Major

            Remote Tx Switch Over

            An active RAU transmitter switch ordered from the far-end. Only 1+1 Hot Standby.

            Major

            RF Input Threshold Protection

            The RF input level of both receivers in a protected terminal has dropped below their respective RF Input Alarm Threshold.

            Warning

            RAU (connected to MMU2 BA/CA)

            ATPC Capability

            The terminal is configured for ATPC, but the RAU does not support ATPC. This alarm is activated only if ATPC is turned on (any direction).

            Major

            Unit Removed

            The RAU is disconnected from the MMU.

            Critical

            Hardware Error

            A malfunction related to hardware.

            Minor: Control system failure.

            Critical: Traffic or power system failure.

            Incompatible Units

            The wrong type of RAU is used.

            Critical

            Unknown

            The status of the unit is unknown, for example due to loss of communication.

            Major

            RF (on RAU connected to MMU2 BA/CA)

            Tx Frequency

            The transmitter frequency synthesizer loop is unlocked.

            Minor: Control system failure.

            Critical: Traffic or power system failure.

            Rx Frequency

            The receiver frequency synthesizer loop is unlocked.

            Minor: Control system failure.

            Critical: Traffic or power system failure.

            RF Output Level

            A major degradation of the transmitter output power is detected.

            Major

            Rx AFC

            The frequency of the received signal is outside the range of the Automatic Frequency Control in the RAU receiver.

            Major

            RF Input Level

            The received RF input signal level has dropped below the threshold for the receiver.

            Minor: Control system failure.

            Critical: Traffic or power system failure.

            RF Input Threshold

            The RF input level has dropped below the specified threshold value in dBm for the input power.

            Warning

            RF Loop (3)

            Indicates that an RF Loop is set.

            Warning

            Tx Off (3)

            Indicates that the transmitter is off.

            Warning

            DS1

            LOS

            Loss Of Signal is detected on the incoming traffic.

            Critical

            LOF

            Loss of Frame

            Critical

            LOMF

            Loss of MultiFrame

            Critical

            RAI

            Remote Alarm Indication

            Minor

            AIS

            An Alarm Indication Signal is detected on the incoming traffic.

            Minor

            Unavailable State

            Unavailable State is activated after 10 consecutive SES. 10 consecutive non-SES will cease the alarm.

            Critical

            LOCD

            Loss of cell delineation

            Ciritical

            1+1 DS1 SNCP

            Unable To Protect

            The protection has failed.

            Minor: The redundant interface fails.

            Critical: Both interfaces fail or the traffic is locked to a failing interface.

            MUX12/MUX23

            LOS

            Loss Of Signal is detected on the incoming traffic.

            Critical

            AIS

            An Alarm Indication Signal is detected on the incoming traffic.

            Minor: MMU2 B/C

            Critical: MMU2/SMU2

            Equipment OoS

            Equipment Out of Service.

            Critical

            LOF(4)

            Loss Of Frame alignment.

            Critical

            RAI (4)

            Remote Alarm Indication

            Critical

            OC-3/STS-3 port

            Clock Loss of Reference

            Loss of clock reference.

            Minor

            Line/Section

            LOS

            Loss Of Signal.

            Critical

            LOF

            Loss Of Frame Alignment.

            Critical

            TIM

            Trace Identifier Mismatch

            Critical

            AIS

            Alarm Indication Signal

            Minor

            RDI

            Remote Defect Indication

            Minor

            DEG

            Degraded Signal

            Critical

            Unavailable State

            Unavailable State is activated after 10 consecutive SES. 10 consecutive non-SES will cease the alarm.

            Critical

            APS

            Unable To Protect

            The protection has failed.

            Minor: The redundant interface fails.

            Critical: Both interfaces fail or the traffic is locked to a failing interface.

            Mode Mismatch

            MSP mode mismatch. Far End configured as MSP 1:n

            Minor

            Unavailable State

            Unavailable State is activated after 10 consecutive SES. 10 consecutive non-SES will cease the alarm.

            Critical

            STS-1

            LOP

            Loss Of Pointer

            Critical

            AIS

            Alarm Indication Signal

            Minor

            RDI

            Remote Defect Indication

            Minor

            Unequipped

            The interface has no content since the unit is not configured

            Critical

            PLM

            Payload Mismatch

            Critical

            TIM

            Trace Identifier Mismatch

            Critical

            DEG

            Degraded Signal

            Major

            LOM/TULOM

            Loss Of Multiframe/Tributary Unit Loss Of Multiframe

            Critical

            Unavailable State

            Unavailable State is activated after 10 consecutive SES. 10 consecutive non-SES will cease the alarm.

            Critical

            VT1.5

            LOP

            Loss Of Pointer

            Critical

            AIS

            Alarm Indication Signal

            Minor

            RDI

            Remote Defect Indication

            Minor

            Unequipped

            The interface has no content since the unit is not configured

            Critical

            PLM

            Payload Mismatch

            Critical

            TIM

            Trace Identifier Mismatch

            Critical

            DEG

            Degraded Signal

            Major

            Unavailable State

            Unavailable State is activated after 10 consecutive SES. 10 consecutive non-SES will cease the alarm.

            Critical

            User Input

            User Defined

            The Specific Problem and Severity is defined on the User Input Configuration page.

            User Defined

            PPP

            PPP Down

            Failure in the DCN communication.

            Minor

            OSPF

            OSPF LSA database overload

            The OSPF routing database is full.

            Major

            HDLC

            Down/No Traffic

            No throughput on the interface. All IM interfaces are Down.

            Critical

            Degraded Service

            One or several (but not all) IM interfaces are Down, leading to decreased speed on the bridge connection.

            Major

            LAN

            Ethernet down

            The interface is down.

            Minor: Site LAN

            Critical: Ethernet Bridge

            Bridge

            Ethernet down

            The interface is down.

            Critical

            IM Group

            Lower Layer Down

            No Traffic

            No throughput on the interface. All IM interfaces are down.

            Critical

            Degraded Service

            One or several (but not all) IM interfaces are down, leading to decreased speed on the bridge connection.

            Major

            Degraded Service: Quality of Service

            The defined threshold for discarded frames on the IM group layer is exceeded.

            Major

            Loss of keep alive

            Keep Alive

            Loss of keep-alive frames is detected.

            Critical

            (1)  Software Upgrade cannot be performed when the NE is in fault mode.

            (2)  Radio Terminal specific alarms. See also general alarms under Plug-in Unit.

            (3)  No notification is sent.

            (4)  MMU2 BA/CA only.

            Note:  
            In addition to the alarms listed above, the Alarm List will also display a few alarms related to Radio Terminal units and interfaces. These alarms are, for terminals with MMU2, presented, described and handled in MSM.


            Table 23    List of events

            Entity

            Specific Problem

            Description

            Severity

            NE

            Cold Restart

            A restart of the control and management system as well as the traffic system. This type of restart will disturb all traffic.

            Warning

            Warm Restart

            A restart of the control and management system. Traffic is not disturbed by this type of restart.

            Warning

            Notification Enable

            Sent to all subscribers indicating that notifications are enabled.

            Warning

            Notification Disable

            Sent to all subscribers indicating that notifications are disabled.

            Warning

            FTP Connection Error

            An error in the communication with the FTP server has occurred.

            Minor

            Load Module Error

            Load module is corrupt or program error during software upgrade.

            Minor

            Software Upgrade Started

            A software upgrade procedure is started.

            Warning

            Software Upgrade Finished

            A software upgrade procedure is finished.

            Warning

            Software Running

            The new software is accepted and running.

            Warning

            Management Software Fallback

            NPU emergency fallback to the previous NPU software release.

            Warning

            Software Upgrade Failed

            Software upgrade failed.

            Warning

            Software Upgrade Canceled

            The software upgrade is canceled.

            Warning

            Plug-in Unit

            Unit Inserted

            A unit is inserted.

            Warning

            Unit Removed

            A unit is removed.

            Warning

            Software not Conform to Baseline

            Version control is enabled but upgrade/downgrade preferences do not allow DP software to be upgraded/downgraded to the revision corresponding to the SBL.

            Warning

            Load Module not Part of Baseline

            The load module that is required for the unit is not part of the SBL.

            Warning

            Minimum Software Revision

            An attempt to downgrade the unit to under its minimum software revision was made.

            Warning

            Load Module Programming Failure

            Software upgrade of this unit failed due to a programming failure (FLASH memory).

            Warning

            Reservation Cleared

            A reservation for a specific unit type in a specific position in the AMM was cleared.

            Warning

            1+1 DS1 SNCP

            Protection Switch

            A protection switch has occurred.

            Warning

            APS

            Protection Switch Reject

            A requested protection switch has been rejected.

            Warning

            Protection Switch Event

            A protection switch has occurred.

            Warning

            SWITCH

            (MMU2 BA/CA)

            Protection Switch

            A protection switch has occurred.

            Warning

            MMU2 BA/CA and corresponding RAU

            Spontaneous Restart

            The processor in the RAU has restarted.

            Warning

            Hot Swap Incomplete

            A hot swap was made, but the configuration of the new unit is incomplete. This happens when the new unit does not support all configuration options of the old unit.

            Warning

            7.3   Viewing the DCN Status

            There are several pages displaying the status of the DCN, in terms of parameters for interfaces and IP routing.

            To view the DCN status:

            1. In the Navigation Tree, click the NE.
            2. On the Fault menu, click DCN.
            3. The DCN parameters are grouped in different categories. Click a link to display a specific category.

            7.4   Loops

            Loops can be used to verify that the transmission system is working properly or they can be used to locate the faulty unit or interface in case of failure.

            7.4.1   General

            The following loops are supported:

            Connection Loop   Loops an DS1 interface connected to the backplane back to its origin. The loop is done in the backplane. If the interface is traffic routed an AIS is transmitted to the other interface in the traffic routing.
            Line Loop   Loops an incoming line signal (Line/Section, MUX23, MUX12 and DS1) back to its origin. The loop is done in the plug-in unit, close to the line interface. An AIS is sent to the backplane.
            Local Loop   Loops a line signal (Line/Section, MUX23, MUX12 and DS1) received from the backplane back to its origin. The loop is done in the plug-in unit. An AIS is transmitted to the line interface.

            Figure 30   Loops

            The following loops are supported for the Radio Terminal:

            Note:  
            Loops for Radio Terminals with MMU2 are mainly set using MSM.

            IF Loop   In the MMU the traffic signal to be transmitted is, after being modulated, mixed with the frequency of a local oscillator and looped back for demodulation (on the receiving side).
            RF Loop   In the RAU a fraction of the RF signal transmitted is shifted in frequency and looped back to the receiving side.
            Rx Loop   This loop is similar to the Connection Loop but the loop is done in the plug-in unit close to the TDM bus, where a group ofDS1s in the traffic connection is looped back to its origin. The Rx Loop can be used to verify the communication over the radio path.
            Note:  
            If the far-end terminal is based on MMU2 BA/CA, the Rx Loop on that side can be set from the near-end EEM, see Section 7.4.3.

            Figure 31   MMU2 BA/CA Loop

            Figure 32   Radio Terminal loops

            Section 7.4.2 and Section 11.148 give more information on how to set loops.

            7.4.2   Setting a Loop on an Interface

            This procedure describes how to set a loop on an interface in order to locate a fault.


            Caution!  
            If the interface is used, the loop will disturb the traffic.
            Note:  
            An active loop will disable notifications from the interface.

            To set a loop:

            1. In the Navigation Tree, click the unit that contains the interface on which you want to set a loop.
              Note:  
              A loop can also be set when the interface is selected in the Navigation Tree.

            2. On the Tools menu, click Loops.
            3. On the Loops page, in the <IF type> Interface list, select the interface on which you want to set a loop.
            4. In the Loop options list, select loop type. See Table 24 for a description of the loop types available for a specific interface.
            5. Click Add. The loop is added to the Active loops list. The loop is removed by clicking Remove or Remove All.
            Note:  
            It is also possible to handle loops from the Activities page, see Section 11.146.

            7.4.3   Setting a Loop on the Far-End Radio Terminal

            This procedure describes how to set a loop on the RAU IF on a far-end radio terminal in order to locate a fault.


            Caution!  
            If the interface is used, the loop will disturb the traffic.
            Note:  
            An active loop will disable notifications from the interface.

            To set an Rx Loop on a far-end radio terminal:

            1. In the Navigation Tree, click an MMU2 BA/CA or RAU IF for the near-end terminal.
            2. On the Tools menu, click Loops.
            3. On the Loops page, click Show Far End to see the loop options for the far-end terminal. If the far-end terminal is protected (1+1) there are two links, one for each RAU IF.
            4. Under Far End, in the Loop options list, click Add to activate the Rx Loop. The loop is added to the Active loops list. The loop is removed by clicking Remove or Remove All.

            7.5   Error Log Handling

            The NE holds an Error Log containing information about internal hardware and software errors as well as restarts and equipment alarms. The Error Log comprises two files, <hostname>_active.elog and <hostname>_passive.elog.

            Note:  
            Evaluation of the Error Log requires deep knowledge about the system. Contact your Ericsson support for more information.

            The following tasks are covered:

            7.5.1   Uploading the Error Log to the FTP Server

            Uploading the Error Log will load the <hostname>_active.elog and <hostname>_passive.elog files to the FTP server.

            To upload the Error Log:

            1. The Error Log will be uploaded to the <drive:>\tn_ftp_home\tn_error_log folder. To avoid overwriting an existing Error Log from the same NE, add the extension .old to the existing files, for example <hostname>_active.elog.old.
            2. In the Navigation Tree, click the NE.
            3. On the Fault menu, click Load Error Log.
            4. Under Error Log File, select Upload to FTP server.
            5. Under FTP, do one of the following:
            6. Click Apply.

            7.5.2   Deleting the Error Log from the NE

            Deleting the Error Log will delete the <hostname>_active.elog file from the NE.

            To delete the Error Log:

            1. In the Navigation Tree, click the NE.
            2. On the Fault menu, click Load Error Log.
            3. Under Error Log File, select Delete error log from Network Element.
            4. Click Apply.

            8   Performance Management

            This section contains instructions for typical performance management tasks.

            The following tasks are covered:

            8.1   Specifying the PM Start Time

            This procedure describes how to specify the PM Start Time for 24 hours performance data error counting interval.

            To specify the PM start time:

            1. In the Navigation Tree, click the NE.
            2. On the Configuration menu, click the Basic NE menu.
            3. On the Basic NE Configuration page, under General Settings, type the PM Start Time (hh:mm where mm is 00, 15, 30 or 45).
            4. Click Apply.

            8.2   Viewing Performance Data

            To be able to view performance data for interfaces, PM view must be enabled.

            Note:  
            Performance data (RF power) for the RF interface is always available, that is, you do not need to enable PM view.

            To enable PM view:

            1. In the Navigation Tree, click the interface for which you want to display performance data.
            2. On the Configuration menu, click Configuration.
            3. On the Configuration page for the interface, make sure Enable PM View is selected.
            4. Click Apply.

            Viewing Performance Data

            To view performance data:

            1. In the Navigation Tree, click the interface for which you want to display performance data.
            2. Click the Performance menu.
            3. The Performance Data page for the selected interface is displayed.

            8.3   Running a BERT on an DS1 Interface

            This procedure describes how to run a Bit Error Ratio Test (BERT) on a DS1 interface for performance measurement. The interface can be selected from the NE or any unit holding a DS1 interface. A Pseudo Random Bit Sequence (PRBS) with test pattern 215 - 1 is sent on the selected interface.

            Figure 33   Bit Error Ratio Test (BERT)

            Several BERTs can be executed concurrently with the following limitations:


            Caution!  
            If the interface is used, the BERT will disturb the traffic.

            To start a BERT:

            1. In the Navigation Tree, click the unit that holds the DS1 interface you want to test. Alternatively, click the NE name.
            2. On the Tools menu, click Test.
            3. On the Test page, under Bit Error Ratio Test - BERT, select the interface on which you want to run a BERT.
            4. Click Start Test. The interface is added to the Running Tests list, indicating that the BERT is running on the interface.

            To stop a BERT:

            1. On the Test page, in the Running Tests list, locate the interface and then click Stop Test. The interface is removed from the Running Tests list and inserted in the Previous Test Results list, where the BER result and the elapsed time for the test is displayed.
            Note:  
            It is also possible to handle BERTs from the Activities page, see Section 11.146.

            9   Security Management

            This section covers the following:

            9.1   User Names

            Two user names are supported.

            Figure 34   Logging in to the EEM

            view_user

            This user can only see the configuration. The default password is ericsson.

            To prevent unauthorized access to the system it is recommended to change the password. This should be done during the initial setup, see Section 5.3. However, the default password can always be used for local access of NPU2 A/NPU1 BA.

            control_user

            This user can view and change the configuration. The default password is ericsson.

            To prevent unauthorized access to the system it is recommended to change the password. This should be done during the initial setup, see Section 5.3. However, the default password can always be used for local access of NPU2 A/NPU1 BA and NPU1 ANSI in Node/NPU Installation mode.

            The control_user can change the passwords, see Section 9.2.

            9.2   Changing Passwords

            This procedure describes how to change the control_user and view_user passwords when the NE is in Normal mode.

            Note:  
            Only the control_user is authorized to change the passwords.

            To change the passwords:

            1. In the Navigation Tree, click the NE.
            2. On the Security menu, click Security
            3. On the Security page there are two passwords to change:
            4. Click Apply.
            Note:  
            You have to log in again if you have changed the control_user password.

            9.3   Replacing Lost Passwords

            Note:  
            This section applies only to NPU1 ANSI. For an NPU2 A/NPU1 BA, the control_user can always access the NE locally using the default password and change the passwords from the Security page, see Section 11.162.

            This procedure describes how to set new passwords in case the existing passwords have been lost.


            Caution!  
            Use this function restrictively and only when you have lost the passwords to an already installed NE.
            Note:  
            The NE is accessed in Node Installation mode. Configure the PC to use a dynamic IP address obtained from the DHCP server in the NE or alternatively use the static IP address 10.0.0.2. For more information on IP addressing, see Section 3.3.3.

            To set new passwords:

            1. Switch off and switch on the power supply.

            Figure 35   Entering Node Installation mode

            1. While the Fault (red), Power (green) and BR (yellow) LEDs on the NPU1 ANSI are ON (NE power up), press the BR button gently and release it. The BR (yellow) LED will start flashing, indicating that the NE is in Node Installation mode.
            2. Connect the Ethernet cable (twisted pair) to the 10/100BASE-T port.
            3. Start a Web browser and enter the URL http://10.0.0.1/.
            4. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
            5. On the Tools menu, click Change Password.
            6. On the Change Password page, click Configure Basic Security.
            7. On the Security page, there are two passwords to set:
            8. Click Apply and then click Next.
            9. On the Change Password page, click Finish Installation.
            10. On the Finish Installation page, click Apply.
            11. When the Installation Finished page is displayed the NE will make a warm restart and run in Normal mode.
            12. Make sure the PC is properly configured regarding the use of DHCP server. The configuration defines if dynamic or static IP addressing is used. For information on how to configure the use of DHCP server, see Section 3.3.3.
            13. Find out the IP address of the NE, typically from the site documentation or the information plate of the NE. Start a Web browser and enter the URL http://<IP address>.
            Note:  
            Installation mode can always be left by pressing the BR button on the front of the NPU1 ANSI.

            10   Hardware Maintenance

            This section describes hardware maintenance procedures.

            Note:  
            Follow the recommendations in MINI-LINK TN ANSI Indoor Installation Manual on troubleshooting and how to handle cables and plug-in units.

            The following tasks are covered:

            10.1   Adding and Removing Plug-in Units

            10.1.1   Position States

            Each position in the AMM has a state, indicating whether a plug-in unit is inserted in that position, and if there are any problems associated with that plug-in unit in that position.

            If there is a problem, this is shown on the NE Alarms and Status page as an icon on that position. The position state icon looks like this: . If you place the pointer on the icon, a ToolTip of the problem is shown.

            A position may be in one of the following states:

            Valid Unit   There are no problems with a plug-in unit of this type in this position.

            Since there are no problems, no icon is shown.

            Free   There is no plug-in unit in this position and the position is not reserved.

            Since there are no problems, no icon is shown.

            Inaccessible Unit   The plug-in unit has been removed from this position and the position is reserved for plug-in units of the same type.

            Whenever you remove a plug-in unit from the AMM, the position where it was inserted remains reserved for plug-in units of the same type. The configuration of the removed unit is saved in the NE, so that when you insert a compatible replacement unit, it will automatically get the configuration of the old unit.

            If you are not going to insert a replacement plug-in unit in this position, you can clear the reservation, see Section 10.1.4. This will make the position Free.

            Clicking the icon, opens the Clear Reservation page, see Section 11.99.

            Wrong Unit   The plug-in unit in this position cannot use the configuration that is saved for this position.

            To use a plug-in unit of a different type, you need to clear the reservation, see Section 10.1.3. After clearing the reservation, the position will be put in status Valid Unit if there are no problems with having the plug-in unit in this position.

            Clicking the icon, opens the Clear Reservation page, see Section 11.99.

            Missing License   When this plug-in unit was inserted, the total number of plug-in units in the AMM became more than 10, but no license for the optional feature AMM 20p Slot Extension was available. Only applicable for AMM 20p.

            The icon is shown on the position.

            A license for AMM 20p Slot Extension allows you to use all positions in the AMM.

            Wrong Position   The plug-in unit is not allowed in this position.

            The icon is shown on the position.

            Follow the rules and recommendations in the MINI-LINK TN ANSI Indoor Installation Manual.

            Insufficient Resources   The NE does not have the resources to handle this plug-in unit.

            The icon is shown on the position.

            For example, the backplane can only handle traffic from eight LTU 155 units.

            Unsupported Unit   The plug-in unit is of a type that is not recognized by the NE.

            The icon is shown on the position.

            For example, this can happen if you insert a plug-in unit that was released after the release of the software baseline running on the NE. Make sure you are using the latest system software.

            10.1.2   Adding Plug-in Units in Free Positions


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.

            This procedure describes how to insert a plug-in unit in a Free position, that is, the position is not reserved for any type of plug-in unit.

            To add a new plug-in unit to a Free position:

            1. Remove the dummy unit.
            2. Insert the new plug-in unit and fit the cables as described in MINI-LINK TN ANSI Indoor Installation Manual.
              Note:  
              Make sure the software baseline supports the new plug-in unit before inserting it. Perform a software upgrade if necessary, see Section 6.13.1.

            3. In the Navigation Tree, click the NE.
            4. On the Fault menu, click Alarms and Status and make sure that the icon is not shown.
            5. Configure the plug-in unit and its interfaces, see Section 6.
            6. On the applicable Alarms and Status page, make sure there are no active alarms.

            10.1.3   Adding Plug-in Units in Reserved Positions


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.

            This procedure describes how to insert a plug-in unit in a position that is reserved for a different type of plug-in unit.

            Note:  
            To replace a plug-in unit with a plug-in unit of the same type, see the specific procedures for replacing plug-in units in Section 10.

            To add a new plug-in unit in a reserved position:

            1. Insert the new plug-in unit and fit the cables as described in MINI-LINK TN ANSI Indoor Installation Manual.
              Note:  
              Make sure the software baseline supports the new plug-in unit before inserting it. Perform a software upgrade if necessary, see Section 6.13.1.

            2. In the Navigation Tree, click the NE.
            3. On the Tools menu, click Clear Reservation.
            4. Select the Clear check box for the position with state Wrong Unit.
            5. Click Apply.
            6. On the Fault menu, click Alarms and Status and make sure that the icon is not shown.
            7. Configure the plug-in unit and its interfaces, see Section 6.
            8. On the applicable Alarms and Status page, make sure there are no active alarms.

            10.1.4   Removing Plug-in Units


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.

            This procedure describes how to remove a plug-in unit from an AMM when that position should be left Free.

            1. Disconnect all cables from the plug-in unit.
            2. Undo the two screws on the latches.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 36   Pressing the BR button

            1. Disconnect all cables from the plug-in unit.
            2. Undo the two screws on the latches.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            4. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            5. Insert a dummy unit in the empty position. All free positions must be covered by dummy units to comply with EMC and cooling specifications.
            6. Tighten the two screws on the latches of the dummy unit.
            7. In the Navigation Tree, click the NE.
            8. On the Tools menu, click Clear Reservation.
            9. Select the Clear check box for the position with state Inaccessible Unit.
            10. Click Apply.
            11. On the Fault menu, click Alarms and Status and make sure that the icon is not shown.

            10.2   Replacing an LTU 16xDS1, LTU 16/1, LTU 12xDS1, LTU 155 ANSI, ETU2, SMU2 ANSI (co-siting)

            This procedure describes how to replace an LTU 16xDS1, LTU 12xDS1, LTU 155 ANSI, ETU2, SMU2 ANSI (co-siting).


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.
            Note:  
            When replacing an LTU 155 ANSI there is a check that the SW load module matches the current software release. If required, an automatic download of a new load module takes place. This requires a working connection to the FTP server and that the load module is present in the <drive:>\tn_ftp_home\tn_system_release folder.

            Note:  
            If an SMU2 ANSI has been used for protection it is recommended to do a preset to factory settings before using it for co-siting. For more information on how to do a preset, see MSM User Guide or MSM online Help.

            To replace the plug-in unit:

            1. Disconnect all cables from the plug-in unit.
            2. Undo the two screws on the latches.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 37   Pressing the BR button

            1. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            2. Insert the new plug-in unit. The plug-in unit will automatically be taken into service with the configuration used by the previous plug-in unit.

              Caution!  
              Be careful when inserting the LTU 12xDS1 as bending the unit, or placing it outside the guides, could cause short-circuits or damages.
            3. Tighten the two screws on the latches.
            4. Connect all cables to the plug-in unit.
            5. Start the LCT. For more information, see Section 3.3.
            6. In the Navigation Tree, click the plug-in unit type being replaced.
            7. On the Alarms and Status page, make sure there are no active alarms.

            10.3   Replacing an MMU2 or SMU2 ANSI (protection)

            This procedure describes how to replace an MMU2, or an SMU2 used for protection in a (1+1) Radio Terminal.


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.
            Note:  
            To avoid transmission using the wrong frequency or output power it is recommended to insert an MMU2 with factory settings. If a preset to factory settings is required, use MSM with the unit inserted in an empty position in the AMM. MSM is launched from the MMU2 Configuration page, see Section 11.35.

            To replace the plug-in unit:

            1. MMU2 only: Disconnect the station radio cable.
            2. Undo the two screws on the latches.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 38   Pressing the BR button

            1. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            2. Insert the new plug-in unit. The plug-in unit will automatically be taken into service.
            3. Tighten the two screws on the latches.
            4. Connect the station radio cable.
            5. Start the LCT. For more information, see Section 3.3.
            6. In the Navigation Tree, click the plug-in unit type being replaced.
            7. On the Configuration menu, click Configuration.
            8. On the Configuration page, click Perform AM Setup and Hop Setup.
            9. In MSM perform a complete AM Setup and Hop Setup. Follow the instructions in MSM User Guide or MSM online Help.
            10. In the Navigation Tree, click the plug-in unit being replaced.
            11. On the Alarms and Status page, make sure there are no active alarms.

            10.4   Replacing an MMU2 BA/CA

            This procedure describes how to replace an MMU2 BA or MMU2 CA.


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.
            Note:  
            To avoid transmission using the wrong frequency or output power it is recommended to insert an MMU2 BA/CA with factory settings.

            Note:  
            When replacing an MMU2 BA or MMU2 CA there is a check that the SW load module matches the current software baseline. If required, an automatic software upgrade takes place. This requires a working connection to the FTP server and that the load module is present in the <drive:>\tn_ftp_home\tn_system_release folder.

            To replace the plug-in unit:

            1. Disconnect the station radio cable.
            2. Undo the two screws on the latches.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 39   Pressing the BR button

            1. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            2. Insert the new plug-in unit. The plug-in unit will automatically be taken into service.
            3. Tighten the two screws on the latches.
            4. Connect the station radio cable.
            5. Start the LCT. For more information, see Section 3.3.
            6. Do one of the following:
            7. In the Navigation Tree, click the MMU being replaced.
            8. On the Alarms and Status page, make sure there are no active alarms.

            10.5   Replacing a PFU

            This procedure describes how to replace a PFU1 (AMM 20p), PFU2 (AMM 6p) or PFU3 (AMM 6p B). PFU1 and PFU3 can be used in redundant power configurations.


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.

            To replace the plug-in unit:

            1. Undo the two screws on the latches.
            2. Disconnect all cables from the plug-in unit.

              Caution!  
              Make sure the external power is switched off when working with the DC cable.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and will suppress notifications from the PFU, including alarms from an FAU1 connected to a PFU1.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 40   Pressing the BR button

            1. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              A PFU failure could mean that the LEDs are not working.

              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            2. Insert the new plug-in unit.
            3. Tighten the two screws on the latches.
            4. Connect all cables to the plug-in unit and switch on the external power supply.

              This will initiate a power up of the plug-in unit and for a non-redundant power configuration a power up of the NE.

            5. Start the LCT. For more information, see Section 3.3.
            6. In the Navigation Tree, click the new PFU.
            7. On the PFU Alarms and Status page, make sure there are no active alarms.

            10.6   Replacing an NPU1 ANSI

            The NPU 8x2, which holds the NE configuration data, can be replaced without disturbing all traffic not directly connected to the unit. The procedure is performed while the NE is running in NPU Installation mode, see also Section 3.3.2.1.

            Note:  
            The NE is accessed in NPU Installation mode. Configure the PC to use a dynamic IP address obtained from the DHCP server in the NE or alternatively use the static IP address 10.0.0.2. For more information on IP addressing, see Section 3.3.3.


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.

            To replace the NPU1 ANSI:

            1. You need a backup configuration file on the FTP server on your PC.

              The configuration file must have the following path: <drive:>\tn_ftp_home\tn_backup_configuration\<hostname.cfg>. The file is typically fetched from the same directory on a remote FTP server.

              Note:  
              If you do not have a configuration file you can, if possible, try to upload the existing configuration file from the NE, see Section 11.89.

              The final alternative is to make a complete setup of the NE, see Section 5.


            2. Disconnect all cables from the plug-in unit and undo the two screws on the latches.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 41   Pressing the BR button

            1. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            2. Insert the new NPU1 ANSI. Press and release the BR button while the Fault (red), Power (green) and BR (yellow) LEDs are ON (NPU power up). The BR (yellow) LED will start flashing, indicating that the NE is in NPU Installation mode.
            3. Tighten the two screws on the latches.
            4. Connect all cables, including the Ethernet cable (twisted pair) to the 10/100BASE-T port.
            5. Start a Web browser and enter the URL http://10.0.0.1/.
            6. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
            7. On the Restore NPU Configuration page, do one of the following:
            8. When the configuration has been loaded, click Activate on the Restore NPU Configuration page.

              If the configuration requires new software to be loaded, this will be done automatically. This requires that the software is present in the <drive:>\tn_ftp_home\tn_system_release folder.

              A progress bar displays the progress of the software upgrade. When the download and software upgrade is finished, the NE will make a warm restart. After the restart the NE will run in Normal mode with the correct configuration.

            9. Type the URL http://<IP address> in the browser Address bar. The IP address is typically found in the site documentation or on the information plate of the NE. See also Section 3.3.2.3.
            10. In the Navigation Tree, click the NPU1 ANSI.
            11. On the NPU1 ANSI Alarms and Status page, make sure there are no active alarms.

            10.7   Replacing an NPU1 BA

            The NPU1 BA, which holds the NE configuration data, can be replaced without disturbing all traffic not directly connected to the unit.

            The procedure for replacing the NPU1 BA is different depending on whether it is equipped with an RMM or not. The procedures are described in the following sections:

            10.7.1   Replacing an NPU1 BA with RMM


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.

            To replace an NPU1 BA that is equipped with an RMM:

            1. Disconnect all cables from the NPU1 BA and undo the two screws on the latches.
            2. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 42   Pressing the BR button

            1. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            2. Move the RMM from the old NPU1 BA to the new NPU1 BA. The location of the RMM is shown in Figure 43.

            Figure 43   RMM Location on NPU1 BA

            1. Insert the new NPU1 BA.
            2. Tighten the two screws on the latches.
            3. Connect all cables, including the USB cable.
            4. Start a Web browser and enter the URL http://<IP address>.
            5. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
            6. In the Navigation Tree, click the NPU1 BA.
            7. On the NPU1 B Alarms and Status page, make sure there are no active alarms.

            10.7.2   Replacing an NPU1 B without RMM


            Caution!  
            Electrostatic Discharge (ESD) may damage the equipment. Always use an approved ESD wrist strap to avoid damage to components fitted on printed circuit boards.

            To replace an NPU1 B that is not equipped with an RMM:

            1. You need a backup configuration file on the FTP server on your PC.

              The configuration file must have the following path: <drive:>\tn_ftp_home\tn_backup_configuration\<hostname.cfg>. The file is typically fetched from the same directory on a remote FTP server.

              Note:  
              If you do not have a configuration file you can, if possible, try to upload the existing configuration file from the NE, see Section 11.89.

              The final alternative is to make a complete setup of the NE, see Section 5.


            2. Disconnect all cables from the NPU1 B and undo the two screws on the latches.
            3. Press the BR button gently and release it. This is a request to take the plug-in unit Out of Service and all traffic related alarms will be disabled.
              Note:  
              The BR button should be pressed before the plug-in unit is removed, even if the Power (green) LED is OFF.

            Figure 44   Pressing the BR button

            1. Wait until the BR (yellow) LED is ON and then remove the plug-in unit within 60 minutes. If the LED is not ON within 60 seconds, press and release the BR button again. Wait another 60 seconds and if the LED is still not ON, remove the unit anyway.
              Note:  
              If you do not remove the plug-in unit within 60 minutes, it is automatically taken into service. You can also take the plug-in unit into service before the end of the 60 minutes by pressing the BR button again.

            2. Insert the new NPU1 BA. Press and release the BR button while the Fault (red), Power (green) and BR (yellow) LEDs are ON (NPU power up). The BR (yellow) LED will start flashing, indicating that the NE is in NPU Installation mode.
            3. Tighten the two screws on the latches.
            4. Connect all cables, including the USB cable.
            5. Start a Web browser and enter the URL http://10.0.0.1/.
            6. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
            7. If you have a configuration file, click Download on the Restore NPU Configuration page.

              If you do not have a configuration file, click Current or Factory Settings and then click Activate. You can skip the rest of this procedure; you need to make a complete setup of the NE, see Section 5.

            8. On the Load Configuration page, type the name of the configuration file in the File Name box and then click Apply.
            9. On the Load Configuration Progress page, click Update Progress until the download is finished.
            10. On the Restore NPU Configuration page, click Activate.

              If the configuration file requires new software to be loaded, this will be done automatically. This requires that the software is present in the <drive:>\tn_ftp_home\tn_system_release folder.

              A progress bar displays the progress of the software upgrade. When the download and software upgrade is finished, the NE will make a warm restart. After the restart the NE will run in Normal mode with the selected configuration.

            11. In the Navigation Tree, click the NPU1 BA.
            12. On the NPU1 BA Alarms and Status page, make sure there are no active alarms.

            10.8   Replacing an NPU2 A

            The NPU2 A supplies the other units in the AMM with power so the NE will be down when replacing the NPU2. All cables and units should be handled according to instructions in the MINI-LINK TN ANSI Installation Manual.


            Caution!  
            Make sure the external power is switched off when working with the DC cable.

            To replace the NPU2 A:

            1. Switch off the external power.
            2. Disconnect all cables from the NPU A2 and undo the two screws on the latches.
            3. Remove the old NPU2 A.
            4. Move the RMM from the old NPU2 A to the new NPU2 A. The location of the RMM is shown in Figure 46.

            Figure 45   RMM Location on NPU2

            Figure 46   RMM Location on NPU2 A

            1. Insert the new NPU2 A and tighten the two screws on the latches.
            2. Connect all cables to the unit, including the USB cable between the unit and the PC.
            3. Switch on the external power.
            4. Start a Web browser and enter the URL http://<IP address>.
            5. In the Enter Network Password dialog box, type the user name and password, and click OK. For more information see Section 9.1.
            6. In the Navigation Tree, click the NPU2 A.
            7. On the NPU2 A Alarms and Status page, make sure there are no active alarms.

            10.9   Replacing a Radio Unit

            This procedure describes how to replace a radio Unit (RAU).

            1. Disconnect the station radio cable from the MMU.
            2. Replace the RAU.

              Follow the instructions in the MINI-LINK TN, MINI-LINK HC, MINI-LINK E, Outdoor Installation Manual when replacing the RAU.

            3. Reconnect the station radio cable to the MMU.

              One of the following happens:

            4. Start the LCT and make sure the no Hot Swap Incomplete events are logged.
              Note:  
              If you intend to replace the old RAU with an incompatible RAU, you need to configure the new RAU manually before proceeding. Follow the procedures in Section 6.5.

            5. Align the new RAU.

              Follow the instructions in the MINI-LINK TN, MINI-LINK HC, MINI-LINK E, Outdoor Installation Manual when aligning the new RAU.

            6. In the Navigation Tree, click the RAU being replaced.
            7. On the Alarms and Status page, make sure there are no active alarms.

            10.10   Changing the Traffic Capacity of a Radio Terminal with MMU2

            This procedure describes how to change the traffic capacity of an unprotected (1+0) or protected (1+1) Radio Terminal (MMU2 only).

            To change the traffic capacity:

            1. Delete the existing traffic routings for DS1s. Follow the instructions in Section 6.9.2.
            2. In the Navigation Tree, select an MMU2 in the terminal.
            3. On the MMU2 Configuration page, click Perform AM Setup and Hop Setup. In MSM, perform AM Setup and Hop Setup to change the traffic capacity. Follow the instructions in MSM User Guide or MSM online Help.
            4. Create new traffic routings for DS1s. Follow the instructions in Section 6.9.1.
            5. On the MMU2 Alarms and Status page, make sure there are no active alarms.

            10.11   Changing the Traffic Capacity of a Radio Terminal with MMU2 BA/CA

            This procedure describes how to change the traffic capacity of an unprotected (1+0) or protected (1+1) Radio Terminal (MMU2 BA/CA only).

            To change the traffic capacity:

            1. In the Navigation Tree, select an MMU2 BA/CA in the terminal.
            2. Click the Configuration menu to open the MMU2 B/C ConfigurationMMU2 BA/CA Configuration page.
            3. Under Traffic Capacity - Modulation, change the traffic capacity, modulation and frame format.
            4. Click Apply.
            5. On the MMU2 Alarms and Status page, make sure there are no active alarms.

            10.12   Changing an 1+0 Radio Terminal to a 1+1 Radio Terminal with MMU2

            This procedure describes how to change an unprotected (1+0) Radio Terminal to a protected (1+1) Radio Terminal.

            1. Insert the new MMU2 and SMU2 ANSI, see Section 10.1.
              Note:  
              The 1+1 configuration is only possible if the units are placed in adjacent AMM positions according to specifications in MINI-LINK TN ANSI Indoor Installation Manual.

            2. Delete the existing traffic routings for DS1s. Follow the instructions in Section 6.9.2.
            3. In the Navigation Tree, click the SMU2 ANSI. On the SMU2 ANSI Configuration page, select Protection and click Apply.
            4. In the Navigation Tree, click one of the MMU2s in the protected terminal.
            5. On the MMU2 Configuration page, under Protection Mode, select Prepare for 1+1 configuration.
            6. Click Apply.
            7. Select In Service and clear the Enable check box, for all three units, and click Apply.
            8. Click Perform AM Setup and Hop Setup. In MSM, perform AM Setup and Hop Setup. Follow the instructions in MSM User Guide or MSM online Help.
            9. Carry out the outdoor equipment installation, indoor and outdoor radio cabling, and antenna alignment. Follow the instructions in MINI-LINK TN ANSI Indoor Installation Manual and MINI-LINK TN, MINI-LINK HC, MINI-LINK E Outdoor Installation Manual.
            10. Configure the applicable interfaces:
            11. Create new traffic routings for DS1s. Follow the instructions in Section 6.9.1.
            12. In the Navigation Tree, click one of the MMU2s in the protected terminal.
            13. On the MMU2 Configuration page, select the Enable check box.
            14. On one of the MMU2 Alarms and Status pages, make sure there are no active alarms.

            10.13   Changing an 1+0 Radio Terminal to a 1+1 Radio Terminal with MMU2 BA/CA

            This procedure describes how to change an unprotected (1+0) Radio Terminal to a protected (1+1) Radio Terminal.

            Note:  
            1+1 configurations are only possible if the units are placed in adjacent AMM positions according to specifications in MINI-LINK TN ANSI Indoor Installation Manual.

            1. Insert the new MMU2 BA/CA, see Section 10.1.
            2. Using the new MMU, configure a temporary unprotected (1+0) Radio Terminal, as described in Section 6.5.1.
              Note:  
              Do not turn on the transmitter when creating the temporary terminal.

              Note:  
              To be able to configure a protected terminal, the following conditions apply:
              • The temporary terminal must be configured to use the same traffic capacity, modulation method, and identity as the existing terminal.
              • For 1+1 Hot configurations, both RAUs must have the same frequency.
              • For 1+1 Work configurations, both RAUs must have different frequencies.

            3. When the temporary terminal is set up, configure a protected terminal as described in Section 6.5.2.
            4. In the Navigation Tree, click one of the MMUs in the protected terminal.
            5. On the Alarms and Status page, make sure there are no active alarms.

            10.14   Changing the Traffic Capacity of an SMU2 ANSI (co-siting)

            The traffic capacity of an SMU2 ANSI in co-siting mode interfacing MINI-LINK E equipment is changed as described below.

            To change the traffic capacity:

            1. Delete the existing traffic routings for DS1s. Follow the instructions in Section 6.9.2 .
            2. In the Navigation Tree, click the SMU2.
            3. Click the Configuration menu.
            4. On the SMU2 ANSI Configuration page, under Traffic Capacity, select the new traffic capacity and click Apply.
            5. Create new traffic routings for DS1s. Follow the instructions in Section 6.9.1.
            6. On the SMU2 ANSI Alarms and Status, make sure there are no active alarms.

            11   User Interface Reference

            This section gives information on all items available on the different pages displayed when working with the EEM. Each page is described in a separate section and the information is accessed from the EEM by clicking Help.

            Note:  
            Each figure in this section reflects a certain setting of the equipment. This means that some of the objects described in the text are not present in the figures.


            11.1   Radio Terminal Configuration

            This page provides a guided setup for configuration of Radio Terminals during the initial setup. At least the terminals used for DCN communication must be set up at this stage.

            Figure 47   The Radio Terminal Configuration page

            See Also


            11.2   Radio Terminal Configuration for MMU2 BA/C

            This page provides a guided setup for configuration of MMU2 BA/CA Radio Terminals during the initial setup.

            Figure 48   Radio Terminal Configuration page for MMU2 BA/CA

            See Also


            11.3   Automatic Configuration

            This page provides a guided setup to configure the NE using a configuration file. This includes configuration security, DCN and system parameters. Depending on the contents of the configuration file this could be a complete configuration excluding the parts configured with MSM.

            Figure 49   The Automatic Configuration page

            See Also


            11.4   Manual Configuration

            This page provides a guided setup to configure the NE without using a configuration file.

            Figure 50   The Manual Configuration page

            See Also


            11.5   Software Upgrade - Installation Wizard

            This page is used to perform an upgrade of baseline in the installation wizard. The baseline is described in a Software Baseline Description File (SBDF).

            Figure 51   The Software Upgrade - Installation Wizard page


            11.6   Finish Installation

            This page is used to save the configuration in the installation wizard.

            Figure 52   The Finish Installation page


            11.7   Installation Finished

            This page is displayed when an NPU1 ANSI NE is making a warm restart after leaving Node Installation mode. After the restart it will run in Normal mode. The IP address of the NE has been changed and you will have to use this address when you access the NE, see also Section 3.3.2.3.

            Figure 53   The Installation Finished page


            11.8   Change Password

            This page provides a guided setup to change the password for the control_user and view_user.

            Figure 54   The Change Password page


            Caution!  
            Use this function restrictively and only when you have lost the passwords to an already installed NE.

            See Also


            11.9   Emergency Fallback

            This page provides a guided setup to activate the previous NPU software release.

            Figure 55   The Emergency Fallback page

            See Also


            11.10   Perform Emergency Fallback

            This page is used to activate the previous NPU software release.

            Figure 56   The Perform Emergency Fallback page


            Caution!  
            Use this function restrictively and only in the unlikely event that you have performed a software upgrade to a software version, from which you cannot perform a full software upgrade back to a correct version.

            11.11   Factory Setting

            This page provides a link to the Delete Configuration File page, used to delete an existing configuration file and revert the NE to factory setting, see Section 11.12.

            Figure 57   The Factory Setting page


            11.12   Delete Configuration File

            This page is used to delete an existing configuration file and revert the NE to factory setting.

            Figure 58   The Delete Configuration File page


            11.13   Configuration File Deleted

            This page is displayed when a NE is restarting after a configuration file has been deleted.

            Figure 59   The Configuration File Deleted page


            11.14   Restore NPU Configuration

            This page provides a guide to restore the NE configuration, residing on the NPU.

            Figure 60   The Restore NPU Configuration page


            11.15   Basic NE Configuration

            This page is used to set general NE parameters. It also allows configuration of the desired status of PFU/FAU.

            Figure 61   The Basic NE Configuration page


            11.16   LAN/Servers Configuration

            This page is used to set parameters for LAN communication and DCN servers.

            Figure 62   The LAN/Servers Configuration page


            11.17   PPP Configuration

            This page is used to configure the PPP interfaces. It can specifically be used to change the default bandwidth of the OC-3/STS-3 PPP interfaces and to set the number of DIG SC (2x64 kbit/s) for SMU2 ANSI in co-siting mode.

            Figure 63   The PPP Configuration page

            See Also


            11.18   Static Routing Configuration

            This page is used to configure static routes. A maximum of 100 static routes is possible.

            Figure 64   The Static Routing Configuration page

            See Also


            11.19   Modify Static Route

            This page is used to modify or delete a static route.

            Figure 65   The Modify Static Route page

            See Also


            11.20   OSPF Area Configuration

            This page is used to create OSPF areas.

            Figure 66   The OSPF Area Configuration page

            See Also


            11.21   Modify OSPF Area

            This page is used to modify or delete an OSPF area.

            Figure 67   The Modify OSPF Area page

            See Also


            11.22   PFU1 Configuration

            This page is used to configure a PFU1.

            Figure 68   The PFU1 Configuration page


            11.23   PFU2 Configuration

            This page is used to configure a PFU2.

            Figure 69   The PFU2 Configuration page


            11.24   PFU3 Configuration

            This page is used to configure a PFU3.

            Figure 70   The PFU3 Configuration page


            11.25   FAU Configuration

            This page is used to configure an FAU.

            Figure 71   The FAU Configuration page


            11.26   NPU1 BA Configuration

            Figure 72   The NPU1 BA Configuration page

            This page is used to configure an NPU1 BA.


            11.27   NPU1 ANSI Configuration

            This page is used to configure an NPU1 ANSI.

            Figure 73  


            11.28   NPU2 A Configuration

            This page is used to configure an NPU2 A.

            Figure 74   The NPU2 A Configuration page


            11.29   Ethernet Bridge Configuration

            This page is used to select which DS1 interfaces that will be used in the Ethernet Bridge, implemented in the NPU2 A. A maximum of 16 DS1s can be used for transmission of Ethernet traffic.

            Figure 75  

            See Also


            11.30   Bridge Configuration (ETU2)

            This page is used to select which DS1 interfaces that will be used in the Ethernet Bridge, implemented in ETU2.

            Figure 76   The Bridge Configuration page for ETU2

            See Also


            11.31   ETU2 Configuration

            This page is used to configure an ETU2.

            Figure 77   The ETU2 Configuration page


            11.32   LTU 12xDS1 Configuration

            This page is used to configure an LTU 12xDS1.

            Figure 78   The LTU 12xDS1 Configuration page


            11.33   LTU 16xDS1 or LTU 16/1 Configuration

            This page is used to configure LTU 16xDS1. Configuration for LTU 16/1 is similar.

            Figure 79   The LTU 16xDS1 Configuration page


            11.34   LTU 155 ANSI Configuration

            This page is used to configure an LTU 155 ANSI.

            Figure 80   The LTU 155 Configuration page


            11.35   MMU2 Configuration

            This page is used to configure an MMU2.

            Figure 81   The MMU2 Configuration page

            See Also


            11.36   SMU2 ANSI Configuration

            This page is used to configure an SMU2 ANSI. The unit can be used for protection in a protected (1+1) Radio Terminal or as a traffic interface with co-sited MINI-LINK E terminals.

            Figure 82   The SMU2 ANSI Configuration page

            See Also


            11.37   MMU2 BA/CA Configuration

            This page is used to configure the MMU2 BA/CAs on the near-end Radio Terminal. For protected (1+1) Radio Terminals, both modems in the terminal are configured at the same time.

            Figure 83   The MMU2 BA/CA Configuration page showing both Near and Far End

            Note:  
            To show the configuration of the far-end, click Show Far End.

            See Also


            11.38   RAU IF Configuration

            This page is used to configure an RAU IF interface for an MMU2 BA/CA.

            Figure 84   The RAU IF Configuration page

            See Also


            11.39   RAU Configuration

            This page is used to configure the radio units on the near- and far end Radio Terminal.

            Figure 85   The RAU Configuration page showing the Far-End

            Note:  
            To show the configuration of the far-end, click Show Far End.

            See Also


            11.40   RF Configuration

            This page is used to configure an RF interface, on an RAU connected to an MMU2 BA/CA or ATU MMU2 B.

            Figure 86   The RF Configuration page

            Figure 87   The RF Configuration page

            See Also


            11.41   Reset Configuration

            This page is used to reset a Radio Terminal with MMU2 BA/CA to the default configuration. The configuration items on the MMU2 BA/CA , RAU, RAU IF, RF and SWITCH configuration pages will get default values. All units in the terminal must be In Service to be able to perform this operation.

            Figure 88   The Reset Configuration page


            Caution!  
            Resetting the configuration will disturb the traffic.

            See Also


            11.42   Restore Configuration

            This page is used, from a near end MMU2 BA/CA, to restore the configuration of near and far end radio terminals, which means:

            All units in the terminal must be In Service to be able to perform this operation.

            Figure 89   The Restore Configuration page

            See Also


            11.43   SWITCH Configuration

            This page is used to configure the SWITCH interface for a Radio Terminal with MMU2 BA or MMU2 CA.

            Figure 90   The SWITCH Configuration page

            See Also


            11.44   SWITCH Protection

            This page is used to configure the protection parameters for a near-end radio terminal with MMU2 BA/CA, and to configure some parameters for a far-end radio terminal.

            Figure 91   The SWITCH Protection page

            Note:  
            To show the configuration of the far-end, click Show Far End.

            See Also


            11.45   Line/Section Configuration

            This page is used to configure an Line/Section interface.

            Figure 92   The Line/Section Configuration page


            11.46   APS Configuration

            This page is used to configure an MSP interface.

            Figure 93   The APS Configuration page


            11.47   STS-1 Configuration

            This page is used to configure a STS-1 interface.

            Figure 94   The STS-1 Configuration page


            11.48   VT1.5 Configuration

            This page is used to configure a VT1.5 interface.

            Figure 95   The VT1.5 Configuration page


            11.49   All VT1.5 Configuration

            This page is used to configure all VT1.5 interfaces simultaneously on an LTU 155 ANSI. One or several parameters can be included in the configuration.

            Figure 96   The All VT1.5 Configuration page

            The page initially displays no parameter values but it is possible to use one of the interfaces as template. If this page is opened by clicking the DEGTHR and DEGM configuration link on the configuration page for an individual VC-12 interface, the values for the interface are displayed as default values with Set selected.


            11.50   MUX23 Configuration

            This page is used to configure an MUX23 interface.

            Figure 97   The MUX23 Configuration page


            11.51   MUX12 Configuration

            This page is used to configure an MUX12 interface.

            Figure 98   The E2 Configuration page


            11.52   DS1 Configuration

            This page is used to configure an DS1 interface.

            Figure 99   The DS1 Configuration page


            11.53   All ANSI Configuration

            This page is used to configure all physical DS1 interfaces simultaneously, on a unit. One or several parameters can be included in the configuration by selecting the Set check box.

            Figure 100   The All DS1 Configuration page

            The page initially displays no parameter values but it is possible to use one of the interfaces as template.


            11.54   DS1 Overview

            This page is opened in a separate window where you can view and change the configuration of an DS1 interface, as well as handle its 1+1 DS1 SNCP protection and traffic routing. Furthermore, it is possible to handle the DS1 as part of the Ethernet Bridge, when working with an ETU2, or an NE based on NPU2 A, or a G.804 as part of an IMA Group.

            The upper part of the page displays the configuration of the related DS1s. The top row is the DS1 for which the page is opened. If this DS1 is protected then the other two DS1s in the 1+1 DS1 SNCP protection is displayed in the next two rows. If the DS1 is routed then the DS1(s) to which it is routed is also displayed in the table.

            The lower part gives a graphical view of how the different DS1s are related.

            Figure 101  

            See Also


            11.55   User Input Configuration

            This page is used to configure a User Input port.

            Figure 102   The User Input Configuration page


            11.56   User Output Configuration

            This page is used to configure a User Output port.

            Figure 103   The User Output Configuration page


            11.57   Traffic Routing Select Interfaces

            This page is used to select interfaces for creation or modification of traffic routing. Based on the selection, the actual configuration is made from either of two separate pages with different views.

            Figure 104   The Traffic Routing Select Interfaces page

            See Also


            11.58   Traffic Routing Matrix View

            This page is used to display, create, modify or delete traffic routing. It contains a matrix with the interfaces on two axes. An intersection point between two interfaces in the matrix is used to handle a certain traffic routing.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Note:  
            Remote traffic routing requires a license. To use traffic routing without a license, you need to connect directly to the O&M/USB port on the NPU. See Section 6.3 for more information on how to work with licenses.

            Figure 105   The Traffic Routing Matrix View page

            Note:  
            The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            See Also


            11.59   Traffic Routing List View

            This page is used to display, create, modify or delete traffic routing.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Note:  
            Remote traffic routing requires a license. To use traffic routing without a license, you need to connect directly to the O&M/USB port on the NPU. See Section 6.3 for more information on how to work with licenses.

            Figure 106  

            Note:  
            The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            See Also


            11.60   Traffic Routing - Current Traffic Routings

            This page shows all current traffic routings.

            Figure 107   The Current Traffic Routings page


            11.61   Create Traffic Routing

            This page is used to create traffic routing for one interface pair.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Figure 108  

            See Also


            11.62   Create Multiple Traffic Routings

            This page is used to create traffic routing for several interface pairs simultaneously.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Figure 109   The Create Multiple Traffic Routings page

            See Also


            11.63   Modify Traffic Routing

            This page is used to modify or delete an existing traffic routing.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Figure 110   The Modify Traffic Routing page

            See Also


            11.64   1+1 DS1 SNCP Select Interfaces

            This page is used to select interfaces for creation or modification of 1+1 DS1 SNCP protection. Based on the selection, the actual configuration is made from either of two separate pages with different views.

            Figure 111   The 1+1 DS1 SNCP Select Interfaces page

            See Also


            11.65   1+1 DS1 SNCP Matrix View

            This page is used to display, create, modify or delete 1+1 DS1 SNCP protection. It contains a matrix with the interfaces of the two selected units. An intersection point between two interfaces in the matrix is used to handle a certain protection.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Note:  
            1+1 SNCP protection requires a license. See Section 6.3 for more information on how to work with licenses.

            Figure 112   The 1+1 DS1 SNCP Matrix View page

            Note:  
            The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            See Also


            11.66   1+1 DS1 SNCP List View

            This page is used to display, create, modify or delete 1+1 DS1 SNCP protection.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Note:  
            1+1 SNCP protection requires a license. See Section 6.3 for more information on how to work with licenses.

            Figure 113   The 1+1 DS1 SNCP List View page

            Note:  
            The interfaces on an MMU2 in a protected (1+1) Radio Terminal are denoted in accordance with the SMU2 ANSI.

            See Also


            11.67   Create 1+1 DS1 SNCP

            This page is used to create 1+1 DS1 SNCP protection for one interface pair.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Figure 114   The Create 1+1 DS1 SNCP page

            See Also


            11.68   Create Multiple 1+1 DS1 SNCP

            This page is used to create 1+1 DS1 SNCP protection for several interface pairs simultaneously.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Figure 115   The Create Multiple 1+1 DS1 SNCP page

            See Also


            11.69   Modify 1+1 DS1 SNCP

            This page is used to modify or delete a 1+1 DS1 SNCP protection.

            Note:  
            If MINI-LINK Connexion is used to provision end-to-end DS1 connections, then only use the EEM to view current connections. Creating, modifying, and deleting DS1 connections shall in this case be done with MINI-LINK Connexion.

            Figure 116   The Modify 1+1 DS1 SNCP page

            See Also


            11.70   Create APS Protection

            This page is used to create APS protection including two adjacent LTU 155s.

            Figure 117   The Create APS Protection page

            Note:  
            The page is only displayed when the units are not included in an APS protection.

            Note:  
            The two LTU 155s have to be placed in adjacent AMM positions according to specifications in MINI-LINK TN ANSI Indoor Installation Manual.

            Note:  
            Creating MSP protection will remove the existing traffic routings on the LTU 155.

            See Also


            11.71   Creating Protection

            This page displays the progress of an ongoing creation of APS protection. It is automatically refreshed every fifth second to give an up-to-date status of the progress. When both units are ready this page is replaced by the Modify APS Protection page, see Section 11.72.

            Figure 118   The Creating Protection page

            See Also


            11.72   Modify APS Protection

            This page is used to modify or delete an existing APS protection.

            Figure 119   The Modify APS Protection page

            See Also


            11.73   Deleting Protection

            This page displays the progress of an ongoing deletion of APS protection. It is automatically refreshed every fifth second to give an up-to-date status of the progress. When both units are ready this page is replaced by the Create MSP Protection page, see Section 11.70.

            Figure 120   The Deleting Protection page

            See Also


            11.74   Inventory

            This page displays hardware and software information about the NE. Units without software modules will not be present in the software table.

            Figure 121   The Inventory page


            11.75   Edit Asset ID

            This page is used to specify identities of indoor hardware units.

            Figure 122   The Edit Asset ID page


            11.76   Report

            This page is used to generate a report of the configuration and inventory data of the NE. Select the check boxes for the items to be included in the configuration report. The contents of the report are further described in Section 11.77.

            Figure 123   The Report page


            11.77   View Report

            This page displays a configuration and inventory report. References are provided to help texts for the different parts of the report.

            Figure 124   The View Report page. Note that the figure shows only the beginning of the report.

            The list below provides references to the pages where the data is set.


            11.78   Upgrade of Baseline

            This page is the start page of a wizard providing a software upgrade to a desired baseline of load modules, defined in a Software Baseline Description File (SBDF).

            Note:  
            MMU2 and SMU2 (protection) are upgraded using MSM, Local Upgrade or MINI-LINK Manager.

            Figure 125   The Upgrade Baseline page

            See Also


            11.79   Upgrade of Modules

            This page is the start page of a wizard providing software upgrade of specific load modules.

            Note:  
            MMU2 and SMU2 ANSI (protection) are upgraded using MSM, Local Upgrade or MINI-LINK Manager.

            Figure 126   The Upgrade of Modules page

            See Also


            11.80   Settings

            This page is used to define software upgrade settings.

            Figure 127   The Settings page


            11.81   Start Upgrade

            This page is used to start a software upgrade, summarizing the requested actions.

            Figure 128   The Start Upgrade page, when an upgrade of baseline is performed


            11.82   View Units

            This page shows information about the load modules in all units.

            Figure 129   The View Units page


            11.83   Preferences

            This page is used to define software upgrade preferences. Preferences are only applicable for a baseline upgrade.

            Figure 130   The Preferences page


            11.84   Upgrade Progress - Baseline

            This page shows the progress of a baseline upgrade.

            Figure 131   The Upgrade Progress - Baseline page


            11.85   Upgrade Progress - Modules

            This page shows the progress of a load module upgrade.

            Figure 132   The Upgrade Progress - Modules page


            11.86   Scheduled Activation

            This page is displayed when the NE is scheduled for an activation of a new software configuration (only upgrade of baseline).

            Figure 133   The Scheduled Activation page


            11.87   Activation in Progress

            This page is displayed when a new software configuration is activated.

            Figure 134   The Activation in Progress page


            11.88   Confirm New Software Configuration

            This page is used to manually confirm the activation of the new software configuration, when performing an upgrade of baseline.

            Figure 135   The Confirm New Software Configuration page


            Caution!  
            If no button is clicked on this page within 15 minutes the NE will revert to the old software configuration.

            11.89   Load Configuration

            This page is used to save a backup file of a configuration on an FTP server or to restore a configuration using a backup file.

            Note:  
            Activating a configuration file that has been fetched from another NE will revert the user passwords to default factory settings. See also Section 9.1.

            Figure 136   The Load Configuration page


            11.90   Load Configuration Progress

            This page is used to display the progress of an ongoing upload or download of a configuration file.

            Figure 137   The Load Configuration Progress page


            11.91   Load Configuration Preview

            This page is used to preview a downloaded configuration before activating it.

            Figure 138   The Load Configuration Preview page


            11.92   Restart

            This page is used to perform a restart of the NE or a single unit.

            Figure 139   The Restart page

            Note:  
            A restart of the NE or NPU will clear the Alarm List, Performance and Event Logs. Configurations that have not been saved, active loops and running BERTs will be lost.

            Note:  
            During a restart of the NE, the PC will lose contact with the Web server. Click Refresh or Reload in your browser after the NE has restarted to connect to the Web server.


            11.93   Help Setup

            This page is used to specify the location of the Help file by typing the path in the text box. For more information on how to set up and use the Help, see Section 4.6.

            Figure 140   The Help Setup page

            Note:  
            A security feature in Internet Explorer 6 SP1 sometimes denies the browser to access the Help on your PC. Should this occur do the following in your browser: Click Tools->Internet Options->Security-> and add http://<IP address of the NE> as a "Trusted Site".


            11.94   Licenses

            This page shows a list of features that are possible to activate with licenses. This list of features is based on the current hardware configuration.

            Note:  
            If you have installed licenses for features that cannot be used in the current hardware configuration, those features will also be shown in the list. That is, they are shown, but cannot be activated.

            Figure 141   The Licenses page


            11.95   Create License Request

            This page is used to create a license request file.

            Figure 142   The Create License Request page


            11.96   License File Overview

            This page shows a list of all LKFs that are stored on the RMM.

            Figure 143   The License File Overview page


            11.97   License File Inventory

            This page shows a list of all features with installed licenses.

            Figure 144   The License File Inventory page


            11.98   License File Content

            This page shows the XML source of an LKF.

            Figure 145   The Install Licenses page


            11.99   Clear Reservation

            This page is used to clear the reservation of a position in the AMM. A position is reserved for a plug-in unit of the same type whenever a plug-in unit is removed.

            To use this position for another type of plug-in unit, the reservation must be cleared. You can also clear a reservation without inserting a new plug-in unit to indicate that this position is no longer used.

            Figure 146   The Clear Reservation page

            Each row in the list represents a position in the AMM. To clear a reservation, select the check box for that position and then click Apply.


            11.100   NE Alarms and Status

            This page gives an overview of the alarms and status of the NE and its plug-in units.

            Figure 147   The NE Alarms and Status page for an AMM 20p

            The position of a plug-in unit is indicated by a figure. Each unit is identified by a label and its accumulated status is indicated by a color. A bluish-green color indicates that a unit has notifications disabled or administration status set to Out of Service. Moving the pointer over a unit will display a tool tip with information on unit type, operational status and severity. Clicking a unit will open the Alarms and Status page for the unit.

            Equipment protection is indicated by the text 1+1. The active LTU 155 ANSI and MMU2 BA/CA is indicated by a label, while the active MMU2 is indicated in MSM.

            A warning will be displayed if notifications from the NE are disabled.

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.101   Ethernet Bridge Alarms and Status

            This page displays the alarms and status of the Ethernet Bridge, implemented in the NPU2 A. It also displays counters for the HDLC and Ethernet interfaces, if desired.

            Figure 148   The Ethernet Bridge Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.

            See Also


            11.102   Bridge Alarm and Status (ETU2)

            This page displays the status of the Bridge interface on ETU2.

            Figure 149   The Bridge Alarm and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.103   LAN Status

            This page displays the status of the LAN interface.

            Figure 150   The LAN Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.104   USB Status

            This page displays the status of the USB interface on the NPU2, NPU1 B and ATU NPU.

            Figure 151   The USB Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.105   PPP Status

            This page displays the status of the PPP and ML-PPP interfaces.

            Figure 152   The PPP Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.

            See Also


            11.106   PPP and ML-PPP Counters

            This page displays the status of the PPP and ML-PPP counters.

            Figure 153   The PPP and ML-PPP Counters page


            11.107   TCP Status

            This page displays the status of the TCP parameters.

            Figure 154   The TCP Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.108   UDP Status

            This page displays the status of the UDP parameters.

            Figure 155   The UDP Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.109   ARP Status

            This page displays the status of the ARP parameters for the effected Ethernet interfaces.

            Figure 156   The ARP Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.110   IP/ICMP Status

            This page displays the status of the IP/ICMP parameters.

            Figure 157   The IP/ICMP Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.111   Static Routing Status

            This page displays static routing parameters.

            Figure 158   The Static Routing Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.

            See Also


            11.112   OSPF General Status

            This page displays general OSPF parameters.

            Figure 159   The OSPF General Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.113   OSPF Area Status

            This page displays OSPF area parameters.

            Figure 160   The OSPF Area Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.

            See Also


            11.114   OSPF Interface Status

            This page displays OSPF interface parameters.

            Figure 161   The OSPF Interface Status page. Note that the figure does not show all parameters that will be displayed on the screen.

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.115   OSPF Neighbor Status

            This page displays OSPF neighbor parameters.

            Figure 162   The OSPF Neighbor Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.116   OSPF Host Status

            This page displays OSPF host parameters.

            Figure 163   The OSPF Host Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.117   PFU Alarms and Status

            This page displays the alarms and status of a PFU. A warning will be displayed if notifications from the unit are disabled.

            Figure 164   PFU Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.118   FAU Alarms and Status

            This page displays the alarms and status of an FAU. A warning will be displayed if notifications from the unit are disabled.

            Figure 165   The FAU Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.119   NPU1 BA Alarms and Status

            This page displays the alarms and status of the NPU1 BA and provides links to the DS1 interfaces and user I/O ports. A warning will be displayed if notifications from the unit are disabled.

            Figure 166   The NPU1 BA Alarms and Status

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.120   NPU1 ANSI Alarms and Status

            This page displays the alarms and status of the NPU1 ANSI and provides links to the DS1 interfaces and user I/O ports. A warning will be displayed if notifications from the unit are disabled.

            Figure 167   The NPU1 ANSI Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.121   NPU2 A Alarms and Status

            This page displays the alarms and status of the NPU2 A and provides links to its interfaces. A warning will be displayed if notifications from the unit are disabled.

            Figure 168   The NPU2 A Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.122   ETU2 Alarms and Status

            Figure 169   The ETU2 Alarms and Status page


            11.123   LTU 16xDS1 and LTU 16/1 Alarms and Status

            This page displays the alarms and status of the LTU 16xDS1 and provides links to the DS1 interfaces. A warning will be displayed if notifications from the unit are disabled.

            Figure 170   The LTU 16xDS1 Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.124   LTU 12xDS1 Alarms and Status

            This page displays the alarms and status of the LTU 12xDS1 and provides links to the DS1 interfaces. A warning will be displayed if notifications from the unit are disabled.

            Figure 171   The LTU 12xDS1 Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.125   LTU 155 ANSI Alarms and Status

            This page displays the alarms and status of the LTU 155 ANSI and its OC-3/STS-3 port and provides a link to the Line/Section interface. A warning will be displayed if notifications from the unit are disabled.

            Figure 172   The LTU 155 ANSI Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.


            11.126   Radio Terminal Alarms and Status for MMU2 BA/CA

            This page gives alarms and status information for a near-end Radio Terminal based on MMU2 BA/CA. It is also possible to view the status of far-end radio terminals based on MINI-LINK TN and MINI-LINK E.

            Figure 173   The Radio Terminal Alarms and Status page showing the Far End

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.

            Note:  
            To show the configuration of the far-end, click Show Far End.

            The upper part of the page illustrates the Radio Terminal, with rectangles representing the units and framed arrows representing the different interfaces. The MMU holds the traffic interfaces (DS1, MUX12 andMUX23) and the RAU IF. The RAU holds the RF interface. For a protected Radio Terminal, a SWITCH interface is available on the active MMU.

            The highest alarm severity for each entity is indicated by a color and detailed information is displayed in the lower part when clicking a specific entity. Tool tips are provided when the pointer is moved over a unit or an interface.


            11.127   MMU2 Alarms and Status

            This page provides alarms and status information for the MMU2.

            Figure 174   The MMU2 Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.

            Note:  
            It is important to use MSM or MINI-LINK E Adapter to get the complete set of alarms for the terminal.

            A warning will be displayed if notifications from the unit are disabled.


            11.128   RAU Alarms and Status for MMU2

            This page provides alarms and status information for an RAU connected to an MMU2.

            Figure 175   The RAU Alarms and Status page

            Note:  
            The page is not updated automatically. Click Reload to display the latest information.

            Note:  
            It is important to use MSM or MINI-LINK E Adapter to get the complete set of alarms for the terminal. There are alarms on the RAU that will not be displayed on this page.

            A warning will be displayed if notifications from the unit are disabled.