You can subscribe to this list here.
2000 |
Jan
(2) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(1) |
Aug
(26) |
Sep
(4) |
Oct
(7) |
Nov
(5) |
Dec
(19) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(7) |
Feb
(16) |
Mar
|
Apr
(12) |
May
(9) |
Jun
|
Jul
(23) |
Aug
(4) |
Sep
(8) |
Oct
(1) |
Nov
|
Dec
|
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2003 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: 'Ard v. Breemen' <ar...@te...> - 2001-07-25 15:09:33
|
On Wed, Jul 25, 2001 at 04:28:45PM +0200, 'Ard van Breemen' wrote: > On Wed, Jul 25, 2001 at 03:21:29PM +0200, 'Ard van Breemen' wrote: > > On Tue, Jul 24, 2001 at 11:26:11AM -0700, San Mehat wrote: > > > As I suspected, it looks like you're having a serial protocol issue.. > > > The reason that only the cisco boxes are qualified as a *network* based > > > connectivity method for EMP are that they have below 1 ms round trip > > > latency on single byte transactions on their raw ports... The EMP > > > protocol requires a MAXIMUM latency of 2ms per byte.. otherwise it will > > > timeout the byte (and sometimes the fame). It is VERY difficult to > > But how is the byte acked? What happens with modems? If I hook up a > > modem, the round trip will probably exceed that 2 ms due to compression > > and other stuff. We are after all talking about almost 4 byte-times. > Allright... > Debugging using tcpdump and ethereal. > My system send a byte to the portmaster. > 1.37 ms later the portmaster acks. > 53 ms later the portmasters sends a packet containing data. > Usually 1 byte as a reaction from my system. But sometimes up to 29 bytes. > But always 53 ms... > As if something was nagging... Or at least some timer seems to be involved... It get's worse: Enabled all emp debugging (like DEBUG_TRANS), the download still takes long, but other actions are currently fast. Refresh of the node will fail the first time. As if it tries to reconnect with a connection still open. The second time it works (maybe the connection is closed due to the failure of opening it :) ). Anyway: ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:124:JOB_STARTED EMP:124:CSTATUS:YES:NO:NO:NO:NO:YES:NO:NO:NO:NO:NO:YES:NO:NO:NO EMP:124:JOB_COMPLETED real 0m0.818s user 0m0.000s sys 0m0.000s ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:127:JOB_STARTED EMP:127:CSTATUS:YES:NO:NO:NO:NO:YES:NO:NO:NO:NO:NO:YES:NO:NO:NO EMP:127:JOB_COMPLETED real 0m0.528s user 0m0.000s sys 0m0.000s The .5 s is median. It either takes .5 s or .8 s. The download_log takes about the same time, but that is probably cached? -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ |
From: 'Ard v. Breemen' <ar...@te...> - 2001-07-25 14:28:51
|
On Wed, Jul 25, 2001 at 03:21:29PM +0200, 'Ard van Breemen' wrote: > On Tue, Jul 24, 2001 at 11:26:11AM -0700, San Mehat wrote: > > As I suspected, it looks like you're having a serial protocol issue.. > > The reason that only the cisco boxes are qualified as a *network* based > > connectivity method for EMP are that they have below 1 ms round trip > > latency on single byte transactions on their raw ports... The EMP > > protocol requires a MAXIMUM latency of 2ms per byte.. otherwise it will > > timeout the byte (and sometimes the fame). It is VERY difficult to > But how is the byte acked? What happens with modems? If I hook up a > modem, the round trip will probably exceed that 2 ms due to compression > and other stuff. We are after all talking about almost 4 byte-times. Allright... Debugging using tcpdump and ethereal. My system send a byte to the portmaster. 1.37 ms later the portmaster acks. 53 ms later the portmasters sends a packet containing data. Usually 1 byte as a reaction from my system. But sometimes up to 29 bytes. But always 53 ms... As if something was nagging... Or at least some timer seems to be involved... -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ |
From: 'Ard v. Breemen' <ar...@te...> - 2001-07-25 13:21:38
|
On Tue, Jul 24, 2001 at 11:26:11AM -0700, San Mehat wrote: > As I suspected, it looks like you're having a serial protocol issue.. > The reason that only the cisco boxes are qualified as a *network* based > connectivity method for EMP are that they have below 1 ms round trip > latency on single byte transactions on their raw ports... The EMP > protocol requires a MAXIMUM latency of 2ms per byte.. otherwise it will > timeout the byte (and sometimes the fame). It is VERY difficult to But how is the byte acked? What happens with modems? If I hook up a modem, the round trip will probably exceed that 2 ms due to compression and other stuff. We are after all talking about almost 4 byte-times. > recover a frame when this occurs, so we end up having to do nasty > re-synchronizing which doesn't always work... But if it needs to re-synchronize, it would tell me, right? It does not say anything about sync... (Hmmm, see the debugging commented out, recompiling...) > I would advise going to a rocketport connectivity solution since its > much cheaper than the cisco method... Well, another good solution would be a real power-boot :). -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ |
From: 'Ard v. Breemen' <ar...@te...> - 2001-07-25 12:13:13
|
On Tue, Jul 24, 2001 at 11:29:06AM -0700, San Mehat wrote: > We had done some initial investigating into the cyclades product to see > if this exact thing could be done... basically it appears that the box > is too underpowered to drive all the ports with the EMP state machine.. Hmmm, that is weird: I guess that with a 50MHz ppc, it is very easy to control 32 serial ports. > We noticed that the machine was so underpowered that it was taking a few > seconds for a connection to be acknowledged as closed by the box.. so > the port that was being listened() on was showing a connection *well* > after shutdown() was called on the socket.... not good... Well, time to look at the source code then.... Hmmm, hands start itching.. It sounds like somebody has programmed the box to generate interrupts for every port. This results on 19.2k (the emp speed) in 1920 interrupts per port per second, that is about 61440 interrupts... Even a pentium will not be able to handle that. > The cyclades box looks to be a good solution for serial console > redirection.. but it just doesn't look like it has the horsepower for > managing the EMP state machine.... Just a question of software.... Like in the old days. Then they did the same, just with less hardware :). > -san > Nope, all of the software that runs on the Cyclades TS1000 (16 port) and > TS2000 (32 port) term servers is open source. The main piece of software > that manages the ports is portslave or pslave. If you are curious the > flash image of exactly what is on them is available for download from > the Cyclades ftp site. Yes! Cool! Now I need the Cyclades itself, and unfortunately we already have serial console systems, so I cannot request one for my work :(... -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ |
From: Ben R. <br...@we...> - 2001-07-24 18:32:20
|
I was wondering if the change from making hardware and the neding of support would stop the development of VACM? Is this the case? Our are you a part of the SourceForge area that is staying in the realigned VALinux? I do not want to begin using the software if it is going away.... Ben Ricker System Administrator Wellinx.com |
From: San M. <net...@va...> - 2001-07-24 18:19:04
|
We had done some initial investigating into the cyclades product to see if this exact thing could be done... basically it appears that the box is too underpowered to drive all the ports with the EMP state machine.. We noticed that the machine was so underpowered that it was taking a few seconds for a connection to be acknowledged as closed by the box.. so the port that was being listened() on was showing a connection *well* after shutdown() was called on the socket.... not good... The cyclades box looks to be a good solution for serial console redirection.. but it just doesn't look like it has the horsepower for managing the EMP state machine.... -san -----Original Message----- From: vac...@li... [mailto:vac...@li...] On Behalf Of sa...@va... Sent: Tuesday, July 24, 2001 10:39 AM To: Ard van Breemen Cc: vac...@li... Subject: Re: [Vacm-general] Slow EMP handling On Tue, Jul 24, 2001 at 07:31:53PM +0200, Ard van Breemen wrote: > Is there a way to (runtime) limit the number of threads started, so that > I can strace, and see what exactly is going on? > The build I use is the wakkerma build: > http://people.debian.org/~wakkerma/vacm > > > The only serial concentrator qualified to work with VACM is a Cisco 36xx > > with 32 port async cards > > -san > Hmmm, the cyclades ts2000 sounds interesting. If we are able to strip > software that is not needed (like radius and stuff like that), and > implement some emp daemon, it could nicely handle all those emp ports, > and serial consoles... > (http://www.cyclades.com/products/stdalone/ts1_2000.htm) > But then again, it might all be cyclades proprietery software that runs > on linux... > Nope, all of the software that runs on the Cyclades TS1000 (16 port) and TS2000 (32 port) term servers is open source. The main piece of software that manages the ports is portslave or pslave. If you are curious the flash image of exactly what is on them is available for download from the Cyclades ftp site. -- Steven A. DuChene sdu...@mi... Racked Solutions Architect & Program Manager lin...@mi... _______________________________________________ Vacm-general mailing list Vac...@li... http://lists.sourceforge.net/lists/listinfo/vacm-general |
From: San M. <net...@va...> - 2001-07-24 18:16:09
|
Hey Ard, As I suspected, it looks like you're having a serial protocol issue.. The reason that only the cisco boxes are qualified as a *network* based connectivity method for EMP are that they have below 1 ms round trip latency on single byte transactions on their raw ports... The EMP protocol requires a MAXIMUM latency of 2ms per byte.. otherwise it will timeout the byte (and sometimes the fame). It is VERY difficult to recover a frame when this occurs, so we end up having to do nasty re-synchronizing which doesn't always work... I would advise going to a rocketport connectivity solution since its much cheaper than the cisco method... -san -----Original Message----- From: Ard van Breemen [mailto:ar...@te...] Sent: Tuesday, July 24, 2001 10:32 AM To: San Mehat Cc: vac...@li... Subject: Re: [Vacm-general] Slow EMP handling On Tue, Jul 24, 2001 at 09:59:56AM -0700, San Mehat wrote: > This is not normal.. please run nexxus with -l and send me the output.. Thanks, I needed to here it is not normal :) > you may have a serial concentrator problem (probably latency), causing > protocol errors... I've seen those errors, when I used telnet as the protocol.... But now: ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:3:JOB_STARTED vash: Nexxus 127.0.0.1 timed out waiting for IPC response real 0m50.113s user 0m0.000s sys 0m0.000s You have mail in /home/ard/Mail/.inbox ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:6:JOB_STARTED EMP:3:CSTATUS:YES:NO:NO:NO:NO:YES:NO:NO:NO:NO:NO:YES:NO:NO:NO EMP:3:JOB_COMPLETED real 0m38.015s user 0m0.000s sys 0m0.000s ard@c24574:/net/home/ard$ And in the log (used /var/log/vacm.log, since that is timestamped): [18:52:08][VACM] 2.0.5 Nexxus daemon (Build Jun 24 2001 23:21:50) [18:52:08][Nexxus] Standard Out Logging Enabled [18:52:08][Nexxus] Identified 11 modules [18:52:08][Nexxus] [Vasenet][0.5][VASENET][Zac Sprackett (za...@va...)] [18:52:08][Nexxus] [VA1000][1.1][VA1000][Jerry Katzung (ka...@va...)] [18:52:08][VA1000] Failed to open /dev/va1000_smbus: device does not exist! [18:52:08][Nexxus] [Sysstat][0.1][SYSSTAT][San Mehat (net...@va...)] [18:52:08][Nexxus] [BayTech][2.0][BAYTECH][Zac Sprackett (zsp...@va...)] [18:52:08][Nexxus] [EMP][2.0][EMP][San Mehat (net...@va...)] [18:52:08][Nexxus] [ICMP ECHO][1.0][ICMP_ECHO][San Mehat (net...@va...)] [18:52:08][Nexxus] [QUANTA][0.1][QUANTA][Zac Sprackett (za...@va...)] [18:52:08][Nexxus] [rsh][2.0][RSH][Dean Johnson (dt...@sg...) & Zac Sprackett (zsp...@va...)] [18:52:08][Nexxus] [SBT2][0.1][SBT2][Zac Sprackett (za...@va...)] [18:52:08][Nexxus] [SERCON][2.0][SERCON][San Mehat (net...@va...)] [18:52:08][Nexxus] [msc][2.0][MSC][Dean Johnson (dt...@sg...)] [18:52:08][SERCON] Unable to lookup 'c24574.telegraafnet.nl'. Connections unavailable (Unknown host) <snipped 17 more of these SERCON> [18:52:09][EMP] Thread rs0 protocol detected [18:52:13][EMP] Thread office protocol unavailable (Connection timed out) [18:53:04][Nexxus] Logging user blum in on client 17 from 127.0.0.1 [18:53:54][Nexxus] Logging user blum out on client 17 from 127.0.0.1 [18:54:01][Nexxus] Logging user blum in on client 17 from 127.0.0.1 [18:54:39][Nexxus] Logging user blum out on client 17 from 127.0.0.1 I've seen errors: [11:25:29][EMP] Thread rs0 received corrupt EMP data field (us 0x49, them 0x48) [11:25:29][EMP] Thread rs0 data c4 2c 10 20 78 11 00 10 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 48 a5 [11:25:30][EMP] Thread rs0 received corrupt EMP data field (us 0x45, them 0x44) [11:25:30][EMP] Thread rs0 data c4 2c 10 20 7c 11 00 10 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 44 a5 [11:25:30][EMP] Thread rs0 received corrupt EMP data field (us 0x45, them 0x44) [11:25:30][EMP] Thread rs0 data c4 2c 10 20 7c 11 00 10 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 44 a5 But these were the typical telnet instead of raw errors. And the following: ard@c24574:/net/home/ard$ sudo lsof -c emp.loose|grep pm2-0|wc -l 56 Is there a way to (runtime) limit the number of threads started, so that I can strace, and see what exactly is going on? The build I use is the wakkerma build: http://people.debian.org/~wakkerma/vacm > The only serial concentrator qualified to work with VACM is a Cisco 36xx > with 32 port async cards > -san Hmmm, the cyclades ts2000 sounds interesting. If we are able to strip software that is not needed (like radius and stuff like that), and implement some emp daemon, it could nicely handle all those emp ports, and serial consoles... (http://www.cyclades.com/products/stdalone/ts1_2000.htm) But then again, it might all be cyclades proprietery software that runs on linux... -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ |
From: <sa...@va...> - 2001-07-24 17:39:09
|
On Tue, Jul 24, 2001 at 07:31:53PM +0200, Ard van Breemen wrote: > Is there a way to (runtime) limit the number of threads started, so that > I can strace, and see what exactly is going on? > The build I use is the wakkerma build: > http://people.debian.org/~wakkerma/vacm > > > The only serial concentrator qualified to work with VACM is a Cisco 36xx > > with 32 port async cards > > -san > Hmmm, the cyclades ts2000 sounds interesting. If we are able to strip > software that is not needed (like radius and stuff like that), and > implement some emp daemon, it could nicely handle all those emp ports, > and serial consoles... > (http://www.cyclades.com/products/stdalone/ts1_2000.htm) > But then again, it might all be cyclades proprietery software that runs > on linux... > Nope, all of the software that runs on the Cyclades TS1000 (16 port) and TS2000 (32 port) term servers is open source. The main piece of software that manages the ports is portslave or pslave. If you are curious the flash image of exactly what is on them is available for download from the Cyclades ftp site. -- Steven A. DuChene sdu...@mi... Racked Solutions Architect & Program Manager lin...@mi... |
From: Ard v. B. <ar...@te...> - 2001-07-24 17:31:59
|
On Tue, Jul 24, 2001 at 09:59:56AM -0700, San Mehat wrote: > This is not normal.. please run nexxus with -l and send me the output.. Thanks, I needed to here it is not normal :) > you may have a serial concentrator problem (probably latency), causing > protocol errors... I've seen those errors, when I used telnet as the protocol.... But now: ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:3:JOB_STARTED vash: Nexxus 127.0.0.1 timed out waiting for IPC response real 0m50.113s user 0m0.000s sys 0m0.000s You have mail in /home/ard/Mail/.inbox ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:6:JOB_STARTED EMP:3:CSTATUS:YES:NO:NO:NO:NO:YES:NO:NO:NO:NO:NO:YES:NO:NO:NO EMP:3:JOB_COMPLETED real 0m38.015s user 0m0.000s sys 0m0.000s ard@c24574:/net/home/ard$ And in the log (used /var/log/vacm.log, since that is timestamped): [18:52:08][VACM] 2.0.5 Nexxus daemon (Build Jun 24 2001 23:21:50) [18:52:08][Nexxus] Standard Out Logging Enabled [18:52:08][Nexxus] Identified 11 modules [18:52:08][Nexxus] [Vasenet][0.5][VASENET][Zac Sprackett (za...@va...)] [18:52:08][Nexxus] [VA1000][1.1][VA1000][Jerry Katzung (ka...@va...)] [18:52:08][VA1000] Failed to open /dev/va1000_smbus: device does not exist! [18:52:08][Nexxus] [Sysstat][0.1][SYSSTAT][San Mehat (net...@va...)] [18:52:08][Nexxus] [BayTech][2.0][BAYTECH][Zac Sprackett (zsp...@va...)] [18:52:08][Nexxus] [EMP][2.0][EMP][San Mehat (net...@va...)] [18:52:08][Nexxus] [ICMP ECHO][1.0][ICMP_ECHO][San Mehat (net...@va...)] [18:52:08][Nexxus] [QUANTA][0.1][QUANTA][Zac Sprackett (za...@va...)] [18:52:08][Nexxus] [rsh][2.0][RSH][Dean Johnson (dt...@sg...) & Zac Sprackett (zsp...@va...)] [18:52:08][Nexxus] [SBT2][0.1][SBT2][Zac Sprackett (za...@va...)] [18:52:08][Nexxus] [SERCON][2.0][SERCON][San Mehat (net...@va...)] [18:52:08][Nexxus] [msc][2.0][MSC][Dean Johnson (dt...@sg...)] [18:52:08][SERCON] Unable to lookup 'c24574.telegraafnet.nl'. Connections unavailable (Unknown host) <snipped 17 more of these SERCON> [18:52:09][EMP] Thread rs0 protocol detected [18:52:13][EMP] Thread office protocol unavailable (Connection timed out) [18:53:04][Nexxus] Logging user blum in on client 17 from 127.0.0.1 [18:53:54][Nexxus] Logging user blum out on client 17 from 127.0.0.1 [18:54:01][Nexxus] Logging user blum in on client 17 from 127.0.0.1 [18:54:39][Nexxus] Logging user blum out on client 17 from 127.0.0.1 I've seen errors: [11:25:29][EMP] Thread rs0 received corrupt EMP data field (us 0x49, them 0x48) [11:25:29][EMP] Thread rs0 data c4 2c 10 20 78 11 00 10 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 48 a5 [11:25:30][EMP] Thread rs0 received corrupt EMP data field (us 0x45, them 0x44) [11:25:30][EMP] Thread rs0 data c4 2c 10 20 7c 11 00 10 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 44 a5 [11:25:30][EMP] Thread rs0 received corrupt EMP data field (us 0x45, them 0x44) [11:25:30][EMP] Thread rs0 data c4 2c 10 20 7c 11 00 10 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 44 a5 But these were the typical telnet instead of raw errors. And the following: ard@c24574:/net/home/ard$ sudo lsof -c emp.loose|grep pm2-0|wc -l 56 Is there a way to (runtime) limit the number of threads started, so that I can strace, and see what exactly is going on? The build I use is the wakkerma build: http://people.debian.org/~wakkerma/vacm > The only serial concentrator qualified to work with VACM is a Cisco 36xx > with 32 port async cards > -san Hmmm, the cyclades ts2000 sounds interesting. If we are able to strip software that is not needed (like radius and stuff like that), and implement some emp daemon, it could nicely handle all those emp ports, and serial consoles... (http://www.cyclades.com/products/stdalone/ts1_2000.htm) But then again, it might all be cyclades proprietery software that runs on linux... -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ |
From: San M. <net...@va...> - 2001-07-24 16:49:55
|
Hey Ard, This is not normal.. please run nexxus with -l and send me the output.. you may have a serial concentrator problem (probably latency), causing protocol errors... The only serial concentrator qualified to work with VACM is a Cisco 36xx with 32 port async cards -san -----Original Message----- From: vac...@li... [mailto:vac...@li...] On Behalf Of Ard van Breemen Sent: Tuesday, July 24, 2001 9:42 AM To: vac...@li... Subject: [Vacm-general] Slow EMP handling Hi, I'm just wondering if it is correct that EMP is *very* slow... Yes, using ipmi-ctl, it was already slow, but this: ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:refresh:rs0' EMP:22:JOB_STARTED EMP:22:STATUS:ENGAGING EMP:22:STATUS:PROTOCOL_DETECTED EMP:22:STATUS:CONNECTION_ACCEPTED EMP:22:STATUS:DOWNLOADING_FRU EMP:22:STATUS:DOWNLOADING_SDR vash: Nexxus 127.0.0.1 timed out waiting for IPC response real 1m37.677s user 0m0.000s sys 0m0.010s ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:25:JOB_STARTED EMP:22:STATUS:DOWNLOADING_SEL EMP:22:JOB_COMPLETED real 0m31.029s user 0m0.000s sys 0m0.010s Hmmm, a bug in vash? Doesn't it wait for the right job to complete? System setup: The emp module is connected through a portmaster using netdata configuration (==raw) to the emp port of a va2230. ard@c24574:/net/home/ard$ vash -c localhost -u blum -p frub -x 'ipc localhost em p:bmc_info:rs0' EMP:10:JOB_STARTED EMP:10:BMCINFO:1.14:Invalid IANA Number:0.9:1 EMP:10:JOB_COMPLETED Anyway, I wanted to check if it is normal to have to wait, say more than 1 minute, before power_off actually turns it off... Regards, Ard -vacm rookie- van Breemen -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ _______________________________________________ Vacm-general mailing list Vac...@li... http://lists.sourceforge.net/lists/listinfo/vacm-general |
From: Ard v. B. <ar...@te...> - 2001-07-24 16:42:14
|
Hi, I'm just wondering if it is correct that EMP is *very* slow... Yes, using ipmi-ctl, it was already slow, but this: ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:refresh:rs0' EMP:22:JOB_STARTED EMP:22:STATUS:ENGAGING EMP:22:STATUS:PROTOCOL_DETECTED EMP:22:STATUS:CONNECTION_ACCEPTED EMP:22:STATUS:DOWNLOADING_FRU EMP:22:STATUS:DOWNLOADING_SDR vash: Nexxus 127.0.0.1 timed out waiting for IPC response real 1m37.677s user 0m0.000s sys 0m0.010s ard@c24574:/net/home/ard$ time vash -c localhost -u blum -p frub -x 'ipc localhost emp:chassis_status:rs0' EMP:25:JOB_STARTED EMP:22:STATUS:DOWNLOADING_SEL EMP:22:JOB_COMPLETED real 0m31.029s user 0m0.000s sys 0m0.010s Hmmm, a bug in vash? Doesn't it wait for the right job to complete? System setup: The emp module is connected through a portmaster using netdata configuration (==raw) to the emp port of a va2230. ard@c24574:/net/home/ard$ vash -c localhost -u blum -p frub -x 'ipc localhost em p:bmc_info:rs0' EMP:10:JOB_STARTED EMP:10:BMCINFO:1.14:Invalid IANA Number:0.9:1 EMP:10:JOB_COMPLETED Anyway, I wanted to check if it is normal to have to wait, say more than 1 minute, before power_off actually turns it off... Regards, Ard -vacm rookie- van Breemen -- <ar...@te...> Telegraaf Elektronische Media http://wwwijzer.nl http://leerquoten.monster.org/ http://www.faqs.org/rfcs/rfc1855.html Let your government know you value your freedom. Sign the petition: http://petition.eurolinux.org/ |
From: Zac 'z. S. <za...@va...> - 2001-07-12 17:33:03
|
On Mon, Jul 09, 2001 at 03:01:20PM -0700, Tony Rose wrote: > Hi, > > We are using VACM and Vash in our server farm of 15 or > so front end servers. I must say that this is an incredible > tool and has saved us many trips and/or phone calls to the > co-lo facility!!! Thanks to the developers!!! > > Here is the problem that I am trying to solve... > > We have 2 machines that each have a rocketport, there is a nexxus > running on each of these and the nodes are split between these two > nexxi(?). Another machine, 'master' it's own binary of Vash to > connect to each nexxus. We want to be able to script some vacm > actions however vacm seems to not always respond, therefore we can > not rely on it for scripting just yet. Here is the error that we get > when we 'ping' each host with a nodestatus. > > vash: Unable to ping nexxus at 192.168.12.15 > vash: Unable to find connected Nexxus 192.168.12.15 > > and then, sometime later (usually immediately) it will work... > EMP:445:JOB_STARTED > EMP:445:NODESTATUS:/dev/ttyR16:DETECTED > EMP:445:JOB_COMPLETED > > this happens intermittently and does not seem to favor > certain nodes over others. If I do this on all 26 of our > nodes there will almost always be 1-3 nodes that respond > in this way. > > the 2 nexxus machines are Debian: > Linux mon-2 2.2.18 #1 SMP Wed Mar 14 11:48:40 PST 2001 i686 unknown > Linux mon-1 2.2.18 #1 SMP Wed Jun 20 12:06:32 PDT 2001 i686 unknown > > and the master machine is Debian: > Linux master 2.2.17 #1 SMP Tue Dec 19 16:07:50 PST 2000 i686 unknown > > I recently upgraded the version of VACM to 2.0.5 and it seems that > it helped some although it is still somewhat unstable. > > Any ideas on what could be causing this? It's a bug in vash and you called my attention to it. to.tv_sec = 5; to.tv_sec = 0; That looks like it would do it :) Are you running rpm's or did you build from source? I can give you an update, a new release is a bit of a ways out. -z -z |
From: Tony R. <tr...@lu...> - 2001-07-09 22:01:57
|
Hi, We are using VACM and Vash in our server farm of 15 or so front end servers. I must say that this is an incredible tool and has saved us many trips and/or phone calls to the co-lo facility!!! Thanks to the developers!!! Here is the problem that I am trying to solve... We have 2 machines that each have a rocketport, there is a nexxus running on each of these and the nodes are split between these two nexxi(?). Another machine, 'master' it's own binary of Vash to connect to each nexxus. We want to be able to script some vacm actions however vacm seems to not always respond, therefore we can not rely on it for scripting just yet. Here is the error that we get when we 'ping' each host with a nodestatus. vash: Unable to ping nexxus at 192.168.12.15 vash: Unable to find connected Nexxus 192.168.12.15 and then, sometime later (usually immediately) it will work... EMP:445:JOB_STARTED EMP:445:NODESTATUS:/dev/ttyR16:DETECTED EMP:445:JOB_COMPLETED this happens intermittently and does not seem to favor certain nodes over others. If I do this on all 26 of our nodes there will almost always be 1-3 nodes that respond in this way. the 2 nexxus machines are Debian: Linux mon-2 2.2.18 #1 SMP Wed Mar 14 11:48:40 PST 2001 i686 unknown Linux mon-1 2.2.18 #1 SMP Wed Jun 20 12:06:32 PDT 2001 i686 unknown and the master machine is Debian: Linux master 2.2.17 #1 SMP Tue Dec 19 16:07:50 PST 2000 i686 unknown I recently upgraded the version of VACM to 2.0.5 and it seems that it helped some although it is still somewhat unstable. Any ideas on what could be causing this? Thanks! -Tony -- $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ Tony Rose $ $ Senior Web Systems Administrator $ $ 650-616-3911 - tr...@lu... $ $ Free! Play for $1 Million every day!!!! $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ |
From: J C L. <cl...@ka...> - 2001-07-02 17:57:31
|
The EMP patch for 2.4.0 has problems (requires hacking to get a kernel that will build and then tends to lock the kernel during boot). Any chance of a patch against say 2.4.5? -- J C Lawrence cl...@ka... ---------(*) http://www.kanga.nu/~claw/ I never claimed to be human. |
From: San 'N. M. <net...@va...> - 2001-05-31 16:48:42
|
Hey Matthew, the ipmi driver source has been moved to the 'ipmitools' project on sourceforge... sorry about the confusion -san ----- Original Message ----- From: "Matthew Newton" <mn...@us...> To: <vac...@li...> Sent: Thursday, May 31, 2001 6:09 AM Subject: [Vacm-general] ipmi kernel patches in new 2.0.5 source? > Hi, > > I downloaded the vacm-2.0.5.tar.gz file from the sourceforge.net ftp site > and it looks like the emp extentd daemon patch files which I expected to > find in vacm-2.0.5/nexxus/nexxus_modules/emp/support_utilities are not > there. Did these get moved somewhere? The reason I ask is that I'm looking > for an ipmi patch for Linux kernel 2.4.0+, preferably 2.4.5. > > Thanks, > > Matt Newton > IT Architect > IBM Global Services > T.J. Watson Research Center > Tie Line 862-2174, External 914-945-2174 > mn...@us... > > > _______________________________________________ > Vacm-general mailing list > Vac...@li... > http://lists.sourceforge.net/lists/listinfo/vacm-general > |
From: Matthew N. <mn...@us...> - 2001-05-31 13:09:14
|
Hi, I downloaded the vacm-2.0.5.tar.gz file from the sourceforge.net ftp site and it looks like the emp extentd daemon patch files which I expected to find in vacm-2.0.5/nexxus/nexxus_modules/emp/support_utilities are not there. Did these get moved somewhere? The reason I ask is that I'm looking for an ipmi patch for Linux kernel 2.4.0+, preferably 2.4.5. Thanks, Matt Newton IT Architect IBM Global Services T.J. Watson Research Center Tie Line 862-2174, External 914-945-2174 mn...@us... |
From: Adam M. <ma...@si...> - 2001-05-09 14:28:23
|
On Wed, May 09, 2001 at 01:00:11AM -0400, sa...@va... wrote: > On Tue, May 08, 2001 at 08:50:33PM -0500, Adam Manthei wrote: > > OK, dumb question, but I'm not seeing it in the documentation. > > How do you exit from sercon_terminal? I just recently upgraded vacm from > > v2.0.0b3 to v2.0.5. Ctrl-C used to do it on v2.0.0b3. > > > > Ctrl-Atl-X This isn't the functionality that I'm looking for. Ctrl-Alt-x kills my window in X, and does nothing if I'm on a virtual terminal. I'm not using flim or hoover, just sercon_terminal, so I'd realy like to be able to escape out of sercon_terminal and be back in my shell. So far I have only found only one way to do this, and that is to kill sercon_terminal from another shell either by 'kill $PID' or 'ipc nexxus sercon:force_disconnect:$NODE:$FD' (I guess that's two ways :-) -- Adam Manthei <ma...@si...> |
From: <sa...@va...> - 2001-05-09 05:30:02
|
On Tue, May 08, 2001 at 09:06:11PM -0500, Adam Manthei wrote: > On Tue, May 08, 2001 at 08:50:33PM -0500, Adam Manthei wrote: > Ahh! Middle clicked into the mailer window! The question should be: > Are there suppsoe to be man pages installed with my RPM's. I can't seem to > find any man pages pretaining to the vacm commands. Bellow is a list of > RPM's that I have installed on my master and client nodes: > I believe all there is as far as docs is the stuff that is included in the vacm-doc rpm. You can see where that got deposited with: rpm -ql vacm-doc -- Steven A. DuChene sa...@va... Racked Solutions Architect & Program Manager VA Linux Systems http://www.valinux.com |
From: <sa...@va...> - 2001-05-09 05:00:17
|
On Tue, May 08, 2001 at 08:50:33PM -0500, Adam Manthei wrote: > OK, dumb question, but I'm not seeing it in the documentation. > How do you exit from sercon_terminal? I just recently upgraded vacm from > v2.0.0b3 to v2.0.5. Ctrl-C used to do it on v2.0.0b3. > Ctrl-Atl-X > Also, are there RPM's that should have been installed? I can't seem to find > any on my system. The following packages have been installed on the master > node: > vacm-2.0.5-1 > vacm-clientlib-2.0.5-1 > vacm-devel-2.0.5-1 > vacm-doc-2.0.5-1 > vacm-flim-2.0.5-1 > vacm-hoover-2.0.5-1 > vacm-sercon-2.0.5-1 > vacm-vash-2.0.5-1 > > and the folowing on the client nodes. > vacm-clientlib-2.0.5-1 > vacm-node-2.0.5-1 > vacm-vash-2.0.5-1 > That seems like a correct list to me. -- Steven A. DuChene sa...@va... Racked Solutions Architect & Program Manager VA Linux Systems http://www.valinux.com |
From: Adam M. <ma...@si...> - 2001-05-09 02:06:13
|
On Tue, May 08, 2001 at 08:50:33PM -0500, Adam Manthei wrote: > OK, dumb question, but I'm not seeing it in the documentation. > How do you exit from sercon_terminal? I just recently upgraded vacm from > v2.0.0b3 to v2.0.5. Ctrl-C used to do it on v2.0.0b3. > > Also, are there RPM's that should have been installed? I can't seem to find > any on my system. The following packages have been installed on the master > node: Ahh! Middle clicked into the mailer window! The question should be: Are there suppsoe to be man pages installed with my RPM's. I can't seem to find any man pages pretaining to the vacm commands. Bellow is a list of RPM's that I have installed on my master and client nodes: Master: > vacm-2.0.5-1 > vacm-clientlib-2.0.5-1 > vacm-devel-2.0.5-1 > vacm-doc-2.0.5-1 > vacm-flim-2.0.5-1 > vacm-hoover-2.0.5-1 > vacm-sercon-2.0.5-1 > vacm-vash-2.0.5-1 > > and the folowing on the client nodes. > vacm-clientlib-2.0.5-1 > vacm-node-2.0.5-1 > vacm-vash-2.0.5-1 > > Thanks. Sorry about the mental lapse. -- Adam Manthei <ma...@si...> |
From: Adam M. <ma...@si...> - 2001-05-09 01:50:36
|
OK, dumb question, but I'm not seeing it in the documentation. How do you exit from sercon_terminal? I just recently upgraded vacm from v2.0.0b3 to v2.0.5. Ctrl-C used to do it on v2.0.0b3. Also, are there RPM's that should have been installed? I can't seem to find any on my system. The following packages have been installed on the master node: vacm-2.0.5-1 vacm-clientlib-2.0.5-1 vacm-devel-2.0.5-1 vacm-doc-2.0.5-1 vacm-flim-2.0.5-1 vacm-hoover-2.0.5-1 vacm-sercon-2.0.5-1 vacm-vash-2.0.5-1 and the folowing on the client nodes. vacm-clientlib-2.0.5-1 vacm-node-2.0.5-1 vacm-vash-2.0.5-1 Thanks. -- Adam Manthei <ma...@si...> |
From: Dale H. <ro...@va...> - 2001-05-02 19:14:17
|
On Wed, May 02, 2001 at 12:22:56PM -0400, August Zajonc wrote: > We've got a bunch of identical machines... > > I'd love it if there was some way we could network ghost these. i.e., stick > a > floppy in each machine and have it suck a drive image over the network. > > How do people keep clusters synced up? rsync scripts? > > Also be interested in tricks to ghost hard drives on the cheap... is there a > software solution we could use? > > Thanks for any pointers, > > August > August, Check out Systemimager: http://systemimager.sf.net It'll do what you want. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dale Harris <ro...@va...> VA Linux Systems Senior Support Engineer 47071 Bayview Pkwy. (877) VA-LINUX Fremont, CA 94538 |
From: August Z. <au...@bi...> - 2001-05-02 16:23:48
|
We've got a bunch of identical machines... I'd love it if there was some way we could network ghost these. i.e., stick a floppy in each machine and have it suck a drive image over the network. How do people keep clusters synced up? rsync scripts? Also be interested in tricks to ghost hard drives on the cheap... is there a software solution we could use? Thanks for any pointers, August |
From: James L. <jim...@we...> - 2001-04-19 15:44:03
|
Hi All, I'm working with VACM and get the following: vash$ ipc localhost vasenet:vasenet_version:web02 VASENET:56:JOB_STARTED VASENET:56:JOB_ERROR:Transport endpoint is not connected vash$ ipc localhost vasenet:vasenet_version:web04 VASENET:57:JOB_STARTED VASENET:57:JOB_ERROR:Transport endpoint is not connected Does anyone know what might be happening here? Jim ------------------------------------------------------------------------ "Man is not a machine built after a model, but a tree that must develop on all sides according to its inward forces." -- John Stuart Mills Jim Louis <mailto:jim...@we...> Unix System Administrator Webhelp <http://www.webhelp.com> "Real People, Real Answers, Real Time" |
From: Ben R. <br...@we...> - 2001-04-18 20:21:56
|
I finally figured out how to get the daemons running on first node I want to monitor However, the docs do not tell you HOW to run them except to run the init.d script which I ran. But if you do not run the sysstat daemon from command line FIRST to set the password, it will not run through the init.d script. I had to dig to find where the rpm installed the systat daemon executable; the instructions are inadequate in this area. However, when I run flim and add the node, the status shows that there is 'No sysstat support on node'. Additionally, when I added the node, I put in the IP for the node in the new node box. However, if I quit flim and go back to it, there is no IP in there. Need there be a port designation in the node section? Why does it not recognize the sysstat daemon running on the server? Why does it lose the password when I quit? I really like the possibilities of this product, but the docs seem to be written assuming a more thorough knowledge of vacm then a newbiw to vacm would have. Ben Ricker System Administrator US-Rx, Inc. |