Good day to all. I am posting this in a desperate attempt to keep my contract with a very important client. I hope somebody can help me out. I am posting as much information as possible so that you might be able to analyze this well. I swear by Canopy in most cases and am about to loose my mind in disbelief.
Here is the scenario:
This client had a 1.5 mile link between two old SMC bridges hooked up to 25 Dbm parabolic grids and 1 watt ampli on each side (yes, I said 1 watt each side!!!). This link worked very well, it was running an average of 3-5 ms PING delays. The purpose of this link is to interconnect two office buildings and use an MS-DOS based accounting program between the two. They did not have anything properly grounded, so one day, and a spike in the electric current caused permanent damage to one of these. SMC discontinued about 1 year ago these bridges and despite vast efforts, they were unable to find a used or forgotten bridge. So the customer called a local telecommunications company who proposed replacing the old bridges with the new SMC 2582W-B corporate bridges. These bridges ran really fast, responding PING at a stable 1ms delay!!! However they made the MS-DOS based database fail very often causing HUGE loss of information. They then attempted to replace the SMC equipment with 2 Linksys WAP 54G on the same setup. This fixed the database crash problem but ran at turtle speeds and although the link was stable, it was unable to return a PING in less than 350 ms. That is when they called me. Their network admin told me about their plans to add VoIP and IP cameras to their network so I immediately offered Canopy as the best, most cost effective solution. I have been working with canopy for about 1 year and have NEVER had any problems with the 12 sites I have running Canopy gear. I even have a 8.5 mile, 5.7 GHz, no reflector, link, up and running servicing a 512 Kbps Internet connection with 0 problems. So I went for the 5.2 GHz system witch I had never tested out. We replaced the 2.4 GHz installation with the Canopy system, put the AP on the MS-DOS server side. We took bearing, height and distance information with a Lawrence GPS and aligned everything as best we could. The first thing I noticed was a flat 1-2 ms PING delay between any station on the local network and de Canopy AP, witch I hadn’t seen with my 5.7 GHz system who returns >1 ms PING delay. This happened on both sides so I thought it was normal. I then noticed that the wireless link was very unstable and was unable to return PING in less than 24 ms at best, timing out 3 or 4 times out of every 8 or 10 PING’s. Delay climbes to 1,5000 at worst. I also noticed via ping plotter (www.pingplotter.com- attached to this document, only in e-mail form), that the link is very unstable but the SM does not show high re reg counts. Rssi was around 800-950 and jitter around 8-15. We then used the Canopy audible alignment tool, and fixed the SM at a position were it gave us the highest pitched tone and highest volume. This improved rssi to about 900- 1000, however jitter still remained at an unacceptable 7-10. I really don’t understand why, there is PERFECT LOS with 0 fresnel zone interference and 1.5 miles really doesn’t seem to be very far considering. The spectrum analyzer doesn’t show any interference in the 5.2 GHz band. Both AP and SM have the latest firmware. Color code is set correctly. We tried CHARIOT benchmark testing and as I had anticipated VoIP will NOT run correctly over this link. Throughput is real lowsy. I really really don’t know what is going on and any help would be greatly appreciated. Below is all the data that the SM outputs on its web-based configuration interface:
SM STATUS
Device Information:
Device type 5.2GHz - Multipoint - Subscriber Modem - 0a-00-3e-00-d1-69
Software Version CANOPY 6.1 Dec 08 2004 09:22:02 SM-DES
Software Boot Version CANOPYBOOT 3.0
FPGA Version 051104 (Single, 40MHz ExtBus, DES, Type0)
Uptime 2d, 21:58:59
System Time 20:52:38 01/06/2000
Ethernet Interface 100Base-TX Full Duplex
Subscriber Modem Stats
Session Status REGISTERED
Registered AP 0a-00-3e-00-b6-d1
RSSI 908
Jitter 5
Air Delay 119 (approximately 1.10 miles (5831 feet))
Radio Slicing Value 533 (decimal)
Radio Transmit Gain Setting 23 (decimal)
Radio Temperature 48°C/119°F
Radio Power Level -76 dBm
LUID 2
IP Address 192.168.101.2
Registration Grant Status Normal
Sustained Uplink Data Rate 2000 (kbps)
Uplink Burst Allocation 4000 (kbits)
Sustained Downlink Data Rate 2000 (kbps)
Downlink Burst Allocation 4000 (kbits)
Frame Configuration Information
Data Slots Down 14
Data Slots Up 14 (Number Hi Priority) : 0
Num U Ack Slots 5 (Number Hi Priority) : 0
Num D Ack Slots 5 (Number Hi Priority) : 0
Num Ctl Slots 5 (Number Hi Priority) : 0
Site Information
Site Name
Site Contact
Key Features Information
Maximum Throughput 7mDn–7mUp
AP EVAL DATA:
AP List
Current entry index: 0
Index: 0 Frequency: 5290.0 MHz ESN: 0a-00-3e-00-b6-d1
Jitter: 4 RSSI: 901 Power Level: -76 Beacon Count: 25 BRcvW: 1
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 5880 feet TxBER: 1 EBcast: 0
Session Count: 3 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 1401 SectorID: 0 Color Code: 8 BeaconVersion: 1 SectorUserCount: 0
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 5 NumContSlots: 5 NumUAckSlots: 5
Index: 1 Frequency: 5300.0 MHz ESN: 0a-00-3e-00-c7-76
Jitter: 6 RSSI: 825 Power Level: -81 Beacon Count: 7 BRcvW: 1
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet TxBER: 0 EBcast: 0
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 365 SectorID: 0 Color Code: 100 BeaconVersion: 1 SectorUserCount: 1
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 3 NumContSlots: 3 NumUAckSlots: 3
Index: 2 Frequency: 5325.0 MHz ESN: 0a-00-3e-00-3a-b8
Jitter: 9 RSSI: 767 Power Level: -84 Beacon Count: 17 BRcvW: 1
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet TxBER: 0 EBcast: 0
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 1024 SectorID: 2 Color Code: 18 BeaconVersion: 1 SectorUserCount: 1
PercentDataDwn: 75 PercentDataUpHi: 0 NumDAckSlots: 3 NumContSlots: 3 NumUAckSlots: 3
Index: 3 Frequency: 5325.0 MHz ESN: 0a-00-3e-00-25-90
Jitter: 4 RSSI: 1022 Power Level: -71 Beacon Count: 1 BRcvW: 0
Type: Multipoint Avail: 0 Age: 2 Lockout: 0 RegFail 0 Range: 0 feet TxBER: 0 EBcast: 0
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 407 SectorID: 6 Color Code: 1 BeaconVersion: 1 SectorUserCount: 1
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 3 NumContSlots: 3 NumUAckSlots: 3
*********************************************
Index: 4 Frequency: 5325.0 MHz ESN: 0a-00-3e-00-23-18
Jitter: 11 RSSI: 720 Power Level: -85 Beacon Count: 2 BRcvW: 1
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet TxBER: 0 EBcast: 0
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 1759 SectorID: 0 Color Code: 0 BeaconVersion: 1 SectorUserCount: 3
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 3 NumContSlots: 3 NumUAckSlots: 3
RF Control Block Statistics:
inoctects Count 64428168
inucastpkts Count 383858
Innucastpkts Count 6233
indiscards Count 0
inerrors Count 0
inunknownprotos Count 0
outoctets Count 152898383
outucastpktsCount 359475
outnucastpkts Count 94350
outdiscards Count 321
outerrors Count 0
The output of the AP Eval Data page shows that the SM can see 5 different APs, 3 of which are transmitting on the same frequency 5325 MHz and 2 of which are within 20 MHz of each other.
The AP needs to be synchornized and placed on a channel that is at least 20 MHz (the more the better) than any other AP that can be seen by that SM.
-ken
yes I agree. What frequency is your AP on? It looks like your are getting high jitter because of bleed over from an adjacent channel that is partly on the channel you are using… You need 25 meg spacing from anyone else.
The other thing we have seen is when the SM scans, if the signal is strong it will sometimes lock on to a channel just a little of the center frequency of the ap. You still get good rssi but the jitter is high and throughput sucks. It is like listening to a radio station tuned just a little to the side of the station. If you deselect the scan options either side of your ap frequency it will lock onto the right center freq and work fine. I haven’t seen this on 5 Ghz but we only have 900 and 2.4 in use. I’m guessing it works the same.
The only place I can find to show what frequency the SM is locked onto is the AP eval screen. It would be nice to have it show up in a data field somewhere in the config, by hilighting one of the scan freqs or something.
Be sure your ap eval shows the frequency you know the ap is transmitting on. This can be a fooler.
I agree with the last two posts in that you have an interference problem. 5.2 has 3 non-overlapping channels, 5275, 5300, and 5325. Set the AP’s back to back with like frequencies.
The SM is registered to a less desirable AP and is getting desensitized by the adjacent AP.
You are locked on 5290 even through 3a-b8 has a much better power level. You need to fix the RF layout of your AP’s and force the SM to reregister.
As a side question are you using a CMM?
my suggestion would be two 5.7Ghz Backhauls with relflectors. the reflector sets the beamwidth down to 6 degrees so the rfi & emi in the surrounding atmosphere isnt such an issue.
The dedicated backhaul will give you much better throughput and lower latency.
But like everyone elso said, get further away from those frequencies, chose a specific frequency, set the sm only to that frequency, do not let it scan other freq’s, and also set the color code on both AP & SM to something other than 0, 0 scans all color codes. I have a feeling your SM is hopping AP’s.
Many thanks to: canopy_support, md, MBWtech and kenm for your most valuable suggestions/observations. Those other 4 AP’s that show up on the AP Eval page are not mine. Nor do I have any control over what frequencies they transmit on. I had overlooked the fact that ESN (a.k.a MAC address) number for each index is given (I had figured it was stored info from prior resets). Apparently I also misread the spectrum analyzer. By the way, does anybody know why the spectrum analyzer shows more frequencies than those you are allowed to choose?
There are effectively 4 intersecting links all in 5.2 GHz and it seems there is gonna be very little I can do about it. They belong to a neighboring beer factory. The sys admin there said he will not change ANYTHING in his setup. As you can see, that means the best clearance I can get between frequencies will be 15 megs. Does anybody have any suggestions?
The bad part is that although rssi is now between 900 – 1000 and jitter 4-8 the throughput performance is very bad. Chariot testing showed an unstable 800 kb effective high performance throughput (not even 1 Mb !). My client is not very pleased. The database works perfectly, but very very slow. The worst part is that at the server side, witch happens to be their main office, there is a Breeze networks Alvarion, linked up to a warehouse 9 km away. This link has EXTREMELY lousy LOS and goes directly through downtown (the most heavily RF’ed area). It has a stable 4 ms ping and rock solid stability. That link’s pingplotter (www.pingplotter.com) graph looks like a dead persons cardiograph, and the owner told me that unless I can get this 1.5 mile Canopy to work at least at the Alvarions certified (certified at this site by HEMAC) 2Mb nominal speed (considering this is a 9 km link and Canopy only has to go 1.5 miles), they were gonna go with someone else for the multipoint part of their upgrade. He also compared this link to the Linksys setup (original post) he had prior to calling me, and stated that they both “protected” the database from “crashing”, but for the price, Canopy was too expensive for such a little performance difference between the 2. This kinda ticked me off, because Canopy is for MULTIPOINT applications and it is not fair to compare it to an over amplified 1.5 mile point to point 2.4 GHz link.
To answer canopy_support’s question: No I am not using CMM. It is just one AP and one SM. The AP is generating sync.
Any help would be greatly appreciated…
Thank you all,
Mr. Lopez
I agree with MBWTech if the other guy wont change freq use two 5.7 bh with reflector
The other 4 are on 5300 and 5325, why not drop yours down to 5275?
This would give you a lot more separation.
Ok… I finally got some 5.7 GHz gear so I can try out everybodys suggestions. Im gonna have to go with the multipoint setup so BH units are out. I took these two 5.7 radios from a freind of mine who is not using them right now. He had them setup at .95 miles with a rock steady ping return and very good throughput, he was recieving 1Mb Internet at his home with these 5.7 radios.
They were running relese 3.25 so I upgraded them both (AP and SM) to 4.23 then to 6.1 software. We fired them up and could not establish the link. The first thing I noticed was that the radios were in need of calibration data. So over the weekend I tried the online post method, however I kept getting this response: (it wasnt until today moday that I got the correct settings)
MAC Address RSSI Slice Power
0a-00-3e-f0-7a-53 * *
0a-00-3e-f0-7d-4a * *
I really didnt know what to do since there was no data. So I ended up storing radio calibration settings and rebooting with no data. The radios did not link. This is the AP eval page right after thrying this:
AP List
Current entry index: 0
Index: 0 Frequency: 5800.0 MHz ESN: 0a-00-3e-f0-7d-4a
Jitter: 15 RSSI: 593 Power Level: -92 Beacon Count: 1 BRcvW: 1
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 506 Range: 5978 feet TxBER: 0 EBcast: 0
Session Count: 5 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 478 SectorID: 0 Color Code: 220 BeaconVersion: 1 SectorUserCount: 1
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 5 NumContSlots: 5 NumUAckSlots: 5
**
Index: 1 Frequency: 5780.0 MHz ESN: 0a-00-3e-f0-9f-e8
Jitter: 11 RSSI: 592 Power Level: -92 Beacon Count: 4 BRcvW: 0
Type: SinglePoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet TxBER: 0 EBcast: 0
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 1130 SectorID: 0 Color Code: 0 BeaconVersion: 1 SectorUserCount: 0
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 1 NumContSlots: 1 NumUAckSlots: 1
I would be f0-7d-4a. So I guess that calibration has a whole lot to do with it. I am going to try this new calibration data that I just recieved from canopy_support and will post the results ASAP. I am still in the running for the contract and have just this week to prove that Canopy is the best solution. The owner agreed to go with Canopy Advantage if this weeks results were satisfactory.
Ok now I am really confused. The 5.7 gear will NOT link. They are at the same site, same height, etc… that the 5.2 gear was, and NOTHING. The SM will register then drop the link. What is really weird is that it will not cause a re reg count on the reg fail SM page on the AP. I input the correct calibration data, witch is:
CALIBRATION DATA
MAC Address RSSI Slice Power
0A003EF07A53 914 451 -79
0A003EF07D4A 816 473 -78
Doing this did not help much. I am posting again all the data I can. First comes the data from the AP and below that the data from the SM:
AP LINK TEST
Stats for LUID: 2 Test Duration: 2
Downlink RATE: 940032 bps
Uplink RATE: 0 bps
Downlink Efficiency: 34 Percent
Max Downlink Index: 97
Actual Downlink Index: 33
Expected Frag Count: 3672
Actual Frag Count: 10864
Uplink Efficiency: 0 Percent
Expected Frag Count: 0
Actual Frag Count: 0
LINK TEST #2
Link Capacity Test
Duration: Seconds
Current Results Status
We failed to receive the handshake from the remote device.
THIS IS THE AP STATUS PAGE:
Device Information
Device type 5.7GHz - Multipoint - Access Point - 0a-00-3e-f0-7d-4a
Software Version CANOPY 6.1 Dec 08 2004 09:22:02 AP-DES
Software Boot Version CANOPYBOOT 3.0
FPGA Version 051104 (Single, 40MHz ExtBus, DES, Type0)
Uptime 00:22:05
System Time 19:16:59 01/03/2000
Last NTP Time Update 00:00:00 00/00/0000
Ethernet Interface 100Base-TX Full Duplex
Access Point Stats
Registered SM Count 1
GPS Sync Pulse Status Generating Sync
Radio Slicing Value 495 (decimal)
Radio Transmit Gain Setting 20 (decimal)
Radio Temperature 40°C/103°F
Site Information
Site Name
Site Contact
Frame Configuration Information
Data Slots Down 14
Data Slots Up 13 (Number Hi Priority) : 0
Num U Ack Slots 5 (Number Hi Priority) : 0
Num D Ack Slots 5 (Number Hi Priority) : 0
Num Ctl Slots 5 (Number Hi Priority) : 0
Key Features Information
Scheduling Type Software
3 DIFERENT AP SESSIONS:
LUID: 002 : MAC: 0a-00-3e-f0-7a-53 State: IN SESSION (Encrypt Disabled)
Site Name : Cacahuatera
Software Version : CANOPY 6.1 Dec 08 2004 09:22:02
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 091102 (DES)
Session Timeout: 22, AirDelay 123
Session Count: 7, Reg Count 2, Re-Reg Count 5
RSSI (Avg/Last): 846/846 Jitter (Avg/Last): 12/12 Power Level (Avg/Last): -73/-73
DnRate: 4000 DnLimit: 20000 UpRate: 4000 UpLimit: 20000 (kbit)
Session Status List
LUID: 002 : MAC: 0a-00-3e-f0-7a-53 State: IDLE
Session Timeout: 0, AirDelay 123
Session Count: 7, Reg Count 2, Re-Reg Count 5
RSSI (Avg/Last): 852/860 Jitter (Avg/Last): 8/5 Power Level (Avg/Last): -73/-72
DnRate: 4000 DnLimit: 20000 UpRate: 4000 UpLimit: 20000 (kbit)
Session Status List
LUID: 002 : MAC: 0a-00-3e-f0-7a-53 State: IN SESSION (Encrypt Disabled)
Site Name : Cacahuatera
Software Version : CANOPY 6.1 Dec 08 2004 09:22:02
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 091102 (DES)
Session Timeout: 12, AirDelay 122
Session Count: 10, Reg Count 3, Re-Reg Count 7
RSSI (Avg/Last): 857/850 Jitter (Avg/Last): 8/7 Power Level (Avg/Last): -73/-74
DnRate: 4000 DnLimit: 20000 UpRate: 4000 UpLimit: 20000 (kbit)
THIS IS THE REG FAIL SM PAGE
Most Recent Registration Failure List
No Entries
THIS IS THE CAPT DUMP
Captured Packets:
AllocLUID 257
BufLen 58
CpyCnt 1
DstLUID 255
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 2
SrcLUID 2
Rcvd RSSI 941
VLAN VID 0
FFFFFFFF FFFF1A00 3EF07A53 08060001 08000604 00011A00 3EF07A53 C0A86502
00000000 0000C0A8 65010000 00000000 00000000 00000000 0000
AllocLUID 257
BufLen 119
CpyCnt 1
DstLUID 260
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 3
SrcLUID 2
Rcvd RSSI 928
VLAN VID 0
0050BFE2 0DEE00D0 0939FD44 0065E0E0 03FFFF00 62000443 08C28400 50BFE20D
EE055143 08C28400 D00939FD 44055200 00000000 00000000 00000000 00000000
00000000 00000000 00000000 000000F3 01038047 454E4941 4C202020 20202020
20202056 454E5441 53204E49 A54F5332 20200096 441868
AllocLUID 257
BufLen 237
CpyCnt 1
DstLUID 260
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 3
SrcLUID 2
Rcvd RSSI 954
VLAN VID 0
0050BFE2 0DEE00D0 0939FD44 00DBE0E0 03FFFF00 D8000443 08C28400 50BFE20D
EE055043 08C28400 D00939FD 440552FF 534D4272 00000000 00000000 00000000
00000001 00000000 0050C100 00013600 77000250 43204E45 54574F52 4B205052
4F475241 4D20312E 3000024D 4943524F 534F4654 204E4554 574F524B 5320332E
30000244 4F53204C 4D312E32 58303032 0002444F 53204C41 4E4D414E 322E3100
0257696E 646F7773 20666F72 20576F72 6B67726F 75707320 332E3161 00024E54
204C4D20 302E3132 0056454E 54415320 4E49A54F 53322020 0047454E 49414C20
20202020 20202020 201E17B2 DF
AllocLUID 257
BufLen 237
CpyCnt 1
DstLUID 260
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 3
SrcLUID 2
Rcvd RSSI 949
VLAN VID 0
0050BFE2 0DEE00D0 0939FD44 00DBE0E0 03FFFF00 D8000443 08C28400 50BFE20D
EE055043 08C28400 D00939FD 440552FF 534D4272 00000000 00000000 00000000
00000001 00000000 0050C100 00013600 77000250 43204E45 54574F52 4B205052
4F475241 4D20312E 3000024D 4943524F 534F4654 204E4554 574F524B 5320332E
30000244 4F53204C 4D312E32 58303032 0002444F 53204C41 4E4D414E 322E3100
0257696E 646F7773 20666F72 20576F72 6B67726F 75707320 332E3161 00024E54
204C4D20 302E3132 0056454E 54415320 4E49A54F 53322020 0047454E 49414C20
20202020 20202020 201E17B2 DF
AllocLUID 257
BufLen 207
CpyCnt 1
DstLUID 255
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 3
SrcLUID 2
Rcvd RSSI 949
VLAN VID 0
FFFFFFFF FFFF00D0 0939FD44 00BDE0E0 03FFFF00 BA001400 000000FF FFFFFFFF
FF055343 08C28400 D00939FD 44055300 00000000 00000000 00000000 00000000
00000000 00000000 00000000 000000FC 01000047 454E4941 4C202020 20202020
20200056 454E5441 53204E49 A54F5332 202020FF 534D4225 00000000 00000000
00000000 00000000 00000000 00000000 00000011 00000200 00000000 00000000
00000000 00000000 00000200 56000300 01000100 02001300 5C4D4149 4C534C4F
545C4252 4F575345 000E0290 784F04
AllocLUID 257
BufLen 58
CpyCnt 1
DstLUID 255
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 2
SrcLUID 2
Rcvd RSSI 927
VLAN VID 0
FFFFFFFF FFFF1A00 3EF07A53 08060001 08000604 00011A00 3EF07A53 C0A86502
00000000 0000C0A8 65010000 00000000 00000000 00000000 0000
AllocLUID 257
BufLen 187
CpyCnt 1
DstLUID 255
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 3
SrcLUID 2
Rcvd RSSI 940
VLAN VID 0
03000000 000100D0 0939FD44 00A9F0F0 032C00FF EF080000 00000000 004D4154
20202020 20202020 20202020 1E56454E 54415320 4E49A54F 53322020 00FF534D
42250000 00000000 00000000 00000000 00000000 00000000 00000000 00110000
24000000 00000000 00000000 00000000 00000000 24005600 03000100 01000200
35005C4D 41494C53 4C4F545C 42524F57 5345000F 0640771B 0056454E 54415320
4E49A54F 53320000 00040003 20450015 0455AA61 626300B9 F0873C
AllocLUID 257
BufLen 58
CpyCnt 1
DstLUID 255
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 2
SrcLUID 2
Rcvd RSSI 925
VLAN VID 0
FFFFFFFF FFFF1A00 3EF07A53 08060001 08000604 00011A00 3EF07A53 C0A86502
00000000 0000C0A8 65010000 00000000 00000000 00000000 0000
AllocLUID 257
BufLen 58
CpyCnt 1
DstLUID 255
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 2
SrcLUID 2
Rcvd RSSI 950
VLAN VID 0
FFFFFFFF FFFF1A00 3EF07A53 08060001 08000604 00011A00 3EF07A53 C0A86502
00000000 0000C0A8 65010000 00000000 00000000 00000000 0000
AllocLUID 257
BufLen 58
CpyCnt 1
DstLUID 255
MsgType 1
NiBufSignature xaa55aa55
SrcAP 0
SrcIF 2
SrcLUID 2
Rcvd RSSI 934
VLAN VID 0
FFFFFFFF FFFF1A00 3EF07A53 08060001 08000604 00011A00 3EF07A53 C0A86502
00000000 0000C0A8 65010000 00000000 00000000 00000000 0000
10 packets captured
THIS IS THE DOWN STAT
Downlink Statistics for LUID 2
High Q to VC 0
Low Q to VC 0
Tx Buffer Complete Count 215
Tx VC Complete Count 61
Tx Expired Count 85
Tx Expired Sent to Session Count 1
RF Fragments Transmitted 16960
Fragments Successfully Transmitted 4515
Air Travel Delay Time 122
Data Lost (Queue Overflow) 179
Get VC Exp While Idle 0
Get VC Exp While OOS 0
Get VC Done While OOS 0
Chain Insert While OOS 0
Data Queued While OOS 0
Luid OOS While OOS 0
Luid INS While INS 0
Tx Bytes(No DiagData) 5684
Tx Unicast Packets(No DiagData) 27
Tx Broadcast Packets(No DiagData) 0
Tx Discards(No DiagData) 0
SQ Remove after RfDeath 0
VC Cleanup after RfDeath 0
THIS IS UPLINK STATS
AP Wide
Schedule Full 0
No BW CBs Available 0
Data Lost 0
Control Lost 0
LUID 2 Specific
BW Req Repeat Rcvd Count 1599
AP VC Rearm 0
Uplink Enable 10
Uplink Disable 10
Transaction Timeout 19
BW Request Received 2916
Schedule Full 0
Received Data Packet(Rf) 61
Received Allocation Expired 1034
No BW Control Block Available 0
Previous Frame Start 819380
Current Frame Start 819416
Schedule Frame Delta 36
Rcv Bytes(Bridge) 0
Rcv Unicast Packets(Bridge) 0
Rcv Broadcast Packets(Bridge) 0
Rcv Discards(Bridge) 0
THIS IS BRIDGE CB DATA
Bridge FEC Stats Bridge NI1 Stats (FEC PNA)
FEC bin 2458 NI1 bin 2
FEC bout 19 NI1 bout 550
FEC btoss 0 NI1 btoss 0
FEC uin 5551 NI1 uin 5179(5517)
FEC uout 5183 NI1 uout 5517(5517)
FEC utoss 31 NI1 utoss 0
Bridge RF Stats Bridge NI2 Stats (RF PNA)
RF bin 23 NI2 bin 0
RF bout 2851 NI2 bout 6
RF btoss 0 NI2 btoss 0
RF uin 21 NI2 uin 25(25)
RF uout 28 NI2 uout 17
RF utoss 0 NI2 utoss 0
Bridge Error Stats Bridge NI3 Stats (RF Public PNA)
ErrNI1QSend 0 NI3 bin 0
ErrNI2QSend 0 NI3 bout 0
ErrBridgeFull 0 NI3 btoss 0
ErrSendMsg 0 NI3 uin 0
ErrApFecQSend 0 NI3 uout 0
ErrApRfQSend 0 NI3 utoss 0
Bridge Sniffing Stats
Sniffed IP Pkts 0
Discarded ARP 0
Sniffed Mac Pkts 0
NOW THE SM DATA:
THIS IS THE STATUS PAGE
Device Information
Device type 5.7GHz - Multipoint - Subscriber Modem - 0a-00-3e-f0-7a-53
Software Version CANOPY 6.1 Dec 08 2004 09:22:02 SM-DES
Software Boot Version CANOPYBOOT 3.0
FPGA Version 091102 (Double, 32MHz ExtBus, DES, Type0)
Uptime 00:04:58
System Time 21:00:05 01/03/2000
Ethernet Interface 100Base-TX Full Duplex
Subscriber Modem Stats
Session Status REGISTERING
Registered AP n/a
RSSI 0
Jitter 0
Air Delay 1620 (approximately 15.03 miles (79380 feet))
Radio Slicing Value 492 (decimal)
Radio Transmit Gain Setting 15 (decimal)
Radio Temperature 52°C/126°F
Radio Power Level -97 dBm
LUID 2
IP Address 192.168.101.2
Registration Grant Status Normal
Sustained Uplink Data Rate 4000 (kbps)
Uplink Burst Allocation 20000 (kbits)
Sustained Downlink Data Rate 4000 (kbps)
Downlink Burst Allocation 20000 (kbits)
Frame Configuration Information
Data Slots Down 14
Data Slots Up 13 (Number Hi Priority) : 0
Num U Ack Slots 5 (Number Hi Priority) : 0
Num D Ack Slots 5 (Number Hi Priority) : 0
Num Ctl Slots 5 (Number Hi Priority) : 0
Site Information
Site Name
Site Contact
Key Features Information
Maximum Throughput 7mDn–7mUp
THIS IS THE AP EVAL PAGE
AP List
Current entry index: 0
Index: 0 Frequency: 5760.0 MHz ESN: 0a-00-3e-f0-7d-4a
Jitter: 15 RSSI: 727 Power Level: -82 Beacon Count: 1 BRcvW: 1
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 12 Range: 5929 feet TxBER: 0 EBcast: 0
Session Count: 3 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 326 SectorID: 0 Color Code: 26 BeaconVersion: 1 SectorUserCount: 0
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 5 NumContSlots: 5 NumUAckSlots: 5
Index: 1 Frequency: 5780.0 MHz ESN: 0a-00-3e-f0-9f-e8
Jitter: 11 RSSI: 685 Power Level: -83 Beacon Count: 2 BRcvW: 0
Type: SinglePoint Avail: 0 Age: 3 Lockout: 0 RegFail 0 Range: 0 feet TxBER: 0 EBcast: 0
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0
FrameNumber: 1097 SectorID: 0 Color Code: 0 BeaconVersion: 1 SectorUserCount: 0
PercentDataDwn: 50 PercentDataUpHi: 0 NumDAckSlots: 1 NumContSlots: 1 NumUAckSlots: 1
THIS IS THE BRIDGE TABLE PAGE
Bridging Table
Mac:000D56DCFAEC DestLUID:104 Age:00* Hash:0048 Ent:01
Mac:1A003EF07A53 DestLUID:103 Age:-1 Hash:0163 Ent:02
Mac:0A003EF07A53 DestLUID:102 Age:-1 Hash:0163 Ent:02
Used: 3 BridgeFree: 4093 BridgeFullErr: 0
THIS IS THE HTTP STATS PAGE
HTTP Stats
HTTP Counters
Loop State: Calling Handlers
Timer Loop Count: 29
Data Loop Count: 1143
Select Error Count: 0
Select Error Number: 0x0
OutOfSocks Count: 1
ClrProxySock Count: 0
ClrWebSock Count: 0
ServerResetCount: 0
Node Information
Web Server Node 0 Active
Web Node 2 Active
Read and Write Masks
Read Mask: 60-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
Write Mask: 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
THIS IS THE UPLINK STAT PAGE
Uplink Statistics
BadTID Count 0
BwReqTmout Count 301
BwReqContinuation Count 117
BwReqIdle Count 24
VCTxDone Count 23
SendBWReq Count 535
RcvdBWGrnt Count 135
BwGrntFailBWCbRtnd Count 8
BwGrntFailNoRoom Count 0
UpLnk Control Q Lost Count 0
UpLnk Data Q Lost Count 7
ActualTxFragsCnt Count 203
ExpectedTxFragsCnt Count 209
BwReqXmtCmpltTmout Count 2649
UpLnkEnable Count 6
UpLnkDisable Count 5
TxPacket Count 42
CurrentSize 5
THIS IS THE RF STAT PAGE
RF Statistics
Transmit Unicast Data Count 19
Transmit Broadcast Data Count 25
Receive Unicast Data Count 90
Receive Broadcast Data Count 14
Transmit Control Count 515
Recieve Control Count 154
In Sync Count 5054
Out of Sync Count 5035
Overrun Count 0
Underrun Count 0
Late Contention Count 0
Out of Range Up Sched 111
Receive Corrupt Data Count 0
Receive Bad Broadcast Control Count 0
PLL Out of Lock Count 0
Old Format Beacon Received 0
Tx Calibration Failures 0
Bad In Sync ID Received 0
Attempt Xmt MultiFrag Cntl Count 0
Temperature Out of Range 0
RSSI Out of Range 148
Range Cap Enforced 0
WELL THERE YOU HAVE IT… ANY HELP OR SUGGESTION WILL BE GREATLY APPRECIATED.
ok…we have done everything we can and the 5.7 still does not work. The AP will show a registered SM but you cannot access it. The SM shows registered status but you cannot PING between the two. My final attempt will be to try a passive reflector. Hopefully before then somebody will figure out what im doing wrong with the data I posted earlier. Thanx anyways and in advance !!!
By the way the SM shows OUT-OF-SYNC and will stop all activity
Its been a while since my last update to this problem. I had let it be until the owner called me up and asked very nicely to see what else I could do to fix the low throughput problem. The wireless link is now stable and will re-establish very nicely even in the event of power failures. So I fire up the pingplotter (www.pingplotter.com) and check the graph set to ping every second, looks really bad. Ten seconds of perfect response then zero response, 2 seconds of response, then zero, 2 then zero, then another ten seconds of good response and we begin agian with the dropouts. After about ten minutes the graph lookes like the canopy is doing this on purpose, exact response time then exact dropouts. Aprox, 5 droputs for every 30 seconds of operation. Considering the passive reflector for a 1.2 mile link, I find this very unexeptable. Any suggestions? The bad thing about this is that the owner keeps refering to the old 2.4 SMC bridge setup he had. The employees also complain a lot and look at me like im some kind of lyer. Theý argument that it is not possible that a setup witch costs half of what the canopy setup cost, will not run 1/3 the speed. So I get really angry and setup the two Linksys WAP54G again, this time about 3 meters below the canopy setup. BOING… linksys runs really fast. They try it out with PC ANYWHERE and notice the difference right off the bat. Then suddenly the database, witch is why they have this link CRASHES. The database crash NEVER happans with the canopy system. We return to the canopy system fire up the PC ANYWHERE and return to turtle speed. I let em work for about 4 hours and the database is secure, safe and sound. Anybody have any suggestions ?
We primarily use 5.7 and 5.2 equipment on our network as an ISP. There have been a few times where a device is accessable, appears fine, but no matter what we do we cannot make it work correctly. The only result i know of is to replace the SM, or in your case possibly the AP since you dont have any other SM’s that are working fine on that AP. You could also try putting a dish on the SM, and if you only have the one SM off the AP you could put a dish on the AP too (I think).