Persistent linkage SP and blade

[Walter Dey]

Customer has SP which during association specifies chassis nr. / blade slot.

OS installed on local disk !

Is there a feature, which keeps this association, even in case the SP is disassociated ? so when associated again, will map to the same blade.

Yes, I know, that server pools with one blade per pool would do it. That's an ugly solution.

[Qiese Dides]

Walter,

That is one of the correct ways you could do it (server pool route).

So just to clarify the problem at hand. You are wanting to disassociate a service profile from a server but want only that service profile to be able to be associated with that server?

I want to make sure I understand the problem fully before answering with another solutions.

Regards,

[Walter Dey]

Hi Qiese

Yes, customer would like to have SP configuration, which maps to a certain chassis and slot, independent if it is associated or not associated.

Thanks

Walter.

[Qiese Dides]

Okay that makes sense now. The server pool method is the only one I know of and as you said it is quite nasty. That is a unique request he is asking about let me do some more research and if I can't find any other solutions I can go ahead and create a bug request to have that availability possibly included in later patches.

If you can give me some time, I will do some research into this.

Regards,

Qiese Dides