Re: [Freeipmi-devel] 2/18 change - configure.ac: fix of automake init
Al, The problem was ustar option was not supported by automake-1.8. If you really need that option we should change minimum required version of automake to 1.10. -- Anand Babu GPG Key ID: 0x62E15A31 Blog [http://ab.freeshell.org] The GNU Operating System [http://www.gnu.org] Albert Chu writes: What was the error? We should work on an alternate solution rather than just revert to the earlier configure.ac. Al Hi Al, ./autogen.sh failed with your chance. I use autoconf 2.61 automake 1.8.5 Thanks, Regards, Bala --- Free as in freedom http://www.gnu.org/ Bala, Is there a reason you reverted my fix to configure.ac from 2/16/07? Do you guys run an older autoconf version that didn't support the changes I made? I'm confused. Al -- Albert Chu [EMAIL PROTECTED] 925-422-5311 Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel -- Albert Chu [EMAIL PROTECTED] 925-422-5311 Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
Re: [Freeipmi-devel] Need help in IPMI over serial
Evgeny,
GNU FreeIPMI doesn't have serial driver yet. So far I haven't found
any users for it. You are the first one!. I have used serial interface
through IPMI TERMINAL MODE though. IPMI TERMINAL MODE doesn't require
any special driver though.
First step is to get access to the board. I assume you have attached a
NULL modem cable to the BMC.
What is your Channel Access Mode?
My advise is to put to ALWAYS-AVAILABLE during your development
stage. Later on may be you can use SHARED mode, if you also with to
share it with the host OS for console prediction.
If you are in ALWAYS-AVAILABLE available mode, do you see BMC
constantly throwing some junk chars (ping) every 2 seconds? This
confirms that your BMC is accessible and ready to accept your
commands.
Obviously serial basic mode is single session based and requires
authentication. Individual packets are not signed. There is no session
header either. To activate a session, you issue Get Channel Auth
Capabilities, Get Session Challenge and Activate Session commands. Get
Channel Auth Capabilities is required to trigger the BMC to enter into
Basic Mode. BASIC mode only support plain text passwords.
Request Packet structure is like this:
serial_basic_msg_hdr_rq (structure explained below)
cmd (8 bits)
data bytes (depends on cmd)
serial_basic_msg_trlr (structure explained below)
Request Packet structure is like this:
serial_basic_msg_hdr_rq (structure explained below)
cmd (8 bits)
completion_code (8 bits)
response data (depends on cmd)
serial_basic_msg_trlr (structure explained below)
/* IPMI Serial-Basic Message Request Header */
fiid_template_t tmpl_serial_basic_msg_hdr_rq =
{
{8, rs_addr, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{2, rs_lun, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{6, net_fn, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{8, checksum1, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{8, rq_addr, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{2, rq_lun, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{6, rq_seq, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{0, , 0}
};
/* IPMI Serial-Basic Message Response Header */
fiid_template_t tmpl_lan_msg_hdr_rs =
{
{8, rq_addr, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{2, rq_lun, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{6, net_fn, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{8, checksum1, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{8, rs_addr, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{2, rs_lun, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{6, rq_seq, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{0, , 0}
};
/* IPMI Serial-Basic Message Trailer */
fiid_template_t tmpl_setial_basic_msg_trlr =
{
{8, checksum2, FIID_FIELD_REQUIRED | FIID_FIELD_LENGTH_FIXED},
{0, , 0}
};
Can you please tell me what type of BMC you have? I can write a driver
for serial mode or help you write one.
--
Anand Babu Periasamy
GPG Key ID: 0x62E15A31
Blog [http://ab.freeshell.org]
The GNU Operating System [http://www.gnu.org]
Evgeny S. Sidorenko writes:
Hi all!
I have the following problem: I have device that connects to the computer
via serial port, and provides IPMI over serial in Basic Mode. I have
problem in understanding how to generate messages (format, etc),
send/receive requests/answers, and so on.
Could you help me in this problem? I need only basically knowledge, i.e.
how to create connections, create messages, etc
--
Best regards,
Evgeny
___
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-devel
[Freeipmi-devel] Re: [Freeipmi-users] bmc-autoconfig: drop for 0.5.0 release?
Hi Al, * It is still maintained. * BMC-Autoconfig is not a GUI wizard for bmc-config. It is supposed to ask minimum questions from the user and automatically configure the BMC with known defaults. It is intended for users without any knowledge of IPMI to quickly get a basic working setup. * It does enable LAN and configure NULL, admin, operator and ipmiuser accounts. See the template file, you will get an idea what all it configures. If you have suggestions to improve, let us know? Albert Chu writes: I'm thinking of dropping this from FreeIPMI: A) It doesn't seem to be maintained by the original authors. B) It apparenly only configures 3 fields of the BMC. No users, lan enabling, etc. I don't really see the use anymore. Any comments? Anyone out there using this? Al -- -- Anand Babu Periasamy GPG Key ID: 0x62E15A31 Blog [http://ab.freeshell.org] The GNU Operating System [http://www.gnu.org] ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
[Freeipmi-devel] Re: [Freeipmi-users] bmc-autoconfig: drop for 0.5.0 release?
Hi Al, Comments inline .. Al Chu writes: Hey A.B., On Tue, 2007-08-14 at 03:27 -0700, Anand Babu Periasamy wrote: Hi Al, * It is still maintained. If that's the case, it is pretty out of date: A) manpage is out of date and not using the common/doc/ common manpage stuff (if it did the later, it would automatically be updated with my changes). I already updated man page before writing my previous mail. B) it doesn't configure anything SOL related Can you please add the best SOL default config to the template? * BMC-Autoconfig is not a GUI wizard for bmc-config. It is supposed to ask minimum questions from the user and automatically configure the BMC with known defaults. It is intended for users without any knowledge of IPMI to quickly get a basic working setup. * It does enable LAN and configure NULL, admin, operator and ipmiuser accounts. See the template file, you will get an idea what all it configures. How does the user know what the default configured usernames are? No documentation indicates what they are. The user is supposed to cat the template file? Or run bmc-config --checkout to figure it out? I shows the configured user names on exit. I did that before writing my previous mail. Also, I see: Note:- Passwords are not set or cleared. If you want to set password for BMC user, run bmc-config --commit -f 'UserN.Password=PASSWORD' in bmc-autoconfig. So the user has to run bmc-config anyways to configure the passwords? Why not set some defaults? I am not sure why Avati did do so. I agree, we should set some default passwords too and throw a nice summary in a dialog screen only. User's may not notice these messages otherwise. We will fix it. If you have suggestions to improve, let us know? The tool also does not handle the fact that BMCs have a variable number of users. So what if the BMC only allows 2 users? In that case, at least anonymous 'NULL' user with administrative privileges and one 'ipmiuser' with user privileges will be configured. How will bmc-autoconfig handle the variable number of supported cipher suite configurations different vendors provide? It configures with PLAIN-TEXT passwords which is supported on all systems. I would consider cipher settings as advanced and recommend bmc-config instead. -- Anand Babu Periasamy GPG Key ID: 0x62E15A31 Blog [http://ab.freeshell.org] The GNU Operating System [http://www.gnu.org] ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
[Freeipmi-devel] Re: [Freeipmi-users] bmc-autoconfig: drop for 0.5.0 release?
Peter Broadwell writes: I have need to configure many machines at the same time and if the templateing file was documented this tool might become the one of choice for such uses. This tool actually throws a dialog screen interface. So you will not be able to automate with it as of now. We will enhance this tool for next release with command line args support for current dialog options as well. In terms of documenting the template, I think we can make the summary screen more elaborate. For complete documentation, users can do bmc-config --checkout to see what is configured on their system. man bmc-config.conf already documents these settings. -- Anand Babu Periasamy GPG Key ID: 0x62E15A31 Blog [http://ab.freeshell.org] The GNU Operating System [http://www.gnu.org] ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
[Freeipmi-devel] Re: [Freeipmi-users] bmc-autoconfig: drop for 0.5.0 release?
Al Chu writes: Can you please add the best SOL default config to the template? This is my point. If you guys aren't interested in maintaining bmc- autoconfig along w/ bmc-config, and I don't want to maintain it, and (it seems) no one uses it, then we should get rid of it!! :-) I am not asking you to maintain it. I only requested you to add SOL settings, because you wrote the SOL. No worries we will take care of it. It configures with PLAIN-TEXT passwords which is supported on all systems. I would consider cipher settings as advanced and recommend bmc-config instead. That's my point A.B. Cipher settings are advanced and necessary for SOL. Most users wouldn't want to touch them. So bmc-autoconfig should handle it. Why would you leave it to bmc-config? bmc-autoconfig's goal was to do basic known default settings to get a system fully functional. Once the user is confident that IPMI is accessible and basic commands work, he/she can fiddle more on top of it. If SOL setting is so advanced, I would rather skip SOL all together for bmc-autoconfig. Alternatively I don't see setting cipher algorithm to NONE as that advanced. I will see what I can do. -- Anand Babu Periasamy GPG Key ID: 0x62E15A31 Blog [http://ab.freeshell.org] The GNU Operating System [http://www.gnu.org] ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
Re: [Freeipmi-devel] ipmi-sensor on processor group: No Result
Hi Sharad, Can you please post the full output without -g option? -- Anand Babu Periasamy Sharad Chandra writes: Sorry, forgot to mention It is a FreeBSD 6.1 box and ipmi version freeipmi-0.3.1. /usr/local/sbin/ipmi-sensors -g Module/Board is not giving any value. And similarly Memory is also not giving me any value. What parameter / tool should i use to figure out the problem location? It is saying there are only 17 record info. Fetching SDR repository information... done Fetching record 16 of 17 (current record ID 17) I am sure it is not related to freeipmi version any how. Right? Thanks Sharad Chandra On Friday 12 October 2007 1:06 pm, Gregor Dschung wrote: Hey Shared, it seems to be an issue related to Supermicro. Query a HP-Server: p300slg01:~/OM/linux/supportscripts # ipmi-sensors -h gtseval-ipmi -u ADMIN -P -g Processor Password: 2352: CPU0 Therm-Trip (Processor): [State Deasserted] 2400: CPU1 Therm-Trip (Processor): [State Deasserted] 2448: CPU0 IERR (Processor): [State Deasserted] 2496: CPU1 IERR (Processor): [State Deasserted] 2640: CPU0 SocketOcc (Processor): [Device Inserted/Device Present] 2688: CPU1 SocketOcc (Processor): [Device Removed/Device Absent] Query a Supermicro-Server: p300slg01:~/OM/linux/supportscripts # ipmi-sensors -h gts00-ipmi -u ADMIN -P -g Module/Board Password: 28: CPU0 Internal E (Module/Board): [OK] 29: CPU1 Internal E (Module/Board): [OK] 30: CPU Overheat (Module/Board): [OK] 31: Thermal Trip0 (Module/Board): [OK] 32: Thermal Trip1 (Module/Board): [OK] You see, the sensor-type is different. Regards, Gregor Hello, Once i run ipmi-sensors -g processor i don't get any output. It has kcs interface at IO base address CA8. System is Supermicro PDSMi. I think this has a support of IPMI. Why it is so? Thanks for any advice Sharad Chandra ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel ___ Freeipmi-users mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/freeipmi-users ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
Re: [Freeipmi-devel] ipmi-sensor on processor group: No Result
Hmm.. it looks like your sensor data repository (SDR) itself has only few entries. It is possible that your IPMI BMC only supports basic sensors, or you will need a SDR firmware update. -- Anand Babu Periasamy. Sharad Chandra writes: [EMAIL PROTECTED] ~]# /usr/local/sbin/ipmi-sensors 22273: CPU 1 (Temperature): 0.00 C (NA/78.00): [OK] 22274: CPU 2 (Temperature): 0.00 C (NA/78.00): [OK] 22275: SYSTEM (Temperature): 0.00 C (NA/83.00): [OK] 22276: 3.3V (Voltage): 0.00 V (0.00/0.00): [OK] 22278: 5V (Voltage): 0.00 V (0.00/0.00): [OK] 22279: 12V (Voltage): 0.00 V (0.00/0.00): [OK] 22280: -12V (Voltage): 105.00 V (0.00/0.00): [OK] 22281: Fan1 (Fan): 11.00 RPM (0.00/NA): [OK] 22282: Fan2 (Fan): 83.00 RPM (0.00/NA): [OK] 22283: Fan3 (Fan): 0.00 RPM (0.00/NA): [OK] 22284: Fan4 (Fan): 26.00 RPM (0.00/NA): [OK] 22285: Fan5 (Fan): 26.00 RPM (0.00/NA): [OK] 22286: Fan6 (Fan): 0.00 RPM (0.00/NA): [OK] 22287: Fan7 (Fan): 0.00 RPM (0.00/NA): [OK] 22288: Fan8 (Fan): 0.00 RPM (0.00/NA): [OK] 22289: Intrusion (Platform Chassis Intrusion): [General Chassis Intrusion] 22290: Power Supply (Power Supply): [Power Supply Failure detected] [EMAIL PROTECTED] ~]# Hi Sharad, Can you please post the full output without -g option? Sharad Chandra ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
Re: [Freeipmi-devel] KCS Driver SMS_ATN Register
Matt Jerdonek wrote: Hello, The KCS driver appears to not use the SMS_ATN register. This register is useful for BMC-to-BMC communication to know when the remote BMC has responded. Are there any plans to monitor this register in future releases? If not, are the maintainers open to including a patch? Thanks, -Matt Hi Matt, If you use SMS_ATN flag, then you should also call Get Message Flags and check if Receive Message Available flag is set. SMS_ATN flag can also be set for other reasons such as watchdog pre-timeout, event message buffer full and OEM events. My understanding was to use OBF flag for this purpose. Check this out: Figure 9-7, KCS Interface BMC to SMS Read Transfer Flow Chart http://download.intel.com/design/servers/ipmi/IPMI2_0E4_Markup_061209.pdf SMS_ATN seems logical for this purpose given its name, but IPMI Spec uses OBF in its data flow diagram. SMS_ATN and OBF both seems to do the same job, except OBF is simple. When should we check for SMS_ATN over OBF or should we check both always? Even OpenIPMI KCS driver uses OBF and not SMS_ATN flag for reading from registers. SMS_ATN seems useful for high level polling (watch dog daemon). If all system management interfaces supports this flag, then it is worth exposing generic bmc_check_idle() api. Your patches are most welcome. -- Anand Babu Periasamy Blog [http://www.unlocksmith.org] Twitter [http://twitter.com/unlocksmith] Gluster Storage Platform [http://www.gluster.org] GNU/Linux Operating System [http://www.gnu.org] ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
