Corning ONE™ Wireless Platform User Manual APRIL 2013
Preface Material About This Manual This user guide provides all the information necessary to understand the architecture and perform the installation of Corning® ONE™ Wireless Platform.
Software Warranty Corning warrants to the original purchaser (“Customer”) that for the duration of the warranty period, one (1) year, commencing on the date of shipment of the Software, unless otherwise agreed in writing by Corning (the “Software Warranty Period”), the Software shall conform with, and perform the functions set forth in the Specifications, and shall be free from defects in material or workmanship (the “Software Warranty”).
Limitations of Liabilities Corning’s liability on any claim, of any kind, including negligence for any loss or damage arising from, connected with, or resulting from the purchase order, contract, quotation, or from the performance or breach thereof, or from the design, manufacture, sale, delivery, installation, inspection, operation or use of any equipment covered by or furnished under this contact, shall in no case exceed the purchase price of the device which gives rise to the claim.
Warnings and Admonishments There may be situations, particularly for workplace environments near high-powered RF sources, where recommended limits for safe exposure of human beings to RF energy could be exceeded. In such cases, restrictive measures or actions may be necessary to ensure the safe use of RF energy. The equipment has been designed and constructed to prevent, as far as reasonably, practicable danger.
ATTENTION! Compliance with RF safety requirements: • • Corning products have no inherent significant RF radiation The RF level on the downlink is very low at the downlink ports. Therefore, there is no dangerous RF radiation when the antenna is not connected. CAUTION! Use of controls, adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure.
T a b l e o f C o n te n ts P refac e Material ................................................................................................................................................... 2 About This Manual ................................................................................................................................................. 2 Hardware ............................................................................................................................................
1.4 Installation Guidelines ................................................................................................................................... 18 1.4.1 Rack Mount Procedure ........................................................................................................................ 18 1.4.1.1 General Instructions ............................................................................................................... 18 1.4.1.2 Rack Installation Safety Instructions ........
2.1.2.3 OIX (Optical Expander Module) .............................................................................................. 37 2.2 RF Path Remote End Site Components ........................................................................................................ 38 2.2.1 ICU (Intermediate Centralized Unit) ..................................................................................................... 38 2.2.2 RAU (Remote Antenna Unit) ..................................................
6.2.2 Ping Tool - Verifying IP Host Access .................................................................................................... 60 6.3 6.4 6.5 6.6 Required Pre-Setup Procedures ................................................................................................................... 61 Running the Setup Procedure ....................................................................................................................... 63 System Adjustment Procedure ....................
8.2.3 Group Users Access Levels ............................................................................................................... 111 8.2.4 Modifying Passwords ......................................................................................................................... 112 8.2.4.1 System Admin Password Change ........................................................................................ 112 8.2.4.2 Group Admin Password Change ..............................................
10 S NMP Management ................................................................................................................................... 137 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 SNMP Destination Address Configuration .......................................................................................... 137 Modifying the Read/Write Community Parameters ............................................................................. 138 SNMP Management using any Third Party SNMP Manager ..
1 Introduc tio n 1.1 About ONE™ The Optical Network Evolution Platform (ONE™) by Corning provides a flexible in-building RF and network digital coverage solution based on a fiber optic transport backbone. The fiber-optics infrastructure is easily deployable via a wide range of pre-terminated composite cables and advanced end-to-end equipment. Easy to design, Plug and Play™ connectors, significantly reduce installation cost and deployment time.
1.2 Key Features and Capabilities • Comprehensive Service Support - SISO/MIMO services. Currently – CELL, PCS, LTE700 and AWS • Flexible, user controlled sectorization - Advanced capacity and coverage management for better macro offload and enhanced user experience. • Broadband enabled: • A range of ready-made fiber-optic (and power) composite cables simplify installation at all levels.
1.3.2.2 Safety and Regulatory Approvals The safety and regulatory specifications listed below are relevant to all ONE™ devices. Regulation/Standard Category Approval Laser Safety FDA/CE 21 CFR 1040.10 and 1040.11 except for deviations pursuant to laser notice no. 50 (July 26, 2001) and IEC 60825-1, Amendment 2 (January 2001) EMC CE EN 301 489, EN55022, EN 61000 FCC 47 CFR Part 15, 22, 24, 27 Safety UL 60950 CAN/CSA-C22.2 No.
1.3.4 Dimensions and Weight of Units The tables below describe the physical specifications of the ONE™ units. Table 1-6. RF Path Headend Units Unit Dimensions (H x W x D) US [International] Weight: lbs [kg] HEU 7 x 17.3 x 18.95 in [177.8 x 440 x 481.7 mm] Chassis: 37 lbs [16.8 kg] Per RIM: 1.9 lbs [0.9 kg] Per RIX: 1.54 lbs [0.7 kg] HCM: 2.2 lbs [1.0 kg] PSM: 1.98 lbs [0.9 kg] OIU 7 x 17.3 x 18.95 in [177.8 x 440 x 481.7 mm] Chassis: : 37 lbs [16.8 kg] Per OIM: 0.7Kg [1.5lbs] Per OIX: 1.54 lbs [0.
1.3.6 Default Network and User Settings 1.3.6.1 Default Network Parameters The following table identifies the default settings for each of the Network Ethernet ports located on the front panel of the HCM. Port Name Configuration LOCAL DHCP: off IP: 193.168.1.1 Subnet Mask: 255.255.0.0 LAN DHCP: Client, or Static IP (default) IP: 192.168.1.1 Subnet Mask: 255.255.0.
1.4 Installation Guidelines The following installation assumes that site survey and installation planning (including power requirements) have been completed. This includes planning the distribution of antennas to provide the required coverage, as well as planning the layout of the devices and cables in the telecom closet or shaft. 1.4.
1.4.1.2 Rack Installation Safety Instructions The following guidelines help ensure your safety and protect the equipment from damage during the installation. • Only trained and qualified personnel should be allowed to install or replace this equipment.
1.5 System Architecture and Topologies The ONE™ solution fiber-optic infrastructure is used to transmit both RF and digital services: • RF services – fiber-optics infrastructure transfers converged wireless services from the headend towards Remote Antenna Units (RAU) deployed at the remote end locations according to user defined configuration.
1.5.2 Digital Path The Digital services from the corporate LAN (received via Ethernet Switch) are converted to optic signals by the CEU (Centralized Ethernet Unit) and routed over optic fibers towards the GEM units. The optical traffic is then converted to 1GbE by the GEM (Gigabit Ethernet Modules) modules and distributed to two third party equipment such as Access Points, Ethernet switch, etc. NOTE: GEMs can be connected to the CEU either directly, or via an ICU (described under RF Path (on page 20)).
The Main Menu Bar includes the following tabs: Tab Description Monitor N/A Config Displayed upon login by default. Displays general module information and device alarms and provides the configuration options for the available selected site devices. A brief description is given in Overall Device Display - Config Tab (on page 22). A detailed description is given in Device Configuration section (on page 91).
1.6.1 Overall Device Display - Configuration Tab The Config window is displayed by default upon login and includes the following for each selected element: • Network Topology Tree - hierarchically displays the connected and available site devices and their status. • Device Configuration Tabs - device specific which include the configurable parameters (e.g. service control, RF parameters) and general information (e.g.
1.7 User Controlled Sectorization ONE™ fiber-optics infrastructure allows various combinations of SISO and MIMO services to be routed from the headend to specified remote locations on each floor, according to user defined configurations. This allows optimizing service coverage and provides equipment savings. While the fiber-optics infrastructure is common, the services can be routed via service provider shared or dedicated equipment.
1.7.1 MIMO Configurations MIMO topologies provide more density by using two independent RF paths for the same service, where the independent paths are implemented by dedicated modules along the path. MIMO configuration is implemented by routing the two RF bands over dedicated RF paths at both the entry point (in the Headend Unit) and at the exit point (at the Remote Unit). Note that the Optical Interface Unit is wideband and the services are combined in a single OIM for routing to the same Remote End Unit.
1.7.3 Dual Sector Example In this example, two sectors (groups/layers) of services are defined: A,B,C and C,D. Note that a service can be allocated to any of the sectors at the same time. For example, service C is allocated to both Sectors. Both sectors are routed to the OIU for optic conversion. Each OIU module (OIM) can be configured to support either one or (if they do not have a common band) to both sectors and the corresponding services are routed from the OIM to its hosted RAU units.
1.7.5 Tri-sector Example with Two HEUs This tri-sector example supports two HEUs. In this topology, one HEU supports three sectors (groups/layers) and the other two sectors for a total of five sectors. These groups of services are all routed towards a common OIU. Each OIU module (OIM) can be configured to support any (legal) combination of sectors and the corresponding services are routed from the OIM to its hosted RAU units.
2 U nit Des c riptio ns - R F P a th This chapter provides detailed descriptions of the ONE™ solution components. The descriptions are organized according to RF and Digital path headend and remote end components. This includes port and LED interface descriptions. 2.1 RF Path - Headend Components ONE™ RF Path coverage solution includes the following headend elements: • HEU – Headend Unit • OIU – Optical Interface Unit Figure 2-1. RF Path Headend Components 2.1.
Figure 2-2. HEU Front Panel with Installed Modules Module Description HCM (Headend Control Module) (on page 30) Provides system management and control functions. In Master/Slave configurations, HCM is installed in the Master and ACM (on page 34) in the Slave. PSM (Power Supply Modules) 110-230VAC. If two are installed, both must be powered on. RIX (RF Expander Module) – Service specific conditioner units.
Port Description INTERNAL (TO ACM) [4] RJ45, 100Mb Ethernet ports - used for management of connected OIU systems (and/or HEU Slaves). LAN RJ45, 1Gb Ethernet port - connects to the corporate LAN for remote management LOCAL RJ45, 1Gb Ethernet port - local configuration and management CONSOLE RJ45, serial port - local configuration for service personnel SD Card Slot Supports uSD cards up to 32GB (used for example for saving configuration files) Table 2-2.
The following tables provide a description of the RIM ports and LED status indicators. Port Description DL/UL UL and DL simplex connections to the RF signal source DUP Duplexed UL and DL connection to the RF signal source Table 2-4.
2.1.1.3 RIX (RF Expander Module) The RIX Expander module provides the RF interface to the OIU unit. Two RIX Expander modules can be installed in each HEU chassis, to support up to four OIU (per HEU). If only one Expander module is installed, it is required to terminate the empty slot with the supplied termination. NOTE: The OIU Expander Modules are similar in appearance to the HEU Expander modules but are NOT INTERCHANGEABLE. Each Expander module is indicated as RIX or OIX on the bottom of the module.
2.1.2 OIU (Optical Interface Unit) The OIU interfaces to the HEU, performs the RF to optic conversion of the received signal and distributes the wireless RF services to the RAU units over the fiber optic infrastructure to the remote site. Each OIU supports up to 12 SM optic fibers (one fiber per OIM), which are routed to up to 36 RAU (three Remote Antenna Units per OIM). Figure 2-7. OIU Front Panel with Installed Modules Module Description ACM (Auxiliary Control Module) (on page 34).
2.1.2.1 ACM (Auxiliary Control Module) The ACM provides basic control functions (only) for the host chassis via a local connection. The ACM module can be remotely managed via an HCM (on page 30) connection. Figure 2-8. ACM Module Port Description INTERNAL (TO HCM) [4] RJ45, 100Mb Ethernet ports used for OIU and/or HEU slave management connections Console [1] RJ45, serial port used for basic IP configuration and local connection for service personnel Table 2-7.
2.1.2.2 OIM (Optical Interface Module) The OIM is a wideband RF to F/O (and vice-versa) media conversion module. Up to 12 OIM units can be installed in each OIU, where each OIM can support up to three Remote Antenna Unit (RAU) connections. Figure 2-9.
2.1.2.3 OIX (Optical Expander Module) Each OIX Expander module provides the RF interface to up to two HEU units via two 9-pin connectors. Two OIX Expander modules can be installed in each OIU chassis. Up to four OIU units can be hosted by an HEU. If only one Expander module is installed, it is required to terminate the empty slot with the supplied termination. NOTE: The OIU Expander Modules are similar in appearance to the HEU Expander modules but are NOT INTERCHANGEABLE.
2.2 RF Path Remote End Site Components The RF coverage solution remote end components comprise the following elements: • ICU (Intermediate Centralized Unit) - forwards optics along with DC to the RAU and its sub-modules. • RAU (Remote Antenna Unit) - provides RF distribution and includes internal antennas. It can also encase data distribution module (GEM). • RxU (Remote Expansion Unit) - installed in the RAU. Provides support for two additonal RF services for a total of 6 services per RAU.
Interface Description Power Connectors Up to eight DC power connectors, depending on number of power supply modules installed. LC/APC SM optics connectors implemented by up to two Edge modules inserted from the rear: six connectors per Edge module. AC Power Input 110-230VAC power input to unit. Table 2-11. ICU Front Panel Interface Descriptions Edge modules and power supplies are extracted and inserted from the rear of the unit. Figure 2-13. ICU Rear Panel Interfaces and PSM Modules 2.2.
Interface Description MGMT RJ45 local management connection PWR DC power inputs Main - connect to DC (from composite cable) Secondary – in case of PoE clients. Used when GEM modules are installed (in addition to Main) F/O LC/APC SM connectors for UL and DL optic connections Listening Mode N/A RF Filter (e.g. LTE, CELL) QMA RF ports for external cavity filter use (In/Out). For CELL and LTE filters. External Antenna Optional connection to broadband external antennas.
3 U nit Des c riptio ns - Digita l P a th This chapter provides detailed descriptions of the Digital Path components. 3.1 Digital Path Components The digital path comprises the following elements - located at the remote end • CEU – Centralized Ethernet Unit • GEM – Gigabit Ethernet Module NOTE: The GEM module can be installed in two configurations: in the RAU enclosure or (as illustrated below) as a standalone unit in a Docking Station. Figure 3-1. ONE™ Digital Path Architecture 3.
3.2.1 CEM (Centralized Ethernet Module) The CEU supports up to three CEM modules, where each CEM supports four Ethernet ports (LAN switch connections) and four F/O connectors (towards GEM modules). All interfaces (except for power) are located on the front panel (see section CEM). Figure 3-4. CEM Interfaces (Installed in CEU) The CEM module interfaces include Ethernet connections to the Ethernet switch, F/O connections and LED status indicators. The following table provides a description of the CEM ports.
3.3 GEM (Gigabit Ethernet Module) The GEM converts the received optical signal to two Ethernet digital connections, which are then routed along with PoE to two remote access points. The GEM module can be installed in the following configurations: • Installed in RAU - as an optional plug-in module (see RAU (on page 39)) • As a standalone module (GEU-S) - (see section GEU-S Installations (on page 52)) Figure 3-5. GEM Interfaces The following tables provide descriptions of the ports and LED indicators.
3.4 GEU-S (GEM Standalone) The GEU-S serves as the GEM docking station, enabling it to function as a standalone unit. The GEU provides the mounting option and DC power supply for the GEM module. See GEU-S Installations (on page 52) section for details on installation. Figure 3-6.
4 Ins ta lla tion – R F P a th E lements This chapter describes the installation of the RF path components. It contains only brief descriptions of the approach of each installation procedure. For step-by-step installation descriptions, refer to the Quick Start Guides provided with the ordered units and modules, and for specific guidelines on infrastructure planning, design and installation, please consult with a Corning Product Line Manager or Corning approved Installer. 4.
To install HEU 1. Mount HEU chassis - mount the (empty) HEU chassis in the 19-in rack. 2. Install modules - install modules (RIM, RIX, PSM and HCM (or ACM for Slaves) into their respective slots (see following figure). IMPORTANT! Unoccupied RIX (Expander Module) slots must be terminated with an Expander Termination module. Figure 4-1. Fully Occupied HEU Chassis 3. Power-On - connect the power cable(s) to the AC outlet(s) and switch On. If two PS modules are installed, both must be connected. 4.
4.1.2 Example of HEU Master-Slave Installation A Master-Slave HEU configuration enables single source management of several HEUs (and hosted elements) from a single HCM. The following figure provides an example of the connections between a Master and one Slave. Each OIU is connected to its host HEU through two connections: MGMT (ETH to INTERNAL port) and RF (RIX/OIX ports).
4.2 RF Remote-End Installation The remote end site (RF coverage) installation consists of installing the ICU (on page 48) unit and RAU (on page 48) module(s). 4.2.1 ICU Installation 4.2.1.1 General Information • The ICU is a passive unit installed at the floor level and provides the power and fiber interfaces to the RAU units (and to the GEU for the digital path).
4.2.2 RAU Installation 4.2.2.1 General Information • The RAU modules are deployed on the floor level and interface to the RF antennas. • The RAU can be provided in a number of configurations: • RAU (without RxU and GEM) • RAU + RxU • RAU + GEM • RAU + RxU + GEM NOTE: Existing RAU units can be upgraded with RxU and/or GEM modules – relevant Quick Start Guide with installation instructions are provided with ordered units.
• DC connection: o o RAU (without GEM) - MAIN POWER connection RAU + GEM - MAIN POWER + SECONDARY POWER connections • Fiber optic connection • External antenna (for above ceiling installations) • (Optional) RF filter connections (check with site planner) - for RAU and RxU (if exists) • GEM module connections (for RAU+GEM) - Ethernet and 3PE connections 5. Verify normal operation - via front cover LEDs: • RUN - Blinking green • LINK – Steady green • POWER – Steady green 4.2.
5 Ins ta lla tion – Digita l C o v era ge E lements This chapter describes the installation of the Digital Coverage components. It contains only brief descriptions of the approach of each installation procedure. For step-by-step installation descriptions refer to the Quick Start Guides provided with the ordered units, and for specific guidelines on infrastructure planning, design and installation, please consult with a Corning Product Line Manager or Corning approved Installer.
5.2 GEM The GEM unit is either pre-installed in the RAU unit or in the Gigabit Ethernet Unit (GEU): • RAU + GEM configurations - only require GEM module connections to Ethernet and 3rd party Access Points (DC power provided via RAU Secondary Power connection) • GEU (includes GEM) configurations - standalone installation which requires mounting the GEU and performing the power and Ethernet connections. NOTE: GEM modules can also be installed in existing RAU enclosures for expanded data coverage.
5.2.2 GEU-S Installations To install the GEU-S assembly 1. Locate the Ethernet and DC power wiring cables. 2. Hold the GEU near the mounting mechanism (not provided) and route the ETH and F/O cables through the mounting bracket. See QSG for details. 3. Mount the GEM with GEU enclosure onto a mounting mechanism. Figure 5-3.
6 C o mmis s io ning the S y s tem After physically installing all of the headend and remote-end elements, the initial setup procedure can be performed and the system can be commissioned either via a local or remote connection. NOTE: When unconfigured elements are detected the following message appears in the Config window of the Web Management GUI: "New uncommissioned units found, please run setup".
The HCM Controller Log In dialog appears. Figure 6-3. Log In Dialog 5. First time access authentication: • User Name = admin • Password = default provided with your system - to receive from CMA • Group = leave blank NOTE: For security, it is highly recommended to immediately change the password (Management tab, Security option) and login again using the new password. 6. Click the Log In button. The System Management (HCM) Module Info tab appears. Figure 6-4.
6.2 Configuring HCM Network Settings for Local and Remote Management There are two options for configuring the HCM network parameters for remote management across the customer LAN: • HCM LAN port – assigning the HCM LAN port a static or dynamic IP address • HCM LOCAL port – assigning a static IP address and connecting to the customer’s LAN for remote management; however, for troubleshooting and service purposes, a local connection is recommended.
3. To change the LAN Port network settings, click the Modify button in the LAN Port Configuration Area. The following dialog appears. Figure 6-6. IP Settings LAN Port Modify Dialog 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. Table 6-1. LAN Port IP Settings 4. To change the LOCAL Port network settings, click the Modify button in the LOCAL Port Configuration Area.
To Define… Do This… Static IP Address Set DHCP as None. Enter the IP Address and Subnet. Click OK. Set DHCP as Server and click OK. DHCP Server 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). Table 6-2. Local Port IP Settings 6.2.
6.2.2 Ping Tool - Verifying IP Host Access 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 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. Figure 6-8.
6.3 Required Pre-Setup Procedures Perform the pre-setup procedures as follows: 1. Verify that all of the installed devices have been automatically detected: • Click the Config tab. In the Topology Tree. • Verify that the LEDs adjacent to all of the Topology Tree items (ACM, RIMs, OIMs, RAUs, etc.) are colored in any other color but gray. • If an item is gray, verify the physical connections.
3. Verify the correct system time and date are set (used for Events time stamp): • In the Topology Tree, click System Management. • In the Module Info tab, Date and Time area, click Modify and set the time and date. 4. (Optional) - you may assign a recognizable name to each of the modules (e.g. ACM, RIM, OIM, etc.) as follows: • Click on the module item in the topology tree. A dedicated Module Info tab is displayed for each module. • Click on the (Name) Modify button and enter the name.
6.4 Running the Setup Procedure To perform the setup procedure NOTE: Make sure that you have performed the required pre-setup procedures (see section Required Pre-Setup Procedures) before running the Setup tool. 1. Click on the main menu Set-up tab. Figure 6-12. Setup Tab in Main Menu The Module Owner screen appears (first phase) and the HEU is displayed in the device view area. The unconfigured and un-assigned RIM modules appear gray.
• If all of the RIM modules are to be accessible to all groups, enable the Select All checkbox and then select All from the list of groups. Figure 6-14. Assigned RIM Modules • The selected and assigned RIM modules appear in green with a blue checkmark. • If not all of the RIM modules are assigned to a group, the following message appears: Figure 6-15. Unassigned RIM Module Alert Message • Click OK to continue or Cancel to assign the remaining RIM modules. 3.
NOTE: The displayed modules can be filtered according to module type by selecting the module type from the drop-down list and clicking the Filter button. Figure 6-16.
4. Enter the location description of all of the modules in the ZONE1-ZONE4 fields. Refer to following figure for example. Figure 6-17. Entering Zone Information There are two options for entering the zone info: • Entering the zone information description directly in the ZONE1-ZONE4 fields (as shown in figure above) • Clicking the Export button to access the Zone Info file (.csv) format. The Zone Info file appears with the list of all detected modules: Figure 6-18. Example of Zone Information .
Figure 6-19. Download Complete Message The Zone Info is displayed in the Zone Information screen in the corresponding fields and in the (Config) Module Info tabs of each module. 5. Click Next to continue to the MIMO SETUP screen. 6. To configure modules for MIMO path: o Select a RIM-M and the available RIM module(s) is indicated. Figure 6-20. MIMO Setup Phase o o Click on the RIM module to be connected to the RIM-M, so that both appear in green. Click on the Join button to connect the selected pair.
Figure 6-21. Connecting RIM and RIM-M Modules NOTE: Each RIM-M can only be connected to one RIM. Use the Break button to disconnect a pair of RIM-M and RIM modules. o Click OK if Progress Result is successful and repeat for additional MIMO pairs. 7. Click Next to continue to the RF Path phase. The RF Path screen appears. Figure 6-22. RF Path Screen - Default Display upon Initial Setup 8. Configure the RF paths between the headend and the remote-end units.
• For up to 3 groups (Layers 1-3) of services, where each group of services is transmitted only to RAUs connected to OIM modules assigned to the layer: o o Set the Layer to be configured to On (green) Select a RIM module (will appear green) NOTE: When a RIM-M module is selected the connected RIM module is automatically selected as well. The user must verify that an RxU is installed before configuring the RF path with a MIMO pair.
NOTE: If not all of the modules all configured before continuing to the next phase of the setup procedure the following alert will appear: "Not all devices are configured, are you sure you want to continue?" Click OK to continue to Max Input or Cancel to configure remaining devices. Figure 6-24. Unconfigured Devices Alert Message 10. Set the BTS DL Max Expected Power for each RIM. • Select the RIM(s) to be configured.
• Click Submit to apply setting. Figure 6-26. Setting ALC 12. Click Next to continue to the UL-Gain phase. Set the Gain Mode for each RIM: • Select the RIM(s) to be configured, either individually or according to Group, Chassis, or Band (selected Rims appear in green). • Set the Gain Mode for the selected RIM(s) to one of the following options: o o AutoSymmetrical (default): UL_gain_delta = band target power - max_exp_pwr Manual: select the value in the range of -19dB and +15dB (in 1dB steps).
• Click the Submit button. Figure 6-27. Setting UL-Gain (Manual) 13. Click Next to continue to AGC phase: • Set System AGC (Automatic Gain Control): On (default)/Off. • Click Submit to apply setting. Figure 6-28. Setting AGC 14. Click Next to continue to Adjustment procedure phase. See System Adjustment Procedure (on page 73) section.
6.5 System Adjustment Procedure The system Adjustment procedure phase is the last stage of the setup procedure.
2. The Adjustment procedure runs through the five process phases where the status is displayed for each process. Figure 6-30. Running the Adjustment Procedure 3. For failed processes – click the info link in the adjacent column to view the fail status details. 4. Upon successfully completing the Adjustment procedure the user can exit the Setup tool and monitor the system and the individual ONE™ solution devices through the Config GUI. 5.
How does it work? • When a Web access session is opened, the system automatically detects the existence of uncommissioned devices and provides a notification message to the user. • The user can then launch the Setup Tool by clicking the Setup tab. • The user is prompted through various GUI screens which display the required parameters and information for configuration. • Upon completion, the user can view a report for each Failed adjustment phase 6.6.1 Overview of Setup Procedure Figure 6-31.
6.6.2 Default Values Assigned in Setup Tool Each phase of the Setup Tool consists of configuring various parameters or settings, where default values are provided, enabling the user to continue to the next phase can if no other user input is given. Refer to the following table for the default values.
• The user cannot toggle between Setup operation and other screens while the Setup tool is running. To access configuration screens of specific devices, it is required to quit the Setup procedure. The Web GUI management application will appear. • The module information (e.g. Serial No., Slot, Band, etc.) can be viewed by pointing on the module (module property window will appear on bottom left of screen).
6.6.3.1 Module Owner The Module Owner phase enables the user to assign the (HEU) service specific RIM modules to groups (usually corresponding to operators). NOTE: The groups must be created before running the Setup Tool - see Defining User Groups (on page 107) section. After a RIM module has been assigned to a specific group, only a user from that group will have access to the RIM.
6.6.3.2 Zone Information The Zone Information phase enables the user to label each unit in the system to help classify and locate the different units with ease. An example of zone information defined for an RAU can be: Building 1; Floor 1; Room 1. The zone information defined in this phase will appear in the Module Info tab (Read-Only) of the device in the Web GUI Management (Config). Figure 6-34.
The user is provided with two options for configuring the zone information: • Entering the zone info in the ZONE1 to ZONE4 fields of each module in the Setup Tool Zone Information screen • Importing a Zone Information .csv file with all the zone information for each module NOTE: Upon initial setup, requires first exporting a .csv file and entering all of the information. The CSV file is stored on the HCM of the master HEU.
6.6.3.3 MIMO-SETUP The MIMO-SETUP phase enables the user to configure the RIM modules for the MIMO paths. The user is required to connect pairs of RIM-M and RIM modules supporting the same band (e.g. AWS) which will then be extended to the corresponding RAU (via the OIM). Figure 6-36. MIMO Setup Procedure • Only one RIM-M can be connected to a specific RIM. • When a RIM-M is selected, the available and compatible RIM modules will appear in grey.
6.6.3.4 RF Path In the RF Path phase, up to three groups of services (Sectors) can be configured, where each sector consists of a number of services (RIM). A RIM can belong to any or all of the sectors at the same time and each OIM module can then be assigned one or more of the sectors in any combination. (The same RIM service cannot be allocated to the same OIM in multiple sectors). The RAU modules hosted by each OIM distributed the services routed by the host OIM.
The following figure shows the RF-Path phase screen. Figure 6-38. RF-Path Phase Screen Note the following: • RF-Path phase default settings: • Layers 1-3 - Off • (HEU) RIM and (OIU) OIM modules - appear transparent ("ghost") • A number of RIMs can be associated with an OIM on each Layer • One RIM can be associated with a number of OIMs on a Layer • When selecting a RIM-M, the connected RIM is automatically selected as well and configured for the same Layer.
6.6.3.5 Max Input The Max Input phase is used to set the BTS DL Max Expected Power for each RIM. The following figure shows the Max-Input phase screen. Figure 6-39. Max-Input Phase Screen 6.6.3.6 ALC The ALC phase of the Setup procedure enables the user to enable or disable the ALC (Automatic Level Control) function for each RIM module (Default=On). The following figure shows the ALC phase screen. Figure 6-40.
6.6.3.7 UL Gain The UL-Gain phase of the Setup Tool is used to set the system UL gain control. There are two modes: • Autosymmetrical gain setting (default): UL Gain Delta=Band Target Power - Max Exp. Power • Manual gain setting: UL Gain delta=User definition (gain range value between -19 to +15 dB) The following figure shows the UL Gain screen. Figure 6-41.
Figure 6-42.
6.6.3.8 AGC The AGC phase of the Setup Tool enables the user to enable/disable the AGC (Automatic Gain Control) function (system level) for the uplink and downlink. The following figure shows the AGC phase screen. Figure 6-43.
6.6.3.9 Adjustment The Adjustment phase performs the adjustment procedure for the uplink and downlink gain of the RIMs and OIMs, as well as adjusting the target output power of the services transmitted from the RAU/RxU. The Adjustment procedure is initiated upon clicking the "Start" button in the screen. The following figure shows the Adjustment phase screen. Figure 6-44. Adjustment Phase Screen There are six processes, where the status for each one is displayed i the adjacent field.
Figure 6-45.
7 Dev ic e C onfigura tion After successfully commissioning the system and performing the setup procedure (using the Setup Tool), you may now proceed with (manually) fine tuning and modifying device parameters to suit the site needs via the Web GUI Management application. The manual configuration and monitoring options are accessed via the Config tab, which provides dedicated configuration tabs for each device/module.
7.1 System Management (HCM) The System Management element is the root element of the Network Topology Tree and is representative of the (HEU) HCM module. Upon selecting the System Management element, all of the HEU and connected OIU chassis (including RIM and OIM modules) are displayed in the device view area. The System Management Config screen also displays the HCM Alarms tab (see section System Management (HCM) Alarms for details) and the Module info tab. Figure 7-2.
7.2 HEU Configuration The HEU configuration consists of defining parameters for the ACM (Auxiliary Controller Module) and for each installed RIM (RIM Interface Module), where each module is configured through dedicated configuration options tabs. 7.2.1 HEU ACM To access the (HEU) ACM, click on the ACM hosted by the HEU in the Network Topology or in the device view area.
7.2.2 RIM Each RIM must be configured individually through its' dedicated Config tabs. To configure RIM 1. Click on the RIM in the Network Topology or in the device view area. The Module Info tab is displayed by default. The selected RIM (and associated OIM) will appear green in the Device View area. Figure 7-4. RIM Module Info Tab The Module Info tab includes general information (R/O) such as Location (defined during Setup procedure), S/N, Band, Carrier, etc. 2.
Figure 7-5. RIM RF Parameters Tab 4. Configure RF parameters according to site settings: • Max Expected Power - set the BTS DL Max Expected Power: o o o Default Max.
7.3 OIU Configuration The OIU configuration consists of defining parameters for the ACM (Auxiliary Controller Module) through which the unit is controlled and managed and for each installed OIM (Optical Interface Module). Each module is configured through dedicated configuration options tabs. 7.3.1 OIU ACM NOTE: The ACM Module Info and Power Alarms are the same for modules installed in either HEU or OIU chassis.
7.3.2 OIM The OIM configuration only consists of assigning the OIM an indicative name (optional). To configure OIM 1. Click on the OIM in the Network Topology or in the device view area. The Module Info tab is displayed by default. The selected OIM (and associated RIMs) will appear green in the Device View area. Figure 7-7. OIM Module Info Tab The Module Info tab includes general information (R/O) such as Location (defined during Setup procedure), S/N, Band, Carrier, etc. 2.
7.4 RAU Configuration To configure the RAU 1. Click on the RAU in the Network Topology (under the hosted OIM) or in the device view area. The Module Info tab is displayed by default. The selected RAU (and associated OIM) will appear green in the Device View area. Figure 7-8. RAU Module Info Tab The Module Info tab includes general information (R/O) such as Location (defined during Setup procedure), S/N, Carrier, etc. 2.
3. Click on the RF Parameters tab. The following tab appears. Figure 7-9. RAU RF Parameters Tab The RAU RF Parameters tab includes the input power (dBm) measured by the DL power detector for each service and the RAU Antenna Source option. 4. The Antenna Source type is set to Internal by default. To change to External - click the Modify button, select External option and click OK. NOTE: make sure that an external antenna is connected to the RAU.
7.5 RxU Configuration To configure the RxU 1. Click on the RxU in the Network Topology (under the hosted RAU) or in the device view area. The Module Info tab is displayed by default. The selected RxU (and associated RAU and OIM) will appear green in the Device View area. Figure 7-10. RxU Module Info Tab The Module Info tab includes general information (R/O) such as Location (defined during Setup procedure), S/N, Carrier, etc. 2.
3. Click on the RF Parameters tab. The following tab appears. Figure 7-11. RxU RF Parameters Tab The RxU RF Parameters tab includes the input power (dBm) measured by the DL power detector for each MIMO service and the RxU Antenna Source option. 4. The Antenna Source type is set to Internal by default. To change to External - click the Modify button, select External option and click OK. NOTE: make sure that an external antenna is connected to the RxU.
7.6 Removing a Hosted Device from Baseline The System Management application 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 Perform Reset the Baseline 1.
8 A dminis tra tion This chapter describes the administrative options supported by the ONE™ system. These include: • IP and SNMP settings • Creating and managing multi-user account groups • Configuration backup and restore • Software version upgrades • Viewing information on devices and various modules • Viewing the activity logs The administrative operations described in this chapter are accessed from the Management Menu Tab (on page 105). 8.
Options Descriptions Firmware HEU HCM firmware upgrade. See Firmware Upgrade (on page 120). Security Creating and managing multi-user account groups and monitoring user activities. See Multi User Account Management (on page 106). SNMP Config For using any SNMP manager. See SNMP Config (on page 137). Reports Summary information on various types of devices in the network along with basic physical and configuration information on each device. See Generating Device Reports (on page 117).
Figure 8-2. Management Tab – Security Menu Option 8.2.1 Defining User Groups Only the System Administrator defines Groups, where the Groups are defined only by name. After the groups are defined, user accounts are created where each user is defined within a group. In addition, during the set-up procedure the system modules (i.e. RIMs) are also associated to defined groups. The group names comprise of case sensitive, alphanumeric characters (no spaces allowed).
To create a new group 1. Login as System Administrator. 2. Click on the Security option of the Management tab. The Group Management dialog appears, displaying all defined groups. Figure 8-3. Group Management Dialog NOTE: To remove a group, click Remove. The group along with its accounts is removed after a verification prompt. 3. Click Add. The Add Group dialog appears. Figure 8-4. Add a New Group 4. Enter new group name (enter only alphanumeric characters - no spaces) and click OK.
8.2.2 Defining User Accounts The Group Administrator is assigned default authentication (which should be modified). Each Group Admin can define and manage the users in his/her group. The Group Administrator does not have access to users from any other Group. Note the following: • Each group can support up to 20 Users. • Each new User is defined by a Name, User Level and Password. • Users in a group can be of different access levels.
5. Select the Access Level (on page 110). The User can be assigned one of five access levels, where users in a group can be of different access levels. 6. Assign the Password - it is recommended to use numbers as well as letters. 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 Group list. Figure 8-7. List of Groups 8.
8.2.3 Group Users Access Levels A Group user can be assigned one of five Access Levels, where users of different access levels can be defined in the same Group. The HCM supports up to three simultaneous sessions for multiple users (local/remote access).
8.2.4 Modifying Passwords Note the following: • Each user (including Admin level (on page 112)) can modify his/her own password • The Group Administrator (on page 112) of each group can reset the passwords of the users in his/her group (does not require old password) • User passwords must consist of at least 8 alphanumeric characters (no spaces); however only four asterisks (****) are displayed. • HCM management auto-checks the strength of the password and indicates if the password is too weak.
8.2.4.2 Group Admin Password Change When the System Administrator creates a group, the group is automatically assigned a Group Administrator with default authentication according to the group name. It is recommended that each Group Administrator change the default authentication. This section describes two operations: • Password change of the Group Admin • Password change of the User by the Group Admin To Modify the Group Admin Password 1.
• You may change the User Name and/or Password. Click OK. Figure 8-12.
8.2.4.3 User Own Password Change Each user can modify his/her password. The User password can also be modified by the Group Admin. (on page 112) User change of own password 1. Log in to the HEU Management GUI with your User authentication. 2. Click on the Security option of the Management tab. 3. To change your password: • Click Modify Password. • Enter the Old Password, New Password, confirm the New Password and click OK. Figure 8-13.
8.2.5 Session Timeout Settings User session timeout is enforced in the event that no user activity has been detected over a specific time period. 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. Figure 8-14. Management Tab – Security Menu Option 2. In the Session Timeout Settings work area, click the Modify button. 3. Enter timeout value between 1 min. and Never. 4.
8.3 Backup & Restore Configurations The management application enables backing up a system configuration, which can later be restored. The configuration file can be stored on a computer or on a micro SD card inserted in the HCM (see section 2.1.1.1 for SD card slot location). It is recommended to backup the configuration after each configuration change. To backup or restore a configuration 1. Click on the Management main menu tab and then click the Backup & Restore sub-menu item. 2.
8.4 Generating Device Reports Inventory reports listing the network elements including module info such as IP and serial number can be generated. The information displayed in the inventory reports varies according to the type of unit or module. To Generate a Report 1. Click the Management tab and click the Reports sub-menu. 2. Click the Create button in the Inventory Reports area. 3. Select a device from the drop-down list (or select All reports including all network devices) and click OK. Figure 8-16.
The File Download dialog appears. Figure 8-17. File Download Dialog 4. Click the Open option to view the report file without saving or Save to save on the generated report on the computer. 5. The inventory report is generated as a .csv file. Example shows report for HCM unit. Figure 8-18. Example of Generated Inventory report in .
8.5 Activity Log The Activity Log is used to view activities such as configuration changes, according to a range of criteria such as User, Date, Device or Activity type. The information can be saved in *.csv format. To view 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. Figure 8-19. Activity Log Display Display options: • Use Show entries to determine the number of displayed events per page.
8.6 Firmware Upgrade The HCM firmware can be upgraded via the web-based GUI. Upgrading the SW requires loading the SW to the Standby Bank, and swapping the Standby Bank with the Active Bank. To perform SW upgrade on an HCM installed in the master HEU 1. Open session to HCM (see Opening a Local Session). Click the Management tab and then the Firmware menu option. The following screen appears. Figure 8-20. Firmware Upgrade Procedure 2.
• Downloaded SW version appears in Standby Bank. Figure 8-21. Management-Firmware Screen 5. Click the Swap button. The Swap and Restart prompt appears. • Click OK. • Downloaded SW version appears in Active Bank area and HCM is automatically restarted. 6. Log out of the system when procedure is complete. 7. Repeat Step 1 (login) and Step 4 (download new SW) - the SW Download procedure is repeated so that the new SW appears in both the Active Bank and the Standby Bank.
9 Mo nito ring a nd T roubles ho o ting IMPORTANT: The available tabs and options in the System Management Web GUI may vary depending on the access level used to open your session. 9.1 Overview The Web Management Application provides several tools for monitoring and troubleshooting the site. The tools are available in the Config and in the Events tabs. The tools include: • Network topology tree (on page 123) - provides general view of system status and status of each device (Config tab).
9.2 Network Topology Tree - Fault Sourcing The Web GUI Management application Network Topology Tree is viewed in the Config main menu tab. The Network Topology tree shows the elements of the HCM controller to which the session was opened, and the hosted devices. The connected network devices are automatically detected in the baseline and displayed in the Network Topology Tree in the hierarchy in which they are connected.
The ONE system element devices are displayed as follows: Item in Tree Description System Management Root item, represents the HCM controller (physically installed in the HEU) HEU Headend Unit hosting corresponding modules (ACM, RIM). NOTE: The HCM controller module is physically installed in the HEU chassis, however in terms of management is divided into two elements (HCM - System Management and ACM).
9.3 Fault Sourcing through the Device View and Alarms Tab When an item in the Network Topology Tree is clicked, an icon representative of the device view appears along with the configuration and Alarms tabs. The LED indicator on each module in the device view represents the overall status of the module which corresponds to the Overall Status alarm in the Alarms tab and the LED in the Network Topology.
Alarm Name Description HW Failure Indicates HCM faulty HW Adjustment Failure Indicates unsuccessful adjustment procedure Installation Failure Indicates faulty physical installation in one of the modules SW Release Mismatch Indicates that a module (or modules) in the system does not have the defined active release; several modules may not have corresponding SW versions; severity – minor Connectivity Indicates faulty connectivity state in one of the in one of the previously discovered (baseline) sy
The following table provides the descriptions for the ACM Alarms. Alarms that are specific for the HEU or the OIU ACM module are indicated as such.
9.3.3 RIM Module Device View and Alarms Click on the RIM module in the Network Topology to display the RIM device Alarms and the module device view. NOTE: When the RIM is selected, the RIM module and the associated OIM module appear green in the Device View Mode. Figure 9-7. RIM Device View and Alarms Figure 9-8. RIM Device View Icon The following table provides the descriptions for the RIM Device Alarms tab.
Device Alarm Description HW Failure Indicates HW problem during startup or during normal operation; Alarm severity – minor (yellow) Overall Status Indicates overall status of enabled (unmasked) alarms Table 9-5. RIM Device Alarms Descriptions 9.3.4 OIM Device View and Alarms Click on the OIM hosted by the OIU module in the Network Topology to display the OIM module Alarms tab and the module device view.
9.3.5 RAU Device View and Alarms Click on the RAU hosted under the hosted OIM module in the Network Topology to display the RAU Alarms tab and the module device view. When the RAU is selected, the corresponding OIM and RIM modules in the RF path are also indicated (appear green). Figure 9-11. RAU Alarms Tab and Device View Mode Figure 9-12.
The following table provides the descriptions for the RAU Device Alarms tab.
Device Alarm Description Inconsistent Version Indicates that the module does not have the defined active release Over Temperature Indicates that the ambient temperature in the OIM is ≥ 75◦C Antenna Indicates faulty antenna connectivity –external antenna not detected; Severity – major (red) Service LTE_MIMO/AWS_MIMO Service disabled by user Configuration Mismatch Unsuccessful adjustment procedure for the selected module HW Failure Indicates HW problem during startup or during normal operation; S
9.5 Events 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.
9.5.1 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. Figure 9-17. Events - Filtering Options 2. To display only events from one type of device, choose the device in Filter by Type field: RIM, OIM, RAU, etc. 3.
• You may also enter specific hours and minutes to further limit the range of time: Figure 9-19.
10 S N MP Ma na gement The SNMP Management is performed using any standard SNMP Manager. 10.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 HCM controller modules assigned to that domain. Up to 10 IP addresses can be defined per domain. To Define the Destination IP Addresses 1. Click the main menu Management tab and select SNMP Config (side bar) menu option.
10.2 Modifying the Read/Write Community Parameters Use this option to modify the Read/Write Community Name of the HCM. 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. Figure 10-3. Management-SNMP Config Screen 3. Define the new Read and Write values and click OK. 10.
10.4 Loading the MIB Files To View the Traps Using a Third Party Management Application: NOTE: It is assumed that the HCM IP address has been configured and that the trap destination addresses are configured according to SNMP Destination Address Configuration section (on page 137). 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 maEvents.mib file. 4. Load and compile the maTraps.mib file.
• Event source indexes (trapsChassisIndex, trapsSlotIndex, trapsPortIndex, trapsRemoteIndex columns) – The device indexes in the system (chassis index, controller port index, device slot and RAU/RxU index) which generated the event. • Event text description (trapsEventText) – A short textual description of the event. • Event source device name (trapsCtrlName) – The textual name of the device which generated the event.
Object Name Description trapsEntry 1: trapsSequenceID Trap sequence ID varbind - sequence number of the trap in the last traps table. Enables tracking missing traps. 2: trapsTimeStamp Time and Date of the current trap. Format H:M:S D/M/Y 3: trapsGeneric The generic type of the trap instance 4: trapsBandNumber The band number that generated the alarm.
To Monitor the Managed System Using the MIB browser, select the desired MIB entry (one of the tables or specific object ID inside the maStd parameters group) and choose table view (in case of a table) or a simple GET command (in case of a maStd 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).
Trap Name Description End OID acmPSMBOutputUnderVoltage ACM Power Supply B Output Under Voltage 110 acmPSMBOutputUnderVoltageClear ACM Power Supply B Output Under Voltage Clear 111 acmPSMOutputUnderVoltage ACM Power Supplies Output Under Voltage 112 acmPSMOutputUnderVoltageClear ACM Power Supplies Output Under Voltage Clear 113 acmMasterClock ACM Master Clock 114 acmMasterClockClear ACM Master Clock Clear 115 acmSlaveClock ACM Slave Clock 116 acmSlaveClockClear ACM Slave Clock Clear
Trap Name Description End OID oimOverTemperatureClear OIM Over Temperature Clear 305 rauRFLowPower RAU RF Low Power 400 rauRFLowPowerClear RAU RF Low Power Clear 401 rauULOverPower RAU UL Over Power 402 rauULOverPowerClear RAU UL Over Power Clear 403 rauServiceOff RAU Service Off.
A ppendix A : S pec ific a tions Supported Services Frequency Range (MHz) Technology Service/Band Uplink (UL) Downlink (DL) LTE 700MHz 698-716 777-787 728-746 746-756 CDMA/WCDMA**/ TDMA/GSM/LTE* CELL800 824-849 869-894 CDMA/WCDMA**/TDMA/GSM/LTE* PCS1900 1850-1915 1930-1995 WCDMA**/LTE* AWS2100 1710-1755 2110-2155 RF Parameters per Service Service/Band RF Parameter Frequency Range [MHz] Max Output Power Per Antenna Port Max Input Power [dBm] LTE CELL PCS AWS 700 MHz 800 MHz 1900 MH
Environmental, Standards and Optical Environmental Operating Temperature 0°C to +50°C (32°F to 122°F) Storage -20°C to 85°C (-4°F to 185°F) Standards and Approvals Laser Safety FDA/CE 21 CFR 1040.10 and 1040.11 except for deviations pursuant to laser notice no. 50 (July 26, 2001) and IEC 60825-1, Amendment 2 (January 2001) EMC CE EN 301 489, EN55022, EN 61000 FCC 47 CFR Part 15, 22, 24, 27 Safety Optical Optical Output Power <9dBm Max.
Unit Specifications RF Coverage Component Specifications Head End Unit (HEU) HEU will host the following modules: • RIM - Radio Interface Module; RF source conditioner. Up to 12 RIMs can be hosted by the HEU.
OIM Interfaces Optical Interface: [1] MTP Connector [6] Kenpole connector for 1:1 direct signal transportation, 3 UL and 3 for DL OIX Interfaces RF Interface – [2] 9-pin connectors ACM Interfaces [4] RJ45 INTERNAL ports [1] RJ-45 CONSOLE port System LEDs – PWR, RUN, SYS, FAN PSM (See PSM in HEU section for interfaces) Power Consumption [Full Chassis]: 300W Physical Characteristics [Chassis] Mounting: Rackmount - 19" and 4U Dimensions [H x W X D] US [International]: Chassis: 7 x 17.3 x 18.
Intermediate Centralized Unit [ICU] Chassis Interfaces Power Input: 110-240V AC, 50-60 Hz power Output: [8] DC ports- 57V DC, Max. 60V [UL limit] Edge Module Interfaces [1] MTP SM fiber port to [6] LC/APC SM Physical Characteristics Mounting: Rackmount - 19" 1U Dimensions [HxWxD]: US [International] 17 x 15 x 19.2 in [430.5 x 379.8 x 488 mm] Weight lbs [kg]: 5.5 lbs [2.
Remote Expansion Unit (RxU) Services Add-on unit supporting two service AWS MIMO and LTE700) MIMO Interfaces [3] pins for integration with RAU [power, control and RF] Management Management via host RAU Physical Characteristics Mounting: Installed in the RAU enclosure Dimensions [H x W X D] US [International]: 1.09 x 12.8 x 9.8 in [27.7 x 327.5 x 250 mm] Weight lbs [kg]: 3.08 lbs [1.
Gigabit Ethernet Module/Unit [GEM]/GEU] Services GEM – Media converter, Ethernet over fiber to Copper. 10/100/1000BASE-T Ethernet 1000BASE-X fiber. [2] 802.3at compliant Power over Ethernet [PoE] PSE ports Interfaces [1] LC/UPC Fiber optic port [2] RJ45 ports supporting 10/100/1000BASE-T copper interface with PoE + 802.3at PSE capability Physical Characteristics Mounting: Standalone: GEU Add-on: RAU Upgrade Module Dimensions [HxWxD] US [International]: 1.28 x 3.79 x 5.95 in [32.7 x 96.3 x 151.
Optical: Cabling, Unit/Modules Specifications Cabling: Fiber Management Vertical Plug & Play™ Plenum Optical cables MTP Fiber Connectors 12 – 144 fibers 2-sided or 1-sided Armored, Non-Armored Horizontal Composite Plenum Tether Assemblies Fiber: LC/APC, 2 – 24 fibers Cu: 16AWG, 14AWG, 12AWG; 2 – 12 Conductors Armored, Non-Armored FMU 1U: 144 Fibers 2U: 288 Fibers 4U: 576 Fibers Plug & Play™ Modules or Splice Cassettes Appendix A: Specifications P/N 709C011801 Page 152
Ordering Information HEU Chassis and Modules Part Number Description HEU Head End Unit Assembly, Support for 1-12 Radio Interface Modules (w/o RIMs) PSM-HO Head End/Optical Interface Unit Power Supply; Includes US plug power cords HCM Head End Control Module; Includes (2) RJ45 cables (2m) FAM-HO Head End/Optical Interface Unit Fan module; One module including four fans RIX Radio Interface Expander – HEU Expansion Module; Two must be ordered RIM-L70 LTE 700 MHz service Radio Interface Module for
Remote Units Part Number Description RAU-C85P19L70A17 CELL 850, PCS1900, LTE700 and AWS1700 Remote Antenna Unit Quad-service CELL, PCS, 700 MHz LTE and AWS; SMF RAU-G-C85P19L70A17-E Remote Antenna Unit with assembled GEM module; Support for CELL/PCS/ 700 MHz LTE and AWS; Support for Ethernet services.
