- WLUG - wlug.mailman3.com

Re: [Wlug] monitoring a Matrix 3000

by Karl Hiramoto

Bill, I've had problems with serial ports in the past. Usually a really dumb reasion for it not working. Verify the BIOS has the port turned on. With the default IO address and IRQ settings. Does a mouse work on the port? If you have a null modem cable. (Switches RX and TX lines) you can hook two computers together. Run terminal programs on each (with the same baud rate settings, no flow control). You should be able to type chars between the two boxes. Have minicom installed? can it open the port without an error? If you don't have a null modem cable/connector you can pick them up at most radio shacks. Or you could try communicating with an external modem. Running a redhat default kernel? Should work fine. If you compiled your own make sure you have the serial port setup correctly in your kernel config. Try chmod 666 /dev/ttyS0 Serial HOWTO: http://tldp.org/HOWTO/Serial-HOWTO.html Serial Laplink howto: http://tldp.org/HOWTO/Serial-Laplink-HOWTO/index.html Have a DOS bootdisk? You could try running an old skool terminal program like procomm or something like that. Or hypertermainal in M$ Windowz. Good luck. On Tue, 4 Jun 2002, Bill Mills-Curran wrote: > Karl, > > I agree that the serial port is the prime suspect. (I'm working the > serial port test you suggested) Can you give any hints as to what > might need to be configured? Note that this is a new installation, > and I've done nothing to set up the port. > > Any suggestions what configuration changes or module loads I might > need to enable traffic on ttyS0 and ttyS1? > > Thanks, > Bill > > On Mon, 3 Jun 2002, Karl Hiramoto wrote: > > > Date: Mon, 3 Jun 2002 15:53:02 -0400 (EDT) > > From: Karl Hiramoto <karl(a)zoop.org> > > Reply-To: wlug(a)mail.wlug.org > > To: Worcester Linux Users Group <wlug(a)mail.wlug.org> > > Subject: Re: [Wlug] monitoring a Matrix 3000 > > > > > > 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. > > > > _______________________________________________ > > Wlug mailing list > > Wlug(a)mail.wlug.org > > http://mail.wlug.org/mailman/listinfo/wlug > > > > _______________________________________________ > 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 ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø If life is a stage, I want some better lighting.

June 4, 2002

Re: [Wlug] Quick tape question...

by Adam ＠ Oak

Simple question (to eliminate the obvious): Is this happening with the norewind tape device? Is it possible you are accidently using the rewind device? -Adam On Tue, 4 Jun 2002, Keller, Tim wrote: > I've got an HP tape drive model C1537A that has the annoying trait of > rewinding itself automatically. > > Does anybody have any suggestions on ways to prevent this behavior? > > mt doesn't seem to have an option to turn this feature off. > > Thanks, > Tim. > > Not so randomly generated tagline: > "Meanwhile behind the facade of this innocent looking bookstore..." > - Some freaky dude who designed the sets for peewee's playhouse > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > "lingua machinationis creo, ergo sum" _____________________________________________ Adam Keck The Mathworks 508-647-7298 Natick, Ma www.mathworks.com FreeNIX/Backup/Unix Administrator _____________________________________________

June 4, 2002

RE: [Wlug] Quick tape question...

by Keller, Tim

Actually I just figured it out... if your tape device is /dev/st0 the non rewinding version is /dev/nst0 Tim. -----Original Message----- From: Keller, Tim [mailto:Tim.Keller@stratus.com] Sent: Tuesday, June 04, 2002 11:56 AM To: 'wlug(a)wlug.org' Subject: [Wlug] Quick tape question... I've got an HP tape drive model C1537A that has the annoying trait of rewinding itself automatically. Does anybody have any suggestions on ways to prevent this behavior? mt doesn't seem to have an option to turn this feature off. Thanks, Tim. Not so randomly generated tagline: "Meanwhile behind the facade of this innocent looking bookstore..." - Some freaky dude who designed the sets for peewee's playhouse _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

June 4, 2002

Quick tape question...

by Keller, Tim

I've got an HP tape drive model C1537A that has the annoying trait of rewinding itself automatically. Does anybody have any suggestions on ways to prevent this behavior? mt doesn't seem to have an option to turn this feature off. Thanks, Tim. Not so randomly generated tagline: "Meanwhile behind the facade of this innocent looking bookstore..." - Some freaky dude who designed the sets for peewee's playhouse

June 4, 2002

Re: [Wlug] Multiple mice on a laptop

by Nate Godin

Hmm... I did this a while back, setting up a serial trackball in addition to my PS2 mouse on my desktop... you have to load a the XInput module, and do some XF86Config tweaking... I don't have the config file I used anymore, but I recall figuring out how to do it by reading the XF86Config man page... here's an example... Here is an example of a ServerLayout section for a dual headed configuration with two mice: Section "ServerLayout" Identifier "Layout 1" Screen "MGA 1" Screen "MGA 2" RightOf "MGA 1" InputDevice "Keyboard 1" "CoreKeyboard" InputDevice "Mouse 1" "CorePointer" InputDevice "Mouse 2" "SendCoreEvents" Option "BlankTime" "5" EndSection My G4 Powerbook actually seems to be able to do this automatically, I'll go boot that over to Linux and post the XF86Config file... Nate -- Experience is not what happens to you; it is what you do with what happens to you. -- Aldous Huxley

June 4, 2002

Multiple mice on a laptop

by Adam Elliott

Hello, I've got a laptop that usually resides in a docking station at work, where it is connected to an ordinary wheelmouse. That works fine. When I take the laptop out of the docking station, disconnect the mouse, and start up Linux again (so using the touchpad), the pointer tends to go crazy. Now, I know the reason for this is the protocol is wrong in the XF86Config file. The wheelmouse uses IMPS/2 with 5 buttons (3+wheel), the touchpad PS/2 with 2 buttons. I can fix this by editing the XF86Config file appropriately, and the touchpad works fine. Now, my question is: Is there any way to get Linux to automatically figure out that the mouse is not attached, and so fall back on the touchpad? BTW, I've set up two "Pointer" sections in XF86Config, and just adjust the CorePointer line to reference the correct one. XFree doesn't like having two CorePointers. I'm using SuSE 7.3, XFree86 4.x if it matters. Thanks, -Adam

June 4, 2002

Re: [Wlug] monitoring a Matrix 3000

by Bill Mills-Curran

Karl, I agree that the serial port is the prime suspect. (I'm working the serial port test you suggested) Can you give any hints as to what might need to be configured? Note that this is a new installation, and I've done nothing to set up the port. Any suggestions what configuration changes or module loads I might need to enable traffic on ttyS0 and ttyS1? Thanks, Bill On Mon, 3 Jun 2002, Karl Hiramoto wrote: > Date: Mon, 3 Jun 2002 15:53:02 -0400 (EDT) > From: Karl Hiramoto <karl(a)zoop.org> > Reply-To: wlug(a)mail.wlug.org > To: Worcester Linux Users Group <wlug(a)mail.wlug.org> > Subject: Re: [Wlug] monitoring a Matrix 3000 > > > 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. > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

June 4, 2002

Re: [Wlug] FORSALE: DEC 3000 model 900 (fwd)

by Aaron Haviland

Chuck Homic said: > > Its 100 bucks OBO now... :-) > > Man, I wish I had room for more crap. I'd love to play with another > non-Intel system. I'm pretty sure Linux will run on it, but anyway.... > > Surely someone has noticed this part: > > > RGB video card w/21 inch RGB monitor > > OBO is a good deal for a 21 inch monitor, with or without an Alpha attached! > Someone should buy this. ;) from what I can tell, linux *won't* run on DEC 3000's... but NetBSD will. seems any attempts to port linux to that specific architecture stoped around kernel v2.2.10 and had a lot to do with the TURBOChannel stuff. (i usually go by debian's port listing to find out what architechtures work. http://debian.org/ports/alpha/sys_types) but man... (like i need another piece of crap in my bedroom) i want to try :) -- Aaron Haviland orion [at] tribble [dot] dyndns [dot] org orion [at] parsed [dot] net This sig. intentionally left blank.

June 4, 2002

RE: [Wlug] FORSALE: DEC 3000 model 900 (fwd)

by Chuck Homic

> Its 100 bucks OBO now... :-) Man, I wish I had room for more crap. I'd love to play with another non-Intel system. I'm pretty sure Linux will run on it, but anyway.... Surely someone has noticed this part: > RGB video card w/21 inch RGB monitor OBO is a good deal for a 21 inch monitor, with or without an Alpha attached! Someone should buy this. ;) -Chuck

June 4, 2002

Re: [Wlug] dual mother suggestons

by David Goss

http://www.intel.com/products/browse/motherbd.htm?iid=Homepage+Find_Products _Motherboards& I work with the STL2 & SCB2 boards. We manufacture for some drug companies and have thousands of these boards in the field. My experience with them is only as far as installing the O/S of which 90% is Wndoze ( NT 4.). The boards I have installed Linux ( Red Hat 7.0-3 ) have been nice to work with. Intel support is good as well. Not trying to plug them but you do get what you pay for and these boards have proven reliable albeit expensive. Hope that helps. Dave Goss Assimilation is futile. ----- Original Message ----- From: <bryon3245(a)netzero.com> To: <wlug(a)mail.wlug.org> Sent: Monday, June 03, 2002 7:33 PM Subject: [Wlug] dual mother suggestons > Dear WLUG Mailing list readers, > > I would appreciate it if you could help me by suggesting a good quality dual Intel p4 (fastest possible) motherboard. > > Thanks, > Bryon > > > > -------------------------------------------------------------------- > mail2web - Check your email from the web at > http://mail2web.com/ . > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug

June 4, 2002

dual mother suggestons

by bryon3245＠netzero.com

Dear WLUG Mailing list readers, I would appreciate it if you could help me by suggesting a good quality dual Intel p4 (fastest possible) motherboard. Thanks, Bryon -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

June 3, 2002

FORSALE: DEC 3000 model 900 (fwd)

by Phillip G Deneault

When I said 'OBO'....I meant it.. :-) Its 100 bucks OBO now... :-) Phil -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Phil Deneault "We work in the dark, We do what we can, deneault(a)wpi.edu We give what we have. Our doubt is our passion, WPI NetOps and our passion is our task. The rest is the OpenVMS Guy maddness of art." - Henry James -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ---------- Forwarded message ---------- Date: Wed, 29 May 2002 15:11:05 -0400 (EDT) From: Phillip G Deneault <deneault(a)wpi.edu> To: wlug(a)mail.wlug.org Subject: FORSALE: DEC 3000 model 900 Full size DEC 3000 model 900 275mhz Alpha 128 megs of RAM 7 internal drive bays 50-pin SCSI, 2 bus chains 1 4 gig hard drive, 1 dual speed caddy CD-ROM built in ethernet RGB video card w/21 inch RGB monitor cables, mice, keyboards, etc Works well, provided as is...$300 obo I run Tru64 on it and I am not sure if Linux will run on it. Any questions e-mail me Phil -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Phil Deneault "We work in the dark, We do what we can, deneault(a)wpi.edu We give what we have. Our doubt is our passion, WPI NetOps and our passion is our task. The rest is the OpenVMS Guy maddness of art." - Henry James -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

June 3, 2002

Re: [Wlug] Wireless nics and linux.

by Jeremy

I had a orinoco card working under linux a while ago.. It seemed to work well at my wireless net in worcester. It varies from card to card: DLINK has linux drivers, lucent has unoffical ports (orinoco cards), 3Com used to have one, but it was a rebrand of another card (symbol S24) Anyone else using lucent cards? if you can afford i would recommend 'em. I bought a 3Com card orginally and thought it would be good, but had quality issues. So I got the Lucent card and am much happier. DLINK is surprising good, but not sure about the linux support. --- Wesley Allen <wallen(a)charter.net> wrote: > Hi All, > I may be FINALLY getting some wireless access in my house (It's amazing > what a simple furniture move can accomplish). So I'm wondering, what > wireless nics work in Linux. I've heard that there are some problems, > do any of you have 802.11b networks at home (what's the mac address > range.....wink)? If so, what nics are you using. Do the USB one's work > (actually, I'll check this one out on my own, it's the pcmcia cards I > need the info on). > > Thanks, > Wes > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug ===== - __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com

June 3, 2002

Re: [Wlug] monitoring a Matrix 3000

by stoffel＠lucent.com

Bill> I sent the message below to the UPS mailing list, but it's a pretty Bill> slow list, so I thought I'd see if anyone on WLUG might have an idea. Bill> I'm beginning to suspect a serial line configuration issue. I'm using apcupsd at home with a Matrix SmartUPS and it works just great. Have you tried that package? Also, making sure the cable and serial ports are working first is a good thing too. I may be able to find a cable or two since we've stopped using Matrix 3k/5k here now that we have a generator. Life is trully good now. John John Stoffel - Senior Unix Systems Administrator - Lucent Technologies stoffel(a)lucent.com - http://www.lucent.com - 978-399-0479

June 3, 2002

Wireless nics and linux.

by Wesley Allen

Hi All, I may be FINALLY getting some wireless access in my house (It's amazing what a simple furniture move can accomplish). So I'm wondering, what wireless nics work in Linux. I've heard that there are some problems, do any of you have 802.11b networks at home (what's the mac address range.....wink)? If so, what nics are you using. Do the USB one's work (actually, I'll check this one out on my own, it's the pcmcia cards I need the info on). Thanks, Wes

June 3, 2002

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