INIT failed status and Problem communicating with BSMP on IBM Blade Chassis

I have a fully loaded Blade Chassis H (ie 14 Blades). I have the following symptoms similar to what was written in IBM Site INIT failed status - IBM BladeCenter HS22, HS22V

   

0X0021600 / Symptom:

BladeCenter HS22 or HS22V status is reported as Init Failed and the following error is posted in the Advanced Management Module (AMM) event log:

0x00216000 Problem communicating with BSMP

The chassis has 14 blades installed.

Workaround:

Remove one blade from the chassis.

Solution:
Install AMM firmware v3.54L (BPET54L) or later.

The file is available by selecting the appropriate machine type on the 'Software and device drivers - IBM BladeCenter' web page, at the following URL:

IBM  Blade Chassis Product View

Patching

Select the correct Blade Chassis Product. Since I am using Blade Chassis H, my fixes were

ibm_fw_amm_bpet62o_anyos_noarch
(IBM BladeCenter Advanced Management Module Firmware Update)

The patching will require restart of the AMM. Restarting the Advanced Management Module will disconnect your current session. 

CUDA Toolkits, Webinars and Downloads

Useful Information for those who are interested in Nvidia GP-GPU

1. GPU Computing Webinars 
2. CUDA Downloads 
3. NVIDIA GPUDirect
4. NVIDIA GPU Computing Documentation
5. CUDA Tools & Ecosystem
6. CUDA GPUs
7. CUDA Newsletter

Listing of Hardware Address of Network Cards

To quickly list Hardware Address of all your Network Cards in a nice listings, you can just use a simple commands

# ifconfig -a |grep HWaddr

eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:1a
eth1      Link encap:Ethernet  HWaddr 00:00:00:00:00:1b
eth2      Link encap:Ethernet  HWaddr 00:00:00:00:00:1c

"Device eth0 does not seem to be present" on cloned CentOS VM

After cloning the a CentOS 6 Virtual Machine from a VMware VM Template. On powering, I encountered the error "Device eth0 does not seem to be present".

Basically, in a nutshell, the OS remembers the old NIC of the template and new NIC provided after the clone are assigns as though they were new NICs. To solve the problem, remove the "SUBSYSTEM" entry that contains the old entry and change the eth1 to eth0 accordingly.

# vim /etc/udev/rules.d/70-persistent-net.rules

# PCI device 0x15ad:0x07b0 (vmxnet3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:50:56:ae:00:1a", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x15ad:0x07b0 (vmxnet3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:50:56:ae:00:1b", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x15ad:0x07b0 (vmxnet3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:50:56:ae:00:1b", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

Remember to modify the /etc/sysconfig/network-scripts/ifcfg-eth0 to reflect the correct changes.

Once you are done, reload the udev configuration. See Updating the udev configuration on CentOS

There is a very good and complete information written on this whole issue.
Cloned Red Hat/CentOS/Scientific Linux Virtual Machines and “Device eth0 does not seem to be present” Message

No module named numpy when executing alpspython on CentOS 5

I was using testing out alps-2.0.2 on CentOS 5.4 .When I typed the following:

$ /usr/local/alps2.0.2/bin/alpspython

$ import pyalps

I got this error instead

Traceback (most recent call last):

  File "", line 1, in ?
  File "/usr/local/alps-2.0.2/lib/pyalps/__init__.py", line 37, in ?
    from dataset import *
  File "/usr/local/alps-2.0.2/lib/pyalps/dataset.py", line 29, in ?
    import numpy as np
ImportError: No module named numpy

The resolution was easier than I thought, just do a

# yum install python-numpy

The respective libraries will be installed