SC-450 Help PDF

Corning
MobileAccess
System Controller (SC-450) SW v5.4
User Manual
P/N: 709C004406
REV: A00
Date: October 2013
Preface Material
About This Guide
This user guide provides all the information necessary to necessary to configure the System Controller (SC-450)
for use with the MobileAccess DAS.
Preface Material
Page 2
[Type text]
Standards and Certification

Corning MobileAccess products have met the approvals of the following certifying organizations:
Company Certification
ISO ISO 9001: 2000 and ISO 13485: 2003
Product Certifications
US
EMC
FCC 47 CFR Part 15 Subpart B, UL 60950-1
NOTE: This equipment has been tested and found to comply with the limits for a Class B digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference in a residential installation. This equipment generates, uses
and can radiate radio frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio or television reception, which can be determined
by turning the equipment off and on, the user is encouraged to try to correct the interference by one or
more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
-Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
-Consult the dealer or an experienced radio/TV technician for help.
Warning! Changes or modifications to this equipment not expressly approved by Corning
MobileAccess could void the users authority to operate the equipment.
Europe
EMC
EN 301 489, EN 60950
Preface Material
Page 3
[Type text]
T a b l e o f C o n te n ts
Preface Material ................................................................................................................................................... 2
About This Guide ....................................................................................................................................................... 2
Standards and Certification ................................................................................................................................ 3

Company Certification ................................................................................................................................................ 3
Product Certifications ................................................................................................................................................. 3
Table of Contents................................................................................................................................................. 4
1
Introduction ................................................................................................................................................. 10
1.1 Key Features and Capabilities ........................................................................................................................... 10

1.2 System Requirements ....................................................................................................................................... 12
1.2.1 Web Client Requirements......................................................................................................................... 12
1.2.2 Supported Browsers ................................................................................................................................ 12
1.2.3 Remote Access Requirements.................................................................................................................. 12
1.3 System Controller Specifications ........................................................................................................................ 13
1.3.1 Environmental and Regulatory Specifications ............................................................................................ 13
1.3.1.1 Temperature and Humidity ........................................................................................................... 13
1.3.1.2 Safety and Regulatory Approvals .................................................................................................. 13
1.3.2 SC-450 Power Requirements ................................................................................................................... 14
1.3.2.1 General Power Safety Instructions ................................................................................................ 14
1.3.2.2 Power Requirements .................................................................................................................... 14
1.3.3 Physical Specifications ............................................................................................................................. 14
1.3.4 Default Parameters .................................................................................................................................. 15
1.3.4.1 Network Parameters .................................................................................................................... 15
1.3.4.2 The System Administrator or Super User .................................................................................... 15
1.3.4.3 Default Group Admin User ............................................................................................................ 15
1.3.5 Front Panel Interfaces and Indicators ........................................................................................................ 16
1.3.5.1 Front Panel Interface Ports ........................................................................................................... 16
1.3.5.2 Front Panel LED Indicators ........................................................................................................... 17
1.3.5.3 Front Panel LCD .......................................................................................................................... 17
1.3.6 Rear Panel Interfaces .............................................................................................................................. 19
1.4 Standalone and Master/Slave Topology.............................................................................................................. 20
1.4.1 Standalone Topology ............................................................................................................................... 20
1.4.2 Master/Slave Topology ............................................................................................................................ 21
Installation Guidelines ................................................................................................................................ 23
2.1 Quick Installation Procedure .............................................................................................................................. 23

2.1.1 Physical Installation Steps ........................................................................................................................ 23
2.1.1.1
2.1.1.2
Table of Contents
Slave Controller Connections........................................................................................................ 23

RIU Connections.......................................................................................................................... 24
Page 4
2.1.1.3 PAU-6 Connections ..................................................................................................................... 24

2.1.1.4 BU and OCH Connections ............................................................................................................ 24
2.1.1.5 WMTS System Connections ......................................................................................................... 24
2.1.1.6 EC560 Solution Connections ........................................................................................................ 24
2.1.1.7 FT-350 Connections..................................................................................................................... 25
2.1.1.8 MobileAccessVE Connections ...................................................................................................... 25
2.1.2 Basic Setup and Configuration ................................................................................................................. 25
2.2 Master/Slave Topologies Controller Connections ................................................................................................ 26
2.2.1 Single-Building Master/Slave Topology ..................................................................................................... 26
2.2.2 Multi-Building Master/Slave Topology ....................................................................................................... 28
2.2.2.1 Master SC-450 to 330 Main .......................................................................................................... 29
2.2.2.2 Slave SC-450 to 330 Remote Unit ................................................................................................ 29
2.2.2.3 Base Unit to 330 Remote Unit ....................................................................................................... 29
2.3 Headend Device Connections to SC-450 ............................................................................................................ 31
2.3.1 RIU to SC-450 Connection ....................................................................................................................... 31
2.3.1.1 RIU-12 Management Connections ................................................................................................ 31
2.3.1.2 RIU-4, RIU-IM and RIU-Lite Management Connections .................................................................. 32
2.3.2 PAU-6 to SC-450 Connections ................................................................................................................. 33
2.3.3 BU to SC-450 Connections ...................................................................................................................... 33
2.3.4 WMTS to SC-450 Connections ................................................................................................................. 34
2.3.5 FT-350 Connections to the SC-450 ........................................................................................................... 34
2.4 MobileAccessVE Management Solution .............................................................................................................. 36
2.4.1 MobileAccessVE Deployed without FT-350 Fiber Backbone ....................................................................... 37
2.4.2 MobileAccessVE Deployed with FT-350 Fiber Backbone ............................................................................ 38
2.4.3 Defining the Master VCU IP Address in the SC-450 Subnet ........................................................................ 39
2.5 EC560 Management Connections ...................................................................................................................... 40
2.5.1 EHU and SC-450 Connections via Network ............................................................................................... 40
2.5.2 EHU and SC-450 via a Dedicated Network ................................................................................................ 41
2.6 SC-450 Auxiliary Input and Alarm Output Connections ........................................................................................ 42
2.6.1 Auxiliary Input Connections ...................................................................................................................... 42
2.6.2 Alarm Output Connections ....................................................................................................................... 42
2.7 Initial Controller Setup ....................................................................................................................................... 43
2.7.1 Initial Login and Setup.............................................................................................................................. 43
2.7.2 Configure SC-450 LOCAL and LAN Port Network Settings for Remote or Local Management ...................... 45
2.7.2.1 Ping Tool ..................................................................................................................................... 48
2.7.3 SC-450 Master/Slave Configuration .......................................................................................................... 49
2.7.3.1 Configure Slave Controllers .......................................................................................................... 49
2.7.3.2 Restoring a Slave Controller to a Master Controller Mode ............................................................... 51
2.7.4 Configure Controller Settings .................................................................................................................... 51
2.7.4.1 Configuring the Controller System Parameters............................................................................... 52
2.7.4.2 Configuring for Heartbeat Enabled Devices ................................................................................... 53
2.8 Auxiliary Device Setup ....................................................................................................................................... 54
Table of Contents
Page 5
Commissioning Wizard for RIU and MA1000/MA2000 Devices ................................................................ 56
3.1 Overview of Commissioning Wizard Procedure ................................................................................................... 57

3.2 Before Running the Wizard ................................................................................................................................ 58
3.3 Accessing the Commissioning Wizard ................................................................................................................ 59
3.4 Running the Wizard ........................................................................................................................................... 61
3.5 Analyzing Failed Devices ................................................................................................................................... 68
3.5.1 Fault Prompt During Commissioning ......................................................................................................... 68
3.5.2 Analyzing Summary Results after Completing Commissioning .................................................................... 69
3.5.3 Saving Details Report Results .................................................................................................................. 71
Commissioning Additional CMA Elements ............................................................................................... 72
4.1 PAU-6 Configuration ......................................................................................................................................... 73

4.2 WMTS-CH System Configuration ....................................................................................................................... 74
4.2.1 RIM-Main Configuration ........................................................................................................................... 76
4.2.2 RIM-1400 Configuration ........................................................................................................................... 78
4.2.2.1 RIM-1400 Synchronization ........................................................................................................... 80
4.3 EC560 Device Configuration .............................................................................................................................. 83
4.3.1 Manually Adding EHU to Network Topology .............................................................................................. 83
4.3.2 EHU (Ethernet Hub Unit) Configuration ..................................................................................................... 85
4.3.3 AU (Antenna Unit) Configuration Dialog .................................................................................................... 87
4.4 FT-350 Solution Configuration ........................................................................................................................... 89
4.4.1 OCH (Optical Central Hub) Configuration .................................................................................................. 89
4.4.2 ORU (Optical Remote Unit) Configuration ................................................................................................. 94
4.5 MobileAccessVE Device Configuration ............................................................................................................... 98
Navigating the Web GUI Application ....................................................................................................... 101
5.1 Network Topology ........................................................................................................................................... 102

5.1.1 Tree Status Colors ................................................................................................................................. 104
5.2 Main Menu ..................................................................................................................................................... 105
5.3 Device Configuration Tabs ............................................................................................................................... 106
5.3.1 Device Extended Name ......................................................................................................................... 107
5.3.2 Comments Tab ...................................................................................................................................... 108
5.3.3 Extended Name/Comments Mismatches ................................................................................................. 109
5.4 Removing a Hosted Device.............................................................................................................................. 110
Administration ........................................................................................................................................... 112
6.1 Multi User Account Management...................................................................................................................... 112

6.1.1 Defining User Groups ............................................................................................................................ 114
6.1.2 Defining User Accounts .......................................................................................................................... 116
6.1.3 Access Levels ....................................................................................................................................... 119
6.1.4 Multi-User Sessions ............................................................................................................................... 121
6.1.5 Group Passwords .................................................................................................................................. 121
Table of Contents
Page 6
6.1.6 Tracking Group Users Activity Logs ........................................................................................................ 122

6.1.6.1 Viewing the Activity Log.............................................................................................................. 123
6.1.6.2 Filtering the Activity Log ............................................................................................................. 124
6.2 User Session Timeout ..................................................................................................................................... 125
6.3 SW Upgrade Procedure................................................................................................................................... 127
6.3.1 Upgrading from v4.0, v5.1, v5.2 and v5.3 to v5.4 ..................................................................................... 127
6.3.2 Master Controller SW Upgrade ............................................................................................................... 128
6.3.3 Remote Master to Slave SW Download ................................................................................................... 131
6.4 Generating Device Reports .............................................................................................................................. 134
Monitoring and Troubleshooting ............................................................................................................. 138
7.1 Monitoring Summary Display ........................................................................................................................... 139

7.2 Event Display.................................................................................................................................................. 140
7.2.1 Viewing Events ...................................................................................................................................... 140
7.2.2 Filtering Displayed Events ...................................................................................................................... 141
7.3 Fault Sourcing Using the Network Topology Tree .............................................................................................. 143
7.4 Fault Sourcing Using the Device View .............................................................................................................. 145
7.4.1 RIU View ............................................................................................................................................... 146
7.4.1.1 RIU-12 Device View ................................................................................................................... 146
7.4.1.2 Legacy RIU Units (RIU-4, RIU-IM and RIU-Lite) ........................................................................... 148
7.4.2 PAU-6 ................................................................................................................................................... 149
7.4.3 Base Units View .................................................................................................................................... 150
7.4.4 RHU View ............................................................................................................................................. 151
7.4.5 Add-On View ......................................................................................................................................... 151
7.4.6 WMTS Element Views ........................................................................................................................... 152
7.4.6.1 RIM-Main View .......................................................................................................................... 152
7.4.6.2 RIM-1400 View .......................................................................................................................... 152
7.4.6.3 WMTS RHU-4 View ................................................................................................................... 152
7.4.7 FT-350 Elements Views ......................................................................................................................... 154
7.4.7.1 OCH View ................................................................................................................................. 154
7.4.7.2 ORU View ................................................................................................................................. 155
7.4.8 VE VCU View ........................................................................................................................................ 156
7.4.9 HX Indoor/Outdoor Views ....................................................................................................................... 157
7.4.10 HXn View .............................................................................................................................................. 159
7.4.11 GX Tri-Band View .................................................................................................................................. 160
7.4.12 GX-Quad View ...................................................................................................................................... 161
7.5 Fault Sourcing through the Device Alarms ........................................................................................................ 162
7.5.1 Viewing Device Alarms .......................................................................................................................... 162
7.5.2 Masking Irrelevant Alarms ...................................................................................................................... 163
7.5.3 RIU-12 .................................................................................................................................................. 164
7.5.3.1 CMU Alarms .............................................................................................................................. 164
7.5.3.2 BTSC Alarms............................................................................................................................. 165
7.5.4 Legacy RIU Units (RIU-4, RIU-IM and RIU-Lite) ....................................................................................... 166
Table of Contents
Page 7
7.5.4.1 BTSC/BDAC Alarms .................................................................................................................. 166

7.5.5 PAU-6 Alarms ....................................................................................................................................... 167
7.5.6 Base Unit Alarms ................................................................................................................................... 168
7.5.7 RHU Alarms .......................................................................................................................................... 169
7.5.8 Add-On Alarms ...................................................................................................................................... 170
7.5.9 WMTS Elements Alarms ........................................................................................................................ 171
7.5.9.1 RIM-Main Alarms ....................................................................................................................... 171
7.5.9.2 RIM-1400 Alarms ....................................................................................................................... 172
7.5.9.3 RHU-4 Alarms ........................................................................................................................... 173
7.5.10 FT-350 Alarms and Troubleshooting ....................................................................................................... 174
7.5.10.1 OCH Alarms .............................................................................................................................. 174
7.5.10.2 ORU Alarms .............................................................................................................................. 175
7.5.10.3 Troubleshooting Procedures ....................................................................................................... 176
7.5.11 EC560 Elements Alarms ........................................................................................................................ 178
7.5.11.1 EHU Alarms .............................................................................................................................. 178
7.5.11.2 AU Alarms ................................................................................................................................. 179
7.5.12 VE Alarms ............................................................................................................................................. 180
7.5.12.1 VCU Alarms .............................................................................................................................. 180
7.5.12.2 VAP Alarms ............................................................................................................................... 181
7.5.13 HX Alarms............................................................................................................................................. 182
7.5.14 HXn Alarms ........................................................................................................................................... 183
7.5.15 QX Alarms ............................................................................................................................................ 185
7.5.16 GX Alarms ............................................................................................................................................ 186
7.5.16.1 GX Tri-Band .............................................................................................................................. 186
7.5.16.2 GX-Quad Band Alarms ............................................................................................................... 189
Management Using Any Standard SNMP Manager ................................................................................. 192
8.1 SNMP Destination Address Configuration ......................................................................................................... 192

8.2 Modifying the Read/Write Community Parameters ............................................................................................. 194
8.3 SNMP Management using any Third Party SNMP Manager ............................................................................... 195
8.4 Loading the MIB Files ...................................................................................................................................... 195
8.5 Viewing the Traps ........................................................................................................................................... 196
8.6 Binding Table.................................................................................................................................................. 197
8.7 Example of Trap Binding for a Specific Setup .................................................................................................... 201
8.8 Monitoring the Managed System ...................................................................................................................... 203
8.9 List of Traps .................................................................................................................................................... 204
8.10 List of MA Optional Device Traps ..................................................................................................................... 221
Appendix A: MA1000/MA2000 Manual Device Configuration................................................................. 222
9.1 Initial Configuration (Commissioning) Steps ...................................................................................................... 222

9.1.1 Phase 1 Commissioning Account for Fiber Loss.................................................................................... 222
9.1.2 Phase 2 Commissioning Prepare System for RF Source ....................................................................... 223
9.2 MobileAccess Headend, MA1000 and MA2000 ................................................................................................ 224
Table of Contents
Page 8
9.2.1 RIU and Signal Conditioner Configuration and Control ............................................................................. 225
9.2.1.1 Manually Defining RIU-4 Type .................................................................................................... 225
9.2.1.2 Standard Conditioner (BTSC/BDAC) Settings .............................................................................. 226
9.2.1.3 BTSC LTE 700 MHz................................................................................................................... 228
9.2.2 RIU-12 and Signal Conditioner Configuration........................................................................................... 231
9.2.2.1 CMU Basic Configuration ........................................................................................................... 232
9.2.2.2 BTSC-12 Configuration .............................................................................................................. 234
9.2.3 Base Unit Configuration ......................................................................................................................... 239
9.2.4 RHU Configuration................................................................................................................................. 241
9.2.5 Add-On Configuration ............................................................................................................................ 244
9.2.5.1 1200 Add-On Configuration ........................................................................................................ 244
9.2.5.2 LTE 700 Add-On Configuration ................................................................................................... 246
9.3 MobileAccessHX/ HXn Device Configuration..................................................................................................... 248
9.3.1 HX Indoor/Outdoor Device Configuration ................................................................................................. 248
9.3.1.1 Basic Setup Procedure ............................................................................................................... 249
9.3.2 HXn Device Configuration ...................................................................................................................... 253
9.4 MobileAccessGX Device Configuration ............................................................................................................. 256
9.4.1 Accessing GX Configuration Options ...................................................................................................... 256
9.4.2 Basic Setup Procedure .......................................................................................................................... 257
9.4.3 Configuring GX Quad-Band External Alarms ........................................................................................... 263
Table of Contents
Page 9
1 Introduc tio n
CMAs (Corning MobileAccess) System Controller (SC-450) is a centralized, system-level Element
Management device that provides comprehensive end-to-end, single source setup and management of CMA
DAS System elements.
Each SC-450 directly interfaces to a number of CMA headend devices through which their hosted
remote-end devices are also available. A controller Web session from any computer on the network
provides access to all headend and remote-end elements for complete system management.
A commissioning Wizard automates the commission procedure for the Remote Interface Unit (RIU) modules
(BTSCs/BDACs) and the MA1000/MA2000 Remote Hub Unit (RHU) devices. The Wizard can run
independently, on default settings and requires minimal user intervention.
The SC-450 minimizes downtime by detecting problems in real-time, and optimizes site coverage by
enabling adjustment of system device parameters according to specific site conditions.
Scalability for larger sites is provided by installing several SC-450 controllers in a Master-Slave
configuration that also provides single-source management via the Master controller.
1.1 Key Features and Capabilities

Device Support
Headend devices - each Controller directly interfaces to (a maximum of) 16 MobileAccess headend
devices
End-to-end auto-detection of all CMA devices:

o MobileAccess headend equipment:
RIU (Radio Interface Unit): RIU-12; RIU-4; RIU-IM; RIU-Lite
PAU-6 (6 Channel Power Attenuation Unit)
Optical Units: BUs (Base Units), OCHs (Optical Central Hubs)
o MobileAccess1000 and MobileAccess2000 remote-end equipment:
Low-Power Indoor Remote Units:
- RHU (Remote Hub Units) service specific dual-band units
- AO (Add-On Units) expansion unit with additional service
- TSX/QSX/QX (Tri-band Quad-band) remote end units
Medium-Power Indoor/Outdoor Remote Units:
- HX - Medium Power (up to 2W), Tri-band or Quad-band remotes
- HXn Medium Power 2W overlay remote end units
High-Power Outdoor Remote Units:
- GX High-Power (up to 40W), Tri-band and Quad-band remote end units
WMTS solution components
EC560 solution components
FT-350 Solution components
MobileAccessVE solution components
o
o
o
o
Scalable Master/Slave configuration of up to 8 Slave controllers per Master (with single-source

management via Master)
Key Features and Capabilities
Page 10
Management and Configurations
Web Management GUI intuitive, graphical, commissioning, real-time monitoring, diagnostics and
configuration of MobileAccess converged DAS networks
Simply setup via the Commissioning Wizard:

o Auto-detection of all un-commissioned MA1000 and MA2000 devices
o Simple automatic commissioning procedure of MA1000/MA2000 devices with minimum user
intervention setup Wizard can run on default value and generates status logs
o User configurable commissioning criteria
o Generated summary reports of the commissioning procedure results
Enhanced Users Management & security:

o Up to 32 users groups can be created per controller, with 20 users (of varying access levels) per
group (for a maximum of 500 users per controller)
o Users Accounts in each group can be managed only by the Group Administrator
o Each user is assigned one of six predefined access levels and a dedicated password
o Six (hard coded) Access Levels, where each level enables access to limited configuration parameters
and tabs.
o Compartmentalization each user level has limited security access, where no one user can see all
user allocation.
o User Activity Log for additional security, user action can be tracked via the User Activity Log so that
any configuration changes or session access can be tracked to the relevant user
o Multi-user sessions supports up to 3 simultaneous user sessions
o Stronger passwords password assigned to each user is subjected to strength check
o Secured Connection support via Mozilla 1.7 WEB browser (over Sun Solaris OS environment)
Single source management and software upgrade SC-450 Slaves are managed and upgraded (single
source upgrade for SC-450 Version 5.0 and higher; i.e. from V5.3 to V5.4) via a single connection to the
Master SC-450
Intuitive display providing status at a glance:

o Hierarchical topology display that includes status icons
o Base Line option that continues to show disconnected devices until they are disabled (as irrelevant)
o Heart-beat notifications (configurable) - maintain proper remote connection to the site
MA 410 Controller Compatibility
Compatible with the 410 Slave Controller loaded with the latest SW version available for the 410 Controller
(version 4.7 Build 5.6).
Note that additional devices and functionalities supported in the SC-450 v4.0 and above are not supported by
the 410 controllers (e.g. Quad-band support, RIU-12, HX and GX remotes, MobileAccessVE).
Key Features and Capabilities
Page 11
1.2 System Requirements

1.2.1
Web Client Requirements
System requirements for running SC-450 Web Client:
Release v5.4 has been tested and verified to operate on the following Operating Systems OS: Microsoft
Windows 7 on x86 (32-bit); Windows XP on x86
Screen resolution: 1024 x 768 pixels min

RAM: 2GB min
Intel Core 2 Duo equal functionality
The client device should not be running along with applications that are CPU or memory-intensive
1.2.2
Supported Browsers
Release v5.4 has been optimized to operate on the following browsers:
Microsoft Internet Explorer 7.0, 8.0 and 9.0 (For proper display on IE 8.0 use compatibility mode by
selecting Tools -> Compatibility View Options, and Add the SC-450 web-site 10.0.0.1)
Mozilla v1.7 and Firefox 3.6.18 (runs over Sun Solaris OS environment).
Mozilla Firefox 5.0 and 13.0
Google Chrome 19.0.01084.56 (Some screens may not appear optimal, but should not prevent the user
from interacting with the user interface.)
1.2.3
Remote Access Requirements
Remote access to the System Controller v5.4 is recommended to be accomplished using the following:
LAN Ethernet connection to the System Controller with a minimum connectivity and throughput capability
of 256 Kbps.
Wireless Modem with a minimum connectivity and throughput capability of at least 256 Kbps.
System Requirements
Page 12
1.3 System Controller Specifications

1.3.1
Environmental and Regulatory Specifications
1.3.1.1
Temperature and Humidity
The environmental specifications listed below are relevant to all GEN II devices.
Operating
Storage
Temperature
0C to +50C (32F to 122F)
-20 C to 85 C (-4C to 185C)
Humidity
95% (non-condensing)
95% (non-condensing)
Table 1-1: Temperature and Humidity Specifications
1.3.1.2
Safety and Regulatory Approvals
Table 1-2 describes the applicable Regulatory approvals for the SC-450.
Regulation/Standard
Category
Approval
US (FCC)
EMC
FCC 47CFR Part 15 Subpart B

Europe (CE)
EN 301489
Safety
ISO
UL 60950-1
EN 60950-1
ISO 9001: 2000
ISO 13485: 2003
Table 1-2: Safety and Regulatory Approvals
System Controller Specifications
Page 13
1.3.2
SC-450 Power Requirements
1.3.2.1
General Power Safety Instructions
Be sure to disconnect all power sources before servicing.

Use only UL approved power supplies.
Use only the power cables (AC and DC) provided with the unit to connect the power supply to the SC-450.
1.3.2.2
Power Requirements
Table 1-3 describes the basic power requirements of the SC-450, as well as the 410 controller that are to be
taken into consideration designing for system level protection mechanisms (UPS, fuse protection, etc.). The
SC-450 requires fuse protection.
Voltage Input
Power
Consumption
Maximum Current
Consumption
36 to 60 VDC
20W (Max)
0.2A
Table 1-3: SC-450 Power Specifications
1.3.3
Physical Specifications
Table 1-4 describes the physical specifications of the SC-450. The SC-450 is intended to be installed in a
standard 19-in rack and requires 1U of rack space.
Dimensions (H
x W x D)
4.44cm x 48.26cm x 29.97cm (1.75 x 19 x 11.8)
Weight
2.6Kg (5.8lb)
Table 1-4: Physical Specifications
Page 14
1.3.4
Default Parameters
1.3.4.1
Network Parameters
Table 1-5 identifies the default settings for each of the Network Ethernet ports located on the front panel of
the SC-450.
Port Name
Configuration
LOCAL
DHCP: Server (this local port is set by default set to

act as a DHCP Server and provide an IP address to
the connected computer so no configuration of the
computer is required)
Factory defaults:
IP: 10.0.0.1
Subnet Mask: 255.255.255.0
DHCP: Client, or Static IP (default)
Factory defaults:
LAN
IP: 10.1.1.1
Subnet Mask: 255.255.255.0
Gateway: 10.1.1.10
SRV 1
Same as LOCAL Normally used for EC560 or

MobileAccessVE (via FT-350) management
SRV 2
For Future Use. Disabled.
Table 1-5. Default Network Port Parameters
1.3.4.2
The System Administrator or Super User
There is only one System Administrator or Super User. This user has the highest access level, does not
belong to any group and is the only user that can create groups.
User Name = admin (cannot be modified)
Password = default provided by Corning MobileAccess (and should be changed immediately).
Group none (leave blank)
Upon initial login, the System Administrator should create user groups. Each new group is assigned by the
system a Group Administrator that manages the users in his/her group (see details in section 6.1.3).
1.3.4.3
Default Group Admin User
When groups are created (by the admin user), a default Group Administrator is automatically created for each
group, where the Group Administrator User Name and Password are based on the group name. The
group_Admin (note capital A in Admin), is authorized to create and manage the users for his/her group. See
section 6.1.3 for detailed description of default group_ Admin user.
Page 15
1.3.5
Front Panel Interfaces and Indicators
The front panel of the SC-450 contains the interfaces to the network, alarm status LEDs, and LCD display.
SC-450 Front Panel
1.3.5.1
Figure 1-1
Front Panel Interface Ports
Table 1-6 provides the descriptions for the SC-450 front panel interface ports.
Port Name
Configuration
LOCAL
Local WEB management connection. Can also be used as an additional network

connection. Supports static and dynamic (DHCP server) IP address setting.
LAN
Network connection. Supports static and dynamic (DHCP client only) IP address
setting.
SRV 1
Local port specifically used only for inbound management of MobileAccessVE and
EC560 equipment.
SRV 2
Future option. Disabled.
RS232
Used in Master-Slave configurations, to connect this controller as a Slave to the rearpanel of a SC-450 Master Controller. (See section 2.2)
USB Port
PCMCIA
Table 1-6. SC-450 Front Panel Interface Definition
Page 16
1.3.5.2
Front Panel LED Indicators
Table 1-7 provides the descriptions for the SC-450 front panel LED indicators.
LED
PWR
Run
Configuration
CONSTANT GREEN - Power supplied to unit
OFF No power is supplied to the unit
BLINKING GREEN Power supplied to unit, boot up sequence is
complete and unit is functioning as intended
OFF No power is supplied to the unit
Minor
RED - Indicates a minor alarm in the system (e.g. a single RHU failure
in a multi-RHU site).
OFF No alarm in the system.
ALARMS
Major
RED Indicates a major alarm in the system (e.g. multiple RHU
failures in a multi-RHU site).
OFF No major alarms in the system.
Refer to the Alarm definitions for information on what alarm is
considered Major and/or Minor.
Table 1-7. SC-450 Front Panel LED Descriptions
1.3.5.3
Front Panel LCD
The LCD display alternatively displays two types of information:
The IP address and subnet mask of the LOCAL port.

Alarm status of the devices managed directly by the SC-450 (details following )
SC-450 LCD Display
Figure 1-2
Details on the alarm status of devices:

The alarm information corresponds to the Major/Minor LEDs. The display slightly differs depending on
whether the SC-450 is installed as a Master (Standalone) or as a Slave (Remote):
Master (Standalone) - Both upper and lower LCD rows are active.
Slave (Remote) Controller - Only the upper LCD row is active
Page 17
Upper Row: Status of devices directly managed by the controller (i.e. not through other controllers or through
another management interface such as the MobileAccessVE), where status can be indicated by one or two
(toggled) messages described below.
Message
Description
LCL AUX MAJOR
Local Auxiliary Fault (Auxiliary faults are always major.)
LCL RHU MAJOR/MINOR
Local RHU Fault. Fault at the remote-end unit managed

by the controller.
Lower Row: Shows overall status of up to (8) remote sites whose status is indicated by the following letters.
This row is only enabled in Master /Standalone) Controllers.

Display
Description
Communication Error
Normal
m (lower case)
Minor malfunction at the remote site
M (upper case)
Major malfunction at the remote site
-- (blank)
Port not configured/connected to a remote site
Example:
LCD of Master SC-450 with four ports connected to Slave controllers.
Example of SC-450 LCD Display
Figure 1-3
Where the message in the lower row should be interpreted as follows:
Building #1 = Normal (OK)

Building #2 = Not configured in the system (_)
Building #3 = Communication Error
Building #6 = minor malfunction
Building #8 = Major malfunction
Page 18
1.3.6
Rear Panel Interfaces
The SC-450 rear panel provides connections to directly connected elements, power and alarms.
SC-450 Rear Panel
Figure 1-4
Table 1-8 provides descriptions for the SC-450 rear panel port interfaces.
Interface
Description
RS485 (Ports 1-8)
RJ-45 connectors utilized as direct interfaces for up to eight headend devices

such as Base Units (BUs), Radio Interface Units (RIUs), WMTS RIM Main unit
and FT-350 Optical Central Hubs (OCH) in any combination.
RS485/RS232
(Ports 9-16)
RJ-45 connectors, SW configurable ports. Can be used either for one of the
following:
Default Settings. Direct interfaces for MobileAccess DAS headend devices

Slave controllers (requires software configuration see section 2.7.3.1)
PWR
DC power input: 36 to 60VDC, 0.2A max.
DIAG
Reserved for MobileAccess service personnel.
AUX ALARMS
D-Type 26 pin connector utilized to support up to eight inputs for alarms from
auxiliary devices (see section 2.6.1)
ALARM OUTPUT
D-Type 15 pin connector utilized to support BTS/Repeater dry-contact alarms

outputs. Used with NMS-BTS/DB15-open cables (see section 2.6.2)
Internal Modem
Table 1-8: Rear Panel Interface Definition
Page 19
1.4 Standalone and Master/Slave Topology

1.4.1
Standalone Topology
Figure 1-5 provides a high level representation of the connections between a single SC-450 and the rest of
the MobileAccess DAS architecture components.
Example of System Controller Basic Connectivity Diagram
Standalone and Master/Slave Topology
Page 20
Figure 1-5
1.4.2
Master/Slave Topology
For larger systems, the SC-450 can provide monitoring and management capabilities for one (SingleBuilding Topology) or more (Multi-Building Topology) remote locations via connections to Slave SC-450 or
410 controllers:
Single-building Topologies: used in buildings requiring more coverage than can be provided by the Base
Units supported by a single controller. The signal source is located in the same building where the wireless
coverage is required.
In this topology, all the controllers are usually installed in a single location in the communication room.
Only the Master controller is connected to the network and the Slaves are connected to the Master.
System Controller Basic Master/Slave Connectivity Diagram
Figure 1-6
NOTE: There may be multiple standalone and independent controller configurations in a single building
(controllers are not inter-connected as Master and Slaves). This is usually the case in buildings where the
existing network infrastructure enables independently connecting any number of SC-450 units directly to the
network.
Page 21
Campus Topologies: used when coverage and monitoring need to be extended to multiple buildings. Only
the SC-450 Master is installed in the main communication room, adjacent to the signal source, whereas
the SC-450/410 Slave controllers are installed in the remote buildings and connected to the Master via the
MA 330 System.
Figure 1-7 provides a connections diagram illustrating how to connect the Master and Slave controllers
with the MA 330 System.
NOTE: Refer to the MA 330 System User Manual for specifics on the MA 330 System components and
capability.
Multi-Building Master/Slave Architecture
Figure 1-7
Page 22
2 Ins ta lla tion G uidelines

This chapter provides two types of descriptions:
Quick Installation Procedure - overview of the physical installation steps for SC-450 hosted elements and
basic setup controller setup.
Detailed installation procedures for each element.

Before you start!
Before installing the SC-450, it is required to perform system site preparation procedures such as fuse
protection, power consumption, space requirements, and design of the MobileAccess DAS equipment headend and remote end (e.g. MA1000/MA2000/VE/HX/GX/EC560/FT-350, etc.).
After completing these procedures, follow the basic steps for installing the SC-450 as described in this
section.
For specific guidelines on infrastructure planning, design and installation, please consult with a MobileAccess
Project Manager or MobileAccess approved Installer.
2.1 Quick Installation Procedure

This section provides a brief overview of the installation procedures for various devices. References are made
to detailed sections.
The installation procedure consists of two phases:
a)
Physical Installation - Consists of the mounting of the controller and physical connections to the
MobileAccess DAS devices.
b)
Basic commissioning of the SC-450 to allow remote access.
2.1.1
Physical Installation Steps
1. Install the SC-450 in a 19-in rack using standard rack mounting screws (not supplied).
2. Apply DC power (36 to 60 VDC, 0.2A max) to the SC-450 Rear Panel PWR connection (see section 1.3.6).
If needed, use the supplied 2-Pole terminal bare wire power connector.
3. Connect any applicable MobileAccess DAS architecture components as described in the following subsections.
4. Connect the AUX ALARMS and ALARM OUTPUT connectors using the DB-26 and DB-15 cables provided
to the dry-contact application. Refer to section 2.6 for more details.
2.1.1.1
Slave Controller Connections
a)
Connect SC-450 Slave Controller front panel RS232 port (refer to section 1.3.5.1 for ports) to the rear
panel RS485/RS232 ports 9-16 using the provided DB-9 to RJ-45 cable. Refer to Section 2.2 for more
details.
b)
For Slave Controllers located at remote locations and connected using MobileAccess 330 System:
i.
Connect the Master SC-450 rear panel ports 9-16 (section 1.3.6) to the 330 Main COM 1/COM 2
ports using the RJ-45 to RJ-45 cable.
Quick Installation Procedure
Page 23
ii.
Connect the Slave Controller front panel RS232 port (1.3.5.1) to the 330 Remote Unit COM Port
using the provided DB-9 to RJ-45 cable.
2.1.1.2
RIU Connections
Connect
To
RIU-4/RIU-IM/RIU-Lite rear panel RS485

Com Port
SC-450 rear panel RS485 ports 1-8 or RS485/RS232

ports 9-16 (see section 1.3.6)
RIU-12 front panel CMU (Control Module

Unit) RS485 port
2.1.1.3
PAU-6 Connections
Connect
To
PAU-6 front panel RS485 Com Port

(located on PCMU module)

ports 9-16 (see section 1.3.6)
2.1.1.4
BU and OCH Connections
Connect
To
BU rear panel RS-485 Com Port

ports 9-16 (see section1.3.6)
OCH rear panel To SC-450 port
Refer to sections 2.3.1 and 2.3.2 for more details.
2.1.1.5
WMTS System Connections
Of the WMTS components, only the RIM-Main unit is directly connected to the SC-450.
Connect
To
RIM-Main rear panel RS-485 Com Port
Any of the RS485 ports 1-8 or RS485/RS232 ports 9-16

on the SC-450 rear panel (see section 1.3.6).
Refer to section 2.3.4 for more details.
2.1.1.6
EC560 Solution Connections
Of the EC560 solution, only the EHU is directly connected to the controller. The EC560 can be connected to
the SC450 either via a dedicated connection (SRV1 port) or through the network.
a)
If EHU and SC-450 are on the network connect the EHU MGMT port to the LAN. See section 2.5.1
b)
EHU and SC-450 via dedicated connection connect according to section 2.5.2
Page 24
2.1.1.7
FT-350 Connections
a)
Connect the OCH To SC-450 to RS485 ports 1-8 or RS485/RS232 ports 9-16 located on the Controller
Rear Panel. Refer to section 2.3.5 for more details.
b)
For management access to remote elements that fed by the FT-350 (i.e. MobileAccessVE elements),
connect according to section 2.4.2.
2.1.1.8
MobileAccessVE Connections
The MobileAccessVE system is not directly connected to the SC-450 Device port. MobileAccessVE can be
connected in the network in one of two ways:
a)
Without FT-350 out-of-band management solution. See 2.42.4.1.
b)
With FT-350 in-band management solution. See 2.4.2.
2.1.2
Basic Setup and Configuration
1. Connect a computer (i.e. laptop) directly to the LOCAL Network Ethernet Port on the SC-450 front panel
using the supplied Ethernet/RS-485 communication cable (P/N 705900003).
If the computer does not connect to the network, verify that the computer is configured as a DHCP client
(usually computer default settings).
2. Launch a standard Web browser (as specified in section 1.2.2) and point it to: http://10.0.0.1.
First time login:
o User Name: admin
o Password: supplied with your system
o User Groups: leave empty
3. Secure access to the system:
o Modify the default admin password provided with the system (see section 6.1.5
o Login again using the new password.
o Create the required User Groups. See section 6.1.1.
A default Group Administrator is automatically created along with each new group. The Group Admin can
manage all users in his/her Group. See section 6.1.2.
4. Configure the SC-450 General System Parameters (i.e. Name, Controller Type and Date/Time) by doubleclicking on the controller in the topology tree (see section 2.7.2).
5. If your installation includes Slave Controllers, configure the SC-450 (designated as Master) RS485/RS232
ports for slave controllers as follows:
Double-click Controller in the Topology TreeSelect Modify button in the Slave Mask paneCheck the
Slave option for the applicable port (see Section 2.7.3.1 for more details).
6. If remote WEB GUI access to the SC-450 is required, configure the SC-450 LAN port as follows (refer to
section 2.7.2 details):
Click the Management TabClick IP Settings from the left pane Click Modify button in the LAN Port
area Change Network Settings as required
7. If remote SNMP access to the SC-450 is required, configure the SNMP parameters and traps destination
address as follows (refer to section 8 details):
Page 25
Click the Management TabClick SNMP Config from the left pane Click Modify buttons in the SNMP
Configuration area and Add New or Remove in the Traps Destination List area as required
8. Commissioning:
o For MA1000/MA2000 elements - run Commissioning Wizard according to Chapter 3.
o For additional CMA DAS components commission elements manually according to Chapter 4.
2.2 Master/Slave Topologies Controller Connections

Two types of SC-450 topologies are supported, where the connections vary depending on the topology:
Single-building Topology RF signal source only in the building where the wireless coverage is required
Multi-building Topology RF signal source is extended from Main building to two additional Remote
buildings using the 330 System.
For more information refer to section 1.4.
2.2.1
Single-Building Master/Slave Topology
This configuration is used in buildings that require more coverage than can be provided by the Base Units /
RIUs supported by a single controller (up to 16 devices ports). In this case, one SC-450 Controller is
configured as the Master and other SC-450 or 410 Controllers as Slaves and it is required to configure the
Master ports 9-16 (to which Slaves are connected) for Slave Controllers connections (See section 2.7.3.1.
In this topology, all the controllers are usually installed in a single location in the communication room. Only
the Master controller is connected to the network and the Slaves are connected to the Master.
You may have multiple standalone, independent controller configurations in a single building (controllers are
not inter-connected as Master and Slaves). This is usually the case in buildings where the existing network
infrastructure enables independently connecting any number of SC-450 Controllers directly to the network.
Master/Slave Topologies Controller Connections
Page 26
Connect Master to Slaves using the (provided) DB-9 to RJ-45 cables:

From Master SC-450
To each MA 410 / SC-450 Slave
Using
Rear panel ports 9-16

(RS485/RS232), one port per Slave
RS232 front panel port
Provided DB-9 to RJ-45 cable
SC-450 Master/Slave Connections
Figure 2-1
Page 27
2.2.2
Multi-Building Master/Slave Topology
Where coverage and monitoring is provided to a number of buildings, a controller is usually installed in the
communication room of each building and are interconnected via a 330 system. The controller is installed in
the same location (and preferably adjacent) to the Base Units.
The SC-450 Master Controller is installed in the building to which the signal sources are directly connected.
The SC-450 or 410 Controllers (configured as) Slaves are installed in the remote buildings and connected to
the Master controller using the 330 System.
This section provides information on how the Master and the Slave controllers are configured with the 330
System.
The RF signal and control signals from the Main building is routed to the remote buildings over fiber optics
using the 330 system consisting of 330 Main (in the Main building) and 330 Remote units (in the Remote
buildings).
Note the following:
SC-450 Master is connected to 330 Main

SC-450 Slaves are connected to 330 Remotes
SC-450 Master-Slave Topology
Figure 2-2
Page 28
2.2.2.1
Master SC-450 to 330 Main
Configure the SC-450 ports to which the 330 Main is connected as Slave ports (section 2.7.3.1).
From SC-450 Master
To MA 330 Main
Using
Any two ports 9 to 16 - one per

MA 330 Remote
COM 1 and/or COM 2 port -one

per MA 330 Remote
Provided DB-9 to RJ-45 cable.
Connecting the Master SC-450 to the 330 Main
2.2.2.2
Figure 2-3
Slave SC-450 to 330 Remote Unit
Connect the SC-450 to MA 330 Remote unit as follows:

From SC-450 Slave
To MA 330 Remote
Using
COM port
330 Remote Unit Connections to Slave Controller
2.2.2.3
Figure 2-4
Base Unit to 330 Remote Unit
Perform the following connection to ensure that the remaining MobileAccess DAS components can also be
managed from the Master SC-450:
Page 29
From Base Unit (at Remote

Location)
To MA 330 Remote
Using
Rear panel COM PORT RS485
330 Remote Unit Connections to Remote Base Unit
Figure 2-5
Page 30
2.3 Headend Device Connections to SC-450

This section provides the following examples of MobileAccess DAS architecture components directly
connected to the controllers Device ports:
Radio Interface Unit (RIU)

Base Unit (BU)
Wireless Medical Telemetry System (WMTS)
FT-350 System
2.3.1
RIU to SC-450 Connection
Corning MobileAccess offers an array of RIU (Radio Interface Units) products, where the location of the
management port for the legacy products and the latest addition to the product line, RIU-12 differ.
2.3.1.1
RIU-12 Management Connections
Connect the SC-450 to the RIU-12 as follows:
From SC-450
To RIU-12
Using
Rear panel ports 1-8 or 9-16
Front panel CMU (Control

Module Unit) RS485 port
RJ-45 to RJ-45 cable
SC-450 to RIU Connections
Headend Device Connections to SC-450
Figure 2-6
Page 31
2.3.1.2
RIU-4, RIU-IM and RIU-Lite Management Connections
The example illustrates an RIU-4 connection, where RIU-IM and RIU-Lite connections are similar.
Connect the SC-450 to the RIU as follows:
From SC-450
To RIU
Using
Rear panel ports 1-8 or 9-16
Rear panel RS485 port
SC-450 to RIU Connections
Figure 2-7
Page 32
2.3.2
PAU-6 to SC-450 Connections
Connect the SC-450 to the PAU-6 as follows:

From SC-450
To PAU-6
Using
Any available rear panel ports 1-16
Front panel PCMU module RS485

COM PORT
SC-450 to PAU-6 Connections
2.3.3
Figure 2-8
BU to SC-450 Connections
Connect the SC-450 to the BU as follows:

From SC-450
To BU
Using
Any available rear panel ports 1-16
Rear panel RS485 COM PORT
SC-450 to BU Connections
Figure 2-9
Page 33
2.3.4
WMTS to SC-450 Connections
The RIM-1400 unit is managed via the RIM-Main and is not directly connected to the SC-450.
Connect the SC-450 to the RIM-Main as follows:
From SC-450
To WMTS RIM-Main
Using
Any available rear panel RS484 ports 1-8

or 9-16
Rear panel RS485 COM LINK port
SC-450 to RIM-Main Connections
2.3.5
Figure 2-10
FT-350 Connections to the SC-450
FT-350 solution management consists of two types of management connections that must both be
implemented for a full management solution:
Management of FT-350 system elements (OCH and ORU) - via direct connection between the OCH and
SC-450.
Management of elements (i.e. VE VCU and VAPs) fed by the FT-350 system
Both of these connections are required for full management of the FT-350 system and Hyperlink
connection to the VE hosted elements.
FT-350 System Elements management connection
From SC-450
To OCH
Using
Any available rear panel RS485 ports 1-8

or 9-16
Rear panel RS485 To SC-450 port
Page 34
SC-450 to OCH Connections
Figure 2-11
NOTE 1: The OCH and corresponding ORUs will be displayed in the tree and full management access will be
provided.
NOTE 2: Refer to the relevant section (i.e. VE Elements fed by FT-350 section 2.4.2) for instructions on
connections for managing the elements fed by FT-350).
Page 35
2.4 MobileAccessVE Management Solution

The MobileAcessVE system provides in-building coverage solution over existing LAN cabling infrastructure.
MobileAccessVE is suitable for both small and large installations:
In small installations - a single VE system is deployed

In large enterprises and campus installations multiple VE systems are deployed and fed from a single RF
source distributed by FT-350 Optical Fiber Backbone links.
The IPs of Master VCUs in both types of deployments (with and without FT-350) are auto-discovered by the
SC-450 and displayed as hyperlinks in the network topology tree. However, to open a Web Management
session to any VE element, the Master VCUs must be in the same subnet as the SC-450. If the Master VCUs
and SC-450 are NOT in the same subnet as the controller, the elements will be auto-discovered and will be
displayed (as hyperlinks) in network topology but without access to Management GUI.
The management connections differ for each type of installations. The following sections describe the
management connections for both types of MobileAccessVE deployments (without FT-350 Fiber Backbone
system or with FT-350).
MobileAccessVE Management Solution
Page 36
2.4.1
MobileAccessVE Deployed without FT-350 Fiber Backbone
This solution is relevant for smaller scale enterprise environments. The MobileAccessVE VCU elements are
not directly connected to the SC-450 Device port; however, the Master VCU is physically located near the SC450 controller and is on the same LAN.
NOTE: The default IP address of each Master VCU is 192.168.1.1/24. The user should change the default IP
address.
The VE elements are managed as follows:
The Master VCU is auto-discovered by the SC-450 (located on same sub-net) and the corresponding IP
address is displayed as a Hyperlink in the topology tree (see section 4.5 for Configuration dialogs).
Click on the Hyperlink address to open a management session to the element.
SC-450 and MobileAccessVE Management Connections
Page 37
Figure 2-12
2.4.2
MobileAccessVE Deployed with FT-350 Fiber Backbone
In large installations and campus environments, coverage requirements are supported by multiple VE
systems where some of the systems are installed in the Remote locations. FT-350 is used to feed all VE
systems from a single RF source by extending the RF signal from the headend to the remote VE systems
over optical fibers.
In these types of installations, the VE system elements are managed via an in-band management connection
created between the SC-450 and the OCH (interfacing using an Ethernet Switch/Hub).
MobileAccessVE with FT-350 Management connections
1. Verify that the FT-350 is connected to the SC-450 according to section 2.3.5.
2. Perform the connections according to the table below:
From
To
OCH rear panel Ethernet Ports 1-4
Network Hub
SC-450 front panel SRV-1 port
Ethernet Switch/Hub (to which OCH is connected)
ORU rear panel Ethernet port
Master VCU front panel Management port
SC-450 and MobileAccessVE Management Connections with FT-350 Solution
Figure 2-13
3. To enable auto-discovery, define the IP address of each Master VCU in the same subnet as the SC-450
SRV1 (see section 2.4.3).
The FT-350 components and hosted MobileAccessVE elements can now be managed through the standard
SC-450 Web management procedure.
Page 38
2.4.3
Defining the Master VCU IP Address in the SC-450 Subnet
To change the IP address

1. Locally connect to the Master VCU using an Ethernet cable.
2. On the computer (i.e. laptop), open a web session to the Master VCU enter default IP address in
address bar (192.168.1.1).
3. Enter login info user name and password) as provided by system administrator.
4. Click on the Management tab and then IP Settings sub-tab.
MobileAccessVE IP Settings Tab
Figure 2-14
5. Click the Modify button and define the IP Address in the same subnet as the SC-450 controller.
6. Click OK.
Page 39
2.5 EC560 Management Connections

The EC560 can be connected to the SC-450 either via a dedicated connection (SRV1 port) or through the
network.
NOTE: The default IP address of each EHU is 192.168.x.x/24. Once the EHUs are detected, the user should
change the IP address of each of the units. The IP address can be added manually in the Network Topology
tree (refer to section 4.3.1).
2.5.1
EHU and SC-450 Connections via Network
Connect as follows:
From
To
EHU front panel MGMT port
LAN
If the EHU (MGMT port) and the SC-450 are connected on the same LAN, the EHU is automatically
discovered by the SC-450 and displayed in the Topology Tree.
EHU and SC-450 Connections via Network
EC560 Management Connections
Figure 2-15
Page 40
2.5.2
EHU and SC-450 via a Dedicated Network
To connect the EHU in a dedicated network connection

Connect as follows and refer to Figure 2-16:
From
To
SC-450 SRV-1 port
Network Hub (dedicated to the relevant Corning MobileAccess

devices)
EHU front panel MGMT port
Same HUB (via the network)
NOTE: If the hub configuration does not support broadcast and the EHU is not displayed in the Network
Topology tree, the EHU IP address can be manually added (refer to section 4.3.1).
The following figure shows an example of a dedicated configuration with the same or different subnets.
Example of SC-450 and EHU Connections via Dedicated Network
EC560 Management Connections
Page 41
Figure 2-16
2.6 SC-450 Auxiliary Input and Alarm Output

Connections
2.6.1
Auxiliary Input Connections
This Auxiliary connector can be used to monitor up to eight auxiliary connections such as fire-alarm, airconditioning alarm, open-door alarm, etc. The connections are normally open.
Connect the relevant alarms according to the connector pinout described in the following table.
Pin Number
Auxiliary Alarm
Pin Number
Auxiliary Alarm
1, 26
8, 9
2, 3
10, 11
4, 5
12, 13
6, 7
14, 15
Table 2-1: Auxiliary Input Connections
2.6.2
Alarm Output Connections
The controller can provide Major and Minor output alarms. These alarms can be connected directly to the
auxiliary input of the Base Station, or to any other dry-contact application.
NOTE: If only one alarm is required (Minor or Major) an external connection of a wire jumper between pins 8
and 13 is necessary (normally closed).
Connect the relevant alarms according to Figure 2-17 and Table 2-2 which describe the connector pinout.
Connector Pinout
Pin
1-6
7
8
11
12
13
15
Figure 2-17
Description
Not Used
Minor Error Signal (Normally Open)
Major Error Signal (Normally Closed)
Major COM
Minor COM
Minor Error Signal (Normally Closed)
Major Error Signal (Normally Open)
Table 2-2: Auxiliary Alarm Output Port Pin Out Description
SC-450 Auxiliary Input and Alarm Output Connections
Page 42
2.7 Initial Controller Setup

This section provides the details on the basic setup and configuration of the SC-450 management interface as
outlined in Section 2.1.2. It is to be completed after the physical installation of the controller and connections
to the relevant devices has been completed as outlined in Section 2.1.1.
After completing this section, run the Commissioning Wizard according to Chapter 3.
IMPORTANT: The available tabs and options may vary depending on the access level used to open your
session
2.7.1
Initial Login and Setup
1. Verify that your computer Local Area Connection (Properties / TCP/IP / Properties) is set to obtains the
DNS Server Address Automatically.
2. Connect a computer (i.e. laptop) directly to the SC-450 LOCAL port via the supplied RJ-45 Ethernet cable
(P/N 705900003) as illustrated below.
Warning!!! Do NOT connect the SC-450 LOCAL port to a network
as its DHCP server can disrupt LAN IP addressing.
Computer Connection to the SC-450 Local Port
Figure 2-18
3. IP Address assignment on your computer:

o DHCP DHCP IP address assignment for your computer can take up to 15 min. to complete.
o Static IP addressing scheme - and select any IP address in the same subnet of the LOCAL port (e.g.
10.0.0.X, X= 2.255 if the LOCAL port is still configured to the factory default address: 10.0.0.1). The
current IP address of the LOCAL port is displayed on the SC-450 LCD screen.
Initial Controller Setup
Page 43
4. Open web browser and enter the SC-450 default IP Address (10.0.0.1) in the address bar.
Example of Local Port default IP Address
Figure 2-19
The SC-450 has been optimized for use on IE 7.0 and 9.0, Firefox 3.0 or later and Google Chrome.
NOTE: For proper display on IE 8.0 use compatibility mode by selecting Tools -> Compatibility View
Options and Add the SC-450 website 10.0.0.1.
The Login dialog appears.
Log in Dialog
Figure 2-20
5. First time access, enter the following authentication:

User Name = admin
Password = default provided with your system
Group = leave blank
NOTE: To prevent access with this user, it is highly recommended to immediately change the password
(Management tab, Security option) and login again using the new password. For information on password
changes, refer to section 6.1.5.
Page 44
2.7.2 Configure SC-450 LOCAL and LAN Port Network Settings for Remote
or Local Management
The SC-450 LAN port can be assigned a static or dynamic IP address in order for the SC-450 to be remotely
accessed across the customer LAN.
The SC-450 LOCAL port can also be assigned a static IP address and connected to the customers LAN for
remote management; however, for troubleshooting and service purposes, a local connection is
recommended.
NOTE: The IP address configuration options are provided on the Management, IP Settings pane. The same
pane also provides a Ping tool used for verifying access to other IP hosts.
To Configure SC-450 for Remote or Local Management
1. Open an SC-450 Web session.
2. Select the Management tab and then click IP Settings on the side bar menu.
Management-IP Settings Tab
Figure 2-21
Page 45
3. To change the LAN Port network settings, click the Modify button in the LAN Port Configuration Area. The
following dialog appears.
IP Settings LAN Port Modify Dialog
Figure 2-22
To Define
Do This
Static IP Address
Set DHCP as None.

Enter the IP Address, Subnet and Gateway.
Click OK.
Dynamic IP Address
Set DHCP as Client and click OK.
Page 46
4. To change the LOCAL Port network settings, click the Modify button in the LOCAL Port Configuration
Area. The following dialog appears. The LOCAL Port configuration settings are displayed on the SC-450
LCD.
IP Settings Local Port Modify Dialog
To Define
Static IP Address
DHCP Server
Figure 2-23
Do This
Set DHCP as None.
Enter the IP Address and Subnet.
Click OK.
Set DHCP as Server and click OK.
WARNING!!! If LOCAL port is set as DHCP Server, DO NOT

connect a network device, as its DHCP server can disrupt
LAN IP addressing. Only use this setting if using the port for
direct connection to a client device (i.e. PC).
Page 47
2.7.2.1
Ping Tool
A Ping Tool option is provided in the IP Settings pane. Use this tool to verify access to IP hosts (rather than
opening another application).
To use the available Ping tool
1. Click the Management tab and then the IP Settings menu option.
2. In the Ping work area, enter the IP address and the click the Ping button.
3. The validity/invalidity result of the IP address will appear in the Result: line.
Management-IP Settings-Ping Tool Option
Figure 2-24
Page 48
2.7.3
SC-450 Master/Slave Configuration
By default, all controllers are set as Masters a mode relevant to a standalone controller (with no slave
controllers) or a Master controller installed in a Master/Slave configuration.
Slave controllers can only be connected to the RS485/RS232 Ports 9-16 located on the rear panel of the SC450. By default, ports 9-12 of each Controller are configured as Device ports. Once connected, these ports
must be configured in the Master SC-450 to be used as slave ports.
2.7.3.1
Configure Slave Controllers
1. In the Network Topology tree, select the SC-450 Master controller. The selected controller configuration
options appear.
Configuring Slave Controllers for Master
Figure 2-25
Page 49
2. In the Slave Mask pane, click the Modify button and for each port (9 to 16) to which a Slave controller will
be connected, enable the Slave option. See Figure 2-26.
Slave Mask Dialog
Figure 2-26
3. Click OK to close the dialog. The configured Slave controllers will now be displayed in the Network
Topology along with the devices under their control.
Master and Slave Controllers in the Network Topology
Page 50
Figure 2-27
The defined Slave controllers will be displayed under the Master controller and will be identified according to
the user defined name.
2.7.3.2
Restoring a Slave Controller to a Master Controller Mode
If a controller is connected via its front 9-pin RS232 connector then it is automatically set as a Slave.
A Slave controller that is physically disconnected from its Master controller is restored to a Master controller
status upon RESET.
2.7.4
Configure Controller Settings
In the Network Topology, double-click on the relevant controller. The controller General tab is displayed,
where the Controller Mode is displayed as shown below.
Controller Mode in Controller General Tab
Figure 2-28
During initial setup and configuration, it is recommended configure the controller with the following system
parameters:
1. Assign the controller a recognizable Name that would indicate its location.
2. Verify that the correct Time and Date are set for the controller since events for devices under this controller
will be received with the set time and date.
3. Set the Controller Type according to your system (see following sections for details on Controller Type
options).
Page 51
2.7.4.1
Configuring the Controller System Parameters
1. In the Network Topology, double-click on the controller to be redefined. The controller General tab is
displayed.
Assigning Controller Name in General Tab
Figure 2-29
2. Click the Name field Modify button and type the controller name using up to 20 characters including
spaces.
3. By default, the controller is set to host standard MobileAccess devices that do not require a heartbeat.
However, if the controller is to monitor MobileAccess devices requiring heartbeat definitions set the values
accordingly and refer to the relevant sections.
o MA1000 and MA2000 Default standard devices. No other configuration is required.
o Heartbeat Enabled Enables a periodical trap indicating that the unit is operational see section
2.7.4.2. The trap is sent every number of minutes. (See section 8.5).
4. In the Time and Date area, verify the correct time (24 hour clock) and date are defined; to modify, click on
Modify and make the required changes in the invoked dialog:
o In the calendar, choose the date, using the <arrows> to scroll to the correct month if necessary
o In the Time field, set the hour and minutes
o Click OK.
5. Click the Base Line button. This sets all of the MobileAccess devices currently displayed in the Network
Topology pane as a reference and will continue displaying them (in gray) even if communication is lost
with a device.
Page 52
2.7.4.2
Configuring for Heartbeat Enabled Devices
This option is used for optional devices. This option enables a periodical trap indicating that the Repeater is
operational. The trap is sent every number of minutes.
1. In the Network Topology, double-click on the controller to be redefined. The controller General tab is
displayed.
2. Set the Controller Type as Heartbeat. The Configuration tab is enabled.
Controller Heartbeat Configuration Tab
Figure 2-30
o In this pane configure the following parameters:

o Heart Beat Interval Period of time between Heartbeat traps sending. The defined interval should be
the same for all Repeaters in the system.
Range: 1 to 59 minutes.
o HB Trap Destination Address: IP address to which traps forwarded by MA Optional device are sent.
o Site ID (Cascading Code). Repeater Network identification (35 alphanumeric characters).
o Longitude and Latitude Define exact location of the Repeater.
o The latitude/longitude format is shown below. Note that all US repeaters will have positive latitudes
and negative longitudes (Use 6 decimal places for the degree values).
o ('N/S ' | 'E/W ') (+|-) ddd.dddddd: (Latitude: N 39.006957 Longitude: W -94.532306) or Latitude: N
37.446823 Longitude: W -122.152390
Page 53
2.8 Auxiliary Device Setup

Auxiliary devices such as switches for power supplies, air conditioners or door-open indicators, which are
connected to the controller, can be monitored through LEDs displayed in the Web GUI.
The auxiliary device LEDs of each controller are displayed in the Aux Alarms tab of the controller Config
menu, when the corresponding controller is selected but only after the auxiliary device connections have
been configured as follows:
1. In the configuration tree, double-click on the SC-450 controller to be configured to open the controller
configuration dialog and select the Aux Alarms tab.
Controller Auxiliary Alarms Tab
Auxiliary Device Setup
Figure 2-31
Page 54
The enabled (relevant) connections are check-marked (i.e. 1, 2, and 4 in the example shown in Figure
2-32). The (user defined) name assigned to each connection is displayed alongside the connection.
Auxiliary Device Tab
Figure 2-32
2. To change the active connections and assigned names, click Modify.

3. Checkmark each of the Auxiliary pins to be activated, assign them identifiable names, and click OK. The
enabled Auxiliary connections will be check marked in the Auxiliary tab display.
Page 55
3 C o mmis s io ning W iz a rd fo r R IU a nd
MA 1000/MA 2000 Dev ic es
The Commissioning Wizard enables automatic basic setup of the MA1000/MA2000 system using an external
RF source. Elements are commissioned according to user selected criteria such as all devices, uncommissioned devices, per specified service, etc.
Any failures are logged and the user may re-attempt the process only on failed devices (or on the complete
system).
Features and Capabilities
Auto-detection of all un-commissioned RIU (BTSC/BDAC elements) and MA1000 and MA2000 devices
Default settings enabling minimal intervention by the user
The Commissioning Wizard is forgiving so that in cases of invalid operations or settings (by the user), the
wizard prompts the user to correct the problem and provides an appropriate suggestion.
Continuously provides status reports on all of the commissioning steps and prompts the user to address
any failure.
Enables importing any standard configuration of a device (e.g. RHU/Add-on) and replicating the
commissioning steps automatically according to this template.
Generates complete summary reports commissioning procedure results which can be exported as csv.
files.
NOTE: Using the Commissioning Wizard to set-up the MA1000/2000 DAS is highly recommended and yet
optional. Manual commissioning is still supported by accessing each device configuration screens.
MA1000/MA2000 device configuration panes are described in Appendix A: MA1000/MA2000 Manual Device
Configuration, whereas all other system device configuration panes are detailed in chapter 4.
Page 56
3.1 Overview of Commissioning Wizard Procedure
Overview of Commissioning Wizard Procedure
Page 57
3.2 Before Running the Wizard

Before running the Wizard:
Verify system controller operation - verify that system controller is set up IP Address, Slave connections
(if relevant), etc.
Verify visibility of commissionable devices - verify all MA1000/MA2000 devices in the installation are
visible in the SC-450 network topology. Refer to section 5.1 for details.
For RIU-4, RIU-IM and RIU-Lite units only - Connect RF signal source(s) to RIU. Connect an RF signal
source to each RIU module (BTSC/BDAC) - except for 700 MHz LTE conditioner that has an internal
Continuous Wave signal generator and does not need an external CW signal for commissioning (See
section 9.2.1.3). You may commission the services one at a time with one signal source, or as many
services as the number of available signal sources allow.
Signal Generator (CW Signal) settings:
o Frequency according to RF service.
o BTSC input power range = +10 to +36dBm
o BDAC input power range = -16 to +10dBm
NOTE: RIU 700LTE BTSC and all RIU-12 BTSC modules include an internal Continuous Wave signal
generator and do not need an external CW signal for commissioning.
For RIU-12 installations with PAU-6 the following PAU-6 related parameters must be configured before
commissioning the RIU-12 with the Wizard (displayed in Advanced tab of relevant connected BTSC)
refer to section 9.2.2.2:
o PAU-6 Support (Enable/Disable)
o PAU-6 Attenuation level
Before Running the Wizard
Page 58
3.3 Accessing the Commissioning Wizard

NOTE: The Commissioning Wizard is available only to RF_Tech or admin levels.
The Commissioning Wizard is accessed automatically under certain conditions or it can be initiated by the
user:
A. Automatically - Upon login as RF_Tech, Group_Admin or Super user (admin), the Wizard is
automatically launched if un-commissioned devices are detected and the Welcome screen appears.
Welcome Screen of Commissioning Wizard
Accessing the Commissioning Wizard
Figure 3-1
Page 59
B. User initiated launch - the wizard can be accessed at any time through the Setup tab in the Web
Management GUI.
If un-commissioned devices are detected while logged in to the Config GUI, the following alert message
appears: Uncommissioned units found, please run setup.
The user can choose to commission them via the Wizard by clicking on the Setup tab (or via the Config
GUI by clicking on the detected device in the topology tree) or to ignore the alert message.
Setup Tab Location and Example of Alert Message
Accessing the Commissioning Wizard
Figure 3-2
Page 60
3.4 Running the Wizard

NOTE: The user cannot toggle between Wizard operation and other screens while the Wizard is running. To
access configuration screens of specific devices (see Appendix A: MA1000/MA2000 Manual Device
Configuration), it is required to quit the Wizard. The Wizard can then be run again at any time.
To commission the system via the Commissioning Wizard
1. When the Wizard is initiated (either automatically or by the user see previous section), the Welcome
screen appears.
Navigating Wizard Screens
Running the Wizard
Figure 3-3
Page 61
Navigating the Wizard:

o The process comprises several phases that are displayed in a menu to the left of the screen. The
current phase is displayed in bold and the stage number is shown at the bottom of the screen.
o Default values are assigned to all the screen parameters, allowing the commissioning process to run
independently. If the user does not click respond (click Next or modify values) within 60 sec, the
default values are assigned and the next screen is automatically accessed.
o Click Help (on each screen) for a description of the current screen.
o You may quit the Wizard any time (using the Quit button) and run the Wizard any time (using the
Setup tab).
o To generate a status report of the current process up to this point, click Reports.
2. Click Next to continue or allow the system to continue automatically after 60 seconds. (Default values will
be assigned in relevant screens). The Select Type of Commissioning screen appears.
Selecting Commissioning Type
Figure 3-4
Select the devices on which commissioning will be performed and click Next:
o New (default) commissions only recently added devices. Recommended for an existing system to
which several new devices have been added.
o Full all devices. For new installations or a clean start.
o Failed devices that failed last commissioning attempt. For verifying fault sourcing.
Running the Wizard
Page 62
3. The services detected in the system are displayed. All are selected by default.
Disable any services whose devices you do not wish to commission at this time and click Next (or allow
automatic continue).
Selecting Services
Running the Wizard
Figure 3-5
Page 63
4. The screen for selecting Max Input Power to BDAC/BTSC for each selected service appears.
For each service, do the following and click Next:
o Expand (click +) to show BDAC/BTSC and Max Input power (see Figure 3-6).
o Define Max Input Power for each BTSC/BDAC service type (default = relevant maximum value):
BTSC*: 10 to 36 dBm (default = 36 dBm)

BDAC: -16 to 10 dBm (default = 10 dBm)
700LTE BTSC*/ BTSC-12: 0 to 40 dBm (default = 40 dBm)
*The Max. Input Power for 700LTE BTSC modules in RIU-IM, RIU-4 and RIU-12 is +40 dBm.
Service Conditioner Configuration
Running the Wizard
Figure 3-6
Page 64
5. The screen for selecting maximum output power for each remote unit appears.
For each service, do the following:
o Expand (click +) to show the RHU or Add-on for the service.
o Define Max Output Power for each remote (default = relevant maximum value):
RHU Service Configuration
Figure 3-7
6. Click Next. The adjustment procedure begins:

o The user is prompt to connect the CW Signal Generator (for RIU-4, RIU-IM and RIU-Lite units) in
order to commission each selected service (if he hasnt done so already)
o The status of the headend (BTSC/BDAC) and remote-end units (RHUs/Add-Ons/HX/GX) is displayed
as the procedure is performed and it is also recorded in the device database.
o The status of the devices can be displayed or hidden by toggling between the Display/Hide button on
the top of the Adjustment screen.
o If a problem is detected during the commissioning procedure, a warning notifying the user of the
problem will be displayed along with the recommended action. If you do not respond within 60
seconds, the commissioning procedure will continue and you can attempt to resolve the issue at a
later stage. See section 3.5 for available response options.
Running the Wizard
Page 65
Adjustment Procedure
Figure 3-8
NOTE: Full commissioning of large DAS deployments may take a couple of hours to complete. A progress bar
will be shown to provide an indication to the user while the automated process is running.
Running the Wizard
Page 66
7. After the commissioning procedure is complete the Summary screen appears with a graphic display of the
number of devices which were successfully and unsuccessfully commissioned.
At the end of the procedure, a summary (success or failure) of the commissioned devices status is
displayed. Refer to section 3.5 for more analysis options.
NOTE: Click Restart to repeat the commissioning process, Exit to quit or Save to save the results as a
*.CSV file.
Summary Screen Graphic Display of Results
Running the Wizard
Figure 3-9
Page 67
3.5 Analyzing Failed Devices

3.5.1
Fault Prompt During Commissioning
If a problem is detected during the commissioning procedure, a warning notifying the user of the problem (e.g.
No RF Signal Detected, No Constant Wave Source Detected) will be displayed along with the recommended
action. See following figure for example.
Adjustment Fault Indication
Figure 3-10
If an RF or Constant Wave Source signal was not detected in relevant unit/module, proceed with one of
the following options:
o Retry Connect RF source or check connection and click Retry.
o Skip - Force continues the procedure regardless of failed RF signal detection (this will happen in any
case if you do not respond within 15 seconds).
o Quit Click Quit and then OK to terminate the Wizard session and attempt to resolve the problem
before running the Wizard again.
NOTE: Click Stop timer button to prevent automatically skipping step.
Analyzing Failed Devices
Page 68
3.5.2
Analyzing Summary Results after Completing Commissioning
1. After the commissioning procedure is complete the Summary screen appears with a graphic display of the
number of devices which were successfully and unsuccessfully commissioned.
NOTE: Click Restart to repeat the commissioning process, Exit to quit or Save to save the results as a
*.CSV file.
Summary Screen Graphic Display of Results
Figure 3-11
2. Click the Details button (see Figure 3-11) to view a list of commissioned devices with information on each
device and commissioning results.
Device information is displayed in green for successfully commissioned devices, and in red for
unsuccessfully commissioned devices. A summary of the total number of successfully commissioned and
failed devices is displayed as well.
Page 69
Each device is displayed along with basic information. You may Search for a specific device and limit the
number of displayed entries.
Summary Screen Details View
Figure 3-12
The following information is available for each device:

Item
Description
Time/Date
Time stamp of this device commission process
Service
Service type (CELL, PCS, etc.)
Device
Device type (e.g. BTSC/BDAC/Remote Unit/Add-On, etc.)
Name
Name assigned to device by user
Serial
Device serial number
Location
Physical connection to controller (direct for RIU elements or via

BU for remote elements)
Result
Commissioning result (Success/Fail)
Max Input
BTSC/BDAC Max Input Power (defined or default)
Max Output
Remote Unit/Add-On target Max Output Power (defined or default)
Page 70
3.5.3
Saving Details Report Results
The Details report results (see section 3.5.2) can be saved as a *.CSV file type for further analysis at a later
stage.
To save the Details Reports results
Click Save to export the report log as a *.CSV file type and OK. The file will be saved to a selected location.
Saving Commissioning Results
Figure 3-13
Page 71
C o mmis s io ning A dditiona l C MA

E lements
This section provides information on how to configure additional CMA system elements via the Web
Management Configuration GUI which are not configurable via the Commissioning Wizard:
PAU-6 unit
WMTS-CH System
EC560 Solution
FT-350 system elements
MobileAccessVE
Page 72
4.1 PAU-6 Configuration

The PAU-6 is a broad-band passive attenuation unit which does not require any configuration apart from
assigning the unit an indicative name.
NOTE: The attenuation level, PAU-6 support and calibration source mode are set via the connected RIU-12
(per BTSC module) and must be configured before the RIU-12 is commissioned via the Wizard. Refer to
section 9.2.2.2.
The PAU-6 unit is automatically detected and displayed in the Network Topology Tree, however it is not
displayed under the RIU to which it is connected. Thus, it is recommended to assign the unit a name
indicating the RIU to which it is physically connected for reference.
To assign the PAU-6 a name
1. Click on the PAU-6 element in the Network Topology Tree (Config window). The Module Info tab appears.
PAU-6 Configuration Module Info Tab
Figure 4-1
2. Verify that the PAU-6 alarms show green indicating normal operation. Refer to section 7.5.5 for details
on PAU-6 alarms.
3. Click on the Name Modify buttons for the Name and Ext. Name fields and enter indicative names for the
PAU-6 unit.
Note: Refer to section 5.3.1 for details on Extended Name field.
4. Click OK. The name will appear in Network Topology Tree.
5. Click on the Comments tab and enter any comments relevant to the device. Refer to section 5.3.2 for more
details.
PAU-6 Configuration
Page 73
4.2 WMTS-CH System Configuration

Once the required physical connections have been completed the WMTS system elements can be
configured. Only the RIM-Main unit is directly connected to the SC-450, whereas the other WMTS units (i.e.
RIM-1400 and RHU-4) are managed via the RIM-Main.
The following steps are required to setup and commission the WMTS-CH system devices:
1. Verify that WMTS system modules are displayed in the Topology tree (RIM-M, RIM-1400, BUs and RHUs)
connected to the controller are displayed in the Network Topology tree (auto-discovery) and are colored
green, red or yellow.
NOTE: Any of these colors are acceptable before the adjustment procedure has been performed.
SC-450 Topology Tree with WMTS Elements
WMTS-CH System Configuration
Page 74
Figure 4-2
2. Disable the irrelevant alarms on the Remote Units:

Once a device fault indication is identified, the Alarms tab in the device configuration dialog can be used to
provide further information on the source of the problem. It is required to disable two OPTM alarms that
are not relevant:
o DL power overload
o DL input power low
Click on the relevant OPTM (BU 1-4; BU 5-8) in the topology tree and mask the DL Power Overload and
DL Input Power Low alarms by clicking on the Modify button and un-checking the specified alarms and
clicking OK.
3. Define the OPTM signal source interface to indicate a RIM connection. In the BU RF Parameters Interface
Type field verify that RIU is selected (where RIU also represents interface to RIM).
4. Configure the RIM-Main unit. See details in section 4.2.2.1.
5. Configure the RIM-1400 unit. See 4.2.2.
NOTE: For optimal results, it is required to power-ON the RIM-1400 unit for at least 48 hours before
performing the adjustment procedure.
6. If necessary adjust the uplink signal gain as explained in corresponding RIM-Main and RIM-1400
configuration sections.
Page 75
4.2.1
RIM-Main Configuration
Each RIM-Main unit is individually configured and controlled through a dedicated configuration dialog.
Double-click on the RIM item in the Network Topology. The RIM configuration dialog appears. The dialog
contains three tabs:
o Module Info tab contains general identifying information and service control options.
o RF Parameters contains uplink gain settings and RIM reset options
o Alarms Display Area contains alarms monitoring and alarm setting options
o Comments tab used for entering any additional general information relevant to the device (see
section 5.3.2 for more details)
RIM-Main Configuration Window
Figure 4-3
Page 76
To configure and control the RIM Main

1. Optional In the Module Info tab, assign the RIM-Main unit an indicative name and Extended Name (see
section 5.3.1 for details) by clicking the corresponding Modify button. See Figure 4-3.
2. Click the RF Parameters tab:
RIM Main RF Parameters Tab
Figure 4-4
The uplink gain is factory set to provide the signal required at the Expansion. The signal level can be
adjusted relative to the factory setting as follows:
Click the Gain Control Browse () button and select the new value:
o Negative (-): decreases signal level relative to the default value
o Positive (+): increases signal level relative to the default value
3. To reset the RIM Main, click the Restart button.
Page 77
4.2.2
RIM-1400 Configuration
In multiple MA WMTS-CH system installations, the RIM-1400 units of each system are interconnected; the
reference signal source is acquired from one of the units (according to the user configuration). Each RIM1400 unit is individually configured and controlled through a dedicated configuration dialog.
To configure and control the RIM-1400
NOTE 1: For optimal results, it is required to power-ON the RIM-1400 unit for at least 48 hours before
performing the adjustment procedure.
NOTE 2: You will need a frequency counter (or similar equipment) with a display that is at least 10 digits.
1. Double-click on the RIM-1400 item in the Network Topology. The RIM configuration dialog appears. The
dialog contains four tabs:
o Module Info contains general identifying information and service control options.
o Frequency Config - contains uplink gain settings and RIM-1400 restart option
o Sync Config used for defining the clock synchronization
o Comments used for free text comments relevant to device (refer to section 5.3.2 for more details)
o Alarms Display contains alarms monitoring and alarm setting options
RIM-1400 Configuration Window
Figure 4-5
Page 78
2. Optional - In the Module Info tab, assign the RIM-1400 unit an indicative name and Extended Name (see
section 5.3.1 for details) by clicking the corresponding Modify button.
3. Click on the Freq Config tab.
RIM-1400 Frequency Config Tab
Figure 4-6
4. The Converter Mode is used to enable or disable the down-conversion functionality of RIM-1400, blocking
or allowing the 1397.5 2.5MHz to 565.5 2.5MHz signals to pass through to the Receivers (via the RIM-M
unit).
o Converting Default. 1400MHz signal is down-converted to 560MHz. Used for 560MHz receivers.
o NOTE: The Frequency In and Frequency Out values are only relevant if the Converter Mode in the
Advanced tab is set to Converting mode.
o Bypassing 1400MHz signal is not down-converted. Used for systems with 1400MHz receivers.
5. The uplink gain is factory set to provide the signal required at the Expansion. The signal level can be
adjusted relative to the factory setting as follows:
Under Uplink Atten. Control, click the Gain Control drop-down list button and select the new value:
o Negative (-): decreases signal level relative to the default value
o Positive (+): increases signal level relative to the default value
o Provides UL signal attenuation control and shows power measurements.
o UL Atten. Value user definable uplink attenuation value. Used to increase or decrease level of the
(converted and non-converted) signal that is output to the RIM-M.
o UL Power Out provides a number relative to the output power.
6. To reset the RIM-1400, click the Restart button.
Page 79
4.2.2.1
RIM-1400 Synchronization
RIM-1400 Synchronization is a procedure which defines the RIM-1400 unit that will be used as reference
clock for synchronizing additional units and to monitor the synchronization parameters
1. It is assumed that the RIM-1400 unit has been powered on for at least 48 hours at this point.
RIM-1400 Rear Panel DC Power Connection
Figure 4-7
2. Connect a frequency counter or similar test equipment to the RIM-1400 front panel LO_TEST connector
(1963MHz).
RIM-1400 Front Panel
Figure 4-8
Page 80
3. Click on the RIM-1400 Sync. Config tab and adjust the Ref. Tune voltage up or down until the LO
Frequency is exactly at 1963MHz.
RIM-1400 Sync. Config Tab
Figure 4-9
4. Under Role Selections set the following parameters:

o Defined - set as Master, the unit whose clock is to serve as the clock synchronization. All other units
are to be defined as Force Slave (default).
NOTE: Any one of the interconnected units (order in daisy-chain is NOT significant) can be defined as
Master. This definition can be overwritten by external conditions.
The following options are available:
Auto Master/Auto Slave - enables setting RIM-1400 synchronization mode:
Force Master /Force Slave unit operates according to its manual_clock_status. In this mode, all
the relevant alarms are cleared.
o Actual - shows Master/Slave status of the operation of the current unit. This may be different than the
initial definition
5. The Ref(erence) Clock shows status of parameters relevant to clock reference and enables tuning the
reference clock signal:
o External Ref. detection of external clock, where Exist indicates that a clock reference from another
RIU-L unit is detected.
o Internal Ref. clock reference is acquired from the unit itself.
Page 81
o Matching of Ref. verifies that external and internal clock are equal, where Equal is the required
status. (In a future revision, if the external and internal clocks are NOT equal, a mechanism that will
automatically correct discrepancies will be activated).
o Ref Tune IMPORTANT. Determines the accuracy of the OCXO reference signal. See Figure 4-9.
6. To synchronize the clock on all RIM-1400 units:
o Click the Adjust button. The Adjust Status shows whether the procedure was successful; the Last
Successful Time and Date shows the last time the procedure was performed successfully.
o You may set the Maintenance Interval to send a notification when the next adjustment procedure is to
be performed. (Maintenance only).
Page 82
4.3 EC560 Device Configuration

If the EC560 components have not been automatically discovered (refer to section 2.5) the EHU can be
manually added to the SC-450 Network Topology. This requires knowing the EHUs IP address. See following
section for details.
4.3.1
Manually Adding EHU to Network Topology
To Manually add EC560 Component

NOTE: The EHU can only be added if the devices are on the same LAN as the SC-450. This requires the EHUs
and the SC-450 LAN port network settings be configured and connected to be able to communicate across
the customer LAN. Refer to the EC560 Solution User Manual for instructions on configuring the network
parameters of the EHU. Refer to section 2.7.2 for instructions on configuring the SC-450 LAN port.
1. In the network topology tree, click the Add (new device) button on the bottom.
Add New Device Option in Topology
Figure 4-10
2. In the Add Device dialog that appears, select the element to be added (EHU) from the drop-down list enter
the IP address of the unit and click OK.
EC560 Device Configuration
Page 83
Select Device Option
Figure 4-11
Enter IP Address Field
Figure 4-12
3. The unit will be added to the network topology

o The EHU element is displayed with its hosted devices (i.e. AUs) and can be accessed from the SC450 via hyperlink.
o The VCU elements are configured via the VE specific Web GUI, which can be accessed from the SC450 via hyperlink.
Example of VE Hyperlink in Network Topology
Page 84
Figure 4-13
4.3.2
EHU (Ethernet Hub Unit) Configuration
Each EHU is individually configured and controlled through a dedicated configuration dialog. The EHU
configuration dialog consists of two tabs: Module Info and Ethernet Config. The main provided functions are:
In the Module Info tab - Viewing basic information on the unit and assigning the unit a recognizable name
In Ethernet Config tab Configuring the Ethernet port priorities and link and port modes.
To Configure and Control the EHU:
1. Double-click on the EHU item in the Network Topology. The EHU configuration dialog appears.
EHU Config-Module Info Tab
Figure 4-14
2. In the Module Info tab click the Modify button and assign the EHU an identifiable name.
3. Click Modify to configure the EHUs network parameters: IP Address, Subnet Mask, and Default Gateway.
Page 85
4. Click the Ethernet Config tab.
EHU Ethernet Config Tab
Figure 4-15
In the Ethernet Config tab define the following for the Ethernet Ports (A,B, C,D):
o Port priority (Controls priorities between Ethernet ports):
None
>B>Rest
B>A>Rest
*A=B>Rest
o Link Mode: Force Up/Force Down/Auto (Default)
o Port Mode:
10 Mbps (Half/Full)
100 Mbps (Half/Full)
Auto
NOTE: The AU port modes are configured automatically according to the EHU port modes, however they can
be modified via the specific AU Ethernet Config tab as well. See section 4.3.3.
Page 86
4.3.3
AU (Antenna Unit) Configuration Dialog
Each EHU is individually configured and controlled through a dedicated configuration dialog. The EHU
configuration dialog consists of three tabs: Module Info, Ethernet Config and AU (Antenna Unit) Port Config.
The main provided functions are:
In the Module Info tab - Viewing basic information on the unit and assigning the unit a recognizable name
In Ethernet Config tab Configuring the Ethernet port priorities and link and port modes.
To Configure and Control the AU:
1. Double-click on the AU item in the Network Topology (under the host EHU). The AU configuration dialog
appears.
AU Module Info Tab
Figure 4-16
2. In the Module Info tab click the Modify button and assign the AU an identifiable name.
Page 87
3. Click the Ethernet Config tab.
AU Ethernet Config Tab
Figure 4-17
In the Ethernet Config tab (above) define the following for the Ethernet Ports (A,B, C,D):
NOTE:
1: The AU Ethernet ports A, B, C and D correspond to those of the EHU unit (A and B support low speed
while C and D support high speed).
2: The AU port and link modes are configured automatically according to the EHU modes, however they can
be modified via the AU specific Ethernet Config tab as well.
o Port priority (Controls priorities between Ethernet ports):
None
>B>Rest
B>A>Rest
*A=B>Rest
o Link Mode: Force Up/Force Down/Auto (Default)
o Port Mode:
10 Mbps (Half/Full)
100 Mbps (Half/Full)
Auto
Page 88
4.4 FT-350 Solution Configuration

The following operations can be performed on the FT-350 via the SC-450:
Central management - the complete FT-350 solution is centrally managed via the SC-450 connection to
the OCH.
Auto-discovery is performed on the FT-350 OCH and ORUs as well as the VCUs connected to the ORUs
no setup is required
Automatic optical adjustment - no manual optical adjustment procedures are usually required the system
automatically performs optical adjustments for each OCH to ORU link.
Full monitoring via dedicated panes - the OCH and ORUs are managed via dedicated panes in the SC450 Topology Tree.
4.4.1
OCH (Optical Central Hub) Configuration
Each OCH is individually configured and controlled through a dedicated configuration dialog. The monitoring
and configuration options are distributed over three tabs:
Module Info - device version and identification definitions

RF Parameters DL and UL RF configuration options. Used to analyze automatic adjustment failure.
Optical Link provides the optical adjustment options. Used for manual adjustment in case of automatic
adjustment failure.
Comments - used for entering any additional information (free text) relevant to the selected device (refer to
FT-350 Solution Configuration
Page 89
To configure OCH
1. In the Network Topology tree, expand the relevant SC-450 Controller.
2. Verify that the OCH unit(s) is detected and appears in the Network Topology. The item appears with an
indication of the highest alarm level detected for it, where green indicates normal operation. Therefore all
items should be green.
Each OCH is displayed as two separate modules (1 to 4 and 5 to 8 ports), where each module hosts
specific ORUs.
OCH Configuration Window (Shows Module Info Tab)
Figure 4-18
3. Click on the host OCH module item and verify that all of the alarms in the OCH Alarms display area are
green. Refer to section 7.5.9 for alarms description.
OCH Alarms Display Area
Page 90
Figure 4-19
4. If the DL Input power Low and DL Input power High alarms are RED, refer to the RF Parameters tab and
perform DL RF adjustment.
OCH RF Parameters Tab
Figure 4-20
o Low or High DL Input power shows Low or High indicates that the measured input power from the
BTS source is either lower or higher than the expected value:
When connected to RIU: Up to -20dBm
When connected directly to BTS (via passive interface): Up to 0dBm
o Adjust RF DL gain with Manual DCA (in 0-31 dB steps).
Table 4-1 provides a description of the parameters displayed in the RF Parameters tab above.
DL Item
Description
(DL) Input Power
Indicates whether the normally expected (factory defined) power input from
the BTS interface source (RIU or passive) is detected at the OCH.
Numerical value displayed only if the expected value range is detected.
Low value is lower by 3dB than expected value. Use the Manual DCA
option to correct.
High value is greater than expected value. Use the Manual DCA option to
correct.
(DL) Manual DCA
Use if a Low or High (DL) Input Power is detected, to manually adjust the DL
RF gain towards laser in 0-31 dB steps.
(DL) Operational DCA
Shows current attenuation.
(DL) Restore button
Restores factory default DCA values:

Up to -20 dBm when connected via MA RIU
Up to 0 dBm when connected directly to a BTS
Up to -15 dBm when connected to a MA VE
DO NOT click Restore button unless adjustment procedure fails
Page 91
DL Item
Description
UL Item
Description
(UL)Output Power
Power output from OCH towards RF source (dBm)

Numerical value displayed only if the expected value range is detected.
Low value is lower by 3dB than expected value. Use the Manual DCA
option to correct.
High value is greater than expected value. Use the Manual DCA option to
correct.
(UL) Manual DCA
Enables overall UL RF gain adjustment in 0-31 dB steps.
(UL) Operational DCA
Shows current attenuation.
(UL) Restore button
Restores factory default DCA values:

Up to -20dBm when connected via MA RIU
Up to 0dBm when connected directly to a BTS
Table 4-1: OCH RF Parameters Tab Description

NOTE: Manual and Factory DCA levels are similar by default unless Manual DCA parameter is modified.
5. The optical link adjustment is performed automatically by the system upon detecting the connected ORU
ports.
NOTE: The OCH-4-XR / OCH-8-XR units automatically perform the optical adjustment calibration when a
connection is detected on the ports.
The Optical Adjustment Fail alarm will usually show green, however if not refer to the Optical Link tab
where the procedure can be performed manually via the Adjust button. See following figure.
OCH Optical Link Tab
Figure 4-21
Page 92
Table 4-2 provides a description of the alarms and operational buttons in the Optical Link tab above.
Item
Description
Optical Adjust Button
Click to manually perform optical link adjustment procedure between the

OCH and remote unit (i.e. ORU)
Optical Adjust Fail (Alarm)
RED - Optical adjustment procedure failed
UL Optical Link (Alarm)
RED Measured optical link level low
Mismatch (Alarm)
RED - Wrong end-equipment connected to OCH module. For example, an

optical module configured for ORU support will alert in case of an RHU
connection, whereas an optical module configured for RHU mode will alert
in case of an ORU connection.
Modify button (per service)
Used to mask/unmask the service specific optical link alarms
Table 4-2: OCH Optical Link Tab Description

6. (Optional) Assign OCH an identifiable Name/Extended Name:
Note: refer to section 5.3.1 for details on Extended Name field.
o Click Module Info tab
o Click Modify button and enter name
o Click OK
Page 93
4.4.2
ORU (Optical Remote Unit) Configuration
The ORU monitoring and configuration options are distributed over five tabs:
Module Info - device version, supported services and general info

Module Control provides RF connection type options
Service Control provides service control options and configurable RF parameters per service
Alarms displays service specific alarms and enables masking irrelevant alarms
To Configure and Control the ORU:

1. In the Network Topology tree, expand the relevant SC-450 Controller.
2. Click and expand the host OCH and verify that the ORU units are detected and appear in the Network
Topology. The items appear with an indication of the highest alarm level detected.
ORU Configuration Window (Shows Module Info Tab)
Figure 4-22
Page 94
3. Click on the Module Control tab and configure the RF connection type for each of the connected ORU
services (Simplex/Duplex).
ORU Optical Link Tab
Figure 4-23
The following table provides a description of the information viewed in the ORU Module Control tab.
Parameter
Description
Port Configuration
Enables setting the type of RF connection (Simplex/Duplex) used for each

connected service
Link Status
ON - Link detected to OCH

OFF No link detected to OCH
N/A
Link Level
ORU link level (0-255)
4. Verify that all of the alarms in the ORU Alarms display area show GREEN. See figure above. If a service
specific alarm (e.g. Service 1) does not show green, refer to the Alarms tab (section 7.5.10.2) in order to
view the specific alarm that was raised for the service.
Page 95
ORU Alarms Tab
Figure 4-24
5. If RF related alarms (i.e. DL Out Pwr High/Low and Service) do not show green, refer to the Service
Control tab.
ORU Service Control Tab
Figure 4-25
Page 96
The following table provides a description of the parameters in the Service Control tab, shown above.
Parameter
Control
DL. Att.
Ctrl.
DL Out Pwr
UL At. Val
Description
Enables enabling/disabling supported service and corresponding parameters:
On= Enabled and user can set configurable service parameters (i.e DL Attenuation
Control)
Off = Disabled and service parameters are inaccessible
Can be set via adjustment process or manually in 0.31.5 dB steps
Read-Only. Displays DL output power as reported from external power amplifier.
Controls attenuation on the uplink. Displays DCA value for each service limiter which
is set during manufacturing.
Table 4-3: ORU Service Control Tab Description

6. In the Service Control tab:
o Verify that the required services are enabled (up to 4)
NOTE: Service 5 is reserved for future use only.
o DL Output Power must be 10 dBm for connected VCU. If lower or higher than 10dBm, modify DCA
accordingly via the DL Att. Ctrl parameter.
7. (Optional) Assign the ORU an identifiable name/Extended Name (see section 5.3.1 for details on Extended
Name field):
o Click the Module Info tab
ORU Module Info Tab
Figure 4-26
Page 97
Parameter
Description
Type
Duplex/Simplex ORU type
Model
USA/ROW/Other
Serial Num.
7 digit alpha-numeric serial number
Firmware Version
Firmware version no. corresponds to SW version
Fiber Range*
XR extended optical range of up to 20Km
Fiber Mode
Type of Fiber Mode (SMF; SMF/WDM; MMF)
First/Second/Third/Fourth/Fifth Band
Band name
Table 4-4: ORU Module Info Tab Description

o Click the Name/Extended Name Modify button
o Enter name and click OK. The assigned name will be displayed in the corresponding field.
4.5 MobileAccessVE Device Configuration

The VE elements IP address is automatically detected by the SC-450 controller and displayed as a hyperlink
in the topology network (see section 2.4 for management connections). Clicking on the hyperlink opens a
management session to the element.
Example of Hyperlink
Figure 4-27
NOTE: See relevant MobileAccessVE Installation and Configuration User Manual for configuration procedure.
The MobileAccessVE VCU units are configured via dedicated Web GUI (See relevant VE Installation and
Configuration User Manual), however the SC-450 enables adding the VE elements to the network topology
for monitoring and fault sourcing.
The number of VCU configuration tabs varies depending on the VCU model. In general, the Configuration
dialog consists of Module Info and RF Service tabs. The main provided functions are:
In the Module Info tab - Viewing basic information on the unit and assigning the unit an identifiable name.
In Service RF tab Configuring the service and RF parameters.
MobileAccessVE Device Configuration
Page 98
To View the VCU Configuration Dialog

NOTE: The SC-450 Web Management GUI provides a hyperlink to the VE specific Web GUI.
1. Click the VE item (hyperlink) in the Network Topology. The VE Web GUI is accessed and the VE Module
Info tab is displayed by default.
Example of MobileAccessVE VCU Module Info Tab
Figure 4-28
To modify the name assigned to VCU, click the (Name) Modify button, enter new name and click OK.
2. Click the Service RF tab for configurable RF parameters.
Page 99
Example of MobileAccessVE Dual-Band VCU Service RF Tab
Figure 4-29
NOTE: See relevant MobileAccessVE User Manuals for description of configuration procedures.
Page 100
N a v iga ting the W eb G U I A pplic a tion
IMPORTANT: The available tabs and options may vary depending on the access level used to open your
session.
The main window shows all the currently connected and defined devices and their status and provides access
to device management functions, as well as to system management options such as security, firmware
upgrade, etc.
The Web GUI application window is divided into the following areas:
Main Menu - Provides access to the available configuration and management options (See section 5.2).
Network Topology Hierarchically displays the defined and available site devices and their status. (See
section 5.1).
Work Area The display corresponds to the selected menu or device from the network topology.
NOTE: For optimal response time, it is recommended to open the minimum required windows and close
unnecessary windows. A window that is not edited for five minutes will be automatically closed. A window
acceleration mechanism accelerates the responses when adjustments are made by temporarily refreshing
only the active window (events, Topology View, Device View, etc. will not be updated).
The following figure shows the Work Area display when the CNTRL-M (Master Controller) item is selected. It
shows any slave units connected to the controller. Control dialogs for the device or for elements hosted by
these devices (such as RHUS for BUs, BTSC/BDAC for RIUs, GXs for OCHs or AUs for EHUs) are accessed
from the tree.
Web GUI Main Window
Figure 5-1
Page 101
5.1 Network Topology

NOTE: It is important to understand the Network Topology display since you will be required to verify the
device connections before the configuration procedure can be performed. The Web GUI Management
application Network Topology tree display differs from the NMS Network Topology Tree display.
The Web GUI Management application Network Topology tree shows the controller to which the session was
opened, and the hosted devices. If a Master/Slave configuration is installed, the Slave controller will be
displayed under the Master controller.
The Network Topology tree includes problem sourcing features such as:
Color indication corresponding to the elements status

Real-time updates of device status
Upward propagated element status colors
Topology Tree
Network Topology
Figure 5-2
Page 102
The devices are displayed as follows:

Item in Tree
Description
CNTRL
Controller (M indicates Master controller).
RIU-4/RIU/RIU LITE
Hosting RIU units with their corresponding modules (BTSC/BDAC/BDACL).
BTSC/BDAC modules displayed under the corresponding RIU or RIU Lite units with
BTSC/BDAC/BDACL the number of the port to which it is connected (Px). The suffix L (i.e. BDACL) stands
for RIU Lite.
RIU-12
Host RIU-12 unit with corresponding modules (CMU and BTSCs).
CMU
Control Module displayed under host RIU-12 unit with number of the SC-450 port to
which it is connected (Px).
BTSC_12
RIU-12 RF conditioner module displayed under host CMU module with the number of
the chassis slot (Px) in which it is installed (e.g. P1-BTSC_12)
PAU-6 unit with the number of the SC-450 port (Px) to which it is connected (e.g. P8PAU6).
Note: Is not necessarily displayed under the RIU unit(s) to which it is connected so it
is recommended to indicate this information in the (configurable) Name field of the
PAU-6
unit. See section 4.1 for PAU-6 device configuration.

Base Unit
Hosting Base Unit with its modules: BU 1-4 (Optical Module 1) and BU 5-8 (Optical
Module 2)
BU 1-4; 5-8
Base Unit displayed according to 4-port modules, where each module is referred to
as BU 1-4 or BU 5-8. Each module is displayed along with the Controller port to which
it is connected.
OCH
(Optical Central
1
Hub)
OCH 1-4; OCH 5-8
RHU
Hosting OCH unit with its modules: OCH 1-4 (Optical Module 1) and OCH 5-8
(optical Module 2)
OCH is displayed according to 4 port optical modules, where each module is referred
to as OCH 1-4 or OCH 5-8. Each module is displayed along with the Controller port to
which it is connected (e.g. OCH 1-4-, OCH 6)
Remote Hub Units. Each RHU is displayed under the BU optical module (BU 1-4; BU
5-8) to which it is physically connected, along with the port to which it is connected.
Note: The chassis (e.g. QX) in which the RHU is installed is not indicated in the
Topology Tree by default. This can be indicated in Name field of RHU which will then
be displayed in the tree (see section 9.2.4).
Add-On
1200 Add-On unit. Each add-on is displayed under the RHU to which it is physically
connected.
HX
MobileAccessHX Indoor unit. Displayed with BU or OCH port to which unit is

connected.
HX Outdoor
MobileAccessHX Outdoor unit. Displayed with BU or OCH port to which unit is

connected.
Does not indicate by default which type of HX unit (i.e. Indoor or Outdoor, QuadBand) although can be viewed in device view recommended to indicate in name field
so it appears in topology.
HXn
MobileAccessHXn Indoor unit (currently supporting LTE 2600 MHz band). Displayed
with OCH port to which unit is connected (e.g. HXn5).
Network Topology
Page 103
Item in Tree
Description
GX
MobileAccessGX unit. Displayed under OCH module to which unit is connected. Does
not indicate by default which type of GX unit (e.g. Tri-Band, Quad-Band)
recommended to indicate in name field so it appear in topology.
ORU
Optical Remote Unit. Each ORU is displayed under the OCH module to which it is
physically connected, along with the OCH port to which it is connected (e.g. ORU6).
EHU
Ethernet Hub Units. Each EHU is displayed under the Controller to which it is
physically connected.
1,2
AU
Antenna Units. Each AU is displayed under the host EHU.
VE IP Address
Hyperlink (e.g. VE172.19.xx.xx)
VCU (Master or Slave VE Control Unit) hyperlink to VE specific Web GUI.
VAPs
VE Access Pods displayed under the host VCU.
These units appear with the Px (e.g. P1, P2) suffix, which indicates the number of the SC-450 port (#1-16 on rear panel) to which the
unit is connected.
If the EHU is connected to the SC-450 indirectly via the LAN, the suffix, which indicates the number of the SC-450 port (#1-16 on the
rear panel) will not appear.
5.1.1
Tree Status Colors
Faults are propagated only through an arrow so that the faulty device can be quickly identified by its color.
The tree colors indicate the status of the elements.
NOTE: Only devices with software v3.17 and higher will be displayed.
Color
Description
Green
OK
Yellow
Minor Error
Red
Major Error
No communication to a (MobileAccess) device set in Base-Line.
Gray
NOTE: If communication to a device that was not set in Base-Line is lost, the device
disappears from the display.
Network Topology
Page 104
5.2 Main Menu
The Main Menu Bar consists of the following tabs:
Monitor Displays summary of controller information (e.g. IP address, HW version) and summary of
events generated in the devices (alerts and normal events).
Config (Configuration) - Displays general module information, RF parameters and configuration options for
the available selected site devices.
Events Displays the events that occurred on the monitored devices and enables generating reports.
Configuration changes that are initiated by the network manager are not considered events display. (See
section 7.2).
Set-up Future Options

Management Provides administration options such as firmware upgrade, user management options and
IP settings required for receiving traps.
Help Opens the complete User Manual of the SC-450.

The following figure shows an example of a Topology Tree showing some of the elements that can be
connected to the SC-450.
Main Menu
Page 105
5.3 Device Configuration Tabs

Each device has dedicated configuration tabs that provide general info and configuration, control, and
monitoring options for that device. Some units (such as RIUs or BUs) have dedicated configuration dialogs for
their sub-modules (BTSC sub-module for RIU and 4-port modules for BUs) as well.
To display the device configuration tabs
Double-click on the device in the Network Topology tree. Figure 5-3 shows an example of the configuration
tabs displayed for a selected RIU-12 CMU module.
RIU-12 CMU Configuration Tab
Figure 5-3
Some common tabs are:
Alarms Device specific alarms used for fault sourcing.

General/Module Info Provides device version and identification definitions such as Name and Ext. Name
(see section 5.3.1 for details on Extended Name field).
Configuration Panes Device specific configuration tabs such as RF Parameters, DL Adjustment and
Alarms relevant to the selected device.
The displayed tabs and parameters vary depending on the device type.
NOTE: The MA1000/MA2000 device configuration panes are described in chapter 4 (elements not
commissioned via Commissioning Wizard) and in Appendix A: MA1000/MA2000 Manual Device Configuration.
Device Configuration Tabs
Page 106
Device View - the device view appears along with the configuration information and can be used for fault
sourcing at a glance. The LED indicators in the device view represent the true LED behavior on the BTSC
front panel. See detailed example in section 7.4.
5.3.1
Device Extended Name
The Extended Name field appears in the General tab of the Controller and in the Module Info tab of each of
the MA1000/MA2000 managed devices. This field can be used for entering additional indicative information
such as the specific physical location of the selected device.
Example of Extended Name Field (Controller General Tab )
Figure 5-4
Note the following:
The Extended Name field option is provided for all managed elements (not including MobileAccessVE
solution).
Field can contain up to 45 ASCII characters

The assigned Ext. Name is saved on the Controller device, so that if the same unit is disconnected and reconnected the Ext. Name info is saved.
Ext. Name activities generate events which are logged in the Activity Log (i.e. any change in the Extended
Name is logged with the details of the modified name).
The Ext. Name field events are also included in the Name field events.
In cases where a unit is disconnected and then replaced with a different unit of the same type a Mismatch
occurs. See section 5.3.3 for details on Mismatch scenarios.
The Extended name info is automatically deleted and not re-assigned in the following cases:
o A unit is disconnected or module extracted and replaced with a different type of element (in terms of
port/slot) (e.g. OCH in place of BU).
o Reset Baseline is performed for the controller
Page 107
To assign device Ext. Name

1. (In the Module Info tab) Click the Ext. Name Modify button (see Figure 5-4). The following dialog appears:
Extended Name Modify Dialog
Figure 5-5
2. Enter the additional information (up to 45 ASCII characters) in the field and click OK to save entry in
Controller.
5.3.2
Comments Tab
Each (Master/Slave) Controller and managed system element has a dedicated Comments tab which can be
used to enter any information relevant to the selected device.
Example of Comments Dialog
Figure 5-6
Note the following:
Information is entered as free flow text of up to 255 ASCII characters

Initial empty Comments tab appears as Comments N/A. After comments have been entered the N/A
disappears (even if the entry is afterwards deleted).
The comments are only saved on the Controller so that the entries in the Comments tab are automatically
deleted and cannot be restored in the following cases:
o Unit/module is disconnected and Reset Baseline is performed (via Controller General tab)
o Unit/module is disconnected and a different type of element is connected in its place
NOTE: Example of disconnected unit/module - different BU unit connected to Controller port or RIU BTSC
is moved to different slot.
Page 108
If a unit is disconnected and its port or slot is replaced with a new unit of the same type (e.g. BU replaced
with different BU), a Mismatch event is generated and a notification appears. Refer to section 5.3.3 for
details.
5.3.3
Extended Name/Comments Mismatches
A Mismatch event can occur for the device Extended Name and/or Comments when a device is disconnected
and replaced with a different unit/module of the same type (e.g. different BU unit connected to Controller port
or RIU BTSC is moved to different slot).
Example of Extended Name Mismatch Message
Figure 5-7
The Mismatch notification will appear in the Modify dialog of the Ext. Name/Comments. Upon receiving
Mismatch message, proceed according to the following:
To accept Mismatch and re-assign the previous name to click the Modify button and then click OK
To assign new Extended Name - click the Modify button, enter new text and then click OK
To accept a batch of all Mismatch events and re-assign previous name for all corresponding devices:
1. Select the host Master/Slave Controller in the Network Topology Tree.
2. In the General tab, refer to the Extended Text options and click the Accept All button. The Accept Ext.
Text Records dialog appears.
Example of Accept Ext. Text Records Dialog
Page 109
Figure 5-8
3. Click Yes to accept. All Mismatch records will be accepted and previous names re-assigned to new
(same type) elements.
To delete a batch of detected Mismatched Extended Names:

1. Select the host Master/Slave Controller in the Network Topology Tree.
2. In the General tab, refer to the Extended Text options and click the Delete All button. The Delete Ext.
Text Records dialog appears.
Example of Delete Ext. Text Records Dialog
Figure 5-9
3. Click Yes. All Mismatched Extended Names will be deleted.

4. Refer to the dedicated Module Info tab of each of the relevant devices to re-assign an Extended Name.
5.4 Removing a Hosted Device

The SC-450 automatically detects system elements physically connected to it and adds it to the base-line.
When the communication with a device is faulty (i.e. the device is disconnected) an alarm is generated.
Therefore, when removing (disconnecting) a hosted device from the system, the base-line must be re-set in
order to update the removal and to prevent an alarm from being raised.
To Reset the Baseline
1. Double-click on the Master Controller (CNTRL-M). The General tab is displayed (Figure 5-10).
2. Click Reset Baseline button to set new baseline that does not include the disconnected device.
Removing a Hosted Device
Page 110
Note: When Reset Baseline is performed the Extended Name and Comments for devices which have been
disconnected are automatically deleted and cannot be restored even if the same device is reconnected.
Master Controller General Tab
Removing a Hosted Device
Figure 5-10
Page 111
A dminis tra tion
This chapter includes information on performing the following operations:
Creating and managing multi-user account groups and monitoring user activities
Reviewing user logs a security measure used to monitor user operations such as configuration changes
Single source SW download for upgrade from V5.0 (or higher) to V5.1 (and higher). This allows Slave
SC-450 controllers to be automatically upgraded from the Master controller. Device reports summary
information on various types of devices in the network along with basic physical and configuration
information on each device
6.1 Multi User Account Management

Access security is based on the definition of a number of user groups with dedicated group administrators,
where each group administrator creates user accounts for his/her group. The user accounts in each group
can be of various authentication levels (six hard-coded authentication levels are available).
NOTE: In later versions, Groups will be used to limit access to specific devices so that only devices allocated
to a group are accessible by members of that group.
Note that groups can only be created by the System Administrator (Super User - admin), where the System
Administrator does not have access to the User Accounts in each Group. (Only the Group Administrators can
manage users in his/her group.)
The SC-450 management platform supports up to 32 groups, which can be assigned up to 20 users per group
for a maximum of 500 users per controller. The various combinations of groups, users and access levels
provide flexible management options and enable compartmentalizing the management capabilities
(monitoring, device configuration, etc.) according to groups and users.
All Multi-User Account operations are performed via the Management tab, Security sub-tab, where the
Security screen options vary according to the login user level.
Multi User Account Management
Page 112
Management Tab Security Menu Option
Figure 6-1
Page 113
6.1.1
Defining User Groups
NOTE: User Groups can only be created by the system administrator (User Name = admin). For access level
details, see section 6.1.3.
How does it work?
The System Administrator logs in as admin and defines various Groups by name only.
As it is defined, each group is automatically assigned a default Group Administrator and the Group
Administrators default password both based on the Group name.
The Group Administrators can then create User Accounts for their own groups.
To create a new group
1. Login as admin.
2. Click on the Security option of the Management tab. The Group Management dialog appears, displaying
any existing groups.
Group Management Dialog
Figure 6-2
NOTE: To remove a group, click Remove. The group along with its accounts is removed after a verification
prompt. (User Accounts cannot be moved to another Group).
Page 114
3. Click Add. The Add Group dialog appears.
Add Group Dialog
Figure 6-3
4. Enter new group name and click OK. Two operations occur:
o The new group name will be listed.
o The Group Administrator is automatically created based on the Group name:
User Name - groupname_Admin (capital A in Admin, group name = up to 10 alphanumeric
characters and no spaces)
Password - Group Name (up to 16 characters).
For example, for Group MobileAccess (first 10 letters are MobileAccess):
o Group Admin name MobileAcce_Admin
o Group Admin password - MobileAccess
5. Notify each Group Administrator of his/her login name, password and group name along with a strong
recommendation (requirement) to change the default assigned password.
NOTE: Only the Group Admin has access to his/her own password definitions.
Page 115
6.1.2
Defining User Accounts
The Group Administrator can define and manage the users in his/her group. The Group Administrator cannot
see Users from any other Group.
How does it work?
The Group Administrator logs in using the Group default name and Password both based on the Group
name. It is strongly recommended to change the password.
Group Users are created via the Security sub-tab (Group Administrator session).
Each new User is defined by a Name, User Level and Password.
Additional Group Admin level users can be created by a Group Admin
Each group can support up to 20 Users.
The Group Administrator can modify the Passwords of Users in his/her Group (including their own).
Each User in a Group can modify his/her Password.
The User can be assigned one of six (0-5) access levels as described in the following sections. Users in a
group can be of different access levels.
User Definitions Management Dialog
Figure 6-4
Page 116
To create a user
1. Log in to the SC-450 with the login information of the Manager of the specific Group:
o User Name Group Administrators User Name (first 10 letters of the Group name_Admin)
o Password if this is a first time login, then use the default password group name (up to 16
characters).
Login Dialog
Figure 6-5
2. Click the Security option of the Management tab. The list of users is displayed.
3. If you are currently using the default password, click Modify Password and change the password. (Use the
new password with your next login).
User Account Management Options
Figure 6-6
4. Click the Add button. The Add User dialog appears.
Page 117
Adding a User to the Group
Figure 6-7
5. Assign the new user a User Name and select Access Level.
6. Assign Password, re-enter the Password to Confirm.
NOTE: Weak passwords will not be accepted. The user may then change his/her own password at any
time.
7. Click OK. The new User Account will be added to the list.
8. You may also:
o Add more Admin Level users to the Group all will have equal access levels.
o Remove selected users from the list (select and click Remove).
o Modify the selected User Account (select account and click Modify).
Page 118
6.1.3
Access Levels
In addition to the System Administrator, six (0-5) Group Users Access Levels are available. Each Group User
can be assigned any one of six access levels, where users of different access levels can be defined in the
same Group.
Access Levels
Figure 6-8
NOTE: Any number of users with the same user levels (including Group Administrators) can be created per
group, for a maximum of 20 users per group (up to 500 per system).
Level
User Type
Description
User
1
2
Operator
Installer
RF Tech
R/O access to Network Topology Tree and customized subset of Config

screen General tab only, not including Alarms, RF Parameters or Comments
tab or any Modify button options). See example in Figure 6-9.
R/O access to Monitor, Config and Events screens.
R/O Access to Monitor, Config and Events screens.
Write access to free text parameters to allow defining location and
identification information.
Access to Commissioning Wizard and Monitor, Config and Events screens:
Write access to all RF parameters
Page 119
Level
User Type
Description
IT Tech
Group
Administrator
R/O to all other parameters
Access to Monitor, Config and Management screens:
Write access to all non-RF parameters
Access to activity log of all users and groups
SC-450 SW upgrade
R/O to all other parameters
Capabilities:
All IT Tech and RF capabilities
Can create and manage users in this group
Example of Access Level 0 View
Figure 6-9
Page 120
6.1.4
Multi-User Sessions
The SC-450 controller supports up to three simultaneous sessions for multiple users (local/remote access).
The login of users is enabled according to priority when the maximum amount of multiple users are logged
in, the SC-450 terminates the session running for the lowest level user logged in the longest (user receives
alert message and force logout is performed) in order to enable a higher access level user to login to the
system.
A message indicating logon denial appears when the maximum number of users are logged in and a lower
level user attempts to log in to the system.
6.1.5
Group Passwords
Note the following:
Each user can modify his/her own password

The Group Administrator of each group can reset the passwords of the users (does not require old
password)
User passwords must consist of at least 8 characters; however only four asterisks (****) are displayed. SC450 management auto-checks the strength of the password and indicates if the password is too weak. Only a
reasonable or higher strength level of password will be accepted - passwords indicated as weak will not be
accepted:
To Modify the Password
1. Log in to the SC-450 Management GUI and click on the Security option of the Management tab.
2. The procedure slightly differs for different users:
Modifying User Options
Figure 6-10
Page 121
o For either a User or Group Administrator modifying own password - click on the Modify Password
button, enter the Old Password and the New Password. Click OK.
o For a Group Administrator modifying a Users password select the User, click Modify and change
the Password. Click OK.
Modifying User Password
6.1.6
Figure 6-11
Adding New User
Figure 6-12
Tracking Group Users Activity Logs
The Activity Log is used to track operations performed of all users in all groups on all devices. The screen
allows filtering according to various criteria. The Activity Log can be viewed by the following user levels:
Admin
Group Administrators
IT Techs
The displayed information can be minimized or rearranged according to options provided in the display
screen. The information can be limited to a specific time period, operations or device types via Filter options.
Page 122
6.1.6.1
Viewing the Activity Log
Click on the Management tab and then on the User Activity Log sub-tab. The full log list of all user activities in
your group is displayed.
Activity Log Display
Figure 6-13
To modify display view:

o Use Show entries to determine the number of displayed events per page.
o Click on a specific header to rearrange activities according to the selected criteria.
o Enter a specific value in Search (i.e. Serial Number, exact Time and Date and so forth) to display a
single activity row
o Use Save to export the information to a *.CSV file.
o Use Filters to limit the displayed information according to Device Type, Action Type, Date, etc.
Page 123
6.1.6.2
Filtering the Activity Log
The display can be limited according to device type, action type and time period.
NOTE: See previous section for required user levels.
To filter the Activity display
1. From the Activity Log pane (click Management tab and choose User Activity Log sub menu), click Filters
button.
Activity Log Filter Area
Figure 6-14
2. You may perform the following operations:

To Filter According to
Do this
Device Type (Controller, Add-on, Base Unit, etc.)
Use the Filter by Type drop-down menu
Action Type (Add Group, Delete User, Configure

device, etc.)
Use the Filter by Action Type drop-down menu
Specific date and time
In From and To select date, hour and minute (24

hour clock format)
Page 124
6.2 User Session Timeout

If no activity is detected by the user, SC-450 is able to enforce session time out. The session timeout period is
configurable between 1 min never.
To configure session timeout period
1. Click the Management tab of the Web GUI and then click the Security menu option.
Management Tab Security Menu Option
User Session Timeout
Figure 6-15
Page 125
2. In the Session Timeout Settings work area, click the Modify button. The session Timeout dialog appears.
Session Timeout Dialog
Figure 6-16
3. Enter timeout value between 1 min. and Never.

4. Click OK.
User Session Timeout
Page 126
6.3 SW Upgrade Procedure

The Master controller SW must be upgraded first and only then can remote master to slave SW download can
be performed. The following sections describe the procedure for both.
6.3.1
Upgrading from v4.0, v5.1, v5.2 and v5.3 to v5.4
1. Load the new image file via the Load New Firmware section in the Management tab of the Master SC-450
Controllers GUI. The new v5.4 SW is now loaded onto the Master Controllers Standby bank and is not yet
active.
2. Swap to the new firmware version. The System Controller will reboot automatically utilizing the new SW
version.
3. Load new boot loader file to support future SW upgrades via the Load New Firmware section. Do not
power cycle when loading new boot loader software. If power is lost during boot loader update, contact
Corning MobileAccess Tech Support.
4. Reboot the Controller.
Section 6.3.2 provides a more detailed description of the upgrade procedure itself.
SW Upgrade Procedure
Page 127
6.3.2
Master Controller SW Upgrade
To perform SW upgrade on Master Controller

1. Open session to controller (see section 2.7.1).
2. Click the Management tab and then the Firmware menu option. The following screen appears.
Management Tab - Firmware Menu Option Screen
Figure 6-17
3. Download the new SW for upgrade procedure as follows (refer to Figure 6-17):
o In the Load New Firmware area, click the Browse button and select SW upgrade img file: SC-450_
xx.yy.img
Note: xx=Version; yy=Build
o Click the Load button
Page 128
4. Download progress bar appears. Click OK when the message Download is Completed appears (see
Figure 6-18).
Download Complete Message
Figure 6-18
5. After the SW download (in previous step) is complete, the downloaded SW version appears in Standby
Bank (see Figure 6-19).
Firmware Menu Option for SW Upgrade
Figure 6-19
NOTE: New SW image file download may take up to 10 minutes to complete - do not attempt to refresh the
browser or perform any operation before download procedure is completed. Download progress appears in
Progress bar.
6. Download new boot loader file for future upgrades as follows (refer to Figure 6-17):
o In the Load New Firmware area, click the Browse button and select the SW upgrade Bootloader file:
Bootloader_V5_04.btl
o Click the Load button (appears after file is selected) to load the selected upgrade file on to the
controller.
Page 129
7. Click the Swap button. The Swap and Restart prompt appears:
o Click OK.
o Downloaded SW version appears in Active Bank area (see Figure 6-20) and controller is
automatically restarted.
SW Upgrade Active Bank
Figure 6-20
8. Repeat Steps 1 to 7 above to upgrade any Slave SC-450 Controller locally on site (if exist).
Page 130
6.3.3
Remote Master to Slave SW Download
NOTE: The remote master to slave SW upgrade procedure must be performed when the new v5.4 SW is
loaded on the Standby Bank of the Master Controller, before performing the Swap (step 7 in section 6.3.2).
This feature enables single-source SW upload by opening a session to the SC-450 Master and downloading
the new SW to the Master and all connected SC-450 slaves. The procedure can be performed for Slaves
connected either via RS232 (located at the headend) or via MA330 links (located at remote ends).
Note the following:
This feature is available for SC-450 Controllers only. MA410 Controllers, if used as Slave Controllers,
cannot be upgraded via the SC-450 Master Controller.
This feature is available for SC-450 Version 5.0 and higher; as such, it can be used for upgrading from
Version 5.3 to Version 5.4 and so on.
If your system includes SC-450 slaves Version 4.0, locally upgrade these to Version 5.4. The remote
upgrade feature can be used from the next upgrade (i.e. V 5.4 to the next release).
The upgrade procedure should not be performed during system setup, commissioning or configuration.
The duration of the SW distribution to upgrade remote Slave controllers via the Master controller can vary
based on the system size and topology (existence of remote Slave controllers via 330 links) and can take
up to a couple of hours to complete.
It is recommended to perform the upgrade procedure during a maintenance window, when upgrade the
alarms and events generated in the Slave controllers are not forwarded.
Page 131
To Download SW from Master Controller to Slaves

1. Click the Management tab and then click the Distribute SW sub-tab. The screen displays the list of Slave
devices according to the Port# of the Master to which they are connected (e.g. Port 9, etc).
Management Tab-Distribute SW Menu Option
Figure 6-21
2. Checkmark the Slave devices on which the upgrade procedure will be performed. (Use Deselect All
checkbox to clear selection.)
3. Load new firmware:
o Click Browse in the Load New Firmware display area and select the upgrade file to be loaded.
o Click Load.
o The new SW version appears in the Inactive SW column of the Firmware Distribution Table display
area.
4. Click the Swap button to begin the upgrade procedure.
NOTE: The progress bar shows the upgrade procedure progress for each Slave controller individually.
Page 132
5. When the upgrade procedure is complete:

o Progress bar shows 100%
o New SW version appears in the Active SW column of the Firmware Distribution Table display area.
o Firmware info is displayed in corresponding Firmware Info display area.
SW Upgrade Procedure in Process
Figure 6-22
Page 133
6.4 Generating Device Reports

The Web Management GUI enables generating inventory reports for the displayed network elements.
To Generate a Report
1. Click the Management tab in the main menu, and then click the Report menu option (on left).
Management Tab Reports Menu Option
Figure 6-23
2. Click the Create button in the Inventory Reports display area.

The Create Reports dialog appears.
Generating Device Reports
Page 134
Device Type Selection
Figure 6-24
Page 135
3. Select the device (or All) for which the report is to be created and click OK. The File Download dialog
appears, as shown in Figure 6-24.
File Download Dialog
Figure 6-25
Page 136
4. Choose Open to view the report file without saving or Save to save on the generated report on the
computer.
The inventory report is generated in an Excel format. Example shows report for BU unit.
Excel Report for BU Unit
Figure 6-26
Page 137
Mo nito ring a nd T roubles ho o ting
IMPORTANT: The available tabs and options in the SC-450 Web GUI may vary depending on the access
level used to open your session.
The Web Management Application provides several tools for monitoring and troubleshooting the site, which
include:
Monitoring connected clients

Display of events
Alarms available in the configuration dialog of each device
Network topology tree
Device view
Various parameter readings in the Advanced tab of the device configuration dialog
Using the Available Tools

Once the adjustment procedures have been completed successfully, all devices should be displayed in green
in the Network Topology tree. In addition, the Event display can be used to verify that no new events are
received and that the system is stable.
If fault notifications are received (events) or devices are displayed in red or yellow colors in the Network
Topology tree, the Alarms and Advanced tabs of the relevant devices can be used to source the problem.
Page 138
7.1 Monitoring Summary Display

The Monitor tab provides a view of the basic controller information and of events generated in the connected
devices.
To Open the Event Log Window
From the main View window, click the Monitor menu option. The Monitor window appears.
Monitor Tab
Figure 7-1
The Monitor screen consists of two display areas:
Controller Summary Displays the controller general information such as, IP address, HW version,
System Up Time (time since last boot up), etc.
Device Summary (Remote/Local) - Displays a summarized view of the events generated in the connected
devices (e.g. controllers, Bus) according to number of alerts, normal events and total events for each
device type.
Monitoring Summary Display
Page 139
7.2 Event Display

The event display is automatically updated with every change in the status of any of the system elements. By
default, up to 1,000 reported events can be displayed. Use the scroll bar on the right to scroll through the
displayed events.
Only events occurring on the network ports or the device are displayed: configuration changes that are
initiated by the network manager are not considered events.
The viewed events may be acknowledged and filtered according to various user defined criteria.
7.2.1
Viewing Events
To View the Events Log

From the main View window, click the Events menu option. The Event window appears.
Each notification consists of a unique sequence number, event date and time stamp, description and device
generating the event and the event severity.
Events Tab
Color
Gray
Yellow
Red
Blue
Figure 7-2
Event Type
Notification
Minor Event
Major Event
Device with NMS version 3.0, connected to host controller with
NMS version 3.1
Event Display
Page 140
7.2.2
Filtering Displayed Events
You may filter the displayed events according to various criteria such as device source, event level (major,
minor, etc.), event date, etc.
To Filter the Displayed Events:
1. In the Events window, click the Filters button.
Events Filter Display Options
Figure 7-3
2. To display only events from one type of device, choose the device in Filter by Type field: Controller, BTSC,
BU, RHU, HX, GX, Add-on, etc.
3. To display only events from a specific severity level and up, choose the minimum level in the Filter by
Severity field. For example, choosing Notify will display all severity levels; choosing Minor will display
Minor and Major levels only.
Event Display
Page 141
4. To display only events initiated within a limited range of time:

o Click on the blue button adjacent to the To or From fields, a calendar is opened:
Defining Date Range for Events Display
Figure 7-4
o Browse to display the appropriate months and click on the days to determine the range of time for the
displayed events.
o You may also enter specific hours and minutes to further limit the range of time:
Defining Time Range for Events Display
Event Display
Figure 7-5
Page 142
7.3 Fault Sourcing Using the Network Topology Tree

What does the Network Topology Tree show?
The Network Topology pane shows the connected network devices in the hierarchy in which they are
connected and colors corresponding to their status. All devices should be displayed in green (OK).
Disconnected devices that have been configured to the base-line will be colored gray (disconnection). These,
Red (major fault) and Yellow (minor fault) colored devices should be investigated to correct the problems.
Network Topology Tree
Figure 7-6
Quickly Finding the Faulty Unit

The color of each unit (except the controller) will depend on its local status and will not depend on the status
of the units below it.
The controller will always be colored by the severest color of any of the units under it or due to its local inputs
(OR operation).
Units name in the tree will consist of the unit type description followed by the user free text: e.g. BTSCCellular Company 1800 north section e.g. Cont-..
The units relative connection (port and slot) will continue to appear in the elements private window on the top
bar
Fault Sourcing Using the Network Topology Tree
Page 143
Table 7-1 shows examples of problems indicated by major and minor faults for various devices.
Device Status
RIU Status
Base Unit Status
RHU Status
OCH Status
GX Status
ORU Status
Description
Minor Fault (Yellow):
Unsuccessful Adjustment, Adjustment not available
RF Overload signal to the system (from BS or signal generator) is higher
than the system was currently calibrated to receive
Major Fault (Red)
RF Underload
SW disconnected RF switch service disabled
Service OFF no RF input detected
Unsuccessful Adjustment state (DRY or WET), (Adjustment not available is
legal(RF overload
Low PDI level from RHU
FSK Unlocked
Laser Unlocked
Major Fault (Red):
Low RF In
Optical Link from BU=LOW
Antenna installed but not OK (but at least one installed antenna is OK)
Unsuccessful Adjustment state , (Adjustment not available is legal)
Laser Status - Unlocked
FSK Status Unlocked
Major Fault(Red):
RF output towards antenna is at least 15 db less than measured during the
adjustment procedure
None of the installed antennas is OK
Both Bands = OFF
Low DL input power
Major Fault (Red):
Communication problems with OCH IF card
Failed optical adjustment procedure
Low or no optical link level
RF switch service disabled by the User (via RF Parameters tab)
Major Fault (Red):
Failed adjustment procedure
High DL output power
Major Fault (Red):
Communication problems with Ethernet card
Faulty fan status
Table 7-1. Device Major and Minor Faults
Fault Sourcing Using the Network Topology Tree
Page 144
7.4 Fault Sourcing Using the Device View

When an item in the Network Topology Tree is clicked, an icon representative of the device view appears
along with the configuration tabs. The LED indicators in the device view represent the true LED behavior on
the unit front panel. The administrator can then analyze the display and assess the situation at a glance.
For example
If a Base Unit Link LED is red, then either the connection or the RHU at the remote end is faulty. If all laser
Link LEDs are red, there may be a problem with the BU.
Grey LEDs indicates that connections have not been detected for the port.
Example of BU Config Tab with Device View
Fault Sourcing Using the Device View
Figure 7-7
Page 145
7.4.1
RIU View
7.4.1.1
RIU-12 Device View
A device view is provided for both the CMU and the selected BTSC. The complete chassis is displayed for
both, however different elements are indicated depending on the selected device.
CMU Device View Indicates the selected service configuration (1-12; 4+8) with a blue frame in addition
to the CMU LEDs. See example in Figure 7-8.
RIU-12 CMU Device View
Figure 7-8
BTSC View - Highlights the selected BTSC module and displays the LED status indicators for both CMU
and for each BTSC module.
BTSC Device View
Figure 7-9
Page 146
Module
LED
Description
CMU
PS
Steady Green power input detected in CMU (25-56 VDC)

Off - No power input detected in CMU
Fans
Indicates fan status of all four modules:

Steady Green Normal operation status for all fans
Blinking Green - Fault detected in at least one fan module
Run
Initialization status of CMU SW:

Steady Green CMU SW up and running
Blinking Green CMU SW initializing
BTSC
Run
Indicates initialization process of conditioner SW:

Steady GREEN - Conditioner module SW up and running
Blinking GREEN - Conditioner module SW halted/SW upgrade in
process
Off - No power detected by conditioner module
Over Power
Indicates if DL RF level in conditioner modules higher than the max

expected power:
OFF - DL RF power in conditioner module is < Max expected power and
> -18 dBm
Blinking RED - DL RF power in conditioner module is +3 dBm > than
Max expected power. The DL over power alarm is triggered
Steady RED - DL RF power in conditioner module is +5 dBm > than Max
expected power. The Protection function is activated, turning the service
off.
Under Power LED
Indicates if DL RF level in conditioner module is lower than the max

expected power:
Off - DL RF power in BTSC module is < Max expected power
and > -18 dBm
For LTE: -25 dBm
Steady RED - DL RF power in BTSC module is < Max expected power 18 dBm
Page 147
7.4.1.2
Legacy RIU Units (RIU-4, RIU-IM and RIU-Lite)
The RIU-4, RIU-3 and RIU-Lite all share common LED status indicators.
Example of RIU Device Views
Figure 7-10
LED
Description
PWR
ON input power is within the required range
RUN
Green Flashing corresponding BTSC/BDAC module is operational
DL Overload LED
Blinks when service is attenuated by 3db or more due to the BTSC

AGC mechanism.
Constantly ON when the service is 30 db attenuated due to AGC
mechanism or turning OFF the service
DL LOW Signal LED
Blinking input signal to the BTSC is at least 15 db lower than the

value measured during the adjustment procedure
NOTE: RIU-IM and RIU-4 BTS/BDA conditioners can be installed in any order. For RIU-4 only - 4th slot must
be occupied in order to be automatically detected as an RIU-4 unit and be displayed as such in the device
view.
Page 148
7.4.2
PAU-6
The PAU-6 device view shows the status LEDs for the PCMU (PAU-6 Control Module Unit) and Backup
PCMU modules.
Example of PAU-6 Device View
Figure 7-11
Module
LED
Description
PCMU
PS
Steady Green Input power is within the required range (21-59V DC)
Off No input power detected
Fans
Steady Green Fan operation status ok for all fans

Blinking Green Fault detected in at least one fan module
Run
Green Steady PCMU SW up and running

Blinking Green PCMU SW initializing
Backup PCMCU
PS
Steady Green Input power is within the required range (21-59V DC)
Off - No input power detected
Page 149
7.4.3
Base Units View
When selecting an OPTM from the network topology, the Base Unit device view shows the LED status
indicators for both OPTM modules.
Example of BU Device View
Figure 7-12
LED
Description
PWR
GREEN - Power input detected for the corresponding unit.

20 to 48 VDC
LSR
GREEN - laser circuitry for the corresponding element (group of four ports) is
functioning correctly.
Link 1-4, 5-8
GREEN - the optical link to/from the connected remote unit functions within the
specifications in both directions.
Blinking - optical power from remote is lower than required
Grey - Ports to which no remote units are defined
Page 150
7.4.4
RHU View
The RHU device view shows the power, communication and link status LED indicators.
RHU Device View
Figure 7-13
LED
Description
COMM
Green - Active communication detected
LINK
Green - Optical link to BU detected
PWR
ON Power input detected for the corresponding unit

20 to 48VDC
7.4.5
Add-On View
The Add-On device view shows the modules Power and RUN LED status indicators.
Add-On Device View
Figure 7-14
LED
Description
RUN
Green Blinking- indicates that the RHU is in normal operating mode.
PWR
Green - Power input detected for the corresponding unit
Page 151
7.4.6
WMTS Element Views
7.4.6.1
RIM-Main View
The RIM-Main view shows an illustration of the front panel Power and Run LEDs.
RIM-Main Device View
Figure 7-15
LED
Description
RUN
Green Blinking- indicates that the unit processor is running
PWR
Green - Power input detected for the corresponding unit
7.4.6.2
RIM-1400 View
The RIM-1400 device view shows an illustration of the units four front panel LEDs.
RIM-1400 Device View
LED
PWR
RUN
(Master) CONFIG
(Master) ACTIVE
7.4.6.3
Figure 7-16
Description
GREEN - Power input detected for the corresponding
unit
GREEN - software running correctly
GREEN - unit is configured as Master (although it may
operate as a Slave due to other conditions).
GREEN - unit is currently operating as a Master
WMTS RHU-4 View
The WMTS RHU-4 view shows the units three front panel LEDs.
Page 152
RHU-4 Device View
Figure 7-17
LED
Description
COMM
GREEN - Internal communication OK
Link
GREEN - Optical link to BU detected
PWR
GREEN - DC power connected
Page 153
7.4.7
FT-350 Elements Views
7.4.7.1
OCH View
The OCH view shows an illustration of the units front panel Link, Power and LSR LEDs for each optic
module.
Example of OCH Device View
Figure 7-18
LED
Description
PWR
GREEN - Power input detected for the corresponding unit.

20 to 48 VDC
LSR
GREEN - laser circuitry for the corresponding element (group of four ports) is
functioning correctly.
Link
GREEN - the optical link to/from the connected remote unit functions within
the specifications in both directions.
Blinking - optical power from remote is lower than required
Grey - Ports to which no remote units are defined
Page 154
7.4.7.2
ORU View
The ORU device view displays the LED status indicators for both optical modules.
Example of ORU (MIMO) Device View
Figure 7-19
LED
Description
Run
Status of optic adjustment procedure as well as unit processor condition:

Green Blinking normal. Successful adjustment and processor running.
Orange Blinking - adjustment failed or not performed
Not blinking (Green, Orange, OFF) unresponsive unit
Link
STEADY GREEN Normal Optical link level from OCH

BLINKING GREEN Low optical level from OCH
OFF No optical link is detected from the OCH
PWR
GREEN - Device is powered

RED No power supplied to the unit
Page 155
7.4.8
VE VCU View
The VCU can either function as a Master or Slave unit, therefore some of the LED status descriptions vary
depending on the function of the unit.
Example of VCU Device View
Figure 7-20
LED
Description
VAP Status
GREEN - Connected VAP/VCU (depends on Master/Slave configuration)

Grey No VAP detected for this unit
ACT
Blinking GREEN normal operation
PWR
GREEN - DC power connected
RF LED
Green Master VCU only. Normal RF level

Off VCU is Slave
Master
Status of the connection to the Master VCU:

Off Master mode (not connected to VCU)
Blinking Green During attachment process with Master VCU
Solid green Slave (IF-IF) mode and connected to Master
Page 156
7.4.9
HX Indoor/Outdoor Views
The HX indoor remote unit displays the Power, Comm and Link status LED indicators (physically located on
the HX services module located inside the cabinet).
HX Indoor Device View
Figure 7-21
LED
Description
Color
Status
Power
Device is powered
GREEN
Steady On
Power not supplied to the unit
GREEN
Off
When connected and discovered by an

OPTM (BU)
GREEN
Blink per communication

attempt
When device is powered on but no

external communication is received
GREEN
Steady Slow Blink
No Optical link is present
GREEN
Off
Low optical link level from OPTM
GREEN
Blink
Normal optical link level from OPTM
GREEN
Steady On
Comm
Link
Page 157
The HX outdoor remote unit device view shows an illustration of the unit.
NOTE: The unit includes only a power LED which is not displayed in the device view.
HX Outdoor Device View
Figure 7-22
Page 158
7.4.10 HXn View

The HXn remote unit device view icon displays the LED Status indicators for Module 1 (SISO) and Module 2
(MIMO) in addition a fan status LED which are all physically located on the HXn front panel.
NOTE: In SISO configurations, the Module 2 LEDs appear gray.
HXn Device View
LED
Run
Comm
Link
Service
ANT
Temp
Fan
Figure 7-23
Description
Steady Green Input power detected in module
Off No power input detected
Blinking Green - Connected and discovered by an OPTM (OCH Optical Module)
Off - No external communication is received
Steady Green Optical link level from OPTM above normal threshold
Blinking Green - Optical link level from OPTM lower than threshold
Off - No Optical link is present
Green Service status OK
Red Fault detected in service (at least one service alarm is set)
Steady Green - VSWR alarm is clear
Red - VSWR alarm is set
Green Temperature between normal threshold
Red - Over Temp alarm or Over Temperature Protection is set
Green Fan status OK
Red Fault detected in at least one fan
Page 159
7.4.11 GX Tri-Band View

The GX device displays the Run, Alarm and FSK status LED indicators (physically located on the underside
of the unit).
GX Device View
Figure 7-24
LED
Description
RUN
GREEN Power on
ALM
OFF Normal operation

RED - Fault
FSK
Indicates status of Frequency Shift Key operation : Green Flashing

Normal FSK
OFF Fault in FSK
operation
Page 160
7.4.12 GX-Quad View

The GX-Quad device displays the Run, Alarm and COMM status LED indicators (physically located on the
underside of the unit), as shown in Figure 7-28.
GX-Quad Device View
Figure 7-25
LED
Description
RUN
GREEN Power on
ALM
OFF Normal operation

RED - Fault
COMM
Indicates status of Frequency Shift Key operation:

Green Flashing Normal FSK
OFF Fault in FSK operation
Page 161
7.5 Fault Sourcing through the Device Alarms

Once a device fault indication is identified, the Alarms pane area in the device configuration dialog can be
used to provide further information on the source of the problem. Users may enable or disable specific alarms
according to their needs.
7.5.1
Viewing Device Alarms
The alarms for each device are available through the Alarms pane area in the device Config tab. To display
the alarms, double-click on the device item in the Network Topology tree. See example in Figure 7-26
Example of Alarms Tab
Figure 7-26
As illustrated in Figure 7-26 (BTSC Alarms), enabled Alarms are displayed with a color indication of their
severity.
Alarm Color
Severity Status
Red
Major fault
Yellow
Minor Fault
Green
OK
Fault Sourcing through the Device Alarms
Page 162
7.5.2
Masking Irrelevant Alarms
This section describes how to mask (disable) alarms which are irrelevant. The example below shows the HX
alarms.
To mask irrelevant alarms
In the example below, the HX Cabinet Alarms dialog shows the alarm response if the Service 2 DL Output
Power Low alarm is NOT masked (enabled). In that case the Service 2 and Overall Status will be RED
indicating a fault.
Example of Masking Irrelevant Alarms
Figure 7-27
If the Service 1 alarm is MASKED (Disabled), then the LED for the alarm will be RED; but, the corresponding
Service alarm in HX Cabinet Alarms area will be GREEN showing NO Fault.
NOTE: The Overall Status alarm will only show green if all of the generated alarms are masked (or if all
alarms are green).
Page 163
7.5.3
RIU-12
There are two types of RIU-12 alarms, where each type is displayed in a dedicated tab:
CMU Alarms displays the system chassis alarms

BTSC displays the RF conditioner alarms
7.5.3.1
CMU Alarms
To Display the CMU Alarms

Double-click the RIU-12 CMU item in the Network Topology tree.
RIU-12 CMU Alarms Tab
Figure 7-28
Table 7-2 describes the CMU (system) alarms:

Alarm Name
Description
General Alarms
N/A
Fans Faulty
Green: Fans status OK
Over Temperature
Green: Ambient temperature inside the HX unit >55C
Overall Status
Overall status of enabled alarms
Table 7-2: CMU Alarms Description
Page 164
7.5.3.2
BTSC Alarms
To Display the BTSC-12 Alarms Tab

Double-click on the BTSC-12 item in the Network Topology tree. See example in Figure 7-29.
BTSC-12 Alarms Tab
Figure 7-29
Table 7-3 describes the RIU-12 alarms:

Alarm Name
Description
Adjustment
Yellow (minor fault) Adjustment procedure was not successful.
DL Power Overload
Red (major fault): BTS RF power input to the BTSC is at least 3 dB higher than
the value measured during the adjustment procedure.
DL Input Power Low
Red (major fault): BTS RF power input to the BTSC is at least 15 dB lower than
the value measured during the adjustment procedure.
Service OFF
Service was turned off either by the system (in response to AGC out of limits) or
by the user.
UL Power Overload
Red (major fault): RF power input to the BTSC is at least 3 dB higher than the
value measured during the adjustment procedure.
Over Temperature
Ambient temperature >55C
Overall Status
Overall status of enabled alarms.
Table 7-3: BTSC Alarms Description
Page 165
7.5.4
Legacy RIU Units (RIU-4, RIU-IM and RIU-Lite)
7.5.4.1
BTSC/BDAC Alarms
To Display the BTSC/BDAC Alarms Tab

Double-click on the BTSC item in the Network Topology tree. The example in Figure 7-30 shows the BTSC
Alarms tab for the RIU-IM, however the tab is the same for the RIU-4 and RIU-Lite products.
BTSC/DBAC Alarms
Figure 7-30
The following table describes the RF Conditioner (i.e. BTSC/BDAC) alarms:

Alarm Name
Description
Adjustment Fail
Yellow (minor fault) Adjustment procedure was not successful.
DL Power Overload
Red (major fault): BTS RF power input to the BTSC is at least 3 dB higher than the
DL Input Power
Low
Red (major fault): BTS RF power input to the BTSC is at least 15 dB lower than the
Service Off
Service was turned off either by the system (in response to AGC out of limits) or by
the user.
Overall Status
Overall status of enabled alarms.
Page 166
7.5.5
PAU-6 Alarms
To Display the PAU-6 Alarms Tab

Double-click on the PAU6 item In the Network Topology tree. The Config window appears with the Alarms
dialog (continuously displayed in window).
PAU-6 Alarms
Figure 7-31
The following table describes the PAU-6 alarms when triggered:

Alarm Name
Description
Fan 1/2/3/4
Green All fans are operating normally

Red - Indicates at least one faulty fan (fan does not match duty cycle set
value)
Power Failure
Green The voltage in both the Main and Backup power sources is > 25 V
Red - Indicates failure in main or backup DC power source (< 25 V)
Over Temperature
Green Measured temperature in unit < 69 C

Red Measured temperature in unit > 72 C
Overall Status
Page 167
7.5.6
Base Unit Alarms
To Display the BU Alarms Tab

Double-click on the BU item In the Network Topology tree.
BU Alarms
Figure 7-32
The following table describes the BU alarms when triggered:

Alarm Name
Description
RF Overload
Indicates overload of BTS RF power input to the BTSC
DL Input Power
Indicates BTSC RF downlink power input to the BTSC is low
UL OPT Link 1-4
Indicates if optical power from remote is lower than required
Overall Status
Page 168
7.5.7
RHU Alarms
To Display the RHU Alarms Tab

Double-click on the RHU item in the Network Topology tree.
RHU Alarms
Figure 7-33
The following table describes the RHU alarms:

Alarm Name
Description
DL OPT Link
Green - Power of optical link input detected
Adjustment 1st/2nd Band
Green - Success of adjustment procedure of 1st/2nd band
Low Output Power 1st/2nd Band
Power level of DL signal on antenna ports lower than threshold
Antenna 1-4
Green - Connections of specific antennas are identified
Overall Status
Page 169
7.5.8
Add-On Alarms
To Display the Add-On Alarms Tab

The Alarms tab may be displayed using one of the following methods:
In the Network Topology tree, double-click on the add-on item.
Add-On Alarms
Figure 7-34
The following table describes the RHU alarms:

Alarm Name
Description
Adjustment
Success of adjustment procedure
Low Output Power
Power level of DL signal on antenna ports is low
Page 170
7.5.9
WMTS Elements Alarms
7.5.9.1
RIM-Main Alarms
The only alarm viewed for the RIM-Main unit is the Overall Status alarm, indicating whether a fault is detected
in one of the hosted units connected to the RIM-MAIN.
To display the RIM-Main Alarms tab
The Alarms display area appears in the RIM-Main Config window.
RIM-Main Configuration Window
Figure 7-35
Page 171
7.5.9.2
RIM-1400 Alarms
To display the RIM-1400 Alarms tab

The Alarms display area appears in the RIM-1400 Config window.
RIM-1400 Alarms
Figure 7-36
The following table describes the RIM-Main al arms:

Alarm
Description
Synth Unlock
Sync alarms. Sync unlocked (major)
Internal Clock Presence
Internal Clock failure. (Major)
External Clock Presence
External Clock failure. (Major)
Reference Draft
No external clock reference is detected.
Adjustment
Synchronization adjustment procedure status.
Maintenance
Synchronization adjustment procedure is due.
Overall Status
Calculated according to its active alarms corresponds to highest

alarm level detected.
Page 172
7.5.9.3
RHU-4 Alarms
The Alarms display area appears in the RHU-4 Config window.
RHU-4 Alarms
Figure 7-37
The following table describes the RHU-4in alarms:

Alarm
Description
DL OPT Link
Power of optical link input
Adjustment 2nd band
Not relevant
DL Output power 2nd band
Power level of DL signal on antenna ports
Antenna 1/2/3/4
Connections of specific antennas are identified
Overall Status

Page 173
7.5.10 FT-350 Alarms and Troubleshooting

7.5.10.1 OCH Alarms
To Display the OCH Alarms tab
The Alarms display area appears in the OCH Config window.
Example of OCH Alarms
Figure 7-38
The following table describes the OCH alarms:

Alarm
Type
Description
I/F Card Comm. Error
General
Indicates communication timeout (5 consecutive time-outs for

communication attempts) between the optical module and the
FPGA in the I/F card. In case of alarm/unit must be replaced.
DL Input Power Low
General
RED - DL RF input Power from the BTS interface source is lower

by 15dBm (or more) from the Max Expected Pin.
DL Input Power High
General
RED - DL RF input Power from the BTS interface source exceeds

the maximum expected Pin by more than 5 dBm.
Optical Adjustment
Fail
Link
RED Optical adjustment procedure failed in one of the links.
Page 174
Alarm
Type
Description
UL Optical Link Fail
Link
Low optical level from ORU (link level < 56)
Mismatch
Link
N/A FUTURE Mismatch between optical module and endequipment.
Overall Status
General

7.5.10.2 ORU Alarms

Click the ORU item in the network topology to view the ORU Alarms display area in the Con fig window.
Example of ORU Alarms
Figure 7-39
The following table describes the ORU alarms:

Alarm
Description
General Alarm
N/A
Optical Link Alarm
Low optical level from OCH
Fans Alarm
Faulty fans
Service 1/2/3/4
Summary of all VE port x monitored parameters displayed in the Alarms sub-tab
Service 5 (BB)
Summary of Add-On port (Broad Band) monitored parameters displayed in

Alarms tab
Page 175
Alarm
Description
Overall Status
Calculated according to its active alarms corresponds to highest alarm level

detected.
7.5.10.3 Troubleshooting Procedures

OCH RF Adjustment
If the (DL) Input power Low or (DL) Input power High alarms are not green, then the RF input signal (from RIU
or passive interface) is correspondingly low or high.
NOTE: This procedure is ONLY for EXPERIENCED service personnel.
Example of Low Input Power Indication in OCH Alarms and RF Parameters Tabs
Page 176
Figure 7-40
To compensate for low or high DL input power signals from BTS

1. Click the OCH RF Parameters tab.
OCH RF Parameters Tab
Figure 7-41
2. If (DL) Input power = Low or High, then the measured input power from the BTSC to the RF to optic
conversion unit.
o When connected to RIU: Up to -20dBm
o When connected directly to BTS (via passive interface): Up to 0dBm
3. For Low Input Power value - in the Manual DCA field, lower the attenuation level by the required amount.
4. For High Input Power value - in the Manual DCA field, increase the attenuation level by the required
amount.
5. To reset to factory levels, click Restore.
Page 177
7.5.11 EC560 Elements Alarms

7.5.11.1 EHU Alarms
To Display the EHU Alarms Tab
The Alarms tab can be displayed by double-clicking the EHU item and viewing the EHU Alarms and Mask
display area.
EHU Alarms Tab
Figure 7-42
The following table describes the EHU alarms:

Alarm Name
Description
Temperature
Green - Normal
Red Temperature of units exceeded normal range
Power Supply Slot 1/2/3
Power Supply Status redundancy ready:

Green Normal
Red Fail
Gray - Empty
Ethernet Port A/B/C/D
Port Status Green: Connected

Red: Disconnected
Page 178
7.5.11.2 AU Alarms
To Display the AU Alarms Tab
In the Network Topology tree, double-click on the AU item (under the host EHU) and refer to the AU Alarms
and Mask display area.
AU Alarms Tab
Figure 7-43
The following table describes the AU alarms:

Alarm Name
Temperature
Ethernet Port A/B/C/D
Description
Green - Normal
Red Temperature of units exceeded normal range
Port Status Indicates whether an STA device is connected to the port.
Page 179
7.5.12 VE Alarms
7.5.12.1 VCU Alarms
To Display the VCU Alarms Tab
In the Network Topology tree click on the VE VCU unit (hyperlink) to access the VE Web GUI. Refer to the
relevant MobileAccessVE User Manual (Single-Band/Dual-Band/UMTS/WiMAX/LTE) for description of VCU
alarms.
Example of VCU Alarms Tab
Figure 7-44
Page 180
7.5.12.2 VAP Alarms

To Display the VAP Alarms Tab
In the Network Topology tree click on the VE VAP (hyperlink) unit (under the host VCU) to access the VE
Web GUI.
Refer to the relevant MobileAccessVE User Manual (Single-Band/Dual-Band/UMTS/WiMAX/LTE) for
description of VAP alarms.
VAP Alarms Tab
Figure 7-45
Page 181
7.5.13 HX Alarms
The following tables provide descriptions of the device alarms displayed in the HX Cabinet Alarms tab (Table
7-4) and HX Service Alarms tab (Table 7-5).
HX Cabinet Alarms Tab
Figure 7-46
Alarm
Description
HX General Alarm
N/A
Optical Link Alarm
Low optical level from BU (link level < 56)
Fans Alarm*
Faulty fans
Service 1/2/3/4
Summary of all port x / PA x monitored parameters displayed in the

Service Alarms sub-tab
Overall status

Table 7-4. HX Cabinet Alarms Description

*The Fans alarm is only relevant for the HX Indoor unit. The alarm can be masked for HX Outdoor units (see section 7.5.2).
Alarm
Description
Service Off
Service disabled by the User
Adjustment
Adjustment for target DL Output Power
VSWR Alarm
Antenna disconnected (VSWR > 5:1)
DL Output Power High
DL Output Power > Target Adjustment value + 2dB
DL Output Power Low
DL Output Power < Target Adjustment value 1 15dB
Over Temperature
Ambient temperature inside the HX unit >65C
Table 7-5. HX Service Alarms Description
Page 182
7.5.14 HXn Alarms

The HXn Alarms are displayed in the Alarms tab of the Config window. The HXn Alarms tab includes both
system and service level alarms. Table 7-6 provides a description of the HXn Alarms tab.
HXn Alarms Tab
Figure 7-47
Alarm
Description
Service OFF
Green Service On
Red - Service shutdown (e.g. User disabled, Temperature
Protection, etc,)
DL Power High
Green - DL Output Power < Max. output power

Red - DL Output Power > Max. output power + 2 dB
DL Power Low
Green - DL Output Power < Max. output power -18 dB

Red - DL Output Power > Max. output power -20 dB
VSWR Alarm
Antenna disconnected (VSWR > 5:1)
Adjustment Fail
Green DL RF Adjustment=Success
Red - DL RF Adjustment=Fail
DL Protection Activated
Green DL Output Power < Max output power

Red DL Output Power > Max output power +3 dB
Low Optical Link
Red - Low optical level from OCH (link level < 56)
Temperature High
Green Measured temperature <Threshold -5C
Page 183
Alarm
Description
Red Measured temperature >Threshold
Temperature Protection
Green Measured temperature <Threshold -5C

Red Measured temperature >Threshold
Note: Measured temperature >Threshold +10C= service
shutdown
Fans Faulty
Green Fan status (operation/speed)of all fans OK

Yellow One fan out of four stalled or wrong fan speed detected
Red More than one fan stalled or wrong fan speed detected in
more than one fan
Overall status

Table 7-6. HXn Alarms Description
Page 184
7.5.15 QX Alarms
Note: RHU modules are not indicated in the topology tree as a QX element. They appear under the host BU
and a dedicated QX Fan alarm appears in the RHU Alarms display.
The displayed QX alarms are per RHU and Add-On module in the QX chassis. However, the QX chassis fan
alarm is displayed only via the RHU GUI.
To Display the QX Alarms
In the Network Topology tree click on the RHU item (under the host BU/ OCH) and refer to the RHU Alarms
display area.
QX (RHU) Alarms Tab
Figure 7-48
The following table describes the QX alarms for the RHU module.
Alarm
Description
DL OPT Link
Green - Power of optical link input detected
Adjustment 1st/2nd
Band
Green - Success of adjustment procedure of 1st/2nd band
Low Output Power

1st/2nd Band
Power level of DL signal on antenna ports lower than threshold
Antenna 1-4
Green - Connections of specific antennas are identified
QX Fan
Green Fan status OK

Red - Faulty fans
Overall Status
NOTE: The QX Add-On alarms are the same as for MA1000/MA2000 Add-On modules see section 7.5.8.
Page 185
7.5.16 GX Alarms
7.5.16.1 GX Tri-Band
To Display the GX Tri-Band Alarms
In the Network Topology tree click on the GX item (under the host OCH) and refer to the GX Service Alarms
display area.
GX Service Alarms Tab
Figure 7-49
Alarm
Description
Door Open
Triggered when a GX panel is open
Optical Link
Triggered upon following conditions:
Optical Tx level<= threshold (0 dBm)

Optical Rx level <= threshold (-11 dBm)
Fans
Indicates fault in one or more of the eight GX fans
Over
Temperature
Ambient temperature inside the GX unit >85C
Service 1/2/3
Summary of all port x / PA x monitored parameters displayed in the Service
Alarms sub-tab
Overall status

detected.
Table 7-7. GX Tri-Band Alarms Description
Page 186
GX Tri-Band Service Alarms Tab
Figure 7-50
Alarm
Description
Service Switch
Service disabled by the User (via RF Parameters tab)
Adjustment
Green Successful adjustment procedure

Red Failed adjustment procedure
DL PA
Faulty PA
VSWR
Antenna disconnected (VSWR > 1.5:1)
UL ALC
UL input power > -40dBm
Note: If alarm is triggered, the input power level will need to be degraded to -43
dBm for normal status.
DL Output Power
High
DL Output Power
Low
DL Output Power lower than low power threshold
UL LNA
Faulty UL LNA (Low Noise Amplifier)
Table 7-8 provides a description of the Service Alarms shown in Figure 9-38.
Alarm
Description
Service Switch
Service disabled by the User (via RF Parameters tab)
Adjustment

DL PA
Faulty PA
VSWR
Antenna disconnected (VSWR > 1.5:1)
UL ALC
UL input power > -40dBm
Page 187
Alarm
Description
DL Output Power
High
DL Output Power
Low
UL LNA
Faulty UL LNA (Low Noise Amplifier)
Table 7-8. GX Tri-Band Service Alarms Description
Page 188
7.5.16.2 GX-Quad Band Alarms

Three types of monitoring alarms are provided for the GX Quad-Band remote unit:
System alarms
Service alarms
External alarms (configurable)
To access the GX Quad-Band Alarms
In the Network Topology tree click on the GX-Quad item (under the host OCH). The GX System Alarms tab
(Figure 7-51) is continuously displayed in the Config window.
To view Service Alarms (Figure 7-51) and External Alarms (Figure 7-52), click on the corresponding tabs.
NOTE: Refer to section 9.4.3 for details on configuring the GX Quad-band external alarms.
GX-Quad System and Service Alarms Tabs
Figure 7-51
Table 7-9 provides a description of the GX Quad-band system alarms shown in Figure 7-51.
Alarm
Description
Door Open
Green GX panels closed

Red GX panel open
Optical Link
Green Optical link levels between threshold values

Red - Triggered upon following conditions:
Optical Tx level<= threshold (0 dBm)
Optical Rx level <= threshold (-11 dBm)
Page 189
Alarm
Description
Fans
Indicates fault in GX fans (Four main fans and three backup fans):
Green Normal operation for all fans
Yellow (Minor) Fault detected in at least one of the four main fans, where
backup fan operational
Major Fault detected in both main and backup fans
Over Temperature
Green - Temperature inside the GX unit between threshold values

Red - Temperature inside the GX unit >85C
Service 1/2/3/4
Summary of all port x / PA x monitored parameters displayed in the Service

Alarms sub-tab
Red Fault detected in at least one of the service ports
Overall status

detected.
Table 7-9. GX Quad-Band System Alarms Description
Table 7-10 provides a description of the GX Quad-band service alarms shown in Figure 7-51.
Alarm
Description
Service Switch
Indicates service control status:

Green - Service enabled
Red - Service disabled/shutdown
Adjustment

DL PA
Indicates DL Main Amplifier status:

Green PA Status ok
Red - Faulty PA
VSWR
Red - Antenna disconnected (VSWR > 1.5:1)
UL ALC
Red - UL input power > -40dBm
DL Output Power High
Red - DL Output Power > Target Adjustment value + 2dB
DL Output Power Low
Red - DL Output Power lower than low power threshold
UL LNA
Indicates UL Main Amplifier status:

Red - Faulty UL LNA (Low Noise Amplifier)
Table 7-10. GX Quad-Band Service Alarms Description
Page 190
Figure 7-52 shows an example of external alarms configured for the GX-Quad. The Severity column displays
the severity determined for the configured alarm, whereas the adjacent LED provides an indication of the
alarm status.
Note: Refer to section 9.4.3 for details on how to configure the external alarms for a device supporting this
feature.
Example of GX Quad-Band External Alarms Tab
Page 191
Figure 7-52`
8 Ma na gement U s ing A ny S ta nda rd S N MP

Ma na ger
8.1 SNMP Destination Address Configuration
Use this option to define the IP addresses to which SNMP traps will be sent. The IP addresses are defined
per domain and are relevant to all the controllers assigned to that domain. Up to 10 IP addresses can be
defined per domain.
To Define the Destination IP Addresses
1. Click the Management in the menu bar and select SNMP Config in the side bar. The following pane
appears.
Management Tab SNMP Config Menu Option
SNMP Destination Address Configuration
Figure 8-1
Page 192
2. Click Add New, the Trap Destination IP Address dialog appears (Figure 8-2).
Trap destination IP Address Dialog
Figure 8-2
3. Enter the IP address and click OK. The IP address will be added to the list.
NOTE: To remove the IP address, click the Remove button adjacent to the IP address.
SNMP Destination Address Configuration
Page 193
8.2 Modifying the Read/Write Community Parameters

Use this option to modify the Read/Write Community Name of the SC-450.
To Modify the Read/Write Community Name
1. Click the Management in the menu bar and select SNMP Config in the side bar. The Management pane
appears.
2. In the SNMP Configuration area, click Modify.
SNMP Community Modify Dialog
Figure 8-3
3. Define the new Read and Write values and click OK.
Modifying the Read/Write Community Parameters
Page 194
8.3 SNMP Management using any Third Party SNMP

Manager
The SC-450 includes several MIB files that enable you to view traps sent by the controller and to configure
and monitor the managed MobileAccess system through any third party SNMP manager (such as HP
OpenView, CA Unicenter, IBM Tivoli, Castelrock SNMPc).
Three MIBs are Provided:
MIB-II system group parameters group (RFC-1213) A standard MIB supported by all SNMP managed
devices.
ma_devices Describes the architecture of the managed system and elements.

ma_events Holds the events in the system and the definitions of the traps and their destinations.
NOTE: Whereas the MIBs provide information regarding the managed system and a general indication of
system failure, the SC-450 management application provides a graphical view of the managed network
topology, a graphical view of the managed element parameters and enables identifying the source of the
problem at a glance.
8.4 Loading the MIB Files

To View the Traps Using a Third Party Management Application:
NOTE: It is assumed that the controller's IP address was configured and that the trap destination addresses
are configured according to section 8.1.
1. Start the management application.
2. Load and compile the MIB-II file (a public domain file which can be found on http://www.rfc-editor.org).
3. Load and compile the ma_devices.mib file.
4. Load and compile the ma_events.mib file.
NOTE: In most cases the MIB file is loaded and compiled using the MIB menu tool items on the main menu of
the management application.
SNMP Management using any Third Party SNMP ManagerPage 195
8.5 Viewing the Traps

After performing the configuration commands, use the MIB browser utility to view the trap destination table.
To do so, simply select the trapDestinationsTable MIB entry and use the table view utility (mostly part of the
MIB browser). The viewed table should hold a list of IP address to whom traps will be send.
NOTE: Set the SNMP manager GET community to the correct community string (default GET community
string is "public"). Default Trap community string is trap. All Get and Set commands are SNMP V2c; all traps
are SNMP V2c except for 430 cold start trap which is SNMP V1.
All traps generated by the controller will now be sent to the configured list of the SNMP managers. A complete
list of traps is found on the ma_events.mib file.
View the Events Table
The controller is logging the last sent events in a table (about the last 1000 sent events). Each sent trap is
kept as single entry in the events table.
Use the MIB browser utility, simply select the traps Table MIB entry and use the table view utility (mostly part
of the MIB browser).
The viewed table should hold a list of logged events (traps). Each trap entry holds the following data items:
Event unique sequence ID (trapsSequenceID column) Unique identifier of the logged event (unsigned
long, 32 bits).
Event time stamp (trapsTimeStamp column) The time and date of the logged event (string formatted time
and date HH:MM:SS DD/MM/YY).
Event generic type (trapsGenericType column) The event generic type (currently all events are
proprietary, generic type = 6).
Event specific type (trapsSpecificType column) The event specific type (equals to the trap type,
according to the list of traps as found on the ma_events.mib file).
Event source device type (trapsDeviceType column) The device type which generated the event (i.e.
controller, BTSC, VU, RHU, Add-On).
Event source serial number (trapsDeviceSerial column) The device serial number which generated the
event.
Event source indexes (trapsDeviceIndex, trapsDevicePortIndex, trapsDeviceConnIndex and

trapsDeviceInternalIndex columns) The device indexes in the system (controller index, controller port
index, device slot ix and RHU/Add-On index) which generated the event.
Event text description (trapEventText) A short textual description of the event.

Serial number of the controller generating the event (trapsCtrlSerialNum)
The last event sequence ID of the controller generating the trap (trapsCtrlLastSeqID)
Event source device name (trapsCtrlName) The textual name of the device which generated the event.
Event severity (trapsSeverity) The severity (Notify, Minor or Major) of the event.
Connector index of the base controller that connects to the generating device (trapsDeviceAddonIndex)
Extended Name assigned to device (trapsExtName)
Viewing the Traps
Page 196
8.6 Binding Table

This section provides details on the bindings included in the traps generated for the devices.
Trap Entry: Trap Name
Description
General Example of Use
1: trapSequenceID
Trap sequence ID varbind.

Sequence number of the trap in the
last traps table. Enables tracking
missing traps.
2: trapTimeStamp
Time and Date when the current

event occurred. Format H:M:S
D/M/Y
3: trapsGenericType
The generic type of trap instance
4: trapsSpecificType
The specific type of trap instance

Additional data sent with the trap.
Type of module that generated the
trap:
5: trapDeviceType
Binding Table
ControllerComm
ControllerBasic
BTSC
Base Unit
RHU
LegacyRHU
AddOn
EHU
32
AU
33
HX
34
VCU
35
VAP
36
OCH
37
ORU
38
GX
39
CMU
40
PAU6
41
Page 197
Description
HXn

=
42
6: trapDeviceSerial

Serial number of the device that
generated the trap.
7: trapDeviceIndex
Index of the base controller that

generated the trap (1 9). Where
1 is the Master, 2 is the slave
connected to Master port-1, etc.
Only describe Controller number

index,
Master controller is always 1
Slave #1 is 2
Slave #2 is 3
Slave #3 is 4 and so on
Index of controller BU port through

which the trap was routed (0-7).
Index for Controller's port to which a

parent device is connected directly 0 means port no 1
1 means port no 2
2 means port no 3 and so on
Connector index of the base

controller that connects to the
generating device, through which
the Trap was routed: BU 0-1, RIU
0-2, Aux 1-8
Index for sub-module connected to a

DevicePort:
BU / OCH consist 1 or 2 optical
modules - this is where it is stated
which module generated the trap or
the trap was routed via it
BU can get 0 for first OPTM or 1 for
second OPTM
OCH can get 0 for first OPTM or 1 for
second OPTM
RIU can get 0 / 1 / 2 / 3 according to
location of BTSC module in the RIU
chassis
In addition this index is also used for
Aux alarm index - in that case it
represent the index # of the Aux
alarm and can get values between 18
10: trapDeviceInternalIndex
Internal index within the generating

device (i.e RHU 1 4 connected to
the BU through which the trap was
routed (0-3))
Trap Device Internal Index stands to

represent the RU device that
generated a trap.
This Remote Unit (RU) will be
connected via parent-device (BU /
OCH) which consist of four ports.
Values can vary from 0-3 according to
optical port connected in the OPTM
module
11: trapEventText
Free text field.
8: trapDevicePortIndex
9: trapDeviceConnIndex
Binding Table
Page 198
Description
12: trapCtrlSerialNum
Serial number of the controller

generating the event; Internal
parameter.
13: trapCtrlLastSeqID
The last event sequence ID of the

controller generating the trap.
Internal parameter.
14: trapCtrlName
Free text field: The name of the

controller
The alarm severity: (1) Notify
15: trapSeverity
(2) Minor
(3) Major
16: trapDeviceAddonIndex

This is the internal index within the
generating device (i.e. RHU #
within base unit).
17: trapsExtName
Device Extended Name free text
Binding Table
Page 199
In case the setup consist of DualAddon configuration, this index will

state the Addon index for the device:
Addon #1 is 0
Addon #2 is 1
The following figure shows an example of the bindings displayed for a btscdisconnected trap.
Example of Trap Binding Entries
Figure 8-4
NOTE: An example of the routes of the traps generated for a specific configuration is given in section 8.7.
Binding Table
Page 200
8.7 Example of Trap Binding for a Specific Setup

This section provides two examples for trap's route from the generating device all the way to the NOC: Green
dotted line and Red dotted line. The Red dotted line example is described following the image.
Example of Trap Binding for a Specific Setup
Page 201
Table 8-1 provides a description of the trap bindings provided for the AddOn example shown in previous
figure.
NOTE: Not all bindings are applicable to all trap events.
Traps Binding
Red Dotted Line in Example
1: trapSequenceID
Sequence number of the trap in the last traps table (e.g. 1242)
2: trapTimeStamp
Time and date event occurred is displayed in string format
3: trapsGenericType
N/A
4: trapsSpecificType
N/A
5: trapDeviceType
7 (AddOn)
6: trapDeviceSerial
Serial number of the AddOn that generated the trap (e.g. 5A47574)
7: trapDeviceIndex
Slave SC-450 is connected to port 7 in the SC-450 master, therefore the

value here will be (8)
8: trapDevicePortIndex
BU is connected to port #7 in the slave, therefore, the value here will be (6)
9: trapDeviceConnIndex
Device that generated the trap is routed via the second OPTM of the BU,
therefore the value here will be (1)
10: trapDeviceInternalIndex
In the second OPTM, the remote unit is connected to the 6th optical port
(seconds optical port of the second optical module) therefore, the value
here will be (1)
11: trapEventText
Free text. An example for an Add-On Disconnected trap: AddOn detach
12: trapCtrlSerialNum
Serial number of the Slave Controller generating the event for the AddOn
will be displayed (e.g. 0C11421)
13: trapCtrlLastSeqID
The last event sequence ID of the controller generating the trap is

displayed (e.g.25152)
14: trapCtrlName
Controller name displayed in free text (e.g. Slave 1)
15: trapSeverity
Alarm severity (e.g. major(3))
16: trapDeviceAddonIndex
Trap is generated by the second AddOn in the RHU-AddOns configuration,

therefore the value here will be (1)
17: trapExtName
(Free text) Extended Name entered for AddOn is displayed
Table 8-1. Description of Trap Binding Example
Example of Trap Binding for a Specific Setup
Page 202
8.8 Monitoring the Managed System

The MIB browser utility enables you to view and modify managed system parameters. The ma_devices.mib
file contains all the parameters for the managed system in one parameters group (maSite MIB entry) and the
following device tables:
baseControllersTable
btscTable
optmTable
rhuTable
addOnTable
rimTable
eocTable
auTable
hxTable
ochTable
maVEVCUTable
maVEVAPTable
oruTable
cmuTable
gxTable
pau6Table
hxnTable
To Monitor the Managed System

Using the MIB browser, select the desired MIB entry (one of the tables or specific object ID inside the maSite
parameters group) and choose table view (in case of a table) or a simple GET command (in case of a maSite
parameter).
NOTE: Set the SNMP manager GET community to the correct community string (default GET community
string is "public").
In order to modify a parameter just select the desired object ID, set a desired value and commit (apply the
command).
NOTE: Set the SNMP manager SET community to the correct community string (default SET community string
is "private").
Monitoring the Managed System
Page 203
8.9 List of Traps

NOTES:
1. MA Optional device traps are described in section 8.10.
2. SNMP Traps mark with (*) shall be reported by the SC-450 Master controller only after they have been
validated as sustainable for more than 30 minutes while no user is logged into the SC-450 WEB GUI.
Trap Name
Description
End OID
controllerFirstRun
Controller first run indication
controllerPowerUp
Controller power up indication
controllerModemSessionStarted
Controller modem session started
controllerModemSessionEnded
Controller modem session ended
controllerSlaveLost
Communication with slave controller

is lost
controllerSlaveRecovered
Communication with slave controller

is restored
legacyRhuDown
Legacy RHU down event
10
legacyRhuUp
Legacy RHU up event
11
auxiliaryInputNormal
Auxiliary input normal event
16
auxiliaryInputAlarm
Auxiliary input fail event
17
btscDetected
BTSC detected.
30
btscDisconnected
BTSC disconnected
31
btscRfLow
BTSC RF low indication
33
btscRfNormal
BTSC RF normal indication
34
btscRfOverload
BTSC RF overload indication
36
btscRfNoOverload
BTSC no RF overload indication
37
btscRfSwOff
BTSC - RF switch off state
38
btscRfSwOn
BTSC - RF switch on state
39
btscWetAdjust
BTSC wet adjustment succeeded
40
btscDryAdjust
BTSC dry adjustment succeeded
41
btscAdjustFailed
BTSC adjustment failed
42
btscRestoreFacDef
BTSC restored to factory defaults
43
btscOverTemperatureSet
BTSC over temperature set
44
btscOverTemperatureClear
BTSC over temperature clear
45
btscUlOverPowerSet
BTSC UL over power protection set
46
btscUlOverPowerClear
BTSC UL over power protection clear
47
List of Traps
Page 204
Trap Name
Description
End OID
btscOverTemperatureSet
BTSC over temperature set
44
optmDetected
OPTM detected
50
optmDisconnected
OPTM disconnected
51
optmRfLow
OPTM RF low indication
53
optmRfNormal
OPTM RF normal indication
54
optmRfHigh
OPTM RF high indication.
55
optmLowOpticalLevel
OPTM low optical level.
57
optmNormalOpticalLevel
OPTM normal optical level.
58
optmWetAdjust
OPTM wet adjustment succeeded.
60
optmDryAdjust
OPTM dry adjustment succeeded.
61
optmAdjustFailed
OPTM adjustment failed.
62
optmRestoreFacDef
OPTM restored to factory defaults.
63
optmUlLock
OPTM uplink locked.
64
optmUlUnlock
OPTM uplink unlocked.
65
optmDllock
OPTM downlink locked.
66
optmDlUnlock
OPTM downlink unlocked.
67
rhuDetected
RHU detected.
70
rhuDisconnected
RHU disconnected.
71 (*)
rhuAntennaChanged
RHU antenna changed.
73
rhuOverTemp
RHU over temperature indication.
74
rhuTempNormal
RHU normal temperature indication.
75
rhuFirstBandAdjust
RHU first band adjustment

succeeded.
76
rhuFirstBandAdjustFailed
RHU first band adjustment failed.
77
rhuSecondBandAdjust
RHU second band adjustment

succeeded.
78
rhuSecondBandAdjustFailed
RHU second band adjustment failed.
79
rhuLowOpticalLevel
RHU low optical level.
80
rhuNormalOpticalLevel
RHU normal optical level.
81
rhuFirstBandOff
RHU first band turned off.
82
rhuFirstBandOn
RHU first band turned on.
83
rhuSecondBandOff
RHU second band turned off.
84
rhuSecondBandOn
RHU second band turned on.
85
List of Traps
Page 205
Trap Name
Description
End OID
rhuNoOpticalLevelOnUL
RHU no optical level on uplink.
90
rhuLowOpticalLevelOnUL
RHU low optical level on uplink.
91
rhuNormalOpticalLevelOnUL
RHU normal optical level on uplink.
92
rhuNoOpticalLevelOnDL
RHU no optical level on downlink.
93
rhuLowOpticalLevelOnDL
RHU low optical level on downlink.
94
rhuNormalOpticalLevelOnDL
RHU normal optical level on

downlink.
95
qxFan1StatusNormal
QX Fan 1 status normal.
96
qxFan1StatusFail
QX Fan 1 status fail.
97
qxFan2StatusNormal
QX Fan 2 status normal.
98
qxFan2StatusFail
QX Fan 2 status fail.
99
addonDetected
Add-On detected.
100
addonDisconnected
Add-On disconnected.
101 (*)
addonOverTemp
Add-On over temperature indication.
102
addonTempNormal
Add-On normal temperature

indication
103
addonAdjust
Add-On adjustment succeeded.
104
addonAdjustFailed
Add-On adjustment failed.
105
addonBandOff
Add-On band turned off.
106
addonBandOn
Add-On band turned on.
107
rim1400Detected
Rim-1400 detected.
110
rim1400Disconnected
Rim-1400 disconnected.
111
rim1400SynthUnlock
Rim-1400 synthesizer is unlocked.
112
rim1400SynthLock
Rim-1400 synthesizer is locked.
113
rim1400intRefFailure
Rim-1400 internal reference failure.
114
rim1400intRefOk
Rim-1400 internal reference is OK.
115
rim1400extRefMissing
Rim-1400 external reference is

missing.
116
rim1400extRefExist
Rim-1400 external reference is

detected.
117
rim1400maintRequired
Rim-1400 maintenance is required.
118
rim1400maintDone
Rim-1400 maintenance is done.
119
rim1400adjFail
Rim-1400 adjustment has failed.
122
rim1400adjSuccess
Rim-1400 adjustment has
123
List of Traps
Page 206
Trap Name
Description
End OID
succeeded.
rim1400multiMasters
Rim-1400 multiple masters.
130
rim1400configOK
Rim-1400 configuration is OK.
131
rim1400driftDetected
Rim-1400 drift is detected.
132
rim1400refAligned
Rim-1400 reference is aligned.
133
EVENT_CUSTOM_MIB_RF_POWER_RHU
RHU/AddOn DL Pout is 15dB below

the tgt-Pout, or BU/RHU/AddOn
disconnected
160
EVENT_CUSTOM_MIB_VSWR_ANT
Antenna connect/disconnect
161
EVENT_CUSTOM_MIB_RSSI_RIU
RIU DL input power is 15dB below

the tgt-adj-input-power, or RIU
disconnected
162
EVENT_CUSTOM_MIB_OVER_OR_UNDER_CURR
ENT
Any unit disconnect
163 (*)
EVENT_CUSTOM_MIB_OVER_TEMPERATURE
Any unit disconnect
164 (*)
tunnlingAgentStarted
Tunneling agent start
200
tunnlingAgentEnded
Tunneling agent end
201
ctrlDialUpStarted
Controller dialup session started
202
ctrlDialUpEnded
Controller dialup session ended
203
ehuConnected
EHU detected.
301
ehuDisconnected
EHU disconnected.
302
ehuEthernetPortADisconnected
EHU Ethernet Port A Disconnected
303
ehuEthernetPortAConnected
EHU Ethernet Port A Connected
304
ehuEthernetPortBDisconnected
EHU Ethernet Port B Disconnected
305
ehuEthernetPortBConnected
EHU Ethernet Port B Connected
306
ehuEthernetPortCDisconnected
EHU Ethernet Port C Disconnected
307
ehuEthernetPortCConnected
EHU Ethernet Port C Connected
308
ehuEthernetPortDDisconnected
EHU Ethernet Port D Disconnected
309
ehuEthernetPortDConnected
EHU Ethernet Port D Connected
310
ehuPowerSupplySlot1Faulty
EHU Power Supply Slot 1 Faulty
311
ehuPowerSupplySlot1Normal
EHU Power Supply Slot 1 Normal
312
313
314
315
List of Traps
Page 207
Trap Name
Description
End OID
316
ehuTemperatureHigh
EHU Temperature High
317
ehuTemperatureNormal
EHU Temperature Normal
318
auConnected
AU detected.
401
auDisconnected
AU disconnected.
402
auEthernetPortADisconnected
AU Ethernet Port A Disconnected
403
auEthernetPortAConnected
AU Ethernet Port A Connected
404
auEthernetPortBDisconnected
AU Ethernet Port B Disconnected
405
auEthernetPortBConnected
AU Ethernet Port B Connected
406
auEthernetPortCDisconnected
AU Ethernet Port C Disconnected
407
auEthernetPortCConnected
AU Ethernet Port C Connected
408
auEthernetPortDDisconnected
AU Ethernet Port D Disconnected
409
auEthernetPortDConnected
AU Ethernet Port D Connected
410
auTemperatureHigh
EHU Temperature High
411
auTemperatureNormal
EHU Temperature Normal
412
hxConnected
HX detected
501
hxDisconnected
HX disconnected.
502 (*)
hxFansAlarm
hx Fans Alarm
503
hxFansAlarmNormal
hx Fans Alarm Clear
504
hxOpticalLinkLevelAlarm
hx Optical Link Level Alarm
505
hxOpticalLinkLevelAlarmNormal
hx Optical Link Level Alarm Clear
506
hxGeneralAlarm
hx General Alarm
507
hxGeneralAlarmNormal
hx General Alarm Clear
508
hxServiceShutdownAlarmService1
hx Service 1 Shutdown Alarm
510
hxServiceShutdownAlarmService1Normal
hx Service 1 Shutdown Alarm Clear
511
hxAdjustmentFailAlarmService1
hx Adjustment Fail Alarm On Service

1
512
hxAdjustmentFailAlarmService1Normal

1 Clear
513
hxVSWRAlarmService1
hx VSWR Alarm Service 1
514
hxVSWRAlarmService1Normal
hx VSWR Alarm Service 1 Clear
515
hxDLOutputPowerHighAlarmService1
hx DL Output Power High Alarm On

Service 1
516
List of Traps
Page 208
Trap Name
Description
End OID
hxDLOutputPowerHighAlarmService1Normal

Service 1 Clear
517
hxDLOutputPowerLowAlarmService1
hx DL Output Power Low Alarm On

Service 1
518
hxDLOutputPowerLowAlarmService1Normal

Service 1 Clear
519
hxOverTemperatureAlarmService1
hx Over Temperature Alarm Service
520
hxOverTemperatureAlarmService1Normal

1 Clear
521
522
523

2
524

2 Clear
525
hxVSWRAlarmService2
526
527

Service 2
528

Service 2 Clear
529

Service 2
530

Service 2 Clear
531
532

2 Clear
533
534
535

3
536

3 Clear
537
hxVSWRAlarmService3
538
539
540
List of Traps
Page 209
Trap Name
Description
End OID
Service 3

Service 3 Clear
541

Service 3
542

Service 3 Clear
543
544

3 Clear
545
546
547

4
548

4 Clear
549
hxVSWRAlarmService4
550
551

Service 4
552

Service 4 Clear.
553

Service 4.
554

Service 4 Clear.
555
hx Over Temperature Alarm Service .
556

4 Clear.
557
ochDetected
OCH detected.
601
ochDisconnected
OCH disconnected.
602
ochIFCommunicationError
OCH IF Card Communication Error.
603
ochIFCommunicationOK
OCH IF Card Communication Error

Clear.
604
ochDLPowerLow
OCH DL Power Low Alarm.
605
ochDLPowerLowClear
OCH DL Power Low Alarm Clear.
606
ochDLPowerHigh
OCH DL Power High Alarm.
607
List of Traps
Page 210
Trap Name
Description
End OID
ochDLPowerHighClear
OCH DL Power High Alarm Clear.
608
ochOpticalAdjastChannel1Fail
OCH Optical Adjust Channel 1 Fail

Alarm.
609
ochOpticalAdjastChannel1Ok

Alarm Clear.
610

Alarm.
611

Alarm Clear.
612

Alarm.
613

Alarm Clear.
614

Alarm.
615

Alarm Clear.
616
ochOpticalLink1Fail
OCH Optical Link 1 Alarm.
617
ochOpticalLink1Ok
OCH Optical Link 1 Alarm Clear.
618
ochOpticalLink2Fail
619
ochOpticalLink2Ok
620
ochOpticalLink3Fail
621
ochOpticalLink3Ok
622
ochOpticalLink4Fail
623
ochOpticalLink4Ok
624
ochRemote1TypeMismatchFail
OCH Remote 1 Type Mismatch

Alarm.
625
ochRemote1TypeOk

Alarm Clear.
626

Alarm.
627
ochRemote2TypeOk

Alarm Clear.
628

Alarm.
629
ochRemote3TypeOk

Alarm Clear.
630
List of Traps
Page 211
Trap Name
Description
End OID

Alarm.
631
ochRemote4TypeOk

Alarm Clear.
632
oruDetected
ORU detected.
701
oRUDisconnected
ORU disconnected.
702 (*)
oruGeneralAlarm
ORU General Alarm.
703
oruGeneralAlarmClear
ORU General Alarm Clear.
704
oruEthernetCardAlarm
ORU Ethernet Card Alarm.
705
oruEthernetCardAlarmClear
ORU Ethernet Card Alarm Clear.
706
oruOpticalLinkAlarm
ORU Optical Link Alarm.
707
oruOpticalLinkAlarmClear
ORU Optical Link Alarm Clear.
708
oruFansAlarm
ORU Fans Alarm.
709
oruFansAlarmClear
ORU Fans Alarm Clear.
710
oruService1ShutdownAlarm
ORU Service1 Shutdown Alarm.
711
oruService1ShutdownAlarmClear
ORU Service1 Shutdown Alarm

Clear.
712
oruService1DLOutputPowerHighAlarm
ORU Service1 DL Output Power

High Alarm.
713
oruService1DLOutputPowerHighAlarmClear

High Alarm Clear.
714
oruService1DLOutputPowerLowAlarm
ORU Service1 DL Output Power Low

Alarm.
715
oruService1DLOutputPowerLowAlarmClear

Alarm Clear.
716
oruService1AddOnCommunicationFailAlarm
ORU Service1 Add-On

Communication Fail Alarm.
717
oruService1AddOnCommunicationFailAlarmClear
ORU Service1 Add-On

Communication Fail Alarm Clear.
718
oruService1AddOnTypeMismatchAlarm
ORU Service1 Type Mismatch Alarm.
719
oruService1AddOnTypeMismatchAlarmClear
ORU Service1 Type Mismatch Alarm

Clear.
720
721

Clear.
722
723
List of Traps
Page 212
Trap Name
Description
End OID
High Alarm.

High Alarm Clear.
724

Alarm.
725

Alarm Clear.
726
ORU Service2 Add-On

727
ORU Service2 Add-On

728
729

Clear.
730
731

Clear.
732

High Alarm.
733

High Alarm Clear.
734

Alarm.
735

Alarm Clear.
736
ORU Service3 Add-On

737
ORU Service3 Add-On

738
739

Clear.
740
741

Clear.
742

High Alarm.
743
744
List of Traps
Page 213
Trap Name
Description
End OID
High Alarm Clear.


Alarm.
745

Alarm Clear.
746
ORU Service4 Add-On

747
ORU Service4 Add-On

748
749

Clear.
750
oruService5BBShutdownAlarm
ORU Service5BB Shutdown Alarm.
751
oruService5BBShutdownAlarmClear
ORU Service5BB Shutdown Alarm

Clear.
752
oruService5BBDLOutputPowerHighAlarm
ORU Service5BB DL Output Power

High Alarm.
753
oruService5BBDLOutputPowerHighAlarmClear

High Alarm Clear.
754
oruService5BBDLOutputPowerLowAlarm

Low Alarm.
755
oruService5BBDLOutputPowerLowAlarmClear

Low Alarm Clear.
756
oruService5BBAddOnCommunicationFailAlarm
ORU Service5BB Add-On

757
oruService5BBAddOnCommunicationFailAlarmClear
ORU Service5BB Add-On

758
oruService5BBAddOnTypeMismatchAlarm
ORU Service5BB Type Mismatch

Alarm.
759
oruService5BBAddOnTypeMismatchAlarmClear
ORU Service5BB Type Mismatch

Alarm Clear.
760
vcuChannel1DLPowerLow
when input RF power is 15 dB lower

than max expected power (or no
signal)
801
vcuChannel1DLPowerHigh
when input RF power is above the

defined max expected power
802
vcuChannel2DLPowerLow
when input RF power is 15 dB lower

than max expected power (or no
signal)
803
List of Traps
Page 214
Trap Name
Description
End OID
vcuChannel2DLPowerHigh
when input RF power is above the

defined max expected power
804
vcuChannel1ServiceOff
when service is off
805
vcuChannel2ServiceOff
when service is off
806
vcuFaulty
when VCU HW is faulty
807
vcuOverTemperature
when VCU temperature is above

threshold
808
vcuMismatchType
When VCU services types is different

than VAP services types
809
vcuAdjustment
when VCU adjustment has failed (or

cable too long)
810
vapAdjustment
when VAP adjustment has failed (or

cable too long)
811
vapChannel1ServiceOff
when VAP service is off
812
vapChannel2ServiceOff
when VAP service is off
813
vapFaulty
when VAP HW is faulty
814
vapOverTemperature
when VAP temperature is above

threshold
815
vcuHeartbeat
system keep alive notification
816
vcuConnected
VCU connected
817
VCU disconnected
VCU disconnected
818
vapConnected
VAP connected
819
vapDisconnected
VAP disconnected
820
vcusInBaseline
At least one VCU-Slave is missing in

the VCU Baseline
821
vapsInBaseline
At least one VAP is missing in the

VCU Baseline
822
vcuChannel1DLPowerLowClear
when the input RF power low alarm

on channel 1 is cleared
851
vcuChannel1DLPowerHighClear
when the input RF power high alarm

852
vcuChannel2DLPowerLowClear
when the input RF power low alarm

853
vcuChannel2DLPowerHighClear
when the input RF power high alarm

854
vcuChannel1ServiceOn
when service is on
855
List of Traps
Page 215
Trap Name
Description
End OID
vcuChannel2ServiceOn
when service is on
856
vcuFaultyClear
when VCU HW faulty alarm is

cleared
857
vcuOverTemperatureClear
when VCU over-temperature alarm is

cleared
858
vcuMismatchTypeClear
When VCU/VAP services types

mismatch alarm is cleared
859
vcuAdjustmentClear
when VCU adjustment alarm is

cleared
860
vapAdjustmentClear
when VAP adjustment alarm is

cleared
861
vapChannel1ServiceOn
when VAP service on channel 1 is on
862
vapChannel2ServiceOn
when VAP service on channel 2 is on
863
vapFaultyClear
when VAP HW faulty alarm is cleared
864
vapOverTemperatureClear
when VAP over-temperature alarm is

cleared
865
vcusInBaselineClear
When VCU-Slave missing

(comparing to Baseline) alarm is
cleared
871
vapsInBaselineClear
When VAP missing (comparing to

Baseline) alarm is cleared
872
gxConnected
GX detected.
901
gxDisconnected
GX disconnected.
902
gxFansSet
GX Fans Alarm.
903
gxFansClear
GX Fans Alarm Clear.
904
gxOpticalLinkSet
GX Optical Alarm.
905
gxOpticalLinkClear
GX Optical Alarm Clear.
906
gxOverTemperatureSet
GX over temperature indication.
907
gxOverTemperatureClear
GX over temperature indication clear.
908
gxDoorOpenSet
GX door open indication.
909
gxDoorOpenClear
GX door open indication clear.
910
gxDLService1Set
GX Service1 PA Alarm.
913
gxDLService1Clear
GX Service1 PA Alarm Clear.
914
gxDLOutputPowerLow1Set
GX Service1 DL Low Alarm.
915
gxDLOutputPowerLow1Clear
GX Service1 DL Low Alarm Clear.
916
List of Traps
Page 216
Trap Name
Description
End OID
gxDLOutputPowerHigh1Set
GX Service1 DL High Alarm.
917
gxDLOutputPowerHigh1Clear
GX Service1 DL High Alarm Clear.
918
gxULProtection1Set
GX Service1 UL ALC Alarm.
919
gxULProtection1Clear
GX Service1 UL ALC Alarm Clear.
920
gxVSWR1Set
GX Service1 Antenna Sense Alarm.
921
gxVSWR1Clear
GX Service1 Antenna Sense Alarm

Clear.
922
gxServiceProtection1Set
GX Service1 Shutdown Alarm.
923
gxServiceProtection1Clear
GX Service1 Shutdown Alarm Clear.
924
gxAdjustment1Set
GX Service1 Adjustment Alarm.
925
gxAdjustment1Clear
GX Service1 Adjustment Alarm

Clear.
926
gxULService1Set
GX Service1 UL LNA Alarm.
927
gxULService1Clear
GX Service1 UL Lna Alarm Clear.
928
gxDLService2Set
929
gxDLService2Clear
930
931
932
933
934
gxULProtection2Set
935
936
gxVSWR2Set
937
gxVSWR2Clear

Clear.
938
939
940
gxAdjustment2Set
941
gxAdjustment2Clear

Clear.
942
gxULService2Set
943
gxULService2Clear
944
gxDLService3Set
945
gxDLService3Clear
946
List of Traps
Page 217
Trap Name
Description
End OID
947
948
949
950
gxULProtection3Set
951
952
gxVSWR3Set
953
gxVSWR3Clear

Clear.
954
955
956
gxAdjustment3Set
957
gxAdjustment3Clear

Clear.
958
gxULService3Set
959
gxULService3Clear
960
gxDLService4Set
961
gxDLService4Clear
962
963
964
965
966
gxULProtection4Set
967
968
gxVSWR4Set
969
gxVSWR4Clear

Clear.
970
971
972
gxAdjustment4Set
973
gxAdjustment4Clear

Clear.
974
gxULService4Set
975
gxULService4Clear
976
List of Traps
Page 218
Trap Name
Description
End OID
gxExternalAlarm1set
GX External Alarm 1 Set
977
gxExternalAlarm1clear
GX External Alarm 1 Clear
978
gxExternalAlarm2set
979
980
gxExternalAlarm3set
981
982
gxExternalAlarm4set
983
984
cmuConnected
CMU detected
986
cmuDisconnected
CMU disconnected
987
cmuFan1Alarm
CMU Fan1 Alarm
988
cmuFan1AlarmNormal
CMU Fan1 Alarm Clear
989
cmuFan2Alarm
CMU Fan2 Alarm
990
cmuFan2AlarmNormal
991
cmuFan3Alarm
CMU Fan3 Alarm
992
cmuFan3AlarmNormal
993
cmuFan4Alarm
CMU Fan4 Alarm
994
cmuFan4AlarmNormal
995
cmuGeneralAlarm
CMU General Alarm
996
cmuGeneralAlarmClear
CMU General Alarm Clear
997
cmuOverTemperatureAlarm
CMU over temperature indication
998
cmuOverTemperatureAlarmClear
CMU over temperature indication

clear
999
pau6Connected
PAU-6 is detected
1003
pau6Disconnected
PAU-6 is disconnected
1004
pau6Fan1Alarm
PAU6 Fan1 Alarm
1005
pau6Fan1AlarmNormal
PAU-6 Fan1 Alarm Clear
1006
pau6Fan2Alarm
PAU-6 Fan2 Alarm
1007
pau6Fan2AlarmNormal
1008
pau6Fan3Alarm
PAU-6 Fan3 Alarm
1009
pau6Fan3AlarmNormal
1010
pau6Fan4Alarm
PAU-6 Fan4 Alarm
1011
pau6Fan4AlarmNormal
1012
List of Traps
Page 219
Trap Name
Description
End OID
pau6PowerAlarm
PAU-6 General Alarm
1013
pau6PowerAlarmClear
PAU-6 General Alarm Clear
1014
pau6OverTemperatureAlarm
PAU-6 over temperature indication
1015
pau6OverTemperatureAlarmClear
PAU-6 over temperature indication

clear
1016
hxnConnected
HXn detected
1021
hxnDisconnected
HXn disconnected
1022
hxnLowOpticalLinkSet
HXn Optical Alarm
1023
hxnLowOpticalLinkClear
HXn Optical Alarm Clear
1024
hxnTemperatureHighSet
HXn over temperature indication
1025
hxnTemperatureHighClear

clear
1026
hxnTemperatureProtectionSet
1027
hxnTemperatureProtectionClear
HXn over temperature indication clea
1028
hxnFansMinorFaultSet
HXn Fans Alarm
1029
hxnFansMinorFaultClear
HXn Fans Alarm Clear
1030
hxnFansMajorFaultSet
HXn Fans Alarm
1031
hxnFansMajorFaultClear
HXn Fans Alarm Clear
1032
hxnServiceOffSet
HXn Service1 PA Alarm
1033
hxnServiceOffClear
HXn Service1 PA Alarm Clear
1034
hxnOutputPowerHighSet
HXn Service1 DL High Alarm
1035
hxnOutputPowerHighClear
HXn Service1 DL High Alarm Clear
1036
hxnOutputPowerLowSet
HXn Service1 DL Low Alarm
1037
hxnOutputPowerLowClear
HXn Service1 DL Low Alarm Clear
1038
hxnVSWRAlarmSet
HXn Service1 Antenna Sense Alarm
1039
hxnVSWRAlarmClear
HXn Service1 Antenna Sense Alarm

Clear
1040
hxnAdjustmentFailSet
HXn Service1 Adjustment Alarm
1041
hxnAdjustmentFailClear
HXn Service1 Adjustment Alarm

Clear
1042
hxnProtectionActivatedSet
HXn Service1 Shutdown Alar
1043
hxnProtectionActivatedClear
HXn Service1 Shutdown Alarm Clear
1044
List of Traps
Page 220
8.10 List of MA Optional Device Traps

Trap Name
Severity
Description
RF Power
Major
Occurs when the relevant RHU/Add-on RF power drops by more

than 3 dB from its original setting of target Pout.
VSWR
Major
Monitors antenna connectivity taking into account antenna

mask. Alarm generated when antenna connection is not detected
and cleared when antenna is detected.
RSSI
Major
Reported when the Repeater input power is 15dB or more, below

the RIU target adjustment input power.
Over/Under Current
Major
Generated upon connection and disconnection of every MA

Repeater system device.
Over Temperature
Major
Generated upon connection and disconnection of every MA

Repeater system device.
List of MA Optional Device Traps
Page 221
A ppendix A : MA 1000/MA 2000 Ma nua l

Dev ic e C onfigura tion
IMPORTANT: The available tabs and options in the SC-450 Web GUI may vary depending on the access
level used to open your session.
9.1 Initial Configuration (Commissioning) Steps

Once the System Controller is set up and MobileAccess devices are physically installed and the connections
are verified, the system must be initially configured. There are two phases to this procedure as follows:
Phase 1 Account for the Fiber Loss
These steps are performed to account for the fiber loss through the system. It preps the headend and remoteend devices of the MA1000 and MA2000 solutions for Phase 2 Commissioning.
Phase 2 Prepare System for RF Source
These steps are performed to prepare the system to receive signal from the RF Signal source.
9.1.1
Phase 1 Commissioning Account for Fiber Loss
1. Log In to the SC-450. Refer to 2.7.1 for details.

2. Check the Network Topology for MobileAccess device visibility. Refer to sections 5.1 for details.
NOTE THE FOLLOWING:
If commissioning and configuring the MobileAccessVE, skip the rest of this section and refer to the
MobileAccessVE User Manual.
If commissioning and configuring the EC560 Solution components, skip the rest of this section and refer to
the EC560 Solution User Manual.
If commissioning and configuring the Headend, MA1000 and MA2000 devices, confirm that the RHU and AO,
where applicable are visible on the Network Topology and continue to the next step.
3. Set the BU to expect and RIU (see section 9.2.2).
a) Click on the BU in the Network Topology Tree Select RF Parameters Tab from the Work Area
Interface Type to MA RIU
b) Optional: Give the BU an identifiable name by Modifying the Name parameter in the Module Info tab
4. Check the DL Optical Link Level on the RHU is acceptable
a) Click on the RHU in the Network Topology Tree Select RF Parameters Tab from the Work Area
Verify Link Level under the Optical Link section is > 100
b) If the level is not >100, clean the fiber at the RHU.
c) Optional: Give the RHU an identifiable name by Modifying the Name parameter in the Module Info tab
d) Refer to section 9.2.4 for details on the RHU configuration dialogs.
5. Using a Fiber Optic Tester, check the UL Optical Link Level of the fiber connected to the BU is >0
a) Set the Fiber Optic Tester to a wavelength of 1310nm
b) Unplug the UL fiber connection from the BU and test to make sure it is at a level >0
Initial Configuration (Commissioning) Steps
Page 222
c) If the level is not >0, clean the fiber and retest

6. Set up CW signal to be connected to the signal conditioner (BTSC/BDAC). The 700 MHz LTE conditioner
does not need an external CW signal (See section 7.5.2).
a) BTSC acceptable input power range = +10 to +36dBm
b) BDAC acceptable input power range = -16 to +10 dBm
c) Acceptable frequency range depends upon the RF service
7. Adjust the signal conditioner (BTSC/BDAC) with the CW signal. The 700 MHz LTE conditioner does not
need an external CW signal. (See section 7.5.2).
a) Connect the CW signal to the BTSC/BDAC DL Port or Duplex port located on the rear of the RIU
associated with the slot that the signal conditioner (BTSC/BDAC) is inserted into
b) Click on the conditioner in the Network Topology Tree Select RF Parameters Tab from the Work
Area Adjust Max Input Power by clicking on the Adjust button in the DL Power section Select Use
Current Input Power
c) After a few moments, verify that the Target Max Input Power and the Current Input Power are
equivalent
8. Perform adjustments for each RHU and AO that will receive the signal from the conditioner adjusted in
Step 7.
a) Click on the RHU in the Network Topology Tree Select RF Parameters Tab from the Work Area
Select the either First Band or Second Band tab as applicable Adjust Output Power to Target by
clicking the Adjust button (Default Target Output Power should be the maximum allowed by the
service. Refer to the datasheet for service specific details)
b) Verify Current Output Power matches Target Output Power
c) Optional: Give the RHU/AO an identifiable name by Modifying the Name parameter in the Module Info
tab
9. Repeat Steps 7 and 8 for each signal conditioner
10. Perform a Quality and Integrity Check of the installed system as per the RF Design and Statement of
Work. Contact a MobileAccess Project Manager for more instructions.
9.1.2
Phase 2 Commissioning Prepare System for RF Source
These steps should only be performed after completing Phase 1 of the commissioning process. Please
consult a MobileAccess certified installer on the details of these steps or access the MobileAccess Partner
Portal for more information.
1. Perform an Emulated Adjustment
2. Perform UL Noise Mitigation
Initial Configuration (Commissioning) Steps
Page 223
9.2 MobileAccess Headend, MA1000 and MA2000

By default, the controller activates an auto detection mechanism that constantly monitors its RS485 rear panel
ports for connected devices, such as BU, OCH, and RIU devices.
Remote Units (RUs), such as HX, QX and HX unitshosted by BUs/OCHs, are detected in a similar manner by
their host element every time the host element (i.e. BU or OCH) is powered-up or reset from the Web GUI
application and added to the Network Topology.
NOTE: Newly added hosted elements will be detected by the Base Unit only after the BU/OCH has been
reset. The reset can be software executed through the BU/OCH configuration dialog.
Verify that all the MobileAccess devices (e.g. RIUs, OPTMs, BUs, RUs, etc.) that are managed by the
controller are displayed in the Network Topology pane under their corresponding hosts, and are colored
green, red, or yellow. Any of these colors are acceptable before the adjustment procedure has been
performed.
Example of Headend Devices in Network Topology Tree
MobileAccess Headend, MA1000 and MA2000
Page 224
Figure 9-1
9.2.1
RIU and Signal Conditioner Configuration and Control
For RIU-4 Master/Slave Configurations Each RIU-4 unit is connected to the System Controller (SC-450) and
configured separately.
RIU-4 units will only be automatically identified as such if a conditioner resides in the 4th slot (conditioners
can be installed in any order). Therefore, if the RIU-4 is not identified as such in the topology, it must be
manually defined as an RIU-4 type unit. See section 9.2.1.1).
Each Signal Conditioner (BTSC or BDAC) unit in the RIU (RIU-4, RIU-IM and RIU-Lite) is individually
configured and controlled through a dedicated configuration dialog. By default the BTSC/BDAC modules are
configured to operate with AGC and are assigned a default name (i.e. BTSC-1, BTSC-2, etc.).
The main functions provided are:
Service control (off/on)

Setting gain control either automatically (AGC) or manually
Resetting the conditioner
Monitoring the downlink signal
9.2.1.1
Manually Defining RIU-4 Type
RIU-4 units, which are not fully configured (LESS than four BTSC/BDAC modules are installed in the unit) will
automatically be identified as RIU-4 units in the SC-450 GUI screens but only if a conditioner resides on the
4th slot. Therefore, for these scenarios it is recommended to either:
Install (1) of the conditioners in the 4th slot to enable the SC-450 to identify the RIU-4 automatically (refer
to RIU Product Line User Manual), or
Manually define the RIU unit type as RIU-4

To manually define the RIU-4 type:
1. Right-click the RIU item in the topology tree. The RIU Quad Settings dialog appears.
RIU Quad Settings Dialog
Figure 9-2
2. Select RIU-Quad option and click OK. The RIU item will appear as RIU-Quad in the topology tree and the
RIU-4 unit icon will appear on the device area.
Page 225
9.2.1.2
Standard Conditioner (BTSC/BDAC) Settings
Note the following:
Mandatory DL input power level should be configured to adjust to the expected power level from the
BTS/BDA.
Optional - A name can be assigned to each BDAC/BTSC any time locally or remotely.
Optional AGC can be disabled.
Optional UL signal may be attenuated to reduce UL Noise
To configure and control the BTSC:
1. Double-click on the BTSC item in the Network Topology. The BTSC configuration dialog appears with the
Module Info tab displayed by default.
This tab provides general information such as software and hardware versions, type and serial number of
the BTSC module and allows assigning the module an identifiable name.
BTSC Module Info
Figure 9-3
2. (Optional) Assign the BTSC an identifiable name (i.e. operator name), by clicking the Modify button and
typing the name.
Page 226
3. Click on the RF Parameters tab, the following is displayed.

This tab shows information on the RF parameters, and provides service and RF signal control options.
BTSC RF Parameters Tab
Figure 9-4
4. (Mandatory) Adjust DL input power level - Click on the Adjust button and select the RF power level for
adjustment (dBm).
5. (Optional) To disable the service, set Service Control to OFF in the RF Parameters tab.
6. (Optional) To adjust UL signal to reduce UL noise Set the UL Attenuation Value in the RF Parameters
tab.
NOTE: The UL Atten. Value controls attenuation on the uplink. This value is set during manufacturing and
should NOT be modified unless unique conditions exist.
7. The DL power gain may be set automatically (AGC) or manually (DCA Digital Control Attenuation). To
control the DL gain control, set the DL AGC Control:
o AGC Status Sets DL AGC mode:
ON Enables automatic gain control to compensate for input power variations (This is the default setting).
OFF Disables automatic gain control. The Attenuation Value can be set manually. (DL DCA Manual
Override Value).
Page 227
9.2.1.3
BTSC LTE 700 MHz
To Configure and Control the MobileAccess BTSC LTE 700 MHz

1. Double-click on the LTE BTSC item in the Network Topology.
LTE BTSC In Topology Tree
Page 228
Figure 9-5
The LTE BTSC configuration dialog appears with the Module Info tab displayed by default.
BTSC LTE 700 Module Info Tab
Figure 9-6
The Module Info tab provides general information such as software and hardware versions, type and serial
number of the LTE BTSC.
2. Assign the BTSC LTE 700 MHz an identifiable name (i.e. operator name) and Extended Name (i.e.
physical location), by clicking the corresponding Modify button and typing the name.
NOTE: The Comments tab can be used to enter any additional information relevant to the module. Refer to
section 5.3 for additional information
3. Click on the RF Parameters tab, the following tab is displayed.

BTSC LTE700 RF Parameters Tab
Figure 9-7
4. To control the service supported by this BTSC choose an option in the Service Control field:
Page 229
o ON Enables Service
o OFF Disables Service
5. Under DL Power section of the tab, click Adjust and select the required value (+10 to +40 dBm) and click
OK.
6. The DL power gain may be set automatically (AGC) or manually (DCA Digital Control Attenuation). To
control the DL gain control, set the DL AGC Status:
o ON Enables automatic gain control to compensate for input power variations. When enabled, gain
control is performed automatically.
o OFF Disables automatic gain control and enables DCA to be set manually (DL DCA Manual
Override Value).
7. UL Atten. Value Controls attenuation on the uplink. This value is set during manufacturing and should be
modified only under special circumstances.
8. Sup. Parameters tab Relevant only for the initial adjustment procedure of the complete system (See LTE
addendum document: UMA_MA1000 MA2000_700MHz LTE AO). Otherwise disregard.
This option provides an internal signal generation source that can be used during the adjustment
procedure instead of connecting an external signal generator.
BTSC LTE700 Sup. Parameters Tab

o ON Internal signal source activated.
o OFF Internal signal source disabled.
9. See section 9.2.5.2 for LTE Add-On configuration.
Page 230
Figure 9-8
9.2.2
RIU-12 and Signal Conditioner Configuration
This section provides the information required to manually perform the commissioning procedure for the RIU12. The commissioning procedure is performed separately for the CMU (Control Module) and for the BTSC
modules (up to 12). Each Signal Conditioner (BTSC-12) unit is individually configured and controlled through
a dedicated configuration dialog. By default the BTSC modules are configured to operate with AGC and are
assigned a default name with an indication of the occupied RIU-12 slot (e.g. P1-BTSC_12, P3-BTSC_12,
etc.).
The main functions provided are:
CMU: RIU-12 chassis configuration (4+8; 1-12)

BTSC:
o
o
o
o
o
o
Service control (ON/OFF)

Setting gain control either automatically (AGC) or manually
Resetting the conditioner
Monitoring the downlink signal
Calibration Source (ON/OFF)
For BTSCs connected to PAU-6 unit (for higher power BTS signal sources):
PAU-6 Support (Enable/Disable)

PAU-6 Attenuation
For RIU-12 Master/Slave Configurations Each RIU-12 unit is connected to the System Controller (SC-450)
and configured separately.
Page 231
9.2.2.1
CMU Basic Configuration
The RIU-12 CMU basic setup configuration consists of assigning the chassis a name, selecting the chassis
service configuration and verifying normal system operation via alarms.
To configure the RIU-12 CMU
1. Double-click on the RIU-12 CMU item in the Network Topology (see Figure 9-9). The CMU Module Info tab
is displayed by default.
CMU Module Info Tab
Figure 9-9
2. Assign the CMU an identifiable name (e.g. operator name), by clicking the Modify button and typing the
name.
3. Select the chassis service configuration (the selected configuration is indicated in the device view):
o 1-12 (default): Configurations with up to 12 SISO services
o 4+8: Configurations with up to 4 MIMO services and 8 SISO services
4. Verify normal system operation via CMU Alarms tab (see section 7.5.3.1 for alarms description).
Page 232
5. Click on Chassis Config tab to view fan and temperature status info. See Figure 9-10.
CMU Chassis Config Tab
Figure 9-10
Page 233
9.2.2.2
BTSC-12 Configuration
To Configure the BTSC-12 module

NOTE: Each BTSC module must be configured individually
1. Double-click on the BTSC-12 item (under the RIU-12 CMU) in the Network Topology.
CMU Chassis Config Tab
Figure 9-11
The selected BTSC-12 module appears green in the device view and the Module Info tab is displayed by
default. See Figure 9-12.
Page 234
BTSC LTE 700 Module Info Tab
Figure 9-12
This tab provides general information such as software and hardware versions, type and serial number of
the BTSC.
2. Assign the BTSC an identifiable name (e.g. service name), by clicking the Modify button and typing the
name.
Page 235
3. Click on the RF Parameters tab, the following tab is displayed.

BTSC -12 RF Parameters Tab
Figure 9-13
4. To control the service supported by this BTSC choose an option in the Service Control field:
o ON Enables Service
o OFF Disables Service
5. To adjust the (DL) Max. Input Power, click the Adjust button and select the required value (0 to +40 dBm)
and click OK.
Page 236
6. The DL power gain can be set automatically via the AGC:

o ON Enables automatic gain control to compensate for input power variations. When enabled, gain
control is performed automatically.
o OFF Disables automatic gain control and enables DCA to be set manually (DL DCA Manual
Override Value).
AGC Status Drop-Down Box (RF Parameters Tab)
Figure 9-14
7. UL Atten. Value Controls attenuation on the uplink. This value is set during manufacturing and should be
modified only under special circumstances.
Page 237
8. Advanced tab relevant only for the initial adjustment procedure of the complete system and can only be
configured by an admin user:
o Calibration Source (ON/OFF) - provides an internal signal generation source that can be used during
the adjustment procedure (instead of connecting an external signal generator).
o PAU6 Support (Default=Disable) This option should be set to Enable when the BTSC module is
connected to a PAU6 unit (interfaces to higher power BTS signal sources). The drop-down box with
the Enable option will only be displayed after performing the following:
BTSC is configured to support Duplex RF connections (PAU-6 supports only RF Duplex ports)
this is configured by a technician via the Engineering GUI
Max Input Power is set to >14 dBm click the Adjust button in the RF Parameters tab and set
the value
o PAU6 Attenuation - set value 0 to 20 dB (in 0.5 dB steps)
o ALA Control (ON/OFF) Automatic Level Adjustment control that enables maintaining the composite
RF level within the range of the optical modules
o ALA Attenuation
BTSC -12 Advanced Tab
Figure 9-15
Page 238
9.2.3
Base Unit Configuration
The configuration dialog consists of two tabs: Module Info and RF parameters. The main provided functions
are:
In the Module Info tab - Viewing basic information on the unit and assigning the unit an identifiable name.
In the RF Parameters tab - Setting gain control, resetting the Base Unit (required when an RHU is added)
and monitoring the downlink signal.
To Configure and Control the Base Unit:
1. Double-click on the Base Unit item in the Network Topology. The Base Unit configuration dialog appears.
Base Unit Config Tab
Figure 9-16
2. In the Module Info tab click the Modify button and assign the BU an identifiable name that indicates the
technology to which it interfaces.
3. Click the RF Parameters tab.
Page 239
Base Unit RF Parameters Tab
Figure 9-17
Set the following parameters:

o Interface Type RF Source interface type (i.e. MA RIU, Other)
o AGC Status Sets DL AGC mode:
ON Automatic gain control to compensate for input power variations. When
enabled, gain control is performed automatically.
OFF - DCA can be set manually (DL DCA Manual Override Value).
o UL Atten. Value Controls attenuation on the uplink. This value is set during manufacturing and
should be modified only under special circumstances.
Page 240
9.2.4
RHU Configuration
Each RHU is individually configured and controlled through a dedicated configuration dialog. The main
functions provided are:
High Band and Low Band configuration

Controlling the services (on/off) and the DL output power to the antennas
Setting the Uplink gain control
Resetting the RHU
Monitoring the signal
To Configure and Control the RHU

1. Double-click on the RHU item in the Network Topology. The RHU Module Info tab is displayed.
RHU Config-Module Info Tab
Figure 9-18
2. Assign the RHU an identifiable name that indicates its supported services and location, by clicking the
Modify button, entering the name and clicking OK.
Page 241
3. Configure the RHU services:
RHU Config-First Band Tab
Figure 9-19
o First Band Select the service for the first band (low).
o Second Band Select the service for the second band (high).
4. To disable one of the bands or change its power output to the antennas:
o Click the RF Parameters tab.
o Under Amplifier Control, select one of the following options:
ON Enables the First Band or Second Band (this is the default setting).
OFF - Disables the First Band or Second Band.
Select value required to configure the DL Power reduction for optimizing the power output to the
antennas in response to changing site conditions.
Page 242
RHU Config-RF Parameters Tab
Figure 9-20
5. To control the UL AGC, set the UL AGC Mode (default = ON), in the RF Parameters tab for the First Band
and Second Band.
6. To reset the RHU, click the Restart button in the RF Parameters tab.
Page 243
9.2.5
Add-On Configuration
Each Add-On unit is individually configured and controlled through a dedicated configuration dialog. The main
functions provided are:
Naming the RHU Add-On

Band configuration
Setting the uplink gain control
Monitoring the signal
9.2.5.1
1200 Add-On Configuration
To Configure and Control the 1200 Add-On

1. Double-click on the 1200 Add-On item in the Network Topology. The 1200 Add-On configuration dialog
appears.
Add-On Config-Module Info Tab
Figure 9-21
Page 244
2. In the Module Info tab, click the Modify button and assign the add-on unit an identifiable name that
indicates its supported service and location.
NOTE: For the PCS G-Block Add-On, the Band field will display Custom Model by default. For web
management application version 3.18 SP2 and higher, the Band field can be set to PCS G-Block via the
adjacent browser button. For web management application lower than 3.18 SP2, this option is not
available. You may type a name (PCS G-block) in the Name field.
3. To disable the service or change its DL power:

o Click the RF Parameters tab.
Add-On Config-RF Parameters Tab
Figure 9-22
o Under Amplifier Control field, you may disable (OFF) the Band.
4. To set the Service Control and DL Power Reduction value to meet changing site conditions select the
relevant option in the Amplifier Control field:
o On Service On
o Off Service Off
o Value - Value of DL Power Reduction
Page 245
9.2.5.2
LTE 700 Add-On Configuration
To Configure and Control the LTE Add-On

1. Double-click on the LTE Add-On item in the Network Topology. The LTE Add-On configuration dialog
appears.
LTE700 Add-On Config-Module Info Tab
Figure 9-23
2. In the Module Info tab, click the Modify button and assign the Add-On unit an identifiable name that
indicates its supported service and location.
Page 246
3. Click the RF Parameters tab:

o To set the Service Control and DL Power Reduction value to meet changing site conditions select the
required value in the Amplifier Control field - On/Off
o Set value of DL Power Reduction
LTE AO RF Parameters Tab
Figure 9-24
4. Click the RF LTE tab.
RF LTE Tab
Figure 9-25
Page 247
RF Filter Selection - When the LTE 700 Add-On unit is used with the Public Safety 700-800 filter, select
the External filter option. Otherwise, select Internal.
RHU Type MobileAccess Tech Support Use Only. (Used for fine tuning UL gain).
UL Atten. Control - Controls attenuation on the uplink. This value is set during manufacturing and should
be modified only under special circumstances.
9.3 MobileAccessHX/ HXn Device Configuration

The HX(Indoor and Outdoor) and HXn remote units are centrally managed via the MobileAccess SC-450
Controller, however are NOT connected to it directly. Each remote unit is managed via the optical converter
unit (i.e. BU/OCH) which is directly connected to the controller.
Each emote unit is managed via several dedicated panes that are accessed by clicking the relevant network
element in the SC-450 Topology Tree.
9.3.1
HX Indoor/Outdoor Device Configuration
The provisioning procedure is similar for both Indoor and Outdoor HX units and consists of two simple steps:
assigning the unit name (Module Info tab) and clicking the Adjust button (Adjustment tab). Additional
configuration options are available as well.
To access the MobileAccessHX management options
In the Network Topology tree, expand the relevant Controller item, expand the relevant BU/OCH (to which the
HX is connected) and click on the HX. The HX alarms and configuration tabs appear (Figure 9-26).
HX Module Info Tab
Figure 9-26
MobileAccessHX/ HXn Device Configuration
Page 248
The HX Cabinet Alarms are continuously displayed (to the left of the tabs). The monitoring and configuration
options are distributed over five tabs:

RF Parameters service control options
RF Adjustment provides the adjustment options
Service Alarms used for masking redundant alarms
Comments used for entering any additional information relevant to the device (see section 5.3.2 for
details).
9.3.1.1
Basic Setup Procedure
To perform basic setup

1. Verify that the alarms in the HX Cabinet Alarms dialog and Service Alarms tab show green:
o HX Cabinet Alarms displays system level alarms
Example of HX Alarms
Figure 9-27
NOTE: Refer to section 7.5.13 for description of HX alarms.
Page 249
o Service Alarms tab displays specific alarms for each supported service.
HX Service Alarms Tab
Figure 9-28
NOTE: Refer to section 7.5.13 for description of HX alarms.

2. Mask irrelevant alarm conditions, in both tabs via the Modify button, to avoid having them reflected in the
overall status of the HX unit (displayed in the HX Alarms area). Refer to section 7.5.2.
3. Assign the unit a recognizable name (i.e. corresponding to its location):
In the Module Info tab, click the Modify button, enter the required text and click OK. The assigned name
will be displayed.
HX Module Info Tab
Figure 9-29
Page 250
4. Click the RF Paramaters tab and verify the following:

o All required services are enabled (Default = On) refer to Module Info tab for details on Service
1/2/3/4 (e.g. Service 1 = CELL800)
o UL Limiter is enabled (Default = On)
NOTE: DL Factory DCA Restore DO NOT click Restore button unless DL adjustment fails.
HX RF Parameters Tab
Figure 9-30
Verify that the System UL Gain is set to default configuration (i.e. Normal). See Table 9-1 for Description of
System UL Gain values.
Table 9-1. System UL Gain Values
Field Value
UL Gain
(dB)
UL Limiter
Threshold
(dBm)
NF Type
(dB)
Low
-30
13
Set in cases where mobile stations are very

near to the HX antenna (e.g. in cases where
HX unit antenna port is split to multiple lower
power antennas to cover standard office
building)
Normal
11
-40
10
Default for standard HX installations
High
21
-50
Set in cases where mobile stations are located

far from the HX antenna (e.g. in a parking lot,
where the HX unit is mounted high on a pole).
* Max. NF = Typical NF + 4dB

.
Page 251
Case Scenario
5. In the DL Adjustment tab, perform DL adjustment manually to complete the commissioning procedure.
o Set the Target Max Pwr (Target Pout) value according to site planning requirements. Default Target
Max Power value is the maximum value per each band (e.g. 33 dBm for 700 LTE band).
o DL Output Power can be adjusted to a lower level (up to 10dB lower) as required.
o Click the Adjust button.
o Confirm that the adjustment procedure is successful (Adjust Result shows Success) and verify
actual readings of Adj. Date and DL Output Pwr.
If adjustment procedure fails, refer to the RF Parameters tab, click the Restore button and perform
adjustment again.
HX DL Adjustment Tab
Figure 9-31
Page 252
9.3.2
HXn Device Configuration
To provision the HXn remote unit:

1. In the Network Topology tree, expand the relevant Controller item, expand the relevant OCH (to which the
HXn is connected) and click on the HXn. The HXn Alarms and Configuration tabs appear, as shown in
Figure 9-32.
HXn Alarms and Configuration Tabs
Figure 9-32
The HXn Alarms tab includes both system level and service level alarms and is continuously displayed in
the Configuration window.
The management and configuration options are distributed over three tabs:
o Module Info - device version and identification definitions
o RF Parameters service control options
o Comments tab used for entering any information relevant to the selected device (see section 5.3.2
for details)
Page 253
2. Verify that the alarms in the HXn Alarms tab show green.
Example of HXn Alarms
Figure 9-33
NOTE: Refer to section 7.5.13 for description of HXn alarms.

3. Mask irrelevant alarm conditions via the Modify button, to avoid having them reflected in the overall status
of the HXn unit. Refer to section 7.5.2.
4. In the Module info tab, enter the following information (by clicking corresponding Modify button for each
field):
o Name Enter an indicative name of up to 20 ASCII characters (e.g. indicating operator) and click OK.
The assigned name will appear in the Name field and in the Network Topology Tree.
o Ext. Name - Enter additional indicative information (such as physical location), click OK. The entry will
appear in the Ext. Name field. See section 5.3.1 for details.
o
Site ID (up to 20 ASCII characters) and Sub-site ID (up to 4 ASCII characters)
HXn Module Info Tab
Figure 9-34
Page 254
5. Click the RF Parameters tab.

Note: The initial values displayed for the configurable RF parameters are default values.
HXn RF Parameters Tab
Figure 9-35
Configure the RF parameters according to site requirements as follows:

o Service Control (Default=ON): ON service PA on; Off service PA off
o DL Max. Power (Default=33 dBm): Set the Target Max Pwr value according to site planning
requirements. Default Target Max Power value is the maximum value per each band (Range: 2133dBm).
o UL Attenuation (Default=0 dB): Range 0 to 31 dB in 0.5 dB steps
o Verify that the System UL Gain is set to default configuration (i.e. Normal). See following table for
Description of System UL Gain values.
Field Value
UL Gain
(dB)
UL Limiter
Threshold (dBm)
Case Scenario
Low
26
-36
Set in cases where mobile stations are very near to

the HXn antenna (e.g. in cases where HXn unit
antenna port is split to multiple lower power
antennas to cover standard office building)
Normal
36
-46
Default for standard HXn installations
High
46
-50
Set in cases where mobile stations are located far

from the HXn antenna (e.g. in a parking lot).
o Set the Target Max Pwr (Target Pout) value according to site planning requirements. Default Target
Max Power value is the maximum value per each band (e.g. 33 dBm for 700 LTE band).
o DL Output Power can be adjusted to a lower level (up to 10dB lower) as required.
o Click the Adjust button.
actual readings of Adj. Date and DL Output Pwr.
o If adjustment procedure fails, refer to the RF Parameters tab, click the Reset button and perform
adjustment again.
Page 255
9.4 MobileAccessGX Device Configuration

This section provides a description of how to manually commission the GX unit for initial operation.
Once the required physical connections have been completed, the GX unit is automatically detected (autodiscover) by the SC-450 and can be remotely monitored and managed.
The MobileAccessGX Remote Unit is centrally managed via the MobileAccess SC-450 Controller. Note that
MobileAccessGX is not connected directly to the controller. It is connected to the Optical Control Hub (OCHGX) which in turn is connected to the controller. Thus, the controller monitors views and manages the GX via
the OCH-GX to which the GX is connected.
The GX unit is managed via several dedicated panes that are accessed by clicking the relevant GX item in
the SC-450 Topology Tree.
NOTE: This section provides examples showing the GX-US Quad-band Web GUI, however the configuration
procedure is the same for al GX flavors. Any differences in configuration parameter values are specified.
9.4.1
Accessing GX Configuration Options
To access the GX configuration options

In the Network Topology tree, expand the relevant Controller item, expand the relevant OCH-GX (to which the
GX is connected) and click on the GX. The GX alarms and Config(uration) tabs appear.
Example of GX Unit Module Info Tab
MobileAccessGX Device Configuration
Figure 9-36
Page 256
The GX Alarms dialog is continuously displayed. The configuration options are distributed over four tabs:

RF Parameters service control options.
RF Adjustment provides the adjustment options.
Service Alarms used for masking redundant alarms
Comments - used for entering any additional information relevant to the device (see section 5.3.2 for
details).
9.4.2
Basic Setup Procedure
The setup procedure consists of the following main phases:
Verifying there are no alarms and masking irrelevant alarms

Assigning unit identification parameters
Verifying RF services are enabled and UL and DL attenuation set to 31dB
Performing DL adjustment for each service
To perform basic setup

1. Verify that the alarms show green in the GX Alarms dialog (system level alarms- Figure 9-37) and the
Service Alarms tab (displays specific alarms for each supported service - Figure 9-38). Refer to subsection of 7.5.16 for alarm descriptions.
Example of GX Alarms
Figure 9-37
Page 257
GX Service Alarms Tab
Figure 9-38
Table 9-2 provides a description of the Service Alarms shown in Figure 9-38.
Table 9-2. GX Service Alarms Description
Alarm
Description
Service Switch
Service control alarm indicating if the service is enabled/disabled. For example, can
be set due to user disabling the service (via RF Paramaters tab) or Over
Temperature alarm:
Green Service On
Red Service Off
Adjustment

DL PA
Green - DL Main Amplifier operating normally

Red - Faulty DL Main Amplifier
VSWR
Red - Antenna disconnected (VSWR > 1.5:1)
UL ALC
UL input power > -40 dBm
NOTE: If alarm is triggered, the input power level will need to be degraded to -43
Page 258
Alarm
Description
DL Output Power
High
DL Output Power
Low
UL LNA
Provide indication of UL Main Amplifier (Low Noise Amplifier):

Green - UL Main Amplifier operating normally
Red - Faulty UL Main Amplifier
2. Mask irrelevant alarm conditions, in both tabs via the Modify button, to avoid having them reflected overall
status of the GX unit (displayed in the GX Alarms area). See section 7.5.2 for description on how to mask
irrelevant alarms.
3. Click the Module Info tab:
Assign the unit a recognizable Name (e.g. indicating operator)/Extended name (e.g.physical location):
o Click on the Modify button adjacent to the Name/Extended name field (see section 5.3.1 for details on
Extended name field)
o Enter the required text and click OK. The assigned name will be displayed.
Assign unit Site ID number:

o Click on the Site ID Modify button
o Enter the Site ID number and click OK.
GX Module Info Tab
Figure 9-39
Page 259
4. Click the RF Parameters tab (shown in Figure 9-40).
GX RF Parameters Tab
Figure 9-40
Verify the following:

o All of the required services (model dependent - e.g. LTE 700F, CELL850F, PCS1900F, AWS2100F)
are enabled (Default = On)
o UL and DL Attenuation are set to default values: 0 dB
NOTE: After successful adjustment the UL and DL attenuation parameters show 0dB. Attenuation can also
be manually set between 0-30dB in 1dB steps.
Page 260
5. Click the DL Adjustment tab (see Figure 9-41).
GX DL Adjustment Tab
Figure 9-41
6. Perform the following for each service:

o Click the Adjust button. The Adjust DL Max Output Power dialog appears (as shown in Figure 9-42).
Adjust DL Max Output Power
Figure 9-42
The default DL Max Output Power is set to the maximum value (depending on GX flavor):
(GX-US: 46 dBm
; GX-EE: 43 dBm).
o Set the DL Max Output Power (GX-US: 37 to 46 dBm; GX-EE: 37 to 43 dBm) for the selected service
and click Adjust.
NOTE: DL Output Power can be adjusted to a lower level (up to 10dB lower) as required.
Page 261
actual readings of Adj. Date and DL Output Pwr:
Successful RF adjustment: ALC Level = Target Max Pwr

Failed RF adjustment: ALC Level Target Max Pwr
Adjust DL Max Output Power
Figure 9-43
Page 262
9.4.3
Configuring GX Quad-Band External Alarms
GX Quad-band supports external alarm connections (physically connected to various sensors which are
triggered according to the configured state of the switch). The external alarms must also be configured via
the SW. The Configuration window includes an External Alarms tab for the relevant devices where the
external alarms are configured according to trigger (i.e. Normally Open/Normally Close).
To configure GX Quad-band external alarms
1. Select the GX device for which external alarms have been connected from the Network Topology Tree.
2. Click on the device External Alarms tab in the Configuration window.
Example of External Alarm Tab
Figure 9-44
Page 263
3. Click the Modify button of the Alarm to be configured (Alarm 1/2/3/4). The External Alarm Dialog appears.
Example of External Alarm Dialog
Figure 9-45
4. Assign the External Alarm a recognizable name in the corresponding Name field.
5. Set the trigger as N.O (Normally Open) or N.C (Normally Closed) to determine the state of the contact
switch when triggered.
6. Determine the severity of the external alarm:
o Notify Green
o Minor Yellow
o Major Red
7. Mask option each external alarm can be disabled so as to be irrelevant if triggered and not to affect the
overall status of the device.
Note: refer to section 7.5.2 for details on masking alarms.
8. Click OK and repeat for each additional external alarm.
Page 264

SC-450 Help PDF

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SC-450 Help PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Corning

Date: October 2013

Standards and Certification

Standards and Certification ................................................................................................................................ 3

1.1 Key Features and Capabilities ........................................................................................................................... 10

Installation Guidelines ................................................................................................................................ 23

2.1 Quick Installation Procedure .............................................................................................................................. 23

Slave Controller Connections........................................................................................................ 23

2.1.1.3 PAU-6 Connections ..................................................................................................................... 24

Commissioning Wizard for RIU and MA1000/MA2000 Devices ................................................................ 56

3.1 Overview of Commissioning Wizard Procedure ................................................................................................... 57

Commissioning Additional CMA Elements ............................................................................................... 72

4.1 PAU-6 Configuration ......................................................................................................................................... 73

Navigating the Web GUI Application ....................................................................................................... 101

5.1 Network Topology ........................................................................................................................................... 102

Administration ........................................................................................................................................... 112

6.1 Multi User Account Management...................................................................................................................... 112

6.1.6 Tracking Group Users Activity Logs ........................................................................................................ 122

Monitoring and Troubleshooting ............................................................................................................. 138

7.1 Monitoring Summary Display ........................................................................................................................... 139

7.5.4.1 BTSC/BDAC Alarms .................................................................................................................. 166

Management Using Any Standard SNMP Manager ................................................................................. 192

8.1 SNMP Destination Address Configuration ......................................................................................................... 192

Appendix A: MA1000/MA2000 Manual Device Configuration................................................................. 222

9.1 Initial Configuration (Commissioning) Steps ...................................................................................................... 222

1.1 Key Features and Capabilities

End-to-end auto-detection of all CMA devices:

Scalable Master/Slave configuration of up to 8 Slave controllers per Master (with single-source

Key Features and Capabilities

Management and Configurations

Simply setup via the Commissioning Wizard:

Enhanced Users Management & security:

Intuitive display providing status at a glance:

Key Features and Capabilities

1.2 System Requirements

Web Client Requirements

System requirements for running SC-450 Web Client:

Screen resolution: 1024 x 768 pixels min

Release v5.4 has been optimized to operate on the following browsers:

Remote Access Requirements

1.3 System Controller Specifications

Environmental and Regulatory Specifications

Temperature and Humidity

0C to +50C (32F to 122F)

-20 C to 85 C (-4C to 185C)

Table 1-1: Temperature and Humidity Specifications

Safety and Regulatory Approvals

FCC 47CFR Part 15 Subpart B

Table 1-2: Safety and Regulatory Approvals

System Controller Specifications

SC-450 Power Requirements

General Power Safety Instructions

Be sure to disconnect all power sources before servicing.

Table 1-3: SC-450 Power Specifications

4.44cm x 48.26cm x 29.97cm (1.75 x 19 x 11.8)

Table 1-4: Physical Specifications

System Controller Specifications

DHCP: Server (this local port is set by default set to

Same as LOCAL Normally used for EC560 or

For Future Use. Disabled.

Table 1-5. Default Network Port Parameters

The System Administrator or Super User