RedMAX Admin and Maintenance Guide

RedMAX AN100U/AN100UXAdministration and Maintenance GuideDecember 2009Version: 2.1.0

Part Number: 70-00133-01-01

Disclaimer:

The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable; however, they are presented without express or implied warranty. Additionally, Redline makes no representations or warranties, either expressed or implied, regarding the contents of this document.Redline Communications Inc. shall not be liable for any misuse regarding this product.The information in this document is subject to change without notice.Safety Notice:

Operators should read the Users Manual and Installation Guide for the RedMAX wireless products described in this manual to understand and follow all operating and safety instructions. Keep all product information for future reference.

Confidential and Proprietary Information:

This document constitutes confidential and proprietary information of Redline Communications Inc.. The contents of this document may be accessed and/or used solely by a licensee of Redline Communications Inc. software product(s) and solely in connection with the licensees authorized use of such product(s), or as otherwise expressly permitted by Redline Communications Inc. in writing. All other uses are prohibited. This document may not in any event be disclosed to any third party without the prior written authorization of Redline Communications Inc.

Trademark Information:

Redline Management Suite, Redline, RMS, RedACCESS, RedCONNEX and RedMAX are trademarks of Redline Communications Inc. All other brands and product names identified in this publication are trademarks or registered trademarks of their respective companies or organizations.

Copyright 2009, Redline Communications Inc.

All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems for any purpose without the express written permission of Redline Communications Inc.

Contact InformationHead Office: Redline Communications Inc.

302 Town Centre Blvd.Markham, ONCanada L3R 0E8

Web Site: http://www.redlinecommunications.comSales Inquiries:

North America:Toll Free Line:International:

[email protected]@redlinecommunications.com

Support:Web Site:

Email:Telephone:

www.redlinecommunications.com/support/[email protected] your local Redline Distributor

Table of Contents

CH APTER 1 About This GuideOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Other Documents in the Redline Product Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Supported Redline Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

CH APTER 2 OverviewMaintenance Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Establishing a Spares Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Monitoring Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Connecting to the Sector Controller Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Connecting to the Sector Controller Command Line Interface . . . . . . . . . . . . . . . 2-5Connecting to the Subscriber Unit Command Line Interface . . . . . . . . . . . . . . . . . 2-6Monitoring System Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Monitoring Statistical Results Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Monitoring the System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-91 Redline Communications Inc. Confidential and Proprietary

Using the Ping Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Using the Iperf Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Network Sniffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Using the rfMonitor Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Planning/Scheduling Equipment Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Personnel Required for Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Establishing and Recording the Baseline Configuration . . . . . . . . . . . . . . . . . . . 2-15Maintenance Record Keeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Establishing Secure, Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

VPN Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Remote Management of an SUO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Configuring a DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Configuring a Time of Day Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

CH APTER 3 Indoor Equipment MaintenancePerforming a Visual Inspection of the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Rebooting the Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Rebooting the AN100U/UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Rebooting the Subscriber Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Redundant Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2RPS Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Uplink Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Sector Controller Synchronization with the GPS Clock . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Local Synchronization versus GPS Synchronization . . . . . . . . . . . . . . . . . . . . . . . 3-6Verifying Network Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Changing from Local to GPS Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6AN100U/UX Operation in GPS Holdover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Working with Service Classes, Service Flows and Classifiers . . . . . . . . . . . . . . . . . . 3-13Checking RF and PHY Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

CH APTER 4 Outdoor Equipment MaintenanceRadio Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Replacing a Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Antenna Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Antenna Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Replacing the Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Verifying Power and RF Signal Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Interface (IF) Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6RF Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Performing a Spectrum Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Sources of Potential Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Inspect and Repair Lightning Protection System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Ground Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Components of Your Lightning Protection System . . . . . . . . . . . . . . . . . . . . . . . 4-11Verifying Your Lightning Protection System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Inspecting and Re-Applying Weatherproofing on Outdoor Connections . . . . . . . . . . 4-12Testing to Validate Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-132Redline Communications Inc. Confidential and Proprietary

CH APTER 5 AN100U/UX TroubleshootingOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Troubleshooting RedMAX Boot Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

AN100U/UX Does Not Power-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Subscriber Unit Does Not Power-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6AN100U/UX Occasionally Reboots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6AN100U/UX Fault LED is Blinking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Inrush Current at Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Troubleshooting Ethernet Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Cross-over versus Straight-through Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Cannot Establish a Connection to the Management Port . . . . . . . . . . . . . . . . . . . 5-9Duplex Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Troubleshooting Device Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Sector Controller Serial Communication Issues . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Sector Controller IP Connectivity Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Subscriber Unit IP Communication Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Troubleshooting Wireless Link Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18Cannot Establish a Wireless Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18LO1, LO2 and Radio Reference Frequency Errors . . . . . . . . . . . . . . . . . . . . . . . 5-21Indoor Subscriber Unit (SUI) Connectivity Issues . . . . . . . . . . . . . . . . . . . . . . . . 5-24Gauging Link Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Link Optimization and Reference RSSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27Subscriber Unit De-Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28RF Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29Viewing Noise Level Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32Performing a Site Spectrum Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

Troubleshooting Data Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Troubleshooting Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34Example of Working with Service Flow Classifiers . . . . . . . . . . . . . . . . . . . . . . . 5-35

Troubleshooting the Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39Common Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39MAC Auto Learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40Tracing Downlink Connectivity Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41Tracing Uplink Connectivity Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Software Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43High Latency on Secondary Management Channel (SMC) Latency . . . . . . . . . . 5-44

CH APTER 6 Self-Install End User TroubleshootingTroubleshooting Self-Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

No Data Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Redline Communications Inc. Confidential and Proprietary

Redline Management Suite Administration and Maintenance GuideEnabling the Secondary Management Channel . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2The Bridge Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Low Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

CH APTER 7 Disaster RecoveryOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Impact Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Lightning Strike . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Wind Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Extreme Temperature Exposure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

APPENDI X A Event Log Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Script - scan.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Input Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Script errorReport.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Input Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Script checkTime.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Input Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Script checkDailyPerSector.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Input Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Script findNoisefloor.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8Input Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-94Redline Communications Inc. Confidential and Proprietary

APPENDI X B AN100U/UX Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Interference Messages at Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19

Detecting Interference with Local or GPS Synchronization . . . . . . . . . . . . . . . . B-19Noise Floor Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20

APPENDI X C Subscriber Unit Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

APPENDI X D Synchronization Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

I N DEX5Redline Communications Inc. Confidential and Proprietary

Redline Management Suite Administration and Maintenance Guide6Redline Communications Inc. Confidential and Proprietary

Re

are either logged into a Web or CLI client session and have the correct user account privileges to access the network equipment, perform upgrades and other diagnostic functions.1-1dline Communications Inc. Confidential and Proprietary1About This Guide

OverviewRedlines RedMAX family of products, includes the AN100U sector controller, the AN100UX Macro sector controller, the RedMAX SU-I indoor subscriber unit and RedMAX SUO outdoor subscriber unit. The RedMAX AN100U/UX facilitate the rapid provisioning of new fixed and nomadic wireless broadband services, while their very low latency ensures reliable delivery of time-sensitive services, including circuit-switched voice traffic, voice-over-IP (VoIP), video and prioritized data traffic. RedMAX sector controllers can be deployed in clusters of up to six sectors, supporting hundreds of simultaneous subscribers per sector. The hardware is fully upgradeable in the field by software download, to accommodate future enhancements for scalability, extended packet classifiers, alternative encryption standards, and the continued development of the 802.16 standard.

About This Document

ScopeThis document provides detailed instructions for administering and maintaining the various components of your AN100U/UX sector controller installation. This document is intended for Redline-certified network maintenance personnel. It covers basic maintenance procedures for AN100U/UX and its optional accessories.

Note Unless indicated otherwise the procedures throughout this guide require that you

RedMAX Administration and Maintenance GuideWorking with RedMAX network elements requires a comprehensive understanding of data networking. You should also have extensive experience with configuration and operation of Redlines broadband, fixed, wireless access products as part of a WiMAX network or backhaul infrastructure. Additional background knowledge should include data networking theory.You should be familiar with the device interface. A detailed description of both the Web and command line interface are provided in the RedMAX AN100U/UX Base Station User Guide.Comprehensive operator and administrator training programs are available from Redline Communications. Please contact [email protected] for detailed information.

Document ConventionsThe following document conventions are used throughout his guide.

In addition to the above formatting conventions a number of naming conventions are also used to denote customer-specific information.

Table 1-1 Document Conventions

Format Description

Bold Commands, titles, and keywords that are displayed in the RMS or the OS graphical user interface are shown in bold.

User Guide:

Arguments, for which you must supply a value are shown in italics with angle brackets. Other Redline documents are also denoted in italics.

Ellipsis...

An ellipsis before or after example text, indicates that there is more content either before or after the examples that are shown. The entire contents of the file are not shown.

[ ] Elements in square brackets are optional. { x | y | z } Required alternative command options are grouped in braces and separated by

vertical bars. [ x | y | z ] Optional command options are grouped in square brackets and separated by vertical

bars. Navigation Steps >

Successive navigational steps are indicated with an arrow. You will need to progress through the navigational path using your mouse or keyboard shortcuts.

Ctrl+click Hold down the Ctrl key and click on line items, to select multiple items in tables or drop-down menus.1-2Redline Communications Inc. Confidential and Proprietary

Chapter 1 About This GuideOther Documents in the Redline Product Suite The following documentation is available for the Redline Management Suite.

Table 1-2 Document Conventions for Customer-Specific Information

Name Description

This is the name or IP address of the host machine, connected to one or more sector controllers, via the data port.

This is the password for accessing the sector controller Web or CLI interface. This is the software or firmware version number.

Table 1-3 Redline Documentation Suite

Title Part Number

RedMAX Hardware

RedMAX Base Station AN100U/AN100UX Install Guide 70-00059-01-02RedMAX Base Station AN100U/AN100UX User Manual 70-00058-01-01RedMAX Base Station AN100U/AN100UX SUO Quick Test 70-00116-01-00RedMAX AN100U/AN100UX Subscriber Outdoor Unit (SUO) Quick Install Guide

70-00091-01-02

RedMAX AN100UX Release Notes 70-00091-01-00RedMAX Subscriber Outdoor Unit (SUO) Quick Install Guide 70-00067-01-01RedMAX Subscriber Outdoor Unit (SUO) Installation Guide 70-00068-01-02RedMAX Subscriber Outdoor Unit (SUO) User Manual 70-00057-01-01RedMAX Subscriber Indoor Unit (SUI) Quick Install Guide 70-00077-01-02RedMAX Subscriber Indoor Unit (SUI) Installation Guide 70-00079-01-01RedMAX Subscriber Indoor Unit (SUI) User Manual 70-00078-01-01Redline Management Suite

Redline Management Suite Installation Guide 70-00065-01-11Redline Management Suite User Guide 70-00066-01-12Redline Management Suite Troubleshooting Guide 70-00084-01-01Redline Management Suite Quick Reference 70-00097-01-02Redline Management Suite Release Notes 70-00106-01-04Redline Management Suite Online Help (printed version) 70-00119-01-01Redline Management Suite Administration and Maintenance Guide 70-00124-01-01Redline Management Suite Northbound Interface Functional Specification 70-00131-01-001-3 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideSupported Redline EquipmentRefer to the RedMAX AN100U/UX Release Notes for a list of supported equipment.1-4Redline Communications Inc. Confidential and Proprietary

Re

Monthly Maintenance

Visually inspect all connections 2-1dline Communications Inc. Confidential and Proprietary2Overview

Effective preventive maintenance routines are essential to ensure the ongoing optimal performance of your sector controllers and outdoor equipment following initial installation and deployment. Effective remedial maintenance routines are also essential to ensure that when a fault does occur, the base station is up and running as soon as possible in order to minimize customer disruption and degradation of QoS.The information and procedures in this manual are intended as a guideline. You will need to define a maintenance plan that addresses the unique concerns of your specific network installation.

Maintenance Schedule You will need to monitor your equipment and make your decision about how frequently you need to perform various maintenance tasks based on the number of components, environmental conditions and the location of the your outdoor equipment.The following table provides general guidelines for system maintenance. You will need to modify this schedule based on your particular network installation and configuration.

Table 2-1 RedMAX Maintenance Schedule

Daily Maintenance Description/Required Tasks

Check Alarm Indicators Review the alarm indicators as outlined in the User's manual.

Log all results and perform any corrective action.Archive syslog messages Store syslog files to your network archive or backup sector

controller log files if you are not using a syslog server.Weekly Maintenance

Run the syslog analysis scripts. Check for GPS, synchronization and IF issues, characterize rates of de-registrations

RedMAX Administration and Maintenance GuideRequired EquipmentYou should have the following items on site to perform both routine maintenance and corrective maintenance. RF AnalyzerA portable, good quality hand held spectrum analyzer is best suited to

this task. Anritsu Model MS2721A or Rohde & Schwarz model FSH6 are both suitable devices. The spectrum analyzer should include a 12V power supply and ~25dB LNA cable. Refer to the Guide to Field Spectral Analysis for details on the requirements and use of a spectrum analyzer

iPerf Network Packet Sniffing software tooliPerf is a free, open source utility used for testing TCP and UDP performance. It's available for download from: http://dast.nlanr.net/Projects/Iperf/.

Torque wrench with gauge Weatherproofing materials including:

Scotch 130C Linerless Rubber Splicing Tape Scotch 2210 Vinyl Mastic RollsThese are self-fusing, rubber-based insulating

compounds laminated to a flexible, all-weather grade vinyl (PVC) backing. These tape rolls are designed to insulate, moisture-seal connections up to 600 volts, and have excellent resistance to abrasion, moisture, alkalies, acid, copper corrosion and varying weather conditions (including sunlight).

Scotch Vinyl Electrical TapeSuper 88 is a premium grade, 8.5-mil thick, all-weather vinyl insulating tape. It is designed to perform continuously in ambient temperatures up to 105C (220F). The tape is conformable for cold weather

Check Spares Check the quantity, model number and version number of spare parts. Ensure that the spare parts are stored in accordance with the manufacturer's instructions with regard to temperature, humidity and anti-static requirements.

Backup Sector Controller configuration

Backup the running configuration file to an FTP server. Refer to the User guide for detailed information.

Log the date on which the backup was performed. Also record the software version number. This will make it easier to identify the required backup file when it is required to restore the device's configuration.

Annual Maintenance

Inspect RF system Review wireless configuration and signal values. Log all of your results and store it with your maintenance

records.Reapply weather proofing on outdoor connections.

Log all dates and replace components/seals. Log all of your results and store it with your maintenance records.

Table 2-1 RedMAX Maintenance Schedule (continued)

Daily Maintenance Description/Required Tasks2-2Redline Communications Inc. Confidential and Proprietary

Chapter 2 Overviewapplications down to -18C (0F). It has excellent resistance to abrasion, moisture, alkalies, acids, corrosion and varying weather conditions (including ultraviolet exposure).

Weatherproofing putty. Refer to your local supplier for detailed specifications. The type of material to be used will depend on your expected weather conditions.

Establishing a Spares ProgramIn order to minimize possible network downtime, you should stock a few maintenance-related items with your base station equipment. Ensure that the spare parts are stored in accordance with the manufacturer's instructions with regard to temperature, humidity and anti-static requirements

.

Refer the RedMAX Base Station Installation Guidelines for details of the required parts, for part numbers and ordering information.

Reference InformationYou will also need to gather the following network-specific information: Device Configuration including both hardware and software configuration of each

RedMAX device, as well as any other devices that are either physically or logically connected to your RedMAX devices. Many network devices make provisions for saving their running configuration to text format and then storing this file on an FTP server. If that is not an option, you will need to collect and store screen captures of the necessary configuration screens. Make sure to include the currently active software versions.

Network diagram: That may consist of multiple drawings. Your network diagram must show the following information. The physical connections between network devices;

Table 2-2 AN100U/UX Spare Parts

Part Description

IF cable This cable connects the indoor unit (IDU) to the radio.RF Cable This cable connects the radio to the antenna.Fuses These fuses are located in the IDU to protect the unit from power surges.SUO/SUI Subscriber unit, with know characteristics can be used when troubleshooting

and can be used as a replacement for customer devices, as required.Power Cord This cord is used to connect the IDU to power outletHardware You should keep the following items on hand: nuts, bolts, washers and lock

washers for the outdoor unit) to replace damaged or corroded parts.2-3 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance Guide The manufacturer and the model number of each device; LAN and WAN protocols used for all types of network communication. Logical connections. These may be listed on a separate diagram. The network interface of each manageable interface. User data and management paths must be clearly defined with appropriate VLAN

IDs and IP subnets, if applicable.

Note It is crucial that your RedMAX system be operating on a supported software pair.

Refer to the RedMAX AN100U/UX Base Station User Guide for list of supported software which specifies which subscriber unit software is supported with each AN100U/UX software version. You must ensure that you are using compatible software versions.

Monitoring Your SystemThe ability to access your sector controllers and actively monitor various items is imperative in order to keep the system operational at a carrier class level.Ideally, you can install a client VPN system on the computer that you are using to monitor your sector controllers. This allows you to both monitor and configure your system remotely. Once the VPN is installed, you should be able to log into any of the sector controllers using either the CLI or the Web interface.

Connecting to the Sector Controller Web ClientThe following table lists the Web browsers supported in this release. This release supports English only.

.

You will need to connect to the web interface of the sector controller to perform most maintenance or troubleshooting procedures. You must have connectivity from your computer to the sector controller or be connected directly to the sector controller before you can use this procedure.

Step 1 Open one of the supported browsers. Step 2 Enter the following command:

http:// 192.168.101.3

Table 2-3 Supported Web Browsers

Web Browser Supported Versions

Internet Explorer 7.xMozilla Firefox 2.0.0.5, 3.0.5 and above2-4Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewIf you have configured another local or network IP address you must use that address.Step 3 When the command prompt screen appears, login using the following values:

Username: adminPassword: admin

You are now connected to the sector controller and can display and modify its current configuration. Refer to the RedMAX AN100U/UX Base Station User Guide for details on using the sector controller Web client.

Connecting to the Sector Controller Command Line InterfaceThe sector controller also provides a command line interface, through which you can display and modify the devices current configuration. You require Telnet or a similar application to connect to this interface. You must have connectivity from your computer to the sector controller before you can use this procedure.

Step 1 Open the Windows Start Menu and select Run:Step 2 Enter the following command:

telnet 192.168.101.3If you have configured another local or network IP address you must use that address.

Step 3 When the command prompt screen appears, login using the following values:Username: adminPassword: admin

You are now connected to the sector controller CLI. Refer to the RedMAX AN100U/UX Base Station User Guide for detailed information on using the CLI.

Accessing the Debug ModeDebug mode is used for factory test and advanced troubleshooting. Logging in to the Web GUI or Telnet session using the debug user name and password provides access to advanced configuration controls. Debug mode should be used only under the explicit direction of Redline field service or their representatives. It is recommended to change the debug mode default password to restrict access to this feature.

Step 1 Open the Windows Start Menu and select Run:Step 2 Enter the following command:

telnet 192.168.101.3If you have configured another local or network IP address you must use that address.2-5 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideStep 3 When the command prompt screen appears, login using the following values:Username: debugPassword: debug

Connecting to the Subscriber Unit Command Line InterfaceThe subscriber unit provides a command line interface, through which you can display and modify the devices current configuration. You require Telnet or a similar application to connect to the subscriber unit. The IP address 192.168.101.2 is also available, but this address can be changed. The IP address, 192.168.101.1 is always available, regardless of build date or custom configuration.

Note The default IP address may differ depending on the firmware build date.

You must have connectivity from the sector controller to the subscriber unit before you can use this procedure.

Step 1 Open the Windows Start Menu and select Run: Start > Run

Step 2 Enter the following command:telnet 192.168.101.1If you have configured another local IP address you must use that address.

Step 3 When the command prompt screen appears, login using the following values:Username: adminPassword: admin

You are now connected to the CLI of the subscriber unit. Refer to the RedMAX Outdoor Wireless Access Subscriber Modem (SUO) User Guide for detailed information on using the CLI.

Monitoring System Event LogsSystem events for both the AN100U/UX and subscriber unit are captured in an event log. The event log for both devices can be accessed via their respective command line interfaces (CLI). Both devices order their event log chronologically with the most recent event first in the list. Each event is time stamped with either the system time, or a time of day obtained from a time server, if one has been configured in your system. 2-6Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewNeither device stores its event log in non-volatile memory, meaning that all information will be lost when the unit reboots. If you plan on rebooting or otherwise interrupting power to your device, make sure to capture the event logs before initiating the reboot.A number of Perl scripts are available to parse your syslog files and generate reports. See Appendix A, Event Log Scripts for details on running these scripts.

AN100U/UX Web Client

Step 1 Login to the Web client as outlined in Connecting to the Sector Controller Web Client on page 2-4.

Step 2 From the Main menu select Monitoring > Event Log.Step 3 Review the Event log, looking for any of the messages listed above. You can use the find

feature (Ctrl + F in most browsers).

AN100U/UX CLI

Step 1 Login to the CLI client as outlined in Connecting to the Subscriber Unit Command Line Interface on page 2-6.

Step 2 Enter the Show command and re-direct the output to a file for review:show event

Step 3 Since it is likely that the event log is longer than a single terminal window, and possibly longer than your client machine's buffer, you can optionally use the following command:show eventLog paged

This will display the event log one page at a time. Press any key or the display the next page.

Step 4 Right-click on the Telnet window and select Select All. Then copy and paste the content into another file for review. This option allows you to collect the event log data for further analysis, if you are not using a syslog server.

Step 5 Review the resulting file for any of the messages listed above.

Refer to the RedMAX AN100U/UX Base Station User Guide for detailed information on using the CLI.

SUO CLI

Step 1 Open a Telnet session to the IP address of the sector controller. The default address is 192.168.101.3. When the command prompt screen appears, login using the following values:Username: adminPassword: admin2-7 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideStep 2 Enter the Show command and re-direct the output to a file for review:show event

Step 3 Since it is likely that the event log is longer than a single terminal window, and possibly longer than your client machine's buffer, you can optionally use the following command:show eventLog paged

This will display the event log one page at a time. Press any key or the display the next page.

Step 4 Right-click on the Telnet window and select Select All. Then copy and paste the content into another file for review. This option allows you to collect the event log data for further analysis, if you are not using a syslog server.

Step 5 Review the resulting file for any of the messages listed above.

Refer to the RedMAX AN100U/UX Base Station User Guide for detailed information on using the CLI.

Monitoring Statistical Results ScreensBoth the AN100U/UX and the subscriber units provide various screens showing wireless, Ethernet, and service flow performance. You can find statistical information on the subscriber unit in the CLI Monitor screen (accessed by simply typing "monitor" from the root menu. The same menu is available via the AN100U/UX's CLI, but most of the AN100U/UX's crucial information is more easily accessed via the GUI using the SS Info and Status menus.

AN100U/UX Web Client


Step 2 From the Main menu select Monitoring > SSInfo.The Subscriber Information page is displayed. You can review this page to view statistical information on each of the connected subscriber units.

Step 3 From the Main menu select Monitoring > Status.The Wireless Status page is displayed. You can review this page to view statistical information on the wireless interface.

AN100U/UX CLI

Step 1 Login to the CLI as outlined in Connecting to the Sector Controller Command Line Interface on page 2-5.2-8Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewStep 2 Enter the monitor command:monitor

Step 3 You can now view a dynamically updated screen of statistics. Press any key to exit monitoring mode.

Step 4 Enter the interfaces command to monitor the wireless interface:interfaces wireless show

Step 5 Select and then copy and paste the output, in the Telnet window, to a file for review.Step 6 Enter Ctrl-Z to return to the root mode.

SUO CLI

Step 1 Login to the CLI as outlined in Connecting to the Subscriber Unit Command Line Interface on page 2-6.

Step 2 Enter the monitor command:monitor

Step 3 You can now view a dynamically updated screen of statistics. Press any key to exit monitoring mode.

Step 4 Enter the diagStatistics command to monitor the wireless interface:diagStatistics show

Step 5 Select and then copy and paste the output, in the Telnet window, to a file for review.Step 6 Enter Ctrl-Z to return to the root mode. You can now logout or keep the session for further

access.

Monitoring the System ParametersYou can monitor basic operation of the sector controller and its registered subscribers through the sector controller GUI or CLI. The baseline RSSI levels for each radio should be monitored in order to establish the performance level for each device. These levels should be recorded when the radios are installed and then regularly thereafter to see any potential trends. You can set threshold traps based on your performance guidelines or within an acceptable range of peak performance and that level is set as the trigger to create an alarm. The exact value of what constitutes an acceptable range is determined by your network performance requirements. For example, a range of 15% allows the radio to continue to perform, but alerts you to a potential problem well before the radio link goes down. When an SNMP trap or TCA has been triggered you can specify what type of alarm will be generated and using applications, such as RMS, you can also perform various actions such as emailing the system administrator or rebooting support equipment. 2-9 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideVerifying fixed WiMAX performance requires that you monitor and record many different parameters including: Channel Power (RSSI)measures the average time domain power within the selected

bandwidth and is expressed in dBm. Occupied Bandwidth (BW)calculated as the bandwidth containing 99% of the

transmitted power in the given RF span. Carrier Frequencythe measured frequency of the received signal. It is equal to the

specified frequency plus the Frequency Error described above. Base Station IDEach transmitter has a unique ID. BTS Master displays it as Base

Station ID by decoding the Frame Control Header (FCH) part of the downlink frame. Adjacent Subcarrier Flatness Peakthe absolute difference between adjacent

subcarriers.

Using the Ping UtilityThe most basic tool available for verifying network connectivity is the ping utility. There are a few parameters that are frequently used during RedMAX maintenance and troubleshooting. The following information applies to ping as implemented on a Windows platform. Details may differ slightly for other operating systems.

Step 1 Open a console window on the PC behind the subscriber unit: Start > Programs > Accessories > Command Prompt

Step 2 In the console window enter the following co mm an dr: ping

where is the address of the destination device Step 3 Review the results. The output should resemble the following:

Example 2-1 ping Output

Reply from 192.168.101.3: bytes=32 time=3ms TTL=30Reply from 192.168.101.3: bytes=32 time=3ms TTL=30Reply from 192.168.101.3: bytes=32 time=3ms TTL=30Reply from 192.168.101.3: bytes=32 time=3ms TTL=30

Ping statistics for 192.168.101.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in subscriber unit -seconds: Minimum = 3ms, Maximum = 3ms, Average = 3ms2-10Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewBy default, four packets are sent, at approximately 1-second intervals. The timeout for each request depends on the version of Windows. For Windows XP the timeout is 4 seconds. The default packet size is 32 bytes. This is the size of the data field in the ICMP packet, but it is not the size of the entire packet. When you add 8 bytes of ICMP overhead, 20 bytes of IP overhead and 18 bytes of Ethernet overhead, we get an Ethernet frame size (for a default ping) which is actually 78 bytes. If you want to test how ping works with the maximum Ethernet frame size, use the following command:ping 192.168.101.3 -l 1472

If the specified size is larger than 1472 bytes, your computer will send more than one IP packet. It will send fragments that will be reassembled at the destination. If the transfer is completed successfully, then a packet (or packets) of the same size will be sent back.The maximum value that you can enter for the ping size is 65500. With 8 bytes of ICMP header, this makes the 65508 bytes of IP payload. IP will fragment this into 45 packets. So for the "maximum ping" to succeed, 45 Ethernet packets of maximum size (actually 44 packets will be 1518 Bytes, the last one will be 426 Bytes long) have to be successfully transmitted, and then in response, an additional 45 packets have to be successfully received.Although ping sends packets at approximately 1-second intervals, fragmentation is under control of the TCP/IP stack, and all of the 45 packets will be sent at the line rate of the network card, which in some cases could cause ping to drop packets simply because buffers across the network are full.

Using the Iperf UtilityIperf is a free, open source utility that can be used for testing TCP and UDP performance. It is available for download at http://dast.nlanr.net/Projects/Iperf/. In order to perform an iperf test, you need two computer's, one at either end of the RedMAX link. The first computer acts as the client, and the other acts as the server. The determination of which computer operates in which mode, and how they are configured, depends on the nature of the test to be performed.Iperf is a CLI-based tool. Arguments are supplied during execution determine the nature of the test to be performed. The following table lists the most commonly used arguments:

Where: -l indicates the buffer size. In this example 1472 bytes of data are sent. 1472 bytes of ping "data" maps to 1518 bytes of an Ethernet packet.2-11 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideThe first step is to decide on your test scenario. For example, if you want to measure overall sector capacity, you should provision a service flow with a maximum rate well above what you expect to achieve. If you plan to test the throughput of a given service package, you should ensure that your subscriber unit is provisioned using the service flow in question. Either way, once you have completed provisioning your subscriber unit, you should first perform a basic connectivity test, using ping as outlined in Using the Ping Utility on page 2-10.Once you have verified connectivity between the devices, you can proceed with one of the iperf tests as described below. Ensure that the server is started first, and then the test is initiated from the client. The server does not have to be restarted between tests unless the nature of the test is to be modified. The server and client devices will change depending on the test that you running. Details of which devices should be configured as the client and as the server are provided for each test.Depending on the system characteristic to be tested, you will use on of the following tests:

Downlink TCP ThroughputFor this test, the computer connected to the subscriber unit is configured as the server.

Step 1 Open a console window on the computer behind the subscriber unit:

Table 2-4 iPerf Options

Flag Description

i This argument specifies the interval at which iperf will output an update of the current measured throughput. Without this argument, iperf will only display a summary at the end of the test.

t This argument defines the duration of the test. It is measured in seconds. Generally, 30 seconds is recommended as a minimum.

u This argument specifies UDP traffic. Without this argument, iperf will use TCPb This argument is used with the -u argument. It specifies the rate at which to pass UDP

packets. Specifying the argument automatically implies the -u argument.d This argument specifies that iperf should perform a bidirectional test; throughput

performance is measured in both the uplink and downlink simultaneously. It is not recommended that this argument be used with TCP tests.

P This argument is used to specify the number of parallel streams to be used for a given test. If you are trying to simulate multiple customers, or multiple network applications in use simultaneously, you can specify how many with this argument.

w This is used to specify the TCP window size to be used by the TCP stack. The default Windows window size is 8k. You will need to need to specify 64k TCP window for TCP tests on both client and server by adding the "-w 64k" argumentThis argument is not relevant for UDP tests.

s This specifies that iperf will run as a server.c This specifies that iperf will run as a client.2-12Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewStart > Programs > Accessories > Command PromptStep 2 In the console window enter the command to start the server:

iperf -s

Step 3 Open a console window on the second computer connected to the sector controller: Start > Programs > Accessories > Command Prompt

Step 4 In the console window enter the command to start the client and run the test:iperf -c -i 5 -t 60 -w 64k

Uplink TCP ThroughputFor this test, the computer connected to the subscriber unit is configured as the client.

Step 1 Open a console window on the computer behind the subscriber unit: Start > Programs > Accessories > Command Prompt

Step 2 In the console window enter the command to start the server: iperf -s


Step 4 In the console window enter the command to start the client and run the test:iperf -c -i 5 -t 60 -w 64k

Bi-directional UDP ThroughputFor this test, it does not matter which computer is configured as the server.

Step 1 Open a console window on the computer behind the subscriber unit: Start > Programs > Accessories > Command Prompt

Step 2 In the console window enter the command to start the server: iperf -s -u


Step 4 In the console window enter the command to start the client and run the test:iperf -c -u -b -i -t 60 -d2-13 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideIf you are checking for packet loss, ensure that the rate you specify is low enough so as not to cause packet loss simply by overloading your service flow.In general you do not need to perform bi-directional TCP throughput tests as this type of test does not accurately replicate any typical usage scenarios. You may find that the net bi-directional throughput of the system is lower than the results of the separate uni-directional tests, where performed. This is due to the fact that TCP acknowledgements for the downlink flow will be caught in the same data queue as data packets for the uplink flow, and vice versa.

Network SniffersIn order to ensure that your system is performing as expected or for troubleshooting purposes you may need to see exactly what packets are sent from a certain device; what packets are received, etc. Software (and hardware) tools that allow you to do this are called network sniffers and there are a few available on the market.Ethereal is a popular, open-source application that contains almost all of the features of the more expensive tools. Some of the better-known, commercial applications are Network General's Sniffer and Wild Packet's Etherpeek. The usage of each of these applications currently is beyond the scope of this document.

Using the rfMonitor ApplicationThe rfMonitor application is provided by the Redline Technical Services department and can be used for monitoring your wireless performance over time. It monitors the RSSI and CINR values at set intervals (500ms ~ 10s) and graphs the results. The results can be saved as either an image, or as a .csv file for use in any spreadsheet program. The latest version can be found on the Redline Partner website, under Support Tools. A User Guide is also provided on the partner site.

Planning/Scheduling Equipment MaintenanceMost RedMAX equipment maintenance, such as upgrading software, replacing cables or replacing antennas, will require you to shut down the sector controller or subscriber unit impacting service. Before performing any maintenance you should first perform the visual inspection outlined in Performing a Visual Inspection of the IDU on page 3-1 and determine the scope of the required work.

Where: represents the rate at which you wish to send UDP traffic. If you are testing system capacity then specify a rate higher than you expect to transfer, and monitor the achieved rate. 2-14Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewOnce you have determined the work that needs to be done, you will need to schedule a maintenance window. When setting the date and duration for this maintenance window you need to consider a number of things:1. What replacement parts are required? Are these parts on hand or do they need to be

ordered? If parts need to be ordered, what is the delivery time?2. If work must be done on the outdoor equipment, do you need to book appropriate

personnel?3. Do you have all of the required test equipment? See Required Equipment on

page 2-2.

Personnel Required for Maintenance Due to the nature of wireless communications, you will need specialized personnel for both installation and maintenance of your network.Your local maintenance team should also be available for dispatch when problems do occur that cannot be addressed remotely. If any RedMAX equipment is installed on a tower or at any location in which accessibility is an issue you will require an experienced tower climber or rigger when installing or replacing outdoor components. Contact your local Redline representative for information on local companies.The local support personnel must be capable of connecting to the equipment via serial or Ethernet connection in order to resolve local device issues. They will need administrative login accounts. Additionally they should have access to the RedMAX documentation provided with the equipment. They should also have access to the logged records for each sector controller so that they can establish baseline performance.They will also need all necessary information to gain access to the site during off hours as well as have access to tower riggers in case of a lightning strike or antenna failure.All maintenance personnel should follow the RedMAX installation and operation specifications strictly, and avoid any operation on the equipment beyond the required maintenance, e.g., opening the chassis, arbitrarily plugging/unplugging, resetting, starting and switching over the equipment, or changing the configuration. Maintenance personnel must wear an anti-static wrist strap when working with any hardware system. You must store any damaged parts and the spare parts in anti-static bags, which must be labeled correctly and stored properly. This is especially important if any parts are being returned for warranty replacement.

Establishing and Recording the Baseline ConfigurationOnce your system is installed and configured correctly, you need to record a number of values to define the baseline operating guidelines. You will then use these measurements to verify that your system is functioning as expected. You will also use these values after performing any maintenance to ensure your system has been returned to its optimum performance level.2-15 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideStep 1 Login to the Web client as outlined in Connecting to the Sector Controller Web Client on page 2-4.

Step 2 From the Main menu, select Monitoring > Status.Step 3 Record the following values or perform a screen capture of the selected screen and save

the file in a maintenance directory. Rename the file accordingly.

Step 4 From the Main menu, select Interface Configuration > Wireless Interface.Step 5 Record the following values or perform a screen capture of the selected screen and save

the file in a maintenance directory. Rename the file accordingly.

Table 2-5 Wireless Status Page

Parameter Value Parameter Value

CINR [dB] 21.3 RF Tx Power [dBm] 36Traffic Downlink [kbps] 0 Traffic Uplink [kbps]BW Margin Downlink [kbps] 4601 BW Margin Uplink [kbps] 4752CRC Errors 0 Registered SS's 1Air Interface Status enabled SC Synchro Status No SynchroIDU Temperature [Celsius] 39 ODU Temperature [Celsius] 36Power Supply Status A-On Fans Status mainActive DL Service Flows 1 Active UL Service Flows 1DL SMC Rate [kbps] 0 UL SMC Rate [kbps] 0DL Bandwidth Usage [%] 0 UL Bandwidth Usage [%] 0Reference RSS [dBm] -75 Noise Level [dBm] -102.7

Table 2-6 Interface Status Page

Parameter Value Parameter Value

Speed 28.8 Mbps Operational Status UpLast Change 00:00:25 Ingress

In Octets 3702085 In Unicast Pkts 26429In Broadcast Pkts 0 In Multicast Pkts 0In Discards 0 In Errors 0Egress

Out Octets 10473071 Out Unicast Pkts 24496Out Broadcast Pkts 9300846 Out Multicast Pkts 0Out Discards 0 Out Errors 02-16Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewMaintenance Record KeepingYou need to retain all of this information, as a hardcopy and optionally in electronic format. Printed versions of all installation settings and measurements as well as regular maintenance logs should be printed and maintained in a binder or file for quick and easy reference. This is usually a requirement of your operational license.All installation and maintenance logs should be dated clearly and contain the name, serial number and MAC address of the device from which they were obtained.

Establishing Secure, Remote Access

LANIf you have configured a LAN that includes your sector controllers, you need to have the correct routing in place, you can then log into the AN100U/UX remotely to monitor its status and change its configuration.

VPN ClientIdeally, you can install a client VPN system on the computer that you are using to monitor your sector controllers. The VPN client allows you to both monitor and configure your system remotely.Refer to the instructions provided with your VPN client software for details on installing and configuring the software for use. Once the VPN is installed, you should be able to log into any of the sector controllers using either the CLI or the Web interface.

Table 2-7 Wireless Interface Status Page

Parameters Values

RF DL Channel (KHz) 3496000RF Channel Separation (KHz) 0Tx Output Power (dBm) 5SS Tx Power Control Enable YesReference RSS (dBm) -69Auto Rx Gain Enable Yes2-17 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideRemote Management of an SUOIn order to remotely access an SUO you need to assign an IP address to the SUO's "air interface". This address can be assigned through a DHCP server. You can also assign a static SMC IP address.

Note Statically-assigned IP addresses are supported in RedMAX v2.1 and higher.

Each SUO can have up to three IP addresses: The default IP address that is assigned at the factory and cannot be deleted or

modified: 192.168.101.1 The local IP address that can be set. This is the IP address that should be used to

connect the SUO directly to a local computer. The remote IP address for the air interface that must be assigned by a DHCP server.

Note All three IP addresses should be on different subnets.

You must ensure that Management Support has been enabled on each SUO.

Configuring a DHCP ServerYou can use a DHCP server to assign IP addresses to registering subscriber units. You do not need to set up service flows for DHCP traffic. The sector controller acts as a DHCP relay.When assigning IP addresses with a DHCP server, the basic DHCP lease must include your default gateway, subnet mask, and an IP offer. Time of Day (ToD) is also highly recommended (option 4).

Step 1 Install and configure the DHCP server as outlined in the documentation provided with the application. Redline recommends commercially-available products, such as Cisco CNR or Nominum Dynamic Configuration Server.

Step 2 Specify the following parameters when configuring your DHCP server: :

Table 2-8 DHCP Server Configuration Parameters

Parameter Description

Name Specify a name and/or description for a new policy. i.e. RedMAX_DHCP_One

IP Address Range Specify the addresses to be assigned as a device requests them. You will need to specify a start and end for the range. i.e. Start=172.29.228.21; End =172.29.228.41. You must ensure that your sector controller(s) and the computer are not within this range.2-18Redline Communications Inc. Confidential and Proprietary

Chapter 2 OverviewNote The ToD server required here is different from the SNTP that is required for the sector controller event log. These devices operate using different protocols and cannot be used interchangeably.

You will need to update the following parameters on each sector controller:


Step 2 From the Main menu select Interface Configuration > Management Interface.Step 3 Enable the option, Obtain IP Parameters from DHCP Server, if you want the sector

controller to obtain its IP address from the DHCP server.Step 4 Select one of the following options for the subscriber units:

SS-s should use the same DHCP Server as SCSelect this option to have the sector controller forward all subscriber DHCP requests to the same DHCP server, used by the sector controller to obtain its IP address. This option is valid only if the field Obtain IP Parameters from DHCP Server is selected.

SS-s should use the following DHCP ServerSelect this option to specify the DHCP server to be used by subscriber units. You must also specify the IP address of the DHCP server. The sector controller will forward all subscriber DHCP requests to this IP address.

Step 5 Click Save to save the required changes to the sector controller configuration.Step 6 Reboot the sector controller to activate these changes. See Rebooting the AN100U/UX

on page 3-2

Subnet Mask i.e. 255.255.255.0IP Address of the Relay Agent

You will need to specify the sector controller as the Relay Agent. i.e. Start=172.29.228.11

Time Offset This value is set in seconds, so for example, to obtain a 5-hour time offset you have to set this value to 18000s. 18000 seconds = 5 hours for the Eastern Time difference from GMT

Gateway IP Address If you are using an ASN gateway, specify the IP address of the host machine.

Time of Day (ToD) Server IP Address

Specify the IP address if you are using a Time of Day (ToD) Server (option 4). It is important to understand that the IP address for ToD server must be a valid IP address with a functional ToD server. The ToD server must respond to a valid time request.

Syslog Server IP address

Specify the IP address if you are using a syslog server.

Table 2-8 DHCP Server Configuration Parameters (continued)

Parameter Description2-19 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideWhen a subscriber unit registers with the sector controller, the IP address will now be assigned by the DHCP server.

Step 1 You can verify the subscribers IP address from the main menu by selecting Monitoring > SS Info.

Step 2 You can also verify the IP address by connecting directly to the subscriber unit using Telnet. The SUO IP address is displayed on the SS Info page. See Connecting to the Subscriber Unit Command Line Interface on page 2-6.

Configuring a Time of Day ServerTime servers are stand-alone devices that obtain and distribute the correct time to all devices and host machine in your network. It is important to note that the AN100U/UX supports only SNTP (RFC-2030), while the subscriber units support only ToD (RFC-868). Network Time Protocol (NTP) is a TCP/IP protocol used to synchronize the real-time clock in computers, network devices and other electronic equipment that is time sensitive. The Coordinated Universal Time (UTC) can be obtained over the Internet, which contains numerous primary and secondary time servers, or it can be acquired from stand-alone devices that receive atomic clock signals from the GPS system. ToD (RFC-868) provides timestamps for logged events. This is required for troubleshooting. Network elements periodically request the time of day from the time server that is specified in their DHCP response. Both Windows and Solaris provide ToD services. Refer to the documentation provided with your OS for details on configuring ToD services.2-20Redline Communications Inc. Confidential and Proprietary

Re

components of your OSS. Refer to the RedMAX Base Station Installation Guidelines for details.

Step 6 Ensure all cables are secured and do not pose a triStep 7 Ensure cables are not pinched or bound too tightly.3-1dline Communications Inc. Confidential and Proprietary

pping hazard.3Indoor Equipment Maintenance

For maintenance purposes it is easier to divide maintenance work between indoor and outdoor maintenance. In some case the personnel required to perform maintenance of the indoor equipment will be different than those required for the outdoor work.Routine maintenance of the indoor equipment will be covered, in this chapter.

Performing a Visual Inspection of the IDUVisually inspect data connections, power cables and grounding connections for indoor equipment on a monthly basis. Ensure all connections are secure and look for any signs of rust or other types of corrosion.

Step 1 Inspect all connections on the AN100U/UX IDU. All connections must be secure and cables in good repair. Cables and connectors should be clearly labelled to facilitate troubleshooting.

Step 2 Inspect all connections to the RPS, if installed. The RPS must be powered down before disconnecting or re-connecting any devices.

Note The AN100UX redundant power supply is a DC-type supply. The RPS power must be connected using positive polarity, i.e. the +48 VDC RPS output must be connected to positive input on the AN100UX. Refer to the RedMAX Base Station Installation Guidelines for detailed instructions.

Step 3 Inspect all connections for local synchronization, if configured. Refer to the RedMAX Base Station Installation Guidelines for details.

Step 4 Inspect all connections to the GPS, if installed. Refer to the Redline GPS Clock User Manual and to the RedMAX Base Station Installation Guidelines for details.

Step 5 Inspect all connections to the computer, syslog server and any other computers that are

RedMAX Administration and Maintenance GuideStep 8 Ensure RF cables are not located next to high voltage cables. Ensure all cables are clearly labelled.

Step 9 Log all of your results and store the inspection results with your maintenance records.

Rebooting the DevicesMost changes that you make to the sector controller configuration require that you save the changes and then reboot the device in order to activate your changes. Changes made to the subscriber unit configuration may also require that you save the changes and then reboot the device in order to activate your changes.This procedure is service impacting and should only be performed during a scheduled maintenance window. However, in general the interruption is only a few minutes and could be done during a period of low network activity.

Rebooting the AN100U/UXStep 1 Log into the sector controller and scroll to the bottom of the main menu.Step 2 Click on the Reboot button at the bottom of the main menu.

The device will terminate all of its connections and reboot itself. This will typically take 1-2 minutes. Any configuration changes that were made will now be active.

Step 3 Verify your changes and ensure the device is operating as expected.Backing up, restoring and upgrading the sector controller software is covered in the RedMAX AN100U/UX Base Station User Guide.

Rebooting the Subscriber UnitStep 1 Log into the sector controller and click SS Info in the menu.Step 2 Click on the Reset button at the top of the page.

The device will terminate all of its connections and reboot itself. This will typically take 1-2 minutes. Any configuration changes that were made will now be active.

Step 3 Verify your changes and ensure the device is operating as expected.

Redundant Power SupplyThe redundant power supply (RPS) is a stand-alone power supply that can be used as a backup power supply for deployments of up to six AN100UX base stations. The RPS can support one AN100UX unit with a failed power supply. It is not intended to be used as an uninterruptable power supply (UPS). 3-2Redline Communications Inc. Confidential and Proprietary

Chapter 3 Indoor Equipment MaintenanceNote The RPS can only be used for the AN100UX.

The RPS scans and sets the power outputs at power-on and following a detected failure of a connected AN100UX. < During this time you need to obtain a replacement device and configure it using the most recent backup from the disabled device and then replace it within the network.

Replacing the Indoor Unit of the AN100U/UX

Note This procedure is service impacting and should only be performed during a scheduled maintenance window.

Step 1 If possible, perform a configuration backup from the disabled device. Refer to the RedMAX AN100U/UX Base Station User Guide for detailed instructions.

Step 2 Power off the RPS and the disabled device.Step 3 Unplug the primary power cable from the supply and then from the disabled device.Step 4 Remove the device from the mounting rack, if applicable.Step 5 Install the replacement device in the rack and connect the power cable from the RPS.Step 6 Connect the primary power cable and then connect the other end to the power supply.Step 7 If the device does not power up automatically, then turn it on.Step 8 Verify the successful restart and correct operation. Review the event log to ensure the

correct radio type is listed. Step 9 Verify that the software version of the new device is the same or higher than the disabled

device.Step 10 Restore the configuration of the disabled device. Refer to the RedMAX AN100U/UX Base

Station User Guide for detailed instructions.Step 11 Log into the Web client and navigate to Monitoring > Status. Review the Status page to

verify that the air interface is enabled and to ensure the sector controller is operating normally.

Step 12 Navigate to Monitoring > SS Info and verify any subscriber units are registered as expected.

Step 13 Verify the wireless interface configuration: Interface Configuration > Wireless Interface.The subscriber units should re-connected as soon as the sector controller is powered up. You can verify the other operating parameters as required. 3-3 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideRPS MaintenanceIn terms of required maintenance, you only need to verify the connections to the RPS from each of the sector controllers. After verifying the connections, you should test each sector controller in turn, to ensure that the RPS will cut in as required in the case of a failed power supply.

Note This work should be done in a maintenance window in case you encounter any issues and a sector controller is powered down.

Step 1 Connect each sector controller to the RPS. Detailed instructions, for connecting each sector controller to the RPS, are provided in the RedMAX Base Station Installation Guidelines.

Step 2 Disconnect the first sector controller from its primary power source. The RPS scans the devices and when a power outage is detected, sets and delivers the required power to the device.

Step 3 Verify that the sector controller continues to operate as outlined in Establishing and Recording the Baseline Configuration on page 2-15.

Step 4 Re-connect the primary power source for the sector controller and again verify that the device continues to operate as outlined in Establishing and Recording the Baseline Configuration on page 2-15.

Step 5 Repeat this for each sector controller that is connected to the RPS.Step 6 Record all of your results and file the written report with your other maintenance logs.

Uplink Power ControlAn important factor in overall network performance is the uplink power control of a RedMAX AN100U/UX. This feature allows the sector controller to automatically adjust the transmit power level for all registered subscriber units in its sector. This is done by enabling, the SS TX Power Control Enable option on the sector controller and specifying an associated Reference RSS value. When this option is enabled, the sector controller continually monitors the registered subscriber units and adjusts their transmission power to maintain optimum levels according to the preset reference RSS. This feature allows the overall system to achieve a determined noise level for the uplink whenever the network is fully loaded.The Reference RSS can be set between -40 and -95dBm. For optimum performance this parameter should be carefully configured dependant on the following factors that are initially determined during the design of the network and adjusted after installation, to satisfy practical network requirements for each sector controller. The exact Reference RSS value depends on the following factors:3-4Redline Communications Inc. Confidential and Proprietary

Chapter 3 Indoor Equipment Maintenance Expected minimum modulation scheme offered over the uplink (64QAM, 16QAM, QPSK etc.).

RedMAX receive sensitivities per modulation scheme and channel size. Designed cell radius. Expected fading conditions within the cell. The expected noise rise from other cells when the network is fully loaded with the

expected traffic. Path condition for the wireless link between the sector controller and the subscriber

unit (e.g., LOS, OLOS, NLOS). Frequency reuse factor in the network or distance to the closest cells where the

frequency is reused.As an example, for a system with 3.5 MHz channel size and offering 64QAM, 3/4 in the uplink, ideally the RSSI at the sector controller should be no less than -77 dBm, under no external noise conditions and assuming a fading of 5 dBm, and expected noise rise of 2 dBm, the ideal requested RSSI should be:

-77dBm + 5 dBm + 2 dBm = -70 dBm.For the same case, but offering 16 QAM, , with receive sensitivity at -89 dBm under no external noise conditions and again assuming a fading of 5 dBm, and expected noise rise of 2 dBm, the ideal requested RSSI should be:

-89 dBm+ 5 dBm + 2 dBm = -82 dBm.In general, this parameter should be initially defined as part of the system design recommendations. Incorrect configuration of the "Reference RSS" parameter may result in less-than-optimum uplink performance or higher inter-system interference.The higher the setting for Reference RSS, the higher the power levels that all of the subscriber units in the sector will need to transmit and you may also see higher noise rise in the neighboring cells. For this reason a reasonable Reference RSS according to the frequency re-use factors and noise floor level should be selected, in order to satisfy the expected service levels in the sectors while avoiding unnecessary power transmitted from the subscriber units in the sector, and hence lowering the inter-system interference.

Step 1 Based on your channel size and modulation, determine the reference RSS value for each sector controller.

Step 2 Record all of your results and file the written report with your other maintenance logs.

Sector Controller Synchronization with the GPS ClockSector controller synchronization must be used to coordinate RF transmissions when operating two or more co-located sector controllers in order to minimize inter-sector RF interference.3-5 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideLocal Synchronization versus GPS SynchronizationEach RedMAX sector controller has synchronization ports to send and receive clock synchronization pulses. When using the sector controllers internal synchronization feature, one sector controller is designated as the master and generates the clocking pulses to synchronize the operation of up to five slave sector controllers, thus providing full 360-degree coverage. All slave sector controllers monitor these clocking pulses and synchronize their transmission and receive periods.If your co-located sector controllers are at an isolated location, at which there are no adjacent cells belonging to the same network, then you can use local synchronization and a GPS clock is not required. Refer to the RedMAX Base Station Installation Guidelines for details of installation and initial configuration of local synchronization.If your network consists of geographically co-located cells, then an external GPS clock is required at each site. As with local synchronization, one sector controller is designated as the master. The master now receives the GPS clocking pulses and then uses this to synchronize the operation of up to five slave sector controllers. Refer to the RedMAX Base Station Installation Guidelines and Redline RedMAX GPS Clock User Manual for details of installation and initial configuration of GPS synchronization.

Verifying Network SynchronizationUse the Web interface or the CLI to view the event log in order to confirm the correct operation of each sector controller. See Monitoring System Event Logs on page 2-6.Additionally, Appendix B, AN100U/UX Event Log Messages lists messages that will appear in the event log. Messages specific to both local and GPS synchronization are listed in Synchronization Messages (See also Appendix D, Synchronization Event Log Messages on page B-15.

Changing from Local to GPS SynchronizationThe following procedure is applicable to sites consisting of two or more sector controllers that are already operating with local synchronization. Please refer to the RedMAX GPS Clock User Manual for detailed information on correct installation and cabling of the required hardware.

Note This procedure is service impacting and should only be performed during a scheduled maintenance window.

To minimize the service impact and ensure successful switch over from local to GPS synchronization, you must follow the procedure in the exact order listed below.3-6Redline Communications Inc. Confidential and Proprietary

Chapter 3 Indoor Equipment MaintenanceSetting the Required Wireless Interface ParametersThe following wireless interface parameters affect transmitter timing and must be set to the same value on each of the sector controllers in all geographically, co-located cells: Frame Duration (ms) Frame Downlink ratio (%) Cell Range (km)

Determine the correct settings and ensure all of the sector controllers are configured correctly before performing any of the following steps.


Step 2 Click Wireless Interface in the menu to view the MAC parameters.Step 3 Update the values of Frame Duration (ms), Downlink ratio (%) and Cell Range (km).Step 4 Click the Save button to save these changes.Step 5 Reboot the sector controller as outlined in Rebooting the Devices on page 3-2.

This can also be done from RMS by modifying the device configuration for the impacted network from the Topology tree. You can also create and apply device configuration templates. Refer to the Redline Management Suite User Guide for details.

Configuring the Master Sector Controller for GPS SynchronizationIf a GPS signal is detected at startup, the Master with GPS immediately synchronizes its clock to this signal and then enables the Master capability and sends synchronization pulses to all connected Slaves. If the GPS signal is not detected at startup, the Master capability is not enabled and the sector controller does not send synchronization pulses. If the GPS signal is detected while the Master with GPS is operating asynchronously (startup completed but master function not enabled), the Master with GPS transitions its clock to match the external GPS signal and then enables the master capability and sends synchronization pulses to slaves.Identify the sector controller that is currently the local master clocking source. It should be clearly labeled in the rack. Change the master sector controller Synchronization Mode from Master to Master with GPS Sync.

Step 1 Log into the sector controller that is currently the local master clocking source, as outlined in Connecting to the Sector Controller Web Client on page 2-4.

Step 2 Click Wireless Interface in the menu to view the MAC parameters.Step 3 Set the Synchronization Mode to Master with GPS.Step 4 Click the Save button to save these changesStep 5 Reboot the sector controller as outlined in Rebooting the Devices on page 3-2.3-7 Redline Communications Inc. Confidential and Proprietary

RedMAX Administration and Maintenance GuideVerifying GPS Receiver OperationStep 1 Verify that the GPS receiver, GPS antenna, the cabling between the receiver and antenna,

and GPS are configured correctly. Refer to the RedMAX GPS Clock User Manual for detailed information.

Step 2 Lighting protection must be properly installed and operating as outlined in the RedMAX Base Station Installation Guidelines and the RedMAX GPS Clock User Manual.

Step 3 Verify that all sector controllers at the site are wired correctly for GPS time synchronization. Refer to the RedMAX GPS Clock User Manual for detailed information.

Step 4 Turn on the GPS receiver, wait for approximately 15-30 minutes to ensure that a valid satellite signal has been received and that time synchronization, with the satellite, has been achieved.

Step 5 Verify that the GPS clock is generating a clocking pulse on its 1 PPS port. The event log for the sector controller configured as the Master with GPS should log an event message "GPS Detected". Review the event log as outlined in Monitoring System Event Logs on page 2-6.If any of these steps cannot be verified DO NOT PROCEED any further, and contact [email protected] for assistance.

Step 6 On the Status page of the master sector controller verify that the device is the Active Master. This confirms that the master sector controller is fully operational and is providing a clocking pulse at its Sync Out port.

Configuring the Backup Master Sector ControllerIf a Master is detected at startup, the Backup Master immediately synchronizes its clock to the Master synchronization pulses and enables the backup capability. If at startup, the Backup Master does not detect an active master, but a GPS clock signal is detected, the Backup Master immediately synchronizes its clock to the GPS signal and enables the backup capability.Identify the Backup Master sector controller, if configured. The device should be clearly labeled.


Step 2 Navigate to Interface > Wireless Interface to verify the values of Frame Duration (ms), Downlink ratio (%) and Cell Range (km). These values must be same on all sector controllers that will be synchronized with the GPS clock.

Step 3 Set the Synchronization Mode to Backup Master.Step 4 Click the Save button to save these changesStep 5 Reboot the sector controller as outlined in Rebooting the Devices on page 3-2.Step 6 Verify the successful restart and correct operation of the sector controller. 3-8Redline Communications Inc. Confidential and Proprietary

Chapter 3 Indoor Equipment MaintenanceStep 7 Click Status on the main menu to open the Status page. Verify that the SC Synchro Status is Backup Master This confirms that this device is receiving the GPS clocking pulse from the Master.

Configuring the Slave Sector Controller(s)Step 1 Log into the sector controller and click Wireless Interface to verify the values of Frame

Duration (ms), Downlink ratio (%) and Cell Range (km). These values must be same on all sector controllers that will be synchronized with the GPS clock.

Step 2 Set the Synchronization Mode to Slave.Step 3 Click the Save button to save these changesStep 4 Reboot the sector controller as outlined in Rebooting the Devices on page 3-2.Step 5 Verify the successful restart and correct operation of the sector controller. Step 6 Click Status on the main menu to open the Status page. Verify that the SC Synchro

Status is Slave. Step 7 Verify that the device is receiving a clocking pulse on the Sync Out port. The event log for

the sector controller should log an event message "Master Detected" or Synchronization OK. Review the event log as outlined in Monitoring System Event Logs on page 2-6.

Step 8 Repeat steps 1 through 7 for each of the remaining sector controllers at the base station site. All sector controllers will now be fully operational and time-synchronized from the GPS satellite's clocking source.

AN100U/UX Operation in GPS HoldoverWhen the GPS clocks input module is locked to a GPS signal, its internal oscillator and memory function ensure the reference synchronization signal adheres to the Timing Characteristics of Primary Reference Clocks standards (ITU-T recommendation G.811)

RedMAX Admin and Maintenance Guide

Documents

Transcript of RedMAX Admin and Maintenance Guide