Re: [Ipmitool-devel] IPMI LAN interface stops working after upgradetoDebian squeeze... [solved]
Hi all sorry for the long delay, but this matter has been solved: It's a feature of the e1000e driver which needs to be disabled, e.g. in a file like etc/modprobe.d/e1000e: options e1000e CrcStripping=0 once this is set and the module reloaded, IPMI works as before. Sorry again for the long delay Carsten signature.asc Description: This is a digitally signed message part. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] IPMI LAN interface stops working after upgradetoDebian squeeze...
Hi On Wednesday 28 September 2011 19:32:16 Andy Cress wrote: It just occurred to me that the OS may be interfering with IPMI LAN by trying to also use the RMCP port 623. The Linux portmap service allocates any port that is not in use by the OS, so it does not know about IPMI LAN RMCP port 623. If the IPMI firmware and OS share an IP, then this could cause conflicts. If so, running a service that keeps port 623 allocated will prevent it. See http://ipmiutil.svn.sourceforge.net/viewvc/ipmiutil/trunk/util/ipmi_port.c ?revision=199 for source to a simple service that does this. If not, it could be a firmware problem. That sound's interesting, I'll have a look (and hopefully can finally come back to this after a very long todo list with higher prios). Thanks for the hint! Carsten signature.asc Description: This is a digitally signed message part. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] IPMI LAN interface stops working after upgradetoDebian squeeze...
Hi again that was easy to disprove - at least netstat -tulpen does not show any service listening on any ports in the range 600..700, but I can still trigger the problem: locally on the node: root@n1670:~# date; ifconfig eth0 up Wed Sep 28 19:38:51 CEST 2011 root@n1670:~# date; ifconfig eth0 down Wed Sep 28 19:39:18 CEST 2011 remotely while sleep 1; do echo -n $(date): ipmitool -U USER -P PASSWORD -H ipn1670 -I lan power status done Wed Sep 28 17:38:34 UTC 2011: Chassis Power is on Wed Sep 28 17:38:36 UTC 2011: Chassis Power is on Wed Sep 28 17:38:37 UTC 2011: Chassis Power is on Wed Sep 28 17:38:38 UTC 2011: Chassis Power is on Wed Sep 28 17:38:39 UTC 2011: Chassis Power is on Wed Sep 28 17:38:41 UTC 2011: Chassis Power is on Wed Sep 28 17:38:42 UTC 2011: Chassis Power is on Wed Sep 28 17:38:43 UTC 2011: Chassis Power is on Wed Sep 28 17:38:44 UTC 2011: Chassis Power is on Wed Sep 28 17:38:46 UTC 2011: Chassis Power is on Wed Sep 28 17:38:47 UTC 2011: Chassis Power is on Wed Sep 28 17:38:48 UTC 2011: Chassis Power is on Wed Sep 28 17:38:49 UTC 2011: Chassis Power is on Wed Sep 28 17:38:51 UTC 2011: Chassis Power is on Wed Sep 28 17:38:52 UTC 2011: Error: Unable to establish LAN session Unable to get Chassis Power Status Wed Sep 28 17:39:12 UTC 2011: Chassis Power is on Wed Sep 28 17:39:24 UTC 2011: Chassis Power is on Wed Sep 28 17:39:25 UTC 2011: Chassis Power is on Wed Sep 28 17:39:27 UTC 2011: Chassis Power is on Wed Sep 28 17:39:28 UTC 2011: Chassis Power is on Wed Sep 28 17:39:29 UTC 2011: Chassis Power is on (sorry about the tie zone difference, CEST is UTC+2) ... Carsten signature.asc Description: This is a digitally signed message part. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] IPMI LAN interface stops working after upgrade toDebian squeeze...
Hi On Friday 23 September 2011 21:05:57 Arkadiusz Miśkiewicz wrote: Did you find out what is the problem? Sorry not yet - I've been totally swamped with other work during the past 2 weeks - but I do need to look into this again. I've just upgraded kernel (and only that) from 2.6.38.8 to 3.0.4 on one of my machines (old Tyan S2891) and BMC stopped responding. Ethernet card here is tg3. Is your card also tg3? no e1000e, it's a Supermicro PDSML-LN2+ but the same happens also on another mainboard. What's worse after ipmitool mc reset cold ipmitool lan ... stopped recognising LAN channels. Ouch If I forget to give feedback, please kick me! Cheers Carsten -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
[Ipmitool-devel] IPMI LAN interface stops working after upgrade to Debian squeeze...
Hi we are using the old venerable PDSML-LN2+ Supermicro boards where the BMC is piggy-backed on top of eth0, thus no dedicated NIC for it. We are finally preparing to upgrade from Debian Lenny to Debian Squeeze and encounter something very special. During installation we reconfigure the IPMI settings and everything seems ok, but upon the reboot into the freshly installed system, suddenly the IPMI LAN interface stops working. Something in the running system seems to disable this, as it usually (but not always) comes back alive with a reboot (and fails again during system start-up). If I do a regular Debian lenny install everything is working as expected, even after a reboot. I'm currently totally puzzled what could be the root cause. The kernel is exactly the same, only the userland has changed: ipmitool versions: 1.8.9-2 vs. 1.8.11-2 ipmitool lan print/user list/channel ... show only the differences expected (other user name for example). locally ipmitool has no problems accessing the card, remotely neither lan nor lanplus interface works with Squeeze userland. Anyone with an idea, what to test/how to home into this problem? Cheers and thanks a lot in advance Carsten -- Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics Callinstrasse 38, 30167 Hannover, Germany Phone/Fax: +49 511 762-17185 / -17193 http://www.top500.org/system/9234 | http://www.top500.org/connfam/6 CaCert Assurer | Get free certificates from http://www.cacert.org/ smime.p7s Description: S/MIME cryptographic signature -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] IPMI LAN interface stops working after upgrade toDebian squeeze...
Hi Andy On Tuesday 06 September 2011 14:34:40 Andy Cress wrote: There are two types of shared OS/BMC NICs: 1) Where the BMC and OS have separate MAC addresses (so separate IP addresses). This is the most common. Or 2) The BMC and OS share the same MAC address and the BMC gets only the IPMI traffic to the RMCP port. Compare the IPMI LAN MAC with your OS MAC from ifconfig to see which it is. If case 2, the IP addresses must match or it will not work (arps will fail, etc.). We have yet another case (which at least for Lenny for the past 2+ yrs): Lenny: n1672:~# ipmitool lan print 1 Set in Progress : Set Complete Auth Type Support : NONE MD2 MD5 PASSWORD Auth Type Enable: Callback : MD2 MD5 PASSWORD : User : MD2 MD5 PASSWORD : Operator : MD2 MD5 PASSWORD : Admin: MD5 PASSWORD : OEM : MD2 MD5 PASSWORD IP Address Source : Static Address IP Address : 172.27.16.72 Subnet Mask : 255.240.0.0 MAC Address : 00:30:48:9a:5a:18 SNMP Community String : public IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10 BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Gratituous ARP Intrvl : 2.0 seconds 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 : Xaa : X=Cipher Suite Unused : c=CALLBACK : u=USER : o=OPERATOR : a=ADMIN : O=OEM n1672:~# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: tunl0: NOARP mtu 1480 qdisc noop state DOWN link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0: NOARP mtu 1476 qdisc noop state DOWN link/gre 0.0.0.0 brd 0.0.0.0 4: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 100 link/ether 00:30:48:9a:5a:18 brd ff:ff:ff:ff:ff:ff inet 172.26.16.72/12 brd 172.31.255.255 scope global eth0 5: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 9000 qdisc pfifo_fast state UP qlen 1000 link/ether 00:30:48:9a:5a:19 brd ff:ff:ff:ff:ff:ff inet 10.10.16.72/8 brd 10.255.255.255 scope global eth1 Thus same MAC, but different IPs (and yes, that's working) On the freshly installed Squeeze box: root@n1673:~# ipmitool lan print Set in Progress : Set Complete Auth Type Support : NONE MD2 MD5 PASSWORD Auth Type Enable: Callback : MD2 MD5 PASSWORD : User : MD2 MD5 PASSWORD : Operator : MD2 MD5 PASSWORD : Admin: MD2 MD5 PASSWORD : OEM : MD2 MD5 PASSWORD IP Address Source : Static Address IP Address : 172.27.16.73 Subnet Mask : 255.240.0.0 MAC Address : 00:30:48:9b:9e:26 SNMP Community String : public IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10 BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Gratituous ARP Intrvl : 2.0 seconds 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 : Xaa : X=Cipher Suite Unused : c=CALLBACK : u=USER : o=OPERATOR : a=ADMIN : O=OEM root@n1673:~# ip addr 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: tunl0: NOARP mtu 1480 qdisc noop state DOWN link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0: NOARP mtu 1476 qdisc noop state DOWN link/gre 0.0.0.0 brd 0.0.0.0 4: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 100 link/ether 00:30:48:9b:9e:26 brd ff:ff:ff:ff:ff:ff inet 172.26.16.73/12 brd 172.31.255.255 scope global eth0 5: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 9000 qdisc pfifo_fast state UP qlen 1000 link/ether 00:30:48:9b:9e:27 brd ff:ff:ff:ff:ff:ff inet 10.10.16.73/8 brd 10.255.255.255 scope global eth1 root@n1673:~# As it was working before, we continued with it, but maybe we are hitting something else now. Cheers Carsten
Re: [Ipmitool-devel] IPMI LAN interface stops working after upgrade toDebian squeeze...
Gi On Tuesday 06 September 2011 15:14:03 Andy Cress wrote: So you are in case 2, where the MAC is shared, so the correct configuration is to make sure that the BMC is configured for the same IP address as the OS. If anything else works, it is technically a flaw in the router, but could happen (ARPs for two different IPs resolve to the same MAC). I'm thoroughly confused now, I'm trying to summarize my current knowledge/the status: In the past we used 172.26.16.73/12 for eth0 and 172.27.16.73/12 for the BMC (same mac address) which works under Debian Lenny but not under Squeeze. If I disable eth0 via ifdown/ifconfig BMC responds almost immediately to lan requests (both lan/lanplus interfaces) If I enable eth0 via ifup/ifconfig again, BMC stops responding at once. It does not matter if I set the IP addr. of the BMC to the one of eth0, or use multiple IP addresses (eth0:0) It does not matter if I unload all ipmi modules. I tested it with the stock Debian kernel, a self built 2.6.32.y kernel (same one used for Lenny, also rebuilt for Squeeze), also 3.0.3 showed the same problem. I tried different libc6 as ifconfig seems only to interact with it (2.7, 2.11 and 2.13) to no avail. right now, I'm completely out of ideas, what to test as well. I'm still suspecting the user land which might be responsible here. but I don't know what. Cheers Carsten -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] Reading GPU temperature via IPMI
Hi On Wednesday 29 December 2010 08:09:00 Vahid wrote: I can read CPU_TEMP, CPU_FAN,... sensors, is it possible to add GPU temperature or GPU fan speed to IPMI ? I'm no developer only a user, but I doubt it. I'm not aware of any standardized interface for GPU temperatures. We - for example - need to use nvidia's smi to gather those. gpu010:~# nvidia-smi --query-gpu-info --gpu=0 ==NVSMI LOG== Timestamp : Wed Dec 29 10:17:20 2010 Driver Version : 260.19.21 GPU 0: Product Name: Tesla C2050 PCI Device/Vendor ID: 6d110de PCI Location ID : 0:A:0 Board Serial: 0321610134404 Display : Not connected Temperature : 68 C Fan Speed : 30% Utilization GPU : 0% Memory : 0% Volatile ECC errors : Single bit: FB : 0 RF : 0 L1 : 0 L2 : 0 Total : 0 Double bit: FB : 0 RF : 0 L1 : 0 L2 : 0 Total : 0 Aggregate ECC errors: Single bit: Total : 0 Double bit: Total : 0 But maybe the developers know about a way to link these, but I fear this needs a standard which does not yet exists... Cheers Carsten -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] Geting ipmitool working with Tyan S7025 IPMI
Addendum: I can configure the lan interface but do not get any readings there either :(. Do I have to activate something? I'll check again the BIOS if everything's alright there, but I think it is. Cheers carsten -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] change ipmi addr
Hi On Tuesday 09 February 2010 08:25:53 Aclhk Aclhk wrote: pls advise how to use ipmitool to change ipmi address What is the address you are referring to? So you mean the IP-settings for remote access? Cheers Carsten -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] Q about SOL during linux kernel boot
Hi James, James Pearson wrote: Does the SOL share the same network interface as used by the OS? I've see cases where SOL will be dropped when the OS loads/uses the NIC driver. On dual NIC machines, we use the 2nd NIC for the OS and leave the first NIC for IPMI Yes, that could be the reason (we are using both, eth0 for mgmt. and eth1 for data), the IPMI is tunneled through eth0. hmmm, do you know a way around that - if there exists something like that at all? Cheers Carsten -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] Q about SOL during linux kernel boot
Hi Mike, Mike Lovell wrote: Check your /etc/inittab. It should have a line that is something like this T1:23:respawn:/sbin/getty -L ttyS1 19200 vt100 It looks like the kernel is using the serial port for the console but there isn't a getty running on it. So give that line in inittab a try. Yes, that's there (not necessarily during our installation but yes), what I see is: kernel starting up, then nothing and after 30-60 seconds I see the login prompt. What I'm missing is the start-up of the daemons and other init scripts. Cheers Carsten -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
[Ipmitool-devel] How to react to intermittent fan failure message?
Hi all, I've a more practical question than one which is directly related to ipmitool itself. If you look at the output of ipmitool sel elist below you will see intermittent fan failures where a fan seems to stop briefly and then continue to run. Anyone with a good approach how to act upon these? o Shall one simply ignore these and delete from the logs unless they come back regularly and are confirmed by ipmitool sensor? o Is there a way to insert a kind of 'timeout' into the IPMI card that the condition has to be true for a period of time? Cheers Carsten 1e1 | 11/01/2008 | 23:33:50 | Fan Fan2 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1e2 | 11/01/2008 | 23:33:50 | Fan Fan2 | Lower Critical going low | Reading 0 Threshold 300 RPM 1e3 | 11/01/2008 | 23:33:50 | Fan Fan2 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1e4 | 11/03/2008 | 00:45:22 | Fan Fan2 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1e5 | 11/03/2008 | 00:45:22 | Fan Fan2 | Lower Critical going low | Reading 0 Threshold 300 RPM 1e6 | 11/03/2008 | 00:45:22 | Fan Fan2 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1e7 | 11/04/2008 | 17:42:38 | Fan Fan3 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1e8 | 11/04/2008 | 17:42:38 | Fan Fan3 | Lower Critical going low | Reading 0 Threshold 300 RPM 1e9 | 11/04/2008 | 17:42:38 | Fan Fan3 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1ea | 11/07/2008 | 09:00:18 | Fan Fan2 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1eb | 11/07/2008 | 09:00:18 | Fan Fan2 | Lower Critical going low | Reading 0 Threshold 300 RPM 1ec | 11/07/2008 | 09:00:18 | Fan Fan2 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1ed | 11/10/2008 | 01:29:09 | Fan Fan4 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1ee | 11/10/2008 | 01:29:09 | Fan Fan4 | Lower Critical going low | Reading 0 Threshold 300 RPM 1ef | 11/10/2008 | 01:29:09 | Fan Fan4 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1f0 | 11/10/2008 | 21:14:35 | Fan Fan4 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1f1 | 11/10/2008 | 21:14:35 | Fan Fan4 | Lower Critical going low | Reading 0 Threshold 300 RPM 1f2 | 11/10/2008 | 21:14:35 | Fan Fan4 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1f3 | 11/18/2008 | 17:30:55 | Fan Fan2 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1f4 | 11/18/2008 | 17:30:55 | Fan Fan2 | Lower Critical going low | Reading 0 Threshold 300 RPM 1f5 | 11/18/2008 | 17:30:55 | Fan Fan2 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1f6 | 11/21/2008 | 01:33:08 | Fan Fan4 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1f7 | 11/21/2008 | 01:33:08 | Fan Fan4 | Lower Critical going low | Reading 0 Threshold 300 RPM 1f8 | 11/21/2008 | 01:33:08 | Fan Fan4 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1f9 | 11/21/2008 | 16:25:24 | Fan Fan4 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1fa | 11/21/2008 | 16:25:24 | Fan Fan4 | Lower Critical going low | Reading 0 Threshold 300 RPM 1fb | 11/21/2008 | 16:25:24 | Fan Fan4 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1fc | 11/23/2008 | 19:44:32 | Fan Fan4 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 1fd | 11/23/2008 | 19:44:32 | Fan Fan4 | Lower Critical going low | Reading 0 Threshold 300 RPM 1fe | 11/23/2008 | 19:44:32 | Fan Fan4 | Lower Non-recoverable going low | Reading 0 Threshold 200 RPM 1ff | 11/24/2008 | 12:54:57 | Fan Fan3 | Lower Non-critical going low | Reading 0 Threshold 400 RPM 200 | 11/24/2008 | 12:54:57 | Fan Fan3 | Lower Critical going low | Reading 0 Threshold 300 RPM -- Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics Callinstrasse 38, 30167 Hannover, Germany Phone/Fax: +49 511 762-17185 / -17193 http://www.top500.org/system/9234 | http://www.top500.org/connfam/6/list/31 -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
[Ipmitool-devel] Q about SOL during linux kernel boot
Hi all, another question just waited for us in the darkness and jumped right into our faces. When we boot a machine we cannot follow the boot process through the end but it just stops at some point and we have no idea why. Can anyone enlighten us please? Cheers Carsten Boot line: append root=/dev/nfs nfsroot=/srv/fai/nfsroot/live/filesystem.dir,v3,tcp,rsize=32768,wsize=32768 ip=::dhcp nofb console=ttyS1,19200 FAI_FLAGS=verbose,sshd,createvt,reboot FAI_ACTION=install Output during SOL session: [0.840001] pnp 00:01: io resource (0x72-0x77) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.844001] pnp 00:01: io resource (0x80-0x80) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.848001] pnp 00:01: io resource (0x90-0x9f) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.852001] pnp 00:01: io resource (0xa4-0xa5) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.856001] pnp 00:01: io resource (0xa8-0xa9) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.860001] pnp 00:01: io resource (0xac-0xad) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.864001] pnp 00:01: io resource (0xb0-0xb5) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.868001] pnp 00:01: io resource (0xb8-0xb9) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.872001] pnp 00:01: io resource (0xbc-0xbd) overlaps :00:1c.0 BAR 7 (0x0-0xfff), disabling [0.876001] pnp 00:01: io resource (0x295-0x296) overlaps :00:1c.0 BAR 7 (0x0-0xfff), diá[3.102325] Simple Boot Flag at 0x36 set to 0x1 [3.130321] IA-32 Microcode Update Driver: v1.14a tig...@aivazian.fsnet.co.uk [3.174527] audit: initializing netlink socket (disabled) [3.206852] type=2000 audit(1231324664.203:1): initialized [3.240339] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [3.278496] SGI XFS with security attributes, large block/inode numbers, no debug enabled [3.327751] msgmni has been set to 16010 [3.351275] async_tx: api initialized (sync-only) [3.379433] io scheduler noop registered [3.402886] io scheduler anticipatory registered [3.430498] io scheduler deadline registered [3.456046] io scheduler cfq registered (default) [3.484413] pcieport-driver :00:01.0: found MSI capability [3.519463] pcieport-driver :00:1c.0: found MSI capability [3.554558] pcieport-driver :00:1c.4: found MSI capability [3.589663] pcieport-driver :00:1c.5: found MSI capability [3.624933] vga16fb: mapped to 0x880a [3.802992] Console: switching to colour frame buffer device 80x30 [4.124312] fb0: VGA16 VGA frame buffer device [4.152912] Non-volatile memory driver v1.2 [4.178074] intel_rng: FWH not detected [4.201046] Linux agpgart interface v0.103 [4.225619] ipmi message handler version 39.2 [4.251719] ipmi device interface [4.271589] IPMI System Interface driver. [4.295608] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca8, slave address 0x20, irq 0 [5.086483] ipmi: Found new BMC (man_id: 0x0015d9, prod_id: 0x1134, dev_id: 0x20) [5.131847] IPMI kcs interface initialized [5.156388] Copyright (C) 2004 MontaVista Software - IPMI Powerdown via sys_reboot. [5.270231] IPMI poweroff: ATCA Detect mfg 0x15D9 prod 0x1134 [5.304660] IPMI poweroff: Unable to find a poweroff function that will work, giving up [5.363646] Serial: 8250/16550 driver4 ports, IRQ sharing enabled [5.400245] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [5.436367] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [5.472672] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [5.506164] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [5.540856] brd: module loaded [5.559750] loop: module loaded [5.578677] nbd: registered device at major 43 [5.606545] Intel(R) PRO/1000 Network Driver - version 7.3.20-k3-NAPI [5.645115] Copyright (c) 1999-2006 Intel Corporation. [5.675922] e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6 [5.712406] e1000e: Copyright (c) 1999-2008 Intel Corporation. [5.747336] e1000e :0d:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [5.916141] :0d:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:30:48:9b:9b:b0 [5.960403] :0d:00.0: eth0: Intel(R) PRO/1000 Network Connection [5.998582] :0d:00.0: eth0: MAC: 2, PHY: 2, PBA No: ff-0ff [6.035625] e1000e that's the end... -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] Ipmi help
Paras pradhan wrote: - r...@xendev1 ~]# ipmitool lan print 1 Set in Progress : Set Complete Auth Type Support : NONE MD5 PASSWORD Auth Type Enable: Callback : : User : : Operator : : Admin: MD5 PASSWORD : OEM : IP Address Source : Static Address IP Address : 10.42.21.28 Subnet Mask : 255.255.0.0 MAC Address : 00:15:17:5a:15:62 With this setup you should be able to do impitool -U admin -P admin -I lan -H 10.42.2.28 chassis status from any machine in the 10.42.0.0/16 range *except* the very same machine *if* the IPMI card and the system are sharing a network interface. Carsten -- ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] Ipmi help
Hi Paras pradhan wrote: Its' not working. If ipmi is correctly setup, i should be able to ping the ip address assigned to the ipmi right?. The network address of eth0 of my machine and that of ipmi interface is same. What i am missing here? No, the IP addresses of eth0 and the IPMI card need to be different, especially when IPMI is tunneled on the same interface. Can you give us the output of ipmitool lan print 1 (or whatever is the lan channel you have configured) as well as the output of ifconfig eth0? Cheers Carsten -- ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Re: [Ipmitool-devel] Supermicro IPMI Network Problems
Hi Mike Mike Lovell wrote: Do any of you have any recommendations on things to try? Have any of you had experiences similar to this? Do the Supermicro cards really suck this bad? At first I was thinking it was just one or two bad cards. But after at least 20 doing something like this, I wonder if it is a flaw in the cards. Any information that you all might have would be greatly appreciated. Thanks for the help. we have also many SM based systems (~1500) and it looks that sometimes these are hanging. Most of the time the cards seem to need a full power cycle which involves a complete disconnection from power. What we found out so far is that it helps if you query the cards quite often over the network, i.e. it seems they die more often when they are idle. Sorry for not having a definite help Cheers Carsten -- Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics Callinstrasse 38, 30167 Hannover, Germany Phone/Fax: +49 511 762-17185 / -17193 http://www.top500.org/system/9234 | http://www.top500.org/connfam/6/list/31 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
[Ipmitool-devel] Setting threshold fails?
Hi there, sorry in advance for this possibly dumb question, but how do I set a threshold? I have many Supermicro AOC-IPMI-1U IPMI cards and they work ok, however the factory defaults of some settings are not good: n0005:~# ipmitool -V ipmitool version 1.8.9 n0005:~# ipmitool sensor list CPU | 25.000 | degrees C | ok| na| na | na| 76.000| 78.000| 80.000 System | 26.000 | degrees C | ok| na| na | na| 76.000| 78.000| 80.000 CPU Core | 1.272 | Volts | ok| 0.896 | 0.904 | 0.912 | 1.384 | 1.392 | 1.400 DIMM | 1.808 | Volts | ok| 1.568 | 1.584 | 1.600 | 1.984 | 2.000 | 2.016 3.3V | 3.344 | Volts | ok| 2.912 | 2.928 | 2.944 | 3.648 | 3.664 | 3.680 5V | 4.968 | Volts | ok| 4.416 | 4.440 | 4.464 | 5.520 | 5.544 | 5.568 5VSB | 4.896 | Volts | ok| 4.416 | 4.440 | 4.464 | 5.520 | 5.544 | 5.568 12V | 11.712 | Volts | ok| 10.464| 10.560 | 10.656| 13.344| 13.440| 13.536 -12V | -12.381| Volts | ok| -13.871 | -13.722 | -13.573 | -10.444 | -10.295 | -10.146 Battery | 3.200 | Volts | ok| 2.912 | 2.928 | 2.944 | 3.648 | 3.664 | 3.680 FAN1 | 13635.000 | RPM| ok| 270.000 | 405.000 | 540.000 | na| na| na FAN2 | 13500.000 | RPM| ok| 270.000 | 405.000 | 540.000 | na| na| na FAN3 | 13770.000 | RPM| ok| 270.000 | 405.000 | 540.000 | na| na| na FAN4 | 0.000 | RPM| ok| 270.000 | 405.000 | 540.000 | na| na| na FAN5 | 0.000 | RPM| ok| 270.000 | 405.000 | 540.000 | na| na| na FAN6/CPU | 0.000 | RPM| ok| 270.000 | 405.000 | 540.000 | na| na| na Intrusion| 0.000 | unspecified | nc| 0.000 | na | 0.000 | 0.000 | na| na Power Supply | 0.000 | unspecified/uns | cr| 0.000 | na | 0.000 | 0.000 | na| na (sorry for the line wrap) For example I want to change the CPU core temperature levels to 60 65 and 70 degrees, i.e. I start n0005:~# ipmitool sensor thresh CPU upper 60 65 70 Locating sensor record 'CPU'... Setting sensor CPU Upper Non-Critical threshold to 60.000 Error setting threshold: Invalid data field in request Setting sensor CPU Upper Critical threshold to 65.000 Error setting threshold: Invalid data field in request Setting sensor CPU Upper Non-Recoverable threshold to 70.000 Error setting threshold: Invalid data field in request Neither stracing nor running with -vvv gives (me) much help: n0005:~# ipmitool -vvv sensor thresh CPU upper 60 65 70 Locating sensor record 'CPU'... Using ipmi device 0 Set IPMB address to 0x20 SDR free space: 5404 SDR records : 18 SDR reservation ID 002d OpenIPMI Request Message (6 bytes) 2d 00 00 00 00 05 SDR record ID : 0x SDR record id mismatch: 0x0001 SDR record type : 0x01 SDR record next : 0x0002 SDR record bytes: 46 Getting 46 bytes from SDR at offset 5 OpenIPMI Request Message (6 bytes) 2d 00 00 00 05 2e Getting 46 bytes from SDR at offset 5 OpenIPMI Request Message (6 bytes) 2d 00 00 00 05 2e Getting 46 bytes from SDR at offset 5 OpenIPMI Request Message (6 bytes) 2d 00 00 00 05 2e Getting 30 bytes from SDR at offset 5 OpenIPMI Request Message (6 bytes) 2d 00 00 00 05 1e Getting 14 bytes from SDR at offset 5 OpenIPMI Request Message (6 bytes) 2d 00 00 00 05 0e Getting 14 bytes from SDR at offset 19 OpenIPMI Request Message (6 bytes) 2d 00 00 00 13 0e Getting 14 bytes from SDR at offset 33 OpenIPMI Request Message (6 bytes) 2d 00 00 00 21 0e Getting 4 bytes from SDR at offset 47 OpenIPMI Request Message (6 bytes) 2d 00 00 00 2f 04 Setting sensor CPU Upper Non-Critical threshold to 60.000 OpenIPMI Request Message (8 bytes) 00 08 00 00 00 3c 00 00 Error setting threshold: Invalid data field in request Setting sensor CPU Upper Critical threshold to 65.000 OpenIPMI Request Message (8 bytes) 00 10 00 00 00 00 41 00 Error setting threshold: Invalid data field in request Setting sensor CPU Upper Non-Recoverable threshold to 70.000 OpenIPMI Request Message (8 bytes) 00 20 00 00 00 00 00 46 Error setting threshold: Invalid data field in request Any idea what I'm missing? Thanks in advance Carsten -- Dr. Carsten Aulbert - Max Planck Institut für Gravitationsphysik Callinstraße 38, 30167 Hannover, Germany Fon: +49 511 762 17185, Fax: +49 511 762 17193 - This SF.net email is sponsored by: Microsoft Defy all
