Will try to strip our stuff out, clean them up a bit and post an example when I get a chance. There pretty ugly right now.
> I love a copy of these scripts, too! More compensation available. :-) > > DaveW > > On 12/8/2014 4:24 PM, Sean Heskett via Af wrote: > > would you care to share your scripts matt? > > i'd be glad to buy beers or other compensation. our guys have been asking > for an easy way to do all this and i've been too busy to build the scripts > myself. > > -sean > > > > On Mon, Dec 8, 2014 at 4:07 PM, Matt via Af <[email protected]> wrote: >> >> I have perl script that programs SM's before they are labeled and go >> to installers. Between interruptions been fighting issues. >> >> snmpset -v 2c -c Canopy 169.254.1.1 .1.3.6.1.4.1.161.19.3.2.1.1.0 s >> all # Set Channel Scan >> No response. >> >> These also seem to not work. >> >> lanMaskSm >> Object ID: 1.3.6.1.4.1.161.19.3.2.1.4 >> >> lanIpSm >> Object ID: 1.3.6.1.4.1.161.19.3.2.1.3 >> >> defaultGwSm >> Object ID: 1.3.6.1.4.1.161.19.3.2.1.5 >> >> >> >> >> >> >> On Mon, Dec 8, 2014 at 4:26 PM, Jonathan Mandziara via Af <[email protected]> >> wrote: >> > Matt, >> > >> > Thanks! >> > >> > With those steps that you provided, I can see the issue that you are >> > having. >> > >> > I will open an issue for this. >> > >> > The obvious workaround (until fixed) would be to set the IPv4 Filter >> > after setting the IPv6 filter in your script. >> > >> > Best, >> > >> > Jonathan >> > >> > -----Original Message----- >> > From: Af [mailto:[email protected]] On Behalf Of Matt via Af >> > Sent: Monday, December 08, 2014 2:53 PM >> > To: [email protected] >> > Subject: Re: [AFMUG] Canopy v13.2 and SNMP Bug? >> > >> > Further investigation. To repeat it. >> > >> > First reset factory defaults to a 3.6 sm running 13.2 then reboot. >> > Enable SNMP read/write in GUI. >> > >> > Then: >> > >> > #set IPv4 filter all >> > snmpset -v 2c -c Canopy 169.254.1.1 .1.3.6.1.4.1.161.19.3.3.2.132.0 i 1 >> > >> > #set IPv6 filter all >> > snmpset -v 2c -c Canopy 169.254.1.1 .1.3.6.1.4.1.161.19.3.3.2.160.0 i 1 >> > >> > The moment you set IPv6 filter it disables the IPv4 filter. After you >> > do this once you cannot reproduce it without resetting defaults and >> > rebooting again. Seeing other SNMP issues. Still testing. >> > >> > >> > >> > >> > >> > On Mon, Dec 8, 2014 at 1:51 PM, Jonathan Mandziara via Af <[email protected]> >> > wrote: >> >> Matt, >> >> >> >> We are not able to reproduce your issue. >> >> >> >> We have some questions for you. >> >> Q1) Is your radio's SNMP setting set to R/W? >> >> Q2) Is the radios' SNMP Community string set to "Canopy"? >> >> Q3) Is the SNMP filter enabled? >> >> Q4) Are you rebooting the SM after sending the SNMP OID? >> >> Q5) Are you trying this to the SM over the SNMP proxy? >> >> Q6) What is the error that snmpset provides after issuing the command? >> >> >> >> Best, >> >> >> >> Cambium Jonathan >> >> >> >> -----Original Message----- >> >> From: Af [mailto:[email protected]] On Behalf Of Matt via Af >> >> Sent: Monday, December 08, 2014 12:01 PM >> >> To: [email protected] >> >> Subject: [AFMUG] Canopy v13.2 and SNMP Bug? >> >> >> >> allIpv4Filter >> >> Object ID: 1.3.6.1.4.1.161.19.3.3.2.132 >> >> >> >> snmpset -v 2c -c Canopy 169.254.1.1 .1.3.6.1.4.1.161.19.3.3.2.132.0 i >> >> 1 >> >> >> >> Keep trying to set the allip4filter with SNMP on a 3.6 450 SM running >> >> 13.2 and it does not seem to work. Anyone else see an issue with it? >> >> Setting the allipv6filter does seem to work. This a bug? > > >
