C7000 chassi unknown device in empty slot1

[Cederberg]

Hi.

We have a problem with one of our C7000 chassies.

The problem we have is that the chassi thinks there is a server connected to slot1 but all server bays are empty. We have tried everything we could think of but the only change we have achieved is from the chassi thinking a specific server is sitting in slot1 to an unknown device sitting in slot1.

The advice we got from HP was that a ebipa adress had stuck and that we should try booting another server in the slot and that should solve our problem. The only thing that achived was that the chassi thought that server sat in slot1 when we removed it instead of the server that sat there before.

We have tried the following.

*The whole chassi has been powerless.
*Upgraded the OA firmware to 2.60
*reset the OA to factory defaults
*booted a fully updated blade in the slot and removed it, Same error.
*disabled the ebipa for server slots.
*reseting the efuse on the slot.
*Failing the redundant OA's back and forward.

This makes me belive that it's a hardware fault rather then a software one. The slot seems to work fine when a server is connected to it but seems doesn't cut it when we put a server into production.

Any suggestions?

[Torsten.]

A screenshot would be nice.


BTW, new OA firmware 3 is there.

[Cederberg]

Here's a screenshot.

I know about the new firmware but HP hasn't published enogh info on firmware dependencies and there has been a few threads here with problems with that firmware so for now I won't upgrade to that version.

[Julian Stenning]

I had a similar issue, although my unknown device was in Bay 16.

I tried anything logical as you have, but the only fix was to actually put a device in that slot. The device works fine.

As I type I realise I haven't tried removing the device to see if the problem comes back.
Julian.

[The Brit]

Following on Julians comment:

Why do you care?. I know that it is aesthetically annoying, but if it recognises a new server which is installed in the slot, and performs as advertised when there IS a server present, who cares.

Dave.

[Cederberg]

Well. Yes because it's annoying and because there is something wrong. It might work fine to run a server in the slot at the moment but the fact that it's there proves that something is wrong in the chassi and why risk something worse happening in the future when I can take this early warning sign and do something about it.

And after all the things i've tried it would appear to be a hardware fault so I wouldn't leave that to chance.

[gregersenj]

Open a call at HP, and have them fix the problem.

Seem like you have tried everything.

Could be a bad backplane, OA or OA sleeve.

BR
/jag

[Cederberg]

Hi.

I have a case at hp they havn't called me back yet. And I thought that maybe someone else have had this problem before and knew what it was.

[gregersenj]

I have never seen that, nor has my colleage, I asked prior to my post.

But please report back.

BR
/jag

[Trygve Henriksen]

Have you verified that nothing is using the IP-address set up for the ILO2 connection for that slot?
(I have no idea what would happen if an external device used the same address, and I have no intention of finding out, either. )