Post more info
Copy "sysinfo" from each end of the radio something might stand out.
Or assuming your RF is all locked and rssi and MSE are OK then its a feeder
port issue so just post "sysinfo 4 " to view the port status is ON for your
cable If not you can set the port speed at 100Nase-T Autoneg
I turned ACM off and ATPC and some packets will get through
occassionally. Still seeing 97% packet loss.
WISPA Wants You! Join today!
http://signup.wispa.org/
Never mind about the few packets getting through. I think that is
just OSPF changes and it seeing the other end of the link.
WISPA Wants You! Join today!
http://signup.wispa.org/
RPS is off. We learned this lesson early on.
I've been pinging the other side all night and I'll see a few packets
get through occasionally. 200 packets made it through out of 2
last night.
Still hoping someone has some ideas!
--
r put gear around here.
>
> Good luck fixing your problem, report back once you figure it out.
>
> Scott Carullo
> Brevard Wireless
> 321-205-1100 x102
>
>
>
> From: "can...@believewireless.net"
> Sent: Sunday, June 2
t;WISPA General List"
Subject: Re: [WISPA] ANOTHER Apex firmware upgrade problem
1. 17dBm / 17 dBm
2. Speed is the same on both sides.
3. (trango-view)# linktest 1
LOCK RSSI MSEBER TX
RX
1> 1 -41.10 dBm -34.40 dB 0.00E+00
Hi,
During the upgrade process, did it give any errors? You did all 4 or 5
files, correct? Have you tried doing them again and re-flashing each one
as you go?
Travis
can...@believewireless.net wrote:
> 1. 17dBm / 17 dBm
> 2. Speed is the same on both sides.
> 3. (trango-view)# linktest 1
>
1. 17dBm / 17 dBm
2. Speed is the same on both sides.
3. (trango-view)# linktest 1
LOCK RSSI MSEBER TX
RX
1> 1 -41.10 dBm -34.40 dB 0.00E+00256QAM
256QAM
(trango-view)#
(trango-config)# linktest 1
...@believewireless.net"
>> Sender: wireless-boun...@wispa.org
>> Date: Sat, 26 Jun 2010 23:07:01
>> To: ; WISPA General List
>> Reply-To: can...@believewireless.net, WISPA General List
>> Subject: [WISPA] ANOTHER Apex firmware upgrade problem
>>
>> We just
Did you check:
(1) power level on each side
(2) speed settings (same modulation and channel size on each side)
(3) what does the linktest show on each side?
Travis
Microserv
can...@believewireless.net wrote:
> We can access the units via their IBM addresses but they won't pass
> traffic. We hav
We can access the units via their IBM addresses but they won't pass
traffic. We have rebooted the radios, power cycled them, and nothing
happens.
Interestingly, the Mikrotik on one end of the link is showing up in
the neighbor list. So something is getting through.
gt; -Original Message-
> From: "can...@believewireless.net"
> Sender: wireless-boun...@wispa.org
> Date: Sat, 26 Jun 2010 23:07:01
> To: ; WISPA General List
> Reply-To: can...@believewireless.net, WISPA General List
> Subject: [WISPA] ANOTHER Apex firmware upg
ss.net"
Sender: wireless-boun...@wispa.org
Date: Sat, 26 Jun 2010 23:07:01
To: ; WISPA General List
Reply-To: can...@believewireless.net, WISPA General List
Subject: [WISPA] ANOTHER Apex firmware upgrade problem
We just upgraded one of our 18GHz links to 1.2.3 and now it won't pass
traff
Reboot both sides? Are you able to get to the far end through the close radio?
Should it be set for 100FDX or auto? Is it?
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
“Success is not final, failure is not fatal: it is the courage to
continue t
We just upgraded one of our 18GHz links to 1.2.3 and now it won't pass
traffic. We can get into both sides but nothing is going between
them. They show a link and linktest is working, just nothing is
passing.
Toggled back to the previous firmware and that didn't fix it either.
Any ideas?
-
15 matches
Mail list logo