|
NOC -> canopy------10.0.0.xxx Canopy (at tower
for backhaul) -->switch --> 10.0.0.xxx two APPO's one north and south
--> client ABO or API --> client router 12.9.xxx.xxx Public
ip
I can ping all the radios thats not the issue the
problem lies on being able to pass traffic beyond the radio to the LAN of the
radio this is where it seems to fail..
I have never had a problem pining the radios its
only the user or router behind the ABO or API at the client site. Rebooting the
radio clears the problem. I am using Servers alive to ping the radios private IP
and it pings all day long. I can then set it up to ping the client public IP it
works well then all of a sudden it just quits but I am still able to ping the
radio and manage it and this must reboot to correct the problem..
----- Original Message -----
Sent: Wednesday, November 12, 2003 7:57
AM
Subject: RE: [smartBridges] 1.08 Lockups
& Powershot question
Hi Martin,
Did you experience this Ethernet
lockup problem only with the specific installation or every installation? In
order to address this issue, we need your help to identify or reproduce it
internally. We have been trying to simulate the same but still we are unable
to do so.
If possible, could you please
reproduce the same issue at your LAB setup by connecting airBridge to the
switch and the PING continuously to the aB and AP. Could you please
kindly update us the setup and how did you simulated the
issue?
We have new BETA software (yet to
release) that added some GUI enhancement and resolves the default gateway
setting when accessing the device from different IP subnet and you can upgrade
the firmware wirelessly from the different subnet.
Please download this software http://www.smartbridges.com/beta/airBridge162.exe
(firmware 0.01.08 included)
Please use the above software
with the same firmware and see if there is any better
result.
Thank you and appreciate your
kind co-operation.
Kind regards,
Seeni
sB
Tech Support
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Blazen
Wireless
Sent: Wednesday, November
12, 2003 10:39
PM
To: [EMAIL PROTECTED]
Subject: Re: [smartBridges] 1.08 Lockups
& Powershot question
All my clients have static public
IP's on their routers and static private IP's on the radios to manage
them.
Like I said its not an issue
with the clients its an issue that from what I can tell the ABO OR ABI locks
up after it reboots after watchdog tells it to reboot and it does not seem to
come up clean?
about 80% of the time when I try
and hit reboot it says failed to reset airbrdige then the second time it does
so to me it sounds almost 100% that the unit is in some state that is not
letting info pass to the lan. I switch users back to 0.01.07 and the are
usually fine but now I have those that lose association and I have to have
them power cycle their radios..
----- Original Message -----
Sent:
Wednesday, November 12,
2003 12:38
AM
Subject: RE:
[smartBridges] 1.08 Lockups & Powershot question
Perhaps easy for
Martin to verify this theory. Do a static IP setup on the client having the
problem and see if it still locks up.
Nimesh
sB
-----Original
Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Winter
Sent: Wednesday,
November 12, 2003 3:54
PM
To: [EMAIL PROTECTED]
Subject: Re: [smartBridges] 1.08
Lockups & Powershot question
How long after setting the
equipment up and leaving it alone does it fail ? Is timing
fairly consistent for the same pc ?
Could it be that during setup
the client pc is set to an appropriate IP address for the network which
allows traffic to pass thro clients AB (is it only ABs and not APs that are
"locking"?). At some stage later (temp loss of network connection,
dhcp lease expiry etc), the clients pc requires a dhcp lease renewal and
cant see the dhcp server ? Client pc (depending on setup) might then
have no IP address set and be unable to talk to anything. The AB will
not pass dhcp to client if dhcp server is not set to respond in broadcast
mode, not unicast, for BootP. AP would not have this prob - discussed
on this forum in some detail a few weeks ago.
If this is so, could it be its
not a sB prob but a dhcp server issue (sB can't reproduce it 'cos they've
got a properly configured dhcp setup) ? For instance, Suse Linux dhcp
ootb does not support BootP and so will not properly support clients on the
ethernet side of a AB without config changes (range
dynamic-bootp). I have seen other
"embedded" dhcp servers wich don't default to this too. Aramiska
Satellite Arc doesn't and can't be configured to. Netscreen 5XP
firewall does and works well.
----- Original
Message -----
Sent:
Wednesday, November 12,
2003 5:57
AM
Subject: Re:
[smartBridges] 1.08 Lockups & Powershot
question
I have several
brands of routers and they all are still locking up on the LAN side of the
SB units..Bt of course it cant be the SB stuff ;-)
----- Original
Message -----
Sent:
Tuesday, November 11,
2003 9:15
PM
Subject: RE:
[smartBridges] 1.08 Lockups & Powershot
question
I have had
issues like this with non SB gear, but it is always the customers
router that is the problem. I have some customers who use linksys
routers and they have to power cycle they linksys once a week
sometimes. Linksys is the only router I have seen issues with. Just
another thing to throw into the mix.
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Blazen
Wireless
Sent:
Tuesday, November 11,
2003 9:34
PM
To:
[EMAIL PROTECTED]
Subject: Re: [smartBridges] 1.08
Lockups & Powershot question
What happens
to most all my client radios running 0.01.08 is that the Ethernet
locks up and no longer passes traffic to the client. You can ping the
radio if you have it set to a private IP to manage and if you log into
it and look at the statistics you will see that the counter is moving
in one direction only. If this is the case all I have had to do in the
past is manually hit the reboot button in the simple monitor screen to
reboot the radio and it comes up fine and you can then see both
counters moving. Its as if when the radios reboots on its on after the
watchdog timer activates,it does not come back up correct. >From what I
am hearing form SB it sounds as though all my clients have a windows
issue, but what's funny is that I don't see this as valid because 90%
of all my clients are on routers and routers don't run windows...
SB please
please investigate harder there has to be an issue and your not seeing
it.
-----
Original Message -----
Sent:
Tuesday, November 11,
2003 6:34
PM
Subject:
RE: [smartBridges] 1.08 Lockups & Powershot
question
I heard
about some ethernet lock up with 1.08.
I have 2
unit running it & it never happen & solve
disassociation.
Should I
install 1.08 on all ABridges ????
When it
occurs, do the ethernet light work ??
Can you
ping the device ???
If it would
be on a swich with 2 PC........ Would it be dead on both
???
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nimesh D.
Parikh
Sent:
Tuesday, November 11,
2003 10:19
PM
To:
[EMAIL PROTECTED]
Subject: RE: [smartBridges]
1.08 Lockups & Powershot question
Colin,
I note in
your message that power cycle of the airBridge does not clear the
problem but the invocation of simpleMonitor does. This leads to
conclude that the problem is not in the firmware/hardware but
something to do with the TCP/IP stack configuration of the
customer�s PC. When you invoke simpleMonitor, it automatically
starts the device discovery and then add appropriate routes to be
able to reach it. This should normally be not required but I am
sure you know about the �unpredictability� of the Windows
networking stack. It may be worth looking at the TCP/IP
configuration on the customer�s PC to see if something is causing
this problem.
In the
recent weeks we have investigated a few reported issues of
�Ethernet lockup of 1.08 firmware� and did not find any
correlation. Hope this helps.
Nimesh
smartBridges
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Colin
Watson
Sent:
Wednesday, November
12, 2003 4:08
AM
To:
[EMAIL PROTECTED]
Subject: [smartBridges] 1.08
Lockups & Powershot question
I'm
wondering if anyone else is experiencing problems still with
AirBridge units locking up? We had a unit (which I informed
support@ about) which locked up with 1.08 firmware, and I was
wondering if anyone else is using 1.08 firmware and expereinced no
problems? We find - if a 1.08 customer locks up you have to 'truck
roll' out to them - the ethernet side just won't come up.
Secondly, what exactly does the PowerShot POE injector do? Or
maybe I should rephrase, does it *only* inject power into the
unit? The reason I ask, is that, tonight we had a truck roll to a
1.08 firmware customer. The unit responded perfectly from the
wireless side, but not from the ethernet side, a power cycle
wouldn't clear it. Went round there, plugged in the trusty Compaq
laptop and as soon as simple monitor started - wallah, ethernet
statistics started incrementing. Problem was, when I disconnected
the laptop, and plugged the cable back into the customers PC - no
internet access. So I pulled out the RJ45 plug that connects to
the smartbridge (The cable carrying power & data) - thus
removing all power to the Smartbridge unit - I left the POE
connected tho, and plugged the end POE's black back end into my
laptop - worked perfectly (I use a different public IP to test
then the one the customer was using). I next changed my IP to that
of my customers PC - and nothing - no traffic. I then
unplugged the powershot (powering off all SmartBridge equipment),
and replugged it in to My PC - all was perfect. I then plugged it
into the customers PC and it was perfect. So
my question is, what else is the PowerShot
doing? or - if it is a pure injector, any ideas why what
happened, happend?
One last
thing, please track down whatever it is causing timeouts on
certain airbridge units using 1.08 - 1.07 suffers
from dissassocation it seems which is bit of a
pain. Oh and finally, I took the liberty of screencapturing the
statistics of a locked up 1.08 unit (from the wireless side )
- You can find them on www.sigmat.demon.co.uk/smartbridge/.
The ethernet counter does not increment, and aged packets seemed
to stick at 4?
|
