User Manual v1.0 x LAN Port: 1 Gb Ethernet connection to the customer's network for remote management. By default, the port is configured to have a static IP address: 192.168.1.1; Subnet Mask: 255.255.0.0. Alternatively, the port can be configured as a DHCP client. IPv4 and IPv6 network protocols can be simultaneously supported. x INTERNAL Ports: Four RJ45, 100 Mb Ethernet ports used for management of connected ACMs. Note: Any one of these ports can also be used for a local connection if required.
User Manual v1.0 1. Go to the Control Panel and select Network and Sharing Center 2.
User Manual v1.0 3. Right click Local Area Connection and select Properties 4. Select Internet Protocol Version 4 and click Properties The window below appears: Set the IP address according to the default IP address of the LOCAL port and the subnet mask. An example of a possible IP address is: 172.16.1.5. The IP address can't be 172.16.1.1 as this address is used by the LOCAL port.
User Manual v1.0 3. Once the connection is established, open a browser and type-in the LOCAL port default IP address in the address bar: 172.16.1.1. The HCM Controller Log In dialog appears: 4. For first-time authentication use the following default values: x Username: admin x Password: default provided with your system. x Group: leave blank.
User Manual v1.0 3.4 Screen Layout The main menu (located to the left of the window) lists all the available management options. Next to the main menu either the system tree or the corresponding sub-options are displayed. The display changes according to the option selected from the main menu.
User Manual v1.0 3.5 Main Menu Options The table below lists the management options provided by the main menu: Table 10: Main Menu Options Icon Enables user to… View the system topology and information about the different system elements. View all system events and generate reports. Perform initial system configurations. This option is only visible to the system administrator. Administrative options to perform system configurations, implement updates, define and monitor user's activity.
User Manual v1.0 3.6 Remote Management This section describes the configurations required for remote session access using Ethernet connection via the LAN port. At this point the system is ready to be connected to the LAN according to the instructions below. For HCM modules only – using the provided RJ45/RJ45 communication cable, connect the HCM LAN port to the corporate LAN: Only HCM modules should be connected to the corporate LAN. ACM modules are connected via the HCM modules.
User Manual v1.0 Make sure the address format matches IPv4 or IPv6, according to the tab being updated. For Dynamic IP Address — set DHCP as Client, then click OK. 5. The HCM restarts after the LAN IP address is updated. 6. To open a remote management session: Open a browser and enter the LAN port IP Address in the address bar. Note: A Ping Tool option is provided to verify access to IP hosts (rather than opening another application).
User Manual v1.0 4. Initial Commissioning This section describes all the initial configurations that must be done by the system administrator. 4.1 Create new user groups Initially the system administrator is the only system user. In order to enable other users to log in to the system, the system administrator must create user groups for the different providers/carriers. When a new group is created the administrator of the new group must log in to add users to the group.
User Manual v1.
User Manual v1.0 4.2 Main Menu Config Option The option in the main menu is only visible to the system administrator. This section describes the configurations that only the system administrator can perform. 4.2.1 Site config When choosing the Site Config option from the Config submenu, the following screen appears: Each relevant site is presented by an image. By clicking on the site image, the configuration options for the specific site appear. The configuration options are described below.
User Manual v1.0 4.2.1.1 Module Owner The Module Owner tab shows all system chassis with the RIMs inside each chassis. The user can click on a RIM to have the carrier name displayed. This view is read only, where changes to RIM carrier assignments can only be done via the Channels tab in the main menu.
User Manual v1.0 4.2.1.2 RF Path The RF Path tab enables the user to easily see which RIMs belong to which service group. A service group consists of one or more RIMs which are connected to a DCM, and via a DRU to one or more remote units. Up to 2 service groups are supported. This view is read only. A RIM can be selected to show to which service group it belongs. Alternatively, a service group can be selected to show all the RIMs which belong to it.
User Manual v1.0 4.2.1.3 Max Input The Max Input tab allows the configuration of three parameters for each RIM: x Max Expected Power - UL gain range enabled is determined by the max expected power setting x UL Gain Mode - Set the UL Gain Mode for the selected RIM x UL Gain Value – Set UL gain (dB) for the selected RIM A single RIM can be clicked to be configured. Alternatively, a group of RIMs can be configured by selecting a service group, chassis or a frequency band.
User Manual v1.0 4.2.2 Power Sharing The Power Sharing tab shows all supported frequency bands and the carriers sharing each band. The carriers are sharing the power associated with the frequency band. 4.2.3 TDD Config The TDD Config tab allows the user to configure TDD related parameters per stack.
User Manual v1.0 4.2.4 Adjustment The Adjustment tab allows the user to start the adjustment process. During adjustment the status and relevant information are updated for each process.
User Manual v1.0 5. System Graphical User Interface (GUI) This section describes the system GUI options. 5.1 Main GUI Options The main menu options are described below. 5.1.1 Devices Screen – Element Management The Devices option provides visual information on the system layout, connected units and hierarchy, alarms etc. The system elements hierarchy tree is detected via an auto-discovery process, executed upon system start-up.
User Manual v1.0 5.1.1.1 System Tree Alarm icons This section includes a description of the different alarm icons. For each element, the system displays the most severe status in the system tree. Each device status is indicated by a coloured circle to its left, according to the symbols shown in the table that follows.
User Manual v1.0 5.1.1.2 Lists of alarms per system element The following tables details all the alarms per system element type. Table 12: HCM Alarms Descriptions Alarm Name HW Failure Description Faulty HCM hardware. Adjustment Failure Unsuccessful Adjustment procedure. Installation Failure Faulty physical installation between chassis. SW Release Mismatch A module (or modules) in the system do not have the defined active release. Several modules may not have corresponding software versions.
User Manual v1.0 Table 14: RIM Alarms Descriptions Alarm Name Overall Status HW Failure Description Overall status of enabled (unmasked) alarms. Hardware failure during startup or during normal operation. Over Temperature/Temp Ambient temperature inside the RIM is more than 75°C. Inconsistent Version/SW Version The module does not have the defined active release. Adjustment Fault Service State Unsuccessful adjustment procedure for the selected module. Service has been disabled by the user.
User Manual v1.0 Table 16: DCM Alarms Descriptions Alarm Name Description Inconsistent Version The module does not have the defined active release. Temperature Ambient temperature inside the DCM is high HW Failure DCM faulty hardware upon initialization or during operation. Adjustment Fault Unsuccessful Adjustment procedure. Overall Optical Links Overall status of enabled (unmasked) alarms in output optical links.
User Manual v1.0 Alarm Name Description SELF_PROTECTION TDD_OUT_OF_SYNC PA_OVERCURRENT The TDD band lost the sync on the TDD pattern. The current consumption of the PA exceeds the limit. CONNECTION_ERROR The following table lists alarms related to the CPRI protocol. These alarms are relevant for the optical links that some of the system elements have (see sections 5.1.1.6 - 5.1.1.8 below). Table 18: CPRI Alarms Descriptions Alarm Name Description LOS Loss of signal.
User Manual v1.0 5.1.1.3 HCM Device Form The device form of an HCM has a single tab: Info. The Info tab includes general information about the system element: Table 19: HCM Info Device Form Fields Field Information Name Chassis Serial Number Serial Number The name of the element as it appears in the system tree. The serial number of the chassis the HCM resides in. The serial number of the HCM. IP Address The IP address of the HCM. SW Version SW version updated in HCM.
User Manual v1.0 5.1.1.4 ACM Device Form The device form of an ACM has two tabs: Info and Power Supply.
User Manual v1.0 The Power Supply tab shows the relevant alarms status for both power supplies. There are two power supplies for backup and the switch between the power supplies is automatic. Explanation of the alarms can be found in section 5.1.1.2, under ACM Alarms Descriptions. In the example below there are no alarms related to any of the power supplies. 5.1.1.5 RIM Device Form The device form of a RIM has at least two tabs: Info and RF Parameters.
User Manual v1.0 Table 21: RIM Info Device Form Fields Field Name Information The name of the element as it appears in the system tree. Chassis Serial Number The serial number of the chassis the RIM resides in. Serial Number The serial number of the RIM. Slot Index The number of the slot in the chassis the RIM resides in. Band Type Band number according to LTE frequency bands. Band number is mapped directly to a frequency range. SW Version SW version updated in RIM.
User Manual v1.0 Table 22: RIM RF Parameters Device Form Fields Field Information DL Power Detector[dBm] Power of base station down link transmission. Range is -10 to +37[dBm]. Automatic Limit Control (ON/OFF switch) enable (On = default)/disable (Off) ALC function for RIM Service State (ON/OFF switch) Max Exp. Power [dBm] Service State OFF simulates RIM is disconnected. Transmission disabled by user. User defined max power for the base station transmission.
User Manual v1.0 A RIM which supports TDD (Time Division Duplexing) has an additional tab: TDD Table 24: RIM TDD device form fields Field Information UL/DL Allocation Mode 0 to 6 CP Type Cycle Prefix: Normal/Extended S Frame Format 0 to 8 Central Frequency (MHz) Low – 2526 Medium – 2593 High – 2660 Custom – 2526 to 2660 (0.
User Manual v1.0 5.1.1.6 DCM Device Form The device form of a DCM element has two tabs: Info and Optical Links. The Info tab has general information about the system element. Table 25: DCM Info Device Form Fields Field Name Information The name of the element as it appears in the system tree. Chassis Serial Number The serial number of the chassis the DCM resides in. Serial Number The serial number of the DCM. Slot Index The number of the slot in the chassis the DCM resides in.
User Manual v1.0 The Optical Links tab has information about the optical links of the DCM. Each optical link displays the colour of the most severe alarm related to it. In the example below, links 1 and 3 have no alarms, link 2 has a major alarm and link 4 has a minor alarm. 5.1.1.7 DRU Device Form The device form of a DRU element has two tabs: Info and Optical Links.
User Manual v1.0 Table 26: DRU Info device form fields Field Name Serial Number Information The name of the element as it appears in the system tree. The serial number of the DRU. SW Version SW version updated in DRU. IP Address The IP address of the DRU. Identify (ON/OFF switch) When the switch is ON the DRU LEDs are blinking (can be used to identify the specific module among many other modules). The Optical Links tab shows information about the optical links of the DRU.
User Manual v1.0 5.1.1.8 dLRU/dMRU/dHRU Device Form The device form of a dL/M/HRU element has three tabs: Info, Supported Bands and Optical Links. The Info tab has general information about the system element: Table 27: dLRU/dMRU/dHRU Info Device Form Fields Field Name Serial Number SW Version HE Chassis SN Information The name of the element as it appears in the system tree. The serial number of the dL/M/HRU. SW version updated in dL/M/HRU.
User Manual v1.0 The Supported Bands tab lists all the bands supported by the dL/M/HRU. Clicking on a band shows the band information. In the example below information about the AWS band is displayed: Bands supported The Optical Links tab has information about the optical links of the dL/M/HRU. Each optical link indicates the colour of the most severe alarm related to it. When clicking on one of the inputs, information about the link appears.
User Manual v1.0 5.1.1.9 DRU to DCM Connection ¾ Example: DRU to DCM(s) Connection The following figures indicate connectivity between DRU and DCM(s). For DRU the device status per DCM is shown in the following manner: Connected Click to access The number of arrows is the number of DCMs the DRU is connected to. The user may skip between the DRUs connected DCMs by clicking the arrow of the desired DCM.
User Manual v1.0 5.1.2 Events Screen The events option provides indications on the different events in the system. This includes: alarms, upgrades, admin-actions, etc. The events may be sorted according to the time they occurred, severity, source, etc. The user may choose to display the alarms history, masked alarms or active alarms.
User Manual v1.0 Tab Information Screen Example ( Set filters for displayed events Save to file Refresh screen view 5.1.3 Admin Screen The admin screen allows the user to define administrators, update credentials, upgrade firmware, generate reports and other admin options as detailed in the table below.
User Manual v1.0 5.1.3.1 Firmware The Firmware tab allows the user to upgrade the firmware version of the system elements. The HCM upgrade procedure consists of downloading the new software version, setting it as the “Active” version, and restarting the HCM. The new software can be activated either immediately or at a more convenient time as defined by the user. The procedures are performed via the Firmware submenu.
User Manual v1.0 Activate the new firmware – either immediately by using the time by using the 4. icon or at a scheduled (user defined) icon. After the new firmware is activated, and the controller automatically restarts: Log in to the system.
User Manual v1.0 5.1.3.2 Security Access security is provided by definitions of user groups created by the system administrator. Groups are used to limit access to specific devices so that only devices allocated to a group are accessible by members of that group. Session timeout Operation buttons Groups and access levels The Security tab allows the definition of the groups and the system users.
User Manual v1.0 Level Group Admin Description x HCM firmware upgrade. x R/O to all other parameters. The group admin has the capabilities of all the other access levels and the permissions to create and manage the users in the group. ¾ To add users to a group 1. Log in as the group administrator (use relevant group name at log in). 2. In the main menu bar, click 3. Click the 4. Enter the relevant data: Æ button.
User Manual v1.0 5. The new user account is added to the group list. For example: ATNT group has three users defined: admin, RF and Installer. 6. Users can be removed from the group list using the can be modified using the the group. icon. User information, including password, icon. The group administrator can change the passwords of the users in Note: Users with "Group Admin" access level can be added by the group admin. The original group admin can be removed.
User Manual v1.0 ¾ Session Access and Timeout Sessions are accessed or terminated according to the following criteria: x Up to ten simultaneous sessions for multiple users are supported. x The login of users is enabled according to priority.
User Manual v1.0 5.1.3.3 SNMP Config The SNMP config allows configuring and using any SNMP manager. 5.1.3.4 Reports The Reports option, provides access to all the reports provided by the system, including the general and Inventory Reports. The reports can be generated either in XLS or in PDF format. In addition, Device Logs can be exported for troubleshooting by the system administrator. ¾ General Reports The General Reports options are detailed in the table below.
User Manual v1.0 The General reports can be exported individually or simultaneously, using the All General Reports option, in PDF or XLS format. When all General files are exported in PDF format, the files are provided as a single ZIP file that includes individual PDF files; when exported in XLS format, the files are provided in a single XLS file with dedicated tabs. ¾ Inventory Reports Inventory reports provide detailed information in the selected format of "All Devices" or a specific system element.
User Manual v1.0 5.1.3.6 IP Settings The IP Settings tab allows the configuration of all stacks in the current MS group. It allows changing IP addresses that were auto assigned by DHCP, pinging a manually typed IP address and more. For more information about remote access configuration refer to section 3.6.
User Manual v1.0 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). In the “‘Ping” work area, enter the IP address and then click the “PING” button. The validity/invalidity result of the IP address appears in the Result line. 5.1.3.7 Backup The Backup tab allows the system administrator to backup and restore system configurations. Other users don’t have the permissions to perform these procedures.
User Manual v1.0 5.1.3.8 Activity Log The Activity Log is used to view activities such as configuration changes, according to a range of criteria such as User, Time, Group, etc. The information can be saved in *.csv format (can be opened with MS-Excel). The full log list of all user activities is displayed: The activity log display can be changed in the following ways: x Rows Per Page can be changed to list a different number of activities per page. Page navigation is at the bottom of the screen.
User Manual v1.0 5.1.4 Multi-Stack Screen MS management allows centralized network management of sites with multiple stacks deployment, sharing common configuration, where user-defined groups of stacks are automatically and immediately updated with common data. MS management allows a main admin (i.e. sysadmin) user to access a single stack GUI and create an MSgroup of up to 100 stacks.
User Manual v1.0 5.1.5 Channels Screen The Channels screen allows the user to create, view and modify the system RF channels. The configuration is done via a map: each map is a group of channels. The system allows storage of two map configurations: one that is currently being used by the system (named VALID map), and another map configuration that may be edited for future use (named INVALID map), where each map determines the configuration of all the system RF channels.
User Manual v1.0 The following table shows the available options for managing the RF channels map: Table 30: Map Options Option Enables user to… When clicking this button the following option appears: Switch between saved maps: invalid map or valid map. Save the map currently loaded in xls format. Load a map from xls file. Create a new map. Add a new RF channel to the map currently loaded. Check validity of the map currently being edited.
User Manual v1.0 5.1.5.1 Map Management Flows Below are examples of two map management scenarios. ¾ Example1: Create a new map from scratch Click the button and chose the invalid map Add all required channels using the Click the button to save the map in xls format. The map is not saved as valid or invalid. To continue working on the map use the button to import the xls file. Validate the map using the button button.
User Manual v1.0 ¾ Example 2: Change an invalid map and repeat the validation process: Click the button and select the invalid map Modify the map as required: add new channels, delete channels or edit existing channels information. Validate the map using the If there are no errors, map status is and it is saved as the valid map. Any previously saved valid map is lost. button. If there are errors, map status is and the updates are saved to the invalid map. The invalid map no longer exists.
User Manual v1.0 5.1.5.2 Add a New Channel When choosing the New Channel option, the following form appears: Table 32: Add Channel Form Field Information Cell Id Channel name entered by the user, may include location and other information regarding the channel. DL CF Downlink Center Frequency (MHz). UL CF Uplink Center Frequency (MHz). BW Bandwidth (MHz). Operator Name of operator (name of telecommunication company). TDD Service YES/NO; Indicates whether Time Division Duplexing is enabled.
User Manual v1.0 5.1.5.3 Submitting a map 1. When changes are made to any map the status of the map is map in process until the changes are submitted: 2. When done making changes to the map, you may press the Submit button. Validation of the map begins, and a progress bar appears: The system performs a basic check to make sure all parameters have valid values according to system limits, such as: Number of channels per specific BW, channels overlap, etc.
User Manual v1.0 3. A pop up window indicates the activation status. If activation fails, the errors are displayed, as well as the activation status per module. In the following example, the map status is "invalid map" (the map will be saved as the invalid map).
User Manual v1.0 6. SNMP Management The Everon system supports SNMP protocol, which allows standard monitoring via a large variety of 3rd party endpoint monitoring tools, also known as SNMP manager agents (e.g., HP OpenView, CA Unicenter, IBM Tivoli, CastelRock SNMPc): The Everon system sends indications on system events and failures to a userdefined monitoring destination-address, by sending SNMP protocol traps.
User Manual v1.0 6.1 SNMP Setup This section details the following steps, required to set SNMP trap monitoring: 1. Through Everon GUI: Set the SNMP protocol version parameters (SNMPv2 / SNMPv3), see 6.1.1 2. Through Everon GUI: Set traps monitoring destination addresses, see 6.1.2 3. Through your 3rd party SNMP monitoring tool: Load the MIB files, see 6.1.3 6.1.1 Set Protocol Version Parameters (SNMPv2 / SNMPv3) ¾ To set SNMP version: 1. Choose Admin from the main menu Æ SNMP Config.
User Manual v1.0 ¾ To configure SNMPv2 parameters 1. In the main menu bar, click 2. In the “V2 Configuration” area, click Æ to change the current configurations. The SNMP Community dialog appears: 3. Select/unselect the checkbox next to "Enable V2" to enable/disable SNMPv2. 4. If necessary, modify the community name in the Community field. 5. Click OK. ¾ To configure SNMPv3 parameters Æ 1. In the main menu bar, click 2.
User Manual v1.0 3. Enable "V3" to get the SNMPv3 configuration options: 4. Configure the following SNMPv3 parameters for the user: 5. 6. x Authentication protocol – MD5/SHA. x Privacy protocol – None/DES/AES-128. x Password – one password for both authentication and privacy protocols. Select the internet protocol version (IPv4/IPv6) for the SNMP traps and enter the trap destination address: x IPv4 - SNMPv3 trap destination address: IP (x.x.x.x).
User Manual v1.0 6.1.2 Set Traps Monitoring Destination Addresses This section explains how to configure the IP addresses to which SNMP traps are sent. Both IPv4 and IPv6 addresses are supported. In addition, each SNMP trap destination can be configured with a HB trap timer (“keep alive”). This option enables a periodical trap indicating that the device is operational. The trap is sent every user-configured time interval: 1-59 minutes.
User Manual v1.0 6.1.3 SNMP manager Setup: Load the MIB Files This section describes the steps necessary to view the traps sent by the monitored system in the management application. Note: It is assumed that the HCM IP address and the trap destination addresses have already been configured. ¾ To view interpreted traps through the 3rd party management application 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.
User Manual v1.0 No. Binding Description mru = (12) lau = (21) och = (24) gx = (25) mxu = (26) 4. trapDeviceSerial Additional data sent with the trap. This is the serial number of the device that generated the trap (up to remote unit level). Chassis serial number of the module 5. trapChassisSN 6. trapChassisIndex 7. trapSlotIndex 8. trapPortIndex 9. trapRemoteIndex 10. trapCtrlSerialNum Additional data sent with the trap.
User Manual v1.0 6.3 List of traps The system supported traps (i.e., alert messages sent by the system to the SNMP manager, indicating system events or failures), are provided in the following table.
User Manual v1.
User Manual v1.
User Manual v1.0 7.
User Manual v1.0 ¾ Radio Interface Frames (IHU/HEU) ¾ IHU Chassis Radio Interface Frame Modules RIMe – up to 8 modules per chassis DCM – up to 2 modules per chassis RIX- one module per chassis OIX - one module per chassis PSM – up to 2 modules per chassis dHCM – one module per system using IHU and 7 HEU chassis ACM -one module per chassis Single band module (see bands table) Interfaces: UL, DL and duplexed interface ports, QMA RF connectors Weight: 1.9 lbs (0.
User Manual v1.0 Mechanical Dimension (H x W x D) Mounting 7” x 17.3” x 18.95” (177.8 x 440 x 481.7 mm) 19”/4U Weight 58 Lbs (26.
User Manual v1.0 ¾ HEU Chassis Radio Interface Frame Modules RIMe – up to 12 modules per chassis RIX- one module per chassis PSM – up to 2 modules per chassis ACM -one module per chassis Single band module (see bands table) Interfaces: UL, DL and duplexed interface ports, QMA RF connectors Weight: 1.9 lbs (0.9 kg) Interfaces: Two 9-pin coaxial interface connectors (RF and Clock) Two QMA ports for reference clock connections between Radio Interface Frames (IHU, HEU) Weight: 1.54 lbs (0.
User Manual v1.0 Mechanical Dimension (H x W x D) Mounting 7” x 17.3” x 18.95” (177.8 x 440 x 481.7 mm) 19”/4U Weight 64.5 Lbs (29.
User Manual v1.0 ¾ DRU - Digital Routing Unit Interfaces & Mechanical CPRI ports CPRI ports Ethernet Ports External synchronization Mounting: Dimension (W x H x D) Weight Powering 32 x SFP+ (10.1 Gbps, CPRI line bit rate option 8) to Remote Units 4 x SFP+ (10.1 Gbps, CPRI line bit rate option 8) to DCM 2x RJ45 - LAN, Local 2*QMA -10MHz In/Out 19” rack, 1U Size: 19” x 1.75” x 16.5” (482.6 x 44.5x 419 mm) 19.
User Manual v1.0 ¾ Low Band LRU-Low power Remote Unit ¾ End to End System Performance ¾ Headend to Digital Low power Remote Unit RF Specifications Frequency Range Name Uplink Downlink Max. Operating Bandwidth-Non-contiguous Instantaneous Bandwidth Downlink Output Power (LRU) Attenuation Adjustable Range (1dB step) Pass Band Ripple (p-p) Channel Bandwidth Uplink Noise Figure (typical) Uplink IIP3 (typical) Frequency Range 600 MHz MHz MHz dBm dB dB MHz dB dBm VSWR EVM (256 QAM) (TM3.
User Manual v1.0 ¾ Medium Band LRU- Low power Remote Unit ¾ End to End System Performance ¾ Headend to Digital Low power Remote Unit RF Frequency Range Name Uplink Downlink Max.
User Manual v1.0 LRU 2:2 MIMO Antenna Combiner The LRU combiner is used to combine the 2 LRU’s: Low Band LRU and Medium Band LRU. The combiner has a total of 6 input ports and 2 output ports. There are two independent three-frequency combiners inside.
User Manual v1.0 ¾ MRU - Medium Power Remote Unit ¾ System performance ¾ Head End to Medium power Remote Unit RF Frequency Range Name 600 Uplink Frequency Range MHz Downlink 663698 617652 700L & 700U & FirstNet 698- 777716 798 728- 746746 768 Max.
User Manual v1.0 Interfaces and Mechanical CPRI Port Antenna Ports CBRS port Coupling port Dimension (W x H x D) Mounting and installation Weight Cooling Environmental Operational Temperature Indoor installation Inch (mm) Lbs (Kg) °F (°C) 2, SFP+ 10.1Gbps 1, 4.3-10 female 1, N-Type female 1 ,QMA connector that will enable measurement of the DL/UL signals while the system is working 17.45 x 10.5 x 15.75 (443.2 x 266.7 x 400) 19”,6U -Wall mount and Rack mount options 83.
User Manual v1.0 ¾ HRU -High-Power Remote Unit ¾ System performance (Head End to High power Remote Unit) RF Frequency Range Name 600 Uplink Frequency Range MHz Downlink Max.
User Manual v1.0 Interfaces and Mechanical CPRI Port Antenna Ports Dimension (W x H x D) 4, SFP+ 10.1Gbps 1 ,4.3-10 female OEU Inch (mm) RFU except 700 RFU 700 Mounting and installation Weight Lbs (Kg) Cooling Environmental Operational Temperature Outdoor installation (Ingress Protection) °F (°C) Wall mount OEU RFU except 700 RFU 700 Convection 14.6 x 3.2 x 13.8 (370 x 80 x 355) 19.7 x 3.2 x 13.8 (500 x80 x355) 19.7 x4.8 x 13.8 (500 x121 x355) 26.4 (12) 39.
User Manual v1.0 Medium Bands Combiner specifications The medium band combiner is designed to combine the following services: 1900, EAWS, WCS and 2.5GHz. If a single module is required a single input (2500) is used. If 2 * 2.5GHz RF modules are used (to support 4G and 5G services) 2 inputs are required (2500 IN1 and 2500 IN2) .
User Manual v1.0 8. APPENDIX B: Ordering information ¾ Headend Unit Assemblies and RF Modules HEU Assemblies Part Number HEU: HEU-1-00-1-A-A HEU-1-00-1-D-A HEU-1-00-2-A-A HEU-1-00-2-D-A Description Head End Unit Assembly (without RIMe); provided with ERFC, one PSM and one RIX ( supports up to 12 RIMe’s) Hosts one RIX module; one ETM. one PSM-AC and one ACM Hosts one RIX module; one ETM.
User Manual v1.0 Integrated Headend Unit Assemblies Note: IHUs support both RIMe and OIMs (ordering information detailed in HEU and OIU ordering information). Part Number IHU: IHU-2-11-1-A-dH IHU-2-11-2-A-dH IHU-2-11-1-A-A IHU-2-11-2-A-A IHU-2-11-1-D-dH IHU-2-11-2-D-dH IHU-2-11-1-D-A IHU-2-11-2-D-A Description Integrated Headend Unit Assembly (without RIMe and DCM’s); provided with ERFC cable, one RIX and one OIX.
User Manual v1.
User Manual v1.
User Manual v1.
