Hi Alistair, Everything seems to be configured correctly. There certainly could be a bug/issue on the motherboard. I have two guesses on the issue and ways to see if we can get things to work:
1) I've seen some motherboards that did not seem to "take" new configuration until the BMC was reset by a hard power cycle (i.e. button push) or a cold reset (/usr/sbin/bmc-device --cold-reset). It's worth a try. 2) The BMC incorrectly expects a perfect combination of inputs to function. Does user ADMIN work? What happens if you change the privilege level (-l admin or -l operator) or authentication type (-a md2 or -a straight_password_key) or using IPMI 2.0 (-D lan20). Unfortunately I've seen a number of motherboards where #2 happens to the case. Despite a perfectly legal & correct combination of options given the configuration, the BMC just gets confused and won't allow a connection. Al On Fri, 2012-09-07 at 16:51 -0700, Alastair Young wrote: > I had forgotten bmc-config can run locally - I never do that normally. > > Here is the checkout > > [ayoung@inw-255 ~]$ sudo bmc-config -o > # > # Section UserX Comments > # > # In the following User sections, users should configure usernames, > passwords, > # and access rights for IPMI over LAN communication. Usernames can be > set to any > # string with the exception of User1, which is a fixed to the > "anonymous" > # username in IPMI. > # > # For IPMI over LAN access for a username, set "Enable_User" to "Yes", > # "Lan_Enable_IPMI_Msgs" to "Yes", and "Lan_Privilege_Limit" to a > privilege > # level. The privilege level is used to limit various IPMI operations > for > # individual usernames. It is recommened that atleast one username be > created > # with a privilege limit "Administrator", so all system functions are > available > # to atleast one username via IPMI over LAN. For security reasons, we > recommend > # not enabling the "anonymous" User1. For most users, > "Lan_Session_Limit" can be > # set to 0 (or ignored) to support an unlimited number of simultaneous > IPMI over > # LAN sessions. > # > # If your system supports IPMI 2.0 and Serial-over-LAN (SOL), a > "Password20" and > # "SOL_Payload_Access" field may be listed below. "Password20" may be > used to > # set up to a 20 byte password for the username rather than a maximum > 16 byte > # password. Its use is optional. Set the "SOL_Payload_Access" field to > "Yes" or > # "No" to enable or disable this username's ability to access SOL. > # > # Please do not forget to uncomment those fields, such as "Password", > that may > # be commented out during the checkout. > # > # Some motherboards may require a "Username" to be configured prior to > other > # fields being read/written. If this is the case, those fields will be > set to > # <username-not-set-yet>. > # > Section User1 > ## Give Username > ## Username NULL > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User Yes > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access Yes > EndSection > Section User2 > ## Give Username > Username ADMIN > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User Yes > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs Yes > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback Yes > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit Administrator > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access Yes > EndSection > Section User3 > ## Give Username > Username nagios > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User Yes > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs Yes > ## Possible values: Yes/No > Lan_Enable_Link_Auth Yes > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit User > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access No > EndSection > Section User4 > ## Give Username > Username > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User No > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access Yes > EndSection > Section User5 > ## Give Username > Username > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User No > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access No > EndSection > Section User6 > ## Give Username > Username > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User No > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access No > EndSection > Section User7 > ## Give Username > Username > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User No > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access No > EndSection > Section User8 > ## Give Username > Username > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User No > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access No > EndSection > Section User9 > ## Give Username > Username > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User No > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access No > EndSection > Section User10 > ## Give Username > Username > ## Give password or blank to clear. MAX 16 chars. > ## Password > ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars. > ## Password20 > ## Possible values: Yes/No or blank to not set > Enable_User No > ## Possible values: Yes/No > Lan_Enable_IPMI_Msgs No > ## Possible values: Yes/No > Lan_Enable_Link_Auth No > ## Possible values: Yes/No > Lan_Enable_Restricted_to_Callback No > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary/No_Access > Lan_Privilege_Limit > ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if > not specified > ## Lan_Session_Limit > ## Possible values: Yes/No > SOL_Payload_Access No > EndSection > # > # Section Lan_Channel Comments > # > # In the Lan_Channel section, general IPMI over LAN can be enabled for > disabled. > # In the below, "Volatile" configurations are immediately configured > onto the > # BMC and will have immediate effect on the system. "Non_Volatile" > # configurations are only available after the next system reset. > Generally, both > # the "Volatile" and "Non_Volatile" equivalent fields should be > configured > # identically. > # > # To enable IPMI over LAN, typically "Access_Mode" should be set to > # "Always_Available". "Channel_Privilege_Limit" should be set to the > highest > # privilege level any username was configured with. Typically, this is > set to > # "Administrator". > # > # "User_Level_Auth" and "Per_Message_Auth" are typically set to "Yes" > for > # additional security. > # > Section Lan_Channel > ## Possible values: > Disabled/Pre_Boot_Only/Always_Available/Shared > Volatile_Access_Mode Always_Available > ## Possible values: Yes/No > Volatile_Enable_User_Level_Auth Yes > ## Possible values: Yes/No > Volatile_Enable_Per_Message_Auth Yes > ## Possible values: Yes/No > Volatile_Enable_Pef_Alerting Yes > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary > Volatile_Channel_Privilege_Limit Administrator > ## Possible values: > Disabled/Pre_Boot_Only/Always_Available/Shared > Non_Volatile_Access_Mode Always_Available > ## Possible values: Yes/No > Non_Volatile_Enable_User_Level_Auth Yes > ## Possible values: Yes/No > Non_Volatile_Enable_Per_Message_Auth Yes > ## Possible values: Yes/No > Non_Volatile_Enable_Pef_Alerting Yes > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary > Non_Volatile_Channel_Privilege_Limit Administrator > EndSection > # > # Section Lan_Conf Comments > # > # In the Lan_Conf section, typical networking configuration is setup. > Most users > # will choose to set "Static" for the "IP_Address_Source" and set the > # appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the > machine. > # > Section Lan_Conf > ## Possible values: > Unspecified/Static/Use_DHCP/Use_BIOS/Use_Others > IP_Address_Source Static > ## Give valid IP address > IP_Address 172.22.6.249 > ## Give valid MAC address > MAC_Address > 00:25:90:7D:8E:36 > ## Give valid Subnet Mask > Subnet_Mask 255.255.255.0 > ## Give valid IP address > Default_Gateway_IP_Address 172.22.6.254 > ## Give valid MAC address > Default_Gateway_MAC_Address > 00:25:90:1E:45:F4 > ## Give valid IP address > Backup_Gateway_IP_Address 0.0.0.0 > ## Give valid MAC address > Backup_Gateway_MAC_Address > 00:00:00:00:00:00 > ## Give valid unsigned number > Vlan_id 0 > ## Possible values: Yes/No > Vlan_Id_Enable No > ## Give valid unsigned number > Vlan_Priority 0 > EndSection > # > # Section Lan_Conf_Auth Comments > # > # In the Lan_Conf_Auth section, allowable authentication mechanisms > for IPMI 1.5 > # is configured. Most users will want to set all "MD5" authentication > to "Yes" > # and the rest to "No". If you have configured a NULL username and a > NULL > # password, you will also want to configure some of the "None" fields > to "Yes" > # to allow "None" authentication to work. Some motherboards do not > allow you to > # enable OEM authentication, so you may wish to set all OEM related > fields to > # "No". > # > Section Lan_Conf_Auth > ## Possible values: Yes/No > Callback_Enable_Auth_Type_None No > ## Possible values: Yes/No > Callback_Enable_Auth_Type_MD2 Yes > ## Possible values: Yes/No > Callback_Enable_Auth_Type_MD5 Yes > ## Possible values: Yes/No > Callback_Enable_Auth_Type_Straight_Password Yes > ## Possible values: Yes/No > User_Enable_Auth_Type_None No > ## Possible values: Yes/No > User_Enable_Auth_Type_MD2 Yes > ## Possible values: Yes/No > User_Enable_Auth_Type_MD5 Yes > ## Possible values: Yes/No > User_Enable_Auth_Type_Straight_Password Yes > ## Possible values: Yes/No > Operator_Enable_Auth_Type_None No > ## Possible values: Yes/No > Operator_Enable_Auth_Type_MD2 Yes > ## Possible values: Yes/No > Operator_Enable_Auth_Type_MD5 Yes > ## Possible values: Yes/No > Operator_Enable_Auth_Type_Straight_Password Yes > ## Possible values: Yes/No > Admin_Enable_Auth_Type_None No > ## Possible values: Yes/No > Admin_Enable_Auth_Type_MD2 Yes > ## Possible values: Yes/No > Admin_Enable_Auth_Type_MD5 Yes > ## Possible values: Yes/No > Admin_Enable_Auth_Type_Straight_Password Yes > ## Possible values: Yes/No > OEM_Enable_Auth_Type_None No > ## Possible values: Yes/No > OEM_Enable_Auth_Type_MD2 Yes > ## Possible values: Yes/No > OEM_Enable_Auth_Type_MD5 Yes > ## Possible values: Yes/No > OEM_Enable_Auth_Type_Straight_Password Yes > EndSection > # > # Section Lan_Conf_Security_Keys Comments > # > # If your system supports IPMI 2.0 and Serial-over-LAN (SOL), a K_g > BMC key may > # be configurable. The K_g key is an optional key that can be set for > two key > # authentication in IPMI 2.0. It is optionally configured. Most users > will want > # to set this to zero (or blank). > # > Section Lan_Conf_Security_Keys > ## Give string or blank to clear. Max 20 chars > K_R > ## Give string or blank to clear. Max 20 bytes, prefix with 0x > to enter hex > K_G > 0x0000000000000000000000000000000000000000 > EndSection > # > # Section Lan_Conf_Misc Comments > # > # The following miscellaneous configuration options are optionally > implemented > # by the vendor. They may not be available your system and may not be > visible > # below. > # > # If set to "Yes", "Enable_Gratuitous_ARPs" will inform the BMC to > regularly > # send out Gratuitous ARPs to allow other machines on a network > resolve the > # BMC's MAC Address. Many users will want to set this to "Yes" because > it offers > # the easiest way to support BMC IP Address resolution. However, it > will > # increase traffic on your network. The "Gratuitous_ARP_Interval" can > be used to > # set the period a Gratuitous ARP is always sent. > # > # If set to "Yes", "Enable_ARP_Response" will inform the BMC torespond > to ARP > # requests from other machines. > # > Section Lan_Conf_Misc > ## Possible values: Yes/No > Enable_Gratuitous_ARPs No > ## Possible values: Yes/No > Enable_ARP_Response Yes > EndSection > # > # Section Rmcpplus_Conf_Privilege Comments > # > # If your system supports IPMI 2.0 and Serial-over-LAN (SOL),cipher > suite IDs > # may be configurable below. In the Rmcpplus_Conf_Privilege section, > maximum > # user privilege levels allowed for authentication under IPMI 2.0 > (including > # Serial-over-LAN) are set for each supported cipher suite ID. Each > cipher suite > # ID supports different sets of authentication, integrity, and > encryption > # algorithms for IPMI 2.0. Typically, the highest privilege level any > username > # configured should set for support under a cipher suite ID. This is > typically > # "Administrator". > # > Section Rmcpplus_Conf_Privilege > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_1 Administrator > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_2 Administrator > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_3 Administrator > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_6 Administrator > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_7 Administrator > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_8 Administrator > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_11 Administrator > ## Possible values: > Unused/User/Operator/Administrator/OEM_Proprietary > Maximum_Privilege_Cipher_Suite_Id_12 Administrator > EndSection > # > # Section SOL_Conf Comments > # > # If your system supports IPMI 2.0 and Serial-over-LAN (SOL), the > following > # configuration options will allow SOL configuration. > # > # For most users that want to enable SOL, minimally "Enable_SOL" > should be set > # to "Yes" and "SOL_Privilege_Level" should be set to the highest > privilege > # level any username configured can authenticate with (typically > # "Administrator"). For security purposes, > "Force_SOL_Payload_Authentication" > # and "Force_SOL_Payload_Encryption" should be set to "Yes", however > forced > # authentication and/or encryption depends on the cipher suite IDs > supported. > # The "Non_Volatile_Bit_Rate" and "Volatile_Bit_Rate" should both be > set to the > # appropriate baud rate for your system. This is typically the same > baud rate > # configured in the BIOS and/or operating system. > # > Section SOL_Conf > ## Possible values: Yes/No > Enable_SOL Yes > ## Possible values: > Callback/User/Operator/Administrator/OEM_Proprietary > SOL_Privilege_Level User > ## Possible values: Yes/No > Force_SOL_Payload_Authentication Yes > ## Possible values: Yes/No > Force_SOL_Payload_Encryption Yes > ## Give a non-zero valid integer. Each unit is 5ms > Character_Accumulate_Interval 0 > ## Give a valid number > Character_Send_Threshold 0 > ## Give a valid integer > SOL_Retry_Count 0 > ## Give a valid integer. Interval unit is 10ms > SOL_Retry_Interval 0 > ## Possible values: Serial/9600/19200/38400/57600/115200 > Non_Volatile_Bit_Rate 115200 > ## Possible values: Serial/9600/19200/38400/57600/115200 > Volatile_Bit_Rate 115200 > ## Give a valid port number > ## SOL_Payload_Port_Number 623 > EndSection > > > > Alastair N. Young | Senior Ground Control > > Rocket Fuel Inc. > > [email protected] > 650.517.8834 p > 925.784.0812 m > www.rocketfuel.com > > > > > > > On Fri, Sep 7, 2012 at 2:44 PM, Albert Chu <[email protected]> wrote: > Hi Alastair, > > It's hard to say with this amount of information. It could > simply be a > BMC configuration problem, perhaps the evaluation boards are > not > "auto-configured" like previous boards. > > What does your BMC configuration look like? You can get it > via > bmc-config --checkout. > > Al > > On Fri, 2012-09-07 at 14:25 -0700, Alastair Young wrote: > > Firmware Revision : 01.65 > > Firmware Build Time : 2012-05-16 > > > > Whatever we do, we get "username invalid". All our other > supermicro boxes > > are fine.These X9DRT-HF+ are new evaluation boxes. > > I compiled up the latest freeipmi - it did not help. Also > tried all the > > workaround flags. > > > > Here is the debug output (credentials obscured). Is this > new? Suggestions? > > > > [ayoung@inw-55 freeipmi-1.2.1]$ ./ipmi-sensors/ipmi-sensors > -h > > 172.22.6.248 -u OBSCURED -p OBSCURED -l User --debug > > 172.22.6.248: > ===================================================== > > 172.22.6.248: IPMI 1.5 Get Channel Authentication > Capabilities Request > > 172.22.6.248: > ===================================================== > > 172.22.6.248: RMCP Header: > > 172.22.6.248: ------------ > > 172.22.6.248: [ 6h] = version[ 8b] > > 172.22.6.248: [ 0h] = reserved[ 8b] > > 172.22.6.248: [ FFh] = sequence_number[ 8b] > > 172.22.6.248: [ 7h] = message_class.class[ 5b] > > 172.22.6.248: [ 0h] = > message_class.reserved[ 2b] > > 172.22.6.248: [ 0h] = message_class.ack[ 1b] > > 172.22.6.248: IPMI Session Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 0h] = authentication_type[ 8b] > > 172.22.6.248: [ 0h] = > session_sequence_number[32b] > > 172.22.6.248: [ 0h] = session_id[32b] > > 172.22.6.248: [ 9h] = ipmi_msg_len[ 8b] > > 172.22.6.248: IPMI Message Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 20h] = rs_addr[ 8b] > > 172.22.6.248: [ 0h] = rs_lun[ 2b] > > 172.22.6.248: [ 6h] = net_fn[ 6b] > > 172.22.6.248: [ C8h] = checksum1[ 8b] > > 172.22.6.248: [ 81h] = rq_addr[ 8b] > > 172.22.6.248: [ 0h] = rq_lun[ 2b] > > 172.22.6.248: [ Dh] = rq_seq[ 6b] > > 172.22.6.248: IPMI Command Data: > > 172.22.6.248: ------------------ > > 172.22.6.248: [ 38h] = cmd[ 8b] > > 172.22.6.248: [ Eh] = channel_number[ 4b] > > 172.22.6.248: [ 0h] = reserved1[ 3b] > > 172.22.6.248: [ 0h] = > get_ipmi_v2.0_extended_data[ 1b] > > 172.22.6.248: [ 2h] = > maximum_privilege_level[ 4b] > > 172.22.6.248: [ 0h] = reserved2[ 4b] > > 172.22.6.248: IPMI Trailer: > > 172.22.6.248: -------------- > > 172.22.6.248: [ 3h] = checksum2[ 8b] > > 172.22.6.248: > ===================================================== > > 172.22.6.248: IPMI 1.5 Get Channel Authentication > Capabilities Response > > 172.22.6.248: > ===================================================== > > 172.22.6.248: RMCP Header: > > 172.22.6.248: ------------ > > 172.22.6.248: [ 6h] = version[ 8b] > > 172.22.6.248: [ 0h] = reserved[ 8b] > > 172.22.6.248: [ FFh] = sequence_number[ 8b] > > 172.22.6.248: [ 7h] = message_class.class[ 5b] > > 172.22.6.248: [ 0h] = > message_class.reserved[ 2b] > > 172.22.6.248: [ 0h] = message_class.ack[ 1b] > > 172.22.6.248: IPMI Session Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 0h] = authentication_type[ 8b] > > 172.22.6.248: [ 0h] = > session_sequence_number[32b] > > 172.22.6.248: [ 0h] = session_id[32b] > > 172.22.6.248: [ 10h] = ipmi_msg_len[ 8b] > > 172.22.6.248: IPMI Message Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 81h] = rq_addr[ 8b] > > 172.22.6.248: [ 0h] = rq_lun[ 2b] > > 172.22.6.248: [ 7h] = net_fn[ 6b] > > 172.22.6.248: [ 63h] = checksum1[ 8b] > > 172.22.6.248: [ 20h] = rs_addr[ 8b] > > 172.22.6.248: [ 0h] = rs_lun[ 2b] > > 172.22.6.248: [ Dh] = rq_seq[ 6b] > > 172.22.6.248: IPMI Command Data: > > 172.22.6.248: ------------------ > > 172.22.6.248: [ 38h] = cmd[ 8b] > > 172.22.6.248: [ 0h] = comp_code[ 8b] > > 172.22.6.248: [ 1h] = channel_number[ 8b] > > 172.22.6.248: [ 0h] = > authentication_type.none[ 1b] > > 172.22.6.248: [ 1h] = > authentication_type.md2[ 1b] > > 172.22.6.248: [ 1h] = > authentication_type.md5[ 1b] > > 172.22.6.248: [ 0h] = > authentication_type.reserved1[ 1b] > > 172.22.6.248: [ 1h] = > > authentication_type.straight_password_key[ 1b] > > 172.22.6.248: [ 0h] = > authentication_type.oem_prop[ 1b] > > 172.22.6.248: [ 0h] = > authentication_type.reserved2[ 1b] > > 172.22.6.248: [ 0h] = > > > authentication_type.ipmi_v2.0_extended_capabilities_available[ 1b] > > 172.22.6.248: [ 0h] = > authentication_status.anonymous_login[ > > 1b] > > 172.22.6.248: [ 1h] = > authentication_status.null_username[ 1b] > > 172.22.6.248: [ 1h] = > > authentication_status.non_null_username[ 1b] > > 172.22.6.248: [ 0h] = > > authentication_status.user_level_authentication[ 1b] > > 172.22.6.248: [ 0h] = > > authentication_status.per_message_authentication[ 1b] > > 172.22.6.248: [ 0h] = > authentication_status.k_g[ 1b] > > 172.22.6.248: [ 0h] = > authentication_status.reserved[ 2b] > > 172.22.6.248: [ 0h] = > channel_supports_ipmi_v1.5_connections[ > > 1b] > > 172.22.6.248: [ 0h] = > channel_supports_ipmi_v2.0_connections[ > > 1b] > > 172.22.6.248: [ 0h] = reserved[ 6b] > > 172.22.6.248: [ 5345h] = oem_id[24b] > > 172.22.6.248: [ 0h] = oem_auxiliary_data[ 8b] > > 172.22.6.248: IPMI Trailer: > > 172.22.6.248: -------------- > > 172.22.6.248: [ BFh] = checksum2[ 8b] > > 172.22.6.248: > ===================================================== > > 172.22.6.248: IPMI 1.5 Get Session Challenge Request > > 172.22.6.248: > ===================================================== > > 172.22.6.248: RMCP Header: > > 172.22.6.248: ------------ > > 172.22.6.248: [ 6h] = version[ 8b] > > 172.22.6.248: [ 0h] = reserved[ 8b] > > 172.22.6.248: [ FFh] = sequence_number[ 8b] > > 172.22.6.248: [ 7h] = message_class.class[ 5b] > > 172.22.6.248: [ 0h] = > message_class.reserved[ 2b] > > 172.22.6.248: [ 0h] = message_class.ack[ 1b] > > 172.22.6.248: IPMI Session Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 0h] = authentication_type[ 8b] > > 172.22.6.248: [ 0h] = > session_sequence_number[32b] > > 172.22.6.248: [ 0h] = session_id[32b] > > 172.22.6.248: [ 18h] = ipmi_msg_len[ 8b] > > 172.22.6.248: IPMI Message Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 20h] = rs_addr[ 8b] > > 172.22.6.248: [ 0h] = rs_lun[ 2b] > > 172.22.6.248: [ 6h] = net_fn[ 6b] > > 172.22.6.248: [ C8h] = checksum1[ 8b] > > 172.22.6.248: [ 81h] = rq_addr[ 8b] > > 172.22.6.248: [ 0h] = rq_lun[ 2b] > > 172.22.6.248: [ Eh] = rq_seq[ 6b] > > 172.22.6.248: IPMI Command Data: > > 172.22.6.248: ------------------ > > 172.22.6.248: [ 39h] = cmd[ 8b] > > 172.22.6.248: [ 2h] = authentication_type[ 4b] > > 172.22.6.248: [ 0h] = reserved[ 4b] > > 172.22.6.248: [ BYTE ARRAY ... ] = user_name[16B] > > 172.22.6.248: [ 6Eh 61h 67h 69h 6Fh 73h 00h 00h ] > > 172.22.6.248: [ 00h 00h 00h 00h 00h 00h 00h 00h ] > > 172.22.6.248: IPMI Trailer: > > 172.22.6.248: -------------- > > 172.22.6.248: [ 8Bh] = checksum2[ 8b] > > 172.22.6.248: > ===================================================== > > 172.22.6.248: IPMI 1.5 Get Session Challenge Response > > 172.22.6.248: > ===================================================== > > 172.22.6.248: RMCP Header: > > 172.22.6.248: ------------ > > 172.22.6.248: [ 6h] = version[ 8b] > > 172.22.6.248: [ 0h] = reserved[ 8b] > > 172.22.6.248: [ FFh] = sequence_number[ 8b] > > 172.22.6.248: [ 7h] = message_class.class[ 5b] > > 172.22.6.248: [ 0h] = > message_class.reserved[ 2b] > > 172.22.6.248: [ 0h] = message_class.ack[ 1b] > > 172.22.6.248: IPMI Session Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 0h] = authentication_type[ 8b] > > 172.22.6.248: [ 0h] = > session_sequence_number[32b] > > 172.22.6.248: [ 0h] = session_id[32b] > > 172.22.6.248: [ 8h] = ipmi_msg_len[ 8b] > > 172.22.6.248: IPMI Message Header: > > 172.22.6.248: -------------------- > > 172.22.6.248: [ 81h] = rq_addr[ 8b] > > 172.22.6.248: [ 0h] = rq_lun[ 2b] > > 172.22.6.248: [ 7h] = net_fn[ 6b] > > 172.22.6.248: [ 63h] = checksum1[ 8b] > > 172.22.6.248: [ 20h] = rs_addr[ 8b] > > 172.22.6.248: [ 0h] = rs_lun[ 2b] > > 172.22.6.248: [ Eh] = rq_seq[ 6b] > > 172.22.6.248: IPMI Command Data: > > 172.22.6.248: ------------------ > > 172.22.6.248: [ 39h] = cmd[ 8b] > > 172.22.6.248: [ 81h] = comp_code[ 8b] > > 172.22.6.248: IPMI Trailer: > > 172.22.6.248: -------------- > > 172.22.6.248: [ EEh] = checksum2[ 8b] > > /home/ayoung/freeipmi-1.2.1/ipmi-sensors/.libs/lt-ipmi-sensors: > username > > invalid > > > > > > > > Alastair N. Young | Senior Ground Control > > > > Rocket Fuel Inc. > > > ** > > [email protected] > > 650.517.8834 p > > 925.784.0812 m > > www.rocketfuel.com > > > _______________________________________________ > > Freeipmi-users mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/freeipmi-users > -- > Albert Chu > [email protected] > Computer Scientist > High Performance Systems Division > Lawrence Livermore National Laboratory > > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list [email protected] https://lists.gnu.org/mailman/listinfo/freeipmi-users
