IBM BladeCenter's

Chuckles · 29-03-2009, 18:08

Anyone here an expert with BladeCenter's?

I've got a bit of a tricky question which I'll type out if anyone is familiar with them!

Daz · 29-03-2009, 18:24

Not familiar with IBMs, but had a good sniff around Dell's if that's any use?

Chuckles · 29-03-2009, 18:44

Probably specific to IBM this, but I'll explain anyway.

Got 2 Blade Center S's on 2 different sites.

IBM released a firmware update (2.48C) for the AMM (Advanced Management Module) which was marked as critical. I updated one, no problems at all.

The second however didn't come back after the AMM restart. The blades however were fine. I noticed from the DHCP server that the AMM had picked up an address from there which it shouldn't as it's static. This made me wonder whether it had somehow reset to defaults. I took it out the LAN and plugged it into my macbook (which I'd assigned a suitable IP to connect to the default IP of 192.168.70.125).

I could connect to the webadmin page using the default IP so I thought I could just reset everything. Unfortunately, I couldn't login (Just got incorrect username/password) using either an account I created, the renamed default account or the default account with the default password.

Logged a call with IBM who agreed to send out a replacement AMM. I swapped them out (they are hotswappable) and I could connect again. Unfortunately, the AMM wouldn't recognise any blades, I/O modules or anything in the hardware VPD. It also couldn't detect the temperature and so put a warning light on the chassis and blew the fans at 100%. It did the same even after 3 restarts via the web interface.

I tried updating the firmware to the latest again and guess what? The IP reset to default and all the accounts were locked out again

The status light did go back to green which indicates that since the FW update, it can read in the blade info and temp sensors etc.

This is my first support request with IBM and to be honest, they aren't a patch on Dell and don't seem to know as much about their hardware than I do, and I've only got about 4 months experience. I'm going to carry on the support log and have updated the situation but I'm not sure they are going to be of much help.

All I can think of is get them to send another AMM and update the firmware revisions 1 at a time until I find a version that can read the VPD but doesn't screw up and reset to defaults.

Thankfully during all this time, the blades themselves have all stayed up and running fine. The documentation says that all the storage zone/permission mapping should stay on the SAS modules which would obviously be the most worrying thing to lose.

Daz · 29-03-2009, 20:29

Sounds fun!

Tbh, I'd be shouting very loudly at IBM to get a guy on site to sort it out, especially after the second one did the same thing.

Garp · 29-03-2009, 21:44

Sounds like you're dealing with some of the dodgy IBM guys. Whilst I've never used IBM myself I've supported Co-Lo customers that have them and they've said that IBM support can be a mixed bag, generally good but with a few really dodgy support techs that ruin the hard work of the majority.

29-03-2009, 18:08	#1
Chuckles '09 sexual conquests: 4.5 Join Date: Sep 2007 Posts: 1,075	IBM BladeCenter's Anyone here an expert with BladeCenter's? I've got a bit of a tricky question which I'll type out if anyone is familiar with them! __________________

29-03-2009, 18:24	#2
Daz The Stig Join Date: Jun 2006 Location: Swad! Posts: 10,713	Not familiar with IBMs, but had a good sniff around Dell's if that's any use? __________________ apt-get moo

29-03-2009, 18:44	#3
Chuckles '09 sexual conquests: 4.5 Join Date: Sep 2007 Posts: 1,075	Probably specific to IBM this, but I'll explain anyway. Got 2 Blade Center S's on 2 different sites. IBM released a firmware update (2.48C) for the AMM (Advanced Management Module) which was marked as critical. I updated one, no problems at all. The second however didn't come back after the AMM restart. The blades however were fine. I noticed from the DHCP server that the AMM had picked up an address from there which it shouldn't as it's static. This made me wonder whether it had somehow reset to defaults. I took it out the LAN and plugged it into my macbook (which I'd assigned a suitable IP to connect to the default IP of 192.168.70.125). I could connect to the webadmin page using the default IP so I thought I could just reset everything. Unfortunately, I couldn't login (Just got incorrect username/password) using either an account I created, the renamed default account or the default account with the default password. Logged a call with IBM who agreed to send out a replacement AMM. I swapped them out (they are hotswappable) and I could connect again. Unfortunately, the AMM wouldn't recognise any blades, I/O modules or anything in the hardware VPD. It also couldn't detect the temperature and so put a warning light on the chassis and blew the fans at 100%. It did the same even after 3 restarts via the web interface. I tried updating the firmware to the latest again and guess what? The IP reset to default and all the accounts were locked out again The status light did go back to green which indicates that since the FW update, it can read in the blade info and temp sensors etc. This is my first support request with IBM and to be honest, they aren't a patch on Dell and don't seem to know as much about their hardware than I do, and I've only got about 4 months experience. I'm going to carry on the support log and have updated the situation but I'm not sure they are going to be of much help. All I can think of is get them to send another AMM and update the firmware revisions 1 at a time until I find a version that can read the VPD but doesn't screw up and reset to defaults. Thankfully during all this time, the blades themselves have all stayed up and running fine. The documentation says that all the storage zone/permission mapping should stay on the SAS modules which would obviously be the most worrying thing to lose. __________________

29-03-2009, 20:29	#4
Daz The Stig Join Date: Jun 2006 Location: Swad! Posts: 10,713	Sounds fun! Tbh, I'd be shouting very loudly at IBM to get a guy on site to sort it out, especially after the second one did the same thing. __________________ apt-get moo

29-03-2009, 21:44	#5
Garp Preparing more tumbleweed Join Date: Jun 2006 Location: Hawaii Posts: 6,038	Sounds like you're dealing with some of the dodgy IBM guys. Whilst I've never used IBM myself I've supported Co-Lo customers that have them and they've said that IBM support can be a mixed bag, generally good but with a few really dodgy support techs that ruin the hard work of the majority. __________________ Mal: Define "interesting"? Wash: "Oh, God, oh, God, we're all gonna die"?