Beruflich Dokumente
Kultur Dokumente
Airmux-200
Broadband Wireless Multiplexer
Version 1.9.3
Airmux-200
Broadband Wireless Multiplexer
Version 1.9.3
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the Airmux-200 to be delivered hereunder shall be free of defects in material and workmanship under normal use and service for a period of twelve (12) months following the date of shipment to DISTRIBUTOR. If, during the warranty period, any component part of the equipment becomes defective by reason of material or workmanship, and DISTRIBUTOR immediately notifies RAD of such defect, RAD shall have the option to choose the appropriate corrective action: a) supply a replacement part, or b) request return of equipment to its plant for repair, or c) perform necessary repair at the equipment's location. In the event that RAD requests the return of equipment, each party shall pay one-way shipping costs. RAD shall be released from all obligations under its warranty in the event that the equipment has been subjected to misuse, neglect, accident or improper installation, or if repairs or modifications were made by persons other than RAD's own authorized service personnel, unless such repairs by others were made with the written consent of RAD. The above warranty is in lieu of all other warranties, expressed or implied. There are no warranties which extend beyond the face hereof, including, but not limited to, warranties of merchantability and fitness for a particular purpose, and in no event shall RAD be liable for consequential damages. RAD shall not be liable to any person for any special or indirect damages, including, but not limited to, lost profits from any cause whatsoever arising from or in any way connected with the manufacture, sale, handling, repair, maintenance or use of the Airmux-200, and in no event shall RAD's liability exceed the purchase price of the Airmux-200. DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes relating to Airmux-200 and for ensuring that replacements and other adjustments required in connection with the said warranties are satisfactory. Software components in the Airmux-200 are provided "as is" and without warranty of any kind. RAD disclaims all warranties including the implied warranties of merchantability and fitness for a particular purpose. RAD shall not be liable for any loss of use, interruption of business or indirect, special, incidental or consequential damages of any kind. In spite of the above RAD shall do its best to provide error-free software products and shall offer free Software updates during the warranty period under this Agreement. RAD's cumulative liability to you or any other party for any loss or damages resulting from any claims, demands, or actions arising out of or relating to this Agreement and the Airmux-200 shall not exceed the sum paid to RAD for the purchase of the Airmux-200. In no event shall RAD be liable for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if RAD has been advised of the possibility of such damages. This Agreement shall be construed and governed in accordance with the laws of the State of Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste equipment in protecting the environment, the owner of this RAD product is required to refrain from disposing of this product as unsorted municipal waste at the end of its life cycle. Upon termination of the units use, customers should provide for its collection for reuse, recycling or other form of environmentally conscientious disposal.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates potential safety hazards regarding product operation or maintenance to operator or service personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while the product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the building protective ground bus.
Warning
Some products may be equipped with a laser diode. In such cases, a label with the laser class and other warnings as applicable will be attached near the optical transmitter. The laser warning symbol may be also attached. Please observe the following precautions: Before turning on the equipment, make sure that the fiber optic cable is intact and is connected to the transmitter. Do not attempt to adjust the laser drive current. Do not use broken or unterminated fiber-optic cables/connectors or look straight at the laser beam. The use of optical devices with the equipment will increase eye hazard.
Use of controls, adjustments or performing procedures other than those specified herein, may result in hazardous radiation exposure. ATTENTION: The laser beam may be invisible! In some cases, the users may insert their own SFP laser transceivers into the product. Users are alerted that RAD cannot be held responsible for any damage that may result if non-compliant transceivers are used. In particular, users are warned to use only agency approved products that comply with the local laser safety regulations for Class 1 laser products. Always observe standard safety precautions during installation, operation and maintenance of this product. Only qualified and authorized service personnel should carry out adjustment, maintenance or repairs to this product. No installation, adjustment, maintenance or repairs should be performed by either the operator or the user.
Connecting AC Mains
Make sure that the electrical installation complies with local codes. Always connect the AC plug to a wall socket with a protective ground. The maximum permissible current capability of the branch distribution circuit that supplies power to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A for USA and Canada). Always connect the power cord first to the equipment and then to the wall socket. If a power switch is provided in the equipment, set it to the OFF position. If the power cord cannot be readily disconnected in case of emergency, make sure that a readily accessible circuit breaker or emergency switch is installed in the building installation. In cases when the power distribution system is IT type, the switch must disconnect both poles simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference to the ground. Any single pole can be externally grounded. Due to the high current capability of DC power systems, care should be taken when connecting the DC supply to avoid short-circuits and fire hazards. Make sure that the DC power supply is electrically isolated from any AC source and that the installation complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A for USA and Canada). Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate the circuit breaker of the panel board that services the equipment and switch it to the OFF position. When connecting the DC supply wires, first connect the ground wire to the corresponding terminal, then the positive pole and last the negative pole. Switch the circuit breaker back to the ON position. A readily accessible disconnect device that is suitably rated and approved should be incorporated in the building installation. If the DC power supply is floating, the switch must disconnect both poles simultaneously.
Ports V.11, V.28, V.35, V.36, RS-530, X.21, 10 BaseT, 100 BaseT, Unbalanced E1, E2, E3, STM, DS-2, DS-3, S-Interface ISDN, Analog voice E&M xDSL (without feeding voltage), Balanced E1, T1, Sub E1/T1
Safety Status SELV Safety Extra Low Voltage: Ports which do not present a safety hazard. Usually up to 30 VAC or 60 VDC.
TNV-1 Telecommunication Network Voltage-1: Ports whose normal operating voltage is within the limits of SELV, on which overvoltages from telecommunications networks are possible. TNV-2 Telecommunication Network Voltage-2: Ports whose normal operating voltage exceeds the limits of SELV (usually up to 120 VDC or telephone ringing voltages), on which overvoltages from telecommunication networks are not possible. These ports are not permitted to be directly connected to external telephone and data lines. TNV-3 Telecommunication Network Voltage-3: Ports whose normal operating voltage exceeds the limits of SELV (usually up to 120 VDC or telephone ringing voltages), on which overvoltages from telecommunication networks are possible.
FXO (Foreign Exchange Office), xDSL (with feeding voltage), U-Interface ISDN
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance of a qualified safety engineer. Always make sure that the equipment is grounded before connecting telecommunication cables. Do not disconnect the ground connection before disconnecting all telecommunications cables. Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables. Extra caution should be exercised during thunderstorms.
When using shielded or coaxial cables, verify that there is a good ground connection at both ends. The grounding and bonding of the ground connections should comply with the local codes. The telecommunication wiring in the building may be damaged or present a fire hazard in case of contact between exposed external wires and the AC power lines. In order to reduce the risk, there are restrictions on the diameter of wires in the telecom cables, between the equipment and the mating connectors.
Caution
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cords.
Attention
Pour rduire les risques sincendie, utiliser seulement des conducteurs de tlcommunications 26 AWG ou de section suprieure.
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In such cases, a notice will be given in the installation instructions. Do not attempt to tamper with any carrier-provided equipment or connection hardware.
Avertissement
Achtung
Franais
Avertissement
Symboles de scurit
Ce symbole peut apparaitre sur l'quipement ou dans le texte. Il indique des risques potentiels de scurit pour l'oprateur ou le personnel de service, quant l'opration du produit ou sa maintenance.
Danger de choc lectrique ! Evitez tout contact avec la surface marque tant que le produit est sous tension ou connect des lignes externes de tlcommunications.
Mise la terre de protection : la cosse ou la borne marque devrait tre connecte la prise de terre de protection du btiment.
Avant la mise en marche de l'quipement, assurez-vous que le cble de fibre optique est intact et qu'il est connect au transmetteur. Ne tentez pas d'ajuster le courant de la commande laser. N'utilisez pas des cbles ou connecteurs de fibre optique casss ou sans terminaison et n'observez pas directement un rayon laser. L'usage de priphriques optiques avec l'quipement augmentera le risque pour les yeux.
L'usage de contrles, ajustages ou procdures autres que celles spcifies ici pourrait rsulter en une dangereuse exposition aux radiations. ATTENTION : Le rayon laser peut tre invisible !
Les utilisateurs pourront, dans certains cas, insrer leurs propres metteurs-rcepteurs Laser SFP dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas tre tenue responsable de tout dommage pouvant rsulter de l'utilisation d'metteurs-rcepteurs non conformes. Plus particulirement, les utilisateurs sont avertis de n'utiliser que des produits approuvs par l'agence et conformes la rglementation locale de scurit laser pour les produits laser de classe 1. Respectez toujours les prcautions standards de scurit durant l'installation, l'opration et la maintenance de ce produit. Seul le personnel de service qualifi et autoris devrait effectuer l'ajustage, la maintenance ou les rparations de ce produit. Aucune opration d'installation, d'ajustage, de maintenance ou de rparation ne devrait tre effectue par l'oprateur ou l'utilisateur.
Franais
Certains produits peuvent tre quips d'une diode laser. Dans de tels cas, une tiquette indiquant la classe laser ainsi que d'autres avertissements, le cas chant, sera jointe prs du transmetteur optique. Le symbole d'avertissement laser peut aussi tre joint. Avertissement Veuillez observer les prcautions suivantes :
Franais
Connexion d'alimentation CC
Sauf s'il en est autrement spcifi dans le manuel, l'entre CC de l'quipement est flottante par rapport la mise la terre. Tout ple doit tre mis la terre en externe. A cause de la capacit de courant des systmes alimentation CC, des prcautions devraient tre prises lors de la connexion de l'alimentation CC pour viter des courts-circuits et des risques d'incendie. Assurez-vous que l'alimentation CC est isole de toute source de courant CA (secteur) et que l'installation est conforme la rglementation locale. La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de court-circuit dpassant 35A (40A aux Etats-Unis et Canada). Avant la connexion des cbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'quipement et fixez-le en position OFF. Lors de la connexion de cbles d'alimentation CC, connectez d'abord le conducteur de mise la terre la borne correspondante, puis le ple positif et en dernier, le ple ngatif. Remettez le coupe-circuit en position ON. Un disjoncteur facilement accessible, adapt et approuv devrait tre intgr l'installation du btiment. Le disjoncteur devrait dconnecter simultanment les deux ples si l'alimentation en courant CC est flottante.
European Community
Radio-sets for use within the EU and most other European states are marked by one of the following signs: CE Mark. Radio-sets marked with this sign alone comply with harmonized standards and use harmonized frequency bands. There is no limitation on their use and they do not require a license. CE Mark with an exclamation mark. Radio-sets marked with this mark comply with harmonized standards but may use frequency bands which are not fully harmonized in all member countries. Certain spectrum or telecommunications authorities may impose restrictions on their use or require notification on the intention to operate them. CE Mark with an exclamation mark with a Notified Body number. Same as above, but with the addition of a survey conducted by a Notified Body (an expert opinion on the compliance of the radio-set with the various regulations). The following AirMux-200 systems comply with European regulations: Airmux-200/F24E/ in the frequency range 2400-2485 MHz (RLAN). No restrictions on use. Airmux-200/F54E/ in the frequency range 5470-5725 MHz (HIPERLAN). The following restrictions (at the date of publication of this manual) are applicable: Germany: Italy: Luxemburg: Macedonia: Romania: Turkey: Frequency assignment by the Federal Network Agency is required General authorization required if used outside own premises General authorization required for public service Frequency band not yet harmonized Frequency band not yet harmonized Frequency band occupied.
NNNN
The user is alerted that this list may be not complete and that in case of a doubt, the local spectrum authorities should be consulted. Radio-sets that use other frequency bands or with high output power, are always marked with and their use may be restricted.
Declaration of Conformity
Manufacturer's Name: Manufacturer's Address: declares that the product: Product Name: Airmux-200/F24E in the frequency range 2.400-2.4835 GHz RAD Data Communications Ltd. 24 Raoul Wallenberg St., Tel Aviv 69719, Israel
Conforms to the following standard(s) or other normative document(s): Radio: EN 300 328 V1.4.1 Electromagnetic compatibility and Radio spectrum Matters (ERM); Wideband transmission systems; Data transmission equipment operating in the 2.4 GHz ISM band and using wide band modulation techniques; Harmonized EN covering essential requirements under article 3.2 of the R&TTE Directive.
EMC:
EN 301 489-1 V1.4.1 Electromagnetic compatibility and radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements. EN 301 489-4 V1.3.1 Electromagnetic compatibility and radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 4: Specific conditions for fixed radio links and ancillary equipment and services.
Safety: EN 60950-1:2001
equipment
Safety
General
Supplementary Information: The product herewith complies with the requirements of the EMC Directive 89/336/EEC, the Low Voltage Directive 73/23/EEC and the R&TTE Directive 99/5/EC. The product was tested in a typical configuration. The equipment is Class 1 sub-class 22 equipment according to Commission Decision 2000/299/EC.
Haim Karshen VP Quality European Contact: RAD Data Ottobrunn-Riemerling, Germany Communications GmbH, Otto-Hahn-Str. 28-30, 85521
Declaration of Conformity
Manufacturer's Name: Manufacturer's Address: declares that the product: Product Name: Airmux-200/F54E in the frequency range 5.470-5.725 GHz RAD Data Communications Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel
Conforms to the following standard(s) or other normative document(s): Radio: EN 301 893 V1.2.3 Broadband radio Access Networks (BRAN); 5 GHz high performance RLAN; Harmonized EN covering essential requirements of article 3.2 of the R&TTE Directive.
EMC:
EN 301 489-1 V1.4.1 Electromagnetic compatibility and radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements. EN 301 489-4 V1.3.1 Electromagnetic compatibility and radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 4: Specific conditions for fixed radio links and ancillary equipment and services.
Safety: EN 60950-1:2001
equipment
Safety
General
Supplementary Information: The product herewith complies with the requirements of the EMC Directive 89/336/EEC, the Low Voltage Directive 73/23/EEC and the R&TTE Directive 99/5/EC. The product was tested in a typical configuration. Notified Body number: 0891 (TRL Compliance Services U.K) Tel Aviv, 08 February 2007 0891
Haim Karshen VP Quality European Contact: RAD Data Ottobrunn-Riemerling, Germany Communications GmbH, Otto-Hahn-Str. 28-30, 85521
1.
Equipment Required
RJ-45 crimp tool (if pre-assembled cable is not used) Drill (for wall mounting only) IDU and ODU grounding cables O-PoE 10 AWG grounding cable 13 mm () spanner/wrench ODU to IDU cable if not ordered (outdoor class, CAT-5e, 4 twisted pairs) ODU to O-PoE both cables (ETH and PoE) if not ordered (outdoor class, CAT-5e, 4 twisted pairs) Cable ties Laptop running Windows 2000 or Windows XP.
2.
1. Verify that all equipment and tools are available. 2. Install the Airmux-200 software on the laptop; the installation takes several minutes. The software installation leaves the Airmux-200 Manager icon on the desktop. 3. BRS systems only - Activate the link.
3.
To install the ODU: 1. At site A, route the ODU cable from the ODU location (on the roof) to the IDU location (inside the building). The maximum length is 100m. 2. Mount the ODU unit to the mast or wall, using the mounting kit and mounting instructions.
Note
Do not tightly secure the ODU until the alignment process is complete When installing the ODU is important to check that there are no direct obstructions in front of the ODU between the two link sites.
3. Verify that the ODU mounting brackets are connected to ground. 4. Connect the ODU chassis ground to ground. 5. Connect the RJ-45 connectors to both ends of the cable using the pinout table and diagram below:
IDU RJ-45 1 2 3 6 4 5 7 8 twisted pair twisted pair twisted pair twisted pair Wire Color White/Green Green White/Orange Orange Blue White/Blue White/Brown Brown Function Ethernet (RxN) Ethernet (RxT) Ethernet (TxT) Ethernet (TxN) Power (+) Power (+) Power () Power () ODU RJ-45 1 2 3 6 4 5 7 8
6. Secure the ODU and ground cables to the mast or brackets using cable ties. 7. Repeat the procedure at site B.
To align the ODU: 1. Connect power to the site A IDU. After approximately 20 seconds the ODU beeper starts beeping. This is normal. 2. Verify normal operation of the IDU by the LED indications on the front panel.
Indicator PWR IDU ODU AIR I/F SERVICE Color Green Orange Green Green Orange Green Green Status ON ON for short duration during startup ON during normal operation ON shows normal operation ON for short duration during startup ON shows normal operation ON shows normal operation OFF when Service is configured for Ethernet only
Caution
Do not stand in front of a live outdoor unit. 3. Align the site A ODU in the direction of the site B ODU. 4. Connect power to the site B IDU. After approximately 20 seconds the ODU beeper starts beeping. This is normal. 5. Verify normal operation of the IDU by the LED indications on the panel.
Indicator PWR IDU ODU AIR I/F SERVICE Color Green Orange Green Green Orange Green Green Status ON IDU-E only ON for short duration during startup ON during normal operation ON shows normal operation ON for short duration during startup ON shows normal operation ON shows normal operation OFF when Service is configured for Ethernet only
6. Make an azimuth sweep with the site B ODU of 180 degrees so that the site A ODU position is learned by the site B ODU. 7. Turn the site B ODU slowly back towards the site A direction, listening to the beep sequence until optimal alignment is achieved.
Note
Three beeps and a pause is the best signal Two beeps and a pause, signal quality increased One beep and pause is no signal change Any other signal detects no signal between ODUs.
8. Secure the site B ODU to the mast/wall. 9. At site A, adjust the ODU slowly while listening to the beeper sequence until the best signal is attained. 10. Secure the site A ODU to the mast/wall. 11. Monitor the link quality for about 15 minutes to verify stability. 12. Connect the management station to one of the two IDUs in the link. 13. Double-click the Airmux-200 Manager icon to start the application. 14. Click the Installation button to open the installation wizard and follow the installation steps. After selection of the radio channel and the link rate (as determined in the Link Budget Calculator utility), verify that the link quality bar in the Airmux-200 manager is within the green range for TDM service and within the yellow range for Ethernet service.
Note
Achieve the best possible link quality values. In case of radio link loss, verify the ODU alignment, or change the radio channel in both sides of the link. When the radio link resumes, continue the installation process.
To install the Outdoor PoE (O-PoE): 1. Route the ODU cable from the ODU location (on the roof) to the O-PoE location (also on the roof). The maximum combined length of the ODU to Outdoor PoE cable and the O-PoE to user hub/router (or any other compatible device) cable is 100m. 2. Mount the O-PoE unit to the mast or wall, using the mounting kit and mounting instructions. 3. Verify that the O-PoE mounting brackets are connected to ground. 4. Connect the O-PoE chassis to ground. 5. Route the O-PoE AC cable along the mast or wall to a protected/shielded AC outlet.
Only UL Listed parts and components will be used for installation. Use UL Listed devices having an environmental rating equal to or better than the enclosure rating to close all unfilled openings
Warning
4.
Before connecting any cable, the protective earth terminals of the AC/DC adapter must be connected to the protective ground conductor of the mains power cord. If you are using an extension cord (power cable) make sure it is grounded as well.
Warning
Any interruption of the protective (grounding) conductor (inside or outside the instrument) or disconnecting of the protective earth terminal can make this unit dangerous. Intentional interruption is prohibited.
Warning
5.
To connect user equipment to the IDU: 1. Connect the user equipment (such as PBX) to the IDU RJ-45 port designated Trunk: On the rear panel of the IDU On the front panel of the IDU-E 2. Connect user hub/router or any other compatible device to the IDU RJ-45 port designated LAN. On the rear panel of the IDU On the front panel of the IDU-E To connect user equipment to the O-PoE: Connect user hub/router or any other compatible device to the port designated ETH via an outdoor shielded CAT-5e cable. To connect directly to PC LAN port, refer to Appendix A.
IDU-E has an integrated LAN switch that provides two 10/100BaseT ports. The
Note
Integrated LAN switch does not support Spanning Tree. The two LAN ports can be connected to two separate LAN segments.
Do not connect both LAN ports to the same LAN segment, a loop will be created that will flood the network. For O-PoE only UL Listed parts and components are used for installation. Use UL listed devices having an environmental rating equal to or better than the enclosure rating to close all unfilled openings.
Caution
Caution
Contents
Chapter 1. Introduction 1.1 Overview.................................................................................................................... 1-1 Product Options...................................................................................................... 1-1 Applications ............................................................................................................ 1-2 Features ................................................................................................................. 1-4 Wireless Link ...................................................................................................... 1-4 LAN Interface ..................................................................................................... 1-4 TDM Interface .................................................................................................... 1-4 Advanced Encryption System .............................................................................. 1-4 1+1 TDM Link Redundancy ................................................................................. 1-4 Management ...................................................................................................... 1-5 Diagnostics and Performance Monitoring ............................................................ 1-5 Automatic Channel Select ................................................................................... 1-5 Adaptive Modulation .......................................................................................... 1-5 Transmit Power Control ...................................................................................... 1-5 Alarm Connector ................................................................................................ 1-6 Link Compatibility ............................................................................................... 1-6 Optional External Antenna .................................................................................. 1-6 Hub Site Synchronization ................................................................................... 1-7 E1 Trunk Redundancy ......................................................................................... 1-7 Ethernet Ring ..................................................................................................... 1-7 VLAN Management ............................................................................................. 1-8 1.2 New in This Version.................................................................................................... 1-8 1.3 Physical Description ................................................................................................... 1-8 IDU ......................................................................................................................... 1-9 IDU-E ...................................................................................................................... 1-9 IDU-R...................................................................................................................... 1-9 ODU ..................................................................................................................... 1-10 PoE-8 ................................................................................................................... 1-10 O-PoE ................................................................................................................... 1-11 GSU ...................................................................................................................... 1-11 1.4 Functional Description.............................................................................................. 1-12 1.5 Technical Specifications............................................................................................ 1-14 Chapter 2. Installation and Setup 2.1 Safety Practices ......................................................................................................... 2-1 Preventing Overexposure to RF Energy .................................................................... 2-1 Grounding .............................................................................................................. 2-2 Protection against Lightning ................................................................................... 2-2 Grounding for Indoor/Outdoor Units ................................................................... 2-3 External Lightning Surge Suppressors ................................................................. 2-3 Internal ESD Protection Circuits .......................................................................... 2-3 RF Exposure ............................................................................................................ 2-3 2.2 Site Requirements and Prerequisites .......................................................................... 2-4 2.3 Package Content ........................................................................................................ 2-4 2.4 Additional Equipment Required................................................................................... 2-5 2.5 Installation Sequence ................................................................................................. 2-6 2.6 Surveying the Site ...................................................................................................... 2-6 Planning the Link Site ............................................................................................. 2-7
Airmux-200 Ver. 1.9.3 i
Table of Contents
Site Survey ............................................................................................................. 2-7 Stage 1 (Preliminary Survey) ............................................................................... 2-8 Stage 2 (Physical Survey) ................................................................................... 2-8 Stage 3 (RF Survey) ............................................................................................ 2-9 RF Planning for Dense Installations and Collocated Sites.......................................... 2-9 2.7 Mounting the ODU or O-PoE..................................................................................... 2-10 2.8 Mounting External Antennas..................................................................................... 2-11 2.9 Mounting the Lightning Protection Devices ............................................................... 2-11 2.10 Connecting the ODU to the IDU ................................................................................ 2-12 2.11 Installing the Airmux-200 Management Software ...................................................... 2-13 2.12 Connecting to Power ................................................................................................ 2-14 Connecting Power to an IDU ................................................................................. 2-14 Connecting Power to an IDU-E .............................................................................. 2-14 Connecting Power to an O-PoE ............................................................................. 2-15 2.13 Aligning Antennas with the Beeper ........................................................................... 2-15 2.14 Starting the Manager Software................................................................................. 2-16 Starting the Airmux Manager ................................................................................. 2-16 Login Errors .......................................................................................................... 2-20 Unsupported Device ......................................................................................... 2-20 Incorrect IP Address ......................................................................................... 2-20 Incorrect Password ........................................................................................... 2-21 Invalid Read/Write Community String ................................................................ 2-21 Logging in to the Over-the-Air Site ................................................................... 2-21 Continuing without an IP Address ..................................................................... 2-22 Changing the Login Password ........................................................................... 2-22 2.15 Installing the Link ..................................................................................................... 2-22 Configuring System Parameters............................................................................. 2-23 Changing the Link Password .................................................................................. 2-25 Selecting Channels ................................................................................................ 2-27 Configuring Hub Site Synchronization .................................................................... 2-29 Configuring Services.............................................................................................. 2-30 Configuring the Jitter Buffer .................................................................................. 2-33 Configuring Hot Standby ....................................................................................... 2-34 Configuring the Clock ............................................................................................ 2-35 Setting the T1 Line Code ....................................................................................... 2-37 Configuring Ethernet Ring ..................................................................................... 2-37 Configuring the TDM Backup ................................................................................. 2-37 2.16 Connecting to E1/T1 Equipment ............................................................................... 2-40 2.17 Connecting to Ethernet Equipment ........................................................................... 2-40 Chapter 3. Operation 3.1 Turning On the Unit ................................................................................................... 3-1 3.2 Controls and Indicators .............................................................................................. 3-1 IDU Front Panel Indicators ....................................................................................... 3-1 3.3 Default Settings ......................................................................................................... 3-3 3.4 Configuration and Management Alternatives .............................................................. 3-4 Working with the Management Utility...................................................................... 3-4 Over the Air Connection Indication ..................................................................... 3-9 Verifying the Application Software Version ....................................................... 3-10 3.5 Working with Telnet ................................................................................................. 3-10 3.6 Turning Off the Unit ................................................................................................. 3-12
ii
Table of Contents
Chapter 4. Configuration 4.1 Configuring the Link ................................................................................................... 4-1 Configuring the System Parameters......................................................................... 4-1 Selecting Channels .................................................................................................. 4-3 Configuring Service Parameters ............................................................................... 4-3 Configuring TDM Services ........................................................................................ 4-4 Configuring Ethernet Ring ....................................................................................... 4-4 Ethernet Ring Behavior ....................................................................................... 4-5 Supported Ethernet Ring Topologies ................................................................... 4-6 Protection Switching .......................................................................................... 4-8 Hardware Considerations ................................................................................... 4-8 Special Case: 1 + 1 Ethernet Redundancy ........................................................... 4-9 Configuring the Ring......................................................................................... 4-10 Configuring TDM Backup ....................................................................................... 4-13 Configuring Cascaded Links ................................................................................... 4-13 Configuring for Video Surveillance Application ....................................................... 4-14 Completing the Link Configuration ........................................................................ 4-16 4.2 Configuring the Sites ................................................................................................ 4-17 Configuring for Management ................................................................................. 4-19 Defining the Management Addresses ............................................................... 4-19 Configuring VLAN Management......................................................................... 4-20 Configuring SNMP Communities ........................................................................ 4-21 Configuring for Operation ..................................................................................... 4-23 Changing the Transmit Power ........................................................................... 4-23 Setting the Maximum Information Rate............................................................. 4-25 Configuring Ethernet Mode ............................................................................... 4-26 Configuring the Bridge...................................................................................... 4-27 Configuring VLANs ............................................................................................ 4-28 Performing Additional Tasks .................................................................................. 4-35 Displaying the Inventory ................................................................................... 4-35 Displaying MHS Status ...................................................................................... 4-36 Changing Passwords ......................................................................................... 4-36 Setting the Date and Time................................................................................ 4-37 Muting the Beeper ........................................................................................... 4-39 Setting External Alarm Inputs............................................................................ 4-39 Managing Configuration Files ............................................................................ 4-40 Reinstalling the Link ......................................................................................... 4-41 Configuring Link Security .................................................................................. 4-41 Resetting Airmux-200....................................................................................... 4-43 Chapter 5. Monitoring and Diagnostics 5.1 Monitoring Performance ............................................................................................. 5-1 Viewing Performance Reports ................................................................................. 5-1 Saving the Monitor Log ........................................................................................... 5-4 5.2 Detecting Problems .................................................................................................... 5-5 Self-Test ................................................................................................................. 5-6 LEDs ....................................................................................................................... 5-6 Alarms and Traps .................................................................................................... 5-6 Statistic Counters ................................................................................................... 5-6 Link Compatibility Information ................................................................................. 5-6 Remote Power Fail Indication .................................................................................. 5-7
iii
Table of Contents
5.3 Handling Events ......................................................................................................... 5-7 Setting the Events Preferences ........................................................................... 5-9 Saving the Events Log ...................................................................................... 5-10 Resetting the Monitoring and Alarm Preferences to Defaults ............................ 5-10 5.4 Collecting Unified Performance Information .............................................................. 5-11 5.5 Troubleshooting ....................................................................................................... 5-12 5.6 Performing Diagnostic Tests ..................................................................................... 5-13 Local External Loopback ........................................................................................ 5-15 Remote Internal Loopback .................................................................................... 5-16 Remote External Loopback .................................................................................... 5-16 Local Internal Loopback ........................................................................................ 5-17 5.7 Replacing an ODU .................................................................................................... 5-18 5.8 Frequently Asked Questions ..................................................................................... 5-18 5.9 Technical Support .................................................................................................... 5-21 Chapter 6. Software Upgrade Chapter 7. Application Tutorial 7.1 Point-to-Point Application .......................................................................................... 7-1 Equipment List ........................................................................................................ 7-1 Calculating Expected Link Performance .................................................................... 7-2 Surveying the Sites ................................................................................................. 7-4 Installing the Airmux-200 Management Software..................................................... 7-5 Installing Airmux-200s............................................................................................. 7-5 Aligning the Antennas ............................................................................................. 7-7 Configuring the Link Using the Link Installation Wizard ............................................ 7-7 Configuring the Local and Remote Sites ................................................................ 7-15 Testing the Application ......................................................................................... 7-17 Collecting Performance Statistics .......................................................................... 7-17 Displaying Performance Report......................................................................... 7-18 Saving a Monitor Log ........................................................................................ 7-18 Collecting Link and Management Data .............................................................. 7-19 7.2 Multipoint-to-Point Application ................................................................................ 7-19 Equipment List ...................................................................................................... 7-20 Installing the HSSU Collocation Hub ....................................................................... 7-20 Configuring the HSS Operation .............................................................................. 7-21 Appendix A. Connection Data Appendix B. Mast and Wall Installation Appendix C. Link Budget Calculator Appendix D. Lightning Protection and Grounding Guidelines Appendix E. AIND Antenna Alignment Procedure Appendix F. Preloading IP Address and Changing Default Band Appendix G. Hub Site Synchronization Appendix H. BRS Installation Procedure Appendix I. MIB Reference Appendix J. FCC/IC DFS Installation Procedure Appendix K. Installing a Hot Standby Link Appendix L. GPS Synchronization
iv
Chapter 1 Introduction
1.1 Overview
Airmux-200 is a carrier-class, high capacity, point-to-point broadband wireless transmission system. Airmux-200 combines legacy TDM and Ethernet services over 2.3 to 2.7 and 4.0 to 6 GHz bands, and is suitable for deployment in FCC, ETSI, CSA-regulated countries, and other regions. The system provides up to 48 Mbps wireless link and supports ranges of up to 80 km (50 miles) with an external antenna.
Product Options
Airmux-200 is available in several different frequency ranges, with versions for ETSI, FCC, IC and other regulations.
Overview
1-1
Chapter 1 Introduction
Band ETSI 5.8 UK 5.8 WPC India 5.8 MII China 5.8 Universal 2.3 Universal 2.4 Universal 2.7 Universal 5.3 Universal 5.4 Universal 5.7 Universal 5.9 Universal 5.9 Universal 6.0
Occupied Frequency Range [GHz] Compliance 5.7255.875 5.7255845 5.8255.875 5.7305.845 2.3022.397 2.3122.482 2.7002.900 5.1405.345 5.4755.720 5.6905.880 5.7305.950 5.7305.950 5.7956.030 NA ETSI EN 302 502 UK VNS 2107 GSR-38 MII China
Several special systems are also available; AIRMUX-200-AIND, All Indoor unit, F58/FCC with 4T1 support. AIRMUX-200-AIND integrates the ODU and the IDU-E into a single 19" IDU-E box. AIRMUX-200-L, Ethernet only units powered over the Ethernet via PoE unit. Available in F23, F24, or F58 frequency ranges. AIRMUX-200-LC, ODU is equipped with special hardware for the collocation of several units, using Hub Site Synchronization (HSS).
Applications
Figure 1-1 illustrates a typical collocation application of Airmux-200 and
Airmux-400 units.
1-2
Overview
Chapter 1 Introduction
Figure 1-1. Airmux-200 and Airmux-400 Collocated at a Central Site (Multiple Point-to-Point) Figure 1-2 illustrates Airmux-200 units in video surveillance applications. The units provide wide area, such as railroad track or pipeline, protection and urban surveillance.
Overview
1-3
Chapter 1 Introduction
Features
Wireless Link
Airmux-200 delivers up to 48 Mbps air rate for Ethernet and E1/T1 traffic. The system supports a variety of spectrum bands and can be configured to operate in any channel in the band with a carrier step resolution of 5 MHz and channel bandwidth of 5, 10, or 20 MHz. Airmux-200 operation complies with ETSI, CSA, CN, UK, and the FCC 47CFR Part 15 and subpart C and E requirements. Airmux-200 employs Time Division Duplex (TDD) transmission. This technology simplifies the installation and configuration procedure. There is no need to plan and to allocate separate channels for the uplink and downlink data streams. Operation over 2.4 GHz and 5.x GHz bands is not affected by harsh weather conditions, such as fog and heavy rain.
LAN Interface
The Airmux-200 LAN port provides 10/100BaseT interfaces with autonegotiation and transparent VLAN support. Traffic handling is provided by a MAC-level self-learning bridge.
TDM Interface
The Airmux-200 TDM interface accepts E1 or T1 traffic, supporting the following: Unframed operation (E1 and T1) AMI and B8ZS zero suppression (T1).
1-4
Overview
Chapter 1 Introduction
A comprehensive solution for protection against both equipment failure and loss of air interface, by simple connectivity between a primary link and a secondary link with switchover between the links in under 50 ms Full interoperability between Airmux-200 and Airmux-400.
Management
Airmux-200 has full local and remote management capabilities. The user-friendly SNMP-based management tool provides full end-to-end configuration, event log and performance monitoring capabilities. Alternatively each site can be configured or monitored via a Telnet terminal.
Adaptive Modulation
Airmux-200 changes modulation automatically depending on channel characteristics in order to guarantee continuation of service. The adaptive modulation enables the user to maximize Ethernet throughput without degradation of the TDM service quality. When Ethernet only service is used, the adaptive modulation enables improving the Ethernet performance in case of air performance degradation (periodical interference or RSS changes). In case of interference at one site, there is no need to use a lower modulation at the other site (as in previous versions). In such a case the actual rate changes automatically only at the problematic site, while the second side of the link maintains the highest possible rate (asymmetric). Adaptive modulation can be selected in both installation and configuration wizards.
Overview
1-5
Chapter 1 Introduction
Alarm Connector
The IDU-E has eight external alarm inputs and outputs in the form of dry-contact relays. The Alarm DB-9 connector is located on the front panel of the IDU-Eit is a 9-pin D-type female connector. The user enables or disables each of the alarms and configures the text that appears in the alarm trap. The ODU sends the alarm within less than a second from actual alarm trigger. The IDU-R has a DB-25 alarm connector with 20 external alarm inputs and outputs. The alarm connector is available as an ordering option for the IDU.
Link Compatibility
Airmux-200 indicates the version compatibility via software traps. As new hardware is added to existing networks compatibility issues may arise. Trap messages indicate the problem and suggest upgrades as appropriate.
1-6
Overview
Chapter 1 Introduction
Grid Antenna
The grid antenna is used for 2.4 GHz applications. Due to the large size, the grid design minimizes weight and windloading.
E1 Trunk Redundancy
IDU-R units have a secondary E1 input which may be connected to external equipment other than the ODU. This provides backup in the event of failure of either the air interface link of the Airmux-200, or the secondary E1 link. The user configures which of the two links is the main link and which is the backup link. The trigger that switches between primary and secondary links is a primary link signal loss lasting 20 ms. IDU-R monitors the primary link constantly and returns to its normal operation if the primary signal is active again for more than 20 ms.
Ethernet Ring
Ethernet rings are used to protect data against link and node failures. The rings ensure high availability of Ethernet services for critical applications.
Overview
1-7
Chapter 1 Introduction
VLAN Management
VLAN management allows the separation of user traffic from NMS traffic. The user decides if such a separation is required. Both the headquarters and remote sites are configured with VLAN management.
1.2
Below are the major changes and additions introduced in version 1.9.3. The new IDU with two LAN ports, two independently clocked TDM ports and a 25-pin dry contact alarm port, HSS support, VLAN tagging and double tagging GPS support for distributed hub sites Ethernet ring and 1+1 Ethernet link redundancy DC PoE devices: A ruggedized version for outdoor use RFD (RFP B) for collocated Airmux-200 and Airmux-400 units Scheduled software upgrades License key for multiple band activation and regulation change Enabling/disabling Telnet access.
1.3
Physical Description
An Airmux-200 system may consist of an Outdoor Unit (ODU) and an Indoor Unit, which may be an IDU or an IDU-E; an All Indoor Unit, AIND; or an outdoor PoE, O-PoE, housed in a weather proof enclosure.
Figure 1-6 shows the IDU, IDU-E carrier class unit, and an ODU with integrated
antenna.
1-8
Physical Description
Chapter 1 Introduction
IDU
The front panel of the IDU includes five LEDs, which display the status of E1/T1 traffic, wireless link, self-test results, the ODU-to-IDU link, and power status. For a detailed description of the front panel LEDs, see Chapter 3. The rear panel of the IDU includes the connectors for power, WAN, LAN, E1/T1, and the ODU. The wiring specifications are detailed in Appendix A. The rear panel LEDs are described in Chapter 3.
IDU-E
The IDU-E front panel includes LEDs that display the status of E1/T1, wireless link, self-test results, and ODU-to-IDU link. For a detailed description of the front panel LEDs, see Chapter 3.
IDU-R
IDU-R is a compact, 19-inch, 1U-high plastic unit for 1 E1/T1 backup. It provides an additional two Ethernet ports and external alarm interface. IDU-R is an indoor unit that automatically backs up leased lines by monitoring the status of leased lines. In the event of a connection failure it automatically switches to the radio link. The user configures which of the two links is the main link and which is the backup link. IDU-R operates with all Airmux-200 outdoor units.
Physical Description
1-9
Chapter 1 Introduction
ODU
ODU includes an RJ-45 connector, which receives -48 VDC, and Ethernet traffic from the IDU. The ODU is attached to a mast using a special mounting kit, which is supplied with the unit. The ODU can be used with an integrated antenna, as illustrated in Figure 1-6, or with an external antenna. If an external antenna is to be used, then the ODU is supplied fitted with an N-type connector.
PoE-8
Airmux-200 PoE-8 is an IDU for collocated Ethernet applications. It features 8 Ethernet ports, 8 decoupled ports of ODU, 2 outputs of dry contact alarms, and receives power by AC, DC, or both as either AC input or DC input 20V - 60V.
Description
8 Ethernet ports 8 decoupled ODU ports
LEDs
Input power red/green bicolor Green Input power is within range Red Input power is out of range LEDs per each ODU port [RJ45] Green The ODU is connected and is normally operating Red Over-current (shorted) When the red LED is On the green LED must be Off.
Alarms
2 dry contact alarm outputs Dry contact #1: A red ODU port LED is on. Dry contact #2: The input power red LED is on (out of range).
Power Source
100240 VAC 20 to 60 VDC (protected against reverse polarity connection) AC/DC or both
1-10
Physical Description
Chapter 1 Introduction
O-PoE
O-PoE (Outdoor Power over Ethernet) includes an AC power cable with no termination which can be connected to 100-220 VAC outlet. The designated PoE connector is connected to an ODU via a shielded CAT-5e twisted pair cable and delivers Ethernet traffic with 48 VDC power towards the ODU. The designated ETH connector is connected via a shielded CAT-5e twisted pair cable which receives and delivers Ethernet traffic. The wiring specification for the twisted pair cable is detailed in Appendix A. The O-PoE is attached to a mast using a special mounting kit, which is supplied with the unit.
Note
To connect the ETH port from O-PoE to a PC, a crossed LAN cable must be used. See Appendix A.
GSU
The GPS-based synchronization unit (GSU) is designed to handle inter-site interferences under large-scale deployment scenarios. The GSU is an outdoor unit consisting of a standard wireless link enclosure, a GPS antenna and a PoE device. The GSU is connected to the HSS unit using a standard HSS cable. It synchronizes the transmission timing of multiple hub sites to the same clock source thus eliminating mutual interference.
Physical Description
1-11
Chapter 1 Introduction
1.4
Functional Description
Airmux-200 system comprises of the following units: Outdoor Unit (ODU): An enclosed aluminum frame with a front sealed plastic cover, containing an integrated transceiver with an antenna, RF module, modem and standard interfaces. The ODU stores all the configuration parameters of the Airmux-200 system. Figure 1-9 shows the ODU block diagram. Indoor Unit (IDU or IDU-E): The interface unit between the ODU and the user. It converts 100240 VAC to -48 VDC, and sends it on to the ODU. The IDU does not store any configuration data. Therefore, there is no need for additional configuration of the Airmux-200 system when replacing an IDU. IDU-R: The unit monitors the status of leased lines, and in the event of a connection failure automatically switches to the radio link. The user configures which of the two links is the main link and which is the backup link. IDU-R operates with all Airmux-200 outdoor units. Outdoor PoE (O-PoE): An enclosed aluminum frame with a front sealed aluminum cover, containing a 110-220 VAC to 48 VDC switching power supply and an interface interconnecting an un-powered Ethernet infrastructure to ODU.
1-12
Functional Description
Chapter 1 Introduction
Functional Description
1-13
Chapter 1 Introduction
1.5
Air Interface
Technical Specifications
OFDM Time Division Duplex (TDD) Configurable up to 48 Mbps OFDM - BPSK, QPSK, 16QAM, 64QAM 5/10/20 MHz (ETSI systems do not support 5/10) (BRS systems, Single and Double only) Specification is different per product, for further details refer to the Link Budget Calculator Up to 80 km (50 miles) with an external antenna L versions up to 20 km See Table 1-1
Technology Duplexing Method Capacity Modulation Channel Resolution Transmitter Power Range Frequency Bands [GHz] and Standards
PHY Framing/Coding Bridging Line Impedance VLAN Support Frame Size Connector
Up to 2 10/100BaseT, auto-sensing IEEE 802.3/U Self-learning, up to 2048 MAC addresses 100 (10/100BaseT) Yes 1536 bytes max 1800 bytes max for PoE RJ-45 ( 10/100BaseT) LC (SFP-based)
E1 Interface
Unframed (transparent) 2.048 MHz (Specification may be different per ordering option) HDB3 RJ-45 IDU: 1 or 2 IDU-E: 4
1-14
Technical Specifications
Chapter 1 Introduction
T1 Interface
Unframed (transparent) 1.544 MHz (Specification may be different per ordering option) AMI, B8ZS RJ-45 IDU: 1 or 2 IDU-E: 4 Power status (IDU only) IDU-E status ODU-to-IDU link status Link status E1/T1 signal status IDU: 100240 VAC via external AC/DC converter IDU-E: 100240 VAC via AC cable -48 VDC (-42 to 60 VDC), 24 VDC -48 VDC
Indicators
PWR (green) IDU (green) ODU (green/red) LINK (green/red) SERVICE (green/red)
Power
Source
ODU plus IDU 10W max ODU plus IDU-E 14W max O-PoE plus ODU 25W max PoE-8 plus 8 ODU units 60W max IDU 2-pin IDU-E AC 3-pin IEC connector DC 3-pin terminal block
Connector
Technical Specifications
1-15
Chapter 1 Introduction
Alarm Connector
DB-9 female for IDU-E/AIND/PoE-8 DB-25 female for IDU-R Dry Contact, 30V/2A Max input current, 0.01A at 0.5W (R=5K) ODU with integrated antenna 30.5 cm (12 in) 30.5 cm (12 in) 5.8 cm (2.3 in) 1.5 kg (3.3 lb) IDU-E 4.5 cm (1.7 in) 1U 29 cm (11.5 in) 43 cm (17.7 in) 1.5 kg (3.3 lb)
Physical
24.5 cm (9.3 in) 13.5 cm (5.13 in) 4.0 cm (1.57 in) 1.0 kg (2.2 lb) IDU 4.5 cm (1.7 in) 1U 23.5 cm (9.3 in) 16.5 cm (6.7 in) 0.5 kg (1.1 lb)
Environment
Enclosure Temperature
Temperature Humidity
1-16
Technical Specifications
Chapter 1 Introduction
Antenna Type
Frequency
Gain
Beam
Dimensions
Weight
Connector
[GHz] External
[dBi]
[degrees] [mm]
[inch]
[kg]
[Ib]
17 (2.7 GHz) Flat panel 2.72.9 16.5 (2.8 GHz) 16 (2.9 GHz) 21.5 (5.155.25 GHz) Flat panel 5.1506.020 22 (5.255.875 GHz) 21.5 (5.8756.0 GHz ) 21.14 (6.020 GHz) 28 (5.155.875 GHz) Flat panel 5.1506.020 27.5 (5.8756.0 GHz) 28.23 (6.020 GHz) Flat panel Flat panel Dish Dish Dish Dish Dish Grid 4.905.35 21.5 9 4.5 8 6 5 4 6 14 Az. 8 El. 10 30530515 30530515 600 900 900 900 600 600900 12120.5 12120.5 23.6 35.4 35.4 35.4 23.6 23.635.4 2.5 2.5 5 10 10 10 5 4.5 5.5 5.5 11 22 22 22 11 9.9 N-type N-type N-type N-type N-type N-type N-type N-type 4.5 30530515 12120.5 2.5 5.5 N-type 9 30530515 12120.5 2.5 5.5 N-type 19 30530525 12120.9 1.5 3.3 N-type
Grid
700900
27.535.4
3.3
7.2
N-type
Technical Specifications
1-17
Chapter 1 Introduction
1-18
Technical Specifications
Warning
Always observe standard safety precautions during installation, operation, and maintenance of this product.
Note
Before installing the product, review Handling Energized Products at the beginning of the manual.
2.1
Safety Practices
Warning
Outdoor units and antennas should be installed ONLY by experienced installation professionals who are familiar with local building and safety codes and, wherever applicable, are licensed by the appropriate government regulatory authorities. Failure to do so may expose the end user or the service provider to legal and financial liabilities. RAD and its resellers or distributors are not liable for injury, damage or violation of regulations associated with the installation of outdoor units or antennas.
Warning
Grounding
All RAD products should be grounded during operation. In addition: The ODU should be earthed by a wire with diameter of at least 12 AWG. The Airmux-200 ODU must be properly grounded to protect against lightning. It is the user's responsibility to install the equipment in accordance with Section 810 of the National Electric Code, ANSI/NFPA No.70-1984 or Section 54 of the Canadian Electrical Code. These codes describe correct installation procedures for grounding the outdoor unit, mast, lead-in wire and discharge unit. It also lays down the size of grounding conductors and connection requirements for grounding electrodes. The Airmux-200 ODU must be grounded to a protective earth as described in Appendix D and in accordance with the local electrical regulations. The earth lug on the IDUE should be connected to the protective earth at all times, by a wire with a diameter of 18 AWG or wider. Rack-mounted equipment should be mounted only in earthed racks and cabinets. Always make the ground connection first and disconnect it last Never connect telecommunication cables to ungrounded equipment Ensure that all other cables are disconnected before disconnecting the ground.
The Airmux-200 lightning protection system consists of the following components, as described below: Individual grounding for each indoor or outdoor unit
2-2
Safety Practices
External primary surge suppressor unit for the CAT-5 outdoor cable Internal ESD protection circuits over the power/telecom lines
RF Exposure
The antennas used for the following transmitters must be installed so as to provide a minimum separation distance from by-standers as specified in the following tables.
Safety Practices
2-3
Installation and Operation Manual Antenna gain [dBi] 24 24 15.2 17.5/24 5100A-AMWL1490H 5100A-AMWL1490H 5100A-AMWL1540C 27 18.5 22 Min. Safety Distance [cm] 36 71 37 200 98 42 20
Frequency Band [GHz] 2.4 2.4 2.4 2.5 4.9 4.9 5.3/5.4
IC ID 5100A-AMWL1240
2.2
For the IDU units, allow at least 90 cm (36 in) of frontal clearance for operating and maintenance. Allow at least 10 cm (4 in) clearance at the rear of the unit for signal lines and interface cables. The ambient operating temperature should be 35 to 60C (31 to 140F) (ODU), or 0 to 50C (32 to 122F) (IDU) at a relative humidity of up to 100% (ODU) or 90% (IDU), non-condensing.
2.3
Package Content
The Airmux-200 packages include the following items: ODU package containing: ODU Mast/Wall mounting kit plus mounting instructions CD-ROM [Airmux-200 Manager, Installation and Operation Manual, and Link Budget Calculator Self adhesive label showing the MAC address and the alternative community string KEY. Keep this label safe.
2-4 Package Content Airmux-200 Ver. 1.9.3
IDU or IDU-R package containing: IDU or IDU-R AC/DC Converter IDU wall-mounting drilling template Self adhesive label showing the IDU LED operation Or
IDU-E package containing: IDU-E For AC model, 110/240 VAC with 3-prong connector cable For DC model, 3-pin terminal block connector (green) 19 mounting kit
ODU/IDU cable at length ordered (optional) O-PoE package contains: O-PoE Mast/wall mounting kit plus mounting instructions
2.4
The following is a list of the equipment required for installing the Airmux-200 hardware: Two RJ-45 connectors and an RJ-45 crimp tool (if pre-assembled ODU/IDU cable is not used) Drill (for wall mounting only) ODU grounding cable 12 AWG IDU grounding cable 18 AWG ODU-IDU cable (outdoor class, CAT-5e, 4 twisted pairs, 24 AWG) For PoE based links: A crossed Ethernet LAN cable O-PoE 10 AWG grounding cable, if applicable BDU grounding cable 18 AWG, if applicable 13 mm () spanner/wrench Cable ties Sealing material Laptop running Windows 2000, XP Pro , Vista or 7.
2-5
2.5
Installation Sequence
Install the Airmux-200 system according to the following the steps: 1. Survey the site. 2. Mount ODUs at both sites of the link. 3. Mount external antennas (if necessary). 4. Mounting the lightning protection devices (if used). 5. Assemble the ODU cable and connecting ODU to IDU or O-PoE at both sites. 6. Connect the power. 7. Align the ODUs. 8. Install the management program on the network management station. 9. Run the installation wizard from the management program. 10. Connect user equipment to the local and remote IDUs.
2.6
This section explains how to survey the site intended for Airmux-200 installation.
2-6
Site Survey
Airmux-200 wireless links must be planned before installation. The designated installation site must be appraised to determine that the wireless system is able to operate efficiently and provide connectivity without signal degradation. Airmux-200 offers a wide operating frequency range. A free frequency channel must be determined within the operating range, for optimum performance. Recommended equipment: Stage 1 (preliminary survey) Topological map of the area Urban map of the area Compass Stage 2 (physical survey) 100 meter tape measure Ohmmeter, to check ground connection Binoculars Map Digital camera Paper, pencil, and a clipboard GPS device (optional) Compass (optional) Stage 3 (RF survey) Spectrum analyzer with Max Hold function and screen capture facility that can store multiple images, for documentation purposes RF accessories (connectors and cables) Communication devices (for example, cellular phones, or a set of walkie talkies).
2-7
Note
It is advisable to go on a clear day, so you can more easily see any obstructions between the two sites.
To perform a physical survey: 1. From the compass readings taken in the preliminary survey, find the azimuth (horizontal position) that the ODU should face towards the second ODU. 2. Using binoculars, locate any obstructions such as tall trees, high buildings, hills or mountains. Look for other RF towers between the two sites. Mark the locations of the obstructions on the map. 3. Determine the location for the ODU (having regard for existing rooftop installations and tower space). It should be above any obstructions, considering the Fresnel zone (see Appendix C).
2-8
4. If you need to install the ODU on a tower, make sure that the tower is far away from overhead electric power lines. 5. Determine a location for the indoor equipment; it should be as close as possible to the ODU. At an existing site, there is probably an equipment room with cable-routing channels.
Note
The IDUODU cable length limit is 100m, in accordance with IEEE 10/100BaseT requirements.
6. Measure and record the path length of the cable from the ODU position to the indoor equipment room. 7. Determine the ground and lightning connection points of the installation. The Airmux-200 ODU and IDU must both be grounded. 8. Using the ohmmeter, measure and record the resistance of the required installation to the grounding point. The resistance must be less than 1O ohm. 9. Review the results of the physical site survey. Decide if the site is suitable for the Airmux-200 wireless network installation. If the site is suitable, continue with stage 3, the RF survey If the site is not suitable, survey another site.
Note N t
It is possible to install the Airmux-200 link and use the Airmux Manager to find a clear channel. Each frequency channel can be evaluated in turn. Achievement of a clear channel is indicated by the Quality bar on the Channel Setting window becoming green.
To avoid or minimize interference, follow these recommendations: For collocated RAD units, use an HSS unit to synchronize between them. Select a different operating channel for each collocated RAD unit.
2-9
If one or more collocated units are not RAD units, ensure that there is a physical separation of at least three meters between a RAD unit and any other collocated radio on the site. Use the largest possible frequency gap between these units. Choose the best frequency channel (as clear as possible form interference). You may change band with Combo Airmux-200 products and all Airmux-400 products). To select a frequency channel, move the link to Installation Mode (using Site configuration) and start the Installation wizard. In the Channel Settings window, use the quality bar at the bottom to help you choose a better channel (clearer of interference). If you are using Airmux-200 radios, install the collocated links with different antenna polarizations. If you are using the Airmux-400 radios, use the Spectrum View tool to find the best working channel (Tools > Spectrum View). Decreasing the Tx power of a link reduces collocation interference (Site Configuration > Air Interface).
Note
Use the Link Budget Calculator to determine the minimum Tx Power required to maintain link stability.
2.7
The ODU is the transmitting and receiving element of the Airmux-200 system. The ODU or O-PoE can be mounted on a mast or a wall. In both installations, the supplied mounting kit is used to secure the ODU. Appendix B describes the mast/wall installation instructions. An Airmux-200 link operates in pairs of two ODUs with the same configuration. Both ODUs must be installed, and the antennas aligned for maximum throughput. Prior to connecting cables to the ODU, the protective earth terminal (screw) of the ODU must be connected to an external protective ground conductor or to a grounded mast. For an O-PoE the grounding cable must be connected to an external protective ground conductor or to a grounded mast via the mounting ear of the O-PoE. Only a qualified person using the proper safety equipment should climb the antenna mast. Only trained professional installers should be used when installing or dismantling ODUs and masts. To mount the ODU or O-PoE: 1. Verify that the ODU or O-PoE mounting brackets are properly grounded. 2. Mount the ODU unit onto the mast or wall. Ensure that the connectors are at the bottom. (If the connectors are mounted upwards, water can enter the enclosure causing damage.) For ODU mounting instructions, refer to Appendix B.
2-10 Mounting the ODU or O-PoE Airmux-200 Ver. 1.9.3
Warning
3. Connect the ground cable to the chassis point on the ODU. 4. Attach the ODU-IDU cable to the ODU RJ-45 connector. If making your own ODU-IDU cable, refer to Appendix A for the connector pinout. 5. Secure the cable to the mast or brackets using UV-rated cable ties. 6. Repeat the procedure at the remote site.
Note
Do not tightly secure the ODU to its mounting brackets until the alignment process of the antenna is complete. When installing the ODU, check that there are no direct obstructions in front of the ODU or interference from man-made obstacles.
Caution For O-PoE, UL listed parts and components must be used for installation. Use UL
listed devices having an environmental rating equal to or better than the enclosure rating to close all unfilled openings.
2.8
The supplied mounting kit is used to mount the antenna onto a pole. The antennas must be aligned for maximum throughput. Do not stand in front of a live antenna.
Warning
To mount an external antenna: 1. To mount an external antenna, ensure that the antenna is properly grounded and then mount the antenna onto the pole. Refer to Appendix B for detailed antenna mounting instructions. 2. Follow the mounting instructions supplied with the antenna.
2.9
The use of lightning protection is dependent on regulatory and end user requirements. The Airmux-200 ODU is designed with surge limiting circuits to minimize the risk of damage due to lightning strikes. RAD recommends the use of additional surge arrestor devices to protect the equipment from nearby lightning strikes. Refer to Appendix D for detailed installation instructions of lightning protection devices.
2-11
2-12
Figure 2-6. Airmux-200 Outdoor PoE (O-PoE) Note Panels may be fitted with different connector combinations than shown, depending on the model ordered.
2-13
Graphics: Card and monitor that support 1024 768 screen resolution with 16 bit color Microsoft Explorer 5.01 or later.
To install the Airmux-200 management program: 1. Insert the CD-ROM into your CD-ROM drive. 2. The autorun feature starts to install the software automatically. If the installation does not start automatically, run setup.exe. 3. Follow the on-screen instructions of the installation wizard to complete setup of the Airmux-200 management program in the desired location. Any PC running the Airmux-200 management application can be used to configure Airmux-200 units.
Warning
Any interruption of the protective (grounding) conductor (inside or outside the instrument) or disconnecting of the protective earth terminal can make this unit dangerous. Intentional interruption is prohibited.
2-14
Connecting to Power
To connect AC power to an IDU-E: 1. Connect the power cable socket to the power connector on the Airmux-200 front panel. 2. Connect the power cable plug to the mains outlet. The unit turns on automatically upon connection to the mains. To connect DC power to an IDU-E A special IEC 60320 adapter for-48 VDC power connection is supplied with the unit.
The unit will be turned on automatically upon connection to the mains. To maintain Overvoltage (Installation) Category II, install a suitable surge suppressor device in the branch circuit to limit expected transients to Overvoltage Category II values. The limits are based on IEC60664 and are also located in Table 2H of UL60950. For mains of 150V, the transient rating is 1500V. For mains between 150V and 300V, the transient rating is 2500V. For mains between 300V and 600V, the transient rating is 4000V.
Warning
Warning
2. The ODU starts beeping 20 seconds after power up, and continues beeping until the antennas are aligned, and the installation is complete. 3. Verify normal operation of the IDU by the LED indications on the front panel. (See Chapter 3.)
2-15
4. Coarsely align the site B antenna in the direction of the site A antenna. 5. Make an azimuth sweep of 180 degrees with the site A antenna. So that the strongest signal from site B can be detected. 6. Slowly turning the site A antenna back towards the position of site B, listen to the beeps until the best signal is reached. Figure 2-8 indicates the beeper signals with the black representing the beeps.
Figure 2-7. Beeper Sequence for Antenna Alignment Three beeps and a pause indicate the best signal. Two beeps and a pause, indicates signal quality has increased. One beep and pause indicates no signal change. Any other sequence detects no signal between the ODUs.
7. Secure the site A antenna to the mast or wall. 8. At site B, adjust the antenna slowly while listening to the beeper sequence until the best signal is attained. 9. Secure the site B antenna to the mast or wall. 10. Monitor the link quality for about 15 minutes to verify stability.
Note
2-16
2-17
Caution If you log on using Local Connection, but your physical connection is not local
(i.e. anything other than a direct connection between the managing computer and the IDU), then any configuration you carry out may affect other links in the network. You will not be able to do this!
If you log in via an over-the-air IP address, you will receive a warning. If you reset the site to which you are connected to factory settings, you can lock yourself out of the link. Network login (IP address to the ODU) is recommended.
Note
If you log on using Local Connection through a PoE device, you will need to connect it to the managing computer using a crossed Ethernet cable. The default IP address for the ODU is 10.0.0.120. The subnet mask is 255.0.0.0. The actual IP address is defined during link configuration (see Chapter 4).
7. Select your user type:
Installer
Read-Write
Note
Note
Airmux-200 is protected with Community passwords. A user may be defined with read-only permission or with read-write permission (see Chapter 4 for more details).
2-18
Figure 2-10. Login Screen with Community Options Visible Note With BRS and 5.4 FCC/IC systems the link must be activated at both sites when installing for the first time. A red Inactive Link box appears in the center of the Manager screen. Activation is performed later.
8. Click OK to log in. The Airmux Manager main window is displayed (see Figure 2-12).
2-19
Login Errors
This section describes problems that may occur during login.
Unsupported Device
Attempting to connect to an unsupported device results in the following error message:
Incorrect IP Address
If the IP address chosen is invalid or the link is unreachable, the following error message will be displayed:
2-20
Incorrect Password
If you type an incorrect password in the Login screen, a warning graphic displayed alongside the password field. is
Note
2-22
2-23
Figure 2-17. Installation Wizard, System Dialog Box with Default Settings
To configure system parameters: 1. Enter a Link ID. The link ID must include at least eight alphanumeric characters. Up to 24 characters are allowed.
Note
Both sides of a link must have the same link ID for data transmission to take place.
2. Enter a Link Name for the link identification. 3. Enter a name for site 1. 4. Enter a name for site 2. 5. Enter the Link Password (version 1.400 and after). See Changing the Link Password for details on the Link Password.
Note
It the Link Password is incorrect a link is established but configuration cannot be performed and no services are available. A new link password may be obtained from Technical Support or use the alternative password supplied with the product. See Changing the Link Password for more details.
2-24
Figure 2-18. Installation Wizard, System Dialog Box, Fields are Filled Out
6. Click Next. The default link with a rate of 6.5 Mbps is evaluated. The Channel Setting dialog box appears. This dialog box may be different according to the version that you have purchased.
Note
2-25
Note
A link password must contain at least eight but no more than 16 characters
Selecting Channels
Airmux-200 has a feature called Automatic Channel Select, which allows you to define several alternative frequency channels if interference is detected on the channel in use. In the event of sync loss, ACS chooses the first available channel in a list of monitored channels nominated in the Channel settings window. A channel switch takes place sufficiently fast as to ensure no loss of service.
2-27
Figure 2-23. Channel Select Dialog Box, Selecting Channel Bandwidth Note ACS is only supported for a Channel Bandwidth of 20 MHz.
3. Click the check box if Automatic Channel Selection is required.
2-28 Installing the Link Airmux-200 Ver. 1.9.3
4. Click the check boxes in the Available Channels List of all the allowable channels that can be automatically selected. Selecting a new channel causes the system quality to change. The Quality bar provides an indication of the link quality from No serv(ice) (red) to Ethernet + TDM (green)
Quality Service
0.1%0.4%
8099%
TDM + Ethernet
0.4%2.0%
7756%
Ethernet
2.0% 50.0%
442%
2-29
Configuring Services
Airmux-200 supports Ethernet and TDM services, which are configured via the Services dialog box.
2. Select a TDM service type: E1 or T1. TDM Ports section becomes available.
Figure 2-27. Link Installation Wizard, TDM Services Dialog Box, TDM Ports are Available
3. Select active TDM ports: Use Select spin box to choose consecutive service ports or Click Select Maximum to choose all TDM port available for current air interface capacity or Click individual ports to choose them.
Note
Ethernet service is always selected. The number of available services is changed in accordance with actual air
interface capacity.
The selected ports are enabled for both sides of the link. You cannot for
2-31
Figure 2-28. Link Installation Wizard, TDM Services Dialog Box, Seven TDM Ports are Selected
4. Click OK. The Services dialog box is updated to reflect your choice.
Figure 2-29. Installation Wizard, Services Dialog Box with Services Added
5. Select the required transmission rate. If Adaptive is selected Airmux-200 constantly monitors and adjusts the transmission rate to ensure maximum throughput for the link at the highest quality. Airmux-200-L versions are preset to adaptive and the rate selection is disabled.
2-32
5 MHz 2.25 Mbps 3 Mbps 4.5 Mbps 6 Mbps 9 Mbps 12 Mbps 13.5 Mbps
64QAM /
2-33
To configure TDM jitter buffer size: 1. Click the TDM Jitter Buffer tab. The TDM Jitter Buffer Configuration dialog box is displayed.
Caution Use extra caution when decreasing the jitter buffer value, since the interference
may affect service quality. In cases of asymmetric interference, the jitter buffer can be set to different values per site. In such cases the latency will also be asymmetric.
Note
If you wish to decrease the number of TDM services, you cannot simultaneously change the Jitter Buffer size, since the Evaluate function is blocked. Complete the wizard, and then re-enter it to change the jitter buffer size. Alternatively, you can:
Change the jitter buffer size, evaluate and then change TDM services. Add TDM services, evaluate and then change the jitter buffer size.
2-34
Transparent/Transparent Airmux-200 transparently regenerates the clock from line clock side to Tx clock on the opposite side of the link. Loop time/Recover The local unit receive clock is the transmit clock on both sides of the link. Recover/Loop time The remote unit receive clock is the transmit clock on both sides. Internal/Recover The local unit internal oscillator generates the clock while the remote unit recovers this clock. Recover/Internal The remote unit internal oscillator generates the clock while the local unit recovers this clock.
Note
2-35
Figure 2-32. TDM Parameters Dialog Box Note This dialog box is available only with IDU units, it is activated after TDM service was chosen in the previous Service dialog box. In Ethernet only services, the TDM dialog box does not appear.
2-36
2-38
Figure 2-39. Main Window of the Manager after Installation with Loaded Trunks
Airmux-200 Ver. 1.9.3 Installing the Link 2-39
When the wireless link is established between the site A and site B units, the Quality bar is within the yellow area for Ethernet only links, or within the green area for Ethernet plus TDM links. 5. Verify that the Radio Signal Strength (RSS) is according to expected results as determined by the Link Budget Calculator.
Notes
Do not connect two LAN ports to the same LAN, or flooding may occur.
To connect to Ethernet equipment with electrical interfaces: Connect Airmux-200 to the hub/router using standard UTP cable. Use a straight cable for router connection.
To connect to Ethernet equipment with fiber optic interfaces: Connect Airmux-200 to the hub/router using a fiber optic cable with LC connectors.
2-40
Chapter 3 Operation
This section provides the following information for Airmux-200: Operating procedures (turning-on and turning-off) IDU indicators Normal indications Default settings Managing the Airmux-200.
3.1
To turn on Airmux-200: Connect the AC/DC converter to the IDU power connector and to the mains. See Chapter 2 for full instructions on connecting the power. The PWR indicator lights up (IDU only) and remains lit as long as the IDU is receiving power. Airmux-200 requires no operator attention once installed, with the exception of occasional monitoring of front panel indicators and statistics data. Intervention is only required when Airmux-200 must be configured to its operational requirements, or diagnostic tests are performed.
3.2
3-1
Chapter 3 Operation
Figure 3-2. Airmux-200-AIND All Indoor Radio Unit Table 3-1. Front Panel LEDs
Name IDU Color Green Orange Red ODU Green Red LINK Green Orange Red SERVICE Green Orange Red Description IDU operational During power-up only Failure ODU-to-IDU communication link is operating ODU-to-IDU communication link is disrupted Wireless link is synchronized During installation only Wireless link lost synchronization E1/T1 line is synchronized Alarm detected on Site B interface or a loopback is active Alarm detected on Site A interface Off Ethernet-only IDU or TDM interface has not been configured yet HSS Green On The ODU is HSS master, generating signal, and synchronization is OK Blinking The ODU is HSS client and synchronization is OK Red Orange HSS not operational due to improper signal detection. This ODU is not transmitting HSS is operational. One of the following conditions apply: This ODU is a master that is generating and detecting signals This ODU is a master that is generating signals, but detected improper signals This ODU is a client Continue Tx, but is not detecting signals This ODU is a client Disable Tx and is detecting signals from multiple sources Front panel Front panel Front panel Front panel Location Front panel
All orange cases transmit. Off HSS is not active or ODU is disconnected from IDU PWR LINK ACT Green Green Yellow Green On Power supply is ON On Good Ethernet link integrity Blinks according to the Ethernet traffic On TDM service is OK Front panel LAN connector LAN connector TDM connector
3-2
Chapter 3 Operation
Name
Color Red
After turning on Airmux-200, the PWR LED in the IDU front panel lights to indicate that Airmux-200 is on. Table 3-2 shows the correct status of the indicators at power-up.
If the above LED indications do not appear following initial power turn-on, see Chapter 5 for diagnostic test instructions.
3.3
Default Settings
Table 3-3 lists the default settings of the Airmux-200 configuration parameters. Table 3-3. Default Settings
Parameter Description Default Value Menu Path Setting Instructions Defining the Management Addresses Defining the Management Addresses Selecting Channels Configuring Service Parameters Configuring Ethernet Mode
ODU IP Address
IP address of the ODU IP address of the ODU Operation channel frequency Transmission rate Line speed and duplex mode negotiation
10.0.0.120
Management
Subnet Mask
255.0.0.0
Management
Default Settings
3-3
Chapter 3 Operation
Parameter
Description
Default Value
Menu Path
Setting Instructions IDU Aging Time Configuring SNMP Communities Configuring SNMP Communities Configuring SNMP Communities Configuring Jitter Buffer
MAC address aging period Read-write community name Local-public community name Remote-public community name Jitter buffer size
Services
3.4
The Airmux-200 configuration and monitoring operations are performed using one of the following tools: GUI-based management utility Telnet.
Most of the Airmux-200 management and operation parameters are set using link configuration wizard. If necessary, the local and remote unit parameters can be reconfigured via the Airmux-200 management utility. Telnet management is performed from a Telnet host using display and set commands. The capabilities of the two options listed above are identical.
3-4
Chapter 3 Operation
File Menu Log off, and exit Configuration use for link configuration, individual site configuration or link installation Tools set performance monitoring, event log handling, change password and preferences Maintenance Loopbacks, system reset
Airmux-200 Ver. 1.9.3 Configuration and Management Alternatives 3-5
Chapter 3 Operation
Help Airmux Manger help Link details pane summarizes information on the radio frequency, IP bandwidth, type of TDM service, number of assigned E1 or T1 timeslots.
The two lower left panels show basic link site details:
Monitor Pane displays the link quality between local and remote devices and the following statistics: Radio signal strength (RSS) in dBm
Current Ethernet bandwidth in Mbps. This is not the actual traffic rate, but the maximum capacity that can be supported currently, see Figure 3-4. The scale on the bar adjusts according the link distance and the link budget.
3-6
Chapter 3 Operation
Local/remote receive and transmit traffic rate, in Mbps or Fps (frames per second). TDM service
The title bar enables you to switch between Accumulative and Current view. Immediately below the title bar is displayed the Estimated Time Between Errors. It is zeroed by the Clear Counters button in the tool bar. Error block count is shown immediately above the active TDM channels display. The color of the TDM ports reflects their current status: Green Operational Red Error: LOS for loss of signal and AIS for Alarm Indication Signal Yellow loopback TDM service: IDU E/R
Immediately below the title bar is displayed the Estimated Time Between Errors. It is zeroed by the Clear Counters button in the tool bar. For each Trunk the line status and Error block count is displayed. It is zeroed by the Clear Counters button in the tool bar. The line status is color coded and may be one of: Green Normal Red Error: LOS for loss of signal and AIS for Alarm Indication Signal Yellow loopback Frequency box. Shows the channel frequency. The color of the box indicates the status.
Chapter 3 Operation
Red is an inactive link Magenta shows an authentication or compatibility problem Brown shows severe compatibility problem Events Log stores alarms generated by local and remote units.
Connectivity icon showing how the device is connected to the Ethernet. Over-the-Air connection using the IP address of the remote unit Local connection direct connection to the IDU without using an IP address Network connection - through a LAN ODU is unreachable Encryption icon showing if the link is encrypted: Encrypted link Unencrypted link - lock open Link Password Validation failed. The link is encrypted with default keys. Service and configuration is unavailable. Need to change the link password in either site Link Lock: Link Lock is enabled Link Lock is encrypted Link Lock mismatch Ethernet ring member DFS in use Active alarm is present TDM Backup (IDU-R) TDM backup is enabled TDM backup is disabled Ethernet bandwidth indication
3-8
Chapter 3 Operation
Figure 3-5. Over the Air Connection Note Over the air connection to remote unit is not recommended
To change link configuration parameters: 1. In the Main menu, click Configure Link. The Configure Link wizard appears. See Chapter 4 for configuration details. 2. Click Next. 3. Continue through the configuration wizard and define the Link name and ID, Channel, Rate and Services. 4. Once you finish changing configuration parameters, click Finish. The system takes a few seconds to activate the link with the new configuration.
3-9
Chapter 3 Operation
3.5
Typically, the Telnet host is a PC or a Unix station with the appropriate suite of TCP/IP protocols. The login name is admin and the login password is identical to the community strings. Read/write allows using display and set commands (default value is netman). To enable Telnet access: 1. Display Protocol tab of the Management menu (Site Configuration > Management). 2. Enable Telnet access by ticking the Telnet check box.
Figure 3-6. Enabling/Disabling Telnet Access Table 3-4 lists the Telnet commands supported by Airmux-200. Table 3-4. Telnet Commands
Command display inventory Description Display ODU product name, name, location, hardware and software revisions, uptime, MAC address, IDU product name, IDU software and hardware revisions
3-10
Chapter 3 Operation
Command display management display link display Ethernet display rfp display ratio display tx_phase display gpsinfo display tdm display ntp display PM <interface:AIR,LAN1,LAN2,TDM1,TDM2,TD M3,TDM4> <interval:current,day,month> set ip <ipaddr> <subnetMask> <gateway> set trap <index:1-10> <ipaddr> <port:0-65535> set readpw <oldpasswd> <passwd> set writepw <oldpasswd> <passwd> set trappw <oldpasswd> <passwd> set buzzer <mode:0=OFF,1 =ON> set tpc<power:Value between minimal TX power, and maximal TX power> set bridge <mode:0=Bridging OFF, 1= Bridging ON > set name <new name> set location <new location> set contact <new contact> set Ethernet <port: MNG,LAN1,LAN2> <mode: AUTO,10H,10F,100H,100F, DISABLE> set rfp <index> (2-6) set ratio <ratio> set tx_phase <mode:1=normal,2=shifted>
Description Display IP, subnet, gateway, traps table Display state, SSID, channel BW, RSS, TSL, frequency/ACS, DFS, rate/ARA, distance Display bridge mode, aging time, port table (state, status and action) Display RFP for GSU Display transmission ratio for GSU Display transmission phase for GSU Display GPS information for GSU Display clock mode, master clock mode, current clock, quality[1], TDM table (line status, error blocks) Display time, server and offset Show the performance monitor tables for each interface according to user defined monitoring intervals Set the ODU IP address, subnet mask and gateway The user must reset the ODU after the command completion Set a specific trap from the traps table (set trap 3 10.0.0.133 162) Set the read access password (read community) Set the read-write access password (read-write community) Set the trap community string Toggle the buzzer mode (0 off, 1 on) Set the ODU transmit power. If a wrong value is entered, both min and max values shall be displayed in the error reply Set the ODU bridge mode (0 off, 1 on) Set the name of the link Set the name of the location Set the name of the site manager Set the mode and speed of each ethernet port
Set RFP for GSU Set transmission ratio for GSU Set transmission phase for GSU
3-11
Chapter 3 Operation
Command reboot
Description Reset both the IDU and the ODU. The user shall be prompt that the command will reset the device and that he/she has to restart the Telnet session. Displays the available commands
help
Figure 3-7 shows the available Telnet commands via the Help command.
Hello admin, welcome to ODU Management CLI! +-----------------------------------------------------------+ Software Revision 1.770_b1115_Aug 13 2007 +-----------------------------------------------------------+
admin@10.103.6.1-> help display inventory display management display link display ethernet display tdm display ntp display PM <interface:AIR,LAN1,LAN2,TDM1,TDM2,TDM3,TDM4> <interval:current,day,month> set ip <ipaddr> <subnetMask> <gateway> set trap <index:1-10> <ipaddr> <port:0-65535> set readpw <oldpasswd> <passwd> set writepw <oldpasswd> <passwd> set trappw <oldpasswd> <passwd> set buzzer <mode:0=OFF,1 =ON> set tpc <power:Value between minimal TX power, and maximal TX power> set bridge <mode:0=Bridging OFF,1= Bridging ON > set name <new name> set location <new location> set contact <new contact> set Ethernet <port:MNG,LAN1,LAN2> <mode:AUTO,10H,10F,100H,100F,DISABLE> reboot help Command "help" finished OK.
3.6
To turn off Airmux-200: 1. Exit the management application. 2. Remove the Airmux-200 power cord from the mains.
3-12
Chapter 4 Configuration
This chapter describes configuration procedures, which are performed after the physical installation of the local and remote Airmux-200 units and the Installation Link wizard has been performed. The following parameters are configured via the Configuration Wizard: System parameters Frequency channel Air interface rate Service parameters TDM Hub site synchronization.
The following parameters are configured via the Configuration dialog box. Transmit power Management and trap addresses Bridge mode Ethernet mode VLAN management Community values.
Note
4.1
The link configuration wizard is used to redefine the link configuration parameters if necessary. Both sites in the link are defined simultaneously.
Note
All parameter changes are automatically applied to both sides of the link.
To change general parameters: 1. In the Main menu, click the Link Configuration button.
4-1
Chapter 4 Configuration
Chapter 4 Configuration
4. In the System dialog box, enter the new data for the link. All fields with a white background can be edited. 5. Click Next. The Frequency dialog box appears.
Selecting Channels
The user is required to define the operating frequency channel. Procedure for selecting channels is the same as during the link installation process, see Selecting Channels in Chapter 2. Automatic Channel Select enables Airmux-200 to change frequency channels automatically if the quality of the current operating channel deteriorates.
4-3
Chapter 4 Configuration
4-4
Chapter 4 Configuration
Ring Protection Link as described above Ring Link any member link controlled by the RPL Independent Link not subject to ring protection Ring Protection Message (RPM) control message used to monitor and control the ring.
Note
associate the RPL and member Ring Links with a VLAN ID. This requires in turn, that equipment used in the ring either supports VLAN or can transparently pass through VLAN tagged packets.
It is recommended to use different VLANs for user, management and ring
traffic.
Chapter 4 Configuration
Ethernet traffic runs in the ring, but does not pass through the RPL, which is blocked. The RPL does however, broadcast RPM packets through the ring. 2. Ring Link down, RPL notified The RPL detects a link-down condition by the non-arrival of an RPM packet. It remains blocked for the Minimum time for failure detection which is configurable using the Airmux Manager. 3. Ring Link down, RPL unblocked for traffic The RPL unblocks for Ethernet traffic after the Minimum time for failure detection expires and no RPM message has been received. 4. Ring Link restored but still blocked for traffic The Ring Link is restored, but remains blocked for the Minimum time for recovery, set using the Airmux Manager, to avoid rapid fluctuations leading to potential short term loops. 5. Ring Link restored, blocked, RPL blocked for traffic The RPL blocks to Ethernet traffic after the Minimum time for recovery expires and restores Ethernet traffic to the Ring Link (with a special RPM packet). Return to 1. Ring Link restored, RPL blocked The ring is back to normal operation. Ring Protection solution prevents Ethernet loops in the ring at all times. The ring is always broken somewhere. Under a ring configuration a RAD Ring Link that was down and commences recovery, keeps blocking Ethernet traffic. The RPL identifies this situation, blocks itself and then unblocks the other Ring Link. This is the transition from step 4 to 5 in Figure 4-5. If the failed hop is not a RAD link then there are two possibilities: If the hop Ring Link can signal that it is down by issuing a Loss of Signal (LOS) at the Ethernet port, then the RPL will control the RAD link connected to that port in the same manner as described above, to prevent an Ethernet loop. Otherwise, there may be a short loop period when the RPL is still open for traffic and the Ring Link is also unblocked during the Minimum time for recovery.
4-6
Chapter 4 Configuration
Dual-homed ring. Two adjacent nodes are connected through a non-RAD link (for example, microwave or fiber):
Note
The network has to be layer 2 and support VLANs. The ring control broadcasts RPM packets. Hence it is recommended to prevent
Repeater sites. Some of the hops are connected through RAD links with PoE devices, not supporting ring functionality:
4-7
Chapter 4 Configuration
Note
A RAD link hop can be a part of up to 4 rings. The RPL cannot be a shared link. The two RPLs should use different Minimum Time for Activation values to
Protection Switching
Protection switching occurs upon failure in the ring. The Ethernet service restoration time depends on the number of hops in the ring. With four hops the Ethernet service is restored in less than 50 ms. In single and dual homed topologies the service restoration may take longer due to the aging time of the external switches. Switches that are immediately aware of routing changes reduce the restoration time.
Hardware Considerations
Ethernet Ring Protection is supported by the IDU, IDU-E and PoE. A typical Ring Protection Link consists of an IDU or IDU-E, a PoE and two ODUs as shown in Figure 4-6. Hence one end of the RPL and of ring controlled links, as shown in Figure 4-6 has to be an IDU. It is recommended to have an IDU at each node to have the flexibility to change the RPL. A ring node is built from two ODUs from adjacent links. The ODUs can be connected to either an IDU or to a PoE device as in Figure 4-6. Port names in the IDU are shown.
4-8
Chapter 4 Configuration
Figure 4-6. Node with IDU and PoE Device Note Connect the switch at the site only to one IDU.
The switching function is carried out by the IDUs, which provide Layer 2 support.
4-9
Chapter 4 Configuration
Figure 4-8. Using IDU-C or IDU-E with PoEs for the RPL
Notice that link content drops from four PoEs plus two switches to two PoEs and two IDUs.
Note
The Ring uses a VLAN ID for the RPL. It is used to manage the Ring and
nothing else; it is completely separate from the management and traffic VLANs referred to elsewhere.
A regular Ring Link may be a member of up to four rings and each of their RPL
4-10
Chapter 4 Configuration
4-11
Chapter 4 Configuration
4-12
Chapter 4 Configuration
When the RPL cuts in as a result of a failure, the Ethernet (Blocked) notice disappears. The Ethernet Services bar indicated that the RPL is active:
Upon restoration of the broken link, the RPL returns to idle status with the appropriate indications on the Airmux Manager main window. On the status bar for all ring member links, you will see the ring membership indicator icon:
Note
Do not configure more than one RPL. If you do, you will break the Ring. If you forget to configure one RPL in a ring, you will introduce a loop into your
network.
Figure 4-13 shows a simple cascaded link with two hops. The trunk to backed up
is shown as Trunk2, from IDU A to IDU B. The first hop is from ODU A to ODU A. The second is from ODU B to ODU B.
Note
If ODU A and ODU B are sited close together, they may require collocation.
4-13
Chapter 4 Configuration
4-14
Chapter 4 Configuration
A Video Surveillance (VS) link consists of a base ODU transmitting at 2 Mbps connected by a PoE device. The camera site uses a PoE connected ODU transmitting at 5 Mbps. Installation, configuration and maintenance of a VS link is substantially the same as for a regular PoE-based link. VS links are readily collocated using RADs HSS system, so that a single base mast can accommodate up to 16 camera stations.
4-15
Chapter 4 Configuration
4-16
Chapter 4 Configuration
Caution After completing the link setup, change the default IP addresses of the ODUs (see Defining the Management Addresses section below.
4.2
You can edit the configuration parameters for each site individually without running a wizard. From the Configuration dialog box, (see Figure 4-19) the following functions are available by selecting the items on the left of the dialog box: System Air Interface HSS Management Inventory Edits the contact person and location details. Views the system details Changes the transmit power Configures the HSS parameters Configures the IP address, subnet mask, default gateway, and the trap destination, VLAN ID. Views the hardware and software inventory.
4-17
Chapter 4 Configuration
Changes the community values, the link password and the link lock Sets the date and time of the server and of the system. Configures the bridge, define the LAN connection, configures TDM services, set the external alarm inputs and restore the unit to the factory settings.
From the Configuration dialog box, the following functions are available by clicking the buttons at the top of the dialog box: Backup Restore Refresh Save a backup.ini file with the current configuration. Load the backup.ini file created by the backup. Refresh current panel with latest values
Installation Mode Return to Installation Mode for the entire link. Selecting the Mute check box before clicking the Install Mode button mutes the beeper. Buzzer Mutes the beeper at startup. Reactivates the beeper during alignment.
To configure the sites: 1. Click Configuration from the main menu. 2. Select which site to configure. The Configuration dialog box opens (see Figure 4-19).
4-18
Chapter 4 Configuration
Note
If performing configuration from the Airmux Manager, the IP address is entered in the login screen.
5. Enter the subnet mask. 6. Enter the default gateway. 7. Enter the trap destination. This is the IP address of the PC running the management application. The event log will be stored at this address. 8. Click Apply to save the changes.
4-19
Chapter 4 Configuration
Notes
The Installation mode button opens the Link Installation wizard to reinstall the link. This option must be used only when the radio link is operational. Activation of the installation mode without an active radio link results in a loss of connectivity between two units. The Backup and Restore buttons are for saving and restoring the configuration files.
Note
It is recommended to use different VLANs for user, management and ring traffic.
To enable VLAN management: 1. Click Configuration from the main menu. 2. Select the site to configure. 3. Select Management. 4. Open the VLAN tab. 5. Check the Enabled box. 6. Enter a VLAN ID. After entering the VLAN ID, only packets with the specified VLAN ID are processed by the ODU. This includes all the protocols supported by the ODU (ICMP, SNMP, Telnet and NTP). The VLAN priority is used for the traffic sent from the ODU to the management workstation. VLAN management affects all types of management connections (local, network, and over-the-air). 7. Enter a Priority number. 8. Click <OK> to save the settings.
4-20
Chapter 4 Configuration
Figure 4-21: Configuring VLAN Settings When this parameter is changed, it causes the management application to immediately disconnect. In order to avoid problems, verify the change by setting the VLAN on only one ODU. Only after proper VLAN network operation is verified, the other VLAN setting can be changed.
To troubleshoot VLAN problems: If the VLAN ID is forgotten or no VLAN network is connected to the ODU: Reset the device. In the first two minutes, neither the VLAN nor any VLAN connections are available.
Warning
The community string must be entered at login. The user must know the password and the correct community string in order to gain access to the system. A user may have read-only privileges. It is not possible to manage the ODU if the read-write or the read community values are forgotten. An alternative community key may be obtained from technical support for the purpose of setting new community; the MAC address of the ODU must be supplied. A new community string can be set if necessary. The read-write community and read-only community have a minimum of five alphanumeric characters. (bru1 and bru4097 are not permitted). Changing the trap community is optional by clicking the check box.
Airmux-200 Ver. 1.9.3 Configuring the Sites 4-21
Chapter 4 Configuration
To change a community: 1. From the Configuration dialog box, select the Security tab 2. Type the current read-write community (default is netman). 3. Select the communities to be changed by clicking the check box. 4. Type the new community and re-type to confirm. A community string must contain at least five and no more than 32 characters excluding SPACE, TAB, and any of >#@|*?;." 5. Click OK to save.
Chapter 4 Configuration
If both the read-write community and the alternative community key are unavailable, then an alternative community key can be obtained from customer support using the ODU MAC address. The MAC address is displayed in the Site Configuration Inventory tab. When you have the alternative community key, click the Forgot Community button and enter the Alternative Community (Figure 4-23). Then reconfigure the read-write community string.
4-23
Chapter 4 Configuration
Figure 4-24. Changing the Transmit Power Table 4-1. Typical Transmit Power Configuration Limits
Regulation Version Min Tx [dB] FCC F58 F58/EXT F53 F53HP ETSI F54 F54-HG/EXT 4 4 4 4 2 -3 Max Tx [dB] 16 16 8 16 8 3 MaxTx at 36 Mbps [dB] 14 14 8 14 8 3 MaxTx at 48 Mbps [dB] 10 10 8 10 8 3 Power Control
If the Current dBm exceeds the Expected dBm, a Tx Power Limits guide is displayed:
4-24
Chapter 4 Configuration
As soon as the Expected dBm falls within the required range a confirmation window is displayed:
6. Click Yes to accept. The change is effected with a short deterioration of link quality.
Note
The minimum value is 64 Mbps. The maximum value will be the minimum between Z above and 18 or
22.5 Mbps.
The MIR setting is independent per direction. To set the Ethernet information rate: 1. From the Configuration menu, select the site to reconfigure. The Configuration dialog box opens. 2. Click Advanced > Ethernet. 3. In the Information Rate pane, use the drop-down menu to select the maximum Information Rate. Select Other to define the throughput with 1 kbps resolution Select Best Effort for the highest information rate possible for the link conditions and settings.
4-25
Chapter 4 Configuration
Note
It is not recommended to configure the port that is used for the management connection, since a wrong configuration can cause management disconnection or Ethernet services interruption.
4-26
Chapter 4 Configuration
To configure the Ethernet mode: 1. From the Configuration menu, select the site to reconfigure. The Site Configuration dialog box opens. 2. Click Advanced > Ethernet. 3. In the Ethernet Ports Configuration pane, use the drop-down menu to select the LAN configuration. 4. Click Apply to save the changes.
Note
It is possible to close the Ethernet service by disconnecting the Ethernet port. (Disable option in LAN port mode configuration) The user should be aware that it is possible to close the port and not have any access to the device. If this should occur the workaround is as follows:
Connect the system from the remote site Connect via other Ethernet port (IDU-E) Power down the equipment and connect immediately after the power up (the
4-27
Chapter 4 Configuration
Hub Mode in Hub mode the ODU transparently forwards the all the packets over the wireless link. Bridge Mode In Bridge mode the ODU performs both learning and aging, the aging time of the ODU is fixed at 300 seconds.
Note
Notes
Any change to these parameters is effective immediately. Each side of the link can be configured separately.
The following list details common configurations; both sides are must be configured with the same parameter. Standard (Default) Configuration for Ethernet Applications with the IDU unit Set IDU aging to 300 seconds, ODU set to Hub mode, Figure 4-27. Standard (Default) Configuration for Ethernet Applications with PoE unit ODU set to Bridge mode, IDU aging is not applicable. Fast aging mode for rapid network topology changes Set IDU aging to one second, ODU set to Hub mode. Hub Mode The ODU is set to HUB mode. IDU aging is not applicable. Ethernet Bridge The ODU is set to Bridge mode. The IDU aging is not applicable.
Configuring VLANs
VLAN tagging enables multiple bridged networks to transparently share the same physical network link without leakage of information between networks. IEEE 802.1Q is used as the encapsulation protocol to implement this mechanism over Ethernet networks.
Note
If you are using a PoE device, this feature is unavailable. You may skip this section.
4-28
Chapter 4 Configuration
Figure 4-28. Two Network Using the Same Link with VLAN Tagging Note Airmux Manager uses the terms VLAN ID and VID interchangeably to denote a VLAN identification number.
4-29
Chapter 4 Configuration
For a frame with a VLAN tag the system will add a tag with VLAN ID and EtherType = 0x9100 so the frame will be double-tagged For a frame with a VLAN tag and a provider tag the system will add a tag with VLAN ID and EtherType = 0x9100 so the frame will be triple-tagged and so on.
VLAN Untagging
VLAN untagging means the removal of a VLAN or a provider tag.
Port Functionality
The VLAN functionality is supported by all LAN and SFP ports in the IDU. Each port can be configured how to handle Ethernet frames at the ingress direction (where frames enter the IDU) and at the egress direction (where frame exit the IDU). The configuration is independent at each port. Ingress Direction Transparent The port does nothing with regard to VLANs, inbound frames are left untouched. Tag Frames entering the port without VLAN or QinQ tagging are tagged with VLAN ID and priority, which are pre-configured by the user. Frames which are already tagged at ingress are not modified.
Egress Direction Transparent The port does nothing with regard to VLANs, outbound frames are left untouched. Untag all All frames are untagged.
4-30
Chapter 4 Configuration
Untag selected VIDs Untags only frames tagged with one of the user defined VIDs. You can define up to eight VIDs per port. Other frames are not modified.
Filtered VLAN IDs at egress This setting allows for mutual filtering of multiple ingress tags not relevant at the egress end.
Provider tagging With provider tagging, the system double-tags egress frames towards the providers network. All frames are tagged QinQ with a VLAN ID, which is configured by the service provider (provider VLAN ID).
4-31
Chapter 4 Configuration
With this setting, ingress frames which are not tagged with the configured provider VLAN ID are blocked (filtered).
Note
Each port can be configured independently to a tagging mode. However, only a single provider VLAN ID can be defined per IDU.
Provider tagging without filtering This setting functions like provider tagging. However, all ingress frames are passed through.
VLAN Configuration
VLAN IDs are used by RAD products in three separate contexts: management VLAN, traffic VLAN and Ethernet ring. It is recommended that you use different VLAN IDs for each purpose. Management Traffic and Ethernet Service Separation You can define a VLAN ID for management traffic separation. You should configure the system to prevent conflicts as detailed below. When configured for the default operational mode, a provider port will handle ingress traffic as follows: Filters frames that are not tagged with the provider VLAN ID Removes the provider double tag
Therefore, if a port is configured for management traffic separation by VLAN and as provider port, then the received management frames must be double tagged as follows: The outer tag has to be the providers tag (so the frame is not filtered) The internal tag has to be management VLAN ID
To avoid mix-ups, best practice is to: Separate the management and data ports Define only a data port with provider function
All IDU models have two LAN ports so you can easily separate management and Ethernet service.
4-32
Chapter 4 Configuration
VLAN configuration is carried out per site. It is up to you to ensure consistency between the link sites. The discussion below is based on Site A, but it also applies to Site B.
Note
Throughout this section, all VLAN IDs must be between 1 and 4094, inclusive. All VLAN priorities must be between 0 and 6, inclusive. The values entered are rangechecked. If for example, you enter a VLAN ID of 4095, then 4094 will be reflected back.
To configure VLAN tagging for Ethernet service: 1. From the Ethernet dialog box (Site Configuration > Advanced > Ethernet), click VLAN Configuration.... VLAN Configuration dialog box is displayed.
Figure 4-31. VLAN Ingress Mode, Setting VLAN ID and Priority for LAN 1
4-33
Chapter 4 Configuration
4. Select egress mode for LAN 1, LAN 2 and SFP ports: Transparent Untag all Untag selected VLAN IDs Provider tagging Provider tagging without filter Filtered VLAN IDs See Port Functionality section above for description of the egress modes. The first two choices, Transparent and Untag all require no further action. Untag selected VIDs causes the eight VLAN ID fields to become available:
4-34
Chapter 4 Configuration
Note
4-35
Chapter 4 Configuration
Changing Passwords
There are two passwords necessary to use the Airmux-200 system. The first is encountered when running the management software, the second, the link Password is used for encryption purposes and is found when installing or configuring the link.
Chapter 4 Configuration
To change the link password: 1. From the Configuration dialog box, select the Security tab 2. Click Change next to the Link Password field box. The Change Link Password dialog box appears. 3. Enter the current link password. 4. Enter the new password. 5. Enter the new password again in the Confirm box.
Note
The NTP uses UDP port 123. If a firewall is configured between the ODU and
the NTP server this port must be opened. (Windows XP command w32tm /stripchart /computer:<server IP> can be use to check the NTP server connectivity).
It can take up to 8 minutes for the NTP to synchronize the ODU date and time. To set date and time: 1. Determine the IP address of the NTP server to be used.
4-37
Chapter 4 Configuration
2. Test it for connectivity using the command (Windows XP), for example: w32tm /stripchart /computer:216.218.192.202 3. Click Configuration from the main menu. 4. Select which site to configure. The Configuration dialog box opens. 5. Select Date & Time (see Figure 4-36).
4-38
Chapter 4 Configuration
3. Click Off to disable the tone. To restore the beeper: 1. Click Configuration in the Menu bar and select the relevant site. The Configuration dialog box opens. 2. In the Configuration dialog box, click the Buzzer button. 3. Select On to have the buzzer beep continuously or Auto to have the buzzer beep only in install mode.
4-39
Chapter 4 Configuration
4-40
Chapter 4 Configuration
4. Click the required Restore type. You are then offered a standard Open File dialog box. 5. From the Open File dialog box, navigate to your backup storage area and choose file to upload. Click OK.
Note
Activating Install Mode causes both sites to go into install mode, causing disruption in service for approximately fifteen seconds.
To reinstall the link: 1. Click Configuration in the Menu bar and select any one of the sites. The Configuration dialog box opens. 2. Click the Install Mode button in the Configuration dialog box. A message box asking if you want to enter install mode appears. 3. Click Yes to continue. Airmux-200 enters install mode and the beeper starts beeping. 4. Realign the ODUs and complete the Installation wizard (see Chapter2).
Chapter 4 Configuration
oriented and activated on a per ODU basis. For example, if you lock the remote ODU to the local ODU, you must still lock the local ODU to the remote ODU to ensure complete two way locking. It can only be removed when the link is unsynchronized. In such a case, an alarm is raised by the Airmux Manager. To enable link lock: 1. From the Link Configuration menu, select 1 Configuration Location A. 2. Choose the Security tab. The following window is displayed:
4-42
Chapter 4 Configuration
The link to the remote unit is now locked. If you repeat steps 1 and 2 above, the Security screen will look like this:
Note
To revert the Link Lock status to unlocked, power down each ODU in turn. Use the above procedure to uncheck the Link Lock status box for the live ODU. Resetting an ODU at either end restores the link to its previous locked or unlocked state.
Resetting Airmux-200
Note Resetting the link causes service disconnection. In order to maintain the link configuration, reset the remote Airmux-200 first.
To reset Airmux-200: 1. From Maintenance, reset the remote Airmux-200. 2. From Maintenance, reset the local Airmux-200. To reset to factory defaults: 1. Click Configuration in the Menu bar and select any one of the sites. The Configuration dialog box opens. 2. Select Operations in the Configuration dialog box.
4-43
Chapter 4 Configuration
5. Click the check box if you want to keep the current IP settings. 6. Click Yes to continue.
4-44
5.1
Monitoring Performance
Airmux-200 constantly monitors traffic over the radio link and collects the following statistics data: Site 1/Site 2 received traffic rate (in Mbps) Site 1/Site 2 received frames rate (in Mbps) Radio signal strength (in dBm) Error (Blocks).
The statistics (monitor) log and event log can be saved as TXT files. New alarms are automatically added to the text file, as they enter the event log.
Monitoring Performance
5-1
UAS This parameter counts the time the air link was not providing any service. There are several possible reasons for this situation; one of the sites has a power failure, high interference, maintenance operation, etc. Radio BBER Threshold This parameter counts the seconds in which the radio performance is below a user specified threshold. The threshold is measured in percent. The threshold can be set from 0.1% up to 50%. For links with E1/T1 service, the recommended value is 1% (system default). Excellent TDM service is expected below the 1% threshold, meaning that for 1% threshold, the expected BBER value should be 0 if there are no problems during the 15 min interval. If the BBER threshold increases some degraded service might be noticed. For links with Ethernet only service, 8% threshold is recommended and not 1% meaning that for 8% threshold, the recommended BBER value should be 0 if there are no problems during the 15 min interval. Since Airmux-200 provides a loss less Ethernet service, there is throughput degradation in case of interference. The degradation is proportional to the BBER. The Radio RSS Threshold can also be used to indicate problems in the radio channel. The expected RSS can be verified by means of the Link Budget Calculator. A value of -5dB from the current RSS is recommended as a threshold.
5-2
Monitoring Performance
Monitoring Performance
5-3
Data type
Explanation The number of seconds count that received traffic exceeded this threshold. It can be used to measure traffic peaks. The number of megabytes received in the specified port within the interval The number of megabytes received in the specified port within the interval.
Close
5. Click the button and in the Select File dialog box indicate in which folder and under what name the alarm log file is to be saved. 6. Set the time interval for adding data to the file. 7. Click OK to save the file.
5.2
Detecting Problems
Airmux-200 employs the following error and fault detection methods: Self-test LEDs Alarms and traps Statistic counters Link compatibility check Remote power fail indication Automatic link data collection.
Detecting Problems
5-5
Self-Test
Airmux-200 performs a hardware self-test upon turn-on. The self-test sequence checks the critical circuit functions of the device. The following error messages indicate hardware problems: BIT Failed (error code 256) WAN adapter failure BIT Failed (error code 512) EPROM failure.
LEDs
LEDs located on the front and rear panel panels of the IDU and ODU inform users about hardware failures; IDU-to-ODU, TDM, Ethernet and air link disruptions. For the detailed description of LEDs and their functions, refer to Chapter 3.
Statistic Counters
The air, TDM and Ethernet interface performance data is continuously collected during equipment operation. The collected data enables the system administrator to monitor the transmission performance, and thus the quality of service provided to users, for statistical purposes. For detailed description of the statistic counter, see Monitoring Performance above.
5-6
Detecting Problems
fullCompatibility restrictedCompatibility
softwareUpgradeRequired
SW Upgrade Required
versionsIncompatibility
Red
5.3
Handling Events
Airmux-200 detects compatibility problems, fault conditions of the radio or user links, and initiates alarms to alert the user.
Note
To store the Event Log, first define the IP address, subnet mask, default gateway and trap address of the management PC, see Chapter 4 for details.
Alarms (traps) are displayed in the Event Log in the lower panel of the Main Menu screen. The event log may be saved as a TXT file. The event log includes the following fields: Sequential number (ID) Date and time stamp Message Trap source IP address of the ODU that initiated alarm.
Handling Events
5-7
Warning Error Information Information Information Warning Warning Warning Warning Information Warning
Factory setting failed due to connectivity problem to ODU Factory setting failed due to connectivity problem to target - ODU will not be reset Free some space on disk on the managing computer and retry Operating System error on the managing computer
Set up a different IP to each site Airmux Manager is incompatible with the ODU software version
The Product is not identified at the <local_site_name> site. Warning The Product is not identified at the <remote_site_name> site. The Product is not identified at both sites. Product Not Identified! Warning Warning Warning
ODU release is newer than AirMux Manager release. The Manager identified a newer ODU release at the <remote_site_name> site. Warning Wizards are not available. AirMux Manager will be used just for monitoring. Upgrade the Airmux Manager. (You will get this message as a pop up)
The Manager identified a newer ODU release at both sites. Warning The Manager identified a newer ODU release at the <local_site_name> site. Warning ODU release is newer than AirMux Manager release. Newer Version identified at the <local_site_name> site. Warning Wizards are not available. AirMux Manager will be used just for monitoring. Upgrade the Airmux Manager.
5-8
Handling Events
Trap Message
Severity
Remarks
Newer Version identified at the <remote_site_name> site. Warning Newer Version Identified! Warning
To view summary of saved alarms From the Tools menu, choose Active Alarm. The Active Alarms Summary window opens. See Table 5-5; for an explanation of the command buttons.
Figure 5-4. Active Alarms Summary Table 5-5. Active Alarms Command Buttons
Command Save Refresh Site Close Action Saves the alarms in CSV or text format for further analysis. Reads the alarms from the ODU, and displays the alarms. Selects site for the active alarms. Closes the active alarm window.
Handling Events
5-9
3. Select the Event priority type and click on the A color chart opens. 4. Select the desired color. 5. Repeat for all the trap types. To set the trap background color:
button.
To reset the trap colors: Click Reset Settings to return to the default color settings.
5-10
Handling Events
To reset the monitoring and alarm preferences to defaults: 1. From the Tools menu, choose Preferences. The Preferences dialog box appears.
5.4
The Get Link Information feature collects all the link and manager information which can be used for diagnostics. In the event of needing to contact technical support send this file so as to speed up the assistance. To get link information 1. Click Help on the menu bar, select Link Information. The Get Link Information dialog box appears. See Figure 5-7.
5-11
2. Select or deselect the data options. If the file is to be sent to Technical Support leave all options checked. 3. Click File Path to get to the directory to save the file in. 4. Click Start to save the information. The file is saved as Link Information.txt
5.5
Troubleshooting
Use Table 5-7 and Table 5-7 to diagnose any faults in the system.
5-12
Troubleshooting
SERVICE
Off Orange
Red
5.6
Airmux-200 supports activation of the internal and external loopbacks on the local and remote units. To activate a loopback: 1. From the Maintenance menu, choose Loopbacks... or right-click the TDM display in the main window. The Loopbacks dialog box appears.
5-13
2. Click an active port that requires loopback activation. The selected port icon changes color to light blue as in the following example:
5-14
Figure 5-11. Main Window with TDM Port 2 of Site A in Reverse Loopback Mode
To deactivate a loopback: From the Configure menu option of the Loopback dialog box, select None and click OK. A loopback is deactivated.
5-15
E1/T1 Interface
Testing Equipment
Local ODU
Management Station
E1/T1 Interface
E1/T1 Interface
Testing Equipment
Remote ODU
Local ODU
Management Station
5-16
An inband command is sent from a management station connected to the local unit.
E1/T1 Interface Inband Loopback Activation Command E1/T1 Interface
Testing Equipment
Remote ODU
Local ODU
Management Station
E1/T1 Interface
E1/T1 Interface
Testing Equipment
Remote ODU
Local ODU
Management Station
5-17
5.7
Replacing an ODU
Prior to any action verify that both ODUs have the same software version (Configuration > Configure site > Inventory). If one ODU has an old software version, perform a software upgrade. It is important to configure the new ODU exactly the same as the old ODU to avoid configuration mismatches, which will disrupt the link. An ODU may be replaced with a new ODU in one several ways. Use the backup If a backup of the configuration is available, restore that configuration using Site A| Restore. Recall that backup files are linked to a MAC address. This wont work for an identical replacement ODU. Manual Configuration The new ODU can be configured manually according to the link configuration. Remember to use the same settings for Link ID, channels, link password, IP addresses, and names. Restore Factory Setup From version 1.6xx the feature of Restore Factory Setup is available. Using this feature we recommend putting the remaining ODU back to factory setup Configuration>Configure site>Advance option, and then activate the second ODU reconfiguring the link from scratch.
5.8
Q: What performance issues will arise due to environmental conditions? A: Airmux-200 is not sensitive to environmental conditions. However if heavy rain or snowfall is expected ensure the performance by allowing a higher fade margin in the link budget planning calculations. Q: When using the Airmux-200, what is the potential for interference between our system and other cellular or wireless network devices? A: The Airmux-200 is a robust system. However since it operates in unlicensed band there maybe some interference. Nevertheless, the fact that we can manually set the frequency gives us the flexibility to find a clear channel. In addition each Airmux-200 link uses unique user configurable SSID code. Q: What protocol does the Airmux-200 use, i.e. 802.11? A: Airmux-200 uses a proprietary protocol; this protocol contains improved options that more efficiently support the clock reconstruction from the TDM services.
5-18
Q: What type of security is offered on Airmux-200? A: Airmux-200 has three levels of security: 1. AES hardware mechanism 2. Each unit uses a unique SSID link-specific code (up to 24 alphanumeric characters) 3. Proprietary protocol protects from eavesdropping from other systems. Q: Can we use horizontal and vertical polarization on the same frequency to double the number of wireless links? A: Installing two Airmux-200 systems in the same band with cross polarization provides 2025 dB separations. Nevertheless, since there are reflections, the cross polarization separation is decreased and spatial separation is recommended. Q: Could you add the frequency of 5.735 to the manual selection in order to increase the number of 20 MHz channels to six? A: Currently the system provides fixed channels, with one manual frequency setting. The manual setting provides flexibility of spectrum selection, including 5.735 MHz. Q: Can we manage Airmux-200 using SNMPc other than the supplied management software that comes with the units? A: Yes. The Airmux-200 is SNMP-based. Airmux-200 can be managed when using other SNMP software after implementing RAD MIBs. Q: Can Airmux-200 be managed and configured via Telnet? A: Yes, starting from software version 1.750. Q: Can I use Airmux-200 with any vendors external antenna? A: Yes. RAD supplies the Airmux-200 external ODU with an N-type typical connector. Any vendors external antenna that can be cascaded to our external unit can be used without problem. Please note that dB losses in the cascading cable between the external ODU and antenna should be taken into consideration. (In the supplied cascading cable of one meter we have 1 dB loss) Q: Do we need to add external arrestors on Airmux-200 cables? A: The Airmux-200 ODU includes arrestors and lightning protection. Therefore there is no need to add additional arrestors. Q: What is the actual Ethernet data rate and maximum throughput? A: The maximum net throughput of Airmux-200 is full duplex 18 Mbps.
Note
5-19
Rate [Mbps] 12 18 36 48
Q: Does Airmux-200 withhold any MAC Addresses? A: The Airmux-200 is a layer 2 Bridge (VLAN transparent). The built-in switch contains a MAC Address table up to 2047. Q: Can I use any category 5e cable in order to connect the IDU and ODU? A: The cable should be suitable for outdoor use, and shielded Category 5e. Q: What are the BER values expected in the Airmux-200 link? A: 10-11 (according to BER sensitivity threshold) Q: Does Airmux-200 use DSSS technique? A: No, Airmux-200 uses the advanced OFDM technique. Q: What are the main advantages of the Airmux-200 solution (e.g., wireline, wireless, etc.) over other possible alternatives? A: Easy and intuitive installation using audio indication. Easy configuration using the management software of overall link site-to-site, there is no need to travel between the two sites in order to change the configuration. Easy migration between transition channels site-to-site. Full backup option backup and restore using ini files. Very light ODU (1.5 kg). No RF loses between IDU and ODU. Robust Air Interface Layer 2 ARQ insures error-free Ethernet service even in harsh conditions. Retransmit mechanism for TDM ensures low BER. Integrated up to 4 E1/T1 and Ethernet radio over one single product. Supports a variety of applications Voice and Data over single radio no need for external mediation device. Smooth migration to VoIP applications. Carrier class compliant with ITU standards for E1 and T1. Low and constant TDM latency (8 msec). Extremely accurate recovered clock low cost replacement to PDH radios.
5-20
5.9
Technical Support
Technical support for this product can be obtained from the local distributor from whom it was purchased. For further information, please contact the RAD distributor nearest you or one of RAD's offices worldwide. This information can be found at www.rad.com (offices About RAD > Worldwide Offices; distributors Where to Buy > End Users).
Technical Support
5-21
5-22
Technical Support
6-1
Figure 6-4. SWU Main Menu, Single Site Added for Upgrade Note
6-2
You can clear the list by clicking the Clear All button.
Airmux-200 Ver. 1.9.3
5. Add multiple sites from a prepared list using the Add from File option. The list has the following format: <IP address>,<Read-Only community>,<Read-Write community> For example: 192.168.1.101,public,netman 192.168.1.102,public,netman 192.168.2.101,public,netman 192.168.2.102,public,netman 6. Having created an update list, click Upgrade Package to choose the relevant SW files. The default files are located in the SWU subdirectory in the Airmux Manager installation area. They are currently named SWU_1k.swu and SWU_2k.swu. You may have to find them elsewhere, depending on your system. 7. You make limited changes to the list by right-clicking any line:
8. To back up your existing system, check Backup device software. Then click the button for a standard file dialog. The default location is the My Documents directory on the managing computer.
Note
The backup provides a fallback software version if the upgrade proves problematic.
9. Check Perform reset to each device after successful upgrade to determine the sites that will be reset immediately after the upgrade. A reset involves a service interruption, but the software upgrade does not become effective until after the reset is carried out. 10. Click Start Upgrade to commence the process. The upgrade begins. The Stop Upgrade button becomes available. It can be used to interrupt the process.
6-3
Figure 6-5. SWU Main Menu, Upgrade In Progress Caution If one or both sites fail to update, a warning notice is displayed.
If one site of a link updates but the other fails, you must correct the problem and update the second site as soon as possible. If you do not, following the next reset of the updated site, you will experience a link software mismatch which may affect service. 11. When the upgrade is finished, click Close to exit the software upgrade utility. If you requested a delayed upgrade, a notice like this will appear in the SWU title bar:
Note
All GSUs in a distributed site can be updated simultaneously. Use an IP list as described above.
6-4
7.1
Point-to-Point Application
Figure 7-1 illustrates a typical point-to-point wireless link using two Airmux-200 units. The wireless link serves as a backup route for the E1 leased line. In real-life applications the Airmux-200 TDM interfaces are connected to the E1/T1 equipment. In this sample application the local and remote units are connected directly to each other, and the two RADs HBTs substitute the TDM equipment.
Equipment List
The following is a list of equipment required for setting up a typical point-to-point application:
Airmux-200 Ver. 1.9.3 Point-to-Point Application 7-1
Two Airmux-200/ODU-HE/F58F/EXT outdoor units Two Airmux-200/IDU-R/E1/ACEU indoor units Two HBT/230/G703-E1 bit testers RF attenuated cable Two CBL-Airmux-UTP IDU-to-ODU cables One straight Ethernet cable with RJ-45 connectors Two CBL-RJ45/DB15/M cables One cross E1 cable with RJ-45 connectors PC running Windows XP.
7-2
Point-to-Point Application
Note
Point-to-Point Application
7-3
The optimal rate should be the minimal one enough to transfer services required. You can see the supported services in the Expected Performance>Services> Max Trunks. 4. As a single trunk is going to be used, specify 1 E1 in order to see the relevant Ethernet rate. 5. 6. 7. Select Tx power. Select the antenna gain (in case of external antenna only). Select the expected link range (in kilometers or miles) and Climate Factor (C Factor) if a TDM service availability estimation is required. The remaining fields are completed automatically depending on the product selected in the Product field. Standard Airmux-200 system parameters are entered as the default. Fields in blue boxes may be edited if non-standard antennas and cables are used. The Fade margin is the minimum margin that is required for LOS (Line Of Sight) conditions. For degraded link conditions, a larger fade margin should be considered. The Tx power EIRP (Effective Isotropic Radiated Power) for the system is given in dBm and Watts and reflects a reference power level that matches the power emitted by an isotropic radiator with an equivalent signal strength. 8. Click Calculate. The following results are displayed: Expected Performance: Parameters are calculated and displayed in the lower part of the table. Expected RSS: This is the value of Received Signal Strength that the Airmux-200 management software displays when the Airmux-200 ODUs are best aligned. Services: The E1/T1 services available for the selected configuration. Ethernet Rate: Maximum Ethernet throughput available with the selected services configuration. Recommended antenna height: Height above ground-level required for achieving the calculated link performance. 9. If the expected performance does not meet your requirements, select a different option (Antenna Gain, Rate, etc.) and re-calculate.
7-4
Point-to-Point Application
To emulate this stage make sure that all ODU and IDU devices are installed in a suitable and convenient place, and the cables can be connected easily and in accordance with safety rules and any other technical requirements. In a real application, ensure that you check proper grounding availability at the ODU and IDU installation points.
Installing Airmux-200s
Before starting configuration, install units as follows: 1. Connect the ODU port of the local IDU to the IDU port the local ODU using the CBL-Airmux-UTP cable. 2. Repeat step 1 at the remote site.
Local ODU
CBL-Airmux-UTP Cable
ODU
LAN
TRUNK 1
TRUNK 2
Local IDU
Point-to-Point Application
7-5
Local ODU
Remote ODU
ODU
LAN
TRUNK 1
TRUNK 2
Local IDU
LAN
PC
ODU
LAN
TRUNK 1
TRUNK 2
ODU
LAN
TRUNK 1
TRUNK 2
Local IDU
7-6
Point-to-Point Application
ODU
LAN
TRUNK 1
TRUNK 2
Local IDU
CBL-RJ45/DB15/M Cable
G703-E1
HBT
Figure 7-9. Beeper Sequence for Antenna Alignment Three beeps and a pause indicate the best signal. Two beeps and a pause, indicate signal quality has increased. One beep and pause indicate no signal change. Any other sequence detects no signal between the ODUs.
To align the antennas: 1. Connect the power to the local and remote IDU units. After approximately 60 seconds the ODUs start beeping. 2. Monitor the link quality for a few minutes to verify stability.
Note
Once the antennas are aligned, we can proceed with the link installation process.
The Login menu is displayed. 2. Use the following credentials for the first login: User name Local Connection or the factory default IP address (10.0.0.120) for the first login Password admin
Note
During the installation procedure, all parameters definitions are automatically applied to both sides of the link.
7-8
Point-to-Point Application
Point-to-Point Application
7-9
Note
If the Automatic Channel Selection box is checked (recommended) the system automatically selects the best channel available.
7-10
Point-to-Point Application
Note
Hub Site Synchronization should be enabled for the second application in this chapter (multipoint-to-point).
8. Click Next.
Point-to-Point Application
7-11
Note
For most applications the adaptive rate is recommended since it automatically adjusts the transmission rate to ensure maximum throughput for current link conditions.
7-12
Point-to-Point Application
Point-to-Point Application
7-13
7-14
Point-to-Point Application
15. Check RSS and link quality. The ODU-HE has a high transmit power. To avoid any damage to the ODU, set the Tx power to 9 dBm, see Configuring the Local and Remote Sites below.
Note
The maximum RSS value that can be accepted by the ODU without causing any damage is -35 dB.
Point-to-Point Application
7-15
2.
7-16
Point-to-Point Application
Point-to-Point Application
7-17
2.
7-18
Point-to-Point Application
3. 4. 5. 6. 7.
Click the
Check the check box to enable the saving the Airmux-200 monitor log in a file. Click Apply. Set the time interval for adding data to the file. Click OK to save the file.
7.2
Multipoint-to-Point Application
Airmux-200 devices can be installed in a multipoint-to-point architecture. Multiple units are deployed in one hub site location, from where they provide a dedicated, high capacity connection to each remote site. This concept is built on the Hub Site Synchronization (HSS) feature, which synchronizes the transmission of collocated Airmux-200 units, thus virtually reducing mutual interference commonly experienced by collocated TDD radios.
Multipoint-to-Point Application
7-19
In order to use Hub Site Synchronization, an external cable is connected from the master ODU to all collocated ODUs; this cable carries pulses sent to each ODU, which synchronize their transmission. The pulse synchronization ensures that the packets transmission occurs at the same time for all collocated units. This also results in all of the hub units receiving data at the same time, eliminating the possibility of interference that could result if some units transmit while other units at the same location receive.
Equipment List
The following is a list of equipment required for setting up a typical multipoint-to-point application: Six Airmux-200/ODU-HE/F58F/EXT outdoor units Six Airmux-200/IDU/ACEU indoor units Airmux-200/HSSU collocation hub Three RF attenuated cables Six CBL-Airmux-UTP IDU-to-ODU cables Six cross Ethernet cables with RJ-45 connectors Three CBL-HSS cables Six PCs.
7-20
Multipoint-to-Point Application
The collocated ODUs must be connected in sequence from SYNC 1. If an ODU is removed from the hub site, all remaining ODUs must be shifted to maintain the continuous connectivity.
Note
Multipoint-to-Point Application
7-21
7-22
Multipoint-to-Point Application
Note
The RFP must be the same for all links of the collocated system.
Multipoint-to-Point Application
7-23
7-24
Multipoint-to-Point Application
Multipoint-to-Point Application
7-25
7-26
Multipoint-to-Point Application
The ODU-IDU cable is standard CAT-5, 4 twisted-pair 24 AWG FTP, terminated with RJ-45 connectors on both ends. It is covered by a cable gland on the ODU side for hermetic sealing.
Table A-1 shows the connector pinout. Table A-1. ODU-IDU Cable Connector Pinout
IDU RJ-45 1 2 3 6 4 5 7 8 twisted pair twisted pair twisted pair twisted pair Wire Color White/Green Green White/Orange Orange Blue White/Blue White/Brown Brown Function Ethernet (RxN) Ethernet (RxT) Ethernet (TxT) Ethernet (TxN) Power (+) Power (+) Power () Power () ODU RJ-45 1 2 3 6 4 5 7 8
ODU-IDU Cable
A-1
A.2
The IDU includes ports for connecting E1/T1 and 10/100BaseT Ethernet user devices.
Trunk Port
The trunk (E1/T1) interface terminates in an 8-pin RJ-45 balanced connector, wired in accordance to Table A-2.
LAN Port
The LAN 10/100BaseT interface terminates in an 8-pin RJ-45 connector, wired in accordance to Table A-3.
A.3
IDU-E Connectors
IDU-E Connectors
A-3
A-4
IDU-E Connectors
A.4
ODUs are connected to HSS unit via a Cat. 5e cable with RJ-45 connectors wired in accordance with Table A-9.
A-5
A-6
B-1
B-2
B-3
B.2
To install external antenna on the mast: 1. Attach the U-bracket to the back of the antenna using four flat washers, four spring washers and four hex nuts. 2. Attach the pivoting bracket to the U-bracket using eight flat washers, four spring washers, four hex nuts and four bolts. 3. Pass both strap clamps through the vertical slots in the pivoting bracket. 4. Attach the antenna to the mast using the two strap clamps. 5. Adjust the required tilt using the angular scale and tighten all bolts and nuts at the required position.
B-4
C.1
The Link Budget Calculator is supplied on the Airmux Manager CD. It may be run directly from the CD or from the Airmux Manager application. To run the Link Budget Calculator directly from the CD: 1. Insert the Airmux Manager CD into the drive on the managing computer. In the window which opens, click the Link Budget Calculator option. 2. If the CD autorun application does not start by itself, then point your browser to: Z:\RAD\Setup\DATA\Link Budget Calculator.htm where Z must be replaced with your own CD drive name. To run the Link Budget Calculator from the Airmux Manager: Choose Help > Link Budget Calculator from the main menu of the Airmux Manager. The Link Budget Calculator window is displayed (Figure C-1).
Note
Allow running scripts when activating the Link Budget Calculator in Internet Explorer.
C-1
For each product (or regulation and band) the calculator stores the following data required for link budget calculations:
C-2
Maximum transmit power (per modulation) Receiver sensitivity (per modulation) for Ethernet service and for TDM services at various BER Maximum linear input power (used to calculate minimum distance)
Airmux-200 Ver. 1.9.3
Antenna gain and cable loss for ODU with integrated antenna Available channel bandwidths.
Calculations
EIRP
EIR P = TxPower + AntennaGain Site A CableLoss SiteA
ExpectedRSS Sensitivity , at the highest air-rate for which this relationship ExpectedRSS Sensitivity + RequiredFadeM arg in .
is true. In a link with adaptive rate this will be the actual behavior. MaxRange (for a given air-rate) is the largest range for which
Service
The Ethernet throughput is calculated according to internal product algorithms.
Availability
The Service Availability calculation is based on the Vigants Barnett method which predicts the downtime probability based on a climate factor (C factor).
Availability = 6 10 10
C-3
Antenna Height
The recommended antenna height required for line of sight is calculated as the sum the Fresnel zone height and the boresight height. See About the Fresnel Zone below. The Fresnel zone height is calculated
300 ExpectedRange 2 2 ---------------------------------- ---------------------------------------frequency GHz 2 ----------------------------------------------------------------------------------------------------ExpectedRange ExpectedRange ---------------------------------------- + ---------------------------------------2 2 as:
The boresight clearance height is calculated
R
as: where
Maean
ExpectedRange + ---------------------------------------2
.
R Maean
R Mean = 6367.4425Km
C.2
To use the Link Budget Calculator for Airmux-200: 1. Choose a product from the drop-down list (or choose a Regulation and Band):
C-4
C-5
3. For a collocated links choose the RFP. Use the Help button to the right of the RFP selection box for help.
C-6
Note
Note
If you choose Adaptive Rate, then the Rate list becomes unavailable as well as the Climate factor list. Both of these quantities are calculated.
Note
For a given air-rate, Ethernet throughput will decrease with increasing range due to propagation delay.
The Fade margin is the minimum required for LOS conditions. For degraded link conditions, a larger Fade margin should be used. The EIRP is given in dBm and Watts.
C-7
If for example, we enter: Site A: 41.1N lat 74.2W Long Site B: 40.8N lat 74.0W Long
C-8
6. Select Climactic C Factor value from the drop-down box next to the Km/Mile drop-down box. It is only available if you choose a non-adaptive rate. Click the ? button to the right of the C-Factor drop-down box to display the C-Factor descriptions.
Figure C-8. C-Factor Descriptions Figure C-9 illustrates a map of the world showing C Factor contours.
C-9
C-10
Note
Placing the cursor in any other calculated field also updates the calculated results.
The Expected Performance parameters are calculated and displayed: Expected RSS - the expected RSS that the Airmux Manager shows when the ODUs are optimally aligned Services Type - max number of T1 or E1 trunks if Max Trunks is selected Ethernet Rate - maximum throughput available for the chosen parameter combination Antenna height for LOS the minimum antenna height required for line-of-sight operation. It is the sum of the height required for boresight clearance due to the earths curvature plus the height required to clear the Fresnel zone 9. If the expected performance is not suitable for your application, try different parameters and repeat the calculation.
C.3
The Fresnel zone is an elliptically shaped conical zone of electromagnetic energy that propagates from the transmitting antenna to the receiving antenna. It is always widest in the middle of the path between the two antennas.
C-11
Fresnel loss is the path loss occurring from multi-path reflections from reflective surfaces such as water, and intervening obstacles such as buildings or mountain peaks within the Fresnel zone. Radio links should be designed to accommodate obstructions and atmospheric conditions, weather conditions, large bodies of water, and other reflectors and absorbers of electromagnetic energy. The Fresnel zone provides us with a way to calculate the amount of clearance that a wireless wave needs from an obstacle to ensure that the obstacle does not attenuate the signal. There are infinitely many Fresnel zones located coaxially around the center of the direct wave. The outer boundary of the first Fresnel zone is defined as the combined path length of all paths, which are half wavelength (1/2 ) of the frequency transmitted longer than the direct path. If the total path distance is one wavelength (1 ) longer than the direct path, then the outer boundary is said to be two Fresnel zones. Odd number Fresnel zones reinforce the direct wave path signal; even number Fresnel zones cancel the direct wave path signal. The amount of the Fresnel zone clearance is determined by the wavelength of the signal, the path length, and the distance to the obstacle. For reliability, point-to-point links are designed to have at least 60% of the first Fresnel zone clear to avoid significant attenuation. The concept of the Fresnel zone is shown in Figure C-11 above. The top of the obstruction does not extend far into the Fresnel zone, leaving 60% of the Fresnel zone clear; therefore, the signal is not significantly attenuated.
C-12
Warning
Note
This appendix is at best a guide. The actual degree of lightning protection required depends on local conditions and regulations.
D.1
Protection Elements
Lightning protection system consists of the following components: Grounding for the antenna coax cable Grounding for each IDU and ODU External primary surge suppressor units and grounding for the outdoor cable Internal ESD protection circuits over the power/telecom lines.
D.2
A grounding kit must be connected to the coax antenna cable and reliably grounded as shown in Figure D-1. The grounding kit is an Andrew Type 223158-2 (www.andrew.com).
D-1
D.3
ODU Grounding
Airmux-200uses a shielded CAT-5e cable to interconnect the outdoor (ODU) and indoor (IDU) units. However, this shielding does not provide a good lightning discharge path, since it cannot tolerate the high lightning current surges. To provide an alternate lightning discharge path, the ODU and antenna grounding posts should be connected to ground point by a 10 AWG short copper wire. The device must be permanently connected to ground.
IDU Grounding
The IDUs grounding post should be connected to the internal ground point, using a grounding wire of at least 10 AWG. The grounding wire should be connected to a grounding rod or the building grounding system. The device must be permanently connected to ground.
D-2
D.4
A grounding kit and surge arrestor unit must be located near the ODU and properly grounded as illustrated below.
D-3
The Transtector protection circuits shown in Figure D-5 below, utilize silicon avalanche diode technology. The unit consists of an outdoor-rated NEMA 3R type enclosure with easy mounting flanges, ground stud attachment and easy wiring. The ALPU-POE features RJ-45 protection circuits for the ODU-IDU data pairs (pins 1, 2 and 3, 6) and DC power (pins 4, 5 and 6, 7 with the pairs bonded). The unit is designed to be wall-mounted. An optional set of bracket is available to allow a wide range of pole mount applications. A dedicated ground stud is provided inside the unit that must be bonded to the nearest grounding system (or master ground bar) for proper surge protection. The system wiring is installed with RJ-45 type connectors that can feed directly into the chassis without having to cut, splice or route through awkward strain relief holes.
Note
There may also be regulatory requirements to cross bond the ODU-IDU CAT-5e cable at regular intervals up the mast. This may be as frequent as every 10 meters (33 feet).
D-5
A second Surge Arrestor Unit should be mounted at the building entry point and must be grounded, as shown in Figure D-3 above. To mount the lightning protection at the building entry point: 1. Mount the device outside the building, located as near as possible to the entrance of the CAT-5e ODU-IDU cable. Mount the unit so that the cable connectors are at the bottom (to prevent water from penetrating), with the strain reliefs facing the ground. 2. Remove the cover by unscrewing the front of the unit. 3. Mount the unit to an outside surface using the two mounting holes. 4. Connect the ODU-IDU cable using the RJ-45 jack. 5. Connect one cable between the IDU and the suppressor using an RJ-45 jack. 6. Connect the suppressors ground stud to a grounding point. Use the appropriate wire gauge and type, keeping the wire as short as possible, less than 1m (3), between the stud and the site grounding point. 7. Replace the cover
D-6
Site A
AirMux
IDUx IDUx
Site B
E-1
E.1
Based on the link budget parameters of the actual Airmux sites, you need to calculate the expected signal level that will be received by the receiving site. Use the Link Budget Calculator utility supplied on the Airmux-200 Manager Software CD-ROM to calculate the expected performance of the Airmux-200 wireless link. The utility allows you to determine the RSS of the link, and find the number of E1/T1 services available at various data rates, with the minimum and maximum distance.
E.2
The supervisor of the antenna alignment is situated at the receive site with the Spectrum Analyzer.
E-2
5. Repeat steps 1 to 4 until the reading on the SA is equal or as close as possible to the calculated receive signal (for Rx Power Level see Expected Signal Level). When the SA reads the expected receive signal, the antennas are aligned and there is an indication of a good link between the sites. 6. Tighten the antenna azimuth axis and elevation axis. 7. Stop the CW function. The NMS will restart the system. 8. Connect Airmux-200-AIND unit to external antenna. 9. Configure Airmux-200 NMS at both sites to operate at the pure channel frequency found in the RF survey. Airmux-200 is now ready for operation.
E.3
1. Run the Installation Wizard in the Airmux-200 Manager Software to set the configuration of the link. 2. Configure the link in accordance with the parameters calculated in the Link Budget Calculator. 3. Airmux-200 has a unique identification number, the SSID. Each side of the link looks for its partner with the same SSID. Therefore both sides of the link must be configured with the same SSID. 4. The Airmux-200 link is now ready for operation.
E.4
With the link operating at a pure channel as determined by the RF survey procedure, the recommended performance threshold of an Airmux-200 link is the following: RSS: 84 dBm minimum There are cases when there is no line of sight, but still the link is of an acceptable quality. If the link is not within the acceptable limit, see Alignment Troubleshooting.
E-3
E.5
Alignment Troubleshooting
If the link is not within the acceptable limit as defined in Evaluating the Link, check the following: Verify that both antennas have the same polarization (horizontal/vertical). Check all the Airmux-200-AIND cable connectors for faulty connections. Verify that there are no obstacles in the Fresnel zone of the antenna path such as large buildings, trees, etc. Use a spectrum analyzer with suitable sensitivity to measure the signal at the distance between the sites.
If nothing improves the receive power level, check the overall link. Reduce the distance of the link. Move the equipment from one site closer to the other site where it is possible to actually see the antennas with the naked eye. If you now get the expected receive signal level, you can assume that the equipment is operational, and the problem arises from interference between the sites.
E-4
Alignment Troubleshooting
F.1
All ODUs supplied by RAD come pre-configured with an IP address of 10.0.0.120. For use in a network, the ODUs must be configured with suitable static IP addresses. The method for doing this under office conditions is explained in Chapter 4. This section explains how do achieve the same thing in the field. The minimal equipment required to pre-load an ODU with an IP address is: Laptop computer (managing computer) An installed copy of the Airmux Manager A PoE device A crossed Ethernet LAN cable An IDU-ODU cable If you have connectorized ODUs, two N-type RF terminators.
To preload an ODU with an IP address: 1. Using the IDU-ODU cable, connect the PoE device to the ODU, ensuring that the cable is plugged into the PoE port marked P-LAN-OUT. 2. For connectorized ODUs, screw the RF terminators into the two antenna ports. A powered up ODU emits RF radiation from the antenna port (or connected antenna). When working with a powered up connectorized ODU, always use RF terminators. For an ODU with an integrated antenna, ensure that the antenna is always directed away from people. 3. Connect the Poe device to AC power. 4. Using a crossed LAN cable, connect the LAN-IN port of the PoE device to the Ethernet port of the managing computer. The ODU will commence beeping at about once per second, indicating correct operation.
Warning
F-1
5. Launch the Airmux Manager. 6. At the log on window, choose Local Connection.
F-2
F-3
F.2
All ODUs supplied by RAD come pre-configured with a factory set up product (part number) dependent band. For ODUs supporting Multi-band, it may be changed using the procedure in this section. The procedure is generic, applying to all ODUs with the Multi-band feature.
Caution If for some reason the default band needs to be changed, it must be done
before link Installation. Use of an incorrect band may be in violation of local regulations.
Equipment Requirements
The minimal equipment required to change an ODU default band is: Laptop computer (managing computer) An installed copy of the Airmux Manager A PoE device A crossed Ethernet LAN cable An IDU-ODU cable.
F-5
To change the factory default band: 1. Using the IDU-ODU cable, connect the PoE device to the ODU, ensuring that the cable is plugged into the PoE port marked P-LAN-OUT. 2. Connect the Poe device to AC power. 3. Using a crossed LAN cable, connect the LAN-IN port of the PoE device to the Ethernet port of the managing computer. The ODU starts beeping at about once per second, indicating correct operation. 4. Launch the Airmux Manager. 5. Log in as Installer.
F-6
Figure F-8. Opening Airmux Manager Window prior to Band Change Caution If you are changing the band on an installed link, change the over the air site
(site B) first. Otherwise you will lock yourself out of the link. 7. Select Tools > Change Band. The Change Band dialog box is displayed.
Figure F-9. Change Band Dialog Box Note The bands appearing in Figure F-9 are product-dependent.
8. Select the required band.
F-7
Note
If you carry out this operation on a link, the band change is effective on both sites and installation mode is initiated. For a DFS band all configurations are made via the main window and the installation mode is disabled.
F-9
F-10
Note
HSS does not eliminate the need for careful RF planning to ensure the design
will work as planned. See Chapter 2 for information on installation site survey.
For Airmux-200, HSS support depends on the product model. The Hub Site Synchronization (HSS) method uses a cable connected from the master ODU to all collocated ODUs; this cable carries pulses sent to each ODU, which synchronize their transmission with each other. The pulse synchronization ensures that transmission occurs at the same time for all collocated units. This also results in all of the hub site units receiving data at the same time, eliminating the possibility of interference that could result if some units transmit while other units at the same location receive.
Hardware Installation
G-1
The remote ODUs that are not located at the hub site, are called independent units and do not require HSS hardware.
G-2
Hardware Installation
G.1
Hardware Installation
A single HSS unit supports up to ten collocated ODUs. In addition to each unit being connected to its IDU or PoE device, the collocated unit has an additional cable that is connected to the HSS unit. The HSS unit is a compact, weatherproof (IP67) connector box that is installed on the same mast as the ODUs. All collocated units connect to this box using CAT-5e cable. Cables in prepared lengths are available for purchase. The HSS unit is supplied with ten protective covers; any port not in use must be closed with a protective cover.
cable.
Ensure that the collocated units are connected in sequence from SYNC 1. If an
ODU is removed from the hub site, then all remaining ODUs must be reconnected to maintain the connectivity.
To connect an ODU to the HSS 1. Prepare a Cat. 5e cable with RJ-45 connectors in accordance to the cable ODU-to-HSS unit cable wiring in Appendix A. 2. Unscrew the protective cover from the port marked SYNC 1. 3. Connect the RJ-45 connector from one end of the CAT 5e cable to SYNC 1. 4. Connect the other end of the CAT 5e cable to the ODU connector labeled SYNC. 5. Tighten the protective seal that is on the prepared cable over the RJ-45 connector. 6. Repeat for all ODUs that are to be collocated at the hub site. The next ODU to be connected is inserted to SYNC 2, followed by SYNC 3 and so on.
Hardware Installation
G-3
Note
In the event of an HSS installation fault, the ODU will sound a beep pattern according to the following chart, which may also be seen on the ODU product label:
G-4
Hardware Installation
Figure G-6. HSS Synchronization Signal Path with ODU 1 as HSS Master
Hardware Installation
G-5
4. To add a further HSS unit: Connect the next available SYNC port from the second HSS unit in descending order (SYNC 5 in Figure G-7) to SYNC 1 of the third HSS unit. 5. ODUs are connected to the third HSS unit from SYNC 2 as shown in Figure G-8, in ascending order:
6. If further ODUs are required, observe the convention that additional even
numbered units are populated in descending order from SYNC 9 and odd numbered HSS units are populated in ascending order from SYNC 2.
Note
If an ODU is disconnected from an HSS unit, then all remaining ODUs must be moved up or down to maintain the connectivity.
G-6
Hardware Installation
G.2
A Radio Frame Pattern (RFP) is the cycle duration of transmit and receive of the air-frame.
Without HSS
When selecting TDM or Ethernet services, the system automatically and transparently chooses the optimal RFP. When TDM and Ethernet services are configured, the RFP is optimized for TDM.
A B
Best N/A
G-7
RFP
20 MHz N/A N/A Fit N/A N/A Fit N/A N/A Fit
C D E
B E
Fit Best
Legend: Fit available RFP for TDM and Ethernet services. Best optimal RFP for TDM and Ethernet services. N/A service unavailable Select the RFP that gives you the Best or Fit for required system services and select the channel bandwidth accordingly.
Note
The RFP must be the same for each link within the collocated system.
Five RFP types (A to E) are available. The RFP is selected depending on the type of the radio products, services and channel bandwidth used by the complete system.
Note
RFP type E should be used if and only if Airmux-400 links are part of the HSS
installation.
The RFP must be the same for each link within the collocated system. Select the RFP that gives you the Best Fit for the system services and select the Channel Bandwidth accordingly. The table below describes the efficiency of the Airmux-200 air interface according to the RFP type, radio products mix, services and channel bandwidth. The table may be viewed in the Airmux Manager and in the Link Budget Calculator and varies according to the product used.
RFP Considerations
When setting the RPF, the following considerations should be borne in mind: When synchronizing Airmux-400 units you must use RFP B or E If you mix Airmux-400 and Airmux-200 units in a collocated site, you must use RFP B or E Selection of the RFP influences the capacity, latency and TDM quality
G-8
RFP influences capacity and latency. Jitter buffer configuration can be used to set the TDM quality Using the Link Budget Calculator, you can see the affect of the RFP on the Ethernet throughput.
Airmux-400 Considerations
RFP B and channel bandwidths 14 MHz, 7 MHz and 5 MHz will only be available for release 1.9.30 and later The performance of Airmux-400 radios that operate with RFPs B or E can be seen in the Link Budget Calculator. For Airmux-400 100M series: If the HSS Master works in asymmetric Tx/Rx ratio, then all other collocated Airmux-400 units must operate in the same Tx/Rx ratio. In this case the ratio will be fixed and not automatic adaptive. Installation/Configuration considerations: If you are using Airmux-400 100M master and Airmux-400 clients, the Services and Rates dialog will look like this:
Figure G-10. Services and Rates - Airmux-400 100M Master, Airmux-400 Clients
The circled areas should not be used. Using those areas, you may lose the collocated link with the longest distance between sites. If you do move the slider into a circled area, you will receive a popup warning:
G-9
Figure G-11. Services and Rates - Airmux-400 100M Master, Airmux-400 Clients, Extreme Asymmetric Allocation
By restricting one direction into the restricted area, the more distant sites may not even be able to sustain the link much less send or receive data. Asymmetric Allocation and Collocation: If the link is collocated, the use of Asymmetric Allocation is limited. The effective available range for Asymmetric Allocation (between the two circled tick in Figure G-10) is primarily determined by three factors: The RFP in use (B or E) Channel bandwidth Link distance The first two parameters are entered during link installation/configuration. Possible scenarios are shown in Table G-3. Whenever asymmetric allocation is available, it is static for all traffic conditions.
G-10
HSS Master
Result Releases prior to 2.4 Link down Release 2.4 later (Airmux-400 10M and Airmux-400 50M series) Link down Release 2.4 and later (Airmux-400 100M series) TDM services stopped, link set to transmission ratio of master
Remarks Release 2.4 and later (Airmux-400 100M series) Asymmetric Allocation slider is visible but cannot be changed
Airmux-400
Airmux-200 Airmux-400 Change client to asymmetric Asymmetric Allocation slider is not displayed
Unavailable
Airmux-200
Airmux-200 Airmux-400 Change client to asymmetric Asymmetric Allocation slider is not displayed
Unavailable
Airmux-200 Considerations
When Airmux-200 radios are collocated with Airmux-200 radios using HSS, all radios must use RFP B or E. The performance of Airmux-200 radios that operate with these RFPs can be seen in the Link Budget calculator The choice of the unit to be the HSS master is a matter of convenience. There is no technical reason to prefer an Airmux-200 over an Airmux-400 as HSS master or vice versa. It is however, recommended that you use the Airmux-400 as master, since it will enforce the correct RFP on the other collocated units.
The following list summarizes the effect of using RFP B or E on AirMux-200 radios. These effects should be taken into consideration when planning new installations: Channel bandwidth 5 MHz is available under RFP E but is only supported for Airmux-200 products For products supporting a maximum throughput of 18.1 Mbps, the maximum Ethernet throughput is 14.5 Mbps at 20 MHz channel bandwidth and 9.3 Mbps at 10 MHz channel bandwidth For products supporting maximum throughput of 22.5 Mbps, the maximum Ethernet throughput is 21.4 Mbps at the 20 MHz channel and 9.3 Mbps at 10 MHz channel bandwidth
G-11
G.3
For HSS-enabled units, the Hub Site Synchronization Settings dialog box appears in the Link Installation and Configuration Wizard.
Note
Continue Transmission is intended to work if there is no HSM pulse. If a wrong HSM pulse is detected, an Airmux-200 will resync, adapting to the HSM RFP and continue whereas Airmux-400 may stop.
Synchronization: N/A- for Master or Independent Units Synchronized for Hub Site Clients Not Synchronized for Hub Site Clients External Pulses: The status of the pulses running through the HSS cable. The Master generates such pulses. The severity of each of these states is indicated by green, yellow or red text color.
G-12
To configure the operational states of the hub site unit: 1. Click the Enabled check box. 2. Click the Configure button The Hub Site Configuration dialog box with the current status of the ODUs is displayed. 3. Select the type of unit configuration from the drop-down list. 4. Select the appropriate RFP radio button. Some RFP options may be disabled depending on the BW previously selected.
Note
Take care to avoid incorrect configuration of bandwidth, RFP or to set multiple Hub Sync Masters, as system interference can occur. Airmux Manager gives error messages and tool tips if the system is configured with mismatches.
G.4
Configuring a Site
For units that support HSS, the Hub Site Sync option appears in the Air Interface section and displays the current HSS of the unit. Configure the unit from the Link Configuration Wizard according to the procedure described above.
G-14
Configuring a Site
In accordance with 2.5 GHz standard, Airmux-200-BRS systems links must be activated before use. This is done at both ODUs independently before installation on site. Both ODUs must be configured the same. To activate a BRS link: 1. Install Airmux Manager software as usual. 2. When the Manager Main Screen is displayed it appears with the Link Status label red and showing Inactive. The Link Configuration and Link installation buttons are disabled.
H-1
H-2
H.2
The BRS link can be reconfigured using the Link Installation or the Link Configuration wizards, or from the Air Interface screen.
Note
Both sites in a BRS link must be configured identically. Any changes to the frequency settings cause the link to re-synchronize. A short loss of service will occur during re-synchronization.
To configure BRS channel settings: 1. Set the Band Plan (see Figure H-3 and Figure H-4). 2. Select the Bandwidth required: Single Band or Double Band. 3. Select the Frequency from the pull-down menu. 4. Click Next. The system is re-synchronized to the changes.
H-3
H-4
This appendix describes the public and private MIB used by RAD.
I.1
Control Method
Interface API
The Airmux Manager application provides all the means to configure and monitor an Airmux-200 link, communicating with the SNMP agent in each ODU. Each SNMP agent contains data on each of the IDUs and ODUs in the link. Both agents communicate with each other over the air using a proprietary protocol.
Note
Interface API
I-1
Community String
To control a link, all SNMP requests must go to the local site IP address.
I.2
Figure I-1 illustrates the sections in the private RAD MIB and its location in
the MIB tree.
The ODU MIB contains the sections: Admin, Service, Ethernet, Bridge, Air, PerfMon and Agent. The IDU MIB contains the sections: Admin, Service, Ethernet, Bridge and TDM. The GpsSynchronizerFamily MIB defines the GSU.
I-2
The general MIB include a single generic parameter that is used by all traps as a trap description parameter.
I.3
MIB Parameters
The following section describes all of the MIB parameters. The MIB parameters follow the following naming convention: <airmux200><Section 1>...<Section n><Parameter Name> For each of the configuration and control parameters (parameters with readwrite access), the Description column describes when the new value is effective. It is recommended that you perform the appropriate action to make the values affective immediately after any change. Where a change is required on both sides of the link, it is recommended that you change both sides of the link first and then perform the action.
ifIndex
.1.3.6.1.2.1.2.2.1.1.x
Integer
RO
A unique value for each interface.Its value ranges between 1 and the value of ifNumber.The value for each interface must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
ifDescr
.1.3.6.1.2.1.2.2.1.2
DisplayString
RO
A textual string containing information about the interface.This string should include the name of the manufacturer, the product name and the version of the hardware interface.
ifType
.1.3.6.1.2.1.2.2.1.3
Integer
RO
The type of interface, distinguished according to the physical/link protocol(s) immediately `below' the network layer in the protocol stack.
ifSpeed
.1.3.6.1.2.1.2.2.1.5
Gauge
RO
An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should obtain the nominal bandwidth.
MIB Parameters
I-3
Name
OID
Type
Description
ifPhysAddress
.1.3.6.1.2.1.2.2.1.6
Phys-Address
RO
The interface's address at the protocol layer immediately `below' the network layer in the protocol stack. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length.
ifAdminStatus
.1.3.6.1.2.1.2.2.1.7
Integer
RW The desired state of the interface. The testing(3) state indicates that no operational packets can be passed.
ifOperStatus
.1.3.6.1.2.1.2.2.1.8
Integer
RO
The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed.
ifInOctets
.1.3.6.1.2.1.2.2.1.10.x
Counter
RO
The total number of octets received on the interface, including framing characters.
ifInUcastPkts
.1.3.6.1.2.1.2.2.1.11.x
Counter
RO
ifInNUcastPkts
.1.3.6.1.2.1.2.2.1.12.x
Counter
RO
The number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.
ifInErrors
.1.3.6.1.2.1.2.2.1.14.x
Counter
RO
The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
ifOutOctets
.1.3.6.1.2.1.2.2.1.16.x
Counter
RO
The total number of octets transmitted out of the interface, including framing characters.
ifOutUcastPkts
.1.3.6.1.2.1.2.2.1.17.x
Counter
RO
The total number of packets that higher-level protocols requested to be transmitted to a subnetworkunicast address, including those that were discarded or not sent.
I-4
MIB Parameters
Name
OID
Type
Description
ifOutNUcastPkts
.1.3.6.1.2.1.2.2.1.18.x
Counter
RO
The total number of packets that higher-level protocols requested be transmitted to a non- unicast (i.e., a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent.
Note
Name
OID
Type
Description
ODU configuration description. ODU Hardware Version. ODU Software Version. Link Name. A change is effective immediately.
radwllMilOduAdmResetCmd
1.3.6.1.4.1.4458.1000.1.1.5
Integer
RW
Reset Command. A set command with a value of 3 will cause a device reset. The read value is always 0.
radwllMilOduAdmAddres
1.3.6.1.4.1.4458.1000.1.1.6
IpAddress
RW
ODU IP address. A change is effective after reset. The parameter is kept for Using the backward compatibility. alternative parameter: radwllMilOduAdmIpParamsCnfg is recommended.
radwllMilOduAdmMask
1.3.6.1.4.1.4458.1000.1.1.7
IpAddress
RW
ODU Subnet Mask. A change is effective after reset. The parameter is kept for Using the backward compatibility. alternative parameter: radwllMilOduAdmIpParamsCnfg is recommended.
radwllMilOduAdmGateway
1.3.6.1.4.1.4458.1000.1.1.8
IpAddress
RW
ODU default gateway. A change is effective after reset. The parameter is Using kept for backward compatibility. the alternative parameter: radwllMilOduAdmIpParamsCnfg is recommended.
radwllMilOduAdmBroadcast
1.3.6.1.4.1.4458.1000.1.1.10
Integer
RW
This parameter is reserved for the Manager application provided with the product.
MIB Parameters
I-5
Name
OID
Type
Description
radwllMilOduAdmHostsTable
N/A
Trap destinations table. Each trap destination is defined by an IP address and a UDP port. Up to 10 addresses can be configured.
radwllMilOduAdmHostsEntry
N/A
RO RW
Trap destinations table index. Trap destination IP address. A change is effective immediately.
radwllMilOduAdmHostsPort
1.3.6.1.4.1.4458.1000.1.1.12.1.3
Integer
RW
radwllMilOduBuzzerAdminState
1.3.6.1.4.1.4458.1000.1.1.13
Integer
RW
This parameter controls the activation of the buzzer while the unit is in install mode. A change is effective immediately. The valid values are: disabled (0) enabledAuto (1) enabledConstantly(2).
radwllMilOduProductId
1.3.6.1.4.1.4458.1000.1.1.14
DisplayString RO
This parameter is reserved for the Manager application provided with the product.
radwllMilOduReadCommunity
1.3.6.1.4.1.4458.1000.1.1.15
DisplayString RW
Read Community String. This parameter always returns ***** when retrieving its value. It is used by the Manager application to change the Read Community String. The SNMP agent accepts only encrypted values.
radwllMilOduReadWriteCommunity 1.3.6.1.4.1.4458.1000.1.1.16
DisplayString RW
Read/Write Community String. This parameter always returns ***** when retrieving its value. It is used by the Manager application to change the Read/Write Community String. The SNMP agent accepts only encrypted values.
radwllMilOduTrapCommunity
1.3.6.1.4.1.4458.1000.1.1.17
DisplayString RW
Trap Community String. This parameter is used by the Manager application to change the Trap Community String. The SNMP agent accepts only encrypted values.
Integer
RO
DisplayString RO
Remote site name. Returns the same value as sysLocation parameter of the remote site.
Integer
RO
I-6
MIB Parameters
Name
OID
Type
Description
radwllMilOduAdmLinkPassword
1.3.6.1.4.1.4458.1000.1.1.21
DisplayString RW
Link Password. This parameter always returns ***** when retrieving its value. It is used by the Manager application to change the Link Password. The SNMP agent accepts only encrypted values.
radwllMilOduAdmSiteLinkPassword 1.3.6.1.4.1.4458.1000.1.1.22
DisplayString RW
Site Link Password. This parameter always returns ***** when retrieving its value. It is used by the Manager application to change the Link Password of the site. The SNMP agent accepts only encrypted values.
radwllMilOduAdmDefaultPassword 1.3.6.1.4.1.4458.1000.1.1.23
Integer
RO
This parameter indicates if the current Link Password is the default password.
radwllMilOduAdmConnectionType
1.3.6.1.4.1.4458.1000.1.1.24
Integer
RO
This parameter indicates if the Manager application is connected to the local ODU or to the remote ODU over the air. A value of 'unknown' indicates community string mismatch.
Integer
RW
Back to factory settings Command. A change is effective after reset. value is always 0. The read
radwllMilOduAdmIpParamsCnfg
1.3.6.1.4.1.4458.1000.1.1.26
DisplayString RW
radwllMilOduAdmVlanID
1.3.6.1.4.1.4458.1000.1.1.27
Integer
RW
VLAN ID. Valid values are 1 to 4094. Initial value is 0 meaning VLAN unaware.
radwllMilOduAdmVlanPriority
1.3.6.1.4.1.4458.1000.1.1.28
Integer
RW
ODU Serial Number This is the product name as it exists at EC Activates a general key. Mobile Application: permitted partner OduType.
Integer Integer
RO RW
CPU ID System mode. The only values that can be set are installMode and slaveMode; normalMode reserved to the Manager application provided with the product. A change is effective after link resynchronization.
radwllMilOduSrvBridging
1.3.6.1.4.1.4458.1000.1.2.3
Integer
RO
MIB Parameters
I-7
Name
OID
Type
Description
(0) enabled (1). radwllMilOduSrvRingLinkMode 1.3.6.1.4.1.4458.1000.1.2.4.1 Integer Integer RW RO Mode of the link regarding ring topology. Ring Topology options are: supported not supported N/A N/A Ring VLAN IDs table. VLAN ID of the internal ring messages. Valid values are 1 to 4094. Initial value is 0 meaning VLAN unaware. INDEX { radwllMilOduSrvRingVlanIdIndex } radwllMilOduSrvRingVlanIdIndex 1.3.6.1.4.1.4458.1000.1.2.4.3.1.1 Integer RO Index of VLAN ID of the internal ring messages. radwllMilOduSrvRingVlanId 1.3.6.1.4.1.4458.1000.1.2.4.3.1.2 Integer RW VLAN ID of the internal ring messages. Valid values are 1 to 4094. Initial value is 0 meaning VLAN unaware. radwllMilOduSrvRingEthStatus 1.3.6.1.4.1.4458.1000.1.2.4.4 Integer RO Represents the Ethernet service blocking state of a Rings link radwllMilOduSrvRingMaxAllowedTim 1.3.6.1.4.1.4458.1000.1.2.4.5 eFromLastRpm radwllMilOduSrvRingWTR 1.3.6.1.4.1.4458.1000.1.2.4.6 Integer RW Integer RW Defines the minimal time (in ms) required for determination of ring failure. Defines the minimal time (in ms) required for ring recovery. radwllMilOduSrvQoSMode radwllMilOduSrvQoSConfTable radwllMilOduSrvQoSConfEntry 1.3.6.1.4.1.4458.1000.1.2.5.1 Integer RW N/A N/A Mode of QoS feature. QoS configuration table. QoS configuration table. INDEX {
radwllMilOduSrvQoSConfIndex } radwllMilOduSrvQoSConfIndex radwllMilOduSrvConfVlanQGroups 1.3.6.1.4.1.4458.1000.1.2.5.2.1.1 1.3.6.1.4.1.4458.1000.1.2.5.2.1.2 Integer Integer RO RO Index of QoS Configuration. Frames classification according to VLAN Priority IDs. radwllMilOduSrvConfDiffservQGrou 1.3.6.1.4.1.4458.1000.1.2.5.2.1.3 ps radwllMilOduSrvConfQueMir radwllMilOduSrvConfQueWeight 1.3.6.1.4.1.4458.1000.1.2.5.2.1.4 1.3.6.1.4.1.4458.1000.1.2.5.2.1.5 Integer Integer RW RW Desired Private MIR. QoS queueu's weights in percent. Frames classification according to VLAN IDs string for set. DisplayString RW Frames classification according to Diffserv IDs string for set. Integer RO Maximal percent for RT & NRT queues. Integer RO Frames classification according to Diffserv.
radwllMilOduSrvQoSVlanQGroupsSe 1.3.6.1.4.1.4458.1000.1.2.5.3 tStr radwllMilOduSrvQoSDiffservQGroup 1.3.6.1.4.1.4458.1000.1.2.5.4 sSetStr radwllMilOduSrvQoSMaxRTQuePerc 1.3.6.1.4.1.4458.1000.1.2.5.5 ent radwllMilOduEthernetRemainingRat 1.3.6.1.4.1.4458.1000.1.3.1 e
DisplayString RW
Integer
RO
I-8
MIB Parameters
Name
OID
Type
Description
radwllMilOduEthernetIfTable radwllMilOduEthernetIfEntry
N/A N/A
ODU Ethernet Interface table. ODU Ethernet Interface table entry. INDEX { radwllMilOduEthernetIfIndex }
radwllMilOduEthernetIfIndex radwllMilOduEthernetIfAddress
1.3.6.1.4.1.4458.1000.1.3.2.1.1 1.3.6.1.4.1.4458.1000.1.3.2.1.5
Integer
RO
ODU Ethernet Interface Index. ODU MAC address. Required state of the interface. Current operational state of the interface. Failure action of the interface. Number of ODU network interfaces. ODU Bridge Ports table. ODU Bridge Ports table entry. INDEX { radwllMilOduBridgeBasePortIndex }
radwllMilOduEthernetIfAdminStatus 1.3.6.1.4.1.4458.1000.1.3.2.1.6 radwllMilOduEthernetIfOperStatus 1.3.6.1.4.1.4458.1000.1.3.2.1.7 radwllMilOduEthernetIfFailAction radwllMilOduEthernetNumOfPorts radwllMilOduBridgeBasePortTable radwllMilOduBridgeBasePortEntry 1.3.6.1.4.1.4458.1000.1.3.2.1.8 1.3.6.1.4.1.4458.1000.1.3.3
RO RO RW
ODU Bridge Port Number. IfIndex corresponding to ODU Bridge port. ODU bridge mode. bridgeMode (1). A change is effective
radwllMilOduBridgeTpPortTable radwllMilOduBridgeTpPortEntry
N/A N/A
ODU Transparent Bridge Ports table. ODU Transparent Bridge Ports table entry. INDEX { radwllMilOduBridgeTpPortIndex }
radwllMilOduBridgeTpPortIndex radwllMilOduBridgeTpPortInFrames 1.3.6.1.4.1.4458.1000.1.4.4.3.1.3 radwllMilOduBridgeTpPortOutFrame 1.3.6.1.4.1.4458.1000.1.4.4.3.1.4 s radwllMilOduBridgeTpPortInBytes 1.3.6.1.4.1.4458.1000.1.4.4.3.1.101 Counter Counter Integer Integer Counter Counter
RO RO RO
ODU Transparent Bridge Port Number. Number of frames received by this port. Number of frames transmitted by this port.
RO RO RO RW
Number of bytes received by this port. Number of bytes transmitted by this port. ODU bridge configuration mode Installation Center Frequency. Valid values are product dependent. A change is effective after link re-synchronization.
radwllMilOduAirDesiredRate
1.3.6.1.4.1.4458.1000.1.5.2
Integer
RW
Deprecated parameter actual behavior is read-only. Required Air Rate. For Channel Bandwidth of 20 10 5 MHz divide the value by 1 2 4 respectively.
radwllMilOduAirSSID
1.3.6.1.4.1.4458.1000.1.5.3
DisplayString RW
radwllMilOduAirTxPower
1.3.6.1.4.1.4458.1000.1.5.4
Integer
RW
MIB Parameters
I-9
Name
OID
Type
Description
nominal value while the actual transmit power includes additional attenuation. The min and max values are product specific. A change is effective immediately. radwllMilOduAirSesState 1.3.6.1.4.1.4458.1000.1.5.5 Integer RO Current Link State. The value is active (3) during normal operation. radwllMilOduAirMstrSlv 1.3.6.1.4.1.4458.1000.1.5.6 Integer RO This parameter indicates if the device was automatically selected into the radio link master or slave. if there is no link. radwllMilOduAirResync 1.3.6.1.4.1.4458.1000.1.5.8 Integer RW Setting this parameter to 1 will cause the link to restart the synchronization process. radwllMilOduAirRxPower radwllMilOduAirTotalFrames radwllMilOduAirBadFrames 1.3.6.1.4.1.4458.1000.1.5.9.1 1.3.6.1.4.1.4458.1000.1.5.9.2 1.3.6.1.4.1.4458.1000.1.5.9.3 Integer Counter Counter RO RO RO Received Signal Strength in dBm. Total Number of received radio frames. Total number of received radio frames with CRC error. radwllMilOduAirCurrentRate 1.3.6.1.4.1.4458.1000.1.5.9.4 Integer RO Deprecated parameter. Actual rate of the air interface in Mbps. For Channel Bandwidth of 20 10 5 MHz divide the value by 1 2 4 respectively. radwllMilOduAirCurrentRateIdx radwllMilOduAirTxPower36 1.3.6.1.4.1.4458.1000.1.5.9.5 1.3.6.1.4.1.4458.1000.1.5.10 Integer Integer RO RW Index of current air rate. Deprecated parameter. Actual behavior is read-only. radwllMilOduAirTxPower48 1.3.6.1.4.1.4458.1000.1.5.11 Integer RW Deprecated parameter. Actual behavior is read-only. radwllMilOduAirCurrentTxPower 1.3.6.1.4.1.4458.1000.1.5.12 Integer RO Current Transmit Power in dBm. This is a nominal value while the actual transmit power includes additional attenuation. radwllMilOduAirMinFrequency radwllMilOduAirMaxFrequency radwllMilOduAirFreqResolution 1.3.6.1.4.1.4458.1000.1.5.13 1.3.6.1.4.1.4458.1000.1.5.14 1.3.6.1.4.1.4458.1000.1.5.15 Integer Integer Integer RO RO RO Minimum center frequency in MHz. Maximum center frequency in MHz. Center Frequency resolution. Measured The value is undefined
in MHz if value < 100 otherwise in KHz. radwllMilOduAirCurrentFreq 1.3.6.1.4.1.4458.1000.1.5.16 Integer RO Current Center Frequency. Measured in MHz if center frequency resolution value < 100 otherwise in KHz. radwllMilOduAirNumberOfChannels 1.3.6.1.4.1.4458.1000.1.5.17 radwllMilOduAirChannelsTable Integer RO N/A Number of channels that can be used. Table of channels used by automatic channels selection (ACS).
I-10
MIB Parameters
Name
OID
Type
Description
radwllMilOduAirChannelsEntry
N/A
radwllMilOduAirChannelsIndex
1.3.6.1.4.1.4458.1000.1.5.18.1.1
RO RO RW
Channel Index. Channel frequency in MHz. Channel state. Can be set by the user. Automatic Channel Selection uses channels that are AirChannelsOperState enabled and AirChannelsAvail enabled. A change is effective after link resynchronization. Valid values: disabled (0) enabled (1).
radwllMilOduAirChannelsAvail
1.3.6.1.4.1.4458.1000.1.5.18.1.4
Integer
RO
Channel state. Product specific and cannot be changed by the user. Automatic Channel Selection uses channels that are AirChannelsOperState enabled and AirChannelsAvail enabled. disabled (0) enabled (1). Valid values:
radwllMilOduAirChannelsDefaultFre 1.3.6.1.4.1.4458.1000.1.5.18.1.5 q
Integer
RO
Default channel's availability for all CBWs. The valid values are: forbidden (0) available (1).
radwllMilOduAirDfsState
1.3.6.1.4.1.4458.1000.1.5.19
Integer
RO
Integer
RO
Deprecated parameter. Indicating Automatic Channel Selection availability at current channel bandwidth. disabled (0) enabled (1). Valid values:
radwllMilOduAirEnableTxPower
1.3.6.1.4.1.4458.1000.1.5.21
Integer
RO
radwllMilOduAirMinTxPower radwllMilOduAirMaxTxPowerTable
1.3.6.1.4.1.4458.1000.1.5.22
Integer
RO N/A
Minimum Transmit power in dBm. Table of Maximum transmit power per air rate in dBm.
radwllMilOduAirMaxTxPowerEntry
N/A
radwllMilOduAirMaxTxPowerIndex radwllMilOduAirMaxTxPower
1.3.6.1.4.1.4458.1000.1.5.23.1.1 1.3.6.1.4.1.4458.1000.1.5.23.1.2
RO RO RW
Air interface rate index. Maximum Transmit power in dBm. Channel bandwidth in KHz. A change is effective after reset.
radwllMilOduAirChannelBandwidth 1.3.6.1.4.1.4458.1000.1.5.24
radwllMilOduAirChannelBWTable radwllMilOduAirChannelBWEntry
N/A N/A
radwllMilOduAirChannelBWIndex
1.3.6.1.4.1.4458.1000.1.5.25.1.1
Integer
RO
MIB Parameters
I-11
Name
OID
Type
Description
radwllMilOduAirChannelBWAvail
1.3.6.1.4.1.4458.1000.1.5.25.1.2
Integer
RO
Channel Bandwidth availability product specific. Options are: Not supported supported with manual channel selection supported with Automatic Channel Selection.
DisplayString RO
Integer
RO
Indication for possible Link drop per CBW due to conflict between HSS and ATDD.
Integer
RO
Minimal TX ratio that may be used by the HSM and still enable proper operation of the aforementioned CBW.
Integer
RO
Maximal TX ratio that may be used by the HSM and still enable proper operation of the aforementioned CBW.
radwllMilOduAirRFD
1.3.6.1.4.1.4458.1000.1.5.26
Integer
RO
radwllMilOduAirRatesTable
N/A
radwllMilOduAirRatesEntry
N/A
radwllMilOduAirRatesIndex radwllMilOduAirRatesAvail
1.3.6.1.4.1.4458.1000.1.5.27.1.1 1.3.6.1.4.1.4458.1000.1.5.27.1.2
Integer Integer
RO RO
Air Rate index. Air Rate availability depending on air interface conditions.
radwllMilOduAirDesiredRateIdx
1.3.6.1.4.1.4458.1000.1.5.28
Integer
RW
Required Air Rate index. 0 reserved for Adaptive Rate. A change is effective immediately after Set operation to the master side while the link is up.
radwllMilOduAirLinkDistance
1.3.6.1.4.1.4458.1000.1.5.29
Integer
RO
A value of -1
indicates an illegal value and is also used when a link is not established. radwllMilOduAirLinkWorkingMode 1.3.6.1.4.1.4458.1000.1.5.30 Integer RO Link working mode as a result of comparing versions of both sides of the link. Possible modes are: Unknown - no with link Normal - versions on both sides are identical with full compatibility restricted compatibility or versions on both sides are different with software upgrade or versions incompatibility. radwllMilOduAirMajorLinkIfVersion 1.3.6.1.4.1.4458.1000.1.5.31 radwllMilOduAirMinorLinkIfVersion 1.3.6.1.4.1.4458.1000.1.5.32 radwllMilOduAirHssDesiredOpState 1.3.6.1.4.1.4458.1000.1.5.40.1 Integer Integer Integer RO RO RW Major link interface version Minor link interface version Required Hub Site Synchronization
I-12
MIB Parameters
Name
OID
Type
Description
operating state. radwllMilOduAirHssCurrentOpState 1.3.6.1.4.1.4458.1000.1.5.40.2 Integer RO Current Hub Site Synchronization operating state. radwllMilOduAirHssSyncStatus radwllMilOduAirHssExtPulseStatus 1.3.6.1.4.1.4458.1000.1.5.40.3 1.3.6.1.4.1.4458.1000.1.5.40.4 Integer Integer RO RO Hub Site Synchronization sync status. Hub Site Synchronization external pulse detection status. In GSS mode: if generating then 1PSP is auto generated by the GSS Unit. if generatingAndDetecting then 1PSP is generated by GPS satellites signal. radwllMilOduAirHssExtPulseType 1.3.6.1.4.1.4458.1000.1.5.40.5 Integer RO Hub Site Synchronization external pulse type. radwllMilOduAirHssDesiredExtPulse 1.3.6.1.4.1.4458.1000.1.5.40.6 Type Integer RW Hub Site Synchronization required external pulse type. Valid values for read write: {typeA(2) typeB(3) typeC(4) typeD(5) typeE(6)}. Valid value for read only: {notApplicable(1)}. radwllMilOduAirHssRfpTable radwllMilOduAirHssRfpEntry N/A N/A ODU Radio Frame Patterns (RFP) Table. ODU RFP Table entry. INDEX { radwllMilOduAirHssRfpIndex } radwllMilOduAirHssRfpIndex 1.3.6.1.4.1.4458.1000.1.5.40.7.1.1 Integer RO ODU RFP Table index. The index represent the Radio Frame Pattern: typeA(2) typeB(3) typeC(4) typeD(5) typeE(6). radwllMilOduAirHssRfpEthChannelB 1.3.6.1.4.1.4458.1000.1.5.40.7.1.2 W5MHz Integer RO Represents the compatibility of Ethernet service under Channel BW of 5MHz the specific Radio Frame Pattern. radwllMilOduAirHssRfpTdmChannel 1.3.6.1.4.1.4458.1000.1.5.40.7.1.3 BW5MHz Integer RO Represents the compatibility of TDM service under Channel BW of 5MHz the specific Radio Frame Pattern. radwllMilOduAirHssRfpEthChannelB 1.3.6.1.4.1.4458.1000.1.5.40.7.1.4 W10MHz Integer RO Represents the compatibility of Ethernet service under Channel BW of 10MHz the specific Radio Frame Pattern. radwllMilOduAirHssRfpTdmChannel 1.3.6.1.4.1.4458.1000.1.5.40.7.1.5 BW10MHz Integer RO Represents the compatibility of TDM service under Channel BW of 10MHz the specific Radio Frame Pattern. radwllMilOduAirHssRfpEthChannelB 1.3.6.1.4.1.4458.1000.1.5.40.7.1.6 W20MHz Integer RO Represents the compatibility of Ethernet service under Channel BW of 20MHz the specific Radio Frame Pattern. radwllMilOduAirHssRfpTdmChannel 1.3.6.1.4.1.4458.1000.1.5.40.7.1.7 BW20MHz Integer RO Represents the compatibility of TDM service under Channel BW of 20MHz the specific Radio Frame Pattern. radwllMilOduAirHssRfpEthChannelB RO Represents the compatibility of Ethernet in in in in in in
MIB Parameters
I-13
Name
OID
Type
Description
W40MHz
in
radwllMilOduAirHssRfpTdmChannel BW40MHz
RO
Represents the compatibility of TDM service under Channel BW of 40MHz the specific Radio Frame Pattern. in
radwllMilOduAirHssRfpStr
1.3.6.1.4.1.4458.1000.1.5.40.8
DisplayString RO
radwllMilOduAirHSSHsmID
1.3.6.1.4.1.4458.1000.1.5.40.9
Integer
RO
A unique ID which is common to the HSM and all its collocated ODUs
Hub Site Synchronization GPS time Hub Site Synchronization GPS Latitude Hub Site Synchronization GPS N/S Indicator
radwllMilOduAirHssLongitude radwllMilOduAirHssEWIndicator
1.3.6.1.4.1.4458.1000.1.5.40.13.0 1.3.6.1.4.1.4458.1000.1.5.40.14.0
DisplayString RO DisplayString RO
Hub Site Synchronization GPS Longitude Hub Site Synchronization GPS E/W Indicator
radwllMilOduAirHssNumSatellites
1.3.6.1.4.1.4458.1000.1.5.40.15.0
DisplayString RO
Hub Site Synchronization GPS Altitude Hub Site Synchronization GPS RFP phase This parameter enables locking the link with a specific ODU. values can be set: The following Unlock (default) - The
ODU is not locked on a specific remote ODU. Unlock can only be performed when the link is not connected. Lock - The ODU is locked on a specific remote ODU. Lock can only be performed when the link is active. radwllMilOduAirAntennaGain 1.3.6.1.4.1.4458.1000.1.5.42 Integer RW Current Antenna Gain in 0.1 dBi resolution. User defined value for external antenna. Legal range: MinAntennaGain<AntennaGain<MaxAntenn aGain. radwllMilOduAirFeederLoss 1.3.6.1.4.1.4458.1000.1.5.43 Integer RW Current Feeder Loss in 0.1 dBm resolution. User defined value for radwllMilOduAirMaxAntennaGain 1.3.6.1.4.1.4458.1000.1.5.44 Integer RO external antenna.
radwllMilOduAirMinAntennaGain
1.3.6.1.4.1.4458.1000.1.5.45
Integer
RO
radwllMilOduAirMaxEIRP
1.3.6.1.4.1.4458.1000.1.5.46
Integer
RO
I-14
MIB Parameters
Name
OID
Type
Description
regulation in 0.1 dBm resolution. radwllMilOduAirAntennaGainConfig 1.3.6.1.4.1.4458.1000.1.5.47 Support Integer RO Antenna Gain Configurability options are product specific: supported not supported. radwllMilOduAirAntennaType 1.3.6.1.4.1.4458.1000.1.5.48 Integer RW External Antenna Type: Monopolar or Bipolar. radwllMilOduAirRssBalance 1.3.6.1.4.1.4458.1000.1.5.49 Integer RO RSS balance. Relation between RSS in radio 1 and RSS in radio 2. radwllMilOduAirTotalTxPower 1.3.6.1.4.1.4458.1000.1.5.50 Integer RO Total Transmit Power in dBm. This is a nominal value While the actual transmit power includes additional attenuation. radwllMilOduAirInstallFreqAndCBW 1.3.6.1.4.1.4458.1000.1.5.51 radwllMilOduAirDFStype radwllMilOduAirComboSubBandTabl e radwllMilOduAirComboSubBandEntr y N/A ODU Multi-band Sub Bands Table entry. INDEX { radwllMilOduAirComboSubBandIndex } radwllMilOduAirComboSubBandInde 1.3.6.1.4.1.4458.1000.1.5.53.1.1.1 x radwllMilOduAirComboSubBandId 1.3.6.1.4.1.4458.1000.1.5.53.1.1.2 DisplayString RO DisplayString RO Represents the Multi-band sub band ID. Multi-band sub band description. Integer RO ODU Multi-band sub bands table index. 1.3.6.1.4.1.4458.1000.1.5.52 DisplayString RW Integer RO N/A Installation frequency Channel BW. DFS regulation type. ODU Multi-band Sub Bands Table.
radwllMilOduAirComboSubBandDes 1.3.6.1.4.1.4458.1000.1.5.53.1.1.3 cription radwllMilOduAirComboSubBandInst 1.3.6.1.4.1.4458.1000.1.5.53.1.1.4 allFreq radwllMilOduAirComboSubBandAdm 1.3.6.1.4.1.4458.1000.1.5.53.1.1.5 inState radwllMilOduAirComboSubBandInst 1.3.6.1.4.1.4458.1000.1.5.53.1.1.6 allationAllowed radwllMilOduAirComboFrequencyBa 1.3.6.1.4.1.4458.1000.1.5.53.1.1.7 ndId radwllMilOduAirComboNumberOfSu 1.3.6.1.4.1.4458.1000.1.5.53.2 bBands radwllMilOduAirComboSwitchSubBa 1.3.6.1.4.1.4458.1000.1.5.53.3 nd
Integer
RO
Integer
RO
Integer
RO
Integer
RO
Integer
RO
DisplayString RW
Switch sub band operation with a given sub band ID. The get operation retrieves the current sub band ID.
radwllMilOduAirInternalMaxRate
1.3.6.1.4.1.4458.1000.1.5.54
Integer
RO
radwllMilOduAirCapacityDirection
1.3.6.1.4.1.4458.1000.1.5.55
Integer
RW
MIB Parameters
I-15
Name
OID
Type
Description
Integer
RW
Spectrum Analysis operation state. Stop Start and Restart. supported on the device. is not a configurable state.
The
configurable values are Spectrum Analysis Not Supported Not Supported value indicates that the feature is not
radwllMilOduAirRxPowerAntennaA 1.3.6.1.4.1.4458.1000.1.5.56.2
Integer
RO
radwllMilOduAirRxPowerAntennaB 1.3.6.1.4.1.4458.1000.1.5.56.3
Integer
RO
Integer
RO
N/A
N/A
radwllMilOduAirSpectrumChannelIn 1.3.6.1.4.1.4458.1000.1.5.56.5.1.1 dex radwllMilOduAirSpectrumChannelFr 1.3.6.1.4.1.4458.1000.1.5.56.5.1.2 equency radwllMilOduAirSpectrumChannelSc 1.3.6.1.4.1.4458.1000.1.5.56.5.1.3 anned radwllMilOduAirSpectrumChannelSc 1.3.6.1.4.1.4458.1000.1.5.56.5.1.4 anningTimestamp
Integer
RO
Integer
RO
Integer
read-only
TimeTicks
RO
Channel last scan timestamp in hundredths of a second since device up time. If the channel was not scanned than the return value will be 0.
Integer
RO
Integer
RO
radwllMilOduAirSpectrumChannelAv 1.3.6.1.4.1.4458.1000.1.5.56.5.1.7 erageNFAntennaA radwllMilOduAirSpectrumChannelAv 1.3.6.1.4.1.4458.1000.1.5.56.5.1.8 erageNFAntennaB radwllMilOduAirSpectrumChannelM 1.3.6.1.4.1.4458.1000.1.5.56.5.1.9 axNFAntennaA radwllMilOduAirSpectrumChannelM 1.3.6.1.4.1.4458.1000.1.5.56.5.1.10 axNFAntennaB
Integer
RO
Average normalized Noise Floor value in dBm - of Antenna A - over all dwells.
Integer
RO
Average normalized Noise Floor value in dBm - of Antenna B - over all dwells.
Integer
RO
Max normalized Noise Floor value in dBm of Antenna A - over all dwells.
Integer
RO
Max normalized Noise Floor value in dBm of Antenna B - over all dwells.
I-16
MIB Parameters
Name
OID
Type
Description
Integer
RO
read-only
TimeTicks
RO
Last CAC performed timestamp in hundredths of a second since device up time. If no CAC has performed on the channel the return value will be 0.
Integer
RO
read-only
TimeTicks
RO
Last Radar Detection timestamp in hundredths of a second since device up time. If no Radar has detected on the channel the return value will be 0.
Integer
RO
read-only
Integer
RO
Description: Antenna configuration and Rates status (1 = Single antenna with single data stream 2 = Dual antenna with single data stream 3 = Dual antenna with dual data stream).
radwllMilOduAirDualAntTxMode
1.3.6.1.4.1.4458.1000.1.5.58
Integer
RW
Description: Transmission type when using Dual radios (MIMO or AdvancedDiversity using one stream of data).
radwllMilOduAirTxOperationMode
1.3.6.1.4.1.4458.1000.1.5.59
Integer
RW
This parameter controls the Operation mode of frames sent over the air. The Operation mode is either normal (1) for regular transmission where frame size is determined by the traffic or throughput test (2) when the user requests an actual over the air throughput estimation using full frames. sec). The latter lasts no more than a predetermined interval (default 30
radwllMilOduAirDesiredNetMasterTx 1.3.6.1.4.1.4458.1000.1.5.60.1 Ratio radwllMilOduAirCurrentNetMasterTx 1.3.6.1.4.1.4458.1000.1.5.60.2 Ratio radwllMilOduAirMinUsableMasterTx 1.3.6.1.4.1.4458.1000.1.5.60.3 Ratio radwllMilOduAirMaxUsableMasterTx 1.3.6.1.4.1.4458.1000.1.5.60.4 Ratio radwllMilOduAirAccumulatedUAS 1.3.6.1.4.1.4458.1000.1.5.61
Integer
RW
This parameter is reserved to the element manager provided with the product.
Integer
RO
Integer
RO
Represents the minimal value the user can configure for Desired net mAster Tx Ratio.
Integer
RO
Represents the maximal value the user can configure for Desired net mAster Tx Ratio.
Integer
RO
radwllMilOduPerfMonCurrTable
N/A
MIB Parameters
I-17
Name
OID
Type
Description
the current 15 min interval. radwllMilOduPerfMonCurrEntry N/A This is an entry in the Current Interval Table. INDEX {ifIndex } radwllMilOduPerfMonCurrUAS 1.3.6.1.4.1.4458.1000.1.6.1.1.1 Gauge RO The current number of Unavailable Seconds starting from the present 15 minutes period. radwllMilOduPerfMonCurrES 1.3.6.1.4.1.4458.1000.1.6.1.1.2 Gauge RO Current number of Errored Seconds starting from the present 15 minutes period. radwllMilOduPerfMonCurrSES 1.3.6.1.4.1.4458.1000.1.6.1.1.3 Gauge RO Current number of Severely Errored Seconds starting from the present 15 minutes period. radwllMilOduPerfMonCurrBBE 1.3.6.1.4.1.4458.1000.1.6.1.1.4 Gauge RO Current number of Background Block Errors starting from the present 15 minutes period. radwllMilOduPerfMonCurrIntegrity radwllMilOduPerfMonIntervalTable 1.3.6.1.4.1.4458.1000.1.6.1.1.5 Integer RO N/A Indicates the integrity of the entry. This table defines/keeps the counters of the last day (in resolution of 15 min intervals). radwllMilOduPerfMonIntervalEntry N/A This is an entry in the Interval Table. INDEX {ifIndex radwllMilOduPerfMonIntervalIdx } radwllMilOduPerfMonIntervalIdx RO This table is indexed per interval number. Each interval is of 15 minutes and the oldest is 96. radwllMilOduPerfMonIntervalUAS RO The current number of Unavailable Seconds per interval. radwllMilOduPerfMonIntervalES RO Current number of Errored Seconds per interval. radwllMilOduPerfMonIntervalSES RO Current number of Severely Errored Seconds per interval. radwllMilOduPerfMonIntervalBBE RO Current number of Background Block Errors per interval. radwllMilOduPerfMonIntervalIntegri ty radwllMilOduPerfMonDayTable N/A RO Indicates the integrity of the entry per interval. This table defines/keeps the counters of the last month (in resolution of days). radwllMilOduPerfMonDayEntry N/A This is an entry in the Days Table. INDEX {ifIndex radwllMilOduPerfMonDayIdx } radwllMilOduPerfMonDayIdx RO This table is indexed per interval number. Each interval is of 24 hours and the
I-18
MIB Parameters
Name
OID
Type
Description
oldest is 30. radwllMilOduPerfMonDayUAS RO The current number of Unavailable Seconds per interval of 24 hours. radwllMilOduPerfMonDayES RO Current number of Errored Seconds per interval of 24 hours. radwllMilOduPerfMonDaySES RO Current number of Severely Errored Seconds per interval of 24 hours. radwllMilOduPerfMonDayBBE RO Current number of Background Block Errors per interval of 24 hours. radwllMilOduPerfMonDayIntegrity RO Indicates the integrity of the entry per interval of 24 hours. radwllMilOduPerfMonAirCurrTable N/A This table defines/keeps the air counters of the current 15 min interval. radwllMilOduPerfMonAirCurrEntry N/A This is an entry in the Current Interval Table. INDEX {ifIndex } radwllMilOduPerfMonAirCurrMinRSL 1.3.6.1.4.1.4458.1000.1.6.4.1.1 Integer RO Current Min Received Level Reference starting from the present 15 minutes period. radwllMilOduPerfMonAirCurrMaxRSL 1.3.6.1.4.1.4458.1000.1.6.4.1.2 Integer RO Current Max Received Level Reference starting from the present 15 minutes period. radwllMilOduPerfMonAirCurrRSLThr 1.3.6.1.4.1.4458.1000.1.6.4.1.3 esh1Exceed Gauge RO Number of seconds Receive Signal Level exceeded the RSL1 threshold in the last 15 minutes. radwllMilOduPerfMonAirCurrRSLThr 1.3.6.1.4.1.4458.1000.1.6.4.1.4 esh2Exceed Gauge RO Number of seconds Receive Signal Level exceeded the RSL2 threshold in the last 15 minutes. radwllMilOduPerfMonAirCurrMinTSL 1.3.6.1.4.1.4458.1000.1.6.4.1.5 Integer RO Current Min Transmit Signal Level starting from the present 15 minutes period. radwllMilOduPerfMonAirCurrMaxTSL 1.3.6.1.4.1.4458.1000.1.6.4.1.6 Integer RO Current Max Transmit Signal Level starting from the present 15 minutes period. radwllMilOduPerfMonAirCurrTSLThr 1.3.6.1.4.1.4458.1000.1.6.4.1.7 esh1Exceed Gauge RO Number of seconds Transmit Signal Level exceeded the TSL1 threshold in the last 15 minutes. radwllMilOduPerfMonAirCurrBBERTh 1.3.6.1.4.1.4458.1000.1.6.4.1.8 resh1Exceed Gauge RO Number of seconds Background Block Error Ratio exceeded the BBER1 threshold in the last 15 minutes. radwllMilOduPerfMonAirIntervalTabl e N/A This table defines/keeps the air counters of the last day (in resolution of 15 min intervals). radwllMilOduPerfMonAirIntervalEntr N/A This is an entry in the Interval Table.
MIB Parameters
I-19
Name
OID
Type
Description
radwllMilOduPerfMonAirIntervalIdx
RO
This table is indexed per interval number. Each interval is of 15 minutes and the oldest is 96.
RO
RO
RO
Number of seconds Receive Signal Level exceeded the RSL1 threshold per interval.
RO
Number of seconds Receive Signal Level exceeded the RSL2 threshold ACCESS read-only per interval.
RO
RO
RO
Number of seconds Transmit Signal Level exceeded the TSL1 threshold per interval.
RO
Number of seconds Background Block Error Ratio exceeded the BBER1 threshold per interval.
radwllMilOduPerfMonAirDayTable
N/A
This table defines/keeps the air counters of the last month (in resolution of days).
radwllMilOduPerfMonAirDayEntry
N/A
radwllMilOduPerfMonAirDayIdx
RO
This table is indexed per Day number. Each Day is of 15 minutes and the oldest is 96.
radwllMilOduPerfMonAirDayMinRSL
RO
radwllMilOduPerfMonAirDayMaxRSL
RO
RO
Number of seconds Receive Signal Level exceeded the RSL1 threshold per Day.
RO
Number of seconds Receive Signal Level exceeded the RSL2 threshold per Day.
RO RO
Current Min Transmit Signal Level per Day. Current Max Transmit Signal Level per Day.
I-20
MIB Parameters
Name
OID
Type
Description
RO
Number of seconds Transmit Signal Level exceeded the TSL1 threshold per Day.
RO
Number of seconds Background Block Error Ratio exceeded the BBER1 threshold per Day.
radwllMilOduPerfMonEthCurrTable
N/A
This table defines/keeps the ethernet counters of the current 15 min interval.
radwllMilOduPerfMonEthCurrEntry
N/A
Gauge
RO
Gauge
RO
Current Transmit Mega Bytes starting from the present 15 minutes period.
Gauge
RO
The number of times throughput was below threshold in the present 15 minutes period.
Gauge
RO
The number of times actual traffic was above threshold in the present 15 minutes period.
Gauge
RO
The number of seconds in which RPL Ethernet swervice was not blocked in the present 15 minutes period.
radwllMilOduPerfMonEthIntervalTab le
N/A
This table defines/keeps the ethernet counters of the last day (in resolution of 15 min intervals).
radwllMilOduPerfMonEthIntervalEnt ry
N/A
radwllMilOduPerfMonEthIntervalIdx
RO
This table is indexed per interval number. Each interval is of 15 minutes and the oldest is 96.
radwllMilOduPerfMonEthIntervalRx MBytes radwllMilOduPerfMonEthIntervalTx MBytes radwllMilOduPerfMonEthIntervalEth CapacityThreshUnder radwllMilOduPerfMonEthIntervalHig hTrafficThreshExceed radwllMilOduPerfMonEthIntervalActi veSeconds
RO
RO
RO
The number of times throughput was below threshold in the each interval.
RO
The number of times actual traffic was above threshold in the each interval.
RO
The number of seconds in which RPL Ethernet service was not blocked in the
MIB Parameters
I-21
Name
OID
Type
Description
each interval. radwllMilOduPerfMonEthDayTable N/A This table defines/keeps the ethernet counters of the last month (in resolution of days). radwllMilOduPerfMonEthDayEntry N/A This is an entry in the Days Table. INDEX {ifIndex radwllMilOduPerfMonEthDayIdx } radwllMilOduPerfMonEthDayIdx RO This table is indexed per Day number. Each interval is of 15 minutes and the oldest is 96. radwllMilOduPerfMonEthDayRxMByt es radwllMilOduPerfMonEthDayTxMByt es radwllMilOduPerfMonEthDayEthCap acityThreshUnder radwllMilOduPerfMonEthDayHighTr afficThreshExceed radwllMilOduPerfMonEthDayActiveS econds RO RO RO The number of times throughput was below threshold each day. The number of times actual traffic was above threshold each day. The number of seconds in which RPL Ethernet service was not blocked each day. radwllMilOduPerfMonTdmCurrTable N/A This table defines/keeps the TDM counters of the current 15 min interval. radwllMilOduPerfMonTdmCurrEntry N/A This is an entry in the Current Interval Table. INDEX {ifIndex } radwllMilOduPerfMonTdmCurrActive 1.3.6.1.4.1.4458.1000.1.6.10.1.1 Seconds Gauge RO Parameter indicating whether the TDM service was active. Under TDM backup link the parameter indicates whether the backup link was active. radwllMilOduPerfMonTdmIntervalTa ble N/A This table defines/keeps the TDM counters of the last day (in resolution of 15 min intervals). radwllMilOduPerfMonTdmIntervalEn try N/A This is an entry in the Interval Table. INDEX {ifIndex radwllMilOduPerfMonTdmIntervalIdx } radwllMilOduPerfMonTdmIntervalIdx RO This table is indexed per interval number. Each interval is of 15 minutes and the oldest is 96. radwllMilOduPerfMonTdmIntervalAc tiveSeconds RO Parameter indicating whether the TDM service was active. Under TDM backup link the parameter indicates whether the backup link was active. RO Current Transmit Mega Bytes per day. RO Current RX Mega Bytes per day.
I-22
MIB Parameters
Name
OID
Type
Description
radwllMilOduPerfMonTdmDayTable
N/A
This table defines/keeps the TDM counters of the last month (in resolution of days).
radwllMilOduPerfMonTdmDayEntry
N/A
radwllMilOduPerfMonTdmDayIdx
RO
This table is indexed per Day number. Each interval is of 15 minutes and the oldest is 96.
radwllMilOduPerfMonTdmDayActive Seconds
RO
Parameter indicating whether the TDM service was active. Under TDM backup link the parameter indicates whether the backup link was active.
radwllMilOduPerfMonTxThresh1
1.3.6.1.4.1.4458.1000.1.6.20
Integer
RW
When the Transmit power exceeds this threshold a performance monitoring TSL1 counter is incremented.
radwllMilOduPerfMonRxThresh1
1.3.6.1.4.1.4458.1000.1.6.21
Integer
RW
When the RX power exceeds this threshold a performance monitoring RSL1 counter is incremented.
radwllMilOduPerfMonRxThresh2
1.3.6.1.4.1.4458.1000.1.6.22
Integer
RW
When the RX power exceeds this threshold a performance monitoring RSL2 counter is incremented.
radwllMilOduPerfMonBBERThresh1 1.3.6.1.4.1.4458.1000.1.6.23
Integer
RW
When the BBER exceeds this threshold a performance monitoring BBER counter is incremented. The units are 1/10 of a percent.
Integer
RW
When the current throughput is below this threshold the corresponding counter is incremented
Integer
RW
When the current traffic is above this threshold then corresponding counter is incremented.
radwllMilOduAgnGenAddTrapExt
1.3.6.1.4.1.4458.1000.1.7.1.1
Integer
RW
If 'yes' is chosen the ifIndex Unit Severity Time_T and Alarm Id from the radwllMilOduAgnCurrAlarmTable will be bind to the end of each private trap.
radwllMilOduAgnGenSetMode
1.3.6.1.4.1.4458.1000.1.7.1.2
Integer
RW
This parameter is reserved to the element manager provided with the product.
IpAddress
RW
Integer
RW
OctetString
RW
This parameter specifies the real time and date Format 'YYYY-MM-DD
MIB Parameters
I-23
Name
OID
Type
Description
HH:MM:SS' (Hexadecimal). range 1 2 3 4 5 6 7 1-2 year 3 4 5 6 7 8 month day hour minutes seconds deci-seconds
A date-
time specification: field octets contents 0..65536 1..12 1..31 0..23 0..59 0..60
(use 60 for leap-second) 0..9 For example Tuesday May 26 1992 at 1:30:15 PM EDT would be displayed as: 07 c8 05 1a 0d 1e 0f 00 (1992 -5 -26 13:30:15) radwllMilOduAgnCurrAlarmLastChan 1.3.6.1.4.1.4458.1000.1.7.3.1 ge Integer RO This counter is initialized to 0 after a device reset and is incremented upon each change in the radwllMilOduAgnCurrAlarmTable (either an addition or removal of an entry). radwllMilOduAgnCurrAlarmTable N/A This table includes the currently active alarms. When a RAISED trap is sent an alarm entry is added to the table. When a CLEAR trap is sent the entry is removed. radwllMilOduAgnCurrAlarmEntry N/A Entry containing the details of a currently RAISED trap. INDEX { radwllMilOduAgnCurrAlarmCounter } radwllMilOduAgnCurrAlarmCounter 1.3.6.1.4.1.4458.1000.1.7.3.2.1.1 Integer RO A running counter of active alarms. The counter is incremented for every new RAISED trap. It is cleared after a device reset. radwllMilOduAgnCurrAlarmSeverity 1.3.6.1.4.1.4458.1000.1.7.3.2.1.2 radwllMilOduAgnCurrAlarmId 1.3.6.1.4.1.4458.1000.1.7.3.2.1.3 Integer Integer RO RO Current Alarm severity. Unique Alarm Identifier (combines alarm type and interface). The same AlarmId is used for RAISED and CLEARED alarms. radwllMilOduAgnCurrAlarmIfIndex 1.3.6.1.4.1.4458.1000.1.7.3.2.1.4 Integer RO Interface Index where the alarm occurred. Alarms that are value: 65535. radwllMilOduAgnCurrAlarmUnit radwllMilOduAgnCurrAlarmTrapID 1.3.6.1.4.1.4458.1000.1.7.3.2.1.5 1.3.6.1.4.1.4458.1000.1.7.3.2.1.6 Integer Integer RO RO Unit associated with the alarm. ID of the raised trap that was sent when this alarm was raised. radwllMilOduAgnCurrAlarmTimeT 1.3.6.1.4.1.4458.1000.1.7.3.2.1.7 Integer RO Timestamp of this alarm. This number is in seconds from Midnight January 1st 1970. not associated with a specific interface will have the following
I-24
MIB Parameters
Name
OID
Type
Description
radwllMilOduAgnCurrAlarmText
1.3.6.1.4.1.4458.1000.1.7.3.2.1.8
DisplayString RO
radwllMilOduAgnLastEventsNumber 1.3.6.1.4.1.4458.1000.1.7.4.1
Integer
RO
radwllMilOduAgnLastEventsTable
N/A
This table includes the last events. When a trap is to the table. sent an event entry is added
radwllMilOduAgnLastEventsEntry
N/A
radwllMilOduAgnLastEventsIndex
1.3.6.1.4.1.4458.1000.1.7.4.2.1.1
RO RO RO
The index of the table Current Trap severity. Interface Index where the event occurred. Traps that are value: 65535. not associated with a specific interface will have the following
radwllMilOduAgnLastEventsTimeT
1.3.6.1.4.1.4458.1000.1.7.4.2.1.4
Integer
RO
Timestamp of this trap. This number is in seconds from Midnight January 1st 1970.
radwllMilOduAgnLastEventsText
1.3.6.1.4.1.4458.1000.1.7.4.2.1.5
DisplayString RO
IDU configuration description. IDU Hardware Revision. IDU Software Revision. Indicates the number of currently available External Alarm Inputs.
N/A
N/A
Entry containing the elements of a single External Alarm Input. INDEX { radwllMilOduAdmExternAlarmInIndex}
Integer
RO
This value indicates the index of the External Alarm Input entry.
DisplayString RW
This field describes the External Alarm Input. It is an optional string of no more than 64 characters which will be used in the event being sent as a result of a change in the status of the External Alarm Input. DEFVAL {Alarm Description}
Integer
RW
Integer
RO
MIB Parameters
I-25
Name
OID
Type
Description
the External Alarm Input. IDU Serial Number The parameter defines whether to send Ethernet frames to detect an IDU. The valid writable values are: userDisabled (3) userEnabled (4). A change requires a reset and is effective after reset.
radwllMilIduAdmIduDetectionMode 1.3.6.1.4.1.4458.1000.2.1.7
RO RO RO
Number of mounted trunks in the IDU Number of Licensed Trunks in the IDU Identifies if the local IDU supports VLAN tag/untag
radwllMilIduAdmVlanEgressMode radwllMilIduAdmVlanIngressMode
1.3.6.1.4.1.4458.1000.2.1.11 1.3.6.1.4.1.4458.1000.2.1.12
VLAN tag/untag egress values VLAN tag/untag ingress values VLAN tag/untag default VLAN ids for each port - Right most digit is Vlan priority (06) other digits compose Vlan Id (1-4094)
radwllMilIduAdmVlanDefaultPortVID 1.3.6.1.4.1.4458.1000.2.1.13 s
radwllMilIduAdmVlanLan1Untagged 1.3.6.1.4.1.4458.1000.2.1.14 VIDs radwllMilIduAdmVlanLan2Untagged 1.3.6.1.4.1.4458.1000.2.1.15 VIDs radwllMilIduAdmVlanSfpUntaggedVI 1.3.6.1.4.1.4458.1000.2.1.16 Ds radwllMilIduAdmVlanLan1FilteredVI 1.3.6.1.4.1.4458.1000.2.1.17 Ds radwllMilIduAdmVlanLan2FilteredVI 1.3.6.1.4.1.4458.1000.2.1.18 Ds radwllMilIduAdmVlanSfpFilteredVIDs 1.3.6.1.4.1.4458.1000.2.1.19 radwllMilIduSrvDesiredTrunks 1.3.6.1.4.1.4458.1000.2.2.2
DisplayString RW
DisplayString RW
DisplayString RW
DisplayString RW
DisplayString RW
DisplayString RW Integer RW
VLAN filtered VIDs for Sfp port Required trunks bitmap. Note that the number of possible trunks that can be configured may vary based on the IDU hardware configuration the selected air interface rate and the range of the installation. The provided Manager application enables the user to select only available configurations. A change is effective immediately if applied to a master unit and the link is in service mode.
radwllMilIduSrvServices
1.3.6.1.4.1.4458.1000.2.2.4
ObjectID
RO
This parameter is reserved to the Manager application provided with the product.
radwllMilIduSrvActiveTrunks
1.3.6.1.4.1.4458.1000.2.2.6
Integer
RO
I-26
MIB Parameters
Name
OID
Type
Description
TDM trunks. radwllMilIduSrvAvailableTrunks 1.3.6.1.4.1.4458.1000.2.2.8 Integer RO A bitmap describing the number of TDM trunks that can be opened in the current configuration. The values take into account the IDU hardware configuration the air rate and the installation range. radwllMilIduSrvPossibleServicesTabl e radwllMilIduSrvPossibleServicesEntr y radwllMilIduSrvPossibleServicesInde 1.3.6.1.4.1.4458.1000.2.2.10.1.1 x radwllMilIduSrvPossibleTdmServices 1.3.6.1.4.1.4458.1000.2.2.10.1.2 Integer RO Integer RO N/A IDU Services table entry. INDEX { radwllMilIduSrvPossibleServicesIndex } Table index Rate index of the air interface. Deprecated parameter. A bitmap describing the TDM trunks that can be opened in the corresponding Air Rate. radwllMilIduSrvPossibleEthServices 1.3.6.1.4.1.4458.1000.2.2.10.1.3 Integer RO Deprecated parameter. This parameter describes if the Ethernet Service can be opened in the corresponding Air Rate. The valid values are: disabled (0) enabled (1). radwllMilIduSrvRemainingRate 1.3.6.1.4.1.4458.1000.2.2.10.1.4 Integer RO Current Ethernet bandwidth in bps per air rate. radwllMilIduSrvTrunkCost radwllMilIduSrvAvailServicesTable radwllMilIduSrvAvailServicesEntry 1.3.6.1.4.1.4458.1000.2.2.10.1.5 Integer RO N/A N/A Cost of the TDM Service in bps. ODU Possible TDM Services table. ODU TDM Services table entry. INDEX { radwllMilIduSrvAvailServicesIndex } radwllMilIduSrvAvailServicesIndex 1.3.6.1.4.1.4458.1000.2.2.11.1.1 Integer RO Table index. The index is the bit mask of the TDM service. radwllMilIduSrvAvailServicesState 1.3.6.1.4.1.4458.1000.2.2.11.1.2 Integer Integer RO RO Represents the TDM service availability. Minimum rate index of the air interface which make the service possible. Integer RO Maximum rate index of the air interface which make the service possible. Integer RO Information about the TDM Service availability. - Not Applicable if the The reasons for TDM - The available service is available. Service unavailability: demands; the service; was detected; N/A IDU Possible Services table.
throughput isn't sufficient for Service - The IDU HW doesn't support - A Link Password mismatch - The external pulse type -
MIB Parameters
I-27
Name
OID
Type
Description
A Software versions mismatch was detected. Obligated. radwllMilIduSrvEthActive 1.3.6.1.4.1.4458.1000.2.2.12 Integer RO Represents the Ethernet service activation state. radwllMilIduSrvEthAvailable 1.3.6.1.4.1.4458.1000.2.2.13 Integer RO Represents the Ethernet service availability state. radwllMilIduSrvEthThroughput 1.3.6.1.4.1.4458.1000.2.2.14 Gauge RO Current available Ethernet service throughput in bps. radwllMilIduSrvEthMaxInfoRate 1.3.6.1.4.1.4458.1000.2.2.15 Integer RW Holds the maximum bandwidth (kbps) to be allocated for Ethernet service. as best effort. Value of zero means that Ethernet service works The maximum value is product specific. Refer to the user manual. radwllMilIduSrvAvailableTrunksT1 1.3.6.1.4.1.4458.1000.2.2.16 Integer RO A bitmap describing the TDM trunks that can be opened under T1 configuration. The values take into account the IDU hardware configuration the air rate and the installation range. radwllMilIduEthernetIfTable radwllMilIduEthernetIfEntry N/A N/A IDU Ethernet Interface table. IDU Ethernet Interface table entry. INDEX { radwllMilIduEthernetIfIndex } radwllMilIduEthernetIfIndex radwllMilIduEthernetIfAddress 1.3.6.1.4.1.4458.1000.2.3.1.1.5 RO DisplayString RO Integer RO If Index corresponding to this Interface. IDU MAC address. Number of LAN interfaces in the IDU. - A-Symetric TDD Mode Is
Integer
RO
DisplayString RO
radwllMilIduBridgeTpAging
1.3.6.1.4.1.4458.1000.2.4.4.2
Integer
RW
Timeout in seconds for aging. Note that for this parameter to be effective change is effective immediately. the ODU must be configured to HUB mode. A
radwllMilIduTdmTxClockAvailStates 1.3.6.1.4.1.4458.1000.2.6.1.1
Integer
RO
Available states of the TDM Transmit Clock Control each input status is represented by a bit. When the state is available the bit value is 1. When the state is unavailable the bit available states are: value is 0. The bit 2 = Transparent
bit 3 = Local Loop Timed bit 4 = Remote Loop Timed bit 5 = Local Internal bit 6 =
I-28
MIB Parameters
Name
OID
Type
Description
Remote Internal radwllMilIduTdmTxClockDesiredStat 1.3.6.1.4.1.4458.1000.2.6.1.2 e Integer RW Required state of the TDM Transmit Clock Control. A change is effective after reactivation of the TDM service. radwllMilIduTdmTxClockActualState 1.3.6.1.4.1.4458.1000.2.6.1.3 Integer RO Actual state of the TDM Transmit Clock Control. radwllMilIduTdmMasterClockAvailOp 1.3.6.1.4.1.4458.1000.2.6.2.1 tions Integer RO Available options of the TDM Master Clock Control each input status is represented by a bit. When the option is available the bit value is 1. When the option is unavailable the bit value is 0. The available options are: bit 2 = Automatic bit 3 = Trunk #1 bit 4 = Trunk #2 bit 5 = Trunk #3 bit 6 = Trunk #4 When no options are available the returned value is: 1 radwllMilIduTdmMasterClockDesired 1.3.6.1.4.1.4458.1000.2.6.2.2 Integer RW Required TDM Master Clock. A change is effective after re-activation of the TDM service. radwllMilIduTdmMasterClockActual 1.3.6.1.4.1.4458.1000.2.6.2.3 radwllMilIduTdmConfigTable radwllMilIduTdmConfigEntry Integer RO N/A N/A Actual Trunk used for TDM Master Clock. IDU TDM Links Configuration table. IDU TDM Links Configuration table entry. INDEX { radwllMilIduTdmConfigIndex } radwllMilIduTdmConfigIndex radwllMilIduTdmIfIndex radwllMilIduTdmLineCoding 1.3.6.1.4.1.4458.1000.2.6.6.1.6 Integer RO RO RW Table index. Link index in the interface table. This parameter applies to T1 trunks only. The parameter controls the line coding. Setting the value to each of the indices applies to all. A change is effective after the next open of the TDM service. radwllMilIduTdmLoopbackConfig 1.3.6.1.4.1.4458.1000.2.6.6.1.9 Integer RW Loop back configuration table. Each of the trunks can be set Normal Line loop back or Reverse line loop back. A change is effective immediately. radwllMilIduTdmLineStatus radwllMilIduTdmCurrentTable radwllMilIduTdmCurrentEntry 1.3.6.1.4.1.4458.1000.2.6.6.1.10 Integer RO N/A N/A Line status. IDU TDM Links Statistics table. IDU TDM Links Statistics table entry. INDEX { radwllMilIduTdmCurrentIndex } radwllMilIduTdmCurrentIndex RO Table index (Same as radwllMilIduTdmLineIndex). radwllMilIduTdmCurrentBlocks 1.3.6.1.4.1.4458.1000.2.6.7.1.101 Counter RO Number of correct blocks transmitted to
MIB Parameters
I-29
Name
OID
Type
Description
the line. radwllMilIduTdmCurrentDrops 1.3.6.1.4.1.4458.1000.2.6.7.1.102 Counter RO Number of error blocks transmitted to the line. radwllMilIduTdmCurrentTxClock 1.3.6.1.4.1.4458.1000.2.6.7.1.103 Integer RW TDM Transmit Clock. A change is effective after re-activation of the TDM service. radwllMilIduTdmCurrentBlocksHigh 1.3.6.1.4.1.4458.1000.2.6.7.1.104 Counter RO High part of the 64 bits counter Current Blocks radwllMilIduTdmRemoteQual 1.3.6.1.4.1.4458.1000.2.6.8 Integer RO Estimated average interval between error second events. The valid values are 12^31 where a value of -1 is used to indicate an undefined state. radwllMilIduTdmRemoteQualEval 1.3.6.1.4.1.4458.1000.2.6.9 Integer RO Estimated average interval between error second events during evaluation process. The valid values are 1-2^31 where a value of -1 is used to indicate an undefined state. radwllMilIduTdmSrvEval 1.3.6.1.4.1.4458.1000.2.6.10 Integer RW Evaluated TDM service bit mask. Setting this parameter to value that is bigger than the activated TDM service bit mask seconds. will execute the evaluation process for 30 Setting this parameter to 0 will stop the evaluation process immediately. radwllMilIduTdmBackupAvailableLin 1.3.6.1.4.1.4458.1000.2.6.11 ks radwllMilIduTdmBackupTable radwllMilIduTdmBackupEntry N/A N/A IDU TDM Links Statistics table. IDU TDM Links Statistics table entry. INDEX { radwllMilIduTdmBackupIndex } radwllMilIduTdmBackupIndex radwllMilIduTdmBackupMode 1.3.6.1.4.1.4458.1000.2.6.12.1.1 1.3.6.1.4.1.4458.1000.2.6.12.1.2 Integer Integer RO RW Table index. TDM backup mode: Enable or Disable where the external link. immediatly. radwllMilIduTdmBackupCurrentActiv 1.3.6.1.4.1.4458.1000.2.6.12.1.3 eLink radwllMilIduTdmJitterBufferSize 1.3.6.1.4.1.4458.1000.2.6.13 Integer RW Integer RO TDM backup current active link: N/A link is active or external link is active. TDM Jitter Buffer Size. The value must The air main link is the air link or the Changes will be effective Integer RO Number of TDM backup trunks.
be between the minimum and the maximum TDM Jitter Buffer Size. units are 0.1 x millisecond. radwllMilIduTdmJitterBufferDefaultS 1.3.6.1.4.1.4458.1000.2.6.14 ize radwllMilIduTdmJitterBufferMinSize 1.3.6.1.4.1.4458.1000.2.6.15 Integer RO Integer RO TDM Jitter Buffer Default Size. The units are 0.1 x millisecond. TDM Jitter Buffer Minimum Size. The units are 0.1 x millisecond.
I-30
MIB Parameters
Name
OID
Type
Description
radwllMilIduTdmJitterBufferMaxSize 1.3.6.1.4.1.4458.1000.2.6.16
Integer
RO
TDM Jitter Buffer Maximum Size. The units are 0.1 x millisecond.
radwllMilIduTdmJitterBufferSizeEval 1.3.6.1.4.1.4458.1000.2.6.17
Integer
RW
TDM Jitter Buffer Size for evaluation. The value must be between the minimum and the maximum TDM Jitter Buffer Size. The units are 0.1 x millisecond.
radwllMilIduTdmType
1.3.6.1.4.1.4458.1000.2.6.18
Integer
RW
radwllMilIduTdmTypeEval radwllMilIduTdmLineStatusStr
1.3.6.1.4.1.4458.1000.2.6.19 1.3.6.1.4.1.4458.1000.2.6.20
Integer
RW
TDM Type for evaluation. Line status. Indicates if Hot Standby is supported. Desired Hot Standby Mode.
radwllMilIduTdmHotStandbySupport 1.3.6.1.4.1.4458.1000.2.6.21 radwllMilIduTdmDesiredHotStandby 1.3.6.1.4.1.4458.1000.2.6.22 Mode radwllMilIduTdmHotStandbyOperati 1.3.6.1.4.1.4458.1000.2.6.23 onStatus radwllMilIduTdmBackupLinkConfigur 1.3.6.1.4.1.4458.1000.2.6.24 ation radwllMilGeneralTrapDescription 1.3.6.1.4.1.4458.1000.100.1
Integer
RO
Integer
RW
DisplayString RO
radwllMilGeneralTrapSeverity radwllMilGeneralCookie
1.3.6.1.4.1.4458.1000.100.2 1.3.6.1.4.1.4458.1000.100.3
Integer
RO
Trap's Severity. Used for Trap parameters. Reserved for the Manager application provided with the product used for saving user preferences affecting ODU operation.
DisplayString RW
radwllMilGeneralEcChangesCounter 1.3.6.1.4.1.4458.1000.100.4
Integer
RO
This counter is initialized to 0 after a device reset and is incremented upon each element constant write operation via SNMP or Telnet.
radwllMilGeneralTelnetSupport
1.3.6.1.4.1.4458.1000.100.5
Integer
RW
I.4
MIB Traps
Each ODU can be configured with up to 10 different trap destinations. When the link is operational, each ODU sends traps originating from both Site A and Site B. The source IP address of the trap is the sending ODU. The trap originator can be identified by the trap Community string or by the trap description text. Each trap contains a trap description and additional relevant information such as alarm severity, interface index, time stamp and additional parameters. See Table I-3 for additional information.
Airmux-200 Ver. 1.9.3 MIB Traps I-31
I-32
MIB Traps
Name probingChannel
ID 12
Severity normal
Description Indicates that the ODU is monitoring radar activity. Contains a single parameter which is its description: 1 - Description: Monitoring for radar activity on channel %n GHz. %n is the channel frequency in GHz.
radarDetected
13
normal
Indicates that radar activity was detected. Contains a single parameter which is its description: 1 - Description: Radar activity was detected in %s on channel %n GHz. %s Is the site name. %n Is the channel frequency in GHz.
transmittingOnChannel
14
normal
Indicates that the ODU is transmitting on channel. Contains a single parameter which is its description: 1 - Description: Transmitting on channel %n GHz. %n Is the channel frequency in GHz.
scanningChannels
15
normal
Indicates that the ODU is scanning channels. Contains a single parameter which is its description: 1 - Description: Channel scanning in progress.
incompatiblePartner
16
critical
Indicates that configuration problem was detected and that link installation is required in order to fix it. Contains a single parameter which is its description: 1 - Description: Configuration problem detected. Link installation required.
timeClockSet
17
normal
Indicates that the ODU time clock was set. Contains a single parameter which is its description: 1 - Description: The time was set to: %p. %p Is the date and time.
configurationChanged
18
normal
Indicates that the ODU recovered from an error but there are configuration changes. Contains two parameters: 1 - Description: Configuration changed. Error code is: %n. 2 - %n number.
hssOpStateChangedToINU
19
normal
Indicates that the HSS operating state was changed to INU type. Contains a single parameter which is its description: 1 - Description: HSS operating state was changed to: INU.
hssOpStateChangedToHSM
20
normal
Indicates that the HSS operating state was changed to HSM type. Contains a single parameter which is its description: 1 - Description: HSS operating state was changed to: HSM.
hssOpStateChangedToHSC
21
normal
Indicates that the HSS operating state was changed to HSC type. Contains a single parameter which is its description: 1 - Description: HSS operating state was changed to: HSC_DT/HSC_CT.
vlanModeActive
22
normal
Indicates to non-VLAN PC that after 2 minutes the system will support only VLAN tag on management interface. Contains a single parameter which is its description: 1 - Description: VLAN Mode is active. Non-VLAN traffic will be blocked in 2 minutes.
spectrumAnalysis
23
normal
Indicates that the ODU is in Spectrum Analysis mode. Contains a single parameter which is its description: 1 -
MIB Traps
I-33
Name
ID
Severity
Description
I-34
MIB Traps
Name mngPortDisconnectedAlarm
ID 111
Severity major
Description Indicates the management port status changed to disconnected.Contains a single parameter which is its description: 1 - Description: Management port status changed to disconnected.
externalAlarmInPort3Alarm
112
major
The trap is sent every time an alarm occurs in the External Alarm Input of port #3. Contains a single parameter which is its description: 1 - Description: External Alarm 3 - <User Text> - Alarm.
externalAlarmInPort4Alarm
113
major
The trap is sent every time an alarm occurs in the External Alarm Input of port #4. Contains a single parameter which is its description: 1 - Description: External Alarm 4 - <User Text> - Alarm.
swVersionsMismatchFullCompatibilityAlarm
114
warning
The trap is sent if SW versions mismatch with full link functionality. Contains a single parameter which is its description: 1 - Description: Software versions mismatch - full link functionality
swVersionsMismatchRestrictedCompatibilityAlar m
115
minor
The trap is sent if SW versions mismatch with restricted link functionality. Contains a single parameter which is its description: 1 - Description: Software versions mismatch - restricted link functionality
swVersionsMismatchSoftwareUpgradeRequired
116
major
The trap is sent if SW versions mismatch and SW upgrade is required. Contains a single parameter which is its description: 1 Description: Software versions mismatch - Software upgrade required
swVersionsIncompatible
117
critical
The trap is sent if SW versions are incompatible. Contains a single parameter which is its description: 1 - Description: SW Versions incompatible
hssMultipleSourcesDetectedAlarm
118
major
Indicates that multiple sync pulse sources were detected. Contains a single parameter which is its description: 1 - Description: HSS multiple sync sources were detected.
hssSyncToProperSourceStoppedAlarm
119
major
Indicates that synchronization to a proper sync pulse source was stopped. Contains a single parameter which is its description: 1 Description: HSS sync pulse - Down. The reason is: %s. %s - Is the reason for the sync down.
hssSyncPulseDetectedAlarm
120
major
Indicates that HSS additional sync pulse was detected. Contains a single parameter which is its description: 1 - Description: HSS additional sync pulse was detected.
tdmBackupAlarm
121
major
Indicates that the TDM backup link was activated. Contains a single parameter which is its description: 1 - Description: TDM backup alarm - backup link was activated.
linkLockUnauthorizedRemoteODU
122
major
Indicates that the remote ODU is unauthorized.Contains a single parameter which is its description: 1 - Description: Unauthorized remote ODU connection rejected.
MIB Traps
I-35
Name linkLockUnauthorizedODU
ID 123
Severity major
Description Indicates that the ODU is unauthorized.Contains a single parameter which is its description: 1 - Description: Unauthorized ODU connection rejected.
hotStandbyAlarm
124
major
Indicates that the hot standby secondary link was activated. Contains a single parameter which is its description: 1 - Description: Secondary Link Is Active.
sfpInsertion sfpPort1DisconnectedAlarm
126 127
major major
Indicates that a device was inserted to SFP Port Indicates the SFP port 1 status changed to disconnected.Contains a single parameter which is its description: 1 - Description: SFP port 1 status changed to disconnected.
desiredRatioCanNotBeAppliedAlarm
cbwMismatch
129 normal
130 major
gpsNotSynchronized
131
major
Indicates that the GPS is not synchronized with satellites. Pulses are self generated.
tdmServiceClear
200
normal
Indicates that TDM Service fault is cleared. Contains a single parameter which is its description: 1 - Description: TDM Service Normal.
ethServiceOpened
201
normal
Indicates that Ethernet Service has been opened. Contains a single parameter which is its description: 1 - Description: Ethernet Service has been opened.
encryptionClear
203
normal
Indicates that encryption is OK. Contains a single parameter which is its description: 1 - Description: Encryption Status - Normal.
changeLinkPasswordClear
204
normal
Indicates that the Link Password was changed successfully. Contains a single parameter which is its description: 1 - Description: Link Password has been changed at/on: %s. %s - Is the Local Site name or Remote Site name or both sides of the Link.
externalAlarmInPort1Clear
205
normal
This Trap is sent every time an External Alarm Input fault of port # 1 is cleared. Contains a single parameter which is its description: 1 Description: External Alarm 1 - <User Text> - Alarm Cleared.
externalAlarmInPort2Clear
206
normal
This Trap is sent every time an External Alarm Input fault of port # 2 is cleared. Contains a single parameter which is its description: 1 Description: External Alarm 2 - <User Text> - Alarm Cleared.
I-36
MIB Traps
Name lanPort1Clear
ID 209
Severity normal
Description Indicates the LAN port 1 status changed to connected. Contains two parameters: 1 - Description: LAN port 1 status changed to connected - %s 2 - %s Is the Eth. mode (speed & duplex)
lanPort2Clear
210
normal
Indicates the LAN port 2 status changed to connected. Contains two parameters: 1 - Description: LAN port 2 status changed to connected - %s. 2 - %s Is the Eth. mode (speed & duplex).
mngPortClear
211
normal
Indicates the management port status changed to connected. Contains two parameters: 1 - Description: Management port status changed to connected - %s 2 - %s Is the Eth. mode (speed & duplex)
externalAlarmInPort3Clear
212
normal
This Trap is sent every time an External Alarm Input fault of port # 3 is cleared. Contains a single parameter which is its description: 1 Description: External Alarm 3 - <User Text> - Alarm Cleared.
externalAlarmInPort4Clear
213
normal
This Trap is sent every time an External Alarm Input fault of port # 4 is cleared. Contains a single parameter which is its description: 1 Description: External Alarm 4 - <User Text> - Alarm Cleared.
swVersionsMatchFullCompatibilityClear
214
normal
The trap is sent if SW versions match. Contains a single parameter which is its description: 1 - Description: Software Versions compatible
swVersionsMatchRestrictedCompatibilityClear
215
normal
The trap is sent if SW versions match and link functionality is not restricted. Contains a single parameter which is its description: 1 Description: Software Versions compatible
swVersionsMatchSoftwareUpgradeRequiredClear
216
normal
The trap is sent if SW versions match and SW upgrade is successful. Contains a single parameter which is its description: 1 - Description: Software Versions compatible
swVersionsCompatibleClear
217
normal
The trap is sent if SW versions compatible Contains a single parameter which is its description: 1 - Description: Software Versions compatible
hssMultipleSourcesDisappearedClear
218
normal
Indicates that multiple sync pulse sources disappeared. Contains a single parameter which is its description: 1 - Description: HSS multiple sync pulse sources disappeared.
hssSyncToProperSourceAchievedClear
219
normal
Indicates that synchronization to a proper Sync source was achieved. Contains a single parameter which is its description: 1 - Description: HSS sync pulse - Up.
hssSyncPulseDisappearedClear
220
normal
Indicates that HSS additional sync pulse disappeared. Contains a single parameter which is its description: 1 - Description: HSS additional sync pulse was disappeared.
MIB Traps
I-37
Name tdmBackupClear
ID 221
Severity normal
Description Indicates that the TDM main link was activated. Contains a single parameter which is its description: 1 - Description: TDM main link was activated.
linkLockAuthorizedRemoteODU
222
normal
Indicates that the remote ODU is authorized. Contains a single parameter which is its description: 1 - Description: Authorized remote ODU connection accepted.
linkLockAuthorizedODU
223
normal
Indicates that the ODU is authorized. Contains a single parameter which is its description: 1 - Description: Authorized ODU connection permitted.
linkAuthenticationDisabled
224
normal
Indicates that the Link Lock is disabled. Contains a single parameter which is its description: 1 - Description: Link Authentication has been disabled.
hotStandbyClear
225
normal
Indicates that the Primary Link Was Activated. Contains a single parameter which is its description: 1 - Description: Primary Link Is Active.
sfpExtraction sfpPort1Clear
226 227
normal normal
Indicates that a device was extracted from SFP Port Indicates the SFP port 1 status changed to connected. Contains two parameters: 1 - Description: SFP port 1 status changed to connected - %s 2 - %s Is the Eth. mode (speed & duplex)
compatibleIdus
228
normal
Indicates that the ODU has identified compatible Idus on both sides of the link.
desiredRatioCanNotBeAppliedClear cbwMatch
229 230
normal normal
Indicates Current UL/DL Ratio Is Equal To Desired Ratio. Indicates that a Channel Bandwidth match was detected. Contains a single parameter which is its description: 1 - Channel Bandwidth value in MHz.
switchCbwAndChannel
231
normal
Indicates that the system is switching Channel Bandwidth and channel frequency. Contains two parameters: 1 - Switching to Channel Bandwith %n0 MHz and to channel %n1 GHz.
ringRplStateIdle ringEthServiceStatus
232 233
normal normal
RPL state changed to Idle. Indicates Ethernet service's state - blocked \ unblocked. Contains a single parameter: 1 - Description: Ethernet's state (blocked \ unblocked)
ringFirstRpmReceived
234
normal
Ring application: in non-RPL link indicates first from a specific RPL was received. Contains a single parameter: 1 - Description: RPM's VLAN ID
ringEthernetSrviceUnblockedTO
235
normal
I-38
MIB Traps
Name
ID
Severity
gpsSynchronized
236
normal
The Airmux Manager application issues traps to indicate various events. These traps are shown in the Airmux Manager Events Log.
MIB Traps
I-39
I-40
MIB Traps
Note
The following procedure is generic to all relevant RAD radio products. What you see on your running Airmux Manager may differ in some details from the screen captures used to illustrate this appendix.
J.1
To activate a FCC/IC 5.4/5.3 GHz link: 1. Install Airmux Manager software as usual. 2. Connect the PC to the IDU-ODU pair to be used as the local site. 3. Run the Airmux Manager and log in as Installer. You will see the following window with the Link Status label red and showing Inactive.
J-1
J-2
Figure J-3. Active Manager Window, Local ODU after Activation Probing Note The Link ID is shown in the Link name pane.
8. Repeat the above procedure for the remote ODU, ensuring that in the Air Interface window, that you enter exactly the same Link ID, but this time that you check the Slave radio button If both ODUs are powered up, after a minute or so a link will be established. If you are still connected to the remote site (from the previous steps), the window of Figure J-3 will look like this:
J-3
J.2
The configuration procedure can be carried out from either site using the configuration wizard as described in Chapter 4.
Note
J-4
J-6
The main service redundancy features of the RAD MHS are: TDM service cut-over from the primary to the secondary link is completely automatic
K-1
TDM service cut-over time no more than 50 ms Automatic restore to primary link as soon as it becomes available Support for up to sixteen TDM channels for Airmux-400 and four TDM channels for Airmux-200.
MHS is supported between: Two Airmux-400 links Two Airmux-200 links An Airmux-400 link and an Airmux-200 link.
Equipment Protection
Equipment protection is provided for the electrically-active network elements, ODU and IDU. The primary IDU and the secondary IDU are connected by a cable to monitor failure and to control protection switching. Switching time is less than 50 ms. When connecting two Airmux-200 links as 1+1, one dual-polarization antenna can be shared by the primary link and the secondary link.
Air-Interface Protection
Air-Interface protection is unique to RAD and is optimized for wireless links operating in license-free bands. The primary link and the secondary link use different frequency channels. If the air-interface of the primary link is disturbed and cannot carry the required TDM service, then the system automatically switches to the secondary link. In addition, improved robustness and frequency planning flexibility is achieved, as the primary and secondary air interfaces can operate in the same frequency band or in different frequency bands. Automatic Channel Selection (ACS) can be configured for each link to add additional robustness. The primary and secondary links are synchronized using Hub Site Synchronization (HSS). It is recommended that both sites be installed with HSS cables. If HSS fails at one site, it can be operated from the other site by remote configuration.
K-2
K.1
In addition to the regular Airmux-200 units and accessories, the following items are required for implementation of a hot standby link: One MHS cable Hot standby patch panels
K.2
The following procedure is substantially generic to all RAD radio products. Differences between Airmux-200 and Airmux-400 class products are stated explicitly. What you see on your running Airmux Manager may differ in some details from the screen captures used to illustrate this appendix.
Figure K-1 illustrate an MHS setup. Figure K-3 shows how to connect the IDUs to the patch panel.
than eight TDM ports use two patch panels at each site.
Ethernet services are carried independently by primary and secondary links.
Each link carries different Ethernet traffic. MHS does not protect Ethernet traffic.
In what follows, it is assumed that:
Airmux-200 Ver. 1.9.3 Installing a Hot Standby Link K-3
We depart from our usual Site A / Site B conventions. Sites A and B on the primary link will be Sites 1.2 and 1.4 respectively. The corresponding sites on the secondary link will be Sites 2.2 and 2.4. The site names reflect their IP addresses. This is a useful convention and is reflected in the screen captures below. The link will be managed from Site 1.2; Site 1.4 may be a remote site. The links intended as the primary and secondary are referred to their respective names, Primary Link and Secondary Link as shown in Figure K-1 above, despite their having yet to be installed.
To install a hot standby link: 1. Set up Primary Link in the usual way. Ensure that it is fully operational in accordance with the relevant instructions in the previous chapters of the manual.
Note
K-4
10. Complete the configuration wizard, and then move to secondary link. 11. Repeat step 10 for secondary link. For the Services Hot Standby tab, this time, check the Secondary button. 12. Complete the configuration wizard. 13. At Site 1.2, reconnect the Hot Standby Patch panel to the external equipment. From this point on, we will simply refer to primary and secondary link (no capitalized names). At the end of the process, the Airmux Manager main windows should look like this:
K-6
K-7
Figure K-8. Primary Link a few Seconds before Regular No-Link Display
K-8
Figure K-9. Active Secondary Link after Switchover Note The active secondary link appears in red, although is operational.
K.3
IDU Replacement
Situation 1
To replace either of the IDUs at Site 1.4 or the secondary IDU at Site 1.2, nothing special is required. Simply disconnect the IDU to be replaced and replace it with a new one. Replacing a secondary link IDU obviously has no effect on the TDM service. Disconnecting the Site 1.4 primary IDU activates Hot Standby. After the Site 1.4 primary IDU is replaced, the Link will detect the change and switch back to the primary link. If you replaced the Site 1.2 secondary IDU, remember to reconnect the MHS cable.
K-9
Situation 2
Replacing the Site 1.2 primary IDU is different, and requires several steps. To replace the Site 1.2 primary link IDU: 1. 1. Power off the Site 1.2 primary IDU. This activates the secondary link using Hot Standby. 2. Run the Configuration manager on the secondary link, and in the Hot Standby panel of Figure K-5 above, check the Disabled button. 3. Replace the Site 1.2 primary IDU without connecting it to the ODU (to prevent transmission by the primary link with the undefined IDU). 4. Reconnect the MHS cable between the IDUs at Site 1.2. 5. Again, run the configuration wizard on the secondary link, and in the panel of Figure K-5 above, check the Secondary button to re-enable the link as secondary. 6. Connect the new Site 1.2 primary IDU to its ODU. The hot standby automatically reverts to the primary link within 50 ms.
ODU Replacement
Both the primary and secondary replacement ODUs require pre-configuration prior to insertion into the link. The items to be pre-configured are HSS mode Link ID Frequency Hot Standby mode using the new Services panel in Figure K-5 above IP address (optional).
Note
Pre-configuration must be carried out before the new ODU is connected to its IDU. If you try to do it "live" against its IDU, it will cause spurious transmissions and a service break.
To pre-configure an ODU: 1. Attach the new ODU to a PoE device or IDU. 2. Run the Airmux Manager and use Hot Standby tab of Figure K-5 above to configure the new ODU to Primary or Secondary mode as required. 3. Ensure that it is set to the proper HSS mode in accordance with Figure K-5 above. Enter the required Link ID and frequency. To replace an ODU for primary or secondary link, at either site: Install the pre-configured ODU. (Since the other link is working normally, nothing need be done with it. If the secondary ODU was replaced, service remains as is on the primary link. If the primary ODU was replaced, then the service switches back to the primary link.)
K-10
K.4
Switching Logic
This section describes logic behind link switchover and restoration process.
Following the switch from the primary to the secondary link, the primary and secondary link Manager main windows should look like this:
Figure K-10. Primary Link after the Switchover to Secondary Link Note After a few seconds the display in Figure K-10 moves to No-Link display, with TDM ports grayed out.
Switching Logic
K-11
Figure K-11. Secondary Link Operating after the Switchover to Secondary Note After a few moments the TDM icons in Figure K-11 become green.
K-12
Switching Logic
Figure K-12. Primary Link Operating after the Switchover from Secondary
Switching Logic
K-13
Figure K-13. Secondary Link operating after the switch back to Primary
Switching to backup link: Loss of the primary air interface due to sync loss Loss of the primary air interface due to failure of the receiver to acquire expected E1/T1 data during a period of 24 ms Primary equipment power off (either ODU or IDU, local or remote) E1 ports on the primary IDUs turn to tri-state E1 ports on the secondary IDUs become active.
Backup operation: E1 services are carried by the secondary link Restoration of primary link: Switching back to primary occurs as soon as the primary link is fully functional for 1 second.
K-14
Switching Logic
L.1
Typical Applications
This section describes possible Airmux-200 deployment scenarios with GPS-based synchronization.
Typical Applications
L-1
dis sites
tributed
L-2
Typical Applications
To see how it works, we use Figure L-2. The GSU towers are numbered and marked for cascading, 12 and 23. There should not be a link between 1 and 3. The GSU can synchronize the TDD timing of several sites enabling the cascading of consecutive links without mutual interference. To use cascading, the TDD timing of the even-ordered links (GSU 2 above) must be shifted (Shifted Phase) and odd-ordered links (GSU 1 and GSU 3 above) must be unshifted (Normal Phase). The phase shift is half of the Radio Frame Duration (RFD) from the chosen RFP. The scheme is shown in Figure L-3. Since the GSU is always HSS master (HSM), at each GSU location, the GSU can force the synchronization of its collocated radios. By half RFD shifting, alternate collocated sites can talk to each other.
L.2
GSU Redundancy
The GSU is designed to support redundancy, improving the robustness of a GSU based topology. In redundancy mode, two GSUs are installed at the same HSS site. One of them self-configures to generate HSS sync signals. We will call it the Primary unit. The other one, the Secondary unit remains dormant merely polling the first GSU. If the Primary GSU fails, then the Secondary GSU becomes active immediately. If the Primary unit becomes active again, it remains dormant, reversing the original roles. The choice of the Primary GSU is random and of no significance.
GSU Redundancy
L-3
If the Primary GSU fails, and then the Secondary GSU also fails to receive sync signals from its GPS, then it moves to self-generation HSM mode like an ordinary HSM ODU until its GPS recovers.
L.3
The GSU uses the same container and cabling as an Airmux-200 unit.
Kit Contents
The GSU package includes: GSU Mounting kit GPS antenna GPS antenna mounting kit RF cable, 1.5m (4.9 ft).
L-4
Note
If you are accessing the GSU through a network it is essential that you use the IP preloading method. The default IP address may be inaccessible and you may not use the Local Connection method over a network.
L.4
Use the method described in Appendix F to change the IP address from the default (10.0.0.120). In the example screen captures below, we use 192.168.222.20 with subnet mask 255.255.252.0. To configure the GSU: 1. Log in as described in Chapter 2. The Main window is displayed.
L-5
The main menu is a subset of the main menu applicable to Airmux-200. Notice that there are no Installation or Configuration wizards. Such configuration as is necessary is carried out using a modified version of Site Configuration for Airmux-200.
If satellite synchronization is lost, then the GSU will function as an independent HSM and the status box will change color:
2. Display the Site Configuration System dialog box and fill out the necessary fields.
L-6
Figure L-8. Site Configuration: GPS Sync Unit Note The 1000 and 2000 labels refer to Airmux-200 and Airmux-400 radios, respectively.
4. Configure the RFP for HSS. The GSU is automatically configured as HSS Master (HSM).
L-7
Note
L-8
L-9
L-10
24 Raoul Wallenberg Street, Tel Aviv 69719, Israel Tel: +972-3-6458181, Fax +972-3-6483331, +972-3-6498250 E-mail: erika_y@rad.com, Web site: http://www.rad.com
Excellent
Installation instructions Operating instructions Manual organization Illustrations The manual as a whole
Good
Fair
Poor
Very Poor
Error Report
Type of error(s) or problem(s): Incompatibility with product Difficulty in understanding text Regulatory information (Safety, Compliance, Warnings, etc.) Difficulty in finding needed information Missing information Illogical flow of information Style (spelling, grammar, references, etc.) Appearance Other Please list the exact page numbers with the error(s), detail the errors you found (information missing, unclear or inadequately explained, etc.) and attach the page to your fax, if necessary.
You are:
Who is your distributor? Your name and company: Job title: Address: Direct telephone number and extension: Fax number: E-mail:
International Headquarters
24 Raoul Wallenberg Street Tel Aviv 69719, Israel Tel. 972-3-6458181 Fax 972-3-6498250, 6474436 E-mail market@rad.com
www.rad.com