similar to: Looking for HP R3000 XR UPS firmware

Hi Matthijs, > Arnaud. >After some trial and error, i found out that the HP R3000 XR ups's we have >can be used with Network Ups Tools. >This using the bcmxcp driver. > >Note that in the code of this driver (line 1420) , the Baudrate is fixed to >9600 baud. >to connect to a serial HP R3000 XR ups one needs to change this to 19200 >baud. > >ideally, this should

Hi, So far I've gleaned heaps of useful info from the list and got mostly running with NUT. There was a thread by Paul Battaglia and Kjell Claesson about the R3000 which has helped me get so far, but now with the patched driver I still have this on startup: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS driver 0.11

Hi I have a HP R3000 XR UPS which NUT never says is at 100% battery. It seems stuck in 98 or 99 . something percentage. How accurate should i expect the reports to be? All my other UPSes has been and is at 100%, even those i have retired. My monitor system runs debian. The host that is physically connected to this ups runs: nut 2.2.2-6.4 The web script runs nut-cgi 2.0.4-4 JonB

Hi All, I'm trying to communication with the HP r3000 XR UP using the latest stable build and I'm getting the following errors. Can anyone enlighten me with the errors below and what other course of action I can take. Thanks in advance. Paul. [root@WRRFtpServer etc]# /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS

UPS: HP R3000 XR with HP UPS Management Module What I Want: I just want the UPS to shut down the client called "tor" before the UPS power drains out, I'd prefer to use a direct serial cable instead of network, in case the network doesn't work. I'll manage the UPS trough the ethernet using the built-in HTTP webinterface in the HP UPS Management Module. I've created a

I have setup nut-2.4.1 with the bcmxcp driver for my HP R3000 XR unit and although it appears to work, I receive the following sorts of errors in syslog: Aug 27 10:33:05 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27 10:33:15 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27

Hi! Have a similar issue with one of our customers having HP R12000/3 UPS with AF430A card. Upsmon shows the UPS as Online, on Battery and Battery discharging at the same time: [root at smrsrvslv06 lib64]# upsc hpups at localhost ambient.temperature: 19.0 ambient.temperature.high: 0.00 ambient.temperature.low: 0.00 battery.charge: 94.00 battery.current: 0.00 battery.runtime: 4620.00

Hello Arnaud, On 05/04/14 22:01, Arnaud Quette wrote: > Philippe, Ivan, > > please see https://github.com/networkupstools/nut/issues/118 > and send back your data. I've pasted the requested files in github, but the auto-formatting may have damaged them, so here they are. Also, when I ran gen-snmp-subdriver.sh, it gave me the following message:

Philippe, Ivan, please see https://github.com/networkupstools/nut/issues/118 and send back your data. cheers Arno -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140405/682f10dd/attachment-0001.html>

Additional question: I noticed on the HP Website that the latest version of "CPQPOWER.MIB" (1.76, dated Sept. 19, 2013) was more recent than the related file (./drivers/compaq-mib.c) in the NUT driver. Is the MIB structure as implemented on the management card perhaps no longer in line with the NUT driver ? The latest MIB file can be downloaded from the following URL:

Further information on this issue, attn. Arnaud Quette: Here is the result of a test I made a few days ago. I've pulled the input plug on the UPS and watched the 3 critical OIDs through a MIB browser: - 1.3.6.1.4.1.232.165.3.4.5.0 goes from 3 (OL) to 5 (OB) (as expected => good) - 1.3.6.1.4.1.232.165.3.7.3.0 stays at 1 (OB) (=> seems meaningless) - 1.3.6.1.4.1.232.165.3.7.4.0

Hello list, I've installed NUT on an HP blade server, and I try to get it communicating via SNMP with 2 HP R3000 UPSes, each fitted with a AF465A management card. To do this, I used the snmp-ups driver, and configured it for the "cpqpower" MIB. Communication with the UPSes is established. My problem is that both UPSes constantly return the "OL OB" status which, in

lejeczek via CentOS wrote: > hi guys > > does anybody here runs on HPE ProLiant? I was hoping you can tell whether > HPE support Linux Vendor > Firmware Service and you actually get to upgrade ProLiants' > BIOS/firmware via fwupdmgr? > > Dunno 'bout "Linux Vendor Firmware Service", but HPE support, ah, yeah... let's not go there. And they *really* want

On 01/07/2019 18:38, mark wrote: > lejeczek via CentOS wrote: >> hi guys >> >> does anybody here runs on HPE ProLiant? I was hoping you can tell whether >> HPE support Linux Vendor >> Firmware Service and you actually get to upgrade ProLiants' >> BIOS/firmware via fwupdmgr? >> >> > Dunno 'bout "Linux Vendor Firmware Service",

On 01/07/2019 17:42, lejeczek via CentOS wrote: > hi guys > > does anybody here runs on HPE ProLiant? > I was hoping you can tell whether HPE support Linux Vendor > Firmware Service and you actually get to upgrade ProLiants' > BIOS/firmware via fwupdmgr? > > many thanks, L. > > _______________________________________________ > CentOS mailing list > CentOS at

On Thu, 2 Feb 2017 16:28:12 +0530 Silambarasan Madhappan via samba <samba at lists.samba.org> wrote: > Hi , > > > We are facing below issue with below AD DC config - Samba 4.5.3 on > HP UX IA64 , > > > # ./smbclient -L localhost -U% > > Domain=[IN] OS=[Windows 6.1] Server=[Samba 4.5.3-HPE CIFS SERVER > 4.5.3.0] > > tree connect failed:

hi guys does anybody here runs on HPE ProLiant? I was hoping you can tell whether HPE support Linux Vendor Firmware Service and you actually get to upgrade ProLiants' BIOS/firmware via fwupdmgr? many thanks, L.

Hi , FQDN of the DC is Hostname.DomainName . In smb.conf: netbios name = <HostName> realm = <DomainName> eg: (ww.xx.yy.zz) workgroup = ww In resolve.conf domain <DomainName> nameserver <IP Address of the DC i.e host IP> # host -t SRV _ldap._tcp.<DomainName>. _ldap._tcp.<DomainName> has SRV record 0 100 389 <HostName>.<DomainName>. # host

> Just starting and trying to boot off the SPP firmware update ISO image > on a USB stick. > > I made the stick with: > > # mkfs.vfat /dev/sdb ^^^^^^^^^^^^^^^^^^^^ Why create an MS-DOS filesystem on the stick which gets immediately overwritten in the next step? > # dd bs=4M > if=P52581_001_gen10spp-2022.09.01.00-SPP2022090100.2022_0930.1.iso > of=/dev/sdb

Hi , We are facing below issue with below AD DC config - Samba 4.5.3 on HP UX IA64 , # ./smbclient -L localhost -U% Domain=[IN] OS=[Windows 6.1] Server=[Samba 4.5.3-HPE CIFS SERVER 4.5.3.0] tree connect failed: NT_STATUS_CONNECTION_DISCONNECTED # # cat /etc/opt/samba/smb.conf # Global parameters [global] netbios name = machinename realm = <MachineName>