Displaying 20 results from an estimated 200 matches similar to: "APC AP9630 support AES ?"
2014 Mar 31
2
AP9630 AES Support
Hello again! Your suggestions the other day did work so thank you! I do
have one more question for you guys though. APC AP9630 SNMP monitoring card
is listed in the HCL and next to it there is privProtocol = AES. Does this
mean only AES works or AES doesn't work? I saw the archived mailing lists
were it looked like it only worked with the AES protocol, though in my set
up it works with
2014 Apr 04
0
AP9630 AES Support
On Mar 30, 2014, at 10:39 PM, Shade Alabsa wrote:
> Hello again! Your suggestions the other day did work so thank you! I do have one more question for you guys though. APC AP9630 SNMP monitoring card is listed in the HCL and next to it there is privProtocol = AES. Does this mean only AES works or AES doesn't work? I saw the archived mailing lists were it looked like it only worked with the
2019 Oct 08
0
APC AP9630 SNMP AES
Hello,
i'm trying to monitor a APC Smart-UPS 1000 behind a APC AP9630 Network
Management Card via SNMPv3 using the AES Privacy Protocol.
* OS name and version:
Debian 10.1
* exact NUT version:
2.7.4
* NUT installation method:
from debian package 2.7.4-8
* exact device name and related information
* Model Number AP9630
* Hardware Revision 08
* Manufacture Date
2013 Aug 22
1
SNMPv3
Updating an old thread. History here.
http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html
http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html
http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html
On Fri, 1 Feb 2013, Tim Rice wrote:
[snip]
>
> In all my testing I discovered the APC AP9630 is kind of flaky when
>
2016 Dec 20
2
NUT Client shuts down when performing runtime calibration on APC UPS
Hello,
I am using an APC UPS (Smart-UPS 2200 RM) to secure my SAN. The SAN runs on FreeBSD 9.1-RELEASE-p5 and is using NUT 2.6.5 version 2. Since the UPS has also a Network card AP9630 I am using the snmp-ups driver to connect the SAN to the UPS for signaling.
Last week I need to change the battery pack and then I needed to perform a runtime calibration. I used the web interface of the AP9630
2014 Feb 19
0
snmp-ups shutdowns
Hi Jim,
On Tue, 18 Feb 2014, Jim Klimov wrote:
> 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
2013 Oct 09
2
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
(Note that I mentioned this *was* previously working with an older version
of Nut).
[irs2-ups1]
driver = snmp-ups
port = irs2-ups1.sum.naoj.org
mibs = auto
community = private
irs2-ups1.sum.naoj.org responds to pings.
On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote:
> On Tue, 8 Oct 2013, Philip Tait wrote:
>
> > Here is the upsc
2011 Jun 13
1
NUT HCL List
Hi All!
Just an update! The snmp driver seems quite happy with an APC AP9618 managment
card in an APC Smart-UPS RT 5000 XL UPS.
I have an APC AP9630 to test in the near future so will give and update on
that one too!
Cheers
Ang
--
Angela Williams
angierfw at gmail dot com
Linux/Networking Hacker
Blog http://angierfw.wordpress.com
Smile! Jesus Loves You!
2013 Oct 09
0
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
On Tue, 8 Oct 2013, Philip Tait wrote:
> Here is the upsc output:
>
> # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1
> Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5)
> 0.000000 debug level is '2'
> 0.000327 SNMP UPS driver : entering upsdrv_initups()
[snip]
> 4.457750 No supported device detected
I'm using a APC smart ups with a
2018 Dec 06
1
battery.runtime
That's an idea Charlie.
The APC UPS I am using has an AP9630 card in it and pfSense is grabbing the snmp. I could try to use the USB cable on the FreeNAS so both could be masters.
----- Original Message -----
From: "Charles Lepple" <clepple at gmail.com>
To: "Danny Siminiuk" <daniel at siminiuk.com>
Cc: "nut-upsuser" <nut-upsuser at
2014 Feb 18
2
snmp-ups shutdowns
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
2013 Jan 29
1
SNMPv3
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
Trying to update the official docs for nut on FreeNAS - help needed to ensure it's written correctly
2018 Mar 30
2
Trying to update the official docs for nut on FreeNAS - help needed to ensure it's written correctly
This is slightly off-topic, I guess, but I'm not sure who better to ask for
help.
I'm active within the FreeNAS community and involved in their (FreeBSD
based) documentation work. There is a long standing bug ticket - years old
now - to update their "network ups tools" docs page, to cover Ethernet
attached UPS that use nut for the link. Currently the docs mainly describes
2013 Oct 09
2
Updated to 2.6.5, previously-working APC SmartUPS now fails completely
Here is the upsc output:
# /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1
Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5)
0.000000 debug level is '2'
0.000327 SNMP UPS driver : entering upsdrv_initups()
0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups)
0.056112 SNMP UPS driver : entering load_mib2nut(auto)
0.056126 trying the new
2014 Feb 19
2
snmp-ups shutdowns
On 2014-02-19 03:04, Tim Rice wrote:
> 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
> #
2018 Dec 04
2
battery.runtime
Hi Charles,
I don't think "ignorelb" will work in my case because that is set on the master. I am using the nut package in pfSense as the master and I want pfSense to shutdown on LOWBATT as designed.
I tried using upssched.conf with timers on the netclients but that's not appropriate because ONBATT by itself doesn't tell you how much capacity remains in the UPS. You still
2017 Jan 09
0
NUT Client shuts down when performing runtime calibration on APC UPS
Thanks for your reply.
Sorry for the delay, but until yet I haven't had a subscription, so I haven't seen your answer.
I can test this, I have three APC USVs, each equipped with the AP9630 network card.
I need to setup a Linux test VM with NUT first. I will give the feedback as soon as I can.
Oliver
________________________________
This email was scanned by Bitdefender
--------------
2018 Sep 21
0
AES-GCM with AES-NI
This is in regards to:
https://bugzilla.samba.org/show_bug.cgi?id=11451
https://bugzilla.samba.org/show_bug.cgi?id=13008
Would it be possible to find out the current state of AES-GCM mode for file shares?
Outside of Samba, CCM is typically slower and considered inferior to GCM
I apologize for formatting issues, I typically don’t use email lists.
In /source3/smbd/smb2_negprot.c lines 494 to
2003 Mar 17
1
ext3 over aes crypted loopback on partition
I'm looking at running an ext3 filesystem on top of a loopback AES
encrypted device, which in turn is on top of a raw partition (so no
other things in the way that should be reordering writes).
Are there likely to be any strange issues with using ext3 in this way?
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham@InTechnology.co.uk ]
[ - Comments in this message are my own and
2007 Jan 22
2
aes unsupported algorithm for ipsec?
Hi all,
I''m trying to create a IPsec tunnel from a Debian Etch machine to a
Cisco PIX. Part of my config is the following:
add x.x.x.x x.x.x.x esp 34501 -m tunnel -E aes-ctr "abcdefghijklmnop";
When I try to set this using setkey, it fails with the following message:
line 9: unsupported algorithm at [abcdefghijklmnop]
parse failed, line 9.
Can anyone tell me what