Hi,

I was wondering if anyone could shed any light on a couple of questions.
I've been reading the archives and docs, but haven't seen an answer to
these as yet. Thanks in advance for any help:

1) Why do any of the "ipmitool chassis policy <state>" commands fail with
the error:

 Power Restore Policy command failed: Invalid command

I've tried sending this both locally and over the network using a lanplus
itnerface. Other commands work, but this command doesn't, but I can see
from "chassis status" that the "Power Restore Policy" is always-off and
I'd like to change it. Looking at the list archives I found a mention of
a "-g" switch to ipmitool if you encounter problems, but I don't see any
documentation for it (and it doesn't seem to help). I tried to use -o, but
I didn't know what OEM to use. Its a Tyan m/b with Tigon 3 NIC's, but
"ipmitool mc info" reports the BMC as unknown:

 | Device ID                 : 32
 | Device Revision           : 1
 | Firmware Revision         : 1.6
 | IPMI Version              : 2.0
 | Manufacturer ID           : 20569
 | Manufacturer Name         : Unknown (0x5059)
 | Product ID                : 17 (0x0011)

lspci lists both NIC's as:

 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit
 Ethernet PCI Express (rev 11)


2) I put my server out in the data center a months or two ago. I can reach
it via ipmi without any problem when its running, but the one time it
crashed I couldn't get it to respond to a power on command. Any suggestions
as to why this might be?

Currently there is only this one server so it is plugged directly into the
data center's switch port. I was wondering if it seems likely that this is
occuring because the switch sees the link drop and so the switch itself
rejects the IPMI traffic, so it never reaches the BMC?  I had this working
on a local LAN segment without any problem which I assume is because it was
on the same LAN segment and thus the other box knew the MAC address of the
server?

If this is the case, how do I prevent this from being a problem?  I enabled
gratuitous arping (see below) on the BMC to fix this problem, but it didn't
help. Since the ARP announcements are generated by the BMC and presently
there's only one cable between it and the switch I have no idea if they're
actually being generated, but I assume it is.

| # ipmitool lan print 6
| Set in Progress         : Set Complete
| 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      : NONE MD2 MD5 PASSWORD
| IP Address Source       : Unspecified
| IP Address              : 38.xx.xx.xx
| Subnet Mask             : 255.255.255.224
| MAC Address             : 00:a0:d1:e1:xx:xx
| SNMP Community String   : XletmeinX
| IP Header               : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
| BMC ARP Control         : ARP Responses Enabled, Gratuitous ARP Enabled
| Gratituous ARP Intrvl   : 2.0 seconds
| Default Gateway IP      : 38.xx.xx.xx
| Default Gateway MAC     : 00:d0:01:03:xx:xx
| 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
| Cipher Suite Priv Max   : Not Available

Will this go away the moment I throw a switch in on my side or do I need
another box out there too and access it across that network segment? I
read on the list that the e1000 NIC's disable this. This board has these
NICs: on it:

 eth0: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express)
 10/100/1000BaseT Ethernet 00:a0:d1:e1:xx:xx

does anyone know if this setting works on this card?


3) Finally - What are the kernel patches on the ipmitools site for?
Are they for local access to the BMC as I don't seem to need them for
remote access at all now that its configured? Do I need it for SOL?
When I load them, this is what is shown in dmesg:

 | ipmi message handler version 38.0
 | IPMI System Interface driver.
 | ipmi_si: Found SMBIOS-specified state machine at I/O address 0xca2, slave
 | address 0x20
 |  IPMI kcs interface initialized
 | ipmi device interface

Thanks in advance,

Colin.

--
 "Developers are like artists; they produce their best work if they
  have the freedom to do so" - Werner Vogels, CTO Amazon.com


-------------------------------------------------------------------------
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

Reply via email to