intel IPMI fails. Is there any workaround for this problem?

intel IPMI fails. Is there any workaround for this problem?

IPMI

 

Please review our problem described below. We’re trying to use IPMI for computers that have this capability. We have a machine with Intel Server Board S1200BTL with a possibility to connect via RMM4. We’re trying to work with its motherboard remotely. We access the web interface via http://ipaddress/ and an Integrated BMC Web Console is opened. The following information’s present:

 

System Information:

Host Power Status :

Host is currently ON

RMM Status :

Intel(R) RMM installed

Device (BMC) Available :

Yes

BMC FW Build Time :

May 25 2012 10:20:47

BMC FW Rev :

01.14

Boot FW Rev :

00.03

SDR Package Version :

SDR Package 1.14

Mgmt Engine (ME) FW Rev :

02.02.00.049

 

FRU Information

Chassis Information

Type:

Main Server Chassis

Part/Model Number:

..................

Serial Number:

..................

Board Information

Manufacturing Date :

2012-05-05   07:30

Manufacturer :

Intel Corporation

Product Name :

S1200BTL

Serial Number :

QSBT21809255

Part/Model Number :

E98681-352

FRU File ID :

FRU Ver 0.03

Product Information

Manufacturer :

ICL-KME CS

Name :

teamRAY

Part/Model Number :

..........

Version :

....................

Serial Number :

1209TR315

Asset Tag :

39891170100

FRU File ID :

 

We need to remotely handle the power of the computer, examine SEL (System event log)and receive information about critical events. Studying the docs we realized that the best way to talk to the machine by IPMI is WS-MAN protocol accompanied by Windows Remote Management (WinRM) utility. We realized also that WS-MAN is understood if the motherboard has a Remote Management module. A few problems followed.

 

Our motherboard supports RMM4 (as displayed both in BIOS and the web interface). We assumed that RMM4 uses the same IP as BMC. Is that correct?

 

Here’s our piece of code using WinRM:

public static void Get()

        {

            var wsman = new WSManClass();

            var options = (IWSManConnectionOptions) wsman.CreateConnectionOptions();

            if (options != null)

            {

                try

                {

                    options.UserName = "root";

                    options.Password = "root";

 

                    int iFlags = wsman.SessionFlagCredUsernamePassword();

                    var session =

                        (IWSManSession) wsman.CreateSession("http://10.182.171.195:8889/wsman", iFlags, options);

                    if (session != null)

                    {

                        try

                        {

                            var identity = session.Identify();

                            var s = "http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/ComputerSystem";

                            var reply = session.Get(s);

                            var doc = new XmlDocument();

                            doc.LoadXml(reply);

                            foreach (var elementName in new string[] {"p:Caption", "p:Description"})

                            {

                                var node = doc.GetElementsByTagName(elementName)[0];

                                if (node != null) Console.WriteLine(node.InnerText);

                            }

                        }

                        finally

                        {

                            Marshal.ReleaseComObject(session);

                        }

                    }

                }

                catch (Exception ex)

                {

                    Console.WriteLine(ex);

                }

                finally

                {

                    Marshal.ReleaseComObject(options);

                }

            }

        }

 

At the line session.Identify() we’re getting ComException:

 

The WinRM client cannot process the request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. For more information on how to set TrustedHosts run the following command: winrm help config.

 

 

How should we set up network configurations in order to work with RMM4?

Is WS-MAN protocol supported for the above BMC?

publicaciones de 2 / 0 nuevos
Último envío
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.

Your board board: http://ark.intel.com/products/53557/Intel-Server-Board-S1200BTL?ui=BIG&wapkw=intel+server+board+s1200btl

Here is the link to the user guide for BMC/RMM4: http://www.intel.com/support/motherboards/server/sb/CS-032371.htm See section 4 on how to configure your network.

Here is a blog that discusses correct configuration of winrm: http://software.intel.com/en-us/blogs/2008/03/24/getting-to-know-ws-man-a-little-better

>winrm quickconfig  -- creates an HTTP listener by default. You may need to create and HTTPS listener:

  • Type the following command: winrm quickconfig -transport:https. You must open port 443 for HTTPS transport to work.
  • Type:  winrm enumerate winrm/config/listener to get a list of all listeners that have been configured.

This forum is not really for Server related issues but I hope the above information helps you.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Inicie sesión para dejar un comentario.