Sorry about that. These should help. IPMI: http://www.intel.com/design/servers/ipmi/ has the specs and various links. AMT: http://www.intel.com/technology/platform-technology/intel-amt/ and http://softwarecommunity.intel.com/articles/eng/1034.htm for the AMT DTK.
Andy -----Original Message----- From: Fred Skrotzki [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 10:45 AM To: Cress, Andrew R; Song, Youquan Cc: ipmitool-devel@lists.sourceforge.net Subject: RE: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Andy, A somebody who lerks to learn. It's a shame you posted links that seem to be internal to Intel only. You have external ones handy? ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cress, Andrew R Sent: Tuesday, September 11, 2007 10:04 AM To: Song, Youquan Cc: ipmitool-devel@lists.sourceforge.net Subject: Re: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Song Youquan, That's good. I'm glad it was solved with configuration. See http://telcoserv.so.intel.com/mgt/index.html for an overview of the management interfaces for Intel servers. Intel position statement for AMT and IPMI: http://telcoserv.so.intel.com/amt/amt-position.txt AMT is for desktops and for one low-end server (SR1530AH). It has features that desktops have never had before (OOB manageability). AMT will probably never be part of Intel server platforms. AMT has some nice desktop features that are not important to servers, like the virus protection from AMT circuit breaker, for instance. See http://telcoserv.so.intel.com/amt/amtfunctions.htm for an overview of AMT functions. IPMI is for server platforms, and has tremendous momentum and support across the industry. IPMI supports more server features than AMT. IPMI is a strategic standard for Intel. Intel server customers would go elsewhere if we moved from IPMI to AMT. There are no near-term plans for an IPMI 3.0. Intel will continue to ship IPMI BMCs indefinitely on all server platforms. See http://telcoserv.so.intel.com/mgt/ipmifunc.htm for an overview of IPMI functions. The key value-add for both AMT and IPMI is adding interfaces and additional functionality on top of both of the hardware management interfaces. The Thurley iBMC will add KVM, WSMAN, and SMASH on top of the IPMI functionality. Andy ________________________________ From: Song, Youquan Sent: Tuesday, September 11, 2007 3:04 AM To: Cress, Andrew R Cc: ipmitool-devel@lists.sourceforge.net Subject: RE: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Hi, Andrew Yes. I establish IPMI SOL. Thank you very much. I SOL connect Harwich by CLI-2.3 tool. I have other questions: IPMI vs AMT. AMT is enterprise PC IT solution, IPMI is a server management solution. AMT have many useful features and it also provider SDK and application tools to complish the features. such as IDE-R. Does IPMI provode those features? How is the IPMI develop status? When do the IPMI 3.0 publish? Will IPMI be replaced by AMT? What's the differences between AMT and IPMI? Thanks & Regards, Song Youquan OTC-Beijing Intel SSG/SSD MOB: 13681289076 TEL: 010-82611515-1326 INET: 8-758-1326 LOC: Raycom 6W062 ________________________________ From: Cress, Andrew R Sent: 2007年9月10日 21:34 To: Song, Youquan Subject: RE: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Oops, I forgot to add "-q 3" to the lan options. ________________________________ From: Cress, Andrew R Sent: Monday, September 10, 2007 8:43 AM To: Song, Youquan Subject: RE: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Song Youquan, There are a few things that need to be fixed in the configuration, shown in red below. First, the SOL Payload Access is disabled, which is probably the main reason that it will not connect. The SOL volatile Baud is not set, but if the payload were enabled, this might be ok, since the non-volatile baud is set ok. The LAN param (2) value means that only MD5 is set up for LAN sessions, which may be ok, but is unusual. Also, only the default user is configured for both LAN and serial, so users like 'admin' would not be able to connect via SOL. Here are two steps to correct these: "ipmiutil lan -e -I 172.16.181.155 -u admin -p adminpswd -q 3 " (should detect the gateway IP if the OS has it also, if not, add -G 172.16.181.9) "ipmiutil serial -c -u admin -p adminpswd -q 3" (defaults to 19.2kbps) Then user 'admin' should be able to connect to 171.16.181.155 via SOL. Andy ________________________________ From: Song, Youquan Sent: Monday, September 10, 2007 5:10 AM To: Cress, Andrew R Cc: Song, Youquan Subject: RE: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Hi Andrew, Here is the information for "ipmiutil lan" and "ipmiutil serial", what's the wrong with the setting paramenters? [EMAIL PROTECTED] ~]# ipmiutil lan ipmiutil ver 1.8 pefconfig ver 1.64 -- BMC version 0.56, IPMI version 2.0 pefconfig: GetPefEntry ... PEFilter(01): 01 Temperature Sensor event - disabled for no action PEFilter(02): 02 Voltage Sensor event - disabled for no action PEFilter(03): 04 Fan Failure event - disabled for no action PEFilter(04): 05 Chassis Intrusion event - disabled for no action PEFilter(05): 08 Power Supply Fault event - disabled for no action PEFilter(06): 0c Memory ECC Error event - disabled for no action PEFilter(07): 0f FRB Failure event - disabled for no action PEFilter(08): 07 BIOS POST Error event - disabled for no action PEFilter(09): 13 Fatal NMI event - disabled for no action PEFilter(10): 23 Watchdog Timer Reset event - disabled for no action PEFilter(11): 12 System Restart event - disabled for no action PEFilter(12): empty PEF Control: 00 PEF Actions: 6f Alert PwrDn Reset PwrCyc DiagInt PEF Startup Delay: 60 sec PEF Alert Startup Delay: 60 sec PEF Alert Policy[1]: 01 00 00 00 Disabled PEF Alert Policy[2]: 02 00 00 00 Disabled PEF Alert Policy[3]: 03 00 00 00 Disabled PEF Alert Policy[4]: 04 00 00 00 Disabled pefconfig: GetLanEntry for channel 1 ... Lan Param(0) Set in progress: 00 Lan Param(1) Auth type support: 15 None MD5 Pswd Lan Param(2) Auth type enables: 04 04 04 14 00 Lan Param(3) IP address: 172 16 181 155 Lan Param(4) IP addr src: 01 Static Lan Param(5) MAC addr: 00 0e 0c 43 46 69 Lan Param(6) Subnet mask: 255 255 0 0 Lan Param(7) IPv4 header: 40 40 10 Lan Param(10) BMC grat ARP : 01 Lan Param(11) grat ARP interval: 09 Lan Param(12) Def gateway IP: 172 16 181 9 Lan Param(13) Def gateway MAC: 00 0f 35 fc d9 8a Lan Param(14) Sec gateway IP: 0 0 0 0 Lan Param(15) Sec gateway MAC: 00 00 00 00 00 00 Lan Param(16) Community string: public Lan Param(17) Num dest: 04 Lan Param(18) Dest type: 01 00 00 00 00 Lan Param(18) Dest type: 02 00 00 00 00 Lan Param(18) Dest type: 03 00 00 00 00 Lan Param(18) Dest type: 04 00 00 00 00 Lan Param(19) Dest address: 01 00 00 [0 0 0 0] 00 00 00 00 00 00 Lan Param(19) Dest address: 02 00 00 [0 0 0 0] 00 00 00 00 00 00 Lan Param(19) Dest address: 03 00 00 [0 0 0 0] 00 00 00 00 00 00 Lan Param(19) Dest address: 04 00 00 [0 0 0 0] 00 00 00 00 00 00 Lan Param(192) DHCP Server IP: 0 0 0 0 Lan Param(193) DHCP MAC Address: 00 00 00 00 00 00 Lan Param(194) DHCP Enable: 00 GetChanAcc(lan), ret = 0, new value = 02 Access = Always Avail, PEF Alerts Enabled Channel Access Mode(Lan): 02 04 GetSOL for channel 1 ... SOL Enable: 01 enabled SOL Auth: c4 Admin SOL Accum Interval: 04 32 20 msec SOL Retry Interval: 06 02 20 msec SOL nvol Baud Rate: 07 19.2k SOL vol Baud Rate: 00 nobaud SOL Payload Access(1,1): 00 00 00 00 disabled SOL Payload Support(1): 03 00 15 00 00 00 00 00 Get User Access(1): 04 02 01 14 IPMI, Admin () Get User Access(2): 04 02 01 0f No access (syq) Get User Access(3): 04 02 01 34 IPMI, Admin (admin) Get User Access(4): 04 02 01 0f No access () pefconfig: completed successfully [EMAIL PROTECTED] ~]# ipmiutil serial ipmiutil ver 1.8 tmconfig ver 1.39 -- BMC version 0.56, IPMI version 2.0 Code 0 SEL Ver 2 Support 15 tmconfig: GetSerEntry for channel 4 ... Serial Param(0) Set in progress: 00 Serial Param(1) Auth type support: 15 None MD5 Pswd Serial Param(2) Auth type enables: 14 14 14 14 00 Serial Param(3) Connection Mode: 87 Serial Param(4) Sess Inactiv Timeout: 00 Serial Param(5) Channel Callback: 00 00 ff ff ff Serial Param(6) Session Termination: 03 Serial Param(7) IPMI Msg Comm: 60 07 RTS/CTS, DTR, 19.2k Serial Param(8) Mux Switch: 16 08 Serial Param(9) Modem Ring Time: 3f 00 Serial Param(10) Modem Init String: 01 ATE1Q0V1X4&D2&C1 Serial Param(11) Modem Escape Seq: +++ Serial Param(12) Modem Hangup Seq: ATH Serial Param(13) Modem Dial Command: ATD Serial Param(14) Page Blackout Interval: 00 Serial Param(15) Community String: public Serial Param(16) Num of Alert Dest: 08 Serial Param(17) Destination Info: 01 00 05 03 00 Serial Param(17) Destination Info: 02 00 05 03 00 Serial Param(17) Destination Info: 03 00 05 03 00 Serial Param(17) Destination Info: 04 00 05 03 00 Serial Param(17) Destination Info: 05 00 05 03 00 Serial Param(17) Destination Info: 06 00 05 03 00 Serial Param(17) Destination Info: 07 00 05 03 00 Serial Param(17) Destination Info: 08 00 05 03 00 Serial Param(18) Call Retry Interval: 3c Serial Param(19) Destination Comm Settings: 01 00 07 no_flow, 8N1, 19.2k Serial Param(19) Destination Comm Settings: 02 00 07 no_flow, 8N1, 19.2k Serial Param(19) Destination Comm Settings: 03 00 07 no_flow, 8N1, 19.2k Serial Param(19) Destination Comm Settings: 04 00 07 no_flow, 8N1, 19.2k Serial Param(19) Destination Comm Settings: 05 00 07 no_flow, 8N1, 19.2k Serial Param(19) Destination Comm Settings: 06 00 07 no_flow, 8N1, 19.2k Serial Param(19) Destination Comm Settings: 07 00 07 no_flow, 8N1, 19.2k Serial Param(19) Destination Comm Settings: 08 00 07 no_flow, 8N1, 19.2k Serial Param(20) Number Dial Strings: 06 Serial Param(21) Dest Dial String: 01 01 Serial Param(21) Dest Dial String: 02 01 Serial Param(21) Dest Dial String: 03 01 Serial Param(21) Dest Dial String: 04 01 Serial Param(21) Dest Dial String: 05 01 Serial Param(21) Dest Dial String: 06 01 Serial Param(22) Number Dest IP Addrs: 04 Serial Param(23) Dest IP Address: 01 0 0 0 0 Serial Param(23) Dest IP Address: 02 0 0 0 0 Serial Param(23) Dest IP Address: 03 0 0 0 0 Serial Param(23) Dest IP Address: 04 0 0 0 0 Serial Param(29) Terminal Mode Config: 66 11 Channel Access Mode(4=Ser): 2b 04 Access = Shared, PEF Alerts Disabled Get User Access (1): 04 01 01 14 IPMI, Admin () Get User Access (2): 04 01 01 0f No access (syq) Get User Access (3): 04 01 01 0f No access (admin) Get User Access (4): 04 01 01 0f No access () Get Serial MUX Status: 04 Get Boot Options(3): 01 03 0c tmconfig: completed successfully Thanks & Regards, Song Youquan OTC-Beijing Intel SSG/SSD MOB: 13681289076 TEL: 010-82611515-1326 INET: 8-758-1326 LOC: Raycom 6W062 ________________________________ From: Cress, Andrew R Sent: 2007年9月7日 21:33 To: Song, Youquan Subject: RE: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Song Youquan, Hmmm. I'm guessing that there are configuration problems. Or, there were some recent firmware changes for iBMC for SOL padding compatibility, but I don't think Harwich has the new iBMC. Can you send me the output of "ipmiutil lan" and "ipmiutil serial"? See http://ipmiutil.sf.net The same parameters can be read from ipmitool with several more commands, but this will give the complete set of configuration parameters. I am assuming that the BIOS has Serial Console redirection enabled? FYI, Here are some tips for setting up SOL: http://telcoserv.so.intel.com/ras/tips.htm Andy ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Song, Youquan Sent: Friday, September 07, 2007 1:13 AM To: ipmitool-devel@lists.sourceforge.net Cc: Song, Youquan Subject: [Ipmitool-devel] IPMI SOL failed on Intel Harwich Ipmitool can work round, however, IPMI SOL can not work round. Please give me some help to solve it?? [EMAIL PROTECTED] ~]# ipmitool -I lanplus -H $IP -U $USER -P $PASSWORD -v -o intelplus sol activate Error activating SOL payload: Invalid data field in request [EMAIL PROTECTED] ~]# ipmitool -I lanplus -H $IP -U $USER -P $PASSWORD -v -o intelplus sol info Info: SOL parameter 'Payload Channel (7)' not supported - defaulting to 0x0e Info: SOL parameter 'Payload Port (8)' not supported - defaulting to 623 Set in progress : set-complete Enabled : true Force Encryption : true Force Authentication : true Privilege Level : ADMINISTRATOR Character Accumulate Level (ms) : 20 Character Send Threshold : 50 Retry Count : 6 Retry Interval (ms) : 20 Volatile Bit Rate (kbps) : IPMI-Over-Serial-Setting Non-Volatile Bit Rate (kbps) : 19.2 Payload Channel : 14 (0x0e) Payload Port : 623 I set force-encryption = false and force-authentication=false, and I also get the same result as "Error activating SOL payload: Invalid data field in request" Harwich with Intel Xeon 3.4G X 4 CPUs, BIOS: HW_P11_56_39_xx_Build01. [EMAIL PROTECTED] ~]# lsmod | grep ipmi ipmi_devintf 44432 0 ipmi_si 72336 0 ipmi_msghandler 70420 2 ipmi_devintf,ipmi_si BIOS, I already set "Console Redirection [Enable] " dmidecode : to show IPMI version information IPMI Device Information Interface Type: KCS (Keyboard Control Style) Specification Version: 2.0 I2C Slave Address: 0x10 NV Storage Device: Not Present Base Address: 0x0000000000000CA2 (I/O) Register Spacing: Successive Byte Boundaries Thanks & Regards, Song Youquan OTC-Beijing Intel SSG/SSD MOB: 13681289076 TEL: 010-82611515-1326 INET: 8-758-1326 LOC: Raycom 6W062 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
