Re: [AFMUG] SAF Hybrid interface question
Yes Sent from my Ranch Phone On Dec 1, 2014, at 10:07 AM, Paul McCall via Af af@afmug.com wrote: We have an SAF Lumina with the Hybrid Interface on it. Optical and Electrcial. Our fiber going to the radio got eaten by a big bird. Not THE Big Bird, but A big bird J Anyway, can we actually use the EL (copper) interface to pass data? I have emailed SAF this AM and not gotten an answer yet Paul Paul McCall, Pres. PDMNet / Florida Broadband 658 Old Dixie Highway Vero Beach, FL 32962 772-564-6800 office 772-473-0352 cell www.pdmnet.com pa...@pdmnet.net
Re: [AFMUG] Dymo label printers
I fold them on half, longways, so that the split in the rear opens up. I have used one for several years and never defaced a label. Once I a while one is difficult, but the backing does come off even then. Allen Sent from my Ranch Phone On Nov 25, 2014, at 1:09 PM, Randy Cosby via Af af@afmug.com wrote: Does anyone use the Dymo Rhino label printers? I got one and love it -- except for trying to peel the backing off labels. It's a real pain and I end up ruining quite a few by stretching them or getting adhesive on my fingers then on the front of the label. Any tricks I haven't figured out? -- mime-attachment.png Randy Cosby InfoWest, Inc 435-674-0165 x 2010 infowest.com This e-mail message contains information from InfoWest, Inc and is for the sole use of the intended recipient(s) and may contain privileged, proprietary or confidential information. Unauthorized use, distribution, review or disclosure is prohibited. If you are not the intended recipient, please contact rco...@infowest.com by reply email and destroy the original message, all attachments and copies.
Re: [AFMUG] 13.2 Issue (Removing frequency checkboxes)
I upgraded a 2.4 sector SM first to 13.2 and it did not reconnect to the tower until I upgraded the AP to 13.2 as well. Allen Sent from my Ranch Phone On Nov 14, 2014, at 12:25 AM, Rajesh Vijayakumar via Af af@afmug.com wrote: We looked at all the recent changes than went in to 13.2 but did not find anything that would explain this behavior. Also tried to recreate it in the lab on a 2.4 GHz setup, but the SM kept all the checked frequencies after upgrade from 13.1.3 to 13.2. Has anyone else upgraded a 2.4 GHz sector and run into this issue (or did not run into this issue)? Rajesh Vijayakumar Cambium Networks On Thu, Nov 13, 2014 at 10:45 PM, Aaron Schneider via Af af@afmug.com wrote: We are investigating the other issues, but with respect to 5767.5 and 5807.5, those two were affected by a bug fix, in that pre-13.2, 5767.5 was actually enabling 5767.20, due to an obvious typo in the scan list code, and 5807.5 was actually enabling 5807.00, due to another typo bug in the code. So correcting these two items may have left them unchecked on an upgrade to 13.2, but they weren’t valid scan frequencies anyways. These two updates didn’t make the release notes due to an oversight. These two frequency updates are in no way related to what is being reported for the 2.5MHz center channels coming back unchecked for 2.4. we are investigating. -Aaron From: Af [mailto:af-boun...@afmug.com] On Behalf Of George Skorup (Cyber Broadcasting) via Af Sent: Thursday, November 13, 2014 9:25 PM To: af@afmug.com Subject: Re: [AFMUG] 13.2 Issue (Removing frequency checkboxes) 13.2 on the SM definitely does not jive with build 32 on the AP. So.. don't do that. I forgot I still had that AP on build 32 until it was too late. SMs would pop in session for about 2 seconds and go down again. Luckily updating the AP to 13.2 official fixed it. I'm also seeing 5GHz SMs losing freqs. But it's funny, like 99% of them only lose 5767.5 and 5807.5. I try to avoid the 2.5 centers whenever I can since I've noticed exactly what you guys are seeing here in the past, ALL of the 2.5 centers disappear. I don't use 5MHz bandwidth, and I usually lock the scan list on the SM down to the band the AP is operating in. So maybe that's why I was losing only a couple freqs. On 11/13/2014 9:12 PM, Ryan Ray via Af wrote: It's crazy. No warning, no release notes about it. How does this come out of all the betas and you lose your SM's because a frequency isn't checked... On Thu, Nov 13, 2014 at 7:09 PM, timothy steele via Af af@afmug.com wrote: Yeah I noticed that same with 5Ghz looks like they unchecked the rarely used channels in SM with 13.2 programmer was probably thinking he was helping but lots are going to complain — Sent from Mailbox On Thu, Nov 13, 2014 at 10:06 PM, Ryan Ray via Af af@afmug.com wrote: Just did a 200 group of SM's and the upgrade has removed frequencies that were previously checked. I followed the guide and did the SM's first and AP's last. Luckily the majority of these can see another AP but what the fuck... About half of these SM's were on 13.2(34) and the other half were on 13.1.3... This is what it looks like after an update image.png Pre update they were all image.png URG
Re: [AFMUG] Accedian/Performant/R-Flo woes
So sad, I have two hardened minds and 6 hardened nurons from that bunch. Never deployed. Sent from my Ranch Phone On Oct 16, 2014, at 4:32 PM, Gino Villarini via Af af@afmug.com wrote: We are going to toss them Gino A. Villarini @gvillarini On Oct 16, 2014, at 6:25 PM, Chris Wright via Af af@afmug.com wrote: 1.2.8.6_21016 released in June of this year. http://forum.performantnetworks.com/threads/2015.1438/ Chris Wright Velociter Wireless From: Af [mailto:af-boun...@afmug.com] On Behalf Of Matthew Jenkins via Af Sent: Thursday, October 16, 2014 3:20 PM To: Timothy D. McNabb via Af Subject: Re: [AFMUG] Accedian/Performant/R-Flo woes I have a tub of equipment I really wanted to deploy. It's not being actively developed, so I have not deployed it. Are you running the latest software? Original message From: Timothy D. McNabb via Af af@afmug.com Date: 10/16/2014 1:58 PM (GMT-07:00) To: af@afmug.com Subject: Re: [AFMUG] Accedian/Performant/R-Flo woes Does anyone here on the list use Performant Nurons/Mind combination? What did you find worked best? -Tim From: Af [mailto:af-boun...@afmug.com] On Behalf Of Chris Wright via Af Sent: Wednesday, October 15, 2014 5:00 PM To: af@afmug.com Subject: [AFMUG] Accedian/Performant/R-Flo woes We’ve been sitting on a Performant Mind and four Nurons for almost a year now. They sat for six months, then I spent another six months tinkering with them here and there. Regardless of their EOL, we’re looking to implement – but I’m running into the silliest of issues. I can’t even get traffic from the Mind to a Nuron to pass without 20% packet loss. This is without any routing, wireless backhauls, nothing. Just a VLAN-tagged NIC plugged straight into the Mind, Ethernet from Mind to a Nuron (where the vlan “pops”), then Ethernet to a second computer. I’ve replaced the SFP adapters, the nuron, and verified none of the Ethernet cables are bad by literally coupling them all down a line and going straight from computer 1 to computer 2. No issue there. This, combined with the fact that this stuff is going to be EOL in three years, is maddening. My boss was under the impression that this should be able to seamlessly integrate into our star topology (nuron at every tower making a ring), but we can’t even get basic LAN functions to work reliably. Chris Wright Velociter Wireless
Re: [AFMUG] PMP450 AP stopped responding
Seeing -237 and such VC counts on the first page of 5.4 450 APs. Other types seem to count correctly. 13.2B30 Allen Sent from my Ranch Phone On Sep 26, 2014, at 3:44 PM, Aaron Schneider via Af af@afmug.com wrote: Hi Ryan – While I can’t say for certain what caused the Ethernet Core to get stuck, there are two things in 13.2 that will help with this. First off, there was a bug in this reporting mechanism that wasn’t allowing a recovery to take place. That recovery should have been an AP reboot but the logging itself was preventing that. Secondly, for PMP450, in 13.2, there were architectural changes made such that this type of a problem can’t happen anymore. Those changes are related to the speed improvements gained with the 13.2 release on PMP450. PMP430 could still be susceptible to this type of a condition, but the first point I mentioned will correct the recovery in that it won’t let the device sit there unresponsive, it will reset itself if it gets stuck in this kind of condition. Please try the 13.2 Build 30 beta if you can. We are close to the 13.2 general release. Regards, -Aaron From: Af [mailto:af-bounces+aaron.schneider=cambiumnetworks@afmug.com] On Behalf Of Ryan Ray via Af Sent: Friday, September 26, 2014 3:17 PM To: af@afmug.com Subject: [AFMUG] PMP450 AP stopped responding About 30 minutes ago I had a 2.4 AP loaded on 13.1.3 just quit responding. CTM said there was still normal power draw, link was up up on the cisco switch with no errors. No traffic. Reset the port from the CTM and it came back. I have another AP up there right beside it on the same software that I haven't seen issues yet. Anyone ever seen this before? I saw this on the bootup log. **System Startup** System Reset Exception -- Software Version : CANOPY 13.1.3 AP-DES Board Type : P12 Device Setting : 2.4GHz MIMO OFDM - Access Point - No valid accounts configured. Using default user account - 2460.0 MHz - 20.0 MHz - 1/16 - CC 4 FPGA Version : 011514 FPGA Features : DES, Sched, US/ETSI; 12/31/2010 : 17:00:24 PDT : Bridge Core : Acquired sync pulse from Power Port. 09/25/2014 : 01:18:10 PDT : : Bridge Core : Time Set 12/31/2010 : 17:00:00 PDT : : Bridge Core : 01/01/2011 : 00:00:00 UTC : : Bridge Core : Time Set 12/31/2010 : 17:00:00 PDT : Bridge Core : **System Startup** System Reset Exception -- Watchdog Reset Software Version : CANOPY 13.1.3 AP-DES Board Type : P12 Device Setting : 2.4GHz MIMO OFDM - Access Point - No valid accounts configured. Using default user account - 2460.0 MHz - 20.0 MHz - 1/16 - CC 4 FPGA Version : 011514 FPGA Features : DES, Sched, US/ETSI; 12/31/2010 : 17:00:24 PDT : Bridge Core : Acquired sync pulse from Power Port. 09/25/2014 : 15:03:05 PDT : : Bridge Core : Time Set 09/26/2014 : 13:10:02 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:05 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:09 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:12 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:16 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:20 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:23 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:27 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:31 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:34 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:38 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:42 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:45 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:49 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:52 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:56 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:00 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:03 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:07 PDT : : Bridge Core : Ethernet Core failing to report. Cheers
Re: [AFMUG] PMP450 AP stopped responding
Thank you. Sent from my Ranch Phone On Sep 26, 2014, at 6:15 PM, Aaron Schneider via Af af@afmug.com wrote: That can be ignored and is fixed already. It has no bearing on operation, just a display issue. From: Af [mailto:af-bounces+aaron.schneider=cambiumnetworks@afmug.com] On Behalf Of RanchBoss via Af Sent: Friday, September 26, 2014 5:27 PM To: af@afmug.com Subject: Re: [AFMUG] PMP450 AP stopped responding Seeing -237 and such VC counts on the first page of 5.4 450 APs. Other types seem to count correctly. 13.2B30 Allen Sent from my Ranch Phone On Sep 26, 2014, at 3:44 PM, Aaron Schneider via Af af@afmug.com wrote: Hi Ryan – While I can’t say for certain what caused the Ethernet Core to get stuck, there are two things in 13.2 that will help with this. First off, there was a bug in this reporting mechanism that wasn’t allowing a recovery to take place. That recovery should have been an AP reboot but the logging itself was preventing that. Secondly, for PMP450, in 13.2, there were architectural changes made such that this type of a problem can’t happen anymore. Those changes are related to the speed improvements gained with the 13.2 release on PMP450. PMP430 could still be susceptible to this type of a condition, but the first point I mentioned will correct the recovery in that it won’t let the device sit there unresponsive, it will reset itself if it gets stuck in this kind of condition. Please try the 13.2 Build 30 beta if you can. We are close to the 13.2 general release. Regards, -Aaron From: Af [mailto:af-bounces+aaron.schneider=cambiumnetworks@afmug.com] On Behalf Of Ryan Ray via Af Sent: Friday, September 26, 2014 3:17 PM To: af@afmug.com Subject: [AFMUG] PMP450 AP stopped responding About 30 minutes ago I had a 2.4 AP loaded on 13.1.3 just quit responding. CTM said there was still normal power draw, link was up up on the cisco switch with no errors. No traffic. Reset the port from the CTM and it came back. I have another AP up there right beside it on the same software that I haven't seen issues yet. Anyone ever seen this before? I saw this on the bootup log. **System Startup** System Reset Exception -- Software Version : CANOPY 13.1.3 AP-DES Board Type : P12 Device Setting : 2.4GHz MIMO OFDM - Access Point - No valid accounts configured. Using default user account - 2460.0 MHz - 20.0 MHz - 1/16 - CC 4 FPGA Version : 011514 FPGA Features : DES, Sched, US/ETSI; 12/31/2010 : 17:00:24 PDT : Bridge Core : Acquired sync pulse from Power Port. 09/25/2014 : 01:18:10 PDT : : Bridge Core : Time Set 12/31/2010 : 17:00:00 PDT : : Bridge Core : 01/01/2011 : 00:00:00 UTC : : Bridge Core : Time Set 12/31/2010 : 17:00:00 PDT : Bridge Core : **System Startup** System Reset Exception -- Watchdog Reset Software Version : CANOPY 13.1.3 AP-DES Board Type : P12 Device Setting : 2.4GHz MIMO OFDM - Access Point - No valid accounts configured. Using default user account - 2460.0 MHz - 20.0 MHz - 1/16 - CC 4 FPGA Version : 011514 FPGA Features : DES, Sched, US/ETSI; 12/31/2010 : 17:00:24 PDT : Bridge Core : Acquired sync pulse from Power Port. 09/25/2014 : 15:03:05 PDT : : Bridge Core : Time Set 09/26/2014 : 13:10:02 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:05 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:09 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:12 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:16 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:20 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:23 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:27 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:31 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:34 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:38 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:42 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:45 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:49 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:52 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:10:56 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:00 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:03 PDT : : Bridge Core : Ethernet Core failing to report. 09/26/2014 : 13:11:07 PDT : : Bridge Core : Ethernet Core failing to report. Cheers
