Menu

Intel S5000pal with rmm2

Help
2009-02-11
2013-04-15
  • Juan Garcia

    Juan Garcia - 2009-02-11

    we try to access to the ethernet card of RMM2 module in a Intel S5000pal moderboard.
    It seems that the card is ignoring the connection from ipmiutil.

    C:\Documents and Settings\Administrator>ipmiutil sensor -x -N 172.17.64.57 -U admin -P password -F lan2i -V 5
    ipmiutil ver 2.33
    sensor: version 2.33
    ipmi_open_lan2(172.17.64.57,admin,00B52650,1)
    Opening lanplus connection to node 172.17.64.57 ...
    seed_prng: RAND_file_name = C:/.rnd, fp=464330
    lan2 intf setup returned 0
    IPMI LAN host 172.17.64.57 port 623

    >> Sending IPMI command payload
    >>    netfn   : 0x06
    >>    command : 0x38

    >> Sending IPMI command payload
    >>    netfn   : 0x06
    >>    command : 0x38
    Get Auth Capabilities error: Invalid data field in request

    >> Sending IPMI command payload
    >>    netfn   : 0x06
    >>    command : 0x38

    >> Sending IPMI command payload
    >>    netfn   : 0x06
    >>    command : 0x38
    Get Auth Capabilities error: Invalid data field in request
    Error issuing Get Channel Authentication Capabilies request
    Error: Unable to establish IPMI v2 / RMCP+ session
    lan2 open.intf(auth=2,priv=5,cipher=3) returned fd -1
    ipmi_open_lan2 error -1
    ipmi_cmd_lan2: interface open error -1
    sensor, error -1

    Thanks & Regards

     
    • Andy Cress

      Andy Cress - 2009-02-11

      The -V 5 looks strange.  I don't think that the OEM privilege level will be supported.  That's probably what is wrong. 
      Also, you don't need to force the interface level, although either lan or lan2i will work.

      If the RMM2 is configured properly, either of these commands will work:
      ipmiutil sensor  -N 172.17.64.57 -U admin -P password
      or
      ipmiutil sensor  -N 172.17.64.57 -U admin -P password -F lan2i
      I've tested against the RMM2 card before and it does handle normal IPMI LAN traffic. 

      If that doesn't work, go to the system with the RMM2 and capture the output of:
      ipmiutil lan -L 3
      so we can see how the RMM2 is configured.
      And knowing the RMM2 firmware version would also help, which can be seen from the RMM2 web console under Device Settings, I think.

       
    • Andy Cress

      Andy Cress - 2009-02-11

      I looked it up, and RMM2 firmware >= 5990 is required to support "IPMI pass-through", so that this will be enabled.
      The latest RMM2 firmware I've seen is 6912.

       
    • Juan Garcia

      Juan Garcia - 2009-02-12

      This is the exit of ipmi lan -L3

      C:\Documents and Settings\Administrator>ipmiutil lan -L 3
      ipmiutil ver 2.33
      pefconfig ver 2.33
      -- BMC version 0.64, IPMI version 2.0
      pefconfig, GetPefEntry ...
      PEFilter(01): 01 Temperature Sensor event - enabled for alert
      PEFilter(02): 02 Voltage Sensor event - enabled for alert
      PEFilter(03): 04 Fan Failure event - enabled for alert
      PEFilter(04): 05 Chassis Intrusion event - enabled for alert
      PEFilter(05): 08 Power Supply Fault event - enabled for alert
      PEFilter(06): 0c Memory ECC Error event - enabled for alert
      PEFilter(07): 0f BIOS POST Error event - enabled for alert
      PEFilter(08): 07 FRB Failure event - enabled for alert
      PEFilter(09): 13 Fatal NMI event - enabled for alert
      PEFilter(10): 23 Watchdog Timer Reset event - enabled for alert
      PEFilter(11): 12 System Restart event - enabled for alert
      PEFilter(12): empty
      PEF Control: 00 :
      PEF Actions: 2f : Alert PwrDn Reset PwrCyc DiagInt
      PEF Startup Delay: 3c : 60 sec
      PEF Alert Startup Delay: 3c: 60 sec
      PEF Alert Policy[1]: 01 18 11 00 : Chan[1] Dest[1] Enabled
      PEF Alert Policy[2]: 02 28 23 00 : Chan[2] Dest[3] Enabled
      PEF Alert Policy[3]: 03 38 11 00 : Chan[1] Dest[1] Enabled
      PEF Alert Policy[4]: 04 38 23 00 : Chan[2] Dest[3] Enabled

      pefconfig, GetLanEntry for channel 3 ...
      Lan Param(0) Set in progress: 00
      Lan Param(1) Auth type support: 15 : None MD5 Pswd
      Lan Param(2) Auth type enables: 15 15 15 15 00
      Lan Param(3) IP address: 172 17 64 57
      Lan Param(4) IP addr src: 01 : Static
      Lan Param(5) MAC addr: 00 0d 5d 05 03 61
      Lan Param(6) Subnet mask: 255 255 255 0
      Lan Param(7) IPv4 header: 40 40 10
      Lan Param(10) BMC grat ARP: 00 : ARP disabled Grat-ARP disabled
      Lan Param(11) grat ARP interval: 0a : 5 sec
      Lan Param(12) Def gateway IP: 172 17 64 254
      Lan Param(13) Def gateway MAC: 00 00 00 00 00 00
      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:
      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
      Channel Access Mode(3=lan): 0a 04 : Access = Always Avail, PEF Alerts Enabled
      pefconfig, GetSOL for channel 3 ...
      SOL Enable: 01 : enabled
      SOL Auth: 02 : User
      SOL Accum Interval: 06 14 : 30 msec
      SOL Retry Interval: 05 06 : 60 msec
      SOL nvol Baud Rate: 07 : 19.2k
      SOL vol Baud Rate: 00 : nobaud
      SOL Payload Support(3): 03 00 15 00 00 00 00 00
      SOL Payload Access(3,1): 02 00 00 00 : enabled
      SOL Payload Access(3,2): 00 00 00 00 : disabled
      SOL Payload Access(3,3): 00 00 00 00 : disabled
      SOL Payload Access(3,4): 00 00 00 00 : disabled
      Get User Access(1): 0f 02 01 34 : IPMI, Admin  ()
      Get User Access(2): 0f 02 01 3f : IPMI, No access (admin)
      Get User Access(3): 0f 02 01 0f : No access ()
      Get User Access(4): 0f 02 01 0f : No access ()
      pefconfig, completed successfully
      ---------------------CUT HERE---------------------

      Wathing this case i found that the users in the lines "Get User Access" were disabled. Even more, there are only 4 users???, that's not match with the users in the administration web of the RMM2...

      Thanks a lot

       
      • Andy Cress

        Andy Cress - 2009-02-12

        Juan,

        First, you probably need to check two things on the RMM2 web console:
        1. Under Maintenance/DeviceInformation, is the Firmware Build Number >= 5990?
        2. Under DeviceSettings/IPMI, it should have "IPMI Channel 3 Forwarding" enabled, and at least MD5 Authentication should be enabled for Admin, Operator, and User.

        Then, once we are sure that IPMI Forwarding is supported and enabled on the RMM2, we need to correct two things that are incorrect in the settings.
        A) The default gateway does not have a resolved MAC address, and
        B) The admin user is not enabled for IPMI channel 3, as you noticed. 

        To resolve this you can do, locally on the SUT:
        ipmiutil lan -L 3 -e -I 172.17.64.57 -u admin -p password

        These could also be changed from the RMM2 web console, I think. 

         
    • Juan Garcia

      Juan Garcia - 2009-02-13

      Yes , our firmware is 5990.

      C:\>ipmiutil lan -L 3
      ipmiutil ver 2.33
      pefconfig ver 2.33
      -- BMC version 0.64, IPMI version 2.0
      pefconfig, GetPefEntry ...
      PEFilter(01): 01 Temperature Sensor event - enabled for alert
      PEFilter(02): 02 Voltage Sensor event - enabled for alert
      PEFilter(03): 04 Fan Failure event - enabled for alert
      PEFilter(04): 05 Chassis Intrusion event - enabled for alert
      PEFilter(05): 08 Power Supply Fault event - enabled for alert
      PEFilter(06): 0c Memory ECC Error event - enabled for alert
      PEFilter(07): 0f BIOS POST Error event - enabled for alert
      PEFilter(08): 07 FRB Failure event - enabled for alert
      PEFilter(09): 13 Fatal NMI event - enabled for alert
      PEFilter(10): 23 Watchdog Timer Reset event - enabled for alert
      PEFilter(11): 12 System Restart event - enabled for alert
      PEFilter(12): 20 OS Critical Stop event - enabled for alert
      PEFilter(13): 09 Power Redundancy Lost event - enabled for alert
      PEF Control: 01 : PEFenable
      PEF Actions: 0f : Alert PwrDn Reset PwrCyc
      PEF Startup Delay: 3c : 60 sec
      PEF Alert Startup Delay: 3c: 60 sec
      PEF Alert Policy[1]: 01 18 11 00 : Chan[1] Dest[1] Enabled
      PEF Alert Policy[2]: 02 28 23 00 : Chan[2] Dest[3] Enabled
      PEF Alert Policy[3]: 03 38 11 00 : Chan[1] Dest[1] Enabled
      PEF Alert Policy[4]: 04 38 23 00 : Chan[2] Dest[3] Enabled

      pefconfig, GetLanEntry for channel 3 ...
      Lan Param(0) Set in progress: 00
      Lan Param(1) Auth type support: 15 : None MD5 Pswd
      Lan Param(2) Auth type enables: 14 14 14 14 00
      Lan Param(3) IP address: 172 17 64 57
      Lan Param(4) IP addr src: 01 : Static
      Lan Param(5) MAC addr: 00 0d 5d 05 03 61
      Lan Param(6) Subnet mask: 255 255 255 0
      Lan Param(7) IPv4 header: 40 40 10
      Lan Param(10) BMC grat ARP: 00 : ARP disabled Grat-ARP disabled
      Lan Param(11) grat ARP interval: 04 : 2 sec
      Lan Param(12) Def gateway IP: 172 17 64 254
      Lan Param(13) Def gateway MAC: 00 14 XX XX XX 40 ----------------------------//It is a resolved MAC
      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:
      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
      Channel Access Mode(3=lan): 22 04 : Access = Always Avail, PEF Alerts Disabled
      pefconfig, GetSOL for channel 3 ...
      SOL Enable: 01 : enabled
      SOL Auth: 02 : User
      SOL Accum Interval: 04 32 : 20 msec
      SOL Retry Interval: 06 14 : 200 msec
      SOL nvol Baud Rate: 07 : 19.2k
      SOL vol Baud Rate: 07 : 19.2k
      SOL Payload Support(3): 03 00 15 00 00 00 00 00
      SOL Payload Access(3,1): 02 00 00 00 : enabled
      SOL Payload Access(3,2): 02 00 00 00 : enabled
      SOL Payload Access(3,3): 00 00 00 00 : disabled
      SOL Payload Access(3,4): 00 00 00 00 : disabled
      Get User Access(1): 0f 04 01 34 : IPMI, Admin  () 
      Get User Access(2): 0f 04 01 14 : IPMI, Admin  (admin)  ---------------------------//activate user admin
      Get User Access(3): 0f 04 01 3f : IPMI, No access (admin2)
      Get User Access(4): 0f 04 01 3f : IPMI, No access (admin3)
      pefconfig, completed successfully

      ok, In local...

      C:\>ipmiutil alarms
      ipmiutil ver 2.33
      alarms ver 2.33
      -- BMC version 0.64, IPMI version 2.0
      get_alarms: ret = 0, ccode 83, alarms = 00
      Could not obtain Telco LED states, Telco alarm panel may not be present.

      disk slot 0 LED:   off
      disk slot 1 LED:   off
      disk slot 2 LED:   off
      disk slot 3 LED:   off
      disk slot 4 LED:   off
      disk slot 5 LED:   off
      alarms, completed successfully

      OK. But in LAN

      C:\>ipmiutil alarms -N 172.17.64.57 -U admin -P password
      ipmiutil ver 2.33
      alarms ver 2.33
      Opening lan connection to node 172.17.64.57 ...
      Connected to node  172.17.64.57
      pong timeout, after bind complete
      ipmilan_open_session error, rv = -3
      ipmilan BMC receive failed
      ipmi_open error = -3
      alarms, BMC receive failed

      C:\>ipmiutil alarms -N 172.17.64.57 -U admin -P password -F lan2i
      ipmiutil ver 2.33
      alarms ver 2.33
      Opening lanplus connection to node 172.17.64.57 ...
      Error: Unable to establish IPMI v2 / RMCP+ session
      ipmi_open_lan2 error -1
      alarms, error -1

      We does not know  how to continue....

       
    • Juan Garcia

      Juan Garcia - 2009-02-16

      Ok, the issue it has been solve.
      We update the firmware to version 6717. And now, it run correct.

      thank you very much for the help

       
      • Andy Cress

        Andy Cress - 2009-02-16

        Good thinking.  That makes sense that it needed a firmware upgrade.  That was the key difference between mine and yours. 

         

Log in to post a comment.

MongoDB Logo MongoDB