search for: snmpv3

I'm trying to get SNMPv3 management working for an APC AP9617 card. It is newly refurbed, running sumx v3.7.2 and aos v3.7.3. In the SNMPv3 user profiles section I have (I don't care about the password leaking, it's temporary): User Name: nut Authentication Passphrase: NutScan at Password43LongerWord Privac...

On Nov 30, 2017, at 6:31 PM, Lee Damon <nomad at ee.washington.edu> wrote: > > SNMPv3 works fine when I have any one of the three configured in > ups.conf while the other two are configured with SNMPv1. It doesn't > matter which _one_ UPS is configured for SNMPv3 in ups.conf, they all > work individually (see below example). > > However, if I configure any two or...

...___________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Lee Damon <nomad at ee.washington.edu> Sent: Tuesday, April 28, 2020 3:28 PM To: nut-upsuser Mailing List Subject: [EXTERNAL] [Nut-upsuser] nut-scanner, SNMPv3, APC UPS not chatting This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ________________________________ I'm trying to get SNMPv3 management wo...

New NUT install dealing with three APC Smart-UPS 5000s, two of which have AP9617 and the third has a AP9619 card. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three UPSs with SNMPv1 with no...

nut-2.6.5 Scientific Linux 6.3 APC AP9630 management card My basic question is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5 privProt...

Dear all, I have installed mrtg via yum on centos 7, and using cron job to load mrtg every 5 mins. Everything work fine but just snmp v3 graph no show up. I try to load the command LAND=C /usr/bin/mrtg /etc/mrtg/metg.cfg it will show an error "SNMP V3 libraries not found, SNMPV3 disabled.". so, i installed all the net-snmp but still showing the error. I can't find any suggestion on google. can anyone have the same problem ? Thanks Alex

...vice is not needed anymore. Stopping. I have a feeling that if I do get this working by setting huge timers I'm just cargo-culting a "fix". nomad On 12/4/17 09:38 , Lee Damon wrote: > Hi Charles, > > Running upsdrvctl -D start on the host with all three configured to > SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all > three but importantly they all start up and keep running. > > I'm starting to suspect the startup is taking so long that systemd is > timing out and killing it. time -p reports real time of 133.27. I'...

...oad_mib2nut: trying classic method with 'apcc' mib 0.044961 Entering nut_snmp_get_str() 0.044965 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0) 0.051353 Unknown mibs value: apcc Now in the months between the last post and this, I had the opportunity to successfully test SNMPv3 using an Eaton Network Card-MS in an evolution 850. Now what was different (besides all the hardware). I remembered that the Eaton card did not have the option of using AES for the privProtocol. So I changed the privProtocol from AES to DES and updated usp.conf and now NUT seems willing to talk to...

One thing I just noticed, all of the COMBAD and COMOK messages are about the same UPS, the other two seem to be fine. nomad On 12/5/17 08:24 , Lee Damon wrote: ... > I suspect there's a deeper problem here. This morning I came in to 22 > emails about COMBAD and 22 emails about COMOK from upsmon on the master > host and a bunch more such messages from upsmon on my test clients. The

On Dec 4, 2017, at 2:43 PM, Lee Damon <nomad at ee.washington.edu> wrote: > > I have it "working" with the following settings changes from the default > in the RPM. By "working" I mean it starts after reboot and after issuing > 'sudo systemctl restart nut-driver' but, as expected, it takes quite a > while to finish startup. Yeah, this doesn't

On 4/28/20 1:58 PM, David Zomaya wrote: > snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X > privpassphrase Evidently, even with argument identifiers order matters. That worked just fine and dandy. Now I guess I need to play with the order of the nut-scanner arguments to see if I get a similar result. thanks, nomad

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of syste...

>How close do the EPEL RPM's systemd configuration files look to the ones in the NUT tree? The only difference between?/lib/systemd/system/nut-driver.service and the one at?https://github.com/networkupstools/nut/blob/v2.7.2/scripts/systemd/nut-driver.service.in (not counting variable substitution for paths) is an additional line in the [Service] section provided by EPEL:

I have it "working" with the following settings changes from the default in the RPM. By "working" I mean it starts after reboot and after issuing 'sudo systemctl restart nut-driver' but, as expected, it takes quite a while to finish startup. /etc/systemd/system/nut-driver.service.d/nut-driver.conf [Unit] StopWhenUnneeded=no [Service] TimeoutSec=600

...SNMP v3 user as your SNMP Set or a different one? > > If it is a different one (e.g. an SNMP v1 or v2c string) does that user > / community string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo snmp-ups -DDDD -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k The output with -DDDD is the same either way. > tcpdump to listen for packets...

...P or rather some telnet/expect scripting? > There are no serial ports to connect the UPS directly to one of > the blade servers... Seems like a similar user case to ESXi. If you've got a AP9630 card these notes may be useful. # APC ap9630 notes: # Use firmware 6.0.6 or later if you want SNMPv3 # Configuration->Shutdown # In "Start of Shutdown" section, set "Low Battery Duration" and # "Shutdown Delay" to get enough grace time for the ESXI shutdown # Optionally, in "End of Shutdown" section set "Return Delay" to 60 seconds. # Now here...

...In particular, no load, no input or output voltage. (And the runtime report is not to be trusted yet until I do a calibration run.) Is this to be expected from snmp-ups? (Also, I can so far connect only using snmpv1, but I don't know whether I should expect to get any additional data from snmpv3 anyway.) The HCL seems to imply that this UPS should *also* be supported by the powerpanel driver. However, I see from the documentation that the powerpanel driver is a lot of best-effort because cyberpower is uncommunicative about details of the protocol, and also I'm not seeing in the docu...

...gement cards for UPSes and such, where the important part is "will that UPS provide reliable power for a reasonable price", a secondary question is "can I monitor that thing in a reasonable way?", and a very very very minor influencing factor is "will the management card do SNMPv3, or SSH with o 2048 bit RSA key size"? Your extreme point of view is just unrealistic for such devices and vendors. > and I'm not sure what your bugaboo is about a fractured user base; at > any given time there are probably hundreds of different versions of > openssh being dist...

Hello all, I was asked about a proper way to ensure powerfail shutdown of a blade server fed off an APC SmartUPS, which is monitored by all hosts over SNMP. In particular, they'd like to avoid the "untimely" return of utility power - when the OSes are already shutting down, and would stay down because the UPS is well-fed now and thus won't power off and later power on to boot

...Not just security but better error handling and more. Good luck learning! On Thu, Mar 29, 2018 at 9:03 AM, Tomasz Chmielewski <mangoo at wpkg.org> wrote: > SNMP is mainly used for monitoring, not _server_ automation. > > Also, it's inherently insecure for anything else - only SNMPv3 offers any > kind of encryption, and it's DES - 56 bit only, and you can easily > brute-force it on an average computer. > > > If you could provide some serious articles about why is CLI insecure, I'd > be interested to read. > > > Tomasz Chmielewski > https://...