search for: silcon

Os is redhat enterprise, kernel 2.6.18-164.2.1.e15 NUT is apparently 2.4.1 It was installed by tar. Monitoring a lot of apc UPS units-mostly Smart-UPS of various flavors, also a Silcon DP380E. Normally works just fine... "upslog" writes status log every 30 seconds with various parameters.. Every so often, one of the UPS units has a log entry of: 20150812+035542+NA+NA+NA+[NA]+NA+NA+NA When it normally looks like: 20150813+114309+100.00+115.00+39.00+[OL]+25.00+60.00...

I have used NUT for many years to monitor our network connected UPS units...until recently they were all APC units. We replaced an old APC Silcon datacenter ups with a GE LP33 unit. It has a network card for web access and snmp support. How do I configure NUT to talk to the LP33 UPS unit? Thank you. -Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/a...

...============== SunSITE Denmark is located at Aalborg University, Institute of Electronic Systems, Denmark, and is running on a Sun Enterprise E3500 Server with 2 CPUs, 2 GB Memory and approximately 240 GB storage. The server was kindly donated by Sun Microsystems. Aalborg University, 3Com Nordic, Silcon Group, Cisco and CLARiiON are sponsoring the project. DISCLAIMER: Neither Aalborg University nor Sun Microsystems are liable for any use, storage or transmission of any files stored on this archive. IMPORTANT: We have limited the number of open connections to the ftp module to 5. If you are tryin...

On Aug 13, 2015, at 12:45 PM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Os is redhat enterprise, kernel 2.6.18-164.2.1.e15 > NUT is apparently 2.4.1 > It was installed by tar. > > Monitoring a lot of apc UPS units?mostly Smart-UPS of various flavors, also a Silcon DP380E. > > Normally works just fine? ?upslog? writes status log every 30 seconds with various parameters.. > > Every so often, one of the UPS units has a log entry of: > > 20150812+035542+NA+NA+NA+[NA]+NA+NA+NA > > When it normally looks like: > > 20150813+...

Hi all! I've been (very) out of the loop for a while, up to the point that I had completely missed that the mailing list has moved. Oh well. However, Kjell Claesson poked at me regarding the 3phase stuff, so I found out that I had missed the recent events. In any case, it seems that the situation is unchanged regarding 3phase support. As some of you remember I made a suggestion for a

...s, the function oid_compare() is present to filter out those cases. To make things worse, it seems to recurse onto next item if you provide it with a complete OID. As you might have guessed, this is not exactly foolproof. For example, instead of returning the number of output phases in our APC Silcon UPS it recurses a bit and decides that I should get the phase rotation flag instead. Not exactly helpful. My fix for this would be to use SNMP_MSG_GET instead and fix the OID table to include the correct OID:s instead. This would remove all recursion, thus removing the oid_compare()-kludge and...

...] status On Aug 13, 2015, at 12:45 PM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Os is redhat enterprise, kernel 2.6.18-164.2.1.e15 NUT is apparently > 2.4.1 It was installed by tar. > > Monitoring a lot of apc UPS units?mostly Smart-UPS of various flavors, also a Silcon DP380E. > > Normally works just fine? ?upslog? writes status log every 30 seconds with various parameters.. > > Every so often, one of the UPS units has a log entry of: > > 20150812+035542+NA+NA+NA+[NA]+NA+NA+NA > > When it normally looks like: > > 20150813+...

...; > 2 or 3 seconds will suffice, or specify to the carrier that the 3-way > > > > calling is to be denied for your lines. > > > > > > > > Hope this helps. > > > > > > > > ----- Original Message ----- > > > > From: <ghost@silcon.com> > > > > To: <asterisk-users@lists.digium.com> > > > > Sent: Thursday, July 08, 2004 4:55 AM > > > > Subject: [Asterisk-Users] Digium FXO Interfaces don't support > > groundstart??? > > > > > > > > > > > &gt...

Hello, I am having problems configuring a TDM400P 4 Port FXO card with groundstart signalling. The box has 2 X100P's, 1 TDM04B and 1 TDM40B. I can configure it for loopstart and it works, just not groundstart, which I need for this installation. What am I missing? Thanks! Mark /etc/zaptel.conf #two X100P FXO Cards # fxsls=1-2 # TDM400P 4 Port FXO (TDM04B) fxsgs=3-6 # TDM400P 4 Port