- WLUG - wlug.mailman3.com

Re: [Wlug] monitoring a Matrix 3000

by Karl Hiramoto

Also, can you use either of those cables you have and make it work with a PC and M$ windows? That would close in on if you have a cable problem. On Mon, 3 Jun 2002, Bill Mills-Curran wrote: > I sent the message below to the UPS mailing list, but it's a pretty > slow list, so I thought I'd see if anyone on WLUG might have an idea. > I'm beginning to suspect a serial line configuration issue. > > Any ideas? > > Thanks, > Bill Mills-Curran > > > > ---------- Forwarded message ---------- > Date: Mon, 3 Jun 2002 08:29:56 -0400 (EDT) > To: Ups mailing list <ups(a)lists.exploits.org> > Subject: monitoring a Matrix 3000 > > Hi, > > I've installed the nut rpm's from the RedHat 7.2 distribution: > > nut-cgi-0.45.0-3 > nut-0.45.0-3 > nut-client-0.45.0-3 > > I am attempting to monitor the state of 2 APC Matrix UPS's; a model > 3000 and a model 5000. > > I have two different sets of cables to work with; 940-0020B and > 940-0024C. > > In short, I can't get any indication of communication between my linux > box and the UPS. I've looked through the FAQ's and other > documentation pretty carefully, but I must be missing something. Any > direction anyone can give would be appreciated. > > Documentation for these UPS's can be found at: > > http://sturgeon.apcc.com/techref.nsf/docID/3BF5FC2524F090888525675200631528… > > There's a description of the pinouts on p. 39. > > **************** > Basic setup: > > I have a couple of racks of inter-dependent equipment powered from 2 > UPS's. The interdependence forces me to shut down all machines before > either UPS fails. > > I plan to use a single linux box to monitor the state of the UPS's and > to send shutdown signals (via small private network) to the servers > when the battery gets low. > > The linux box is old hardware, but the linux software installation is > new. > > In an effort to simplify the problem, I've dropped back to monitoring > a single UPS. > > Below are the config files and results for using the two different > cable types. For both config's, I set the permissions on /dev/ttyS0 > to 666. > > **************** > Using the 940-0020B cables. > > Config files (without the comments): > > **** > # /etc/sysconfig/ups > SERVER=yes > MODEL=genericups > DEVICE=/dev/ttyS0 > OPTIONS="-t 2" > **** > # /etc/ups/upsd.conf > > UPS tls01 /usr/bin/genericups-ttyS0 -t 2 /dev/ttyS0 > ACL all 0.0.0.0/0 > ACL localhost 127.0.0.1/32 > ACCESS grant monitor localhost password > ACCESS deny all all > **** > # /etc/ups/upsmon.conf > > MONITOR tls01@localhost 1 password slave > MINSUPPLIES 1 > SHUTDOWNCMD "/root/bin/ups.pl shutdown" > NOTIFYCMD "/root/bin/ups.pl notify" > POLLFREQ 5 > POLLFREQALERT 5 > HOSTSYNC 15 > DEADTIME 15 > POWERDOWNFLAG /etc/killpower > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > ******* > Results: > > 1. The services (genericups, upsd, upsmonitor) started ok. I do get > the message: UPS tls01@localhost is unavailable > > 2. upsc tls01@localhost gives the following: > > host: tls01@localhost > No variables available! Check your upsd.conf entry for this UPS > > **************** > Using the 940-0024C cables. > > Config files (without the comments): > > **** > # /etc/sysconfig/ups > SERVER=yes > MODEL=apcsmart > DEVICE=/dev/ttyS0 > OPTIONS= > **** > # /etc/ups/upsd.conf > > UPS tls01 /usr/bin/apcsmart-ttyS0 /dev/ttyS0 > ACL all 0.0.0.0/0 > ACL localhost 127.0.0.1/32 > ACCESS grant monitor localhost password > ACCESS deny all all > **** > # /etc/ups/upsmon.conf > > MONITOR tls01@localhost 1 password slave > MINSUPPLIES 1 > SHUTDOWNCMD "/root/bin/ups.pl shutdown" > NOTIFYCMD "/root/bin/ups.pl notify" > POLLFREQ 5 > POLLFREQALERT 5 > HOSTSYNC 15 > DEADTIME 15 > POWERDOWNFLAG /etc/killpower > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > ******* > Results: > > 1. The services (apcsmart, upsd, upsmonitor) started ok. I do get > the message: UPS tls01@localhost is unavailable > > 2. upsc tls01@localhost gives the following: > > host: tls01@localhost > No variables available! Check your upsd.conf entry for this UPS > > **************** > > What am I doing wrong? > > TIA, > Bill > > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Karl Hiramoto <karl(a)hiramoto.org> Work: 978-425-2090 ext 25 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.org/ Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Facts are stubborn, but statistics are more pliable.

June 3, 2002

Re: [Wlug] monitoring a Matrix 3000

by Karl Hiramoto

Eliminate the basic stuff. Is the Serial port working? Hookup a null modem to another box and verify that. On Mon, 3 Jun 2002, Bill Mills-Curran wrote: > I sent the message below to the UPS mailing list, but it's a pretty > slow list, so I thought I'd see if anyone on WLUG might have an idea. > I'm beginning to suspect a serial line configuration issue. > > Any ideas? > > Thanks, > Bill Mills-Curran > > > > ---------- Forwarded message ---------- > Date: Mon, 3 Jun 2002 08:29:56 -0400 (EDT) > To: Ups mailing list <ups(a)lists.exploits.org> > Subject: monitoring a Matrix 3000 > > Hi, > > I've installed the nut rpm's from the RedHat 7.2 distribution: > > nut-cgi-0.45.0-3 > nut-0.45.0-3 > nut-client-0.45.0-3 > > I am attempting to monitor the state of 2 APC Matrix UPS's; a model > 3000 and a model 5000. > > I have two different sets of cables to work with; 940-0020B and > 940-0024C. > > In short, I can't get any indication of communication between my linux > box and the UPS. I've looked through the FAQ's and other > documentation pretty carefully, but I must be missing something. Any > direction anyone can give would be appreciated. > > Documentation for these UPS's can be found at: > > http://sturgeon.apcc.com/techref.nsf/docID/3BF5FC2524F090888525675200631528… > > There's a description of the pinouts on p. 39. > > **************** > Basic setup: > > I have a couple of racks of inter-dependent equipment powered from 2 > UPS's. The interdependence forces me to shut down all machines before > either UPS fails. > > I plan to use a single linux box to monitor the state of the UPS's and > to send shutdown signals (via small private network) to the servers > when the battery gets low. > > The linux box is old hardware, but the linux software installation is > new. > > In an effort to simplify the problem, I've dropped back to monitoring > a single UPS. > > Below are the config files and results for using the two different > cable types. For both config's, I set the permissions on /dev/ttyS0 > to 666. > > **************** > Using the 940-0020B cables. > > Config files (without the comments): > > **** > # /etc/sysconfig/ups > SERVER=yes > MODEL=genericups > DEVICE=/dev/ttyS0 > OPTIONS="-t 2" > **** > # /etc/ups/upsd.conf > > UPS tls01 /usr/bin/genericups-ttyS0 -t 2 /dev/ttyS0 > ACL all 0.0.0.0/0 > ACL localhost 127.0.0.1/32 > ACCESS grant monitor localhost password > ACCESS deny all all > **** > # /etc/ups/upsmon.conf > > MONITOR tls01@localhost 1 password slave > MINSUPPLIES 1 > SHUTDOWNCMD "/root/bin/ups.pl shutdown" > NOTIFYCMD "/root/bin/ups.pl notify" > POLLFREQ 5 > POLLFREQALERT 5 > HOSTSYNC 15 > DEADTIME 15 > POWERDOWNFLAG /etc/killpower > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > ******* > Results: > > 1. The services (genericups, upsd, upsmonitor) started ok. I do get > the message: UPS tls01@localhost is unavailable > > 2. upsc tls01@localhost gives the following: > > host: tls01@localhost > No variables available! Check your upsd.conf entry for this UPS > > **************** > Using the 940-0024C cables. > > Config files (without the comments): > > **** > # /etc/sysconfig/ups > SERVER=yes > MODEL=apcsmart > DEVICE=/dev/ttyS0 > OPTIONS= > **** > # /etc/ups/upsd.conf > > UPS tls01 /usr/bin/apcsmart-ttyS0 /dev/ttyS0 > ACL all 0.0.0.0/0 > ACL localhost 127.0.0.1/32 > ACCESS grant monitor localhost password > ACCESS deny all all > **** > # /etc/ups/upsmon.conf > > MONITOR tls01@localhost 1 password slave > MINSUPPLIES 1 > SHUTDOWNCMD "/root/bin/ups.pl shutdown" > NOTIFYCMD "/root/bin/ups.pl notify" > POLLFREQ 5 > POLLFREQALERT 5 > HOSTSYNC 15 > DEADTIME 15 > POWERDOWNFLAG /etc/killpower > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > ******* > Results: > > 1. The services (apcsmart, upsd, upsmonitor) started ok. I do get > the message: UPS tls01@localhost is unavailable > > 2. upsc tls01@localhost gives the following: > > host: tls01@localhost > No variables available! Check your upsd.conf entry for this UPS > > **************** > > What am I doing wrong? > > TIA, > Bill > > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Karl Hiramoto <karl(a)hiramoto.org> Work: 978-425-2090 ext 25 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.org/ Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø Facts are stubborn, but statistics are more pliable.

June 3, 2002

Re: [Wlug] monitoring a Matrix 3000

by Theo Van Dinter

On Mon, Jun 03, 2002 at 02:32:14PM -0400, Bill Mills-Curran wrote: > I sent the message below to the UPS mailing list, but it's a pretty > slow list, so I thought I'd see if anyone on WLUG might have an idea. > I'm beginning to suspect a serial line configuration issue. > > I have two different sets of cables to work with; 940-0020B and > 940-0024C. Well, in my recollection, the 20B is the grey "dumb" cable, and the 24C is the black "smart" cable. The Matrix is, I believe, essentially just a big SmartUPS. I would try using the 24C cable, then downloading PowerChute from the APC website (www.apcc.com) I'm currently using it on a SM700 and it works pretty well. Never messed around with a MatrixUPS before, so ... YMMV. -- Randomly Generated Tagline: DOS: n., A small annoying boot virus that causes random spontaneous system crashes, usually just before saving a massive project. Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS. (from David Vicker's .plan)

June 3, 2002

monitoring a Matrix 3000

by Bill Mills-Curran

I sent the message below to the UPS mailing list, but it's a pretty slow list, so I thought I'd see if anyone on WLUG might have an idea. I'm beginning to suspect a serial line configuration issue. Any ideas? Thanks, Bill Mills-Curran ---------- Forwarded message ---------- Date: Mon, 3 Jun 2002 08:29:56 -0400 (EDT) To: Ups mailing list <ups(a)lists.exploits.org> Subject: monitoring a Matrix 3000 Hi, I've installed the nut rpm's from the RedHat 7.2 distribution: nut-cgi-0.45.0-3 nut-0.45.0-3 nut-client-0.45.0-3 I am attempting to monitor the state of 2 APC Matrix UPS's; a model 3000 and a model 5000. I have two different sets of cables to work with; 940-0020B and 940-0024C. In short, I can't get any indication of communication between my linux box and the UPS. I've looked through the FAQ's and other documentation pretty carefully, but I must be missing something. Any direction anyone can give would be appreciated. Documentation for these UPS's can be found at: http://sturgeon.apcc.com/techref.nsf/docID/3BF5FC2524F090888525675200631528… There's a description of the pinouts on p. 39. **************** Basic setup: I have a couple of racks of inter-dependent equipment powered from 2 UPS's. The interdependence forces me to shut down all machines before either UPS fails. I plan to use a single linux box to monitor the state of the UPS's and to send shutdown signals (via small private network) to the servers when the battery gets low. The linux box is old hardware, but the linux software installation is new. In an effort to simplify the problem, I've dropped back to monitoring a single UPS. Below are the config files and results for using the two different cable types. For both config's, I set the permissions on /dev/ttyS0 to 666. **************** Using the 940-0020B cables. Config files (without the comments): **** # /etc/sysconfig/ups SERVER=yes MODEL=genericups DEVICE=/dev/ttyS0 OPTIONS="-t 2" **** # /etc/ups/upsd.conf UPS tls01 /usr/bin/genericups-ttyS0 -t 2 /dev/ttyS0 ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCESS grant monitor localhost password ACCESS deny all all **** # /etc/ups/upsmon.conf MONITOR tls01@localhost 1 password slave MINSUPPLIES 1 SHUTDOWNCMD "/root/bin/ups.pl shutdown" NOTIFYCMD "/root/bin/ups.pl notify" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 300 ******* Results: 1. The services (genericups, upsd, upsmonitor) started ok. I do get the message: UPS tls01@localhost is unavailable 2. upsc tls01@localhost gives the following: host: tls01@localhost No variables available! Check your upsd.conf entry for this UPS **************** Using the 940-0024C cables. Config files (without the comments): **** # /etc/sysconfig/ups SERVER=yes MODEL=apcsmart DEVICE=/dev/ttyS0 OPTIONS= **** # /etc/ups/upsd.conf UPS tls01 /usr/bin/apcsmart-ttyS0 /dev/ttyS0 ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCESS grant monitor localhost password ACCESS deny all all **** # /etc/ups/upsmon.conf MONITOR tls01@localhost 1 password slave MINSUPPLIES 1 SHUTDOWNCMD "/root/bin/ups.pl shutdown" NOTIFYCMD "/root/bin/ups.pl notify" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 300 ******* Results: 1. The services (apcsmart, upsd, upsmonitor) started ok. I do get the message: UPS tls01@localhost is unavailable 2. upsc tls01@localhost gives the following: host: tls01@localhost No variables available! Check your upsd.conf entry for this UPS **************** What am I doing wrong? TIA, Bill

June 3, 2002

Re: [Wlug] strange filenames

by Michael Frysinger

or just do what i do, rm ./--file_name -mike ----- Original Message ----- From: "Michelle Vadeboncoeur" <mrv(a)kluge.net> To: <wlug(a)mail.wlug.org> Sent: Saturday, May 25, 2002 11:55 Subject: Re: [Wlug] strange filenames > On Sat, 25 May 2002, Joe Riopel wrote: > > JR> If you want you can also open up midnight commander, just delete it > JR> that way. I had the same problem with a file named '-s' > > for files that start with a "-" character, to remove them you include a > "--" before the file name. > > for your example: rm -- -s > > I had to move and delete a bunch of files that were named with a "-" at > the beginning... Lots of graphics for a report for one of my math > classes... > > -- > --==*==-- --==*==-- Michelle R. Vadeboncoeur --==*==-- --==*==-- > mrv(a)kluge.net: http://www.kluge.net/~mrv/ > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

May 31, 2002

RE: [Wlug] weird ethernet problem...

by Keller, Tim

Well I'm running rh7.3 and I've got another box with this same card running 7.3 as well on the same network without a problem?? Weirdness. Tim. -----Original Message----- From: Charles R. Anderson [mailto:cra@WPI.EDU] Sent: Thursday, May 30, 2002 11:55 AM To: 'wlug(a)mail.wlug.org' Subject: Re: [Wlug] weird ethernet problem... On Thu, May 30, 2002 at 11:48:21AM -0400, Keller, Tim wrote: Tim.Keller> http://lists.us.dell.com/pipermail/linux-poweredge/2002-February/001688.html Tim.Keller> I also looked at the next message and I'm already running the eepro100 Tim.Keller> driver. Ahh. So it looks like it was a crappy card/driver problem after all. I did see somewhere else that you might want to download the driver from Intel and try that instead...of course I think that was the e100 they were referring to in that message :-/ -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 30, 2002

Re: [Wlug] weird ethernet problem...

by Charles R. Anderson

On Thu, May 30, 2002 at 11:48:21AM -0400, Keller, Tim wrote: Tim.Keller> http://lists.us.dell.com/pipermail/linux-poweredge/2002-February/001688.html Tim.Keller> I also looked at the next message and I'm already running the eepro100 Tim.Keller> driver. Ahh. So it looks like it was a crappy card/driver problem after all. I did see somewhere else that you might want to download the driver from Intel and try that instead...of course I think that was the e100 they were referring to in that message :-/ -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

May 30, 2002

RE: [Wlug] weird ethernet problem...

by Keller, Tim

I just changed the format of the netstat so it would be more readable. also, I found a message that accurately describes the problem... http://lists.us.dell.com/pipermail/linux-poweredge/2002-February/001688.html I also looked at the next message and I'm already running the eepro100 driver. Tim. -----Original Message----- From: Charles R. Anderson [mailto:cra@WPI.EDU] Sent: Thursday, May 30, 2002 11:36 AM To: 'wlug(a)mail.wlug.org' Subject: Re: [Wlug] weird ethernet problem... On Thu, May 30, 2002 at 11:16:48AM -0400, Keller, Tim wrote: Tim.Keller> here's what netstat -i gives me... Tim.Keller> Thanks, Tim.Keller> Tim. Tim.Keller> Tim.Keller> Iface: eth0 Tim.Keller> mtu: 1500 Tim.Keller> met: 0 Tim.Keller> rx-ok: 0 Tim.Keller> rx-err: 0 Tim.Keller> rx-drp: 0 Tim.Keller> rx-ovr: 0 Tim.Keller> tx-ok: 0 Tim.Keller> tx-err: 0 Tim.Keller> tx-ovr: 3 Tim.Keller> flg: BMRU That's a strange netstat. I've never seen output formatted like that before. tx-ovr (overruns) is the statistic to watch out for. What does lspci -v -v say about your ethernet card? Any other relavent dmesg output? -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 30, 2002

Re: [Wlug] weird ethernet problem...

by Charles R. Anderson

On Thu, May 30, 2002 at 11:16:48AM -0400, Keller, Tim wrote: Tim.Keller> here's what netstat -i gives me... Tim.Keller> Thanks, Tim.Keller> Tim. Tim.Keller> Tim.Keller> Iface: eth0 Tim.Keller> mtu: 1500 Tim.Keller> met: 0 Tim.Keller> rx-ok: 0 Tim.Keller> rx-err: 0 Tim.Keller> rx-drp: 0 Tim.Keller> rx-ovr: 0 Tim.Keller> tx-ok: 0 Tim.Keller> tx-err: 0 Tim.Keller> tx-ovr: 3 Tim.Keller> flg: BMRU That's a strange netstat. I've never seen output formatted like that before. tx-ovr (overruns) is the statistic to watch out for. What does lspci -v -v say about your ethernet card? Any other relavent dmesg output? -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

May 30, 2002

RE: [Wlug] weird ethernet problem...

by Keller, Tim

here's what netstat -i gives me... Thanks, Tim. Iface: eth0 mtu: 1500 met: 0 rx-ok: 0 rx-err: 0 rx-drp: 0 rx-ovr: 0 tx-ok: 0 tx-err: 0 tx-ovr: 3 flg: BMRU -----Original Message----- From: Charles R. Anderson [mailto:cra@WPI.EDU] Sent: Thursday, May 30, 2002 10:51 AM To: 'wlug(a)wlug.org' Subject: Re: [Wlug] weird ethernet problem... On Thu, May 30, 2002 at 10:08:52AM -0400, Keller, Tim wrote: Tim.Keller> NETDEV WATCHDOG: eth0: transmit timed out status 7088 0c00 at 241/301 Tim.Keller> command 001c000 Tim.Keller> Tim.Keller> the box has a Intel 10/100 Pro card running at 100 full duplex. Is the port the card is plugged into also running at full duplex? If autonegotiation is disabled on only one end of the link, you will have a duplex mismatch since the other end will fall back to half duplex. Always use autonegotiation on both ends, or on neither end. Any other errors? What does netstat -i show? Tim.Keller> I hooked up a win2k laptop configured it to the proper ip in the DMZ and it Tim.Keller> worked fine, so I know it's not the link. Try running tcpdump or ethereal on the link. I usually use tcpdump to write to a file, then copy it to my workstation and load it into ethereal there: server# tcpdump -i eth0 -s 1500 -w capture.pcap (the -s 1500 makes sure it captures the whole ethernet frames) I usually see these errors due to one of three reasons: 1. the netcard and/or driver is misconfigured (duplex, interrupt, etc.) 2. the netcard and/or driver is buggy or bad (usually seen on 3c503's :) 3. there is a TON of traffic on the network which is causing the card to not be able to keep up with the reception and transmission of all the packets. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

May 30, 2002