Re: [WISPA] Does anybody have any ideas?
I had that happen on an RB493. I got tired of it and replaced it with an RB493AH. I opened up the 493 and saw some physical damage on the board, of unknown origin. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -- From: "Scott Reed" Sent: Wednesday, March 31, 2010 3:50 PM To: "WISPA General List" Subject: Re: [WISPA] Does anybody have any ideas? > Do the radios show link connection before you reboot? If so, have you > tried to MAC telnet into them? > I have a couple that would show down but I could MAC telnet into them. > All of the onboard functions worked. Then I tried to ping something > else and got a buffer overflow error. Reboot would fix for some period > of time. At least with mine I did not have to go to the site. > > Forbes Mercy wrote: >> We have been plagued with an ongoing issue in our Mikrotik backhauls. >> It happens about once a month and only on three radios that feed each >> other, all other sites work fine. Site A is my head end, it is a >> Mikrotik 433 with an XR5 chip that feeds about five miles to another >> site to Site B. Site B has the same equipment that goes through a >> managed switch then passes on to Site C about 7 miles further. >> >> What happens is we are suddenly paged that all three are down. >> Sometimes Site A stays up, most times not, we can get into Site A since >> it's the head end and we reboot it, it comes right back up. Site B and >> C stay down, we have to drive to Site B and reboot it, it comes back up >> but Site C stays down. We have a remote reboot for it from a redundant >> feed so after rebooting it C reconnects to B and they are all up. This >> will happen three or four more times in a single day or not at all again >> for a month, it's totally unpredictable. The boards are up but not >> communicating, it also takes down the other 2.4 Mikortik AP's at Site B >> and that has to be rebooted. We normally run arp -d to clear up any >> residual, it sure appears to be traffic related and we are on a bridged >> not routed network. >> >> The only similarities is it's only this feed, it usually happens in >> spurts of a day or two then stops for a long time, it always happens >> during the working day leading me to believe it's coming from a day >> user. We run Wireshark but see nothing, we torch the towers and they >> don't show much unusual. We're thinking it might be a deluge of traffic >> between Site B and C and are thinking of putting a PC at the C tower to >> run diagnostics there. This is very manpower heavy as we have to send >> people two places and average down time is one hour to do this. We are >> going to turn our network into a routed network this Summer but that >> doesn't help now. Any ideas would be appreciated. >> >> Forbes >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> > > -- > Scott Reed > Sr. Systems Engineer > GAB Midwest > 1-800-363-1544 x2241 > 1-260-827-2241 > Cell: 260-273-7239 > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
- Original Message - From: "Justin Wilson" To: "WISPA General List" ; "Forbes Mercy" Sent: Wednesday, March 31, 2010 11:01 AM Subject: Re: [WISPA] Does anybody have any ideas? >All sites have good, clean power? Do the logs say anything before you > reboot? I've been down there with my kill-a-watt. We had only a couple of volts of fluctuation. Power factor looked fine etc. > >Dirty power causes a ton of weird issues. If you have something that > regulates the power you can rule that out. It could be maybe a motor or > something kicks on and causes enough voltage drop to lockup the board. We were at one of the sites for quite a while and saw nothing. marlon > >If would turn on graphing on the Tiks themselves. Have it write to > disk > so it survives a reboot. See if the CPU spikes, bandwidth spikes, or > whatever. Logging to disk is also a good idea. > -- > Justin Wilson > http://www.mtin.net > http://www.metrospan.net > > > > From: Forbes Mercy > Reply-To: WISPA General List > Date: Wed, 31 Mar 2010 10:46:11 -0700 > To: WISPA General List > Subject: Re: [WISPA] Does anybody have any ideas? > > Thanks for the interest in helping here is the info: > > Site A > RB532A board > AR5212 chip > v3.30 OS > Running as an AP Bridge > Running WDS and Nstreme > > Site B to Site A > RB133 board > A5413 chip > v3.30 OS > Running as Station WDS > Running WDS and Nstreme > > Site B to Site C > RB532A board > AR5413 chip > v3.30 OS > Running as an AP Bridge > Running Nstreme (not WDS) > > Site C > RB532A > AR5413 chip > v3.30 OS > Running as station pseudobridge > Running Nstreme (not WDS) > > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
70KW linears? I throw the BS flag on that one. 500 miles with no skip? That pesky law of physics throws the BS flag on that one. I would LOVE to see a mobile antenna capable of handling 70KW. Much less the power source, as well as the feedline. Don't take your organs to heaven, heaven knows we need them down here! Be an organ donor, sign your donor card today. - Original Message - From: "Chuck Profito" To: "'WISPA General List'" Sent: Wednesday, March 31, 2010 8:48 PM Subject: Re: [WISPA] Does anybody have any ideas? > Forbes, > Hope the rest of the list doesn't think I'm nuts: > Do you see any large, hi gain CB or Ham beam antennas or Truckers from the > southern area parked or loading nearby? > Within say 1/4 mile of B tower? The new mobile 70KW class C Linear's are > about as dirty as they come. Some of those > drivers from Mexico and AZ are talking direct, no skip, 500 miles on the > lower vertical channels. That much bleed over > in radiated power may trip ground on your switch and or MT boards. It > could > come right thru your tower grounding, let alone your antennas and CAt5. > Could you try batteries there? Say a smart charger thru a UPS, then to > batteries. i.e. no common ground. > > Chuck Profito > > > -Original Message- > From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On > Behalf Of Forbes Mercy > Sent: Wednesday, March 31, 2010 10:06 AM > To: WISPA General List > Subject: [WISPA] Does anybody have any ideas? > > We have been plagued with an ongoing issue in our Mikrotik backhauls. > It happens about once a month and only on three radios that feed each > other, all other sites work fine. Site A is my head end, it is a > Mikrotik 433 with an XR5 chip that feeds about five miles to another > site to Site B. Site B has the same equipment that goes through a > managed switch then passes on to Site C about 7 miles further. > > What happens is we are suddenly paged that all three are down. > Sometimes Site A stays up, most times not, we can get into Site A since > it's the head end and we reboot it, it comes right back up. Site B and > C stay down, we have to drive to Site B and reboot it, it comes back up > but Site C stays down. We have a remote reboot for it from a redundant > feed so after rebooting it C reconnects to B and they are all up. This > will happen three or four more times in a single day or not at all again > for a month, it's totally unpredictable. The boards are up but not > communicating, it also takes down the other 2.4 Mikortik AP's at Site B > and that has to be rebooted. We normally run arp -d to clear up any > residual, it sure appears to be traffic related and we are on a bridged > not routed network. > > The only similarities is it's only this feed, it usually happens in > spurts of a day or two then stops for a long time, it always happens > during the working day leading me to believe it's coming from a day > user. We run Wireshark but see nothing, we torch the towers and they > don't show much unusual. We're thinking it might be a deluge of traffic > between Site B and C and are thinking of putting a PC at the C tower to > run diagnostics there. This is very manpower heavy as we have to send > people two places and average down time is one hour to do this. We are > going to turn our network into a routed network this Summer but that > doesn't help now. Any ideas would be appreciated. > > Forbes > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Chuck, You hope we don't *think* you're nuts?! ;-) Chuck On Mar 31, 2010, at 9:48 PM, Chuck Profito wrote: > Forbes, > Hope the rest of the list doesn't think I'm nuts: > Do you see any large, hi gain CB or Ham beam antennas or Truckers from the > southern area parked or loading nearby? > Within say 1/4 mile of B tower? The new mobile 70KW class C Linear's are > about as dirty as they come. Some of those > drivers from Mexico and AZ are talking direct, no skip, 500 miles on the > lower vertical channels. That much bleed over > in radiated power may trip ground on your switch and or MT boards. It could > come right thru your tower grounding, let alone your antennas and CAt5. > Could you try batteries there? Say a smart charger thru a UPS, then to > batteries. i.e. no common ground. > > Chuck Profito > > > -Original Message- > From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On > Behalf Of Forbes Mercy > Sent: Wednesday, March 31, 2010 10:06 AM > To: WISPA General List > Subject: [WISPA] Does anybody have any ideas? > > We have been plagued with an ongoing issue in our Mikrotik backhauls. > It happens about once a month and only on three radios that feed each > other, all other sites work fine. Site A is my head end, it is a > Mikrotik 433 with an XR5 chip that feeds about five miles to another > site to Site B. Site B has the same equipment that goes through a > managed switch then passes on to Site C about 7 miles further. > > What happens is we are suddenly paged that all three are down. > Sometimes Site A stays up, most times not, we can get into Site A since > it's the head end and we reboot it, it comes right back up. Site B and > C stay down, we have to drive to Site B and reboot it, it comes back up > but Site C stays down. We have a remote reboot for it from a redundant > feed so after rebooting it C reconnects to B and they are all up. This > will happen three or four more times in a single day or not at all again > for a month, it's totally unpredictable. The boards are up but not > communicating, it also takes down the other 2.4 Mikortik AP's at Site B > and that has to be rebooted. We normally run arp -d to clear up any > residual, it sure appears to be traffic related and we are on a bridged > not routed network. > > The only similarities is it's only this feed, it usually happens in > spurts of a day or two then stops for a long time, it always happens > during the working day leading me to believe it's coming from a day > user. We run Wireshark but see nothing, we torch the towers and they > don't show much unusual. We're thinking it might be a deluge of traffic > between Site B and C and are thinking of putting a PC at the C tower to > run diagnostics there. This is very manpower heavy as we have to send > people two places and average down time is one hour to do this. We are > going to turn our network into a routed network this Summer but that > doesn't help now. Any ideas would be appreciated. > > Forbes > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -- Chuck Bartosch Clarity Connect, Inc. 200 Pleasant Grove Road Ithaca, NY 14850 (607) 257-8268 "When the stars threw down their spears, and water'd heaven with their tears, Did He smile, His work to see? Did He who made the Lamb make thee?" >From William Blake's Tiger!, Tiger! WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Forbes, Hope the rest of the list doesn't think I'm nuts: Do you see any large, hi gain CB or Ham beam antennas or Truckers from the southern area parked or loading nearby? Within say 1/4 mile of B tower? The new mobile 70KW class C Linear's are about as dirty as they come. Some of those drivers from Mexico and AZ are talking direct, no skip, 500 miles on the lower vertical channels. That much bleed over in radiated power may trip ground on your switch and or MT boards. It could come right thru your tower grounding, let alone your antennas and CAt5. Could you try batteries there? Say a smart charger thru a UPS, then to batteries. i.e. no common ground. Chuck Profito -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Forbes Mercy Sent: Wednesday, March 31, 2010 10:06 AM To: WISPA General List Subject: [WISPA] Does anybody have any ideas? We have been plagued with an ongoing issue in our Mikrotik backhauls. It happens about once a month and only on three radios that feed each other, all other sites work fine. Site A is my head end, it is a Mikrotik 433 with an XR5 chip that feeds about five miles to another site to Site B. Site B has the same equipment that goes through a managed switch then passes on to Site C about 7 miles further. What happens is we are suddenly paged that all three are down. Sometimes Site A stays up, most times not, we can get into Site A since it's the head end and we reboot it, it comes right back up. Site B and C stay down, we have to drive to Site B and reboot it, it comes back up but Site C stays down. We have a remote reboot for it from a redundant feed so after rebooting it C reconnects to B and they are all up. This will happen three or four more times in a single day or not at all again for a month, it's totally unpredictable. The boards are up but not communicating, it also takes down the other 2.4 Mikortik AP's at Site B and that has to be rebooted. We normally run arp -d to clear up any residual, it sure appears to be traffic related and we are on a bridged not routed network. The only similarities is it's only this feed, it usually happens in spurts of a day or two then stops for a long time, it always happens during the working day leading me to believe it's coming from a day user. We run Wireshark but see nothing, we torch the towers and they don't show much unusual. We're thinking it might be a deluge of traffic between Site B and C and are thinking of putting a PC at the C tower to run diagnostics there. This is very manpower heavy as we have to send people two places and average down time is one hour to do this. We are going to turn our network into a routed network this Summer but that doesn't help now. Any ideas would be appreciated. Forbes WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
last year we had problems in passing traffic and we were instructed by a fellow WISP to do it this way. Its worked for about 8 months with no problem until this started happening. Perhaps we should make them all the same, we're considering that as one of the fixes. Forbes On 3/31/2010 12:37 PM, Greg Ihnen wrote: > Why aren't you using WDS on the site B-C link? > > Greg > On Mar 31, 2010, at 1:16 PM, Forbes Mercy wrote: > > >> Thanks for the interest in helping here is the info: >> >> Site A >> RB532A board >> AR5212 chip >> v3.30 OS >> Running as an AP Bridge >> Running WDS and Nstreme >> >> Site B to Site A >> RB133 board >> A5413 chip >> v3.30 OS >> Running as Station WDS >> Running WDS and Nstreme >> >> Site B to Site C >> RB532A board >> AR5413 chip >> v3.30 OS >> Running as an AP Bridge >> Running Nstreme (not WDS) >> >> Site C >> RB532A >> AR5413 chip >> v3.30 OS >> Running as station pseudobridge >> Running Nstreme (not WDS) >> >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Excellent question, we have never tried that yet, we simply reboot. It's 400 people down so we kind of hurry, next time we will. On 3/31/2010 12:39 PM, Greg Ihnen wrote: > Do you mean that at site A when your system is in trouble you are able to > communicate with the 433 over the wired connection? What about sites B and C? > When the tech gets on scene does he have access to the gear that's down via > ethernet? Does the gear respond? > > Greg > On Mar 31, 2010, at 12:36 PM, Forbes Mercy wrote: > > >> We have been plagued with an ongoing issue in our Mikrotik backhauls. >> It happens about once a month and only on three radios that feed each >> other, all other sites work fine. Site A is my head end, it is a >> Mikrotik 433 with an XR5 chip that feeds about five miles to another >> site to Site B. Site B has the same equipment that goes through a >> managed switch then passes on to Site C about 7 miles further. >> >> What happens is we are suddenly paged that all three are down. >> Sometimes Site A stays up, most times not, we can get into Site A since >> it's the head end and we reboot it, it comes right back up. Site B and >> C stay down, we have to drive to Site B and reboot it, it comes back up >> but Site C stays down. We have a remote reboot for it from a redundant >> feed so after rebooting it C reconnects to B and they are all up. This >> will happen three or four more times in a single day or not at all again >> for a month, it's totally unpredictable. The boards are up but not >> communicating, it also takes down the other 2.4 Mikortik AP's at Site B >> and that has to be rebooted. We normally run arp -d to clear up any >> residual, it sure appears to be traffic related and we are on a bridged >> not routed network. >> >> The only similarities is it's only this feed, it usually happens in >> spurts of a day or two then stops for a long time, it always happens >> during the working day leading me to believe it's coming from a day >> user. We run Wireshark but see nothing, we torch the towers and they >> don't show much unusual. We're thinking it might be a deluge of traffic >> between Site B and C and are thinking of putting a PC at the C tower to >> run diagnostics there. This is very manpower heavy as we have to send >> people two places and average down time is one hour to do this. We are >> going to turn our network into a routed network this Summer but that >> doesn't help now. Any ideas would be appreciated. >> >> Forbes >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
They do not show registered at the site that feeds them so no, something is causing them is dissociate. Thanks for the input, Forbes On 3/31/2010 1:50 PM, Scott Reed wrote: > Do the radios show link connection before you reboot? If so, have you > tried to MAC telnet into them? > I have a couple that would show down but I could MAC telnet into them. > All of the onboard functions worked. Then I tried to ping something > else and got a buffer overflow error. Reboot would fix for some period > of time. At least with mine I did not have to go to the site. > > Forbes Mercy wrote: > >> We have been plagued with an ongoing issue in our Mikrotik backhauls. >> It happens about once a month and only on three radios that feed each >> other, all other sites work fine. Site A is my head end, it is a >> Mikrotik 433 with an XR5 chip that feeds about five miles to another >> site to Site B. Site B has the same equipment that goes through a >> managed switch then passes on to Site C about 7 miles further. >> >> What happens is we are suddenly paged that all three are down. >> Sometimes Site A stays up, most times not, we can get into Site A since >> it's the head end and we reboot it, it comes right back up. Site B and >> C stay down, we have to drive to Site B and reboot it, it comes back up >> but Site C stays down. We have a remote reboot for it from a redundant >> feed so after rebooting it C reconnects to B and they are all up. This >> will happen three or four more times in a single day or not at all again >> for a month, it's totally unpredictable. The boards are up but not >> communicating, it also takes down the other 2.4 Mikortik AP's at Site B >> and that has to be rebooted. We normally run arp -d to clear up any >> residual, it sure appears to be traffic related and we are on a bridged >> not routed network. >> >> The only similarities is it's only this feed, it usually happens in >> spurts of a day or two then stops for a long time, it always happens >> during the working day leading me to believe it's coming from a day >> user. We run Wireshark but see nothing, we torch the towers and they >> don't show much unusual. We're thinking it might be a deluge of traffic >> between Site B and C and are thinking of putting a PC at the C tower to >> run diagnostics there. This is very manpower heavy as we have to send >> people two places and average down time is one hour to do this. We are >> going to turn our network into a routed network this Summer but that >> doesn't help now. Any ideas would be appreciated. >> >> Forbes >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> >> > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Do the radios show link connection before you reboot? If so, have you tried to MAC telnet into them? I have a couple that would show down but I could MAC telnet into them. All of the onboard functions worked. Then I tried to ping something else and got a buffer overflow error. Reboot would fix for some period of time. At least with mine I did not have to go to the site. Forbes Mercy wrote: > We have been plagued with an ongoing issue in our Mikrotik backhauls. > It happens about once a month and only on three radios that feed each > other, all other sites work fine. Site A is my head end, it is a > Mikrotik 433 with an XR5 chip that feeds about five miles to another > site to Site B. Site B has the same equipment that goes through a > managed switch then passes on to Site C about 7 miles further. > > What happens is we are suddenly paged that all three are down. > Sometimes Site A stays up, most times not, we can get into Site A since > it's the head end and we reboot it, it comes right back up. Site B and > C stay down, we have to drive to Site B and reboot it, it comes back up > but Site C stays down. We have a remote reboot for it from a redundant > feed so after rebooting it C reconnects to B and they are all up. This > will happen three or four more times in a single day or not at all again > for a month, it's totally unpredictable. The boards are up but not > communicating, it also takes down the other 2.4 Mikortik AP's at Site B > and that has to be rebooted. We normally run arp -d to clear up any > residual, it sure appears to be traffic related and we are on a bridged > not routed network. > > The only similarities is it's only this feed, it usually happens in > spurts of a day or two then stops for a long time, it always happens > during the working day leading me to believe it's coming from a day > user. We run Wireshark but see nothing, we torch the towers and they > don't show much unusual. We're thinking it might be a deluge of traffic > between Site B and C and are thinking of putting a PC at the C tower to > run diagnostics there. This is very manpower heavy as we have to send > people two places and average down time is one hour to do this. We are > going to turn our network into a routed network this Summer but that > doesn't help now. Any ideas would be appreciated. > > Forbes > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > -- Scott Reed Sr. Systems Engineer GAB Midwest 1-800-363-1544 x2241 1-260-827-2241 Cell: 260-273-7239 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Do you mean that at site A when your system is in trouble you are able to communicate with the 433 over the wired connection? What about sites B and C? When the tech gets on scene does he have access to the gear that's down via ethernet? Does the gear respond? Greg On Mar 31, 2010, at 12:36 PM, Forbes Mercy wrote: > We have been plagued with an ongoing issue in our Mikrotik backhauls. > It happens about once a month and only on three radios that feed each > other, all other sites work fine. Site A is my head end, it is a > Mikrotik 433 with an XR5 chip that feeds about five miles to another > site to Site B. Site B has the same equipment that goes through a > managed switch then passes on to Site C about 7 miles further. > > What happens is we are suddenly paged that all three are down. > Sometimes Site A stays up, most times not, we can get into Site A since > it's the head end and we reboot it, it comes right back up. Site B and > C stay down, we have to drive to Site B and reboot it, it comes back up > but Site C stays down. We have a remote reboot for it from a redundant > feed so after rebooting it C reconnects to B and they are all up. This > will happen three or four more times in a single day or not at all again > for a month, it's totally unpredictable. The boards are up but not > communicating, it also takes down the other 2.4 Mikortik AP's at Site B > and that has to be rebooted. We normally run arp -d to clear up any > residual, it sure appears to be traffic related and we are on a bridged > not routed network. > > The only similarities is it's only this feed, it usually happens in > spurts of a day or two then stops for a long time, it always happens > during the working day leading me to believe it's coming from a day > user. We run Wireshark but see nothing, we torch the towers and they > don't show much unusual. We're thinking it might be a deluge of traffic > between Site B and C and are thinking of putting a PC at the C tower to > run diagnostics there. This is very manpower heavy as we have to send > people two places and average down time is one hour to do this. We are > going to turn our network into a routed network this Summer but that > doesn't help now. Any ideas would be appreciated. > > Forbes > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Why aren't you using WDS on the site B-C link? Greg On Mar 31, 2010, at 1:16 PM, Forbes Mercy wrote: > Thanks for the interest in helping here is the info: > > Site A > RB532A board > AR5212 chip > v3.30 OS > Running as an AP Bridge > Running WDS and Nstreme > > Site B to Site A > RB133 board > A5413 chip > v3.30 OS > Running as Station WDS > Running WDS and Nstreme > > Site B to Site C > RB532A board > AR5413 chip > v3.30 OS > Running as an AP Bridge > Running Nstreme (not WDS) > > Site C > RB532A > AR5413 chip > v3.30 OS > Running as station pseudobridge > Running Nstreme (not WDS) > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
DFS enabled on any of them? There was something about DFS issues, I think before the 3.3 firmware. Anyone know if that was fixed in 3.3? Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Forbes Mercy Sent: Wednesday, March 31, 2010 1:46 PM To: WISPA General List Subject: Re: [WISPA] Does anybody have any ideas? Thanks for the interest in helping here is the info: Site A RB532A board AR5212 chip v3.30 OS Running as an AP Bridge Running WDS and Nstreme Site B to Site A RB133 board A5413 chip v3.30 OS Running as Station WDS Running WDS and Nstreme Site B to Site C RB532A board AR5413 chip v3.30 OS Running as an AP Bridge Running Nstreme (not WDS) Site C RB532A AR5413 chip v3.30 OS Running as station pseudobridge Running Nstreme (not WDS) WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Is there a reason you are using Pseudobridge? You will not be able to pass any MAC addresses behind the Station (CPE/Slave), it MAC NATs. Change to WDS instead and see if your problems go away. It is better to have a layer 2 bridge and deal with the broadcasts at each site. Eric Rogers Precision Data Solutions, LLC (317) 831-3000 x200 -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Forbes Mercy Sent: Wednesday, March 31, 2010 1:46 PM To: WISPA General List Subject: Re: [WISPA] Does anybody have any ideas? Thanks for the interest in helping here is the info: Site A RB532A board AR5212 chip v3.30 OS Running as an AP Bridge Running WDS and Nstreme Site B to Site A RB133 board A5413 chip v3.30 OS Running as Station WDS Running WDS and Nstreme Site B to Site C RB532A board AR5413 chip v3.30 OS Running as an AP Bridge Running Nstreme (not WDS) Site C RB532A AR5413 chip v3.30 OS Running as station pseudobridge Running Nstreme (not WDS) WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
All sites have good, clean power? Do the logs say anything before you reboot? Dirty power causes a ton of weird issues. If you have something that regulates the power you can rule that out. It could be maybe a motor or something kicks on and causes enough voltage drop to lockup the board. If would turn on graphing on the Tiks themselves. Have it write to disk so it survives a reboot. See if the CPU spikes, bandwidth spikes, or whatever. Logging to disk is also a good idea. -- Justin Wilson http://www.mtin.net http://www.metrospan.net From: Forbes Mercy Reply-To: WISPA General List Date: Wed, 31 Mar 2010 10:46:11 -0700 To: WISPA General List Subject: Re: [WISPA] Does anybody have any ideas? Thanks for the interest in helping here is the info: Site A RB532A board AR5212 chip v3.30 OS Running as an AP Bridge Running WDS and Nstreme Site B to Site A RB133 board A5413 chip v3.30 OS Running as Station WDS Running WDS and Nstreme Site B to Site C RB532A board AR5413 chip v3.30 OS Running as an AP Bridge Running Nstreme (not WDS) Site C RB532A AR5413 chip v3.30 OS Running as station pseudobridge Running Nstreme (not WDS) WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Thanks for the interest in helping here is the info: Site A RB532A board AR5212 chip v3.30 OS Running as an AP Bridge Running WDS and Nstreme Site B to Site A RB133 board A5413 chip v3.30 OS Running as Station WDS Running WDS and Nstreme Site B to Site C RB532A board AR5413 chip v3.30 OS Running as an AP Bridge Running Nstreme (not WDS) Site C RB532A AR5413 chip v3.30 OS Running as station pseudobridge Running Nstreme (not WDS) WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
What RouterOS version are you running? Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Forbes Mercy Sent: Wednesday, March 31, 2010 1:06 PM To: WISPA General List Subject: [WISPA] Does anybody have any ideas? We have been plagued with an ongoing issue in our Mikrotik backhauls. It happens about once a month and only on three radios that feed each other, all other sites work fine. Site A is my head end, it is a Mikrotik 433 with an XR5 chip that feeds about five miles to another site to Site B. Site B has the same equipment that goes through a managed switch then passes on to Site C about 7 miles further. What happens is we are suddenly paged that all three are down. Sometimes Site A stays up, most times not, we can get into Site A since it's the head end and we reboot it, it comes right back up. Site B and C stay down, we have to drive to Site B and reboot it, it comes back up but Site C stays down. We have a remote reboot for it from a redundant feed so after rebooting it C reconnects to B and they are all up. This will happen three or four more times in a single day or not at all again for a month, it's totally unpredictable. The boards are up but not communicating, it also takes down the other 2.4 Mikortik AP's at Site B and that has to be rebooted. We normally run arp -d to clear up any residual, it sure appears to be traffic related and we are on a bridged not routed network. The only similarities is it's only this feed, it usually happens in spurts of a day or two then stops for a long time, it always happens during the working day leading me to believe it's coming from a day user. We run Wireshark but see nothing, we torch the towers and they don't show much unusual. We're thinking it might be a deluge of traffic between Site B and C and are thinking of putting a PC at the C tower to run diagnostics there. This is very manpower heavy as we have to send people two places and average down time is one hour to do this. We are going to turn our network into a routed network this Summer but that doesn't help now. Any ideas would be appreciated. Forbes WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
He says he's all bridged right now. Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of e...@wisp-router.com Sent: Wednesday, March 31, 2010 1:22 PM To: WISPA General List Subject: Re: [WISPA] Does anybody have any ideas? Bridged or routed ? /Eje Sent via BlackBerry from T-Mobile -Original Message- From: Forbes Mercy Date: Wed, 31 Mar 2010 10:06:29 To: WISPA General List Subject: [WISPA] Does anybody have any ideas? We have been plagued with an ongoing issue in our Mikrotik backhauls. It happens about once a month and only on three radios that feed each other, all other sites work fine. Site A is my head end, it is a Mikrotik 433 with an XR5 chip that feeds about five miles to another site to Site B. Site B has the same equipment that goes through a managed switch then passes on to Site C about 7 miles further. What happens is we are suddenly paged that all three are down. Sometimes Site A stays up, most times not, we can get into Site A since it's the head end and we reboot it, it comes right back up. Site B and C stay down, we have to drive to Site B and reboot it, it comes back up but Site C stays down. We have a remote reboot for it from a redundant feed so after rebooting it C reconnects to B and they are all up. This will happen three or four more times in a single day or not at all again for a month, it's totally unpredictable. The boards are up but not communicating, it also takes down the other 2.4 Mikortik AP's at Site B and that has to be rebooted. We normally run arp -d to clear up any residual, it sure appears to be traffic related and we are on a bridged not routed network. The only similarities is it's only this feed, it usually happens in spurts of a day or two then stops for a long time, it always happens during the working day leading me to believe it's coming from a day user. We run Wireshark but see nothing, we torch the towers and they don't show much unusual. We're thinking it might be a deluge of traffic between Site B and C and are thinking of putting a PC at the C tower to run diagnostics there. This is very manpower heavy as we have to send people two places and average down time is one hour to do this. We are going to turn our network into a routed network this Summer but that doesn't help now. Any ideas would be appreciated. Forbes WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Bridged or routed ? /Eje Sent via BlackBerry from T-Mobile -Original Message- From: Forbes Mercy Date: Wed, 31 Mar 2010 10:06:29 To: WISPA General List Subject: [WISPA] Does anybody have any ideas? We have been plagued with an ongoing issue in our Mikrotik backhauls. It happens about once a month and only on three radios that feed each other, all other sites work fine. Site A is my head end, it is a Mikrotik 433 with an XR5 chip that feeds about five miles to another site to Site B. Site B has the same equipment that goes through a managed switch then passes on to Site C about 7 miles further. What happens is we are suddenly paged that all three are down. Sometimes Site A stays up, most times not, we can get into Site A since it's the head end and we reboot it, it comes right back up. Site B and C stay down, we have to drive to Site B and reboot it, it comes back up but Site C stays down. We have a remote reboot for it from a redundant feed so after rebooting it C reconnects to B and they are all up. This will happen three or four more times in a single day or not at all again for a month, it's totally unpredictable. The boards are up but not communicating, it also takes down the other 2.4 Mikortik AP's at Site B and that has to be rebooted. We normally run arp -d to clear up any residual, it sure appears to be traffic related and we are on a bridged not routed network. The only similarities is it's only this feed, it usually happens in spurts of a day or two then stops for a long time, it always happens during the working day leading me to believe it's coming from a day user. We run Wireshark but see nothing, we torch the towers and they don't show much unusual. We're thinking it might be a deluge of traffic between Site B and C and are thinking of putting a PC at the C tower to run diagnostics there. This is very manpower heavy as we have to send people two places and average down time is one hour to do this. We are going to turn our network into a routed network this Summer but that doesn't help now. Any ideas would be appreciated. Forbes WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Do you have other 5GHz in that area? Any possibility of the DFS being triggered? Bob- -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Forbes Mercy Sent: Wednesday, March 31, 2010 1:06 PM To: WISPA General List Subject: [WISPA] Does anybody have any ideas? We have been plagued with an ongoing issue in our Mikrotik backhauls. It happens about once a month and only on three radios that feed each other, all other sites work fine. Site A is my head end, it is a Mikrotik 433 with an XR5 chip that feeds about five miles to another site to Site B. Site B has the same equipment that goes through a managed switch then passes on to Site C about 7 miles further. What happens is we are suddenly paged that all three are down. Sometimes Site A stays up, most times not, we can get into Site A since it's the head end and we reboot it, it comes right back up. Site B and C stay down, we have to drive to Site B and reboot it, it comes back up but Site C stays down. We have a remote reboot for it from a redundant feed so after rebooting it C reconnects to B and they are all up. This will happen three or four more times in a single day or not at all again for a month, it's totally unpredictable. The boards are up but not communicating, it also takes down the other 2.4 Mikortik AP's at Site B and that has to be rebooted. We normally run arp -d to clear up any residual, it sure appears to be traffic related and we are on a bridged not routed network. The only similarities is it's only this feed, it usually happens in spurts of a day or two then stops for a long time, it always happens during the working day leading me to believe it's coming from a day user. We run Wireshark but see nothing, we torch the towers and they don't show much unusual. We're thinking it might be a deluge of traffic between Site B and C and are thinking of putting a PC at the C tower to run diagnostics there. This is very manpower heavy as we have to send people two places and average down time is one hour to do this. We are going to turn our network into a routed network this Summer but that doesn't help now. Any ideas would be appreciated. Forbes WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Does anybody have any ideas?
Maybe others have the power to keep this in mind but a network diagram would certainly help. >From what I'm gathering the issue isn't a MT backhaul but rather things at a site going up/down in weird patterns. My first guess would be bad switch. 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 that counts.” --- Winston Churchill On Wed, Mar 31, 2010 at 1:06 PM, Forbes Mercy wrote: > We have been plagued with an ongoing issue in our Mikrotik backhauls. > It happens about once a month and only on three radios that feed each > other, all other sites work fine. Site A is my head end, it is a > Mikrotik 433 with an XR5 chip that feeds about five miles to another > site to Site B. Site B has the same equipment that goes through a > managed switch then passes on to Site C about 7 miles further. > > What happens is we are suddenly paged that all three are down. > Sometimes Site A stays up, most times not, we can get into Site A since > it's the head end and we reboot it, it comes right back up. Site B and > C stay down, we have to drive to Site B and reboot it, it comes back up > but Site C stays down. We have a remote reboot for it from a redundant > feed so after rebooting it C reconnects to B and they are all up. This > will happen three or four more times in a single day or not at all again > for a month, it's totally unpredictable. The boards are up but not > communicating, it also takes down the other 2.4 Mikortik AP's at Site B > and that has to be rebooted. We normally run arp -d to clear up any > residual, it sure appears to be traffic related and we are on a bridged > not routed network. > > The only similarities is it's only this feed, it usually happens in > spurts of a day or two then stops for a long time, it always happens > during the working day leading me to believe it's coming from a day > user. We run Wireshark but see nothing, we torch the towers and they > don't show much unusual. We're thinking it might be a deluge of traffic > between Site B and C and are thinking of putting a PC at the C tower to > run diagnostics there. This is very manpower heavy as we have to send > people two places and average down time is one hour to do this. We are > going to turn our network into a routed network this Summer but that > doesn't help now. Any ideas would be appreciated. > > Forbes > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
