Hi John – The complete list of OIDs affected by this problem are:
1.3.6.1.4.1.161.19.3.2.1.1 rfScanList DisplayString 1.3.6.1.4.1.161.19.3.2.1.79 pppoeAccessConcentrator DisplayString 1.3.6.1.4.1.161.19.3.2.1.80 pppoeServiceName DisplayString 1.3.6.1.4.1.161.19.3.2.1.81 pppoeUserName DisplayString Doing a SET on any of these will cause the SM crash to occur. We can make a fix available if you would like, and are working on a Field Support Bulletin. The devices are not being shipped with 13.2, so we suggest you program your devices on the shipped version and then upgrade them after setting these values with 13.1.3 SW. -Aaron From: Af [mailto:af-boun...@afmug.com] On Behalf Of John Babineaux via Af Sent: Friday, November 14, 2014 3:26 PM To: af@afmug.com Subject: Re: [AFMUG] Issue with SNMP OID .1.3.6.1.4.1.161.19.3.2.1.1.0 That is a huge problem to use b/c that is how we preprogram all our SMs before deployment Also check the PPPoE username snmp .1.3.6.1.4.1.161.19.3.2.1.81.0 ____________________________________ John Babineaux System Administrator REACH4 Communications | Website: www.REACH4Com.com<http://www.reach4com.com/> Phone: 337-783-3436 x105 | Email: john.babine...@reach4com.com<mailto:john.babine...@reach4com.com> 927 N Parkerson Ave, Crowley, LA 70526 From: Af [mailto:af-boun...@afmug.com] On Behalf Of Jonathan Mandziara via Af Sent: Thursday, November 13, 2014 7:10 PM To: af@afmug.com<mailto:af@afmug.com> Subject: [AFMUG] Issue with SNMP OID .1.3.6.1.4.1.161.19.3.2.1.1.0 Importance: High 13.2 Users, There is an issue with the following SNMP OID to set the frequency list on an SM. .1.3.6.1.4.1.161.19.3.2.1.1.0 For Example: snmpset -v 2c -c "Canopy" 169.254.1.1 .1.3.6.1.4.1.161.19.3.2.1.1.0 s "548000" If this OID is used to set aa frequency on an SM, it will cause the SM to crash. After the SM reboots, the list of frequencies listed the SNMP set will not be set on the SM. We have carefully reviewed the code, and this is the only OID effected. This issue is being tracked under Issue Number "CPY-10392" and is slated to 13.3 for repair. We apologize for any inconvenience that this may have caused. Sincerely, The Cambium Team
