TL45 troubleshooting

First, please consult the Trangolink 45 Manual.

You can use either web interface or CLI to mange TL45. It would be nice if you use CLI while troubleshooting. 

Quick steps to check what is the problem with the link?

1. No Ethernet connection/No Power:

1. Make sure unit is powered up properly. Proper grounding. Proper Cable length according IEEE standards. If necessary check voltages going to the PoE and comming out of PoE. Check datasheet for TL45.                                     

2.Default IP of TL45 unit is 192.168.100.100 255.255.255.0. If you are connecting to TL45 first time configure your laptop IP in same subnet. 

2. No link:

1.First of all check if you have telnet access to the unit. If not follow above instructions to get access to the unit. 

2.Once there use "RSSI" Command to check if there there is no link at all or it's an intermittent connection.

Example: 

It's showing good connection both sides. 

Commands: 

 

rssi

 

#> rssi
Press 'q' to stop.
0> MU -41 dB RU -41 dB Connected
1> MU -41 dB RU -41 dB Connected
2> MU -41 dB RU -41 dB Connected
3> MU -41 dB RU -41 dB Connected
Success.
#>

autorateshift

 

#> autorateshift
off
Success.
#>

speed

#> speed
54 Mbps
Success.
#>

linktest 54 54 1600 100 10

 

Note: If you are seeing packet drops out of 100 than link should be experiencing interference, may be you are pushing way much traffic or small packets ( less than 256 bytes or more than 1600 bytes). If there are small packets then you will see degradation in your throughput. You can check using different supported speed setting and use linktest command to check if link gives you better throughput at lower speed settings. You can tweak the link speed until you will see minor or no packet drop under TX/RX results. 100/100.

 

linktest <loc speed> <peer speed> :[<pkt size> [<# of pkt>  [<# of cycles>]]]]

 

RF link test, opmode on only 
<speed> = 6,12,18 24,36,48,54 Mbps 
<pkt size> = 256..3600 bytes default = 1600 
<# of pkt> = packets per cycle 100..1000 default = 1000 
<# of cycle> = 10..1000 default = 10

Example: 

 

#> linktest 54 54 1600 100 10

local tx rate = 54 Mbps
peer tx rate = 54 Mbps
packet size = 1600 bytes
# of packets per period = 100
# of Cycle = 10
0> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.23 Mbps
1> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.11 Mbps
2> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.19 Mbps
3> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 43.91 Mbps
4> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.13 Mbps
5> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 43.92 Mbps
6> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.14 Mbps
7> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.07 Mbps
8> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.23 Mbps
9> [tx] 100 [rx] 100 [rssi] -41 peer: [tx] 100 [rx] 100 [rssi] -41 -> 44.25 Mbps

--> [tx] 1000 [rx] 1000 [rssi] -41 peer: [tx] 1000 [rx] 1000 [rssi] -41
--> [Local PER] 0.00 % [Peer PER] 0.00 %

Success.

 

Once you try everything explained above and couldn't figure out what is the problem please post in this forum. Make sure you attached all necessary information along with your testing results so We can help you to troubleshoot your problem as soon as possible. 

We will need "sysinfo" command result from CLI or sysinfo page screenshot from web interface (both MU & RU) to verify if configuration is all good. 

Should you need to request an RMA to return damaged equipment, you may do so by submitting a new ticket. Please only one item per ticket.