Menu
▾
▴
vacm-general
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: Jeremy H. <je...@xx...> - 2000-08-22 21:33:13
|
So I'm playing with vacm, it's great, this is obvious, so now I'm trying to do a little research on how we would roll something like this into our production environment. Serial cards? What are people using? I'm looking for low cost things. Although I think I can justify the cost just by showing people the advantages to control over EMP, telling the boss that we have to spend $1500 on a serial card for support only 16 machines *might* be a little touchy. I don't know. Thanks -jeremy http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 18:22:45
|
Ok, well the IPMI_KCS driver is loaded, but nothing shows up in proc webtest3: root:~ 97>lsmod Module Size Used by lockd 44880 0 (autoclean) (unused) sunrpc 57316 0 (autoclean) [lockd] ipmi_kcs 5084 0 (unused) webtest3: root:~ 99>ls /proc/ip* ls: /proc/ip*: No such file or directory dmesg: IPMI KCS driver (San Mehat net...@va...) v0.10 at io 0xca2 --Using 4096 byte ring buffer for incomming IPMI data --Polling frequency set to 10 ticks Thanks -jeremy > Jeremy, > > Make sure you are using BMC version 1.14 as your firmware if you're using a > Lancewood class motherboard. Older revisions of this firmware may hang up > on a POWER OFF. > > You can check which version you're using by installing the IPMI_KCS driver > and catting /proc/ipmi > > -san > On Mon, Aug 21, 2000 at 09:53:20PM -0400, Jeremy Hansen wrote: > > > > Here's a little session just to show that I am getting emp information, > > but as soon as I try to do a POWER_OFF, that's the last command I can > > issue: > > > > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > > EMP:4:JOB_STARTED > > EMP:4:CCAPABLE:YES:YES:YES:NO > > EMP:4:JOB_ERROR:Unknown Condition Code > > vash$ ipc localhost EMP:POWER_OFF:webtest3 > > EMP:5:JOB_STARTED > > vash$ > > vash$ > > vash$ > > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > > EMP:6:JOB_STARTED > > vash$ > > vash$ > > > > and that's it... > > > > -jeremy > > > > > Jeremy Hansen wrote: > > > > > > > > I actually figured out that I had console redirection turn on the nexxus > > > > controller, so that was screwing it up. Turn it off and the command > > > > completed and I was able to get EMP information. > > > > > > > > So then I ran into another issue. I tried to issue the POWER_OFF command, > > > > and then EMP or nexxus stopped responding and never returned a status. > > > > > > > > > > Never seen that. > > > > > > > > > > > Question, has anyone seen any weirdness with EMP and bios versions? The > > > > machines I'm trying this stuff on seem to have fairly old revision of the > > > > bios. I'm going through the upgrade right now, but I thought perhaps it > > > > could be related, or I'm just doing something wrong :-) > > > > > > > > > > I am taking a silly guess here, but I don't think that the EMP has > > > anything to do with BIOS, given that it functions when the machine is > > > turned off (yet plugged in). I could certainly be wrong about that. > > > > > > -Dean > > > > > > > > > > http://www.xxedgexx.com * je...@xx... > > ---------------------------------------------- > > > > > > > > > > _______________________________________________ > > Vacm-general mailing list > > Vac...@li... > > http://lists.sourceforge.net/mailman/listinfo/vacm-general > > -- > ----------------------------------------------- > San-Respect-my-.Xauthoritah-Mehat > Principal Engineer & Digital Groovemaster > VA Linux Systems > net...@va... > 408-542-8654 > ----------------------------------------------- > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: San N. M. <net...@va...> - 2000-08-22 18:20:25
|
On Tue, Aug 22, 2000 at 12:12:49AM -0400, Jeremy Hansen wrote: > > So, does it make sense that things started working properly after doing > the refresh? > Not really.. once i land in toronto ill see if theres something wrong... > Flim is really cool btw. Will this continue to expand or is further work > being down with hoover? > > Thanks > -jeremy > > > If the node is already configured and you send a configuration message which > > contains identical values (serial port / password), the emp module will send > > back a JOB_COMPLETED message but will not actually do anything. It's already > > configured in that manner so it basically just returns ok. When you send a > > REFRESH command, you force a renegotiation. > > > > Zac > > > > > > _______________________________________________ > > Vacm-general mailing list > > Vac...@li... > > http://lists.sourceforge.net/mailman/listinfo/vacm-general > > > > > > http://www.xxedgexx.com * je...@xx... > ---------------------------------------------- > > > _______________________________________________ > Vacm-develop mailing list > Vac...@li... > http://lists.sourceforge.net/mailman/listinfo/vacm-develop -- ----------------------------------------------- San-Respect-my-.Xauthoritah-Mehat Principal Engineer & Digital Groovemaster VA Linux Systems net...@va... 408-542-8654 ----------------------------------------------- |
|
From: San N. M. <net...@va...> - 2000-08-22 18:15:42
|
Jeremy, Make sure you are using BMC version 1.14 as your firmware if you're using a Lancewood class motherboard. Older revisions of this firmware may hang up on a POWER OFF. You can check which version you're using by installing the IPMI_KCS driver and catting /proc/ipmi -san On Mon, Aug 21, 2000 at 09:53:20PM -0400, Jeremy Hansen wrote: > > Here's a little session just to show that I am getting emp information, > but as soon as I try to do a POWER_OFF, that's the last command I can > issue: > > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > EMP:4:JOB_STARTED > EMP:4:CCAPABLE:YES:YES:YES:NO > EMP:4:JOB_ERROR:Unknown Condition Code > vash$ ipc localhost EMP:POWER_OFF:webtest3 > EMP:5:JOB_STARTED > vash$ > vash$ > vash$ > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > EMP:6:JOB_STARTED > vash$ > vash$ > > and that's it... > > -jeremy > > > Jeremy Hansen wrote: > > > > > > I actually figured out that I had console redirection turn on the nexxus > > > controller, so that was screwing it up. Turn it off and the command > > > completed and I was able to get EMP information. > > > > > > So then I ran into another issue. I tried to issue the POWER_OFF command, > > > and then EMP or nexxus stopped responding and never returned a status. > > > > > > > Never seen that. > > > > > > > > Question, has anyone seen any weirdness with EMP and bios versions? The > > > machines I'm trying this stuff on seem to have fairly old revision of the > > > bios. I'm going through the upgrade right now, but I thought perhaps it > > > could be related, or I'm just doing something wrong :-) > > > > > > > I am taking a silly guess here, but I don't think that the EMP has > > anything to do with BIOS, given that it functions when the machine is > > turned off (yet plugged in). I could certainly be wrong about that. > > > > -Dean > > > > > > http://www.xxedgexx.com * je...@xx... > ---------------------------------------------- > > > > > _______________________________________________ > Vacm-general mailing list > Vac...@li... > http://lists.sourceforge.net/mailman/listinfo/vacm-general -- ----------------------------------------------- San-Respect-my-.Xauthoritah-Mehat Principal Engineer & Digital Groovemaster VA Linux Systems net...@va... 408-542-8654 ----------------------------------------------- |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 16:40:03
|
I built it myself. Figured that was best since 7.0 changes some libraries and things, like realine and curses and such. -jeremy > Hrm... did you build it yourself or install from rpms? I've never played > with a 7.0 beta system... > > -- > VACM - Couldn't Your SysAdmin Use Some Beauty Sleep? > > http://vacm.sourceforge.net > > _______________________________________________ > Vacm-general mailing list > Vac...@li... > http://lists.sourceforge.net/mailman/listinfo/vacm-general > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: <zsp...@va...> - 2000-08-22 12:40:49
|
On Tue, Aug 22, 2000 at 01:54:23AM -0400, Jeremy Hansen wrote: > > I realize that 7.0 is beta, etc, but I just thought I'd pass along that > I'm having some issue on a 7.0 beta machine. Maybe it's important, maybe > not. > > Basically for some reason I just can't get vash to connect: > > adsl-63-206-195-31:~# vash -c localhost -u blum -p frub > select: Invalid argument > vash: Unable to ping nexxus at localhost > vash$ > > nothing shows up in the logs. nexxus is running. Hrm... did you build it yourself or install from rpms? I've never played with a 7.0 beta system... -- VACM - Couldn't Your SysAdmin Use Some Beauty Sleep? http://vacm.sourceforge.net |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 05:54:37
|
I realize that 7.0 is beta, etc, but I just thought I'd pass along that I'm having some issue on a 7.0 beta machine. Maybe it's important, maybe not. Basically for some reason I just can't get vash to connect: adsl-63-206-195-31:~# vash -c localhost -u blum -p frub select: Invalid argument vash: Unable to ping nexxus at localhost vash$ nothing shows up in the logs. nexxus is running. -jeremy http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 04:12:59
|
So, does it make sense that things started working properly after doing the refresh? Flim is really cool btw. Will this continue to expand or is further work being down with hoover? Thanks -jeremy > If the node is already configured and you send a configuration message which > contains identical values (serial port / password), the emp module will send > back a JOB_COMPLETED message but will not actually do anything. It's already > configured in that manner so it basically just returns ok. When you send a > REFRESH command, you force a renegotiation. > > Zac > > > _______________________________________________ > Vacm-general mailing list > Vac...@li... > http://lists.sourceforge.net/mailman/listinfo/vacm-general > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: <zsp...@va...> - 2000-08-22 03:44:44
|
On Mon, Aug 21, 2000 at 10:39:23PM -0400, Jeremy Hansen wrote: > > Well, I'm not sure what I did exactly, but it's working. I was able to > power off and power on a machine over EMP. The only thing I can think of > is that I did a EMP:REFRESH. Does this do anything? REFRESH instructs the emp thread for a node to attempt to renegotiate a connection. > >From the quickstart it leads me to believe that when initially configuring > the EMP module, I should have seen output like this: > > vash$ ipc localhost emp:configuration:www:/dev/ttyS1:NONE > EMP:18:JOB_STARTED > EMP:18:STATUS:ENGAGING > EMP:18:STATUS:PROTOCOL_DETECTED > EMP:18:STATUS:CONNECTION_ACCEPTED > EMP:18:STATUS:DOWNLOADING_FRU > EMP:18:STATUS:DOWNLOADING_SDR > EMP:18:STATUS:DOWNLOADING_SEL > EMP:18:JOB_COMPLETED > > which I did not. I only saw job start then job completed. BUt, then I > did the refresh, this is when I saw all this information. If the node is already configured and you send a configuration message which contains identical values (serial port / password), the emp module will send back a JOB_COMPLETED message but will not actually do anything. It's already configured in that manner so it basically just returns ok. When you send a REFRESH command, you force a renegotiation. Zac |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 02:39:26
|
Well, I'm not sure what I did exactly, but it's working. I was able to power off and power on a machine over EMP. The only thing I can think of is that I did a EMP:REFRESH. Does this do anything? From the quickstart it leads me to believe that when initially configuring the EMP module, I should have seen output like this: vash$ ipc localhost emp:configuration:www:/dev/ttyS1:NONE EMP:18:JOB_STARTED EMP:18:STATUS:ENGAGING EMP:18:STATUS:PROTOCOL_DETECTED EMP:18:STATUS:CONNECTION_ACCEPTED EMP:18:STATUS:DOWNLOADING_FRU EMP:18:STATUS:DOWNLOADING_SDR EMP:18:STATUS:DOWNLOADING_SEL EMP:18:JOB_COMPLETED which I did not. I only saw job start then job completed. BUt, then I did the refresh, this is when I saw all this information. Does this mean anything? I'm done until tomorrow :-) Thanks -jeremy > > Hmm, now I'm getting a lot of this: > > vash$ ipc localhost EMP:CHASSIS_STATUS:webtest3 > EMP:22:JOB_STARTED > EMP:22:JOB_ERROR:Protocol not available > > and this appear in the logs: > > [12:07:11][Nexxus] [EMP][2.0][EMP][San Mehat (net...@va...)] > [12:07:16][EMP] Thread webtest3 protocol unavailable (Connection timed > out) > > SEL:IMLW00902615:0x5003:System Event Record:0x00000003:IPMB addr 0x10 (LUN > 0):0x02:Physical Security:Unknown Sensor Name:State Asserted > SEL:IMLW00902615:0x6003:System Event Record:0x39a17877:SSID > 0x8:0x02:System Event:Unknown Sensor Name:No Description Available > SEL:IMLW00902615:0x5003:System Event Record:0x00000003:IPMB addr 0x10 (LUN > 0):0x02:Physical Security:Unknown Sensor Name:State Asserted > SEL:IMLW00902615:0x5003:System Event Record:0x39a178da:SSID > 0x8:0x02:System Event:Unknown Sensor Name:No Description Available > > -jeremy > > > > > Here's a little session just to show that I am getting emp information, > > but as soon as I try to do a POWER_OFF, that's the last command I can > > issue: > > > > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > > EMP:4:JOB_STARTED > > EMP:4:CCAPABLE:YES:YES:YES:NO > > EMP:4:JOB_ERROR:Unknown Condition Code > > vash$ ipc localhost EMP:POWER_OFF:webtest3 > > EMP:5:JOB_STARTED > > vash$ > > vash$ > > vash$ > > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > > EMP:6:JOB_STARTED > > vash$ > > vash$ > > > > and that's it... > > > > -jeremy > > > > > Jeremy Hansen wrote: > > > > > > > > I actually figured out that I had console redirection turn on the nexxus > > > > controller, so that was screwing it up. Turn it off and the command > > > > completed and I was able to get EMP information. > > > > > > > > So then I ran into another issue. I tried to issue the POWER_OFF command, > > > > and then EMP or nexxus stopped responding and never returned a status. > > > > > > > > > > Never seen that. > > > > > > > > > > > Question, has anyone seen any weirdness with EMP and bios versions? The > > > > machines I'm trying this stuff on seem to have fairly old revision of the > > > > bios. I'm going through the upgrade right now, but I thought perhaps it > > > > could be related, or I'm just doing something wrong :-) > > > > > > > > > > I am taking a silly guess here, but I don't think that the EMP has > > > anything to do with BIOS, given that it functions when the machine is > > > turned off (yet plugged in). I could certainly be wrong about that. > > > > > > -Dean > > > > > > > > > > http://www.xxedgexx.com * je...@xx... > > ---------------------------------------------- > > > > > > > > > > http://www.xxedgexx.com * je...@xx... > ---------------------------------------------- > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 02:11:53
|
Hmm, now I'm getting a lot of this: vash$ ipc localhost EMP:CHASSIS_STATUS:webtest3 EMP:22:JOB_STARTED EMP:22:JOB_ERROR:Protocol not available and this appear in the logs: [12:07:11][Nexxus] [EMP][2.0][EMP][San Mehat (net...@va...)] [12:07:16][EMP] Thread webtest3 protocol unavailable (Connection timed out) SEL:IMLW00902615:0x5003:System Event Record:0x00000003:IPMB addr 0x10 (LUN 0):0x02:Physical Security:Unknown Sensor Name:State Asserted SEL:IMLW00902615:0x6003:System Event Record:0x39a17877:SSID 0x8:0x02:System Event:Unknown Sensor Name:No Description Available SEL:IMLW00902615:0x5003:System Event Record:0x00000003:IPMB addr 0x10 (LUN 0):0x02:Physical Security:Unknown Sensor Name:State Asserted SEL:IMLW00902615:0x5003:System Event Record:0x39a178da:SSID 0x8:0x02:System Event:Unknown Sensor Name:No Description Available -jeremy > > Here's a little session just to show that I am getting emp information, > but as soon as I try to do a POWER_OFF, that's the last command I can > issue: > > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > EMP:4:JOB_STARTED > EMP:4:CCAPABLE:YES:YES:YES:NO > EMP:4:JOB_ERROR:Unknown Condition Code > vash$ ipc localhost EMP:POWER_OFF:webtest3 > EMP:5:JOB_STARTED > vash$ > vash$ > vash$ > vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 > EMP:6:JOB_STARTED > vash$ > vash$ > > and that's it... > > -jeremy > > > Jeremy Hansen wrote: > > > > > > I actually figured out that I had console redirection turn on the nexxus > > > controller, so that was screwing it up. Turn it off and the command > > > completed and I was able to get EMP information. > > > > > > So then I ran into another issue. I tried to issue the POWER_OFF command, > > > and then EMP or nexxus stopped responding and never returned a status. > > > > > > > Never seen that. > > > > > > > > Question, has anyone seen any weirdness with EMP and bios versions? The > > > machines I'm trying this stuff on seem to have fairly old revision of the > > > bios. I'm going through the upgrade right now, but I thought perhaps it > > > could be related, or I'm just doing something wrong :-) > > > > > > > I am taking a silly guess here, but I don't think that the EMP has > > anything to do with BIOS, given that it functions when the machine is > > turned off (yet plugged in). I could certainly be wrong about that. > > > > -Dean > > > > > > http://www.xxedgexx.com * je...@xx... > ---------------------------------------------- > > > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: <zsp...@va...> - 2000-08-22 01:55:35
|
On Mon, Aug 21, 2000 at 08:56:05PM -0400, Jeremy Hansen wrote: > > So I have my test machines and I'm going through the quickstart stuff and > I seem to be having issues setting up emp. > > I have a straight serial cable between two machines. The EMP port on the > node is connected to ttyS0 on the nexxus controller, so I issue this > command: > > ipc localhost emp:configuration:webtest3:/dev/ttyS0:NONE > > and I get > > EMP:9:JOB_STARTED > EMP:9:STATUS:ENGAGING Hrm... everything looks correct up until that point. I would expect to see further messages. When you run minicom on ttyS0 do you see any data? Also, look in /var/log/vacm.log and make sure you don't see anything about a thread for node webtest crashing... Zac -- VACM - Couldn't Your SysAdmin Use Some Beauty Sleep? http://vacm.sourceforge.net |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 01:53:25
|
Here's a little session just to show that I am getting emp information, but as soon as I try to do a POWER_OFF, that's the last command I can issue: vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 EMP:4:JOB_STARTED EMP:4:CCAPABLE:YES:YES:YES:NO EMP:4:JOB_ERROR:Unknown Condition Code vash$ ipc localhost EMP:POWER_OFF:webtest3 EMP:5:JOB_STARTED vash$ vash$ vash$ vash$ ipc localhost EMP:CHASSIS_CAPABILITIES:webtest3 EMP:6:JOB_STARTED vash$ vash$ and that's it... -jeremy > Jeremy Hansen wrote: > > > > I actually figured out that I had console redirection turn on the nexxus > > controller, so that was screwing it up. Turn it off and the command > > completed and I was able to get EMP information. > > > > So then I ran into another issue. I tried to issue the POWER_OFF command, > > and then EMP or nexxus stopped responding and never returned a status. > > > > Never seen that. > > > > > Question, has anyone seen any weirdness with EMP and bios versions? The > > machines I'm trying this stuff on seem to have fairly old revision of the > > bios. I'm going through the upgrade right now, but I thought perhaps it > > could be related, or I'm just doing something wrong :-) > > > > I am taking a silly guess here, but I don't think that the EMP has > anything to do with BIOS, given that it functions when the machine is > turned off (yet plugged in). I could certainly be wrong about that. > > -Dean > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 01:42:25
|
I actually figured out that I had console redirection turn on the nexxus controller, so that was screwing it up. Turn it off and the command completed and I was able to get EMP information. So then I ran into another issue. I tried to issue the POWER_OFF command, and then EMP or nexxus stopped responding and never returned a status. Question, has anyone seen any weirdness with EMP and bios versions? The machines I'm trying this stuff on seem to have fairly old revision of the bios. I'm going through the upgrade right now, but I thought perhaps it could be related, or I'm just doing something wrong :-) Thanks -jeremy > > Give the minicom method a try. It will tell you if you are getting back > from the EMP. > > -Dean > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: San N. M. <net...@va...> - 2000-08-22 01:33:06
|
Hmm.. if you run minicom on the port do you see a little burping of binary data every 2 seconds? if not then either your cabling is wrong, or the bios isn't setup properly -san -- ----------------------------------------------- San-Respect-my-.Xauthoritah-Mehat Principal Engineer & Digital Groovemaster VA Linux Systems net...@va... 408-542-8654 ----------------------------------------------- |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 01:13:06
|
Hmm, the cable *should* be fine. This is the same cable I was using for other serial consoles that didn't have any issue. I will definitely verify though... How do I see the status of things? Is there anything I can do to see what it's failing on? -jeremy > Jeremy Hansen wrote: > > > > So I have my test machines and I'm going through the quickstart stuff and > > I seem to be having issues setting up emp. > > > > I have a straight serial cable between two machines. The EMP port on the > > node is connected to ttyS0 on the nexxus controller, so I issue this > > command: > > > > ipc localhost emp:configuration:webtest3:/dev/ttyS0:NONE > > > > and I get > > > > EMP:9:JOB_STARTED > > EMP:9:STATUS:ENGAGING > > > > but that's it. It never returns any success or failure. > > > > What hints? > > > > First of all, it needs be a null-modem cable. That caused me a bit of > confusion at first. ;-) > > A great troubleshooting tool 'minicom'. Set it up as if it were a modem > and you are successful when you get blurts of gibberish every coupla > seconds. Its a binary protocol, so don't be dismayed by it being > gibberish. > > Feel free to holler if you have any further questions about setting it > up. > > -Dean > > http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: Jeremy H. <je...@xx...> - 2000-08-22 00:56:18
|
So I have my test machines and I'm going through the quickstart stuff and I seem to be having issues setting up emp. I have a straight serial cable between two machines. The EMP port on the node is connected to ttyS0 on the nexxus controller, so I issue this command: ipc localhost emp:configuration:webtest3:/dev/ttyS0:NONE and I get EMP:9:JOB_STARTED EMP:9:STATUS:ENGAGING but that's it. It never returns any success or failure. What hints? Thanks -jeremy http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: <zsp...@va...> - 2000-08-21 19:09:07
|
On Mon, Aug 21, 2000 at 01:29:26PM -0400, Jeremy Hansen wrote: > > So I'm assuming that you would like something like the BAYTECH power > module only if the machines you're worried about do not have something > like EMP in the bios, or if you're administering devices such as switches, > etc. Is this correct? > > Also, what BAYTECH device was used for the development of the module? You are correct... Baytech would be used to manage devices not controlled via EMP. We used a Baytech RPC-3. -- VACM - Couldn't Your SysAdmin Use Some Beauty Sleep? http://vacm.sourceforge.net |
|
From: Jeremy H. <je...@xx...> - 2000-08-21 17:29:29
|
So I'm assuming that you would like something like the BAYTECH power module only if the machines you're worried about do not have something like EMP in the bios, or if you're administering devices such as switches, etc. Is this correct? Also, what BAYTECH device was used for the development of the module? Thanks -jeremy http://www.xxedgexx.com * je...@xx... ---------------------------------------------- |
|
From: Arno M. <Ar...@gm...> - 2000-07-06 01:45:20
|
Hi! I am not on this project and (for now) just asking out of curiosity: Is there any effort to create a LINUX enterprise manager based on CIM (see also http://www.dmtf.org/spec/cims.html) ? (Or better: do you know of any effort?) Any CIM support within LINUX at all? I know this is not in your scope specifically but it might be important in the future... Any pointers well appreciated.. Thanks, AM -- Sent through GMX FreeMail - http://www.gmx.net |
|
From: San N. M. <net...@va...> - 2000-04-20 16:14:29
|
On Wed, Apr 19, 2000 at 03:23:37PM -0700, Dale Harris wrote: > Hey, > > Using the CVS checkout as of last night (after Raster rewrote flim, not that > this has anything to do with that). I've been trying to work through > the documentation to make one node work. However the behavior I'm seeing > right now is that nexxus is reporting back anything from the vash ipc > commands I enter. > > VACM 2.0.0 (Beta 2 Candidate) nexxus daemon (Build Apr 18 2000 21:47:30) > Hey Dale, run nexxus with the -l option (log to stdout). There is also a file log kept in /var/log (by default_ called vacm.log. -- ----------------------------------------------- San Mehat Senior Software Engineer & Digital Groovemaster VA Linux Systems net...@va... 408-542-8654 ----------------------------------------------- |
|
From: Dale H. <ro...@va...> - 2000-04-19 22:31:10
|
Hey, Using the CVS checkout as of last night (after Raster rewrote flim, not that this has anything to do with that). I've been trying to work through the documentation to make one node work. However the behavior I'm seeing right now is that nexxus is reporting back anything from the vash ipc commands I enter. connect localhost NEXXUS_READY ipc localhost NEXXUS:NODE_ADD:fcnode1 NEXXUS:1:JOB_STARTED NEXXUS:1:JOB_COMPLETED ipc localhost EMP:CONFIGURATION:fcnode1:/dev/ttyR0:NONE EMP:2:JOB_STARTED EMP:2:JOB_COMPLETED ipc localhost NEXXUS:SET_VAR:fcnode1:IP_ADDRESS:172.16.1.11 NEXXUS:3:JOB_STARTED NEXXUS:3:JOB_COMPLETED yadda yadda. All I see out of nexxus is: VACM 2.0.0 (Beta 2 Candidate) nexxus daemon (Build Apr 18 2000 21:47:30) and nothing else. /var/log/vacm.log has (repeating): [EMP-THREAD] selclear_cb2(): Failed (0xc1) [EMP-THREAD] selclear_cb2(): Failed (0xc1) /usr/lib/vacm_configuration looks good: # VACM Configuration file # Autogenerated by Nexxus - Wed Apr 19 14:57:40 2000 #Definition for node 'fcnode1' NODE:fcnode1 EMP:SERIAL_PORT:/dev/ttyR0 EMP:PASSWORD:NONE EMP:SERIAL_NUMBER:IMLW93202167 GLOBAL:IP_ADDRESS:172.16.1.11 SERCON:DEVICE_ADDRESS:/dev/ttyR10 SERCON:LOGIN:NONE SERCON:PASSWORD:NONE END_NODE So I guess things are working, it just a little hard to tell. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dale Harris <ro...@va...> VA Linux Systems Sr. Support Engr. 1382 Bordeaux Dr. (408) 543-8025 Sunnyvale, CA 94089 |
|
From: Antonio W. C. <to...@vo...> - 2000-04-14 21:16:41
|
Hi Ari Jort & San Mehat, April 14, 2000 Tom Throwe and I would like to install VACM on the VA Linux boxes at the Rhic Computing Facility (RCF) at Brookhaven National Lab to streamline our cluster management software. I downloaded version 2.0.0 Beta from http://vacm.sourceforge.net a few days ago and installed it on one of our Linux boxes. We managed to configuring Nexxus on the "Node Controller" with "vash", but we ran into a problem. The message I get in my "vash" session says: >ipc localhost EMP:NODE_ADD:/dev/ttyR32:NONE:rcrs4001:130.199.205.1 >[EMP] Creating new persistant database entry for node 'rcrs4001' >[EMP] Persistant database flushed >EMP:3:JOB_STARTED >EMP:3:JOB_COMPLETED >[EMP] Node 'rcrs4001' on port /dev/ttyR32 reports WAITING. According to the installation instructions, I have to reconfigure the remote node (rcrs4001) in order to complete the configuration. I assume this means changing the BIOS on the remote node. Can either of you suggest how the BIOS should be changed? Thank you. Cheers, Tony W. Chan |
|
From: Steven A. D. at VA L. S. <sa...@va...> - 2000-01-15 19:09:05
|
In looking over the code and usage statement from the emp_sensord_client it looks like it has the ability to make requests against the emp_sensord Is this something to test on the local managed node box that the sensord program is actually working or am I still way out in left field here? -- Steven A. DuChene sa...@va... |
|
From: Steven A. D. at VA L. S. <sa...@va...> - 2000-01-15 17:46:30
|
OK, the README down in nexxus/nexxus_modules/emp/support_utilities/ states: >To use this utility, simply transfer it to a monitored node and add the daemon >to the nodes startup init scripts. The daemon will have to be manually >backgrounded as so: > >/usr/bin/emp_sensord & I have done this, however the README makes no mention of what if anything to do with the "other" executable that gets built when doing a make in that directory. This is the emp_sensord_client program. Is this something that should be placed onto the managed node with the emp_sensord program or is this something that should go on the mayor to be used by nexxus and the emp module? If this is actually needed perhaps this is why the nodes I have been trying this with are not showing up but instead stick in the "Negotiating" stage in hoover and I get the GET_CHASSIS_CAPABILITIES failed output from nexxus. -- Steven A. DuChene sa...@va... |