Trango Wireless Backhaul Solutions
Trango Wireless Backhaul Solutions
Complete Solutions
How to Participate Today
Leading Manufacturer of
Wireless IP Backhaul
Solutions
Focused on Licensed
Bands 6-40 GHz
Based in San Diego,
California
Delivering wireless
solutions since 1996
1996 1998 2000 2002 2004 2006 2008 2010 2011 2012 2013
New products to be
Access5800 PtMP Wireless announced
Broadband Radio
GigaPlus Released
ApexPlus
All Outdoor
GigaPlus
Split System
Sparta Elite
Encryption & Compression
GigaPro
Dual Modem
Antennas & Accessories
• Native IP
• Full Duplex, Layer 2 Throughput up to 375 Mbps
• Ultra low packet latency & jitter
• Supports 10/100/1000BaseT & Fiber Interfaces
• Compact ½ Rack Unit IDU. Same IDU for all frequencies
• High Power ODU & Industry leading system gain
• T1/E1 interfaces for timing or legacy TDM
• Hitless ACM
• QoS
Up to 750 Mbps Full Duplex (2+0 Mode) 4 GigE Copper / 2 Gige SFP Data Ports
Link Protection Modes
16 T1/E1 & 1 OC3/STM-1 per modem
– 1+1 Hitless Hot Standby
Hitless ACM
– Frequency Diversity
– Space Diversity
Relay (East / West) Mode
Actual data from 220 km link over water using frequency diversity
Maximum Expected value IF loopback -36 -36 -36 -36 -36 -36
Maximum Expected value Normal
operation at max power
-34 -33 -32 -30 -30 -29
Absolute Maximum for 1E-6 BER
Sensitivity Threshold
-28 -25 -22 -19 -16 -9
Loopback Debug>
Allows testing IDU/OMU Linux Command Prompt
Also useful for TDM termination Ping, SSH, Telnet, Route
Diagnostic Uptime
Check some hardware functions How long radio has been running
Create a .bin with current radio state CPU usage monitoring
Rx Symrate: 17422930
What symbol rate the receiver has locked onto.
Should match set symbol rate from speed cmd closley.
If number is changing or is not close to set rate, may be physical
problem with ODU or IDU.
TROUBLESHOOTING – Siglevel
Block Counter: 0
Accumulated data blocks since last link establishment.
Collected on 20 second periodic basis.
Cleared when read using siglevel cmd.
Uncorrect Block: 0
Accumulative demodulated data block errors since last link
establishment.
Tracks errors reported by modem when passing traffic.
Should be 0.
Collected on 20 second periodic basis.
If non-zero, packets are being dropped over RF link.
TROUBLESHOOTING – Siglevel
LDPC Avg Iteration: 0
Power Sensors
Check accuracy of transmit and receive.
Supported items vary.
Will show OK or alarmed.
Tx Power Alarm
Tx PA Alarm
PA on/off alarm
Tx Power Range alarm
Tx Power actual – should match within a few dB of set tx power.
Rx Power actual
Pass or Fail:
Channel test
Telemetry debug
Traffic Conversion
• Traffic is carried in native format.
• No conversion devices
• No conversion overhead
• No added latency
• Also means we can’t convert TDM framing or
TDM to Ethernet.
Data & VoIP GigE ports
No Extra
Bandwidth
AMI AMI
B8ZS B8ZS
B8ZS AMI
TROUBLESHOOTING – TDM
TX Frequency must EXACTLY match the RX frequency on the remote side. Type freq command to
view. Verify that the frequencies used match the regulatory body (FCC) approved frequencies.
Opmode is off. Run opmode command to view, and run opmode on to enable. If the unit was
rebooted and the default opmode is not on, the unit will come back on but the opmode will be off.
To prevent, run default_opmode on command and save (Apex) or config save (GigaPlus/Pro).
Are the frequencies configured correctly on each radio (TX and RX)? High frequency on the ODU B
model and low frequency on the ODU A model.
Is the waveguide transition installed properly (SP ODUs only)? The rectangular openings on the
ODU and transition must be lined up, and the transition tightened properly. Remove and reconnect
if not. This is shown in the manual.
Where the IDUs and ODUs swapped when the link was taken to the field? The frequencies may
need to be reassigned and saved if so.
TROUBLESHOOTING - DIAGNOSIS
No Link (Lock =0 during linktest) cont’d
Are both ODUs mounted on the same polarization? ODUs must be mounted with matching
polarizations at each end of the link. If one side is mounted on the antenna differently than the other
side, the link will not lot or the signal level will be 30 or more dB lower than expected.
If ACM is being used, ACM or Rateshift may not be enabled on both ends of the link. Enable the
ACM and reset the speed on each end. The speed must be set the same on both ends.
NOTE: For Giga, the downspeed must match on both ends and the target RSSI must be set to a level
just below the unfaded RSSI (normal operating RSSI)
NOTE: MSE= -32 dB or lower is typical for 256 QAM, -29 is a worse number and is not typical
Is the transmitter power set too high for the modulation being used. Consult the license
information to verify that the power level is no higher than the maximum allowed for the highest
modulation that will be used.
Target RSSI setup may be set incorrectly It should be set about 3 to 5 dB lower than the actual RSSI
so the in the ODU will set it’s RX gain for optimum Noise figure and input level. ODURXAGC should
be turned on after this is done and the link verified.
Are the ends on the LMR400 cable terminated properly? Have you tested your cable for return loss
and insertion loss? – Improperly terminated cable will cause degraded MSE and more loss than
expected, potentially making the link unusable. Additionally, some cables have inferior ground shield
that can allow noise to enter the transmit and receive intermediate frequency circuits and cause low
MSE. Ensure only cables with shielding levels of 90 dB or more at 350 MHz are used. Conduct a
“wiggle” test on the IF cables to ensure that they are tight at the connection to the IDU and ODU.
TROUBLESHOOTING - DIAGNOSIS
MSE is too high and/or bit errors are showing when running linktest , cont’d
Are the loss values correct for the length of cable being used? Reset them if not.
Are both ODUs mounted on the same polarization? ODUS must be mounted with matching
polarizations at each end of the link. If one side is mounted on the antenna differently than the other
side, the link will not lot or the signal level will be 30 or more dB lower than expected.
Is the waveguide transition installed properly (SP ODUs only)? The rectangular openings on the
ODU and transition must be lined up, and the transition tightened properly. Remove and reconnect
if not. This is shown in the manual.
Target RSSI setup may be set incorrectly It should be set about 3 to 5 dB lower than the actual RSSI
so the in the ODU will set it’s RX gain for optimum Noise figure and input level. ODURXAGC should
be turned on after this is done and the link verified.
Reported RSSI more than 3 dB off the expected RSSI: There may be a alignment problem with the
antenna, especially if both sides of the link show the same symptom . Solution : Realign the
antenna(s). Opmode must be on at the remote side of the link to do alignment of the local side.
Ensure that ATPC is off and that after the alignment is completed, the alignment mode is turned off.
Are both ODUs mounted on the same polarization? ODUS must be mounted with matching
polarizations at each end of the link. If one side is mounted on the antenna differently than the other
side, the link will not lot or the signal level will be 30 or more dB lower than expected.
Is the waveguide transition installed properly (SP ODUs only)? The rectangular openings on the
ODU and transition must be lined up, and the transition tightened properly. Remove and reconnect
if not. This is shown in the manual.
TROUBLESHOOTING - DIAGNOSIS
RF Link is good but packet loss is occurring:
Verify the duplex and speed settings in the Ethernet port are correct (100 or 1 Gbit) and match the
connected equipment, and that no CRC errors on the port are occurring.
Verify that the Ethernet ports are connected properly. The Giga and Apex family of Radios are port
mapped, meaning that the traffic going into Ethernet Port 1 on the local side will only appear at port
1 of the remote side, local side port 2 traffic will appear on the remote side port 2, etc..
Check the Ethernet cables for correct wiring. If 1000BaseT is being implemented, Cat6 cable
should be used.
Verify the In-Band management is set up properly - Check to see if the IP configuration is correct,
the VLAN ID is set and matches on both ends, and that IBM is enabled. (See How-To on IBM).
Ping from one radio’s IBM to the other. Then try pinging switch/router.
Allows management of the link in-band with the data traffic, without use of the
(OBM) Management port.
Must use a VLAN tag (trunk port)
Best practice: Dedicated management vlan
Separate IP subnet from OBM interface
Both OBM & IBM can work at same time
Set default gateway for off subnet access in IBM or OBM subnet.
Use IBM as a backup channel between radios if far end switch seems to be down
Consider OBM backup for loopback testing and management with RPS.
Hold mode for more than 2 seconds, but less than 6 seconds
The CLI management passwords will be reset to default
The Web interface passwords will be reset to default.
The SNMP read/write/trap community strings will be set to defaults.
The CLI prompt will be reset.
The IP Address will be reset.
How to Upgrade
Contact
Phone: +1-858-391-0010
Email: [email protected]
http://www.trangosys.com
http://support.trangosys.com