That is like cheating, I like it. Thanks for the info Adam.. I will have to
dig into that this winter.

Thanks,


Joe



On Mon, Sep 25, 2017 at 2:15 PM, Adam Moffett <[email protected]> wrote:

> Use python and snimpy to pre-config.
> Snimpy is awesome.  For this one to work, put the ePMP MIB in the same
> directory as the script.  Install Snipmy per the author's instructions.
> I use this script to correct units in the field that are wrong, so for
> example where the unit has the wrong SNMP string I set "fixaccess" to 1.
> It could just easily be a preconfig script.
>
>
> #!/usr/bin/python
> from snimpy.manager import Manager as M
> from snimpy.manager import load
> import sys
>
> #usage:
> # ePMPSetup.py [read write string] [fixaccess enable] [setvlans enable]
> [setmaestro] [unit ip]
> # ePMPSetup.py private 1 1 1 169.254.1.1
>
> ip = sys.argv[5]
> rwcomm = sys.argv[1]
> fixaccess = sys.argv[2]
> setvlans = sys.argv[3]
> setmaestro = sys.argv[4]
>
> #print sys.argv
> #print ip
> #print rwcomm
>
>
> #Load Compact MIB
> load("./CAMBIUM-ePMP-3.2-MIB.txt")
>
> m = M(host=ip, community=rwcomm, version=2)
> print "Device Name = "+m.systemConfigDeviceName
>
> if setvlans=="1":
>   print "Setting up mgmt VLAN...."
>   m.mgmtVLANVID = 101
>   m.mgmtVLANVP = 7
>   m.mgmtVLANEnable = 1
>
>   print "Setting up data VLAN..."
>   m.dataVLANVID = 102
>   m.dataVLANVP = 0
>   m.dataVLANEnable = 1
>
> print "Enable spanning tree..."
> m.networkSTP = 1
>
> print "Setting Timezone to EST..."
> m.systemConfigTimezone = "EST5"
>
> print "Enable ethernet port security (limit to one device on ethernet
> port)..."
> m.networkPortSecurityMax = 1
> m.networkPortSecurityAgingTime = 300
> m.networkPortSecurity = 1
>
> print "Enable broadcast limit (prevent broadcast storm)..."
> m.networkBroadcastStormRate = 100
> m.networkBroadcastStormEnabled = 1
>
> if fixaccess == "1":
>   print "Fixing SNMP Strings..."
>   m.snmpReadOnlyCommunity = "ourreadcomm"
>   m.snmpReadWriteCommunity = "ourwritecomm"
>
> if setmaestro == "1":
>   print "Populate CN Maestro config..."
>   m.cambiumDeviceAgentCNSURL = "https://cloud.cambiumnetworks.com";
>   m.cambiumCNSDeviceAgentID = "agentID"
>   m.cambiumCNSDeviceAgentPassword = "maestropass"
>
> print "saving config..."
> m.cambiumpmp80211ConfigurationSave = 1
> print "applying config..."
> m.cambiumpmp80211ConfigurationApply = 1
>
> print "rebooting"
> m.cambiumpmp80211DeviceReboot = 1
>
>
>
>
>
> ------ Original Message ------
> From: "Steve Jones" <[email protected]>
> To: "[email protected]" <[email protected]>
> Sent: 9/25/2017 2:11:21 PM
> Subject: Re: [AFMUG] ePMP Release 3.5
>
> we have found with config files, never, ever, under any circumstance load
> one from one firmware to another, ever, disease and pestulence always
> follow.
>
> its irritating because we load a default config into each unit before
> deployment, so each firmware we upgrade a bench unit, factory default it,
> manually rebuild the entire config and export it.
>
> cnmaestro onboarding and passwords are almost always jacked regardless
>
> On Mon, Sep 25, 2017 at 12:53 PM, Nate Burke <[email protected]> wrote:
>
>> I haven't spent any time on the forums, or opened any tickets.   But the
>> one thing I've noticed from my little usage of 3.4 and 3.5 revolves around
>> saving config changes.  Click the save button, and radio will just to go
>> 'applying' for several seconds, may or may not actually come back from the
>> 'applying' state.
>>
>> And loading in a backup config file requires the radio to power cycle to
>> access the radio, it's like it locks the IP portion.
>>
>> I'm sticking with 2.6.2 for almost everything for now, and just dealing
>> with the Slow GUI.
>>
>> On 9/25/2017 12:42 PM, Paul McCall wrote:
>>
>> What bugs have you actually experienced?  It seems that others are not
>> having major issues with 3.5.  a few things as mentioned on Cambium forums.
>>
>>
>>
>> Paul
>>
>>
>>
>> *From:* Af [mailto:[email protected] <[email protected]>] *On
>> Behalf Of *Josh Luthman
>> *Sent:* Sunday, September 24, 2017 10:58 AM
>> *To:* [email protected]
>> *Subject:* Re: [AFMUG] ePMP Release 3.5
>>
>>
>>
>> Rolling 3.2.2 still.  I've got known issues in 3.4 and 3.5 that doesn't
>> make it worth it.
>>
>>
>>
>> I would really like to have my downlink% OID that came with 3.3 or
>> 3.4...but not at the cost of the bugs.
>>
>>
>>
>>
>> Josh Luthman
>> Office: 937-552-2340 <(937)%20552-2340>
>> Direct: 937-552-2343 <(937)%20552-2343>
>> 1100 Wayne St
>> <https://maps.google.com/?q=1100+Wayne+St+%0D+Suite+1337+%0D+Troy,+OH+45373&entry=gmail&source=g>
>> Suite 1337
>> Troy, OH 45373
>>
>>
>>
>> On Sat, Sep 23, 2017 at 7:23 PM, Mathew Howard <[email protected]>
>> wrote:
>>
>> I guess I over estimated a bit, looks like we've only got a hundred or so
>> on 3.5. I think we have somewhere around a thousand customers on ePMP.
>>
>>
>>
>>
>>
>> On Sep 23, 2017 1:14 PM, "Paul McCall" <[email protected]> wrote:
>>
>> How big is your network?
>>
>>
>>
>> *From:* Af [mailto:[email protected]] *On Behalf Of *Mathew Howard
>> *Sent:* Saturday, September 23, 2017 10:38 AM
>> *To:* af < <[email protected]>[email protected]>
>> *Subject:* Re: [AFMUG] ePMP Release 3.5
>>
>>
>>
>> I've got 3.5 running on probably about half our stuff now. I haven't
>> noticed any major issues.
>>
>>
>>
>> On Sep 23, 2017 8:15 AM, "Paul McCall" <[email protected]> wrote:
>>
>> I see a few problems on the Cambium form on 3.5.   They may be isolated
>> incidences but enough to have caution. Has anybody rolled it out to a large
>> number of APs and SMs?
>>
>>
>>
>>
>>
>>
>>
>> Paul McCall, President
>>
>> PDMNet, Inc. / Florida Broadband, Inc.
>>
>> 658 Old Dixie Highway
>> <https://maps.google.com/?q=658+Old+Dixie+Highway%0D+Vero+Beach,+FL+32962%0D+772&entry=gmail&source=g>
>>
>> Vero Beach, FL 32962
>> <https://maps.google.com/?q=658+Old+Dixie+Highway%0D+Vero+Beach,+FL+32962%0D+772&entry=gmail&source=g>
>>
>> 772-564-6800 <%28772%29%20564-6800>
>>
>> <[email protected]>[email protected]
>>
>> <http://www.pdmnet.com>www.pdmnet.com
>>
>> <http://www.floridabroadband.com>www.floridabroadband.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>

Reply via email to