[AFMUG] Software 13.4
Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
If anyone is good with Cacti could they create a graph template with the new Frame Utilization tests? Seems like that would be a good metric to graph to determine if an AP is overloaded. On Thu, Jul 2, 2015 at 2:11 PM, Ryan Ray wrote: > Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade > and let us know how it goes :P > >
Re: [AFMUG] Software 13.4
We're running build 10 on about 15-20 subs right now. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
On 3.65 450 should the AP or SM be updated first? Running build 10 and 11 on a few units here and there, betting its been tested pretty well.
Re: [AFMUG] Software 13.4
Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. From: Ryan Ray Sent: Thursday, July 02, 2015 4:11 PM To: af@afmug.com Subject: [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
We have seen no (new) show stoppers. We still see the occasional dropped session to an individual SM, but easy to clear from the AP. If you're already running 13.4-build X, I think you should be able to upgrade in any order. Otherwise, it is my practice to upgrade the SMs first, then the AP. bp On 7/2/2015 2:29 PM, Matt wrote: On 3.65 450 should the AP or SM be updated first? Running build 10 and 11 on a few units here and there, betting its been tested pretty well.
Re: [AFMUG] Software 13.4
Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof wrote: > Is it just me, or was this distributed differently than in the past? I > don’t remember .zip files with the release notes inside. Also when I > opened the release notes, Adobe Reader wanted to connect to a “review > server” and share my email address etc. with all other reviewers. WTF? > Did I just hit some hotkey accidentally? > > Also, I don’t see anything in the release notes about SM alignment tone. > Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my > brain just not working today. I thought it was 13.3 and all its progeny > were dead to me because I can’t live without oxygen, water, and alignment > tone. > > Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment > tone. > > > *From:* Ryan Ray > *Sent:* Thursday, July 02, 2015 4:11 PM > *To:* af@afmug.com > *Subject:* [AFMUG] Software 13.4 > > Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade > and let us know how it goes :P > >
Re: [AFMUG] Software 13.4
I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof <mailto:af...@kwisp.com>> wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. *From:* Ryan Ray <mailto:ryan...@gmail.com> *Sent:* Thursday, July 02, 2015 4:11 PM *To:* af@afmug.com <mailto:af@afmug.com> *Subject:* [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
There is an announcement on the 430 page that the 450 load should be used on 430s needing to connect to a 450 AP. How is this supposed to be managed? Is there a reason to actually load the 430 firmware on a 430 (anything)? bp On 7/2/2015 3:02 PM, George Skorup wrote: I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof <mailto:af...@kwisp.com>> wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. *From:* Ryan Ray <mailto:ryan...@gmail.com> *Sent:* Thursday, July 02, 2015 4:11 PM *To:* af@afmug.com <mailto:af@afmug.com> *Subject:* [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
We have been running 13.4 build 11 for some time now. I have not seen any major issues with it. The 450 build works fine on the 430 AP’s. The only thing that I know was a problem was P8 FSK radios bricking when upgraded to build 11. I have not read the release notes to see if the release version addresses that problem. Mark > On Jul 2, 2015, at 6:10 PM, Bill Prince wrote: > > There is an announcement on the 430 page that the 450 load should be used on > 430s needing to connect to a 450 AP. > > How is this supposed to be managed? Is there a reason to actually load the > 430 firmware on a 430 (anything)? > > > bp > > > On 7/2/2015 3:02 PM, George Skorup wrote: >> I'm just about to look through the release notes. And then GTFO here for the >> long weekend! >> >> They said the alignment tone issue required a new FPGA build. Guess they got >> it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. >> Maybe it messed up the 430 too? >> >> Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a >> separate package. >> >> On 7/2/2015 4:53 PM, Ryan Ray wrote: >>> Definitely different than before. There are mentions of the alignment tone >>> being fixed in the release notes but I'm not sure if it's for PMP450 or >>> PMP100 or what. Now that it's all combined firmware. >>> >>> On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof >> <mailto:af...@kwisp.com>> wrote: >>> Is it just me, or was this distributed differently than in the past? I >>> don’t remember .zip files with the release notes inside. Also when I >>> opened the release notes, Adobe Reader wanted to connect to a “review >>> server” and share my email address etc. with all other reviewers. WTF? >>> Did I just hit some hotkey accidentally? >>> >>> Also, I don’t see anything in the release notes about SM alignment tone. >>> Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my >>> brain just not working today. I thought it was 13.3 and all its progeny >>> were dead to me because I can’t live without oxygen, water, and alignment >>> tone. >>> >>> Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment >>> tone. >>> >>> >>> From: Ryan Ray <mailto:ryan...@gmail.com> >>> Sent: Thursday, July 02, 2015 4:11 PM >>> To: af@afmug.com <mailto:af@afmug.com> >>> Subject: [AFMUG] Software 13.4 >>> >>> Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade >>> and let us know how it goes :P >>> >>> >> >
Re: [AFMUG] Software 13.4
Hopefully the watchdog resets on 450 APs goes away. That is getting stupid on 13.2.1. Just had another one about 10 minutes ago. On 7/2/2015 7:50 PM, Mark Radabaugh wrote: We have been running 13.4 build 11 for some time now. I have not seen any major issues with it. The 450 build works fine on the 430 AP’s. The only thing that I know was a problem was P8 FSK radios bricking when upgraded to build 11. I have not read the release notes to see if the release version addresses that problem. Mark On Jul 2, 2015, at 6:10 PM, Bill Prince <mailto:part15...@gmail.com>> wrote: There is an announcement on the 430 page that the 450 load should be used on 430s needing to connect to a 450 AP. How is this supposed to be managed? Is there a reason to actually load the 430 firmware on a 430 (anything)? bp On 7/2/2015 3:02 PM, George Skorup wrote: I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof <mailto:af...@kwisp.com>> wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. *From:* Ryan Ray <mailto:ryan...@gmail.com> *Sent:* Thursday, July 02, 2015 4:11 PM *To:* af@afmug.com <mailto:af@afmug.com> *Subject:* [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
We spent a LOT of time on those George… we nailed many of them cold in 13.4. Please let us know if you’re still seeing them (“watchdog reset” can mean lots of things, there were a couple of cases that we couldn’t reproduce). Regarding the “Adobe connecting to review server” thing… ignore it. That was likely an oversight on our part. We use that server to allow multiple folks to review and comment on the release notes (you know, for version control, collaboration, etc.). We were rushing a bit to get the documentation over the finish line this week before the holiday. Alignment tone is there and working! Let us know if you guys find anything else we should know about, this one was a long time coming… but we’re proud of the finished product. Enjoy. Happy 4th of July to all! Matt From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 02, 2015 9:33 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4 Hopefully the watchdog resets on 450 APs goes away. That is getting stupid on 13.2.1. Just had another one about 10 minutes ago. On 7/2/2015 7:50 PM, Mark Radabaugh wrote: We have been running 13.4 build 11 for some time now. I have not seen any major issues with it. The 450 build works fine on the 430 AP’s. The only thing that I know was a problem was P8 FSK radios bricking when upgraded to build 11. I have not read the release notes to see if the release version addresses that problem. Mark On Jul 2, 2015, at 6:10 PM, Bill Prince mailto:part15...@gmail.com>> wrote: There is an announcement on the 430 page that the 450 load should be used on 430s needing to connect to a 450 AP. How is this supposed to be managed? Is there a reason to actually load the 430 firmware on a 430 (anything)? bp On 7/2/2015 3:02 PM, George Skorup wrote: I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof mailto:af...@kwisp.com>> wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. From: Ryan Ray<mailto:ryan...@gmail.com> Sent: Thursday, July 02, 2015 4:11 PM To: af@afmug.com<mailto:af@afmug.com> Subject: [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
I thought they were done updating fsk On Jul 2, 2015 11:01 PM, "Matt Mangriotis" < matt.mangrio...@cambiumnetworks.com> wrote: > We spent a LOT of time on those George… we nailed many of them cold in > 13.4. Please let us know if you’re still seeing them (“watchdog reset” can > mean lots of things, there were a couple of cases that we couldn’t > reproduce). > > > > Regarding the “Adobe connecting to review server” thing… ignore it. That > was likely an oversight on our part. We use that server to allow multiple > folks to review and comment on the release notes (you know, for version > control, collaboration, etc.). We were rushing a bit to get the > documentation over the finish line this week before the holiday. > > > > Alignment tone is there and working! > > > > Let us know if you guys find anything else we should know about, this one > was a long time coming… but we’re proud of the finished product. Enjoy. > > > > Happy 4th of July to all! > > > > Matt > > > > *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *George Skorup > *Sent:* Thursday, July 02, 2015 9:33 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] Software 13.4 > > > > Hopefully the watchdog resets on 450 APs goes away. That is getting stupid > on 13.2.1. Just had another one about 10 minutes ago. > > On 7/2/2015 7:50 PM, Mark Radabaugh wrote: > > We have been running 13.4 build 11 for some time now. I have not seen > any major issues with it. > > > > The 450 build works fine on the 430 AP’s. > > > > The only thing that I know was a problem was P8 FSK radios bricking when > upgraded to build 11. I have not read the release notes to see if the > release version addresses that problem. > > > > Mark > > > > > > On Jul 2, 2015, at 6:10 PM, Bill Prince wrote: > > > > There is an announcement on the 430 page that the 450 load should be used > on 430s needing to connect to a 450 AP. > > How is this supposed to be managed? Is there a reason to actually load the > 430 firmware on a 430 (anything)? > > > > bp > > > > > > On 7/2/2015 3:02 PM, George Skorup wrote: > > I'm just about to look through the release notes. And then GTFO here for > the long weekend! > > They said the alignment tone issue required a new FPGA build. Guess they > got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't > affected. Maybe it messed up the 430 too? > > Combined firmware? You mean for 430 and 450? I guess so. But FSK is still > a separate package. > > On 7/2/2015 4:53 PM, Ryan Ray wrote: > > Definitely different than before. There are mentions of the alignment > tone being fixed in the release notes but I'm not sure if it's for PMP450 > or PMP100 or what. Now that it's all combined firmware. > > > > On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof wrote: > > Is it just me, or was this distributed differently than in the past? I > don’t remember .zip files with the release notes inside. Also when I > opened the release notes, Adobe Reader wanted to connect to a “review > server” and share my email address etc. with all other reviewers. WTF? > Did I just hit some hotkey accidentally? > > > > Also, I don’t see anything in the release notes about SM alignment tone. > Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my > brain just not working today. I thought it was 13.3 and all its progeny > were dead to me because I can’t live without oxygen, water, and alignment > tone. > > > > Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment > tone. > > > > > > *From:* Ryan Ray > > *Sent:* Thursday, July 02, 2015 4:11 PM > > *To:* af@afmug.com > > *Subject:* [AFMUG] Software 13.4 > > > > Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade > and let us know how it goes :P > > > > > > > > > > > > >
Re: [AFMUG] Software 13.4
It ain't dead yet.
On 7/2/2015 11:50 PM, That One Guy /sarcasm wrote:
I thought they were done updating fsk
On Jul 2, 2015 11:01 PM, "Matt Mangriotis"
<mailto:matt.mangrio...@cambiumnetworks.com>> wrote:
We spent a LOT of time on those George… we nailed many of them
cold in 13.4. Please let us know if you’re still seeing them
(“watchdog reset” can mean lots of things, there were a couple of
cases that we couldn’t reproduce).
Regarding the “Adobe connecting to review server” thing… ignore
it. That was likely an oversight on our part. We use that server
to allow multiple folks to review and comment on the release notes
(you know, for version control, collaboration, etc.). We were
rushing a bit to get the documentation over the finish line this
week before the holiday.
Alignment tone is there and working!
Let us know if you guys find anything else we should know about,
this one was a long time coming… but we’re proud of the finished
product. Enjoy.
Happy 4^th of July to all!
Matt
*From:*Af [mailto:af-boun...@afmug.com
<mailto:af-boun...@afmug.com>] *On Behalf Of *George Skorup
*Sent:* Thursday, July 02, 2015 9:33 PM
*To:* af@afmug.com <mailto:af@afmug.com>
*Subject:* Re: [AFMUG] Software 13.4
Hopefully the watchdog resets on 450 APs goes away. That is
getting stupid on 13.2.1. Just had another one about 10 minutes ago.
On 7/2/2015 7:50 PM, Mark Radabaugh wrote:
We have been running 13.4 build 11 for some time now. I have
not seen any major issues with it.
The 450 build works fine on the 430 AP’s.
The only thing that I know was a problem was P8 FSK radios
bricking when upgraded to build 11. I have not read the
release notes to see if the release version addresses that
problem.
Mark
On Jul 2, 2015, at 6:10 PM, Bill Prince
mailto:part15...@gmail.com>> wrote:
There is an announcement on the 430 page that the 450 load
should be used on 430s needing to connect to a 450 AP.
How is this supposed to be managed? Is there a reason to
actually load the 430 firmware on a 430 (anything)?
bp
On 7/2/2015 3:02 PM, George Skorup wrote:
I'm just about to look through the release notes. And
then GTFO here for the long weekend!
They said the alignment tone issue required a new FPGA
build. Guess they got it done for 13.4. AFAIK, this
was only on the 450, PMP100 wasn't affected. Maybe it
messed up the 430 too?
Combined firmware? You mean for 430 and 450? I guess
so. But FSK is still a separate package.
On 7/2/2015 4:53 PM, Ryan Ray wrote:
Definitely different than before. There are
mentions of the alignment tone being fixed in the
release notes but I'm not sure if it's for PMP450
or PMP100 or what. Now that it's all combined
firmware.
On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof
mailto:af...@kwisp.com>> wrote:
Is it just me, or was this distributed
differently than in the past? I don’t
remember .zip files with the release notes
inside. Also when I opened the release notes,
Adobe Reader wanted to connect to a “review
server” and share my email address etc. with
all other reviewers. WTF? Did I just hit
some hotkey accidentally?
Also, I don’t see anything in the release
notes about SM alignment tone. Didn’t this
break from 13.2.1 to 13.3? To be fixed in
13.4? Or is my brain just not working today.
I thought it was 13.3 and all its progeny were
dead to me because I can’t live without
oxygen, water, and alignment tone.
Lots of cool stuff in 13.4, like sector wide
SA, but I need my alignment tone.
*From:*Ryan Ray <mailto:ryan...@gmail.com>
*Sent:*Thursday, July 02, 2015 4:11 PM
*To:*af@afmug.com <mailto:af@afmug.com>
*Subject:*[AFMUG] Software 13.4
Who's gonna be the first guinea pig? Make sure
to do a 1000 unit upgrade and let us know how
it goes :P
Re: [AFMUG] Software 13.4
This is the last hurrah for PMP 100… Matt From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Friday, July 03, 2015 12:18 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4 It ain't dead yet. On 7/2/2015 11:50 PM, That One Guy /sarcasm wrote: I thought they were done updating fsk On Jul 2, 2015 11:01 PM, "Matt Mangriotis" mailto:matt.mangrio...@cambiumnetworks.com>> wrote: We spent a LOT of time on those George… we nailed many of them cold in 13.4. Please let us know if you’re still seeing them (“watchdog reset” can mean lots of things, there were a couple of cases that we couldn’t reproduce). Regarding the “Adobe connecting to review server” thing… ignore it. That was likely an oversight on our part. We use that server to allow multiple folks to review and comment on the release notes (you know, for version control, collaboration, etc.). We were rushing a bit to get the documentation over the finish line this week before the holiday. Alignment tone is there and working! Let us know if you guys find anything else we should know about, this one was a long time coming… but we’re proud of the finished product. Enjoy. Happy 4th of July to all! Matt From: Af [mailto:af-boun...@afmug.com<mailto:af-boun...@afmug.com>] On Behalf Of George Skorup Sent: Thursday, July 02, 2015 9:33 PM To: af@afmug.com<mailto:af@afmug.com> Subject: Re: [AFMUG] Software 13.4 Hopefully the watchdog resets on 450 APs goes away. That is getting stupid on 13.2.1. Just had another one about 10 minutes ago. On 7/2/2015 7:50 PM, Mark Radabaugh wrote: We have been running 13.4 build 11 for some time now. I have not seen any major issues with it. The 450 build works fine on the 430 AP’s. The only thing that I know was a problem was P8 FSK radios bricking when upgraded to build 11. I have not read the release notes to see if the release version addresses that problem. Mark On Jul 2, 2015, at 6:10 PM, Bill Prince mailto:part15...@gmail.com>> wrote: There is an announcement on the 430 page that the 450 load should be used on 430s needing to connect to a 450 AP. How is this supposed to be managed? Is there a reason to actually load the 430 firmware on a 430 (anything)? bp On 7/2/2015 3:02 PM, George Skorup wrote: I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof mailto:af...@kwisp.com>> wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. From: Ryan Ray<mailto:ryan...@gmail.com> Sent: Thursday, July 02, 2015 4:11 PM To: af@afmug.com<mailto:af@afmug.com> Subject: [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
Clarify this Matt… Alignment tone 430 SM to 450 AP now? Tyson Burris, President Internet Communications Inc. 739 Commerce Dr. Franklin, IN 46131 317-738-0320 Daytime # 317-412-1540 Cell/Direct # Online: www.surfici.net What can ICI do for you? Broadband Wireless - PtP/PtMP Solutions - WiMax - Mesh Wifi/Hotzones - IP Security - Fiber - Tower - Infrastructure. CONFIDENTIALITY NOTICE: This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by unauthorized organizations or individuals is strictly prohibited. From: Af [mailto:af-boun...@afmug.com] On Behalf Of Matt Mangriotis Sent: Friday, July 3, 2015 12:02 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4 We spent a LOT of time on those George… we nailed many of them cold in 13.4. Please let us know if you’re still seeing them (“watchdog reset” can mean lots of things, there were a couple of cases that we couldn’t reproduce). Regarding the “Adobe connecting to review server” thing… ignore it. That was likely an oversight on our part. We use that server to allow multiple folks to review and comment on the release notes (you know, for version control, collaboration, etc.). We were rushing a bit to get the documentation over the finish line this week before the holiday. Alignment tone is there and working! Let us know if you guys find anything else we should know about, this one was a long time coming… but we’re proud of the finished product. Enjoy. Happy 4th of July to all! Matt From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 02, 2015 9:33 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4 Hopefully the watchdog resets on 450 APs goes away. That is getting stupid on 13.2.1. Just had another one about 10 minutes ago. On 7/2/2015 7:50 PM, Mark Radabaugh wrote: We have been running 13.4 build 11 for some time now. I have not seen any major issues with it. The 450 build works fine on the 430 AP’s. The only thing that I know was a problem was P8 FSK radios bricking when upgraded to build 11. I have not read the release notes to see if the release version addresses that problem. Mark On Jul 2, 2015, at 6:10 PM, Bill Prince mailto:part15...@gmail.com> > wrote: There is an announcement on the 430 page that the 450 load should be used on 430s needing to connect to a 450 AP. How is this supposed to be managed? Is there a reason to actually load the 430 firmware on a 430 (anything)? bp On 7/2/2015 3:02 PM, George Skorup wrote: I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof mailto:af...@kwisp.com> > wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. From: Ryan Ray <mailto:ryan...@gmail.com> Sent: Thursday, July 02, 2015 4:11 PM To: af@afmug.com <mailto:af@afmug.com> Subject: [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
Can 13.4 connect to older firmware? Do we need to upgrade sm’s first before an AP? Thanks, Josh Heide Network Engineer Velociter Wireless, Inc. (209)838-1221 x108 From: Af [mailto:af-boun...@afmug.com] On Behalf Of Tyson Burris @ Internet Communications Inc Sent: Monday, July 06, 2015 1:21 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4 Clarify this Matt… Alignment tone 430 SM to 450 AP now? Tyson Burris, President Internet Communications Inc. 739 Commerce Dr. Franklin, IN 46131 317-738-0320 Daytime # 317-412-1540 Cell/Direct # Online: www.surfici.net [ICI] What can ICI do for you? Broadband Wireless - PtP/PtMP Solutions - WiMax - Mesh Wifi/Hotzones - IP Security - Fiber - Tower - Infrastructure. CONFIDENTIALITY NOTICE: This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by unauthorized organizations or individuals is strictly prohibited. From: Af [mailto:af-boun...@afmug.com] On Behalf Of Matt Mangriotis Sent: Friday, July 3, 2015 12:02 AM To: af@afmug.com<mailto:af@afmug.com> Subject: Re: [AFMUG] Software 13.4 We spent a LOT of time on those George… we nailed many of them cold in 13.4. Please let us know if you’re still seeing them (“watchdog reset” can mean lots of things, there were a couple of cases that we couldn’t reproduce). Regarding the “Adobe connecting to review server” thing… ignore it. That was likely an oversight on our part. We use that server to allow multiple folks to review and comment on the release notes (you know, for version control, collaboration, etc.). We were rushing a bit to get the documentation over the finish line this week before the holiday. Alignment tone is there and working! Let us know if you guys find anything else we should know about, this one was a long time coming… but we’re proud of the finished product. Enjoy. Happy 4th of July to all! Matt From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 02, 2015 9:33 PM To: af@afmug.com<mailto:af@afmug.com> Subject: Re: [AFMUG] Software 13.4 Hopefully the watchdog resets on 450 APs goes away. That is getting stupid on 13.2.1. Just had another one about 10 minutes ago. On 7/2/2015 7:50 PM, Mark Radabaugh wrote: We have been running 13.4 build 11 for some time now. I have not seen any major issues with it. The 450 build works fine on the 430 AP’s. The only thing that I know was a problem was P8 FSK radios bricking when upgraded to build 11. I have not read the release notes to see if the release version addresses that problem. Mark On Jul 2, 2015, at 6:10 PM, Bill Prince mailto:part15...@gmail.com>> wrote: There is an announcement on the 430 page that the 450 load should be used on 430s needing to connect to a 450 AP. How is this supposed to be managed? Is there a reason to actually load the 430 firmware on a 430 (anything)? bp On 7/2/2015 3:02 PM, George Skorup wrote: I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof mailto:af...@kwisp.com>> wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. From: Ryan Ray<mailto:ryan...@gmail.com> Sent: Thursday, July 02, 2015 4:11 PM To: af@afmug.com<mailto:af@afmug.com> Subject: [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
No. This is not in R13.4. What I meant was that Alignment Tone was completely broken (on PMP 450) in R13.3, and it is now fixed (for PMP 450 AP to PMP 450 SM). Matt From: Af [mailto:af-boun...@afmug.com] On Behalf Of Tyson Burris @ Internet Communications Inc Sent: Monday, July 06, 2015 3:21 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4 Clarify this Matt… Alignment tone 430 SM to 450 AP now? Tyson Burris, President Internet Communications Inc. 739 Commerce Dr. Franklin, IN 46131 317-738-0320 Daytime # 317-412-1540 Cell/Direct # Online: www.surfici.net [ICI] What can ICI do for you? Broadband Wireless - PtP/PtMP Solutions - WiMax - Mesh Wifi/Hotzones - IP Security - Fiber - Tower - Infrastructure. CONFIDENTIALITY NOTICE: This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by unauthorized organizations or individuals is strictly prohibited. From: Af [mailto:af-boun...@afmug.com] On Behalf Of Matt Mangriotis Sent: Friday, July 3, 2015 12:02 AM To: af@afmug.com<mailto:af@afmug.com> Subject: Re: [AFMUG] Software 13.4 We spent a LOT of time on those George… we nailed many of them cold in 13.4. Please let us know if you’re still seeing them (“watchdog reset” can mean lots of things, there were a couple of cases that we couldn’t reproduce). Regarding the “Adobe connecting to review server” thing… ignore it. That was likely an oversight on our part. We use that server to allow multiple folks to review and comment on the release notes (you know, for version control, collaboration, etc.). We were rushing a bit to get the documentation over the finish line this week before the holiday. Alignment tone is there and working! Let us know if you guys find anything else we should know about, this one was a long time coming… but we’re proud of the finished product. Enjoy. Happy 4th of July to all! Matt From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 02, 2015 9:33 PM To: af@afmug.com<mailto:af@afmug.com> Subject: Re: [AFMUG] Software 13.4 Hopefully the watchdog resets on 450 APs goes away. That is getting stupid on 13.2.1. Just had another one about 10 minutes ago. On 7/2/2015 7:50 PM, Mark Radabaugh wrote: We have been running 13.4 build 11 for some time now. I have not seen any major issues with it. The 450 build works fine on the 430 AP’s. The only thing that I know was a problem was P8 FSK radios bricking when upgraded to build 11. I have not read the release notes to see if the release version addresses that problem. Mark On Jul 2, 2015, at 6:10 PM, Bill Prince mailto:part15...@gmail.com>> wrote: There is an announcement on the 430 page that the 450 load should be used on 430s needing to connect to a 450 AP. How is this supposed to be managed? Is there a reason to actually load the 430 firmware on a 430 (anything)? bp On 7/2/2015 3:02 PM, George Skorup wrote: I'm just about to look through the release notes. And then GTFO here for the long weekend! They said the alignment tone issue required a new FPGA build. Guess they got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't affected. Maybe it messed up the 430 too? Combined firmware? You mean for 430 and 450? I guess so. But FSK is still a separate package. On 7/2/2015 4:53 PM, Ryan Ray wrote: Definitely different than before. There are mentions of the alignment tone being fixed in the release notes but I'm not sure if it's for PMP450 or PMP100 or what. Now that it's all combined firmware. On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof mailto:af...@kwisp.com>> wrote: Is it just me, or was this distributed differently than in the past? I don’t remember .zip files with the release notes inside. Also when I opened the release notes, Adobe Reader wanted to connect to a “review server” and share my email address etc. with all other reviewers. WTF? Did I just hit some hotkey accidentally? Also, I don’t see anything in the release notes about SM alignment tone. Didn’t this break from 13.2.1 to 13.3? To be fixed in 13.4? Or is my brain just not working today. I thought it was 13.3 and all its progeny were dead to me because I can’t live without oxygen, water, and alignment tone. Lots of cool stuff in 13.4, like sector wide SA, but I need my alignment tone. From: Ryan Ray<mailto:ryan...@gmail.com> Sent: Thursday, July 02, 2015 4:11 PM To: af@afmug.com<mailto:af@afmug.com> Subject: [AFMUG] Software 13.4 Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4
I just tried to use the 450 firmware on auto update on a 430 AP to upgrade the SM's. CNUT told me "No SM auto update packages available" So should I just use the 430 build or is there a workaround? On Mon, Jul 6, 2015 at 5:08 PM, Matt Mangriotis < matt.mangrio...@cambiumnetworks.com> wrote: > No. This is not in R13.4. > > > > What I meant was that Alignment Tone was completely broken (on PMP 450) in > R13.3, and it is now fixed (for PMP 450 AP to PMP 450 SM). > > > > Matt > > > > *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Tyson Burris @ > Internet Communications Inc > > *Sent:* Monday, July 06, 2015 3:21 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] Software 13.4 > > > > Clarify this Matt… > > > > Alignment tone 430 SM to 450 AP now? > > > > *Tyson Burris, President* > *Internet Communications Inc.* > *739 Commerce Dr.* > *Franklin, IN 46131* > > *317-738-0320 <317-738-0320> Daytime #* > *317-412-1540 <317-412-1540> Cell/Direct #* > *Online: **www.surfici.net* <http://www.surfici.net> > > > > [image: ICI] > > *What can ICI do for you?* > > > *Broadband Wireless - PtP/PtMP Solutions - WiMax - Mesh Wifi/Hotzones - IP > Security - Fiber - Tower - Infrastructure.* > > *CONFIDENTIALITY NOTICE: This e-mail is intended for the* > *addressee shown. It contains information that is* > *confidential and protected from disclosure. Any review,* > *dissemination or use of this transmission or its contents by* > *unauthorized organizations or individuals is strictly* > *prohibited.* > > > > *From:* Af [mailto:af-boun...@afmug.com ] *On > Behalf Of *Matt Mangriotis > *Sent:* Friday, July 3, 2015 12:02 AM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] Software 13.4 > > > > We spent a LOT of time on those George… we nailed many of them cold in > 13.4. Please let us know if you’re still seeing them (“watchdog reset” can > mean lots of things, there were a couple of cases that we couldn’t > reproduce). > > > > Regarding the “Adobe connecting to review server” thing… ignore it. That > was likely an oversight on our part. We use that server to allow multiple > folks to review and comment on the release notes (you know, for version > control, collaboration, etc.). We were rushing a bit to get the > documentation over the finish line this week before the holiday. > > > > Alignment tone is there and working! > > > > Let us know if you guys find anything else we should know about, this one > was a long time coming… but we’re proud of the finished product. Enjoy. > > > > Happy 4th of July to all! > > > > Matt > > > > *From:* Af [mailto:af-boun...@afmug.com ] *On > Behalf Of *George Skorup > *Sent:* Thursday, July 02, 2015 9:33 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] Software 13.4 > > > > Hopefully the watchdog resets on 450 APs goes away. That is getting stupid > on 13.2.1. Just had another one about 10 minutes ago. > > On 7/2/2015 7:50 PM, Mark Radabaugh wrote: > > We have been running 13.4 build 11 for some time now. I have not seen > any major issues with it. > > > > The 450 build works fine on the 430 AP’s. > > > > The only thing that I know was a problem was P8 FSK radios bricking when > upgraded to build 11. I have not read the release notes to see if the > release version addresses that problem. > > > > Mark > > > > > > On Jul 2, 2015, at 6:10 PM, Bill Prince wrote: > > > > There is an announcement on the 430 page that the 450 load should be used > on 430s needing to connect to a 450 AP. > > How is this supposed to be managed? Is there a reason to actually load the > 430 firmware on a 430 (anything)? > > bp > > > > > > On 7/2/2015 3:02 PM, George Skorup wrote: > > I'm just about to look through the release notes. And then GTFO here for > the long weekend! > > They said the alignment tone issue required a new FPGA build. Guess they > got it done for 13.4. AFAIK, this was only on the 450, PMP100 wasn't > affected. Maybe it messed up the 430 too? > > Combined firmware? You mean for 430 and 450? I guess so. But FSK is still > a separate package. > > On 7/2/2015 4:53 PM, Ryan Ray wrote: > > Definitely different than before. There are mentions of the alignment > tone being fixed in the release notes but I'm not sure if it's for PMP450 > or PMP100 or what. Now that it's all combined firmware. > > > > On Thu, Jul 2, 2015 at 2:35 PM, Ken Hohhof wrote: > > Is it just me, or was this distributed differently than in the past
Re: [AFMUG] Software 13.4
Oops, other message went to the wrong thread. It's telling you that because you don't have the 430 (OFDM AES or DES) package loaded. CNUT won't use the 450 package for auto-update on a 430 AP. I think this confusion is coming from 430 SMs on 450 APs in interop mode. Only those SMs will take the 450 image from auto-update (when they're registered on a 450 AP). On 7/7/2015 3:42 PM, Sam Lambie wrote: I just tried to use the 450 firmware on auto update on a 430 AP to upgrade the SM's. CNUT told me "No SM auto update packages available" So should I just use the 430 build or is there a workaround?
Re: [AFMUG] Software 13.4: P8 FSK not recommended
We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Bill, Can you please send us the Engineering.cgi for the P8 SM's while it is working fine in 13.3 and then again when it has problems in 13.4? Best, Jonathan Mandziara Cambium Networks, Inc. -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 09, 2015 12:54 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: > We did another couple groups of updates to 13.4 last night. On one > sector we had a couple of very low volume users on P8 FSK. Both of > them bricked. > > Well, not exactly bricked. We should have updated them to newer > hardware a long time ago, and since they were not heavy users, it > really was not a priority item. > > So we swapped them out today, and brought them back to the shop. Turns > out you could bring them back to life if you default them. Cool I > thought. However, as soon as you apply a "real" configuration, they > revert to brick mode. No ethernet, no life. You can re-reset them and > bring them back. So I defaulted one, and downgraded to 13.1.3, and all > is well, or as well as a P8 can be. > > Not real valuable, but if you have some old P8 FSK still running > anywhere, I do not recommend you try 13.4 on them. > > bp > > > On 7/2/2015 2:11 PM, Ryan Ray wrote: >> Who's gonna be the first guinea pig? Make sure to do a 1000 unit >> upgrade and let us know how it goes :P >> >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
I wasn't the one investigating the P8's that came back. It's possible Matt just started with a default plug with the ones he was looking at so it's entirely possible. Mark On 7/9/15 11:51 AM, Bill Prince wrote: I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
What I did with what appeared to be a bricked radio was just insert the default plug. The unit then came back to life. Once I was able to access the device, I pushed the "Reset to factory defaults" button, saved the configuration, pulled the default plug, and rebooted. At that point I could still access the unit. I then applied the configuration and rebooted. It did not come back; no ethernet, no RF. I did re-reset it, and it came back again. bp On 7/9/2015 9:04 AM, Mark Radabaugh wrote: I wasn't the one investigating the P8's that came back. It's possible Matt just started with a default plug with the ones he was looking at so it's entirely possible. Mark On 7/9/15 11:51 AM, Bill Prince wrote: I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
I assume you're talking about uploading and applying a config file? Maybe there's something in it that's incompatible with the P8? So now we wait for 13.4.1.. ducking :o On 7/9/2015 11:32 AM, Bill Prince wrote: What I did with what appeared to be a bricked radio was just insert the default plug. The unit then came back to life. Once I was able to access the device, I pushed the "Reset to factory defaults" button, saved the configuration, pulled the default plug, and rebooted. At that point I could still access the unit. I then applied the configuration and rebooted. It did not come back; no ethernet, no RF. I did re-reset it, and it came back again. bp On 7/9/2015 9:04 AM, Mark Radabaugh wrote: I wasn't the one investigating the P8's that came back. It's possible Matt just started with a default plug with the ones he was looking at so it's entirely possible. Mark On 7/9/15 11:51 AM, Bill Prince wrote: I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Actually no. I just made some basic changes. Set color code, turn on NAT, remove the admin user, set bandwidth shaping. It didn't like something. Just not sure what, because once I changed it, it was opaque. bp On 7/9/2015 4:03 PM, George Skorup wrote: I assume you're talking about uploading and applying a config file? Maybe there's something in it that's incompatible with the P8? So now we wait for 13.4.1.. ducking :o On 7/9/2015 11:32 AM, Bill Prince wrote: What I did with what appeared to be a bricked radio was just insert the default plug. The unit then came back to life. Once I was able to access the device, I pushed the "Reset to factory defaults" button, saved the configuration, pulled the default plug, and rebooted. At that point I could still access the unit. I then applied the configuration and rebooted. It did not come back; no ethernet, no RF. I did re-reset it, and it came back again. bp On 7/9/2015 9:04 AM, Mark Radabaugh wrote: I wasn't the one investigating the P8's that came back. It's possible Matt just started with a default plug with the ones he was looking at so it's entirely possible. Mark On 7/9/15 11:51 AM, Bill Prince wrote: I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Well that's lame. I have a couple P8s. I'll pull one out tomorrow if I have time and update it and see if I get the same thing. On 7/9/2015 6:05 PM, Bill Prince wrote: Actually no. I just made some basic changes. Set color code, turn on NAT, remove the admin user, set bandwidth shaping. It didn't like something. Just not sure what, because once I changed it, it was opaque. bp On 7/9/2015 4:03 PM, George Skorup wrote: I assume you're talking about uploading and applying a config file? Maybe there's something in it that's incompatible with the P8? So now we wait for 13.4.1.. ducking :o On 7/9/2015 11:32 AM, Bill Prince wrote: What I did with what appeared to be a bricked radio was just insert the default plug. The unit then came back to life. Once I was able to access the device, I pushed the "Reset to factory defaults" button, saved the configuration, pulled the default plug, and rebooted. At that point I could still access the unit. I then applied the configuration and rebooted. It did not come back; no ethernet, no RF. I did re-reset it, and it came back again. bp On 7/9/2015 9:04 AM, Mark Radabaugh wrote: I wasn't the one investigating the P8's that came back. It's possible Matt just started with a default plug with the ones he was looking at so it's entirely possible. Mark On 7/9/15 11:51 AM, Bill Prince wrote: I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
So.. I remember why I had this one P8 radio in the WTF pile. It's a 5700BH20. At some point, a long, long time ago, it decided to turn itself into an Advantage SM. Anyway, I finally got through getting the stupid thing and CNUT to make it H/W scheduled. Then I tried to go from 7.3.6 to 13.4. Didn't happen, filesystem out of space. Had to go 10.5 > 11.2 > 12.1 then 13.4 worked. I factory defaulted it. Then put some basic config on it. Set a color code, deleted root, set admin account password. Really nothing more than that. Reboot, comes up fine. Now enable NAT and reboot. It's not scanning. The power, sync, session and GPS LEDs are all solid. Ethernet LEDs are off and can't ping it. Default plug it, factory default, boots fine. This time all I did was enable NAT and it will not boot again. NAT on P8 be broke. I'm glad you stumbled on this, Bill. Those few P8 SMs I have on the network have NAT enabled, so those would be screwed like yours. Guess I can't update that AP. WTF. On 7/9/2015 6:21 PM, George Skorup wrote: Well that's lame. I have a couple P8s. I'll pull one out tomorrow if I have time and update it and see if I get the same thing. On 7/9/2015 6:05 PM, Bill Prince wrote: Actually no. I just made some basic changes. Set color code, turn on NAT, remove the admin user, set bandwidth shaping. It didn't like something. Just not sure what, because once I changed it, it was opaque. bp On 7/9/2015 4:03 PM, George Skorup wrote: I assume you're talking about uploading and applying a config file? Maybe there's something in it that's incompatible with the P8? So now we wait for 13.4.1.. ducking :o On 7/9/2015 11:32 AM, Bill Prince wrote: What I did with what appeared to be a bricked radio was just insert the default plug. The unit then came back to life. Once I was able to access the device, I pushed the "Reset to factory defaults" button, saved the configuration, pulled the default plug, and rebooted. At that point I could still access the unit. I then applied the configuration and rebooted. It did not come back; no ethernet, no RF. I did re-reset it, and it came back again. bp On 7/9/2015 9:04 AM, Mark Radabaugh wrote: I wasn't the one investigating the P8's that came back. It's possible Matt just started with a default plug with the ones he was looking at so it's entirely possible. Mark On 7/9/15 11:51 AM, Bill Prince wrote: I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Not an issue for us any more. No more P8s. Guess that's not a bad thing... bp On 7/10/2015 4:23 PM, George Skorup wrote: So.. I remember why I had this one P8 radio in the WTF pile. It's a 5700BH20. At some point, a long, long time ago, it decided to turn itself into an Advantage SM. Anyway, I finally got through getting the stupid thing and CNUT to make it H/W scheduled. Then I tried to go from 7.3.6 to 13.4. Didn't happen, filesystem out of space. Had to go 10.5 > 11.2 > 12.1 then 13.4 worked. I factory defaulted it. Then put some basic config on it. Set a color code, deleted root, set admin account password. Really nothing more than that. Reboot, comes up fine. Now enable NAT and reboot. It's not scanning. The power, sync, session and GPS LEDs are all solid. Ethernet LEDs are off and can't ping it. Default plug it, factory default, boots fine. This time all I did was enable NAT and it will not boot again. NAT on P8 be broke. I'm glad you stumbled on this, Bill. Those few P8 SMs I have on the network have NAT enabled, so those would be screwed like yours. Guess I can't update that AP. WTF. On 7/9/2015 6:21 PM, George Skorup wrote: Well that's lame. I have a couple P8s. I'll pull one out tomorrow if I have time and update it and see if I get the same thing. On 7/9/2015 6:05 PM, Bill Prince wrote: Actually no. I just made some basic changes. Set color code, turn on NAT, remove the admin user, set bandwidth shaping. It didn't like something. Just not sure what, because once I changed it, it was opaque. bp On 7/9/2015 4:03 PM, George Skorup wrote: I assume you're talking about uploading and applying a config file? Maybe there's something in it that's incompatible with the P8? So now we wait for 13.4.1.. ducking :o On 7/9/2015 11:32 AM, Bill Prince wrote: What I did with what appeared to be a bricked radio was just insert the default plug. The unit then came back to life. Once I was able to access the device, I pushed the "Reset to factory defaults" button, saved the configuration, pulled the default plug, and rebooted. At that point I could still access the unit. I then applied the configuration and rebooted. It did not come back; no ethernet, no RF. I did re-reset it, and it came back again. bp On 7/9/2015 9:04 AM, Mark Radabaugh wrote: I wasn't the one investigating the P8's that came back. It's possible Matt just started with a default plug with the ones he was looking at so it's entirely possible. Mark On 7/9/15 11:51 AM, Bill Prince wrote: I didn't look at the frequency checklist. However, after I apply the configuration, the ethernet link goes completely off (as if it were turned off). So it's impossible to get any data as to what is actually happening inside. No ethernet link, no RF link. Once it's defaulted, it appears "normal". I did not try to selectively apply "parts" of the configuration. That would be an adventure bp On 7/9/2015 8:44 AM, Mark Radabaugh wrote: It appears the update to 13.4 clears all of the frequencies in a P8 radio which makes it not associate. Reselect the frequencies and they are fine. Obviously not good for your truck roll schedule. Mark On 7/9/15 1:53 AM, George Skorup wrote: Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi Bill Is 13.4 GA? Any issues other than FSK? Thanks Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince Sent: Wednesday, July 08, 2015 8:06 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: > Who's gonna be the first guinea pig? Make sure to do a 1000 unit > upgrade and let us know how it goes :P >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
13.4 is released. Other than the P8 thing Bill mentioned (and I confirmed on the bench), haven't seen any issues yet. I have a very small number of APs and SMs update so far though. On 7/13/2015 6:20 PM, SmarterBroadband wrote: Hi Bill Is 13.4 GA? Any issues other than FSK? Thanks Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince Sent: Wednesday, July 08, 2015 8:06 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Doing my network tonight. Had been planning for 13.2.1. Just saw this on 13.4? Most of my network is on 12.1. Do I need to go to an interim release or can I safely jump to 13.2.1 (or even 13.4). Not sure I am willing to risk 13.4 tonight. Maybe wait a month. Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Monday, July 13, 2015 4:30 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 13.4 is released. Other than the P8 thing Bill mentioned (and I confirmed on the bench), haven't seen any issues yet. I have a very small number of APs and SMs update so far though. On 7/13/2015 6:20 PM, SmarterBroadband wrote: > Hi Bill > > Is 13.4 GA? Any issues other than FSK? > > Thanks > > Adam > > -Original Message- > From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince > Sent: Wednesday, July 08, 2015 8:06 PM > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > We did another couple groups of updates to 13.4 last night. On one sector we > had a couple of very low volume users on P8 FSK. Both of them bricked. > > Well, not exactly bricked. We should have updated them to newer hardware a > long time ago, and since they were not heavy users, it really was not a > priority item. > > So we swapped them out today, and brought them back to the shop. Turns out > you could bring them back to life if you default them. Cool I thought. > However, as soon as you apply a "real" configuration, they revert to brick > mode. No ethernet, no life. You can re-reset them and bring them back. So I > defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 > can be. > > Not real valuable, but if you have some old P8 FSK still running anywhere, I > do not recommend you try 13.4 on them. > > bp > > > On 7/2/2015 2:11 PM, Ryan Ray wrote: >> Who's gonna be the first guinea pig? Make sure to do a 1000 unit >> upgrade and let us know how it goes :P >>
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Probably shouldn't have any issues going straight to 13.4. But Cambium will tell you it's untested and unsupported. Some issues to watch out for: uncalibrated 450 APs and SMs (since you're coming from 12.1); 450 APs on 2.5MHz center frequencies, SMs may get 2.5 centers deselected in the scan list. Although, I think 2.5MHz centers didn't come until 12.2? Man, it's been so long and so much changing that it's hard to remember everything that could give you a horrible morning after a system-wide update. For FSK though, shouldn't be much to break. Well, besides this P8 NAT issue. On 7/13/2015 7:04 PM, SmarterBroadband wrote: Doing my network tonight. Had been planning for 13.2.1. Just saw this on 13.4? Most of my network is on 12.1. Do I need to go to an interim release or can I safely jump to 13.2.1 (or even 13.4). Not sure I am willing to risk 13.4 tonight. Maybe wait a month. Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Monday, July 13, 2015 4:30 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 13.4 is released. Other than the P8 thing Bill mentioned (and I confirmed on the bench), haven't seen any issues yet. I have a very small number of APs and SMs update so far though. On 7/13/2015 6:20 PM, SmarterBroadband wrote: Hi Bill Is 13.4 GA? Any issues other than FSK? Thanks Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince Sent: Wednesday, July 08, 2015 8:06 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
You can generally go from one major release to the next without having to go to the point releases in between. So if you are on 12.1, or 12.2, or 12.3, etc. Then you should be able to go to 13.x (e.g 13.1.2 or 13.2 or 13.4). But try it on the bench first if you have any doubts. bp On 7/13/2015 5:04 PM, SmarterBroadband wrote: Doing my network tonight. Had been planning for 13.2.1. Just saw this on 13.4? Most of my network is on 12.1. Do I need to go to an interim release or can I safely jump to 13.2.1 (or even 13.4). Not sure I am willing to risk 13.4 tonight. Maybe wait a month. Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Monday, July 13, 2015 4:30 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 13.4 is released. Other than the P8 thing Bill mentioned (and I confirmed on the bench), haven't seen any issues yet. I have a very small number of APs and SMs update so far though. On 7/13/2015 6:20 PM, SmarterBroadband wrote: Hi Bill Is 13.4 GA? Any issues other than FSK? Thanks Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince Sent: Wednesday, July 08, 2015 8:06 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
I would say you really, really need to take your 450 stuff to at least 13.2. I didn't go beyond that because of the alignment tone screwup. Which I think is fixed in 13.4, so I will start cautiously going there. But while I don't remember the exact issues or sequence of events, I know 13.2 fixed some serious performance/stability issues we were having. George probably remembers better than I do. -Original Message- From: SmarterBroadband Sent: Monday, July 13, 2015 7:04 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Doing my network tonight. Had been planning for 13.2.1. Just saw this on 13.4? Most of my network is on 12.1. Do I need to go to an interim release or can I safely jump to 13.2.1 (or even 13.4). Not sure I am willing to risk 13.4 tonight. Maybe wait a month. Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Monday, July 13, 2015 4:30 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 13.4 is released. Other than the P8 thing Bill mentioned (and I confirmed on the bench), haven't seen any issues yet. I have a very small number of APs and SMs update so far though. On 7/13/2015 6:20 PM, SmarterBroadband wrote: Hi Bill Is 13.4 GA? Any issues other than FSK? Thanks Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince Sent: Wednesday, July 08, 2015 8:06 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Yes, you get MIMO-A and improved automatic rate adapt. Compared to 12.x anyway. 12.1 is really old, I'm surprised anyone has held out so long. Most of the 12.x issues were resolved in the final 12.2.2 release. So if I wanted to stay in the stone age, that's where I'd be. No offense. :) I'm still waiting for the AutoSync bugs to be fixed. Matt is on vacation (must be nice to get vacations) and Aaron went MIA from the list months ago. They did have him and his team locked in a room though. I heard they pushed food under the door sometimes. :) On 7/13/2015 9:29 PM, Ken Hohhof wrote: I would say you really, really need to take your 450 stuff to at least 13.2. I didn't go beyond that because of the alignment tone screwup. Which I think is fixed in 13.4, so I will start cautiously going there. But while I don't remember the exact issues or sequence of events, I know 13.2 fixed some serious performance/stability issues we were having. George probably remembers better than I do. -Original Message- From: SmarterBroadband Sent: Monday, July 13, 2015 7:04 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Doing my network tonight. Had been planning for 13.2.1. Just saw this on 13.4? Most of my network is on 12.1. Do I need to go to an interim release or can I safely jump to 13.2.1 (or even 13.4). Not sure I am willing to risk 13.4 tonight. Maybe wait a month. Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Monday, July 13, 2015 4:30 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 13.4 is released. Other than the P8 thing Bill mentioned (and I confirmed on the bench), haven't seen any issues yet. I have a very small number of APs and SMs update so far though. On 7/13/2015 6:20 PM, SmarterBroadband wrote: Hi Bill Is 13.4 GA? Any issues other than FSK? Thanks Adam -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince Sent: Wednesday, July 08, 2015 8:06 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi George, I suppose by AutoSync bug you meant Sync not coming back to power port when the config is Power Port+Free Run. If yes, then we have fixed the issue in 13.4 Official Release. Please give it a try. Thanks, Chitrang Srivastava Cambium Networks -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: 14 July 2015 08:33 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Yes, you get MIMO-A and improved automatic rate adapt. Compared to 12.x anyway. 12.1 is really old, I'm surprised anyone has held out so long. Most of the 12.x issues were resolved in the final 12.2.2 release. So if I wanted to stay in the stone age, that's where I'd be. No offense. :) I'm still waiting for the AutoSync bugs to be fixed. Matt is on vacation (must be nice to get vacations) and Aaron went MIA from the list months ago. They did have him and his team locked in a room though. I heard they pushed food under the door sometimes. :) On 7/13/2015 9:29 PM, Ken Hohhof wrote: > I would say you really, really need to take your 450 stuff to at least > 13.2. I didn't go beyond that because of the alignment tone screwup. > Which I think is fixed in 13.4, so I will start cautiously going > there. But while I don't remember the exact issues or sequence of > events, I know 13.2 fixed some serious performance/stability issues we > were having. George probably remembers better than I do. > > > -Original Message- From: SmarterBroadband > Sent: Monday, July 13, 2015 7:04 PM > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > Doing my network tonight. Had been planning for 13.2.1. Just saw > this on 13.4? Most of my network is on 12.1. Do I need to go to an > interim release or can I safely jump to 13.2.1 (or even 13.4). > > Not sure I am willing to risk 13.4 tonight. Maybe wait a month. > > Adam > > -Original Message- > From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup > Sent: Monday, July 13, 2015 4:30 PM > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > 13.4 is released. Other than the P8 thing Bill mentioned (and I > confirmed on the bench), haven't seen any issues yet. I have a very > small number of APs and SMs update so far though. > > On 7/13/2015 6:20 PM, SmarterBroadband wrote: >> Hi Bill >> >> Is 13.4 GA? Any issues other than FSK? >> >> Thanks >> >> Adam >> >> -----Original Message- >> From: Af [mailto:af-boun...@afmug.com] On Behalf Of Bill Prince >> Sent: Wednesday, July 08, 2015 8:06 PM >> To: af@afmug.com >> Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended >> >> We did another couple groups of updates to 13.4 last night. On one >> sector we had a couple of very low volume users on P8 FSK. Both of >> them bricked. >> >> Well, not exactly bricked. We should have updated them to newer >> hardware a long time ago, and since they were not heavy users, it >> really was not a priority item. >> >> So we swapped them out today, and brought them back to the shop. >> Turns out you could bring them back to life if you default them. Cool >> I thought. However, as soon as you apply a "real" configuration, they >> revert to brick mode. No ethernet, no life. You can re-reset them and >> bring them back. So I defaulted one, and downgraded to 13.1.3, and >> all is well, or as well as a P8 can be. >> >> Not real valuable, but if you have some old P8 FSK still running >> anywhere, I do not recommend you try 13.4 on them. >> >> bp >> >> >> On 7/2/2015 2:11 PM, Ryan Ray wrote: >>> Who's gonna be the first guinea pig? Make sure to do a 1000 unit >>> upgrade and let us know how it goes :P >>> > >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Yes, getting stuck in FreeRun is one of the issues. The other is AutoSync selecting the on-board GPS at boot if it has a lock when the radio is soft rebooted. There are more related issues. Sessions drop when AutoSync changes sources which is supposed to be hit-less. And some other weird problems. One I've seen somewhat often, although only on a small number of APs, is all sources say no sync, yet the AP is sitting there saying it's receiving sync from a source which says has no sync pulse! Or the timing port pulse going from receiving sync to no sync every second or two until the AP is rebooted. Like I've said for quite a while, these issues seem much more prevalent on the 3GHz 450, and I have no idea why that is, but something is different, like perhaps LBT is in the mix. And most of this happens more often in the winter. Oh god, I said winter. No!! I will load up 13.4 on some more sectors and see what happens I guess. On 7/13/2015 11:19 PM, Chitrang Srivastava wrote: Hi George, I suppose by AutoSync bug you meant Sync not coming back to power port when the config is Power Port+Free Run. If yes, then we have fixed the issue in 13.4 Official Release. Please give it a try. Thanks, Chitrang Srivastava Cambium Networks
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Winter. Is that the season without storms? Starting to sound good. -Original Message- From: George Skorup Sent: Monday, July 13, 2015 11:53 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Yes, getting stuck in FreeRun is one of the issues. The other is AutoSync selecting the on-board GPS at boot if it has a lock when the radio is soft rebooted. There are more related issues. Sessions drop when AutoSync changes sources which is supposed to be hit-less. And some other weird problems. One I've seen somewhat often, although only on a small number of APs, is all sources say no sync, yet the AP is sitting there saying it's receiving sync from a source which says has no sync pulse! Or the timing port pulse going from receiving sync to no sync every second or two until the AP is rebooted. Like I've said for quite a while, these issues seem much more prevalent on the 3GHz 450, and I have no idea why that is, but something is different, like perhaps LBT is in the mix. And most of this happens more often in the winter. Oh god, I said winter. No!! I will load up 13.4 on some more sectors and see what happens I guess. On 7/13/2015 11:19 PM, Chitrang Srivastava wrote: Hi George, I suppose by AutoSync bug you meant Sync not coming back to power port when the config is Power Port+Free Run. If yes, then we have fixed the issue in 13.4 Official Release. Please give it a try. Thanks, Chitrang Srivastava Cambium Networks
Re: [AFMUG] Software 13.4: P8 FSK not recommended
What's this season without storms you speak of? You mean like tornadoes in November? Or a tower getting hit by lightning in thundersnow? On 7/14/2015 5:10 AM, Ken Hohhof wrote: Winter. Is that the season without storms? Starting to sound good. -Original Message- From: George Skorup Sent: Monday, July 13, 2015 11:53 PM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Yes, getting stuck in FreeRun is one of the issues. The other is AutoSync selecting the on-board GPS at boot if it has a lock when the radio is soft rebooted. There are more related issues. Sessions drop when AutoSync changes sources which is supposed to be hit-less. And some other weird problems. One I've seen somewhat often, although only on a small number of APs, is all sources say no sync, yet the AP is sitting there saying it's receiving sync from a source which says has no sync pulse! Or the timing port pulse going from receiving sync to no sync every second or two until the AP is rebooted. Like I've said for quite a while, these issues seem much more prevalent on the 3GHz 450, and I have no idea why that is, but something is different, like perhaps LBT is in the mix. And most of this happens more often in the winter. Oh god, I said winter. No!! I will load up 13.4 on some more sectors and see what happens I guess. On 7/13/2015 11:19 PM, Chitrang Srivastava wrote: Hi George, I suppose by AutoSync bug you meant Sync not coming back to power port when the config is Power Port+Free Run. If yes, then we have fixed the issue in 13.4 Official Release. Please give it a try. Thanks, Chitrang Srivastava Cambium Networks
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Bill, Can you please send us the Engineering.cgi file to: soluti...@cambiumnetworks.com Best, Jonathan Mandziara Cambium Networks, Inc. -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Jonathan Mandziara Sent: Thursday, July 09, 2015 7:47 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Bill, Can you please send us the Engineering.cgi for the P8 SM's while it is working fine in 13.3 and then again when it has problems in 13.4? Best, Jonathan Mandziara Cambium Networks, Inc. -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 09, 2015 12:54 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: > We did another couple groups of updates to 13.4 last night. On one > sector we had a couple of very low volume users on P8 FSK. Both of > them bricked. > > Well, not exactly bricked. We should have updated them to newer > hardware a long time ago, and since they were not heavy users, it > really was not a priority item. > > So we swapped them out today, and brought them back to the shop. Turns > out you could bring them back to life if you default them. Cool I > thought. However, as soon as you apply a "real" configuration, they > revert to brick mode. No ethernet, no life. You can re-reset them and > bring them back. So I defaulted one, and downgraded to 13.1.3, and all > is well, or as well as a P8 can be. > > Not real valuable, but if you have some old P8 FSK still running > anywhere, I do not recommend you try 13.4 on them. > > bp > > > On 7/2/2015 2:11 PM, Ryan Ray wrote: >> Who's gonna be the first guinea pig? Make sure to do a 1000 unit >> upgrade and let us know how it goes :P >> >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
I can send you one after the reset, but after we apply the configuration, the SM won't boot at all, so it's impossible to catch this after the fact. George has isolated the issue to turning on NAT, so that is about the best we can do. Maybe I should just send you one of the P8 SMs? You pay shipping. ;-) bp On 7/14/2015 10:13 AM, Jonathan Mandziara wrote: Bill, Can you please send us the Engineering.cgi file to: soluti...@cambiumnetworks.com Best, Jonathan Mandziara Cambium Networks, Inc. -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Jonathan Mandziara Sent: Thursday, July 09, 2015 7:47 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Bill, Can you please send us the Engineering.cgi for the P8 SM's while it is working fine in 13.3 and then again when it has problems in 13.4? Best, Jonathan Mandziara Cambium Networks, Inc. -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 09, 2015 12:54 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
It would be scary if they didn't have any P8s laying around to test with. Next question... I wonder if this affects P9 boards as well? That would suck. Not sure if I have one around the office to test. On 7/14/2015 12:19 PM, Bill Prince wrote: I can send you one after the reset, but after we apply the configuration, the SM won't boot at all, so it's impossible to catch this after the fact. George has isolated the issue to turning on NAT, so that is about the best we can do. Maybe I should just send you one of the P8 SMs? You pay shipping. ;-) bp On 7/14/2015 10:13 AM, Jonathan Mandziara wrote: Bill, Can you please send us the Engineering.cgi file to: soluti...@cambiumnetworks.com Best, Jonathan Mandziara Cambium Networks, Inc. -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of Jonathan Mandziara Sent: Thursday, July 09, 2015 7:47 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Bill, Can you please send us the Engineering.cgi for the P8 SM's while it is working fine in 13.3 and then again when it has problems in 13.4? Best, Jonathan Mandziara Cambium Networks, Inc. -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: Thursday, July 09, 2015 12:54 AM To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Well thanks for being the guinea pig Bill. I have a sector with a couple P8 SMs. Awesome. I haven't started updating anything to 13.4 yet though. Sure will be fun getting the P9s on that AP to update since P7, P8 and P9 is a one-shot deal. On 7/8/2015 10:06 PM, Bill Prince wrote: We did another couple groups of updates to 13.4 last night. On one sector we had a couple of very low volume users on P8 FSK. Both of them bricked. Well, not exactly bricked. We should have updated them to newer hardware a long time ago, and since they were not heavy users, it really was not a priority item. So we swapped them out today, and brought them back to the shop. Turns out you could bring them back to life if you default them. Cool I thought. However, as soon as you apply a "real" configuration, they revert to brick mode. No ethernet, no life. You can re-reset them and bring them back. So I defaulted one, and downgraded to 13.1.3, and all is well, or as well as a P8 can be. Not real valuable, but if you have some old P8 FSK still running anywhere, I do not recommend you try 13.4 on them. bp On 7/2/2015 2:11 PM, Ryan Ray wrote: Who's gonna be the first guinea pig? Make sure to do a 1000 unit upgrade and let us know how it goes :P
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with them. Have also loaded 13.4 on PMP430 and PMP450. bp On 7/14/2015 4:59 PM, George Skorup wrote: I wonder if this affects P9 boards as well? That would suck. Not sure if I have one around the office to test.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi Bill, In order to investigate P8 issue, please do following, AFTER upgrade to P8 and applying configuration changes but BEFORE doing reboot, take out engineering.cgi. Please also send configuration file as well from Configuration - > Unit Setting. Does without NAT P8 is accessible? If the above steps didn't work ( actually they should because most of our configuration changes applies on next reboot) they please send screen shot of NAT configuration page before you press Save Changes. Thanks, Chitrang Srivastava Cambium Networks From: Af on behalf of Bill Prince Sent: 15 July 2015 05:35:23 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with them. Have also loaded 13.4 on PMP430 and PMP450. bp On 7/14/2015 4:59 PM, George Skorup wrote: > I wonder if this affects P9 boards as well? That would suck. Not sure > if I have one around the office to test.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi George, Did you get chance to check Gps sync issue with 13.4 Build? From: Af on behalf of George Skorup Sent: 14 July 2015 10:23:46 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Yes, getting stuck in FreeRun is one of the issues. The other is AutoSync selecting the on-board GPS at boot if it has a lock when the radio is soft rebooted. There are more related issues. Sessions drop when AutoSync changes sources which is supposed to be hit-less. And some other weird problems. One I've seen somewhat often, although only on a small number of APs, is all sources say no sync, yet the AP is sitting there saying it's receiving sync from a source which says has no sync pulse! Or the timing port pulse going from receiving sync to no sync every second or two until the AP is rebooted. Like I've said for quite a while, these issues seem much more prevalent on the 3GHz 450, and I have no idea why that is, but something is different, like perhaps LBT is in the mix. And most of this happens more often in the winter. Oh god, I said winter. No!! I will load up 13.4 on some more sectors and see what happens I guess. On 7/13/2015 11:19 PM, Chitrang Srivastava wrote: > Hi George, > > I suppose by AutoSync bug you meant Sync not coming back to power port when > the config is Power Port+Free Run. > If yes, then we have fixed the issue in 13.4 Official Release. Please give it > a try. > > Thanks, > Chitrang Srivastava > Cambium Networks
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi Bill, Please reduce the NAT table size from Configuration - >NAT, to 1024 and try it out. Thanks, Chitrang Srivastava Cambium Networks From: Chitrang Srivastava Sent: 15 July 2015 07:38:49 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Hi Bill, In order to investigate P8 issue, please do following, AFTER upgrade to P8 and applying configuration changes but BEFORE doing reboot, take out engineering.cgi. Please also send configuration file as well from Configuration - > Unit Setting. Does without NAT P8 is accessible? If the above steps didn't work ( actually they should because most of our configuration changes applies on next reboot) they please send screen shot of NAT configuration page before you press Save Changes. Thanks, Chitrang Srivastava Cambium Networks From: Af on behalf of Bill Prince Sent: 15 July 2015 05:35:23 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with them. Have also loaded 13.4 on PMP430 and PMP450. bp On 7/14/2015 4:59 PM, George Skorup wrote: > I wonder if this affects P9 boards as well? That would suck. Not sure > if I have one around the office to test.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
That fixes it. If the subscriber uses a router, and it is on the DMZ, then that could work (you get zero entries in the NAT table). However, if they are bridging through to the SM, then it probably won't be useable. A couple of Macs bridged will eat >1024 connections in no time. A lot of Apple software has the nasty habit of never closing a connection, so the NAT table fills up in no time. bp On 7/15/2015 7:04 PM, Chitrang Srivastava wrote: Hi Bill, Please reduce the NAT table size from Configuration - >NAT, to 1024 and try it out. Thanks, Chitrang Srivastava Cambium Networks From: Chitrang Srivastava Sent: 15 July 2015 07:38:49 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Hi Bill, In order to investigate P8 issue, please do following, AFTER upgrade to P8 and applying configuration changes but BEFORE doing reboot, take out engineering.cgi. Please also send configuration file as well from Configuration - > Unit Setting. Does without NAT P8 is accessible? If the above steps didn't work ( actually they should because most of our configuration changes applies on next reboot) they please send screen shot of NAT configuration page before you press Save Changes. Thanks, Chitrang Srivastava Cambium Networks From: Af on behalf of Bill Prince Sent: 15 July 2015 05:35:23 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with them. Have also loaded 13.4 on PMP430 and PMP450. bp On 7/14/2015 4:59 PM, George Skorup wrote: I wonder if this affects P9 boards as well? That would suck. Not sure if I have one around the office to test.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
We will work some acceptable solution. Because lots of new features get added in 13.4(refer Release Notes) hence the code size get increased and we ran short of DRAM. Thanks, Chitrang Srivastava Cambium Networks From: Bill Prince Sent: 16 July 2015 22:19:52 To: af@afmug.com; Chitrang Srivastava; Jonathan Mandziara Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended That fixes it. If the subscriber uses a router, and it is on the DMZ, then that could work (you get zero entries in the NAT table). However, if they are bridging through to the SM, then it probably won't be useable. A couple of Macs bridged will eat >1024 connections in no time. A lot of Apple software has the nasty habit of never closing a connection, so the NAT table fills up in no time. bp On 7/15/2015 7:04 PM, Chitrang Srivastava wrote: > Hi Bill, > > Please reduce the NAT table size from Configuration - >NAT, to 1024 and try > it out. > > Thanks, > Chitrang Srivastava > Cambium Networks > > > From: Chitrang Srivastava > Sent: 15 July 2015 07:38:49 > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > Hi Bill, > > In order to investigate P8 issue, please do following, > > AFTER upgrade to P8 and applying configuration changes but BEFORE doing > reboot, take out engineering.cgi. > Please also send configuration file as well from Configuration - > Unit > Setting. > > Does without NAT P8 is accessible? > If the above steps didn't work ( actually they should because most of our > configuration changes applies on next reboot) they please send screen shot > of NAT configuration page before you press Save Changes. > > Thanks, > Chitrang Srivastava > Cambium Networks > > ________ > From: Af on behalf of Bill Prince > Sent: 15 July 2015 05:35:23 > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with > them. > > Have also loaded 13.4 on PMP430 and PMP450. > > bp > > > On 7/14/2015 4:59 PM, George Skorup wrote: >> I wonder if this affects P9 boards as well? That would suck. Not sure >> if I have one around the office to test.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
I don't know how hard it would be to limit the bridge table to 1 entry, but that would solve the basic problem, and why we end up using NAT (for the most part). It would also help on a P8 simply because of the limited resources. Would not be a bad thing for most of the other Canopy SMs either (regardless of hardware version). It's been something that many of us have been asking for for some time. bp On 7/16/2015 10:16 AM, Chitrang Srivastava wrote: We will work some acceptable solution. Because lots of new features get added in 13.4(refer Release Notes) hence the code size get increased and we ran short of DRAM. Thanks, Chitrang Srivastava Cambium Networks From: Bill Prince Sent: 16 July 2015 22:19:52 To: af@afmug.com; Chitrang Srivastava; Jonathan Mandziara Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended That fixes it. If the subscriber uses a router, and it is on the DMZ, then that could work (you get zero entries in the NAT table). However, if they are bridging through to the SM, then it probably won't be useable. A couple of Macs bridged will eat >1024 connections in no time. A lot of Apple software has the nasty habit of never closing a connection, so the NAT table fills up in no time. bp On 7/15/2015 7:04 PM, Chitrang Srivastava wrote: Hi Bill, Please reduce the NAT table size from Configuration - >NAT, to 1024 and try it out. Thanks, Chitrang Srivastava Cambium Networks From: Chitrang Srivastava Sent: 15 July 2015 07:38:49 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Hi Bill, In order to investigate P8 issue, please do following, AFTER upgrade to P8 and applying configuration changes but BEFORE doing reboot, take out engineering.cgi. Please also send configuration file as well from Configuration - > Unit Setting. Does without NAT P8 is accessible? If the above steps didn't work ( actually they should because most of our configuration changes applies on next reboot) they please send screen shot of NAT configuration page before you press Save Changes. Thanks, Chitrang Srivastava Cambium Networks From: Af on behalf of Bill Prince Sent: 15 July 2015 05:35:23 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with them. Have also loaded 13.4 on PMP430 and PMP450. bp On 7/14/2015 4:59 PM, George Skorup wrote: I wonder if this affects P9 boards as well? That would suck. Not sure if I have one around the office to test.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Chitrang - where do you want the bricks? Just for you we pulled the engineering.cgi from a 12.2 and a 13.1.3 P8 FSK radio and then bricked them both with 13.4 and gave the customers new radios. Where do you want the dead radios and the dump files sent? You can keep the P8’s and add them to your regression testing lab. Mark > On Jul 14, 2015, at 10:08 PM, Chitrang Srivastava > wrote: > > Hi Bill, > > In order to investigate P8 issue, please do following, > > AFTER upgrade to P8 and applying configuration changes but BEFORE doing > reboot, take out engineering.cgi. > Please also send configuration file as well from Configuration - > Unit > Setting. > > Does without NAT P8 is accessible? > If the above steps didn't work ( actually they should because most of our > configuration changes applies on next reboot) they please send screen shot > of NAT configuration page before you press Save Changes. > > Thanks, > Chitrang Srivastava > Cambium Networks > > > From: Af on behalf of Bill Prince > Sent: 15 July 2015 05:35:23 > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with > them. > > Have also loaded 13.4 on PMP430 and PMP450. > > bp > > > On 7/14/2015 4:59 PM, George Skorup wrote: >> I wonder if this affects P9 boards as well? That would suck. Not sure >> if I have one around the office to test. > >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Is it safe to say that upgrading a P8 SM remotely to 13.4 is ok as long as you are not using NAT? On Thu, Jul 16, 2015 at 1:39 PM, Mark Radabaugh wrote: > Chitrang - where do you want the bricks? > > Just for you we pulled the engineering.cgi from a 12.2 and a 13.1.3 P8 FSK > radio and then bricked them both with 13.4 and gave the customers new > radios. > > Where do you want the dead radios and the dump files sent? > > You can keep the P8’s and add them to your regression testing lab. > > Mark > > > > On Jul 14, 2015, at 10:08 PM, Chitrang Srivastava < > chitrang.srivast...@cambiumnetworks.com> wrote: > > > > Hi Bill, > > > > In order to investigate P8 issue, please do following, > > > > AFTER upgrade to P8 and applying configuration changes but BEFORE doing > reboot, take out engineering.cgi. > > Please also send configuration file as well from Configuration - > Unit > Setting. > > > > Does without NAT P8 is accessible? > > If the above steps didn't work ( actually they should because most of > our configuration changes applies on next reboot) they please send screen > shot of NAT configuration page before you press Save Changes. > > > > Thanks, > > Chitrang Srivastava > > Cambium Networks > > > > ________ > > From: Af on behalf of Bill Prince < > part15...@gmail.com> > > Sent: 15 July 2015 05:35:23 > > To: af@afmug.com > > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > > > Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with > > them. > > > > Have also loaded 13.4 on PMP430 and PMP450. > > > > bp > > > > > > On 7/14/2015 4:59 PM, George Skorup wrote: > >> I wonder if this affects P9 boards as well? That would suck. Not sure > >> if I have one around the office to test. > > > > > >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
But they're not bricked. They will boot up with the default plug inserted and you can change the NAT settings. On 7/16/2015 1:39 PM, Mark Radabaugh wrote: Chitrang - where do you want the bricks? Just for you we pulled the engineering.cgi from a 12.2 and a 13.1.3 P8 FSK radio and then bricked them both with 13.4 and gave the customers new radios. Where do you want the dead radios and the dump files sent? You can keep the P8’s and add them to your regression testing lab. Mark On Jul 14, 2015, at 10:08 PM, Chitrang Srivastava wrote: Hi Bill, In order to investigate P8 issue, please do following, AFTER upgrade to P8 and applying configuration changes but BEFORE doing reboot, take out engineering.cgi. Please also send configuration file as well from Configuration - > Unit Setting. Does without NAT P8 is accessible? If the above steps didn't work ( actually they should because most of our configuration changes applies on next reboot) they please send screen shot of NAT configuration page before you press Save Changes. Thanks, Chitrang Srivastava Cambium Networks From: Af on behalf of Bill Prince Sent: 15 July 2015 05:35:23 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with them. Have also loaded 13.4 on PMP430 and PMP450. bp On 7/14/2015 4:59 PM, George Skorup wrote: I wonder if this affects P9 boards as well? That would suck. Not sure if I have one around the office to test.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Yes, bridge works fine. On 7/16/2015 2:08 PM, Eric Muehleisen wrote: Is it safe to say that upgrading a P8 SM remotely to 13.4 is ok as long as you are not using NAT? On Thu, Jul 16, 2015 at 1:39 PM, Mark Radabaugh <mailto:m...@amplex.net>> wrote: Chitrang - where do you want the bricks? Just for you we pulled the engineering.cgi from a 12.2 and a 13.1.3 P8 FSK radio and then bricked them both with 13.4 and gave the customers new radios. Where do you want the dead radios and the dump files sent? You can keep the P8’s and add them to your regression testing lab. Mark > On Jul 14, 2015, at 10:08 PM, Chitrang Srivastava mailto:chitrang.srivast...@cambiumnetworks.com>> wrote: > > Hi Bill, > > In order to investigate P8 issue, please do following, > > AFTER upgrade to P8 and applying configuration changes but BEFORE doing reboot, take out engineering.cgi. > Please also send configuration file as well from Configuration - > Unit Setting. > > Does without NAT P8 is accessible? > If the above steps didn't work ( actually they should because most of our configuration changes applies on next reboot) they please send screen shot of NAT configuration page before you press Save Changes. > > Thanks, > Chitrang Srivastava > Cambium Networks > > > From: Af mailto:af-boun...@afmug.com>> on behalf of Bill Prince mailto:part15...@gmail.com>> > Sent: 15 July 2015 05:35:23 > To: af@afmug.com <mailto:af@afmug.com> > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with > them. > > Have also loaded 13.4 on PMP430 and PMP450. > > bp > > > On 7/14/2015 4:59 PM, George Skorup wrote: >> I wonder if this affects P9 boards as well? That would suck. Not sure >> if I have one around the office to test. > >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi Mark, Yes they aren't dead, you can still use them with 13.4 release & NAT but keeping table size to 1024. In the next release we will fix the issue. Thanks, Chitrang Srivastava Cambium Networks From: Af on behalf of Mark Radabaugh Sent: 17 July 2015 00:09:53 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended Chitrang - where do you want the bricks? Just for you we pulled the engineering.cgi from a 12.2 and a 13.1.3 P8 FSK radio and then bricked them both with 13.4 and gave the customers new radios. Where do you want the dead radios and the dump files sent? You can keep the P8’s and add them to your regression testing lab. Mark > On Jul 14, 2015, at 10:08 PM, Chitrang Srivastava > wrote: > > Hi Bill, > > In order to investigate P8 issue, please do following, > > AFTER upgrade to P8 and applying configuration changes but BEFORE doing > reboot, take out engineering.cgi. > Please also send configuration file as well from Configuration - > Unit > Setting. > > Does without NAT P8 is accessible? > If the above steps didn't work ( actually they should because most of our > configuration changes applies on next reboot) they please send screen shot > of NAT configuration page before you press Save Changes. > > Thanks, > Chitrang Srivastava > Cambium Networks > > > From: Af on behalf of Bill Prince > Sent: 15 July 2015 05:35:23 > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > Nope. Have already loaded 13.4 on P9, P10, and P11, and all is good with > them. > > Have also loaded 13.4 on PMP430 and PMP450. > > bp > > > On 7/14/2015 4:59 PM, George Skorup wrote: >> I wonder if this affects P9 boards as well? That would suck. Not sure >> if I have one around the office to test. > >
Re: [AFMUG] Software 13.4: P8 FSK not recommended
450 APs still boot up using the on-board GPS on 13.4 release. Just updated an AP with a SyncPipe attached and it came right up on the on-board instead like 13.2. So I guess that's not fixed. I've mentioned this before. If you have on-board + power port, it will boot up using the power port. It's only when you have timing port & on-board. This started early in 13.2 builds with the GPS data bug (like Motorola binary on the timing port, aka CMM2 or SyncPipe). I know most of the story behind that. I could be wrong, but I'm going to say that NMEA data is preferred over Mot binary and that's why it comes up on the on-board. This is very annoying, especially when you get an iGPS lock that sucks and you don't get time/date info for hours or days and all of the log entry times are stupid.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi George, By the Freerun fix, I mean this issue, where the Power Port shows Sync but the Sync Status still says searching. http://community.cambiumnetworks.com/t5/image/serverpage/image-id/279i18BB3380325BDEA1/image-size/original?v=mpbl-1&px=-1 This issue what you are reporting is still present where the software looks for the GPS Lock from any of the source and whichever it get first, locks it. We will try to fix this in future releases. Thanks, Chitrang -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: 17 July 2015 10:35 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 450 APs still boot up using the on-board GPS on 13.4 release. Just updated an AP with a SyncPipe attached and it came right up on the on-board instead like 13.2. So I guess that's not fixed. I've mentioned this before. If you have on-board + power port, it will boot up using the power port. It's only when you have timing port & on-board. This started early in 13.2 builds with the GPS data bug (like Motorola binary on the timing port, aka CMM2 or SyncPipe). I know most of the story behind that. I could be wrong, but I'm going to say that NMEA data is preferred over Mot binary and that's why it comes up on the on-board. This is very annoying, especially when you get an iGPS lock that sucks and you don't get time/date info for hours or days and all of the log entry times are stupid.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
My bad. I thought I read in the release notes that this was fixed. Maybe it was in the known issues section and I'm just stupid. On 7/17/2015 1:17 AM, Chitrang Srivastava wrote: Hi George, By the Freerun fix, I mean this issue, where the Power Port shows Sync but the Sync Status still says searching. http://community.cambiumnetworks.com/t5/image/serverpage/image-id/279i18BB3380325BDEA1/image-size/original?v=mpbl-1&px=-1 This issue what you are reporting is still present where the software looks for the GPS Lock from any of the source and whichever it get first, locks it. We will try to fix this in future releases. Thanks, Chitrang -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: 17 July 2015 10:35 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 450 APs still boot up using the on-board GPS on 13.4 release. Just updated an AP with a SyncPipe attached and it came right up on the on-board instead like 13.2. So I guess that's not fixed. I've mentioned this before. If you have on-board + power port, it will boot up using the power port. It's only when you have timing port & on-board. This started early in 13.2 builds with the GPS data bug (like Motorola binary on the timing port, aka CMM2 or SyncPipe). I know most of the story behind that. I could be wrong, but I'm going to say that NMEA data is preferred over Mot binary and that's why it comes up on the on-board. This is very annoying, especially when you get an iGPS lock that sucks and you don't get time/date info for hours or days and all of the log entry times are stupid.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi George, Did you get a chance to checkout Gps sync issue on 13.4 release? Thanks, Chitrang From: Af on behalf of George Skorup Sent: 17 July 2015 22:36:42 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended My bad. I thought I read in the release notes that this was fixed. Maybe it was in the known issues section and I'm just stupid. On 7/17/2015 1:17 AM, Chitrang Srivastava wrote: > Hi George, > > By the Freerun fix, I mean this issue, where the Power Port shows Sync but > the Sync Status still says searching. > http://community.cambiumnetworks.com/t5/image/serverpage/image-id/279i18BB3380325BDEA1/image-size/original?v=mpbl-1&px=-1 > > This issue what you are reporting is still present where the software looks > for the GPS Lock from any of the source and whichever it get first, locks it. > We will try to fix this in future releases. > > Thanks, > Chitrang > > -Original Message- > From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup > Sent: 17 July 2015 10:35 > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > 450 APs still boot up using the on-board GPS on 13.4 release. Just updated an > AP with a SyncPipe attached and it came right up on the on-board instead like > 13.2. So I guess that's not fixed. > > I've mentioned this before. If you have on-board + power port, it will boot > up using the power port. It's only when you have timing port & on-board. This > started early in 13.2 builds with the GPS data bug (like Motorola binary on > the timing port, aka CMM2 or SyncPipe). I know most of the story behind that. > I could be wrong, but I'm going to say that NMEA data is preferred over Mot > binary and that's why it comes up on the on-board. > > This is very annoying, especially when you get an iGPS lock that sucks and > you don't get time/date info for hours or days and all of the log entry times > are stupid.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
No. Too busy right now. Weather is nice and we're trying to get tower work done. If you guys are coming up on 13.4.1 soon, I'll probably just wait for that. Hopefully you'll just limited the P8 NAT table to 1024 so it will boot. Because physical access to those few I have is nearly impossible (chemical plants, and they have to shut down for us to get access). I noticed that 450 AP screenshot you linked on the community site is mine. That just happens to be the AP that we discovered was leaking (yes, the case itself). Some components on the board have visible corrosion, so I bet that has been the issue at that site all along. We put a Lite AP in its place a couple weeks ago and it hasn't had a single problem. I sent an email with pictures to supp...@cambiumnetworks.com last Saturday about this leaky AP, but nobody has responded. And the"open a support case" option on the website doesn't work. Maybe it does now, I haven't tried. I need minions. Or maybe a Stewie Griffin cloning machine. No wait, time machine would be better. On 7/22/2015 10:35 PM, Chitrang Srivastava wrote: Hi George, Did you get a chance to checkout Gps sync issue on 13.4 release? Thanks, Chitrang From: Af on behalf of George Skorup Sent: 17 July 2015 22:36:42 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended My bad. I thought I read in the release notes that this was fixed. Maybe it was in the known issues section and I'm just stupid. On 7/17/2015 1:17 AM, Chitrang Srivastava wrote: Hi George, By the Freerun fix, I mean this issue, where the Power Port shows Sync but the Sync Status still says searching. http://community.cambiumnetworks.com/t5/image/serverpage/image-id/279i18BB3380325BDEA1/image-size/original?v=mpbl-1&px=-1 This issue what you are reporting is still present where the software looks for the GPS Lock from any of the source and whichever it get first, locks it. We will try to fix this in future releases. Thanks, Chitrang -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: 17 July 2015 10:35 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended 450 APs still boot up using the on-board GPS on 13.4 release. Just updated an AP with a SyncPipe attached and it came right up on the on-board instead like 13.2. So I guess that's not fixed. I've mentioned this before. If you have on-board + power port, it will boot up using the power port. It's only when you have timing port & on-board. This started early in 13.2 builds with the GPS data bug (like Motorola binary on the timing port, aka CMM2 or SyncPipe). I know most of the story behind that. I could be wrong, but I'm going to say that NMEA data is preferred over Mot binary and that's why it comes up on the on-board. This is very annoying, especially when you get an iGPS lock that sucks and you don't get time/date info for hours or days and all of the log entry times are stupid.
Re: [AFMUG] Software 13.4: P8 FSK not recommended
Hi George, I got an update that support case is working, please try and send us the details. Thanks, -Original Message- From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup Sent: 23 July 2015 09:40 To: af@afmug.com Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended No. Too busy right now. Weather is nice and we're trying to get tower work done. If you guys are coming up on 13.4.1 soon, I'll probably just wait for that. Hopefully you'll just limited the P8 NAT table to 1024 so it will boot. Because physical access to those few I have is nearly impossible (chemical plants, and they have to shut down for us to get access). I noticed that 450 AP screenshot you linked on the community site is mine. That just happens to be the AP that we discovered was leaking (yes, the case itself). Some components on the board have visible corrosion, so I bet that has been the issue at that site all along. We put a Lite AP in its place a couple weeks ago and it hasn't had a single problem. I sent an email with pictures to supp...@cambiumnetworks.com last Saturday about this leaky AP, but nobody has responded. And the"open a support case" option on the website doesn't work. Maybe it does now, I haven't tried. I need minions. Or maybe a Stewie Griffin cloning machine. No wait, time machine would be better. On 7/22/2015 10:35 PM, Chitrang Srivastava wrote: > Hi George, > > Did you get a chance to checkout Gps sync issue on 13.4 release? > > Thanks, > Chitrang > > > From: Af on behalf of George Skorup > > Sent: 17 July 2015 22:36:42 > To: af@afmug.com > Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended > > My bad. I thought I read in the release notes that this was fixed. > Maybe it was in the known issues section and I'm just stupid. > > On 7/17/2015 1:17 AM, Chitrang Srivastava wrote: >> Hi George, >> >> By the Freerun fix, I mean this issue, where the Power Port shows Sync but >> the Sync Status still says searching. >> http://community.cambiumnetworks.com/t5/image/serverpage/image-id/279 >> i18BB3380325BDEA1/image-size/original?v=mpbl-1&px=-1 >> >> This issue what you are reporting is still present where the software looks >> for the GPS Lock from any of the source and whichever it get first, locks it. >> We will try to fix this in future releases. >> >> Thanks, >> Chitrang >> >> -Original Message- >> From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup >> Sent: 17 July 2015 10:35 >> To: af@afmug.com >> Subject: Re: [AFMUG] Software 13.4: P8 FSK not recommended >> >> 450 APs still boot up using the on-board GPS on 13.4 release. Just updated >> an AP with a SyncPipe attached and it came right up on the on-board instead >> like 13.2. So I guess that's not fixed. >> >> I've mentioned this before. If you have on-board + power port, it will boot >> up using the power port. It's only when you have timing port & on-board. >> This started early in 13.2 builds with the GPS data bug (like Motorola >> binary on the timing port, aka CMM2 or SyncPipe). I know most of the story >> behind that. I could be wrong, but I'm going to say that NMEA data is >> preferred over Mot binary and that's why it comes up on the on-board. >> >> This is very annoying, especially when you get an iGPS lock that sucks and >> you don't get time/date info for hours or days and all of the log entry >> times are stupid.
