BMC issues with Poweredge 1950

Ram, Prashanth Prashanth.Ram at stratus.com
Thu Aug 2 15:17:10 CDT 2007


Hi Fred:
 
Sorry for the delay in getting back to you. I am communicating to the
bad node from the good node via a cross link. I can successfully
communicate to the good node via the bad node, so I know that the
connection is functional. I can also ping successfully both ways (good <
-- > bad)
 
 
Thanks!
 
== The output from the bad node  ==
$ ipmitool -I open lan print 1
Set in Progress         : Set In Progress
Auth Type Support       : NONE MD2 MD5 PASSWORD
Auth Type Enable        : Callback : NONE MD2 MD5 PASSWORD
                        : User     : NONE MD2 MD5 PASSWORD
                        : Operator : NONE MD2 MD5 PASSWORD
                        : Admin    : NONE MD2 MD5 PASSWORD
                        : OEM      : MD2 MD5
IP Address Source       : Static Address
IP Address              : 169.254.241.13
Subnet Mask             : 255.255.0.0
MAC Address             : 00:13:72:f8:dc:6b
SNMP Community String   : private
IP Header               : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
Default Gateway IP      : 0.0.0.0
Default Gateway MAC     : 00:00:00:00:00:00
Backup Gateway IP       : 0.0.0.0
Backup Gateway MAC      : 00:00:00:00:00:00
802.1q VLAN ID          : Disabled
802.1q VLAN Priority    : 0
RMCP+ Cipher Suites     : 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14
Cipher Suite Priv Max   : aaaaaaaaaaaaaaa
                        :     X=Cipher Suite Unused
                        :     c=CALLBACK
                        :     u=USER
                        :     o=OPERATOR
                        :     a=ADMIN
                        :     O=OEM
 
 
== The output from the good node  ==
$ipmitool -I open lan print 1
Set in Progress         : Set In Progress
Auth Type Support       : NONE MD2 MD5 PASSWORD
Auth Type Enable        : Callback : NONE MD2 MD5 PASSWORD
                        : User     : NONE MD2 MD5 PASSWORD
                        : Operator : NONE MD2 MD5 PASSWORD
                        : Admin    : NONE MD2 MD5 PASSWORD
                        : OEM      : MD2 MD5
IP Address Source       : Static Address
IP Address              : 169.254.38.186
Subnet Mask             : 255.255.0.0
MAC Address             : 00:13:72:f8:c6:aa
SNMP Community String   : private
IP Header               : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
Default Gateway IP      : 0.0.0.0
Default Gateway MAC     : 00:00:00:00:00:00
Backup Gateway IP       : 0.0.0.0
Backup Gateway MAC      : 00:00:00:00:00:00
802.1q VLAN ID          : Disabled
802.1q VLAN Priority    : 0
RMCP+ Cipher Suites     : 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14
Cipher Suite Priv Max   : aaaaaaaaaaaaaaa
                        :     X=Cipher Suite Unused
                        :     c=CALLBACK
                        :     u=USER
                        :     o=OPERATOR
                        :     a=ADMIN
                        :     O=OEM
 
________________________________

From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Fred Skrotzki
Sent: Friday, July 27, 2007 1:04 PM
To: linux-poweredge at dell.com
Subject: RE: BMC issues with Poweredge 1950
 
You can't issue the Lan based commands to the BMC of the system you are
running the command from, you must send it from a different system.  The
reasoning behind this is simple.  the BMC lisens on the same receive
lines as the NIC and if the local system is tranmitting the recieve
lines will NEVER hear the command.  Also the switch upstream will NOT
repeat the request down the port the request came only the other
available active ports.
 
Issue the following command on the box in question
ipmitool -I open lan print 1
and provide what it reports please.
 
 
 
________________________________

From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Ram, Prashanth
Sent: Friday, July 27, 2007 8:28 AM
To: Krishnaprasad_K at dell.com; linux-poweredge at lists.us.dell.com
Subject: RE: BMC issues with Poweredge 1950
Sad but true; Same error
 
$ ipmitool -I lan -U root -H 169.254.150.49 -P rootuser  sdr
Error: Unable to establish LAN session
ipmi_lan_send_cmd failed to open intf
Get Device ID command failed
Unable to open SDR for reading
 
Thanks!
Prashanth
 
 
________________________________

From: Krishnaprasad_K at Dell.com [mailto:Krishnaprasad_K at Dell.com] 
Sent: Friday, July 27, 2007 8:09 AM
To: Ram, Prashanth; linux-poweredge at lists.us.dell.com
Subject: RE: BMC issues with Poweredge 1950
 
Hi,
 
                Instead of giving peerbmc can you try with BMC IP
address. How about the command below
 
                ipmitool -I lan -U root -H < BMC IPaddress > sdr 
 
      
Thanks
Krishnaprasad
 
            
 
From: Ram, Prashanth [mailto:Prashanth.Ram at stratus.com] 
Sent: Friday, July 27, 2007 5:19 PM
To: K, Krishnaprasad; linux-poweredge-Lists
Subject: RE: BMC issues with Poweredge 1950
 
Hi..
            No luck, I'm still getting the same error message. I even
tried to power cycle to bmc via the mc command, to no avail.
 
Thanks!
 
 
== peerbmc node ==
[root at chojp ~]# ipmitool user list 1
ID  Name             Callin  Link Auth  IPMI Msg   Channel Priv Limit
1                    true    true       true       ADMINISTRATOR
2   root             true    true       true       ADMINISTRATOR
[root at chojp ~]# ipmitool user list 2
ID  Name             Callin  Link Auth  IPMI Msg   Channel Priv Limit
1                    true    true       true       NO ACCESS
2   root             true    true       true       ADMINISTRATOR
 
==  good node ==
ipmitool user list 1
ID  Name             Callin  Link Auth  IPMI Msg   Channel Priv Limit
1                    true    true       true       ADMINISTRATOR
2   root             true    true       true       ADMINISTRATOR
[root at chojs ~]# ipmitool user list 2
ID  Name             Callin  Link Auth  IPMI Msg   Channel Priv Limit
1                    true    true       true       NO ACCESS
2   root             true    true       true       ADMINISTRATOR 
________________________________

From: Krishnaprasad_K at Dell.com [mailto:Krishnaprasad_K at Dell.com] 
Sent: Friday, July 27, 2007 3:12 AM
To: Ram, Prashanth; linux-poweredge at lists.us.dell.com
Subject: RE: BMC issues with Poweredge 1950
 
Hi,
 
You may have to enable lan access for getting BMC values from a remote
machine. You can do the same using BMC bios or utilities like ipmitool .
Have a look into the link below
 
Using ipmitool u can enable lan access by the following command
 
/usr/bin/ipmitool -I open lan set 1 access on
 
Have a look into the link below for configuring BMC using ipmitool
 
http://lonesysadmin.net/2005/09/23/configuring-and-securing-ipmi-on-dell
-poweredge-x8xx-hardware/
 
 
Hope this helps !
 
Thanks, 
Krishnaprasad 
 
 
Thanks, 
Krishnaprasad 
 
From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Ram, Prashanth
Sent: Friday, July 27, 2007 8:44 AM
To: linux-poweredge-Lists
Subject: BMC issues with Poweredge 1950
 
Hi,
 
            We have a BMC that won't respond to commands sent to it via
the network, but will respond to local inquiries. I've tried the basics,
(reset BMC, update FW/BIOS, check username/password for BMC), but still
no luck!  Does anyone have any ideas how to debug this problem?
 
Thanks!
 
== from node 1 to peerbmc node ==
$ipmitool -P rootuser -H peerbmc bmc info -v
Get Auth Capabilities command failed
Get Auth Capabilities command failed
Error: Unable to establish LAN session
ipmi_lan_send_cmd failed to open intf
Get Device ID command failed
 
 
== peerbmc node ==
$ipmitool  ipmitool bmc info
Device ID                 : 32
Device Revision           : 0
Firmware Revision         : 1.33
IPMI Version              : 2.0
Manufacturer ID           : 674
Manufacturer Name         : Unknown (0x2a2)
Product ID                : 256 (0x0100)
Device Available          : yes
Provides Device SDRs      : yes
Additional Device Support :
    Sensor Device
    SDR Repository Device
    SEL Device
    FRU Inventory Device
    IPMB Event Receiver
    Bridge
    Chassis Device
Aux Firmware Rev Info     :
    0x00
    0x00
    0x00
    0x00
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20070802/eb4eec0c/attachment-0001.htm 


More information about the Linux-PowerEdge mailing list