Hi Duncan, Tom,
I already can get the display screen of my ESB2 platform correctly through
SOL.
But I have another problem that when I tried to input a character to my
platform through SOL,
then my platform can not get this character correctly, actually it get a lot
of chaotic character.
May I know how I can do for this problem ?
another question,
I got a tool "CLI-1.4-1.i386.tz.tgz" from Intel and successfully installed
it.
Then I executed the following command under a terminal
./dpcproxy -f -d .
Then I opened another terminal session and executed :
telnet 127.0.0.1 623
server : 192.168.0.10 (which 192.168.0.10 is my BMC IP)
username : admin (which admin is my BMC user name)
password : admin (which admin is my BMC password)
Then I expected that I can make a connection to my BMC.
But actually I had a message " connection failed" and dpcproxy has some
messages as follows
************** ./Debug.Log ***************
Attempting LAN connection to : 192.168.0.10
05:56:20.215 outgoing: get channel authentication capabilities[38] 20 18 C8
81 04 38 0E 04 31
05:56:20.229 INCOMING: GET CHANNEL AUTHENTICATION CAPABILITIES[38] 81 1C 63
20 04 38 00 01 04 05 00 00 00 00 00 9A
05:56:20.230 outgoing: get channel authentication capabilities[38] 20 18 C8
81 08 38 0E 04 2D
05:56:20.365 INCOMING: GET CHANNEL AUTHENTICATION CAPABILITIES[38] 81 1C 63
20 08 38 00 01 04 05 00 00 00 00 00 96
-------------- Authentication Information --------------
Channel Number: 1
Supported Authentication: MD5
Per Message Authentication Enabled.
User Level Authentication Enabled.
Non-null user names enabled.
Anonymous Login enabled (A user that has a null username and password is
presently enabled).
-------------- Authentication Information --------------
05:56:20.366 outgoing: get session challenge[39] 20 18 C8 81 0C 39 01 61 64
6D 69 6E 00 00 00 00 00 00 00 00 00 00 00 30
05:56:20.488 INCOMING: GET SESSION CHALLENGE[39] --{Error: INVALIDFIELD} 81
1C 63 20 0C 39 CC CF
************** ./Debug.Log ***************
Could you help me to find out the errors with my procedure.
Thank You & Best Regards,
Sophia
>
> Hi Sophia,
>
> After looking at your original output in one of your previous email's,
> it seems that IPMITOOL, once establishing an RMCP+ session successfully,
> is doing the following:
>
> - setting SOL config parameter set-in-progress to set-in-progress
> - setting SOL config parameter to enable
> - setting SOL config parameter set-in-progress to commit-write
> - setting SOL config parameter set-in-progress to set-complete
> - closing the session
>
> This is a different procedure to the output on my system which is also
> an ESB2 based board (Intel).
>
> What version of IPMITOOL are you using, I am using 1.8.8, this looks
> like it could be a previous version of code as it should rely on the
> BMC's SOL settings and not have to enable them manually.
>
> I had to set the set-in-progress SOL setting to set-complete to enable
> SOL before activating it, also I set force encryption and force
> authentication to disabled.
>
> A warning: I have been working on this for a while now and although you
> can start a SOL connection, when you send the first key across the
> connection to the remote system a constant stream of data is sent to the
> remote system which cannot be terminated (escape sequence doesn't work,
> I had to open a new terminal and then deactivate the SOL session. Even
> then the RMCP+ session stays open as I checked with "session info
> active" command.).
>
> I have had to use the DPCproxy application to solve SOL issues, and
> unfortunately there are licensing issues with this as I'm sure you are
> aware.
>
> Other things I did were to disable the serial channel to avoid any
> serial port sharing issues.
>
> I am sure this could be fixed within the IPMITOOL code, unfortunately I
> am not in a position to do so.
>
> This is a script that I used to enable SOL on Intel S5000PAL servers:
>
> #!/bin/bash
> # Script to create an IP address for the management network
> and configures SOL for 19.2k
>
> # start IPMI service
> service ipmi start
> # load modules manually incase service is not installed
> modprobe ipmi_msghandler
> modprobe ipmi_devintf
> modprobe ipmi_si
> # test to see if ipmitool is installed and communicating correctly
> ipmitool raw 0x06 0x01
> # get the 3rd octet of eth0's IP address
> OCTET3=`ifconfig eth0 | grep "inet addr" | awk -F: '{print $2}' | awk
> -F. '{print $3}'`
> # get the 4th octet of eth0's IP address
> OCTET4=`ifconfig eth0 | grep "inet addr" | awk -F: '{print $2}' | awk
> -F. '{print $4}' | awk '{print $1}'`
> # management IP address
> MGMT="10.3.$OCTET3.$OCTET4"
> echo $MGMT
> # The management IP address can now be applied to LAN2 on the cluster
> nodes
> echo on
> ipmitool lan set 1 ipaddr $MGMT
> ipmitool lan set 1 netmask 255.255.0.0
> #ipmitool lan set 2 user
> #ipmitool lan set 2 access on
> #ipmitool lan set 2 alert on
> ipmitool lan set 1 arp respond on
> ipmitool lan set 1 arp generate on
> ipmitool lan set 1 arp interval 5
> ipmitool lan set 1 auth CALLBACK MD5
> ipmitool lan set 1 auth USER MD5
> ipmitool lan set 1 auth OPERATOR MD5
> ipmitool lan set 1 auth ADMIN MD5
> ipmitool lan set 1 ipsrc static
> ipmitool user enable 1
> ipmitool channel setaccess 1 1 callin=on ipmi=on link=on
> ipmitool channel setaccess 1 1 privilege=4
> # volatile and non-volatile channel access settings
> ipmitool raw 0x06 0x40 0x01 0x42 0x44
> ipmitool raw 0x06 0x40 0x01 0x82 0x84
> # Setup SOL dependencies
> # Serial channel access disable
> ipmitool raw 06 0x40 04 0x40 0x44
> ipmitool raw 06 0x40 04 0x80 0x84
> # Check serial channel disabled. should both return 00 04
> ipmitool raw 06 0x41 04 0x40
> ipmitool raw 06 0x41 04 0x80
> # SOL payload activate
> ipmitool raw 06 0x4c 01 01 02 00 00 00
> # Check SOL payload is activated, should return 02 00 00 00
> ipmitool raw 06 0x4d 01 01
> # SOL configuration settings
> ipmitool -I lan -H <hostname> -P <password> sol set set-in-progress
> set-complete 1
> ipmitool sol set enabled true 1
> ipmitool sol set force-encryption false 1
> ipmitool sol set force-authentication false 1
> ipmitool sol set privilege-level admin 1
> ipmitool sol set character-accumulate-level 6 1
> ipmitool sol set character-send-threshold 0x14 1
> ipmitool sol set retry-count 6 1
> ipmitool sol set retry-interval 20 1
> ipmitool sol set non-volatile-bit-rate 19.2 1
> ipmitool sol set volatile-bit-rate 19.2 1
> #ipmitool lan print 2
> ### NOT NEEDED, MAY PROVE USEFUL ELSEWHERE ###
> # increment 4th octet by 1 to get management IP 4th octet
> #OCTET4M=`ifconfig eth0 | grep "inet addr" | awk -F: '{print $2}' | awk
> -F. '{print $4}' | awk '{print ++$1}'`
> # echo management IP address
> #MGMT="10.3.$OCTET3.$OCTET4M"
> #echo $MGMT
> #NEWOCT=`$OCTET4 | awk '{print $1}'`
> #awk '{$OCTET4++}'
> #$ENDOCT = awk '{$OCTET4++}';
> #awk '{$OCTET4A += $1}'
>
>
> Best regards
> Tom Nabarro
> Intel Corporation
> ________________________________________________________________________
> ____
> Message: 2
> Date: Fri, 14 Jul 2006 13:51:24 +0800
> From: "Sophia[IWill]" <[EMAIL PROTECTED]>
> Subject: Re: [Ipmitool-devel] SOL active - 2
> To: <[email protected]>, "Duncan Laurie"
> <[EMAIL PROTECTED]>, "Narayan, Nilesh"
> <[EMAIL PROTECTED]>
> Cc: Jack_Hsu <[EMAIL PROTECTED]>, "Hung, Checa"
> <[EMAIL PROTECTED]>, "Kosaraju, Sridhar"
> <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Tom, Duncan, Nilesh,
>
> I followed your instruction to add a command "raw 06 0x4c 01 01 02
> 00 00
> 00" and had a successful return.
> But I still could not activate SOL successfully, and the command
> sequence
> stopped at "Sending IPMI command payload".
> Then I checked the detail of that part and found some strange data below
> :
>
> >> Sending IPMI command payload
> >> netfn : 0x0c
> >> command : 0x21
> >> data : 0x0e 0x00 0x02 =====================> It may be 0x01
> 0x00
> 0x02
>
> BUILDING A v2 COMMAND
> >> sending packet (26 bytes)
> 06 00 ff 07 06 00 c3 b4 a3 05 06 00 00 00 0a 00
> 20 30 b0 81 10 21 0e 00 02 3e
> << Received data (24 bytes)
> 06 00 ff 07 06 00 a4 a3 a2 a0 04 00 00 00 08 00
> 81 34 4b 20 10 21 cc e3
> << IPMI Response Session Header
> << Authtype : Unknown (0x6)
> << Payload type : IPMI (0)
> << Session ID : 0xa0a2a3a4
> << Sequence : 0x00000004
> << IPMI Msg/Payload Length : 8
> << IPMI Response Message Header
> << Rq Addr : 81
> << NetFn : 0d
> << Rq LUN : 0
> << Rs Addr : 20
> << Rq Seq : 04
> << Rs Lun : 0
> << Command : 21
> << Compl Code : 0xcc
> Error setting SOL parameter 'set-in-progress': Invalid data field in
> request
>
> [EMAIL PROTECTED] ~]#
>
> *****************************************
>
>
>
> ------------------------------
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
>
> ------------------------------
>
> _______________________________________________
> Ipmitool-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
>
>
> End of Ipmitool-devel Digest, Vol 2, Issue 10
> *********************************************
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Ipmitool-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
